Siebel Master Data Applications Reference for Industry Applications > Configuring Siebel Master Data Applications > Configuring Siebel Master Data Application Features >

Configuring UCM Inbound Server Communication

Configuring inbound UCM Siebel Server communications depends on the registered system protocol type for the Siebel Connector for Master Data Applications, either the Siebel EAI MQSeries Transport, the Siebel EAI JMS Transport, or the Siebel EAI HTTP Transport. (For further details on the Siebel Connector for Master Data Applications, see Siebel Connector and Integration of Siebel Master Data Applications.)

The Siebel EAI MQSeries Transport allows you to integrate data between Siebel Business Applications and external applications that can interface with the IBM MQSeries. The EAI MQSeries Server Transport transports messages to and from IBM MQSeries queues. To configure Siebel EAI MQSeries Transport, see Configuring for Siebel EAI MQSeries Transport.

Siebel EAI HTTP Transport allows you to send XML messages over HTTP to a target URL. The Siebel Web Engine (SWE) serves as the transport to receive XML messages sent over the HTTP protocol to a Siebel application. To configure Siebel EAI HTTP Transport, see Configuring Siebel EAI HTTP Transport.

For background information and details on configuring Siebel EAI MQSeries Transport and Siebel EAI HTTP Transport, see Transports and Interfaces: Siebel Enterprise Application Integration.

Configuring for Siebel EAI MQSeries Transport

To configure UCM inbound communication using the Siebel EAI MQSeries Transport, you must:

• Create and configure two named subsystems.
• Configure the Siebel Server component MQSeries Server Receiver (alias: MqSeriesSrvRcvr)

NOTE:  Make sure Siebel EAI MQSeries Transport is enabled prior to configuring for UCM. For further information on enabling Siebel EAI MQSeries Transport, see Transports and Interfaces: Siebel Enterprise Application Integration.

For background information on these Siebel Server administrative tasks, see Siebel System Administration Guide.

To configure named subsystems

1. Navigate to the Administration—Server Configuration screen.
2. From the link bar, click Enterprises.
3. Select the Profile Configuration view tab.
4. Create two new records in the Profile Configuration list and provide the following information.

   	Record 1	Record 2
   Name	Any name, CIFMQConnSubsy for example	Any name, CIFMQDataSubsys for example
   Alias	This field is required for creation of this record.	This field is required for creation of this record.
   Subsystem Type	MQSeriesServerSubsys	EAITransportDataHandlingSubsys

   NOTE:  The subsystem type that you select must have a check mark in the Is Named Enabled field.

5. For each record, modify the following parameters in the Profile Parameters list:

   Parameter Name	Record 1	Record 2
   MQSeries Physical Queue Name	Queue name to receive inbound request message from	N/A
   MQSeries Queue Manager Name	Queue manager name who own the queues	N/A
   MQSeries Response Physical Queue Name	Queue name to send response message to	N/A
   MQSeries Sleep Time	100 (or longer if required)	N/A
   Workflow Process to Execute	N/A	UCM Customer Profile Integration Process

6. Save both records.

   For details on this procedure and the Named Subsystems, see Siebel System Administration Guide.

To configure MQSeries Server Receiver Siebel Server component

1. Navigate to the Administration—Server Configuration screen.
2. From the link bar, click Servers.
3. In the Siebel Servers list, select the Siebel Server of interest.
4. Click the Components view tab.
5. In the Components list, select MQSeries Server Receiver (alias: MqSeriesSrvRcvr).
6. Select the Parameters view tab under the Components list.
7. Set the following parameters as follows:

   Parameter Name	Alias	Value
   Receiver Connection Subsystem	ReceiverConnectionSubsystem	Subsystem name created in To configure named subsystems. For example, CIFMQConnSubsys or CIFMQDataSubsys.
   Receiver Method Name	ReceiverMethodName	ReceiveDispatch or ReceiveDispatchSend.
   Default Tasks	DfltTasks	1 or number of tasks desired.

8. Restart the Siebel Server and make sure the MQSeries Server Receiver server component is running.

