Options for setting up the domain controller service on IBM Streams resources
An IBM Streams domain can include resources that run the domain controller service as a registered Linux system service and an unregistered service. Both options can be used together in a domain. However, you cannot use both options on a resource in the domain. You must run the controller on each resource as either a system service or an unregistered service.
Options
- For high availability with automatic recovery from failures, a root user must set up the
domain controller service as a registered Linux system service on the
resource. If a system crash or failure occurs, the controller is automatically restarted on the
resource when the system is restarted. Notes:
- If the domain is stopped, the controller continues to run.
- Running the domain controller service as a system service is required if you plan to use the security.runAsRoot domain property.
- For high availability with limited automatic recovery from failures, a root or non-root user can
set up the domain controller service as an unregistered service on the resource. If a system crash or
failure occurs, the controller must be manually restarted on the resource after the system is
restarted. Notes:
- If the domain is stopped and the controller is running as user root, the controller continues to run.
- If the domain is stopped and the controller is running as non-root, the controller shuts down.
- If SSH is enabled, the controller is automatically restarted when the domain is restarted.
- If SSH is not enabled, the user who restarts the domain must manually restart the controller on the resource.
By default, the domain.sshAllowed property is set to true, and IBM Streams attempts to use SSH for communication between resources in the domain. If you are not using SSH for your communication mechanism, setting this property to false prevents unnecessary communication attempts between resources and SSH error messages. You can set this property when you create the domain or after the domain is created by using the Domain Manager or the streamtool command-line interface.
Commands
The following table lists the streamtool commands that you use to set up the domain controller service on IBM Streams resources.
Command | Description |
---|---|
streamtool mkhostpkg | This command generates a domain host installation
package that you can use to add IBM
Streams resources to a domain. If you do not want the controller to run as a registered Linux system service, specify the --unregistered option on the command. If a non-root user runs the command with this option, the domain must exist and be started. The streamsdomainhostsetup.sh script file is in the domain host installation package. This script installs IBM Streams on the resource, registers the resource in the domain, and starts the domain controller service on the resource. If you specify the --unregistered option on the streamtool mkhostpkg command, the controller starts as an unregistered service. Otherwise, the controller starts as a registered Linux system service. |
streamtool registerdomainhost | This command registers the IBM
Streams resource in the domain, sets up the domain controller service as a registered Linux system service, and starts the
controller on the resource. You can run the streamtool registerdomainhost command before or after you create an IBM Streams enterprise domain. Example:
Notes:
|
streamtool startdomainhost | This command starts the domain controller service on an IBM
Streams resource.
|