Before you update

Consider the following guidelines when you update a CDI-PC domain:

•Before you initiate or retry an update, make sure that the nodes are available. Do not start or stop the domain, nodes, or services manually.

• To ensure a smooth update process, verify the following items:

- Confirm that there are no jobs currently in progress to prevent disruption during the update. When a domain is shutdown or unavailable during update, running jobs might be impacted.
- Make sure that the following directory is not open in any file explorer:

<CDI-PC Installation Directory>\Informatica\platform\home

- Disable any custom scripts used to start and monitor the CDI-PC domain to avoid unexpected errors during or after the update.

•When you create a domain, join a domain, migrate a domain, or update a domain, make sure that you do not configure the following directories under INFA_HOME:

- sitekey
- Administrator Console keystore
- Node keystore
- Node truststore
- Domain log
- System log
- Database truststore location
- SAML keystore directory
- SAML truststore directory
- Backup directory

•Make sure that you create custom configuration files or directories only within the /usr directory and avoid placing them elsewhere in the installation folder.

•If you use PowerExchange, back up the dbmover.cfg file before you update the domain. After you complete the domain update, copy the dbmover.cfg file to the new <CDI-PC HOME>\usr\config\pwx\ directory. If you have configured an overrides.cfg file, make sure that you copy the overrides.cfg file to the new directory.

For more information, see Post-installation step for PowerExchange.

•When you start the domain update, all existing service jobs are terminated. You can't cancel, pause, or stop the update after you start.

•After the update begins, don't start or stop the domain, nodes, or services manually, unless asked to by the Informatica Global Customer Support team.

•Don't edit the details of a domain after you initiate an update. The update fails when you shut down the domain to edit the details. If you retry the update, it fails because of a mismatch in domain details. Editing the domain details on the CDI-PC service page does not resolve the mismatch.

Review the environment variables

Before you update the CDI-PC domain, review the environment variables mentioned in the following table:

Variable	Description
IATEMPDIR	Location of the temporary files created during installation. Informatica requires 1 GB disk space for temporary files. Configure the environment variable if you do not want to create temporary files in the /tmp directory. If you want to change the default /tmp directory, you must set IATEMPDIR and _JAVA_OPTIONS environment variables to the new directory. For example, set the variable to export IATEMPDIR=/home/user. Note: Unset the IATEMPDIR variable after the installation.
_JAVA _OPTIONS	Configure the environment variable to change the temporary directory. If you want to change the default /tmp directory, you must set IATEMPDIR and _JAVA_OPTIONS the environment variables to the new directory. For example, set the variable to export _JAVA_OPTIONS=-Djava.io.tmpdir=/home/user. Note: Unset the _JAVA _OPTIONS variable after the installation.
DISPLAY	For UNIX and Linux, unset the DISPLAY environment before you run the installer. Installation might fail if the DISPLAY environment variable has some value.
LAX_DEBUG	For UNIX and Linux, unset the LAX_DEBUG flag before the update. If LAX_DEBUG is set, the installer runs in debug mode and generates a sea.log file under UID/sys/data/installer/<version>/extracted/. This sea.log file disrupts the update process.

Note: Make sure that the NOEXEC flag is not set for the file system mounted on the /tmp directory.