bstr_node_setup(1) — Commands
Name
bstr_node_setup − This command creates a series of directories and configuration files on the Node on which you execute it. It allows you to define configuration parameters relative to the Name Services, BASEstar Open working directories, database and communication parameters, and miscellaneous run-time parameters.
Syntax
bstr_node_setup -l location [-y | -adv] [-v]
Description
You must execute the bstr_node_setup command for each Node on which you want to run BASEstar Open. You can only execute this command on a Node where BASEstar Open is installed.
Before running the bstr_node_setup command, you must log in as a root. The bstr_node_setup command is in the etc directory, under the BASEstar Open installation directory.
You cannot execute the bstr_node_setup command if there are BASEstar Open processes currently active. You must shut down all environment and application components first.
The bstr_node_setup command performs the following operations:
•Creates configuration files for the Node-specific environment components.
•Creates script files (one for "sh" and one for "csh") that can be used to set the values of the installation-dependent BASEstar Open global variables.
•Allows you to upgrade the /etc/services file for BASEstar Open network service daemons (see services(5) and udp(4n)).
•If ORACLE is installed, the bstr_node_setup command asks you to specify whether the Node is a PODB Node. If it is, it creates the database configuration file, and requests configuration parameters to be specified.
•Creates the subtree that stores the BASEstar Open temporary files created at run-time.
To display some or all of the configuration parameters, select one of the following options: --y (default), or --adv.
Options
-l locationPathname of the directory where the BASEstar Open kit is installed. It must be an absolute pathname.
-ySimplified Node setup. The only value you can supply is the name of the BASEstar Open Nodes where the primary and secondary copies of the Name Services server were activated.
-advAdvanced Node setup. Same as the --y option. In addition, you can change the name and characteristics of the subtree under which the BASEstar Open temporary and snapshot files are stored at run-time.
-vThis option displays additional information on the execution of the command.
Usage Notes
While executing the bstr_node_setup command, press <Return>
to accept the default value that is displayed between square brackets. Press <Ctrl/C>
at any time to abort the bstr_node_setup command.
The lines displayed by the bstr_node_setup command start with different character strings, depending on the operation being performed. The following character strings can be displayed:
•The @@@ string identifies a message that describes the operation in progress.
•The &&& string identifies an error message (error or fatal error).
Lines displayed without any of the above character strings are input requests. The name of the less extensive option that displays a given parameter is specified within brackets. In other words, if the --y option is specified, it means that the parameter is also displayed by the -adv option.
Have You Specified the Right Directory?
The bstr_node_setup command prompts you to confirm that the pathname specified by the --l option argument is correct:
Do you want to set up the kit installed in
installation_directory? [yes]:
(--y option). Enter no to terminate the command execution immediately.
Changing the Configuration Parameters
The bstr_node_setup command allows you to display a series of configuration parameters and, if necessary, modify their values.
BSTR.Spool_Root [/usr/var/opt/bstbase310/etc/../spool_root]:
(--adv option). Pathname of the BASEstar Open work and snapshot subdirectories root. Do not specify a directory mounted by NFS, otherwise you will not be able to run BASEstar Open on your system. Likewise, the IVP will fail if you specify a /tmp directory mounted via NFS.
BSTR.Spool_Owner [root]:
(--adv option). Name of the owner of the BASEstar Open work subdirectories.
BSTR.Spool_Group [users]:
(--adv option). Name of the group that owns the BSTR.Spool_Root directory tree (this entry must correspond to an existing group).
BSTR.Spool_Protection_Mode [0771]:
(--adv option). Protection mask applied to the BSTR.Spool_Root directory tree. The default value is 0771 (that is, "rwxrwx---"), which restricts directory access to the owner (BSTR.Spool_Owner) and the group (BSTR.Spool_Group).
LNS.Server_Node [current_node]:
(--y option). Name of the Node where you want BASEstar Open to activate the primary copy of the Name Services server. This entry must be identical for all BASEstar Open Nodes.
LNS.Server_Node_2 []:
(--y option). The name of the Node on which you want BASEstar Open to activate the secondary copy of the Name Services server. This entry (if specified) must be identical for all BASEstar Open Nodes. Note that you cannot activate the secondary copy of the Name Services server on the same Node that you specified for the primary copy.
This parameter is optional.
Specifying the Role of the Node
The bstr_node_setup command asks whether you want your Node to act as a PODB Node:
DB.Node_Is_Cfg_Server ? [False]
Enter True if you want the Node that you are setting up to act as a PODB Node, otherwise enter False.
Creating Configuration and Script Files
After displaying the values of the configuration parameters (and allowing you to modify them if necessary), the bstr_node_setup command displays a series of messages informing you that configuration and script files are being created or edited. Any original files are copied to files of the same name (with the ".old" extension) and maintained for recovery purposes, or to allow reference to old values. The files created by bstr_node_setup are:
•The installation_file.h_node_name, which contains all the configuration parameters entered in response to the bstr_node_setup command prompts, together with a few reserved configuration parameters.
•The lns.conf.h-node_name file, which contains all the configuration parameters entered in response to the bstr_node_setup command prompts regarding the LNS network service.
•The bstrusers.sh file, a Bourne shell script that allows you to set installation-dependent global variables. The file is created under the etc sub-directory of the BASEstar Open installation directory and is symbolically linked to /etc/bstruser.sh.
•The bstrusers.csh file, a Bourne shell script that allows you to set installation-dependent global variables. The file is created under the etc sub-directory of the BASEstar Open installation directory and is linked symbolically to /etc/bstruser.sh.
Upgrading the /etc/services File
After creating the configuration and script files, bstr_node_setup prompts you to specify whether you wish to upgrade the /etc/services file in order to insert the BASEstar Open IP services used by the communication daemons.
Would you like to upgrade /etc/services ? [yes]
@@@ upgrading /etc/services ...
If you enter y, bstr_node_setup automatically upgrades the /etc/services file.
Enter y or n, depending on the following considerations:
•If the /etc/services file is not upgraded via yellow pages, enter y
•If the /etc/services file is upgraded via yellow pages, then:
•If you are performing the installion on a yellow pages master server, enter y
•Otherwise, enter n.
If you enter y (default), bstr_node_setup copies the original /etc/services to /etc/services.old. It checks that there are no duplicated entries before adding the BASEstar Open entries as appropriate. If it finds a duplicated entry, bstr_node_setup requests confirmation that you wish to remove it:
# remove existing entries? [yes]
If you enter y, bstr_node_setup removes the duplicated entry. Enter n if you do not want bstr_node_setup to upgrade the /etc/services file.
If you chose not to upgrade /etc/services automatically, or the upgrade fails because of a duplicated entry, bstr_node_setup creates a file called etc/bstr_services in the location directory. This file contains the records that should have been added to /etc/services. For instance, you could use it for appropriate upgrading of the "services" map (via the Yellow Pages). However, it is the responsibility of the environment manager to upgrade /etc/services or any other equivalent file used locally.
Creating the Database Configuration File
The bstr_node_setup command only displays the prompts listed below if your Node is a PODB Node:
DBA_Username [ORACLE]:
Enter the name of the ORACLE user.
DB_Identifier [BSTR]:
Enter the ORACLE DBMS identifier.
Initial_DB_datafile_Path
[<Work_Directory>/node/cnf]:
Initial_DB_RedoLog1_Path
[<Work_Directory>/node/cnf]:
Initial_DB_RedoLog2_Path
[<Work_Directory>/node/cnf]:
Initial_DB_Tables_Path
[<Work_Directory>/node/cnf]:
Initial_DB_Indexes_Path
[<Work_Directory>/node/cnf]:
Initial_DB_Rollseg_Path
[<Work_Directory>/node/cnf]:
For each of the above requests, you must provide pathnames for the following:
•The database file that contains the ORACLE data dictionary
•The ORACLE Redo log files
•The database file that contains the BASEstar Open objects
•The database file that contains the BASEstar Open indexes
•The database file that contains the rollback segments
•The database file that contains the temporary segments.
At this point, bstr_node_setup creates the DB_parameters.h_node_name database configuration file and inserts the database SID in /etc/oratab.
Creating BASEstar Open Work Directories
Finally, the bstr_node_setup command creates the basic BASEstar Open work directories from the user entries. If the root directory (or a subdirectory) already exists, bstr_node_setup requests confirmation before removing it. You cannot specify a directory mounted via NFS as the work and snapshot subdirectories root ($BSTR_WORK_ROOT).
On completion, the bstr_node_setup command returns you to the shell prompt.
Examples
$ /usr/kits/bstr310/etc/bstr_node_setup -adv
<Return>
@@@ Using default kit_location: /usr/kits/bstr310
LNS.Server_Node [NODE1]: NODE2<Return>
do you want to setup the kit installed in /usr/kits/bstr310? [yes]
Y<Return>
@@@ reading configuration... please wait...
@@@ defining the basic communication parameters ...
-------------------------
The answers to the following questions control the configuration of
the work directories and the users authorized to access them, i.e. to
work with BASEstar.
-------------------------
Name of the BASEstar work and snapshot subdirectories root:
BSTR.Spool_Root [/usr/var/opt/bstbase310/etc/../spool_root]:<Return>
Name of the owner of the BASEstar work subdirectories:
BSTR.Spool_Owner [root]:<Return>
Name of the group authorized to access the BASEstar work
subdirectories:
BSTR.Spool_Group [users]:<Return>
Protection Mask of the BASEstar work subdirectories
(octal value):
BSTR.Spool_Protection_Mode [0771]:<Return>
Name of the host where the primary LNS Server will run:
LNS.Server_Node [NODE1]: NODE2<Return>
Name of the host where the secondary LNS Server will run:
--- Note that the primary and secondary LNS Server Hosts cannot
coincide.
LNS.Server_Node_2 []: NODE1<Return>
-------------------------
The answers to the following questions control what global daemons
have to be started at node startup (i.e., by bstr_node_start).
-------------------------
Answer True if you want local-only realms to be active on the node.
BSTR.Local_Only_Enabled [False]:<Return>
Answer True if this node will run the Database Server.
DB.Node_Is_Cfg_Server ? [FALSE]True<Return>
@@@ creating shell setup file /usr/var/opt/bstbase310/etc/bstrusers.sh ...
@@@ creating shell setup file /usr/var/opt/bstbase310/etc/bstrusers.sh.h_ayrton.mln.dec.com ...
@@@ creating c-shell setup file /usr/var/opt/bstbase310/etc/bstrusers.csh ...
@@@ creating c-shell setup file /usr/var/opt/bstbase310/etc/bstrusers.csh.h_ayrton.mln.dec.com ...
@@@ creating shell setup file /usr/var/opt/bstbase310/etc/bstradmin.sh ...
@@@ creating shell setup file /usr/var/opt/bstbase310/etc/bstradmin.sh.h_ayrton.mln.dec.com ...
@@@ creating c-shell setup file /usr/var/opt/bstbase310/etc/bstradmin.csh ...
@@@ creating c-shell setup file /usr/var/opt/bstbase310/etc/bstradmin.csh.h_ayrton.mln.dec.com ...
@@@ creating /usr/var/opt/bstbase310/etc/lns.conf.h_ayrton.mln.dec.com...
&&& Warning: Secondary LNS Server not configured.
would you like to upgrade /etc/services ? [yes]
@@@ upgrading /etc/services ...
@@@ moving /etc/services in /etc/services.old ...
@@@ going to create the BASEstar spool directory,
@@@ containing the BSTR_WORK_ROOT and BSTR_DBACCESS_KEY subdirectories.
$
If you are logged in to NODE_DB, the bstr_node_setup command creates the BASEstar Open static structures on NODE_DB. In addition, BASEstar Open expects the primary copy of the Name Services server to be available on NODE2 and the secondary copy on NODE1. NODE_DB is also set up as a PODB Node.