Rational Developer for System z

Learning more about push-to-client

Learning more about push-to-client can help you to avoid problems when you use this feature.

Overview of push-to-client

The push-to-client feature of Rational® Developer for System z® enables your site to store product updates, preferences, and configurations in a central location on a remote system and automatically distribute them to client workstations when users connect to that remote system.

Known limitations with push-to-client

You might avoid some typical problems with push-to-client by being aware of and planning for the following limitations:
  • When creating a response file for distributing product updates, include in the response file only the features that are supported on all platforms to which users need to install the updates.

    For more information about feature installation problems, see Feature cannot be installed using push-to-client.

  • When creating a response file for updating Rational Developer for System z by using push-to-client, specifying the minimum information required by Installation Manager to allow the most flexibility across different user configurations.

    For more information about creating response files in Installation Manager, see Response files.

  • When updating the Rational Developer for System z product using push-to-client, a package name is required in the response file. All users whose product installations are to be updated using push-to-client, must have installed Rational Developer for System z under the same package name that is used in the response file.

    For more information about package names, see Package names in response files

  • Before distributing product updates by using push-to-client, ensure that all users have stored their credentials for the server from which the product updates are installed in Installation Manager.

    For more information about storing credentials, see Authentication with the Installation Manager repository.

  • Users who are installing a product update by using push-to-client, must be logged in to the client workstation with the same user authority level that was used to create the response file. If the initial Rational Developer for System z installation was performed with administrator authority, for example, then the user running Rational Developer for System z when the update is initiated must have administrator authority. If the initial installation was performed without administrator authority, then the user running Rational Developer for System z when the update is initiated does not need administrator authority.
  • If an expected product update fails to start, tracing can be helpful in troubleshooting problems in the installconfig.xml file. Trace entries for product updates are included in the workspace/.matadata/.trace file if the following is level is set on the Tracing preferences page, which you can open by clicking Window > Preferences > Tracing:
    • Tracer Name: com.ibm.ftt.resources.core
    • Tracing Level: FINE or higher
  • If a user's push-to-client update is unsuccessful, look in the following location for the update log that contains information on the reason for the failure: workspace/.metadata/.plugins/com.ibm.ftt.resources.zos/responseFileName.log.
  • If you connect to a remote system from the SCLM perspective, the connection does not support push-to-client updates.

    For more information about push-to-client support in the SCLM perspective, see Push-to-client updates are not supported in the SCLM perspective.

  • Rational Developer for System z v8.0.1 push-to-client does not work with Installation Manager v1.4.3.

    For more information about working around this limitation, see Rational Developer for System z v8.0.1 push-to-client does not work with Installation Manager v1.4.3 or later.


Feedback