Upgrading from Version 6.4.x/6.5.x/6.6.0 to Version 6.6.1

These instructions apply if you are upgrading from version 6.4.2 or later versions of 6.4.x/6.5.x/6.6.0 to version 6.6.1.

1. Install the software in the same TIBCO_HOME directory.
   Follow the instructions in Installation section to install the software in a same TIBCO_HOME directory using GUI, console, or silent mode.

   The installer copies the following files, if they are present, from the TIBCO_HOME/bw/6.x/config/ folder to TIBCO_HOME/bw/6.6/config/ folder and renames the new files as they are with the _orig suffix.

   • bwagent_db.json
   • bwadmin_ftlrealmserver.json
   • bwagent_ftl.json
   • jaas.login.conf
   • realm.properties
   • krb5.conf
   • mashery.ini
   • logback.xml
2. Optional. If you use FTL 5.x in FT mode, add the following properties manually:

   File Name	Changes Required
   bwagent_ftl.json	ftlsecondary: true statsftlsecondary: true
   bwagent_db.json	statsftlsecondary: true

   To create an application on FTL side, use the bwadmin_ftlrealmserver.json_orig file.
3. 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.
4. 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 an external database and TIBCO FTL for data persistence and transport, run the following command.

   bwadmin config -cf ../config/bwagent_ftl.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

   Note: Use bwagent_db/ftl.json_orig file if you want to use new features like Process Monitoring.
5. 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 TIBCO ActiveMatrix BusinessWorks™ Bindings and Palettes Reference.

   Note: If you had already installed third party JDBC drivers in the previous version of ActiveMatrix BusinessWorks 6.3.x/6.4.x, the drivers do not need to be re-installed.
6. Install EMS client libraries to use activities from the JMS palette, or the BWAgent with a database and TIBCO Enterprise Message Service (EMS) for persistence and transport. For instructions about how to configure the EMS client libraries, see Integrating with TIBCO Enterprise Message Service™.
7. Install FTL client libraries to use the activities from the FTL palette, or if the BWAgent is configured to use the dbftl mode. For instructions about how to configure the FTL client libraries, see Integrating with TIBCO FTL.
8. Optional. If you are using a file based or an LDAP authentication, see "Securing the bwagent REST API " section in TIBCO ActiveMatrix BusinessWorks™ Administration.
9. Start the BWAgent.
10. 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 details on recreating runtime artifacts, see "Administration Tasks and Reference" section in TIBCO ActiveMatrix BusinessWorks™ Administration.
    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 

       Note: If you encounter issues with the TIBCO ^® Enterprise Administrator web client UI, 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.