Updating the installation configuration file

Create or update the installation configuration file.

This type of update supports only modification-level updates. You can use push-to-client to update clients from version 3.1 to version 3.1.1, for example, but not from version 3.1 to version 4.0 and not from version 4.0 to version 4.1.

Create or edit the installconfig.xml file.
If this file exists, you can add entries for the installation to this file. If the file does not exist, you can copy the sample installation configuration file that is shown at the end of this procedure, modify it for your installation, and save it to the z/OS® server. The installation configuration file is a UTF-8 encoded XML file.
Include the <installedOffering> tag to identify the offering ID of the product you want to distribute updates for.
The <installedOffering> tag has the following syntax:
```
<installedOffering id="installedOfferingID">
```
You can specify an offering ID for any product that is installed in the same package group as the IBM® Explorer for z/OS product. The offering ID is stored in the <offering> tag of the response file. The following is an example of the <offering> tag:
```
<offering id='com.ibm.zos.explorer.v30' version='3.0.0.20151002_1738' profile='IBM Software Delivery Platform' features='listOfInstalledFeatures'/>
```
Specify the value in the id attribute of the <offering> tag for the id attribute in <installedOffering id="installedOfferingID">.
Include an <install> tag with one of the following attributes to specify a range of product versions to be updated and the name of the response file to install the product update.
Only one of the following attributes can be defined for each installed offering ID in the installation configuration file. If both attributes are specified, the installedVersion attribute takes precedence over the forcedUpgradeVersion attribute.
Important: The behavior that is triggered by the installedVersion and forcedUpgradeVersion attributes is further defined by the reject.product.updates parameter of the pushtoclient.properties file. For more information about how these attributes are affected by the reject.product.updates parameter, see the related topics.
- An installedVersion attribute. If the version currently installed on a client workstation is within the installedVersion range, a confirmation window opens and the client can accept or refuse the update. When the update is accepted, Installation Manager starts with the response file specified in the responseFile attribute to update the client.
```
<install installedVersion="[minimumVersionInclusive, maximumVersionInclusive] | (minimumVersionExclusive, maximumVersionExclusive)" responsefile="fileName">
```
- A forcedUpgradeVersion attribute. If the version currently installed on a client workstation is within the forcedUpgradeVersion range, a confirmation window opens, but the client cannot reject the update. If the version is outside of the range, the client is not prompted with a confirmation window and cannot be updated.
```
<install forcedUpgradeVersion="[minimumVersionInclusive,maximumVersionInclusive] | (minimumVersionExclusive, maximumVersionExclusive)" responsefile="fileName">
```
You can specify the value for installedVersion and forcedUpgradeVersion as an inclusive, exclusive, or mixed range:
- To specify a range of product versions that includes the minimum and maximum versions, use square brackets. For example, installedVersion="[3.0.1, 3.0.2]" prompts an installation update for product versions 3.0.1, 3.0.2, and all versions between this range.
- To specify a range of product versions that excludes the minimum and maximum versions, use parentheses. For example, installedVersion="(3.0.1, 3.0.2)" prompts an installation update for product versions greater than 3.0.1 but less than 3.0.2.
- You can mix brackets and parentheses to specify a range that includes one end of the range but excludes the other:
  - For example, installedVersion="(3.0.1, 3.0.2]" prompts an installation update for product versions greater than 3.0.1 but less than or equal to 3.0.2.
  - For example, installedVersion="[3.0.1, 3.0.2)" prompts an installation update for product versions greater than or equal to 3.0.1 but less than 3.0.2.
For either of these attributes, the version numbers must include at least the major version number. It can include minor version, micro version, and qualifier: major[.minor[.micro[.qualifier]]] The following examples show valid version numbers for the installedVersion and forcedUpgradeVersion attributes:
```
3
3.0
3.0.0
3.0.0.201510140202
```
Place the installation configuration file and the response file on the z/OS server and point to that location in the key mapping file.

The installation configuration file is a UTF-8 encoded XML file. It contains one or more sets of <installedOffering> tags that define a target product offering ID and one or more pairs of installed version ranges and response file names. The push-to-client feature processes the following sample installation configuration file as follows:

Scans the file until it finds a product offering ID that matches the ID of any product that is installed in the same package group as the currently running IBM Explorer for z/OS version. For example, if a client is running the IBM Explorer for z/OS product in the same package group as the Engineering Workflow Management product, then the matching offering ID can be either
com.ibm.team.install.rtc.client.eclipse or

com.ibm.zos.explorer.v30
If the current product version of the matching offering ID falls within the range that is provided in any of the pairs of <installedVersion> and <responseFile> attributes, Installation Manager starts by using the response file. If the Engineering Workflow Management version, for example, is greater than or equal to 3.0.0 and less than 3.0.1, Installation Manager starts by using the response file update_rtc_from_600_to_601.xml.

<?xml version="1.0" encoding="UTF-8"?>
<installConfig>
   <installedOffering id="com.ibm.zos.explorer.v31">
      <install
         installedVersion="[3.0.1, 3.0.2)"
         responseFile="update_zxpl_from_301_to_302.xml">
      </install>
      <install
         installedVersion="[3.1.0, 3.1.1)"
         responseFile="update_zxpl_from_310_to_311.xml">
      </install>
   </installedOffering>
<installedOffering id="com.ibm.team.install.rtc.client.eclipse">
      <install
         installedVersion="[6.0.0, 6.0.1)"
         responseFile="update_rtc_from_600_to_601.xml">
      </install>
   </installedOffering>
   </installConfig>