CA Client Automation

  • 1.  What is the flow from the first information collected from an agent?

    Posted Sep 30, 2015 12:13 PM

    What is the flow from the first information collected from an agent?

    I mean in the first time that the agent starts, is it send the inventory to Domain directly or to the Scalability? Is there a doc that explain it in detail.



  • 2.  Re: What is the flow from the first information collected from an agent?

    Broadcom Employee
    Posted Sep 30, 2015 12:32 PM

    That depends on what you caf setserveraddress the agent to.

     

    If you point it to a DM it will go to the DM, if you point it to the SS it will talk to the SS, which will talk to the DM.

     

    When you install agents with Deploywrapper locally or Infrastructure Deployment via the DM, you can tell it what machine to point to.

     

    Then depending on what plugins you installed it will either do just the basic hardware scan if AM is not installed

    OR  if AM is installed it will do the basic scan and once it is registered AM will check which Collect Tasks AM scan should Run.

     

    The data is stored on the agent in the UAM\bak folders

    Temporarily stored in the CA\DSM\Serverdb\Sector\Collect\0000001\ on the SS

    and then finally imported in the MDB, by the SS's  Collect Engine



  • 3.  Re: What is the flow from the first information collected from an agent?
    Best Answer

    Posted Sep 30, 2015 12:44 PM

    The Agent does not under normal conditions talk directly to the Domain, only to the Scalability Server. The general flow during FIRST run is:

     

     

    ·         Register all components with SS

     

    o   Run the BASIC inventory scan and deliver to SS

     

    ·         Run a Software Delivery JOBCHECK to check for pending jobs and deliver data regarding DSM Packages installed

     

    ·         Run AMAGENT to collect inventory:

     

    o   AMAgent connects to a component on the SS known as the ‘Sector’ and:

     

    o   Uploads a ‘status’ and ‘execution time’ record to the Scalability Server

     

    o    Requests a list of inventory modules and jobs to run. If set to defaults, this will include:

     

    §  General Inventory module – this will run and collect the initial inventory

     

    §  Software Signature scan – this will run and:

     

    ·         Download the software signatures from the SS

     

    ·         Run the scan

     

    §  Any additional jobs you may have created

     

    o   If there is already a BAK subdirectory AMAgent will run a compare and produce a delta. If there is no ‘BAK’ directory the delta produced will be the complete inventory, software and hardware.

     

    o   Uploads the ‘Delta’ inventory to the Scalability Server

     

    o   Uploads a ‘status’ record to the Scalability server

     

    We should be clear at this point that even if the ‘serveraddress’ of the Agent is set to the Domain Manager, the Agent is still communicating with a Scalability Server component which is running on the Domain Manager, and it operates in exactly the same way.

     

    Steve McCormick, ITIL

    CA Technologies

    Principal Services Consultant

    Tel: +1-731-676-4223

    Stephen.McCormick@ca.com

    <mailto:Stephen.McCormick@ca.com>