IBM WebSphere Message Broker 6.1 installation in AIX

1. Create two groups mqm and mqbrkrs
2. Create a user mqm and add to mqm/mqbrkrs groups
3. install WebSphere MQ V6.0

WMB - Detailed steps - Deploy application using external(MS SQL server 2005 express) database

Prerequisites - the following software must be installed on the windows XP

Websphere MQ V6
Websphere Message Broker Toolkit V6.1
Microsoft SQL Server 2005 Express


Let us deploy a message flow application in the Websphere Message Broker toolkit with the database Microsoft SQL Server Express 2005 on Windows XP. To achieve this purpose, we need to have

1. A Database named "ROHINIDB" to store the Broker configuration (repository).
2. A Database user "rohini" for the database
3. Datasource named "ROHINIDBDS" for the database ROHINIDB.
4. Queue Manager "ROHINIBKR_QMGR" for the Broker
5. Queue Manager "ROHINICFGMGR_QMGR" for the configuration Manager
6. Broker "ROHINIBKR"
7. Configuration Manager "ROHINICFGMGR"


1. Creating "ROHINIDB"

Programs -> Microsoft SQL Server 2005 -> SQL Server Management Studio Express
Login with the userid/password authorised to create the database

Creating a database by name ROHINIDB
If you observe there are no tables that are populated under this database.

2. Creating user "rohini"

Create a user(rohini) for the ROHINIDB
right click on Login -> new login and provide the name(rohini) for the database(ROHINIDB).

Now it's time to configure the most important part, the driver for using the database ROHINIDB on Microsoft SQL Server 2005 Express. The supported driver in this case is "SQL Native Client"

3. Creating Data source "ROHINIDS"

Goto Administrative Tools -> Data sources -> System DSN -> click "add" and select the driver to setup a data source for.
Provide the data source name
SQL Server you want to connect(In this case "hostname\SQLEXPRESS")
select the default database you want to use (In this case "ROHINIDB")
the authenticity of the database is checked
the connection to the database can be tested from the same wizard


4. Create Queue managers for Broker

crtmqm ROHINIBKR_QMGR

WebSphere MQ queue manager created.
Creating or replacing default objects for ROHINIBKR_QMGR.
Default objects statistics : 43 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.


C:\Documents and Settings\skamani>dspmq

QMNAME(ROHINIBKR_QMGR) STATUS(Ended immediate
ly)
QMNAME(WBRK61_DEFAULT_QUEUE_MANAGER) STATUS(Quiescing)
QMNAME(WMB61_QUEUE_MANAGER) STATUS(Quiescing)

C:\Documents and Settings\skamani>strmqm ROHINIBKR_QMGR

WebSphere MQ queue manager 'ROHINIBKR_QMGR' starting.
5 log records accessed on queue manager 'ROHINIBKR_QMGR' during the log replay p
hase.
Log replay for queue manager 'ROHINIBKR_QMGR' complete.
Transaction manager state recovered for queue manager 'ROHINIBKR_QMGR'.
WebSphere MQ queue manager 'ROHINIBKR_QMGR' started.



5. Create Queue managers for Configuration Manager

C:\Documents and Settings\skamani>crtmqm ROHINICFGMGR_QMGR

WebSphere MQ queue manager created.
Creating or replacing default objects for ROHINICFGMGR_QMGR.
Default objects statistics : 43 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.

C:\Documents and Settings\skamani>strmqm ROHINICFGMGR_QMGR

WebSphere MQ queue manager 'ROHINICFGMGR_QMGR' starting.
5 log records accessed on queue manager 'ROHINICFGMGR_QMGR' during the log repla
y phase.
Log replay for queue manager 'ROHINICFGMGR_QMGR' complete.
Transaction manager state recovered for queue manager 'ROHINICFGMGR_QMGR'.
WebSphere MQ queue manager 'ROHINICFGMGR_QMGR' started.


The queue managers have been created and started. However, the queues for communication need to be created for testing the message flow application(firstFlow.msgflow) given as an example for setting up the default configuration.


Create the following objects under the ROHINIBKR_QMGR

Queues

