CEPM Install and Config Guide
CEPM Migration Information

Table Of Contents

CEPM Migration Information


CEPM Migration Information


This chapter contains migration information for your existing CEPM installation. If you are already using an older version of the CEPM (for example, Securent-V3.2.0.0) and want to upgrade to the CEPM V3.3.0.0, you can do so by migrating the database from your older (existing) version to the latest version. Before upgrading, it is highly suggested to make a full backup of your existing installation directory.


Note Make sure that the DB replication activities (for both Oracle and MSSQL) are suspended before executing the migration script. If you are using MSSQL, increase the Database Transaction Log size to 1GB while doing the migration.


To upgrade the installation, take the following steps:


Step 1 Complete steps 1 through 17 in Chapter 3, "Common Installation Steps."

Step 2 Manually update the new config files (pap_config.xml, pdp_config.xml and logging.xml) by mapping the existing (say, V3.2.0.0) config parameter values to the V3.3.0.0 parameters. This is because a version upgradation will not migrate these values to the new config files and thus must be updated manually. Refer to Appendix B, "Updating configuration files while doing migration" for details.

Step 3 Run the appropriate migration script from .../CEPM-V3.3.0.0/migrate folder.

For example, if you are currently using the CEPM V3.2.0.0, instead of running the createtables.bat file, upgrade your CEPM application from version 3.2.0.0 to 3.3.0.0 by running the Migration-v3.2-3.3.sql file in your corresponding database client.

The following migration scripts are available for the CEPM v3.3.0.0:

Table 10-1 Migration Scripts

DB-Type
Migration Type
Migration Scripts
Oracle (9i/10g/11g)

V3.0.2 to V3.3.0.0

Migration-v3.0.2-3.3.SQL

V3.1GA to V3.3.0.0

Migration-v3.1GA-3.3.SQL

V3.2.0.0 to V3.3.0.0

Migration-v3.2-3.3.SQL

MSSQL(2000/2005)

V3.0.2 to V3.3.0.0

Migration-v3.0.2-3.3.SQL

V3.1GA to V3.3.0.0

Migration-v3.1GA-3.3.SQL

V3.2.0.0 to V3.3.0.0

Migration-v3.2-3.3.SQL

V3.2.3.0 to V3.3.0.0

Migration-v3.2.3-3.3.SQL


Step 4 Run templateloader.bat (for Windows) or templateloader.sh (for Linux and Solaris) file from /CEPM-V3.3.0.0/bin folder to load the latest templates into the CEPM database.


Note Do not run the templateloader.bat file when the installation is fresh, because the createtables.bat file is run while installing CEPM for the first time. This file must be run only when migration is required.


Step 5 Run ruleconversionto33.bat (for Windows) or ruleconversionto33.sh (for Linux and Solaris) file from /CEPM-V3.3.0.0/bin folder which will update your existing application with the latest rule creation feature.

Step 6 Execute the database procedures in the following way:

Table 10-2 Executing DB Procedures

DB Type
Action

Oracle9i

To execute the procedure in Oracle 9i, open any Oracle client (such as SQL Plus, Benthic, Putty etc.) and run the pap.sql and pdp.sql files from the /CEPM-V3.3.0.0/db/scripts/oracle folder.

Example: Open SQL Plus and use the following command to invoke pap.sql in the client:

SQL> @ /CEPM-V3.3.0.0/db/scripts/oracle/pap.sql

Oracle (10g/11g)

To execute the procedure in Oracle 10g or 11g, open the Oracle client (use SQL Plus only) and run the pap_wrapped.sql and pdp_wrapped.sql files from the /CEPM-V3.3.0.0/db/scripts/oracle folder.

MSSQL (2000/2005)

To execute the procedure in MSSQL Server 2005, open the MS SQL client and run the pap.sql and pdp.sql file from /CEPM-V3.3.0.0/db/scripts/mssql folder. For MSSQL 2000, these scripts are available in /CEPM-V3.3.0.0/db/scripts/mssql/mssql2000 folder.

It is recommended to run these scripts in MSSQL Query Analyzer, because executing these scripts through SQLCMD might not compile all the functions and procedures.

DB2

To execute the procedure in DB2, open the DB2 client and run the pap.sql and pdp.sql files from /CEPM-V3.3.0.0/db/scripts/DB2 folder.

Refer to Chapter 12, "Running CEPM Scripts in DB2 Client"for more information about how to run the pap.sql and pdp.sql scripts in DB2.


(If you get any error at this stage, see Chapter 15, "Troubleshooting CEPM Installation.")