Siebel Application Services Interface Reference > Customizing an Application Services Interface >

User Scenarios for ASIs

The Siebel prebuilt ASIs might not be sufficient, depending on your business needs. You can extend existing ASIs for further customization, or you can create new interfaces using the ASI Framework. The following scenarios describe an integration developer who needs to customize the interface to reflect her company's business needs, rules, and processes. The key activities in these scenarios are:

• Defining an Outbound ASI
• Defining an Outbound ASI

Extending an ASI

At the ABC company, Jane needs to extend an existing ASI by adding a new field, LifeTimeValue, to the business component, Account, and expose the new field in the ASI, Siebel Account, which uses data synchronization services.

To accomplish these tasks, Jane must:

1. Create the new field, LifeTimeValue, in the Account business component using Siebel Tools.
2. Add LifeTimeValue to Account's internal integration object using Siebel Tools.
3. Add LifeTimeValue to Account's interface integration object using Siebel Tools. She must make sure that the two fields in the internal and interface integration objects have matching names.
4. Recompile the integration objects and project into an SRF file, and test the new ASI.
5. Use the Auto-Map function in the Siebel Data Mapper to automatically map the new field in the internal integration object to the new field in the interface integration object.

After completing these tasks, the new field is available to the business component, Account, and all ASIs based on it, including Siebel Account.

Defining an Outbound ASI

Jane needs to define an outbound ASI for her company, ABC Company, that submits an order to a back-office system using data synchronization services. She calls the ExternalOrder ASI.

To create this ASI, Jane must do the following in Siebel Tools:

1. Create an internal integration object, ExternalOrder Internal, with the necessary components and fields based on ABC Company's business needs.
2. Create an interface integration object, ExternalOrder Interface, with the same components and field names as the ExternalOrder Internal integration object. Because both integration objects have the same component and field names, Jane does not need to create a data map, because she uses the data synchronization service's implicit mapping function.
3. Define a new Business Service, named ExternalOrder, as an outbound ASI, by specifying CSSWSOutboundDispatcher as Class.
4. Define all the methods used by this ASI.
5. For each method, create the method argument parameters as Integration Object, String, Hierarchy, Number, or Date, and specify the Type as input or output.
6. Specify the implementation for the ASI by setting the Business Service User Properties, because she does not have a current WSDL template to import. Consequently, Jane must create the following Business Service User Properties:

7. Compile all integration objects and business services into an SRF file for the Siebel Server.
8. In the Siebel Client, navigate to the Administration - Web Services screen, and then Outbound Web Services.
9. Define a new outbound ASI called ExternalOrder, provide a namespace, and make it Active.
10. For the outbound ASI, create the Service Port External Order and reference it to the External Order that she created and compiled in Siebel Tools.
11. Select the correct transport, WSDL address, and binding.
12. Under Operations, list the methods needed for this ASI. The new ExternalOrder ASI is created and ready to use.