Gateway Manager overview

Gateway Manager coordinates and controls Manager runs by integrating multiple Gateway Servers on UNIX. You can perform any of the following actions:

• List what is running on each console (both Manager run information and agent information)
• Start, stop, view, and recover existing Manager runs
• View reports and logs
• Agent History
• Data Collection and Processing Exception Report
• Manager run logs
• View console configuration (operating system and console version)
• Create new Manager runs and corresponding computer lists

Gateway Manager consists of the Gateway Manager Client component and the Gateway Manager Server component. The server and client communicate via web services.

The Gateway Manager Server resides on the same node as the Manager console. The Gateway Manager Client user interface is integrated with the BMC Helix Continuous Optimization as a separate section under the Administration tab.

Advantages

Gateway Manager offers the follows advantages over traditional Windows and Unix consoles:

• A web-based interface to access all your consoles from one place
• Common functionality, look, and feel between UNIX and Windows consoles
• Ability to determine what is broken and to fix it faster
• Functionalities available only in Gateway Manager include:
  • Multi-select Recovery Run
  • Multi-select Stop Run
  • Agent Listing and Filtering
  • Time-based Analysis: How long has a run been broken?

Overview of Gateway Server components

To manage the collection of data from the required servers, add an agent list (identifies servers from which data is to be collected) in the Gateway Server. Using this list, policy files and Manager runs are created in the Gateway Server. Policy files contain information about the schedule for collecting data from the required servers and the repository to be used for storing the collected data.

Manager runs use the policy files to schedule the data collection, and to extract and store the collected data in the Gateway Server. After the required data is stored in the repository, the Analyze and Predict (Gateway Server components) process the data to convert it to vis format. For details about the Analyze and Predict components, refer to the guides on PDFs-and-videos page.

To automatically send the processed data to the Application Server on a daily basis, use Auto-create ETLs in the Gateway Server (recommended approach). You can also use the BMC - TrueSight Capacity Optimization Gateway VIS file parser ETL for extracting data from Gateway Server. This is mainly required when you want to view historical data. For more information, see BMC-TrueSight-Capacity-Optimization-Gateway-VIS-files-parser.

In BMC Helix Continuous Optimization, use the Out-of-the-box views to perform the capacity planning based on the collected data. These views are organized according to the supported platforms. You can also create a custom view using the available templates to customize the representation of data according to the requirement of your organization. For more information, see Managing-capacity-views.

Recovering data that is yet to be loaded into BMC Helix Continuous Optimization

If data is missed for any reason, you can "recover" it using existing VIS files provided you have been retaining them according to the recommended procedure above. For recovery, you can use a Gateway Server vis files parser ETL with a special configuration. When you use the vis files parser as a recovery ETL, you can use a single one to recover all the Gateway Server ETLs in a task chain. The particular VIS files to be recovered are automatically identified by recovery scripts on the Gateway Server and made available in a predefined directory for the VIS files parser to consume. For more information, see Recovering data using the vis files parser.