WCC 11.4 SP6 with AutoSys 11.3.5

[Legacy User]

We have a situation where we are trying to get WCC on the latest version before the AutoSys upgrade. We will upgrade AutoSys, but wondered if anyone tried configuring WCC 11.4 SP6 with AutOSys 11.3.5

 

We can configure the AutoSys server in Configuration, but it doesn't show up anywhere in WCC. Not in Monitoring, Quick View or Quick Edit.

 

I suspect that the collector is having trouble trying to get the information, and this is one of the cases where forcing the collector to run and if the logs were more meaningful to read, would have made life easier to debug why the server wont show up.

 

are there additional patches that are needed to make this work?

[Legacy User]

Just as I hit Post, we made a change in the Monitoring to change the collector mode from Filter to All, saved it and now we see the server. Interesting that we had to change the collector mode. Anyone have any insight into why this would have worked and why it didn't work when the server was added initially?

[Chandru.Venkataraman]

Hi Deekshit,

 

Please review this post back from  SEP 2015.

 

https://communities.ca.com/docs/DOC-231160229

 

QV, Monitor views, server widget all relies on the collector to perform an initial scoop which doesn't happen on a newly added server because no filters are defined yet.

 

Collector mode 'Filter' has performance implications and not recommended.

 

Thanks & Regards,

Chandru

CA Technologies

[Legacy User]

Hi Chandru,

 

Why does WCC 11.4 SP6 ship with the collector mode set to "filter" by default then? Seems very bad design if the "filter" mode has performance implications and is not recommended and yet CA decides to ship the product with an setting that is not recommended. I do remember that previous version (don't remember how far back) did ship with collector mode "all" and during some debugging calls, we were told "all" is the BAD option.

 

On the flip side, if the collector wont scoop up the server because there are no filters defined, how do I define a filter, when WCC doesn't see the server.

 

Seems like switching to all and filter and praying to the gods is one way...

[Chandru.Venkataraman]

Hi Deekshit,

 

Collector mode: "all" is still the default. Have done a couple fresh installs and it defaults to "all".

Was yours an upgrade or fresh install? Did you import configuration from a pre-11.4 SP6 environment?

 

Regarding performance, the filter option only collects data from servers already part of the Monitoring views. So, there is no way newly configured AE server is going to be part of that group because we won't have any views/filters defined yet.

 

This is what the documentation has to say and I have validated this to be true based on some customer experiences.

 

Optimize Monitoring

You can optimize Monitoring by modifying Monitoring preferences in Configuration.

Follow these steps:

1. Click the Configuration tab, select Monitoring from the View/Modify Preferences drop-down list in the Preferences section, and click Go.
   The Monitoring preferences are displayed.
2. Modify the following fields according to the recommended settings:
   • Collector Mode
     Specifies whether to collect data for all defined servers or only the servers that are part of the active view filters. The recommended setting is all.
     Example: CA Workload Automation AE servers defined in Configuration are: A1, A2, A3, A4, and A5. Only A1 and A2 are defined in active monitoring view filters.
     The effects of the settings are:
     • all -- collect data from servers A1, A2, A3, A4, A5.
     • filter -- collect data only from servers A1, A2.
     Note: Selecting filter instead of all has an adverse effect on performance. Selecting filter enables data collection from servers defined in active Monitoring view filters.

   • Job Collector Run Interval
     Specifies the interval (in seconds) between collector runs and server changes synchronization.

     Note: If the collector service generates a high load on the server, you can increase this value (10 seconds or 15 seconds is sufficient). This situation can occur if CA WCC is attached to many CA Workload Automation AE servers that generate a high load (many updates during a 5-second interval).
3. Click Save.