Bookshelf Home | Contents | Index | Search | PDF

Application Services Interface Reference > Customizing an Application Services Interface > User Scenarios >

Defining an Outbound ASI

---

Jane needs to define an outbound ASI for her company that submits an order to a back office system using data synchronization services. She calls the ASI ExternalOrder. To create ExternalOrder, Jane must:

Create an internal integration object, ExternalOrder Internal, with the necessary components and fields based on ABC's business needs.
Create an interface integration object, ExternalOrder Interface, with the same components and field names as the ExternalOrder Internal. Because both integration objects have the same component and field names, Jane does not need to create a data map, but uses data synchronization service's implicit mapping functionality.
Define a new Business Service, named ExternalOrder, as an outbound ASI. She must also define all the methods used by this ASI. Additionally, she must set the method parameters as Integration Object.
Manually specify the implementation for the ASI by setting the Business Service User Properties under Siebel Tools, because she does not have a current WSDL template to import. Consequently, Jane must specify:
The siebel_web_service_namespace as http://ABCcompany/asi.
The siebel_web_services_name as ExternalOrder Interface.
The siebel_port_name as the default value.
Recompile all the integration objects and business services into an SRF file, and test ExternalOrder to make sure it is working properly.
Define a new outbound ASI called ExternalOrder, referencing the business service, ExternalOrder, that she created earlier.

After completing these tasks, the new ASI, ExternalOrder, has been created and is now ready to use.

Bookshelf Home | Contents | Index | Search | PDF