Upgrading InfoSphere Streams Version 3.2.1 Instances to Version 4.0.0.0

As part of the new functions and features, InfoSphere Streams Version 4.0.0.0 has introduced the concept of a domain. An InfoSphere Streams domain is a container for InfoSphere Streams instances which provides a single point for configuring and managing common resources, security, and instances. A domain has some but not all the characteristics of instances defined in Version 3.2.1. The components of the instance that are now part of the domain are:

  • Security (AAS)
  • Hosts or Resources
  • Host or Resource Tags and definitions
  • SWS
  • Logging

To assist in updating V3.2.1 instances to V4.0.0.0 domains, we have developed an upgrade aid tool. The tool will output commands and generate scripts that will create a basic working domain and instances with the same hosts and tags with upgraded properties. The domain and instances will be created with the user running the command (owner of the .streams directory for instances being upgraded) as the owner.

Note: the configurations may need to be adjusted for high availability or application balancing etc… To create production ready domains and instances you may need to make additional changes and modifications to get the optimal environment for your particular needs. Be sure to read: Planning to install IBM InfoSphere Streams in the IBM InfoSphere Streams Version 4.0 documentation.

The tool accepts one or more instance names (as defined in the user’s .streams directory). For each instance the instance.properties file is parsed, the properties for the instance are upgraded, any properties that have moved to the domain level are upgraded (and merged if there are more than one instance being migrated to the domain). Similarly, the security definition file for each instance will be merged into the domain.

Note: Because a domain has only one security authentication method, only instances with matching security authentication methods can be merged. An error will result if the instances have different authentication methods.

Specific host names and tags defined in the instances will also be merged to the domain. The domain creation parameters generated will include the hosts specified in the instances as well as the host tags assigned to them in the instance.properties files.
Note: The “build”and “execution” tags from V3.2.1 are no longer used in in V4.0.0.0 and will not be used in the domain. Also hosts that had an hc service defined, will be tagged with the “application” tag.
Note:In V4.0.0.0 service placement is controlled entirely by tag definitions, this tool will only consider the hc service placement and automatically tag those hosts with the “application” tag. You will need to adjust the other service placement once the domain has been created.

The tool will generate and list streamtool commands that can be used to generate the domain, the tag definitions, and the instances.  The tool also generates a script with the commands that can be executed. The user is prompted when conflicting property definitions are found. Duplicate tag definitions are skipped.

Before creating the new domain, InfoSphere Streams Version 4.0 must be installed on each of the hosts to be included in the new domain, either by running as a system service or have SSH setup and configured per the Installation documentation.

Be sure to read: Planning to install IBM InfoSphere Streams in the IBM InfoSphere Streams Version 4.0 documentation and Upgrading to InfoSphere Streams Version 4.0.

Important: This tool does not affect the instance configurations being used from the owners .streams directory.

To use the tool:  Upgrade Tool

  1. Download the .tar.gz file from the Upgrade Tool link above.
  2. Create a directory for the instance owner of the instances to upgrade (ie: /homes/streamsadmin/upgradeinstance)
  3. Move the .tar.gz file to the directory created in step 2 and untar the file in the directory (ie: tar -zxvf upgrade-Multiple_Instances.tar.gz)
  4. Open the UpgradeInstances.pdf file and follow the steps outlined in the document.

Join The Discussion