Siebel Order Management Guide > Integrating Order Management with Third-Party Product Availability Applications > Process of Setting Up Third-Party Product Availability Applications >

Configuring Web Services for Availability to Promise

Web services are used to direct the inbound and outbound messages to and from:

• The third-party ATP engine
• A demonstration script, which can be used to test your integration setup
• A middleware or integration server that will integrate with your fulfillment engine

You must make sure that the Web services are correctly configured.

This task is a step in Process of Setting Up Third-Party Product Availability Applications.

To configure Web services for availability to promise

1. In your Siebel Business Application, navigate to the Administration - Web Services screen, and then the Outbound Web Services view.
2. Select the row with External ATP Check in the Name field.
3. Verify that the fields in the Outbound Web Services list match those in the following table.

   Namespace	Name	Status
   http://siebel.com/asi/	External ATP Check	Active

4. In the Service Ports list, click New, and enter the following values in the fields of the new record.

   Field	Comments
   Name	Enter Default.
   Service Display Name	Enter External ATP Check.
   Transport	Select from the list. If you want to set up testing, for example when you are customizing applets or extending the ASI, then select Local Business Service.
   Address	When you select a transport, the field is populated with a template address. Edit the address according to whether you are sending the data to middleware or the ATP engine. If you want to set up testing, for example when you are customizing applets or extending the ASI, then enter ATP ASI Test. For more information, see Using the ATP ASI Testing Script.
   Binding	If a SOAP header is expected by the receiving application, then select SOAP_RPC. If you are using ATP ASI Test, then select Property Set.

For more information about configuring Web Services and setting up demonstration scripts, see Integration Platform Technologies: Siebel Enterprise Application Integration.

Using the ATP ASI Testing Script

The ATP ASI test is a testing script that simulates a simple fulfillment engine. It writes the output and response to an XML file on the server. By default the script writes the output and the response to ${SIEBEL_HOME}/bin, for example, D:\Siebel\bin. It writes an output file named ATPOutput.xml. This file represents what you would be sending to your middleware or fulfillment engine. Then the script generates a real-time response and sends the XML back to the Web service. The XML response that is generated is written into a file named ATPFinished.xml, which you can see in the file structure.

This testing infrastructure allows you to analyze what is sent to the middleware and what the Siebel Business Application is expecting back, and allows you to test your user interface.