The following information describes how to validate the successful
completion of each installation step. The Monitor installation process is complex
and time consuming, so a step by step verification is highly recommended.
Finding a problem at the end of the entire process may necessitate a complete
reinstallation of some portions of the software stack.
If you are not able to verify the successful completion of an installation
step, contact "IBM Technical Support" and they will assist you further.
Note: <temp> refers to the "%temp%\" directory on Windows® and
to the "/tmp" directory on AIX®.
DB2® Enterprise
Server Edition
After DB2 Enterprise Server Edition installation,
do the following:
- Validate that DB2 icon appears in system tray (Windows)
and that you can start up DB2 Control Center.
- If databases will be local, make sure that you can create a database on
the local machine.
- If databases will be remote, make sure that you can catalog and access
databases created on the remote machine.
- On the AIX platform,
make sure that the db2inst1 instance was created under /home/db2inst1/sqllib
and that you can start db2cc (Control Center) manually.
DB2 Cube
Views™
After DB2 Cube Views™ installation, do the following:
- Validate that "OLAP Center" menu item has been added to the DB2 Control Center
"Tools" menu and/or that the "OLAP Center" menu item has been added to the
"Business Intelligence Tools" menu on the Start Menu, and that the OLAP Center
application initializes.
- On AIX:
Run a display package command to make sure that the Cubeviews packages were
laid down correctly. The command "lslpp -L all | grep db2" should return
db2_08_01.cbsg, db2_08_01.cube.services, and db2_08_01.olsampdb among other DB2 packages.
To make sure that the db2inst1 instance was updated, check /tmp/db2setup.log
to ensure everything is a success. The following information will be displayed:
db2inst1 instance was updated successfully.
WebSphere® Application
Server
After
WebSphere Application
Server installation using the "dashboard"
profile, do the following:
- Run the "Install Verification" feature from the "First Steps" console,
and check for success message.
- Validate that you can successfully start/stop the "server1" application
server by checking the startServer.log and stopServer.log in C:\IBM\WebSphere\AppServer\profiles\dashboard\logs\server1.
- Verify that the "Administrative Console" application can be successfully
accessed at: http://localhost:9060/ibm/console
- Check SystemOut.log in C:\IBM\WebSphere\AppServer\profiles\dashboard\logs\server1
for errors.
- If unable to validate the install, see the Application Server installation
log "<temp>log.txt", and the Monitor installation log "<temp>launchpad-monitor.log".
Other Application Server files used in debugging an installation
are located on:
- C:\IBM\WebSphere\AppServer\logs, especially C:\IBM\WebSphere\AppServer\logs\log.txt
and C:\IBM\WebSphere\AppServer\logs\wbi\log.txt
- C:\IBM\WebSphere\AppServer\logs\dashboard\*
- C:\IBM\WebSphere\AppServer\profiles\dashboard\logs\*
- C:\IBM\WebSphere\AppServer\profiles\dashboard\
- C:\IBM\WebSphere\AppServer\profiles\dashboard\properties\*
- C:\IBM\WebSphere\AppServer\properties\profileRegistry.xml
WebSphere Process
Server
After
WebSphere Process
Server installation using the "monitor"
profile, do the following:
- Run the "Install Verification" feature from the "First Steps" console
and check for success message.
- Validate that you can successfully start/stop the "server1" application
server by checking the startServer.log and stopServer.log in C:\IBM\WebSphere\ProcServer\profiles\monitor\logs\server1
- Verify that the "Administrative Console" application can be successfully
accessed at "http://localhost:9060/ibm/console".
- Check SystemOut.log in C:\IBM\WebSphere\ProcServer\profiles\monitor\logs\server1
for errors.
- Check that the following databases exist on DB2: WPRCSDB and EVENT. If the EVENT database
was not created, you can create it by running %ProfileHome%\event\dbscripts\db2\cr_event_db2.{sh|bat}
server {db2inst1 | db2admin}
- If unable to validate the installation, see the Process Server installation
log "<temp>log.txt", and the Monitor installation log "<temp>launchpad-monitor.log".
Other Process Server files used in debugging an installation are
located on:
- C:\IBM\WebSphere\ProcServer\logs, especially C:\WebSphere\ProcServer\logs\log.txt
and C:\WebSphere\ProcServer\logs\wbi\log.txt
- C:\IBM\WebSphere\ProcServer\logs\monitor\*
- C:\IBM\WebSphere\ProcServer\profiles\monitor\logs\*
- C:\IBM\WebSphere\ProcServer\profiles\monitor\
- C:\IBM\WebSphere\ProcServer\profiles\monitor\properties\*
- C:\IBM\WebSphere\ProcServer\properties\profileRegistry.xml
WebSphere Portal
After
installing
WebSphere Portal, do the
following:
- Validate that you can successfully start/stop the "WebSphere_Portal" application
server. You may want to use the "First Steps" to launch the server.
- Verify that the IBM® WebSphere Portal web application can be successfully
accessed.
- If using "First Steps", after the server starts, it will automatically
launch the web app.
- Or you can use "Start the Server" and after the server starts, bring up
the web app in a browser at "http://localhost:9081/wps/portal".
- You should see the "Login Portlet" page. Login using the default ID/Password,
"wpsadmin/wpsadmin".
- After logging in, you should be able to see a web page with the message
"Welcome to WebSphere Portal
version 5.1.0.2".
- If you are unable to validate the installation, see the WebSpherePortal
installation log files "wpsinstalllog.txt", "pznInstallLog.txt", "pzninstall.log",
and wpinstalllog.txt", and check the Monitor installation log file "launchpad-monitor.log"
in the <temp> directory. Also check SystemOut.log on C:\WebSphere\PortalServer\log
for errors.
DB2 Alphablox
After
installing
DB2 Alphablox, do
the following:
- Validate that you can successfully access the Alphablox Administrative
Pages at "http://localhost:9081/AlphabloxAdmin/home". Login using the default
ID/Password, "admin/password".
- Check the Alphablox installation log files "alphablox_install_log.html"
or IBM_DB2_Alphablox_8.3_InstallLog.log in the C:\IBM\DB2Alphablox directory.
- To obtain the required Alphablox
maintenance, complete the Alphablox installation via Monitor Launchpad, then
go to the following URL and follow the instructions. http://www-1.ibm.com/support/docview.wss?rs=2026&context=SSCPX3&dc=D600&uid=swg21227687&loc=en_US&cs=UTF-8&lang=en
Database Creation
- Before using the Launchpad to create any databases, follow these steps:
- If you used Launchpad to install DB2, make sure to stop Launchpad and then
restart it in a new command window. This ensures that the DB2 environment
is set up correctly.
- Make sure that DB2 is started.
- Make sure that the directories used for Backups and Table spaces exist.
On AIX,
these directories need to have permissions set to "777" or the owner should
be set to "db2inst1".
- Upon completion of database creation (i.e. after clicking Finish),
verify that the tables were created in the databases. Verify that the following
databases contain these tables:
Database |
Tables |
Repository |
Database_Characteristics, Property, Monitor_Client (last
table created) |
State |
DEPLOYED_DDL, RMPRUNECTRL (last table created) |
Runtime |
TIME_BASED_SITUATIONS, RMPRUNECTRL (last table created)
|
Historical |
DIM_TIME, RMPRUNECTRL (last table created) |
Potential problems and corrective actions:
- Database is not created.
Action: Make sure DB2 is started.
- Database was created, but there are no tables in the database.
Action:
Make sure you typed a valid user ID and password on the Database Creation
panel. Look in the <Monitor_Home> /install/logs/db2Create****Out.log file
where "****" is either State, Runtime, Historical, or Repository. Look for
the following message:
"SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID")"
If this message exists, uninstall the database and then reinstall
it with a valid user ID and password.
- Verify that the correct data was written to the DATABASE_CHARACTERISTICS
table in the Repository database. There should be one row for each of the
three databases (State, Runtime, and Historical). The row should contain
the database name, the schema name, and the host name. Also, when the Historical
database is created, a row should be added to the Property table in the Repository
database. The row should contain a property called "CubeDataSource" with a
value of "<Hist_Name>_CUBE" where "<Hist_Name>" is the name of the Historical
database. If there are no entries, look in <temp>launchpad-monitor.log.
Search for "repos command0" and see if there are any errors. If the information
was written correctly, the following statement should exist in the log file:
"repos command finished, rc=0"
Potential problems and corrective actions:
- On AIX,
cannot access the bundled JVM. In <temp>launchpad-monitor.log, you will
see "repos command finished rc=126".
Action: The parent directory containing
launchpad.sh must have a read and execute permission for all users.
- Cannot access DB2 libraries.
Action: Make sure DB2 is started.
If you used launchpad to install DB2, make sure you stopped launchpad and
then restarted it in a new command window.
- Cannot connect to Repository database.
Action: If the Repository database
is on the local machine, make sure that you typed a valid user ID and password
on the Database Creation panel. If the Repository database is on a remote
machine, make sure the database is cataloged on your local machine. Also,
make sure that you typed a valid user ID and password on the Repository Database
Information panel.
- AIX ONLY:
Verify that the Runtime database was populated correctly. Open DB2 Control Center
and connect to the Runtime database. Verify that there are two user-defined
functions in the database named GMTLONG2TIMESTAMP and GMTTIMESTAMP2LONG.
If these functions do not exist, the Replication Manager will fail. Check <Monitor_Home>/install/logs/db2CreateRuntimeOut.log
file to determine if the functions were created successfully. Search for "call
sqlj.install_jar". If the functions were created, you should see the following
message:
"DB20000I The CALL command completed successfully".
If the functions were not created, you may see this message:
"SQL4302N Procedure or user-defined function "sqlejReadJar", specific name "SQL051206175332050"
aborted with an exception "Permission denied /home/db2inst1/sqlli". SQLSTATE=38501".
If
this happens, use the Monitor uninstaller to uninstall the Runtime database.
Drop the database, reboot you machine, and then reinstall the Runtime database.
- To debug Monitor database creation problems, check the <Monitor_Home>/install/logs/db2CreateAAAAOut.log
file where "AAAA" represents State, Runtime, Historical, or Repository.
Monitor Server
Start Process Server using the "monitor"
profile, then start the "Administrative Console" application at "http://localhost:9060/ibm/console".
Verify the following in:
- Enterprise Applications: Make sure IBM_WB_ACTIONMANAGER and IBM_WB_MONITOR_SERVER
are started successfully.
- JDBC Resources: Test the Database Connections under Server &
Node scope to the data sources under the MonitorDB2XADriver1JDBC Resource.
- WebSphere Business Monitor: Make
sure all Monitor Specific plugins/panels are installed correctly. This can
be verified by simply clicking every hyperlink under the WebSphere Business Monitor heading.
If any of the enterprise applications is missing, check the MonitorAppInstallOut.log
file and MonitorAppInstallErr.log file under <Monitor_Home>/install/logs.
In MonitorAppInstallOut.log file, search for "ADMA5016I: Installation of
IBM_WB_MONITOR_SERVER started." and "ADMA5016I: Installation of IBM_WB_ACTIONMANAGER
started.". If the applications were installed successfully, you should see
the following two statements: "ADMA5013I: Application IBM_WB_MONITOR_SERVER
installed successfully" and "ADMA5013I: Application IBM_WB_ACTIONMANAGER installed
successfully".
If any of the JDBC resources is missing, check the MonitorAppInstallOut.log
and MonitorAppInstallErr.log files under <Monitor_Home>/install/logs.
In the MonitorAppInstallOut.log file, search for "## Installing DataSource:
???? on node Node01" where "????" can be "RepositoryDBDataSource" or "RuntimeDBDataSource".
Also search for "## Installing DataSource: MonitorDataSource on server1".
Make sure there are no errors.
If any of the WAS admin console plug-ins
are missing, check the MonitorConsoleInstallOut.log and MonitorConsoleInstallErr.log
files under <Monitor_Home>/install/logs. In MonitorAppInstallOut.log,
search for "PLPR0013I: Saving Console Enterprise Application". If the plug-ins
were installed successfully, you should see "PLPR0014I: Closing Console Enterprise
Application".
If you uninstall and then reinstall Monitor Server, you
must delete the SIB database directory after you uninstall Monitor Server.
If you do not delete the directory, you will have errors upon starting the
server after the reinstallation. The following directory must be deleted:
C:\WebSphere\ProcServer\profiles\monitor\databases\com.ibm.ws.sib\<Node_Name>.server1-MONITOR.<Cell_Name>.Bus.
Problems
can also be diagnosed from the SystemOut.log and SystemErr.log files in C:\WebSphere\ProcServer\profiles\monitor\logs\server1.
Dashboard Client
Start WebSphere_Portal server and
access the "
WebSphere Business Monitor Welcome"
page at "http://localhost:9081/wps/portal".
- Verify the correct theme is being used. The WebSphere Business Monitor theme
is purple and has WebSphere Business Monitor icons
and images instead of the normal WebSphere Portal icons
and images. Also, there should be a different welcome page pertaining toWebSphere Business Monitor, instead of the normal WebSphere Portal welcome page.
- At the top right of the page, click Log in. Login using the default
ID/Password, "wpsadmin/wpsadmin".
- Under Administration > Portal Management > Portlets, search by Unique
Name and use the string 'com.ibm' and make sure all of dashboard views are
installed.
- Start dashboard profile "server1" and verify the following in the WebSphere Application
Server Administrative Console:
- Resources -> JDBC Providers: Test the Database Connections under Node
scope to the data sources under the MonitorDB2XADriver1 JDBC Resource
- Problems can be diagnosed from the SystemOut.log and SystemErr.log files
in C:\WebSphere\AppServer\profiles\portal\logs\server1.
If any of the JDBC resources are missing, check the DashboardClientDeployOut.log
and DashboardClientDeployErr.log files under <Monitor_Home>/install/logs.
In DashboardClientDeployOut.log file, search for "## Installing DataSource:
???? on node Node01" where "????" can be "RepositoryDBDataSource", "RuntimeDBDataSource"
or "HistoricalDBDataSource". Make sure there are no errors.
Verify
that the correct data was written to the Monitor_Client table in the Repository
database. There should be one row containing the host name of the Dashboard
Client machine and the SOAP port number of the Dashboard Client machine.
If there is no entry in the table, check the DashboardClientDeployOut.log
file. Search for "Register Dashboard Client..." and see if there are any
errors.
The Dashboard Client install script performs several steps.
Here are the messages that indicate the beginning of a step. Check the DashboardClientDeployOut.log
file and verify that each step finishes with no errors.
Step
|
Message |
Create WebSphere Application
Server resources,
like datasources |
Create WAS resources.. |
Deploy the WAR file |
Deploying war... |
Deploy the WebSphere Business Monitor theme
|
Deploying themes... |
Save the WebSphere Portal Welcome
page |
Exporting Welcome Page ... |
Set the WebSphere Business Monitor Welcome
page |
Setting Welcome Page ... |
Create the name space binding |
Creating namespace bindings and mapping EJB Refs ... |
Create the DB2 Alphablox datasource
|
Create Alphablox data source... |
Update the Monitor_Client table |
Register Dashboard Client... |