Adding web-service deployment entries in the EGL deployment descriptor

You can update the EGL deployment descriptor with details that are needed to deploy SOAP and EGL REST-RPC services.
  1. Open the EGL Deployment Descriptor editor by double-clicking an EGL deployment descriptor. For details about creating the file, see “Creating an EGL deployment descriptor.”
  2. Click Service Deployment. The Web Service Deployment tab is displayed.
  3. Click Add. The Add Web Services window opens.
  4. Select or clear the check boxes that indicate whether to deploy a SOAP service, an EGL REST-RPC service, or both.
  5. The main task is to add Service parts from the EGL service parts found list to the EGL service parts to be generated as web services list. You can select all of the listed Service parts by clicking Add all. Also, you can select one or more services from the EGL service parts found list and then click Add. The selection occurs in either of two ways:
    • Type the beginning of a name into the Locate EGL Service Parts field. Specifically, type the beginning of the package name (if any) or the beginning of the Service part name (if the part is in the default package). You can use the following wildcard characters: a question mark (?) to accept one character of any kind, or an asterisk (*) to accept a series of characters of any kind.
    • Alternatively, select a service name in the EGL service parts found list by clicking the name. To select multiple names, press the Ctrl key and click the names. To select a contiguous set of names, click a name, press the Shift key, and click the last name of interest.

    You can use that last set of alternatives to select Service parts in the EGL service parts to be generated as web services list. You can then move the selected names back to the EGL service parts found list by clicking Remove. Also, you can move all of the names back to that list by clicking Remove All.

  6. When the list of Service parts in the EGL service parts to be generated as web services list reflects your intent, click Finish. The Web Service Deployment tab is available again, with an entry for each Service part being deployed.
  7. To change the output type for a given Service part, click an entry in the Services Deployment grid, in the Generate column, and make a different selection.
  8. To change values for a given Service part, click an entry in the Services Deployment grid.
    For SOAP services, your options are as follows:
    • If you want to generate a WSDL file, clear Use Existing WSDL file. The value in the Style field indicates an aspect of the message transmitted to the service. Select document-wrapped, which is the default, unless rpc is required by the service requesters.
    • If you want to use an existing WSDL file, select Use Existing WSDL file and specify three details:
      • In the WSDL File field, specify the location of the WSDL file, which must be in the EGL build path, in an EGLSource folder. You can browse to access the file.
      • In the WSDL Service field, specify the WSDL file service element that corresponds to the service. In most cases, accept the value that the workbench retrieves from the WSDL file.
      • In the WSDL Port field, specify the WSDL file port element of interest. In most cases, accept the value that the workbench retrieves from the WSDL file.
    For most EGL REST-RPC services, your options are as follows:
    • Select the Stateful check box if you want to maintain stateful behavior when you deploy an EGL REST-RPC service to access a UI program or a program on IBM® i. For a description of these capabilities, see the following topics:
      • “Accessing IBM i programs as web services: overview”
      • “UI program and the gateway service”

      When you deploy other EGL REST-RPC services, the behavior is not stateful.

    • In the URI field, identify the low-level qualifier for the address used to access the REST service. In most cases, accept the name of the Service part, as provided by the workbench.
    Beyond those options are the following choices:
    • If you are deploying the service to IBM i or CICS® and need to specify a sharable protocol, select a value from the Protocol list. For details, see “Sharable protocols.”
    • If you are deploying the service to CICS, you can also specify a value in the CICS URI field: That value is the relative location of the service, after the host name and port number. The default is /services/serviceName, where serviceName is the name of the service.

Feedback