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

Building Customized Interfaces Using the ASI Framework

You can build your own interfaces using the ASI Framework.

To define an inbound interface

1. Determine the schema and fields of the integration objects based on your business needs.
2. Open Siebel Tools, create the internal integration object using the Integration Object Wizard, and deactivate the components and fields that are not required.

   NOTE:  Deleting fields is not recommended. For more information about creating integration objects, see Integration Platform Technologies: Siebel Enterprise Application Integration.

3. Create the interface integration object in Siebel Tools using one of the following methods:
   • Copy the internal integration object, if the internal and interface objects are the same.
   • Use the DTD or XML schema wizard. For more information about using the XML schema wizard, see Integration Platform Technologies: Siebel Enterprise Application Integration.
   • Create the object manually.
4. Deactivate the components and fields that are not required.

   Deleting fields is not recommended.

5. Choose the Tools menu and select Validate Object to check the definition of the integration objects.
6. Compile the SRF file, and import it to the Siebel Server.
7. Open Siebel Client, select the Administration - Integration menu, and select the Data Maps screen.

   NOTE:  Do not create an explicit data map if an object is a subset of another or if the objects are the same. The data synchronization service automatically maps the subsets if the root integration components have the same name.

8. Open the Integration Administration menu and choose the Data Map editor to create an explicit data map if the two objects contain different component or field names.

   A map is required for each direction:

   • From Interface Object to Internal Object
   • From Internal Object to Interface Object
9. Click Validate in the Data Map editor to check the data map changes before testing.
10. Open Siebel Tools, define the business service, and set the class property to CSSEAIDataSyncService.

    Within the business service:

    1. Define the methods needed for this service. See Data Synchronization Methods for ASIs for more details.
    2. Define the Business Service User Properties to configure the internal object and the data map names. See Business Service User Properties for ASIs for more details.
11. Recompile the projects with the integration objects and business services definition into the SRF file.
12. Open Siebel Client, select the Administration - Web Services menu, and choose the Inbound Web Services screen. Create an entry if the inbound interface is to be made available as a Web service.

To create an outbound interface, you must publish it as a Web service to use it externally.

To define an external interface

1. Open Siebel Tools and define the integration objects manually or by using the Integration Object Wizard.
   1. Deactivate components and fields that are not required.

      Deleting fields is not recommended.

   2. Create interface integration objects manually by copying and changing the internal object, or by importing an XML DTD.

      NOTE:  Skip to Step 5 of this procedure if a WSDL file exists for the internal interface. You can run the WSDL Wizard to automatically import the information that is created manually in Step 3 through Step 5. If a WSDL file does not exist, complete Step 2 through Step 4. For more information about using the WSDL Wizard, see Integration Platform Technologies: Siebel Enterprise Application Integration.

2. Open Siebel Tools and define the business service to describe the interface to the ASI, including all methods and parameters for each method.

   This business service references the integration objects created in Step 1.

   1. Set the business service's class to CSSWSOutboundDispatcher.
   2. Set the parameters on methods to type Integration Object and refer to the specified interface object.
3. Define the Business Service User Properties in Siebel Tools:
   1. Choose a name for the default service, siebel_web_service_name.
   2. Choose the properties for the default port, siebel_port_name.
   3. Register the name on the business service as a user property, and define the service and port name as the proxy's default service name, siebel_web_service_namespace.

      NOTE:  The user property, ApplicationServicesInterface, is set to Y for each ASI Business Service. You can use it for visual identification to differentiate this business service from other business services. The user property has no functional implication.

4. Open Siebel Client, choose the Outbound Web Services screen, and select a name for the default service. Configure the following properties:
   • Port types are all the published proxy business services used to define the outbound ASI interface. The port name is the business service you created in Siebel Tools in Step 2.
   • Transports describe the transport type for your particular platform and system. For more information, see Exposing ASIs with Interface Technologies.
   • Protocols describes the formatting of the integration object being sent. For more information, see Protocols Used with ASIs.
   • Address is the physical location of the touchpoint files.
5. Recompile the projects with the integration objects and business services definition into the SRF file.
6. Define an entry for the outbound ASI in the Outbound Services Administration View.

   The port type should reference the business service created for the outbound ASI. The name of the business service and port must match the default names set on the business services definition.

To define the data map

• An inbound and outbound data map need to be created for each interface. In Siebel Client, use the Data Maps view under the Administration - Integration menu to create a new data map for new or customized integration objects. See Data Mapping for ASI Release Independence for more information about data mapping.

For more information about creating a data map for the ASI, see Business Processes and Rules: Siebel Enterprise Application Integration.