Upgrading From Versions Lower than TIBCO ActiveMatrix BusinessWorks™ 6.3.1

These instructions apply if you are upgrading from a version of the software that is lower than ActiveMatrix BusinessWorks™ 6.3.1, for example ActiveMatrix BusinessWorks 6.2.1 to ActiveMatrix BusinessWorks 6.3.5. You can upgrade to a higher version of the software when new features are available or when problems in the software have been fixed. Typical steps include downloading and installing the newer version of the software, and some manual tasks to complete the upgrade. The manual tasks consist of generic tasks required for all versions and some additional tasks that depend on the version you are upgrading to.

Procedure

  1. Install the software in a new TIBCO_HOME directory.
    Follow the instructions in the Installation section to install the software in a new TIBCO_HOME directory using GUI, console, or silent mode.
  2. Back up the domains.
    Important: Before you back up your domains, ensure that all runtime artifacts have been stopped, and are not running.
    To back up a domain, open a console window and navigate to the TIBCO_HOME/bw/<older_version>/bin directory. Then run the following command: 
    bwadmin backup -s <destination_file>.cmd domain <domain_name>
    The bwadmin command file <destination_file>.cmd is generated.
  3. Restore the domains.
    By default, the runtime components are installed under the TIBCO_HOME/bw/<new_version> directory and the runtime artifacts such as domains, AppSpaces, and AppNodes are created under the TIBCO_HOME/bw/<new_version>/domains directory. If you want to use the runtime artifacts created using the older version of the software, you can restore the runtime artifacts for the newer version of the software. Complete the following tasks to restore the runtime artifacts to the new environment:
    Note: You also have the option to re-create the runtime artifacts. For more information about recreating runtime artifacts, see "Administration Tasks and Reference" section of the TIBCO ActiveMatrix BusinessWorks™ Administration guide.
    1. Before restoring the domain, edit the <destination_file>.cmd as described:
      • In the create -agent command, update the argument domainHome to provide the TIBCO_HOME/bw/<new_version>/domains directory.
      • In the upload -domain command, update the location of the archive file to provide the absolute path to the archive file. For example, update the upload -domain command to the following: 
        upload -domain BookStore-Domain <TIBCO_HOME>/bw/<old_version>/bin/archives/BookStore-Domain/tibco.bw.sample.binding.rest.BookStore.application_1.0.0.ear
      Note: You also have the option to import the TIBCO Business Studio™ for BusinessWorks™ projects to a new workspace.

      After installing the latest version of the software, use a new TIBCO Business Studio for BusinessWorks workspace when developing applications, modules, or rebuilding archive files. To use projects created in the older version, import the projects to the new workspace using the File > Import... menu in TIBCO Business Studio for BusinessWorks. Reusing an existing workspace with the newer version of the software makes that workspace unusable with the older version of the software.

      Note: If the agent name is specified as localhost in the command file, update it to specify the bwagent name. The bwagent name (bw.agent.memberName) is the specified in the bwagent.ini file.
    2. To restore the domain, or other runtime entities, in the new TIBCO_HOME environment, navigate to the TIBCO_HOME/bw/<new_version>/bin on the console, and run the following command: 
      bwadmin -f <destination_file>.cmd
  4. Optional. If you have made manual updates to configuration files, or .tra files, copy them from your previous TIBCO_HOME to the appropriate locations in your new TIBCO_HOME.
  5. Reconfigure the bwagent to use an external database with TIBCO Enterprise Message Service, or TIBCO FTL, for data persistence and transport.
    For more information, see "Database with TIBCO Enterprise Message Service Configuration for bwagent" or "Database with TIBCO FTL for bwagent" in the TIBCO ActiveMatrix BusinessWorks™ Administration guide.
  6. Register the bwagent. For more information about compatibility chart, see "Compatibility Chart for TIBCO ActiveMatrix BusinessWorks and TIBCO Enterprise Administrator" in the TIBCO ActiveMatrix BusinessWorks™ Administration guide.
    Note: If you encounter issues with the TIBCO® Enterprise Administrator web client UI after completing this step, stop the TIBCO® Enterprise Administrator server, clean up the sr folder under $TEA_ConfigHome/tibco/cfgmgmt/tea/data/sr, and restart the TIBCO® Enterprise Administrator server.
  7. Optional. Ensure third party JDBC drivers are installed.

    If you want to use other databases, other than PostgreSQL or Microsoft SQL Server, you must add them separately. This is a one time process for every installation of ActiveMatrix BusinessWorks. Open the README.txt in the respective database shells at BW_HOME/config/drivers/shells/ for details on what JAR files to download, and where to add them.

    To add the drivers at run time for Oracle, MySQL or DB2, run the bwinstall command from <BW_Home>/6.x/bin. Ensure that you run bwinstall with no arguments to access the help and instructions to add the driver to the run time. For more information, see "Installing Supported Drivers for Run Time" in the TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference guide.

  8. Optional. Install EMS client libraries. For instructions, see Integrating with TIBCO Enterprise Message Service™.
    Note: This applies if you are upgrading to ActiveMatrix BusinessWorks 6.3.4 or higher.
  9. Drop, and recreate the engine tables.
    Note: This step only applies if you are upgrading to a version of the software that is lower than ActiveMatrix BusinessWorks 6.3.4, for example, ActiveMatrix BusinessWorks 6.3.3 or lower.

    If the engine persistance mode property is set to datastore mode, run the bundled scripts create.sql and create-scp.sql to create tables in the engine database.

    If the engine persistance mode property is set to group mode, run the bundled scripts create.sql and create-dcp.sql to create tables in the engine database.

    To clean the engine database that is configured for datastore mode, run the drop.sql and drop-scp.sql scripts. If the engine database is configured for group mode, run the drop.sql and drop-dcp.sql scripts.

    Note: Before you clean the engine database, ensure that you have backed up all important data.