Bookshelf Home | Contents | Index | PDF     

Integration Platform Technologies: Siebel eBusiness Application Integration Volume ll > Web Services > Consuming External Web Services Using Siebel Web Services >

Outbound Web Services Administration

The WSDL Import Wizard exports the data to a file that you must import to the run-time database (the Web Services address) using the Outbound Web Services screen.

To import run-time data about external Web Services

  1. Restart the Siebel Server (or Siebel Mobile Web Client) with a recompiled version of the SRF file that includes the new objects created by the Web Services Import Wizard.

    NOTE:  You do not need to update your SRF file at design time. However, the service definition must exist in the SRF file during run time.

  2. From the application-level menu, choose Navigate > Site Map > Administration - Web Services > Outbound Web Services view.
  3. In the Outbound Web Services list applet, click Import to bring up the EAI Web Service Import dialog box.
  4. Specify the export file created by the Web Services Import Wizard.
  5. Click Import to import the Web Service definition into the database.

WSDL does not provide native bindings for EAI MQSeries and EAI MSMQ transports. If your business requires you to pick up messages using these transports, you can manually create an outbound Web Service definition and update a corresponding business service in Siebel Tools to point to that Web Service. The following procedure describes this process.

To manually create a new outbound Web Service

  1. From the application-level menu, choose Navigate > Site Map > Administration - Web Services > Outbound Web Services view.
  2. In the Outbound Web Services list applet, create a new record.
    1. Enter the namespace of the Web Service in the Namespace column.
    2. Enter the name of the Web Service in the Name column.
    3. Select Active or Inactive in the Status field.
    4. Enter a description of the Web Service in the Comment column.

      NOTE:  When importing an external Web Service, you do not need to specify the proxy business service, integration objects, or the run-time parameters.

  3. In the Service Ports list applet, create a new outbound service ports record.
    1. Enter the name of the Web Service port in the Name column.
    2. Select a transport name for the protocol or queuing system for the Transport.
    3. Enter the address appropriate for the transport chosen.
      • Enter the URL or queue that will publish the Web Service. The URL format to publish over HTTP is:

    http://webserver/eai_anon_lang/start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute

    Where:

    webserver = the machine name of the Siebel Web Server.

    lang = the default language of the Object Manager to handle the request.

    • The format to publish over JMS transport is:

    jms://queue name@connection factory

    Where:

    queue name = The JNDI name of the queue.

    connection factory = The JNDI name of the JMS connection factory.

    NOTE:  The JNDI name will vary depending upon the JMS provider and your implementation.

    • For the Local Web Service transport, enter the name of the inbound port.
    • The format to publish over EAI MQSeries or EAI MSMQ transports is:

    mq://queue name@queue manager name

    msmq://queue name@queue machine name

    Where:

    queue name = The name of the queue that is specified by either the EAI MQ Series or the EAI MSMQ transports at the time of their design.

    queue manager name = The name of the EAI MQSeries Transport queue manager.

    queue machine name = The name of the machine that owns the queue specified by the physical queue name for the EAI MSMQ Transport.

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

    • For the Local Workflow or the Local Business Service transports, enter the name of a Business Process or Business Service that should be called.
    1. Select the binding that will publish the Web Service.

      NOTE:  Release 7.7 supports RPC_Encoded, RPC_Literal, DOC_Literal, and Property Set styles of binding.

      Property Set Binding should be used when the input Property Set to the proxy service is forwarded without changes to the destination address. This is intended primarily for use in combination with Local Workflow or Local Business Service transport to avoid overhead of processing XML.

    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.
    1. Select the name of the business service method in the Method Display Name column to complete the process.
    2. Select the authentication type from the drop-down list.

      NOTE:  For more information on using the Username/Password Authentication Type, see About Web Services Security Support.

  5. Generate the WSDL file. For details, see To generate a WSDL file.

Once you have created your outbound Web Service, you need to update a corresponding outbound proxy business service in Siebel Tools to point to that Web Service. This associates the outbound proxy business service and the outbound Web Service. The following procedure outlines the steps you need to take to accomplish this task.

To update an outbound Web Service proxy business service to point to an outbound Web Service

  1. Start Siebel Tools.
  2. Select the outbound Web Service proxy business service you want to use to call your outbound Web Service.
  3. Add the following user properties for this business service and set their values based on the outbound service port of your Web Service:
    • siebel_port_name
    • siebel_web_service_name
    • siebel_web_service_namespace
    
Integration Platform Technologies: Siebel eBusiness Application Integration Volume ll