000039201 - How to update the HXTT Text JDBC Driver in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Aug 5, 2020
Version 1Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000039201
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.2.x
 
IssueThe HXTT Text JDBC Driver is used by RSA Identity Governance & Lifecycle for CSV data collections. If a defect in the HXTT Text JDBC Driver is reported, a new driver is needed to replace the existing driver. This is done through the RSA Identity Governance & Lifecycle patch process. As a workaround, the driver may be replaced manually without applying the patch. The purpose of this RSA Knowledge Base Article is to describe the steps needed to update the HXTT Text JDBC Driver by customizing the aveksa.ear file.
 
ResolutionThe resolution in this article assumes that you have already acquired the version of the HXTT Text JDBC Driver that you will be using to update the ear file and have placed it in a directory on the RSA Identity Governance & Lifecycle server.

To update the HXTT Text JDBC Driver, the aveksa.ear file needs to be customized.
  1. First make sure the version of the HXTT Text JDBC Driver you are trying to install isn't already installed. Do this by following the steps in RSA Knowledge Base Article 000039102 -- How to identify the deployed version of the HXTT Text JDBC Driver in RSA Identity Governance & Lifecycle.
  2. If the currently deployed version is different from the one you plan to install, then continue to Step 3.
  3. Follow the steps to customize the aveksa.ear file described in RSA Knowledge Base Article 000038700 -- How to customize the application using customizeACM.sh in RSA Identity Governance & Lifecycle until you get to Step 6.
  4. Go to the /tmp/customizeACM directory and backup and replace the existing HXTT Text JDBC Driver.


$ cd /tmp/customizeACM
$ cp aveksa.war/WEB-INF/LocalAgent/common/lib/Text_JDBC<major-version#>.jar $AVEKSA_HOME/Text_JDBC<major-version#>.jar_backup
$ rm aveksa.war/WEB-INF/LocalAgent/common/lib/Text_JDBC<major-version#>.jar
$ cp <location of new jar>/Text_JDBC<major-version#>.jar aveksa.war/WEB-INF/LocalAgent/common/lib


Example:



$ cd /tmp/customizeACM
$ cp aveksa.war/WEB-INF/LocalAgent/common/lib/Text_JDBC42.jar $AVEKSA_HOME/Text_JDBC42.jar_backup
$ rm aveksa.war/WEB-INF/LocalAgent/common/lib/Text_JDBC42.jar
$ cp $AVEKSA_HOME/Text_JDBC42.jar aveksa.war/WEB-INF/LocalAgent/common/lib




  1. Return to RSA Knowledge Base Article 000038700 -- How to customize the application using customizeACM.sh in RSA Identity Governance & Lifecycle and complete the customization steps.

 

Attachments

    Outcomes