IBM Streams 4.2.1
Configuring IBM Streams
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.
- Setting up an IBM Streams basic domain on a single resource
A basic domain has a single IBM Streams resource and user. This type of domain is typically used for test or development environments. - Setting up an IBM Streams enterprise domain on multiple resources
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. - Configuring security for IBM Streams
Each IBM Streams domain and instance maintains its own security configuration. - Configuring audit logging for IBM Streams
IBM Streams supports comprehensive, multiple-level auditing of product and user operations. By default, audit logging is not enabled. - Configuring transport mechanisms for IBM Streams
IBM Streams supports several high-performance and configurable transport mechanisms for communicating across processing elements (PEs). You can configure the transport mechanism by updating IBM Streams properties or by specifying options in streams processing applications. - Configuring Streams Studio for remote development
You can install Streams Studio on a local Linux or Windows system that acts as a client and install IBM Streams on a remote Linux system that acts as a server. To connect to the remote Linux system where IBM Streams is installed, you must configure a connection. - Configuring a checkpoint data store for IBM Streams domains and instances
Use this procedure to configure a checkpoint data store for IBM Streams domains and instances. A checkpoint data store is used by applications that call the IBM Streams Checkpointing API.