WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Migrating WebSphere Premises Server

Use these instructions to migrate from WebSphere® Premises Server 6.1 to WebSphere Premises Server 6.1.0.1.

Before you begin
  1. Close the Data Transformation service console.
  2. Stop all WebSphere Application Server processes.
  3. If you are using a remote Bundle Repository Server, update WebSphere Application Server and IBM® HTTP Server on the Bundle Repository Server to the level required by the fix pack. See Hardware and software requirements for details.
  4. If you are using Oracle, update to the level required by the fix pack. See Hardware and software requirements for details.
  5. Back up your database.
Procedure
  1. Run the installation program located in the sat_installer directory of the WebSphere Premises Server disk appropriate for your operating system.

    If you have a Linux® operating system, make sure you run LinuxSetup from a new shell window.

    • Windows WindowsSetup.exe
    • Linux LinuxSetup

    When you run the installation program, the deployment wizard is temporarily installed on your hard drive. It will uninstall itself when the installation is complete. When the deployment wizard installation completes, it automatically launches and guides you through the installation of the product and its prerequisite software. It may take a few minutes to begin.

    You can also run the installation program in silent mode. Refer to Installing silently for further instructions.

  2. Select the radio button beside the I accept both the IBM and the non-IBM terms statement if you agree to the license agreement and click Next to continue.
  3. When the Welcome panel appears you can either:
    • Click Next to continue installing the product.
    • Or, if you would like to change the default path used for the deployment package, follow the instructions in Changing the deployment package path before continuing with the next steps.
  4. On the Select Tasks panel, click Next to install the product and to choose the database type.
  5. Choose to use either DB2® or Oracle as your local or remote database.
  6. Choose to install WebSphere Premises Server only and click Next.
    Important: Migration of Location Awareness Services for WebSphere Premises Server is not supported. You can update your Location Awareness Services for WebSphere Premises Server version from 6.1 to 6.1.0.1 using the installer, but any customization, such as defined areas and classes, will not be retained.
  7. Click Next to install the required Bundle Repository Server.
    Note: If you do not install Bundle Repository Server on your local server, then you need to install the prerequisite middleware on the remote server before installing Bundle Repository Server. Make sure that you have purchased a separate license for the required middleware that you install on a remote server. Also, you will need to modify the WebSphere Premises Server SystemAgent to reflect the correct location of your Bundle Repository Server.
  8. On the Specify Target Computers panel for your database server, specify the target computer for DB2 or your existing Oracle database and click Next.
    • For a local server installation for DB2 or an existing installation of Oracle, the default value is localhost. You can either keep this value or change it.
    • If you are installing the product and DB2 on separate servers, specify the fully qualified host name, operating system, user ID, and password of the server where DB2 should be installed.
    • If you are installing the product on one server and using an existing Oracle installation on another server, specify the fully qualified host name, operating system, user ID, and password of the server where Oracle is installed.
    • Optionally, use the Test connections button to test access to the remote target computer. Firewalls can have an adverse effect on the installation even though the connection test result is successful.
  9. On the Specify Target Computers panel for WebSphere Premises Server, specify the target computer for WebSphere Premises Server and click Next.
    • For a local server installation, the default value is localhost. You can either keep this value or change it.
    • If you are installing WebSphere Premises Server and its required middleware on a remote server, specify the fully qualified host name, operating system, user ID, and password of the server where it should be installed.
    • Optionally, use the Test connections button to test access to the remote target computer. Firewalls can have an adverse effect on the installation even though the connection test result is successful.
  10. On the Specify Target Computers panel for Bundle Repository Server, specify the target computer for Bundle Repository Server and click Next.
    • For a local server installation, the default value is localhost. You can either keep this value or change it.
    • If you are installing Bundle Repository Server on a remote server, specify the fully qualified host name, operating system, user ID, and password of the server where it should be installed.
      Remember: You must install the required middleware on the remote server before installing Bundle Repository Server.
    • Optionally, use the Test connections button to test access to the remote target computer. Firewalls can have an adverse effect on the installation even though the connection test result is successful.
  11. Enter your database configuration information.
    • If you would like the installation program to run database scripts to migrate your existing tables and data on the database, check Migrate existing 6.1 tables and click Next.
    • If you would like the installation program to run database scripts to create new tables and populate new data on the database, check Create and populate 6.1.0.1 tables and click Next.
    • If you have already migrated your database manually with the scripts provided, select Do not change the database.
  12. Enter the necessary information for WebSphere MQ and click Next.
    • Windows If you are installing on a Windows® operating system, you are prompted to enter the installation directory for WebSphere MQ or accept the default installation directory.
    • Linux If you are installing on a Linux operating system, you are prompted for a password.
  13. Enter your WebSphere Application Server configuration information and click Next.
    Important:
    • If you have an existing version of WebSphere Application Server that is 6.1.0.0 or later (but not the required version 6.1.0.17), and you want the installer to update your WebSphere Application Server version, then you must have WebSphere Application Server stopped before deploying the WebSphere Premises Server installation.
    • WebSphere Application Server security is not enabled by the installer. You must set up and configure security separately.
    • If you are going to use any WebSphere Premises Server APIs or the Print, Verify, and Ship application, make sure that the profile you choose to use has the HTTP transport port set to 9080.
    • If you do not plan to install WebSphere Premises Server and WebSphere Application Server on the default drive (such as the C drive on Windows operating systems), click the Advanced tab for the configuration parameters and make sure your WebSphere Application Server profile path reflects the correct drive location for your installation.
  14. Enter your IBM HTTP Server configuration information and click Next.
  15. Enter the installation directory for WebSphere Premises Server.
  16. Enter the configuration information for Bundle Repository Server.
  17. On the Summary Panel, confirm your choices. The summary provides a list of tasks that you selected and an estimated time for their completion.
    • To start all installation and configuration tasks, click Deploy all.
    • If you only want to start a specific task, click Deploy task, but make sure that the tasks you choose are in the correct sequence on the panel. For example, you cannot deploy WebSphere Premises Server before deploying DB2 if you do not already have a database installed.
    Click Back to make any changes. After you start the deployment, you have the option to click Stop Deployment if you need to stop the installation before it is finished. Once all deployment tasks are complete, the Deployment Status screen indicates if the deployment was successful.
  18. When the installation is complete, check the log files for any errors. From the Deployment wizard, you can view detailed messages or the master log. Click Master log and select Save as... to save the log file. The logs can be found in deployment_wizard_installation_dir/logs, where deployment_wizard_installation_dir is the installation location of the Deployment wizard.
    • Windows C:\Program Files\SolutionFiles\logs
    • Linux opt/SolutionFiles/logs
  19. Click the X at the top, right-hand side of the panel to exit the wizard. The wizard displays some messages:
    • A prompt for whether you want to save changes. If you plan to run the wizard again, click Yes. Otherwise, click No.
    • A prompt for whether you wish to exit. Click Yes to exit the wizard.
  20. If you want to use the simulated reader to verify your migration, run these SQL scripts for your database, either from a DB2 command line or from the Oracle sqlplus tool.
    INSERT INTO SAGE.DCDEVICELOCATIONAGENT VALUES ('IBMSimulatedReaderAgent', 
    'com.ibm.rfid.reader.simulator.bundle.ReaderSimulatorManagedServiceFactoryActivator', 
    'TagReadingExpression', '(b1=true)', 'String', 'Tag Reading Expression',
    'IBM Simulated Reader' ,'0','true', 'true' );
    
    INSERT INTO SAGE.DCDEVICELOCATIONAGENT VALUES ('IBMSimulatedReaderAgent', 
    'com.ibm.rfid.reader.simulator.bundle.ReaderSimulatorManagedServiceFactoryActivator', 
    'log.level', '', 'String', 'log level','IBM Simulated Reader', '0','true', 'true' );
Results

When you have successfully completed the migration, the following software has been updated:

What to do next

Follow the post-installation steps to verify your installation.


Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.