Installing Business Space powered by WebSphere: V7.0.0.4 Interim Fix 3

Product documentation


Abstract

This document contains instructions on how to install V7.0.0.4 Interim Fix 3 for Business Space powered by WebSphere (Business Space V7.0.0.4 Interim Fix 3).

Content

 

Installing Business Space V7.0.0.4 Interim Fix 3
Uninstalling Business Space V7.0.0.4 Interim Fix 3



Installing Business Space V7.0.0.4 Interim Fix 3


Before you install Business Space V7.0.0.4 Interim Fix 3, do the following:


Important: Before you install this Interim Fix, you must back up your WebSphere product profile. Use the instructions below titled "Backing up your WebSphere product profile."

Backing up your WebSphere product profile
Note: Before you install this Interim Fix, use these steps for each WebSphere product 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 <WAS_root>\bin.
  4. Run the following 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."

The console should display the following message: INSTCONFSUCCESS: Success: The profile backup operation was successful. You can proceed with installing Business Space V7.0.0.4 Interim Fix 3.


For more information about these parameters, access the link: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/rxml_manageprofiles.html


Installing the Interim Fix in a network deployment environment

In a network deployment environment, if you have any WebSphere product profiles that were created prior to installing Business Space V7.0.0.4 Interim Fix 3, please proceed to the section Upgrading your WebSphere product profiles in a network deployment environment for the correct procedure to install Business Space V7.0.0.4 Interim Fix 3. If you do not have any WebSphere product profiles that were created prior to installing Business Space V7.0.0.4 Interim Fix 3, please continue with the procedure in the section Installing the Interim Fix to install Business Space V7.0.0.4 Interim Fix 3 on each WebSphere Application Server installation where Business Space V7.0 exists.

Installing the Interim Fix




If the machine where you are installing Business Space V7.0.0.4 Interim Fix 3 has Internet access, skip to step 3.
  1. Download Business Space V7.0.0.4 Interim Fix 3 to a temporary disk location.
  2. Unpack the repository to any directories you choose. Take note of where you have unpacked the repository.
  3. Start IBM Installation Manager.
  4. Click File > Preferences.
  5. If the machine has Internet access, ensure that the Search service repositories during installation and updates option is selected, and skip to step 7.
  6. On the Repositories panel click the Add Repository button. Type or browse to the location of the repository.config file for the Business Space V7.0.0.4 Interim Fix 3 repository that you unpacked in step 2. Click OK to save the new repository settings.
  7. Click Update, and click Next.
  8. From the Update Packages panel, select the package group that has IBM Business Space 7.0.0.4 installed, and click Next. If only one package group is available, it is selected by default; therefore, just click Next.
  9. Under the installed IBM Business Space Version 7.0.0.4, select 7.0.0.4-WS-BSPACE-IFJR43860 7.0.4.20110518_1923, and click Next.
  10. Ensure that you have already backed up all profiles. If yes, click Next.
  11. Verify the information on the panel and click Update to start applying the Interim Fix.
  12. When the update is completed, click View Log File on the last panel to verify that there are no errors.


Upgrading your WebSphere product profiles in a stand-alone environment



Use the procedure in this section to upgrade your WebSphere product profiles that were created prior to installing Business Space V7.0.0.4 Interim Fix 3, in a stand-alone environment. If you do not have any WebSphere product profiles that were created prior to installing Business Space V7.0.0.4 Interim Fix 3, proceed to the section Restarting the environment after installation of Business Space V7.0.0.4 Interim Fix 3.

You will use one of the following scripts depending on your platform:

Windows: <WAS_root>\BusinessSpace\scripts\upgradeBSpaceProfile.bat
UNIX and Linux: <WAS_root>/BusinessSpace/scripts/upgradeBSpaceProfile.sh

Run the script as shown:

upgradeBSpaceProfile -profileName <profile_name> -nodeName <node_name> -serverName <server_name>


