With Multi-Config you have the ability to control the pulls through a configuration , meaning that the pulls are no longer completed automatically by the Device Services.

When you select to pull a configuration you have the option to pull the entire configuration set, or to pull individual files and configurations.

Pull Configurations Options

You have the following Pull options: 

  • Pull after an Auto Discovery

  • Pull after a Push

  • Pull after an OS Upgrade

  • Pull after a Credentials Update

What happens during this operation?

  • After your pull option is selected, the Application Server sends a Pull Configuration Command to the Device Services indicating if it is a complete pull, or a subset, with relevant parameters such as TARGETS/CONFIG CATEGORIES, etc.  

  • The Device Services Communications Manager transforms this command into a set of calls into the relevant driver by referencing the META DATA XML, which describes TASK->OPERATION mapping. 

  • The Driver returns a configuration unit, per driver call. 

  • The Communications Manager compares each configuration unit with its cached copy, and creates a complete set of changed configuration units and in the new XML interchange format to be sent to the application. 

  • The Communications Manager sends additional messages, such as NEW_REVISION, COMMUNICATION_ATTEMPTED, SYNC_STATE change etc.

Push Configuration

When you select a push configuration you also have the option of pushing the entire configuration set, or individual files or configuration units, or even configlets.

What happens during this operation?

  • The Application Server sends a Push configuration command to the Device Services, indicating if it is complete push, or a subset with relevant parameters, such as TARGETS / CONFIG  CATEGORIES, etc. 

  • The Device Services Communications Manager transforms this command into a set of calls into the relevant driver by referencing the META DATA XML, which describes TASK->OPERATION mapping. 

  • The operation defines the push routine input parameters. 

  • The driver returns a success or failure, per driver call, into a pushConfig or pushFile. 

  • The Communications Manager refers to Meta DATA XML to find out its operation set, describing the next steps based on META DATA XML

Example of META DATA Info:

  • Does each push failure result in complete failure?

  • Does the push have to be a best effort?  

  • Does it need to pull the entire config after a successful / failed push?

  • The Communications Manager sends additional messages, such as PUSH _SUCCESS, NEW_REVISION , COMMUNICATION_ATTEMPTED, SYNC_STATE change, etc.