Create and configure the MQe QueueManager.
The file mqeconfig.jar placed in TDI_Install_dir/pwd_plugins/jars contains a utility program (MQe Configuration Component) that automatically creates and configures the MQe QueueManager that is used by the Storage Component.
When specifying Windows filepaths in the property files, the backslash file separator ( \ ) must be escaped with a second backslash ( \\ ).
clientRootFolder=C:\\Program Files\\IBM\\TDI\\V7.1\\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.1\\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
When specifying Windows filepaths in the property files, the backslash file separator ( \ ) must be escaped with a second backslash ( \\ ).
The serverRootFolder property is not used when configuring the Storage Component (it is used to configure the QueueManager at the MQe Connector) and its value is not taken into account here.
.\mqeconfig.bat ..\etc\mqeconfig.props create client
The log of this command is displayed on the console. After successful completion, the message Client MQe configuration successfully completed displays. If the mqeconfig.props file contains the optional parameters for MQe authenticated access, this step will automatically request the necessary certificates from the MQe Mini-Certificate server.
Tip: If attempting to perform an MQe certificate authenticated access deployment, it is important to remember that certificates may be requested once only per authenticate-able entity. If an exception message similar to the one below is reported during configuration, it may be necessary to re-enable certificate issue for that entity 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)
If we need to change the configuration of the QueueManager, we have two options: