Postinstallation roadmap for Teracloud® Streams

The postinstallation roadmap summarizes required and optional postinstallation tasks and options for Teracloud® Streams.
Table 1. Postinstallation tasks for Teracloud® Streams

This table lists required and optional postinstallation tasks for Teracloud® Streams, and provides references to more detailed information.
Task Description
Configure the Teracloud® Streams environment variables. Before you can use Teracloud® Streams, you must configure the product environment variables. For more information, see Configuring the Teracloud Streams environment by running streamsprofile.sh.
Set up the domain controller service on resources with the main installation package installed. 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. For more information, see Options for setting up the domain controller service.
Set up a Teracloud® Streams domain. Before you use Teracloud® Streams, you must create at least one domain. A Teracloud® Streams domain is a container for Teracloud® Streams instances which provides a single point for configuring and managing common resources, security, and instances.

A basic domain has a single Teracloud® 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 Teracloud® Streams can continue to run even if resources fail or are not available.

For more information, see the following procedures:
Optional: Install the Uncrustify source code formatter. When you generate C++ code using the sc command, Teracloud® 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 Teracloud® Streams is optional. For more information, see Installing the Uncrustify source code formatter for Teracloud Streams.
Optional: Change the default location for Teracloud® Streams log and trace files. The default root directory for class cache, log, and trace files that are generated by Teracloud® 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 Teracloud® Streams domain properties:
  • domain.fileStoragePath: This property specifies the root directory where Teracloud® Streams class cache and other temporary files are stored. If the class cache files are removed, the web management service might fail and not recover correctly.

  • domainLog.path: This property specifies the root directory where Teracloud® Streams log and trace files are stored. If these files are removed, it might be difficult to resolve Teracloud® Streams problems.

You can update these properties when you create the domain or after the domain is created.