PMQ 2.0: Setting up PMQ-ESB Windows development environment
Author: Sumitha Mp/India/IBM :8+ years of experience in various integration technologies such as
WebSphere Message Broker, IBM Integration Bus, DataPower, WebSphere MQ.
Current Role: Integration Specialist in PMQ project
Vrunda R Negandhi/India/IBM : 8+ years of experience in J2EE platform and integration technologies such as
WebSphere Message Broker, IBM Integration Bus, DataPower.
Current Role: Integration Specialist in PMQ project
Introduction:
The article describes the detailed steps on how to set up PMQ development environment for ESB on
windows. This article is targeted at architects and developers implementing PMQ for various customers
Software requirement for development environment
IBM Integration Bus Toolkit 9.0.0.1
IBM WebSphere MQ 7.5.0.2
PMQ Development Environment set up
1. WorkSpace Setup

Open IBM Integration Toolkit : All Programs > IBM Integration Toolkit > IBM Integration
Toolkit 9.0.0.1

Select the workspace and then click “OK”
2. Import Project Interchange
 Copy the required project interchange from the installation path of PMQ on Linux environment
PMQ Project interchange path on Linux: /var/PMQ/MQSIFileInput/PMQSource
Below given are the lists of project interchange
Project Interchange
PMQMasterDataLoad_PI.zip
PMQEventDataLoad_PI.zip
PMQQEWSInspection_PI.zip
PMQQEWSWarranty_PI.zip
PMQQEWSIntegration_PI.zip
PMQMaintenance_PI.zip
PMQTopNFailure_PI.zip
PMQModelTraining_PI.zip
PMQMaximoIntegration_PI.zip (optional)

Feature/Functionality associated
Master data loading
Event loading and processing
Inspection and Warranty
Maintenance
Top N Failure
Integration Analytics
Maximo Integration
To import the project interchange: In IBM Integration Toolkit , Go to File > Import > Other >
Project Interchange > Click “Next” > Browse the Project Interchange file > Click “Select All” to
import all the projects to workspace > Click “Finish”
3. Deployment
 Before connecting the remote broker , ensure that the remote connectivity is enables on the
server to connect
On the esb node which is linux, start a queue manager listener running at the default port.
 runmqlsr -m pmqmanager -p 1414 -t tcp &
 Issue the queue manager commands to


Enable CHLAUTH for queue manager
Set the MCAUSER to mqm and set the right authorization as per customer’s
requirement and security setting for the server connection channel
Remove all users from block user list.

For eg:
runmqsc pmqmanager
ALTER QMGR CHLAUTH(ENABLED)
SET CHLAUTH(SYSTEM.BKR.CONFIG) TYPE(ADDRESSMAP) ADDRESS(*)
MCAUSER('mqm')
SET CHLAUTH(SYSTEM.BKR.CONFIG) TYPE(BLOCKUSER)
USERLIST('*NOACCESS')

To connect to remote PMQ broker: In Toolkit, Go to Integration Nodes view > Right Click on
Integration Nodes > Click on ‘Connect to a Remote Integration Node’ > Enter queue manager
name,ESB server ip and port > Click ‘Finish’

To create bar file , Go to File > New > Integration Bus – Application Development > BAR file >
Next > Provide bar file name > Finish > Add the application > Click ‘Build and Save’

To deploy bar file , Right click on the bar > select ‘Deploy’ > select the remote broker and
execution group
Setting up local broker on windows for a customer who has IBM
Integration Broker installed (Optional)
1. Create the broker and execution broker on local system
 To create a local broker , in IIB Toolkit , Go to Integration Nodes view > Right Click on ‘New’
>Click on’Local Integration Node’ > Enter new broker,queue manager name and execution
group as shown in below screenshot > Click ‘Finish’
4. JDBC configuration
Below command needs to be executed from IBM Integration Console to make JDBC connection from
broker to the existing PMQ database
mqsicreateconfigurableservice
mqsisetdbparms
mqsichangeproperties
mqsichangeproperties
Eg
mqsicreateconfigurableservice pmqbroker -c JDBCProviders -o PMQ -n
connectionUrlFormat,databaseName,description,jarsURL,portNumber,serverName,type4DatasourceCla
ssName,type4DriverClassName -v
"jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];password=[password];,IBMPMQ,I
BMPMQ Database,C:\Program
Files\IBM\SQLLIB\java,50000,127.0.0.1,com.ibm.db2.jcc.DB2XADataSource,com.ibm.db2.jcc.DB2Dr
iver"
mqsisetdbparms pmqbroker -n jdbc::SP2identity -u username -p password
mqsichangeproperties pmqbroker -c JDBCProviders -o PMQ -n securityIdentity -v SP2identity
mqsichangeproperties pmqbroker -c JDBCProviders -o PMQ -n type4DatasourceClassName -v
com.ibm.db2.jcc.DB2XADataSource
5. Queue creation
 Copy Queues.txt from the installation path of PMQ on Linux environment to local system
PMQ Queues.txt path on Linux: /var/PMQ/MQSIFileInput/properties
 To create queues, Go to command prompt and do ‘runmqsc pmqmanager’ > Copy the content of
Queues.txt to the command prompt
6. Foundation configurations
 Copy foundation related jar files and xml files from shared-classes path on Linux environment to
shared-classes on Windows
Shared-classes path on Linux: /var/mqsi/shared-classes
Shared-classes path on Windows 7: C:\ProgramData\IBM\MQSI\shared-classes
7. Setting input file directory
 Input file directory for the message flows to pick up the files should be set up.
Create MQSIFileInput directory and create below set of sub-directories under that
masterdatain
eventdatain
batchdatain
maximointegration
error
restricted
properties
log
8. Configuring input directories and files
MQSIFileInput:
 Create the input directories- masterdatain, eventdatain, properties, batchdatain, integrationin ,
maximointegration ,log , error, restricted

Copy credentials.properties from /var/PMQ/MQSIFileInput/restricted to the restricted folder of
windows

Copy all the properties file from /var/PMQ/MQSIFileInput/properties to the properties folder of
windows
Shared-classes:
 Copy all folders and files from /var/mqsi/shared-classes to shared-classes folder of windows
Below given is the complete set of files and folders to be copied
9. Setting the classpath
 To add MQSIFileInput and shared-classes path to the Classpath , Right Click on My Computer
> Open System settings > Open Environment Variable setting > In classpath system variable add
the complete path for MQSIFileInput and shared-classes directory
10. Enable foundation logging for broker
 To enable foundation logging for broker , execute the below command
mqsichangeproperties BrokerName -e ExecutionName -o ComIbmJVMManager -n jvmSystemProperty
-v-Dlog4j.configuration=file:///Log4jPropertiesFile
For eg :
mqsichangeproperties pmqbroker -e default -o ComIbmJVMManager -n jvmSystemProperty -vDlog4j.configuration=file:///C:\MQSIFileInput\properties\log4j.properties
11. Deployment on local broker
 Before deploying the bar files, ensure that the correct end point urls are set in the message flows
To deploy bar file, right click on the bar file > click on deploy > select broker and execution group and
click ‘Finish’