Feature released in SummitAI Asset Management 

What's New?

Earlier, while synchronizing the Patch schema from the SummitAI cloud, the Patch schema job was downloading the schema from the SummitAI could which fetched the information from the Patch database directly. The patch synchronization process was a time-consuming activity, and sometimes due to the network bandwidth limitations, the syncing was becoming unsuccessful too. Due to this, the patches could not be deployed immediately as the customer has to wait until all the patches are downloaded and synchronized.

To avoid this issue, the SummitAI Patch Cloud Server is optimized.

Now, the Patch schema job downloads the Patch schema information from the SummitAI Patch Cloud repository to respective customer’s instance consistently (See Step1, Figure 1), so that all the customer instances are up to date by consuming minimal time. Instead of directly downloading the schema from the Patch cloud database, it downloads the data from the extracted and compressed file. The cloud patch server extracts the data on schedule basis, compress it, and stores it in flat file so that every customer instance can download from the extracted file.

Similar flat file will be available in the Customer’s local environment once patch schema job is completed. This will enable the Administrator to perform the patch deployment into its multiple instances without hitting the SummitAI cloud Patch Repository. (See Step2, Figure 1).

Figure: Patch Schema Sync Architecture

As part of this optimization, now there are two options to download the patches:

• Option 1: Download Patches from SummitAI cloud server
  Specify the “app:ProcessOfflineFiles” to False in the Patch schema job exe config file. This option can be used by the customers for main instance to synchronize the Patch details from the cloud.

• Option 2: Download Patches from customer parent instance to child instance
  The customers who have multiple instances of patching server, can download the schema details from the main Patch instance instead of downloading from to the SummitAI cloud.
  
  Below settings are required to be made in the child patch job server config file:
  
  
  • Specify the path of the parent patch downloaded schema folder, which was downloaded from SummitAI cloud in the below key. So that another child patch job server can process from the offline data. For example:
    <add key="CentralizedProxyUrl" value="\\PARENTPATCHSERVER\Patch_Schema_ZipData_Live_Master\"/>
  • Specify the “app:ProcessOfflineFiles” key to True in the child proxy.
    <add key="app:ProcessOfflineFiles" value="True"/>
    
    
    

For more information, see Patch Management.