Administration Guide › Subscription › About On-Demand Updates › How On-Demand Updates Work

How On-Demand Updates Work

Unlike scheduled subscription update cycles that update all proxies and clients, Update Now affects only the selected host. Processing starts when you click the Update Now button as long as the scheduled update is not in progress. If a scheduled update is in progress, clicking Update Now has no effect. If the start time for a scheduled update occurs while update now processing is in progress, the scheduled process does not run. When the on-demand processing completes, the scheduled update cycle resumes.

If you change configured values, be sure to wait for the update interval (300 seconds by default) to elapse before running an on-demand update. CA Enterprise Log Manager generates a self-monitoring event after the update completes.

Important! If the modules to download contain Reports or Integrations, which are content updates, you must update the content proxy before performing any other on-demand update.

The tasks performed by an on-demand update depend on the subscription role of the selected server. Consider the differences in results for the following distinct subscription roles a server can have.

• If the selected server is a subscription proxy for content updates (online), it does the following:
  • Retrieves the latest updates for the selected modules to download from the CA Subscription server and loads them into its download path.
  • Searches for new content and configuration updates in its download path, and if found, pushes these updates to the content repository or remote CA EEM.
  • Searches for new binary updates in its download path, and self-installs them on its client.
• If the selected server is a subscription proxy for content updates (offline), it does the following:
  • Searches for new content and configuration updates in its download path, and if found, pushes these updates to the content repository or the remote CA EEM.
  • Searches for new binary updates in its download path, and self-installs them on its client.
• If the selected server is not a subscription proxy for content updates, but is its own online proxy for clients, it does the following:
  • Retrieves the latest updates for the selected modules to download from the CA Subscription server and loads them into its download path.
  • Searches for new binary updates in its download path, and self-installs them on its client.
• If the selected server is a client only with an online proxy, it does the following:
  • Contacts one of its online proxy servers and download the available updates.
  • Searches for new binary updates in its download path and, if found, self-installs them.
• If the selected server is an offline proxy, it does the following:
  • Searches for new binary updates in its download path and, if found, self-installs them on its client.
• If the selected server is a client only with an offline proxy, it does the following:
  • Contacts its offline proxy server and downloads the available updates.
  • Searches for new binary updates in its download path and, if found, self-installs them.