Upgrading your WebSphere product profiles in a network deployment environment


Use the procedure in this section to upgrade your WebSphere product profiles that were created prior to installing Business Space V7.0.0.4 Interim Fix 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 Business Space V7.0.0.4 Interim Fix 3, proceed to the section Restarting the environment after installation of Business Space V7.0.0.4 Interim Fix 3.


Security-enabled network deployment environments

When you apply the Interim Fix 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 Identifying Profile Update Errors section.

For more information on how to configure security for WebSphere administration scripts (which the Business Space scripts depend on), see Configuring security with scripting in the WebSphere Application Server Information Center.


Upgrading the deployment manager

  1. Install Business Space V7.0.0.4 Interim Fix 3 onto the deployment manager’s installation using IBM Installation Manager as described in the section Installing the Interim Fix.
  2. On the deployment manager change to <WAS_root>.
  3. Depending on the platform, run one of the following commands:

    Windows: bin\ws_ant.bat -f BusinessSpace\upgrade\BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    UNIX and Linux: bin/ws_ant.sh -f BusinessSpace/upgrade/BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    where <profileName> is the name of the deployment manager profile.
  4. Check for any errors, as explained in the Identifying Profile Update Errors section, before continuing.


Upgrading the nodes
  1. Start the deployment manager. The deployment manager must be running when you apply the Interim Fix to an installation with a managed profile.
  2. For each managed node hosted by the same physical installation as the deployment manager, perform the following steps:

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

    b. On the deployment manager change to <WAS_root>.

    c. Depending on the platform, run one of the following commands:

    Windows: bin\ws_ant.bat -f BusinessSpace\upgrade\BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    UNIX and Linux: bin/ws_ant.sh -f BusinessSpace/upgrade/BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    where <profileName> is the name of the managed profile.

    d. Check for any errors, as explained in the Identifying Profile Update Errors section, before continuing.
  3. For each managed node with an independent installation, perform the following steps:

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

    b. Install Business Space V7.0.0.4 Interim Fix 3 onto the managed node's installation using IBM Installation Manager as described in the section Installing the Interim Fix.

    Note: When applying the Interim Fix 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 may have to enter the credentials in a separate prompt near the end of the update process. Please refer to Security enabled network deployment environments for details.

    c. On the managed node's physical installation change to <WAS_root>.

    d. Depending on the platform, run one of the following commands:

    Windows: bin\ws_ant.bat -f BusinessSpace\upgrade\BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    UNIX and Linux: bin/ws_ant.sh -f BusinessSpace/upgrade/BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    where <profileName> is the name of the managed profile.

    e. Check for any errors, as explained in the Identifying Profile Update Errors section, before continuing.
  4. If any of the nodes contain cluster members follow the steps described under Upgrading Clusters before starting the servers.
  5. For each node, restart the node agent and wait for the node synchronization to complete.
  6. If you have disabled automatic synchronization, ensure all your nodes are correctly synchronized before starting the cluster members.
  7. Start all the servers and cluster members as needed.


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. On the deployment manager change to <WAS_root>.
  2. Depending on the platform, run one of the following commands for each cluster:

    Windows: bin\ws_ant.bat -f BusinessSpace\upgrade\BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true -Dcluster=<clusterName>

    UNIX and Linux: bin/ws_ant.sh -f BusinessSpace/upgrade/BSpaceProfileUpgrade.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.
  3. Check the following log file for errors:

    <profile_root>/logs/BSpaceProfileUpgrade.<profileName>.<timestamp>.log

    where <profile_root> is the root directory of the managed profile. There may 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 2.
  4. When all clusters have been successfully upgraded, stop and restart the deployment manager.
  5. For each node, restart the node agent and wait for the node synchronization to complete.
  6. If you have disabled automatic synchronization, ensure all your nodes are correctly synchronized before starting the cluster members.
  7. Start all the servers and cluster members as needed.


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 <WAS_root>/logs/bspace/install.FP7004/installconfig_bspace_profileMaintenance.log.
If it contains the message:

