Name

bstr_realm_start_node − Starts up the realm-specific environment components on the Node. 

Syntax

  bstr_realm_start_node realm_name [-v] -w  [-nocs]  work_dir

Parameters

realm_nameSpecifies the local name of the Realm for which the environment components are to be started up. 

Description

Execute the bstr_realm_start_node command on a given Node for a given Realm to make the specified Realm available on the Node. 

Before executing the bstr_realm_start_node command, start up the Node using the bstr_node_start command, and set up the Realm on the same Node using the bstr_realm_setup_node command. 

Note that the user-defined global variables that you set before executing this command are visible to the Application Management Services server. Therefore, they are also visible to all processes (that is, Programs) started by the server. 

In addition, if you wish to specify a different port number for the PC Communication server, set the new value in the BSTR_PC_PORT global variable. 

The bstr_realm_start_node command performs the following steps:

1Starts up the Communication Service. 

2Starts up the Global Object Services
  server.

3Starts up the Application Management Services server. 

4Starts up the PC Communication server. 

5Checks for license and environment integrity on the Node. 

Options

-w work_dir

This option specifies the pathname of the directory where BASEstar Open stores Realm-specific work files. The specified directory must exist. 

-nocs

This option allows you to disenable the mechanism that automatically starts up the Communication Server for the Realm. If you do not need to connect a client, -nocs allows you to save an environment process for each Realm. 
 

-v

Displays additional information on the execution of the command. 

Examples

$ bstr_realm_start_node MY_REALM<Return>

If you are logged in to NODE1, the bstr_realm_start_node command starts up MY_REALM on that Node. 

See Also