After you update the CDI-PC domain, restore your previous customizations and copy any necessary files to ensure the updated CDI-PC domain functions seamlessly.
•Copy the custom JAR files from PowerCenter INFA_HOME/server/bin/javalib folder to CDIPC_HOME/server/bin/javalib.
•After the update completes, the assigned permissions in the pmimpprocess executable changes. Configure the pmimpprocess executable to change the ownership and access permissions required for each user.
Update the configuration files
When you update, the installer overwrites configuration files, such as odbc.ini, odbcinst.ini, or sapnwrfc.ini. If any of the configuration files contain customization, updated, or new properties, you can manually merge the changes from the backup files into the latest installed file. For instance, if odbc.ini contains some variables or connection options, you need to manually merge the changes to the latest install file paths.
Manually merge the latest configuration changes into the following install file paths after you update:
$INFA_HOME/ODBC7.1/odbc.ini
$INFA_HOME/ODBC7.1/odbcinst.ini
$INFA_HOME/server/bin/sapnwrfc.ini
Here, $INFA_HOME denotes <install_dir>/Informatica/platform/home and $INFA_HOME/ODBC7.1 is a softlink for <install_dir>/Informatica/platform/usr/bin/ODBC7.1.
The backup files are available in the following location: <install_dir>/Informatica/platform/sys/data/backup/<release_version>/PLATFORM/home
During an update, the installer creates a backup copy of the odbcinst.ini file in the same folder, appending the pre-update version number to the backup file name.
The following table lists examples of configuration files and their corresponding backup files:
Sample configuration file
Backup file
File to be updated
odbc.ini
<install_dir>/Informatica/platform/sys/data/backup/202404/PLATFORM/home/ODBC7.1/odbc.ini_202404_<DateTime of Backup>
Use script files to set environment variables for infaservice and infasetup commands. If you added custom configuration values in your Informatica domain, copy those values to the corresponding script file before performing an update.
You can find the script files, infasestupconfig.sh and infaserviceconfig.sh, in the following location:
Note: Any values that you edit in the infasetup.sh and infaservice.sh files might be overwritten when you apply updates.
Add external certificates to the trust certificates file
Consider the following guideline for adding external trust certificate files:
•After you update the CDI-PC domain, you must import all the previously imported certificate files to cacerts and ca-bundle.crt files. During the update, the installer moves your previously imported certificate files to the following location:
Use script files to set environment variables for infaservice and infasetup commands. If you added custom values in your Informatica domain, copy the values to the corresponding script file after you migrate or update the domain.
You can find the script files, infasestupconfig.sh and infaserviceconfig.sh, in the following location:
For any custom settings, use the Informatica/platform/usr/bin/infaserviceconfig.sh file to configure JVM parameters for the domain.
If you use environment variables such as INFA_JAVA_OPTS or INFA_JAVA_CMD_OPTS to set customized values for JVM parameters that infaservice and infasetup commands use, set the variables and values in the configuration file for each command.
For example, to set the maximum heap size to 4 GB for each of the commands, configure each file as follows:
Note: Any values that you edit in the infasetup.sh and infaservice.sh files might be overwritten when you apply updates.
Rules and guidelines for Java Runtime Environment on AIX
Consider the following guidelines for Java Runtime Environment on AIX:
•Informatica doesn't ship the Java libraries for AIX. Before you install CDI-PC on AIX, you must download the IBM Semeru Runtime Certified Edition 11.0.25.0 (build 11.0.25+9).
Download the following file: OpenJ9 VM 11.0.25.0 (build openj9-0.48.0)
If you have problems installing the JRE, contact the JRE vendor.
•Provide the updated JAVA version path before starting the CDI-PC update.
Set the INFA_JRE_HOME_<release_version> property in infaserviceconfig.sh pointing to the path of the updated JAVA version installation. The JAVA version must match the version to which the CDI-PC domain needs to be updated. You must set JAVA version path on all the nodes before updating the domain.
After a successful domain update, you must update the environment variable INFA_JRE_HOME to the new JAVA installation.
Restart a failed update
The update job goes through multiple stages to complete the update. You can monitor the progress of the update on the Update Domain page. If the update fails at any stage, you can retry the update.
On the Update Domain page, click Retry Update in the Final Status column.
A retry might fail if there is a mismatch between the domain status required to restart the update and the actual domain status. View the logs for information on the failure and troubleshoot the issue before you retry the update.