Communicating Between Systems - Starting Up Channels And Listeners

You must set up communications between the JD Edwards EnterpriseOne IBM WebSphere MQ Server (functioning on the EnterpriseOne server) and the third-party IBM WebSphere MQ server. This section provides example tasks for setting up communications. The example communications setup uses these sequenced and machine dependent steps:

Start the Queue Manager on the third-party IBM WebSphere MQ Server.
Start the Queue Manager on the JD Edwards EnterpriseOne IBM WebSphere MQ Server.
Start the channel on the third-party IBM WebSphere MQ Server.
Start the channel on the JD Edwards EnterpriseOne IBM WebSphere MQ Server.

Note: The first time you start your communications channels, you might need to manually start the sender channel on the local machine and then manually start the receiver channel on the remote machine. After the initial start of the channels, when you start the sender on the local machine, the receiver on the remote machine should automatically start.

To start the Queue Manager on the third-party IBM WebSphere MQ Server

Access the third-party IBM WebSphere MQ server.

In a shell, enter this command to start the queue manager:
strmqm ECE_MQI_QMGR
Note: ECE_MQI_QMGR is the third-party queue manager name.
In the same shell, enter these commands to start the listener:
runmqlsr -m JDE_QMGR -t TCP
where this is an interactive command that ends when terminal session ends.
nohup runmqlsr -m JDE_QMGR -t TCP &
where this is set equivalent to batch process and defines no hang up; this is run as background process.

To start the Queue Manager on the JD Edwards EnterpriseOne IBM WebSphere MQ Server

Access the JD Edwards EnterpriseOne IBM WebSphere MQ Server.

In a shell, enter this command to start the Queue Manager:
strmqm ECE_MQI_QMGR
Note: ECE_MQI_QMGR is the third-party queue manager name.
In the same shell, enter these commands to start the listener:
runmqlsr -m JDE_QMGR -t TCP
where this is an interactive command that ends when terminal session ends.
nohup runmqlsr -m JDE_QMGR -t TCP &
where this is set equivalent to batch process and defines no hang up; this is run as background process.

To start channel on the third-party IBM WebSphere MQ Server

Access the third-party IBM WebSphere MQ server.

In the same shell you used to start the Queue Manager, enter these commands:

runmqchl MQI2OW_CHL

runmqchl OW2MQI_CHL

To start the channel on the JD Edwards EnterpriseOne IBM WebSphere MQ server

Access the JD Edwards EnterpriseOne IBM WebSphere MQ server.

In the same shell you used to start the Queue Manager, enter these commands:

runmqchl OW2MQI_CHL

runmqchl MQI2OW_CHL