Home
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
Resources
After you add resources to domains and instances, you can administer them by using the Streams Console or the streamtool command-line interface.
Monitoring resources
Use the Streams Console to view the status of resources.
Resource status values
Resources have state values that provide information about their status.

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.
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
- Domains
  After you create a Teracloud® Streams domain, you can administer it by using the Streams Console graphical user interface and the streamtool command-line interface.
- Resources
  After you add resources to domains and instances, you can administer them by using the Streams Console or the streamtool command-line interface.
  - Resource allocation for application services
    A resource for application services can be static (added explicitly to an instance) or dynamic (added to or removed from an instance dynamically based upon the job or processing element requirements). A static resource is specified manually by name or automatically by a resource specification and remains allocated to the instance until it is explicitly removed. A dynamic resource is released from the instance when the instance is stopped or when the resource is no longer needed.
  - Resource allocation for management services
    Management services are placed on static resources if available. If the instance does not have any static resources and dynamic resource allocation is enabled, management resources are dynamically requested at the time the instance is started.
  - Resource identifiers
    A resource identifier uniquely identifies a resource in a domain or instance.
  - Tags
    Tags are a mechanism for differentiating and identifying resources that have different physical characteristics or logical uses.
  - Monitoring resources
    Use the Streams Console to view the status of resources.
    - Resource status values
      Resources have state values that provide information about their status.
  - Stopping and quiescing resources
    You can stop or quiesce resources when you want to perform maintenance activities.
  - Removing resources
    You might choose to remove a resource if the host is no longer available or you want to replace it with a different resource.
- Instances
  To create and manage instances, you can use the Streams Console or the streamtool command-line interface.
- Domain and instance services
  Before you can perform Teracloud® Streams tasks, Teracloud Streams domain and instance services need to be running on resources in the domain. Domain services are started by starting the domain and instance services are started by starting the instance.
- Jobs
  You can start and administer jobs by using Streams Console or the streamtool command-line interface.
- Recovery
  You can back up your Teracloud® Streams system files and directories and then restore them later if necessary. In general, you can recover from application and runtime failures without restoring Teracloud Streams from a backup.
- Streams Console
  You can use the Streams Console to monitor and manage the Teracloud® Streams instances and applications in your domain from any computer that has HTTP connectivity to the server that is running the web management service.
- Logs and traces
  Teracloud® Streams provides options that enable administrators, instance owners, and application developers to manage log and trace data.
- Managing and monitoring Teracloud® Streams using management APIs
  Teracloud® Streams provides two API sets to manage and monitor Streams services and jobs.
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.

Resource status values

Resources have state values that provide information about their status.

Table 1. Resource state
Resource state	Description
FAILED	All services on the resource report as failed or degraded.
PARTIALLY_FAILED	Some services, but not all, report as failed or degraded.
PARTIALLY_RUNNING	Not all services report as running, but no services report as failed or degraded.
QUIESCED	The resource is quiesced and no services are running on it.
QUIESCING	Services on the resource are being stopped so that the resource can be quiesced.
RESTARTING	The domain controller service is restarting on the resource.
RUNNING	All services on the resource are running or waiting as expected.
STARTING	Services on the resource are being started.
STOPPED	Services on the resource are stopped.
UNKNOWN	No Teracloud® Streams services are running on the resource.

The streamtool getresourcestate command output also includes information about whether the resources are schedulable, which means the resource is available for running stream applications.

Table 2. Schedulable states
Schedulable state	Description
Degraded	The resource is not schedulable because the application deployment service is degraded.
Draining	The resource is doing a controlled shutdown. Existing stream applications are terminating and no additional stream applications can be started on this resource. This situation occurs because of a stop instance, quiesce resource or remove resource operation.
Failed	The resource is not schedulable because the domain controller service failed or is not responding.
Not Applicable	The resource cannot be used to schedule processing elements because it is not configured to run applications. If the application deployment service is not running on the resource, it cannot run applications.
Schedulable	The resource is running normally, the application deployment service is available, and the resource can be used to run stream applications.
Starting	The resource is not schedulable because the domain controller service is starting and is not yet available to schedule processing elements.
Stopped	The domain controller service and all applications are stopped.