In WSO2 3.0, I am not able to open the carbon component.
https://{localhost}:9443/carbon
Related
Some times ago, I used Alfresco 5.2 CE. When I needed to develop some kind of customization, I used the Alfresco Maven SDK with three different Maven archetypes, it was:
Alfresco Repository AMP;
Alfresco Share AMP;
Alfresco all-in-one (AIO).
By using this SDK I developed AMP files that overlaid on either the alfresco.war or share.war by using the module management tool (MMT):
...
java -jar bin/alfresco-mmt.jar install amps/some-customization-share.amp tomcat/webapps/share.war -force
java -jar bin/alfresco-mmt.jar install amps/some-customization-repo.amp tomcat/webapps/alfresco.war -force
...
Now I am using Alfresco 4.2.2 Enterprise and looking for the right way to do the same things that I did with Alfresco 5.2 CE.
Let's say, I want to develop a two tier Spring Surf customization that can remotely connect to different repositories. Or, for example, I need to develop a new Spring Surf page for a site, or just make some little changes in some FTL-template.
What is the right way? Is there a similar SDK for Alfresco 4.2.2 Enterprise?
I would be very grateful for the information. Thanks to all.
The Maven-based Alfresco 3.0 SDK is compatible with Alfresco 4.2, both Enterprise and Community Edition.
Is there any plan to support .NET Core in the near future? I mean, without refactoring my bot code. There are still components not compatible with it.
Yes, it is planned and in the works. You can follow the topic on this related GitHub issue: [Feature Request] Porting to .NET core #572
Update 2017-10-26:
Bot Framework team is working on a complete rewrite of BotBuilder SDK (v4) which will be fully compatible with .NET Core.
Update 2017-12-14
Bot Builder v3 - New Bot Connector support for ASP.NET Core 2.0 and 1.1 has been released on NuGet!
We’ve released two new nuget packages for the Microsoft Bot Connector to support .NET Core 2.0:
Microsoft.Bot.Connector.AspNetCore.1.1.3.2.nupkg
Microsoft.Bot.Connector.AspNetCore.2.0.0.3.nupkg
The above packages each target ASPNetCore 1.x and ASPNetCore 2.x respectively, and provision authentication for your bot. They must also use Microsoft.Bot.Connector.3.12.2.4 or higher.
I recently downloaded the 5.3 RC1 distribution of IS and now I want to set it up to be a key manager for WSO2 API Manager 1.10. I checked the Wilkes p2 repo for a compatible version of the key manager to be installed as a feature, but I can't find any. Neither of versions 5.0.3 and 6.0.4 are installable with the 5.3 RC1 version of WSO2 IS. Is there any way I can proceed from this point, or do I have to wait for the GA release and hope for the compatible key management feature to appear in the p2 repo?
Furthermore, will it even be possible to use the combination of APIM 1.10 and IS 5.3, or will 5.3 require an update of APIM or that IS 5.3 be treated as a 3rd party key manager?
Finally, we managed to sort this out. To start with, WSO2 IS 5.3 was released Jan 11, 2017, but it took a few weeks after APIM 2.1.0 was relased that the required feature (Key Manager feature v 6.1.66) appeared in the p2 repository. Then we used the instructions in the documentation for API Manager to configure Identity Server as key manager.
But that only did part of the work since there are incompatibility issues at database and service levels, so we had to fix those. A description of what we did to get APIM 1.10.0 to work with IS 5.3 can be found at Github.
I'm using WSO2 developer studio for building BPEL workflow. My requirement also needs FTP/SFTP functionality to be added to the BPEL project. Could anyone advice if there is any feature pack that i can add to my WSO2 developer studio installation to get this functionality.
I am creating the >car file using Developer studio and deploying using Wso2 Carbon server4.0.
When i am deploying always getting the older versions. Some times the server not properly deploying the car. And also how to build the project to get the latest changes.
Please suggest me a better procedure creating and deploying the car file.
I am using Wso2 esb 4.7.0 version,
Developer studio 3.2 version.
Refer to the following documentation.
http://docs.wso2.org/display/DVS310/Deploying+and+Debugging