IBM Support

Installing IBM Business Monitor V8.0.1 Fix Pack 3

Product Documentation


Abstract

This document details and provides the installation and usage instructions for IBM Business Monitor V8.0.1 Fix Pack 3.

Content


Installing IBM Business Monitor V8.0.1 Fix Pack 3
Updating IBM Business Monitor applications
Updating plug-ins on your CEI server in a network deployment environment
Updating support applications in a cross-cell environment
Updating the Cognos widget catalog in WebSphere Portal
Applying library code fixes to monitor model applications
Installing a new or updating an existing showcase model
Updating the context root in an existing network deployment environment
Uninstalling IBM Business Monitor V8.0.1 Fix Pack 3
Restoring IBM Business Monitor applications
Restoring plug-ins on your CEI server in a network deployment environment
Restoring support applications in a cross-cell environment
Restoring monitor model applications


Installing IBM Business Monitor V8.0.1 Fix Pack 3
Note the following:
  • IBM Business Monitor V8.0.1 Fix Pack 3 updates any IBM Business Monitor V8.0.0 or V8.0.1 installation to the 8.0.1.3 level, in the following environments:
    • IBM Business Monitor server installation
    • WebSphere test environment (WTE) installation (for IBM Integration Designer or Rational Application Developer) that includes IBM Business Monitor
  • If the WTE is installed, in addition to updating the WTE, you must also update the development toolkit separately:

Throughout this document, <Monitor_root> will be used to designate the installation location of IBM Business Monitor. For the location of <Monitor_root>, see <Monitor_root> in Directory conventions.


Back to top

Problems addressed in the fix pack
The fixes included in IBM Business Monitor V8.0.1 Fix Pack 3 are detailed in the Fix/Update list for IBM Business Monitor V8.0.

Back to top

Prerequisites

  • In the WTE installed under Rational Application Developer, you must ensure that the following repository is included in the list of repositories in IBM Installation Manager:
http://public.dhe.ibm.com/software/websphere/repositories/

Important: If you have IBM Business Monitor V8.0.1.0 installed on a server with IBM Business Process Manager V8.0.1.0, you must install IBM Business Process Manager V8.0.1 Fix Pack 3 at the same time you install this fix pack for IBM Business Monitor.

WebSphere Application Server V8.0.0 Fix Pack 9 is required and can be applied prior to or concurrently with IBM Business Monitor V8.0.1 Fix Pack 3.

Additional prerequisites before installing the fix pack:


Backing up your IBM Business Monitor profile

Notes:
  • For the WTE, profile backup is not required, and should not be performed. Additionally, when you roll back IBM Business Monitor in the WTE from V8.0.1.3 to V8.0.1.0, V8.0.1.1, or V8.0.1.2, all Monitor data in the WTE server profiles will be lost.
  • It is important that you make a backup of your Monitor and Cognos databases at the same point in time at which you are making a backup of your profile.

