Application Services Interface Reference > Customizing an Application Services Interface >

ASI Framework

As defined earlier, an ASI is a release-independent interface published by Siebel in a standard metadata format and built using the ASI Framework (see What Are ASIs?).

The ASI Framework provides the technology in which ASIs are implemented. You can use this framework to extend existing ASIs or to define your own Web service and proxies in a Siebel application for externally defined services. Other interfaces can be built using the ASI Framework, but are not considered to be ASIs. Only Siebel prebuilt ASIs are supported across releases.

NOTE:  Interfaces built using the ASI framework are not supported across releases and are not considered upgradeable.

The following procedure describes extending an existing Siebel ASI to meet your business needs.

To extend an ASI

  1. Identify the integration objects to modify—the internal integration object and the interface integration object.
  2. Open Siebel Tools, select the internal integration object, and add the required components and fields.
  3. Select the interface integration object and add the required components and fields, matching the component and field names from the internal integration object.
  4. Choose the Tools menu and select Validate Object to check the definition of the integration objects in Siebel Tools.
  5. Recompile the project into an SRF file, and replace the SRF file on your Application Server with the new SRF file.
  6. Open the Siebel Client, select the Integration Administration menu, choose the Data Maps screen, query for the data map, and click Auto-Map if an explicit map exists for this service.

    7. Clicking Auto-Map automatically creates an explicit map for the newly added components and fields to the ASI. Auto-Map maps the matching root components, fields, and child components between the integration objects, if the names are the same and no current mapping exists. For more information on the Auto-Map feature, see Automatic Mapping.

  7. Click Validate in the Data Map screen to check any changes to the data map before testing.
  8. Purge the Data Map cache, if a data map for the ASI is currently being used.

    9. This action removes any traces of the current data map and allows the correct data map to be used. Purge the data map only during the development and testing phases of the ASI.

    NOTE:  To purge the Data Map cache, you need to define a workflow under Business Process Administration. For more information about creating this workflow, see Business Processes and Rules: Siebel eBusiness Application Integration Volume IV.

  9. Test the ASI to make sure it is accurate and correct.

 Application Services Interface Reference 
 Published: 15 May 2003