Special considerations for deploying COBOL SOAP services on IBM i

Deploying COBOL SOAP services on IBM® i requires that you generate outputs for both Java™ and COBOL. For an overview of the generated output and the runtime architecture, see “Overview of EGL support for SOA.”
Your task has two aspects:
  1. Generate the service to COBOL by using a build descriptor that could also be used to generate a COBOL program. The build descriptor options include genDirectory, destDirectory; destHost; prep; and, in most cases, destUserID and destPassword. Set the system option to iseriesc.
  2. Expose the logic as a SOAP service:
    1. Specify an entry in the Service Deployment tab of the EGL deployment descriptor editor, ensuring that the service logic will be deployed as a SOAP service.
    2. Use a build descriptor to set the deployment target. In this case, you use a build descriptor for the Java components. The build descriptor options include genProject, serverType, j2ee, and JEELevel. Again, the value of the system build descriptor option is iseriesc.
    3. To fulfill the deployment step, do as follows: right-click the deployment descriptor or an enclosing project and then click the Deploy option.

You can use a single build descriptor for both the Java and COBOL components. However, you might have multiple services, each of which is being deployed to a separate web archive (WAR) file. In this case, write a Java-related build descriptor for deploying each service and a single COBOL-related build descriptor for generating the COBOL outputs.

As noted in “Introduction to EGL generation and deployment,” your use of an EGL deployment step can save you time, but you have the option of generating all components and avoiding the deployment step altogether.


Feedback