Migrate the Common Components Database

CA Advanced Authentication Upgrade Guide › CA Advanced Authentication Upgrading › How to Upgrade CA Strong Authentication on UNIX › Migrate the Common Components Database

Migrate the Common Components Database

To migrate the database for the common components that CA Strong Authentication uses, perform the following steps.

Follow these steps:

Copy the upgrade directory to a temporary location on the system where you plan to upgrade.
This folder contains the following zip files that are applicable for this migration path:
- ca-common-upgrade-1.0.x-2.0.zip
- ca-strongaauth-upgrade-6.2.9-or-7.x-8.0 .zip
Important! If CA Risk Authentication is already upgraded to 8.0, or if current CA Strong Authentication version is 7.x, or if current CA Risk Authentication version is 3.x, then ignore Steps# 2 to 12.
Copy the ca-common-upgrade-1.0.x-2.0.zip file to the $ARCOT_HOME directory:
Extract the contents of the ca-common-upgrade-1.0.x-2.0.zip file in this directory.
Navigate to the following directory:
```
%ARCOT_HOME%/tools/common/upgrade/
```
Extract the contents of the arcot-common-db-upgrade zip in this directory.
Copy the database jar file corresponding to the following database with the same name, to the %ARCOT_HOME%/tools/common/upgrade/lib/ directory:
- Oracle Database: ojdbc.jar
- Microsoft SQL Server: sqljdbc.jar
- IBM DB2 UDB: db2jcc.jar
Note: For Oracle Database and IBM DB2 UDB, use the JDBC JAR version that is applicable to the database. For Microsoft SQL Server, use sqljdbc4.0 (Microsoft JDBC Driver 4.0 for SQL Server).
Copy the libArcotAccessKeyProvider.so file to <JAVA_HOME used by App Server>/jre/sbin. Example: In CA Strong Authentication release 6.x, the libArcotAccessKeyProvider.so file is available in <ARCOT_HOME>/java/ext/<platform name>/<32bit or 64 bit>.
Copy the $ARCOT_HOME/java/lib/arcot-crypto-util.jar file
to
```
JAVA_HOME-used-by-App-Server/jre/lib/ext
```
Set and export the LD_LIBRARY_PATH to the directory where libArcotAccessKeyProvider.so is copied.
Change your working directory to:
```
$ARCOT_HOME/tools/common/upgrade/
```

Run the arcot-common-upgrade-framework.jar file by using the following command:

java [JVM_Options] -jar arcot-common-upgrade-framework.jar [--log-file <log-file-name>] [--log-level <log-level>][--commit-batch-size <batch_size>] [--product-name common][--prompt][--mst]

The following table describes the options that are supported by this JAR:

Option	Description
JVM-Options	The following JVM options are required only if LDAP organizations are configured: -Xmx1024m: Sets the maximum heap size to 1GB. If more than 1,00,000 users exist in the configured LDAP, then it is highly recommended that you increase the heap size to 2048m (2 GB). -Dcom.arcot.ldap.migration.timeout=<duration>: The time duration, in minutes, after which the migration of the LDAP organization is marked as failed. The LDAP migration timeout for 1,00,000 users is approximately 240 minutes or 4 hours. However, this would depend on the type of hardware configuration being used. The default value of this parameter is 240 minutes.
log-file	Specifies the path to the log file: If you do not provide any value, the arcot_common_upgrade.log file is created in the %ARCOT_HOME%\logs\ directory. If you provide an absolute path, the log file is created at the given location. If you provide a file name, the log file is created in %ARCOT_HOME% with the given file name.
-log-level	Specifies the log level. If you do not provide any value, the upgrade log level is set to INFO.
commit-batch-size	Specifies the number of transactions to be issued to the database before a COMMIT statement is issued.
product-name	Specifies the name of the product that has to be migrated. The default value is common.
prompt	Prompts whether to proceed further after each phase is completed successfully. You can choose to run the tool later to continue from where it stopped. If this option is not specified, the upgrade tool runs without any prompting until the upgrade process is completed.
mst	Refers to the Monitoring Sleep Time. If you specify this option, the upgrade tool prints diagnostic messages describing the progress made during upgrade after sleeping for the specified duration (in minutes.) The default value is two minutes.

12. Check the log file $ARCOT_HOME/logs/arcot_common_upgrade.log to ensure that the common database migration was successful.

Important! While migrating the database, if you encounter errors due to a step that you have performed incorrectly, restore the database backup that you created earlier. After you verify that the database is correctly restored, retry the database migration procedure.