Component Duplication Scenario

To explain component duplication for the server, refer to the following scenario:

1. The Apex One server compares its current full pattern version with the latest version on the ActiveUpdate server. If the difference between the two versions is 14 or less, the server only downloads the incremental pattern that accounts for the difference between the two versions.

   Note:

   If the difference is more than 14, the server automatically downloads the full version of the pattern file and 14 incremental patterns.

   To illustrate based on the example:

   • The difference between versions 171 and 175 is 2. In other words, the server does not have versions 173 and 175.

   • The server downloads incremental pattern 171.175. This incremental pattern accounts for the difference between versions 171 and 175.

2. The server merges the incremental pattern with its current full pattern to generate the latest full pattern.

   To illustrate based on the example:

   • On the server, Apex One merges version 171 with incremental pattern 171.175 to generate version 175.

   • The server has 1 incremental pattern (171.175) and the latest full pattern (version 175).

3. The server generates incremental patterns based on the other full patterns available on the server. If the server does not generate these incremental patterns, agents that missed downloading earlier incremental patterns automatically download the full pattern file, which will consequently generate more network traffic.

   To illustrate based on the example:

   • Because the server has pattern versions 169, 167, 165, 163, 161, 159, it can generate the following incremental patterns:

     169.175, 167.175, 165.175, 163.175, 161.175, 159.175

   • The server does not need to use version 171 because it already has the incremental pattern 171.175.

   • The server now has 7 incremental patterns:

     171.175, 169.175, 167.175, 165.175, 163.175, 161.175, 159.175

   • The server keeps the last 7 full pattern versions (versions 175, 171, 169, 167, 165, 163, 161). It removes any older version (version 159).

4. The server compares its current incremental patterns with the incremental patterns available on the ActiveUpdate server. The server downloads the incremental patterns it does not have.

   To illustrate based on the example:

   • The ActiveUpdate server has 14 incremental patterns:

     173.175, 171.175, 169.175, 167.175, 165.175, 163.175, 161.175, 159.175, 157.175, 155.175, 153.175, 151.175, 149.175, 147.175

   • The Apex One server has 7 incremental patterns:

     171.175, 169.175, 167.175, 165.175, 163.175, 161.175, 159.175

   • The Apex One server downloads an additional 7 incremental patterns:

     173.175, 157.175, 155.175, 153.175, 151.175, 149.175, 147.175

   • The server now has all the incremental patterns available on the ActiveUpdate server.

5. The latest full pattern and the 14 incremental patterns are made available to agents.