A system administrator must install at least one vRealize Automation EPI agent to manage interaction with HP Server Automation. The agent can be installed anywhere, including the vRealize Automation server or the HP Server Automation server, as long as the agent can communicate with both servers.

About this task

Prerequisites

  • Verify that the HP Server Automation PowerShell Snap-in is installed on the same host as your EPI agent. If the EPI agent is installed before the snap-in, then the agent service must be restarted after the snap-in is installed. See Install the HP Server Automation PowerShell Snap-In.

  • The agent must be installed on Windows Server 2008 SP1, Windows Server 2008 SP2 (32 or 64-bit), Windows Server 2008 R2 system, or Windows 2012 with .NET 4.5.

  • The credentials of the agent must have administrative access to all HP Server Automation hosts with which the agent will interact.

  • Install the IaaS components, including the Manager Service and Website.

  • See Installing vRealize Automation 7.3 for complete information about installing vRealize Automation agents.

  • Log in to the vRealize Automation console as a system administrator.

Procedure

  1. Select Custom Install and Proxy Agent on the Installation Type page.
  2. Accept the root install location or click Change and select an installation path.

    Even in a distributed deployment, you might sometimes install more than one IaaS component on the same Windows server.

    If you install more than one IaaS component, always install them to the same path.

  3. Click Next.
  4. Log in with administrator privileges for the Windows services on the installation machine.

    The service must run on the same installation machine.

  5. Click Next.
  6. Select EPIPowerShell from the Agent type list.
  7. Enter an identifier for this agent in the Agent name text box.

    Maintain a record of the agent name, credentials, endpoint name, and platform instance for each agent. You need this information to configure endpoints and to add hosts in the future.

    Important:

    For high availability, you may add redundant agents and configure them identically. Otherwise, keep agents unique.

    Option

    Description

    Redundant agent

    Install redundant agents on different servers.

    Name and configure redundant agents identically.

    Standalone agent

    Assign a unique name to the agent.

  8. Configure a connection to the IaaS Manager Service host.

    Option

    Description

    With a load balancer

    Enter the fully qualified domain name and port number of the load balancer for the Manager Service component, mgr-svc-load-balancer.mycompany.com:443.

    Do not enter IP addresses.

    Without a load balancer

    Enter the fully qualified domain name and port number of the machine where you installed the Manager Service component, mgr-svc.mycompany.com:443.

    Do not enter IP addresses.

    The default port is 443.

  9. Configure a connection to the IaaS Web server.

    Option

    Description

    With a load balancer

    Enter the fully qualified domain name and port number of the load balancer for the Web server component, web-load-balancer.mycompany.com:443.

    Do not enter IP addresses.

    Without a load balancer

    Enter the fully qualified domain name and port number of the machine where you installed the Web server component, web.mycompany.com:443.

    Do not enter IP addresses.

    The default port is 443.

  10. Click Test to verify connectivity to each host.
  11. Click Opsware in EPI Type.
  12. Type the fully qualified domain name of the managed server in the EPI Server text box.

    Optionally, you can leave this blank to let the agent interact with multiple hosts.

    The HP Server Automation server with which the agent interacts when provisioning a machine by using HP Server Automation depends on the value of the required custom property, EPI.Server.Name, in the blueprint.

    Therefore, if you install a dedicated EPI agent by specifying an HP Server Automation server name during installation, only machines whose EPI.Server.Name property exactly matches the server name configured for the agent can be provisioned by that server.

    If you install a general EPI agent by not specifying an HP Server Automation server name during installation, a machine can be provisioned by any server specified in the blueprint EPI.Server.Name property, that is assuming the agent can contact that server.

    Note:

    If no matching agent can be found, or there are no agents with unspecified server values, Opsware provisioning will wait until a suitable agent is found.

  13. Click Add.
  14. Click Next.
  15. Click Install to begin the installation.

    After several minutes a success message appears.

  16. Click Next.
  17. Click Finish.

What to do next

Determine the type of integration method to use. See Integrating HP Server Automation.