Rational Developer for System z

Distributing product and configuration updates

You can configure Rational® Developer for System z® to automatically distribute product updates and updates to configuration files, preference settings, and remote system connections when client workstations connect to a remote system. This feature is called push-to-client. It allows you to store workspace configurations in a central location and push them out to client workstations so that your developers have a consistent workspace environment.

Push-to-client overview

Implementing a push-to-client environment involves several tasks: some performed on the z/OS® system and some on a client workstation. The following is an overview of how to implement a push-to-client environment. It defines some of the terms and resources used in this environment. The details for implementing push-to-client are described in subtopics.

  1. Configure push-to-client on z/OS.

    Each remote system from which you intend to distribute product updates and configurations needs to be set up to support push-to-client.

    1. One z/OS system must be defined as the primary system. The primary system is the controlling system in a push-to-client environment. Only one z/OS system can be defined as primary. The primary system stores global configuration files, which apply to all systems in the push-to-client environment, and system configuration files, which apply only to the primary system itself. The global configurations are product updates, Eclipse preferences, and remote system connections.
    2. Other z/OS systems can be enabled for push-to-client as non-primary systems. Non-primary systems define only system configurations, which apply only to the non-primary system itself. System configurations are property groups, default values, file mappings, and host-based projects.
    The starting point for configuring push-to-client on a z/OS system is a root file called pushtoclient.properties, which is located in the /etc/rdz/ directory on the z/OS system. This file contains entries that specify configuration parameters, such as:
    • Whether the function is enabled for product updates: indicated by setting product.enabled=true.
    • Whether the function is enabled for configuration updates: indicated by setting config.enabled=true.
    • Whether the current system is the primary system, that is, the system that controls the push-to-client feature: indicated by specifying primary.system=true|false.
    • Where to find the main configuration file, keymapping.xml: indicated by setting pushtoclient.folder=/var/rdz/pushtoclient, the default location. The key mapping file contains pointers to a set of files that contain the application-related settings. These pointers are created from a Rational Developer for System z client as part of the configuration file export process, described in step 3, below.

    For information about preparing z/OS systems for push-to-client configuration, refer to the IBM® Rational Developer for System z Host Configuration Guide (SC23-7658).

  2. Configure a master workspace with settings that you want to push out to other workspaces when they connect to the z/OS system.

    After the remote system has been set up, you can begin configuring the Rational Developer for System z settings you want to push out to the rest of the organization. For most settings, such as Eclipse preferences, remote system connections, property groups, and file system mappings, this is accomplished by updating the settings locally on a Rational Developer for System z client. Some settings, such as product updates, host-based projects, and default values, need to be configured manually on the z/OS system.

  3. Export the workspace settings to the z/OS system by using the Rational Developer for System z configuration export wizard.

    The export wizard uploads the local configuration files (Eclipse preferences, remote system connections, property groups, and file system mappings) from the master workspace to the z/OS system. Only users who have authority to write files to the folder containing the key mapping file on the remote system can export settings. After the settings have been exported, users who connect to the z/OS system are prompted to update their workspaces with these settings.

For information about configuring and exporting the Rational Developer for System z settings you want to push out to client workstations, see the remaining topics linked to in the following section.

Creating and distributing updates

Rational Developer for System z can distribute the following types of updates:


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)