Starting Security Domain Controllers

Prerequisites

Make sure that the paths to the required system variables are set.

Procedure

See the TIBCO ActiveSpaces Installation document for information on setting the environment variables.
Make sure that you have a valid policy file for the domain.
Start the as-admin utility:
```
as-admin
```
Issue the following CLI command to start the domain controller node:
```
connect security_policy <string> [name <string>] [member_name <string>]
```
For example:
```
connect security_policy ’mypolicy.txt’ name ’ms’ member_name ’secure1’ listen ’tcp://127.0.0.1:50000’
```
where:
security_policy

Specifies a string indicating the name of the security policy file for the security domain.

name

Specifies a string containing the name of the metaspace that is specified in the Metaspace Access List within the security policy file

member_name

Is an optional parameter that specifies a metaspace member name.

listen
Specifies a string indicating the listen parameter for the metaspace.
Note: Do not specify the discovery parameter for the connect command when starting either a security domain controller or a security domain requestor. When you start these nodes, the connect command picks up the discovery setting specified in the security policy file or the security token file for the node.
Note: On the UNIX platform, if a controller is started in background mode, it issues a password error without prompting for a password.
There are several possible workarounds:

Start the controller normally and provide the password; when authentication is completed, type CTRL-Z and then enter the command bg to run in the background.

Alternatively, if customized authentication is required, implement a custom callback function; for example, an application can send its credentials from its command line if needed and the custom callback will use them.