- Create two groups mqm and mqbrkrs
- Create a user mqm and add to mqm/mqbrkrs groups
- install WebSphere MQ V6.0
Saturday, May 15, 2010
IBM WebSphere Message Broker 6.1 installation in AIX
Thursday, May 13, 2010
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
Channels
Listener
Create the following objects under the ROHINICFGMGR_QMGR
Queues
Channels
Listener
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.
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.
Saturday, May 8, 2010
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.
Thursday, May 6, 2010
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]
Tuesday, April 27, 2010
MQ Interview questions
What is MQ?
MQ stands for Message queuing. MQ allows application programs to use the message queuing to participate in message-driven processing.
what are the advantages of MQ?
- Integration
- Asynchrony
- Assured delivery
- Scalability
What is the format of the command "dspmqver"?
Version.release.modification.fixpack.
6.0.2.7
What is a user exit in terms of MQ?
Using these user exits, we can insert our code into the queue manager function.
What are the logging configuration files?
mqs.ini - config file for mq level settings
qm.ini - config file for queue manager level settings
What is the algorithm used in MQ for ensuring integrity?
Log write integrity is the algorithm used to ensure integrity. This can be changed in QM config file
Version.release.modification.fixpack.
6.0.2.7
What is a user exit in terms of MQ?
Using these user exits, we can insert our code into the queue manager function.
What are the logging configuration files?
mqs.ini - config file for mq level settings
qm.ini - config file for queue manager level settings
What is the algorithm used in MQ for ensuring integrity?
Log write integrity is the algorithm used to ensure integrity. This can be changed in QM config file
When a queue manager starts, what are the default components that start with the Queue manager?
The Queue Manager task:
- LOGGER-IO
- ERROR-LOG
- CHECKPOINT
- ASYNCQ
- EXPIRER
- STATISTICS
What is the communication protocol used by MQ Explorer to connect to the remote QMs?
TCP/IP Protocol
What is a Channel?
Channel can be depicted as a pipe/connection for communication between queue managers to exchange messages.
What are various types of channels in MQ v6?
- Sender(SDR)
- Receiver(RCVR)
- Cluster Receiver(CLUSRCVR)
- Cluster Sender(CLUSSDR)
- Server(SVR)
- Requester(RQSTR)
- Client Connection(CLNTCONN)
- Server connection(SVRCONN)
What is the purpose of Channel Initiator in MQ?
monitor the system-defined initiation queue SYSTEM.CHANNEL.INITQ
Channel Listener - listens for any incoming network requests and starts the appropriate receiver channel.
monitor the system-defined initiation queue SYSTEM.CHANNEL.INITQ
Channel Listener - listens for any incoming network requests and starts the appropriate receiver channel.
What are the types of Queues available in MQ V6?
- Local
- Alias
- Remote
- Model - dynamic queues that are created on the fly by the applications
- Cluster queue
What are the types of logging in MQ?
- Circular -lc
- Linear - ll
Inorder to instruct Websphere MQ to advance/write to a new linear log, "RESET QMGR TYPE(ADVANCELOG)"
In order to recover a queue from a media failure, what type of logging combined with messaging should be?
ans. Linear logging with persistent messaging
Name the log control file in MQ v6?
Log control file is amqhlctl.lfh
Default location of logs
- UNIX: /var/mqm/log/
- Windows: C:\Program Files\IBM\WebSphere MQ\log\
Log Defaults in UNIX:
- LogPrimaryFiles=3
- LogSecondaryFiles=2
- LogFilePages=1024
- LogType=CIRCULAR
- LogBufferPages=0
- LogDefaultPath=/var/mqm/log
What is a dead-letter queue handler? How do you invoke it?
runmqdlq - command to start the DLQ handler(monitor & handle messages in DLQ)
dead letter queue handler can be used to both select a message and perform various actions on that message. The runmqdlq command takes its input from stdin. When the command is processed, the results and a summary are put into a report that is sent to stdout. By taking stdin from the keyboard, you can enter runmqdlq rules interactively.
What is a MCA?
A Message Channel Agent(MCA) - sits at each end of the channel controlling the sending and receiving messages. MCA takes the messages from the transmission queue and puts them on the communication link(channel) between the queue managers.
What is an Initiation queue?
Queues that are used in triggering. A message is put by the queue manager on the initiation queue when the trigger event occurs
What is a Command Server in Websphere MQ z/OS?
Command Server is a component of Websphere MQ that works with command processor component.
Reads messages from system-command input queue, verifies them, passes the valid ones as commands to the command processor
command processor processes the message and replies back to the reply-to queue that is specified.
System command input queue -> SYSTEM.COMMAND.INPUT
SYSTEM.ADMIN.COMMAND.QUEUE
reply-to queue -> SYSTEM.COMMAND.REPLY.MODEL
Security/Authorization
Authorization for using MQI calls, commands and access to objects is provided by the Object Authority Manager (OAM). The “setmqaut” command is used to grant or revoke authorizations as required.
A security refresh is required after setmqaut commands are issued. This can be done by recycle of QMGR to refresh the security cache or
by runmqsc command “refresh security(*) all”
“dspmqaut” and “dmpmqaut” can be used to view authorities.
A security refresh is required after setmqaut commands are issued. This can be done by recycle of QMGR to refresh the security cache or
by runmqsc command “refresh security(*) all”
“dspmqaut” and “dmpmqaut” can be used to view authorities.
Thursday, April 15, 2010
Top 15 - Websphere MQ best practices
- Use short names for queue managers and MQ objects
- Always assign a dead letter queue (DLQ) to the queue manager
- Use standards like JMS whenever possible
- Build with performance in mind
- Avoid location assumptions and fixed queue names in programs
- When feasible, cluster your MQ servers
- Design infrastructures with fewer queue managers with more queues
- Capture completion and reason codes in all application MQI calls
- Code applications to continually process messages
- Close and disconnect connections properly
- Be aware of the different features of various MQ clients
- Use security best practices
- Restrict remote administrative authority using SYSTEM.ADMIN.SVRCONN channels on production-level (restricted-access) boxes
- Do not use the sample get/put utilities for production purposes
- Use runmqlsr in lieu of inetd listener
- Use SupportPacs to extend MQ functionality
- When not using third-party configuration tools, automate all configuration and changes via MQSC scripts
- Use the appropriate logging mechanism
- Configure automated maintenance of queue managers
- Schedule and apply fix packs on a regular basis
Monday, April 12, 2010
Triggering in MQ v6
1. Define a local queue by name TESTTRIG under the Queue Manager QM.ROH as follows:
DEFINE QLOCAL('TESTTRIG') DESCR('To test how the property trigger works')
1 : DEFINE QLOCAL('TESTTRIG') DEFPSIST(YES) DESCR('To test how the propert
y trigger works')
AMQ8006: WebSphere MQ queue created.
2. Create a process that needs to be invoked with the trigger.
DEFINE PROCESS(process_name)
[ APPLICID(string) ]
[ APPLTYPE( CICS | DEF | DOS | OS2 | UNIX | WINDOWS | WINDOWSNT |
NOTESAGENT | OS400 | integer) ]
[ DESCR(string) ]
[ ENVRDATA(string) ]
[ LIKE(process_name) ]
[ REPLACE | NOREPLACE ]
[ USERDATA(string) ]
Example:
DEFINE PROCESS('IE') DESCR('Internet explorer') APPLTYPE(WINDOWS) APPLICID('iexplore')
5 : DEFINE PROCESS('IE') DESCR('Internet explorer') APPLTYPE(WINDOWS) APPLI
CID('iexplore')
AMQ8010: WebSphere MQ process created.
DISPLAY PROCESS('IE')
6 : DISPLAY PROCESS('IE')
AMQ8407: Display Process details.
PROCESS(IE) APPLTYPE(WINDOWS)
APPLICID('iexplore')
ENVRDATA( ) USERDATA( )
DESCR(Internet explorer) ALTDATE(2010-04-12)
ALTTIME(14.09.48)
3. Created a Queue to use as an Initiation queue
DEFINE QLOCAL('trig.initq') descr('initiation queue for triggering ie')
5 : DEFINE QLOCAL('trig.initq') descr('initiation queue for triggering ie')
AMQ8006: WebSphere MQ queue created.
Enable triggering on hosting a queue "TESTTRIG"
4. ALTER QLOCAL('TESTTRIG') TRIGGER TRIGTYPE(FIRST) INITQ('trig.initq') PROCESS('IE')
6 : ALTER QLOCAL('TESTTRIG') TRIGGER TRIGTYPE(FIRST) INITQ('trig.initq') PR
OCESS('IE')
AMQ8008: WebSphere MQ queue changed.
DISPLAY QLOCAL('TESTTRIG')
5. The most important part is to START the MQ TRIGGER MONITOR and let this trigger monitor run till you need the queue to trigger the application.
C:\IBMWMQ\WebSphereMQ\bin>runmqtrm -m QM.ROH -q trig.initq
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
__________________________________________________
Waiting for a trigger message
6. Now start putting the messages in the queue TESTTRIG and notice that with every first occurence of the message in the queue manager QM.ROH, the internet explorer application opens up.
DEFINE QLOCAL('TESTTRIG') DESCR('To test how the property trigger works')
1 : DEFINE QLOCAL('TESTTRIG') DEFPSIST(YES) DESCR('To test how the propert
y trigger works')
AMQ8006: WebSphere MQ queue created.
2. Create a process that needs to be invoked with the trigger.
DEFINE PROCESS(process_name)
[ APPLICID(string) ]
[ APPLTYPE( CICS | DEF | DOS | OS2 | UNIX | WINDOWS | WINDOWSNT |
NOTESAGENT | OS400 | integer) ]
[ DESCR(string) ]
[ ENVRDATA(string) ]
[ LIKE(process_name) ]
[ REPLACE | NOREPLACE ]
[ USERDATA(string) ]
Example:
DEFINE PROCESS('IE') DESCR('Internet explorer') APPLTYPE(WINDOWS) APPLICID('iexplore')
5 : DEFINE PROCESS('IE') DESCR('Internet explorer') APPLTYPE(WINDOWS) APPLI
CID('iexplore')
AMQ8010: WebSphere MQ process created.
DISPLAY PROCESS('IE')
6 : DISPLAY PROCESS('IE')
AMQ8407: Display Process details.
PROCESS(IE) APPLTYPE(WINDOWS)
APPLICID('iexplore')
ENVRDATA( ) USERDATA( )
DESCR(Internet explorer) ALTDATE(2010-04-12)
ALTTIME(14.09.48)
3. Created a Queue to use as an Initiation queue
DEFINE QLOCAL('trig.initq') descr('initiation queue for triggering ie')
5 : DEFINE QLOCAL('trig.initq') descr('initiation queue for triggering ie')
AMQ8006: WebSphere MQ queue created.
Enable triggering on hosting a queue "TESTTRIG"
4. ALTER QLOCAL('TESTTRIG') TRIGGER TRIGTYPE(FIRST) INITQ('trig.initq') PROCESS('IE')
6 : ALTER QLOCAL('TESTTRIG') TRIGGER TRIGTYPE(FIRST) INITQ('trig.initq') PR
OCESS('IE')
AMQ8008: WebSphere MQ queue changed.
DISPLAY QLOCAL('TESTTRIG')
5. The most important part is to START the MQ TRIGGER MONITOR and let this trigger monitor run till you need the queue to trigger the application.
C:\IBMWMQ\WebSphereMQ\bin>runmqtrm -m QM.ROH -q trig.initq
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
__________________________________________________
Waiting for a trigger message
6. Now start putting the messages in the queue TESTTRIG and notice that with every first occurence of the message in the queue manager QM.ROH, the internet explorer application opens up.
Sunday, April 11, 2010
Record(rcdmimg) & Recreate(rcrmqobj) objects in MQ v6
My websphere MQ install directory on windows machine is C:\IBMWMQ\WebSphereMQ\
1. Started MQ explorer through command prompt using "runmqcfg"
2. Created a Queue manager QM.ROH -> crtmqm -q -d QM.ROH.Q.TRANQ -u QM.ROH.Q.DLQ QM.ROH with logging option "LINEAR LOGGING"
3. Created a local queue under the QM.ROH -> QM.RECD.REC
Set the message persistence on the queue so that messages are not lost at the restart of the queue manager.
4. Started putting the messages in QM.Q.RECD.REC -> amqsput QM.Q.RECD.REC QM.ROH
5. Deleted the "Q" file under C:\IBMWMQ\WebSphereMQ\data\Qmgrs\QM!ROH\queues\QM!ROH!QM!Q!RECD!REC\Q to verify the record and recreate commands provided in MQ V6
6. Stopped and restarted the Queue Manager QM.ROH using
endmqm QM.ROH
strmqm QM.ROH
C:\IBMWMQ\WebSphereMQ\bin>strmqm QM.ROH
WebSphere MQ queue manager 'QM.ROH' starting.
11 log records accessed on queue manager 'QM.ROH' during the log replay phase.
Log replay for queue manager 'QM.ROH' complete.
Transaction manager state recovered for queue manager 'QM.ROH'.
WebSphere MQ queue manager 'QM.ROH' started.
7. After having deleted the Q file for queue QM.ROH.Q.LOCALQ, when we try to view the messages in the queue QM.Q.RECD.REC,
- MQ explorer throws the error message "Object damaged. AMQ4038"
- When we do it through command line, the following error is displayed. C:\IBMWMQ\WebSphereMQ\bin>amqsbcg QM.Q.RECD.REC
AMQSBCG0 - starts here ********************** MQOPEN - 'QM.Q.RECD.REC' MQOPEN failed with CompCode:2, Reason:2101 MQDISC
8. To display the reason code in understandable format, use "mqrc" command
C:\IBMWMQ\WebSphereMQ\bin>mqrc 2101 2101 0x00000835 MQRC_OBJECT_DAMAGED
You can see that the queue manager error log(AMQERR01.log) contains the following information.
-------------------------------------------------------------------------------
4/12/2010 10:54:55 - Process(2272.1) User(skamani) Program(amqzxma0.exe)
AMQ7472: Object QM.Q.RECD.REC, type queue damaged.
EXPLANATION:
Object QM.Q.RECD.REC, type queue has been marked as damaged. This indicates
that the queue manager was either unable to access the object in the file
system, or that some kind of inconsistency with the data in the object was
detected.
ACTION:
If a damaged object is detected, the action performed depends on whether the
queue manager supports media recovery and when the damage was detected. If the
queue manager does not support media recovery, you must delete the object as no
recovery is possible. If the queue manager does support media recovery and the
damage is detected during the processing performed when the queue manager is
being started, the queue manager will automatically initiate media recovery of
the object. If the queue manager supports media recovery and the damage is
detected once the queue manager has started, it may be recovered from a media
image using the rcrmqobj command or it may be deleted.
----- amqaocua.c : 549 --------------------------------------------------------
9. Inorder to retrieve or create the object from the logs, we should first be recording the image through the "rcdmqimg" command and then use the "rcrmqobj" command to recreate the object as follows8. To display the reason code in understandable format, use "mqrc" command
C:\IBMWMQ\WebSphereMQ\bin>mqrc 2101 2101 0x00000835 MQRC_OBJECT_DAMAGED
You can see that the queue manager error log(AMQERR01.log) contains the following information.
-------------------------------------------------------------------------------
4/12/2010 10:54:55 - Process(2272.1) User(skamani) Program(amqzxma0.exe)
AMQ7472: Object QM.Q.RECD.REC, type queue damaged.
EXPLANATION:
Object QM.Q.RECD.REC, type queue has been marked as damaged. This indicates
that the queue manager was either unable to access the object in the file
system, or that some kind of inconsistency with the data in the object was
detected.
ACTION:
If a damaged object is detected, the action performed depends on whether the
queue manager supports media recovery and when the damage was detected. If the
queue manager does not support media recovery, you must delete the object as no
recovery is possible. If the queue manager does support media recovery and the
damage is detected during the processing performed when the queue manager is
being started, the queue manager will automatically initiate media recovery of
the object. If the queue manager supports media recovery and the damage is
detected once the queue manager has started, it may be recovered from a media
image using the rcrmqobj command or it may be deleted.
----- amqaocua.c : 549 --------------------------------------------------------
9a) rcdmqimg -> Record an object in the log
record image for Queue manager-> rcdmqimg -m QM.ROH -l -t qmgr *
record image for Queue under the queue manager QM.ROH
C:\IBMWMQ\WebSphereMQ\bin>rcdmqimg -m QM.ROH -z -l -t queue QM.Q.RECD.REC
When you execute this command, you can find the following entry in the respective Queue Manager error log at C:\IBMWMQ\WebSphereMQ\data\Qmgrs\QM!ROH\errors\AMQERR01.log
-------------------------------------------------------------------------------
4/12/2010 10:54:54 - Process(2272.1) User(skamani) Program(amqzxma0.exe)
AMQ7467: The oldest log file required to start queue manager QM.ROH is
S0000001.LOG.
EXPLANATION:
The log file S0000001.LOG contains the oldest log record required to restart
the queue manager. Log records older than this may be required for media
recovery.
ACTION:
You can move log files older than S0000001.LOG to an archive medium to release
space in the log directory. If you move any of the log files required to
recreate objects from their media images, you will have to restore them to
recreate the objects. An older log file is one with a numerically smaller log
number (but allowing for log number wrapping at 9999999).
-------------------------------------------------------------------------------
Media image for object QM.ROH, type qmgr recorded.
AMQ7467: The oldest log file required to start queue manager QM.ROH is S0000000.
LOG.
AMQ7468: The oldest log file required to perform media recovery of queue manager
QM.ROH is S0000000.LOG.
Record image for Queue -> rcdmqimg -m QM.ROH -l -t queue QM.ROH.Q.LOCALQ
Note: Object will be recorded to the log file and no file would be generated.
9b) rcrmqobj -> recreate an object or group of objects from their images
Recreate local queue QM.Q.RECD.REC under the qmgr QM.ROH
C:\IBMWMQ\WebSphereMQ\bin>rcrmqobj -m QM.ROH -z -t queue QM.Q.RECD.REC
Object QM.Q.RECD.REC, type queue recreated.
The Q file for the Local queue QM.Q.RECD.REC was recreated and could browse through the messages in the queue through MQ Explorer or through the amqsbcg command.
other examples:
Recreate local queues under the default queue manager
rcrmqobj -t ql *
Thursday, April 1, 2010
What is a profile in WAS terms?
- A profile is the set of files that define the WebSphere® Application Server runtime environment. At least one profile must exist to run the WebSphere Application Server.
- A feature pack extends the functionality of the WebSphere Application Server in a particular technology, for example the Feature Pack for Web services.
WAS Admin interview questions
ICE-BREAKER QUESTIONS
1. Brief me about your profile (Academics, Current Company – Designation – Role
and Websphere activities)
2. Which Versions of WAS you have worked on?? Expect some more questions on
enhancements from WAS V5 to V6 to V7
3. Which versions of WAS you have in your current organization? What are latest
Refresh Pack and Fix Packs available for V6.0/6.1/7.0?
4. How many (physical) WAS servers and how many application/environments you
are currently supporting?
5. WAS architecture/topology in current org??
6. List out internal components of WAS
7. Production Support?? L1/L2/L3?? Which ticketing tool is being used?
8. How do you escalate?
WAS Questions
9. How do you install WAS?
10. How do you upgrade WAS (Refresh Pack and Fix Pack installation)?
11. What’s a profile? Different types of profiles?
12. How do you know the version of WAS?
13. versionInfo.sh Vs historyInfo.sh
14. Whats a managed Node?
15. How do you federate a Node to DMGR?
16. What’s default SOAP Port of DMGR?
17. How to start/stop DMGR/Nodeagent/Instance?
18. What’s the ideal order to start/stop DMGR/Nodeagent/Instances? Are there any
dependencies among them?
19. How do you deploy Applications?
20. Important steps in Application Deployment
21. Define EAR/WAR
22. What’s ContextRoot and Deployment Descriptor?
23. What’s Plugin and how do you install?
24. What are the contents of plugin-cfg.xml?
25. What’s VirtualHost?
26. List out various logs available in WAS environment
27. How do you enable trace?
28. In how many ways you can administer/configure/operate WAS?
29. List out the objects available in wsadmin
30. What’s Sync and FullSync? How do you Sync a Node?
31. What’s Garbage Collection?
32. What’s classloader? Modes? Policies?
33. What’s session management? Session Persistence? Session Affinity?
34. JDBC Provider? Driver Types?
35. Connection Pool settings: Max, Min, Connection TimeOut, Aged time, unused
time, Reap time, Purge Policy
36. How do you configure Global Security?
37. List out user registries supported by WAS
38. Minimum details required to configure Global Security with LDAP
39. Vertical Clustering Vs Horizantal Clustering
40. How do you create Clusters
41. Core Dump/Thread Dump?? Heap Dump?
42. What will be your approach when an application hangs?
IHS Questions
43. How do you install IHS?
44. How to start/stop IHS instance?
45. How to check the syntax of httpd.conf?
46. How do you configure SSL for IHS?
47. Browser Error codes – 200, 300, 400?
48. What’s a DMZ?
UNIX/LINUX Questions
49. Command to list out all running JAVA processes
50. How do you terminate/kill a process listed above
51. How to copy plugin-cfg.xml from WAS machine to IHS machine
52. How to list all the ports in use and their status
53. How to find the process to which a port is bound to
54. How to mount/unmount?
55. Which tools do you use to connect to remote Unix/Linux/Windows servers
56. How to remove a directory and its subfolders?
57. How to change ownership and access permissions
58. How to find differences between two text files?
59. How to find Filesystem space?
60. How to find the usage details or folder sizes?
61. How do you search a file?
62. How do you rename a file?
63. How do you view last few lines of a text file (for ex. SystemOut.log)
64. How do you compress/uncompress?
65. VI editor: Quit? Save Quit? Quit without save? Search a keyword? Substitute a
word?
WebSphere Application Server Library
This is one good place for the documentation of all WAS versions so far…
http://www-01.ibm.com/software/webservers/appserv/was/library/
WebSphere Application Server V6.1: Technical Overview
http://www.redbooks.ibm.com/redpapers/pdfs/redp4191.pdf
IBM Education Assistant
http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp
WebSphere Application Server Administration Using Jython
http://www.ibmpressbooks.com/bookstore/product.asp?isbn=0137009526w
IBM HTTP Server User's Guide
ftp://ftp.software.ibm.com/software/webserver/appserv/library/v60/ihs_60.pdf
WebSphere Application Server V6.1: System Management and Configuration
http://www.redbooks.ibm.com/redbooks/pdfs/sg247304.pdf
IBM WebSphere Application Server V6.1 Security Handbook
www.redbooks.ibm.com/redbooks/pdfs/sg246316.pdf
WebSphere Application Server V6.1: Planning and. Design
www.redbooks.ibm.com/redbooks/pdfs/sg247305.pdf
WebSphere Application Server Network Deployment V6: High Availability Solutions
http://www.redbooks.ibm.com/redbooks/pdfs/sg246688.pdf
WebSphere Application Server V6 Problem Determination for Distributed Platforms
http://www.redbooks.ibm.com/redbooks/pdfs/sg246798.pdf
WebSphere Application Server V6.1: JMS Problem Determination
http://www.redbooks.ibm.com/redpapers/pdfs/redp4330.pdf
Monday, March 29, 2010
IBM WAS V7 supported platforms
WAS v7 supported platforms
AIX 5L 5.3 (ppc32, ppc64)
Linux(ia32, x64, SystemZ)
Windows Server 2003(ia32, x64)
Solaris 9 or 10 (Sparc, 32- or 64-bit)
HP-UX 11iv2 or 11iv3 (PA-RISC, IA-64)
z/OS 1.8 or later(31- or 64-bit)
i5/OS 5.4 or later (32- or 64-bit)
Installation of IBM WebSphere Application Server V7.0 on windows
Extract the contents from C1G2HML.zip and C1G2IML.zip
The launchpad console is the starting point for installing IBM WebSphere Application Server Network Deployment.
The launchpad is a Web application. Before using the launchpad, you must have a supported Web browser. The launchpad supports the following browsers:
Mozilla, Version 1.7 or later
Mozilla Firefox, Version 2.0 or later
Internet Explorer, Version 6.0 or later
SeaMonkey, Version 1.1.4 or later.
For Windows: Install a browser for the Windows® operating system. – Download Internet Explorer from the following location: http://www.microsoft.com/windows/ie/default.mspx – Download Mozilla Firefox from the following location: http://www.mozilla.org/products/firefox/.
1. Installation wizard page is displayed. Click next to continue
2. Software license agreement - accept the agreement and click next
3. System prerequisite check - the system should pass this check. Click next.
4. Optional features installation page -
5. Installation Directory
6. Websphere application server environments - choose (Cell, Management, Application Server, Custom, Secure proxy, none)
7. Enable Administrative security
List of supported software for WebSphere Application Server V7.0
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27012369
Sunday, March 28, 2010
How to determine whether a computer is running a 32-bit version or 64-bit of the Windows operating system?
How to determine whether a computer is running a 32-bit version or 64-bit of the Windows operating system?Generally, a computer's bit count indicates how much data it can process, the speed with which it can process the data, and the memory capacity. In order to optimize the computer's performance, the bit count of the operating system that is installed on the computer should match the bit count of the computer itself.
It meansthe CPU/hardware may be 32 bit/64 bit supportthe OS that is running on the hardware may be 32bit/64 bit supportthe applications that are running on the OS may be 32 bit/64bit supportSo before downloading/choosing the software, by the above equation, we need to choose 32 bit or 64 bit application.
Generally, a computer's bit count indicates how much data it can process, the speed with which it can process the data, and the memory capacity. In order to optimize the computer's performance, the bit count of the operating system that is installed on the computer should match the bit count of the computer itself.
It means
the CPU/hardware may be 32 bit/64 bit support
the OS that is running on the hardware may be 32bit/64 bit support
the applications that are running on the OS may be 32 bit/64bit support
So before downloading/choosing the software, by the above equation, we need to choose 32 bit or 64 bit application.
Tuesday, January 19, 2010
IBM WebSphere Portal Server get started
Download IBM WebSphere Portal Server software:
http://www-947.ibm.com/support/entry/portal/Downloads/Software/WebSphere/WebSphere_Portal
Download document for WebSphere Portal Server (Required & Optional parts)
http://www-01.ibm.com/support/docview.wss?uid=swg24024463
| Prerequisites | |
| |
 | |
| Installation Instructions | |
|
WPS -> uses the Virtual memory module
Subscribe to:
Posts (Atom)
