Application Services Dependencies
A dependent application service is an application service that requires one or more other application services. Before you create a dependent service, you must create all of the application services that the dependent service requires.
For example, the Data Integration Service depends on the Model Repository Service. When you create a Data Integration Service, the Informatica Administrator tool prompts you for the name of a Model Repository Service. Therefore, you must create a Model Repository Service before you create a Data Integration Service.
Services that access Model repository objects can depend on each other. The application service dependencies determine the order that you must create the services.
Services that Access Model Repository Objects
Create the application services that access Model repository objects in the following order:
- 1. Model Repository Service.
The Model Repository Service has no application service dependencies.
- 2. Data Integration Service.
The Data Integration Service depends on the Model Repository Service.
- 3. Catalog Service.
The Catalog Service depends on the Model Repository Service and the Data Integration Service.
- 4. Content Management Service.
The Content Management Service depends on the Model Repository Service and the Data Integration Service.