Bookshelf Home | Contents | Index | Search | PDF

Siebel Universal Customer Master Applications Reference for Industry Applications > Siebel UCM Applications Administration > Integration Objects >

Siebel UCM Applications Integration Services

---

Siebel UCM Applications provide an object called a business service, which you can reuse in multiple applications. The Siebel Connector for the Customer Information File provides the following prebuilt business services, which you can configure to meet your business requirements:

FINS CIF Transaction Manager
FINS CIF Converter
FINS CIF Dispatcher
FINS CIF Security Manager
FINS CIF Publish/Subscribe Service

You can configure business services by manipulating their user properties, or you can create your own business service in Siebel Tools. For information on Siebel Tools, see Siebel Tools Reference.

NOTE:  After you have configured your business services to accomplish the tasks required for your business scenario, you need to compile the business service to include the new information in your Siebel repository file (.srf). Then copy the .srf file to the directory where your servers can access it.

FINS CIF Transaction Manager

You can extend this business service by manipulating its Operation user property. The basic format for value entry for each operation is as follows:

CIFOperation_Query

Service/Method/Argument;Argument; or /Method/Argument;Argument;

Service, Method, and Argument are separated by a forward slash (/).
Each Argument ends with a semi-colon (;).

CIFOperation_XMLQuery

EAI Siebel Adapter/Query/#XMLHierarchy;

The default Service name is EAI Siebel Adapter and the default argument name is SiebelMessage.
SiebelMessage indicates turning off the SiebelMessage.
XMLHierarchy indicates replacing SiebelMessage with XMLHierarchy.

CIFOperation_GetValue

FINS Industry/BC Facility Service/HierarchySearchSpec/!SiebelMessage;A=>B;

A=>B means getting argument value of A from argument value of B where argument B is Connector Integration Object Instance's arguments

Table 26 lists the user properties examples for the FINS CIF Transaction Manager.

Table 26. User Properties for FINS CIF Transaction Manager

Operation Name	Value
IXMLOperation_ADD	EAI Siebel Adapter/Insert/
IXMLOperation_DELETE	EAI Siebel Adapter/Delete/
IXMLOperation_QUERY	EAI Siebel Adapter/Query/
IXMLOperation_QUERY_BY_ID	EAI Siebel Adapter/Query/PrimaryRowId;!SiebelMessage;
IXMLOperation_SYNCH	EAI Siebel Adapter/Synchronize
IXMLOperation_UPDATE	EAI Siebel Adapter/Update

FINS CIF Converter

Table 27 displays the only user property you can configure for this business service. This value appears in the preheader section of your CRMML message.

Table 27. User Property for FINS CIF Converter

Name	Value
XMLEnvIntObjectName	Name of the envelope integration object shipped or customized by you.

The FINS CIF Converter uses the hierarchy represented in the CIF integration object to guide the message through the converting process. If there are elements in the integration object instance received that do not have a definition defined in the integration object definition, the converter errors out. If you expect such a situation, you can set the Ignore Undefined XML Tag parameter on the user property of the corresponding integration object.

NOTE:  This user property is created by the wizard and is set to Y. You can turn it off if you wish the converter to error out.

FINS CIF Dispatcher

You can modify both user properties for this business service as shown in Table 28.

Table 28. User Properties for FINS CIF Dispatcher

Name	Value
DispatcherMapName	Name of the dispatcher map shipped or customized by you.
XMLEnvIntObjectName	Name of the envelope integration object shipped or customized by you.

FINS CIF Security Manager

You can modify or extend this business service by manipulating its user properties. The Name column stands for the CIF Transaction Manager Operation Name, while the Value column represents the Field Name for different types of privileges in the System Privileges View. Table 29 displays these user properties.

Table 29. User Properties for FINS CIF Security Manager

Name	Value
IXMLOperation_ADD	Insert
IXMLOperation_DELETE	Delete
IXMLOperation_QUERY	Query
IXMLOperation_UPDATE	Update

Inbound Server Administration

A server task is an instantiation of a server component. To run a server task, you need to run a component request, which requests one or more server tasks to run. The server task you need to run for the Siebel Connector for Universal Customer Master Applications depends on the registered system protocol type, either the Siebel EAI MQSeries Server Transport or the Siebel HTTP Server Transport.

