Documenting Custom Components

Document any custom components, including the following:

• Custom File-System Objects

• Custom Repository Objects

Documenting Custom File-System Objects

Oracle recommends upgrading custom file-system objects. File-system objects that may have been customized include the following:

• Modified file

  Record any changes made to the default iam.properties file.

• Modified file

  Record any changes made to the default jdbc.properties file.

• Modified file

  Record any changes made to the default ldap.properties file.

• Modified file

  Record any changes made to the default rm_idm_init.xml file.

• Modified file

  Record any changes made to default log4j.properties file for customized loggings.

• Modified file

  Record any changes made to the default rbacxmessages.properties file.

• Modified file

  Record any changes made to the default rbacxaudit-messages.properties file.

• Customized property files

  Record any changes made to other property files on the system.

• Customized resource adapters (and any other custom Java code)

  Customized resource adapters may require recompilation depending on the target Oracle Identity Analytics version. All custom Java that uses Oracle Identity Analytics APIs (including custom resource adapters) requires a recompilation as part of an upgrade. Also, consider other Java classes that may use the Oracle Identity Analytics library.

• Custom utilities

  Custom Java utilities, pre-processors, and data parsers may require review and recompilation depending on the target Oracle Identity Analytics version. Plan to re-evaluate the code in these scripts to ensure that they align with database schema changes or application modifications.

• Modified JavaServer Pages (JSP Files)

  Recent Oracle Identity Analytics versions may include API changes. If JSP files were modified during installation, they need to be updated when upgrading. Any JSP file that shipped with the product and was modified during a deployment (or any custom JSP file that uses Oracle Identity Analytics APIs) should be updated so that it is compatible with the JSP structure and API in the target release.

Documenting Custom Repository Objects

Oracle recommends upgrading custom repository objects. Repository objects that may have been customized include the following:

• Modified Email Templates

  Custom e-mail templates may require an export to take advantage of current product enhancements.

• Custom Repository Schema

  If a schema change occurred since Oracle Identity Analytics was last installed or upgraded, a schema update is required.

• Custom Reports

  • Changes made to any reports in the $RBACX_HOME/reports directory should be incorporated into the reports present in the latest version of Oracle Identity Analytics.

  • Do not overwrite reports in the target release with previous versions because any changes made to the Oracle Identity Analytics schema will cause the reports to break.

  • Custom reports uploaded to Oracle Identity Analytics may require modification in order to comply with schema changes.

    Note - The $RBACX_HOME environment variable denotes the path to Oracle Identity Analytics Installation directory.

• Custom Workflow Steps

  Document all custom workflow steps created during Oracle Identity Analytics implementation. These steps would need to be recreated in the newer version of Oracle Identity Analytics.

• Custom CRON Expression

  Custom CRON expressions must be included in the latest version of the Oracle Identity Analytics jobs.xml file, otherwise the CRON expressions will be lost.

• Custom Import Triggers

  To retain previous triggering/scheduling customizations, changes should also be made in the target release scheduling-context.xml file