HP_Enterprise_Integration_Packages__________________ Installation Guide May 2005 This guide provides installation information for products licensed by the HP Enterprise Integration Packages. License/Package Release: 3.5 Software Product Library: OpenVMS Alpha SPL, Q2/June 2005 Revision/Update Information: OpenVMS Alpha Version: 8.2 Hewlett-Packard Company Palo Alto, California ________________________________________________________________ May 2005 © Hewlett-Packard Company. 2005. All Rights Reserved. The following are registered trademarks: Microsoft, Windows, Windows XP Professional, Windows 2000, Windows 98, Windows NT and Windows 95 are registered trademarks of Microsoft Corporation. Motif is a registered trademark of the Open Software Foundation, Inc. Netscape, Netscape Communications, and Netscape Navigator are registered trademarks of Netscape Communications Corporation. PostScript is a registered trademark of Adobe Systems Incorporated. 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. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Proprietary computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. This document was prepared using DECdocument, Version 3.3- 1b. _________________________________________________________________ Contents Preface................................................... v 1 Overview 1.1 Product Location and Licenses................. 1-1 1.2 Mounting a CD on OpenVMS...................... 1-3 1.3 Installation Documentation.................... 1-4 1.3.1 HP PATHWORKS 32 Documentation............. 1-4 2 Preparing to Install the HP Enterprise Integration Packages 2.1 Prerequisites for Installation................ 2-1 2.1.1 Back Up Your System Disk ................. 2-1 2.1.2 Hardware Requirements..................... 2-1 2.1.3 Software Requirements..................... 2-2 2.1.4 Installation Account Requirements......... 2-2 2.1.5 Checking and Setting Process Account Quotas.................................... 2-2 2.1.6 OpenVMS Class Requirements................ 2-3 2.2 Component Disk Space and Installation Times... 2-3 2.3 Preinstallation Considerations................ 2-4 2.3.1 Register Each License..................... 2-4 2.3.2 DECnet-Plus Component Restrictions........ 2-5 2.3.3 TCP/IP Services for OpenVMS Considerations............................ 2-5 2.3.4 HP Enterprise Integration Extension License Package for NAS 200............... 2-5 2.3.5 OpenVMS Cluster License Requirements ..... 2-5 2.4 Modifying System Parameters .................. 2-6 2.4.1 DECnet-Plus System Parameter Considerations............................ 2-6 2.4.2 OpenVMS Cluster System Parameters ........ 2-6 iii 2.4.3 Using MODPARAMS_EIS.DAT to Update System Parameters................................ 2-7 2.4.4 Calculating the Values for Global Pages (GBLPAGES) and Global Sections (GBLSECTIONS)............................. 2-7 2.4.5 System Parameter Requirements............. 2-9 2.4.6 Checking System Parameter Values.......... 2-11 2.4.7 Changing System Parameter Values with AUTOGEN................................... 2-12 3 Installing the HP Enterprise Integration Packages Components 3.1 HP Enterprise Integration Packages Installation Checklist........................ 3-1 3.2 Using the VMSINSTAL Utility................... 3-2 3.2.1 Error Detection and Follow Up............. 3-3 3.3 Using the POLYCENTER Software Installation Utility....................................... 3-3 3.4 Component Installation Order and Dependencies.................................. 3-3 3.5 Component Installation........................ 3-7 3.6 Identifying and Reporting Installation Problems...................................... 3-8 A Ordering Hardcopy Documentation Index Tables 1-1 HP Enterprise Integration Packages Components and Licenses................... 1-2 2-1 Minimum Installation Account Quotas....... 2-2 2-2 Disk Space and Installation Time.......... 2-4 2-3 System Parameter Requirements for R3.0 ... 2-9 3-1 Enterprise Integration Packages Installation Checklist.................... 3-1 3-2 Component Installation Order, Installation File Names, and Dependencies.............. 3-5 A-1 Documentation Order Numbers............... A-1 iv _________________________________________________________________ Preface This guide provides installation information for products licensed by the HP Enterprise Integration Packages. It is organized as follows: o Chapter 1 lists the products and licenses in the Enterprise Integration Packages, and contains pointers to the documentation for those products. o Chapter 2 contains required disk quota, system and cluster parameters, and minimum operating system version information necessary for product installation. o Chapter 3 contains installation information, including installation order and checklist. o Appendix A explains how to order hardcopy documentation for the Enterprise Integration Packages products. v 1 _________________________________________________________________ Overview The HP Enterprise Integration Packages provide licenses for layered software products that allow users to merge Microsoft Windows environments with OpenVMS systems, applications, and data. The Enterprise Integration Packages consist of: o HP Enterprise Integration Server for OpenVMS License Package o HP Enterprise Integration Client for Microsoft Windows License Package o HP Enterprise Integration Extension License Package for NAS 200 The products provide OpenVMS and Windows integration services for: o Management o Network transport and connectivity o File, print, and disk o Internet products o Mail o Presentations 1.1 Product Location and Licenses The products licensed by the Enterprise Integration Packages are contained in the OpenVMS Alpha Software Product Library (SPL). Refer to the SPL Master Index to determine the location within the SPL multi-CD set of the individual products listed in this guide. A hardcopy of this Master Index is included in the SPL, and is also available in the [README] directory on SPL disc 1. Overview 1-1 A License Management Facility Product Authorization Key (PAK) allows you to access a software product. A PAK must be registered and loaded before you can install the associated software. Table 1-1 lists the products and associated license PAK names. Table 1-1 HP Enterprise Integration Packages Components and __________Licenses_________________________________________ License Component_Name________________________Version_____PAK_Name_ HP Advanced Server for OpenVMS 7.3A ECO4 PWLMXXXCA07.03 ___________________________________________________________ HP Archive Backup System HP Archive Backup System for 4.3 ABS-OMT OpenVMS Management Tools HP Archive Backup System NT 4.3 ABS_NT_ Client software CLIENT_ USER ___________________________________________________________ HP DECnet-Plus for OpenVMS Alpha, 8.2 DVNETEND End System ___________________________________________________________ HP DECwindows Motif HP DECwindows Motif for OpenVMS 1.5 DW_MOTIF Alpha ___________________________________________________________ HP PATHWORKS for OpenVMS (Advanced 6.1 PWLMXXXCA06.01 Server) ___________________________________________________________ HP PATHWORKS 32 V7.4 PWXXWINAT07.03 (continued on next page) 1-2 Overview Table 1-1 (Cont.) HP Enterprise Integration Packages __________________Components_and_Licenses__________________ License Component_Name________________________Version_____PAK_Name_ ___________________________________________________________ Compaq Office Server for OpenVMS 6.1 See the instal- lation guide.[1] ___________________________________________________________ HP TCP/IP Services for OpenVMS 5.5 UCX ___________________________________________________________ HP DECprint Supervisor (DCPS) for OpenVMS Alpha[2] Open 2.4 license not required Plus 2.4 license not required ___________________________________________________________ [1]This_product_has_multiple_license_certificates._See_the_ product's Installation Guide for details. [2]Beginnning with Version 2.0, rights to this product are included in the operating system license, and separate licenses are not required. The DECprint licenses have been removed from EIP as of September, 2001. ___________________________________________________________ 1.2 Mounting a CD on OpenVMS To access documentation and files on the CDs described in this document, insert the CD into the drive and mount the CD using the following command: $ MOUNT/MEDIA_FORMAT=CDROM/OVERRIDE=ID cd-device where cd-device is the CD drive. Overview 1-3 1.3 Installation Documentation In general, you install products using the VMSINSTAL or the POLYCENTER Software Installation (PCSI) utilities, as described in Chapter 3. Each product also has its own Installation Guide, which you should consult. For products on the SPL multi-CD set, Installation Guides and other documentation are on the Online Documentation Library (ODL) CDs, which accompany the SPL. Some products in the SPL are on their own CDs. The following sections explain how to access the Installation Guides for these products. Documentation is also available on the Internet for some products, in which case the URL is provided. 1.3.1 HP PATHWORKS 32 Documentation The documentation for this product is in ASCII text and PostScript formats, on the product CD included in the SPL. It contains the Software Product Description (.txt and .ps), User's Guide (.txt and .ps), and Application Programming Interfaces Manual (.ps only). Installation information is in the User's Guide. The CD also includes the eXcursion User's Guide (.ps only). Print the file README_PRINT_DOCS.TXT, which contains information necessary to print the other documents, as follows. Insert the CD and: OpenVMS: Mount the CD. Print the file: $ PRINT cd-device:[000000]README_PRINT_DOCS.TXT Windows XP Professional, Windows 2000, Windows 98 or Windows NT: Open the file with an application that can read an ASCII text file, such as Notepad, and print it. 1-4 Overview Follow the directions in this file to print the documentation. At a minimum, print Part 1 of the User's Guide, which contains the information necessary to install and configure the product. Overview 1-5 2 _________________________________________________________________ Preparing to Install the HP Enterprise Integration Packages This chapter describes the preparation for installing the Enterprise Integration Packages including: o Prerequisites for hardware, software, OpenVMS classes, installation account, and backup o Component disk space and installation times o Component preinstallation considerations o Licensing requirements o Modifying the system parameters 2.1 Prerequisites for Installation The following sections contain requirements for hardware, software, OpenVMS classes, installation account and backup. 2.1.1 Back Up Your System Disk Perform a backup of your system disk before installing any software. Use the backup procedures that have been established at your site. See the OpenVMS System Managers Manual: Essentials and the OpenVMS System Management Utilities Reference Manuals in the OpenVMS operating system documentation for more information. 2.1.2 Hardware Requirements The Enterprise Integration Packages support all valid OpenVMS Alpha CPU configurations. The Enterprise Integration Server for OpenVMS License Package products require 64 MB of memory, 525MB (1.05 M blocks) of disk space during installation, and 512MB (1 M blocks) of disk space after installation. Preparing to Install the HP Enterprise Integration Packages 2-1 2.1.3 Software Requirements Enterprise Integration Packages Release 3.5 component versions are fully supported only on OpenVMS Alpha 8.2. HP strongly recommends that you upgrade to this operating system version. See the individual component SPDs or installation guides for components that support other versions of OpenVMS. 2.1.4 Installation Account Requirements Install the products from an installation account with: o Full privileges (SETPRV) o Account quotas specified in the following table: Table_2-1_Minimum_Installation_Account_Quotas______________ R3.0, R3.1, Parameter_______R3.2_Value____R2.0_Value___________________ ASTLM 200 250 BIOLM 10 000 150 BYTLM 300 000 64 000 DIOLM 200 150 ENQLM 2 048 2 048 FILLM 300 300 PRCLM 10 3 PGFLQUOTA 65 000 65 000 WSEXTENT 16 384 16 384 TQELM 200 200 WSDEF 1 024 2 000 WSQUO 2 048 4 000 JTQUOTA____________4_096_________4_096_____________________ 2.1.5 Checking and Setting Process Account Quotas The file SYSUAF.DAT contains user account quotas. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: 2-2 Preparing to Install the HP Enterprise Integration Packages $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the (UAF) prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SYSTEM To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SYSTEM account and then exits from the utility: UAF> MODIFY SYSTEM /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, refer to the description of the Authorize Utility in the OpenVMS System Management Documentation Subkit. 2.1.6 OpenVMS Class Requirements The Enterprise Integration Packages-related components require that you have installed all the OpenVMS default classes. 2.2 Component Disk Space and Installation Times Table 2-2 lists disk space needed for Enterprise Integration Packages components during and after installation. It also lists the approximate installation times, based on CD installations. This does not include the time needed for pre- and postinstallation configuration tasks, or for running the Installation Verification Procedures (IVPs). Preparing to Install the HP Enterprise Integration Packages 2-3 Table_2-2_Disk_Space_and_Installation_Time_______________________ Blocks Blocks During After Time Component________________________________InstallationInstallation(Minutes) HP Advanced Server for OpenVMS 139 500 139 500 10 HP Archive Backup System for OpenVMS 50 000 50 000 Management Tools HP DECnet-Plus for OpenVMS Alpha (End 89 000 89 000 4 System) Base Kit 82 000 82 800 5 OSAK 5 000 6 900 5 FTAM 28 000 28 000 5 VT 4 000 3 500 5 HP DECprint Supervisor (DCPS) for 7 400 6 900 5 OpenVMS Alpha (Open and Plus) HP DECwindows Motif for OpenVMS Alpha 317 000[1] 210 000[1] 20 [1] Compaq Office Server for OpenVMS 277 500 277 500 90 HP PATHWORKS for OpenVMS (Advanced 226 000 126 732 10[2] Server) HP TCP/IP Services for OpenVMS 125 000 125 000 5 [1]The_POLYCENTER_Software_Installation_Utility_Version_1.0_is___ required when installing on V7.1 systems. [2]During this installation you will be prompted for PATHWORKS for OpenVMS (NetWare). Answer "No"-it is not licensed with Enterprise Integration Packages. _________________________________________________________________ 2.3 Preinstallation Considerations 2.3.1 Register Each License You must register the software license for each component with the OpenVMS License Management Facility (LMF) before you install the component. The Product Authorization Keys (PAKs) that are shipped with the Enterprise Integration Packages contain the license registration information you need. 2-4 Preparing to Install the HP Enterprise Integration Packages 2.3.2 DECnet-Plus Component Restrictions Some Enterprise Integration Packages components have restrictions about the use of DECnet-Plus: o PATHWORKS for OpenVMS (Advanced Server) This component does not support the use of long names. It will work with DECnet-Plus using node synonyms (allowing the continued use of the standard 6-character node name). o TCP/IP Services for OpenVMS If you plan to use the DECnet-Plus over TCP/IP feature, then TCP/IP software is a prerequisite. Your end system will be able to operate over TCP/IP only if the TCP/IP product used on your system supports the PATHWORKS Internet Protocol (PWIP) interface. 2.3.3 TCP/IP Services for OpenVMS Considerations If you plan to use the DECnet-Plus over TCP/IP feature of DECnet-Plus, then TCP/IP software is a prerequisite. Your end system will be able to operate over TCP/IP only if the TCP/IP product used on your system supports the PATHWORKS Internet Protocol Interface (PWIP). 2.3.4 HP Enterprise Integration Extension License Package for NAS 200 If you have NAS 200, you have licenses for some, but not all, of the products in Enterprise Integration Packages. The Enterprise Integration Extension License Package for NAS 200 gives you licenses for the Enterprise Integration Packages products that are not licensed by NAS 200. 2.3.5 OpenVMS Cluster License Requirements There may be restrictions on how certain products are licensed. Refer to the individual product documentation for details. Preparing to Install the HP Enterprise Integration Packages 2-5 2.4 Modifying System Parameters The following sections describe: o Using MODPARAMS_EIS.DAT to update system parameters o Calculating the values for GBLPAGES and GBLSECTIONS o Checking system parameter values o Changing system parameter values with AUTOGEN 2.4.1 DECnet-Plus System Parameter Considerations If you are using Phase IV names with DECnet-Plus, you must determine the values for SCSNODE,SCSSYSTEMID, and SYSMWCNT (see the PATHWORKS[TM] Version 6.1 for OpenVMS (Advanced Server) Server Installation and Upgrade Guide). For example: SCSNODE = same as DECnet node name for the server SCSSYSTEMID = (1024x DECnet area number) + DECnet node number SYSMWCNT = current value of SYSMWCNT + (number of GBLPAGES being added / 128) Round up SYSMWCNT to the nearest integer. For example, if you are using GBLPAGES=78 000 to install PATHWORKS Version 6.0D for OpenVMS, add an additional 610 to SYSMWCNT. 2.4.2 OpenVMS Cluster System Parameters If you are in an OpenVMS Cluster environment, SCSNODE and SCSSYSTEMID should already be appropriately set. If you must change SCSNODE to make it the same as the DECnet[TM] node name, you must also create a new queue file and redefine the queues. See the OpenVMS system management documentation for instructions on this procedure. 2-6 Preparing to Install the HP Enterprise Integration Packages 2.4.3 Using MODPARAMS_EIS.DAT to Update System Parameters The Enterprise Integration Packages provide the data file, MODPARAMS_EIS.DAT, that includes the minimum parameters necessary to install all the Enterprise Integration Packages components on OpenVMS Alpha. (Table 2-3 lists the parameter requirements for all the components.) The MODPARAMS_EIS.DAT file enables you to optimize preinstallation tasks in the following ways: o You can reset all your system parameters. o You will need only one system reboot. To reset all your system parameters using MODPARAMS_ EIS.DAT: 1. Find MODPARAMS_EIS.DAT in the [DEIS030.DOCUMENTATION] directory; to locate the volume number of the CD where this directory resides, refer to your SPL master index. 2. Append the MODPARAMS_EIS.DAT file to the end of SYS$SYSTEM:MODPARAMS.DAT. 3. After combining the two files, delete the lines that contain the lower values if there are two values for the same MIN_parameter. 4. Use AUTOGEN to tune the parameters based upon your system workload. 5. Reboot the system. You may need to increase the parameters specified in these files, depending on what other products are installed on your system. 2.4.4 Calculating the Values for Global Pages (GBLPAGES) and Global Sections (GBLSECTIONS) To install and run the Enterprise Integration Packages, you must have sufficient free global pages (GBLPAGES) and global sections (GBLSECTIONS). Table 2-3 specifies the unused global sections and unused global pages your system needs for the installation to execute successfully. Preparing to Install the HP Enterprise Integration Packages 2-7 To calculate how many unused global pages and global sections your system has: 1. Run the Install utility (INSTALL) using the following command: $ INSTALL LIST /GLOBAL /SUMMARY The Install utility displays a summary of global pages and global sections used by your system, as well as the current number of unused global pages. For example: Summary of Memory Global Sections 258 Global Sections Used, 22580/3420 Global Pagelets Used/Unused 2. Determine if the number of unused global pages (3420 in the example) is equal to or greater than what you need. If the number of unused pages is less than what you require, you need to increase the value for GBLPAGES. 3. Note the amount shown for global sections used (258 in this example). 4. Run the System Generation utility (SYSGEN) and use the SHOW command to determine how many global sections have been allocated. For example: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections 5. Add the amount shown in the example summary in step 1 (258) to the value for GBLSECTIONS in Table 2-3. If the resulting value is greater than the value for currently available GBLSECTIONS as shown in step 4, you must increase the value of the GBLSECTIONS parameter. Section 2.4.7 describes the procedures for increasing these values using AUTOGEN. See the OpenVMS System Management Utilities Reference Manuals or the OpenVMS System Manager's Manual for information on using AUTOGEN. 2-8 Preparing to Install the HP Enterprise Integration Packages You can use the WRITE command with the F$GETSYI lexical function to find the number of contiguous free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 2.4.5 System Parameter Requirements Table 2-3 lists the system parameters required if you install all of the components of the Enterprise Integration Packages. These system parameters are provided in the file MODPARAMS_EIS.DAT. See Section 2.4.7 to fine tune system parameters for the particular work load needs of your system. ________________________ Note ________________________ A system reboot is necessary to incorporate system parameter changes and should be done using AUTOGEN (see Section 2.4.7). ______________________________________________________ Table_2-3_System_Parameter_Requirements_for_R3.0___________ R3.0, R3.1 Parameter_______Value_________R2.0_Value____Notes__________ GBLPAGES 275 000[1] 275 000[1] GBLPAGFIL 3 248[1] 3 248[1] GBLSECTIONS 1 525[1] 1 525[1] MAXPROCESSCNT 50 50 CLISYMTBL 750 512 [1]The_values_given_are_the_number_of_free_(unused)_pages__ and sections that must be available before installation. (continued on next page) Preparing to Install the HP Enterprise Integration Packages 2-9 Table_2-3_(Cont.)_System_Parameter_Requirements_for_R3.0___ R3.0, R3.1 Parameter_______Value_________R2.0_Value____Notes__________ RESHASHTBL 2 048 2 048 WSMAX 32 768 32 768 CHANNELCNT 255 568 Or any number larger than the largest FILLM used on the system (whichever is larger). MAXBUF 8 192 8 192 If Motif is loaded. PROCSECTCNT 100 100 SWPOUTPGCNT 512 512 NPAGEDYN 1 998 848 1 642 000 PAGEDYN 901 120 901 120 NPAGEVIR 6 496 256 6 496 256 KSTACKPAGES 2 2 WINDOW_SYSTEM 1 1 LOCKIDTBL 45 000 CTLPAGES 100 PQL_MJTQUOTA 4 096 PQL_MTQELM 200 PQL_MASTLM 200 210 PQL_MBIOLM 10 000 100 PQL_MBYTLM 300 000 100 000 PQL_MDIOLM 200 100 PQL_MENQLM 2 048 350 PQL_MFILLM 300 100 PQL_MPGFLQUOTA 65 000 32 768 PQL_MPRCLM 10 10 (continued on next page) 2-10 Preparing to Install the HP Enterprise Integration Packages Table_2-3_(Cont.)_System_Parameter_Requirements_for_R3.0___ R3.0, R3.1 Parameter_______Value_________R2.0_Value____Notes__________ PQL_MWSDEFAULT 1 024 1 024 PQL_MWSEXTENT 16 384 8 192 PQL_MWSQUOTA 2 048 2 048 GH_RES_CODE 1 024 1 024 GH_RSRVPGCNT 2 000 2 000 IMGREG_PAGES 2 000 2 000 SCSNODE - - See the discussion in Section 2.4. SCSSYSTEMID - - See the discussion in Section 2.4. SYSMWCNT - - See the discussion ____________________________________________in_Section_2.4. 2.4.6 Checking System Parameter Values To check the values of your system parameters: 1. Enter the following command at the DCL prompt to invoke the System Generation (SYSGEN) utility: $ RUN SYS$SYSTEM:SYSGEN The screen displays the SYSGEN> prompt. 2. Enter the SHOW command and a system parameter name to display the value of that parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 2-3 for the Enterprise Integration Packages package you are installing. For example, the following command displays the value for the WSMAX system parameter: SYSGEN> SHOW WSMAX Preparing to Install the HP Enterprise Integration Packages 2-11 3. After checking the parameters, enter EXIT at the SYSGEN> prompt to return to the DCL level. 2.4.7 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. Each Enterprise Integration Packages component has its own system parameter requirements. If the components are treated separately, you will have to reboot, using AUTOGEN, for each component. See the individual component installation guides for detailed preinstallation information. ________________________ Note ________________________ You can avoid multiple reboots if you use MODPARAMS_ EIS.DAT as described in Section 2.4.3. ______________________________________________________ To change system parameters with AUTOGEN: 1. Edit the file SYS$SYSTEM:MODPARAMS.DAT using these guidelines: o To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. o To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example: WSMAX = 4200 o To modify incremental parameters such as GBLPAGES and GBLSECTIONS, use ADD_. For example, the following increases the global page setting by 2000: ADD_GBLPAGES = 2000 When you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. 2-12 Preparing to Install the HP Enterprise Integration Packages OpenVMS recommends that you use MIN_parameter to set parameters in MODPARAMS.DAT. (An exception does exist: values for NPAGEDYN are additive.) Add the values supplied in Table 2-3 to the current system values. Use SYSGEN to determine the current values of NPAGEDYN and NPAGEVIR. For example: $ MCR SYSGEN SYSGEN> USE ACTIVE SYSGEN> SHOW NPAGEDYN Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- NPAGEDYN 4884992 360000 16384 -1 Bytes The current column shows what your system is currently using. In this example you would add a line in the following format to your MODPARAMS.DAT file: MIN_NPAGEDYN = 4884992 + value-from-sys-param-table In this format, value-from-sys-param-table is the value from Table 2-3. 2. Exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Reboot using the following command: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT ________________________ Note ________________________ When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged in to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. ______________________________________________________ The AUTOGEN utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, refer to the OpenVMS System Manager's Manual: Essentials. Preparing to Install the HP Enterprise Integration Packages 2-13 3 _________________________________________________________________ Installing the HP Enterprise Integration Packages Components This chapter describes the following: o An installation checklist o Using the VMSINSTAL Utility o Using the POLYCENTER Software Installation Utility (PCSI) o Component installation order and dependencies o Component installation o Identifying and reporting errors 3.1 HP Enterprise Integration Packages Installation Checklist Table 3-1 lists the major steps in installing components. Table 3-1 Enterprise Integration Packages Installation __________Checklist________________________________________ Check_Step___Description___________Text_References_________ < > 1 Decide which Table 1-1, Table 3-2, components you need. and the component SPDs < > 2 Work from an Table 2-1, Table 2-2, installation account Table 2-3 with full privileges (SETPRV), and the required quotas and disk space. < > 3 Back up your system. Section 2.1.1 (continued on next page) Installing the HP Enterprise Integration Packages Components 3-1 Table 3-1 (Cont.) Enterprise Integration Packages __________________Installation_Checklist___________________ Check_Step___Description___________Text_References_________ < > 4 Register the Table 1-1, Section 2.3 component licenses. < > 5 Modify system Section 2.4 parameters and reboot. < > 6 Install the Table 3-2 components in the _____________order_specified.______________________________ 3.2 Using the VMSINSTAL Utility Use the VMSINSTAL utility to install most of the Enterprise Integration Packages components. A few products, identified in Table 3-2, require the POLYCENTER Software Installation Utility described in Section 3.3. To use VMSINSTAL: 1. Set your default directory to SYS$UPDATE. 2. Invoke VMSINSTAL using a command in the following format: $ @SYS$UPDATE:VMSINSTAL save-set-name device-name: OPTION N In this format: o save-set-name is the name of the save set you are installing. o device-name is the name of the device on which you are installing. If you do not supply these two parameters, VMSINSTAL prompts you for the product and device names. If you want to be prompted for the product and device names and to display or print the release notes, use the following format: $ @SYS$UPDATE:VMSINSTAL "" "" OPTIONS N 3-2 Installing the HP Enterprise Integration Packages Components 3.2.1 Error Detection and Follow Up If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. If you have any questions about whether you should continue, see the appropriate Enterprise Integration Packages component installation guide. To stop the installation process and correct the situation, enter N and press Return. Then correct the problem and restart the installation. Some of the problems may include: o You are not logged in to a privileged account. HP recommends that you install software from the system manager's account with your default device and directory set to SYS$UPDATE. o You do not have adequate quotas for installation. o Other users are logged in to the system. 3.3 Using the POLYCENTER Software Installation Utility Some of the Enterprise Integration Packages components, identified in Table 3-2, are provided in POLYCENTER Software Installation format. PCSI distributions have advantages over traditional VMSINSTAL kits, such as improved installation speed and the ability to track and deinstall products at a later date. ________________________ Note ________________________ Read the component installation guides before performing an installation using PCSI. Each component's installation guide provides the specific installation commands for that component. ______________________________________________________ 3.4 Component Installation Order and Dependencies Table 3-2 provides the installation order and dependencies for all the components provided through the Enterprise Integration Packages. Information in Table 3-2 is organized in the following columns: o Component Name Installing the HP Enterprise Integration Packages Components 3-3 Lists all the Enterprise Integration Packages components. You can select any components you want but they must be installed in the order shown. o Installation File Name Lists the names of the initial files used to install a product. The file name consists of the component identifier followed by an appropriate file extension type, as shown in the following example: DEC-AXPVMS-DWMOTIF-V0102-5-1.PCSI DEC-AXPVMS-DWMOTIF-V0102-5-1 is the component identifier and .PCSI is the file extension. o Dependencies Indicates component dependencies. These products must be installed on your system before you can install or run a specific component. There are five types of file extensions. Each requires a different installation method. 1. .A Files with .A extensions represent the first file of a possible set of files required to install a product using VMSINSTAL. (See Section 3.2.) 2. .COM Files with .COM extensions are OpenVMS DCL command procedures used to install a product or group of products. 3. .ZIP Files with .ZIP extensions are compressed files. Using .ZIP files requires that you have PKZIP and PKUNZIP installed on your PC. 4. .EXE Files with .EXE extensions are executable files. Use them as you would a .COM file. 5. .PCSI Files with .PCSI extensions are installation files. Use them as you would a VMSINSTAL file. 3-4 Installing the HP Enterprise Integration Packages Components Table 3-2 Component Installation Order, Installation File Names, __________and_Dependencies_______________________________________ Component Name Installation File Name ____Dependencies_________________________________________________ HP DECwindows Motif Version 1.5 DEC-AXPVMS-DWMOTIF- V0105-1.PCSI$COMPRESSED Dependencies: Requires OpenVMS Version 8.2. _________________________________________________________________ HP Advanced Server Version 7.3A ECO4 CPQ-AXPVMS- ADVANCEDSERVER-V0703- A4-1.PCSI Dependencies: Requires OpenVMS version 7.3-1, 7.3-2, or 8.2. _________________________________________________________________ HP TCP/IP Services for OpenVMS Version DEC-AXPVMS-TCPIP-V0505- 5.5 11-1.PCSI$COMPRESSED Dependencies: Requires OpenVMS version 8.2 _________________________________________________________________ HP DECnet-Plus for OpenVMS Alpha (End DEC-AXPVMS-DECNET_OSI- System) Version 8.2 V0802-1.PCSI$COMPRESSED Dependencies: 1. Requires OpenVMS version 8.2. 2. Requires HP TCP/IP Services for OpenVMS if you are using DECnet-Plus over TCP/IP. _____________________________________________________________ OSAK HP-AXPVMS-OSAK-V0300-T- 1.PCSI Dependencies: OSAK must be installed and started first if you plan to install the optional FTAM or VT software. _____________________________________________________________ FTAM HP-AXPVMS-FTAM-V0301-P- 1.PCSI (continued on next page) Installing the HP Enterprise Integration Packages Components 3-5 Table 3-2 (Cont.) Component Installation Order, Installation File __________________Names,_and_Dependencies________________________ Component Name Installation File Name ____Dependencies_________________________________________________ Dependencies: None _____________________________________________________________ VT HP-AXPVMS-VT-V0201-K- 1.PCSI Dependencies: LAT and TCP/IP must be installed and started before VT can be installed. _________________________________________________________________ HP DECprint Supervisor Version 2.4 HP-AXPVMS-DCPS-V0204- 1.PCSI Dependencies: 1. Requires DECwindows Motif. 2. Requires TCP/IP Services for OpenVMS Version 5.1 or greater for Raw TCP/IP configuration only. 3. The Job Queue Manager must be running prior to installation. 4. Depending on your configuration, there may be other products that you will need to install. _________________________________________________________________ Compaq Office Server for OpenVMS A1061.A Version 6.1 Dependencies: Requires: 1. OpenVMS Version 7.2-1 or higher; 2. DECnet for OpenVMS Version 1.5 or higher; 3. DECnet-Plus for OpenVMS Version 6.2 or higher. _________________________________________________________________ (continued on next page) 3-6 Installing the HP Enterprise Integration Packages Components Table 3-2 (Cont.) Component Installation Order, Installation File __________________Names,_and_Dependencies________________________ Component Name Installation File Name ____Dependencies_________________________________________________ HP PATHWORKS for OpenVMS (Advanced PWRK061.A Server) Version 6.1[4] Dependencies: 1. Requires OpenVMS Version 7.3.1, 7.3-2, 8.2 2. If the transport you use is DECnet, you must also use TCP/IP; and if you use TCP/IP as your transport, you must also use DECnet. _________________________________________________________________ HP Archive Backup System Version 4.3 ABSB043.A Dependencies: Requires: 1. OpenVMS 6.2, 7.1-2, 7.2-2, 7.3, 7.3-1, 7.3-2 and 8.2 2. DECnet-Plus for OpenVMS or TCP/IP Services for OpenVMS _________________________________________________________________ HP PATHWORKS 32 Refer to product documentation. [4]During_this_installation_you_will_be_prompted_for_PATHWORKS___ for OpenVMS (NetWare). Answer "No"- it is not licensed with the Enterprise Integration Packages. _________________________________________________________________ 3.5 Component Installation Refer to the individual product installation guides for instructions on installing the components. Install the components according to the order listed in Table 3-2. Installing the HP Enterprise Integration Packages Components 3-7 3.6 Identifying and Reporting Installation Problems If an error occurs that you believe is caused by a problem with the Enterprise Integration Packages installation, see the release notes for the individual component products. If the release notes do not provide a solution, do one of the following: o If you have a BASIC or DECsupport Software Agreement, call your Customer Support Center. o If you have a Self-Maintenance Software Agreement, submit a Software Performance Report (SPR) for the component exhibiting problems. o If neither of the previous statements describes your situation and you are under warranty, submit an SPR for the component exhibiting problems. Include the name of the problem component when you call or file an SPR. 3-8 Installing the HP Enterprise Integration Packages Components A _________________________________________________________________ Ordering Hardcopy Documentation Documentation order numbers for Enterprise Integration Packages components are as follows: Table_A-1_Documentation_Order_Numbers______________________ Component_____________Order_Number__________Notes__________ HP DECnet[TM] for QA-MT3AE-GZ DECnet for OpenVMS, End System OpenVMS Guide to Networking DECnet-Plus for QA-MTFAA-GZ OpenVMS Alpha End System DECprint Supervisor QA-09NAA-GZ (DCPS) for OpenVMS Alpha DECwindows Motif QA-XA1AA-GZ User for OpenVMS Alpha QA-XA1AB-GZ documentation Programming Documentation TCP/IP Services for QA-0LXAA-GZ OpenVMS Alpha PATHWORKS for QA-A93AA-GZ OpenVMS (Advanced Server) PATHWORKS_32__________QA-5LKAA-GZ__________________________ Ordering Hardcopy Documentation A-1 _________________________________________________________________ Index A GBLSECTIONS _______________________________ calculating values, 2-7 AUTOGEN used to modify system H______________________________ parameters, 2-12 HP Enterprise Integration B Packages _______________________________ components Backing up the system disk, identified, 1-2 2-1 I______________________________ C______________________________ Installation checklist, 3-1 Checklist installation, 3-1 L______________________________ D License _______________________________ registration, 2-4 DECnet-Plus system parameters, 2-6 M______________________________ Disk space MODPARAMS_EIS.DAT files, 2-7 required install, 2-3 E O______________________________ _______________________________ OpenVMS Cluster Enterprise Integration license requirements, 2-5 Packages system parameters, 2-6 license registering, 2-4 P _______________________________ G______________________________ PCSI GBLPAGES See POLYCENTER Software calculating values, 2-7 Installation Index-1 POLYCENTER Software with AUTOGEN, 2-12 Installation Utility (PCSI), OpenVMS Cluster, 2-6 3-3 required to install Process account quotas, Enterprise Integration checking and setting, 2-2 Packages components, 2-9 _______________________________ T______________________________ System disk TCP/IP Services for OpenVMS backing up, 2-1 installation considerations, System parameters 2-5 checking, 2-11 Time DECnet-Plus, 2-6 required to install, 2-3 modifying, 2-6 using MODPARAMS_EIS.DAT V______________________________ files, 2-7 VMSINSTAL, 3-2 Index-2