By jason on Sep 20, 2009
Deploying apps from GlassfishESB v2.1 to GlassfishESB v3.
There's lots of new functionality being implemented for GlassfishESB v3 as part of the Fuji research project. However a very important consideration is that existing projects that run in the current release (v2.1) will continue to work in the next major release (v3).
This how-to shows how to take a simple BPEL project from GFESBv2.1 and deploy and test it in the latest milestone release of Fuji (M8).
- Start in the GlassfishESBv2.1 environment
- I already have a simple service assembly with a HTTP BC and a BPEL SE Service Unit
- The BPEL SU simply returns "Hello <string>" for whatever string is passed to it
- Run the unit test to show it working
- The Fuji runtime does not yet support Application Variables, so I replace the variable with the hardcoded value for the HTTP Port
- Rebuild the application with the hardcoded value so it can be deployed to the Fuji runtime
- Stop the GFESBv2.1 server so the Fuji Server can be started and use the same ports.
- Milestone8 of Fuji requires the latest version of NetBeans, so start up NetBeans 6.7.1
- The Fuji Server is already installed and the plugins installed into NetBeans as described in the installation instructions.
- The current fuji installer doesn't include BPEL SE, so you'll need to download and install it separately (plus the saxon library it depends on)
- Start the BPEL SE and HTTP BC components
- Now install the zip file for our BPEL application Service Assembly.
- start the application
- Check the the same URL for the WSDL file to ensure the server is running and the service is available
- To test the project, I've installed the SOAPUI netbeans plugin.
- Create a SOAPUI project, point it to the service, and test.