Configuring Dedicated IDX AE Server Processes in Service Manager - Automic Automation
Article ID: 445239
Updated On:
Products
Issue/Introduction
Implementing dedicated Index (IDX) processes ensures that specific Automation Engine roles are always available. This guide provides the syntax and best practices for configuring these processes using the Service Manager and addressing common startup challenges.
Environment
- Automic Automation Engine 21.0, 24.X
- Service Manager (Linux/Unix and Windows)
Cause
Issues with IDX processes failing to appear in the Administration perspective are often caused by:
- Attempting to start multiple IDX processes on a single server (not supported).
- Incorrectly formatted
smdorsmcfiles. - Service Manager not being restarted to pick up new configuration changes.
Resolution
Follow these steps to configure one REST and one IDX process per server.
1. Update the Service Manager Definition (SMD) file Add the following entries, ensuring the -role parameter is placed before -svc%port%:
2. Update the Service Manager Commands (SMC) file Ensure there is a delay between process starts to allow the Java Virtual Machine (JVM) to initialize:
3. Restart the Service Manager Changes to .smd and .smc files require a restart of the Service Manager process to take effect:
- Find the PID:
ps -ef | grep ucybsmgr - Terminate the process:
kill -15 #### - Restart:
nohup ./ucybsmgr -i<Path/To/ucybsmgr.ini> > /dev/null 2>&1 &
4. Verify via Command Line Use the ucybsmcl utility to verify or manually toggle the processes: ./ucybsmcl -c START_PROCESS -h localhost:8871 -n UC4 -s "UC4 IDX"
Additional Information
- Only one IDX process is supported per server.
- Additional Helpful Links:
- If you need to speak with a customer representative or a Support Engineer, see .
Feedback
