Configuring the Teracloud® Streams environment by running streamsprofile.sh
Procedure
source product-installation-root-directory/7.2.0.0/bin/streamsprofile.sh
- Add the source command to your
home-directory/.bashrc shell
initialization file. Otherwise, you must enter the command every time you start
Teracloud®
Streams. For example, if the product is installed in the /home/streamsadmin/InfoSphere_Streams/7.2.0.0 directory, add the
following line to your .bashrc
file:
source /home/streamsadmin/InfoSphere_Streams/7.2.0.0/bin/streamsprofile.sh
- For shared installations, you can add the source command to the /etc/profile.d script so that all users do not need to edit their own shell initialization files. Users can modify their own shell initialization files if they need to use a different installation of Teracloud® Streams.
- If you install a new product version or a Version 7.2 fix pack or interim fix, you must update the .bashrc or /etc/profile.d file. Teracloud® Streams appends a unique version directory for a new product version, fix pack, or interim fix to the installation root directory.
Results
- STREAMS_INSTALL=product-installation-root-directory/7.2.0.0
- STREAMS_INSTANCE_ID=StreamsInstance
For compatibility with previous releases, if the STREAMS_DEFAULT_IID environment variable is already configured when you run the script, STREAMS_INSTANCE_ID is set to the value of STREAMS_DEFAULT_IID.
- STREAMS_DOMAIN_ID=StreamsDomain
- STREAMS_JAVA_HOME
For instructions on how to override the streamsprofile.sh behavior by explicitly setting the STREAMS_JAVA_HOME variable, see Java requirements, options, and settings for Teracloud Streams.
This script will report an error if the Java™ requirements are not met. For details of the Java requirements, see Java requirements, options, and settings for Teracloud Streams.
This script also adds the product-installation-root-directory/7.2.0.0/bin directory to the PATH environment variable so that you can run streamtool commands without specifying a fully qualified path.