Hello
DanielLahman610562Is your Service Manager running on Windows or Unix / Linux ?
It's true that changes in UC4.smc and UC4.smd will not be taken into account until the ServiceManager service is restarted.
However you may try the following in Windows - it's trickier in Unix/Linux as you need to know the Smgr's process ID to kill it:
Add entries to UC4.smd & UC4.smc in command line
- UC4.smd
echo DEFINE <Agent name>;<Start Command>;<StartPath> >> <path to SMGR\bin>\UC4.smd
example:
echo DEFINE WIN01;C:\Automic\Agents\WIN01\bin\ucxjwx6.exe;C:\Automic\Agents\WIN01\bin\ >> C:\Automic\SMgr\bin\UC4.smd
2. UC4.smc
echo !AIT 0 >> <path to SMGR\bin>\UC4.smc
echo !REATE <Agent Name> >> <path to SMGR\bin>\UC4.smc
example:echo !AIT 0 >> C:\Automic\SMgr\bin\UC4.smc
echo !REATE WIN01 >> C:\Automic\SMgr\bin\UC4.smc
The exclamation marks at the beginning of the lines mean that the instruction will not be taken into account at startup :
- No WAIT between the process is created.
- The process "WIN01" will not start automatically when the SMgr starts.
If you change '!AIT 0' to 'WAIT 30' for instance the SMgr will wait 30 seconds before starting the agent, and if you use 'CREATE WIN01' instead of '!REATE WIN01' the agent will start automatically when the SMgr starts.
Stop and restart the Service Manager
Please note you will need admin rights to do this.
Use net stop <Service Name> then net start <Service Name>
example :
net stop UC4.ServiceManager.AE
net start UC4.ServiceManager.AE
Hope this helps.
Kind regards,
Antoine