Install a Device Pack in DX NetOps Mediation Manager
Use this article to install a device pack in on the Windows or UNIX systems. This article contains the following topics:
Use this article to install a device pack in
DX NetOps Mediation Manageron the Windows or UNIX systems. This article contains the following topics:
A device pack is a set of XML configuration, ServingXml or Groovy, and XQuery files. Device packs pull data from a specific set of devices and convert it to a form that can be read by eHealth,
DX NetOps Spectrum, CA Infrastructure Management, or
DX NetOps Performance Management.
Install Engine and Presenter
You can install the Engine and Presenter through the
DX NetOps Mediation ManagerWeb UI.
Follow these steps:
- Launch theDX NetOps Mediation ManagerWeb Manager:http://<PrimaryMCMachineIP>:<web-port>Where <web-port> is the port number that is configured during theDX NetOps Mediation Managerinstallation, and <PrimaryMCMachine IP> is the IP address or hostname of the primary MultiController system.
- Enter the login credentials.Confirm that the working environment is CA eHealth.
- Select the Device Packs tab and click Install.
- Specify the destination of the LocalController using the LocalController drop-down.
- Perform one of the following steps in the Device Pack configuration dialog:
- If the device pack is located in the Device Pack repository that is shipped with the current release ofDX NetOps Mediation Manager, select the DevicePack Repository check box.
- If the device pack is not located in the Device Pack repository and resides in the local system, click Browse and locate the device pack.
- Select the ENGINE_<devicepack>.zip file or the PRESENTER_<devicepack>.zip file that you want to install.
- Click Next.
- Provide the configuration parameters in Global External Variables and Component Configuration for the Engine or Presenter being installed.For more information about specific device pack configuration files, see the corresponding Engine readme file by selecting ReadMe from the Web UI.
- Select Finish.The device pack is installed.
Install CA eHealth Certification
To view the reports in CA eHealth, install eHealth certification. Installation of certification consists of the following two steps:
- Deploy Certification manually or automatically
- Manually import the elements to CA eHealth.
Deploy the eHealth Certification Automatically
Deploy the eHealth Certification automatically through
DX NetOps Mediation ManagerWeb.
Follow these steps:
- Launch theDX NetOps Mediation ManagerWeb UI:http://<PrimaryMCMachineIP>:<web-port>Where <web-port> is the port number configured during theDX NetOps Mediation ManagerInstallation and <PrimaryMCMachine IP> is the IP address or hostname of the primary MultiController system.
- Enter the login credentials.
- Select the Device Packs tab and click Certification.
- Specify the Certification destination from the Destination drop-down.
- (Optional) Select OverWrite Existing cert check box.
- Do one of the following steps:
- If the Certification to install is in the eHealth Certification repository shipped with the current release ofDX NetOps Mediation Manager, select eHealth Cert.
- If the Certification to install is in the local system, click Browse and locate the Certification.
- Select the Certification and select Deploy.
Deploy the Certification Manually
Deploy the eHealth Certification manually.
Follow these steps:
- Verify that you meet the following prerequisites:
- The LocalController is installed on the CA eHealth server using the same user credentials that are used for installing eHealth.
- The PRESENTER_<devicepack> component is installed on the LocalController that is running on the CA eHealth server.
- $NH_HOME is set to the eHealth installation directory. To confirm, execute the following command:echo $NH_HOME
- Copy the $CAMM_HOME/MC/eHealthCerts/CERT_<devicepack>.zip file to the $NH_HOME directory of your eHealth server.
- Open a command prompt, type bash, and execute the following command:unzip CERT_<devicepack>.zip
- Modify the $NH_HOME/modules/<devicepack>/camm.env script to provide the path details to JRE and the CAMM installation folder.
- Create a soft link from $CAMM_HOME/output/PRESENTER_<devicepack> to $NH_HOME/modules/<devicepack>/ddiData.
- Append the content of the $NH_HOME/db/data/variable.usr_<devicepack> file to $NH_HOME/db/data/variable.usr.
- Before you combine the content, verify if there are any duplicate variables in both files. If you find duplicate variables, remove the duplicate variables and save the final $NH_HOME/db/data/variable.usr file.
- Consider the final variables in the variable.usr file and map the variables.
- Verify the mapping of the variable IDs in the variable.usr file and the elementTypeVariable.usr file.
- Make sure that the variable IDs mapped in the elementTypeVariable.usr file are located in the variable.usr file.
- Append the content of the $NH_HOME/db/data/elementTypeVariable.usr_<devicepack> file to $NH_HOME/db/data/elementTypeVariable.usr.
Import the Elements
Manually import the elements to CA eHealth.
Follow these steps:
- Stop the CA eHealth server with the following command:nhServer stop
- Convert the database schema for a software upgrade using the following command:nhConvertDbWait until the database conversion executes successfully.
- Start the eHealth server with the following command:nhServer start
- Modify $NH_HOME/modules/<devicepack>/modules.defaults.init to suit your specific poll requirements.
- Go to $NH_HOME/modules/camm<devicepackname> directory and execute the following command to discover your new elements:./cammpoll - c - j -leHealth automatically calls cammpoll to poll the elements.cammpoll is successful when you see the elements in eHealth OneClick in Manage Resources, Groups, <devicepack>.
You only execute cammpoll manually once. Take note of any situation afterward in which you execute the cammpoll command manually, because it represents an error condition. In normal operations, eHealth executes the cammpoll command automatically.