Starting a Security Domain Requestor with a Token File

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

See the TIBCO ActiveSpaces Installation document for information on setting the environment variables.

Make sure that you have a valid token file for the domain

Start the as-admin utility:

 as-admin

Issue the following CLI command to start the requestor node:

connect security_token <string> [name <string>] [member_name <string>] [listen <string>]

For example:

as-admin> connect security_token ’mytoken.txt’ name ’ms’ member_name 
’client1’ listen ’tcp://127.0.0.1:50000’

where,

security_token: Specifies a string indicating the name of the token 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.
The metaspace name that you use to start the requestor must be the same metaspace name that you used to start the security domain controller.
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.

Procedure