Home
Installing
Use this information to install, upgrade, and uninstall the Teracloud® Streams product.
Planning to install Teracloud® Streams
To plan for installing Teracloud® Streams, start by reviewing the information in the planning roadmap.
Software requirements
Before you install Teracloud® Streams, run the dependency checker script to verify that the target system satisfies the product software requirements.
Java requirements, options, and settings
Ensure that you use a Java™ development kit that is supported by Teracloud® Streams. If Java memory issues occur, Teracloud Streams provides configuration properties that you can use to allocate more memory for the Java environment.
Upgrading Java

Welcome
Learn about the core capabilities of Teracloud® Streams, its architecture, and key concepts.
Installing
Use this information to install, upgrade, and uninstall the Teracloud® Streams product.
- Planning to install Teracloud® Streams
  To plan for installing Teracloud® Streams, start by reviewing the information in the planning roadmap.
  - Preparing to install Teracloud® Streams
    Use the information in this topic to plan and prepare for your Teracloud® Streams installation. The plan that you create for your environment determines your tasks and choices throughout the installation process.
  - Considerations for environments with multiple resources
    Review these options and requirements for Teracloud® Streams environments before you install the product.
  - Hardware requirements
    Before you install Teracloud® Streams, ensure that the target system satisfies the minimum hardware requirements.
  - Software requirements
    Before you install Teracloud® Streams, run the dependency checker script to verify that the target system satisfies the product software requirements.
    - Operating system requirements for Teracloud® Streams
      Teracloud® Streams supports Red Hat Enterprise Linux™ (RHEL).
    - Required RPMs for Teracloud® Streams
      To operate correctly, Teracloud® Streams requires a set of prerequisite RPMs.
    - Java requirements, options, and settings
      Ensure that you use a Java™ development kit that is supported by Teracloud® Streams. If Java memory issues occur, Teracloud Streams provides configuration properties that you can use to allocate more memory for the Java environment.
      - Supported Java™ development kits for application development
        For application development, Teracloud® Streams requires Java™ SDK Version 17 or later to be installed.
      - Configuration settings for Java™ memory issues
        If Java™ out-of-memory errors occur when you use Teracloud® Streams, you can allocate more memory for the Java environment by increasing the maximum JVM size for Teracloud Streams services and user interfaces.
      - Upgrading Java
    - Dependency checker script
      The dependency checker script verifies that your system satisfies the operating system, RPM, and other software requirements for Teracloud® Streams.
  - Domain controller service options
    A domain controller service runs on every resource in a Teracloud® 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.
  - Firewall configuration guidelines
    If firewall usage is required, the preferred configuration is to set up a firewall at the perimeter of the Teracloud® Streams cluster to restrict network access to resources in the cluster but not communication between the resources. When any communication passes through a firewall, latency is introduced. These guidelines apply to clients that are in the Teracloud Streams cluster as well as clients that are external to the cluster.
  - Linux ulimit configuration guidelines
    The default Linux™ user limit (ulimit) values might be too small for some Teracloud® Streams environments. Use these guidelines to ensure that your ulimit settings are sufficient for Teracloud Streams.
  - Name resolution requirements for resources
    All resources must satisfy the product network configuration requirements or Teracloud® Streams fails to start on the resource.
- Installing the Teracloud® Streams product
  Use these procedures to install Teracloud® Streams Version 7.2.
- Upgrading Teracloud® Streams
  Use these procedures to install a new version of Teracloud® Streams when a previous version of the product is already installed, or to update a Version 7.2 Non-Production Edition license.
- Uninstalling Teracloud® Streams
  Use this procedure to remove the Teracloud® Streams product from your system.
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
Developing
Develop stream applications with the Streams Processing Language (SPL), Java, and Python.
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
Glossary
Use this glossary to find terms and definitions for Teracloud® Streams.

Upgrading Java

If you are using OpenJDK to install a new version of Java, it is recommended to install it using the RPM and then update the alternatives to the version of Java you want to use. For information on how to do so, refer to Supported Java development kits for application development.

If you are setting the STREAMS_JAVA_HOME environment variable explicitly, you must update the following symlink /etc/alternatives/java_sdk to point to the new version of Java. When the Streams processes are restarted, they will use the new version of Java.

If you are not using a symlink for the STREMS_JAVA_HOME environment variable, you must explicitly update it. In addition, if running the controller as a system service, you must update the STREAMS_JAVA_HOME property in the /var/InfoSphereStreams/domainscript/.<domain-id>.properties file on each domain host where you are running the controller as a system service.