Predeployment considerations
You can deploy Z Asset Optimizer to use a single Repository or multiple Repositories.
Implementing a deployment in a single Repository is relatively
straightforward because the data from all systems is imported into
a single Repository. Before you deploy with a single Repository,
plan the following aspects of the deployment:
- How frequently will the Inquisitor scan each system?
- If you have systems that are located at remote sites, what mechanism will transfer collected Inquisitor and usage data through file transfer protocol (FTP) to the central site, and how frequently will these transfers occur?
- How often is it necessary to load Inquisitor and usage data from each system into the Repository?
To deploy with multiple
Repositories, plan the following aspects
of the deployment:
- How frequently will the Inquisitor scan each system?
- How many Repositories to include in the deployment and are all of these Repositories located at the central site?
- For each system, which Repository loads the Inquisitor and usage data for the system?
- If you have systems that are located at remote sites, what mechanism will transfer collected Inquisitor and usage data through file transfer protocol (FTP) to the central site, and how frequently will these transfers occur?
- How often is it necessary to load Inquisitor and usage data from each system into its specified Repository?