A split domain configuration is more complex than a single domain configuration.
In a split domain, you must create duplicate services, repositories, and users. If you install both domains on the same machine, you must ensure that there are no port conflicts for the components in each domain. When you run different Informatica versions in each domain, you must also consider possible database version conflicts. For example, you create PowerCenter repositories for different Informatica product versions in the same Oracle database. You must ensure that both Informatica product versions support the Oracle database version.
There might be license implications.
If you use Informatica products for data integration, your license agreement usually limits data integration activities to one domain. Your license agreement might limit the number of machines on which you can create application services or the types of services that you can duplicate. You might also need a separate license file for each domain.
For questions about licensing, contact your Informatica products representative.
You need additional database schemas and user accounts.
In a split domain, you must create duplicate repositories. For example, you create a domain configuration repository in each domain. If you run PowerCenter and Metadata Manager in separate domains, you also create a PowerCenter repository in each domain.
Each repository must be in a separate schema. You also need a separate database user account for each domain configuration repository.
You need additional RAM and disk space.
When you install Informatica services, the amount of required RAM and disk space for two domains is twice the required amount for one domain.
There are product version restrictions.
In a split domain, the components in the secondary domain can run the same version or a later version of Informatica products than the components in the primary domain. Therefore, you can run a later version of Metadata Manager than PowerCenter. However, you cannot run a later version of PowerCenter than Metadata Manager.
You might need to run a different version of the PowerCenter Client in each domain.
For example, you run the PowerCenter Client in the primary domain to perform data integration operations. In the secondary domain, you run a later version of Metadata Manager. To view session logs from Metadata Manager resource loads, you must run a later version of the PowerCenter Client in the secondary domain.
You cannot access Metadata Manager data lineage from the PowerCenter Designer.
In a split domain, the PowerCenter services in the primary domain do not communicate with the Metadata Manager Service in the secondary domain. Therefore, you cannot access Metadata Manager data lineage from the PowerCenter Designer.