Confirm Cantara Agent Installation

Overview

Use this page to confirm that the Cantara Agent installation completed successfully and that the service is ready for validation. This page covers post-installation checks only and does not prescribe a specific network architecture.

Service and script verification

• Script output: Review the final output from the installation script to confirm it finished without errors.

• Service status: If you’ve installed the Cantara Agent as a service verify the Cantara Agent service is running. On Windows, check Windows Services. On Linux, confirm the agent process or service is active. If not a startup and shutdown script will be found in the <Agent Root Directory>/bin folder

• If the service is not running: Review the startup logs contained in <Agent Root Directory>/tomcat/logs and confirm the service account has the required permissions.

Folder structure validation

Confirm the installation script created the standard directory structure.

• /bin: Startup and shutdown scripts, where applicable.

• /etc: Primary configuration files, such as config/application.yml

• /logs: Agent and runtime log files.

• /tomcat: Bundled runtime environment managed by the installation script.

Log-based confirmation

Review the logs to confirm the agent started cleanly.

• Confirm the JVM started successfully.

• Verify the configuration loaded using the namespace details and agent signing key provided during installation.

• Check for connectivity errors to the configured JDE AIS endpoints.

Reachability and cloud visibility

• Endpoint reachability: Confirm the agent external endpoint is reachable through the customer network path, including any firewall, WAF, or load balancer.

• Cantara Cloud: Verify the agent appears as expected in the Cantara Console and is associated with the correct namespace. [Screenshot?]

Health check validation

Health check validation is required for load balancer monitoring.