BASEstar_Open_Server_for_Compaq_Tru64_UNIX__________ Inst. & Management Guide Order Number: AA-QSD6B-TE June 1999 This guide provides instructions for installing BASEstar Open for Compaq Tru64 UNIX . Revision/Update Information: This is a revised document for the current release. Operating System and Version: Compaq Tru64 UNIX from V3.2C to Version 5.0 Software Version: BASEstar Open Version 3.2 Compaq Computer Corporation Houston,Texas ii ________________________________________________________________ First printing, February 1996 Revised, September 1996 Revised, June 1999 © Digital Equipment Corporation 1999. All Rights Reserved. The software described in this guide is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of the agreement. Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. COMPAQ,the Compaq logo and the Digital logo are registered in the U.S. Patent and Trademark Office. Tru64 is a trademark of Compaq Computer Corporation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, BASEstar, DEC, DECmessageQ, DECnet, DECnet-DOS, DECosap, DEComni, DIGITAL, DIGITAL UNIX, FMS, LN03, MicroVAX, NAS, OpenVMS, OpenVMS Alpha, PATHWORKS, PDAS, Rdb/VMS, ReGIS, ThinWire, TK, ULTRIX, VAX, VAXcluster, VAX COBOL, VAX FORTRAN, VAX Pascal, VAX RMS, VMS/ULTRIX Connection, and VT. Microsoft and Windows NT are registered trademarks of Microsoft Corporation. The following are third-party trademarks: Other product names mentioned herein may be the trademarks of their respective companies. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... ix Installation - Compaq Tru64 UNIX 1 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.1 Release Notes.................................... 1-1 1.2 License Registration............................. 1-2 1.3 Checking the Media Software Distribution Kit..... 1-3 1.4 BASEstar Open Server Subsets..................... 1-3 1.5 Installation Procedure Requirements.............. 1-4 1.5.1 Checking Login Privileges ..................... 1-4 1.5.2 Hardware Requirements ......................... 1-4 1.5.3 Software Requirements ......................... 1-5 1.5.4 Determining Disk Space Requirements ........... 1-6 1.5.5 Increasing the Available Disk Space for BASEstar Open Server Installation.............. 1-8 1.6 Backing Up Your System Disk...................... 1-8 1.7 Stopping the Installation........................ 1-8 1.8 Error Recovery................................... 1-9 2 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.1 Installing CD-ROM Consolidated Distribution Media............................................ 2-1 2.2 Responding to Installation Procedure Prompts..... 2-2 2.2.1 Selecting Subsets ............................. 2-2 2.2.2 Monitoring Displays During the Subset Loading Process........................................ 2-4 2.2.3 Running the IVP ............................... 2-5 iii 2.2.4 Setting Up and Starting the BASEstar Open Server Environment............................. 2-5 2.3 The Installation Verification Procedure.......... 2-6 2.3.1 Prerequisites and Constraints ................. 2-7 2.3.2 Running the Installation Verification Procedure...................................... 2-8 2.4 Getting Help and Reporting Problems.............. 2-8 2.5 Deleting BASEstar Open Server From Your System... 2-9 2.6 Using the Startup Files Created During the Installation..................................... 2-10 3 Installing BASEstar CIMfast 3.1 Starting the Installation Procedure.............. 3-1 3.1.1 Using CD-ROM Consolidated Distribution Media .. 3-1 3.2 Responding to Installation Procedure Prompts..... 3-2 3.2.1 Selecting Subsets ............................. 3-2 3.2.2 Monitoring Displays During the Subset Loading Process........................................ 3-3 3.3 Completing the Installation...................... 3-3 3.3.1 Running the Installation Verification Procedure...................................... 3-4 3.3.2 Using the Startup Files Created During the Installation................................... 3-4 Part II Environment Management 4 Introduction to Environment Management 4.1 Environment Management Overview.................. 4-1 4.2 Environment and Application Components Relationship..................................... 4-2 4.3 BASEstar Open Environment Components............. 4-2 4.3.1 Nodes ......................................... 4-3 4.3.2 PODB Nodes .................................... 4-4 4.3.3 Managing the PODB on an ORACLE Database ....... 4-5 4.3.4 Realms ........................................ 4-5 4.3.5 Sample Environment Configuration .............. 4-8 iv 5 Environment Management Procedures 5.1 Setup Procedures................................. 5-2 5.1.1 Setting Up a Node ............................. 5-2 5.1.2 Setting Up a Realm ............................ 5-2 5.1.2.1 Setting Up a Realm on a Node................ 5-2 5.1.2.2 Setting Up the Realm Database on the PODB Node........................................ 5-3 5.1.3 Setting Up the Sample Environment ............. 5-3 5.2 Startup Procedures............................... 5-5 5.2.1 Starting Up a Node ............................ 5-5 5.2.2 Starting Up a Realm ........................... 5-5 5.2.2.1 Starting Up a Realm on a Node............... 5-5 5.2.2.2 Starting Up the Database Server for a Realm on the PODB Node............................ 5-5 5.2.3 Starting Up the Sample Environment ............ 5-6 5.3 Shutdown Procedures.............................. 5-8 5.3.1 Shutting Down a Realm ......................... 5-8 5.3.1.1 Shutting Down the Database Server for a Realm on the PODB Node...................... 5-8 5.3.1.2 Shutting Down a Realm on a Node............. 5-8 5.3.2 Shutting Down a Node .......................... 5-9 5.3.3 Shutting Down the Sample Environment .......... 5-10 5.4 Unset Procedures................................. 5-12 5.4.1 Unsetting a Realm ............................. 5-12 5.4.1.1 Unsetting a Realm from a Node............... 5-12 5.4.1.2 Unsetting a Realm Database on the PODB Node........................................ 5-12 5.4.2 Unsetting a Node .............................. 5-12 5.4.3 Unsetting the Sample Environment .............. 5-13 5.5 Monitoring BASEstar Open......................... 5-14 6 Environment Management Command Reference 6.1 Executing Environment Commands................... 6-1 6.1.1 Requirements and Constraints .................. 6-1 6.1.1.1 Users and Commands.......................... 6-1 6.1.1.2 Executing a Command......................... 6-3 v 6.2 Privileges for Running Environment Management Procedures....................................... 6-4 cli_bstr......................................... 6-5 bstr_env_show.................................... 6-7 bstr_node_setup.................................. 6-13 bstr_node_shut................................... 6-22 bstr_node_start.................................. 6-24 bstr_node_unset.................................. 6-26 bstr_realm_check_env............................. 6-28 bstr_realm_setup_db.............................. 6-31 bstr_realm_setup_node............................ 6-33 bstr_realm_shut_db............................... 6-35 bstr_realm_shut_node............................. 6-36 bstr_realm_start_db.............................. 6-38 bstr_realm_start_node............................ 6-39 bstr_realm_unset_db.............................. 6-41 7 BASEstar Open Environment Monitor 7.1 Introduction..................................... 7-1 7.2 Running the BASEstar Open Environment Monitor.... 7-3 7.3 General Characteristics.......................... 7-3 7.4 Views............................................ 7-4 7.4.1 Active Realm View ............................. 7-4 7.4.2 Active Node View .............................. 7-7 8 BASEstar Open-Supplied Servers 8.1 Servers, Activities and Owned Resources.......... 8-3 8.1.1 Snapshots ..................................... 8-3 8.1.2 Logged Information ............................ 8-4 8.2 Global Object Services........................... 8-5 8.3 Application Management Services.................. 8-7 8.3.1 Environment Variables - Inheritance and Usage.......................................... 8-7 8.4 Event Services................................... 8-9 8.4.1 Using Application Management Services to Manage an Event Services Server....................... 8-9 8.4.2 Starting Up and Shutting Down an Event Services Server from the Command Interpreter............ 8-9 8.5 Packet Services.................................. 8-12 vi 8.5.1 Using Application Management Services to Manage a Packet Services Server....................... 8-12 8.5.2 Starting Up and Shutting Down a Packet Services Server from the Command Interpreter............ 8-12 8.6 Data Services.................................... 8-15 8.6.1 Environmental Variables ....................... 8-15 8.6.2 Using Application Management Services to Manage a Data Services Server......................... 8-16 8.6.3 Starting Up and Shutting Down a Data Services Server from the Command Interpreter............ 8-17 8.7 Device Services.................................. 8-19 8.7.1 Global Variables .............................. 8-19 8.7.1.1 Specifying the Calling VMD.................. 8-19 8.7.1.2 Specifying the Connection Retry Timeout to a VMD......................................... 8-20 8.7.2 Using Application Management Services to Manage a Device Services Server....................... 8-21 8.7.3 Starting Up and Shutting Down a Device Services Server from the Command Interpreter............ 8-22 8.8 Combined Data & Device Services.................. 8-24 8.8.1 Environmental Variables ....................... 8-24 8.8.2 Using the Data & Device Services to Support Passive Connections............................ 8-26 8.9 PC Communication Servers......................... 8-27 9 Application Management Services Monitor 9.1 Introduction..................................... 9-1 9.2 Running Application Management Services Monitor.. 9-1 9.3 General Characteristics.......................... 9-2 9.4 Views............................................ 9-4 9.4.1 Actor View .................................... 9-5 9.4.2 Activity View ................................. 9-8 9.4.3 Program View .................................. 9-10 9.4.4 Process View .................................. 9-12 9.4.5 Node View ..................................... 9-14 vii 10 Log Services Features 10.1 Saving Copies of Log Files....................... 10-1 10.1.1 Purging Log Files ............................. 10-2 10.2 Log File Record Format........................... 10-2 10.2.1 Displaying Log Files .......................... 10-6 10.2.1.1 Displaying a Save Copy...................... 10-7 10.2.1.2 Displaying a Working Copy................... 10-7 10.3 Log Services Server Activities................... 10-7 11 Log Services Command Reference DISPLAY LOG...................................... 11-2 OPEN LOG......................................... 11-4 A Files Installed by BASEstar Open Server on Compaq Tru64 UNIX Systems A.1 Directories Installed by the BSTBASE320 Subset... A-1 A.2 Files Installed by the BSTBASE320 Subset......... A-3 A.3 Files Installed by the DOUBASE310 Subset......... A-13 A.4 Files Installed by the DOUMAN310 Subset.......... A-16 B BASEstar Open Global Variables B.1 Global Variable List............................. B-1 B.2 Installation-specific Global Variables........... B-8 B.2.1 Setting the Values of Global Variables ........ B-9 B.3 BSTR_REALM Global Variable....................... B-9 B.4 Global Variables for Server Activation........... B-9 B.5 Application Management Services Global Variables........................................ B-10 C Environment and Parameter Files C.1 General Record Format............................ C-1 C.2 Format of the File for the Node environment Attribute........................................ C-3 C.3 Format of the File for the Program parameters Attribute........................................ C-4 C.3.1 File Format ................................... C-4 viii D Environment Component Processes E Managing Snapshot Files in a Distributed Environment E.1 Using Configuration Management Commands in a Multi-Node Environment........................... E-1 E.2 Snapshot File Location........................... E-2 E.3 The BSTR_DBACCESS_KEY Global Variable............ E-2 E.4 Making Snapshot Files Accessible................. E-3 E.4.1 Mounting Snapshot Directories with NFS ........ E-3 E.4.2 Copying Snapshot Files Using a File Transfer .. E-4 F Sample Listings for BASEstar Open Installation Index Examples 10-1 Node Log File Example ......................... 10-4 10-2 Realm Log File Example ........................ 10-5 Figures 4-1 Sample BASEstar Open Environment .............. 4-9 7-1 Active Realm View ............................. 7-4 7-2 Active Node View .............................. 7-7 9-1 Cursor Mode ................................... 9-4 9-2 Actor View with Actor Attributes .............. 9-5 9-3 Actor View with Activity Attributes ........... 9-7 9-4 Activity View ................................. 9-9 9-5 Program View .................................. 9-11 9-6 Process View .................................. 9-13 9-7 Node View ..................................... 9-14 ix Tables 1 Conventions Used in BASEstar Open ............. xii 1-1 BASEstar Open Server Subsets .................. 1-3 1-2 Required Subsets .............................. 1-5 1-3 Worksheet for Disk Space Requirements (Kilobytes).................................... 1-7 6-1 Relationship Between Environment Management Commands and Users............................. 6-2 6-2 Environment Management Privileges ............. 6-4 8-1 Environment Variables - Validity and Usage .... 8-8 8-2 Data Management-Environmental Variables ....... 8-15 8-3 Device Management-Environmental Variables ..... 8-20 8-4 Data and Device Management-Environmental Variables...................................... 8-24 10-1 Log Services CLI Commands ..................... 10-1 10-2 Log File Component Identifier ................. 10-3 A-1 Directories Installed by the BSTBASE320 Subset......................................... A-1 B-1 BASEstar Open Global Variables ................ B-2 C-1 Valid Values of the File for the Node environment Attribute.......................... C-3 C-2 Valid Values of the File for the Program parameters Attribute........................... C-5 D-1 Processes ..................................... D-1 x _________________________________________________________________ Preface This guide describes how to install the BASEstar Open software on COMPAQ processors running the Compaq Tru64 UNIX operating system. Keep this document with your distribution kit. You may need it to install maintenance updates or to reinstall BASEstar Open Server. Multiplatform Applicability The information in this manual is only applicable to BASEstar Open server nodes on Compaq Tru64 UNIX systems. Intended Audience This guide is addressed to system managers responsible for installing and setting up BASEstar Open Server software on Compaq Tru64 UNIX systems. Pre-requisites Any users required to install and manage the BASEstar Open environment must know how to manage a Compaq Tru64 UNIX system. A basic knowledge of BASEstar Open features is also recommended. Structure of this Document This manual is organized as follows: o Chapter 1 describes the Compaq Tru64 UNIX operating system, the hardware/software requirements for installation, and the related procedures that you must complete before installing BASEstar Open Server on a Compaq Tru64 UNIX system. ix o Chapter 2 describes how to install BASEstar Open Server on a Compaq Tru64 UNIX system. o Chapter 3 describes how to install BASEstar CIMfast on a Compaq Tru64 UNIX system. o Chapter 4 provides an overview of environment management issues. o Chapter 5 describes the procedures that allow you to set up, start up and shut down the components of your BASEstar Open Server environment. o Chapter 6 contains reference information for the above procedures, including the necessary prerequisites and privileges. o Chapter 7 describes the BASEstar Open Environment Monitor, an interactive tool that enables you to monitor the BASEstar Open environment at run-time. o Chapter 8 explains how to start up, shut down and manage BASEstar Open-supplied servers. o Chapter 9 describes the Application Management Services Monitor, an interactive tool that enables you to monitor Application Management Services objects. o Chapter 10 describes how Node-specific log services collect information from the environment components. o Chapter 11 contains reference information for the log services commands. o Appendix A lists the files and directories that the BASEstar Open Server installation procedure installs on a Compaq Tru64 UNIX system. o Appendix B lists and describes the BASEstar Open global variables. o Appendix C describes the format and contents of: - The environment file, as specified in the environment attribute of a Node object - The parameter file, as specified in the parameters attribute of a Program object o Appendix D lists the platform-dependent processes that implement each BASEstar Open environment component. x o Appendix E provides information about managing snapshot files in a multi-node environment. This appendix is relevant to Compaq Tru64 UNIX systems only. BASEstar Open Documentation Set This manual describes a software component or aspects of the BASEstar Open family of products. The complete set of documents relating to the BASEstar Open family is as follows: o BASEstar Open: - BASEstar Open Introduction - BASEstar Open Reference Guide - BASEstar Open Command Language Interface - BASEstar Open Application Programming Interface - BASEstar Open Messages - Platform-specific installation and management guides - BASEstar Open Guide to DCM-Modeled Device Connectivity (for supported platforms) o BASEstar CIMfast (for supported platforms): - BASEstar CIMfast User's Guide - BASEstar CIMfast Programmer's Reference Guide - BASEstar CIMfast Guide to DECmessageQ Support (not available on Windows NT platforms) - BASEstar CIMfast Guide to SQL Support o DEComni API: - DEComni API and MMS User Guide - DEComni API Guide to Using Omni Directory Services (for supported platforms) - DEComni API Guide to Using OmniView (for supported platforms) - DEComni API Omni Definition Facility User Guide (for supported platforms) xi o Device Access Software documentation - Specific manuals for each supported device Conventions Table 1 lists the conventions used in the BASEstar Open documentation set. Table_1_Conventions_Used_in_BASEstar_Open________________________ % The default user prompt is your system name followed by a right angle bracket (>). In the BASEstar Open docset, a percent sign (%) is used to represent this prompt. / Indicates that you must hold down the Ctrl key while you press another key. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) . A vertical ellipsis indicates the omission of . items from a code example or sample command; . the items are omitted because they are not important to the topic being discussed. . . . A horizontal ellipsis in format descriptions or in examples indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. (continued on next page) xii Table_1_(Cont.)_Conventions_Used_in_BASEstar_Open________________ [] In format descriptions, brackets indicate optional elements; you can select none, one, several, or all of the choices. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification, or in the syntax of a substring specification in an assignment statement.) ( ) In format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. boldface text Boldface text represents one of the following cases: o user input o the introduction of a new term o the status values true or false italic type Indicates titles of manuals, variables, arguments, data structures, fields, callable functions, operands, and utilities. Italic text also represents information that can vary in system messages (for example, Internal error number), command lines (for example, /PRODUCER=name), and command operands in text. code type Indicates information that is part of the code for a program or application. numbers Unless otherwise noted, all numbers in the text are assumed to be decimal. Nondecimal radixes- binary, octal, or hexadecimal-are explicitly indicated. UPPERCASE TEXT Uppercase text indicates a command, the name of a file, the name of a file protection code, the abbreviation for a system privilege, the name of a field, or the value of an attribute where attributes are chosen from a list. (continued on next page) xiii Table_1_(Cont.)_Conventions_Used_in_BASEstar_Open________________ "point_a + Literal string. Using quotation marks is point_b" optional unless there is a space, slash (/), or parenthesis in the string. BASEstar Open Valid characters for the names of BASEstar Open names objects are the alphanumeric characters (A-Z) and (0-9), the underscore (_), the dollar sign ($), and the following multinational __________________characters:_ÅÀÁÂÃÄÇÈÉÊËÌÍÎÏÒÓÔÕÖÙÚÛÜÆÑ@Øß._____ xiv Installation - Compaq Tru64 UNIX _________________________________________________________________ 1 _________________________________________________________________ Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System This chapter provides the necessary information to make your installation run smoothly. Before attempting the installation procedures in Chapter 2, you should complete the pre-installation requirements outlined here. 1.1 Release Notes Your documentation includes the BASEstar Open Server Release Notes. Read this document before installing and using the product. The release notes may contain information about changes to the application. Once you have installed the BASEstar Open Server software, you can also access the online release notes in the form of an ASCII text file by entering the following command: # more /usr/opt/bstbase320/doc/relnotes.txt (Compaq Tru64 UNIX) Your documentation may also include the BASEstar Open Release Notes Addendum or Read Before Installing letter. This letter provides information that is important for you to know before installing Compaq Tru64 UNIX, BASEstar Open or BASEstar CIMfast, and that may not be included either in management guides or primary release notes documents. If the Release Notes Addendum or Read Before Installing letter is listed on your BOM (Bill of Material), please check to see whether it contains information about BASEstar Open or BASEstar CIMfast. 1-1 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.2 License Registration 1.2 License Registration BASEstar Open Server includes support for the Compaq Tru64 UNIX License Management Facility (LMF). A License Product Authorization Key (License PAK) must be registered in the License Database (LDB) in order to use BASEstar Open Server on a newly-licensed node. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing BASEstar Open Server as an update on a node already licensed for this software, you have already completed the License PAK registration requirements. If you are installing pre-requisite or optional software along with BASEstar Open Server, review the PAK status and install the PAKs for any pre-requisite or optional software before you install BASEstar Open Server. To register a license under the Compaq Tru64 UNIX system, follow these steps before installing BASEstar Open Server: 1. Log in as superuser. 2. At the superuser prompt, edit an empty PAK template with the lmf register command and include all the information on your License PAK as follows: # lmf register Refer to the current BASEstar Open Server Version 3.2 Software Product Description (SPD) for complete information on possible licenses and associated PAKs. After you register your license, use the following lmf reset command to copy the license details from the License Database (LDB) to the kernel cache: # lmf reset For complete information on using the Compaq Tru64 UNIX License Management Facility, see the Compaq Tru64 UNIX Guide to Software Licensing or the lmf(8) reference page. 1-2 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.3 Checking the Media Software Distribution Kit 1.3 Checking the Media Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your BASEstar Open Server software distribution kit. The kit includes this installation guide and the CDROM optical disk for Alpha systems. Your distribution kit may also include a letter titled BASEstar Open Release Notes Addendum or Read Before Installing BASEstar Open. This letter provides information that is important for you to know before installing the product and may not be included in this installation guide or release notes. If you have this letter, please read it now. 1.4 BASEstar Open Server Subsets Table 1-1 lists and describes the subsets contained in the BASEstar Open Server software kit, together with their installation requirements. Table_1-1_BASEstar_Open_Server_Subsets_____________________ Subset_Name_________Description____________________________ BSTBASE320 BASEstar Open Server Version 3.2 base system. You must always install this subset. BSTMAN320 Manual pages for the BASEstar Open Server Application Programming Interface. BSTCONTRIB320 BIT/BOS software and documentation. DOUBASE310 DEComni Application Programming Interface. You need only install this subset if the Device Services MMS- modeled device connectivity is used. DOUMAN310 Manual pages for the DEComni Application Programming Interface. You can install this subset as desired (usually after installation of the DOUBASE310 subset). (continued on next page) 1-3 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.4 BASEstar Open Server Subsets Table_1-1_(Cont.)_BASEstar_Open_Server_Subsets_____________ Subset_Name_________Description____________________________ CIMfast BCFASE220 BASEstar CIMfast for Compaq Tru64 UNIX base components BCFMAN220 BASEstar CIMfast for Compaq Tru64 UNIX online documentation BCFDEV220 BASEstar CIMfast for Compaq Tru64 UNIX development option BCFDMQ220 BASEstar CIMfast for Compaq Tru64 UNIX DECmessageQ support BCFSQLORA220 BASEstar CIMfast for Compaq Tru64 UNIX ____________________ORACLE_SQL_support_____________________ 1.5 Installation Procedure Requirements Installing BASEstar Open Server and running the Installation Verification Procedure (IVP) on your Compaq Tru64 UNIX system takes approximately 5 to 20 minutes. 1.5.1 Checking Login Privileges You must be able to log in as superuser on the system where you are installing BASEstar Open Server. Only if you are logged in as superuser do you have sufficient privileges to install the BASEstar Open Server software. 1.5.2 Hardware Requirements To perform the installation, you require a minimum hardware configuration as spelled out in your BASEstar Open Server Software Product Description (SPD). The minimum hardware requirements are as follows: o A supported Alpha AXP processor (see the BASEstar Open Server Version 3.2 Software Product Description (SPD) for details) o A terminal o Sufficient free disk space (as described in Section 1.5.4) 1-4 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.5 Installation Procedure Requirements Check the SPD to see if there are further hardware requirements that apply to your particular application. 1.5.3 Software Requirements BASEstar Open Server Version 3.2 requires Compaq Tru64 UNIX Version 3.2C or higher. Future BASEstar Open Server releases may require higher versions of the operating system, as described in the online release notes or the Read Before Installing or Using Letter. The Software Product Description contains a complete list of pre-requisite and optional software and their required version numbers. If you are installing BASEstar Open Server on a system that is to perform the role of a PODB node, you must also install and start up the ORACLE 7.3.4 and 8.0 database, using the RDBMS, TPO and SQL*Plus options. You must load the subsets of the various software products required onto the system where you wish to install BASEstar Open Server, for example for Compaq Tru64 UNIX V3.52: Table_1-2_Required_Subsets_________________________________ Subset_Name_________Comment________________________________ OSFBASE350 Always required OSFPGMR350 Always required OSFCLINET OSFDCMT350 Required for installing the online ____________________reference_pages_only___________________ To check whether the subsets are loaded, do the following: 1. Log in to the system where you wish to install BASEstar Open Server. 2. Enter the following commands: # /usr/sbin/setld -i | grep OSFBASE350 # /usr/sbin/setld -i | grep OSFPGMR350 # /usr/sbin/setld -i | grep OSFDCMT350 1-5 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.5 Installation Procedure Requirements Check the displayed rows for the name of the relevant subset and any patches. The word "installed" appears in a row after the subset identifier when a subset is loaded. If the word "installed" does not appear (the second column in a row is blank), the subset or patch is not loaded. In this case, you must load the missing Compaq Tru64 UNIX software before installing BASEstar Open Server. 1.5.4 Determining Disk Space Requirements Table 1-3 lists the disk space requirements for loading BASEstar Open Server software subsets. They specify disk space requirements by file system for the convenience of those performing installations on systems where these file systems are mount points for different disk partitions. 1-6 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.5 Installation Procedure Requirements Table_1-3_Worksheet_for_Disk_Space_Requirements_(Kilobytes)[1]___ /usr Subset /var Subset_Title_______________Name________/___________/usr/opt____/opt BASEstar Open BSTBASE320 0 70,000 1,000 [1] DEComni DOUBASE310 4,340 36,000 160 DEComni Reference Pages DOUMAN310 0 140 80 _________________________________________________________________ ________________________BASEstar_CIMfast_________________________ BASEstar CIMfast for BCFASE220 0 4000 0 Compaq Tru64 UNIX Base Components BASEstar CIMfast for BCFMAN220 0 10 0 Compaq Tru64 UNIX Online Documentation BASEstar CIMfast for BCFDEV220 0 3800 0 Compaq Tru64 UNIX Development Option BASEstar CIMfast for BCFDMQ220 0 110 0 Compaq Tru64 UNIX DECmessageQ Support BASEstar CIMfast for BCFSQLORA220[1] Compaq Tru64 UNIX ORACLE SQL Support _________________________________________________________________ Totals:________________________________4,340_______114,060_____1,240 ____________________ [1] If you are using the ORACLE database, BASEstar Open checks that there are 50Mb of disk space in the /usr/tmp directory before running the IVP (see Section 2.3.1). 1-7 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.5 Installation Procedure Requirements Using these tables, calculate the total values for the subsets that you plan to load in each system. Compare the space required for subsets with the free space currently on the disks where BASEstar Open Server files will reside. 1.5.5 Increasing the Available Disk Space for BASEstar Open Server Installation The BASEstar Open Server installation procedure creates the following directories and loads files into subordinate directories: /usr/opt/bstbase320 /usr/var/opt/bstbase320 If the bstbase320 node in the previous paths already exists, the installation procedure uses it; otherwise, it creates the node. If you find that there is insufficient disk space for the BASEstar Open Server subsets, and there is space available on other disks or disk partitions for your system, ask the system manager to take the necessary action. 1.6 Backing Up Your System Disk COMPAQ recommends that you back up your system disk before installing any software. For details of how to perform a system disk backup, refer to your Compaq Tru64 UNIX documentation. 1.7 Stopping the Installation You can stop the installation procedure any time by using /. However, files created up to this point are not deleted automatically. You must delete these files interactively. Appendix A lists the files and directories created during the installation procedure. 1-8 Preparing to Install BASEstar Open Server on a Compaq Tru64 UNIX System 1.8 Error Recovery 1.8 Error Recovery If errors occur during the installation, the system displays failure messages. If the installation fails due to insufficient disk space, a message appears. For example, if the disk space lack is detected while installing the BSTBASE320, the following message is displayed: There is not enough file system space for subset BSTBASE320 BASEstar Open (BSTBASE320) will not be loaded. Errors may occur during the installation if: o The operating system version is incorrect o The pre-requisite software version is incorrect o The system parameter values for successful installation are insufficient. For descriptions of error messages generated by these conditions, see the Compaq Tru64 UNIX documentation on system messages, recovery procedures, and Compaq Tru64 UNIX software installation. For information on system software requirements, see Section 1.5.3. If an error occurs while using BASEstar Open Server and you believe the error is caused by a problem with the product, take the appropriate action as described in Section 2.4. 1-9 2 _________________________________________________________________ Installing BASEstar Open Server on a Compaq Tru64 UNIX System This chapter describes how to: o Install BASEstar Open Server on a Compaq Tru64 UNIX system o Run the Installation Verification Procedure (IVP) o Remove BASEstar Open Server from a Compaq Tru64 UNIX system Before starting the installation, read Chapter 1, which describes general options and requirements for installing the product. This installation procedure allows you to install BASEstar Open Server locally. In a local (node-specific) installation, the system on which you install the product uses its own disks to run it. The installation procedure loads BASEstar Open Server files onto the disks that belong to the system where you perform the installation. When you run BASEstar Open Server, its executable files are mapped into memory on the same system. 2.1 Installing CD-ROM Consolidated Distribution Media Start the installation procedure as follows: 1. Mount the media on the appropriate disk drive. 2. Log in as superuser (login name root) to the system where you are installing BASEstar Open Server. 3. Make sure that you are at the root (/) directory by entering the following command: # cd / 2-1 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.1 Installing CD-ROM Consolidated Distribution Media 4. Specify the /mnt directory to be the mount point for the distribution file system on the drive. If your drive is rz4, enter the following command: # mount -dr /dev/rz4c /mnt 5. Enter a setld command that specifies the load function (-l) and identifies the directory in the mounted file system where BASEstar Open Server subsets are located. For example, if the directory location for these subsets is /mnt/BSTBASE320, enter the following command: # setld -l /mnt/BSTBASE320 2.2 Responding to Installation Procedure Prompts This section explains the installation procedure prompts. 2.2.1 Selecting Subsets After you enter the setld command for local (node-specific) installations, the installation procedure displays the names of the BASEstar Open Server subsets and asks you to specify the subsets that you want to load: Copyright Digital Equipment Corporation. 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 2-2 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.2 Responding to Installation Procedure Prompts 1 BASEstar Open Server V3.2 2) BASEstar Open V3.2 Reference Pages 3) CIMfast Base Components 4) CIMfast DECmessageQ Support 5) CIMfast Development Option 6) CIMfast On-line Manual Pages 7) CIMfast Oracle SQL Support 8) DASware - Common Run-Time Environment 9) DASware - Services for OSI 10) DASware - Services for RS-232 11) DASware - Services for TCP/IP 12) DASware - Services for X25 Or you may choose one of the following options: 13) ALL of the above 14) CANCEL selections and redisplay menus 15) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 1 2 Choices (for example, 1 2 4-6):1 2 If you specify more than one number at the prompt, separate each number with a space, not a comma. Next, the script lets you verify your choice. For example, if you enter 5 in response to the previous prompt, you will see the following display: You are installing the following optional subsets: BASEstar Open Server V3.2 BASEstar Open V3.2 Reference Pages Is this correct? (y/n): y If the displayed subsets are not the ones you intended to choose, enter n. In this case, the subset selection menu is again displayed, and you can correct your choice of optional subsets. If the displayed subsets are those you want to load, enter y. 2-3 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.2 Responding to Installation Procedure Prompts 2.2.2 Monitoring Displays During the Subset Loading Process The procedure displays a message that the installation is starting: Checking file system space required to install selected subsets: File system space checked OK. Installation procedure for: The installation procedure continues and it displays the time required for the full installation The installation will complete in 5 to 15 minutes depending on processor type The installation procedure continues. If, during the course of the installation, you encounter errors from the setld utility, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take. If the verification process fails, consult the /var/adm /smlogs/fverify.log file for information that may help you diagnose the problem. The final step of the installation procedure is signalled by the following prompt: To start up BASEstar Open Server V3.2 on each system bootstrap, you should create a link in the /sbin/rc3.d directory to the file /sbin/init.d/bstbaseboot. Do you want to create it now? (y/n) [y]: If you answer y, the installation procedure creates the bstbaseboot file in the /var/optbstbase320/etc directory. BASEstar Open Server starts up the BASEstar Open Node services by executing bstr_node_start during the normal bootstrap procedure. To stop BASEstar Open, it executes bstr_node_shut during the system shutdown procedure. 2-4 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.2 Responding to Installation Procedure Prompts 2.2.3 Running the IVP After the message that notifies you that BASEstar Open Server has been installed successfully, the procedure displays the following prompt which allows you to start the IVP: Do you want to run the BASEstar IVP now ? [yes] It is recommended that you run the IVP to verify the installation. You can either run it during installation by answering yes to the above question, or later, as explained in Section 2.3. 2.2.4 Setting Up and Starting the BASEstar Open Server Environment After installing BASEstar Open Server, you must execute a series of procedures which set up and start Nodes and Realms. To make this task easier, the installation procedure displays the following prompts which allow you to set up and start the BASEstar Open Server environment: To configure this node, you should execute the script bstr_node_setup (/usr/var/opt/bstbase320/etc/bstr_node_setup). Do you want to execute it now? (y/n) [y]: If you answer y, the installation procedure sets up BASEstar Open on the local node by executing the bstr_ node_setup procedure. To start up BASEstar Open Server V3.2 on this node, you should execute the script (/usr/var/opt/bstbase320/etc/bstr_node_start). Do you want to execute it now? (y/n) [y]: If you answer y, the installation procedure starts up BASEstar Open on the local node by executing the bstr_ node_start procedure. For a full explanation of the bstr_ node_setup and bstr_node_start procedures, refer to Part II of this guide. 2-5 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.3 The Installation Verification Procedure 2.3 The Installation Verification Procedure Once you have completed BASEstar Open installation and any additional post-installation operations, it is advisable to run the Installation Verification Procedure (IVP) independently to verify that the software is available on your system. In order to verify the installation, the BASEstar Open Server IVP: 1. Checks that: - All kit files and directories are present and correct - A valid license is correctly registered - The BASEstar Open Server node on which you are operating has been set up and started. If this is not the case, it performs both these operations. 2. Sets up and starts the BSTR_IVP Realm on the Node on which it is executed 3. Loads the appropriate Application Management Services configuration for the BSTR_IVP Realm. 4. It performs the following operations on the BSTR_IVP Realm: - Starts Data Services and Event Services servers - Creates objects in the Domains managed by the above servers - Shuts down the Data Services and Event Services servers. 5. If it is necessary to verify the PODB capabilities (see Section 2.3.1), the IVP performs the following operations: - Creates the BSTR_IVP/BSTR_IVP ORACLE login/password for the BSTR_IVP Realm - Starts the Database Services server for the BSTR_IVP Realm - Creates the object definitions for the BSTR_REALM Realm in the PODB 2-6 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.3 The Installation Verification Procedure - Generates a snapshot configuration and tries to start up the Data & Device Services server and the Event Services server, before performing operations on the object - Shuts down the Data & Device Services server and the Event Services server - Shuts down the Database Services server and deletes the BSTR_IVP/BSTR_IVP ORACLE login/passwords. 6. Shuts down the node in an orderly fashion (if started by the IVP). 7. Resets the node in an orderly fashion (if set up by the IVP). The IVP procedure execution takes about 5 minutes (if your system is not a PODB Node) or 20 minutes (if your system is a PODB Node). 2.3.1 Prerequisites and Constraints Execution of the IVP is subject to the following prerequisites and constraints: o A valid BASEstar Open Server license has been registered o The account from which you run the IVP must have superuser status. o If you wish to verify the PODB feature on the node, ensure that the selected database has been started up successfully before running the IVP. For further details, refer to the product-specific documentation. o If you run the IVP procedure before setting up the node, BASEstar Open Server checks that there are 50Mb of disk space in the /usr/tmp directory. If this space is not available, the IVP does not verify the capabilities of the PODB database. o The resources used are as follows: - The IVP automatically creates (and deletes after use) the BSTR_IVP Realm and, if verification of the PODB capabilities must also be performed, the BSTR_ IVP/BSTR_IVP ORACLE login/password. Therefore, you cannot create a Realm and an ORACLE login/password with these names. 2-7 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.3 The Installation Verification Procedure - The IVP uses the UDP port numbers from 14073 to 14078. o Note that, during execution, the IVP modifies and restores the /etc/services system file. 2.3.2 Running the Installation Verification Procedure After installing BASEstar Open Server, it is recommended that you run the Installation Verification Procedure (IVP) independently to verify that the software is correctly installed and ready to use on your system. You might also want to run the IVP after a system failure to be sure that users can access BASEstar Open Server. To run the IVP, enter the following command: # setld -v BSTBASE320 Each time you run the IVP, it creates the /tmp/bstr_ivp_.log and /tmp/ivp_bstrlogfiles log files. The /tmp/ivp_bstrlogfiles file contains a copy of the Node and Realm BASEstar Open Server log files generated during IVP execution (see Part II for details). 2.4 Getting Help and Reporting Problems If an error occurs while you are using BASEstar Open Server, and you believe the error is the result of a problem associated with the product, take one of the following actions: o If you have a basic or COMPAQ support Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you purchased BASEstar Open Server within the last 90 days and you think the problem is caused by a software error, you can submit an SPR. 2-8 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.4 Getting Help and Reporting Problems If you submit an SPR, please take the following steps: 1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. Include the description and version number of BASEstar Open Server that you were using. Demonstrate the problem with specific examples. 2. Reduce the problem to as small a size as possible. 3. Remember to include listings of any command files, include files, relevant data files, and so forth. 4. Provide a listing of the program. 5. If the program is longer than 50 lines, submit a copy of it on machine-readable media (floppy diskette or magnetic tape). If necessary, also submit a copy of the program library used to build the application. 6. Report only one problem per SPR. This will facilitate a faster response. 7. Mail the SPR package to COMPAQ. Experience shows that many SPRs do not contain enough information to duplicate or identify the problem. Concise, complete information helps COMPAQ give accurate and timely service to software problems. If you find an error in the BASEstar Open Server documentation, send an electronic mail message to manufacturing@compaq.com. 2.5 Deleting BASEstar Open Server From Your System To remove a version of BASEstar Open Server from your system, delete each subset that you previously installed. To delete subsets, follow these steps: 1. Log into a superuser account(login name root). 2. Make sure you are at the root directory (/) by entering the following command: # cd / 2-9 Installing BASEstar Open Server on a Compaq Tru64 UNIX System 2.5 Deleting BASEstar Open Server From Your System 3. Enter the following setld commands: # setld -i | grep BSTBASE320 # setld -i | grep DOUBASE310 # setld -i | grep DOUMAN310 4. Look for the word "installed" in the listing produced, then delete the installed subsets. For example: # setld -d BSTBASE320 # setld -d DOUBASE310 # setld -d DOUMAN310 2.6 Using the Startup Files Created During the Installation BASEstar CIMfast users must execute the BASEstar CIMfast setup file when logging on to the system. The setup command depends on the user's shell: o Sh or Sh5 shell # ./etc/bcf_setup.sh o C shell # source /etc/bcf_setup.csh 2-10 3 _________________________________________________________________ Installing BASEstar CIMfast This chapter describes how to install BASEstar CIMfast, an application development environment for creating real-time event-driven applications, on a Compaq Tru64 UNIX system. Before attempting to install BASEstar CIMfast, make sure that you have already installed BASEstar Open as described in Chapter 2. This installation procedure loads BASEstar CIMfast for Compaq Tru64 UNIX onto the disks that belong to the system where you perform the installation. When you run BASEstar CIMfast, BASEstar Open maps its executable files into memory on the same system. You can install BASEstar CIMfast in a number of ways: o Locally o From disk o From CD-ROM 3.1 Starting the Installation Procedure 3.1.1 Using CD-ROM Consolidated Distribution Media Start the installation procedure as follows: 1. Mount the media on the appropriate disk drive. 2. Log in as superuser (login name root) to the system where you are installing BASEstar CIMfast. Make sure that BASEstar Open Server is up and running before you execute the BASEstar CIMfast IVP. 3-1 Installing BASEstar CIMfast 3.1 Starting the Installation Procedure 3. Enter the following command to ensure that you are at the root (/) directory: # cd / 4. Specify the /mnt directory as the mount point for the distribution file system on the drive. If your drive is rz4, enter the following command: # mount -r /dev/rz4l /mnt 5. Identify the directory in the mounted file system where BASEstar CIMfast subsets are located and enter a setld command, specifying the directory with the load (-l flag). For example, to load BASEstar CIMfast subsets onto a system, enter the following command: # # setld -l /mnt/your_mnt_point/BCF220 See Section 3.2 to continue the installation. 3.2 Responding to Installation Procedure Prompts This section describes the installation procedure prompts and displays. 3.2.1 Selecting Subsets When you enter the setld command, the installation procedure: o Displays the names of the BASEstar CIMfast for Compaq Tru64 UNIX subsets o Asks you to specify the subsets that you want to load: *** Enter Subset Selections *** The subsets listed below are optional: 1 CIMfast Base Components 2) CIMfast Development Option 3) CIMfast On-line Manual Pages 4) CIMfast DECmessageQ Support 5) CIMfast SQL Oracle Support 6) All of the Above 7) None of the Above 8) Exit without installing subsets 3-2 Installing BASEstar CIMfast 3.2 Responding to Installation Procedure Prompts Enter your choice(s): If you specify more than one number at the prompt, separate each number with a space, not a comma. o Allows you to verify your choice. For example, if you enter 6 in response to the previous prompt, the following is displayed: You are installing the following subsets: CIMfast Base Components CIMfast Development Option CIMfast On-line Manual Pages CIMfast DECmessageQ Support CIMfast SQL Oracle Is this correct? (y/n): In response to the prompt, enter: o n, if the subsets displayed are not the ones you intend to choose. If this is the case, the procedure redisplays the subset selection menu so that you can correct your choice of optional subsets. o y, if the subsets displayed are the ones you want to load. 3.2.2 Monitoring Displays During the Subset Loading Process The procedure displays a message that the installation is starting. Refer to Section 3.3 for information regarding the postinstallation requirements specified in the final informational messages from the procedure. If you encounter errors from the setld utility during the course of the installation, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take. If the verification process fails, the information in the file /usr/var/adm /smlogs/fverify.log may help you to diagnose the problem. 3.3 Completing the Installation 3-3 Installing BASEstar CIMfast 3.3 Completing the Installation 3.3.1 Running the Installation Verification Procedure After installing BASEstar CIMfast, you must run the Installation Verification Procedure (IVP) independently to verify that the software is available on the system. To run the IVP for BCFDEV, make sure that BASEstar Open Server is up and running. To run the IVP after an installation, enter the following command: # setld -v BCFBASE220 If you installed the BASEstar CIMfast for Compaq Tru64 UNIX Development Option, you can also run the IVP for this subset. The Development Option IVP builds the BASEstar CIMfast example programs. Make sure that you run this IVP from the root account, otherwise the IVP will not build the example programs, and the users will be unable to execute them. To run the Development Option, enter the following command: # setld -v BCFDEV220 It is also recommended that you run the IVP after a system failure to make sure that users can access BASEstar CIMfast. 3.3.2 Using the Startup Files Created During the Installation BASEstar CIMfast users must execute the BASEstar CIMfast setup file when logging on to the system. The command to use depends on the user's shell: o Sh or Sh5 shell # ./etc/bcf_setup.sh o C shell # source/etc/bcf_setup.csh 3-4 Part II _________________________________________________________________ Environment Management This section contains a series of chapters that describe the procedures and utilities that allow you to manage BASEstar Open Server on your Compaq Tru64 UNIX system. ________________________ Note ________________________ The management procedures described in this section are also valid for BASEstar Open Client on Compaq Tru64 UNIX platforms. ______________________________________________________ 4 _________________________________________________________________ Introduction to Environment Management An application consists of a set of application components; that is, user-written programs and BASEstar Open-supplied servers running on a distributed system configuration, including various types of computers, plant devices and cables. To provide users with transparent access to BASEstar Open objects, regardless of their physical location in the distributed system, you must prepare your BASEstar Open environment. For example, you must set up and start up Nodes and Realms. 4.1 Environment Management Overview This section provides an overview of the BASEstar Open environment management operations. Setting Up BASEstar Open To set up BASEstar Open, you must set up Nodes and Realms. Setting up a Node involves creating the static resources (directories, files and environment-specific components) that enable a system of any supported platform to function as a BASEstar Open Node. Setting up a Realm involves creating directories and files that contain object definitions within a Realm. Starting Up BASEstar Open To make the BASEstar Open environment available to users, you must start up Nodes and Realms. Shutting Down BASEstar Open To make BASEstar Open unavailable to users, you must shut down Nodes and Realms in an orderly fashion. Unsetting BASEstar Open To unset BASEstar Open, you must delete Realm and Node directories and files, and the database containing the Realm object definitions. 4-1 Introduction to Environment Management 4.1 Environment Management Overview Monitoring BASEstar Open At any time, you can establish whether the BASEstar Open environment has been set up and started up successfully on Nodes and Realms. For example, you can display the list of the Realms available (that is, started up) on a given Node. 4.2 Environment and Application Components Relationship Once you have completed the setup and startup operations for the BASEstar Open environment, you can request the Application Management Services to start up, monitor, and shut down the application components (that is, user-written programs and BASEstar Open-supplied servers). When you shut down BASEstar Open, you must first shut down the application components and then the environment components. You can shut down the application components using, for example, the Application Management Services. The BASEstar Open Command Language Interface describes how to configure, start up and shut down the application components using Application Management Services features. Chapter 5 describes the procedures that you must use to set up, start up, shut down and unset the environment components. 4.3 BASEstar Open Environment Components The components of a BASEstar Open environment are: o Nodes o PODB Nodes o Realms In this context, Nodes and Realms are not considered as objects, but as a set of environment components that make Nodes and Realms available in the multi-Node, multi- platform, distributed BASEstar Open environment. 4-2 Introduction to Environment Management 4.3 BASEstar Open Environment Components 4.3.1 Nodes A BASEstar Open Node is a computer of any of the supported platforms on which BASEstar Open has been installed and set up. To make a Node available in the BASEstar Open environment, you must start up its components by executing the bstr_node_start command. The following are Node-specific components: o Log Services o Watchdog o Name Service Each of these components is described in the sections that follow. See also Appendix D for a list of the processes that implement components on each platform. Log Services On each Node, the Log Services server collects log information from Node-specific environment components and from the environment components of the Realms that are started up on each Node. The Log Services server writes the collected information to the appropriate log files. This information is valuable for monitoring the behavior of environment components and also facilitates troubleshooting activity when necessary. For information about Log Services features and functions, and about how to display and manage log files, refer to Chapter 10 and Chapter 11. Watchdog The Watchdog is a background task that BASEstar Open starts when you execute the bstr_node_start procedure. The Watchdog component of a Node performs periodic checks on the availability of the other Nodes in a BASEstar Open environment. If a Node suddenly becomes unavailable, or if a BASEstar Open application running on one of the configured Nodes terminates abnormally, the Watchdog notifies the relevant components. 4-3 Introduction to Environment Management 4.3 BASEstar Open Environment Components Name Service The Name Service component of a Node makes internal symbols and their values unique and globally available to BASEstar Open. The Name Service consists of: o A Name Service client process that must be active on each Node o A Name Service server that must be active on one Node of the distributed BASEstar Open multi-Node environment. The Name Service server is fundamental to the availability of the BASEstar Open environment. If the server fails, the BASEstar Open environment becomes unavailable. To avoid this, a redundancy mechanism is provided, based on a primary and a secondary copy of the Name Service server. When the Nodes are started up, the primary copy is activated on the specified Node and becomes the current Name Service server. At the same time, BASEstar Open activates the secondary copy in stand-by mode on another Node. If the current Name Service server fails or becomes unavailable for any reason, BASEstar Open activates the secondary copy, which thus becomes the current Name Service server. The Node setup procedure allows you to specify on which Nodes BASEstar Open activates the primary and secondary copies of the Name Service server. 4.3.2 PODB Nodes When you set up the BASEstar Open environment, you can choose which BASEstar Open Nodes you want to act as PODB Nodes (that is, contain the PODB object definitions). However, bear in mind the following considerations: o You can only designate ONE Node to act as the PODB Node for a given Realm o It is possible to designate a given Node as the PODB Node for different Realms. The example in Section 4.3.5 illustrates that NODE_DB has been set up as the PODB Node for both MY_REALM and TS_REALM. Alternatively, you could set up NODE_DB as the PODB Node for MY_REALM, and NODE1 (or NODE2) as the PODB Node for TS_REALM. 4-4 Introduction to Environment Management 4.3 BASEstar Open Environment Components BASEstar Open supports various databases for the storage of PODB object definitions, depending to the native operating system. On Compaq Tru64 UNIX Nodes, you can use an Oracle database. Refer to Section 4.3.3 for hints about managing the PODB on an ORACLE database. When you start up your environment, you must also start up the Database Services server on the PODB Node of each Realm that requires object definitions to be stored in the PODB. 4.3.3 Managing the PODB on an ORACLE Database The list that follows contains a series of hints about how to manage a PODB on an ORACLE database: o ORACLE_HOME environment variable Make sure that the ORACLE_HOME environment variable points to the login directory of the ORACLE account. o Modifying ORACLE resources If you create several databases for different Realms on the same Node, some ORACLE resources may be insufficient. If this is the case, run bstr_realm_setup_db: this command displays ORACLE error messages that indicate which resources you need to increase. To increase resources, follow these steps: 1. Edit the $ORACLE_HOME/dbs/init$ORACLE_SID.ora file 2. Shut down ORACLE processes 3. Restart ORACLE processes by supplying the name of the above file as a parameter file The bstr_node_setup command creates $ORACLE_HOME/dbs /init$ORACLE_SID.ora with default values. 4.3.4 Realms User-written application processes and BASEstar Open- supplied servers are the application components of each Realm. These components are managed directly by the end- users through the Application Management Services or from the command interpreter. 4-5 Introduction to Environment Management 4.3 BASEstar Open Environment Components Before starting up Realm application components, you must start up the Realm environment components on the appropriate Node(s). When you start up a Realm on a Node, BASEstar Open activates the following environment components: o Communication Service o Global Object Services server o Application Management Services server o Database Services server o PC Communication server BASEstar Open activates the per Node Realm-specific components when you execute the bstr_realm_start command. The sections that follow provide a brief description of each component. See also Appendix D for a list of the processes that implement components on each platform. Communication Service The Communication Service allows transparent communication between application and environment components of a Realm. This communication is independent of the number of Nodes on which the Realm has been started up. For example, the Communication Service features allow you to access a Data_Point (through an API or a CLI service request) without needing to know the physical location of the Data & Device Services server that makes the Data_Point available. Global Object Services Server Global Object Services servers make global objects available in a Realm. Global objects are those that already exist before servers that use them can be started up. For example, a Data & Device Services server must already find the associated Domain in the VODB, otherwise it could not create objects in the VODB. Global objects also include those objects that must be globally available in the Realm to all the other servers. For example, the same Datatype could be referred to by Event Services and Data & Device Services objects, and therefore it must be available in the Realm, regardless of whether any other server is available. 4-6 Introduction to Environment Management 4.3 BASEstar Open Environment Components A Global Object Services server is started up on each Node where a Realm is started up. This allows distributed management of the global objects; all the Global Object Services servers of a distributed Realm work together to make available to any user or to other servers all the same global objects independently of their location. Application Management Services Server When you start up a Realm on a given Node, the Application Management Services server is also activated and makes the Application Management Services objects and features available on that Node. This enables users at any Realm Node to request services such as executing, suspending, resuming and terminating Activities. As soon as you start up the Realm on other Nodes, an Application Management Services server is activated on each of them, thus allowing distributed management of the Realm application components. For example, you can execute an Activity on a Realm Node from any Node of the Realm. As another example, if a Realm Node fails, the Application Management Services servers running on the other Nodes of the Realm cooperate to restart the Realm application components on the Node(s) specified by the user in the configuration. To provide such dynamic and distributed services, the Application Management Services servers of a Realm continuously notify each other of their respective availability and operations in progress. PC Communication Server One PC Communication server is activated on a Node when a Realm is started up on that Node. BASEstar Open applications running on client Nodes can operate in transparent mode on the objects of a Realm through any PC Communication server active for that Realm. This is independent of the Realm Node on which the servers that make these objects available have been started. See the BASEstar Open Client Inst. & Management Guide for details of how to install, configure and manage BASEstar Open Client on PC platforms. 4-7 Introduction to Environment Management 4.3 BASEstar Open Environment Components Database Services Server It is recommended that you activate a Database Services server on the Realm PODB Node. You only need to start up a Database Services server for Realms that require object definitions to be stored in the Permanent Object Database. The Database Services server is activated when you execute the bstr_realm_start_db command. 4.3.5 Sample Environment Configuration Figure 4-1 is an example of a BASEstar Open environment that consists of three systems interconnected through a LAN. To make this sample environment available, you must: 1. Set up NODE_DB, NODE1 and NODE2. In the example, NODE_DB acts as the PODB Node for both MY_REALM and TS_REALM. 2. Start up each Node. 3. Set up MY_REALM on each Node. 4. Set up TS_REALM on each Node. 5. Start up the environment components of MY_REALM on each Node where MY_REALM must be available (that is, on all the Nodes). 6. Do the same for TS_REALM, but on NODE_DB and NODE1 only. 7. On the PODB Node, start up a Database Services server for each Realm. In Figure 4-1, it is assumed that NODE_DB is a Compaq Tru64 UNIX system capable of acting as the PODB Node (ORACLE is the selected database). It is also assumed that NODE1 is a OpenVMS system and NODE2 is a Compaq Tru64 UNIX system. However, there are numerous alternatives to this configuration; for example, you could also have MS Windows client Nodes. 4-8 Introduction to Environment Management 4.3 BASEstar Open Environment Components Figure 4-1 Sample BASEstar Open Environment NODE_DB +-----------------------------+ | MY_REALM | | +-----------+-------+ | | | | | | PODB | | Realm- | DB | | +-----------------+ | | Specific | Server| | | | | | Environment | | | +------------+ | | | Components| | +--------| | my_realm | | | +-----------+-------+ | | +------------+ | | TS_REALM | | | | +-----------+-------+ | | +-------------+ | | | | | | | | test_realm | | | | Realm- | DB | | | +-------------+ | | | Specific | Server| | +-----------------+ | | Environment | | | | Components| | | | +-----------+-------+ | | Node-Specific | | Environment Components | +-----------------------------+ || LAN ================================================================ NODE1 || NODE2 || +-----------------------------+ +-----------------------------+ | MY_REALM TS_REALM | |MY_REALM | |+------------+ +------------+| |+------------+ | ||Realm- | |Realm- || || Realm- | | ||Specific | |Specific || || Specific | | ||Environment | |Environment || ||Environment | | ||Components | |Components || ||Components | | || | | || || | | |+------------+ +------------+| |+------------+ | | Node-Specific | | Node-Specific | | Environment Components | | Environment Components | +-----------------------------+ +-----------------------------+ 4-9 5 _________________________________________________________________ Environment Management Procedures This chapter describes the procedures that allow you to manage the BASEstar Open environment. You must perform the operations in the order prescribed: 1. Set up Nodes, Realms and databases on PODB Nodes. A setup operation creates files and directories for the corresponding component. 2. Start up Nodes, Realms and Realm PODB servers. A startup operation runs the system processes that constitute the active part of the given component. 3. Shut down Nodes, Realms and Realm PODB servers. A shutdown operation terminates the system processes in an orderly fashion. 4. Unset Realms, Nodes and Realm PODB servers. An unset operation deletes files and directories for a specified component. You must set up a Realm before you can start it up. However, it is not necessary to set up all the components in order to start up just one of them. The BASEstar Open environment management procedures described in this chapter refer to the BASEstar Open environment commands documented in Chapter 6. Before issuing any of these commands, read the command description given in Chapter 6, which also highlights pre-requisites and constraints. 5-1 Environment Management Procedures 5.1 Setup Procedures 5.1 Setup Procedures This section describes the procedures that you must use to set up Nodes and Realms. Execute the procedure described in Section 5.1.1 for each Node that you wish to set up, and the procedure described in Section 5.1.2 for all the Realms in your environment. For information regarding the parameters used by the procedures described in this chapter, refer to the relative man pages. 5.1.1 Setting Up a Node To create Node-specific directories and configuration files, use the bstr_node_setup command, located in /usr /opt/bstbase320/etc/. This command allows you to select the Node on which to activate the Name Service server. If you use the advanced bstr_node_setup option, it allows you to select the BASEstar Open working directory root database, and the communication configuration parameters. When you set up a Node, BASEstar Open usually asks you to specify just the names of the Nodes on which you want it to start the primary and secondary copies of the Name Service servers. On the PODB Node, it also prompts you to provide details of the selected database. The bstr_node_setup command also creates the bstrusers.* command files, for setting up installation-dependent global variables (see Appendix B). 5.1.2 Setting Up a Realm You must set up a Realm for each Node on which the Realm is to be available, as explained in Section 5.1.2.1. If you wish to store Realm object definitions in the PODB, create a database for the Realm on the PODB Node (see Section 5.1.2.2). 5.1.2.1 Setting Up a Realm on a Node The bstr_realm_setup_node command allows you to create the directories and files that are required at run-time by the internal Realm components started on the Node. 5-2 Environment Management Procedures 5.1 Setup Procedures 5.1.2.2 Setting Up the Realm Database on the PODB Node To create a database for a Realm, run the bstr_realm_setup_ db command on the PODB Node. 5.1.3 Setting Up the Sample Environment The following command sequence demonstrates how to set up the BASEstar Open environment for the sample configuration illustrated in Figure 4-1. Note that these instructions cause BASEstar Open to activate the primary copy of the Name Service server on NODE2 and the secondary copy on NODE1. You can set up the Nodes shown in this example in any order. For details of the rules governing the execution of environment commands, refer to Chapter 6. Setting Up the Nodes Log in as SYSTEM on NODE1 and issue the following command: $ /usr/opt/bstbase320/etc/bstr_node_setup -l /usr/opt/bstbase320 -y ... LNS.Server_Node [NODE1]: NODE2 LNS.Server_Node_2[]: NODE1 DB.node_is_cfg_server ?: FALSE ... Execute the following command on NODE2: $ /usr/opt/bstbase320/etc/bstr_node_setup -l /usr/opt/bstbase320 -y ... LNS.Server_Node [NODE2]: NODE2 LNS.Server_Node_2[]: NODE1 DB.node_is_cfg_server ?: FALSE ... Execute the following command on NODE_DB: $ /usr/opt/bstbase320/etc/bstr_node_setup -l /usr/opt/bstbase320 -y ... LNS.Server_Node [NODE_DB]: NODE2 LNS.Server_Node_2[]: NODE1 DB.node_is_cfg_server ?: TRUE Pathname of your ORACLE kit (II_SYSTEM): /usr/kits/oracle ... 5-3 Environment Management Procedures 5.1 Setup Procedures Setting Up the MY_REALM Realm To set up the MY_REALM Realm on NODE1, NODE2 and NODE_DB, execute the appropriate setup file for your shell on each Node: $ . /etc/bstrusers.sh (Sh or Sh5 shell) $ source /etc/bstrusers.csh (C shell) Then issue the following command on NODE1 (you can set up the Realms on the Nodes in any order): $ bstr_realm_setup_node MY_REALM Then issue the following command on NODE2: $ bstr_realm_setup_node MY_REALM Execute the following commands on NODE_DB: $ bstr_realm_setup_node MY_REALM $ bstr_realm_setup_db MY_REALM Setting Up the TS_REALM Realm To set up the TS_REALM Realm on NODE1 and NODE_DB, issue the following command on NODE1: $ bstr_realm_setup_node TS_REALM The setup operations for TS_REALM are similar to those performed for MY_REALM. Note that TS_REALM has not been set up on NODE2. This is because there was no request for the Realm to be available on this Node. Execute the following commands on NODE_DB: $ bstr_realm_setup_node TS_REALM $ bstr_realm_setup_db TS_REALM 5-4 Environment Management Procedures 5.2 Startup Procedures 5.2 Startup Procedures This section describes the procedures that allow you to start up a Node or a Realm in the BASEstar Open environment. You must execute the procedure described in Section 5.2.1 for each Node that you wish to start up. Execute the procedure described in Section 5.2.2 for each Realm that you wish to make available in your environment. 5.2.1 Starting Up a Node The bstr_node_start command activates the node-specific components, and checks for license and environment integrity on the Node. Note that the started Nodes only become available when you start up the Node on which the Name Service server is activated. 5.2.2 Starting Up a Realm Start up the Realm on each Node on which you want the Realm to be available (see Section 5.2.2.1). You must also start up the Database Services server process (allowing access to the Realm database) on the PODB Node (see Section 5.2.2.2). 5.2.2.1 Starting Up a Realm on a Node The bstr_realm_start_node command starts up Realm-specific components on the Node on which it is executed. It also checks for license and environment integrity on the Node. ________________________ Note ________________________ BASEstar Open components that are active on a Node cannot access components that are active on other Nodes until you start up the Node where the Name Service server resides. ______________________________________________________ 5.2.2.2 Starting Up the Database Server for a Realm on the PODB Node You must only use the bstr_realm_start_db command on the PODB Node. This command activates the Database Services server for the specified Realm. 5-5 Environment Management Procedures 5.2 Startup Procedures 5.2.3 Starting Up the Sample Environment The command sequence in this section demonstrates how to start up the BASEstar Open environment for the sample configuration illustrated in Figure 4-1. Starting Up the Nodes You can start up the sample Nodes in any order. Execute the following command on NODE1: $ bstr_node_start Execute the following command on NODE2: $ bstr_node_start Execute the following command on NODE_DB: $ bstr_node_start Starting Up the MY_REALM Realm To start up MY_REALM on NODE1, NODE2 and NODE_DB, execute the command sequence illustrated below (you can start up the Realm on the Nodes in any order). First, you must set up the MY_REALM Realm on NODE1, NODE2 and NODE_DB. Execute the appropriate setup file for your shell on each Node: $ . /etc/bstrusers.sh (Sh or Sh5 shell) $ source /etc/bstrusers.csh (C shell) Then issue the following command on NODE1: $ bstr_realm_start_node MY_REALM Execute the following command on NODE2: $ bstr_realm_start_node MY_REALM Execute the following commands on NODE_DB: $ bstr_realm_start_node MY_REALM $ bstr_realm_start_db MY_REALM If you execute the above command sequence correctly, BASEstar Open makes the MY_REALM Realm available. At this point, you can use, for example, the Application Management Services to start up the Realm application components as explained in the BASEstar Open Command Language Interface. 5-6 Environment Management Procedures 5.2 Startup Procedures Starting Up the TS_REALM Realm To start up TS_REALM on NODE1 and NODE_DB, execute the following command on NODE1: $ bstr_realm_start_node TS_REALM Execute the following commands on NODE_DB: $ bstr_realm_start_node TS_REALM $ bstr_realm_start_db TS_REALM The startup operations for TS_REALM are similar to those performed for MY_REALM. Note that TS_REALM has not been started up on NODE2, since there was no request for the Realm to be available on this Node. 5-7 Environment Management Procedures 5.3 Shutdown Procedures 5.3 Shutdown Procedures This section describes the procedures that allow you to shut down a Node and a Realm in the BASEstar Open environment. You must execute the procedure described in Section 5.3.1 for each Realm that you wish to be make unavailable in your environment. You must also execute the procedure described in Section 5.3.2 for each Node to be made unavailable in your environment. 5.3.1 Shutting Down a Realm To shut down a Realm in an orderly fashion, you must first shut down the application components. To do so, use either the command interpreter on your platform or the Application Management Services. You must then shut down the active Database Services server on the Realm PODB Node (see Section 5.3.1.1). Finally, you must shut down the Realm on each Node where the Realm was started, as explained in Section 5.3.1.2. ________________________ Note ________________________ It is possible to shut down a Realm on one Node and leave it available on the remaining Nodes. However, it is recommended that you shut down all the Realm application components in an orderly fashion on all Realm Nodes before shutting down the Realm environment on the Node. ______________________________________________________ 5.3.1.1 Shutting Down the Database Server for a Realm on the PODB Node The bstr_realm_shut_db command stops the Realm Database Services server. You can only perform this operation on the PODB Node. 5.3.1.2 Shutting Down a Realm on a Node The bstr_realm_shut_node command makes a Realm unavailable on a Node. It also shuts down any active Realm-specific components on the Node. 5-8 Environment Management Procedures 5.3 Shutdown Procedures 5.3.2 Shutting Down a Node The bstr_node_shut command deactivates the node-specific environment components. Note that once you have completed the shutdown operation for the Node on which the Name Service server is running, BASEstar Open becomes unavailable on all other Nodes unless you activate a secondary copy of the server on a Node that is still active. 5-9 Environment Management Procedures 5.3 Shutdown Procedures 5.3.3 Shutting Down the Sample Environment The command sequence in this section demonstrates how to shut down the BASEstar Open environment for the sample configuration illustrated in Figure 4-1. Shutting Down the MY_REALM Realm You can shut down MY_REALM on NODE1, NODE2 and NODE_DB in any order. Before shutting down the Realm on the PODB Node, you must first issue the bstr_realm_shut_db command on that Node. Execute the appropriate setup file for your shell on each Node: $ . /etc/bstrusers.sh (Sh or Sh5 shell) $ source /etc/bstrusers.csh (C shell) Execute the following command on NODE1: $ bstr_realm_shut_node MY_REALM Execute the following command on NODE2: $ bstr_realm_shut_node MY_REALM Execute the following commands on NODE_DB: $ bstr_realm_shut_db MY_REALM $ bstr_realm_shut_node MY_REALM Shutting Down the TS_REALM Realm To shut down TS_REALM on NODE1 and NODE_DB, issue the following command on NODE1: $ bstr_realm_shut_node TS_REALM Execute the following commands on NODE_DB: $ bstr_realm_shut_db TS_REALM $ bstr_realm_shut_node TS_REALM The shutdown operations for TS_REALM are similar to those performed for MY_REALM. ________________________ Note ________________________ You do not need to be a superuser (root) to shut down a Realm. However, the user who shuts down the Realm must be the same user that started up the Realm. ______________________________________________________ 5-10 Environment Management Procedures 5.3 Shutdown Procedures Shutting Down the Nodes Once you have shut down MY_REALM and TS_REALM in an orderly fashion, you can shut down the Nodes in any order. Execute the following command on NODE1: $ bstr_node_shut Execute the following command on NODE2: $ bstr_node_shut Execute the following command on NODE_DB: $ bstr_node_shut 5-11 Environment Management Procedures 5.4 Unset Procedures 5.4 Unset Procedures This section describes the procedures that allow you to unset Realms and Nodes. Execute the procedure described in Section 5.4.1 for all the Realms in your environment, and the procedure described in Section 5.4.2 for all the Nodes to be unset. 5.4.1 Unsetting a Realm Unsetting a Realm implies unsetting it for all the Nodes on which it was set, as described in Section 5.4.1.1. In addition, you must delete the PODB database created for that Realm, as explained in Section 5.4.1.2. 5.4.1.1 Unsetting a Realm from a Node To unset a Realm from a Node, execute the bstr_realm_unset_ node command on the Node in question. This command deletes all Realm-specific directories and files previously created by the bstr_realm_setup_node command from the file system of the Node. The PODB Node also performs the actions described in Section 5.4.1.2. 5.4.1.2 Unsetting a Realm Database on the PODB Node To unset a Realm database on the PODB Node, execute the bstr_realm_unset_db command on the PODB Node. This command deletes the database for the specified Realm. ________________________ Note ________________________ If you delete the database for a specified Realm, BASEstar Open also deletes all PODB object definitions. ______________________________________________________ 5.4.2 Unsetting a Node The bstr_node_unset command deletes the directories and node-specific files previously created by the bstr_node_setup command from the file system of the Node. 5-12 Environment Management Procedures 5.4 Unset Procedures 5.4.3 Unsetting the Sample Environment The command sequence in this section demonstrates how to unset the BASEstar Open environment for the sample configuration illustrated in Figure 4-1. Unsetting the MY_REALM Realm You can unset the MY_REALM Realm from NODE1, NODE2 and NODE_DB in any order. Execute the following command on NODE1: $ bstr_realm_unset_node MY_REALM Execute the following command on NODE2: $ bstr_realm_unset_node MY_REALM Execute the following commands on NODE_DB: $ bstr_realm_unset_db MY_REALM $ bstr_realm_unset_node MY_REALM Unsetting the TS_REALM Realm To unset the TS_REALM Realm on NODE1 and NODE_DB, issue the following command on NODE1: $ bstr_realm_unset_node TS_REALM Execute the following commands on NODE_DB: $ bstr_realm_unset_db TS_REALM $ bstr_realm_unset_node TS_REALM The operations required to unset TS_REALM are similar to those performed for MY_REALM. Note that TS_REALM has not been unset from NODE2. This is because it was not set on this Node. Unsetting the Nodes You can unset the Nodes shown in the example in any order. Execute the following command on NODE1: $ bstr_node_unset Execute the following command on NODE2: $ bstr_node_unset Execute the following command on NODE_DB: $ bstr_node_unset 5-13 Environment Management Procedures 5.5 Monitoring BASEstar Open 5.5 Monitoring BASEstar Open In addition to the general management procedures, you can use the bstr_mon tool (or the bstr_env_show command) to monitor the active components of the BASEstar Open environment. It displays: o All available Realms o For each Realm, the Nodes on which the Realm is available, and the available Domains and VMDs o A list of available Nodes and Realms available on each Node. For a complete description of the bstr_mon tool, refer to Chapter 7. Refer to Chapter 6 for a description of the bstr_env_show command. You can also use the bstr_realm_check_env command to check whether the BASEstar Open environment has been set up and started successfully on a given Node. 5-14 6 _________________________________________________________________ Environment Management Command Reference 6.1 Executing Environment Commands This section outlines the general requirements for executing environment commands successfully. The description of each individual command includes specific command requirements. If you execute a command successfully, BASEstar Open returns the following exit status: 0 (zero) If a command fails, it returns a different value in the command exit status. It also displays one or more messages that provide information about the error(s) that occurred during execution of the command. The log file often contains additional information about the components used to execute the command (see Chapter 10). 6.1.1 Requirements and Constraints This section explains which users can execute specific environment management commands, and specifies the rules that you must follow when executing a command. 6.1.1.1 Users and Commands Not all users can execute all the environment management commands. Table 6-1 indicates which user can execute a given command, where: o Root represents the superuser 6-1 Environment Management Command Reference 6.1 Executing Environment Commands o Spool user indicates the user responsible for managing a given Node. For a given Node, the spool user is the root user (default) or the user whose name was specified when the advanced bstr_node_setup command was executed for that Node. o Realm user indicates the user responsible for managing a given Realm. For a given Realm, the Realm user is the user who executed the bstr_realm_setup_node command for that Realm. o Generic user indicates any Compaq Tru64 UNIX user. ________________________ Note ________________________ If root, spool user or Realm user is specified for a command, only that user can execute the command. ______________________________________________________ Table 6-1 Relationship Between Environment Management __________Commands_and_Users_______________________________ Command_______________Type_of_User_________________________ _____________Monitoring_Environment_Components_____________ bstr_env_show Generic user bstr_realm_check_env Generic user ___________________________________________________________ _______________________Managing_Nodes______________________ bstr_node_setup Root bstr_node_start Spool user bstr_node_shut Spool user bstr_node_unset Root (continued on next page) 6-2 Environment Management Command Reference 6.1 Executing Environment Commands Table 6-1 (Cont.) Relationship Between Environment __________________Management_Commands_and_Users____________ ___________________________________________________________ ______________________Managing_Realms______________________ bstr_realm_setup_ Realm user node bstr_realm_start_ Realm user node bstr_realm_shut_node Realm user bstr_realm_unset_ Realm user node bstr_realm_setup_db Realm user bstr_realm_start_db Realm user bstr_realm_shut_db Realm user bstr_realm_unset_db___Realm_user___________________________ 6.1.1.2 Executing a Command Follow the rules listed below when executing an environment command (except for the bstr_node_setup command, the instructions for which are contained in the command description): o Log in as the appropriate user (as specified in Table 6-1) on the selected Compaq Tru64 UNIX Node o Ensure that the installation-dependent global variables have been correctly set by executing the bstrusers.sh, or bstrusers.csh script files (see Appendix B for details). For specific information on command requirements and constraints, refer to the description of each individual command. 6-3 Environment Management Command Reference 6.2 Privileges for Running Environment Management Procedures 6.2 Privileges for Running Environment Management Procedures Table 6-2 lists the privileges required to run the various BASEstar Open Server environment management commands. Table_6-2_Environment_Management_Privileges________________ Privileges Required Phase_________________Procedure________for_Execution_______ Set up BASEstar Open bstr_node_setup Superuser Start up BASEstar bstr_node_start Superuser Open Shut down BASEstar bstr_node_shut Superuser Open Unset BASEstar Open bstr_node_unset Superuser Set up a Realm bstr_realm_ Normal user setup_node Start up a Realm bstr_realm_ Normal user start_node Shut down a Realm bstr_realm_ Normal user shut_node Unset a Realm bstr_realm_ Normal user unset_node Set up a database bstr_realm_ Normal user setup_db Start up a database bstr_realm_ Normal user start_db Shut down a database bstr_realm_ Normal user shut_db Unset a database bstr_realm_ Normal user ______________________unset_db_____________________________ 6-4 cli_bstr _________________________________________________________________ cli_bstr Invokes the BASEstar Open CLI. Syntax cli_bstr [-c] [-e "command1" "command2"..."command10"] [-f command_file] [-i startup_file] [-v] Description The cli_bstr command allows you to invoke the BASEstar Open CLI. You can execute CLI commands either interactively, or in batch mode by specifying the name of a command file from the command interpreter prompt. Options -c This option allows you to check the syntax and semantics of a CLI command file without executing the file. -e "command1" "command2"..."command10" This option allows you to execute up to ten CLI commands without leaving the platform-dependent command interpreter. After executing the specified commands, the command interpreter redisplays the CLI prompt. Enclose each CLI command between double quotes, and make sure that the commands are separated by at least one blank. -f command_file Pathname of a CLI command file that BASEstar Open executes at the shell prompt. -i startup_file An optional startup command file that you can request the CLI to execute. If you fail to specify the -i option, BASEstar Open does not execute a startup command file unless the following CLI command file exists in your home directory: .cli_login 6-5 cli_bstr -v This option displays additional information on execution of the command. Examples 1. $ cli_bstr BSTR> This command invokes the CLI so that you can execute commands in interactive mode. 2. $ cli_bstr -e "SET SCOPE VOLATILE" "SHOW DATA_POINT /DOM1/DP3" $ This command sequence sets the VODB scope and displays the /DOM1/DP3 Data_Point. 3. $ cli_bstr -f exec2.com $ This command executes the exec2.com CLI command file at the shell prompt. See Also None 6-6 bstr_env_show _________________________________________________________________ bstr_env_show This command displays information about the environment components (Nodes and Realms) and services (server activities, PODB and Application Management Services servers currently started up in the BASEstar Open environment. Syntax bstr_env_show -q query [-s] | -d Description The bstr_env_show command allows you to display information about the components active in your BASEstar Open environment. It displays information on Nodes, Realms, or services, depending on what is specified in the query argument of the -q qualifier. The bstr_env_show command displays the components that are active at the time the command is executed (it does not provide information on components that have been set up but not started). To execute the bstr_env_show command: o Log in as a generic user (see Section 6.1 for details). o Check that the BASEstar Open environment has been started up successfully on the Node on which you want to execute the bstr_env_show command (see Chapter 5 for details). Note that this command accesses the Node where the Name Service server is active. o Ensure that the BASEstar Open installation-dependent global variables have been appropriately set, by executing the bstrusers.sh or bstrusers.csh script file (see Appendix B for details). If the command completes successfully, a zero value is returned in the command exit status, otherwise a value other than zero is returned. 6-7 bstr_env_show Options -q query The query expression specifies the kind of information displayed by the bstr_env_show command. The following expressions are valid: o N Displays a list of available BASEstar Open Nodes, that is, the Nodes for which the bstr_node_start command has been executed, and whose components have been started up successfully. o R Displays, for each Realm, a list of the BASEstar Open Nodes on which the Realm is available. (In this context, a Realm is