Additional files needed
You need the following files to configure and run your message receiver:
JMSAdmin.sh: JMSAdmin tool executable from QSH
JMSAdmin.config: Configuration file used by JMSAdmin
SendTestMessage.sh: Enables test messages to be sent
You can find these programs in the /OrderManagement/mq directory on the iSeries server. If these files are missing, map to the iSeries root directory using Windows Explorer, navigate to the mq directory, and copy the missing files.
You may need to edit the JMSAdmin.config file. You can do this by using Windows Explorer. Alter the line that starts with PROVIDER_URL…… so that it points to the correct port number on
your iSeries, for example:
PROVIDER_URL=iiop://localhost:900/
Creating the JNDI/MQ objects
Follow these steps to create the JNDI/MQ objects:
1.Use Qshell to create the objects. Enter the STRQSH command.
2.Change the directory, using cd directory name, to where you installed the JMSAdmin files, for example:
cd /OrderManagement/Build/mq
3.Type the following command:
JMSAdmin.sh
Press Enter. The JMSAdmin tool creates the objects within the namespace stated in your JMSAdmin.config file.
4.Type the following commands in the order shown in your qsh session. Press Enter after you enter each command:
Note: You must use the exact case as shown here.
def ctx(geac) change ctx(geac)
def qcf(CallConnectQueueManager) qmgr(CALLCONNECTQM)
def q(SalesOrderQueue) qmgr(CALLCONNECTQM) queue(SALESORDER.QUEUE) end
You have now created your JNDI/MQ objects. Press F3 to exit Qshell.
Standard properties
Add the following properties to your standard.properties file either on the iSeries server or client:
MQ.queue.manager=geac/CallConnectQueueManager
MQ.queue=geac/SalesOrderQueue
messaging=1
You can also add “fakeunusual=1” if you want to test unusual messages through JMS or MQSeries.
Chapter 3. Installing and setting up call.connect 35
