Creating and distributing configuration files

The push-to-client feature provides tools for system administrators to define remote system connections, define configuration files, and set client workstation preferences from a central location. These connection definitions, configuration files, and preferences can be distributed to individual client workstations automatically when they connect to a remote system. Product updates can also be pushed to client workstations when they connect to a remote system.

Before you begin

To create and distribute remote connection definitions, configuration files, and preferences from a central location, the server must be configured to enable push-to-client updates.

About this task

When a user connects to the primary remote system or to another remote system for which system configuration files are defined, the configuration files that are stored on that system are compared to the configuration files on the workstation. If updates are available, users are prompted to install them.
By using the push-to-client feature, you can distribute the following configuration files:
  • Global configuration files:
    • Database connections
    • Eclipse preferences
    • Remote system connections
    • Menu Manager files
    • Software Analyzer Configurations
    • Snippets
    • Installation configuration
  • System configuration files
    • Remote index locations
    • z/OS® file system mappings
    • Property groups
    • Default values
    • Host-based projects

Procedure

To create and distribute configuration files, do these steps. Each of these steps links to more information about completing the step.

  1. Create a workspace that serves as the model workspace for the configurations and preferences to be distributed.
  2. From the model workspace, create connections to the primary remote system from which you intend to distribute global and system configurations and to each remote system from which you intend to distribute system configurations.
  3. Configure remote system connections, configuration files, and preferences in the model workspace.
  4. Export the configuration files that are to be distributed to other client workspaces.