Home
Installing
A HCL DevOps Deploy (Deploy) installation consists of a Deploy server, a database server, and at least one agent.
Starting DevOps Deploy
Both UNIX™ and Windows™ installations require the HCL DevOps Deploy (Deploy) server and at least one agent. If you are using a database other than Derby, make sure that the appropriate driver is installed and configured.
Accessing DevOps Deploy
You can access the HCL DevOps Deploy (Deploy) server with a Web browser.

Installing
A HCL DevOps Deploy (Deploy) installation consists of a Deploy server, a database server, and at least one agent.
- Firewall and communication configuration
  This topic describes the communication between the HCL DevOps Deploy (Deploy) components, the firewall, and the ports involved in the communication.
- Installing the server database
  HCL DevOps Deploy (Deploy) requires a database. You can use the following database types for an evaluation or production server.
- Installing the DevOps Deploy server
  The server provides services such as the user interface used to configure application deployments, the security service, and the artifact repository, among others. Installing the server involves specifying configuration information for the server, such as the ports that the server uses.
- Installing with Kubernetes
  The HCL DevOps Deploy (Deploy) server can be installed in a cloud-based environment, as a containerized server cluster, managed by Kubernetes. Deploy works with Kubernetes to simplify application deployment and manage versions in the containers.
- Installing agents
  You can install agents from the server or from the command line on the agent system. To configure a failover server for an agent, you must install the agent from the command line.
- Installing agent relays
  An agent relay is a communication proxy for agents that are located behind a firewall or in another network location. You can install agent relays in interactive mode or in silent mode.
- Installing plug-ins
  Plug-ins can be installed at any time. You do not need to restart the server after you install a plug-in.
- Starting DevOps Deploy
  Both UNIX™ and Windows™ installations require the HCL DevOps Deploy (Deploy) server and at least one agent. If you are using a database other than Derby, make sure that the appropriate driver is installed and configured.
  - Starting the DevOps Deploy server
    To run the server, run the batch file or shell script for the server.
  - Starting agents
    To start an agent, run the shell script or batch file.
  - Starting z/OS agents from the z/OS UNIX command line
    The z/OS agent can be started from ISPF as a started task or from the z/OS UNIX command line. To start an agent from ISPF as a started task refer to install/topics/run_agent.html. To start the z/OS agent from the z/OS UNIX command line, follow this procedure.
  - Starting agent relays
    To start an agent relay, run its batch file or shell script.
  - Accessing DevOps Deploy
    You can access the HCL DevOps Deploy (Deploy) server with a Web browser.
- Installing and uninstalling test fixes (patches) from the server
  Test fixes are provided to correct specific issues. They are applied to the server as patches.
- Uninstalling
  Learn how to uninstall the HCL DevOps Deploy (Deploy) server, and agent.

Accessing DevOps Deploy

You can access the HCL DevOps Deploy (Deploy) server with a Web browser.

Before you begin

Pre-requisite

Start the server. See Starting and stopping the server.

Procedure

Procedure

Open a web browser and go to the server host name that you configured during installation.
Login URL: The installation log shows the complete URL for the server. The default URL is https://hostname:port, where hostname host name of the computer on which the server is running and port is the HTTPS port that you used when you installed the server. The default HTTPS port is 8443.

Admin URL: As an administrator, you can access the server using the URL https://hostname:port/admin when password-based login is disabled for user authentication.
Log on to the server.
When you access the server for the first time, the default user name is admin, and password is what you specified when you installed the server. You can change these credentials later by using the Settings tab on the Deploy web application. See Server settings and configuration for a detailed information on the Settings tab. Also, see Authentication realms for information about how you can manage user accounts.
Optional: Check the Keep me logged in box option and the login cookie gets the expiration date one year in the future.

What to do next

If you set the server to use secure connections, your web browser might show a security warning that says that the connection is not secure. This warning appears because the server does not have a trusted certificate. See Configuring SSL on Apache Tomcat and LDAP servers.