Upgrading from TIBCO ActiveMatrix BusinessWorks™ 6.3.1 or a Higher Version of ActiveMatrix BusinessWorks™ 6.3.x

These instructions apply if you are upgrading from ActiveMatrix BusinessWorks 6.3.1, or later, to a higher version of the software up to ActiveMatrix BusinessWorks 6.3.5, for example, from ActivActiveMatrix BusinessWorks 6.3.1, to ActiveMatrix BusinessWorks 6.3.5. You can upgrade the software when new features are available or when problems in the software have been fixed. Upgrading the software typically includes downloading and installing the newer version, 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.

Prerequisites

  • The base version required for this upgrade scenario is ActiveMatrix BusinessWorks 6.3.1 or higher.
  • Though creating a backup and restoring your files from the earlier version is optional, TIBCO recommends to create a backup of the domain.
    Note: Ensure that all the runtime artifacts have been stopped, and are not running.
  • Stop the bwagent.

Procedure

  1. Install the software in the same TIBCO_HOME directory.
    For instructions on how to complete this upgrade, see Upgrading From Versions Lower than 6.3.1.
    Note: If you are upgrading from a version lower than ActiveMatrix BusinessWorks 6.3.1 to higher, for example ActiveMatrix BusinessWorks 6.2.2 to higher, install the software in the same TIBCO_HOME. For instructions about how to complete this upgrade, see Upgrading From Versions Lower than 6.3.1.
    The installer performs a backup of the config and the bin folders in your BW_HOME, and stores the files at BW_HOME/backup. The installer also performs a backup of the following folders in your BW_HOME, and stores the files at TIBCO_HOME/_installInfo/.spbackup/bw_6.3/bw/6.3:
    • bin
    • config
    • domains
    • ext
    • p2repos
    • system
    The installer also restores the bwagent_as.json and the bwagent_db.json files at BW_HOME/config/.
    Tip: You can delete the bwagent_as.json_bkp and the bwagent_db.json_bkp files at BW_HOME/config/after confirming the contents of these files match the contents of the bwagent_as.json and the bwagent_db.json files .

    After upgrading, you can copy the configuration and .tra files from the backup folder to retrieve your settings before the upgrade.

  2. Update the bwagent.ini file by running the config command with the -cf option. The command changes based on how the bwagent is configured for data persistence and transport.
    If the bwagent is configured to use TIBCO ActiveSpaces, run the following command.
    bwadmin config -cf ../config/bwagent_as.json agent
    If the bwagent is configured to use an external database and TIBCO Enterprise Messaging Service, run the following command.
    bwadmin config -cf ../config/bwagent_db.json agent
    If the bwagent is configured to use an external database and TIBCO FTL for data persistence and transport, run the following command.
    bwadmin config -cf ../config/bwagent_ftl.json agent
    
  3. Unregister and reregister the bwagent. For compatibility details, 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.
  4. Optional. If bwagent is configured to use an external database and TIBCO Enterprise Message Service (EMS) for data persistence and transport, update the database schemas for PostgreSQL, Microsoft SQL, Oracle, DB2, and MySQL. For instructions, see Updating the Database Schema to Enable bwagent to Use Database with TIBCO Enterprise Message Service.
    Note: This applies if you are upgrading from ActiveMatrix BusinessWorks 6.3.1, or from ActiveMatrix BusinessWorks 6.3.2, to a higher version of the software, up to ActiveMatrix BusinessWorks 6.3.5.
  5. Install EMS client libraries. For instructions, see Integrating with TIBCO Enterprise Message Service™.
    Note: This applies if you are moving to ActiveMatrix BusinessWorks 6.3.4 or higher.
  6. 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. Make sure 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 for additional details.

  7. 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.

What to do next

After you have completed the upgrade, import your projects to a new workspace and confirm all of your applications are running properly.
Note: Reusing an existing workspace with the newer version of the software makes that workspace unusable with the older version of the software.