• BKRTQ - Transmit queue
• VIC_INPUT
• VIC_OUTPUT

Channels

• BKR_TO_CFG - SENDER (SDR)
• CFG_TO_BKR - RECEIVER(RCVR)

Listener

• create your own listener or use the SYSTEM.DEFAULT.LISTENER.TCP. For this example change the control parameter to QMGR and port at 2222.
  

Create the following objects under the ROHINICFGMGR_QMGR

Queues

• CFGTQ - Transmit queue

Channels

• BKR_TO_CFG - RECEIVER(RCVR)
• CFG_TO_BKR - SENDER(SDR)

Listener

• create your own listener or use the SYSTEM.DEFAULT.LISTENER.TCP. For this example change the control parameter to QMGR and port at 3333.
  

6. Creating the Broker

Now start the WMB Command console.
start -> programs -> Message Broker 6.1 -> command console

Create the Queue Managers for Configuration Manager, Broker and Database through the MQ explorer or through MQSC commands. The queue managers used in these commands, if not created before executing these commands, it creates the queue managers with the names specified in the command to create the Broker and config Mgr.

ROHINICFGMGR_QMGR - Queue manager for Configuration Manager
ROHINIBRK_QMGR - Queue manager for Broker

7. Create a Configuration Manager

Configuration manager(ROHINICFGMGR)

C:\IBMWMQ\WMB\bin>mqsicreateconfigmgr.exe ROHINICFGMGR -i mqadmin -a pass1234 -q ROHINICFGMGR_QMGR

AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion.

C:\IBMWMQ\WMB\bin>mqsicreatebroker.exe ROHINIBKR -i mqadmin -a pass1234 -q ROHINIBKR_QMGR -n ROHINIDBDS -u rohini -p pass1234

AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion.

C:\IBMWMQ\WMB\bin>mqsistart ROHINICFGMGR

WebSphere MQ queue manager running.
BIP8096I: Successful command initiation, check the system log to ensure that the
component started without problem and that it continues to run without problem.


C:\IBMWMQ\WMB\bin>mqsistart ROHINIBKR

WebSphere MQ queue manager running.
BIP8096I: Successful command initiation, check the system log to ensure that the
component started without problem and that it continues to run without problem.


=========================================================
Now that the environment is ready, we can start deploying applications or message flows on to the broker. Open the Websphere Message broker toolkit v6.1 and perform the following steps
=========================================================

1. select the workspace and go to the Broker administration perspective
2. Create a new domain connection by right clik on the DOMAIN CONNECTION.
3. Provide the cfg manager queue name and port number and click next
4. Provide the project name(RohiniProject) and connection name(Domain connection name --- RohiniDomain)
5. You can develop a sample application through the broker development perspective
6.
5.

Understanding of Websphere Message Broker

What is distributed messaging?

Applications in an organization or across organizations might be running on various platforms.

The applications might be developed in different languages using different protocols. Hence the message format/language/protocols in which the applications exchange messages will be different.

Communication through messages between applications on distributed environment is known as distributed messaging

What is the need to integrate applications on distributed environments? Is the integration of applications not easy without brokers?

Integrating applications is recommended with the rapid growing business needs in distributed environment.

For instance, The message sent by an application may not understandable by the target application. Therefore, the integration of such applications becomes very complex if we do not have any interface/ broker in between to make the communication easier.

For example: Consider an example where a customer reaches a travel agency.

There is an application A which needs to talk to application B to achieve the business objective. However A and B are written in different languages. Therefore for application A to communicate with application B, B should understand the message sent by A. This logic needs to be embedded into application B. And if B needs to send any acknowledgement to A, application A should have the capability to understand the message sent by B.

This becomes very complex with more number of applications in an enterprise.

What is a Message Broker?

Broker is a powerful broker that allows messages to flow between disparate applications across multiple hardware and software platforms. Using the message broker capabilities, business rules can be applied to these messages to route, transform and enrich information.

What are the features/Capabilities of Websphere Message broker?

Message routing

Transformation & Enrichment

Publish/subscribe

What are the different components of the Websphere Message broker runtime environment?

