the about-page of wso2ei 6.1.1 (https://docs.wso2.com/display/EI611/About+this+Release)
mentioned the possibility to develop and especially to deploy msf4j apps in wso2ei:
From WSO2 EI 6.1.0 onwards, it does not ship the functionalities of
WSO2 Application Server (AS). However, you can develop applications
using MSF4J, JAX-RS or JAX-WS technologies and deploy in WSO2 EI. If
you already have applications in WAR or AAR formats, use WSO2 AS 5.3.0
or Tomcat as the server to deploy web apps. Nevertheless, WSO2 still
provides complete development and production support for WSO2 AS.
I am very interested to do this, but unfortunally I can not find any information on this topic. I would be happy to receive information and links to this topic.
You can develop a service using MSF4J and deployed it with the MSF4J profile which is available with the WSO2 EI. Sample is mentioned in Doc 1
Highlevel steps would be
Develop the MSF4J service
Put that jar file in <EI_HOME>/wso2/msf4j/deployment directory
Start the MSF4J profile in EI <EI_HOME>/wso2/msf4j/bin/carbon.sh
Related
Like we use DeployPortlet.xml file to deploy portlet on webspehre portal server, is there a similar way to deploy web services on webspehere portal server
unless they are WSRP services you cannot using xmlaccess, you would need to use the websphere appserver commands for doing it, either using the automated deployment steps using the properties files and the deployment directory, or using wsadmin to deploy them
I am trying to implement an OSGI based JAX-WS WebService client on WebSphere Application Server(8.5.5). I created a web project in my RAD (Rational Application Developer) workbench and added the programming model as osgi.
After that I tried to create the webservice client from the available wsdl.
But I am getting the following error " The IBM WebSphere JAX-WS Web service runtime does not support Client projects with the OSGi Bundle facet."
Are you using JAX-WS on WebSphere Application Server traditional (i.e. not the Liberty Profile)? If so, then traditional does not support JAX-WS in OSGi Applications. The Liberty profile does support JAX-WS.
If not, then this could be a tools check that's no longer valid. I know the tools used to prevent you doing this when JAX-WS was not supported on traditional or Liberty. You could try using the latest WebSphere Developer tools from the Ecilpse Marketplace or https://wasdev.net/repo to create a simple test project to see if you hit the same problem.
I hope this helps.
Regards, Graham.
At a customer we use WAS to develop and run web apps. The problem is that WAS running locally is not the fasted web server.
With the release of Websphere Liberty Profile (WLP) it could be a good alternative to run on our local development environment.
Will Java apps developed on WLP run on a 'real' WAS server? Without changes??
Yes, Java EE applications developed on Liberty will run on WebSphere Application Server traditional without changes because both are Java EE compliant application servers. Because of it's composabilility, smaller size and faster starter startup time, developing applications on Liberty and deploying them on WebSphere Application Server traditional is a common paradigm and can provide a good development experience.
If you develop on Liberty with a goal to deploy on traditional WebSphere Application Server, and limit your applications to the EE6 web profile programming model (https://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.wlp.doc/ae/rwlp_feature_webProfile-6.0.html) your application is likely to run unmodified on traditional WebSphere Application Server.
The WebSphere Migration Toolkit can help answer some of theses kinds of questions by analyzing your application:
https://www.ibm.com/developerworks/websphere/downloads/migtoolkit/config.html
Do IBM WebSphere Application Server 7.0 have a web server plugin like in version 8.5? or in WAS7 we need IIS as a web server.
To add to what Gas has pointed out, if you intend to use a web server in front of your WebSphere Application Server (WAS) deployment, installing the WAS HTTP Plugin on the web server is a requirement.
All versions of WAS have this requirement and offer a plugin for the following web servers:
IBM HTTP Server (IHS)
Apache HTTP Server
Domino Web server
Internet Information Services (IIS)
Sun Java Web server
The plugin itself is available on the "Supplements" image for which ever WAS bundle you're licensed for. The following document provides the appropriate WAS v7 part numbers for each OS:
Download WebSphere Application Server Version 7.0 for Windows operating systems
The "Supplements" image is Download 3 in the list, and is a two part download.
Also, here is the Plugin install parent doc from the WAS v7 Knowledge Center:
Installing Web server plug-ins
Yes, every WAS version has Plugin for most major web servers (IHS, Apache, IIS). You need to download separate package, known as Supplements. There you will find WebSphere Plugins.
Is there a straightforward way to run WSO2 API Manager on Heroku? I've been through the basic Heroku docs on how to deploy Java applications and understand that process but it seems like jumping through hoops that maybe aren't needed.
I'd like to be able to simply upload the installed application (binary version of application) and a procfile that defines the bootstrap class file as the starting point.
Is this possible? Is there another way to get Java apps to run in Heroku without defining a pom.xml and having it build the application prior to deployment?
Thanks,
Dave
WSO2 offers the hybrid API model to deploy your WSO2 API gateway on Heroku and use WSO2 API Cloud to manage your APIs.
You can use WSO2 WSO2 Heroku Add-on which can be used as WSO2 API publisher and Store. Then use Heroku Button to deploy WSO2 API Gateway on Heroku.
More info: https://devcenter.heroku.com/articles/wso2apicloud
It looks like there is no straightforward way to run WSO2 API Manager on Heroku. I looked at how Java programs are run on Heroku and it seems your requirement cannot be achieved currently. Heroku seems to be depending on Maven projects.
WSO2 API Manager product is built from WSO2 Carbon platform, which is not a simple Maven Java project.
Heroku also runs the Java application on OpenJDK, which is not supported by WSO2 API Manager. Only Oracle JDK is supported as mentioned in Installation Prerequisites.
I hope this helps.