Configuring CA Automation Point › Apply Configuration Changes to a Running AP Desktop

Apply Configuration Changes to a Running AP Desktop

When the Automation Point Desktop is started, it is initialized with settings configured by the AP Administrator using Configuration Manager. During the AP Desktop startup, sessions and function windows are opened on the desktop according to configuration settings associated with the session definition set designated as active. While the AP Desktop is running, Configuration Manager can be used to update configuration settings offline. Updated session definition set configuration settings can be applied to a running AP Desktop without:

• Restarting AP Desktop.
• Affecting items that were not modified.
• Interrupting automation for sessions that were not modified.

All other updated configuration settings that are not dynamically loaded by Configuration Manager cannot be applied to the runtime environment until the next time the AP Desktop is started. The process of applying the configuration changes is further referred to as a reload.

The AP Administrator can control how the configuration changes are applied to the AP Desktop runtime environment. Applied configuration changes can be limited to:

• The ADDRESS AXC CONFIG RELOAD command processor.
• Session Definition Sets dialog in Configuration Manager.

The AP Administrator can control the scope of configuration changes that are applied to the AP Desktop runtime environment by reloading all settings for:

• A selected Session Definition Set
• An active Session Definition Set
• All sessions in the active Session Definition Set
• All function windows in the active Session Definition Set
• A selected session in the active Session Definition Set
• A selected function window in the active Session Definition

The AP Administrator can control when configuration changes are applied to the AP Desktop runtime environment:

• On-demand configuration reload due to dynamic system operating requirements can be manually triggered using Configuration Manager.
• Event driven configuration reload can be automatically triggered using rules and REXX programs.
• Scheduled configuration reload due to system maintenance requirements can be automatically triggered using rules and Rexx programs.

Note: To dynamically load one or more configuration updates that add, remove, or rename a session or function window affecting an active AP Desktop, we recommend applying or reloading the configuration update at session definition set level. At this level, rules that correlate with an updated set of sessions and function windows can also be loaded, if necessary. This product can start termination and initialization Rexx programs, which are updated to correlate with a changing AP Desktop, in the correct sequence for a configuration reload.

Note: Sessions and function windows are identified by their name. Before applying configuration changes for a single session or function window, ensure that the session or function window does not conflict with:

• Other existing sessions or function windows.
• Automation that is defined in rules or Rexx scripts.

For example, verify that a duplicate session managing the same console is not currently running or that function window of the same unique type (any except PLOT) does not already exist.

Note: A license check is done before the reload from Configuration Manager. If the number of enabled 3270/5250 sessions exceeds the licensed maximum, a warning message displays. The user can choose to ignore the warning message and continue with the reload process. If the user complies with the license warning, then the reload process is aborted.