ObjectBroker__________________________________ Installation Guide December 1996 This guide provides information about how to install the ObjectBroker Version 2.7 software on DIGITAL UNIX and DIGITAL OpenVMS computers. Software Version: ObjectBroker Version 2.7 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ December 1996 Digital Equipment 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. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha, DEC, DECnet, DIGITAL, DIGITAL UNIX, DIGITAL OpenVMS, ObjectBroker, PATHWORKS, ULTRIX, VAX, VMScluster, VMS, and the DIGITAL logo. The following are third-party trademarks: HP and HP-UX are registered trademarks of Hewlett- Packard Company. IBM and AIX are registered trademarks of International Business Machines Corporation. Intel is a trademark of Intel Corporation. Macintosh is a registered trademark of Apple Computer, Inc. Microsoft, MS-DOS, Visual Basic are registered trademarks and Windows and Windows NT are trademarks of Microsoft Corporation. Motif, OSF, and OSF/1 are registered trademarks and Open Software Foundation is a trademark of the Open Software Foundation, Inc. Novell is a registered trademark of Novell, Inc. OMG is a registered trademark and CORBA, COSS, OMG IDL, Object Request Broker, and ORB are trademarks of the Object Management Group. Sun is a registered trademark and SPARCstation is a trademark of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 Overview of the Installation Process 2 Installing ObjectBroker on DIGITAL UNIX Systems 2.1 Disk Space Requirements...................... 2-1 2.2 Before You Begin............................. 2-1 2.3 Upgrade Notes................................ 2-2 2.4 Installation................................. 2-4 2.5 After the Installation....................... 2-8 3 Installing ObjectBroker on DIGITAL OpenVMS Systems 3.1 Disk Space Requirements...................... 3-1 3.2 Before You Begin............................. 3-1 3.3 Installation................................. 3-2 3.4 After the Installation....................... 3-7 Tables 1 General Coding and Operating System-Specific Conventions.............. vi iii ________________________________________________________________ Preface Purpose of This Manual This manual explains how to install ObjectBroker Version 2.7 on each supported platform. Intended Audience This manual is written for system administrators and system integrators who are responsible for installing the ObjectBroker software. Structure of This Manual This manual contains two chapters, as follows: o Chapter 1 provides an overview of the installation process. o Chapter 2 describes how to install ObjectBroker on DIGITAL UNIX platforms. o Chapter 3 describes how to install ObjectBroker on DIGITAL OpenVMS platforms. Conventions Table 1, General Coding and Operating System-Specific Conventions explains the conventions that are used throughout this guide. v Table 1 General Coding and Operating System-Specific ________Conventions_______________________________________ Convention__Meaning_______________________________________ ... A horizontal ellipsis indicates one of the following conditions: o The statement omits additional optional arguments. o You can repeat the preceding item or items one or more times. o You can enter additional parameters, values, or other information. . A vertical ellipsis indicates the omission of . items from a code example or from a command . format. The author omitted the items because they are not important to the topic being discussed. ( ) In syntax diagrams, parentheses indicate that if you choose more than one option, you must enclose the choices in parentheses. [ ] In syntax diagrams, brackets indicate that whatever is enclosed in the brackets is optional. { } In syntax diagrams, braces indicate that you must choose at least one of the options listed. | In syntax diagrams, a vertical bar inside brackets or braces indicates that you should choose one of the items listed. $ The dollar sign represents the DIGITAL Command Language (DCL) prompt. (The DCL prompt on your system may be different.) # The number sign represents the DIGITAL UNIX prompt. (The UNIX prompt on your system may be different.) (continued on next page) vi Table 1 (Cont.) General Coding and Operating System- ________________Specific_Conventions______________________ Convention__Meaning_______________________________________ > The right angle bracket represents the Microsoft Windows 3.1 or Windows NT prompt. (The Microsoft Windows NT prompt on your system may be different.) monospaced Monospaced text indicates ObjectBroker file text names, operations, values, routine names, attributes, command names (including command switches and switch parameters), and system output. Monospaced text also indicates text that you must enter from the keyboard. boldface Boldface text indicates arguments, field text names, and terms that are defined in the glossary. (The ObjectBroker Introduction and Glossary contains the glossary.) italic Italic text indicates either the author's text emphasis or information that can vary, such as a command parameter. UPPERCASE Uppercase letters indicate attribute names, text attribute values, error message names, data types, and flag values. lowercase Lowercase text in the monospace font indicate monospace UNIX command names and command switches. text OpenVMS The term OpenVMS refers to both OpenVMS VAX operating systems and OpenVMS Alpha operating systems, unless otherwise specified. UNIX________The_term_UNIX_refers_to_DIGITAL_UNIX_systems._ For More Information For more information about ObjectBroker, CORBA, C++ bindings, and the OMG, see the following documents and World Wide Web sites: o ObjectBroker Introduction and Glossary-The entry point into the ObjectBroker information set for all audiences. vii o ObjectBroker Using QuickStart-Describes how to use the QuickStart development tool to generate the components needed for a client and server system. o ObjectBroker Guide to Examples-Describes how to use and build a set of progressive ObjectBroker examples in C; also includes an example in C++. This manual is a companion to ObjectBroker Designing and Building Applications. o ObjectBroker Designing and Building Applications- Contains detailed information about how to design, develop, and deploy an application using ObjectBroker. o ObjectBroker Installation Guide (this manual)-Describes how to install the ObjectBroker software. o ObjectBroker Administration Guide-Describes how to configure, administer, and troubleshoot the ObjectBroker software. o ObjectBroker Programming Reference-Contains routine descriptions for ObjectBroker's C, C++, and Visual Basic language bindings, as well as authentication routines and server management routines. This manual also includes information about the OMG IDL, IML, and MML definition languages, and ObjectBroker error messages. o ObjectBroker Commands and Utilities Reference-Describes the ObjectBroker commands and graphical user interface utilities. o Understanding CORBA-Describes the CORBA specification and explains how to design, develop, and deploy a CORBA application. This manual is vendor neutral; it describes how to create a CORBA client and server application using the vendor's CORBA product, not just the DIGITAL ObjectBroker product. This manual is a companion to ObjectBroker Designing and Building Applications. o The Common Object Request Broker Architecture and Specification, Revision 2.0, published July 1995 by the Object Management Group. viii o ObjectBroker World Wide Web site at http://www.digital.com /info/objectbroker. o OMG World Wide Web site at http://www.omg.org. ix 1 ________________________________________________________________ Overview of the Installation Process This chapter gives a high-level overview of the ObjectBroker installation process for all supported platforms. ObjectBroker consists of two products: the run-time kit, and the development kit. Each product is available on a separate distribution volume. Use the following guidelines to determine which kit to install on a given computer. Run-time kit Install the ObjectBroker run-time kit on all licensed systems that run ObjectBroker applications. To deploy ObjectBroker, you must have the appropriate platform-specific ObjectBroker run-time license for each system included in the deployment. Development kit Install the ObjectBroker development kit on all licensed systems that you use for ObjectBroker application development. The development kit includes the run-time kit and example programs that demonstrate features and capabilities of the ObjectBroker software. To develop ObjectBroker applications, you must have the appropriate platform- specific ObjectBroker development license per computer on which ObjectBroker is used to develop, compile, and/or link applications. ________________________Note ________________________ You install only one kit on a given computer. Do not install both the run-time kit and the development kit on a single computer. You must also have the prerequisite operating systems, network transport(s), and compiler(s) (for Overview of the Installation Process 1-1 Overview of the Installation Process development) that are specified in the ObjectBroker Software Product Descriptions (SPDs). _____________________________________________________ The Release Notes, available only on line, contain important information about the software. ________________________Note ________________________ If your ObjectBroker kit is on a CD-ROM, you have the ability to read the Release Notes before installation, which we recommend that you do. (For other media types, such as tape or diskette, you must complete the ObjectBroker installation procedure before you can access the Release Notes.) On CD-ROM kits, the Release Notes are located in the docs directory in the file release.nts. The media from which you install your ObjectBroker software does not affect the location of Release Notes file on your system, but the file location does vary according to your operating system. On DIGITAL UNIX, the Release Notes are copied into /usr/doc ObjectBroker027.release_notes. On DIGITAL OpenVMS, the Release Notes are copied into SYS$HELP:OBBDEV026.RELEASE NOTES (development kit) and SYS$HELP:OBBRTO026.RELEASE NOTES (runtime kit). _____________________________________________________ After you complete the ObjectBroker installation process, refer to the ObjectBroker Administration Guide for details on customizing, configuring, and managing your ObjectBroker system. 1-2 Overview of the Installation Process 2 ________________________________________________________________ Installing ObjectBroker on DIGITAL UNIX Systems 2.1 Disk Space Requirements The following table lists the disk space used by ObjectBroker Version 2.7 both during and after the installation procedure: __________________________________________________________ Used During ______________Installation_____Used_After_Installation____ Run-time kit 8.0 MB 6.6 MB Development 14.2 MB 12.7 MB kit_______________________________________________________ 2.2 Before You Begin Before you start the installation, answer the following questions: o Is your system running DIGITAL UNIX Version 3.2 or later up to Version 4.0 with patch OSF400-019? o Do you have the required minimum amount of free disk space? o Do you have the prerequisite network transport and compiler(s) (if you are installing the development kit) that are specified in the ObjectBroker Software Product Description (SPD)? The SPD is included in every ObjectBroker kit. o Are you using TCP/IP (included with the base operating system) as your transport? o Have you backed up your system disk? Installing ObjectBroker on DIGITAL UNIX Systems 2-1 Installing ObjectBroker on DIGITAL UNIX Systems 2.2 Before You Begin o Do you have the Product Authorization Key (PAK) that contains the information you need to register the ObjectBroker license with the License Management Facility (LMF)? If the answer to any question is "No," you do not have the hardware or software required to use the product. Obtain the required hardware and software, and then proceed. If the answer to all of the questions is "Yes," complete the procedure explained in Section 2.4 to perform a local installation on a DIGITAL UNIX system. 2.3 Upgrade Notes Please note the following information if you are upgrading to ObjectBroker Version 2.7 from an earlier version of ObjectBroker. o If you remove a previously installed version of ObjectBroker: If you first use the setld command with the -d (delete) option to remove the OBBBASE*250, OBBBASE*251, OBBBASE*252, OBBBASE*253, OBBBASE*260, or OBBBASE*261 subsets before you install ObjectBroker Version 2.7, you will lose your ObjectBroker system registries, the ObjectBroker system repository, and the system context object. o If you do not remove a previously installed version of ObjectBroker: If you do not use the setld command with the -d option to remove an earlier version of ObjectBroker before installing ObjectBroker Version 2.7, the installation procedure puts ObjectBroker Version 2.7 (subsets OBB*270) into its own directory tree (/usr/kits /OBB270), and retains all existing ObjectBroker system registries, the ObjectBroker system repository, and the system context object. At the end of the installation, the installation procedure asks if you want to remove the directory tree that contains the earlier version of ObjectBroker. 2-2 Installing ObjectBroker on DIGITAL UNIX Systems Installing ObjectBroker on DIGITAL UNIX Systems 2.3 Upgrade Notes If you lack adequate disk space on your computer to hold both the new and an earlier version of ObjectBroker, complete the following procedure to preserve the ObjectBroker system registries, the ObjectBroker system repository, and the system context object: 1. Stop the ObjectBroker agent, if you have not done so already, using the following steps: a. Use the obbmsho command to identify all active implementations. Note the identifiers that the system displays. b. Use the identifiers next to the label Inst UUID to stop the active implementation processes one by one, as shown in the following example: # obbmstp 56220ba949cc.0c.00.00.00.00.00.00.00 Redisplay the list of active implementations to verify that the process has been stopped. If the process still exists, re-enter the command using the -a (abort) option, as shown in the following example: # obbmstp -a 56220ba949cc.0c.00.00.00.00.00.00.00 Repeat until all active implementation processes have been stopped. You can use the obbmstp -p command to purge stopped implementations from memory, if desired. c. Stop the ObjectBroker agent itself by entering the following command: # obbmstp -A 2. Copy the /usr/var/adm/ObjectBroker directory, as shown in the following example: # cd /usr/var/adm # cp -r ObjectBroker obb_old 3. Verify that the copy of the directory contains the OBB* files, which hold the ObjectBroker system registries, the ObjectBroker system repository, and the system context object. For example: # ls /usr/var/adm/obb_old/OBB* Installing ObjectBroker on DIGITAL UNIX Systems 2-3 Installing ObjectBroker on DIGITAL UNIX Systems 2.3 Upgrade Notes Although there may be additional backup versions, at a minimum, you should see the following files listed: /usr/var/adm/obb_old/OBB_ADVERTISEMENT_REGISTRY /usr/var/adm/obb_old/OBB_SECURITY_REGISTRY /usr/var/adm/obb_old/OBB_SOFTWARE_REGISTRY /usr/var/adm/obb_old/OBB_SYSTEM_CONTEXT /usr/var/adm/obb_old/OBB_SYSTEM_REGISTRY /usr/var/adm/obb_old/OBB_SYSTEM_REPOSITORY 4. Use the setld command with the -d option to remove the earlier version of ObjectBroker from your system. For example: # setld -d OBBBASEDEV260 OBBMANDEV260 ________________________Note ________________________ To obtain the name of any old ObjectBroker files on your system, enter the following command: # setld -i | grep OBB* _____________________________________________________ 5. Rename the saved directory to /usr/var/adm/ObjectBroker: # mv obb_old ObjectBroker 2.4 Installation Complete the following steps to perform a local installa- tion on a DIGITAL UNIX system: 1. Register your ObjectBroker license before you install the ObjectBroker software. ________________________Note ________________________ If you do not register the license and you do not load the appropriate Product Authorization Key, you will not be able to complete the installation, run the Installation Verification Procedure (IVP), or use ObjectBroker. Refer to the VAX/VMS Licence Management Facility manual for more information about registering 2-4 Installing ObjectBroker on DIGITAL UNIX Systems Installing ObjectBroker on DIGITAL UNIX Systems 2.4 Installation the license and loading the appropriate Product Authorization Key. _____________________________________________________ 2. Log in as superuser (login name root). 3. If any ObjectBroker implementations are running, or if the ObjectBroker agent is running, do the following. a. Use the obbmsho command to identify all active implementations. Note the identifiers that the system displays. b. Use the identifiers next to the label Inst UUID to stop the active implementation processes one by one, as shown in the following example: # obbmstp 56220ba949cc.0c.00.00.00.00.00.00.00 Redisplay the list of active implementations to verify that the process has been stopped. If the process still exists, re-enter the command using the -a (abort) option, as shown in the following example: # obbmstp -a 56220ba949cc.0c.00.00.00.00.00.00.00 Repeat until all active implementation processes have been stopped. You can use the obbmstp -p command to purge stopped implementations from memory, if desired. c. If the ObjectBroker agent is running, stop it by entering the following command: # obbmstp -A Note Stopping the server applications and the agent before the installation, as described in the preceding steps, is usually sufficient to ensure that none of the shared libraries replaced by the installation are in use. However, you may receive one or more error messages during the installation indicating that a file is in use. This may be caused by an ObjectBroker Graphical User Interface (GUI) application or by a VMS command-line facility that is accessing a shared library from a local or Installing ObjectBroker on DIGITAL UNIX Systems 2-5 Installing ObjectBroker on DIGITAL UNIX Systems 2.4 Installation remote node. In this case, you may need to ask the respective users to stop accessing those libraries and start the installation again. d. Delete outdated SAK files, if any exist: # rm /usr/adm/ObjectBroker/sak/* e. Make sure that you are at the root directory: # cd / 4. If you are installing from CD-ROM, mount the installa- tion media. Create the /mnt/cdrom directory, and then enter the following command, substituting your CD-ROM device number for n and using /mnt/cdrom for the mounting point: # mount -t cdfs -o rrip,noversion /dev/rznc /mnt/cdrom Note: you can use the following command to determine the device number of your CD-ROM drive: # file /dev/rrz?c _______________________ Notes _______________________ Without the rrip option, the setld subset names appear as lowercase letters, causing problems with the installation's dependency checking. This results in a failed installation, leaving the file system in a state where the software is not installed and setld -d cannot delete the software. If you installed ObjectBroker from the CD-ROM and the installation fails with the BASE is not installed message, check the contents of /usr/.smdb. /. If there are files named obbbasedev270.* and /or obbmandev270.* rather than OBBBASEDEV270.* and OBBMANDEV270.*, check the options that you used to mount the CD-ROM. _____________________________________________________ 5. Load the software from the distribution media, using the device file name. 2-6 Installing ObjectBroker on DIGITAL UNIX Systems Installing ObjectBroker on DIGITAL UNIX Systems 2.4 Installation If you are installing ObjectBroker from tape, enter the following command: # setld -l /dev/rmt0h If you are installing ObjectBroker from CD-ROM, enter the following command: # setld -l /mnt/cdrom/OBJBROKR/DEC_UNIX 6. The installation procedure displays the subset name for ObjectBroker. Select any optional subsets you want to install: 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. 1) ObjectBroker Base System 2) ObjectBroker Man Pages Or you may choose one of the following options: 3) ALL of the above 4) CANCEL selections and redisplay menus 5) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 3 7. Verify your choice. For example, in response to the preceding prompt, your system displays: You are installing the following optional subsets: ObjectBroker Base System ObjectBroker Man Pages Is this correct? (y/n): y Enter y to load the selected subsets. Enter n to redisplay the subset selection menu if you did not select the correct subsets. Then, correct your choice of optional subsets and enter y to load the subsets you selected. Installing ObjectBroker on DIGITAL UNIX Systems 2-7 Installing ObjectBroker on DIGITAL UNIX Systems 2.4 Installation No more questions will be asked. Informational messages that report on the progress of the installation will appear. The installation takes 5 to 15 minutes, depending on your hardware. 2.5 After the Installation After you complete the ObjectBroker installation procedure, we recommend the following steps: 1. Review the Release Notes, which contain important information about this version of ObjectBroker. You can display the Release Notes by entering the following command: # more /usr/doc/ObjectBroker027.release_notes 2. Run the Installation Verification Procedure (IVP). For the ObjectBroker development kit, enter the following command: # setld -v OBBBASEDEV270 For the ObjectBroker run-time kit, enter the following command: # setld -v OBBBASERT270 Note that running the IVP automatically starts the ObjectBroker agent. 3. If your system mounts NFS disks that hold system context object files, ObjectBroker system repository files, and ObjectBroker system registry files that could be accessed by ObjectBroker and its utilities, enable the NFS file locking feature. 4. To have the ObjectBroker agent start automatically when your system is booted, create a symbolic link between the existing file /sbin/init.d/ObjectBroker and a new file named /sbin/rc3.d/S75obb, as in the following example: # ln -s /sbin/init.d/ObjectBroker /sbin/rc3.d/S75obb 5. To unload the CD-ROM, enter the following command : # umount /mnt/cdrom 2-8 Installing ObjectBroker on DIGITAL UNIX Systems 3 ________________________________________________________________ Installing ObjectBroker on DIGITAL OpenVMS Systems 3.1 Disk Space Requirements The following table lists the disk space used by ObjectBroker both during and after the installation procedure: __________________________________________________________ Used During ______________Installation_____Used_After_Installation____ Run-time kit 13,000 blocks 12,000 blocks Development 18,500 blocks 17,500 blocks kit_______________________________________________________ 3.2 Before You Begin Before you start the installation, answer the following questions: o Can you log in to the SYSTEM account on the system where you will install ObjectBroker? o Is your system running OpenVMS VAX or OpenVMS Alpha Version 6.1 or higher up to and including Version 7.0? o Do you have the required minimum amount of free disk space? o Do you have the prerequisite network transport(s) and compiler(s) (if you are installing the development kit) that are specified in the ObjectBroker Software Product Description (SPD)? The SPD is included in every ObjectBroker kit. o If you are running OpenVMS VAX, do you have at least 2400 GBLPAGES free? Installing ObjectBroker on DIGITAL OpenVMS Systems 3-1 Installing ObjectBroker on DIGITAL OpenVMS Systems 3.2 Before You Begin o If you are running OpenVMS Alpha, do you have at least 4700 GBLPAGES free? o Have you backed up your system disk? o Do you have the Product Authorization Key (PAK) that contains the information you need to register the ObjectBroker license with the License Management Facility (LMF)? (The PAK is available in print as part of your distribution kit.) If the answer to any question is "No," you do not have the hardware or software required to use the product. Obtain the required hardware and software, and then proceed. If the answer to all of the questions is "Yes," complete the instructions in the following section. 3.3 Installation Complete the following steps to perform a local installa- tion on an OpenVMS system: 1. Log in to the SYSTEM account on the computer where you are installing ObjectBroker. 2. If any ObjectBroker implementations are running, or if the ObjectBroker agent is running, do the following: a. Enter the following command to identify all active implementations: $ APPLICATION/BROKER SHOW SERVERS Note the identifiers that appear on the screen. b. Use the identifiers next to the label Inst UUID to stop the active implementation processes one by one, as shown in the following example: $ APPLICATION/BROKER STOP SERVER - _$ 56220BA949CC.0C.00.00.00.00.00.00.00 Redisplay the list of active implementations to verify that the process has been stopped. If the process still exists, re-enter the command using the /ABORT qualifier, as shown in the following example: 3-2 Installing ObjectBroker on DIGITAL OpenVMS Systems Installing ObjectBroker on DIGITAL OpenVMS Systems 3.3 Installation $ APPLICATION/BROKER STOP SERVER/ABORT - _$ 56220BA949CC.0C.00.00.00.00.00.00.00 Repeat this step until all active implementation processes have been stopped. You can enter the APPLICATION/BROKER STOP SERVER/PURGE command to purge stopped implementations from memory, if desired. c. If the ObjectBroker agent is running, stop it by entering the following command: $ APPLICATION/BROKER STOP AGENT d. Delete outdated SAK files, if any exist: $ DELETE OBB$SAK:*.SAK;* 3. Register your ObjectBroker license before you install the ObjectBroker software. ________________________Note ________________________ If you do not register the license and you do not load the appropriate Product Authorization Key, you will not be able to complete the installation, run the Installation Verification Procedure (IVP), or use ObjectBroker. See the VMS License Management Facility manual for information about registering the license and loading the Product Authorization Key. _____________________________________________________ 4. Mount the development or run-time installation media in the appropriate drive: a. If you are installing from CD-ROM, mount the installation media and enter the following command: $ MOUNT /MEDIA=CDROM /OVERRIDE=IDENTIFICATION - _$ /UNDEFINED_FAT=(FIXED:NONE:9216) b. If you are installing ObjectBroker from a TK50/70 tape, the installation procedure prompts you to mount the tape, as explained in step 7. Installing ObjectBroker on DIGITAL OpenVMS Systems 3-3 Installing ObjectBroker on DIGITAL OpenVMS Systems 3.3 Installation 5. Invoke the VMSINSTAL command procedure: $ @SYS$UPDATE:VMSINSTAL saveset_name device_name: - _$ OPTIONS N If you install the ObjectBroker development kit, replace saveset_name with OBBDEV027. If you install the ObjectBroker run-time kit, replace saveset_name with OBBRTO027. Replace device_name with the name of the device from which you install ObjectBroker. ________________________Note ________________________ If you are installing ObjectBroker from a CD-ROM, use :[OBJBROKR.VMS] as the kit location. _____________________________________________________ If you do not supply the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the Release Notes during the installation. For example, the following command installs the ObjectBroker development kit from tape drive MUA0: $ @SYS$UPDATE:VMSINSTAL OBBDEV027 MUA0: The installation procedure displays several messages on the screen, such as in the following example: OpenVMS AXP Software Product Installation Procedure V6.1 It is 19-JUNE-1996 AT 8:05. Enter a question mark (?) at any time for help. The installation procedure may ask other questions, depending on your configuration environment. Refer to the appropriate VMS manual for more information 3-4 Installing ObjectBroker on DIGITAL OpenVMS Systems Installing ObjectBroker on DIGITAL OpenVMS Systems 3.3 Installation 6. VMSINSTAL asks if you are satisfied with your system backup. * Are you satisfied with the backup of your system disk [YES]? Always back up your system disk before performing an installation. If you have not backed up your system disk, enter NO to stop the installation. Perform a backup, then restart the installation. If you have backed up your system disk, press Return to continue the installation. 7. If you are installing from tape, the installation procedure prompts you to mount the tape, as in the following example: Please mount the first volume of the set on MUA0:. * Are you ready? YES $MOUNT-I-MOUNTED, OBBDEV027 MOUNTED ON __NODE1$MUA0: The following products will be processed : OBBDEV V2.7 Beginning installation of OBBDEV V2.7 at 8:05 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... Mount the first distribution volume on the device you specified when you invoked VMSINSTAL. VMSINSTAL then asks if you are ready to continue the installation. If you respond YES, VMSINSTAL displays a message that the media containing the product has been mounted on the specified device and that the installation has begun. If you entered the wrong device name when you invoked VMSINSTAL and you need to restart the installation, respond NO. To cancel the installation for other reasons, press Ctrl/Y. 8. You are prompted to indicate whether you want to display or print the Release Notes. Installing ObjectBroker on DIGITAL OpenVMS Systems 3-5 Installing ObjectBroker on DIGITAL OpenVMS Systems 3.3 Installation Release Notes included with this kit are always copied to SYS$HELP. Additional Release Notes options: 1) Display Release Notes 2) Print Release Notes 3) Both 1 and 2 4) None of the above Select option [2]: Choose the desired Release Notes option, and press Return. After you make your choice, VMSINSTAL copies the release notes into SYS$HELP. 9. Select your transport: You can select the following transport usage for your system: 1) DECnet only 2) TCP/IP only 3) Both DECnet and TCP/IP * Enter the number of the transport setup to be enabled [2]: 10.Purge files from the previous version of ObjectBroker that are superseded by this installation: * Do you want to purge files replaced by this installation [YES]? Purging is recommended. However, if you need to keep files from the previous version, enter NO. 11.Run the Installation Verification Procedure (IVP). If the transport you selected is running, you are prompted to run the IVP, which verifies that the installation is successful. We recommend that you run the IVP. * Do you want to run the IVP after the installation [YES]? You can run the IVP independently at any time after the installation to verify that your system can access the software. For example, in the event of a system failure, you run the IVP to make sure that users can access the product. Note that running the IVP automatically starts the ObjectBroker agent. 3-6 Installing ObjectBroker on DIGITAL OpenVMS Systems Installing ObjectBroker on DIGITAL OpenVMS Systems 3.3 Installation The installation procedure displays a number of infor- mational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates online help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. If you chose to run the IVP in step 11, the following message appears: *********************************************************** Beginning Installation Verification Procedure for ObjectBroker for OpenVMS *********************************************************** When the IVP successfully completes, the following message appears: Installation of OBBDEV V2.7 completed at 8:20 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file VMI$ROOT:[SYSUPD]OBBDEV027.VMI_DATA VMSINSTAL procedure done at 8:22 The installation is complete. You can log out of the privileged account. 3.4 After the Installation After you complete the ObjectBroker installation procedure, we recommend the following steps: 1. Review the Release Notes, which contain important information about this version of ObjectBroker. You can find the Release Notes at the following locations: SYS$HELP:OBBDEV027.RELEASE_NOTES (development kit) SYS$HELP:OBBRTO027.RELEASE_NOTES (run-time kit) 2. Do the following if you are using ObjectBroker in a VMScluster: Installing ObjectBroker on DIGITAL OpenVMS Systems 3-7 Installing ObjectBroker on DIGITAL OpenVMS Systems 3.4 After the Installation If you intend to use ObjectBroker on other computers in your VMScluster and you have the appropriate software license, you must also create the appro- priate system-specific directories by executing the SYS$MANAGER:OBB$ADD_CLUSTER_NODE.COM procedure on the selected computer, using a suitably privileged account, before starting ObjectBroker. 3-8 Installing ObjectBroker on DIGITAL OpenVMS Systems