Important: Before you install this fix pack, use these steps for each IBM Business Monitor profile that you want to back up.
  1. Stop the server and the running processes for the profile that you want to back up.
  2. Create a directory to store the backup of the profile. For example, C:\backup\profiles.
  3. Go to <Monitor_root>\profiles\<profileName>\bin.
  4. Run the following command or see the note below for an alternate command:
    manageprofiles.bat
    -backupProfile
    -profileName <    profileName>
    -backupFile <    backupDirectory>\<profileName>.backup.zip

    Where:

    <    profileName> represents the name of your profile

    <backupDirectory> is the directory you created to store the backup of the profile. You must provide a fully qualified file path for the backup file. If the path contains any spaces, you must use quotation marks ( " ) before and after the fully qualified path name. For example, "C:\Program Files\profiles\myprofilename.backup.zip."

    Note: Another way to backup your profile configuration is using the backupConfig command. From the <profile_root>/bin directory, run the command backupConfig.bat -help. This command displays the following usage:

    backupConfig [backup_file] [-nostop] [-quiet] [-logfile <filename>]
    [-replacelog] [-trace] [-username <username>] [-password <password>]
    [-profileName <profile>] [-help]

The console should display the following message: INSTCONFSUCCESS: Success: The profile backup operation was successful. You can proceed with installing IBM Business Monitor V8.0.1 Fix Pack 3.

For more information about these parameters, refer to the topic manageprofiles command in the product documentation.


Back to top

Installing the fix pack in a network deployment environment

In a network deployment environment, if you have any IBM Business Monitor profiles that were created prior to installing IBM Business Monitor V8.0.1 Fix Pack 3, proceed to the section Upgrading your IBM Business Monitor profiles in a network deployment environment for the correct procedure to install IBM Business Monitor V8.0.1 Fix Pack 3. If you do not have any IBM Business Monitor profiles that were created prior to installing IBM Business Monitor V8.0.1 Fix Pack 3, continue with the procedure in the section Installing the fix pack to install IBM Business Monitor V8.0.1 Fix Pack 3 on each WebSphere Application Server installation where IBM Business Monitor V8.0 exists.


Back to top

Installing the fix pack
Note: In a network deployment environment, if you have any IBM Business Monitor profiles that were created prior to installing IBM Business Monitor V8.0.1 Fix Pack 3, proceed to the section Upgrading your IBM Business Monitor profiles in a network deployment environment for the correct procedure to install IBM Business Monitor V8.0.1 Fix Pack 3 (that procedure will refer to this section).

Note: On Windows 7, use these instructions to install IBM Business Monitor development toolkit and WebSphere test environment V8.0 and update them to V8.0.1.3,
  1. If the machine where you are installing IBM Business Monitor V8.0.1 Fix Pack 3 has Internet access, skip to step 7.
    Important Note: Even if you have Internet access you may be unable to connect to the live repositories that contain the required fixes. See the technote Unable to connect to the IBM Business Process Manager or Monitor V8.0.1 service repository during Custom Install for important information on how to work around this issue. You may also use steps 2 through 6 below and download the repositories locally.
  2. Installation of IBM Business Monitor V8.0.1 Fix Pack 3 requires IBM Installation Manager V1.6.0 or later. Refer to this document for instructions for updating IBM Installation Manager to V1.6.0 on a machine without Internet access.
  3. Download IBM Business Monitor V8.0.1 Fix Pack 3 to a temporary disk location.
  4. If IBM Business Process Manager V8.0.1.0 is installed in the same server, download IBM Business Process Manager V8.0.1 Fix Pack 3.
  5. Download WebSphere Application Server V8.0 Fix Pack 9.
  6. Unpack the repositories to any directories you choose. Take note of where you have unpacked the repositories. You should unpack each repository to its own directory.
  7. Start IBM Installation Manager.

    Note: At this point, the following message might be displayed, indicating that your Installation Manager needs to be updated: "A new version of IBM Installation Manager is available. You must update Installation Manager before you can continue. To update Installation Manager, click Yes..." Click Yes. When the Installation Manager update completes, click OK to restart the Installation Manager, and then click Update. (This will update Installation Manager to V1.6.0 or higher, as required for installation of IBM Business Monitor V8.0.1 Fix Pack 3.)
  8. Click File > Preferences.
  9. If the machine has Internet access, ensure that the Search service repositories during installation and updates option is selected, and skip to step 11.
  10. On the Repositories panel, click the Add Repository button. Type or browse to the location of the repository.config file for the IBM Business Monitor V8.0.1 Fix Pack 3 repository that you unpacked in step 6. Repeat this for each of the other repositories you downloaded in steps 3 through 5 and unpacked in step 6. Click OK to save the new repository settings.
  11. Click Update, and click Next.
  12. From the Update Packages panel, select the package group that has IBM Business Monitor V8.0 installed, and click Next. If only one package group is available, it is selected by default; therefore, just click Next.
  13. Under the installed IBM Business Monitor Version 8.0.0.0, Version 8.0.1.0, Version 8.0.1.1, or Version 8.0.1.2, select Version 8.0.1.3. If WebSphere Application Server Version 8.0.0.0 is displayed, select Version 8.0.0.9 (or higher version, if that is displayed) underneath. If IBM Business Process Manager Version 8.0.0.0, Version 8.0.1.0, Version 8.0.1.1, or Version 8.0.1.2 is displayed, select Version 8.0.1.3 underneath. Click Next.
  14. Accept the License Agreement and click Next.
  15. Ensure that you have already backed up all IBM Business Monitor profiles. If yes, click Next.
  16. Verify the information on the panel and click Update to start applying the fix pack.
  17. When the update is completed, click View Log File on the last panel to verify that there are no errors.

    Note: If you are updating the WTE, one or more of the following error messages may appear in the log file. These can be safely ignored.

    Stand-alone development WebSphere Monitor on WebSphere Enterprise Service Bus profile (<profile_name>) feature is not available for installation because either IBM WebSphere Process Server or IBM WebSphere Enterprise Service Bus is not installed.
    Stand-alone development WebSphere Monitor on WebSphere Process Server profile (<profile_name>) feature is not available for installation because IBM WebSphere Process Server is not installed.
    Installation Manager cannot remove the Stand-alone development WebSphere Monitor profile (<profile_name>) feature from this installation package.
    Installation Manager cannot remove the Server runtime feature from this installation package.
    Installation Manager cannot remove the Stand-alone development WebSphere Monitor profile (<profile_name>) feature from this installation package.
    The installation package 'IBM Business Monitor' requires components supplied by other packages.
    Installation Manager cannot remove the Server runtime feature from this installation package.
    Installation Manager cannot remove the Stand-alone development WebSphere Monitor profile (<profile_name>) feature from this installation package.
  18. If any profiles have been created, run the appropriate command to update the administrative console:

    Linux or UNIX: <Monitor_root>/bin/iscdeploy.sh -restore
    Windows: <Monitor_root>\bin\iscdeploy.bat -restore

Back to top

Upgrading your IBM Business Monitor profiles in a network deployment environment
Use the procedure in this section to upgrade your IBM Business Monitor profiles that were created prior to installing IBM Business Monitor V8.0.1 Fix Pack 3, in a network deployment environment. If you have a stand-alone profile or you do not have any WebSphere product profiles that were created prior to installing IBM Business Monitor V8.0.1 Fix Pack 3, proceed to the section Restarting the environment after installation of IBM Business Monitor V8.0.1 Fix Pack 3.

Security-enabled network deployment environments


When you apply the fix pack in a network deployment environment where WebSphere administrative security is enabled, the connection to the deployment manager requires a user ID and password to be supplied. The IBM Installation Manager does not prompt for these credentials when you start updating an installation containing managed profiles. However, depending on your configuration, you may have to enter the credentials in a separate prompt near the end of the upgrade process.

Note: The credential panel appears twice during the upgrade process, and has a default timeout period of one minute. If you miss this prompt, or your security configuration is set up such that no prompt is displayed, or if you are running the silent installation script, follow the instructions in the section Identifying profile update errors.

For more information on how to configure security for WebSphere administration scripts (which the IBM Business Monitor scripts depend on), see Configuring security with scripting in the WebSphere Application Server product documentation.


Upgrading the deployment manager
  1. Install IBM Business Monitor V8.0.1 Fix Pack 3 onto the deployment manager’s installation using IBM Installation Manager, as described in the section Installing the fix pack. The deployment manager profile is automatically updated during fix pack installation.
  2. Check for any errors, as explained in the section Identifying profile update errors, before continuing.


Upgrading the nodes
  1. Start the deployment manager. The deployment manager must be running when you apply the fix pack to an installation with a managed profile.

    Note: The only exception to this rule is for managed profiles hosted by the same installation as their deployment manager profile. The managed node configuration is updated as part of the deployment manager profile in this scenario and a separate log file is not written.

    Skip step 2 in this section for managed nodes that are hosted by the same installation as their deployment manager.
  2. For each managed node with an independent installation, perform the following steps:

    a. Ensure that all the servers and their node agents are stopped.

    b. Install IBM Business Monitor V8.0.1 Fix Pack 3 onto the managed node’s installation using IBM Installation Manager, as described in the section Installing the fix pack.

    Note: When applying the fix pack in a network deployment environment where WebSphere administrative security is enabled, the connection to the deployment manager requires a user ID and password. Depending on your configuration, you might have to enter the credentials in a separate prompt near the end of the update process. Refer to the section Security enabled network deployment environments for details.

    The managed node (profile) is updated automatically during fix pack installation.
    Log files are saved as:

    <profile_root>/logs/BPMProfileUpgrade.<profileName>.<clusterName>.<timestamp>.log

    where <profile_root> is the root directory of the managed profile.

    c. Check for any errors, as explained in the section Identifying profile errors, before continuing.
  3. If any of the nodes contain cluster members, follow the steps described in the section Upgrading clusters before starting the servers.
  4. For each node, restart the node agent and wait for the node synchronization to complete.

    5. Back to top


Upgrading clusters
After upgrading the deployment manager and the managed nodes containing cluster members, follow these steps to upgrade the clusters before starting the cluster members (servers).
  1. Make sure the deployment manager is stopped.
  2. On the deployment manager, change to <Monitor_root>.
  3. Depending on the platform, run one of the following commands for each cluster:

    Windows: <Monitor_root>\bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Dcluster=<clusterName>

    UNIX and Linux: <Monitor_root>/bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Dcluster=<clusterName>

    where <profileName> is the name of the deployment manager profile and <clusterName> is the name of the cluster.
  4. Check the following log file for errors:

    <profile_root>/logs/BPMProfileUpgrade.<profileName>.<clusterName>.<timestamp>.log

    where <profile_root> is the root directory of the deployment manager profile. There might be more than one file whose name matches this pattern. Open the log files and search for "-cluster" to find the cluster associated with this particular log file. If there is an error, fix the cause, then rerun step 3.
  5. When all clusters have been successfully upgraded, start the deployment manager.
  6. For each node, start the node agent and wait for the node synchronization to complete.

Back to top

Identifying profile update errors
If an error message "The packages are updated with warnings" is displayed on the Installation Manager summary panel, check the log file <Monitor_root>/logs/wbm/install.FP8013/installconfig_server_profileMaintenance.log.
If it contains the message:

Result of executing [...]BPMProfileMaintenance.ant was: false

then a profile update error has occurred. If multiple profiles in the installation are being updated, search for the first occurrence of
"profileName=" prior to the error to know which profile this error is associated with. Fix the cause, then follow the appropriate steps in the section Recovering after profile update errors.

Note: For network deployment environments, the most likely cause of an error is that a connection to the deployment manager cannot be established.

Back to top

Recovering after profile update errors
Note: For network deployment environments that are not using clusters, refer to this technote for instructions on identifying and recovering from a particular Business Space profile upgrade error that can occur. For all other profile upgrade errors (in any type of environment), follow the instructions in this section that are appropriate for the profile for which update failed.

Stand-alone profiles and deployment manager profiles
  1. Make sure the stand-alone application server or the deployment manager is stopped.
  2. Change to the <Monitor_root> directory where the profile update error has occurred and run one of the following commands as appropriate for your platform.

    Windows: <Monitor_root>\bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    UNIX and Linux: <Monitor_root>/bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    where <profileName> is the name of the stand-alone profile or deployment manager profile that had update errors.


Federated profiles
  1. Make sure the deployment manager has been started. This is necessary because the BPMProfileUpgrade.ant script must connect to the central configuration repository on the deployment manager to make the updates.
  2. Change to the <Monitor_root> directory where the profile update error has occurred and run one of the following commands as appropriate for your platform.

    Windows: <Monitor_root>\bin\ws_ant.bat -f util\BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Duser=<user> -Dpassword=<password>

    UNIX and Linux: <Monitor_root>/bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Duser=<user> -Dpassword=<password>

    where <profileName> is the name of the federated profile that had update errors.

    The -Duser and -Dpassword parameters are required because WebSphere administrative security is enabled. The -Duser parameter should be set to a user with administrative authority; the -Dpassword parameter is the password for this user.

Back to top

Restarting the environment after installation of IBM Business Monitor V8.0.1 Fix Pack 3
  • In a network deployment environment, start the following components if they are not already started (use the links for instructions):

Verifying the fix pack installation
  • Log in to the administrative console.
  • Verify that the Welcome Page contains 8.0.1.3 as the version of IBM Business Monitor.


Back to top

Updating IBM Business Monitor applications
You must update the following IBM Business Monitor applications in your clusters or servers after applying IBM Business Monitor V8.0.1 Fix Pack 3:


REST Services (RESTServicesGateway)
<Monitor_root>/installableApps/RESTServiceGateway.ear


In a network deployment environment, you must also update the following IBM Business Monitor applications in your clusters or servers after applying IBM Business Monitor V8.0.1 Fix Pack 3 (you do not need to update these applications in a stand-alone environment):


Data Services (IBM_WBM_DATA_SERVICES)
<Monitor_root>/installableApps.wbm/MonitorDataServices.ear

Action Services (IBM_WBM_ACTIONSERVICES)
<Monitor_root>/installableApps.wbm/monactionmgr.ear

REST Services Emitter (IBM_WBM_EMITTER_SERVICES)
<Monitor_root>/installableApps.wbm/EmitterServices.ear

Mobile Dashboard (IBM_WBM_MOBILE_DASHBOARD)
<Monitor_root>/installableApps.wbm/MobileDashboard.ear


Details on the procedure to update IBM Business Monitor applications are documented at the following location:

Updating applications with the console

Note: For the procedure documented at the above location, note the following:
  • In step 3b, select Replace the entire application.
  • In step 4b, where you use the update wizard to specify or edit application binding information, ensure that the Fast Path option is selected on the first page. Click Next on each page of the wizard (do not modify any information) until you reach the last page, then continue with step 5 of the documented procedure (where you will click Finish on the last page of the wizard).

Updating IBM Business Monitor widgets

You must also update the IBM Business Monitor widgets for Business Space, by running the wsadmin command.
  1. For your profile, open a command window. For a clustered environment, go to the <deployment_manager_profile_root>/bin directory. For a stand-alone server environment, go to the <profile_root>/bin directory.
  2. At the command prompt, type the wsadmin command to start the wsadmin environment.
  3. Run the updateBusinessSpaceWidgets command:

    For a stand-alone environment, use the following command:

    $AdminTask updateBusinessSpaceWidgets {-serverName <server> -nodeName <node> -noEndpoints true -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets}

    For a network deployment environment, use the following command:

    $AdminTask updateBusinessSpaceWidgets {-clusterName <BSpace_cluster_name> -noEndpoints true -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets}

    where <BSpace_cluster_name> is the name of the cluster where Business Space is deployed.

In a network deployment environment, start the following components (use the links for instructions):

Back to top

Updating plug-ins on your CEI server in a network deployment environment
If your CEI server is on WebSphere Application Server V8.0 and is in the same network deployment cell as IBM Business Monitor, and IBM Business Monitor is not installed on that server, you must copy certain plug-ins to the CEI server after installing IBM Business Monitor V8.0.1 Fix Pack 3. Refer to the following technote for instructions:

Monitor model is not receiving events and instances are not viewable on the dashboard

Note that if CEI is on IBM Business Process Manager V8.0.1, the plug-ins have already been updated.

If CEI is in a different network deployment cell than IBM Business Monitor, you must update the cross-cell files on the remote CEI system, using the procedure in the section Updating support applications in a cross-cell environment.

Back to top

Updating support applications in a cross-cell environment
In a cross-cell environment, where CEI is on WebSphere Application Server V8.0, after applying IBM Business Monitor V8.0.1 Fix Pack 3 you must update the cross-cell files on the remote CEI system, using the procedure below. Note that if CEI is on IBM Business Process Manager V8.0.1.3, the cross-cell files have already been updated. Also note that if IBM Business Monitor is installed on the remote CEI server, there is no additional action required in this section.

Note: The term “remote CEI server” in this section refers to the remote stand-alone server (comprising its own remote cell) or the deployment manager of the remote cell containing the CEI target.
  1. Stop the remote CEI cell. (For a stand-alone CEI server, stop the server. For CEI in a network deployment environment, stop the cell in this sequence: servers, clusters, node agents, deployment manager.)

  2. Copy the updated cross-cell files to the remote CEI server.

    a. Delete all files named <WAS_root>/plugins/com.ibm.wbimonitor.monresources_8.0*.jar ('*' is a wildcard character representing any pattern of characters between "8.0" and ".jar") from the remote CEI server.

    b. From the <WAS_root>/scripts.wbm/crosscell folder of the local IBM Business Monitor server installation, locate the appropriate file depending on your operating system:

    Linux or UNIX: monitorCommunicationWithWAS80BasedCells.tar
    Windows: monitorCommunicationWithWAS80BasedCells.zip

    Copy the appropriate file to the <WAS_root>/plugins folder of the remote CEI server, and extract the contents.

    c. On the remote CEI server, for each server profile, go to the <profile_root>/bin folder, and run the appropriate command to configure the application server to recognize the .jar file:

    Linux or UNIX: osgiCfgInit.sh
    Windows: osgiCfgInit.bat

  3. Restart the remote CEI cell. (For a CEI stand-alone server, restart the server. For CEI in a network deployment environment, restart the cell in this sequence: deployment manager, node agents, clusters, servers.)


Back to top

Updating the Cognos widget catalog in WebSphere Portal
If you have previously installed IBM Business Monitor widgets in WebSphere Portal, use the procedure below to update the Cognos widget catalog. (Note: In a clustered WebSphere Portal environment, the procedure only needs to be executed on one of the nodes.)
  1. Copy the file update_reportviewer_portlet.xml (attached below) to a temporary directory on the WebSphere Portal server (for example, C:\temp for Windows, or /tmp for Linux or UNIX platforms).

    update_reportviewer_portlet.xml
  2. On the WebSphere Portal server, open a command prompt, and go to the directory <WP_root>/bin.
  3. Run the following command

    Windows: xmlaccess.bat -url http://<WP_hostname>:<WP_port>/wps/config
    -user <    WP_admin> -password <WP_pw>
    -in c:\temp\update_reportviewer_portlet.xml
    -out c:\temp\update_reportviewer_portlet_out.xml

    Linux or UNIX: xmlaccess.sh -url http://<WP_hostname>:<WP_port>/wps/config
    -user <    WP_admin> -password <WP_pw>
    -in /tmp/update_reportviewer_portlet.xml
    -out /tmp/update_reportviewer_portlet_out.xml

    <    WP_hostname> = WebSphere Portal server hostname
    <WP_port> = WebSphere Portal server HTTP port
    <    WP_admin> = WebSphere Portal server administrative user ID
    <WP_pw> = WebSphere Portal administrative password


Back to top

Applying library code fixes to monitor model applications
After updating your IBM Business Monitor installation with a fix pack, you still need to update the individual monitor model applications because they are not updated automatically. To help you update these applications, a script and sample response file are included in the fix pack in the <Monitor_root>/scripts.wbm/MM_App_Updater directory.

Before you begin, back up your monitor model applications using the export function from the Enterprise Applications page in the administrative console. To display the administrative console page, click Applications > Application Types > WebSphere enterprise applications.

To apply fixes to the library code for your monitor model applications, use the following steps to update the response file (MM_App_Updater_Config_80.properties) and then run the updateMMApplicationLibraries_80 script on your deployment manager or stand-alone server. After you update the properties file, the script updates the library code for all monitor model applications that are compatible with the update that you are applying and it matches the restrictions declared in the response file.



To update the configuration properties file, make a backup copy of the MM_App_Updater_config_80.properties file located in the <Monitor_root>/scripts.wbm/MM_App_Updater directory, and complete the following steps on the deployment manager or stand-alone server:
  1. In a text editor, open the MM_App_Updater_config_80.properties file located in the <Monitor_root>/scripts.wbm/MM_App_Updater directory.
    The response file documents all the options with comments in the file.
  2. Check the response file options and update them if necessary because they vary for individual installations:
  • hostname - set to localhost because you should always run this script from the deployment manager or stand-alone server.
  • port - enter the port to use to transport information. For SOAP, use the SOAP_CONNECTOR_ADDRESS port for the stand-alone server or deployment manager. For RMI, use the BOOTSTRAP_ADDRESS port for the stand-alone server or deployment manager. The default is the default SOAP port, 8880. (The default RMI port is 2809.)
  • username - remove the pound sign (#) before the username property, and then enter the user name to use for authentication. Note that any trailing spaces will be interpreted as being part of the user name, so ensure that the right number of trailing spaces is included. If you do not have security enabled, leave this field blank.
  • password - remove the pound sign (#) before the password property, and then enter the password to use for authentication. Note that any trailing spaces will be interpreted as being part of the password, so ensure that the right number of trailing spaces is included. If you do not have security enabled, leave this field blank.
3. To check your response file before running it, set the validateResponseFileOnly property. This test is always done as part of the script's execution, but setting this flag forces the script to check the response file without performing any updates.

4. To test the compatibility of your applications with the update, set the testMMAppCompatibilityOnly property. This test is always done as part of the script's execution to ensure that no incompatible monitor model application is updated. However, setting this flag forces the script to check the compatibility of the monitor model applications without performing any updates.

5. To turn on tracing, which is usually not necessary, edit the logging.properties file and uncomment this line: com.ibm.wbimonitor.server.updater.level = FINEST.

6. Stop all the monitor models currently installed.

7. Back up each installed monitor model application by exporting it to an EAR file.  Use this link for instructions:

http://www-01.ibm.com/support/knowledgecenter/SS7JFU_8.0.0/com.ibm.websphere.express.doc/info/exp/ae/trun_app_distr.html?lang=en

8. Run the appropriate command to install the updated library code:
  • updateMMApplicationLibraries_80.bat (Windows)
  • updateMMApplicationLibraries_80.sh (UNIX)

Note: If you are installing on a network deployment environment, wait until the nodes have finished synchronizing before starting the monitor model applications. You can view the synchronization status from the administrative console by clicking System Administration > Nodes.

9. Start the monitor model applications.

Back to top

Installing a new or updating an existing showcase model
Note: The showcase model is only supported on a stand-alone IBM Business Monitor profile.

Installing a new showcase model

Refer to this link in the IBM Business Monitor product documentation for instructions to install a new showcase model:

http://www-01.ibm.com/support/knowledgecenter/SSTLXK_8.0.1/com.ibm.wbpm.mon.imuc.doc/inst/inst_showcase.html?lang=en
Updating an existing showcase model

Updating an existing showcase model

Use these steps to update an existing showcase model:
  1. After installing V8.0.1 Fix Pack 3, log on to Business Space.
  2. Delete the existing "Better Lender Space."
  3. On a command line, change directories to the directory, <Monitor_root>/installableApps.wbm/showcase/scripts.
  4. Execute the following command, showcase.bat/sh -w <monitor_profile_root>.
    This command uninstalls the prior version of the showcase model, and then installs the new showcase model and all of its new artifacts.
    Note: If the pathname represented by <monitor_profile_root> contains any spaces, you must use the "8.3" notation to specify the pathname in the command. For example, if the pathname is C:\IBM\WebSphere 80\profiles\MonSrv01, you must use C:\IBM\WEBS80~1\profiles\MonSrv01 as the pathname in the command.


Updating the context root in an existing network deployment environment
If you updated the context root in your previous network deployment environment before performing the profile upgrade, you must update the context root again. Refer to Updating context roots in an existing network deployment environment.

Back to top



Uninstalling IBM Business Monitor V8.0.1 Fix Pack 3
Backing up your Business Space pages added by the 8.0.1.3 upgrade
To prevent losing your Business Space pages, before you roll back IBM Business Monitor from V8.0.1.3, export your newly created Business Spaces and pages to a file. Refer to Exporting business spaces for instructions.

Uninstalling the fix pack

Before uninstalling IBM Business Monitor V8.0.1 Fix Pack 3, do the following:

  1. Start the IBM Installation Manager and click Roll Back.
  2. Select the package group that has IBM Business Monitor V8.0.1.3 installed and click Next. If only one package group is available, it is selected by default; therefore, just click Next.
  3. Under the installed IBM Business Monitor V8.0.1.3, select the version to which you want to roll back, and click Next.
  4. Verify the information on the panel and click Roll Back to start uninstalling the fix pack.
  5. When the roll back is completed, click View Log File on the last panel to verify that there are no errors.

Restoring a profile backup after successful uninstallation of IBM Business Monitor 8.0.1 Fix Pack 3

For a WTE installed on Rational Application Developer:

Although you cannot restore a backed up profile to the WTE, you can use the following procedure to rebuild the profile:
  1. Launch Rational Application Developer and stop the server and the running processes for the profile that you want to rebuild.
  2. Go to <RAD_WTE_root>\runtimes\bi_v8\bin.
  3. Run the following command:

    manageprofiles.bat -delete -profileName <profileName>
  4. Delete the profile directory <RAD_WTE_root>\runtimes\bi_v8\profiles\qmwas from the file system.
  5. Launch IBM Installation Manager and click Modify.
  6. Select the IBM WebSphere Application Server -ND package group and click Next.
  7. Expand the feature IBM Business Monitor 8.0.1.2 and then IBM Business Monitor Server.
  8. Click the checkbox Stand-alone development WebSphere Monitor profile (qmwas). and click Next.
  9. Follow the instructions in Installation Manager to complete this process, and click Modify.

For a WTE installed on IBM Integration Designer:

Although you cannot restore a backed up profile to the WTE, you can use the following procedure to reset the profile:
  1. Launch IBM Integration Designer.
  2. Stop your server if it is started.
  3. Right-click your server in the Servers tab and select Manage server profiles.
  4. Follow the instructions to select the checkbox to Reset your server(s) and click OK.

For an IBM Business Monitor server:

Note: When you restore your profile, you should also restore the Monitor and Cognos databases to match the point in time at which you made a backup of your profile.
  1. Stop the server and the running processes for the profile that you want to restore.
  2. Go to <Monitor_root>\profiles and rename the <profileName> directory to <profileName>.8013.
  3. Go to <Monitor_root>\bin.
  4. Run the following command:

    manageprofiles.bat -validateAndUpdateRegistry

    The output on the console should display [ <profileName> ], for example [WBMon01].
  5. Run the following command:

    manageprofiles.bat -restoreProfile
    -backupFile <    backupDirectory>\<profileName>.backup.zip

    Where:

    <    backupDirectory> is the directory where the backup of the profile is located. You must provide a fully qualified file path for the backup file.If the path contains any spaces, use quotation marks ( " ) before and after the fully qualified path name. For example, "C:\Program Files\profiles\myprofilename.backup.zip."

    <profileName> is the name of your profile that is being restored.

    The output on the console should display the message: INSTCONFSUCCESS: Success: The profile was successfully restored. If the restoration fails, refer to If your profile restoration fails below.

    For more information about these parameters, refer to the topic manageprofiles command in the product documentation.

Note: If you want to view your IBM Business Monitor dashboards after your profile is successfully restored, start the server and access the Business Space dashboard page. If you cannot see your dashboards when accessing the Business Space dashboard page, clear the browser cache using the appropriate method below.
  • Firefox

    • 1. Go to Tools > Options.
    2. Click Privacy.
    3. Click clear your recent history.
    4. Restart your browser.
  • Internet Explorer:

    • 1. Go to Tools > Internet Options > General Tab.
    2. Under Browsing history, click Delete.
    3. Make sure that Temporary Internet files is selected and click Delete.
    4. Restart your browser.

If your profile restoration fails
If you receive an error message that your profile restoration failed because the directory path exceeds the maximum number of characters, create a new profile with a directory path with fewer characters. To create your new profile, complete the following steps:
  1. Go to the directory where WebSphere Application Server is installed. For example, C:\IBM\WebSphere\MonServer.
  2. Change directories to the \bin\ProfileManagement directory.
  3. Start the Profile Management Tool to create a new profile. Specify a profile name and store it in a directory path that is short to avoid exceeding the maximum number of characters.

After restoring your profile
  1. Verify that the server is stopped.
  2. Copy com.ibm.bspace.plugin_<version ID>.jar  
    from <Monitor_root>\BusinessSpace\wbm\plugins
    to <Monitor_root>\plugins.
  3. From a command line, run the <Monitor_root>\bin\osgicfginit.bat file.
  4. Restore the Business Space and pages that you backed up before rolling back IBM Business Monitor from V8.0.1.3 by importing them from your backup location. Refer to the topic Importing business spaces in the product documentation for instructions.

Verifying the fix pack uninstallation
  • In a network deployment environment, start the following components (use the links for instructions):
  • Verify that the Welcome Page contains the version to which you rolled back for IBM Business Monitor.
Restoring IBM Business Monitor applications in a network deployment environment
You must update the following IBM Business Monitor applications in your clusters or servers after uninstalling IBM Business Monitor V8.0.1 Fix Pack 3:


REST Services (RESTServicesGateway)
<Monitor_root>/installableApps/RESTServiceGateway.ear


In a network deployment environment, you must also update the following IBM Business Monitor applications in your clusters or servers after applying IBM Business Monitor V8.0.1 Fix Pack 3 to restore them to the previous levels (you do not need to update these applications in a stand-alone environment):


Data Services (IBM_WBM_DATA_SERVICES)
<Monitor_root>/installableApps.wbm/MonitorDataServices.ear

Action Services (IBM_WBM_ACTIONSERVICES)
<Monitor_root>/installableApps.wbm/monactionmgr.ear

REST Services Emitter (IBM_WBM_EMITTERSERVICES)
<Monitor_root>/installableApps.wbm/EmitterServices.ear

Mobile Dashboard (IBM_WBM_MOBILE_DASHBOARD)
<Monitor_root>/installableApps.wbm/MobileDashboard.ear


Details on the procedure to update IBM Business Monitor applications are documented at the following location:

Updating applications with the console

Note: For the procedure documented at the above location, note the following:
  • In step 3b, select Replace the entire application.
  • In step 4b, where you use the update wizard to specify or edit application binding information, ensure that the Fast Path option is selected on the first page. Click Next on each page of the wizard (do not modify any information) until you reach the last page, then continue with step 5 of the documented procedure (where you will click Finish on the last page of the wizard).

Updating IBM Business Monitor widgets

You must also update the IBM Business Monitor widgets for Business Space, by running the wsadmin command.
  1. For your profile, open a command window. For a clustered environment, go to the <deployment_manager_profile_root>/bin directory. For a stand-alone server environment, go to the <profile_root>/bin directory.
  2. At the command prompt, type the wsadmin command to start the wsadmin environment.
  3. Run the updateBusinessSpaceWidgets command:

    For a stand-alone environment, use the following command:

    $AdminTask updateBusinessSpaceWidgets {-serverName <server> -nodeName <node> -noEndpoints true -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets}

    For a clustered environment, use the following command:

    $AdminTask updateBusinessSpaceWidgets {-clusterName <BSpace_cluster_name> -noEndpoints true -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets}

    where <BSpace_cluster_name> is the name of the cluster where Business Space is deployed.

In a network deployment environment, start the following components (use the links for instructions):
Restoring plug-ins on your CEI server in a network deployment environment
If your CEI server is on WebSphere Application Server V8.0 and is in the same network deployment cell as IBM Business Monitor, and IBM Business Monitor is not installed on that server, you must copy certain plug-ins to the CEI server after uninstalling IBM Business Monitor V8.0.1 Fix Pack 3. Refer to the following technote for instructions:

Monitor model is not receiving events and instances are not viewable on the dashboard

If CEI is in a different network deployment cell than IBM Business Monitor, you must update the cross-cell files on the remote CEI system, using the procedure in the section Restoring support applications in a cross-cell environment.

Restoring support applications in a cross-cell environment
In a cross-cell environment, where CEI is on WebSphere Application Server V8.0, after uninstalling IBM Business Monitor V8.0.1 Fix Pack 3 you must update the cross-cell files on the remote CEI system, using the procedure below.

Note: The term “remote CEI server” in this section refers to the remote stand-alone server (comprising its own remote cell) or the deployment manager of the remote cell containing the CEI target.
  1. Stop the remote CEI cell. (For a stand-alone CEI server, stop the server. For CEI in a network deployment environment, stop the cell in this sequence: servers, clusters, node agents, deployment manager.)

  2. Follow the appropriate steps to copy the updated cross-cell files to the remote CEI server:

    Choose the appropriate action depending on whether or not IBM Business Monitor V8.0 is already installed on the remote CEI server.

    If IBM Business Monitor V8.0.1 is installed locally, but not on the remote CEI server:

    a. Delete all files named <WAS_root>/plugins/com.ibm.wbimonitor.monresources_8.0*.jar ('*' is a wildcard character representing any pattern of characters between "8.0" and ".jar") from the remote CEI server.

    b. From the <WAS_root>/scripts.wbm/crosscell folder of the local IBM Business Monitor server installation, locate the appropriate file depending on your operating system:

    Linux or UNIX: monitorCommunicationWithWAS80BasedCells.tar
    Windows: monitorCommunicationWithWAS80BasedCells.zip.

    Copy the appropriate file to the <WAS_root>/plugins folder of the remote CEI server, and extract the contents.

    c. On the remote CEI server, for each server profile, go to the <profile_root>/bin folder, and run the appropriate command to configure the application server to recognize the .jar file:

    Linux or UNIX: osgiCfgInit.sh
    Windows: osgiCfgInit.bat

    If IBM Business Monitor V8.0.1 is installed both locally and on the remote CEI server:

    a. From the <WAS_root>/scripts.wbm/crosscell folder of the local IBM Business Monitor server installation, copy the com.ibm.wbimonitor.observationmgr.crosscell_8.0.1.0.jar file to the <WAS_root>/plugins folder of the remote CEI server.

    b. On the remote CEI server, for each server profile, go to the <profile_root>/bin folder, and run the appropriate command to configure the application server to recognize the .jar file:

    Linux or UNIX: osgiCfgInit.sh
    Windows: osgiCfgInit.bat

  3. Restart the remote CEI cell. (For a CEI stand-alone server, restart the server. For CEI in a network deployment environment, restart the cell in this sequence: deployment manager, node agents, clusters, servers.)

Restoring monitor model applications
You need to restore the monitor model applications that were exported during the "Applying library code fixes to monitor model applications" steps.

1. Stop all the monitor models currently installed.

2. Update each monitor model application from the corresponding monitor model application EAR file you exported in step 7 of the procedure in the section “Steps for updating”.  Details on the procedure to update IBM Business Monitor applications are documented at the following location:

Updating applications with the console

Note: For the procedure documented at the above location, note the following:


  • In step 3b, select Replace the entire application.
  • In step 4b, where you use the update wizard to specify or edit application binding information, ensure that the Fast Path option is selected on the first page. Click Next on each page of the wizard (do not modify any information) until you reach the last page, then continue with step 5 of the documented procedure (where you will click Finish on the last page of the wizard).

Note: If you are installing on a network deployment environment, wait until the nodes have finished synchronizing before starting the monitor model applications. You can view the synchronization status from the administrative console by clicking System Administration > Nodes.

3. Start the monitor model applications.

[{"Product":{"code":"SS7NQD","label":"IBM Business Monitor"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Documentation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.0.1.3;8.0.1.2;8.0.1.1;8.0.1;8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg27042247

Page Feedback