Model Repository Architecture
The Model Repository Service process fetches, inserts, and updates metadata in the Model repository database tables. A Model Repository Service process is an instance of the Model Repository Service on the node where the Model Repository Service runs.
The Model Repository Service receives requests from the following client applications:
- •Informatica Developer. Informatica Developer connects to the Model Repository Service to create, update, and delete objects. Informatica Developer and Informatica Analyst share objects in the Model repository.
- •Informatica Analyst. Informatica Analyst connects to the Model Repository Service to create, update, and delete objects. Informatica Developer and Informatica Analyst client applications share objects in the Model repository.
- •Data Integration Service. When you start a Data Integration Service, it connects to the Model Repository Service. The Data Integration Service connects to the Model Repository Service to run or preview project components. The Data Integration Service also connects to the Model Repository Service to store run-time metadata in the Model repository. Application configuration and objects within an application are examples of run-time metadata.
Note: A Model Repository Service can be associated with one Analyst Service and multiple Data Integration Services.
Model Repository Objects
The Model Repository Service stores design-time and run-time objects in the Model repository. The Developer and Analyst tools create, update, and manage the design-time objects in the Model repository. The Data Integration Service creates and manages run-time objects and metadata in the Model repository.
When you deploy an application to the Data Integration Service, the Deployment Manager copies application objects to the Model repository associated with the Data Integration Service. Run-time metadata generated during deployment are stored in the Model repository.
If you replace or redeploy an application, the previous version is deleted from the repository. If you rename an application, the previous application remains in the Model repository.
The Model repository locks objects by default, and when the Model repository is integrated with a version control system, you can manage checked out objects. For more information, see
Repository Object Administration.