Build and Deployment

The EAR file containing the web service wrapper is built by target websphereEAR (for WebSphere) or weblogicEAR (for WebLogic Server). The resulting EAR file is deployed in the same way as the normal application EAR file.

Note: The web services EAR file may be deployed into a different server to the application server. This server does not require any database or JMS resources.

In order for a third party to use an IBM Cúram Social Program Management web service, they need the WSDL which describes the web service. A WSDL document is produced for each webservice process class. The WSDL is generated at run time, and is therefore available only once the web service EAR has been deployed onto an application server. The WSDL is obtained via HTTP from the server. The URL of the WSDL is determined by the following factors:

The HTTP port of the server onto which the EAR file has been deployed;
The application name;
The process class name.

For example, if the application is named Curam and a class named MyWebServiceBPO has been deployed as a web service, and the web service server is listening on port 9082 on server testserver then the WSDL for this web service can be obtained from http://testserver:9082/CuramWS/services/MyWebServiceBPO?wsdl. In addition, a list of all web services available on this server can be seen by going to http://testserver:9082/CuramWS/services.

Note: The WSDL for a web service is not available at development time. It is generated at run time by Axis 1.4 once the web service has been deployed.