This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Using Rational Application Developer to generate a web service proxy for a web services application

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
You can use the Rational® Application Developer integrated development environment to generate a web service proxy for your web services client application.

Before you begin

Before generating a web service proxy, you must have previously exported the WSDL and XSD files that describe the BPEL process or human task web services interfaces from the WebSphere® environment and copied them to your client programming environment.

About this task

Topic scope: This topic applies to the following Business Process Choreographer web services interfaces:
  • HTTP transport layer
  • JMS transport layer

Procedure

  1. Add the appropriate WSDL file to your project:
    • For BPEL processes (HTTP and JMS transport layers):
      1. Extract the exported file BPEContainer_nodename_servername_WSDLFiles.zip to a temporary directory. Do not change the contents of this directory, and be aware that only the following WSDL and XSD files are used for the web service proxy generation for interactions with BPEL processes:
        • BFMJAXWSService.wsdl (HTTP) or BFMJMSService.wsdl (JMS)
        • BFMJAXWSInterface.wsdl
        • BFMJAXWSCallbackService.wsdl
        • BFMJAXWSCallbackInterface.wsdl
        • BFMDataTypes.xsd
        • BPCDataTypes.xsd
        • wsa.xsd
      2. Import the subdirectory META-INF from the extracted directory.
        • For HTTP, the directory is: BPEContainer_nodename_servername.ear/bfmjaxws.war
        • For JMS, the directory is: BPEContainer_nodename_servername.ear/bfmjaxwsjms.jar
    • For human tasks (HTTP transport layer only):
      1. Extract the exported file TaskContainer_nodename_servername_WSDLFiles.zip to a temporary directory. Do not change the contents of this directory, and be aware that only the following WSDL and XSD files are used for the web service proxy generation for interactions with human tasks:
        • HTMJAXWSService.wsdl
        • HTMJAXWSInterface.wsdl
        • HTMJAXWSCallbackService.wsdl
        • HTMJAXWSCallbackInterface.wsdl
        • HTMDataTypes.xsd
        • BPCDataTypes.xsd
        • wsa.xsd
      2. Import the subdirectory META-INF from the extracted directory: TaskContainer_nodename_servername.ear/htmjaxws.war.
    A new wsdl directory and subdirectory structure are created in your project.
  2. Select the BFMJAXWSService.wsdl or the BFMJMSService.wsdl file in the newly-created wsdl directory.
  3. Right-click and choose Web services > Generate client.

    Before continuing with the remaining steps, ensure that the server has started.

  4. On the Web Services window, click Next to accept all the defaults.
  5. On the WebSphere JAX-WS Web Service Client Configuration window, click Finish to accept all the defaults.
  6. Optional: For the HTTP transport layer only: Redo steps 2 to 5 of this procedure with HTMJAXWSService.wsdl and overwrite all the files if you are prompted.

Results

A web service proxy, made up of a number of proxy, locator, and JAXB classes, is generated and added to your project.