| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Connector for SAP R/3 > Installing and Configuring the SAP Connector > Configuring the Connector for Use with IBM MQSeries >
Setting Server Subsystem
Because the EAI Receiver infrastructure and transport mechanisms have changed in Siebel 7, the previous parameter specification at the Business Service level and the server Component parameter level is no longer used for the EAI transport related receivers. The new receivers use named subsystems.
There are two kinds of subsystems to be specified to start the SAP IDOC AMI Receiver for MQSeries (sapidocamimqrcvr):
- ReceiverConnectionSubsystem
- ReceiverDataHandlingSubsystem
Because the ReceiverDataHandlingSubsystem is preconfigured for sapidocamimqrcvr, you only need to provide ReceiverConnectionSubsystem.
To set the ReceiverConnectionSubsystem
- Log in to server manager line mode (you may also use server administration).
- Type in this command:
create named subsystem <your subsystem name> for subsystem MQSeriesAMISubsys with MqPolicyName=<your MQ AMI Policy name>, MqReceiverServiceName=<your MQ AMI Receiver Service name>- Use the command, list named subsystem, to make sure the subsystem is created.
- Stop the Siebel server service and restart it.
- Start the receiver with this command:
start server for comp sapidocamimqrcvr with ReceiverConnectionSubsystem=<your subsystem name>The SAP IDOC AMI Receiver can be used to trigger workflows upon the receipt of an IDOC just as the BAPIRcvr does. The receiver is configured by default to allow the invocation of all the Standard Integration inbound workflows: Account - Receive SAP Customer (4x IDOC Input), Product - Receive SAP 4x Material (4x IDOC Input) and Order - Changes SAP 4x Order Status.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Connector for SAP R/3 Published: 22 August 2003 |