DEC/EDI Installation DEC/EDI V3.2 AA-Q8WTF-TE January, 1998 1994, 1998 The following are trademarks of Digital Equipment Corporation: DEC, DEC/EDI, DECforms, DIGITAL, MAILbus, OpenVMS, PATHWORKS, VAX, and the DIGITAL logo. Adobe is a registered trademark of Adobe Systems Incorporated AIX and IBM are registered trademarks and AS/400 is a trademark of International Business Machines Corporation. BT is a registered trademark of British Telecommunications plc. HP and HP-UX are registered trademarks of Hewlett-Packard Company. INFORMIX is a registered trademark of Informix Software, Inc. InstallShield is a registered trademark of InstallShield Corporation. INTERSOLV is a registered trademark of INTERSOLV, Inc. MS MS-DOS and Windows are registered trademarks, and Windows 95 and Windows NT are trademarks, of Microsoft Corporation. ObjectBroker is a registered trademark of BEA. Oracle is a registered trademark of Oracle Corporation. SAP is a registered trademark of SAP AG. Sun and Solaris are registered trademarks of Sun Microsystems Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks not listed above are acknowledged as the the property of their respective holders. Preface Purpose For DEC/EDI Version 3.2 This book describes how to install the following DEC/EDI components: • Server • Application Client • Message Updates • Cockpit • CommandCenter Enables you to perform basic system configuration, to ensure that DEC/EDI is installed and configured correctly, and can communicate with other DEC//EDI components installed within the same network. Audience This document is for anyone who wants to install, configure or support a 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 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 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 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 DEC/EDI software. For detailed configuration of DEC/EDI and its external communications components please refer to the 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 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 DEC/EDI product wishing to upgrade or migrate to this version of 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 DEC/EDI. The book is organized to enable easy location of information relating to the installation activities for the required DEC/EDI configuration. Read Part I of this book from start to finish, and then read the sections that relate to the required DEC/EDI configuration. DEC/EDI Documentation This is one of a set of DEC/EDI books. The complete list is as follows: • DEC/EDI: Introduction This book introduces general EDI concepts, and Digital's EDI system, DEC/EDI. It describes the main components of the 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 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 DEC/EDI. • DEC/EDI: Installation This book describes how to install the 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. • 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 DEC/EDI. • DEC/EDI: User's Guides (Digital UNIX and Open VMS) These guides contain information on setting up and operating 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 DEC/EDI Server they describe. Digital UNIX DEC/EDI: UNIX User Support Manual OpenVMS DEC/EDI: OpenVMS User Support Manual - Volume 1 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 DEC/EDI software: for example, on-line help libraries and UNIX man page help information. In addition the DEC/EDI Cockpit and CommandCenter kits contains the 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 CommandCenter CD-ROM provides on-line versions of all DEC/EDI books in Adobe Acrobat format. 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.digital.com/edi/ 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 DEC/EDI. The following conventions are used to indicate such text: Oracle7 This indicates the adjoining paragraph contains information specific to running DEC/EDI with the Oracle7 database. OnLine This indicates the adjoining paragraph contains information specific to running DEC/EDI with the INFORMIX-OnLine database. OnLine... This indicates the start of several paragraphs of information specific to running DEC/EDI with the INFORMIX-OnLine database. ...OnLine This indicates the last of several paragraphs of information specific to running DEC/EDI with the INFORMIX-OnLine database. Similar conventions are used to indicate text specific to other components. For example: • Rdb refers to the Oracleฎ Rdb™ database. • V2.1A refers to Cockpit Version 2.1A • V3.1A refers to Cockpit Version 3.1A. Chapter 1 Preparing to Install DEC/EDI This chapter describes what actions are necessary prior to installation of DEC/EDI. Overview Before installing 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 DEC/EDI. It is not necessary to know everything about all the systems on which you will be using DEC/EDI at this stage, as you may add further components or systems at a later date. DEC/EDI System Configuration The collection of systems within the same network, on which DEC/EDI and its components are installed, is known as the 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 DEC/EDI system configuration. 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. DEC/EDI product documentation is described in DEC/EDI Documentation on page -xv of the Preface. 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 DIGITAL UNIX 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. 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. FileBridge UI For OpenVMS servers, the FileBridge user interface provides the facility to develop Mapping Tables for integrating your Business Applications, and for tracking mapping activities. The FileBridge development user interface runs on any OpenVMS system connected to the Server. The FileBridge tracking interface runs on the same system as the Server Establishing the Configuration of Your System DEC/EDI supports a number of different system configurations, and you must determine the desired system configuration before proceeding with the installation of DEC/EDI and its components. The following section describes the supported configuration options, and directs you to the relevant parts of the 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 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: 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: Figure 1-2 Multi-node Client/Server system: DEC/EDI V1.3 Application and Server System Your business application runs on a remote VAX system using either the DEC/EDI V1.3 data label API or DEC/EDI FileBridge, and is connected to the Server on OpenVMS using DECnet or DECnet/Plus. The following figure shows a typical V1.3 system connected to a DEC/EDI Version 3.2 Server on OpenVMS: Figure 1-3 Remote V1.3 Application and Server 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: Figure 1-4 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. A network interface is required even on a single node system, to support interprocess communication between the Application Client and the Server. OpenVMS On an OpenVMS Server, you must select one or more of the following Network interfaces: ObjectBroker over DECnet ObjectBroker must be installed and the OpenVMS system must be configured to support either DECnet or DECnet/OSI (DECnet Plus). ObjectBroker over TCP/IP ObjectBroker must be installed and the OpenVMS system must be configured with a TCP/IP implementation that is compatible with ObjectBroker. TCP/IP only The OpenVMS system must have DEC TCP/IP Services installed and configured. If you are using the Server to support remote DEC/EDI V1.3 applications, then you must have one of the following communications protocols installed and configured: DECnet DECnet must also be installed on the remote application node. DECnet/OSI (DECnet Plus) DECnet/OSI must also be installed on the remote application node. DIGITAL UNIX On a DIGITAL UNIX Server, you must select one of the following Network interfaces: ObjectBroker over TCP/IP ObjectBroker must be installed and the DIGITAL UNIX system must be configured with the TCP/IP implementation supplied with DIGITAL UNIX. TCP/IP only The DIGITAL UNIX system must be configured with the TCP/IP implementation supplied with DIGITAL UNIX. Database The database provides the means of auditing application files, documents and transmission files processed by the Server system. On DIGITAL UNIX, the database additionally provides the means of storing the Server configuration details. Except for V1.3 installations, you do not need to install any database components on remote Application Client nodes. 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. DIGITAL UNIX On a DIGITAL UNIX Server you need to select one of the following database options: ORACLE Rdb You need to have a minimum of the run-time components licensed and installed, along with ORACLE SQL/Services to support the Cockpit and CommandCenter. ORACLE 7 You need to install ORACLE 7, and the required components to support the Cockpit and CommandCenter. Informix Online You need to install Informix Online, and the required components to support the Cockpit and CommandCenter. Server Software OpenVMS On OpenVMS, the VMSINSTAL command is used to install DEC/EDI from the supplied media. To install the Server, you must select the server installation option. 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. DIGITAL UNIX On DIGITAL UNIX, the setld command is used to install 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-18 for details of options available. 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. 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 one of the following Network interfaces: ObjectBroker over DECnet ObjectBroker must be installed and the OpenVMS system must be configured to support either DECnet or DECnet/OSI (DECnet Plus). ObjectBroker over TCP/IP ObjectBroker must be installed and the OpenVMS system must be configured with a TCP/IP implementation that is compatible with ObjectBroker. TCP/IP only The OpenVMS system must have DEC TCP/IP Services installed and configured. OpenVMS and DEC/EDI V1.3 If you are also using DEC/EDI V1.3 applications on the application client node, then you must have one of the following communications protocols installed and configured: DECnet DECnet must also be installed on the Server node. The Server must be an OpenVMS Server. DECnet/OSI (DECnet Plus) DECnet/OSI must also be installed on the Server node. The Server must be an OpenVMS Server. DIGITAL UNIX, Sun Solaris, HP-UX On a DIGITAL UNIX, Sun Solaris or HP-UX Application Client node, you must select one of the following network interfaces: TCP/IP only The system must be configured with the TCP/IP implementation supplied with the operating system. ObjectBroker over TCP/IP ObjectBroker must be installed and 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 DEC/EDI from the supplied media. The installation procedure provides the option to install only the Application Client components. DIGITAL UNIX, Sun Solaris, HP-UX On DIGITAL UNIX, Sun Solaris and HP-UX, the setld utility, which is provided with the installation kit where required, is used to install DEC/EDI from the supplied media. You must install the application client subsets. 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 3.1x, Windows 95, Windows NT On Windows 3.1, Windows for Workgroups 3.11, Windows 95 or Windows NT you must select one of the following Network Interfaces: * ObjectBroker over DECnet ObjectBroker must be installed on the PC, along with PATHWORKS to support either DECnet or DECnet/OSI (DECnet Plus). *Does not support Windows 95. ObjectBroker over TCP/IP ObjectBroker must be installed on the PC, along with a TCP/IP implementation that is compatible with ObjectBroker. 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 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 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. ORACLE ODBC Driver for Rdb You need to install the appropriate driver for the operating system you are running on the PC. DIGITAL UNIX For connection to a DIGITAL UNIX Server, you must install one of the following ODBC drivers, and related connectivity software on the PC: ORACLE ODBC Driver for Rdb You need to install the appropriate driver for the operating system you are running on the PC. ORACLE 7 You need to install ORACLE TCP/IP protocol adapter, ORACLE SQL*NET and the ORACLE 7 ODBC driver onto the PC. Informix Online For Windows 3.1 and Windows for Workgroups 3.11, you need to install Informix I*Net and the INTERSOLV ODBC driver for Informix Online. For Windows 95 and Windows NT, you need to install either Informix CLI, which includes the ODBC drivers, or Informix I*net and the INTERSOLV ODBC driver for Informix Online. Software Installation Cockpit The Cockpit is supplied as a set of floppy disks, one set for Windows 3.1 and Windows for Workgroups 3.11, the other set for Windows 95 and Windows NT. CommandCenter The CommandCenter is provided on CD-ROM, and contains two kits, one for Windows 3.1 and Windows for Workgroups 3.11, the other for Windows 95 and Windows NT. If you are installing on Windows 3.1 or Windows for Workgroups 3.11, you additionally need to install Win32s, which is provided on the CD-ROM. The CommandCenter CD-ROM also contains the DEC/EDI documentation suite in Adobe Acrobat format, and the free Acrobat reader software. You are recommended to install the online documentation for ease of reference. Server Communications Options The Server supports a number of communications options, and you must install any pre-requisite hardware or software prior to installing DEC/EDI. After installation, you must configure the communications components to enable 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. 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. DIGITAL UNIX On a DIGITAL 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 DIGITAL 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. Chapter 2 Installation Activities This chapter provides pre-installation information. Introduction The following pages show the 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-5). 4. Setting up any Cockpit installations (See Setting Up the Cockpit on page 2-6). 5. Using the CommandCenter or INTERCHANGE (OpenVMS) to configure the Server (See Configuring the Server on page 2-7). Figure 2-1 DEC/EDI System Components The first four tasks establish the 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 DEC/EDI book where the activity is described in more detail. The majority of these activities need to be performed in all DEC/EDI systems where normal routing is used. Where either bypass or application- to-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). Setting Up the Server and Local Application Clients This task covers the physical installation of the 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 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 DEC/EDI Server and Application Client Chapter 6 OpenVMS - Installation of Server and Client Chapter 9 Installing DEC/EDI Cockpit and CommandCenter 1. Install DEC/EDI product licenses, including CommandCenter license 2. Install and verify prerequisite software 3. (UNIX only) Create a decedi account for DEC/EDI to use 4. Install and verify DEC/EDI software 5. Create the database 6. Register 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ฎ Rdb™ only) Configure SQL/Services™ for database access by users of Cockpit and CommandCenter Setting Up Remote Application Clients This task covers the physical installation and configuration of any 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 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 DEC/EDI to use 3. Install and verify DEC/EDI software 4. Register DEC/EDI with Network Interface 5. Configure Network Interface for remote access by DEC/EDI Server Setting Up the CommandCenter This task covers the installation and configuration of the DEC/EDI CommandCenter on a PC. Because the CommandCenter also contains a copy of the 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 DEC/EDI Cockpit and CommandCenter 1. Install and verify prerequisite software 2. Install CommandCenter software 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 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 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 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 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 5. Register your business applications with DEC/EDI, and the nodes on which they run 6. Configure your communications links 7. Define your Trading Partner agreements 8. Start the DEC/EDI system Chapter 3 Configuring the Network Interfaces This chapter describes how to configure the DEC/EDI network interfaces. Introduction The DEC/EDI Server can support connection from local and remote application clients, and remote PC's running the DEC/EDI Cockpit or CommandCenter. The following network interfaces are supported for connection to the DEC/EDI Server: DIGITAL 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 3.xx, 95 and NT. • ObjectBroker over TCP/IP ObjectBroker is used to provide the network interface, using TCP/IP as the underlying network protocol. OpenVMS Server Only • ObjectBroker over DECnet ObjectBroker is used to provide the network interface, using DECnet as the underlying network protocol. This supports Windows 3.xx and Windows NT. The DEC/EDI Server may be configured to support simultaneous connections using one or more of these network interfaces. You must install and configure the DEC/EDI Server network interface prior to configuring the client interfaces. Configuring the DEC/EDI Server This section describes how to configure the network interface on the DEC/EDI Server, and how to set up the local application client to use the network interface. TCP/IP Network Interface This section describes how to configure the TCP/IP network interface on the 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. DIGITAL 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 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 DIGITAL UNIX The 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 DEC/EDI Services will listen for and handle incoming client requests. This assigns unique port numbers for the DEC/EDI Services within the TCP/IP services file /etc/services. # /usr/sbin/decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure ObjectBroker 3. Configure database 4. Modify database users 5. Dump database 6. Load database 7. Manage database 8. Exit Configuration Select option [8] :1 Configuring the TCP/IP Client-Server link ****************************************************** ** Assigned 5150/tcp in /etc/services for decedi_csf. ** (DEC/EDI Post-Fetch service) ** ** ** ** This port number must match that used on any remote ** DEC/EDI client system. ** ** ** ****************************************************** ****************************************************** ** Assigned 5151/tcp in /etc/services for decedi_cst. ** (DEC/EDI Track document service) ** ** ** ** This port number must match that used on any remote ** DEC/EDI client system. ** ** ** ****************************************************** ****************************************************** ** Assigned 5152/tcp in /etc/services for decedi_csg. ** (DEC/EDI GUI service) ** ** ** ** This port number must match that used on any remote ** DEC/EDI Cockpit or CommandCenter installations. ** ** ** ****************************************************** To supply the server node information, create a file: /var/adm/decedi/decedi_servers.dat Use the template, /var/adm/decedi/decedi_servers.template . Step 2: Note down the TCP/IP port numbers that have been assigned to each of the DEC/EDI Services in Step 1 using the following table: Table 3-1 DEC/EDI Services TCP/IP Port Numbers Purpose DEC/EDI Post/Fetch Server DEC/EDI Tracking Server DEC/EDI GUI Server Service Name decedi_csf decedi_cst decedi_csg Enter your Port Number here 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. The same TCP/IP port numbers must be used for all 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 DEC/EDI Server to handle client requests. For further information on specifying the use of another DEC/EDI Server node to handle client requests, refer to Configuring the DEC/EDI Application Client on page 3-14 OpenVMS Configure the local application client to use the TCP/IP network link, using the DEC/EDI Client/Server configuration utility as follows: $ @decedi$configure_client_server DEC/EDI V3.2 DEC/EDI Client/Server Configuration Utility Copyright ฉ 1995,1996,1997 DIGITAL Equipment Corporation. All rights reserved. 1. Configure ObjectBroker 2. Configure TCP/IP Enter client/server interface type [2] : 2 Adding decedi_csf at port 5150 Adding decedi_cst at port 5151 Adding decedi_csg at port 5152 Server information is held in the user editable file: DECEDI$DATA:DECEDI_SERVERS.DAT Do you wish to use TCP/IP for local client access ? (Y/N) : y TCP/IP Configuration completed. Post-Configuration Tasks Once you have configured the network interface, you may start up DEC/EDI. This enables the DEC/EDI Cockpit and CommandCenter, running on a suitably configured PC, to access the DEC/EDI Server. DIGITAL UNIX If you have not yet configured DEC/EDI using the CommandCenter, then you need to start up just the GUI port server. To start up the GUI port server only: # /usr/sbin/decedi_start_gui_server Once you have configured the DEC/EDI Server, you may start up the DEC/EDI Server in full, using the following command: # /usr/sbin/decedi_start OpenVMS If you have not yet configured the DEC/EDI Server, then you should perform a minimal start-up: $ @SYS$STARTUP:DECEDI$STARTUP Once you have configured the DEC/EDI Server, you may start up the DEC/EDI Server in full, using the following command: $ @SYS$STARTUP:DECEDI$STARTUP FULL 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 DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS). 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 names are: OpenVMS @DECEDI$TOOLS:DECEDI$PS_CONTROL DIGITAL Unix decedi_ps_control Example: # /usr/sbin/decedi_ps_control show DEC/EDI Port Server Environment =============================== Hostname = mynode.company.com Tracing = none Service decedi_csg AVAILABLE Maximum Servers = 3 Service decedi_cst SHUTTING DOWN Maximum Servers = 3 Service decedi_csf SHUTTING DOWN Maximum Servers = 3 Further Details These are provided in the DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS), , and also through the DIGITAL UNIX man pages. ObjectBroker This section describes how to configure the ObjectBroker network interface on the DEC/EDI Server. This includes configuration of ObjectBroker using the following network protocols: • ObjectBroker over TCP/IP • ObjectBroker over DECnet Pre-Configuration tasks Prior to configuring ObjectBroker, you should verify that ObjectBroker is installed and is functioning correctly. If you have more than one network protocol installed on your Server system, for example both DECnet and TCP/IP, you should ensure that ObjectBroker is at minimum configured to use the network protocol that you intend to use to communicate with any remote client installations. DIGITAL UNIX The DEC/EDI Server must use the TCP/IP network protocol as the underlying transport for ObjectBroker. OpenVMS The DEC/EDI Server may use either the TCP/IP or DECnet network protocol as the underlying transport for ObjectBroker, or both. If you specify both DECnet and TCP/IP, the DEC/EDI Server may support remote connections over either protocol. DIGITAL UNIX From the root account, determine the name of the ObjectBroker base subset that is installed on your system, as follows: # setld -i | grep OBBBASE | grep installed OBBBASEDEV260 installed ObjectBroker Base System Run the Installation Verification Procedure, and ensure that it completes successfully: # setld -v OBBBASEDEV260 ObjectBroker Base System (OBBBASEDEV260) ************************************************************** About to execute the Installation Verification Procedure. If error messages are displayed, take any necessary corrective action and then re-run the ivp. Verification will take between 1 and 3 minutes depending on CPU type. ************************************************************** ************************************************************** Beginning Installation Verification Procedure for ObjectBroker for DIGITAL UNIX, V2.6-07 Copyright (c) 1991, 1996 by DIGITAL Equipment Corporation, Maynard, MA All Rights reserved. ************************************************************** Starting the ObjectBroker agent... Agent on node: mynode.company.com Version: OBB V2.6-07 Username: root Time Started: Fri Jun 6 08:43:45 1997 Pid: 528 Log Filename: /tmp/obbagent.log Attributes: Debug Server Startup AuthrWOAuthn is ENABLED Active transports are TCPIP OrbV12 style Agent ObjectBroker Network Tester for version OBB V2.6-07 Client side tests will be performed. Time: Wed Jul 23 09:19:45 1997 Tests: All Transport selected: TCP (TCPIP) Server nodename: local node Connection id: none Message size: 512 Num. Sends: 1 1. Loading the transport Please verify the local nodename and local node address. mynode.company.com (1.2.30.123) 2. Connecting to the server. No connection id; connect test will not be performed. The test completed successfully. ************************************************************** Installation Verification Procedure successfully completed. ************************************************************** Verify that the active transports specified for the ObjectBroker agent include TCP/IP. OpenVMS From a suitably privileged account, run the ObjectBroker Installation Verification Procedure and verify that it completes successfully: $ @SYS$TEST:OBB$IVP ************************************************************** Beginning Installation Verification Procedure for ObjectBroker for OpenVMS V2.6-08 ************************************************************** Showing the ObjectBroker agent attributes... Agent on node: SERVER Version: OBB V2.6-08 Username: system Time Started: Wed Jul 16 15:51:42 1997 Pid: 0000021D Log Filename: SYS$SPECIFIC:[OBB.SCRATCH.SARK]OBB$AGENT.LOG;7 Attributes: AuthrWOAuthn is ENABLED Active transports are DECnet, TCPIP OrbV12 style Agent Showing the ObjectBroker default configuration... Configuration "DECnet and TCP/IP Configuration" (Current) ------------------------------------------------------- Authentication AuthrWOAuthn: Enabled Package: Trusted Description: Trusted authentication package Network Package: DECnet Description: DECnet transport package Package: TCP Description: TCP/IP transport package Logging Level None Repository Cache Size 5 Maximum Active Servers 0 Verify that the active transports specified for the ObjectBroker agent include those required for connection from any remote client installations. Configuration Tasks DIGITAL UNIX The 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 ObjectBroker. # decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure ObjectBroker 3. Configure database 4. Modify database users 5. Dump database 6. Load database 7. Manage database 8. Exit Configuration Select option [8] : 2 Step 2: You are asked to enter the name of your DEC/EDI Server. At this stage, you are setting up the Server node, so select the default answer of OBB_LOCAL, that ObjectBroker interprets as the current node: Configuring ObjectBroker Enter the name of the DEC/EDI Server [OBB_LOCAL] : ...creating repository ...registering servers ...creating client object ...creating context object ObjectBroker Configuration Complete Press to continue. You are recommended to use the TCP/IP network interface for local client access, though you may elect to use ObjectBroker if you prefer. If you do not wish to use the ObjectBroker network interface for local client access, then you must configure the TCP/IP network interface, as described in TCP/IP Network Interface on page 3-2, after you have configured ObjectBroker. OpenVMS The DEC/EDI Server configuration consists of the following steps: Step 1: From a suitably privileged account, invoke the DEC/EDI Client/Server configuration utility: @DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER.COM DEC/EDI V3.2 DEC/EDI Client/Server Configuration Utility Copyright (C) 1995,1996,1997 DIGITAL Equipment Corporation. All rights reserved. 1. Configure ObjectBroker 2. Configure TCP/IP Enter client/server interface type [2] : 1 WARNING ------- This utility shuts down and restarts ObjectBroker during the configuration. Do you wish to continue ? (Y/N) : y Configuring ObjectBroker... Step 2: You are asked whether you wish to use ObjectBroker for local client access. DECnet For DECnet, you must use ObjectBroker for local client access. TCP/IP For TCP/IP, if you are using DIGITAL TCP/IP Services, then you are recommended to use the TCP/IP network interface for local client access, as described in TCP/IP Network Interface on page 3-2. Do you wish to use ObjectBroker for local client access ? (Y/N) : n ObjectBroker Configuration completed. Post-Configuration Tasks Once you have configured the DEC/EDI Server, you must configure ObjectBroker to enable access from any remote application clients and PCs running Cockpit or CommandCenter. The steps you need to take are described in Configuring the DEC/EDI Application Client on page 3-14 and on page 3-31. Once you have configured ObjectBroker for remote access, you may start up the DEC/EDI Server as follows: DIGITAL UNIX # /usr/sbin/decedi_start OpenVMS $ @SYS$STARTUP:DECEDI$STARTUP This enables the DEC/EDI Cockpit and CommandCenter, running on a suitably configured PC, to access the DEC/EDI Server. For Further Information For information on ObjectBroker security, refer to the DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS). For information on installing and configuring ObjectBroker, refer to the ObjectBroker Installation and Configuration book. Configuring the DEC/EDI Application Client This section describes how to configure the network interface on the DEC/EDI Application Client, along with any steps that need to be performed on the DEC/EDI Server, to enable connection from the remote application client. The DEC/EDI Application Client may be configured to use either one of the TCP/IP network interface or the ObjectBroker network interface, though not at the same time. If you are able to upgrade your client and server installations, you are recommended to use the TCP/IP network interface, though you may continue to use ObjectBroker if you wish. TCP/IP Network Interface This section describes how to configure the TCP/IP network interface on the DEC/EDI Application Client. The TCP/IP network interface may be used for connection from the following DEC/EDI Application Client releases: • DEC/EDI for DIGITAL UNIX, Version 3.2 • DEC/EDI for OpenVMS VAX, Version 3.2 • DEC/EDI for OpenVMS Alpha, Version 3.2 • DEC/EDI Application Client for Sun Solaris, Version 3.2 • DEC/EDI Application Client for HP-UX, Version 3.2 The Application Client may be configured to connect to one or more DEC/EDI Server systems, selected by application name, or to a default DEC/EDI Server. In addition, one or more failover DEC/EDI Servers may be specified to handle client requests, if the primary DEC/EDI Server is not currently available. 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 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: DIGITAL UNIX, Sun Solaris, HP-UX # 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 Configuration Tasks DIGITAL UNIX, Sun Solaris, HP-UX The 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 DEC/EDI Server for handling incoming client requests. The port numbers are defined within the TCP/IP services file /etc/services. DIGITAL UNIX # /usr/sbin/decedi_config Sun Solaris, HP-UX # /usr/bin/decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure ObjectBroker 3. Exit Configuration Select option [3] :1 Configuring the TCP/IP Client-Server link ****************************************************** ** Assigned 5150/tcp in /etc/services for decedi_csf. ** (DEC/EDI Post-Fetch service) ** ** ** ** This port number must match that used on the remote ** DEC/EDI server system. ** ** ** ****************************************************** ****************************************************** ** Assigned 5151/tcp in /etc/services for decedi_cst. ** (DEC/EDI Track document service) ** ** ** ** This port number must match that used on the remote ** DEC/EDI server system. ** ** ** ****************************************************** To supply the server node information, create a file: /var/adm/decedi/decedi_servers.dat Use the template, /var/adm/decedi/decedi_servers.template . Press to continue. Step 2: The TCP/IP port numbers specified on the client must match those defined on the DEC/EDI Server. Compare these with the values you have noted in the table 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 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 DEC/EDI Server OpenVMS The DEC/EDI Application Client configuration consists of the following steps: Step 1: Configure the application client to use the TCP/IP network link, using the DEC/EDI Client/Server configuration utility as follows: $ @DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER.COM DEC/EDI V3.2 Client/Server Configuration Utility Copyright (C) 1995,1996,1997 DIGITAL Equipment Corporation. All rights reserved 1. Configure ObjectBroker 2 Configure TCP/IP Enter client/server interface type [2]: 2 Server information is held in user editable file: DECEDI$DATA:DECEDI_SERVERS.DAT This can be created from the template file: DECEDI$DATA:DECEDI_SERVERS.TEMPLATE Do you wish to use TCP/IP for local client access? (Y/N): y TCP/IP configuration completed. Step 2: Specify the default DEC/EDI Server that should be used for handling requests from the application client. Copy the 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 DEC/EDI Server Post-Configuration Tasks If you wish, you may add additional DEC/EDI Server definitions and specify which application names should access those servers. These must be placed within the DEC/EDI Servers definition file prior to the line specifying the default DEC/EDI Server. DIGITAL 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 DEC/EDI Server on node myserver.com. In the event that the DEC/EDI Server is unavailable, the backup DEC/EDI Server on node backup.com is used. The application JOLLY-OLD-SYSTEMS uses the DEC/EDI Server on node edidev as the primary 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 DEC/EDI Server. DEC-DIRECT-UK-LTD myserver.com backup.com SHINY-NEW-SYSTEMS myserver.com backup.com JOLLY-OLD-SYSTEMS edidev edidev2 edidev3 * edigate.com ! default 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 DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS). ObjectBroker This section describes how to configure the ObjectBroker network interface on the DEC/EDI Application Client. The ObjectBroker network interface may be used for connection from the following DEC/EDI Application Client releases: • DEC/EDI for DIGITAL UNIX, Version 3.1 or higher • DEC/EDI for OpenVMS VAX, Version 2.1A or higher • DEC/EDI for OpenVMS Alpha, Version 2.1A or higher • DEC/EDI Application Client for Sun Solaris, Version 3.1 or higher • DEC/EDI Application Client for HP-UX, Version 2.1A or higher In addition, this interface may be used to support earlier releases of the DEC/EDI Application Client, including the following: • DEC/EDI Application Client for IBM AIX, Version 2.1A • DEC/EDI Application Client for IBM AS/400, Version 2.1A Configuring ObjectBroker for Remote Access So that the DEC/EDI Server can pass data back to the Application Client, ObjectBroker on the Application Client node needs to be configured to register the node that is running the DEC/EDI Server. The precise detail of what you need to do to achieve this depends on what security model you have previously selected for ObjectBroker on the Application Client node. The DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS) provides a short introduction to ObjectBroker security models, and how you cope with models other than the NORMAL model. This section assumes you are using the NORMAL security model. Pre-Configuration Tasks Prior to configuring ObjectBroker, you should verify that ObjectBroker is installed and is functioning correctly on both the application client and DEC/EDI Server systems. on the Server Step 1: On the DEC/EDI Server node, verify that the ObjectBroker agent is running, and make a note of the exact node name as displayed by the ObjectBroker agent. You will need this information later when configuring the ObjectBroker proxies on the application client node. DIGITAL UNIX # obbmsho -A Agent on node: myserver.company.com Version: OBB V2.6-07 Username: root Time Started: Fri Jun 6 08:43:45 1997 Pid: 528 Log Filename: /tmp/obbagent.log Attributes: Debug Server Startup AuthrWOAuthn is ENABLED Active transports are TCPIP OrbV12 style Agent OpenVMS $ APPLICATION/BROKER SHOW AGENT Agent on node: VMSERV Version: OBB V2.7-11 Username: system Time Started: Tue Jul 1 12:43:01 1997 Pid: 0000021F Log Filename: SYS$SPECIFIC:[OBB.SCRATCH.SCARP]OBB$AGENT.LOG;14 Attributes: AuthrWOAuthn is DISABLED Active transports are DECnet, TCPIP OrbV12 style Agent on the Client Step 2: On the DEC/EDI Application Client node, verify that the ObjectBroker agent is running, and make a note of the exact node name as displayed by the ObjectBroker agent. You will need this information later when configuring the ObjectBroker proxies on the DEC/EDI Server node. DIGITAL UNIX, Sun Solaris, HP-UX # obbmsho -A Agent on node: myclient.company.com Version: OBB V2.6-07 Username: root Time Started: Fri Jun 6 08:43:45 1997 Pid: 528 Log Filename: /tmp/obbagent.log Attributes: Debug Server Startup AuthrWOAuthn is ENABLED Active transports are TCPIP OrbV12 style Agent OpenVMS $ APPLICATION/BROKER SHOW AGENT Agent on node: CLIENT Version: OBB V2.7-11 Username: system Time Started: Tue Jul 1 12:43:01 1997 Pid: 0000021F Log Filename: SYS$SPECIFIC:[OBB.SCRATCH.SCARP]OBB$AGENT.LOG;14 Attributes: AuthrWOAuthn is DISABLED Active transports are DECnet, TCPIP OrbV12 style Agent on the Server Step 3: On the DEC/EDI Server node, start up the server side network test: DIGITAL UNIX # obbntst -s OpenVMS using TCP/IP $ APPLICATION/BROKER OBB> TEST NETWORK SERVER/TRANSPORT=TCPIP OpenVMS using DECnet $ APPLICATION/BROKER OBB> TEST NETWORK SERVER This displays a connection identifier, which should be specified when running the client side network test. In the following example, the connection identifier is 00000451: ObjectBroker Network Tester for version OBB V2.5A-04 Server side tests will be performed. Time: Thu Jul 24 14:55:02 1997 Tests: All Transport selected: TCP (TCPIP) 1. Loading the transport Please verify the local nodename and local node address. ediserv.company.com (1.101.2.34) 2. Registering on network as server Connection identifier: 00000451 3. Waiting for network events. Please initiate client- side tests. Use the connection identifier shown above when starting the client-side. The server side network test waits until it receives a valid connection from a client side network test. on the Client Step 4: On the DEC/EDI Application Client node, run the client side network test: DIGITAL UNIX, Sun Solaris, HP-UX # obbntst -c 00000451 -n ediserv.company.com OpenVMS using TCP/IP $ APPLICATION/BROKER OBB> TEST NETWORK CLIENT - /SERVER=(NODE=ediserv.company.com,CONNECT=00000451)- /TRANSPORT=TCPIP OpenVMS using DECnet $ APPLICATION/BROKER OBB> TEST NETWORK CLIENT - /SERVER=(NODE=VMSERV,CONNECT=00000451) This connects to the specified server node, and completes the network test. Verify that both the client and server network tests have completed successfully. For example, the following is displayed on the client node: ObjectBroker Network Tester for version OBB V2.7-11 Client side tests will be performed. Time: Thu Jul 24 15:54:37 1997 Tests: All Transport selected: TCP (TCPIP) Server nodename: MYNODE.COMPANY.COM Connection id: 00000451 Message size: 512 Num. Sends: 1 1. Loading the transport Please verify the local nodename and local node address. client.company.com (1.102.3.123) 2. Connecting to the server. 3. Sending the message to the specified server. 001) Send: header=24 bytes; data=512 bytes; total=536 bytes. Receive: header=24 bytes; data=512 bytes; total=536 bytes. The test completed successfully. Configuration Tasks - Server The following configuration tasks must be performed on the DEC/EDI Server node, to enable connection from the DEC/EDI Application Client. Step 1: Check that all old methods are stopped by entering: DIGITAL Unix # obbmstp or OpenVMS $ APPLICATION/BROKER STOP SERVER Step 2: Check you are using the NORMAL security model, by entering: DIGITAL UNIX # obbshsec OpenVMS $ APPLICATION/BROKER SHOW SECURITY Step 3: Check to see what remote nodes are already registered, by entering: DIGITAL UNIX # obbshpxy OpenVMS $ APPLICATION/BROKER SHOW PROXY Step 4: If the remote application client node is not already registered, then add a proxy to allow any account on the application client node to use the decedi account on the Server node. Specify the client node name exactly as given by the ObjectBroker agent on the application client node. On OpenVMS, if the node name is in lower case, specify the node name within quotes. DIGITAL UNIX # obbadpxy -h myclient.company.com -u `*' decedi OpenVMS using TCP/IP $ APPLICATION/BROKER OBB> ADD PROXY DECEDI- /REMOTE_USER=(USER="*",HOST="myclient.company.com") OpenVMS using DECnet $ APPLICATION/BROKER OBB> ADD PROXY DECEDI- /REMOTE_USER=(USER=*,HOST=MYCLI) TCP/IP only If you are using TCP/IP, you are recommended to add proxies for both the long and short forms of the application client node name: # obbadpxy -h myclient.company.com -u `*' decedi # obbadpxy -h myclient -u `*' decedi If the application client node name is not registered with your domain name server, add the TCP/IP address of the client, along with both the long and short forms of the application client node name to the TCP/IP hosts file /etc/hosts. Step 5: Reset the system context for the ObjectBroker agent, to ensure that any changes to the proxy access list become effective. DIGITAL UNIX # obbmset -A -C OpenVMS $ APPLICATION/BROKER SET AGENT/NEW_CONTEXT You need to repeat the above steps to enable access from all Application Client nodes. Configuration Tasks - Application Client The following configuration tasks must be performed on the DEC/EDI Application Client node, to enable the DEC/EDI Server to return any requested files back to the application client. Step 1: From a suitably privileged account, invoke the DEC/EDI Application Client configuration utility, to configure the ObjectBroker network interface. DIGITAL UNIX, Sun Solaris, HP-UX # decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure ObjectBroker 3. Exit Configuration Select option [3] : 2 OpenVMS $ @DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT.SERVER DEC/EDI V3.2 Client/Server Configuration Utility Copyright (C) 1995,1996,1997 DIGITAL Equipment Corporation. All rights reserved 1. Configure ObjectBroker 2 Configure TCP/IP Enter client/server interface type [2]: 1 all clients You are asked to enter the name of the DEC/EDI Server. Enter the name of your DEC/EDI Server that you have configured in Configuration Tasks - Server on page 3-25. Configuring ObjectBroker Enter the name of the DEC/EDI Server [OBB_LOCAL] : myserver.company.com ...creating repository ...registering servers ...creating client object ...creating context object ObjectBroker Configuration Complete Press to continue. Step 2: Check you are using the NORMAL security model, by entering: DIGITAL UNIX, Sun Solaris, HP-UX # obbshsec OpenVMS $ APPLICATION/BROKER SHOW SECURITY Step 3: Check to see what remote nodes are already registered, by entering: DIGITAL UNIX, Sun Solaris, HP-UX # obbshpxy OpenVMS $ APPLICATION/BROKER SHOW PROXY Step 4: Determine or create the user accounts on the application client node under which you will run any DEC/EDI applications. These user accounts must have sufficient privelege to access the DEC/EDI software, and to create files in the directory which is used for sending to and receiving files from DEC/EDI. Step 5: If the remote DEC/EDI Server node is not already registered, then add a proxy to allow decedi account on the DEC/EDI Server node to use the user accounts for DEC/EDI applications. Specify the server node name exactly as given by the ObjectBroker agent on the DEC/EDI Server node. On OpenVMS, if the node name is in lower case, specify the node name within quotes. DIGITAL UNIX, Sun Solaris, HP-UX # obbadpxy -h myserver.company.com -u decedi myuser OpenVMS using TCP/IP $ APPLICATION/BROKER OBB> ADD PROXY MYUSER- /REMOTE_USER=(USER="decedi",HOST="myserver") OpenVMS using DECnet $ APPLICATION/BROKER OBB> ADD PROXY MYUSER- /REMOTE_USER=(USER=DECEDI,HOST=MYCLI) TCP/IP only If you are using TCP/IP, you are recommended to add proxies for both the long and short forms of the server node name: # obbadpxy -h myserver.company.com -u decedi myuser # obbadpxy -h myserver -u decedi myuser If the server node name is not registered with your domain name server, add the TCP/IP address of the server, along with both the long and short forms of the server node name to the TCP/IP hosts file /etc/hosts. Step 6: Reset the system context for the ObjectBroker agent, to ensure that any changes to the proxy access list become effective. DIGITAL UNIX, Sun Solaris, HP-UX # obbmset -A -C OpenVMS $ APPLICATION/BROKER SET AGENT/NEW_CONTEXT Step 7: Verify that the proxies on both the application client and DEC/EDI Server nodes are configured correctly, by using the proxy details to show the ObjectBroker agent on the remote node. DIGITAL UNIX server # obbmsho -A -n myclient.company.com OpenVMS server $ APPLICATION/BROKER OBB> SHOW AGENT/NODE=MYCLI DIGITAL UNIX, Sun Solaris, HP-UX client # obbmsho -A -n myserver.company.com OpenVMS client $ APPLICATION/BROKER OBB> SHOW AGENT/NODE="myserver.company.com" If you receive the following error message, verify that the proxies have been configured correctly on the remote node: OBB_INV_NOTAUTHORIZED (e), Client user is not authorized to access server. The following example shows the expected output from an ObjectBroker agent running on the remote node: # obbmsho -A -n myserver.company.com Agent on node: myserver.company.com Version: OBB V2.6-07 Username: root Time Started: Fri Jun 6 08:43:45 1997 Pid: 528 Log Filename: /tmp/obbagent.log Attributes: Debug Server Startup AuthrWOAuthn is ENABLED Active transports are TCPIP OrbV12 style Agent You need to repeat the above steps to enable communication with all required DEC/EDI Server nodes. Post-Configuration Tasks You should be able to issue the following Application Client command on each node where the Application Client is installed. This verifies the network link between the Application Client node and the ObjectBroker configuration on the Server. You should be able to issue the following command: DIGITAL UNIX, Sun Solaris, HP-UX # trade track TEST -type=document OpenVMS $ TRADE TRACK TEST -TYPE=DOCUMENT This command should produce the following message: Not authorized to access the EDI Server System This indicates that the network was correctly able to pass command information from the Application Client to the correct ObjectBroker function on the DEC/EDI Server. This means that the network is set up correctly, and that ObjectBroker on the Server is configured to allow proxy access from the Application Client. If you encounter other errors, refer to the DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS). The not authorized message indicates that you haven't yet registered any business applications (in this case TEST) with the DEC/EDI Server. Registering business applications with the Server is described the DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS). For Further Information For information on ObjectBroker security, refer to the DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS). For information on installing and configuring ObjectBroker, refer to the ObjectBroker Installation and Configuration book. 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 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 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. Account Privileges DIGITAL 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 • DIGITAL UNIX Oracle 7 • DIGITAL UNIX INFORMIX • DIGITAL UNIX Oracle Rdb • OpenVMS VAX/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 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-8. Oracle7 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 Oracle7 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. 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 Oracle7 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 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. INFORMIX OnLine If you are using INFORMIXฎ OnLine to provide your database, you need to create or specify a raw device for the database to occupy, before you can proceed to create the database. Creation of raw devices is a standard UNIX system management function. You should refer to your UNIX system documentation for more details of creating raw devices. In particular you should refer to the disklabel command. You do need to decide how large to create the raw device, as this affects the size of the database and in consequence how much data it can contain. The database uses the whole device, destroying any other data on the device. When creating the database, you need to specify a device that is at least 40 Mbytes. However this is a minimum size required to run a Server, and most systems will require considerably more disk space. It is important to ensure you create a database that is sufficiently large for your intended workload. If the database fills up, when the Server is running, the Server will fail. In most DEC/EDI systems, the main consumers of space in the database are the various audit trail tables and EDI Standards tables. The following formula can be used to calculate the approximate size of database required for a specified workload. Note that this is intended as a guide, and actual requirements may differ. The value is calculated in MBytes. DatabaseSize = 31 +EDIStandardSize +DocumentSize+TransmissionFileSize Where: EDIStandardSize is the amount of space required in the database to store EDI Standards information, and can be calculated from the expression: 5 x peak number of EDI standards versions DocumentSize is the amount of space required in the database to store audit trail information about documents. This includes information about documents in the current audit trail and in the archive audit trail. This can be calculated from the following expression: 0.004 x (peak documents in current system + peak documents in archive system) TransmissionFileSize is the amount of space required in the database to store audit trail information about transmission files. This includes information about transmission files in the current audit trail and in the archive audit trail. This can be calculated from the following expression: 0.007 x (peak transmission files in current system + peak transmission files in archive system) Note that in the above equations it is important to calculate based on peak amounts for each of the values. This is because the database tables are expanded to the peak size used, and do not reduce if data is removed from the tables, for example by using the decedi_arch command. Typical Example For example, a DEC/EDI system that is to contain 2 EDI Standards, 500 current documents, 20000 archive documents, 100 current transmission files and 4000 archive transmission files, would need a database of 152 Mbytes, calculated as follows: DatabaseSize = 31 + (5 x 2) + 0.004 x (500 + 20000) + 0.007 x (100 + 4000) It should be noted that you should have knowledge of these peak values when you did an initial EDI planning exercise. These are the absolute maximums you intend your system to cope with. In general there should not be much in the current audit trail, as most things get moved to the archive audit trail as soon as possible. The number of current transmission files is controlled by how regularly outbound communications jobs run versus how many transmission files get built in that interval. If you have an export job which just runs once a day, but you send in 200 documents per hour with a transmission build interval of once every 10 minutes then you could expect to get a 144 transmission files and 4800 documents in the current audit trail before the export job ran. Similarly on inbound, the rate at which transmission files enter the system versus how often the Application Clients fetch them will control the amount of current documents in the system. The count of the archive transmission files and documents is the total number of documents and transmission files the system is expected to cope with between the times that you perform a secondary archive onto tape, using the decedi_arch command. Using the above example, if you only ran decedi_arch in the above example once a week then the archive audit trail needs to cope with 1008 transmission files, and 33600 documents. Please note that this does not build in any safety factors for such cases as when something does not happen as expected so the actual peak values used should always be set higher than those expected. DIGITAL UNIX Oracle Rdb If you are using Oracle Rdb to provide your database, you need to specify a directory location on a disk with enough spare disk space. For example, 50 Mbytes of disk space is sufficient to store information for: Number of documents in the Current Audit Trail Number of documents in the Archive Audit Trail Number of transmission files in the Current Audit Trail Number of transmission files in the Archive Audit Trail 1000 10000 500 5000 If you anticipate the need to store more than this, you should ensure extra space is available on the disk on which you locate your database. 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. Performance Limiting Aspects Disk speed. The performance of your Server can easily be limited by the speed of access to the 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 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. 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 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: Number of documents in the Current Audit Trail Number of documents in the Archive Audit Trail Number of transmission files in the Current Audit Trail Number of transmission files in the Archive Audit Trail 1000 1000 1000 1000 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 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 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. B - Creating the Database • DIGITAL UNIX Oracle 7 • DIGITAL UNIX INFORMIX • DIGITAL UNIX Oracle Rdb • OpenVMS VAX/Alpha Oracle Rdb DIGITAL UNIX All Databases This task is performed by using the 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 ObjectBroker 3. Configure database 4. Modify database users 5. Dump database 6. Load database 7. Manage database 8. Exit Configuration Select Option [8] : 3 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 is either a raw device (for INFORMIX OnLine), or the name 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 INFORMIX Example Enter the database to be used (Rdb, Inf, Ora) [Inf] : Inf Enter raw device on which to hold the database [ ] : /dev/rre1e ...Creating /usr/informix/etc/onconfig.decedi ...Starting new DEC/EDI database server Database created. Database closed. ... ... Database Configuration Complete Typical Oracle7 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] : Enter DEC/EDI Oracle 7 database location [/var/adm/decedi/db] : /userb/oracle/db ...Modifying /etc/oratab ...Modifying /var/adm/decedi/config.dat Enter DEC/EDI Oracle 7 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 DEC/EDI Oracle password. Database Configuration Complete Typical Oracle Rdb Example Configuring Database Enter the database to be used (Rdb, Inf, Ora) [Inf] : Rdb Enter Oracle Rdb database location : /usr/users/rdbdb/decedi_db.rdb ...Modifying //.dbsrc ...Modifying.. ... ... Database Configuration Complete OpenVMS The 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-0 * Please enter the Rdb/VMS version to be used by DEC/EDI [V7.0-0]: 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-0 (STANDARD) Current PROCESS SQL environment is version V7.0-0 (STANDARD)Current PROCESS Rdb/Dispatch environment is version V7.0-0 (STANDARD) Database Version It is essential that the database version on your system is the same as that used by 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 Migrating the Database If you are installing DEC/EDI over a previous version then the database structure needs migrating to the new structure. DIGITAL UNIX After installing 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 DEC/EDI database will normally be migrated during the installation process. If you are upgrading from DEC/EDI version 2.0 or older, a new empty database structure is created and the old version is kept safely. Messages similar to those shown below will appear: Creating new database in DECEDI$TOP:[AUDIT_DB]... Creating new database in DECEDI$TOP:[ARCHIVE_DB]... WARNING: The structure of all mapper databases needs to be modified. All previous FileBridge databases and DEC/EDI V2.0 mapper databases will need to be migrated before using the DEC/EDI V2.1 mapper. To migrate the live and test databases in FBR$HOME run the post-installation task DECEDI$V21_MIGRATE.COM. Migration of all local test databases should be done using FBR$ARCHIVE.COM. Read the release notes for details. Execute the actions described in the second half of the Warning message to migrate the database if needed. Creating User Accounts for Database Access Each PC running either the CommandCenter or the Cockpit accesses the DEC/EDI database on the Server via ODBC™ 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. 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. DIGITAL UNIX Oracle Rdb and Informix You create a user account on the Server by using the UNIX adduser utility. You should do this from the root account. Note that the account that you are creating need not be the same as the one that ObjectBroker uses. This means that you can have one account that ObjectBroker uses for proxy access to the Server, and multiple separate accounts for individual access to the database. DIGITAL UNIX Oracle7 Oracle7 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 Oracle7 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. Note that the account that you are creating need not be the same as the one that ObjectBroker uses. This means that you can have one account that ObjectBroker uses for proxy access to the Server, and multiple separate accounts for individual access to the database. Oracle 7 User Registration DIGITAL UNIX All GUI users who log in, access an account on the Server machine which is authorized to access the database. Oracle7 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 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 DEC/EDI database is protected via OpenVMS ACLs. To allow a user to access the DEC/EDI databases, the 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 DEC/EDI database. Oracle 7 and Enhanced C2-Security Only the Oracle 7 database currently supports C2 Enhanced Security. Neither the Informix Online nor Oracle Rdb version that are compatible with this release of DEC/EDI support C2 Enhanced Security. To determine whether your system is running with enhanced security, use the following command: # setld -i | grep OSFC2SEC OSFC2SEC350 installed C2-Security (System Administration) To set up enhanced security on your system, read the documentation and use the following command: # /usr/sbin/secsetup You need to reboot your system in order for enhanced security to become effective. Granting Database Access to User Accounts For each account you have created, you need to grant access to the DEC/EDI database. You use decedi_config, Option 4 to do this. This example grants access to a user account called ediusr: # decedi_config 4. Modify database users Select option [8] : 4 There are no DEC/EDI database users (other than decedi). 1. Add User 2. Remove User 3. Return Select option [3] : 1 Enter user name : ediusr Current DEC/EDI database users (other than decedi) are: ediusr 1. Add User 2. Remove User 3. Return Select option [3] : 3 ...Creating /var/adm/decedi/decedi_db_inf_users.sql ...Modifying database access ... ... Database users updated. Press to continue. Note that by selecting the option to add users, you are creating a list of users to add. The database is updated only when you select the Return option. 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. DIGITAL Unix SQL Services Example SQL/Services scripts are supplied in files that can be found in the following location: /usr/examples/decedi/sqs/*.sqs. These are supplied as examples of what you need to do. If you are using SQL/Services on the Server only in conjunction with DEC/EDI, then you can use them almost unchanged. However, if you have other uses for SQL/Services, you have to merge the commands in these examples with those you are already using. The example scripts are called: • sqs_create.sqs - to be run ONCE to create the DEC/EDI service. • sqs_startup.sqs - to be executed on system startup. • sqs_shutdown.sqs - to be executed on system shutdown. As a minimum, these examples need to be modified to add the password for the dbsmgr account, and then run from the root account, for example: # sqs_manage -i sqs_startup.sqs For more information on configuring SQL/Services refer to the Oracle SQL/Services Installation and Configuration Guide. DIGITAL Unix Informix No extra configuration is required. DIGITAL Unix Oracle 7 As part of creating the DEC/EDI Oracle 7 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 7 TNS listener re-started for these to take effect. Merging Files Refer to the DEC/EDI: User's Guides (DIGITAL UNIX and Open VMS) for information on merging the files. Backing up the DEC/EDI Database OpenVMS No DEC/EDI tools are provided on OpenVMS to achieve this, instead the user should refer to the Oracle Rdb RMU documentation, and in particular, the /BACKUP qualifier. Restoring the DEC/EDI Database From Backup OpenVMS No DEC/EDI tools are provided on OpenVMS to achieve this, instead the user should refer to the Oracle Rdb RMU documentation, and in particular, the /RESTORE qualifier. Starting and Stopping the DEC/EDI Database OpenVMS It is assumed Oracle Rdb is started before the Server, normally as part of system startup. Oracle Rdb can be started or stopped manually using the startup and shutdown procedures supplied with the version of Oracle Rdb you have installed. For further help on this command please refer to the Oracle Rdb documentation. Similar procedures are supplied for starting and stopping the Oracle SQL Services. Shutting Down Oracle Rdb Please note that before shutting down Oracle Rdb, you should ensure that both DEC/EDI and SQL/Services have been shutdown. DIGITAL UNIX DECEDI_CONFIG Options The decedi_config utility presents a number of other options. These are described in the following sections. Saving a Copy of the Database By Using the Dump Database Option This option dumps the contents of the DEC/EDI database to a file whose name you are prompted to specify. You are most likely to use this option to take a copy of the data in your database before you perform any database maintenance. You may also use this option to take a copy of your database for transferring it to another Server. This option utilises the database vendor's tools, and as such varies between the various databases supported. They are: • Oracle7 The exp utility to do a FULL database unload • Informix The onunload utility to do a database unload • Oracle Rdb The rmu -Backup utility to backup the entire database Each of these has its own restrictions and the user should refer to the database vendor's documentation for more details. For Oracle, database dumping and re-loading must be performed by an Oracle user who has `dba' privilege. You will be asked for the user and their password as part of this option. Populating the Database By Using the Load Database Option This option loads a DEC/EDI database from a file previously created by using the Dump Database option. This operation destroys any existing data already in the database. If you have many records in the database, this option can take many minutes to complete. This option utilises the database vendor's tools, and as such varies between the various databases supported. They are: • Oracle Rdb The rmu -Restore utility to restore the entire database • Informix The onload utility to do a database load • Oracle7 The imp utility to do a FULL database load Each of these has its own restrictions, and you should refer to the database vendor's documentation for more details. Oracle7 Database dumping and re-loading must be performed by an Oracle 7 user who has dba privilege. You will be asked for the user and their password as part of this option. It is highly recommended that you recreate the Oracle7 database prior to performing a reload to ensure that no duplication of information occurs. Starting and Stopping the Database Server By Using the Manage Database Option This behaviour of this option depends on the database you are using. INFORMIX OnLine only If you are using INFORMIX OnLine, this option allows you to: • See whether the INFORMIX database server for DEC/EDI is started. • Start the INFORMIX database server. • Stop the INFORMIX database server. Before you can run the Server or access the database by using Cockpit or CommandCenter, the database server must be started. The database server is normally started automatically when needed, for example when you start the Server, or when you use decedi_config to configure, dump or load the database. The Manage database option is provided in case you need to use it. For further information on stopping or starting the INFORMIX database server see the INFORMIX OnLine Administrators Guide, Volume 1. Oracle Rdb only If your database is provided by Oracle Rdb, this option displays messages indicating whether the database server is started or not. It does not allow to start or stop the database server. It is assumed Oracle Rdb is started before the Server, normally as part of system startup. Oracle Rdb can be started or stopped manually using the rmu command from the root account. For further help on this command please refer to the man entry on rmu. Please note that before shutting down Oracle Rdb, you should ensure that both DEC/EDI and SQL/Services have been shutdown. See Configuring the Database Network Connectivity on page 4-19 for more information on shutting down SQL/Services. Oracle7 If you are using the Oracle7, this option allows you to: • See whether the Oracle7 database server for DEC/EDI is started • Start the Oracle7 database server • Stop the Oracle7 database server Before you can run the Server or access the database by using Cockpit or CommandCenter, the database must be started. The database server is normally started automatically when needed, for example when to start the Server, or when you use decedi_config to configure, dump or load the database. The Manage Database option is provided in case you need to start or stop the database at other times. For further information on stopping or starting the Oracle7 database server, see the Oracle7 Server Administrator's Guide. Using DECEDI_CONFIG Again Once you have a running Server, you may wish to use the decedi_config utility again, perhaps because you want to maintain the database, or perhaps because you suspect there are configuration problems with ObjectBroker. The configuration options provided by decedi_config destroy any existing configuration. Before you run decedi_config, you should be sure that: • You have first stopped the Server. Oracle Rdb only • You have shut down SQL/Services. This ensures that there are no users of Cockpit or CommandCenter accessing the database. See Configuring the Database Network Connectivity on page 4-19 for information on shutting down SQL/Services. • You use the Dump database option to save a copy of your current database, before either re-creating or using the Load database option. Chapter 5 UNIX - Installation of DEC/EDI Server and Application Client This chapter describes the preparation for and installation of DEC/EDI Server and Application Client by the System Manager or Administrator, onto a DIGITAL UNIX platform. Introduction This chapter is divided into sections as shown below: • Preparing to Install DEC/EDI on page 5-2 • Installing DEC/EDI on page 5-26 • After Installation on page 5-32 • Setting Up the System on page 5-34 Preparing to Install DEC/EDI Before attempting to proceed with the instructions contained within this book you should be familiar with the contents of DEC/EDI Introduction and have decided on which components will be installed on this and any other nodes. Before attempting to install 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 DEC/EDI from Your System on page 5-24 • # setld -d DEDICLT311 DEDICLTMAN311 on page 5-24 Reading the Online Release Notes DEC/EDI provides online release notes. DIGITALDIGITAL 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 DEC/EDI will be placed in the following location after installation: /usr/doc/DECEDI(subset_number).release_notes /usr/doc/DECEDI(subset_number)_release_notes.ps Installation Options Your media kit contains one or more DEC/EDI components which are as follow: • DEC/EDI Application Client. Select if applications on the installation platform are to either exchange files with the DEC/EDI Server, or track files in the DEC/EDI Server using the DEC/EDI Application Programming Interface (API) or the DEC/EDI Command Line Interface (CLI). Necessary whether or not the DEC/EDI Server is on the same platform as the applications. • 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. • 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 the 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. The components, and their subsets are detailed below:. Table 5-1 DEC/EDI Component Subsets Component (DEC/EDI ...) Application Client Server Message Update Service (MUS) Subset (DEC/EDI ...) Base Client Client Man Pages Base Server Server Man Pages EDI Translation Services Mailbus 400 Gateway OFTP Gateway SMTP/MIME Communications Gateway 3780 (BISYNC) Communications Gateway Message Updates Base Message Updates EDIFACT IMPDEF files Message Updates ODETTE IMPDEF files Message Updates X12 files Message Updates TDCC files Message Updates TRADACOMS files Install ? Mandatory Mandatory Optional Mandatory Mandatory Optional Optional Optional Optional Optional Optional Mandatory Optional Optional Optional Optional Optional Additional Information on DEC/EDI Subsets The following provides additional information on the DEC/EDI subsets: • The DEC/EDI Client Man Pages optional subset should be selected if the man pages for the DEC/EDI API and CLI calls are required. • The DEC/EDI Server Man Pages optional subset should be selected if the man pages for the DEC/EDI System Administrator Utilities, such as Secondary Archiving, are required. • The DEC/EDI EDI Translation Services optional subset should be selected if any EDI Translation is required for either outgoing or incoming files. • The DEC/EDI Mailbus 400 Gateway optional subset should be selected if the DEC/EDI Server is to provide X.400 or X.435 Communications Services. • The DEC/EDI OFTP Gateway optional subset should be selected if the DEC/EDI Server is to provide OFTP Communications Services. • The DEC/EDI SMTP/MIME Communications Gateway optional subset should be selected if the DEC/EDI Server is to provide SMTP/MIME Communications Services. • The DEC/EDI 3780 (BISYNC) Communications Gateway optional subset should be selected if the DEC/EDI Server is to provide 3780 (BISYNC) Communications Services. • The DEC/EDI Message Updates Man Pages optional subset should be selected if the man pages for the DEC/EDI Message Updates Service are required. • The DEC/EDI Message Updates EDIFACT IMPDEF files optional subset should be selected if the 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 DEC/EDI Message Updates ODETTE IMPDEF files optional subset should be selected if the DEC/EDI Server requires that new ODETTE tables need to be installed on the system or to replace existing tables already on the system. • The DEC/EDI Message Updates X12 files optional subset should be selected if the 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 DEC/EDI Message Updates TDCC files optional subset should be selected if the 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 DEC/EDI Message Updates TRADACOMS files optional subset should be selected if the DEC/EDI Server requires that new TRADACOMS tables need to be installed on the system or to replace existing tables already on the system. Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your 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 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 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. DEC/EDI supports a number of license types, depending on which DEC/EDI component subsets you wish to use. The individual License PAK names, and what they control are shown on the following table. Table 5-2 DEC/EDI Component Licensing Subset (DEC/EDI ...) Client Server EDI Translation Mailbus400 Gateway OFTP Gateway SMTP/MIME Communications Gateway 3780 (BISYNC) Communications Gateway Functionality Post, Fetch, Track via API or CLI This includes bypass trans- lation Import/Export Gateway. Run- time Mapper, Application to- Application Routing Convert to EDI Format, Build EDI Transmissions, Split EDI Transmissions, Translate from EDI Format X.400 (84) P0 and P2, X.400 (88) P0 and P2, X.435 OFTP send and receive SMTP send and receive 3780 send and receive LMF_PAK_Name EDI- APP-SERV or EDI X400 PACKAGE or EDI OFTP PACKAGE No license required EDI-TRANSLATION- SERV or EDI-X400- PACK- AGE or EDI-OFTP-PACK- AGE EDI EDI-X400-SERV or X400-PACKAGE EDI-OFTP-SERV or EDI OFTP- PACKAGE EDI-SMTP LICENSE or EDI-SMTP-PACKAGE license EDI-BISYNC- LICENSE or EDI-BISYNC-PACKAGE license Important In addition, you must install the EDI-COMCEN license on the Server. This permits the DEC/EDI CommandCenter to manage the Server node. If you are installing pre-requisite or optional software along with DEC/EDI, review the PAK status and install the PAKs for them before you install DEC/EDI. Registering Licenses on DIGITAL UNIX To register a license under the DIGITAL 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. Installation Pre-requisites This section discusses requirements for installing DEC/EDI. Login Privileges You must have superuser privileges to install the DEC/EDI software and to register the license PAK(s). Hardware Requirements To run the DEC/EDI Application Client, DEC/EDI Server or DEC/EDI Message Update Service you need a DIGITAL machine running the DIGITAL UNIX Operating System. Please refer to the 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 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 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. Checking Software Requirements The software requirements for DEC/EDI are shown below. Table 5-3 DEC/EDI Software Requirements Subset (DEC/EDI ...) Base Client Client Man Pages Server Server Man Pages Translation Services Mailbus 400 Gateway OFTP Gateway SMTP/MIME Communica- tions Gateway 3780 (BISYNC) Communi- cations Gateway Message Updates Base Message Updates Man Pages Message Updates EDI- FACT IMPDEF files Message Updates ODETTE IMPDEF files Message Updates X12 IMPDEF files Message Updates TDCC IMPDEF files Message Updates TRADA- COMS IMPDEF files Software DIGITAL UNIX TCP/IP ObjectBroker DEC/EDI Base DIGITAL UNIX Documen- tation Subset DEC/EDI Base Informix-OnLine runtime Informix-ESQL/C runtime Oracle Rdb Oracle SQL Services Oracle7 Oracle SQL*NET V2 DIGITAL UNIX Documen- tation Subset DEC/EDI Server DEC/EDI Server Mailbus 400 Base DEC/EDI Server DEC/EDI Server DEC/EDI DEC X.25 Base DEC/EDI Server DIGITAL UNIX Documen- tation Subset DEC/EDI Message Updates Base DEC/EDI Message Updates Base DEC/EDI Message Updates Base DEC/EDI Message Updates Base DEC/EDI Message Updates Base Install? Mandatory Mandatory (included with O/S) Optional Mandatory Optional Mandatory Mandatory if using Informix OnLine Mandatory if using Informix OnLine Mandatory if using Oracle Rdb Mandatory if using Oracle Rdb Mandatory if using Oracle7 Mandatory if using Oracle7 Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Database Requirement The Server requires a database to hold its definitions, one of the following database types must be installed: • Informix On-Line • Oracle Rdb • Oracle7 See the DEC/EDI Software Product Description (SPD) for more information on software requirements such as version numbers. Run Time Libraries The following DIGITAL UNIX Run Time Libraries must be installed. These are provided with the DIGITAL UNIX operating system software distribution on CD-ROM: Subset Name DPORTL5nn DFARTL3nn Description DEC Pascal for DIGITAL UNIX Alpha Runtime Support DEC Fortran for DIGITAL UNIX Alpha Runtime Support For example, to determine whether the subset is installed, use the following command: # setld -i | grep DFARTL DFARTL361 installed DEC Fortran for DIGITAL UNIX Alpha Runtime Support 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 ObjectBroker Installation Applicable only if ObjectBroker is installed To check that ObjectBroker is installed, log in as the superuser (root), and enter the following command: # setld -i | grep OBBBASE This produces an output with a mark against each version of the ObjectBroker Base System currently installed. Checking Client/Server Communication with ObjectBroker Applicable only if ObjectBroker is installed If the DEC/EDI Application Client and DEC/EDI Server are on different systems, the network between them should be tested as follows: 1. On one node, invoke the ObjectBroker Network Tester as the Server by entering the following command: # obbntst -s This will return a Server Connection Identifier which should be noted. 2. On the other node, invoke the ObjectBroker Network Tester as the client by entering the following command but adding the name of the server the client is to connect to and the Connection Identifier from the previous step: # obbntst -c [Server Connection Identifier] -n [Server Name] The server's Network Tester should return a Successful Test message. Checking DIGITAL UNIX Documentation Subset is Installed To check DIGITAL UNIX Documentation Subset is installed, log in as the superuser (root), and enter the following command: # setld -i | grep OSFDCMT This produces an output, with a mark against each version of the DIGITAL UNIX Documentation Subset currently installed. Checking that Oracle7 is Installed Before you can check completely that all Oracle7 components have been installed, you need to set some environment variables specific to Oracle7. Ensure that the Listener Services have been started from the Oracle account using the following command: # lsnrctl start Setting Oracle7 Environment Variables To set Oracle7 environment variables: 1. Check the /etc/passwd file to make sure that an Oracle7 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 Oracle7 and its components are installed: 1. Run the Oracle7 Installer This utility produces a listing of components and respective versions. 2. Check for individual Oracle7 components by using specific commands. In checking an installation by this method, you need to know what components should be installed. Running the Oracle7 Installer The Oracle7 Installer is located on the Oracle CD-ROM disk. Run the utility to give you a listing (with respective locations) of Oracle7 files installed on your system. This may take a few minutes. Checking for Individual Oracle7 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. Checking for the Server Manager and DBMS From the Oracle account, and with the environment variables set as described in Setting Oracle7 Environment Variables on page 5-17, enter the following command: # svrmgrl This returns an output similar to the following: Server Manager: Release 2.0.3 Production Copyright (c) Oracle Corporation 1994. All rights reserved. Oracle7 Server Release 7.1.4.1.1 Production Release 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 Oracle7 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 3.1.3.5.1 Production on Sat Oct 26 12:08:24 1996 Copyright (c) Oracle Corporation 1979, 1994. 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 Drivers version numbers. Checking Informix-OnLine is Installed To check that Informix-OnLine is installed on DIGITAL UNIX log in as the superuser (root), and enter the following commands: # setenv INFORMIXDIR # setenv PATH ${PATH}:${INFORMIXDIR}/bin # onstat -V This produces an output indicating the version of InformixOnLine and its serial number. Note that Informix-OnLine does not need to be started prior to starting DEC/EDI or running any of the DEC/EDI utilities such as decedi_config. Checking Informix-ESQL/C is Installed To check that Informix-ESQL/C is installed on DIGITAL UNIX log in as the superuser (root), and enter the following commands: # setenv INFORMIXDIR # setenv PATH ${PATH}:${INFORMIXDIR}/bin # esql -V This produces an output indicating the version of InformixESQL and its serial number. Note that Informix-ESQL/C does not need to be started prior to starting DEC/EDI or running any of the DEC/EDI utilities such as decedi_config. Checking Oracle Rdb is Installed To check that Oracle Rdb is installed on DIGITAL UNIX log in as the superuser (root), and enter the following command: # setld -i | grep RDBSRV This produces an output with a mark against each version of the Oracle Rdb currently installed. To check that Oracle Rdb is running, enter the following command: # rmu rmu> show system DEC Rdb V6.1-0 on node edisrv.edi.dec.com 16-MAY-1995 13:36:23.42 monitor log filename is "/usr/lib/dbs/rdb/v61/adm/rdmmon61.log" database /usr/users/rdbdb/decedi_db.rdb/rdb_system.rdb 9 active database users rmu> exit # Checking Oracle SQL Services is Installed To check that Oracle SQL Services is installed on DIGITAL UNIX log in as the superuser (root), and enter the following command: # setld -i | grep RDBSQL This produces an output with a mark against each version of the Oracle SQL Services subset currently installed. Checking Oracle SQL Services is Running To check that Oracle SQL Services is running, enter the following commands: # sqs_manage SQS manage> connect server sqs_default user `dbsmgr' using `password'; SQS manage> show server; The message detailing the server shows whether it is running or not. Type exit to return to the command prompt. Checking Mailbus 400 is Installed To check that Mailbus 400 is installed on DIGITAL UNIX log in as the superuser (root), and enter the following command: # setld -i | grep MTAABASE This produces an output with a mark against each version of the Mailbus 400 Base subset currently installed. Checking DEC X.25 is Installed To check that DEC X.25 is installed on DIGITAL UNIX log in as the superuser (root), and enter the following command: # setld -i | grep XXAACC This produces an output with a mark against each version of the DEC X.25 subset currently installed. Checking the DEC/EDI account When installing the DEC/EDI Server subset, some files will be assigned the ownership of decedi. This means that a decedi needs to be set up prior to installing the DEC/EDI Server subset. To check that the decedi account has been set up, log in as the superuser (root), and enter the following command: # grep decedi /etc/passwd If the decedi account exists, then this will produce a line containing the account details. If no decedi account exists, no output will be generated. Adding a DEC/EDI Account To add a decedi account, enter the following command: # adduser This will take you through a series of questions and then sets up the decedi account. Disk Space Requirements The Table below lists the disk space requirements for loading each of the DEC/EDI software subsets. The figures shown in these tables are peak requirements. After installation, slightly less disk space is required. Table 5-4 Disk Space Requirements DEC/EDI Subset DEC/EDI Base DEC/EDI Client DEC/EDI Client Man Pages DEC/EDI Server DEC/EDI Server Man Pages DEC/EDI Translation Services DEC/EDI Mailbus 400 Gateway DEC/EDI OFTP Gateway DEC/EDI SMTP Gateway DEC/EDI BISYNC (3780) Gateway DEC/EDI Message Updates Base DEC/EDI Message Updates Man Pages DEC/EDI Message Updates TDCC files DEC/EDI Message Updates X12 files DEC/EDI Message Updates TRADACOMS files DEC/EDI Message Updates EDIFACT IMPDEF files DEC/EDI Message Updates ODETTE_IMPDEF_files Space needed (Kb) 2,000 2,500 150 75,000 50 6,000 1,500 1,200 500 50 1,200 300 8,000 21,000 500 7,000 200 Compare the space required for subsets with the free space currently on the disks where DEC/EDI files will reside. Determining Disk Space To determine the amount of disk space available on your system, enter the following command: # df -k /usr This will produce an output similar to the example below: Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/re0g 1580378 970579 451761 68% /usr Note that this display shows that there are 451,761 KiloBytes available. Deleting DEC/EDI from Your System If you already have a DEC/EDI subset installed on your system, and want to replace it with another version of that subset, you must delete the original subset first. For instance, if you are upgrading from one version of DEC/EDI to another. Note that deleting the subset does not cause any user data to be lost, so on deleting a subset, and then installing a new subset no data will be lost. If you already have a version of DEC/EDI from your system, and wish to re- install it, or replace it with a newer version, then you must delete each DEC/EDI subset that you previously installed. To delete subsets: 1. Log in as superuser (login name, root). 2. Make sure you are at the root directory (/) by entering the following command: # cd / 3. Enter the following setld command (you may need to use the Bourne shell sh to run setld): # setld -i | grep DEDI This will return a list of subsets with a mark against installed items as shown in the following example: DEDICLT311 installed DEC/EDI DIGITAL UNIX Client DEDICLTMAN311 installed DEC/EDI DIGITAL UNIX Client Man Pages 4. Look for the word "installed" in the listing produced, and then delete the installed subsets. For example: # setld -d DEDICLT311 DEDICLTMAN311 Backing Up Your System Disk DIGITAL recommends that you back up your file systems before installing any software. For information about backing up your file systems, see the DIGITAL UNIX system documentation. Installing DEC/EDI This section describes how to install DEC/EDI. Before starting your installation, perform the pre-installation tasks listed in the previous section. The beginning of this section describes how to en