Digital DEC/EDI Installation Compaq Computer Corporation Houston, Texas Revised for Software Version: Digital DEC/EDI V4.0 November 2001 (c)Compaq Computer Corporation 1990,2001 Compaq, the Compaq logo, and VMS Registered in U.S. Patent and trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX is a trademark of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq 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. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. This document is the property of, and is proprietary to Compaq Computer Corporation. It is not to be disclosed in whole or in part without the express written authorization of Compaq Computer Corporation. No portion of this [enter document] shall be duplicated in any manner for any purpose other than as specifically permitted herein. Compaq service tool software, including associated documentation, is the property of and contains confidential technology of Compaq Computer Corporation. Service customer is hereby licensed to use the software only for activities directly relating to the delivery of, and only during the term of, the applicable services delivered by Compaq or its authorized service provider. Customer may not modify or reverse engineer, remove, or transfer the software or make the software or any resultant diagnosis or system management data available to other parties without Compaq's or its authorized service provider's consent. Upon termination of the services, customer will, at Compaq's or its service provider's option, destroy or return the software and associated documentation in its possession. Printed in the U.S.A. The following are trademarks of Compaq Computer Corporation : DEC, DEC/EDI, DIGITAL, OpenVMS, and the Compaq logo. Adobe is a registered trademark of Adobe Systems Incorporated. BT is a registered trademark of British Telecommunications plc. InstallShield is a registered trademark of InstallShield Corporation. MS and Windows are registered trademarks, and Windows 95, Windows 98, Windows NT and Windows 2000 are trademarks, of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation. SAP is a registered trademark of SAP AG. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks not listed above are acknowledged as the the property of their respective holders. Contents Preface Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii How to Use this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Digital DEC/EDI Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Digital DEC/EDI InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Related Third Party Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Chapter 1 Preparing to Install Digital DEC/EDI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Digital DEC/EDI System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Application Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Product Installation Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Digital DEC/EDI User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Digital DEC/EDI INTERCHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Establishing the Configuration of Your System . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Single Node System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Multi-node Client/Server System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Cockpit and CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 iv Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Communication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Digital DEC/EDI Message Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Application Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Tru64 UNIX, Sun Solaris, HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Application Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Tru64 UNIX, Sun Solaris, HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 RedHat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Cockpit and CommandCenter Configuration . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Windows NT, Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Database Configuration (ODBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Server Communications Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Chapter 2 Installation Activities Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Setting Up the Server and Local Application Clients . . . . . . . . . . . . . . . . . . . 2-3 Setting Up Remote Application Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Setting Up the CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Setting Up the Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Configuring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 v Part I Network Configuration Chapter 3 Configuring the Network Interfaces Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Configuring the Digital DEC/EDI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 TCP/IP Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Pre-Configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Post-Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 For Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 TCP/IP Port Server Monitoring Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Configuring the Digital DEC/EDI Application Client . . . . . . . . . . . . . . . . . . . 3-8 TCP/IP Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Pre-Configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Post-Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 For Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Part II Database Administration Chapter 4 Configuring the Database Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Account Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Open VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Configurations Covered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Setting Up Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 A - Deciding Where to Locate the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Oracle8i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Typical Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 OpenVMS Oracle Rdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Performance Limiting Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 B - Creating the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 All Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 vi Typical Oracle 8i Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Typical Oracle Rdb Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Migrating the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Creating User Accounts for Database Access . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Digital DEC/EDI Access Control Editor . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Tru64 UNIX Oracle8i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 OpenVMS Oracle Rdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Oracle User Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Configuring the Database Network Connectivity . . . . . . . . . . . . . . . . . . . . . 4-12 OpenVMS Oracle SQL Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Tru64 UNIX Oracle 8i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 Part III Software Installation Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Preparing to Install Digital DEC/EDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Additional Information on Digital DEC/EDI Subsets . . . . . . . . . . . . 5-6 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Registering Your Software Licenses on Digital Systems . . . . . . . . . . . . . 5-8 Registering Licenses on Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . 5-10 Installation Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Database Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Run Time Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 vii TCP/IP Link Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Checking Tru64 UNIX Documentation Subset is Installed . . . . . . . . 5-14 Checking that Oracle8i is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Setting Oracle8i Environment Variables . . . . . . . . . . . . . . . . . . . . . . 5-16 Running the Oracle8i Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Checking for Individual Oracle8i Components . . . . . . . . . . . . . . . . . 5-16 Checking for the Server Manager and DBMS . . . . . . . . . . . . . . . . . . 5-17 Checking for Oracle8i SQLPLUS . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Checking for TCP/IP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Checking Mailbus 400 is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Checking DEC X.25 is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Checking the Digital DEC/EDI account . . . . . . . . . . . . . . . . . . . . . . 5-18 Adding a Digital DEC/EDI Account . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 Determining Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Deleting Digital DEC/EDI from Your System . . . . . . . . . . . . . . . . . . . . . 5-21 Backing Up Your System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Installing Digital DEC/EDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Stopping the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Time Required for Complete Installation . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Installing From CD-ROM Consolidated Distribution Media . . . . . . . . . . 5-24 Installing From a Remote Installation Services (RIS) Distribution Area . 5-25 Running the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26 Specifying Subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26 Messages Displayed During the Loading Process . . . . . . . . . . . . . . . 5-28 Problems During Product Installation . . . . . . . . . . . . . . . . . . . . . . . . 5-28 Files Created During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29 After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29 Installation Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29 Running the Installation Verification Procedure . . . . . . . . . . . . . . . . . . . 5-30 Setting Up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Problems After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32 Chapter 6 OpenVMS - Installation of Server and Client Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Prerequisites - All Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 viii Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Software Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Mapping Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 OpenVMS Alpha Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Mandatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Pedi Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 3780Plus Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Application Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Supported Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 OpenVMS Alpha Application Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Mandatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Software Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Privileges For The Installing Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Disk Space Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Determining Diskspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10 Checking System Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11 Calculating Values for GBLPAGES and GBLSECTIONS . . . . . . . . . . . 6-12 Changing System Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Account Quotas For The Installing Account . . . . . . . . . . . . . . . . . . . . . . . . . 6-14 Changing Account Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 Other Pre-Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Accessing the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Files and Logical Names Added to Your System . . . . . . . . . . . . . . . . . . 6-16 Running the Installation Verification Procedure (IVP) . . . . . . . . . . . . . . 6-16 VMSINSTAL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Aborting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Time to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Information Needed During Installation . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Upgrades Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Installation: Client On Top Of Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19 Installation: Server On Client-Only System . . . . . . . . . . . . . . . . . . . . . . . . . 6-19 Upgrading to V4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 ix General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Installing on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Migration Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 All Services on a Single Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21 Multinode System with Translation and Communications all on One Node 6-21 The Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22 Starting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23 About Client-Only Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25 Warning if you are Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25 Remainder of the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27 Installation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28 Completing the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29 Installing the Message Update Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30 After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31 Editing the System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32 System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32 Network and Rdb Monitor Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33 Defining Digital DEC/EDI Logical Names . . . . . . . . . . . . . . . . . . . . . . . 6-33 Using the Correct Pascal Run-Time Library . . . . . . . . . . . . . . . . . . . . . . 6-34 Modifying the System Page File Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34 Re-booting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35 Re-naming the Digital DEC/EDI Error Log . . . . . . . . . . . . . . . . . . . . . . . 6-35 Modifying User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36 Page File Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36 Access From a Local Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36 Adding Symbols to User's LOGIN.COM . . . . . . . . . . . . . . . . . . . . . 6-36 Determining and Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . 6-37 The DECEDI Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38 Increasing Disk Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39 Calculating the Required Number of Processes . . . . . . . . . . . . . . . . . 6-40 Modifying Quota for the DECEDI Account . . . . . . . . . . . . . . . . . . . . . . . 6-41 Calculating the WSEXTENT Value . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41 Calculating the ENQLM Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41 Ownership of the DECEDI Account . . . . . . . . . . . . . . . . . . . . . . . . . 6-42 Account privileges on the DECEDI Account . . . . . . . . . . . . . . . . . . 6-42 x Defining Mapping Service Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43 The Rights Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44 FBR$SUPERVISOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44 FBR$DEVELOPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45 FBR$OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46 Upgrades - Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46 Files Created During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46 Chapter 7 Other Platforms - Installation of Digital DEC/EDI Application Client Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Preparing to Install on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . 7-2 Checking Installation Procedure Requirements . . . . . . . . . . . . . . . . . 7-2 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Determining Which Subsets to Load . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . 7-3 Backing Up Your System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Preparing to Install on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Checking Installation Procedure Requirements . . . . . . . . . . . . . . . . . . . . 7-5 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Determining Which Subsets to Load . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . 7-6 Backing Up Your System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 Installing the Digital DEC/EDI Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8 Installing From CD-ROM Consolidated Distribution Media . . . . . . . . . . 7-8 Installing From an RIS Distribution Area . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 Running the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 Specifying Subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10 xi Messages Displayed During the Loading Process . . . . . . . . . . . . . . . 7-10 After Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11 After the Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11 Running the Installation Verification Procedure . . . . . . . . . . . . . . . . . . . 7-11 Deleting Digital DEC/EDI Application Client from Your System . . . . . 7-12 DIGITAL DEC/EDI Application Client on Redhat Linux . . . . . . . . . . . . . . . 7-12 Preparing to Install on Redhat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Checking the Installation Procedure Requirements . . . . . . . . . . . . . . . . . 7-13 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Backing up your System Disk: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14 Installing from the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14 After Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15 Configuring the Applicatin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15 Deleting DEC/EDI Application Client from your System . . . . . . . . . . . . 7-15 DIGITAL DEC/EDI Application Client on Windows NT/ 2000 . . . . . . . . . . 7-16 Preparing to Install on Windows NT/ 2000 . . . . . . . . . . . . . . . . . . . . . . . 7-16 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking the Installation Procedure Requirements . . . . . . . . . . . . . . . . . 7-16 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Installing from the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Chapter 8 Managing Message Updates Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Using the Message Update Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Tru64 UNIX and OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 xii Installing New Versions of EDI Standards . . . . . . . . . . . . . . . . . . . . . 8-3 Copying Existing Versions to New Ones . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Copying Data Labels Between Versions . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Deleting a Version of an EDI Standard . . . . . . . . . . . . . . . . . . . . . . . 8-4 Dealing with Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Where to Look If Things Go Wrong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Check your Cockpit or CommandCenter Kit . . . . . . . . . . . . . . . . . . . . . . 9-1 CommandCenter Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Cockpit Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Check for Prerequisite Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 Check for Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Backup your Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Additional Notes on Installing Pre-requisite Software . . . . . . . . . . . . . . . 9-5 Pre-Installation Tasks for Oracle 8i on the PC . . . . . . . . . . . . . . . . . . . . . 9-5 Checking for the Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Time to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Server Configuration Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12 Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13 General Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13 Tru64 UNIX Server - Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . 9-15 TCP/IP Network Interface related Problems . . . . . . . . . . . . . . . . . . 9-15 OpenVMS Server - Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 ODBC-related problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 Getting More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 The Digital DEC/EDI Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 ODBC Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19 SQL/Services Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19 Network Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 xiii TCP/IP Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21 Part IV System Verification Chapter 10 UNIX System Verification Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Beyond the Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3 An Example Application File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4 Preparation Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 A: Installing the Software and EDI Definitions . . . . . . . . . . . . . . . . . . . . . . . 10-6 B: Configuring the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9 Configure Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9 Register the Client Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10 Define Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11 C: Compiling the Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12 D: Defining Gateway and Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Defining the Gateways: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Creating the Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Enabling the Gateway and Connection . . . . . . . . . . . . . . . . . . . . . . . . . 10-14 E: Adding Trading Partner Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15 F: Restart the Digital DEC/EDI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17 G: Running the Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18 Sending the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18 Network Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20 Troubleshooting Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21 Tracing in the TCP/IP Client/Server Interface . . . . . . . . . . . . . . . . . . . . 10-21 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21 ODBC-related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21 Chapter 11 OpenVMS System Verification Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 xiv Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 About the Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Beyond the Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 An Example Application File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4 Preparation Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5 A: Installing the Software and EDI Definitions . . . . . . . . . . . . . . . . . . . . . . . 11-6 B: Configuring the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8 Granting User Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8 Configure Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9 C: Compiling the Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10 D: Configuring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 Registering the Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 Registering the Business Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 Registering a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12 E: Adding Trading Partner Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13 F: Start the Digital DEC/EDI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14 G: Running the Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15 Sending the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15 Network Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17 Troubleshooting Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18 ODBC Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18 SQL/Services Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19 Tracing in the TCP/IP Client/Server Interface . . . . . . . . . . . . . . . . . . . . 11-19 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19 ODBC-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21 Appendix A OpenVMS Server and Client Log of New Server and Client Installation on OPEN VMS AXP . . . . . . . . . . A-1 Log of Migration of Server and Client on OPEN VMS AXP . . . . . . . . . . . . . A-9 Appendix B OpenVMS Client only Log of New Client Installation of OPEN VMS AXP . . . . . . . . . . . . . . . . . . . B-1 Log of Migration of Client on OPEN VMS AXP . . . . . . . . . . . . . . . . . . . . . . B-4 xv Appendix C OpenVMS Message Updates Kit Appendix D Digital UNIX Server and Client Installtion Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Deinstalltion Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Appendix E DIGITAL UNIX Client only Appendix F DIGITAL UNIX Message Updates Appendix G Sun Solaris Client Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Deinstallation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Directory and File listing for SUN Solaris Client . . . . . . . . . . . . . . . . . . . . . . . 32 Appendix H HP-UX Client Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Installtion Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Configuration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Deinstallation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Directory and File listing for HP-UX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Appendix I RedHat Linux Client Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Configuration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Deinstallation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Directory and File listing for Redhat Linux Client . . . . . . . . . . . . . . . . . . . . . . 43 xvi Appendix J Directory and File listing for Windows NT/2000 Client Appendix K UNIX Installation - Directory and File Listing Appendix L OpenVMS Installation - Directory and File Listing Preface Purpose For Digital DEC/EDI Version 4.0 This book describes how to install the following Digital DEC/EDI components: • Server • Application Client • Message Updates • Cockpit • CommandCenter Enables you to perform basic system configuration, to ensure that Digital DEC/EDI is installed and configured correctly, and can communicate with other Digital DEC/EDI components installed within the same network. Audience This document is for anyone who wants to install, configure or support a Digital DEC/EDI installation.The audience for this book may be described in terms the activities required for a successful installation and basic configuration of a Digital DEC/EDI system. These activities may be performed by one or more people within your organization. Software Installation System Managers and Administrators who are responsible for installing Digital DEC/EDI and its related components on the required operating system. Network Configuration Network administrators who are responsible for performing any network configuration required to enable Digital DEC/EDI components located within the same network to communicate with one another. Database Administration Database administrators who are responsible for setting up the required user accounts, access rights or ODBC drivers for the database used by the Digital DEC/EDI software. For detailed configuration of Digital DEC/EDI and its external communications components please refer to the Digital DEC/EDI: User's Guides (Digital UNIX and Open VMS) Structure • Part 1 - describes the preparation necessary before starting installation. • Part 2 - describes network configuration • Part 3 - describes database installation and configuration • Part 4 - covers the Client and Server software installation • Part 5 - describes basic system verification • Part 6 - provides a set of appendices giving installation examples and a listing of the files installed. How to Use this Book This book details the preparation, installation, post-installation and basic configuration tasks that must be completed in order to successfully install the Digital DEC/EDI software components on the supported hardware and software platforms. The book also provides sample installation logs and screen captures for your guidance during the installation process. An existing user of the Digital DEC/EDI product wishing to upgrade or migrate to this version of Digital DEC/EDI, must read the chapter on upgrading and migration. Completion of all tasks stipulated is essential to successful upgrading or migration from a previous version of Digital DEC/EDI. The book is organized to enable easy location of information relating to the installation activities for the required Digital DEC/EDI configuration. Read Part I of this book from start to finish, and then read the sections that relate to the required Digital DEC/EDI configuration. Digital DEC/EDI Documentation This is one of a set of Digital DEC/EDI books. The complete list is as follows: • Digital DEC/EDI: Introduction This book introduces general EDI concepts, and Digital's EDI system, Digital DEC/EDI. It describes the main components of the Digital DEC/EDI system, and how business documents are processed and communicated to trading partners. The book seeks to establish the concepts and terms used by Digital DEC/EDI. These are also summarized in a glossary. You are strongly recommended to become familiar with the material in this book before proceeding to install or use Digital DEC/EDI. • Digital DEC/EDI: Installation This book describes how to install the Digital DEC/EDI software, how to perform basic system configuration and how to verify such an installation. It describes how to install the Application Client, Server, Cockpit and CommandCenter components. • Digital DEC/EDI: Application Development This book describes the Application Client interfaces and the means of connecting business applications to the Application Client. It also details the creation and deployment of mapping tables as part of the process of integrating applications with Digital DEC/EDI. • Digital DEC/EDI: User's Guides (Digital UNIX and Open VMS) These guides contain information on setting up and operating Digital DEC/EDI systems. They also contain information covering configuration, maintenance and problem solving. The term User's Guides is used throughout this book to refer to the following books which are provided along with the Digital DEC/EDI Server they describe. Digital UNIX Digital DEC/EDI: UNIX User Support Manual OpenVMS Digital DEC/EDI: OpenVMS User Support Manual - Volume 1 Digital DEC/EDI: OpenVMS User Support Manual - Volume 2 • Release Notes Further to the above, each software kit contains a set of release notes applicable to that software. These release notes contain information about known product problems (with workarounds where appropriate) and any operational tips or hints not provided as part of the above documentation set. You are strongly recommended to review these release notes before installing the software. Refer to the appropriate installation guide for information on how to locate the release notes. • On-line Documentation Comprehensive on-line documentation is supplied with the Digital DEC/EDI software: for example, on-line help libraries and UNIX man page help information. In addition the Digital DEC/EDI Cockpit and CommandCenter kits contains the Digital DEC/EDI: Error Messages Help Library. This contains all error messages the product may log along with a description of why the message occurred and what to do about it. It is provided in MS-Windows help library format. In addition, the CD-ROM provides on-line versions of all Digital DEC/EDI books in Adobe Acrobat format. Digital DEC/EDI InfoCenter For further information on Digital's EDI and Electronic Commerce Solutions and Services, please visit the EDI InfoCenter on the World Wide Web. The location is: http://www.decedi.com Related Third Party Documentation Refer to the documentation provided with third-party products for installation and configuration details. Typographical Conventions Some information within this guide is specific to the database product you are using in conjunction with Digital DEC/EDI. The following conventions are used to indicate such text: Oracle8 This indicates the adjoining paragraph contains information specific to running Digital DEC/EDI with the Oracle8 database. Similar conventions are used to indicate text specific to other components. For example: • Rdb refers to the Oracle(r) Rdb(tm) database. • V4.0 refers to Cockpit Version V4.0. Chapter 1 Preparing to Install Digital DEC/EDI This chapter describes what actions are necessary prior to installation of Digital DEC/EDI. Overview Before installing Digital DEC/EDI there are a number of things which need to be determined about your system, and the configuration in which you intend to run Digital DEC/EDI. It is not necessary to know everything about all the systems on which you will be using Digital DEC/EDI at this stage, as you may add further components or systems at a later date. Digital DEC/EDI System Configuration The collection of systems within the same network, on which Digital DEC/EDI and its components are installed, is known as the Digital DEC/EDI system configuration. The different parts are described on the following pages. Server The Server acts as a communications gateway, providing EDI mapping, translation and communications services for one or more Application Client systems. You may have one or more Server systems within your Digital DEC/EDI system configuration. 1-2 Digital DEC/EDI User Interfaces PREPARING TO INSTALL DIGITAL DEC/EDI A typical system configuration may have one Server for live EDI transactions, and another for backup or development use. Application Client The Application Client provides a file based interface to your business application, and may operate either via a command line or script- based interface, or via API calls directly from the business application. One or more Application Clients may communicate with the Server. The Application Client may reside on the same system as the Server, or may be on another system within the same network. A typical system may have many Application Clients communicating with a Server. Product Installation Documentation Installation instructions are provided in the documentation associated with each product described in this chapter. Digital DEC/EDI product documentation is described in Digital DEC/EDI Documentation on page -xv of the Preface. Digital DEC/EDI User Interfaces Cockpit The Cockpit is a monitoring and basic audit administration tool which runs on a PC connected to the Server. The Cockpit can be used to monitor multiple Servers simultaneously. Access controls enable you to restrict the data which may be either viewed or modified by a particular user of the Cockpit. A typical system may have multiple Cockpit installations for a number of users, each responsible for monitoring a particular set of business applications. CommandCenter The CommandCenter includes the Cockpit plus the ability to define Mapping Tables for integrating your business applications. The CommandCenter runs on a PC connected to the Server. For Tru64 UNIX Establishing the Configuration of Your System 1-3 PREPARING TO INSTALL DIGITAL DEC/EDI servers, the CommandCenter also includes a suite of applications for configuring and managing the Server. The CommandCenter may be used to manage one or more Servers simultaneously. A typical system may have multiple CommandCenter installations for a number of users, each responsible for integrating a particular set of business applications, or for configuring and managing one or more Servers. Digital DEC/EDI INTERCHANGE For OpenVMS servers, the INTERCHANGE user interface provides commands for configuring and managing the Server, and for monitoring EDI transactions. The INTERCHANGE user interface runs on the same system as the Server. Establishing the Configuration of Your System Digital DEC/EDI supports a number of different system configurations, and you must determine the desired system configuration before proceeding with the installation of Digital DEC/EDI and its components. The following section describes the supported configuration options, and directs you to the relevant parts of the Digital DEC/EDI documentation set that describe the installation of those options. Supported Configurations This section describes the supported configurations and interconnection options between the various components of Digital DEC/EDI. Single Node System Your business application runs on the same node as the Server, or you have a custom module which is responsible for transferring files to and from your business application. Your business application uses either the Application Client interface or one of the supported legacy interfaces (where available) to connect to the Server. The following figure shows a typical single node system configuration: 1-4 Establishing the Configuration of Your System PREPARING TO INSTALL DIGITAL DEC/EDI Figure 1-1 Single Node System Multi-node Client/Server System Your business application runs on a separate node from the Server and uses the Application Client interface to connect to the Server. The following figure shows a typical multi-node Client/Server system: Mapping Services Translation Services Communications Services Server Local Application Client Server System Data Label Translation API Bypass API Network Interface = Legacy interfaces, OpenVMS Only Trading Partners RedHat Linux Windows Client Application Client Application Client Establishing the Configuration of Your System 1-5 PREPARING TO INSTALL DIGITAL DEC/EDI Figure 1-2 Multi-node Client/Server system: Cockpit and CommandCenter In addition, you may install the Cockpit and CommandCenter GUI components on one or more PCs within the same network. A separate license is required for each PC on which the Cockpit or CommandCenter is installed. You may use the Cockpit and CommandCenter to monitor and configure one or more Server systems. The following figure shows a typical configuration with several Cockpit installations and a CommandCenter installation communicating with multiple Servers: Mapping Services Translation Services Communications Services Server Network Interface Local OpenVMS Tru64 UNIX Sun Solaris HP-UX Application Client Application Client Application Client Application Client Application Client Server System Remote Systems Trading Partners RedHat Linux Windows Client Application Client Application Client 1-6 Server Configuration PREPARING TO INSTALL DIGITAL DEC/EDI Figure 1-3 Cockpit and CommandCenter Configuration Server Configuration This section describes the components that you need to install on the designated Server node. Network Interface The network interface provides the means to exchange files and data between the Application Client, Cockpit or CommandCenter and the Server. The Server can support multiple simultaneous connections using any of the available network interfaces. Note: A network interface is required even on a single node system, to support interprocess communication between the Application Client and the Server. Development System Production System Supervisors Cockpit Cockpit Developer CommandCenter Cockpit Test Engineer Trading Partners Digital DEC/EDI Server Digital DEC/EDI Server Server Configuration 1-7 PREPARING TO INSTALL DIGITAL DEC/EDI OpenVMS On an OpenVMS Server, you must select the following Network interface: TCP/IP only The OpenVMS system must have DEC TCP/IP Services installed and configured. Tru64 UNIX On a Tru64 UNIX Server, you must select the following Network interface: TCP/IP only The Tru64 UNIX system must be configured with the TCP/IP implementation supplied with Tru64 UNIX. Database The database provides the means of auditing application files, documents and transmission files processed by the Server system. On Tru64 UNIX, the database additionally provides the means of storing the Server configuration details. OpenVMS On an OpenVMS Server the following database components are required: ORACLE Rdb You need to have a minimum of the run-time components licensed and installed. ORACLE SQL/Services for Rdb This is required if you intend to use the Cockpit or CommandCenter to access the Server. Tru64 UNIX On a Tru64 UNIX Server you need to select the following database options: ORACLE 8i You need to install ORACLE 8i, and the required components to support the Cockpit and CommandCenter. Server Software OpenVMS On OpenVMS, the VMSINSTAL command is used to install Digital DEC/EDI from the supplied media. To install the Server, you must select the server installation option. 1-8 Application Client Configuration PREPARING TO INSTALL DIGITAL DEC/EDI The Server installation includes support for translation of ANSI X12, TDCC (UCS/WINS), EDIFACT, ODETTE and TRADACOMS standards, and industry-specific and trading partner specific variations of those standards. Tru64 UNIX On Tru64 UNIX, the setld command is used to install Digital DEC/EDI from the supplied media. You may select specific subsets to install, depending on the communications and translation options you require from the following: X12 This includes support for translation of ANSI X12 and TDCC (UCS/WINS) transactions, and industry-specific and trading partner specific variations. EDIFACT This includes support for translation of UN EDIFACT and ODETTE messages, and industry-specific and trading partner specific variations. TRADACOMS This includes support for translation of TRADACOMS messages, and industry-specific and trading partner specific variations. Communication Options Refer to Server Communications Options on page 1-11 for details of options available. Digital DEC/EDI Message Updates After installation of the Server system, you must install the versions of EDI standard dictionaries and messages that you require. You are recommended to install at least the following standard and version, which is required for performing the basic system configuration tests described in this book: EDIFACT Version 90.1 Application Client Configuration This section describes the components you need to install on any Application Client nodes. Application Client Configuration 1-9 PREPARING TO INSTALL DIGITAL DEC/EDI Network Interface The network interface provides the means to exchange files and data between the Application Client and the designated Server node. The same network interface must be installed and configured on both the application client and server systems. OpenVMS On an OpenVMS Application Client node, you must select the following Network interface: TCP/IP only The OpenVMS system must have DEC TCP/IP Services installed and configured. Tru64 UNIX, Sun Solaris, HP-UX On a Tru64 UNIX, Sun Solaris or HP-UX Application Client node, you must select the following network interface: TCP/IP only The system must be configured with the TCP/IP implementation supplied with the operating system. Application Client Software OpenVMS On OpenVMS, the VMSINSTAL command is used to install Digital DEC/EDI from the supplied media. The installation procedure provides the option to install only the Application Client components. Tru64 UNIX, Sun Solaris, HP-UX On Tru64 UNIX, Sun Solaris and HP-UX, the setld utility, which is provided with the installation kit where required, is used to install Digital DEC/EDI from the supplied media. You must install the application client subsets. Windows Client On Windows NT/2000, run the self extracting utility to install Digital DEC/EDI client from the supplied media. 1-10 Cockpit and CommandCenter Configuration PREPARING TO INSTALL DIGITAL DEC/EDI RedHat Linux On RedHat Linux, use the RPG package to instll Digital DEC/EDI client from the supplied media. Cockpit and CommandCenter Configuration This section describes the components that you need to install on any PCs running Cockpit or CommandCenter. The CommandCenter software includes the Cockpit, so you do not additionally need to install the Cockpit on those systems. Network Interface The network interface provides the means to exchange files and data between the Cockpit or CommandCenter and the Server. The same network interface must be installed and configured on both the PC and server systems, however as the server can support multiple simultaneous transport types, you can use more than one type of network if needed. Windows NT, Windows 2000 On Windows NT or Windows 2000 you must select the following Network Interface: TCP/IP only The PC must be configured with a supported TCP/IP implementation. Database Configuration (ODBC) The Cockpit and CommandCenter use Open Database Connectivity (ODBC) to communicate with the Digital DEC/EDI database on the Server. The Cockpit and CommandCenter may connect to multiple Servers, each of which may be using a different database. You must install the appropriate ODBC drivers and related software to support connection to the Digital DEC/EDI database on each of the Server systems. OpenVMS For connection to an OpenVMS Server, you must install the ODBC driver onto the PC. Server Communications Options 1-11 PREPARING TO INSTALL DIGITAL DEC/EDI ORACLE ODBC Driver for Rdb You need to install the appropriate driver for the operating system you are running on the PC. Tru64 UNIX For connection to a Tru64 UNIX Server, you must install one of the following ODBC drivers, and related connectivity software on the PC: You need to install ORACLE TCP/IP protocol adapter, ORACLE SQL*NET and the ORACLE 8i ODBC driver onto the PC. Software Installation Cockpit Cockpit is supplied on CD-ROM for Windows NT and Windows 2000. CommandCenter CommandCenter is supplied on CD-ROM for Windows NT and Windows 2000. Server Communications Options The Server supports a number of communications options, and you must install any pre-requisite hardware or software prior to installing Digital DEC/EDI. After installation, you must configure the communications components to enable Digital DEC/EDI to communicate with your trading partners. This section outlines the communications options that are available: OpenVMS On an OpenVMS Server, all communications options are installed by the Server installation procedure. Each communications option, apart from the Import/Export gateway, requires a license for its use. The following communications options are available: X.400 Communication You need to install DECnet/OSI, MAILbus 400 and DEC X.500 Directory Services. 1-12 Server Communications Options PREPARING TO INSTALL DIGITAL DEC/EDI OFTP Communication You need to install DECnet/OSI, and X.25 connector services. Bisynchronous Communication For Bisynchronous communications, you need to install the CLEO 3780Plus product together with SYNCcable+ and a compatible modem. X.25 VAN Communication For X.25 VAN communications with the TRADANET VAN, you need to install DECnet/OSI, and X.25 connector services. Import/Export Communication No additional licensing or software is required for use of the Import/Export gateway. Tru64 UNIX On a Tru64 UNIX Server, you may select specific communications subsets to install. Each communications option, apart from the Import/Export gateway, requires a license for its use. The following communications options are available: X.400 Communication You need to install DECnet/OSI, MAILbus 400 and DEC X.500 Directory Services. OFTP Communication You need to install DECnet/OSI, and X.25 connector services. Bisynchronous Communication For Bisynchronous communications, you need to install the CLEO 3780Plus product together with SYNCcable+ and a compatible modem. X.25 VAN Communication For X.25 VAN communications with the TRADANET VAN, you need to install DECnet/OSI, and X.25 connector services. Internet SMTP/MIME Communication For Internet SMTP/MIME Communication, the sendmail function provided with Tru64 UNIX must be installed, along with connection to a wide area network or Internet Service Provider. You may additionally wish to install a third party security or encryption product if communication over a public access network. Import/Export Communication Zero additional licensing or software is required for use of the Import/Export gateway. Server Communications Options 1-13 PREPARING TO INSTALL DIGITAL DEC/EDI Chapter 2 Installation Activities This chapter provides pre-installation information. Introduction The following pages show the Digital DEC/EDI Component Subsets. You should read through these pages and note which of the optional elements are required for your particular installation. This information will be required during the Installation process described in Part 4. 1. Setting up the Server, and any Application Clients local to it (See Setting Up the Server and Local Application Clients on page 2-3). 2. Setting up any remote Application Clients, that is, those on different nodes to the Server (See Setting Up Remote Application Clients on page 2-4). 3. Setting up any CommandCenter installations (See Setting Up the CommandCenter on page 2-4). 4. Setting up any Cockpit installations (See Setting Up the Cockpit on page 2-5). 5. Using the CommandCenter or INTERCHANGE (OpenVMS) to configure the Server (See Configuring the Server on page 2-5). 2-2 Introduction INSTALLATION ACTIVITIES Figure 2-1 Digital DEC/EDI System Components The first four tasks establish the Digital DEC/EDI system as a network of components. These activities are done only once, or repeated infrequently, for example, when you want to bring another node into the system. The final task deals with the detailed configuration of the Server. This may need more regular maintenance, for example, as you add new Trading Partners and applications. These separate stages are outlined in the following sections. The individual activities are listed for each task, along with the Digital DEC/EDI book where the activity is described in more detail. The majority of these activities need to be performed in all Digital DEC/EDI systems where normal routing is used. Where either bypass or applicationto- application routing is deployed, some of the Server configuration activities may not be needed, such as Translation services, and in the case of application-to-application routing, the Communications services. Likewise, the activities to install and configure remote Application Clients are needed only where you have a need to use such clients (as opposed to Application Clients located on the same node as the Server). Business Application Trading Partner Audit Trail CommandCenter Configuration Data Digital DEC/EDI Digital DEC/EDI Client Application DEC/EDI Digital Cockpit Server DEC/EDI Digital Setting Up the Server and Local Application Clients 2-3 INSTALLATION ACTIVITIES Setting Up the Server and Local Application Clients This task covers the physical installation of the Digital DEC/EDI software and any necessary prerequisite software. It also covers the initial configuration of the software sufficient to create the database, and configure the Network Interface for use by Digital DEC/EDI. The following list summarizes the steps to be performed on the Server node, the details are provided in the chapters detailed below: Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Chapter 6 OpenVMS - Installation of Server and Client Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter 1. Install Digital DEC/EDI product licenses, including CommandCenter license 2. Install and verify prerequisite software 3. (UNIX only) Create a decedi account for Digital DEC/EDI to use 4. Install and verify Digital DEC/EDI software 5. Create the database 6. Register Digital DEC/EDI with Network Interface 7. Configure Network Interface for remote access by Application Clients, Cockpit and CommandCenter 8. Create user accounts for database access by users of Cockpit and CommandCenter 9. Grant access to database for user accounts 10.(Oracle(r) Rdb(tm) only) Configure SQL/Services(tm) for database access by users of Cockpit and CommandCenter 2-4 Setting Up Remote Application Clients INSTALLATION ACTIVITIES Setting Up Remote Application Clients This task covers the physical installation and configuration of any Digital DEC/EDI Application Clients on nodes remote from the Server. The following list summarizes the steps to be performed on each separate node running an Application Client, the details are provided in the chapters detailed below: Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Chapter 6 OpenVMS - Installation of Server and Client The procedure is defined in the following list: 1. Install and verify prerequisite software 2. (UNIX only) Create a decedi account for Digital DEC/EDI to use 3. Install and verify Digital DEC/EDI software 4. Register Digital DEC/EDI with Network Interface 5. Configure Network Interface for remote access by Digital DEC/EDI Server Setting Up the CommandCenter This task covers the installation and configuration of the Digital DEC/EDI CommandCenter on a PC. Because the CommandCenter also contains a copy of the Digital DEC/EDI Cockpit, this task also covers that component where it is installed as part of the CommandCenter. The following activities need to be performed on each PC where the CommandCenter is to be used, the details are provided in the chapter detailed below: Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter 1. Install and verify prerequisite software 2. Install CommandCenter software Setting Up the Cockpit 2-5 INSTALLATION ACTIVITIES 3. Define the main Server that CommandCenter is to access 4. Verify CommandCenter link to the Server Setting Up the Cockpit This task covers the installation and configuration of the Digital DEC/EDI Cockpit on a PC where it is installed separately from the CommandCenter. The following activities need to be performed on each PC where the Cockpit is to be used, the details are provided in the chapter detailed below: Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter 1. Install and verify prerequisite software 2. Install Cockpit software 3. Define the main Server that Cockpit is to access 4. Verify Cockpit link to the Server Configuring the Server This task covers the configuration of the Digital DEC/EDI Server and the development and integration of the business applications that post data to, and fetch data from the Server. The following activities need to be performed on each Server and the details are provided in the chapters detailed below: Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Chapter 6 OpenVMS - Installation of Server and Client 1. Select which Translation and Communications Services are to run 2. Define the EDI documents to be exchanged with your Trading Partners 3. Develop or modify your business applications 4. Develop Mapping Tables for your business applications 2-6 Configuring the Server INSTALLATION ACTIVITIES 5. Register your business applications with Digital DEC/EDI, and the nodes on which they run 6. Configure your communications links 7. Define your Trading Partner agreements 8. Start the Digital DEC/EDI system Part I Network Configuration This part describes the configuration, installation and verification of the network components. Introduction Describes installation of the network components, covering the following topics: • TCP/IP • Verifying the network. Intended Audience The audience is the network administrator for the following: • Digital DEC/EDI Server node • Digital DEC/EDI Application Client node(s). Chapter 3 Configuring the Network Interfaces This chapter describes how to configure the Digital DEC/EDI network interfaces. Introduction The Digital DEC/EDI Server can support connection from local and remote application clients, and remote PC's running the Digital DEC/EDI Cockpit or CommandCenter. The following network interfaces are supported for connection to the Digital DEC/EDI Server: Tru64 UNIX and OpenVMS Server • TCP/IP Network Interface The network interface is provided through a direct TCP/IP connection between the client and the server. This supports Windows 95 and NT. The Digital DEC/EDI Server may be configured to support simultaneous connections using one or more of these network interfaces. You must install and configure the Digital DEC/EDI Server network interface prior to configuring the client interfaces. Configuring the Digital DEC/EDI Server This section describes how to configure the network interface on the Digital DEC/EDI Server, and how to set up the local application client to use the network interface. 3-2 Configuring the Digital DEC/EDI Server CONFIGURING THE NETWORK INTERFACES TCP/IP Network Interface This section describes how to configure the TCP/IP network interface on the Digital DEC/EDI Server. Pre-Configuration tasks Prior to configuring the TCP/IP network interface, you should verify that the TCP/IP protocol is installed and is functioning correctly. Tru64 UNIX For example, this may be achieved by verifying that the host name of the computer you are installing on is registered with a local domain name server: # nslookup 'hostname' Server: dnsserver.company.com Address: 1.20.30.4 Name: mynode.company.com Address: 1.20.30.124 Alternatively, you may use the ping command to verify that the computer may connect to another node within the same network. Press CTRL+C to stop the ping command. # /sbin/ping clientnode.company.com PING clientnode.company.com (1.20.30.101): 56 data bytes 64 bytes from 1.20.30.101: icmp_seq=0 ttl=128 time=0 ms 64 bytes from 1.20.30.101: icmp_seq=1 ttl=128 time=0 ms ----1.20.30.101 PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/1 ms # OpenVMS The TCP/IP protocol must be provided by DIGITAL TCP/IP Services. You may verify that this has been installed correctly by running the Installation Verification Procedure for DIGITAL TCP/IP Services: $ @sys$test:ucx$ivp.com %%% UCX IVP: started %%% UDP/IP test started at 18-JUL-1997 11:33:27.63 UDP/IP test ended at 18-JUL-1997 11:33:39.12 UDP/IP transferred successfully in 11 seconds 4198400 bytes Configuring the Digital DEC/EDI Server 3-3 CONFIGURING THE NETWORK INTERFACES TCP/IP test started at 18-JUL-1997 11:33:39.17 TCP/IP test ended at 18-JUL-1997 11:33:48.04 TCP/IP transferred successfully in 8 seconds 4198400 bytes RAW_IP test started at 18-JUL-1997 11:33:48.08 RAW_IP test ended at 18-JUL-1997 11:33:49.25 RAW_IP transferred successfully in 1 seconds 251000 bytes %%% UCX IVP: completed successfully %%% Configuration Tasks Tru64 UNIX The Digital DEC/EDI Server configuration consists of the following steps: Step 1: From the root account, use the decedi_config command, and select the option to configure the TCP/IP Client-Server link. This procedure assigns the TCP/IP port numbers on which the Digital DEC/EDI Services will listen for and handle incoming client requests. This assigns unique port numbers for the Digital DEC/EDI Services within the TCP/IP services file /etc/services. # decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 1 Configuring the TCP/IP Client-Server link Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 2 Configuring Database Compaq DEC/EDI no longer contains a fixed database configuration utility. Instead, customers are encouraged to create 3-4 Configuring the Digital DEC/EDI Server CONFIGURING THE NETWORK INTERFACES their own databases using the Oracle 8i or later database environment. Required schemas and example configuration scripts are available in the /var/adm/decedi/db directory. This configuration procedure simply gathers the information from you on how to connect to your database. Please make sure you have created and tested your database before running this option. Do you want to continue (y/n) [n] : y Enter the database environment to be used (Ora) [Ora] : Enter the local ORACLE HOME directory [] : /usr/app/oracle/product/8.1.6 Enter the Compaq DEC/EDI database's TNS name [ediot_decedidb.world] : Enter the Oracle Username and Password (username/password) : Verifying database connectivity ... Database access verified and saved. Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 3 Configuring Memory Queues Enter the number of slots to hold in memory (10000- >300000) [10000] : 20000 Verifying memory availability... New queue size verified and saved. Press to continue. Step 2: Note down the TCP/IP port numbers that have been assigned to each of the Digital DEC/EDI Services in Step 1 using the Configuring the Digital DEC/EDI Server 3-5 CONFIGURING THE NETWORK INTERFACES following table: You may need to specify these values when configuring any remote application clients or setting up any Cockpit or CommandCenter installations to use the TCP/IP network interface. Note: The same TCP/IP port numbers must be used for all Digital DEC/EDI client and server installations within the same network. Step 3: You are asked whether you wish to use the TCP/IP link for local client access, for example: Do you wish to use TCP/IP for local client access ? [y or n] y TCP/IP Configuration Complete Press to continue. If you confirm this option, then the file /var/adm/decedi/decedi_servers.dat is automatically created with the following value: * LOCAL This ensures that any local applications will use the local Digital DEC/EDI Server to handle client requests. For further information on specifying the use of another Digital DEC/EDI Server node to handle client requests, refer to Configuring the Digital DEC/EDI Application Client on page 3-14 Table 3-1 Digital DEC/EDI Services TCP/IP Port Numbers Purpose Service Name Enter your Port Number here Digital DEC/EDI Post/Fetch Server decedi_csf Digital DEC/EDI Tracking Server decedi_cst Digital DEC/EDI GUI Server decedi_csg 3-6 Configuring the Digital DEC/EDI Server CONFIGURING THE NETWORK INTERFACES Post-Configuration Tasks Once you have configured the network interface, you may start up Digital DEC/EDI. This enables the Digital DEC/EDI Cockpit and CommandCenter, running on a suitably configured PC, to access the Digital DEC/EDI Server. Tru64 UNIX If this is a new installation then you need to copy the file /var/adm/decedi/decedi_servers.template to /var/adm/decedi/decedi_servers.dat. Edit the file and add name of any DEC/EDI Servers and their backups to use and the name of the application Ids (or a * for all) that should use these servers. Note that if you are configuring on a TruCluster Server or on a client that will use a TruCluster Server enabled DEC/EDI Server, you should use the Cluster Alias rather than the LOCAL name or the name of a node in the cluster. OpenVMS Once you have configured the Digital DEC/EDI Server, you may start up the Digital DEC/EDI Server, using the following command: $ @SYS$STARTUP:DECEDI$STARTUP For Further Information There are a number of logical names or environment variables which may be used to tune the behaviour of the TCP/IP network interface, and to monitor the network traffic and processes. For further information on the use of these environment variables and logical names, refer to the Digital DEC/EDI: User's Guides (Tru64 UNIX and Open VMS). Configuring the Digital DEC/EDI Server 3-7 CONFIGURING THE NETWORK INTERFACES TCP/IP Port Server Monitoring Tools There is now an additional tool which allows the TCP/IP Port server and its child process to be monitored and which can tell the Port Server to re-cache the control environment variables whilst it is running. This is useful when you want to change the tracing behaviour or increase the number of maximum child processes. The tool name is: OpenVMS @DECEDI$TOOLS:DECEDI$PS_CONTROL 3-8 Configuring the Digital DEC/EDI Application Client CONFIGURING THE NETWORK INTERFACES Configuring the Digital DEC/EDI Application Client This section describes how to configure the network interface on the Digital DEC/EDI Application Client, along with any steps that need to be performed on the Digital DEC/EDI Server, to enable connection from the remote application client. The Digital DEC/EDI Application Client may be configured using the TCP/IP network interface. TCP/IP Network Interface This section describes how to configure the TCP/IP network interface on the Digital DEC/EDI Application Client. The TCP/IP network interface may be used for connection from the following Digital DEC/EDI Application Client releases: • Digital DEC/EDI for Tru64 UNIX, Version 4.0 • Digital DEC/EDI for OpenVMS Alpha, Version 4.0 • Digital DEC/EDI Application Client for Sun Solaris, Version 4.0 • Digital DEC/EDI Application Client for HP-UX, Version 4.0 • Digital DEC/EDI Application Client for RedHat Linux, Version 4.0 • Digital DEC/EDI Application Client for Windows NT/2000, Version 4.0 The Application Client may be configured to connect to one or more Digital DEC/EDI Server systems, selected by application name, or to a default Digital DEC/EDI Server. In addition, one or more failover Digital DEC/EDI Servers may be specified to handle client requests, if the primary Digital DEC/EDI Server is not currently available. Configuring the Digital DEC/EDI Application Client 3-9 CONFIGURING THE NETWORK INTERFACES Pre-Configuration tasks Prior to configuring the TCP/IP network interface, you should verify that the TCP/IP protocol is installed and is functioning correctly. Step 1: Ensure that any Digital DEC/EDI Servers that will service requests from the application client have been configured to support the TCP/IP network interface as described in TCP/IP Network Interface on page 3-2. Step 2: Verify that the TCP/IP connection between the application client and the server nodes is functioning correctly. For example, this may be achieved by using the ping command as follows: Tru64 UNIX, Sun Solaris, HP-UX, RedHat Linux # ping myserver.company.com PING myserver.company.com (1.20.30.101): 56 data bytes 64 bytes from 1.20.30.101: icmp_seq=0 ttl=128 time=0 ms 64 bytes from 1.20.30.101: icmp_seq=1 ttl=128 time=0 ms ----1.20.30.101 PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/1 ms OpenVMS $ UCX UCX> PING myserver.company.com %UCX-I-LOOPACT, myserver.company.com is alive Windows NT/2000 C:\WINNT\SYSTEM32> ping myserver.company.com Pinging myserver.company.com [1.20.30.101] with 32 bytes of data: Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 3-10 Configuring the Digital DEC/EDI Application Client CONFIGURING THE NETWORK INTERFACES Configuration Tasks Tru64 UNIX, Sun Solaris, HP-UX, RedHat Linux, The Digital DEC/EDI Application Client configuration consists of the following steps: Step 1: From the root account, use the decedi_config command, and select the option to configure the TCP/IP Client-Server link. This procedure sets up the TCP/IP port numbers that are used on the Digital DEC/EDI Server for handling incoming client requests. The port numbers are defined within the TCP/IP services file /etc/services. Tru64 UNIX # /usr/sbin/decedi_config Sun Solaris, HP-UX, RedHat Linux # /usr/bin/decedi_config Configuring the TCP/IP Client-Server link To supply the server node information, create a file: /var/adm/decedi/decedi_servers.dat Use the template, /var/adm/decedi/decedi_servers.template . Do you wish to use TCP/IP for local client access ? [y or n] Configuring the Digital DEC/EDI Application Client 3-11 CONFIGURING THE NETWORK INTERFACES Step 2: The TCP/IP port numbers specified on the client must match those defined on the Digital DEC/EDI Server. Compare these with the values you have noted in the table Digital DEC/EDI Services TCP/IP Port Numbers on page 3-4. If the TCP/IP port numbers differ, edit the values stored in the file /etc/services, so that the same values are used for all client and server installations within the same network. Step 3: Specify the default Digital DEC/EDI Server that should be used for handling requests from the application client. Copy the template file /var/adm/decedi/decedi_servers.template to the file /var/adm/decedi/decedi_servers.dat, as follows: # cp /var/adm/decedi/decedi_servers.template \ /var/adm/decedi/decedi_servers.dat Edit the file /var/adm/decedi/decedi_servers.dat and add the following line to the end of the file. For example, if the server node name is myserver.company.com. * myserver.company.com ! default Digital DEC/EDI Server OpenVMS The Digital DEC/EDI Application Client configuration consists of the following step: Step 1: Specify the default Digital DEC/EDI Server that should be used for handling requests from the application client. Copy the Digital DEC/EDI Servers template file DECEDI$DATA:DECEDI_SERVERS.TEMPLATE, to the file DECEDI$DATA:DECEDI_SERVERS.DAT, as follows: $ COPY DECEDI$DATA:DECEDI_SERVERS.TEMPLATE - DECEDI$DATA:DECEDI_SERVERS.DAT Edit the file DECEDI$DATA:DECEDI_SERVERS.DAT and add the following to the end of the file. For example, if the server node name is myserver.company.com. * myserver.company.com ! default Digital DEC/EDI Server 3-12 Configuring the Digital DEC/EDI Application Client CONFIGURING THE NETWORK INTERFACES Post-Configuration Tasks If you wish, you may add additional Digital DEC/EDI Server definitions and specify which application names should access those servers. These must be placed within the Digital DEC/EDI Servers definition file prior to the line specifying the default Digital DEC/EDI Server. Tru64 UNIX Edit the file /var/adm/decedi/decedi_servers.dat OpenVMS Edit the file DECEDI$DATA:DECEDI_SERVERS.DAT In the following example, the applications DEC-DIRECT-UK-LTD and SHINY-NEW-SYSTEMS both use the primary Digital DEC/EDI Server on node myserver.com. In the event that the Digital DEC/EDI Server is unavailable, the backup Digital DEC/EDI Server on node backup.com is used. The application JOLLY-OLD-SYSTEMS uses the Digital DEC/EDI Server on node edidev as the primary Digital DEC/EDI Server. If this is unavailable, the backup server on edidev2 is tried, followed by edidev3. All other applications in this example use the primary server edigate.com and have no backup Digital DEC/EDI Server. DEC-DIRECT-UK-LTD myserver.com backup.com:5150:5151 SHINY-NEW-SYSTEMS myserver.com backup.com:5150:5151 JOLLY-OLD-SYSTEMS edidev edidev2 edidev3:5150:5151 * edigate.com:5150:5151 ! default Digital DEC/EDI Server For Further Information There are a number of logical names or environment variables which may be used to tune the behaviour of the TCP/IP network interface, and to monitor the network traffic and processes. For further information on the use of these environment variables and logical names, refer to the Digital DEC/EDI: User's Guides (Tru64 UNIX and Open VMS). Part II Database Administration This part describes the configuration and installation of the database components. Intended Audience The audience for this part is the database administrator for the following: • Digital DEC/EDI Server node • PC's running Cockpit or CommandCenter Describes installation of the database components, covering the following: • Oracle Rdb • Oracle 8i • ODBC • SQL network drivers. Chapter 4 Configuring the Database This chapter describes the configuration of the database on the Server node by the Database Administrator. Overview Configuration takes place in two stages. In the first stage, the connectivity software which links the Application Client to the Server, or the Cockpit/ CommandCenter to the Server is initialized. In the case of the Server this phase will also include creating the Digital DEC/EDI database and allowing access to it from the CommandCenter. The second phase of configuration is the detailed configuration of the Server by using the CommandCenter which is described in Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter. The alternative is to configure using INTERCHANGE when installed on OpenVMS servers. This chapter describes the first of these stages. 4-2 Overview CONFIGURING THE DATABASE Account Privileges Tru64 UNIX Note that many of the activities described in this section that involve running decedi_config, assume you have access to the root account on the Server node. Open VMS You will need an account with full system manager privileges. Configurations Covered The following configurations are covered • Tru64 UNIX Oracle 8i • OpenVMS Alpha Oracle Rdb Setting Up Process The setting up process which happens after the chosen database application has been installed, has two parts as shown below: • A - Decision process for location of the database • B - Creation of the database A - Deciding Where to Locate the Database 4-3 CONFIGURING THE DATABASE A - Deciding Where to Locate the Database When locating the database it is important that a location with sufficient resource is chosen. A badly located database can significantly reduce the performance of a Server, meaning you need to consider the disk space and room for expansion. Factors that can decrease the performance are further detailed later in Performance Limiting Aspects on page 4-5. Oracle8i You need to specify a directory location on disk with enough spare disk space, use the following formula to calculate the required size: maximum size = overhead + peak map size + peak doc size + peak comms size + standards size Where: overhead = 18MB +(((maximum size - 18MB)* 3)/10) peak map size = (peak live maps + peak archive maps)* 0.003 MB peak doc size = (peak live docs + peak archive docs) * 0.0015 MB peak comms size = (peak live comms + peak archive comms) * 0.003 MB standards size = number of standards * 5MB We recommend a minimum of 50MB for the Oracle8i database. Typical Example As an example, a user system which processes a 500 maps per weekday, generating or consuming 500 EDI documents which in turn go to, or come from 100 communications transmission files using two EDI standards, and where secondary archiving is done once a week, the calculation is as follows. We assume that be the end of the day all live documents are processed, so peak live size is peak daily rate, whilst the peak archive size is the cumulation of the five-day week's worth of data. The calculation includes some contingency, so that we double the peak live counts in case everything fails due to some disaster and we take a day to fix it, and we double the archive size in case we forget one weekend to do the secondary archive. 4-4 A - Deciding Where to Locate the Database CONFIGURING THE DATABASE We also double the number of standards we use to cater for near term expansion. So, we end up with a calculation of: maximum size = 18MB + (((maximum size -18MB) * 3) / 10) + (1000 + 5000) * 0.003 MB + (1000 + 5000) * 0.0015 MB + (200 + 1000) * 0.003 MB 4 * 5MB; = 85 MB (approximately) Having worked out the size, find a suitable directory, which resides on a disk with sufficient free space, and create a database directory for it. Set the ownership of this directory to be the main Oracle account. The main Oracle account is the account under which this instance of the Oracle8i RDBMS software was installed. For standard Oracle installations this is oracle by default, or if installed on behalf of another application it could be ora , for example orapd1. Note that the database size can be increased later by adding extra datafiles to the relevant tablespaces if a particular tablespace becomes full. NFS mounted disks Digital does not recommend placing the database for Digital DEC/EDI onto an NFS mounted disk. Access. The database account needs to have write access to the directory where your database is to be created. A - Deciding Where to Locate the Database 4-5 CONFIGURING THE DATABASE OpenVMS Oracle Rdb If you are on OpenVMS then Oracle Rdb will provide your database, and it will be created on the device on which you have elected as Digital DEC/EDI's top level directory. The default database is created of approximately 20 Mbytes in size which will allow it to hold information for: The tables within the database will automatically extend when you store more data in them that the original configuration can hold, but performance will be reduced the more the database becomes extended. Should the database become too small or if you wish to move the database to another device then a tool, DECEDI$TOOLS:DECEDI$TAILOR.COM, is provided to help you with this. Performance Limiting Aspects Disk Speed. The performance of your Server can easily be limited by the speed of access to the Digital DEC/EDI database. This means that you should avoid placing the database on slow disks. I/O Bottlenecks. During the software installation, you specified one or more disk locations for your store directories. These are directories used to hold the actual document and transmission files. By placing the database on a different physical disk to those holding store directories, you help to avoid the performance of individual disks being a bottleneck on overall system performance. NFS Mounted Disks Digital does not recommend placing the database for Digital DEC/EDI onto an NFS mounted disk. Access. The database account needs to have write access to the directory where your database is to be created. Number of documents in the Current Audit Trail 1000 Number of documents in the Archive Audit Trail 1000 Number of transmission files in the Current Audit Trail 1000 Number of transmission files in the Archive Audit Trail 1000 4-6 B - Creating the Database CONFIGURING THE DATABASE B - Creating the Database • Tru64 UNIX Oracle 8i • Alpha Oracle Rdb Tru64 UNIX All Databases This task is performed by using the Digital DEC/EDI configuration utility: decedi_config. To use this, you need to be logged in to your Server under the root account. Questions, Getting Help If you are unsure about how to reply to any of the questions asked by this utility, enter a question mark character followed by . Help text is displayed giving you more information about any choices you can make. Invoke the configuration utility, and select the option to configure the database, as in the following example: # decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 1 Configuring the TCP/IP Client-Server link Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 2 Configuring Database Compaq DEC/EDI no longer contains a fixed database configuration utility. Instead, customers are encouraged to create their own databases using the Oracle 8i or later database environment. Required schemas and example configuration scripts are available in the /var/adm/decedi/db directory. This configuration procedure simply gathers the information from you on how to connect to your database. B - Creating the Database 4-7 CONFIGURING THE DATABASE Please make sure you have created and tested your database before running this option. Do you want to continue (y/n) [n] : y Enter the database environment to be used (Ora) [Ora] : Enter the local ORACLE HOME directory [] : /usr/app/oracle/product/8.1.6 Enter the Compaq DEC/EDI database's TNS name [ediot_decedidb.world] : Enter the Oracle Username and Password (username/password) : Verifying database connectivity ... Database access verified and saved. Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 3 Configuring Memory Queues Enter the number of slots to hold in memory (10000->300000) [10000] : 20000 Verifying memory availability... New queue size verified and saved. Press to continue.You are asked what product is to be used to provide the database, and where the database is to be located. The device or directory to contain the database must already exist. The location of the file that is to contain the database for Oracle Rdb. The database creation procedure displays each individual statement executed in setting up the database. The database creation procedure may take several minutes to complete. Typical Oracle 8i Example Configuring Database Enter the database to be used (Rdb, Inf, Ora) [Inf] : Ora ...Creating /var/adm/decedi/config.dat Enter Oracle Home directory /usera/oracle] : 4-8 B - Creating the Database CONFIGURING THE DATABASE Enter Digital DEC/EDI Oracle 8 database location [/var/adm/decedi/db] : /userb/oracle/db ...Modifying /etc/oratab ...Modifying /var/adm/decedi/config.dat Enter Digital DEC/EDI Oracle 8 database size in KB [182671] : 100000 ******************************************************* Default oracle network templates have been generated in /userb/oracle/db/. The files being: listener.ora tnsnav.ora tnsnames.ora These files should be merged with those already on this server (in /etc), and those residing on any PC wishing to use the CommandCenter or Cockpit to access this server. ...Creating /usera/oracle/dbs/initdecedidb.ora ...Creating database /userb/oracle/db ...Loading system tables ...Creating schema ...Storing system version ...Setting Digital DEC/EDI Oracle password. Database Configuration Complete B - Creating the Database 4-9 CONFIGURING THE DATABASE OpenVMS The Digital DEC/EDI database is created during the installation process. Typical Oracle Rdb Example A typical installation detail example is provided below: =================================================== The following versions of Rdb/VMS are available: V7.0-3 * Please enter the Rdb/VMS version to be used by Digital DEC/EDI [V7.0-3]: At this point the installation will list the installed databases. The default is selected by pressing , should you need to use one of the alternates (when available) enter the version as displayed followed by . The example continues below assuming acceptance of the default: Current PROCESS Oracle Rdb environment is version V7.0-3 (STANDARD) Current PROCESS SQL environment is version V7.0-3 (STANDARD)Current PROCESS Rdb/Dispatch environment is version V7.0-3 (STANDARD) Database Version It is essential that the database version on your system is the same as that used by Digital DEC/EDI. Use the following command to establish the version currently in use: $@sys$library:rdbvms_shover To set the version, use the following command: $@sys$library:rdbvms_setver For example, to set the version to V7.0, use the following command: $@sys$library:rdbvms_setver v70 4-10 Migrating the Database CONFIGURING THE DATABASE Migrating the Database If you are installing Digital DEC/EDI over a previous version then the database structure needs migrating to the new structure. Tru64 UNIX After installing Digital DEC/EDI, run decedi_config from the root account. Select the option to configure the database. Select the database type being used and location of existing database, then select the [m]igrate option. The database is migrated to a structure compatible with the current version of the Server. If the current database is already in a compatible structure (that is, if there have not been any database structure changes between the version of the Server that was used to create/migrate the database to its current structure and the currently installed Server version) then no migration is needed and none takes take place. The database is then ready for use by the currently installed Server. OpenVMS The Digital DEC/EDI database will normally be migrated during the installation process. Creating User Accounts for Database Access 4-11 CONFIGURING THE DATABASE Creating User Accounts for Database Access Each PC running either the CommandCenter or the Cockpit accesses the Digital DEC/EDI database on the Server via ODBC(tm) on the PC. This needs to happen through an account on the Server. You can have a single account for all users of the CommandCenter and the Cockpit, or you can have individual accounts for each separate user of either PC product. Having a single account is easier to set up and maintain, and though inherently less secure, allows you to be more selective about what individual users can access. Digital DEC/EDI Access Control Editor This application, which is provided with the CommandCenter/Cockpit, enables you to define which users may access which data and the level of their access to the CommandCenter. Tru64 UNIX Oracle8i Oracle 8i maintains its own usernames and passwords. It can also support server accounts and passwords, but as these apply only when making requests from the server, they are of no value to CommandCenter and Cockpit users. To create Oracle8i accounts, use the decedi_config option described in the following section, Granting Database Access to User Accounts. In addition to defining the users, you will be prompted for the passswords associated with any new users. When you start any of the CommandCenter editors or the Cockpit, the account and password you are asked to specify are those of the user accounts you have now created on the Server. OpenVMS Oracle Rdb You create a user account on the Server by using the OpenVMS AUTHORIZE utility. You should do this from the 'system' account or another highly privileged account. 4-12 Oracle User Registration CONFIGURING THE DATABASE Oracle User Registration Tru64 UNIX All GUI users who log in, access an account on the Server machine which is authorized to access the database. Oracle8i is different in that it takes the username as being local to the machine from which the request was made; the GUI PC. This type of treatment reduces the effectiveness of the logging in procedure. To deal with this situation, you (as system administator) need to create user accounts within the Digital DEC/EDI Oracle database by using decedi_config. PC users can then use those accounts to access the database. OpenVMS Oracle SQL Services provides a number of mechanisms by which access to a database can be granted or revoked. By default, the Digital DEC/EDI database is protected via OpenVMS ACLs. To allow a user to access the Digital DEC/EDI databases, the Digital DEC/EDI INTERCHANGE command should be used to add the user. This in turn grants the user's account the correct ACLs to allow access to the Digital DEC/EDI database. Configuring the Database Network Connectivity OpenVMS Oracle SQL Services By default, when you install Oracle SQL Services it will create a class for the version of software you have installed for instance, if installing Oracle Rdb V5.1 then a 'V51' class will be automatically configured. As long as this class used by the CommandCenters and Cockpits trying to access the database then no further configuration is required. Options are: GENERIC, V51, V60, V61. Specify GENERIC if you have standard SQL Services installed on your OpenVMS Server. Specify one of the other options if you have multi-version SQL installed, to tell it which version to use. Configuring the Database Network Connectivity 4-13 CONFIGURING THE DATABASE Tru64 UNIX Oracle 8i As part of creating the Digital DEC/EDI Oracle 8i database, the following was reported: ******************************************************* Default oracle network templates have been generated in /userb/oracle/db/. The files being: listener.ora tnsnav.ora tnsnames.ora These files should be merged with those already on this server (in /etc), and those residing on any PC wishing to use the CommandCenter or Cockpit to access this server. This needs to be done, and the Oracle 8i TNS listener re-started for these to take effect. Merging Files Refer to the Digital DEC/EDI: User's Guides (Tru64 UNIX and Open VMS) for information on merging the files. Part III Software Installation This part describes the software installation onto a variety of platforms. Introduction Installation of the following software is covered: • Client/Server or Client software • Message Updates • CommandCenter and Cockpit. Intended Audience The audience of this part is the system manager or administrator of the following: • Digital DEC/EDI Server node • Digital DEC/EDI Application client node(s) • PCs running CommandCenter and/or Cockpit Supported Platforms This part also includes installation of the following on the Digital DEC/EDI Server node: The following servers running Digital DEC/EDI are covered • OpenVMS • Tru64 UNIX The following clients running Digital DEC/EDI are covered: • OpenVMS • Tru64 UNIX • Sun Solaris • HP-UX • RedHat Linux • Windows NT/2000 The following operating systems on PCs running CommandCenter and/or Cockpit are supported: • Windows NT/2000 Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client This chapter describes the preparation for and installation of Digital DEC/EDI Server and Application Client by the System Manager or Administrator, onto a Tru64 UNIX platform. Introduction This chapter is divided into sections as shown below: • Preparing to Install Digital DEC/EDI on page 5-2 • Installing Digital DEC/EDI on page 5-23 • After Installation on page 5-29 • Setting Up the System on page 5-31 5-2 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Preparing to Install Digital DEC/EDI Before attempting to proceed with the instructions contained within this book you should be familiar with the contents of Digital DEC/EDI Introduction and have decided on which components will be installed on this and any other nodes. Before attempting to install Digital DEC/EDI software on your system, complete the preparation requirements outlined in Chapters 1 and 2. You will need the Installation Checklist prepared from Chapter 2 to complete the preparation and installation described in this chapter. This section describes the activities that must be completed before starting the installation: • Reading the Online Release Notes on page 5-3 • Installation Options on page 5-4 • Checking the Software Distribution Kit on page 5-8 • Registering Your Software Licenses on Digital Systems on page 5-8 • Installation Pre-requisites on page 5-11 • Deleting Digital DEC/EDI from Your System on page 5-24 • # setld -d DEDICLT400 DEDICLTMAN400 on page 5-21 Preparing to Install Digital DEC/EDI 5-3 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Reading the Online Release Notes Digital DEC/EDI provides online release notes. Digital strongly recommends that you read the release notes before using the product. The release notes contain information about changes to the application that are not included in the standard published documentation set. The release notes for Digital DEC/EDI will be placed in the following location after installation: /usr/doc/DECEDI(subset_number).release_notes 5-4 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Installation Options Your media kit contains one or more Digital DEC/EDI components which are as follow: • Digital DEC/EDI Application Client. Select if applications on the installation platform are to either exchange files with Digital DEC/EDI Server, or track files in the Digital DEC/EDI Server using the Digital DEC/EDI Application Programming Interface (API) or the Digital DEC/EDI Command Line Interface (CLI). Necessary whether or not the Digital DEC/EDI Server is on the same platform as the applications. • Digital DEC/EDI Server. Select to provide Communications Services, EDI Translation Services, or Mapping Services on the installation platform. Necessary even to only use this platform as the common connection point for Application-to- Application routing. • Digital DEC/EDI Message Update Service. Select to install a new set of EDI message standards for use by the EDI Translation Services, or for use when developing mapping tables. It can only be installed on a platform with Digital DEC/EDI Server component. The components share some common subsets and have other subsets which are specific to themselves and which may be either mandatory or optional. Preparing to Install Digital DEC/EDI 5-5 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT The components, and their subsets are detailed below:. Table 5-1 Digital DEC/EDI Component Subsets Component (Digital DEC/EDI ...) Subset (Digital DEC/EDI ...) Install ? Application Client Base Mandatory Client Mandatory Client Man Pages Optional Server Base Mandatory Server Mandatory Server Man Pages Optional EDI Translation Services Optional Mailbus 400 Gateway Optional OFTP Gateway Optional SMTP/MIME Communications Gateway Optional 3780 (BISYNC) Communications Gateway Optional Message Update Service (MUS) Message Updates Base Mandatory Message Updates EDIFACT IMPDEF files Optional Message Updates ODETTE IMPDEF files Optional Message Updates X12 files Optional Message Updates TDCC files Optional Message Updates TRADACOMS files Optional 5-6 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Additional Information on Digital DEC/EDI Subsets The following provides additional information on the Digital DEC/EDI subsets: • The Digital DEC/EDI Client Man Pages optional subset should be selected if the man pages for the Digital DEC/EDI API and CLI calls are required. • The Digital DEC/EDI Server Man Pages optional subset should be selected if the man pages for the Digital DEC/EDI System Administrator Utilities, such as Secondary Archiving, are required. • The Digital DEC/EDI EDI Translation Services optional subset should be selected if any EDI Translation is required for either outgoing or incoming files. • The Digital DEC/EDI Mailbus 400 Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide X.400 or X.435 Communications Services. • The Digital DEC/EDI OFTP Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide OFTP Communications Services. • The Digital DEC/EDI SMTP/MIME Communications Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide SMTP/MIME Communications Services. • The Digital DEC/EDI 3780 (BISYNC) Communications Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide 3780 (BISYNC) Communications Services. • The Digital DEC/EDI Message Updates Man Pages optional subset should be selected if the man pages for the Digital DEC/EDI Message Updates Service are required. • The Digital DEC/EDI Message Updates EDIFACT IMPDEF files optional subset should be selected if the Digital DEC/EDI Server requires that new EDIFACT tables need to be installed on the system or to replace existing tables already on the system. • The Digital DEC/EDI Message Updates ODETTE IMPDEF files optional subset should be selected if the Digital DEC/EDI Server requires that new ODETTE tables need to be installed on the system or to replace existing tables already on the system. Preparing to Install Digital DEC/EDI 5-7 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT • The Digital DEC/EDI Message Updates X12 files optional subset should be selected if the Digital DEC/EDI Server requires that new X12 tables need to be installed on the system or to replace existing tables already on the system. • The Digital DEC/EDI Message Updates TDCC files optional subset should be selected if the Digital DEC/EDI Server requires that new TDCC tables need to be installed on the system or to replace existing tables already on the system. • The Digital DEC/EDI Message Updates TRADACOMS files optional subset should be selected if the Digital DEC/EDI Server requires that new TRADACOMS tables need to be installed on the system or to replace existing tables already on the system. 5-8 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your Digital DEC/EDI software distribution kit. If your software distribution kit is damaged or incomplete, contact your Digital representative. Registering Your Software Licenses on Digital Systems Digital DEC/EDI includes support for the License Management Facility (LMF). You must register your License Product Authorization Key(s) (License PAK(s)) in the License Database (LDB) in order to use Digital DEC/EDI on a newly-licensed node. If you ordered the licenses and media together then the License PAK(s) will be shipped along with the kit. Otherwise, the License PAK(s) are shipped separately to a location described on your license order. Digital DEC/EDI supports a number of license types, depending on which Digital DEC/EDI component subsets you wish to use. The individual License PAK names, and what they control are shown on the following table. Preparing to Install Digital DEC/EDI 5-9 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Table 5-2 Digital DEC/EDI Component Licensing Important In addition, you must install the EDI-COMCEN license on the Server. This permits the Digital DEC/EDI CommandCenter to manage the Server node. If you are installing pre-requisite or optional software along with Digital DEC/EDI, review the PAK status and install the PAKs for them before you install Digital DEC/EDI. Subset (Digital DEC/EDI ...) Functionality LMF_PAK_Name Client Post, Fetch, Track via API or CLI This includes bypass translation EDI- APP-SERV or EDI X400 PACKAGE or EDI OFTP PACKAGE Server Import/Export Gateway. Runtime Mapper, Application to- Application Routing No license required EDI Translation Convert to EDI Format, Build EDI Transmissions, Split EDI Transmissions, Translate from EDI Format EDI-TRANSLATIONSERV or EDI-X400- PACKAGE or EDI-OFTP-PACKAGE Mailbus400 Gateway X.400 (84) P0 and P2, X.400 (88) P0 and P2, X.435 EDI EDI-X400-SERV or X400-PACKAGE OFTP Gateway OFTP send and receive EDI-OFTP-SERV or EDI OFTP- PACKAGE SMTP/MIME Communications Gateway SMTP send and receive EDI-SMTP LICENSE or EDI-SMTP-PACKAGE license 3780 (BISYNC) Communications Gateway 3780 send and receive EDI-BISYNC- LICENSE or EDI-BISYNC-PACKAGE license 5-10 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Registering Licenses on Tru64 UNIX To register a license under the Tru64 UNIX operating system: 1. Log in as superuser. 2. At the superuser prompt, enter the following command to edit your License PAK: # lmf register 3. An empty PAK template is displayed in a text editor. Enter all the information from the License PAK form supplied with your software. 4. After you register your license, use the following command to copy the license details from the LDB to the kernel cache: # lmf reset For complete information on using the License Management Facility, see the Guide to Software License Management. Preparing to Install Digital DEC/EDI 5-11 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Installation Pre-requisites This section discusses requirements for installing Digital DEC/EDI. Login Privileges You must have superuser privileges to install the Digital DEC/EDI software and to register the license PAK(s). Hardware Requirements To run the Digital DEC/EDI Application Client, Digital DEC/EDI Server or Digital DEC/EDI Message Update Service you need a Digital machine running the Tru64 UNIX Operating System. Please refer to the Digital DEC/EDI Software Product Description (SPD) for the additional details of the hardware models and supported versions of the operating system. To perform the installation, you need the following hardware: • A software distribution device (if installing from media). You need a distribution device that corresponds with the software distribution media. For example, if you have a CD-ROM, you need a CD-ROM drive. The documentation for the tape or disk drive explains how to load the media supplied with the software distribution kit. • A terminal. You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. If you wish to install the Digital DEC/EDI Mailbus 400 Gateway subset, you may require additional hardware that supports specific communication protocols to provide external connectivity. See the Mailbus 400 Software Product Description (SPD) for more information on these requirements. If you wish to install the Digital DEC/EDI OFTP Gateway subset, you may require additional hardware to provide the X.25 connectivity. See the DEC X.25 Software Product Description (SPD) for more information on these requirements. 5-12 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Checking Software Requirements The software requirements for Digital DEC/EDI are shown below. Table 5-3 Digital DEC/EDI Software Requirements Subset (Digital DEC/EDI ...) Software Install? Base Tru64 UNIX Mandatory TCP/IP Mandatory (included with O/S) Client Digital DEC/EDI Base Mandatory Client Man Pages Tru64 UNIX Documentation Subset Optional Server Digital DEC/EDI Base Mandatory Oracle 8i Mandatory if using Oracle 8i Oracle SQL*NET V2 Mandatory if using Oracle 8i Server Man Pages Tru64 UNIX Documentation Subset Optional Translation Services Digital DEC/EDI Server Optional Mailbus 400 Gateway Digital DEC/EDI Server Optional Mailbus 400 Base Optional OFTP Gateway Digital DEC/EDI Server Optional SMTP/MIME Communications Gateway Digital DEC/EDI Server Optional 3780 (BISYNC) Communications Gateway Digital DEC/EDI Optional DEC X.25 Base Optional Message Updates Base Digital DEC/EDI Server Optional Message Updates Man Pages Tru64 UNIX Documentation Subset Optional Preparing to Install Digital DEC/EDI 5-13 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Message Updates EDIFACT IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates ODETTE IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates X12 IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates TDCC IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates TRADACOMS IMPDEF files Digital DEC/EDI Message Updates Base Optional Subset (Digital DEC/EDI ...) Software Install? 5-14 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Database Requirement The Server requires a database to hold its definitions and the following database type must be installed: • Oracle8i See the Digital DEC/EDI Software Product Description (SPD) for more information on software requirements such as version numbers. Run Time Libraries The following Tru64 UNIX Run Time Libraries must be installed. These are provided with the Tru64 UNIX operating system software distribution on CD-ROM: For example, to determine whether the subset is installed, use the following command: # setld -i | grep DFARTL DFARTL361 installed installed DIGITAL Fortran RTL #384 for DIGITAL UNIX Alpha Systems (f90 and f77) Network Interfaces TCP/IP Link Checking Check that the TCP/IP link works in both directions by pinging the other node you intend to use. The command is: # ping [remote node name] Use CTRL C to stop the test. Checking Tru64 UNIX Documentation Subset is Installed To check Tru64 UNIX Documentation Subset is installed, log in as the superuser (root), and enter the following command: # setld -i | grep OSFDCMT Subset Name Description DPORTL5nn DEC Pascal for Tru64 UNIX Alpha Runtime Support DFARTL3nn DEC Fortran for Tru64 UNIX Alpha Runtime Support Preparing to Install Digital DEC/EDI 5-15 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT This produces an output, with a mark against each version of the Tru64 UNIX Documentation Subset currently installed. Checking that Oracle8i is Installed Before you can check completely that all Oracle8i components have been installed, you need to set some environment variables specific to Oracle8i. Ensure that the Listener Services have been started from the Oracle account using the following command: # lsnrctl start 5-16 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Setting Oracle8i Environment Variables To set Oracle8i environment variables: 1. Check the /etc/passwd file to make sure that an Oracle8i account has been created. Note that the name of the account starts with the letters, ora. By default, the name is oracle. 2. Note the whole specification of its home directory, and switch to that user (for example, su - oracle). 3. Set the following environment variables as specified: • ORACLE_HOME-to home directory specification • ORACLE_SID-to decedidb • ORACLE_TERM-to vt100 After setting the environment variables, there are two ways in which you can check that Oracle8i and its components are installed: 1. Run the Oracle8i Installer This utility produces a listing of components and respective versions. 2. Check for individual Oracle8i components by using specific commands. In checking an installation by this method, you need to know what components should be installed. Running the Oracle8i Installer The Oracle8i Installer is located on the Oracle CD-ROM disk. Run the utility to give you a listing (with respective locations) of Oracle8i files installed on your system. This may take a few minutes. Checking for Individual Oracle8i Components You may check that individual components are installed by using commands that are specific to each one. You also have the option to list the version number of each component for which you check. Preparing to Install Digital DEC/EDI 5-17 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Checking for the Server Manager and DBMS From the Oracle account, and with the environment variables set as described in Setting Oracle8i Environment Variables on page 5-16, enter the following command: # svrmgrl This returns an output similar to the following: Oracle Server Manager Release 3.1.6.0.0 - Production Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved. Oracle8i Enterprise Edition Release 8.1.6.2.0 - Production JServer Release 8.1.6.2.0 - Production SVRMGR> exit Note that this shows that both the Server Manager and DBMS are installed. Their version numbers are also included in the output. Checking for Oracle8i SQLPLUS To check that the PL/SQL package is installed, enter the following command: migrgb.reo.dec.com> sqlplus An output similar to the following shows that it is installed: SQL*Plus: Release 8.1.6.0.0 - Production on Thu Mar 15 04:50:41 2001 (c) Copyright 1999 Oracle Corporation. All rights reserved. Enter user-name: Press CTRL C to escape. Checking for TCP/IP Services To check for the TCP/IP Services, enter the following command: # $ORACLE_HOME/bin/drivers This returns an output listing the installed SQL*Net Drivers To get their versions, enter the following commands: # $ORACLE_HOME/bin/lsnrctl LSNRCTL> version This produces an output listing the SQL*Net D