Bookshelf Home | Contents | Index | PDF     

Siebel Connector for SAP R/3 > IDOC Interfaces > IDOC Integration with the Siebel Application >

Sending IDOCs with MQSeries

You can use MQ Series to transport IDOCs from the Siebel application to SAP. The following sections discuss how to configure your implementation to use the EAI SAP IDOC MQ AMI Adapter business service to send IDOCs through MQ Series.

Configuring the MQSeries Adapter

The EAI SAP IDOC MQ AMI Adapter business service can be invoked from workflow. See the following section for more information on how to do this. The following tables summarize the User Properties, Method Arguments, and Component Parameters that may be set to control its behavior. The EAI SAP IDOC MQ AMI Adapter is a cached business service. Variables that are defined to be User Properties in the Business Service are generally used only once for initialization purposes at the time of the first call to the Business Service. Variables that are defined to be Method Arguments are used on each call and may vary from call to call.

Table 33 contains User Properties, Component Parameters, and Input Method Arguments for the Send Method.

Table 33. IDOC MQ AMI Adapter Configuration Options
Name
User Prop
Comp Param
Method Arg
Valid Values
Usage

SiebelMessage

 

 

X

 

EAI Siebel Message containing IDOC integration object instance.

SAPReceiverPrtnrNum

 

X

X

Logical system name

Logical system for the SAP client you are sending the IDOC to.

SAPReceiverPrtnrType

 

X

X

Partner type

Defaults to LS if not set for logical system.

SAPSenderPrtnrNum

 

X

X

Logical system name

Logical system name for your external system. This name must be set up in SAP. Read Creating Logical Systems Within SAP.

SAPSenderPrtnrType

 

X

X

Partner type

Defaults to LS if not set for logical system.

DispatchFormat

X

 

 

"MQ"

Currently set to MQ for the AMI Adapter. This should not be changed.

SAPCodepage

X

X

X

Value from Transcode Encoding drop-down list

Siebel code page name for SAP code page.

SAPIgnoreCharSetConvErrors

X

X

X

True or False

Default is False. If True, code page conversion errors are handled by substitution of the question mark (?) character in place of an unrecognized character.

In addition, the default format on the AMI service point needs to be set to MQSTR or MQHSAP depending upon whether or not a user exit is used. For more information, see your MQSeries documentation.

Invoking the MQSeries Adapter from Workflows

If you are sending an IDOC to SAP and want to use MQSeries as the transport, use the sample workflow "Send46CIdoc_UpdateSAPCustomer_MQAMI" or create your own workflow. To create a new workflow, add the EAI SAP IDOC MQ AMI Adapter business service and the EAI MQSeries AMI Transport as a minimum, and you need to add Value as a process property.

To add Value as a process property

  1. Using Process Properties of Workflow Process editor, add a new record.
  2. For the Name field enter Value.
  3. For the Data Type field, specify String.

To add the EAI SAP IDOC MQ AMI Adapter business service

  1. Using the Workflow Diagram Editor, drag a Business Service box to your diagram.
  2. Use a connector arrow to link the box into your flow.
  3. Double-click on the Business Service box to open the business service arguments screen.
  4. Edit the Name field to add a name for your step.
  5. From the drop-down list for Business Services, choose the EAI SAP IDOC MQ AMI Adapter.
  6. From the drop-down list for Business Service Methods, choose the Send method.
  7. Enter appropriate input arguments.

    At a minimum, you must pass an EAI SiebelMessage into the IDOC adapter which contains an IDOC Input integration object you have created with the Integration Object wizard. The SAPSenderPtnrNum input argument must either be set or your map must set the sender partner field in the IDOC control record.

  8. Enter appropriate output argument. You must set an output argument as Value which is defined from Process Property.

To add EAI MQSeries AMI Transport business service

  1. Using the Workflow Diagram Editor, drag a Business Service box to your diagram.
  2. Use a connector arrow to link the box into your flow.
  3. Double-click on the Business Service box to open the business service arguments screen.
  4. Edit the Name field to add a name for your step.
  5. From the drop-down list for Business Services, choose the EAI MQSeries AMI Transport.
  6. From the drop-down list for Business Service Methods, choose the Send method.
  7. Enter appropriate input arguments.

    You must pass Value into the transport which is the output from EAI SAP IDOC MQ AMI Adapter. To allow binary data to be exchanged, set the input argument IsReceivingTextData to false. In addition, set the Connection Subsystem argument to a name of your choice.

  8. Create a named subsystem on the server with the same name as that defined in the Connection Subsystem argument.

    On this subsystem, define the values you are using for MqPolicyName and MqSenderServiceName. For example, using server manager command line mode the command to create the subsystem would look like this:

    create named subsystem your connection subsystem name for subsystem
    MQSeriesAMISubsys with MqPolicyName=your MQ AMI Policy name,
    MqSenderServiceName=your MQ AMI Sender Service name

The IDOC MQ AMI Adapter converts the IDOC to a buffer which MQSeries can understand, and passes this to the AMI Transport which sends the IDOC to the MQSeries Queue. For more information on MQSeries, see the Transports and Interfaces: Siebel Enterprise Application Integration guide.

    
Siebel Connector for SAP R/3