IBM Streams 4.2.1
Postinstallation roadmap for IBM Streams
The postinstallation roadmap summarizes required and
optional postinstallation tasks and options for IBM®
Streams.
| Task | Description |
|---|---|
| Configure the IBM Streams environment variables. | Before you can use IBM Streams, you must configure the product environment variables. For more information, see Configuring the IBM Streams environment by running streamsprofile.sh. |
| If you are upgrading to IBM Streams Version 4.2.1 and have a previous version of the product installed, review the migration guidelines. | To review the migration guidelines, see the guidelines for your current IBM Streams version: |
| Optional: Configure SSH for IBM Streams. | In previous releases, IBM Streams used Secure Shell (SSH) to run product applications, commands, and scripts. Beginning in Version 4.0, using SSH is optional. If you are using SSH, see Configuring a Secure Shell environment for IBM Streams. |
| If you are not using SSH for your communication mechanism, you must set up the domain controller service on resources with the main installation package installed. | A domain controller service runs on every resource in an IBM Streams domain and manages all of the other services on that resource. You can set up the domain controller service as a registered Linux system service or an unregistered service. For more information, see Options for setting up the domain controller service. |
| Set up an IBM Streams domain. | Before you use IBM
Streams, you must create at least one domain.
An IBM
Streams domain is a container for IBM
Streams instances which provides a single point for configuring and managing common resources, security, and instances.
A basic domain has a single IBM Streams resource and user. This type of domain is typically used for test or development environments. An enterprise domain can have multiple resources and users. This type of domain is typically used for production environments. You can configure high availability to ensure that IBM Streams can continue to run even if resources fail or are not available. For more information, see the following procedures:
|
| Optional: Install IBM Streams Studio. | Streams Studio is an integrated development environment that enables you to create, edit, visualize, test, debug, and run streams processing applications. You can install Streams Studio on a Linux or Microsoft Windows system. For information about installation requirements and procedures for Streams Studio, see Installing IBM Streams Studio. |
| Optional: Install the Uncrustify source code formatter. | When you generate C++ code using the sc command or Streams Studio, IBM Streams can use the Uncrustify source code formatter to ensure that the generated code is indented and formatted correctly. Installing and using the Uncrustify source code formatter with IBM Streams is optional. For more information, see Installing the Uncrustify source code formatter for IBM Streams. |
| Optional: Change the default location for IBM Streams class cache, log, and trace files. | The default root directory for class cache, log, and trace files
that are generated by IBM
Streams is the /tmp directory. If you use a system maintenance utility such as
tmpwatch, either modify the utility to exclude these files or configure a
different root directory by using the following IBM
Streams domain properties:
You can update these properties when you create the domain or after the domain is created. |
| Optional: Review your options for extending IBM Streams. | You can expand the capability of IBM Streams by using additional features such as IBM Streams for Microsoft Excel or Apache Edgent. For more information, see Extending IBM Streams. |