Push Application Configurations

Anytime you change values in a value set, to merge those changes with the configuration file on the target server you must push the application configuration to the server. For more information, see Push Application Configurations to servers.

To push application configuration changes to a server or group of servers:

1. From the SA Client navigation pane, select the Devices tab.
2. Select either All Managed Servers or Device Groups. Navigate to the desired server or device group.
3. Select a server or device group and select the Actions > Open menu.
   • If you selected a server, select the Management Policies tab.
   • If you selected a device group, skip to the next step.
4. Open the Configured Applications node in the navigation pane and select the application configuration instance you want to push.
   
   You can optionally preview the changes that will be made on an individual server by selecting the Preview button. The comparison screen shows any differences. Select Close when you are finished.
5. When you are ready to apply the changes to the server or servers, select Push.
6. In the Push Configurations screen, verify the Application Configuration and the value set to be pushed.
   To accept the remaining defaults for Scheduling, Notifications and Job Status, click Start Job. Otherwise click Next to continue reviewing the wizard options.
7. In the Scheduling pane, specify when you want the Application Configuration to be pushed. You can use the Scheduling pane to schedule the job to run in the future or to run at regular recurring intervals such as weekly or monthly.
   To accept the remaining defaults for Notifications and Job Status, click Start Job. Otherwise click Next to continue reviewing the wizard options.
8. In the Notifications pane, optionally specify one or more email addresses and a ticket identifier. For each recipient, select the options for when to send an email notification:
   • On Success: sends email to recipient if the job succeeds.
   • On Failure: sends email to recipient if the job fails.
   • On Termination: sends email to recipient if the job is terminated.
     • Termination occurs when you stop an actively running job via the End Job action.

     • This notification does not apply to jobs that are cancelled before they are run.

   To accept the remaining defaults for Job Status, click Start Job. Otherwise click Next to continue reviewing the wizard options.

9. Click Start Job.
   
   After the job has started, you can view its status by selecting the Jobs and Sessions tab then Job Logs on the main SA Client screen.
   
   You can also perform any of the following optional actions:
   • Click Export to export the job status results to a text file.
   • Click End Job to stop the job. See Stopping a push configuration job.
   • Click Close to close the window. To view job status later, click Job Status from the SA Client navigation pane, and then double-click on the job to view details.

Stopping a push configuration job

You can terminate a push configuration job that is actively running. For example, you may need to stop a job that is producing erroneous results or will run beyond an allotted maintenance window.

To maintain job integrity, some steps in the push configuration job flow are non-cancellable. When you stop the job, the Job Status window will indicate which steps completed and which were skipped.

To stop an active application configuration push job:

1. From the Job Status window, click End Job. (This button only appears if the job is in progress.)
2. The End Job warning dialog will be displayed advising you how job termination works:
   • The job will not initiate work on any additional servers
   • If work has started on a server, the job will only skip steps that can be safely cancelled
   • The Job Status will indicate the steps that were completed or skipped
   • If the job terminates successfully, the final job status will be “Terminated”
3. Click OK to confirm that you wish to terminate the job. The Job Status window displays the progress of the termination.
   
   The job status will be Terminated. The server status will be Cancelled. The task statuses will be Succeeded or Skipped.
4. When the termination is complete, you can also view the job in the SA Client Job Log.
   
   From the SA Client navigation pane, click Jobs and Sessions. The Job Logs view appears with your job listed with Terminated status.

Modifying push timeout values

By default, when you push an Application Configuration, the default timeout value is ten minutes, plus one minute for each template inside the Application Configuration. Each template in that Application Configuration appends its timeout to the base timeout for the Application Configuration.

For example, if you have an Application Configuration that contains three templates, the default timeout value for the entire Application Configuration is 13 minutes. If you pushed the template and the entire push took longer than 13 minutes, the push will time out and the operation is cancelled, including any changes that were already made.

To extend a template’s timeout value, you can use the CML timeout tag for individual templates inside the Application Configuration. The CML timeout tag syntax is as follows:

@!timeout=1@

Valid values are 0-999, in minutes.

If the Application Configuration times out in the middle of a push, all changes to the target file of the push are backed out and the operation is cancelled.

For details on the CML timeout tag, see the CML Reference.