Architecture of BMC AMI Command Center for Db2

If they were not already installed for other BMC products, installing BMC AMI Command Center also installs the following components:

• UIM—started task for User Interface Middleware. A minimum of one UIM is required for each SYSPLEX.
• DBC—started task for BMC Execution Component for z/OS. One DBC is required for each LPAR where BMC AMI Command Center is installed.
• LGC—a BMC Configuration Component for z/OS agent that runs within the DBC. One LGC is required for each DBC started task.
• RTCS—started task for Runtime Component Services. One RTCS is required for each LPAR where BMC AMI Command Center is installed.

Infrastructure operation

The following process summarizes how the infrastructure components help control the product's operation:

1. You enter your BMC AMI Command Center URL in your web browser and provide your logon credentials.
2. You are signed on to the UIM, which matches the host and port from the URL.
3. When you request information from a DB2 subsystem, the UIM contacts the local DBC that is running the GUDWBNCH namespace.
4. The DBC contacts other DBCs in the same DBC Group to return a list of DB2 subsystems that are available to you as a BMC AMI Command Center user.

DBC agents

The BMC AMI Command Center client uses multiple agents that run under the control of a DBC to provide Db2 related information. Each agent (Navigation, DDL, Execution, and Explain) is responsible for specific information requests from the BMC AMI Command Center client:

• The Navigation agent (GUD) processes all requests related to Db2 catalog objects, such as generating a list of tables.
• The DDL agent (DDL) processes all requests related to generating SQL or Db2 command syntax, such as CREATE, DROP, START, STOP, DISPLAY, and BIND.
• The Execution agent (EXE) processes all DDL, DML, DB2 commands, and MVS job submission requests, such as processing the SQL syntax that the DDL agent generated.
• The Explain agent (EXP) is responsible for processing all requests related to SQL tuning, such as accessing information in the Db2 statement cache or performing an Explain of an SQL statement.

The agents run as a service within the DBC. As such, multiple instances of each agent can be active at any given time, based on the configuration parameters that are set up in the DBC. For more information, see the Common mainframe infrastructure documentation.