Anyone know of a way to get the plugin list without using cybAgent -v?

[Legacy User]

Does anyone know if there's a way to get the list of plugins installed on the agent without having to run cybAgent -v on every machine?

 

I haven't looked at the Webservice reference guide yet, since I am pretty sure there isn't a service that exposes this functionality, and I know that the SDK doesn't give this information either...

 

just trying to look for a programmable way to get the list of plugins that are installed on each agent in the environment....any thoughts would be appreciated.

 

Thanks,

Deekshit

[Kishore Kumar Udathaneni]

Run the command 'autorep -M <agent_machine_name> -p' from the Autosys command line. It will list out all the plugins installed.

 

Thank You!

Kishore Kumar Udathaneni

CA Technologies

[Legacy User]

What I really need is a single point from where I can query the DB or a Webservice or use the SDK instead of having to login to each machine and run an autorep or a cybAgent -v or look at the agentparm.txt

 

I should have pointed it out in the initial post...sorry about that...

[Legacy User]

I think I can use the autorep approach...but a more programmatic approach like exposing this information through the Java/C++ SDK would be beneficial

[Steve Carrobis]

logging in huh? no no no. you do an autorep -M machine -p

have you tried ALL ?

;-)

as long as the agent is up you can do it from anymachine that has the client as long as the ID allows you to inspect the machine ;-)

eEM and all.

[Legacy User]

Yes I know we can use autorep –M ALL –p…

It still means I’ll need to call the autosys command and parse the output from my Java code, which does a lot of other checks and this is a smaller piece of the puzzle.

 

I am looking more towards the WebService/SDK option where I just write the code and the App Server takes care of getting the information I ask of it, much like autorep, but with the advantage that I don’t have to parse fields and grab columns.

 

Deekshit Addepalli | Senior Consultant | RMT

(651)-600-9490 – Cell | [phone] – Office | [phone] – Fax

[e-mail]<mailto:[e-mail]> | Robert Mark Tech<http://www.robertmarktech.com/>

Visit RMT’s partner, Arbiter Software, for Lifecycle Management with AutoSys: Arbiter Software<http://arbitersoftware.com/>

 

Follow Robert Mark on LinkedIn: RMT on LinkedIn<http://www.linkedin.com/company/robert-mark-technologies/>

 

"Like" us on Facebook: RMT on Facebook<http://www.facebook.com/pages/Robert-Mark/149566531779416>

[Steve Carrobis]

and one day it will give the version of teh agent :-)

as i had requested back in 11.3

[Steve Carrobis]

Java for parsing?! why? perl does so much better and i have had no such issues doing similar ;-)

Also remember you want eEM to handle what you do. not everyone uses the SDK etc and you need to think about who can maintain the code when you leave etc. .. just my 3 cents..

Good luck.

[Legacy User]

Yes, this is actually a requirement from their side and the SDK is pretty easy to use. It goes through the app server and I don’t have to make a separate EEM call to figure out permissions. I just pass in the username and password to the jar file and the app server does everything for me. I just need to ask for what I want

[Steve Carrobis]

hmm the point of using autorep 0is that you wont need id and password to make the call and be found in plain text etc.

But hey .. if they want it so be it.

i would explain to them.. but its your gig..

good luck

[Legacy User]

The username and password is optional. By default, it will take the logged in user, just as the command prompt does. And just as the command prompt allows you to provide the username and password with the –usr and –pw (or –pwx for encrypted password), the util will do the same.

[Steve Carrobis]

good to hear