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
Processing business objects that support 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 EAI Siebel Adapter, a generic business service provided by Siebel; Siebel-defined Applications Services Interfaces (ASIs); and custom-written business services.
EAI Siebel Adapter and ASIs are treated similarly with respect to IBM business objects. They implement similar methods that are used as verbs for processing the IBM business objects. EAI Siebel Adapter can take any integration object that is based on a Siebel business object. The IBM WebSphere Business Integration adapter for Siebel therefore supports EAI Siebel Adapter by representing an integration object with an IBM business object. Similarly, the adapter supports Siebel ASIs by representing the integration objects implementing them with an IBM business object.
Custom-written business objects are treated differently. Because they can implement any method, the IBM business object represents the service itself, not an integration object.
EAI Siebel Adapter and ASIs can be treated by the adapter as custom-written business services, and IBM business objects can be created to directly represent these services, although this is not recommended. See Creating business objects.
The adapter constructs the property set for the incoming business object, which is the representation of the integration object. The following example describes how the adapter constructs the property set out of the IBM business object representing the integration object.
Example:
Example: Siebel Integration
object
Account (PRM ANI) (Integration object)
+Account (Integration component)
+Business address (Integration component)
Example: IBM business object representing Siebel integration
object
Siebel <IntObjectName> (ParentIntegrationComponent)
Attribute1 FN=<fieldname>
Attribute2 FN=<fieldname>
Attribute3 FN=<fieldname>
+ChildIntegrationComponent
childAttribute1 FN=<fieldname>
childAttribute2 FN=<fieldname>
Object level ASI for the Parent Integration Component would be BSN=<name>;IO=<Name>;IC=<Name>
For the Child Integration Component, it would be 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 14. 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 Siebel Enterprise Applications Integration (EAI) must be present. |
SiebASI= | (Deprecated) When a business object represents the ASI integration object, it contains SiebASI=true |
BSTYPE= | Determines the type of business service.
|
Table 15. Simple attribute level application text
Parameter | Description |
---|---|
FN= | The field name of the field in the Siebel integration component corresponding to this attribute |