Previous Topic: How Subscription WorksNext Topic: Subscription Architecture

Implementation Guide › Planning Your Environment › Subscription Update Planning › How to Plan Subscription Updates

How to Plan Subscription Updates

Planning the architecture of subscription updates for your CA User Activity Reporting Module environment lets you ensure that all servers receive the updates you select, in a timely and secure manner.

To plan subscription updates for your CA User Activity Reporting Module environment, complete the following process. For details, see the related procedures.

  1. Begin by designing a proxy-client structure for your CA User Activity Reporting Module servers. Decide which servers to designate as proxies and which to designate as clients, keeping in mind the role of each server, and network traffic considerations.
  2. Consider any Internet access limitations in your environment, and decide whether you need one or more offline proxies.
  3. Consider any Internet security and traffic concerns, and decide whether to include a local HTTP proxy in your subscription architecture. Online subscription proxies can contact the CA Technologies Subscription Server directly, or using your local HTTP proxy.
  4. Consider whether you want to download all updates automatically, according to the subscription schedule you set, or if there are some update types you want to download manually. For example, internal security policies may require that you test certain upgrades before applying them to your environment.
  5. Consider how frequently to update your CA User Activity Reporting Module environment. Updates are available on a regular basis; the frequency depends on the type of update. For details on update types, see About Modules to Download in the More Information section.

    Note: Confirm that you have adequate disk space to download subscription updates to each CA User Activity Reporting Module server, before proceeding with subscription updates. If the available disk space on a server is less than 5 GB, the Subscription Service issues a self-monitoring event and suspends the download process.

More information:

Subscription Architecture

Offline Subscription Architecture

About Modules to Download