MQe Queue Manager setup

You must run the WebSphere® MQ Everyplace® Configuration Component utility, which is in thetdi_install_dir/pwd_plugins/jars directory to automatically create and configure IBM WebSphere MQ Everyplace Queue Manager.

• Before you run the IBM WebSphere MQ Everyplace Configuration Component, open the TDI_install_dir/pwd_plugins/etc/mqeconfig.props properties file and set values for the following properties:

  clientRootFolder

  The folder where you want to store the IBM WebSphere MQ Everyplace Queue Manager. For example, on Windows, C:\\Program Files\\IBM\\TDI\\V7.2\\pwd_plugins\\tds\\MQePWStore.Note: When you specify the Windows file paths in the property files, the backslash file separator (\) must be escaped with a second backslash (\\).

  serverIP

  IP address of the system where the SDI and the JMS Password Store are deployed.

  communicationPort

  The TCP/IP port used for communication between the two IBM WebSphere MQ Everyplace Queue Managers.

  clientRegistryType

  Optional. Required only for authenticated IBM WebSphere MQ Everyplace access deployments. If used, value must be set to PrivateRegistry. The PrivateRegistry stores the certificates that are issued by the IBM WebSphere MQ Everyplace Mini-Certificate server.

  clientRegistryPin

  Optional. Required only for authenticated IBM WebSphere MQ Everyplace access deployments. If used, this value represents the PIN access code, which is used by the SDI JMS Password Store to access the PrivateRegistry. This value is stored as plain text in the IBM WebSphere MQ Everyplace .ini file.

  clientKeyRingPassword

  Optional. Required only for authenticated IBM WebSphere MQ Everyplace access deployments. This value is used when you request a certificate from the IBM WebSphere MQ Everyplace Mini-Certificate server. The value is the seed value for certificate generation. This value is stored as plain text in the IBM WebSphere MQ Everyplace .ini file.

  certServerReqPin

  Optional. Required only for authenticated IBM WebSphere MQ Everyplace access deployments. This value is used as a one time authentication PIN by this Queue Manager when you request certificates from the IBM WebSphere MQ Everyplace Mini-Certificate server. This value must match the Request PIN value from the Mini-Certificate server setup.

  certServerIPAndPort

  Optional. Required only for authenticated IBM WebSphere MQ Everyplace access deployments. This value is used as the destination address for IBM WebSphere MQ Everyplace Mini-Certificate server requests. The format of the value is "FastNetwork:<host>:<port> where host is the system name or TCP/ IP address where the IBM WebSphere MQ Everyplace Mini-Certificate server is running. Port value must match the port value from the Mini-Certificate server setup.

  debug

  Specify true or false to turn on or off the debug information.

  Specifying the value true collects binary trace information that is logged by the IBM WebSphere MQ Everyplace. Enabling the flag generates a single trace file in the current directory, that is, solution directory. The size of the trace file is unrestricted. The file size increases until trace collection is stopped, or there is no disk space left. Name of the file is mqe0.trc.

  The following example shows a sample mqeconfig.props configuration file:

  clientRootFolder=C:\\Program Files\\IBM\\TDI\\V7.2\\pwd_plugins\\tds\\MQePWStore
  serverIP=127.0.0.1
  #clientRegistryType=PrivateRegistry
  #clientRegistryPin=<Private client registry access PIN>
  #clientKeyRingPassword=<Seed value for certificate generation>
  
  
  # Properties used for setting up MQe Queue Manager as server
  
  serverRootFolder=C:\\Program Files\\IBM\\TDI\\V7.2\\MQePWStore
  #serverRegistryType=PrivateRegistry
  #serverRegistryPin=<Private client registry access PIN>
  #serverKeyRingPassword=<Seed value for certificate generation>
  
  #certServerReqPin=<One time certificate request PIN>
  #certServerIPAndPort=FastNetwork:<Mini-Certificate server hostname or IP>:<port>
  #certRenewalEntityName=<QueueManager name or QueueManager+Queue name>
  
  communicationPort=41001
  
  #disableQueueRegistry=
  debug=true

  Note: When you specify the Windows file paths in the property files, the backslash file separator ( \ ) must be escaped with a second backslash ( \\ ).

  The serverRootFolder property is not used when you configure the Storage Component. The property is used to configure the IBM WebSphere MQ Everyplace Queue Manager in the IBM WebSphere MQ Everyplace Connector and its value is ignored.

• To create and automatically configure the IBM WebSphere MQ Everyplace Queue Manager for the Storage Component, open a command prompt in the TDI_install_dir/pwd_plugins/bin folder and enter the following command as one line:

  .\mqeconfig.bat ..\etc\mqeconfig.props create client

  The log of this command is displayed on the console. After successful completion, the Client MQe configuration successfully completed message is displayed. If the mqeconfig.props file contains the optional parameters for IBM WebSphere MQ Everyplace authenticated access, this step automatically requests the necessary certificates from the IBM WebSphere MQ Everyplace Mini-Certificate server. Tip: If you run the IBM WebSphere MQ Everyplace certificate authenticated access deployment, certificates are requested only once per authenticate-able entity. If the following exception message is reported during configuration, re-enable certificate issue for that entity by using the Mini-Certificate server GUI.

  [MQeConfig] [28/07/05 10:10:01]: Action failed: 
  Code=351;com.ibm.mqe.MQeException: Registration exception = 
  com.ibm.mqe.MQeException: certificate request failed[PWStoreClient 4]
   (code=8)[PWStoreClient 8] (code=351) [MQeConfig] [28/07/05 10:10:01]: 
  Error: Server MQe configiration failed; exception:java.lang.Exception:
  Code=351;com.ibm.mqe.MQeException: Registration exception = com.ibm.mqe.
  MQeException: certificate request failed[PWStoreClient4] (code=8)
  [PWStoreClient 8] (code=351) 

  Note: To change the configuration of the IBM WebSphere MQ Everyplace Queue Manager, the following two options are available:
  • Delete the IBM WebSphere MQ Everyplace Queue Manager from the disk and create it by following the preceding procedure.
  • Install the IBM WebSphere MQ Everyplace admin tool compatible with IBM WebSphere MQ Everyplace 2.0.1.7 Queue Managers and use it to change the Queue Manager settings. For example, IBM WebSphere MQ Everyplace Explorer.

Parent topic:

JMS Password Store