Backwards Compatibility in the Agent Controller

The new technology Agent Controller introduces a new set of interfaces for client, agent, and Agent Controller interaction.  Clients and agents are expected to adopt these new interfaces because new features and performance improvements will be occurring in the new technology Agent Controller.

In order to allow time for the transition to occur for existing tools, backwards compatibility layers were added to the new technology Agent Controller.  The client compatibility layer allows a client to communicate with an Agent Controller and agents as it always has, using the original Execution Framework API.  The client compatibility transport layer processes commands based on the older protocol and translates them to equivalent commands in the new protocol, making requests of the Agent Controller using the new API and bridging any gaps. The agent compatibility transport layer allows an agent to communicate with the the Agent Controller using the old API and respond to requests from a client which is using the old API as well.

Whether or not a compatibility transport layer is active is determined by its presence in serviceconfig.xml.  If present, any communication on the ports assigned to these transport layers is expected to use the command format and semantics defined by the old APIs.  All other transport layers expect that the new API is being used.

The option for enabling security is only present when the backwards compatibility layer is active.  The same is true for accessing the file transfer functionality available through the old API.  A basic file transfer service is available through the new API.

Attivitą correlate
Modello concettuale di raccolta dati
Gestione di Agent Controller
 

Copyright (C) 2006 Intel Corporation.