Automation Analytics & Intelligence (AAI)

View Only

AAI 24.0 and Automic Automation connector.

Mladen Ilisinovic posted Feb 19, 2025 04:52 AM

Hi community,
I managed to install AAI 24.0 HF1, and I use Automic Automation connector 24.

I was doing testing of the system and installed AAI 24 HF1 on Windows 10 workstation machine , using remote MSSQL 2019.
AAI gui was loaded and works fine.
Also I installed on same machine conector for automic, and set up scheduler using this connector to my test environment..

this scheduler is showing that it is Status behind, no events, no last events, Job definition updated shows datetime as it runs, I have 10 jobs and 1 deleted.

I added jobstreams for some JOBS, JOBP objects.
Problem is that I do not see any detals about them , no Last start time or End time. no runs.
Maybee someone can pinpoint where to seek solution.

Also I have Dashboard that state following error in view:
Unexpected token '<', "<html><hea"... is not valid JSON

Is this related?

b.r.

Mladen

Broadcom Employee John Hiett posted Feb 19, 2025 06:34 AM

Hi Mladen,

What you describe sounds like the Automic job definitions have been successfully retrieved and that you can see entries in the Active Jobs and Deleted Jobs columns, nothing in the Events As Of and Last Event columns and you see 'Behind' in the Status column.

It sounds like you have already addressed the required EXECUTION_TRIGGER parameter within Automic's UC_SYSTEM_SETTINGS.

Does the account being used to connect to Automic (the account specified in the scheduler definition's Automic REST API User field) have the correct privileges within Automic - Read (R) and Executions (S) as well as Access to Administration and Access to deactivated tasks?

Below are some links to AAI documentation that will help you to ensure that you are configured correctly.
Setting Up the Automic Connector
Administer Automic Automation Schedulers in AAI

If you are still having an issue after checking this information then perhaps you will find messages within the Connector log file that will help. Please feel free to raise a Support case so that our engineers can assist you.

Many thanks and kind regards,
Jon

Mladen Ilisinovic posted Feb 20, 2025 08:07 AM

I tried to reply last night to "NO reply"
so here we go again :)

Instead of retyping I am attaching PDF with my reply e-mail as answer.
Mail response with Pictures

Hi John,

Today it was really looooooong day , but as we know, while incident is fresh it can be fixed 😊

So its almost midnight 😊

Hopefully Support site improved and I can forward pictures over direct mail answer:

This is my current status in Schedulers section.

This is list aof my test jobs:

You said:
It sounds like you have already addressed the required EXECUTION_TRIGGER parameter within Automic's UC_SYSTEM_SETTINGS.

Since I forget quickly, I had to jump to my Automic LAB to see this , because in current state while writing I can't remember what I eat this morning 😊

and it seems under user 0 of Automic Automation under DIV_VARIABLES in UC_SYSTEMSETTINGS variable I had EXECUTION_TRIGGER under Value1 set to N, which I „repaired“ to Y

You said:
Does the account being used to connect to Automic (the account specified in the scheduler definition's Automic REST API User field) have the correct privileges within Automic - Read (R) and Executions (S) as well as Access to Administration and Access to deactivated tasks?

Account created just for this purpose is called REST_USER and it is total admin. Hopefully I made it this way to be sure it works 😊

Regardind documentation, Now when I see this part:
Important !

For performance reasons, it is recommended to install the Automic Connector near the Automation Engine, not near AAI.
Make sure that the EXECUTION_TRIGGER parameter of the UC_SYSTEM_SETTINGS variable in Automic Automation is set to Y[es]. Otherwise, Automic Automation cannot establish the connection to the Automic Connector. For more information, please refer to the Automic Automation documentation at https://docs.automic.com/.

I installed connector next to AAI since it is just POC, and ignored second row ☹ just because I could not find it from 1st attempt ….

So You pinponted to this steps, and now it is 0:19 ( I am slow) and I changed EXECUTION_TRIGGER TO Y, restarted AE, restarted AAI, Automic connector and I present to You following results:

new thing is : green ON TIME marking status.

Jammer on Time also finally green.

Overview still have same parsing error.

Jobs still have no details about start end times, and reoccurences.

So I think I might start some job manually, to see if this triger works. Since there is no retroactive variable ?

after some time:

Seems we have some progress….. it's only 0:41 😊

So this was kind of interactive trooubleshooter. But I still have in

0:51 its time to settle down and go to sleep 😊

Jobs are appearing as I start them.

I would like to have all past jobs data available in my list , so My future POC would make sense ..

Thank You John.

I will continue this troubleshooter tomorow. And hopefully try linux AAI server with connector.

b.r.
Mladen

Mladen Ilisinovic posted Feb 25, 2025 03:00 AM

Hi,

Just update.
I made installation on Rocky linux 9.3 and connected it to remote MSSQL 2019 database engine with new database, and I can confirm, that I now have valid dasboard and no errors so far.

It took some time to troubleshoot it.
I will make fresh reinstallon Microsoft Windows Server 2019 and with MSSQL 2019 and see will be there same error as on old instance.

b.r.
Mladen