Home
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, 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.

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.
- 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.
  - Changing the secure port number for the web management service
    By default, the web management service runs on port 8443. You can specify a different port number when you create or update a domain.
  - Changing the secure port number for the REST management API service
    By default, the REST management API service runs on port 9714. You can specify a port number when you create or update a domain.
  - Changing the secure port number for the JMX management API service
    By default, the JMX management API service runs on port 9975. The JMX management API service uses an HTTP service for handling large data operations. By default, an open port is dynamically chosen for this HTTP service when the domain is started. You can specify port numbers for each of these services when you create or update a domain.
  - Changing the secure port number for the Teracloud® Streams data service
    By default, an open port is dynamically chosen for the Teracloud® Streams data service when an instance is started. This is done to avoid port conflict errors when starting multiple instances on the same resource. You can override this behavior by specifying a port number when you create or update an instance. If you try to start an instance and the port is already being used, the instance fails to start and you receive a message that the port is in use.
  - Monitoring domain and instance services
    Use the Streams Console to view the status of Teracloud® Streams services.
- 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.

Administering 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.

About this task

To determine whether a domain service is running, you can use the Streams Console or the streamtool command line interface. For example, you can run the streamtool getdomainstate command. The following command output shows all domain services running on host1:

domain: domain1 State: STARTED
Resource              Status    Services                                      Tags
host1.teracloud.com   RUNNING   RUNNING:aas,auditlog,controller,jmx,rest,sws

To determine whether an instance service is running, you can use the Streams console or the streamtool command line interface. For example, you can run the streamtool getresourcestate command. The following command output shows all instance services running on host2:

Instance: instance1 Started: yes State: RUNNING Resources: 1 (1/1 Management, 1/1 Application) Version: 7.2.0.0
Resource               Status  Schedulable Services                       Tags ResourceSpecId[count,tags,..]
host2.teracloud.com    RUNNING yes         RUNNING:app,data,sam,srm,view  1[1(none)[shared]]

You can access Streams functionality such as the Streams Console, REST APIs, JMX APIs, and data exchange APIs by making a connection to the domain or instance service providing the functionality. In order to establish the connection, you need to provide a URL that includes the host where the service is running and the port used to establish connections.