Result of executing [...]BSpaceProfileMaintenance.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 Recovering after profile update errors section.

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


Recovering after profile update errors



Note: For network deployment environments that are not using clusters, please 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 <WAS_root> directory where the profile update error has occurred and run one of the following commands as appropriate for your platform.

    Windows: bin\ws_ant.bat -f BusinessSpace\upgrade\BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    UNIX and Linux: bin/ws_ant.sh -f BusinessSpace/upgrade/BSpaceProfileUpgrade.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 BSpaceProfileUpgrade.ant script must connect to the central configuration repository on the deployment manager to make the updates.
  2. Change to the <WAS_root> directory where the profile update error has occurred and run one of the following commands as appropriate for your platform.

    Windows: bin\ws_ant.bat -f BusinessSpace\upgrade\BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

    UNIX and Linux: bin/ws_ant.sh -f BusinessSpace/upgrade/BSpaceProfileUpgrade.ant -profileName <profileName> -Dupgrade=true

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

    If you are updating a federated node when WebSphere administrative security is enabled, you must also supply the -Duser=<userID> -Dpassword=<password> parameters, where <userID> is a user ID from the user registry that has administration authority and <password> is the password for that user ID.


Restarting the environment after installation of Business Space V7.0.0.4 Interim Fix 3



If you have not already restarted your environment, do so now, as follows.

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



Uninstalling Business Space V7.0.0.4 Interim Fix 3


Before you uninstall Business Space V7.0.0.4 Interim Fix 3, do the following:

  • Deployment manager - http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/rxml_stopmanager.html

    Uninstalling the Interim Fix

    1. Start the IBM Installation Manager and click Uninstall.

    2. Select the package group that has your WebSphere product installed and click Next.
    3. Select 7.0.0.4-WS-BSPACE-IFJR43860 and click Next.
    4. Verify the information on the panel and click Uninstall to start uninstalling the Interim Fix.
    5. When the uninstallation 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 Business Space V7.0.0.4 Interim Fix 3

Important: After uninstalling Business Space V7.0.0.4 Interim Fix 3, you must follow the steps below for each WebSphere profile that you want to restore.
  1. Stop the server and the running processes for the profile that you want to restore.
  2. Go to <WAS_HOME>\profiles and rename the <profileName> directory to <profileName>.7004if3.
  3. Go to <WAS_HOME>\bin.
  4. Run the following command:

    manageprofiles.bat -validateAndUpdateRegistry

    The output on the console should display [ <profileName> ].
  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, you must 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, access the link: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/rxml_manageprofiles.html

Restarting the environment after uninstallation of Business Space V7.0.0.4 Interim Fix 3

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

Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere Business Compass Business Space AIX, Linux, Linux zSeries, Windows, Linux pSeries 7.0.0.4
Business Integration WebSphere Business Events Not Applicable AIX, HP-UX, Linux, Solaris, Windows 7.0.1.1, 7.0.1, 7.0
Business Integration WebSphere Enterprise Service Bus Business Space AIX, HP-UX, Linux zSeries, Solaris, Windows, z/OS 7.0.0.4
Business Integration WebSphere Process Server Business Space AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows 7.0.0.4
Business Integration WebSphere Service Registry and Repository Business Space AIX, HP-UX, HP Itanium, Linux, Linux pSeries, Linux zSeries, Linux/x86, Solaris, Windows 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0
Enterprise Content Management Case Foundation ECM Widgets AIX, HP-UX, Solaris, Windows, Linux 4.5.2.1, 4.5.2

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Business Monitor
Business Space

Software version:

7.0.0.4

Operating system(s):

AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows

Reference #:

7036404

Modified date:

2012-10-26

Translate my page

Machine Translation

Content navigation