I have deployed WSO2 API manager4.0.0 All-in-one on my vm, which was downloaded from WSO2 API Manager website, “click TRY IT NOW, and then click Zip Archive to download the API Manager distribution as a ZIP file”.
I could find component versions from pom.xml , which were under the path of \repository\deployment\server\webapps. Most of the war or jar were built from carbon-apimgt and identity-governance、identity-apps.
But I can't find where was the front version, I don't know what' difference between repo apim-apps and jaggery.
If apim-apps is the front source of apim, what's the version or tag it build from?
I am searching for a long time on net. But no use. Please help or try to give some ideas how to achieve this
UI source code was moved to apim-apps repository after the WSO2 APIM 4.0.0 release. So, if you want to access the UI source code of APIM 4.0.0 you have to refer to carbon-apimgt-v9.0.174. Following are the links to each portal.
Publisher Portal
Developer Portal
Admin Portal
I have created a project using Qt and I found the Repogen tool that cames with Qt.
In the official documentation says that I must host the repo in a server in order to receive updates or create an online installer. I tried using GitHub as a hosting but maintenance tool doesn't recognize it.
I added he repository url in the settings window of the maintenance tool pointing to the base repo path and then pointing directly to Updates.xml but the same error.
What kind of web server must I use to deliver the release files?
I resolve this issue, by creating a file service in Flask and using a free hosting to deliver files.
Seems like hosting in GitHub is not useful in that case.
I have a web application from which i have to invoke a WSO2 Admin service..
I am following this https://docs.wso2.com/display/IS570/Calling+Admin+Services
When I used wsdl2java , I got a zip file...When i opened it , it has just a pom.xml..
How can i use this? My web app is using Maven itself..But no clue how to use this pom.xml and invoke admin service? How to generate stub out of this pom.xml?
Once you build it with maven client stubs will be generated. See [1] as a sample. Any way client stubs are already available in nexus for released products.
EX: If I want to use client stubs for ChallengeQuestionManagementAdminService I can do it by adding maven dependency
<dependency>
<groupId>org.wso2.carbon.identity.governance</groupId>
<artifactId>org.wso2.carbon.identity.recovery.stub</artifactId>
<version>xxx</version>
</dependency>
[1] https://github.com/wso2-extensions/identity-governance/tree/master/service-stubs/identity/org.wso2.carbon.identity.recovery.stub
Bamboo supports shared credentials.
I would like to use these shared credentials to commit tags to git using the artifactory maven addon.
According to this ticket: https://www.jfrog.com/jira/browse/BAP-189 it should work.
I do however not know where to configure it.
We are using bamboo 5.14.3.1
Artifactory plugin 2.1.0
Was this feature removed?
I am trying to deploy my Spring MVC application on WSO2 Application Server by going to Main > Manage > Applications > Add > Web Applications and upload my Spring MVC's WAR file. The upload completed successfully, but I still can't run the web app itself. The error message just basically complaining it doesn't have org.springframework.
The same WAR file can be run on Apache Tomcat with no problem at all. All I did is dropping the same WAR file to \webapps, and it works.
Is there a special setting that needs to be configured to get Spring MVC run on WSO2 Application Server? I would assume WSO2 Application is also using Apache Tomcat, so why it won't run by just uploading the WAR file?
Thanks!
What is your WSO2 AS version ? please make sure to use latest AS 5.1.0 version. We have tested large number of Spring (including SpringMVC) based applications on AS 5.1.0, basically if something working on Tomcat it should be work on WSO2 AS too. If you still have issues on AS 5.1.0 please let me know.
I solved this issue by:
Upgrading WSO2 AS to latest version (5.1.0) as mentioned by Sagara Gunathunga. For some reasons, previous WSO2 AS doesn't take my JSTL templating (something like $ {blabla}). Only in 5.1.0 did the issue resolved. I start to wonder what this WSO2 is doing with its half-baked product.
Modify Maven POM file, specifically slf4j-api dependency. WSO2 has its own slf4j-api library and I have to set the scope of slf4j-api in my app to "provided" before deploying to WSO2. This solve the issue with unable to load all JavaScript files.
Downside for this is you will need the scope of slf4j-api to be "compiled" when you run this locally under regular Tomcat. Setting it to "provided" will not work under Tomcat. But in WSO2, the scope will need to be "provided" to run. So, there is manual work to change before deploying the application.
I did try to match the slf4j-api version to match what WSO2 and set the scope to "compile", but it still won't work. WSO2, for some bad reasons, can't use my app's compiled slf4j-api.
yes there is a separate workaround to deploy a spring service to wso2 appserver. Please follow [1] for instructions.
[1]. http://docs.wso2.org/wiki/display/AS510/Spring+Services
Thank you,
Dharshana
#stack247,
Well I'm from WSO2 and it's nice to hear that your JSTL issue is solved by now. But I completely disagree with " I start to wonder what this WSO2 is doing with its half-baked product" statement. You may know that spec like Servelt , JSP and JSTL having different versions and update it's version with time. Previous version of application server does not supported for latest JSP 2.0 and JSTL 1.2 specs hence you can't use application which depends on JSP 2.0 or JSTL 1.2 that was a known limitation but can't consider it as half-baked product due to that. This is very common nature with any software product and that's why we are actively developing, fixing issues, upgrading dependencies and frequently releasing new versions, also we are responding to community issues like this.
With Latest AS 5.1.0 release we officially support for Servelt 3.0, JSP 2.0 and JSTL 1.2 and any dependent applications too. When it come to logging case most of the application server having their own logging mechanisms and some cases it's required remove logging dependencies from applications.