Home
Implementing deployment scenarios
Most implementations of HCL Z Asset Optimizer are based on one of the common deployment scenarios. An example is provided for implementing each of these common deployment scenarios with a Db2® Repository database. You can adapt an example for use with a SQLite Repository database.
Scenario 4: Collecting and transferring Inquisitor and usage data from remote sites
This scenario extends each of the deployment scenarios to collect data from remote sites and transfer the data back to the central site for processing.

Implementing deployment scenarios
Most implementations of HCL Z Asset Optimizer are based on one of the common deployment scenarios. An example is provided for implementing each of these common deployment scenarios with a Db2® Repository database. You can adapt an example for use with a SQLite Repository database.
- Scenario 1: Implementing a single Repository database with a single GKB database
  The most common deployment scenario is an implementation with a single Repository database and a single global knowledge base (GKB) database.
- Scenario 2: Implementing multiple Repositories with a shared GKB database
  This deployment scenario implements two Repositories in a single Db2® subsystem that share a single global knowledge base (GKB) database. The advantage of sharing the same GKB is that you need only apply monthly updates to a single GKB database.
- Scenario 3: Implementing multiple Repositories with multiple GKB databases
  This deployment scenario implements two Repositories in a single Db2® subsystem, each with its own global knowledge base (GKB) database. This deployment scenario is not common because you must apply monthly updates to each GKB database.
- Scenario 4: Collecting and transferring Inquisitor and usage data from remote sites
  This scenario extends each of the deployment scenarios to collect data from remote sites and transfer the data back to the central site for processing.
- Scenario 5: Implementing in a sysplex environment
  This deployment scenario is for a sysplex environment, where the DASD is fully shared across all z/OS® LPARs that belong to the sysplex. This special deployment is similar to the deployment scenarios 1, 2, or 3, but the implementation steps are slightly different. This approach is intended to achieve operational efficiency by processing only a single z/OS LPAR within a sysplex.

Scenario 4: Collecting and transferring Inquisitor and usage data from remote sites

This scenario extends each of the deployment scenarios to collect data from remote sites and transfer the data back to the central site for processing.

Procedure

At the remote site, install the target libraries.
Customize an instance of the HZASCUST member in the hza.SHZASAMP data set with the following parameter:
```
DBTYPE=REMOTE
```
Submit the HZASCUST job.
Collect Inquisitor and Usage Monitor data and transfer the files to the central site for processing:
1. Run the HZASINQZ job on all z/OS® LPARs to collect Inquisitor data.
2. Run the HZASINQU job on all z/OS® LPARs to collect Inquisitor data for UNIX®.
3. Run the HZASUMON job on all z/OS® LPARs to collect usage data.
4. Transfer the collected Inquisitor and Usage Monitor data to the central site using file transfer protocol (FTP).

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.