===================================================================================
IBM® WebSphere® Business Modeler Advanced Version 6.0.2
Test Fix 3 Readme
===================================================================================

© Copyright International Business Machines Corporation. 2006. All rights reserved. 

This is a test fix for WebSphere Business Modeler Publishing Server Version 6.0.2. This fix adds tracing to enable further analysis, but risks causing instability in other parts of the product. In a product installation modified by this fix, only the specific function addressed by the fix is supported by IBM. Support may not be available for any other issues encountered after applying this fix. The fix has undergone only informal unit and incomplete integration testing. It is only intended to be applied to an installation of WebSphere Business Modeler Publishing Server Version 6.0.2.

What is a test fix? It is an uncertified temporary fix used to validate the suitability of the fix in a customer environment. This fix has the following characteristics:

Installing the test fix

The installation wizard for Test Fix 3 is very similar to the installation wizard used to install WebSphere Business Modeler Publishing Server Version 6.0.2. The biggest difference between the two wizards is the test fix wizard will ignore any role assignments you make. Instead, WebSphere Business Modeler Publishing Server Version 6.0.2 will use the existing role assignments. For the other fields in the installation wizard, use the same values you used when you installed WebSphere Business Modeler Publishing Server Version 6.0.2. Consult the Installation Guide for more information on these values.

Before you begin installing the test fix, make sure all of the prerequisite servers are running.

To install WebSphere Business Modeler Publishing Server Version 6.0.2 Test Fix 3:

  1. Backup the following databases on the Lotus Domino Server:
  2. Windows: Extract the installable files to a directory with sufficient space. In that directory, double click the WBModeler-PubServer602-iFix1.exe file.
    Linux: Extract the installable files to a directory with sufficient space. In that directory, enter the following command: ./WBModeler-PubServer602-iFix1.bin
  3. Select the language that the installation wizard will use.
  4. In the Welcome panel, click Next.
  5. In the License Agreement panel, accept the terms and then click Next.
  6. Type the path to where WebSphere Business Modeler Publishing Server is installed and then click Next.

    Important: If the installation directory is not correct, the installation will fail without providing any warning or message about the failure.
     
  7. Type the path to the WebSphere Portal Server installation and then click Next.
  8. In the Server Administrator page, type the Profile Name, the WebSphere Application Server administrator user name and password and the WebSphere Portal Server administrator user name and password. Click Next. If you are not sure of the user names and passwords, consult the following settings in the <Portal install root>\config\wpconfig.properties file:
  9. In the LDAP Server Information page, provide the following information:

Click Next.

  1. In the Role Assignment page, click Next. Do not make any role assignments. The installation wizard ignores any role assignments you do because WebSphere Business Modeler Publishing Server Version 6.0.2 will use the existing role assignments.
  2. In the Application Deployment page, verify that the correct WebSphere Application Server instance hosts the Draft and the Released portal applications and that the Help port is correct. Click Next.
  3. In the Lotus Domino information page,

    Click Next. A window that asks about replacing or reusing the databases opens.

  4. Click Reuse. The wizard starts installing the test fix.
  5. Important: If you see messages about replacing more recent files with older files, click No To All.
  6. Click Finish.
  7. Stop the applications in the following order:
    1. WebSphere Portal Server
    2. WebSphere Application Server
  8. Restart the applications in the following order:
    1. WebSphere Application Server
    2. WebSphere Portal Server