Cantara Agent

Overview

The Cantara Agent is an optional component installed within your network environment. It provides secure connectivity between Cantara and your JD Edwards (JDE) environment.

In the Cantara Administration Console, agents are configured from the Cantara Agent tab as agent pools. An agent pool defines the endpoint URL, API key, and signing key used by Cantara Cloud to communicate with one or more installed Cantara Agent services.

Use the topics in this section to configure an agent pool in the console, prepare and install the agent on the host server, and verify connectivity.

Key points

• Agent pools can be shared: An agent pool is not limited to a single namespace. One agent pool can be assigned to multiple namespaces.

• Region must match: The agent pool must be in the same region as the namespaces that use it.

• One URL can represent one or more agents: The agent URL can point directly to a single installed agent or to multiple agents behind a load balancer.

• Status checks validate the endpoint: When agents are behind a load balancer, the status reflects whichever agent responds to the request. It confirms the endpoint is reachable, rather than reporting the status of every individual agent.

• Signing keys establish trust: The agent signing key generates the public key installed on the agent host. Regenerating the signing key changes the public key and breaks communication until the new public key is copied to the agent host.

• Agent notices support diagnostics: Agents phone home to Cantara Cloud every 15 minutes by default. Notices can be used to change the agent log level or request log files from agents in the pool. Only one active notice can exist at a time.

Deployment workflow

Deploying a Cantara Agent involves both console configuration and host server installation:

1. Configure the agent pool in the Cantara Administration Console. Add the agent, select the region, configure the agent URL, and obtain the API key and public signing key.

2. Install the Cantara Agent on the host server. Prepare the server, run the installation script, and provide the values generated from the console.

3. Confirm connectivity. Verify that the agent service is running and that the console can communicate with the configured endpoint.

Explore This Section