MB+MQ development technology example (zero) environment construction

MB+MQ development technology example (zero) environment construction

(1) Preparations:
1. Install DB2, MQ, MB, and MessageBrokersToolkit in sequence.

2. Start DB2 and WebSphere MQ.

3. Open the IBM WebSphere Message Brokers 6.0 command console.

(2) Basic parameters:
1. System login account: Username Admin Password Admin
Note : The system account name is no more than 8 characters, and the authority is the system administrator

2.DB2 database: Username: Admin Password: Admin.

(3) Start creating an agent with the command line:
1. mqsicreatedb LROI -i Admin -a Admin -p 50000 -e "DB2"
command options:
"databaseName" is the name of the database to be created (this is LROI)
Optional:
" -i serviceUserID" The user ID under which DatabaseInstanceMgr should be running.
"-a servicePassword" Password for the DatabaseInstanceMgr user ID.
"-p portNumber" the port number that DatabaseInstanceMgr should use (default=1527)
"-e dbType" the database type to use, currently reported as: "DB2" or "Derby"

1. mqsicreatebroker LORI_BROKER -i Admin -a Admin -q LORI_QM -n LORI -u Admin -p Admin -j
   Command options:
   "brokerName" Broker name to create (this is LORI_BROKER)
   "-i serviceUserId" User ID under which to run the broker
   "-a servicePassword" Password for the broker user ID
   "-q queueManagerName" The WebSphere MQ queue manager that the broker will use. If it doesn't exist, create it.
   "-n dataSourceName" agent's database name
   "-u dataSourceUserId" agent's userid to access its database
   "-p dataSourcePassword" agent's database userid password
   "-s unsQMgrName" user name server's WebSphere MQ queue manager
   "- j" to enable publish/subscribe access control for the broker

1. mqsicreateconfigmgr LORI_ConfigMgr -i Admin -a Admin -q LORI_QM
   command option
   "configMgrName" Name of the configuration manager (can be omitted on Windows) (this is LORI_ConfigMgr)
   "-i serviceUserId" User ID to run the configuration manager under
   "- a servicePassword" password for the configuration manager user ID
   "-q queueManagerName" the WebSphere MQ queue manager that the configuration manager will use (create it if it does not exist)

1. mqsicreateusernameserver -i Admin -a Admin -q LORI_QM
   command options:
   "-i serviceUserId" User ID under which the username server will run
   "-a servicePassword" Password for the username server's user ID
   "-q queueManagerName" The username server will use WebSphere MQ queue manager (create it if it does not exist)
   

2. At this point, the proxy creation is successful. Let's start the broker with the mqsistart command.
   

3. Create a listener for this proxy.
   Start the WebSphere MQ Explorer.
   -> Advanced -> Right click on Listeners -> New -> TCP Listener...
   Name: LORI.LISTENER.TCP
   Click "Next"
   Control: Queue Manager Startup
   Port : 1414
   IP Address: Empty
   Click "Finish"
   - > Start the TCP listener LORI.LISTENER.TCP
   
   

4. Right-click [LORI_QM] and select [Remote Management] to automatically create a default channel.