IBM Software Group. RDz - Push to client IBM Corporation

Transcription

1 IBM Software Group RDz - Push to client 2008 IBM Corporation

2 Questions raised when rolling out RDz What are the best practices for the initial installation of RDz and the subsequent roll out to a large developer community? We have hundreds of developers using RDz. How can I quickly get them updated to the same version when a new release is available? RDz is highly configurable. There are developers I work with who do not even know about some of these very useful Preferences. RDz Some developers obtain their own fixes and others wait until they are told to upgrade. How can I share a configuration that works best in our environment with my colleagues? If I want to use a new workspace it takes me an hour to get RDz customized to where I had it before. 2

3 RDz Push to client support Trigger client product version updates Centralize common configurations Update workstation upon login to Remote System RDz Config 3

4 What are some examples of Configurations? Global System specific 4

5 Primary vs Non-primary systems Examples of information pushed to RDz client upon system connection Global System specific RDz product upgrades RSE Connections Preferences z/os File System Mappings Property Groups Host-based projects Global + System specific Primary System System specific Non-primary System 5

6 Roles RDz Administrator o Could be the System Administrator who maintains RDz host o Could be an expert RDz Developer who coordinates with System Administrator o Responsibilities may include: configuring push-to-client support on the host creating Installation Manager response files maintaining a Master Workspace exporting configuration files RDz Developer o Typical RDz user you are familiar with today Receives product updates automatically Receives configuration files automatically 6

7 Roles RDz Administrator o Could be the System Administrator who maintains RDz host o Could be an expert RDz Developer who coordinates with System Administrator o Responsibilities may include: configuring push-to-client support on the host creating Installation Manager response files maintaining a Master Workspace exporting configuration files RDz Developer o Typical RDz user you are familiar with today Receives product updates automatically Receives configuration files automatically 7

8 RDz Administrator product updates Set up for distribution of product updates 1) Create a push-to-client properties file called pushtoclient.properties enables Push to Client support and defines the location of the key mapping file 1) Create an installation configuration file called installconfig.xml defines the minimum acceptable version of RDz and the associated response file scanned during RDz client connections If RDz client is below the minimum acceptable version, RDz shuts down the workbench and starts IBM Installation Manager using a response file downloaded from the remote system 1) Create a key mapping file called keymapping.xml defines the location of response files (and configuration files) can be created manually or using the Export... RDz Configurations wizard 1) Create an IBM Installation Manager response file enables workstations to complete an unattended product installation 8

9 Push-to-client properties file Default location of /etc/rdz/ Standard properties file Requires RSED restart after editing Enables/Disables Push To Client support o Configuration file updates o Product version updates o Ability for user to reject updates Primary system indicator o Only one system can be the primary system o Primary system stores all global, non-system specific, configuration files and settings Location of key mapping file Central store for configuration files Access permissions for files created by the USS store 9

10 Installation configuration file Location defined in key mapping file UTF-8 encoded XML file Target Product ID element o must not be changed Target Version element o Defines the acceptable version of RDz that the client can be without being forced to update o major[.minor[.micro[.qualifier]]] Response File element o name of IBM Installation Manager response file to use during update If the client is earlier than RDz version 8.0, it does nothing (because <responsefile> element is empty). If the client version is 8.0 or later but before v _0717, it launches Installation Manager using response file update_80.xml. If the client version is v _0717 or later but earlier than 9.0, it does nothing. If the client version is 9.0 or later but before 9.0.1, it launches Installation Manager using response file update_9.0.1.xml. 10

11 Key mapping file Location defined in push to client file UTF-8 encoded XML file Location element o One per configuration file used in rollout File Id element o Specifies the type of file at this location, configuration file, response file, etc o RDz defined values (also extensible) Container Path element o Specifies the location of the file o Install Config & Response files must be on primary system File Mask element o Specifies the name of file Encoding element o Specifies the encoding of the file The administrator has placed installconfig.xml in the /var/rdz/pushtoclient/install directory of the z/os server. The administrator has placed update_80.xml and update_901.xml in the /var/rdz/pushtoclient/install/response_files directory of the z/os server. 11

12 Response file Location defined in key mapping file UTF-8 encoded XML file Contains all the information necessary for IBM Installation Manager to upgrade the RDz client (and any other bundled offering) o Product update runs unattended (silent install) Includes support for o Uninstall, Install or Update o Modify features o Configure license support More details can be found: IBM Rational Developer for System z Installation Guide IBM Installation Manager Information Center 12

13 Roles RDz Administrator o Could be the System Administrator who maintains RDz host o Could be an expert RDz Developer who coordinates with System Administrator o Responsibilities may include: configuring push-to-client support on the host creating Installation Manager response files maintaining a Master Workspace exporting configuration files RDz Developer o Typical RDz user you are familiar with today Receives product updates automatically Receives configuration files automatically 13

