If you need to manually install an HTTPS agent with a custom configuration, you can create an agent profile. An agent profile contains a list of settings for an agent on a specific node. For example, you can use an agent profile to configure the communication ports and certificate handling for a node.
Open a command prompt 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>]
If you omit the /d
option, the command downloads
the packages to the current directory. You only need to specify one
of the command line options /fqdn
, /ip
,
or /nodeid
. The command generates a file on the
management
server 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 on the management server in the file
c:\temp\node100.example.com.profile
ovpmutil dnl prf /d c:\temp /fqdn
node100.example.com
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.
%OvShareDir%Packages\HTTPS\PrerequisiteCheck\Windows
%OvShareDir%Packages\HTTPS\PrerequisiteCheck\Unix
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.
ovoreqcheckagt -sum -agt_comm_type HTTPS -agt_bin_format
<agent_binary_format>
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.
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 are optional:
<package version>
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.
opc_inst
, which you use to start
the installation as follows:
cscript opc_inst.vbs -configure
<profile_filename>
opc_inst
(for example,
using the command chmod u+x opc_inst
)../opc_inst -configure
<profile_filename>
This installs the agent and starts it with the configuration settings from the profile. You must ensure that the node receives a certificate.
Related Topics: