Inbound Web Services

The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding.

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.

To create a new Inbound Web Service record

1. From the application-level menu, choose View > Site Map > Web Services Administration> Inbound Web Services view.

2. In the Inbound Web Services list applet, create a new Inbound Web Services record.

1. Enter the namespace for your organization's Web Services in the Namespace column.

2. Enter the name of the inbound Web Service in the Name column.

3. Select Active or Inactive in the Status field.

NOTE: If the Web Service is inactive, then the external applications cannot invoke the Web Service. If the status is changed, the server component running the inbound transport, such as HTTP, requires a restart for the change to take effect.

3. Enter a description of the Web Service in the Comment column.

4. Create a new inbound service port record in the Service Ports list applet.

1. 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 workflow 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 to publish the Web Service on.

8. Enter the URL or queue to publish the Web Service on.

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

• The format to publish over EAI MQSeries or EAI MSMQ Server transports is:

mq://send receive service point name@policy name

msmq://queue name@queue machine name

• The URL format to publish over HTTP is:

http://webserver/eai_lang/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=username&Password=password

Where:

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

webserver is the machine name of the Siebel Web Server.

username is the Siebel user to execute the request.

password is the password of the Siebel user.

NOTE: The Siebel application supports only one type of binding, SOAP_RPC, for each Inbound Web Service.

5. Enter a description of the Port in the Comment column.

6. In the Operations list applet, create a new operation record for the new service port you created in Step 4 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.

• Enter the name of the Web Service operation.

• Select the name of the business service method in the Business Service Method column to complete the process.

NOTE: The Business Service Method column defaults to RunProcess if you have chosen Workflow Process in Step 4 as the Type for your Service Port.

Generating a WSDL File

Once you have created a new Inbound Web Service record you can generate a WSDL document, as described in the following procedure.

To generate a WSDL file

1. Choose the inbound Web Services you want to publish and click GenerateWSDL.

A WSDL file is generated that describes the Web Service.

2. Save the generated file.

3. Import the WSDL to the external system using one of the following utilities.
• In VisualStudio.Net, use the wsdl.exe utility—for example, wsdl.exe /l:CS mywsdlfile.wsdl.
• In Apache's AXIS, use the wsdl2java utility—for example, java org.apache.axis.wsdl.WSDL2Java mywsdlfile.wsdl.
• In IBM's WSADIE, add the WSDL file to the Services perspective and run the Create Service Proxy wizard.

NOTE: These utilities only generate proxy classes. Developers are responsible for writing code that uses the proxy classes.