Rational Developer for System z

Creating and distributing configuration files

Rational® Developer for System z® 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, Rational Developer for System z must have been configured to enable push-to-client updates. For information about configuring push-to-client updates, refer to "pushtoclient.properties, Host-based client control" in the IBM® Rational Developer for System z Host Configuration Guide (SC23-7658).

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 stored on that system are compared to those on the workstation. If updates are available, users are prompted to install them.
You can distribute the following configuration files:
  • Database connections
  • Eclipse preferences
  • Remote system connections
  • Menu Manager files
  • Installation configuration
  • Software Analyzer Configurations
  • 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 each step.

  1. Create a new workspace that serves as the master workspace for the configurations and preferences to be distributed.
  2. From the master 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 master workspace.
  4. Export the configuration files that are to be distributed to other client workspaces.

Feedback