Application Services Interface Reference > Administering Application Services Interfaces > Using ASIs >

Configuring ASIs

Although ASIs are prebuilt, for them to be exposed to external applications, you must configure them to the requirements of the IT application environment.

To configure an inbound data synchronization ASI

1. Open Siebel Tools and select the integration object you want to update and deactivate the components and fields you do not require for your business service.

   NOTE:  If an inbound ASI needs to be invoked through a workflow process, you need to define a named subsystem. See Integration Platform Technologies: Siebel eBusiness Application Integration Volume II for more information about named subsystems and how to define them.

   See Deactivating ASI Components and Fields for more information. If you only deactivated fields and no map is specified in the ASI, a data map is unnecessary. Implicit data mapping still applies.

2. Recompile the project into an SRF file.

   The ASI is now ready to use as a business service.

3. (Optional) If the ASI is to be made into a Web Service, create a new entry in the Inbound Web Services Administration view.

To configure an outbound ASI

1. Open Siebel Tools and select the integration object you want to change and deactivate the components and fields you do not require for the ASI.

   See Deactivating ASI Components and Fields for more information.

   NOTE:  Skip steps 3 through 5 of this procedure if a WSDL file exists for the internal interface. You can run the WSDL Wizard to import the necessary information. If a WSDL file does not exist, complete steps 2 through 4 of this procedure.

2. Open the Siebel Client, choose the Administration - Web Services menu, select the Outbound Web Services screen, and define an entry for the outbound ASI.

   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.

3. Open Siebel Tools, select Business User Properties, and configure the following properties:
   • Transport. The service to send the request. See Exposing ASIs with Interface Technologies for more information.
   • Protocol. Defines the formatting of the data. See Protocols Used with ASIs for more information.
   • Address. The location to send the request. Use the URL or queue name associated with the transport.
4. Recompile the projects with the integration objects and business services definition into the SRF file.