Updating WebSphere MQ configuration

The WebSphere® MQ configuration affects event notifications so that Global Mailbox sends events to registered applications, including Sterling B2B Integrator, to perform routing rules. You can modify event notifications based on your requirements.

1. Locate the /<install_dir>/MailboxUtilities/admin/bin directory (UNIX/Linux) or \<install_dir>\MailboxUtilities\admin\bin directory (Windows).
   Tip: Replace <install_dir> with the directory where your instance is installed.
2. Optional: To see the available options, run the ./appConfigUtility.sh (Linux® or UNIX) or appConfigUtility.bat (Windows).
3. To modify WebSphere MQ configuration for each data center, type ./appConfigUtility.sh setMQConfig (Linux or UNIX) or appConfigUtility.bat setMQConfig command (Windows).
4. Enter the following parameters and values to suit your needs, in the format: ./appConfigUtility.sh setMQConfig <parameter="value"> (Linux or UNIX) and appConfigUtility.bat setMQConfig <parameter="value"> (Windows).

   --appName

   The name of the application. This name is displayed in the Application field in the user permissions wizard in Global Mailbox. For example:

   --appName="B2Bi"

   --dcName

   The name of a data center to configure WebSphere MQ for. Specifying a value for this parameter is required. The following value is an example for the --dcName parameter:

   --dcName="DC1"

   --qmgr

   The name of the queue manager for the data center specified for the --dcName parameter.

   --connList

   The list of all queue manager instances (active and standby) that reside on the data center specified for the --dcName parameter, in the format host(port).

   --mqUser

   A user name to authenticate to the queue manager.

   --mqPassword

   The password of the user specified for the --mqUser parameter.

   --channelName

   The name of a WebSphere MQ server connection channel used to connect to the queue manager.

   --appQueue

   The name of the queue that the Global Mailbox Event Rule Adapter listens to in order to receive events.

   --test

   Tests the connection to WMQ if specified, and saves the changes only if the connection is successful. Optional.

   Example

   ./appConfigUtility.sh setMQConfig --appName=B2Bi --dcName=<dc name> --qmgr=<queue manager for dc>
    --channel=<channel name for dc> --connList=<connection list for dc> --appQueue=<B2Bi queue for dc>
    --mqUser=<WMQ user for dc> --mqPassword=<password of mqUser> --adminUser=admin --adminPassword=password --test

   --adminUser

   Global Mailbox administrator user. Optional. Utility prompts for value if not provided. For example:

   --adminUser="userid"

   --adminPassword

   Global Mailbox administrator password. Required if --adminUser is specified. Otherwise, utility prompts for value. For example:

   --adminPassword="password"

   --appName

   The name of the application. This name is displayed in the Application field in the user permissions wizard in Global Mailbox. For example:

   --appName="application_name"

   --enable

   You can enable or disable event notifications with this parameter. Set the value to true to enable event notifications for Sterling B2B Integrator, or set the value to false to disable event notifications. For example:

   --enable="true"

   --processingType

   Specify the processing type for events.

   Valid value for this parameter is distributed. The event can be assigned to the message queue for processing when the message payload replicates to all data centers in the Global Mailbox system.

   --processingType="distributed"

   --dcList

   The list of the data center names for all of the data centers in the Global Mailbox system that a message must replicate to for the event processing status to be complete.

   Restriction: To configure dcList, the --processingType must be configured for distributed processing.

   Use commas to separate the list of data center names for the --dcList parameter. The default value is *, which configures replication to all data centers in the Global Mailbox system:

   --dcList="DC1,DC2,DC3,DC4,DC5"

   --mqType

   Specify the message broker the mailbox application uses. Valid value is webspheremq:

   --mqType="webspheremq"

   --mqHost

   Specify the host name or IP address of the message broker that Global Mailbox publishes events to. For example:

   --mqHost="192.168.37.1"

   --mqPort

   The port number of the message broker that Global Mailbox publishes events to. For example:

   --mqPort="1414"

   --mqUser

   The user ID that is used to authenticate the connection between Global Mailbox and the message broker. For example:

   --mqUser="mquser"

   --mqPassword

   The password that is used to authenticate the connection between Global Mailbox and the message broker. For example:

   --mqPassword="mqpassword"

   --endPoint

   The name of the queue that Global Mailbox publishes events to. For example:

   --endPoint="MESSAGE_EVENT_Q2"

   --channel

   A server connection channel name, specific to WebSphere MQ. For example:

   --channel="SYSTEM.DEF.SVRCONN"

   Restriction: Use the same channel name that you provide for the queue manager. Otherwise Sterling B2B Integrator is not able to connect to the queue manager.

   --qmgr

   The queue manager name for WebSphere MQ. For example:

   --qmgr="DISTMBX_QM"

   --connList

   A comma separated list of the IP addresses and the corresponding ports of each WebSphere MQ server in the Global Mailbox system:

   --connList="localhost(1514),localhost(1515),localhost(1516)"

   --test

   An optional parameter that tests the connection to the message broker with the specified parameters. No values need to be specified for this parameter.