The Siebel EAI MQSeries Server Transport is designed to provide a messaging solution to help you integrate data between Siebel eBusiness Applications and external applications that can interface with the IBM MQSeries. The EAI MQSeries Server Transport transports messages to and from IBM MQSeries queues. In order to run this server task successfully you need to first configure two named subsystems.

To configure named subsystem

Navigate to the Server Administration screen, Enterprise Configuration view.
Click the Enterprise Profile Configuration view tab.
Create a two new records in the Component Profiles list and provide the following information.

	Record 1	Record 2
Name	Any name, CIFMQConnSubsy for example	Any name, CIFMQDataSubsys for example
Type	MQSeriesServerSubsys	EAITransportDataHandlingSubsys

NOTE:  The subsystem type that you select should have a checkmark in the Is Named Enabled field.

For each record, modify the following parameters in the Enterprise Profile Configuration list:

Parameter Name	Record 1	Record 2
MqPhysicalQueueName	Queue name to receive inbound request message from	N/A
MqQueueManagerName	Queue manager name who own the queues	N/A
MqRespPhysicalQueueName	Queue name to send response message to	N/A
MqSleepTime	100 (or longer if required)	N/A
DispatchWorkflowProcess	N/A	CIF Server Party Package Workflow (MQSeries Server Transport Error Handling)

Save both records.

For details on this procedure and the Named Subsystem, see Siebel Server Administration Guide.

After creating and configuring your Named Subsystem, you need to configure the MQSeries Receiver. For details on configuring MQSeries, see Transports and Interfaces: Siebel eBusiness Application Integration Volume III.

To configure MQSeries Receiver parameters

Navigate to the Server Administration screen, Server Component view.
Query for MQSeries Server Receiver and click the Component Parameters tab.
Set the following parameters as follows:
Receiver Connection Subsystem—Subsystem name created in To configure named subsystem. For example, CIFMQConnSubsys or CIFMQDataSubsys.
Receiver Method Name—ReceiveDispatch or ReceiveDispatchSend.
Default Tasks—1 or number of tasks desired.
Restart the Siebel Server and make sure the MQSeries Receiver server component is running.

If the registered system is using the HTTP protocol type, you need to configure the Inbound EAI HTTP Transport. The Inbound EAI HTTP Transport is built into the Siebel Web Engine (SWE). To use it, you need to specify certain parameters listed as follows.

To configure the Siebel Web Engine to run the Inbound HTTP Transport

Open eapps_sia.cfg file in the \bin subdirectory in the install directory.
Locate the section [/cif_%language%], for example [/cif_enu].
Add the EnableExtServiceOnly configuration parameter or set it as follows, if it already exists:

[/cif_enu]

ConnectString = <Connect String>

EnableExtServiceOnly = TRUE

Save and close the configuration file.

After creating and configuring the SWE, configure the required Named Subsystem.

To configure named subsystem

Navigate to the Server Administration screen, Enterprise Configuration view.
Click the Enterprise Profile Configuration view tab.
Create a new record in the Component Profiles list and provide the following information.
Name—Name of the Named Subsystem. For example, CIFInboundHTTPDispatch.
Type—Type of the Named Subsystem, EAITransportDataHandlingSubsys.

NOTE:  The subsystem type that you select should have a checkmark in the Is Named Enabled field.

Modify the following parameter in the Enterprise Profile Configuration list:

DispatchWorkflowProcess—CIF Server Party Package Workflow (MQSeries Server Transport Error Handling)

Save the record.

For details on this procedure and the Named Subsystem, see Siebel Server Administration Guide.

After creating and configuring your Named Subsystem, configure the Siebel UCM Applications.

To configure the Siebel Universal Customer Master Application to run the Extension Service

Open cif.cfg file in the \bin subdirectory in the install directory.
Locate the section [/HTTP Services], or add this section if it is not found.
Add the services and corresponding named subsystems configured. For example:

[/HTTP Services]

SiebelCIFContact = CIFInboundHTTPDispatch

The name SiebelCIFContact in the queryString matches the name CIFInboundHTTPDispatch, which in turn looks up for the named subsystem list and dispatches accordingly.

Save and close the configuration file.

NOTE:  For details on creating and configuring server tasks, see Siebel Server Administration Guide, and for details on configuring MQSeries and HTTP, see Transports and Interfaces: Siebel eBusiness Application Integration Volume III.

Bookshelf Home | Contents | Index | Search | PDF