AAI 26.0: Usage Guide for the aai.sh Script
search cancel

AAI 26.0: Usage Guide for the aai.sh Script

book

Article ID: 457020

calendar_today

Updated On:

Products

Automation Analytics & Intelligence

Issue/Introduction

In AAI 26.0, the previous jaws.sh script has been replaced by a new aai.sh script. This script provides enhanced capabilities to manage the application server as well as individual microservices introduced in this version. jaws.sh can still be used as it has a symbolic link to aai.sh.

 

This document has a comprehensive list of usage examples fro AAI 26.0 and later

Environment

  • Product: Automic Automation Intelligence (AAI)
  • Version: 26.0 and later

Resolution

Version 26.0 adds several new supporting services alongside the main application server: a Webswing viewer, a front-end gateway, a search/AI indexing service, and two AI-related services. The startup script was updated to manage all of these together instead of only starting the application server.

Starting or stopping everything at once

  • startbg: starts every AAI service in the background. This also runs automatically if you call the script with no option at all.
  • startfg: same as above, but keeps the application server running in the foreground, which is useful if you're watching startup output directly.
  • stopall: sends a shutdown request to everything and returns immediately, without waiting for services to finish stopping.
  • stopsyncall: waits for a clean shutdown of everything before returning, and force-stops anything that doesn't shut down in time.
  • killall: force-stops everything immediately. Use only if a normal stop isn't working.
  • statusall: reports whether the application server and every supporting service are currently running.
  • restartall: stops everything cleanly, then starts it all back up.

Starting or stopping just the main application server

If you want to manage the application server on its own, for example when the supporting services are started separately as part of an automated deployment, these options skip the supporting services entirely:

  • startjbossfg: starts only the application server, in the foreground.
  • stop, stopsync, kill: stop only the application server. These are fire-and-forget, wait-for-clean-shutdown, and force-stop, respectively.
  • status: reports whether just the application server is running.
  • restart: stops and restarts only the application server.

Controlling one supporting service at a time

You can also start, stop, check, or restart a single supporting service by name. The six supporting services in 26.0 are Webswing, FrontendGateway, MCP, Denormalizer, AutomationAI, and AIInsights. Each one accepts the same four operations, for example:

aai.sh Webswing start
aai.sh FrontendGateway start
aai.sh MCP start
aai.sh Denormalizer start
aai.sh AutomationAI start
aai.sh AIInsights start

Swap start for stop, status, or restart to run that operation against any of the six, for example:

aai.sh Webswing status
aai.sh FrontendGateway status
aai.sh MCP status
aai.sh Denormalizer status
aai.sh AutomationAI status
aai.sh AIInsights status

To see the full list of supporting service names available on your system at any time, run:

aai.sh listExternalServices

Checking status of everything in one command

Rather than checking each service one at a time, statusall reports the status of the application server and all six supporting services together:

aai.sh statusall

Getting help

Running aai.sh help (or aai.sh -h) prints the full list of options at any time, so it's always available as a quick reference on the server itself.

Powered by Wolken Software