• Broker
• Execution groups
• Configuration Manager
• Broker domain
• User Name Server

How do you connect/disconnect to a broker domain?

There are two ways to connect to a broker domain

1. Websphere Message Broker Toolkit

2. Configuration Manager Proxy Java API

How do you stop the message flows running in WMB Toolkit?

On the Broker toolkit Broker administration perspective, navigate to

Broker topology

Broker

Execution groups

message flows - right click and stop it.

WMB - Default configuration - detailed steps

Verifying that the default queue manager [WBRK61_DEFAULT_QUEUE_MANAGER] does not already exist.

The task succeeded

Verifying that the default broker [WBRK61_DEFAULT_BROKER] does not already exist.

The task succeeded

Verifying that the default broker database [DEFBKD61] does not already exist.

The task succeeded

Verifying that the default Configuration Manager [WBRK61_DEFAULT_CONFIGURATION_MANAGER] does not already exist.

The task succeeded

Verifying that the local domain connection file does not already exist.

The task succeeded

Creating the database [DEFBKD61] for the default broker.

The database was created using Cloudscape.

The task succeeded

Creating the Configuration Manager. [WBRK61_DEFAULT_CONFIGURATION_MANAGER]

The task succeeded

Creating the default broker. [WBRK61_DEFAULT_BROKER]

The task succeeded

Changing the configuration of the default broker. [WBRK61_DEFAULT_BROKER]

The task succeeded

Creating a listener for queue manager [WBRK61_DEFAULT_QUEUE_MANAGER] on port 2414.

The task succeeded

Setting the service [IBM MQSeries Broker WBRK61_DEFAULT_CONFIGURATION_MANAGER] to start automatically.

The task succeeded

Setting the service [IBM MQSeries Broker WBRK61_DEFAULT_BROKER] to start automatically.

The task succeeded

Setting the Configuration Manager's Queue Manager automatic startup property.

The task succeeded

Starting the Configuration Manager [WBRK61_DEFAULT_CONFIGURATION_MANAGER].

The task succeeded

Starting the default broker [WBRK61_DEFAULT_BROKER].

The task succeeded

Creating the local domain connection [LocalDomain.configmgr].

The task succeeded

Deploying the broker topology.

The task succeeded

++++++++++

All tasks were completed successfully.

++++++++++

FROM THE LOG

========================

========================

May 6, 2010 2:25:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:25:47 EDT 2010]

May 6, 2010 2:25:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Checking for the Default Configuration

May 6, 2010 2:25:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

BIP8099I: DbInstMgr: DatabaseInstanceMgr6 -

BIP8071I: Successful command completion.]

Stderr: []

May 6, 2010 2:25:48 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:25:48 EDT 2010]

May 6, 2010 2:25:48 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Checking for the Default Configuration

May 6, 2010 2:25:49 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

BIP8099I: DbInstMgr: DatabaseInstanceMgr6 -

BIP8071I: Successful command completion.]

Stderr: []

May 6, 2010 2:26:15 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Problem: can't query windows registry for MQ Server Version Number

May 6, 2010 2:26:24 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:26:24 EDT 2010]

May 6, 2010 2:26:24 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Verifying that the default queue manager [WBRK61_DEFAULT_QUEUE_MANAGER] does not already exist.

May 6, 2010 2:26:24 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: []

May 6, 2010 2:26:25 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:26:25 EDT 2010]

May 6, 2010 2:26:25 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Verifying that the default broker [WBRK61_DEFAULT_BROKER] does not already exist.

May 6, 2010 2:26:25 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

BIP8013E: Component does not exist.

A component may only be used if it has first been created.

No user action required.]

Stderr: []

May 6, 2010 2:26:30 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:26:30 EDT 2010]

May 6, 2010 2:26:30 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Verifying that the default broker database [DEFBKD61] does not already exist.

