When you change the password of a user ID used by WebSphere® Business Monitor components
on the system without also changing the same password in the components' locations,
the components will not respond. You must complete the password change to
ensure communication with the WebSphere Business Monitor components.
On the machine on which the Dashboard Client is installed, complete
the following steps:
- Open the DB2 Control Center.
- From the menu, select .
- In the databases table, right-click each WebSphere Business Monitor database whether it was created
locally on the machine or cataloged from a different machine.
- From the pop-up menu, select Change Password.
- Change the password you have changed for any DB2 user ID (db2admin on
the Windows platform or db2inst1 on the AIX platform).
- Start the WebSphere Application
Server administrative
console, and do the following:
- From the navigation tree, select .
- Select MonitorDB2XADriver.
- Click Data Sources.
- Select MonitorDataSource.
- Click J2EE Connector Architecture (J2C) authentication data
entries.
- Select each alias that has the DB2 user ID whose password you have changed
(db2admin on the Windows platform or db2inst1 on the AIX platform).
- On the General Properties page of each alias, in
the Password field, change the password to the new
password.
- Click OK, and save your changes.
- Log off the administrative console.
- Login to DB2® Alphablox administrative
console page.
- Change all datasources to reflect new password.
- Stop the WebSphere_Portal application server on the WebSphere Application
Server by
running the following command:
On the Windows® platform: stopServer WebSphere_Portal
On
the AIX® platform: stopServer.sh
WebSphere_Portal
Note: If the WebSphere Application
Server global
security feature is enabled, provide the user ID and password of a valid user
who can start and stop the WebSphere Application
Server with
the above commands. For example, stopServer WebSphere_Portal user <User_ID>
password <Password>
- Stop the server1 application server on the WebSphere Application
Server by
running the following command:
On the Windows platform: stopServer server1
On
the AIX platform: stopServer.sh server1
- Stop any running replication manager scripts.
- Change the password.aut file to reflect the new password.
- Start any stopped replication manager scripts.
- Stop DB2 by
running the db2stop force command
- Start DB2 by
running the db2start command
- Restart the server1 application server by running the following
command:
On the Windows platform: startServer server1
On
the AIX platform: startServer.sh
server1
- Start the WebSphere_Portal application server on the WebSphere Application
Server by
running the following command:
On the Windows platform: startServer WebSphere_Portal
On
the AIX platform: startServer.sh
WebSphere_Portal
On the machine on which the Monitor Server is installed, complete
the following steps:
- Open the DB2 Control
Center.
- From the menu, select .
- In the databases table, right-click each WebSphere Business Monitor database
whether it was created locally on the machine or cataloged from a different
machine.
- From the pop-up menu, select Change Password.
- Change the password you have changed for any DB2 user ID (db2admin on the Windows platform
or db2inst1 on the AIX platform).
- Start the WebSphere Application
Server administrative
console, and do the following:
- From the navigation tree, select .
- Select MonitorDB2XADriver.
- Click Data Sources.
- Select MonitorDataSource.
- Click J2EE Connector Architecture (J2C) authentication data
entries.
- Select each alias that has the DB2 user ID whose password you have changed
(db2admin on the Windows platform or db2inst1 on the AIX platform).
- On the General Properties page of each alias, in the Password field,
change the password to the new password.
- Click OK, and save your changes.
- Log off the administrative console.
- Stop the server1 application server on the WebSphere Application
Server by
running the following command:
On the Windows platform: stopServer server1
On
the AIX platform: stopServer.sh
server1
- Stop any running replication manager scripts.
- Stop DB2 by running the db2stop force command.
- Start DB2 by
running the db2start command.
- Change the password.aut file to reflect the new password
- Start any stopped replication manager scripts.
- Restart the server1 application server by running the following command:
On
the Windows platform: startServer
server1
On the AIX platform: startServer.sh server1