Understanding business services

This section explains what a business service is and describes how to create business objects that support business services. The following topics are covered:

Description of business services

Creating business objects that support business services

Description of business services

A business service is an object that encapsulates and simplifies the use of some sets of functionality, such as moving and converting data formats between the Siebel application and external applications. Business components and business objects are objects that are typically tied to specific data and tables in the Siebel data model. Business services, on the other hand, are not tied to specific objects, but rather operate on objects to achieve a particular goal.

The adapter supports generic business services and ten application-specific interfaces. The business services take the integration object instances (or property sets) as the input. The integration object instance is created by building the definition for the integration object, then building the property set based on the values of the integration object definition. Once the integration object instance is created, it can be sent to the business services. Existing integration object definitions can be used, as can existing business services, such as EAI Siebel Adapter.

Note:
If an object contains the application-specific information BSN, then it will be treated as a business service.

Creating business objects that support business services

The adapter constructs the property set for the incoming business object, which is the representation of the integration object. The following example describes how to construct the property set.

Example:

//instantiate a new property set for type Siebel Message

//set the type as Siebel MEssage and properties such as IntObject Format,

MessageType, MessageId, IntObjectName

//instantiate a new property set for type ListOf<Parent Component>

//set the type as ListOf<Parent componet name>

//instantiate a new property set for type <Parent Component>

//set type as <parent object type>

//set different properties

//do the same for child components

You can create business objects that support business services using one of the following methods:

The following examples show how to create each type of integration object.

Siebel Integration object

Account (PRM ANI) (Integration object)

+Account (Integration component)

+Business address (Integration component)

Integration object

Siebel <IntObjectName> (ParentIntegrationComponent)

BSN=<name>;IO<Name>;IC=<Name>

Attribute1 FN=<fieldname>

Attribute2 FN=<fieldname>

Attribute3 FN=<fieldname>

+ChildIntegrationComponent

IO=<Name>:IC=<Name>

childAttribute1 FN=<fieldname>

childAttribute2 FN=<fieldname>

Object level ASI:

for Parent Integration Component

BSN=<name>;IO=<Name>;IC=<Name>

for Child Integration Component:

IO=<Name>;IC=<Name>

The following tables describe the Business object level application text and the Simple attribute level application text used when creating integration objects.

Table 21. Business object level application text
Parameter Description
IO= The name of the Siebel integration object corresponding to this business object.
IC= The name of the Siebel integration component corresponding to this business object.
BSN= The name of the business service used by this business object. When using application specific information, such as Siebel Account or Siebel Contact, the specific business service must be present. When using other integration objects, the EAI (put explanation of acronym here) must be present.
SiebASI= When a business object represents the ASI integration object, it contains SiebASI=true
Table 22. Simple attribute level application text
Parameter Description
FN= The field name of the field in the Siebel integration component corresponding to this attribute

Copyright IBM Corp. 1997, 2003