IBM InfoSphere Streams Version 4.1.1
Planning roadmap for InfoSphere Streams
This roadmap summarizes planning considerations, options, and requirements for InfoSphere® Streams.
Verification tools: InfoSphere
Streams provides the following tools that help you to verify many of the requirements listed in the
Planning roadmap:
- Before installation, run the dependency checker script to verify requirements on the resources that you plan to install InfoSphere Streams on. If you are installing the product on a cluster of resources, run the dependency checker script on each resource in the cluster.
- After installation, use the streamtool checkhosts command to verify requirements on single or multiple resources.
| Task | Description | Verification tools | |
|---|---|---|---|
| Dependency checker script | streamtool checkhosts command | ||
| Ensure that you download the correct InfoSphere Streams installation package for your target system. | The operating system and architecture of the target system and
the product installation package must be the same. For example, if your target system is a 64-bit
RHEL 6 system, you must download the InfoSphere
Streams 64-bit RHEL 6 installation package. For information about downloading InfoSphere Streams Version 4.1.1, see the Download Document. |
✓ | |
| Review the requirements and options for setting up an InfoSphere Streams environment with multiple resources. | The preferred and most reliable environment
for multiple resources is a production environment. This option provides
high availability so that InfoSphere
Streams continues
to run even if resources fail or are not available. If you do not
need high availability, a development or test environment might be
your preferred option. For more information, see Considerations for InfoSphere Streams environments with multiple resources. |
||
| Verify that the firewall on the resource is disabled. | If firewall usage is necessary, see the Firewall configuration guidelines for InfoSphere Streams. | ||
| Verify that you satisfy the hardware requirements for InfoSphere Streams. | For more information, see Hardware requirements for InfoSphere Streams. | ||
| Verify that you satisfy the operating system requirements for InfoSphere Streams. | For more information, see Operating system requirements for InfoSphere Streams. | ✓ | ✓ |
| Ensure that you have installed the prerequisite RPMs for InfoSphere Streams. | For more information, see Required RPMs for InfoSphere Streams. | ✓ | ✓ |
| Review the Java™ requirements, options, and settings for InfoSphere Streams. | For more information, see Java requirements, options, and settings for InfoSphere Streams. | ||
| Ensure that an X Window System is installed on resources, if required | An X Window System is required
to use the following InfoSphere
Streams interfaces. Alternative options are available if you
do not have an X Window System installed.
|
||
| Verify that all resources satisfy InfoSphere Streams dependency requirements. | Before installation, use the InfoSphere Streams dependency checker script to verify that all resources satisfy dependency requirements. After installation, use the streamtool checkhosts command. | ✓ | ✓ |
| Verify that all resources satisfy InfoSphere Streams network requirements. | Each resource must have full TCP networking
capabilities (binding to non-reserved TCP sockets) that are available
to programs running in user mode. Important: Ensure that all
resources satisfy the name resolution requirements for InfoSphere
Streams. If you receive warnings about name resolution during the product installation, you can complete
the installation. However, you must resolve any name resolution issues before you use InfoSphere
Streams.
For more information about network configuration requirements for InfoSphere Streams, see Name resolution requirements for InfoSphere Streams hosts. |
✓ | ✓ |
| If you are running InfoSphere Streams across multiple resources and using SSH, a common user management system is the preferred method for creating and managing InfoSphere Streams users. | An automated common user management system is
an efficient mechanism for creating and managing users across all
resources in a cluster environment. Otherwise, you must manually maintain
the user credentials repository for all resources. As the number of
resources and users increases, manual updates can become difficult
to manage. In an environment with multiple resources, InfoSphere Streams requires that user information be the same across all resources in the cluster. For example, if the installation owner is streamsadmin, the administrator must create the user streamsadmin with the same user ID, group ID, and other user information across all resources in the cluster. Using a common management system to create and manage users ensures that user information is the same across all resources. Examples of common user management systems are IBM® Tivoli® Directory Server and Network Information Service (NIS). |
||
| Ensure that the character encoding of your locale configuration is set to UTF-8. | InfoSphere Streams provides multicultural support using the UTF-8 character encoding. | ✓ | ✓ |