|Bookshelf Home | Contents | Index | PDF|
In many instances, Web Services use specialized SOAP headers for common tasks such as authentication, authorization, and logging. In order to support this common Web Service extensibility mechanism, a Local Business Service, as a transport option for outbound Web Services, is supported in the Siebel application. When specified as a transport, the Web Services infrastructure will route the message to the specified business service for additional processing and delivery to the Web Service endpoint as shown in the top half of Figure 24.
An example of using a local business service is a department store developing a workflow in Siebel Tools to perform credit card checks before purchases. The purchase is entered into the sales register along with the credit card information (the outbound Web Service proxy). If the credit card is issued by the department store, the information can be checked using the internal database (a local business service). The send request stays within the department store's own computer network. An approval or denial is the output (the Web Service endpoint). If the credit card is a MasterCard or a Visa card, the card information is passed through the Internet for verification. No local business service would be involved.
The input to the local business service is a property set representation of the SOAP request. Once within the local business service, additional SOAP headers may be added to address infrastructure requirements by direct modification of the input property, set by using Siebel eScript or Siebel VB.
|Integration Platform Technologies: Siebel Enterprise Application Integration||Copyright © 2008, Oracle and/or its affiliates. All rights reserved. Legal Notices.|