Exposing a Business Process as a Web Service

Prerequisite: Installation of EAServer 5.0, which is provided with Unwired Orchestrator.

After a business process has been deployed, it can be considered for use as a Web service. All runtime service instances that can be used as a Web service are listed in the Business Process Web Services servlet GUI. For information about which services can be considered as Web services, see characteristics of a business process that can be used as a Web service.

To expose a business process as a Web service:

1. Open a browser.

2. Enter the following URL:
   http:/<YOURHOST>:<8080>/iobpws/                
   YOURHOST is replaced with the host name of the machine where Unwired Orchestrator Runtime libraries are installed and 8080 is the port for the EAServer hosting the Business Process Web Services servlet GUI.
    

3. Under Services, expand the desired service from the list of all deployed instances.
    

4. Expand a service.
   If the process has exposable notifications, one or more nodes appear beneath the process node. When you select one of these nodes, a drop-down list displays all of the possible outputs for this notification.
    

Note: You can select more than one notification from a business process but each notification can be used as a public operation only one time.  

5. Select an output to be used by the Web Service.
   If you select the default of None for the output, the Web service is treated as a one-way operation. If you select a specific output, the operation is treated as a request reply operation.  

Notes:
If the process does not have any exposable notifications, you will not be able to expose the business process as a web service.
Business processes for Web services can expose only business processes that have valid namespaces. Namespaces generated when importing a schema that contains a complex type but does not have a namespace are not valid. These invalid namespaces start with the following:
http://schemas.sybase.com/ebd/eai/es/ot/
http://www.sybase.com/ebd/eai/es/db/wsdl/.

6. Enter a value for Operation Name.
   In the generated WSDL, this value is used to name the operation that corresponds to the exposed business process.

7. In the Ignore original transports? checkbox:

• If processing should ignore the originally configured transports for the business process and listen only to the Web interface, check the box.

• If processing should listen to both the originally configured transport as well as the Web interface, do not check the box.

Note: If you select Yes, the original error and no-hit transports are replaced by file transports named ERROR and NOHIT. The ERROR and NOHIT transports are automatically created in the instance runtime folder.

7. Enter a valid user name and password to access the EAServer JMS Queues.
   This user permission will be used to deploy the web service so it must have the authority to create JMS queues. This name will also be used by the engine to access the EAServer JMS Queues. The defaults are user = jagadmin and password = <blank>.

8. Click Deploy as a web service.
   The resultant files are deployed to a .WAR file in EAServer, and the Web interface is started.

9. Close the Successful deploy message window.
   A link to the generated WSDL in the internet explorer browser appears.

10. From the internet explorer browser menu, select Save as.

11. Save the WSDL, providing a descriptive name.
    You can now import the WSDL into the services folder of a UO project using the file-system option. The process can now be called using the new Web interface.

12. If you select Remove all web services, the Web interface is stopped and completely removed.

For more information about a business process as a Web service, go to Business Process as a Web Service.