Implementation Overview for the Google Cloud Run Agent

There are different components required to integrate your Automation Engine and Google Cloud Run so that you can trigger and monitor Cloud Run jobs from your Automic Automation system.

As a system administrator, you carry out the steps required to integrate Automic Automation and Cloud Run.

These are the steps you have to follow for the integration:

Download the Google Cloud Run Agent Installation Package

You can download the relevant Agent installation package from our download center at https://docs.automic.com/documentation or our marketplace at https://marketplace.automic.com/.

For more information, see Downloads and Marketplace.

Install the Google Cloud Run Agent

After downloading the relevant installation package, you have to install the Agent so that you can establish communication between the two systems.

Important!

Before installing the Agent, check the version compatibility information in the compatibility matrix. For information about how to use the compatibility matrix, see the Compatibility Information.

You can install the Agent manually or in a container. The containerized Agent installation refers to building and running a Docker image hosting Java Agents in a container.

Regardless of how you install the Agents, you can use them in on-premises Automic Automation systems as well as in an Automic Automation Kubernetes Edition system.

For more information, see the Automic Automation documentation:

Installing Containerized Java Agents in the Automic Automation documentation
Agents (HOST) in the Automic Automation documentation

For more information on how to install the Google Cloud Run agent, see Installing the Agent for Google Cloud Run

Define the Google Cloud Run Agent

Once you have installed the Agent, you have to configure its INI file to cover your system's requirements, for example, the connection between the Agent and the Automation Engine instance. Then, you define the Agent object in AWI. There are definition pages that are common to all Agents and some that are Agent-specific.

The Agent definition allows you to configure the communication between the Automation Engine and the Google Cloud Run application, on which your clusters live. The Agent starts the execution of these jobs and makes both their monitoring and the corresponding reporting possible.

For more information, see Defining the Google Cloud Run Agent.

Establish the Connection from the Automation Engine to the Google Cloud Run Agent

Now you must ensure that the login data required to establish the connection to the Google Cloud Run application is available; otherwise, you cannot run your clusters on the Cloud Run application from the Automic Web Interface.

To do so, you have to create and define Google Cloud Run Connection objects.

For more information, see Establishing the Connection to Google Cloud Run .

Define the Google Cloud Run Jobs

Now that the Agent is installed and defined, and both systems can communicate with each other, you have to create and define Cloud Run jobs so that you can execute the relevant processing steps in your Google Cloud Run application.

Once the jobs are defined, you can execute them and monitor their progress from the Automic Web Interface.

For more information, see Defining Google Cloud Run Job Properties.