Deploying the WSP

This section provides two deployment options, either on Talend ESB or on Tomcat.

Deploying the WSP to Talend ESB (OSGi)

About this task

During the previous build process Maven installed the application's bundles in your local Maven repository. It is from there that Talend ESB will load bundles and activate them. To deploy the web service provider on Talend ESB:

Procedure

Start Talend ESB from the command-line, from the container/bin folder, run either ./trun (Linux) or trun.bat (Windows). When the container starts up, you will see a short introduction (similar to the one below) followed by the OSGi console command prompt:
```
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown TRUN.

karaf@trun>
```
From the Talend ESB karaf prompt, enter:
```
install mvn:org.talend.cxf-examples.dev-guide-wsdl-first/dev-guide-wsdl-first-service/
```
For the above bundle, mvn refers to the protocol (http:// and file:/ are other common alternatives), while the remaining portion refers to the Maven group ID, artifact ID, and version separated by forward slashes.

After Talend ESB reports the bundle ID, next enter start <bundleID>. Typing list afterwards from the Karaf prompt should show that the web service provider has successfully started. If any failure is indicated, check the container/data/log file for any error information. Prior to calling the client in the next step, make sure you can bring up the web service's WSDL at http://localhost:8040/services/doubleit?wsdl.

Results

For more information on working with Talend ESB including its OSGi commands, see Using console commands.

Deploying the WSP to Tomcat (WAR archive)

Make sure you've configured Tomcat and Maven as discussed in Download Tomcat 7.x (optional) and Download Maven 3, and that you've updated the soap:address element in the WSDL as discussed in Creating the WSDL. If so, starting Tomcat and running mvn tomcat7:redeploy from the project root folder should deploy the web service provider onto Tomcat. As a check to make sure the WSP has loaded successfully, make sure you can view the WSDL from a browser at http://localhost:8080/doubleit/services/doubleit?wsdl before running the client. If it cannot be viewed, check the Tomcat logs (logs/catalina.out is usually the most helpful) for error messages to help with troubleshooting.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here