Home
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
Configuring audit logging
Teracloud® Streams supports comprehensive, multiple-level auditing of product and user operations. By default, audit logging is not enabled.
Enabling audit logging
To enable audit logging for Teracloud® Streams, use this procedure to create a log4j configuration file and update the required domain properties.

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.
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
- Setting up a basic domain on a single resource
  A basic domain has a single Teracloud® Streams resource and user. This type of domain is typically used for test or development environments.
- Setting up an 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 Teracloud® Streams can continue to run even if resources fail or are not available.
- Configuring security
  Each Teracloud® Streams domain and instance maintains its own security configuration.
- Configuring audit logging
  Teracloud® Streams supports comprehensive, multiple-level auditing of product and user operations. By default, audit logging is not enabled.
  - Enabling audit logging
    To enable audit logging for Teracloud® Streams, use this procedure to create a log4j configuration file and update the required domain properties.
  - Customizing audit logging
    The sample log4j configuration file that is installed with Teracloud® Streams includes an appender example that shows you how to filter out audit event entries and messages based on certain conditions.
  - Audit log examples
    Audit log entries contain information about Teracloud® Streams domains, instances, users, operations, and operation objects. Detailed messages can provide additional information.
- Configuring transport mechanisms
  Teracloud® Streams supports several high-performance and configurable transport mechanisms for communicating across processing elements (PEs). You can configure the transport mechanism by updating Teracloud Streams properties.
- Configuring a checkpoint data store
  Use this procedure to configure a checkpoint data store for Teracloud® Streams domains 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.

Enabling audit logging for Teracloud® Streams

To enable audit logging for Teracloud® Streams, use this procedure to create a log4j configuration file and update the required domain properties.

About this task

Procedure

Create a log4j configuration file for audit logging.
1. Make a copy of the following sample file that is installed with Teracloud® Streams:
```
product-installation-root-directory/7.2.0.0/etc/trc/log.default.properties.xml
```
2. Edit the copy as needed.
Important: Do not edit the sample .xml file. If you edit the sample .xml file and it becomes corrupted, errors can occur.
Optional: Customize audit logging by adding filters to your log4j configuration file.
Optional: Change the default location of the audit log files in your log4j configuration file.

By default, Teracloud® Streams saves the audit log files in the same location as the other product log files, which is the directory that is specified on the domainLog.path property. To save the audit log files in a different location, change the streams_log_path variable in your log4j configuration file to another path on your system.
Set the auditlog.log4jPropertiesFile domain property to point to your log4j configuration file.
The log4j configuration file must be accessible in the path that is specified by the auditlog.log4jPropertiesFile property by all resources that run the audit log service. This can be a shared file location or an exact copy on each resource.
Optional: Set the auditlog.log4jAppenderClassPath domain property. This property is used to find the customized log4j appender ClassPath.
Set the auditlog.level domain property to standard.
The default setting is off.
If the domain is running, you must restart the domain for the changes to be effective.

Results

After the changes become effective for the domain, users can dynamically enable or disable audit logging by updating the auditlog.level domain property. Possible settings are off (no auditing) or standard (auditing performed at the standard level).

Note: For more information about the audit logging properties, enter streamtool man domainproperties. All properties that apply to audit logging are prefixed with auditlog. To set properties, use the streamtool setdomainproperty command.