May 6, 2010 2:26:30 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [C:\Program Files\IBM\SDP70Shared\plugins\com.ibm.etools.mft.eou.win32_6.1.200.v20081119_1245>db2 start database manager

DB20000I The START DATABASE MANAGER command completed successfully.

C:\Program Files\IBM\SDP70Shared\plugins\com.ibm.etools.mft.eou.win32_6.1.200.v20081119_1245>echo off

C:\Program Files\IBM\SDP70Shared\plugins\com.ibm.etools.mft.eou.win32_6.1.200.v20081119_1245>db2 terminate

DB20000I The TERMINATE command completed successfully.

C:\Program Files\IBM\SDP70Shared\plugins\com.ibm.etools.mft.eou.win32_6.1.200.v20081119_1245>echo off

C:\Program Files\IBM\SDP70Shared\plugins\com.ibm.etools.mft.eou.win32_6.1.200.v20081119_1245>db2 list database directory

System Database Directory

Number of entries in the directory = 1

Database 1 entry:

Database alias = BRKDB1

Database name = BRKDB1

Node name = DBIMCNS

Database release level = a.00

Comment =

Directory entry type = Remote

Authentication = SERVER

Catalog database partition number = -1

Alternate server hostname =

Alternate server port number =

C:\Program Files\IBM\SDP70Shared\plugins\com.ibm.etools.mft.eou.win32_6.1.200.v20081119_1245>echo off]

Stderr: []

May 6, 2010 2:26:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:26:31 EDT 2010]

May 6, 2010 2:26:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Verifying that the default Configuration Manager [WBRK61_DEFAULT_CONFIGURATION_MANAGER] does not already exist.

May 6, 2010 2:26:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

BIP8013E: Component does not exist.

A component may only be used if it has first been created.

No user action required.]

Stderr: []

May 6, 2010 2:26:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:26:31 EDT 2010]

May 6, 2010 2:26:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Verifying that the local domain connection file does not already exist.

May 6, 2010 2:26:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: []

May 6, 2010 2:26:48 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:26:48 EDT 2010]

May 6, 2010 2:26:48 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Creating the database [DEFBKD61] for the default broker.

May 6, 2010 2:26:48 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>CALL mqsicreatedb DEFBKD61 -i mqadmin -a ********

BIP9828I: Connecting to the Cloudscape Network Server on port 1527.

BIP9809I: Creating Derby Database 'DEFBKD61', this may take a while.

BIP9829I: Cataloguing the 'Derby' database 'DEFBKD61'.

BIP9818I: IBM Cloudscape/Apache Derby was used to create the 'DEFBKD61' database.

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: []

May 6, 2010 2:27:46 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:27:46 EDT 2010]

May 6, 2010 2:27:46 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Creating the Configuration Manager. [WBRK61_DEFAULT_CONFIGURATION_MANAGER]

May 6, 2010 2:27:46 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsicreateconfigmgr -i mqadmin -a ******** -q WBRK61_DEFAULT_QUEUE_MANAGER WBRK61_DEFAULT_CONFIGURATION_MANAGER

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: [WebSphere MQ queue manager created.

Creating or replacing default objects for WBRK61_DEFAULT_QUEUE_MANAGER.

Default objects statistics : 43 created. 0 replaced. 0 failed.

Completing setup.

Setup completed.

WebSphere MQ queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' starting.

5 log records accessed on queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' during the log replay phase.

Log replay for queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' complete.

Transaction manager state recovered for queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER'.

WebSphere MQ queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' started.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.]

May 6, 2010 2:28:45 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:45 EDT 2010]

May 6, 2010 2:28:45 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Creating the default broker. [WBRK61_DEFAULT_BROKER]

May 6, 2010 2:28:45 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsicreatebroker WBRK61_DEFAULT_BROKER -i mqadmin -a ******** -q WBRK61_DEFAULT_QUEUE_MANAGER -n DEFBKD61

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: [AMQ8110: WebSphere MQ queue manager already exists.

WebSphere MQ queue manager running.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.

The setmqaut command completed successfully.]

May 6, 2010 2:28:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:47 EDT 2010]

May 6, 2010 2:28:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Changing the configuration of the default broker. [WBRK61_DEFAULT_BROKER]

May 6, 2010 2:28:47 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsichangebroker WBRK61_DEFAULT_BROKER -f all

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: []

May 6, 2010 2:28:48 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:48 EDT 2010]

