Automic Automation V26 Standard Administration - Advanced Processes

This course is Part 2 of 4 in the Automic Automation v26 Standard Administration learning path.

This course covers the Automation Engine (AE) server processes in Automic Automation version 26 (Standard). It explains the five process types: the work process (WP), the communication process (CP), the Java work process (JWP), the Java communication process (JCP), and the REST process. It describes how each type is configured in the UCSRV.ini file, how it binds to ports, and where its logs and traces are stored.

The course details the roles of the primary work process (PWP) and the dialogue work process (DWP). It also covers the server roles assigned to the first four WPs (output, resource calculation, sync, and max parallel executions), and how to assign them with the WP minimum number setting. It covers the JWP roles (authorization, periodic, utilities, and indexing), how to assign them through start options, how to rank them in the JWP roles table, and Broadcom's recommended JWP deployment. It then compares warm and cold starts, and explains why processes should be started and stopped through the Service Manager or AWI and not on the command line.

The demonstration covers the Automation Engine management page in AWI. It shows how to filter and monitor processes, read the WP utilization view, and interpret the busy-time, time difference, CPU, memory, and role columns. It also shows how to enable tracing for a process.

Certification

Upon completion, you will receive:

• A certificate validating the course completion
• The Automic v26 STD Admin Processes Badge

Value: 500 points

By the end of this course, you will be able to:

• Differentiate between the five primary Automation Engine server processes (WP, CP, JWP, JCP, and REST) and their distinct operational roles.
• Distinguish between Warm and Cold starts, understanding the critical database implications of clearing message queue tables.
• Monitor live process health, network ports, and active connections using the Processes and Utilization dashboard in the AWI.
• Evaluate actual system load by analyzing process busy time metrics (B.01, B.10, B.60) rather than standard CPU utilization percentages.
• Assign and prioritize specific backend roles (such as Authentication, Indexing, and Periodic tasks) across available Java Work Processes (JWPs).
• Execute safe process starts, stops, and advanced troubleshooting traces using both the AWI context menus and the Service Manager.