14 RDz Administrator configuration updates Set up for distribution of configuration updates 1) Create a push-to-client properties file called pushtoclient.properties enables Push to Client support and defines the location of the key mapping file 1) Create a key mapping file called keymapping.xml defines the location of configuration files can be created manually or using the Export... RDz Configurations wizard 1) Create a master workspace using RDz client Create Remote System connections (including to the primary system) Define configuration information and set Preferences 1) Export the Configuration Files using the new RDz Export wizard Places common configuration information into Configuration Store for push to clients 14

15 Key mapping file Location defined in push to client file UTF-8 encoded XML file Location element o One per configuration file used in rollout File Id element o Specifies the type of file at this location, configuration file, response file, etc o RDz defined values (also extensible) Container Path element o Specifies the location of the file o RSE Connections & Preferences files must be on primary system File Mask element o Specifies the name of file Encoding element o Specifies the encoding of the file 15

16 Master workspace Administrator defines all the configuration information o Create Remote System connections o Define Preferences o Create system specific information 16

17 Export Configuration Files An Export Wizard to help one person preferably an Admin to configure various settings on RDz client and upload it to a central location. o Settings are grouped by function into configuration files such as remote connections or system mappings. o The export wizard allows the administrator to specify a host location o Can be invoked from File Export Rational Developer for System z Configuration files 17

18 Export Configuration Files Global configuration information o settings that are not host system specific but apply across all systems Remote Systems Preferences o allows editing of Path File mask File encoding Global Exports data from client to config store in the form of files Updates key mapping file element values 18

19 Export Configuration Files System specific configuration information o Settings that are specific or dependent on the system the user is connecting to z/os File System Mappings Property Groups System specific Exports data from client to config store in the form of files Updates key mapping file element values 19

20 Roles RDz Administrator o Could be the System Administrator who maintains RDz host o Could be an expert RDz Developer who coordinates with System Administrator o Responsibilities may include: configuring push-to-client support on the host creating Installation Manager response files maintaining a Master Workspace exporting configuration files RDz Developer o Typical RDz user you are familiar with today Receives product updates automatically Receives configuration files automatically 20

21 RDz Developer Initial RDz installation Setting up RSE connections at install time o Defined once o Created in each new workspace Limited to 1 connection today o Daemon only Optional panel Can be driven by IM silent install o Set up by RDz Administrator Primary system 21

22 Product Updates Available Upon connecting to the host, a user may be notified that product updates are available to be installed. o Settings on the host control whether users can reject incoming product updates minimum acceptable client version which response file to use during product update 22

23 Configuration Updates Available Upon connecting to the host, a user may be notified that incoming updates are available for their configuration. o Settings on the host control whether users can reject incoming changes or not 23

24 Setting preferences for configuration updates Notify me of all updates o Each time you connect to the remote system you are notified of all available updates. Notifications continue until you install the updates. Notify me of updates that I have not rejected o Each time you connect to the remote system, you are notified of available updates for the configurations and preferences you have updated previously. If, on previous connections, you have rejected any updates, you are no longer notified of them. Do not notify me of updates o Rational Developer for System z never notifies you that configuration and preference updates are available. o No updates are performed The administrator must have reject updates enabled in push-to-client properties file for these client preferences to have meaning. 24

25 25

26 Where to learn more RDz Information center Configuring section IBM Education Assistant V8.0.1 Installation and configuration 26

27 IBM Software Group RDz Push to client enhancements 2008 IBM Corporation

28 Groups - Background In RDz v8.0.1 all clients are treated equally by push-to-client (PTC) For v8.0.3 we are providing finer grained control by taking into account what "group" a client belongs to. Some potential uses of groups include: Install different product versions for different groups Allow a subset of users to refuse PTC updates Provide different configuration settings for different groups Group membership is determined using existing access control mechanisms Security Access Facility (SAF) RACF, Top Secret & ACF2 all support SAF interface Lightweight Directory Access Protocol (LDAP)

29 Groups - Configuration See Push-to-client considerations in Host Configuration Reference (SC ) for more information about supporting multiple groups. New values of SAF and/or LDAP are used in the pushtoclient.properties file When SAF is specified for a setting, we check whether the user has read access permits to security profiles which determine a user's PTC group When LDAP is specified for a setting, we check the LDAP Server (defined in rsed.envvars) for the user's membership in various LDAP groups which determine a user's PTC group

30 Groups Workspace binding Even though a developer can be part of multiple groups simultaneously, the developer s active workspace cannot. The active workspace must be bound to a specific group (which can be the default group) to receive configuration or product updates. Once the bind is done, it cannot be undone. A new workspace must be created if a new group binding is required. Note: if necessary, you can select one group for product updates and a different group for configuration updates.

31 Groups - Miscellaneous We display a message or other indication that the configuration files which the user accepted have been downloaded successfully The dialog shown to the user when the client version is in the range specified by the forcedupgradeversion attribute explains that the Product Update is mandatory (and therefore no Cancel button exists on the dialog).

32 Additional pushable configuration items Menu Manager actions Database connections Software Analyzer configurations New items present in: Administrator's Export dialog Developer's Update dialog