Upgrade Guide › WebSphere Version › Manual Upgrades › Manually Upgrade the Provisioning Directory

Manually Upgrade the Provisioning Directory

CA Directory no longer uses Ingres as a data store. Starting at CA Directory r12 SP1, a new memory-mapped file technology named DXgrid is used. For Provisioning to work with CA IdentityMinder 12.6.2, upgrade the Provisioning Directory schema and CA Directory.

Note: If you want to install your Provisioning Directory on a new system, migrate the Provisioning Directory instead of performing an upgrade. See the Provisioning Components Upgrade chapter.

Important! Upgrading the Provisioning Directory must be done by running the upgrade.bat (or upgrade.sh) file located in the CADirectory/dxserver directory. Do not perform the upgrade by running the Provisioning Directory setup.exe file. The upgrade.bat script will examine your system and then upgrade CA Directory after performing any prerequisite cleanup, then the script will upgrade the Provisioning Directory.

To manually upgrade the Provisioning Directory

1. If you have primary and alternate Provisioning Directories, back up your primary Provisioning Directory.
2. Shut down all Provisioning Directories in your environment.
3. Stop Ingres with the following command:

   ingstop -service(or ingstop -kill)
   

4. Verify that all of the following Ingres processes are stopped:
   • dmfacp.exe
   • dmfrcp.exe
   • iidbms.exe
   • iigcc.exe
   • iigcn.exe
   • iijdbc.exe
   • iistar.exe
5. Restart Ingres with the following command:

   ingstart -service
   

6. Verify that the Provisioning and Connector services are stopped.
7. (Windows only) Be sure the Local Service account has read/write permissions to the folder where CA Directory will be installed. 
8. Navigate to the CADirectory/dxserver folder on the CA IdentityMinder installer media.
9. Run the upgrade.bat file.

   The Provisioning Directory upgrade wizard starts.

   Note the following:

   • Part of the Provisioning Directory upgrade is the upgrade of CA Directory to the latest bundled r12.0 Service Pack. Due to architectural changes in CA Directory r12 SP1 (and higher), reporting databases and unnecessary DSAs are removed before the CA Directory upgrade. Once the CA Directory upgrade completes, the Provisioning Directory upgrade will resume
   • If you are installing the Provisioning Directory in an FIPS 140-2 enabled environment, select the FIPS 140-2 Compliance mode check box during installation and provide the FIPS Key File.
10. Go through the wizard and enter the information you collected for the upgrade. Select a Typical installation type when prompted during the CA Directory upgrade.

    The Provisioning Directory and CA Directory are upgraded.

Note: You can select a check box during upgrade to configure Provisioning Directory high availability. If you choose this option, you must supply the hostnames of any alternate Provisioning Directories and specify the primary Provisioning Directory. When the upgrade completes, uninstall and reinstall any alternate Provisioning Directories. For more information, see the Installation Guide.

For details on using CA Directory, you can find CA Directory documentation at support.ca.com.