Migrating the Database to Release 7.1 for Arcot Common Components

CA AuthMinder UNIX Installation Guide › Upgrading to Release 7.1 › Upgrading to 7.1 › Migrating the Database to Release 7.1 for Arcot Common Components

Migrating the Database to Release 7.1 for Arcot Common Components

Important! If you have installed CA RiskMinder with AuthMinder and you have completed the RiskMinder upgrade, then do not migrate the database for Arcot common components because this step has already been performed during the RiskMinder upgrade.

Migrate the database for the Arcot common components that are used in release 7.1.

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:
- arcot-common-upgrade-1.0.x-2.0.zip
- arcot-webfort-upgrade-6.x-or-7.0-7.1.zip
Copy the arcot-common-upgrade-1.0.x-2.0.zip file to the following directory:
```
$ARCOT_HOME
```
Extract the contents of the arcot-common-upgrade-1.0.x-2.0.zip file in this directory.
Navigate to the $ARCOT_HOME/tools/common/upgrade/ directory.
Extract the contents of the arcot-common-db-upgrade.zip file in this directory.
Copy the database jar file corresponding to your database to the $ARCOT_HOME/tools/common/upgrade/lib directory with the same name, as follows:
- Oracle: ojdbc.jar
- Microsoft SQL Server: sqljdbc.jar
- DB2: db2jcc.jar
Note: For Oracle and DB2, use the JDBC jar version that is applicable to your database. For Microsoft SQL Server, use sqljdbc4.0 (Microsoft JDBC Driver 4.0 for SQL Server).
Locate the JAVA_HOME used by the existing installation. When you run the upgrade tool, ensure that you use the same JAVA_HOME or the JAVA_HOME from a later, supported version.
Ensure that the libArcotAccessKeyProvider.so file is configured for your application server. This file is in the $ARCOT_HOME/native/<platform-name>/32bit-or-64bit/ directory.
Set and export the LD_LIBRARY_PATH to the directory where the libArcotAccessKeyProvider.so file 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 file:

Option	Description
JVM-Options	The following JVM options are required only if LDAP organizations are configured: -Xmx1024m: Sets the maximum heap size to 1 GB. 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.

Check the log file (default file is $ARCOT_HOME/logs/arcot_common_upgrade.log) to make sure that the common database upgrade is successful.
The upgrade tool also prints verification information.

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.