Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > Invoking Siebel Web Services Using an External System >

Publishing Inbound Web Services

You can create and publish an inbound Web Service using the Inbound Web Services view, as illustrated in the following procedure. You can then use the new Inbound Web Service when generating a WSDL document.

NOTE:  If publishing an ASI as an inbound Web Service, make sure that ASI is enabled for external use in Siebel Tools.

To create an Inbound Web Service record

  1. Navigate to the Administration - Web Services screen > Inbound Web Services view.
  2. In the Inbound Web Services list applet, create an Inbound Web Services record:
    1. Enter the namespace for your organization's Web Services in the Namespace column.

      NOTE:  This step is required for generating various XML documents.

    2. Enter the name of the inbound Web Service in the Name column.
    3. Select Active in the Status field to enable external applications to call the Web Service.

      NOTE:  If the Web Service is inactive, then the external applications cannot invoke the Web Service without clearing the cache.

    4. (Optional) Enter a description of the Web Service in the Comment column.
  3. Create an inbound service port record in the Service Ports list applet:
    1. Click New and enter the name of the port in the Name column.
    2. Pick the type of object published.

      If the required type is not available, add a new type following Step c through Step f; otherwise, move to Step g.

    3. Click New and select the implementation type (Business Service or Workflow).
    4. Select the implementation name (the business service or business process that implements the port type).
    5. Enter a name for the new type in the Name field and click Save.
    6. Click Pick in the Inbound Web Services Pick Applet to complete the process of adding a new Type.
    7. Select the protocol or transport that will publish the Web Service.
    8. Enter the address appropriate for the transport chosen:
      • For the HTTP Transport, enter an HTTP address of the Web Service to be called, for example:

    • For the JMS Transport, enter the following:


    • For the Local Web Service transport, enter the name of the inbound port.
    • For the EAI MSMQ Server transport, enter one of the following:



    NOTE:  When publishing using EAI MQSeries, EAI MSMQ, or EAI JMS, you cannot generate WSDL files.

    1. Select the binding that will publish the Web Service.

      NOTE:  RPC_Encoded, RPC_Literal, and DOC_Literal styles of binding are supported for publishing Web Services.

    2. Enter a description of the Port in the Comment column.
  4. In the Operations list applet, create a new operation record for the new service port you created in Step 3 and want to publish:

    NOTE:  Only the operations created in this step will be published and usable by applications calling the Web Service. Other business service methods will not be available to external applications and can only be used for internal business service calls.

    1. Enter the name of the Web Service operation.
    2. Select the name of the business service method in the Method Display Name column.

      NOTE:  The Method Display Name column defaults to RunProcess if you have chosen Workflow Process in Step 3 on page 77 as the Type for your Service Port. However, you can change this to another name.

    3. Select the authentication type from the drop-down list.

      For more information on using the Username/Password Authentication Type, see About RPC-Literal and DOC-Literal Bindings.

Integration Platform Technologies: Siebel Enterprise Application Integration Copyright © 2008, Oracle and/or its affiliates. All rights reserved. Legal Notices.