Collaboration for Business Console - Upgrading Collaboration (from previous version)

Table of Contents [-]

If you are upgrading Collaboration from an earlier version, install the latest version side-by-side and follow the upgrade instructions for the products in the Upgrading webMethods and Intelligent Business Operations Products guide.

Earlier version of Collaboration supported only Oracle database. Collaboration 9.8 includes support for Microsoft SQL Server and IBM DB2 databases.

The following sections describe how to upgrade the Oracle database and list the changes in the latest version of Collaboration.

1. Migrating User Data #

To export the user data from the previous version, do the following:

1.    Ensure that the previous version of Collaboration is running and the latest version is installed.

2.    Access the user management component of the previous version by using URL:

[[http://localhost:18271/umc|http://localhost:18271/umc]]

If you installed Collaboration in a remote machine, replace “localhost” with the actual host name or IP address of the machine on which you installed Collaboration.

3.    Log in as a user with administrative privileges.

4.    Click the User Management tab.

5.    Select Back up data from the Additional functions drop-down on the top right:

6.    Choose the location where you want to put the backup file. Optionally, you can specify a password with which the backup will be encrypted.

7.    To restore the user management data in the user management component of the new version, ensure that the new version of Collaboration has started. See Starting and Stopping Collaboration Server Components . You can access the user management component of new version of Collaboration by using URL:

[[http://localhost:18272/umc|http://localhost:18272/umc]]

8.    Log in to the new version of the user management component as a user with administrative privileges. Since the system has just been installed, the default administrative user is “system” and password is “manager”.

9.    Click on the User Management tab.

10.    Select Restore data from the Additional functions drop-down.

11.    Locate the backup file created in the earlier step. If you specified a password while backing up old data, specify the same password again.

12.    Click OK. All user data and technical settings should now be imported.

2. Upgrading Oracle-based Installation #

2.1. Prerequisites #

To upgrade an old Collaboration installation that is using Oracle, you need the following:

  • Working Oracle database system containing data of the old Collaboration installation.
  • Credentials (usernames and passwords) of the “application user” and “tenant user” that you created for the old installation, and the credentials of a user with administrative privileges to run the scripts.
  • ojdbc6.jar Oracle driver. You can download this driver from the Oracle website to any directory on a physical drive (not a mounted drive).
  • SQL scripts and all the additional files. These scripts and files are located in the installation directory at <Software AG_directory>\ecp\server\scripts\oracle . For example, if you installed to c:\SoftwareAG, you can find these scripts in C:\SoftwareAG\ecp\server\scripts\oracle directory.
  • Oracle SQL*PLUS tool available on the system on which you are running the scripts.

2.2. Backing up Collaboration Data #

Before you start updating the schema, use the DBMS tool to back up of your existing Collaboration data in the Oracle schema (or user) of your old installation. Back up the Oracle schema (or user) referred by the “tenant schema” or “tenant user”. The default name of that schema/user is “ecp_default”. If you have used a different name for the schema/user in your old installation, back up the appropriate schema.

2.3. Updating Existing Schema in Oracle Database #

To migrate the Collaboration data of the previous version stored in Oracle DBMS to the new version of Collaboration, you make the existing data available to the new installation by just making the new installation use the old database and users.

However, the structure of the database schema is slightly changed in the new version. In order to use the existing data with the new version, migrate the schema using the script provided in the installation.

2.4. Updating envset.bat #

Run the <Software AG_directory>\ecp\server\scripts\oracle\inst.bat script file to update the en-vset.bat file as described in Configuring envset.bat. Use the username and password of administrative user and of already existing application and tenant users.

2.5. Updating Tenant Schema in Oracle Database #

To update the existing schema of your Collaboration data to the latest version, run the cip_update_schema_for_tenant.bat script and pass the schema user name of the existing schema as parameter:

cip_update_schema_for_tenant.bat <schemaUserName>

For example, if you used the default “ecp_default” schema user name, the command would be:

cip_ update_schema_for_tenant.bat ecp_default

2.6. Adding Oracle JDBC Driver #

To make the Oracle JDBC driver available to the new version, perform the steps described in Adding Oracle JDBC Driver.

2.7. Registering Oracle DBMS #

You must register the Oracle DBMS used by the previous version with the new version. Perform steps described in Registering Oracle DBMS.

See also #