Preinstall an HTTPS agent

You can preinstall the HTTPS agent software on a system without configuring or starting the agent. You then can start the agent at a later date, using either the default configuration or a custom configuration.

To preinstall an HTTPS agent

1. Log in to the node as a user with administrative rights.
2. Optional. Check that the node meets all prerequisites for the agent.
   1. For up-to-date information on supported agent platforms, see the support matrix at HP Software Support Online.
   2. Copy the files for prerequisite checking into a temporary folder on the node. The files are available on the management server in the following folders:
      • For nodes with a Windows operating system, copy all the files from the folder:
        %OvShareDir%Packages\HTTPS\PrerequisiteCheck\Windows
      • For nodes with a UNIX or Linux operating system, copy all the files from the folder:
        %OvShareDir%Packages\HTTPS\PrerequisiteCheck\Unix

   1. Open a command prompt on the node and navigate to the temporary folder that you copied the files into. The folder contains ovoreqcheckagt, which you use to start the prerequisite checks.

      • On Windows operating systems type the following command:
        ovoreqcheckagt -sum -agt_comm_type HTTPS -agt_bin_format <agent_binary_format>
      • On UNIX and Linux operating systems type the following commands:
        chmod +x ovoreqcheckagt
./ovoreqcheckagt -sum -agt_comm_type HTTPS -agt_bin_format <agent_binary_format>

      Replace <agent_binary_format> with one of the following values:

      • Alpha
      • IPF32
      • PA-RISC
      • PowerPC
      • SPARC
      • x64
      • x86

      After you start the command, details of any failed requirements and recommendations appear.

3. Copy the HTTPS agent installation packages into a temporary directory on the node. The agent packages are available on the management server. Different packages are available to support different platforms. You can obtain the correct package using the command ovpmutil on the management server.

   If the node already exists on the management server, and the node's system properties are correct, use the following parameters:

   ovpmutil dnl pkg Operations-agent [<package version>] [/d <target directory>] /pnn <primary node name>

   Otherwise, you must specify the system properties on the command line, using the following parameters:

   ovpmutil dnl pkg Operations-agent [<package version>] [/d <target directory>] /ost <OS type> /osv <OS version> /abf <agent binary format>

   The package version and target directory parameters are optional:

   <package version>

   Specify the version of the agent package that you want to download.

   /d <target directory>

   Specify the directory to which you want to download the agent package. If you omit this parameter, the command downloads the packages to the current directory.

   For example:
   ovpmutil dnl pkg Operations-agent /pnn node1.example.com
ovpmutil dnl pkg Operations-agent 8.50.10 /d c:\temp /ost Solaris /osv 9 /abf SPARC

   TIP:
   To check which agent packages are available, and find values for the package version, OS type, OS version, and agent binary format parameters, view the deployment packages report. In the console tree, right-click Deployment packages, and then click ViewPackage details.

4. Open a command prompt and navigate to the temporary directory that contains the installation packages. The directory contains opc_inst, which you use to start the installation as follows:

   • On Windows operating systems type cscript opc_inst.vbs -no_start and then press Enter.
   • On UNIX and Linux operating systems:
     1. Add permission to execute opc_inst (for example, using the command chmod u+x opc_inst).
     2. Type ./opc_inst -no_start and then press Enter.

To start a preinstalled HTTPS agent with the default configuration

Open a command prompt on the node and navigate to the directory %OvInstallDir%bin\OpC\install. The directory contains opcactivate, which you use to start the agent as follows:

• On Windows operating systems:
  cscript opcactivate.vbs -srv <management_server_host_name> -cert_srv <certificate_server_host_name>
• On UNIX and Linux operating systems:
  ./opcactivate -srv <management_server_host_name> -cert_srv <certificate_server_host_name>

This starts the agent and sends a certificate request to the certificate server that you specify. If it does not already exist, you must create the node in the console and ensure that the node receives a certificate.

To start a preinstalled HTTPS agent with a custom configuration

1. Create the profile on the management server and copy it to the node.
   1. Open a command prompt on the management server and use the following command to generate an agent profile for the node:

      ovpmutil dnl prf [/d <target directory>] [/fqdn <fully qualified domain name>] | [/ip <ip address>] | [/nodeid <object id>]

      You only need to specify one of the command line options /fqdn, /ip, or /nodeid. The command generates a file with a name in the format <node>.profile, where <node> matches the command line option you choose.

      For example, the following command generates the profile for a node with the host name node100.example.com and saves it in the file c:\temp\node100.example.com.profile

      ovpmutil dnl prf /d c:\temp /fqdn node100.example.com

   2. The profile contains a list of settings for the node. If the file %OvShareDir%conf\PMAD\agent_install_defaults.cfg exists, the profile includes defaults from this file. If necessary, edit the profile with a text editor. You can specify default values for any attributes that you would otherwise set using ovconfchg on the node.

2. Open a command prompt on the node and navigate to the directory <install_dir>\bin\OpC\install. The directory contains opcactivate, which you use to start the agent as follows:

3. • On Windows operating systems:
     cscript opcactivate.vbs -configure <profile_filename>
   • On UNIX and Linux operating systems:
     ./opcactivate -configure <profile_filename>

   This starts the agent with the configuration settings from the profile. You must ensure that the node receives a certificate.

Related Topics:

• Configure managed nodes
• ovoreqcheckagt
• Configuring Certificates