Before you can begin using the management pack, you must create an adapter instance to identify the host from which the management pack will retrieve data.

Prerequisites

Procedure

  1. From the top navigation bar, select Administration. In the right panel, the Solutions view will be displayed.
  2. Select EpicCareAdapter from the Solutions list on the right.
    solutions_list_after_install-9
  3. Click theConfigure configure_icon icon. The Manage Solution window will appear.
    Note: Click the Add add_icon icon above the Instance Namelist on the left to create multiple adapter instances.

    manage_solution-9
  4. In the Manage Solution window, enter the following information:
    1. Instance Settings:

      • Display Name: A name for this particular instance of the Epic management pack.
      • Description: Optional, but it can be helpful to describe multiple adapter instances of the management pack.
    2. Basic Settings:
      • SystemPulse server: Enter the FQDN or IP address of the Epic System Pulse server instance to which you are connecting.

        Note: The Epic System Pulse server FQDN/IP address must be reachable from all nodes in the vRealize Operations Manager cluster. In addition, depending on your network configuration, you may:
        • Be able to just use the Hostname of the System Pulse server.

        • Have to update firewall rules to enable communication for the vRealize Operations Manager virtual machine with the System Pulse server over ports 80 and 443.

      • HTTPS: Set to true if using HTTPs; set to false if using HTTP.
      • Auto Discovery: When you enable autodiscovery (set to true ; default and recommended setting), the management pack creates resources and relationships in vROps, then collects data for the discovered resources after the main collection query runs. This should not be set to false.
      • Group filter: This option filters resources based on their groups. If you do not enter a filter, resources from all groups are discovered. To discover resources from multiple groups, enter the names of the groups using a comma-separated list.

        Note: PRD is the convention used by Epic to denote production systems in the Caché Host/Instance and Environment hierarchy. So you may use PRD as the group filter to monitor groups that only belong to the Production installation. However, the Epic Windows‐based services hierarchy does not use the same group name convention. If you know exactly which resource groups you want to monitor, you can enter all the groups separated by commas, for example: PRD, Interconnect, EPS. Otherwise it is recommended to leave this field empty to discover all resources and then delete the resources that you do not want to monitor.
      • Credential: Select the credential you created when Creating a Credential (Care Systems Analytics), or click the Add add_iconicon to create a set of credentials now.
    3. Advanced Settings:
      • Collector(s)/Groups: The collector you select determines which vRealize Operations Manager collector is used to manage the adapter processes. Default Collector/Group is automatically selected. Click the drop-down menu if you want to run the collection on a different node.
      • Custom Path for hosted WSDLs: A backup method to provide WSDLs. This path is used only in the event that both the server WSDL and the one hard-coded one in the adapter fail.
      • Include Windows Metrics: Set to true to include metrics for Windows machines. Set to false to help lower the server load by avoiding collection of windows metrics that are already collected by the vSphere adapter.
      • Connect only to simulator:Warning! For development purposes only; keep set to false.
  5. Click Test Connection to test the configured connection information. If you encounter any errors, see: Troubleshooting the Management Pack (Care Systems Analytics).
  6. Click Save Settings and Close to save your adapter instance. 

What to do next