May 6, 2010 2:28:48 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Creating a listener for queue manager [WBRK61_DEFAULT_QUEUE_MANAGER] on port 2414.

May 6, 2010 2:28:49 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.

Starting MQSC for queue manager WBRK61_DEFAULT_QUEUE_MANAGER.

1 : DEFINE LISTENER(WBRK61_DEFAULT_QUEUE_MANAGER) TRPTYPE(TCP) PORT(2414) CONTROL(QMGR)

AMQ8626: WebSphere MQ listener created.

One MQSC command read.

No commands have a syntax error.

All valid MQSC commands were processed.

5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.

Starting MQSC for queue manager WBRK61_DEFAULT_QUEUE_MANAGER.

1 : START LISTENER(WBRK61_DEFAULT_QUEUE_MANAGER)

AMQ8021: Request to start WebSphere MQ Listener accepted.

One MQSC command read.

No commands have a syntax error.

All valid MQSC commands were processed.]

Stderr: []

May 6, 2010 2:28:49 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:49 EDT 2010]

May 6, 2010 2:28:49 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Setting the service [IBM MQSeries Broker WBRK61_DEFAULT_CONFIGURATION_MANAGER] to start automatically.

May 6, 2010 2:28:50 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: []

May 6, 2010 2:28:50 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:50 EDT 2010]

May 6, 2010 2:28:50 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Setting the service [IBM MQSeries Broker WBRK61_DEFAULT_BROKER] to start automatically.

May 6, 2010 2:28:51 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: []

May 6, 2010 2:28:52 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:52 EDT 2010]

May 6, 2010 2:28:52 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Setting the Configuration Manager's Queue Manager automatic startup property.

May 6, 2010 2:28:52 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.

Queue Manager 'WBRK61_DEFAULT_QUEUE_MANAGER' successfully set to 'Automatic' mode]

Stderr: []

May 6, 2010 2:28:55 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:55 EDT 2010]

May 6, 2010 2:28:55 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Starting the Configuration Manager [WBRK61_DEFAULT_CONFIGURATION_MANAGER].

May 6, 2010 2:28:55 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsistart WBRK61_DEFAULT_CONFIGURATION_MANAGER

BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

C:\IBMWMQ\WMBT610>exit]

Stderr: [WebSphere MQ queue manager running.]

May 6, 2010 2:28:59 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:28:59 EDT 2010]

May 6, 2010 2:28:59 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Starting the default broker [WBRK61_DEFAULT_BROKER].

May 6, 2010 2:28:59 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsistart WBRK61_DEFAULT_BROKER

BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

C:\IBMWMQ\WMBT610>exit]

Stderr: [WebSphere MQ queue manager running.]

May 6, 2010 2:29:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:29:19 EDT 2010]

May 6, 2010 2:29:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Creating the local domain connection [LocalDomain.configmgr].

May 6, 2010 2:29:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: []

May 6, 2010 2:29:22 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:29:22 EDT 2010]

May 6, 2010 2:29:22 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Deploying the broker topology.

May 6, 2010 2:29:22 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: []

WMB - Delete the default configuration in V 6.1

May 6, 2010 2:18:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:18:19 EDT 2010]

May 6, 2010 2:18:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Checking for the Default Configuration

May 6, 2010 2:18:19 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

BIP8099I: DbInstMgr: DatabaseInstanceMgr6 -

BIP8099I: Broker: WBRK61_DEFAULT_BROKER - WBRK61_DEFAULT_QUEUE_MANAGER

BIP8099I: ConfigMgr: WBRK61_DEFAULT_CONFIGURATION_MANAGER - WBRK61_DEFAULT_QUEUE_MANAGER

BIP8071I: Successful command completion.]

Stderr: []

May 6, 2010 2:18:20 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:18:20 EDT 2010]

May 6, 2010 2:18:20 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Checking for the Default Configuration

May 6, 2010 2:18:20 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

BIP8099I: DbInstMgr: DatabaseInstanceMgr6 -

BIP8099I: Broker: WBRK61_DEFAULT_BROKER - WBRK61_DEFAULT_QUEUE_MANAGER

