Domain Configuration Management
The Service Manager on the master gateway node manages the domain configuration. The domain configuration is a set of metadata tables stored in a relational database that is accessible by all gateway nodes in the domain. Each time you make a change to the domain, the Service Manager writes the change to the domain configuration. For example, when you add a node to the domain, the Service Manager adds the node information to the domain configuration. The gateway nodes use a JDBC connection to access the domain configuration database.
You can perform the following domain configuration management tasks:
- •Back up the domain configuration. Back up the domain configuration on a regular basis. You may need to restore the domain configuration from a backup if the domain configuration in the database becomes corrupt.
- •Restore the domain configuration. You may need to restore the domain configuration if you migrate the domain configuration to another database user account. Or, you may need to restore the backup domain configuration to a database user account.
- •Migrate the domain configuration. You may need to migrate the domain configuration to another database user account.
- •Configure the connection to the domain configuration database. Each gateway node must have access to the domain configuration database. You configure the database connection when you create a domain. If you change the database connection information or migrate the domain configuration to a new database, you must update the database connection information for each gateway node.
- •Configure custom properties. Configure domain properties that are unique to your environment or that apply in special cases. Use custom properties only if Informatica Global Customer Support instructs you to do so.
Note: The domain configuration database and the Model repository cannot use the same database user schema.
Backing Up the Domain Configuration
Back up the domain configuration on a regular basis. You may need to restore the domain configuration from a backup file if the domain configuration in the database becomes corrupt.
Run the infasetup BackupDomain command to back up the domain configuration to a binary file.
Note: If the infasetup BackupDomain command fails with a Java memory error, increase the system memory available for infasetup. To increase system memory, set the -Xmx value in the INFA_JAVA_COMD_OPTS environment variable.
When you run this command, infasetup backs up the domain configuration database tables. To restore the domain to another database, you must back up the ISP_RUN_LOG table contents manually to get the previous workflow and session logs.
Additionally, use the database backup utility to manually back up additional repository tables that the infasetup command does not back up.
Restoring the Domain Configuration
You can restore domain configuration from a backup file. You may need to restore the domain configuration if the domain configuration in the database becomes inconsistent or if you want to migrate the domain configuration to another database.
Informatica restores the domain configuration from the current version. If you have a backup file from an earlier product version, you must use the earlier version to restore the domain configuration.
You can restore the domain configuration to the same or a different database user account. If you restore the domain configuration to a database user account with existing domain configuration, you must configure the command to overwrite the existing domain configuration. If you do not configure the command to overwrite the existing domain configuration, the command fails.
Each node in a domain has a host name and port number. When you restore the domain configuration, you can disassociate the host names and port numbers for all nodes in the domain. You might do this if you want to run the nodes on different machines. After you restore the domain configuration, you can assign new host names and port numbers to the nodes. Run the infasetup DefineGatewayNode or DefineWorkerNode command to assign a new host name and port number to a node.
If you restore the domain configuration to another database, you must reset the database connections for all gateway nodes.
Important: You lose all data in the summary tables when you restore the domain configuration.
Complete the following tasks to restore the domain:
- 1. Disable the application services. Disable the application services in complete mode to ensure that you do not abort any running service process. You must disable the application services to ensure that no service process is running when you shut down the domain.
- 2. Shut down the domain. You must shut down the domain to ensure that no change to the domain occurs while you are restoring the domain.
- 3. Run the infasetup RestoreDomain command to restore the domain configuration to a database. The RestoreDomain command restores the domain configuration in the backup file to the specified database user account.
- 4. Assign new host names and port numbers to the nodes in the domain if you disassociated the previous host names and port numbers when you restored the domain configuration. Run the infasetup DefineGatewayNode or DefineWorkerNode command to assign a new host name and port number to a node.
- 5. Reset the database connections for all gateway nodes if you restored the domain configuration to another database. All gateway nodes must have a valid connection to the domain configuration database.
Migrating the Domain Configuration
You can migrate the domain configuration to another database user account. You may need to migrate the domain configuration if you no longer support the existing database user account. For example, if your company requires all departments to migrate to a new database type, you must migrate the domain configuration.
- 1. Shut down all application services in the domain.
- 2. Shut down the domain.
- 3. Back up the domain configuration.
- 4. Create the database user account where you want to restore the domain configuration.
- 5. Restore the domain configuration backup to the database user account.
- 6. Update the database connection for each gateway node.
- 7. Start all nodes in the domain.
- 8. Enable all application services in the domain.
Important: Summary tables are lost when you restore the domain configuration.
Step 1. Disable All Application Services
You must disable all application services to disable all service processes. If you do not disable an application service and a user starts a service process while you are backing up and restoring the domain, the service process changes may be lost and data may become corrupt.
Disable application services in complete mode to ensure that you do not abort running service processes.
Disable the application services in the following order:
- 1. Analyst Service
- 2. Catalog Service
- 3. Cluster Service
- 4. Data Integration Service
- 5. Model Repository Service
Step 2. Shut Down the Domain
You must shut down the domain to ensure that users do not modify the domain while you are migrating the domain configuration. For example, if the domain is running when you are backing up the domain configuration, users can create new services and objects. Also, if you do not shut down the domain and you restore the domain configuration to a different database, the domain becomes inoperative. The connections between the gateway nodes and the domain configuration database become invalid. The gateway nodes shut down because they cannot connect to the domain configuration database. A domain is inoperative if it has no running gateway node.
Step 3. Back Up the Domain Configuration
Run the infasetup BackupDomain command to back up the domain configuration to a binary file.
Step 4. Create a Database User Account
Create a database user account if you want to restore the domain configuration to a new database user account.
Step 5. Restore the Domain Configuration
Run the infasetup RestoreDomain command to restore the domain configuration to a database. The RestoreDomain command restores the domain configuration in the backup file to the specified database user account.
Step 6. Update the Database Connection
If you restore the domain configuration to a different database user account, you must update the database connection information for each gateway node in the domain. Gateway nodes must have a connection to the domain configuration database to retrieve and update domain configuration.
Step 7. Start All Nodes in the Domain
Start all nodes in the domain. You must start the nodes to enable services to run.
1. Shut down the gateway node that you want to update.
2. Run the infasetup UpdateGatewayNode command to update the gateway node.
3. Start the gateway node.
4. Repeat this process for each gateway node.
Step 8. Enable All Application Services
Enable all application services that you previously shut down. Application services must be enabled to run service processes.
Updating the Domain Configuration Database Connection
All gateway nodes must have a connection to the domain configuration database to retrieve and update domain configuration. When you create a gateway node or configure a node to serve as a gateway, you specify the database connection, including the database user name and password. If you migrate the domain configuration to a different database or change the database user name or password, you must update the database connection for each gateway node. For example, as part of a security policy, your company may require you to change the password for the domain configuration database every three months.
To update the node with the new database connection information, complete the following steps:
- 1. Shut down the gateway node.
- 2. Run the infasetup UpdateGatewayNode command.
If you change the user or password, you must update the node.
To update the node after you change the user or password, complete the following steps:
- 1. Shut down the gateway node.
- 2. Run the infasetup UpdateGatewayNode command.
If you change the host name or port number, you must redefine the node.
To redefine the node after you change the host name or port number, complete the following steps:
- 1. Shut down the gateway node.
- 2. In the Administrator tool, remove the node association.
- 3. Run the infasetup DefineGatewayNode command.