Bookshelf Home | Contents | Index | Search | PDF |
Siebel eSales Administration Guide > Using Third-Party Product Availability Management Applications > Required Setup Procedures >
Configuring Web Services
Web services are used to direct the inbound and outbound messages to and from:
- The third-party ATP engine.
- A script, called ATP ASI test, that can be used to test your integration setup.
- A middleware or integration server that will integrate with your fulfillment engine.
ATP ASI test is a testing script that simulates a simple fulfillment engine. The script writes the output and response to an XML file on the server machine. By default, the output and response are written to ${SIEBEL_HOME}/bin, for example D:\Siebel\bin. The script writes an output file, called ATPOutput.xml, which represents what you would be sending to your middleware or fulfillment engine. Then it generates a real-time response and sends that back to the Web service. The generated response is written into a file called ATPFinished.xml, which you can see in the file system.
This testing infrastructure allows you to analyze what will be sent to the middleware and what Siebel eSales is expecting back. Based on this data, it will show you how it populates the data on the UI.
You must make sure that the Web services are correctly configured.
To configure the Web services
- Navigate to the Web Services Administration screen.
- From the Show drop-down list, select Outbound Web Services.
- Select the row with External ATP Check in the Name field.
- Verify that the fields in the Outbound Web Services list match those in the following table.
- In the Service Ports list, click New, and enter the following values in the fields of the new record.
For more information about configuring Web Services and setting up demonstration scripts, see Integration Platform Technologies: Siebel eBusiness Application Integration Volume II.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel eSales Administration Guide Published: 18 April 2003 |