JR51587 IBM Business Monitor 8.0.1.2 interim fix dependency information and installation instructions:


1. Interim fix dependencies
===========================

Prerequisite APARs:
JR49279 (8.0.1.2-WS-BSPACE-IFJR49279)
JR50336
JR51565 (8.0.1.2-WS-BSPACE-IFJR51565)

Indirect Prerequisite APAR:
JR48069

Superseded APARs:
JR49245
JR49868
JR49087
JR49300
JR50187
JR50562
JR50791
JR51087
JR51314


2. Interim fix installation order (Installation Manager)
========================================================

JR49279
JR48069
JR50336
JR51565
JR51587
                               
                                                            
3. Interim Fix installation instructions                                   
========================================

a. Stop the stand-alone server or network deployment environment.

b. Install JR51587 using steps that are documented in http://www-01.ibm.com/support/docview.wss?uid=swg21417656.  Note that the interim fix must be installed for every Business Monitor installation that supports a network deployment environment.

c. Start the stand-alone server or network deployment environment.


4. Post Installation Manager install instructions
=================================================

The following steps update IBM Business Monitor widgets.  

a. Make sure that the stand-alone server or network deployment environment has been started.

b. Open a command window for your profile. For a stand-alone server environment, go to the <profile_root>/bin directory.  For a network deployment environment, go to the <deployment_manager_profile_root>/bin directory. 

c. At the command prompt, type the wsadmin command to start the wsadmin environment.

d. Run the updateBusinessSpaceWidgets command relative to the Widgets_WBMonitor.zip file.

Note that if the <Monitor_root> path contains a space, then the Widgets_WBMonitor.zip file may need to be copied from the <Monitor_root>/BusinessSpace/registryData/WBM/widgets directory to a path without spaces before running the updateBusinessSpaceWidgets command.

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

$AdminTask updateBusinessSpaceWidgets {-serverName <server> -nodeName <node> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_WBMonitor.zip}

For a network deployment environment, use the following command:

$AdminTask updateBusinessSpaceWidgets {-clusterName <BSpace_cluster_name> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_WBMonitor.zip}

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

Note that space files are not included in the Widgets_WBMonitor.zip file, so a CWM001134E messsage when running the command does not indicate that there is a problem.

e. Run the updateBusinessSpaceWidgets command relative to the Widgets_Cognos.zip file.

Note that if the <Monitor_root> path contains a space, then the Widgets_Cognos.zip file may need to be copied from the <Monitor_root>/BusinessSpace/registryData/WBM/widgets directory to a path without spaces before running the updateBusinessSpaceWidgets command.

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

$AdminTask updateBusinessSpaceWidgets {-serverName <server> -nodeName <node> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_Cognos.zip}

For a network deployment environment, use the following command:

$AdminTask updateBusinessSpaceWidgets {-clusterName <BSpace_cluster_name> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_Cognos.zip}

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

Note that space and template files are not included in the Widgets_Cognos.zip file, so a CWM001134E messsage when running the command does not indicate that there is a problem.

f. Run the following command to save changes.

$AdminConfig save

If you wish to enable Instances widget column sizing changes from JR49245, then follow steps g-i.  Otherwise, skip to step j. 

g. In the WebSphere administrative console, navigate to Resources-> Resource Environment-> Resource Environment Providers and choose "Mashups_ConfigService".

h. Select the "Custom properties" link, choose "New", and add the "com.ibm.monitor.instancesview.fullcolumnheaders" property (without double quotes around the property name), setting the value to true.

i. Back on the "Custom properties" list, select "com.ibm.mashups.properties.client" (the first entry in the list) and append ",com.ibm.monitor.instancesview.fullcolumnheaders" at the end of the value string.

j. After widgets have been updated, Business Space users should clear their browser cache and login to Business Space again so that updates are reflected.

          
5. Uninstall instructions
=========================

a. Stop the stand-alone server or network deployment environment.

b. Using IBM Installation Manager, uninstall JR51587.

c. Start the stand-alone server or network deployment environment.

d. Open a command window for your profile. For a stand-alone server environment, go to the <profile_root>/bin directory.  For a network deployment environment, go to the <deployment_manager_profile_root>/bin directory. 

e. At the command prompt, type the wsadmin command to start the wsadmin environment.

f. Run the updateBusinessSpaceWidgets command relative to the Widgets_WBMonitor.zip file.

Note that if the <Monitor_root> path contains a space, then the Widgets_WBMonitor.zip file may need to be copied from the <Monitor_root>/BusinessSpace/registryData/WBM/widgets directory to a path without spaces before running the updateBusinessSpaceWidgets command.

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

$AdminTask updateBusinessSpaceWidgets {-serverName <server> -nodeName <node> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_WBMonitor.zip}

For a network deployment environment, use the following command:

$AdminTask updateBusinessSpaceWidgets {-clusterName <BSpace_cluster_name> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_WBMonitor.zip}

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

g. Run the updateBusinessSpaceWidgets command relative to the Widgets_Cognos.zip file.

Note that if the <Monitor_root> path contains a space, then the Widgets_Cognos.zip file may need to be copied from the <Monitor_root>/BusinessSpace/registryData/WBM/widgets directory to a path without spaces before running the updateBusinessSpaceWidgets command.

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

$AdminTask updateBusinessSpaceWidgets {-serverName <server> -nodeName <node> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_Cognos.zip}

For a network deployment environment, use the following command:

$AdminTask updateBusinessSpaceWidgets {-clusterName <BSpace_cluster_name> -widgets <Monitor_root>/BusinessSpace/registryData/WBM/widgets/Widgets_Cognos.zip}

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

h. Run the following command to save changes.

$AdminConfig save

If you followed steps 4g-i to enable changes for JR49245, then follow steps i-k below.  Otherwise, skip to step l.

i. In the WebSphere administrative console, navigate to Resources-> Resource Environment-> Resource Environment Providers and choose "Mashups_ConfigService".

j. Select the "Custom properties" link and remove the "com.ibm.monitor.instancesview.fullcolumnheaders" property.

k. Back on the "Custom properties" list, select "com.ibm.mashups.properties.client" (the first entry in the list) and remove ",com.ibm.monitor.instancesview.fullcolumnheaders" from the end of the value string.

l. After widgets have been updated, Business Space users should clear their browser cache and login to Business Space again so that updates are reflected.