Run Deployment Automation

This topic describes how to start and stop Deployment Automation services and what permissions you need to run Deployment Automation agents.

Start and stop the server

The installer installs Deployment Automation under the application server and starts the service automatically.

To start or stop the server service:

Windows: Use Administrative Tools > Services to start or stop Common Tomcat.

UNIX/Linux: Follow these steps to run the associated command script:

  1. Navigate to the server_installation/bin directory, for example:

    /opt/MicroFocus/da/common/tomcat/8.5/bin

  2. To start the server, run the following: startup.sh

    To stop the server, run the following: shutdown.sh

Back to top

Start and stop an agent relay

If you install the agent relay as a service, the agent relay installer installs the agent relay service but does not start the service. By default, it is set to manual start.

To start or stop an agent relay service on your agent relay machine:

Note: If you are using an agent relay, you must start it before starting any agents that will communicate through it.

Windows: Use Administrative Tools > Services to start or stop the agent relay of the name you gave it during the installation. The default name is agentrelay.

UNIX/Linux: Follow these steps to run the associated command script:

  1. Navigate to the agent_relay_installation/bin directory, for example:

    /opt/MicroFocus/agentrelay/bin

  2. To start the agent relay in a new shell, run the following: agentrelay start

    To stop the agent relay, run the following: agentrelay stop

Back to top

Start and stop an agent

The agent installer installs the agent service, but does not start the service. By default, it is set to manual start.

Note: If you are using an agent relay, you must start it before starting any agents that will communicate through it.

To start or stop an agent service:

Windows: Use Administrative Tools > Services to start or stop the agent, DA-Agent.

UNIX/Linux: Follow these steps to run the associated command script:

  1. Navigate to the agent_installation/bin directory, for example:

    /opt/microfocus/Deployment Automation Agent/core/bin

  2. To start or stop the agent, run the following: agent {start|stop}

    Note: For information on configuring agents to start automatically under a dedicated account, see the Community website.

After you have started the agent, in the Deployment Automation user interface, navigate to Management > Resources and select the Agents tab. The agent is listed with a Connected status.

Back to top

Permissions for users running agents

Each agent needs the appropriate permission to communicate with the Deployment Automation server.

For production environments, create a user account dedicated to running the agent on the machine where the agent is installed.

For simple evaluations, the administrative user can run the agent on the server machine.

As a user running the agent, you need the following permissions at a minimum:

Permission Description
Create a cache By default, the cache is located in the home directory of the user running the agent. You can move or disable the cache.
Open a TCP connection The agent uses a TCP connection to communicate with the server's JMS port.
Open a HTTP(S) connection The agent must be able to connect to the Deployment Automation user interface to download artifacts from CodeStation.
Access the file system Many agents need read/write permission to items on the file system.

Back to top

Log in to Deployment Automation

After you have completed at minimum a server installation, login to the user interface to start configuring Deployment Automation.

To access the Deployment Automation user interface:

  1. In your web browser, enter the following URL:

    http://<serverName>:<port>/da/

    Use the host name and port for the application server where you installed Deployment Automation. The default port is 8080 for Common Tomcat.

  2. Log in to the server using the credentials (Username and Password) you set up during the server installation.

Back to top

See also: