Check In a New Version of a WSDL

You can check in a new version of a WSDL from the Deployment menu.

About this task

To check in a new version for a WSDL:

Procedure

  1. From the Deployment menu, select Web Services > WSDL Check In.
  2. In the WSDL page, under List, select All from the Alphabetically drop-down list, click Go!
  3. In the WSDL page, click source manager next to the WSDL for which you want to check in a new version.
  4. In the WSDL Source Manager page, click check out next to the WSDL.
  5. When prompted with the following message, click OK to check out the file or click Cancel to check out a read-only copy of the file:

    Click OK to lock the file for editing. During the check in process, you can release the lock. Click Cancel to check out a read-only copy of the file.

  6. In the WSDL Source Manager Page, next to Check in a new version of this WSDL, click Go!
  7. In the Naming: WSDL Transport Binding Settings page that is displayed, select a protocol to use as the transport binding to send the SOAP message to the Web service provider and click Next.

    Field

    Description

    Default Transport (HTTP)

    Uses HTTP as the transport binding. This option generates the dynamic service and configures the associated business processes (including message processing and security services) and URIs automatically. Choose for backward compatibility.

    Uses HTTP services and SOAInbound and SOAOutbound Services internally.

    Other Transport (HTTP/HTTPS)

    Uses HTTP or HTTP with SSL as the transport binding. This option creates the dynamic service for the checked-in WSDL.

    Configure the business process as follows:

    DynamicService --> SOAOutboundSecurity Service (optional) --> SOAOutboundMessageProcessingService --> Transport --> SOAInboundMessageProcessingService --> SOAInboundSecurityService (optional)

    Uses either an HTTP Server adapter or a new HTTP Server adapter instance (SOA SSL Http Server adapter). You may need to manually configure services.

    For more information on configuring services, refer to the services documentation.

    By using this option, you should:
    • Use the GPM to configure the SOAOutboundMessageProcessing and (if desired) the SOAOutboundSecurityService manually at the business process level for use after Dynamic Service Generation generates the SOAP message. You must provide an end point address and port to use to send the SOAP message to the Web service provider.
    • Configure the SOAInboundMessageProcessing and (if desired) SOAInboundSecurityService for use after the SOAP message is sent to the Web service provider.
  8. In the Naming: Select WSDL page that is displayed, enter information in the following fields and click Next.

    Field

    Description

    WSDL filename(.wsdl)

    (Required) Enter the name of the WSDL filename or browse and select the WSDL from your system.

    Check-in Comments

    (Required) Enter any comments necessary. For example, you can enter a version number or whether this WSDL is for test environment or production environment.

    Encoding Type

    Select the encoding type from the drop-down list. Default is UTF-8.
  9. In the WSDL: Set Default Version page, select the WSDL under the OTHER Versions section.
  10. In the Confirm page that is displayed, perform the following tasks:
    1. Select Enable for Business Processes check box if you want to use this WSDL for use with business processes.
    2. Select Release the lock on the file check box to unlock the WSDL file.
  11. Click Finish.