Configuring for Siebel EAI JMS Transport

Use the Siebel EAI JMS Transport to integrate data between Siebel Business Applications and external applications that can interface using JMS Protocol. The EAI JMS Transport transports messages to and from JMS queues.

To configure UCM inbound communication using the Siebel EAI JMS Transport, you must:

• Create and configure two named subsystems.
• Configure the Siebel Server component JMS Receiver (alias: JMSReceiver)

NOTE:  Make sure Siebel EAI JMS Transport is enabled prior to configuring for UCM. For more information on enabling Siebel EAI JMS Transport, see Transports and Interfaces: Siebel Enterprise Application Integration.

For background information on these Siebel Server administrative tasks, see Siebel System Administration Guide.

To configure named subsystems

1. Navigate to the Administration-Server Configuration screen.
2. From the link bar, click Enterprises.
3. Click the Profile Configuration view tab.
4. Create two new records in the Profile Configuration list and provide the following information.

   	Record 1	Record 2
   Name	Any name, such as: CIFJMSConnSubsy	CIFJMSDataSubsys
   Alias	This field is required for creation of this record	This field is required for creation of this record
   Subsystem Type	JMSSubsys	EAITransportDataHandlingSubsys

   NOTE:  The subsystem type that you select must have a check mark in the Is Named Enabled field.

5. For each record, modify the following parameters in the Profile Parameters list:

   Parameter Name	Record 1	Record 2
   ConnectionFactory name	Name of Connection Factory	N/A
   ConnectionUsername	User Name for the connection
   ConnectionPassword	User Password for the connection
   ReceiveQueue name	Queue name to receive inbound request message from	N/A
   SendQueue name	Queue name to send response message to	N/A
   JVM Subsystem name	JAVA	N/A
   DispatchWorkflowProcess	N/A	UCM Customer Profile Integration Process

   NOTE:  Make sure that you have JAVA named subsystem created for subsystem JVMSubSys with DLL, Classpath, and VMOPTIONS parameters defined. For information on how to create this subsystem, see Business Processes and Rules: Siebel Enterprise Application Integration.

6. Save both records.

For details on this procedure and the Named Subsystems, see Siebel System Administration Guide.

To configure JMS Receiver Siebel Server component

1. Navigate to the Administration-Server Configuration screen.
2. From the link bar, click Servers.
3. In the Siebel Servers list, choose a Siebel Server.
4. Click the Components view tab.
5. In the Components list, choose JMS Receiver (alias: JMSReceiver).
6. Click the Parameters view tab under the Components list.
7. Set the following parameters:

   Parameter Name	Alias	Value
   Receiver Connection Subsystem	ReceiverConnectionSubsystem	Subsystem name created previously. For example: CIFJMSConnSubsy
   Receiver Method Name	ReceiverMethodName	ReceiveDispatch or ReceiveDispatchSend

8. Restart the Siebel Server and make sure the JMS Receiver server component is running.

Configuring Siebel EAI HTTP Transport

To configure UCM inbound communication using the Siebel EAI HTTP Transport, you must:

• Configure the Siebel Web Engine (SWE)
• Modify the Siebel Universal Customer Master Configuration file (.cfg file) to run the extension service.

NOTE:  Make sure Siebel EAI HTTP Transport is enabled prior to configuring for UCM. For further information on enabling Siebel EAI HTTP Transport, see Transports and Interfaces: Siebel Enterprise Application Integration.

For background information on these Siebel Server administrative tasks, see Siebel System Administration Guide.

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

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

   [/ucm_enu]

   ConnectString = <Connect String>

   EnableExtServiceOnly = TRUE

4. Save and close the configuration file.

After creating and configuring the SWE, configure the required Named Subsystem. For more information on this procedure, see Transports and Interfaces: Siebel Enterprise Application Integration.

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

1. Open ucm.cfg file in the \bin subdirectory in the install directory.
2. Locate the section [/HTTP Services], or add this section if it is not found.
3. 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.

4. Save and close the configuration file.