BIP8099I: ConfigMgr: WBRK61_DEFAULT_CONFIGURATION_MANAGER - WBRK61_DEFAULT_QUEUE_MANAGER

BIP8071I: Successful command completion.]

Stderr: []

May 6, 2010 2:18:59 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:18:59 EDT 2010]

May 6, 2010 2:18:59 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Ensure that the Database Instance Manager is started.

May 6, 2010 2:18:59 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsistart DatabaseInstanceMgr6

BIP8018E: Component running.

This component is running, the command issued cannot be run against a running component.

Stop the component and reissue the command.

C:\IBMWMQ\WMBT610>exit]

Stderr: []

May 6, 2010 2:19:01 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:19:01 EDT 2010]

May 6, 2010 2:19:01 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Deleting the local domain connection [LocalDomain.configmgr].

May 6, 2010 2:19:01 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: []

May 6, 2010 2:19:15 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:19:15 EDT 2010]

May 6, 2010 2:19:15 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Stopping the default broker [WBRK61_DEFAULT_BROKER].

May 6, 2010 2:19:15 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsistop -i WBRK61_DEFAULT_BROKER

BIP8145I: Execution Group process IDs default-0 were forced to terminate.

The Broker was shutdown forcibly, this caused Execution Group processes to be killed.

This action may leave system, database, WebSphere MQ or Application resources in a locked state. Some resource locks may need freeing manually, others will not need any action to be taken.

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: []

May 6, 2010 2:19:34 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:19:34 EDT 2010]

May 6, 2010 2:19:34 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Stopping the Configuration Manager [WBRK61_DEFAULT_CONFIGURATION_MANAGER].

May 6, 2010 2:19:34 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsistop -i WBRK61_DEFAULT_CONFIGURATION_MANAGER

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: []

May 6, 2010 2:20:22 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:20:22 EDT 2010]

May 6, 2010 2:20:23 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Deleting the default broker. [WBRK61_DEFAULT_BROKER]

May 6, 2010 2:20:23 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsideletebroker WBRK61_DEFAULT_BROKER

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: [WebSphere MQ queue manager running.]

May 6, 2010 2:21:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:21:31 EDT 2010]

May 6, 2010 2:21:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Deleting the Configuration Manager.

May 6, 2010 2:21:31 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsideleteconfigmgr -q -n -w WBRK61_DEFAULT_CONFIGURATION_MANAGER

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: [WebSphere MQ queue manager running.

Waiting for queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' to end.

Waiting for queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' to end.

WebSphere MQ queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' ended.

WebSphere MQ queue manager 'WBRK61_DEFAULT_QUEUE_MANAGER' deleted.]

May 6, 2010 2:21:46 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:21:46 EDT 2010]

May 6, 2010 2:21:46 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Deleting the database [DEFBKD61] for the default broker.

May 6, 2010 2:21:46 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: [MQSI 6.1.0.3

C:\IBMWMQ\WMB

C:\IBMWMQ\WMBT610>mqsideletedb DEFBKD61

BIP9827I: Removing the ODBC Data Source name 'DEFBKD61'.

BIP9837I: Shutting down the Derby Database 'DEFBKD61'.

BIP9830I: Deleting the Derby Database 'DEFBKD61'.

BIP8071I: Successful command completion.

C:\IBMWMQ\WMBT610>exit]

Stderr: []

May 6, 2010 2:21:49 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:21:49 EDT 2010]

May 6, 2010 2:21:49 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Stopping the Configuration Manager's Queue Manager.

May 6, 2010 2:21:49 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: [AMQ8118: WebSphere MQ queue manager does not exist.]

May 6, 2010 2:21:51 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO:

+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++

TIMESTAMP [Thu May 06 14:21:51 EDT 2010]

May 6, 2010 2:21:51 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: Deleting the Configuration Manager's Queue Manager.

May 6, 2010 2:21:51 PM com.ibm.etools.mft.eou.wizards.EouWizard logAction

INFO: The above task succeeded

Collected output from task >

Stdout: []

Stderr: [AMQ8118: WebSphere MQ queue manager does not exist.

AMQ7048: The queue manager name is either not valid or not known]