Overview
As part of the installation process, you can configure TIBCO EMS or WebSphere MQ for TIBCO MDM. In general, this involves creating queues and configuring associated property files.
Pre-defined Queues and Topics
TIBCO MDM provides some pre-defined queues and topics; for a complete list of queues and topics, refer the TIBCO MDM System Administrator’s Guide (Queue Management chapter).
Queue and topic names can also be customized.
If TIBCO MDM changes the format of these configuration files in the future, all customizations made to these files may need to be applied to new files shipped with the new version of TIBCO MDM.
Mapping between logical and physical queue and topic names can be done using Configurator.
Configuring TIBCO EMS
|
29Configuring TIBCO EMS
Ensure that the EMS Server is running. The required queues and topics are located in the $MQ_HOME/bin/createQueues.txt file.
To create Queues:
1. Go to All Programs > TIBCO > TIBCO EMS <version> and click Start EMS Administration Tool. The command prompt is displayed.
2. Type Connect.
3. Enter login name and password.
The connected to: tcp://localhost:<port_number> message is displayed.
4. Copy content createQueues.txt file and place it in the command prompt.
Queues are created.
To verify Queues and Topics:
1. Type show queues in the command prompt and press Enter. A list of created queues is displayed.
2. Type show topics in the command prompt and press Enter. A list of created topics is displayed.
If you have not created the administration credentials, press Enter. By default, admin login name and password is retrieved.
For TIBCO MDM 8.x versions with EMS 6.x, while creating queues and topics using the $MQ_HOME/bin/createQueues.txt script; Queues can be created using the command create queue Q_ECM_CORE_WORKFLOW store=$sys.failsafe
Topics can be created using the following command create topic T_ECM_CORE_ADMIN store=$sys.failsafe
30
|
Chapter 2 Configuring Java Messaging ServerConfiguring WebSphere MQ
A shell script for creating WebSphere MQ queues - TibcoMqseries.sh- is included with the TIBCO MDM build jar file. This script is located in the
$MQ_HOME/bin directory.
Creating WebSphere MQ Queue Manager and Queues
To create WebSphere MQ queue manager and queues:
1. Set the MQSERIES_HOME environment variable.
$ export MQSERIES_HOME=/opt/mqm
2. Set the environment variable MQMGR. It is recommended that the queue manager conforms to the QM_eCM<hostname> naming convention.
$ export MQMGR=QM_eCM<hostname>
3. Copy the $MQ_HOME/bin/tibcoMQSeries.sh to $MQSERIES_HOME/bin. 4. Go to the /opt/mqm directory.
$ cd /opt/mqm
5. Make the shell script executable.
$ chmod +x tibcoMQSeries.sh
6. To see your options, run the tibcoMQSeries script file.
$ ./tibcoMQSeries.sh -printSpecDetails: Print Specific values of All Queues -setDefaultQueueMgr: Set Default Queue Manager -startQueues <QMGR Port>: Start All Queues : QMGR Port is Optional
: Default port 1414 is used if not specified
-startQueueMgr: Start Queue Manager -stopQueues: Stop All Queues -stopQueueMgr: Stop Queue Manager
7. Create all queues needed to run TIBCO MDM.
a. To create a queue manager with the name defined by the MQMGR
environment variable, enter the following command. This command also starts the Queue Manager.
$./tibcoMQSeries.sh -createQueueMgr
Configuring WebSphere MQ
|
31b. To create all queues and topics, enter:
$./tibcoMQSeries.sh -createQueues
c. To start all queues, and start the broker, channel, and listener, enter:
$./tibcoMQSeries.sh -startQueues <QMGR Port>
8. Run the following script to create queues required while using JMS. These queues are internally used by MQ series.
runmqsc MQMGR < ..\Java\bin\MQJMS_PSQ.mqsc
Changes to Configuration Files
You need to change the following properties in the Configurator. This is a minimum list of properties. If you are using a clustered environment, you need to configure cluster-related properties as well.
You can provide a specific Channel Name or accept the default SCC_ECM.
If no port number is specified, the listener is started on default port number 1414.
Ensure that the listener and channel manager are running and the listener control type is Queue Manager.
32
|
Chapter 2 Configuring Java Messaging ServerBus Setup
Queue Setup
Property Description
cluster Switch for selecting Messaging software
MQ Series Cluster Server
List Group level name for MQSeries related properties.
MQ Series Connection
Factory Queue Manager Specifies the Queue Manager. Associate physical queue manager to the logical name.
MQ Series Connection
Factory Host Name Specifies the machine on which the Queue manager is located.
MQ Series Connection
Factory Port Number Specifies the port number assigned to the Queue manager. If not specified, the default is 1414.
MQ Series Connection
Factory Channel Name Specifies the name of the server channel assigned.
Property Description
Cluster Association Switch for selecting Messaging software.
MQ Series Cluster
Name Group level name for MQSeries related properties.
MQ Series Queue
Manager Name Name of the Queue manager.
MQ Series Server Host Name of the host where MQSeries server is running.
MQ Series Server Port
Number Port number assigned to the Queue manager. The default is 1414.
MQ Series Coded
Character Set ID Specifies the Code Set SID. This applies to all queues. If nothing is specified, the value specified during queue manager creation is used.
Configuring WebSphere MQ
|
33Changing the qm.ini Parameters
The following are recommended settings for the qm.ini file:
• Channels:
MAXCHANNELS=400 MAXACTIVECHANNELS=400
Note that number of channels will increase as more queues and TIBCO MDM servers are added.
• TCP:
KeepAlive=Yes HBINT = 60 secs
• Log:
LogPrimaryFiles=8 LogSecondaryFiles=4 LogFilePages=4096 LogType=CIRCULAR
qm.ini is applicable for UNIX, for Windows please refer to the appropriate WebSphere documentation.
34
|
Chapter 2 Configuring Java Messaging ServerVerifying and Testing EMS / WebSphere MQ
Verify that all processes are running: all queues, the Queue Manager, the channel, and the listener. You can test these processes using the topicChat.sh and
queueChat.sh utilities.
The topicChat.sh utility is a chat program that is invoked interactively. This utility tests the messaging framework, and verifies the connectivity to the messaging service.
Testing with the topicChat.sh, queueChat.sh and browseQueue.sh Utilities
1. Log in to your server (where TIBCO MDM is installed) using ssh or telnet.
2. Go to the $MQ_HOME/bin directory.
3. Start the utility by entering the following command:
./topicChat.sh SimpleChat
When initialization is complete, the following message is displayed:
Initialization Complete
You will be publishing to ‘Chat’ topic.
Press Enter to publish each message.
Messages are delivered as soon as they are published.
You will be listening to ‘Chat’ topic.
Type ‘P: BYE’ to stop publishing.
Type ‘L: BYE’ to stop listening.
Type ‘L: UNSUBSCRIBE’ to remove the durable listening & stop listening.
Type ‘BYE’ to exit the program.
4. Enter any text at the command line; it will be sent to the JMS server. The Chat program itself will receive the message and display it.
The messaging service should be running before you run the topicChat.sh or the queueChat.sh utility.
The following jars should be present in $MQ_HOME/thirdparty/{OS}/
• com.ibm.mq.jar
• com.ibm.mqjms.jar
• com.ibm.mq.jmqi.jar
• dhbcore.jar
• j2ee.jar
Verifying and Testing EMS / WebSphere MQ
|
355. Run queueChat.sh to test the queue configuration in the same manner as the topics.
36
|
Chapter 2 Configuring Java Messaging ServerConfiguring EMS over SSL
1. Stop the application server.
2. Edit the following values in
<EMS-Configuration>\tibco\cfgmgmt\ems\data\tibemsd.conf file
— specify the SSL protocol in the listen parameter listen= ssl://<hostname>:<portno>
— ssl_server_identity =
<TIBCO_HOME>/ems/7.0/samples/certs/server.cert.pem
— ssl_server_key =
<TIBCO_HOME>/ems/7.0/samples/certs/server.key.pem
— ssl_password = $man$WjtSRCpaXu7hoTkDlcEPr6KNKRr
— ssl_server_trusted =
<TIBCO_HOME>/ems/7.0/samples/certs/client_root.cert.pem
3. Start EMS server using updated tibemsd.conf file.
— <TIBCO_HOME>/ems/7.0/bin/tibemsd –config
<EMS-Configuration>/tibco/cfgmgmt/ems/data/tibemsd.conf
4. The EMS server will now be running over SSL.
Ensure that tibcrypt.jar is in the CLASSPATH of the application server.
Configuring EMS over SSL on Websphere
|
37Configuring EMS over SSL on Websphere
1.
1. Stop the application server.
2. Copy slf4j-api-1.4.2.jar, slf4j-simple-1.4.2.jar and tibcrypt.jar from $EMS_HOME/lib to $WAS_HOME/lib/ext folder.
3. Go to the Configurator -> Queue Setup -> Messaging Cluster -> TIBCO EMS.
— Set TIBCO EMS Server Connection URL Change as
ssl://<hostname>:<portno>
4. Go to Bus Setup -> Cluster -> TIBCO EMS.
— - Set Localhost Server Connection URL Change as
ssl://<hostname>:<portno>
5. Go to the Configurator ->InitialConfig -> Member1 -> Security Provider ->
IBM
— change the value of SSL Protocol Handler Package property from:
com.ibm.net.ssl.internal.www.protocol to:
com.ibm.net.ssl.www2.protocol
— change the value of SSL Provider property from:
com.ibm.jsse.JSSEProvider to:
com.ibm.jsse2.IBMJSSEProvider2
6. Add the following in the JVM arguments:
— Dcom.tibco.tibjms.naming.security_protocol=ssl
— Djsse.providerClass=com.ibm.jsse2.IBMJSSEProvider2
— Dcom.tibco.tibjms.ssl.expected_hostname=server
— Dcom.tibco.tibjms.ssl.enable_verify_host_name=false
— Dcom.tibco.tibjms.ssl.enable_verify_host=false
38