DIGITAL Software Product Description __________________________________________________________________ PRODUCT NAME: DEC/EDI[TM] for OpenVMS VAX and Alpha, SPD 53.14.04 Version 3.2 DESCRIPTION Electronic Data Interchange (EDI) enables users to electronically ex- change structured business documents such as Purchase Orders, Dispatch Advice and Invoices with their Trading Partners using International, National and Industry-specific EDI standards. DEC/EDI offers appli- cation developers all the facilities necessary to EDI-enable Business Applications within an Enterprise. Extensive communication options are also provided to facilitate inter-enterprise communication via EDI VANs or direct with Trading Partners using OSI[R] protocols. DEC/EDI uses a Client/Server architecture to provide EDI services to local and remote Business Applications hosted on multi-vendor plat- forms within an enterprise. DEC/EDI Application Client The DEC/EDI Application Client facilitates the integration of local and remote Business Applications to the DEC/EDI Server, to make them EDI-capable. Either a sockets based protocol or the BEA ObjectBroker[R] protocol can be used to link the locally or remotely installed DEC/EDI Version 3.2 Application Clients to the DEC/EDI Server using the TCP/IP communication protocol. December 1997 AE-Q8WKD-TE DEC/EDI Version 3.2 Application Clients are available today for: o Digital UNIX[R] o OpenVMS[TM] VAX and Alpha o HP-UX[R] o Sun[R] Solaris[R] These DEC/EDI Application Clients can interoperate with a DEC/EDI Server running on Digital UNIX, OpenVMS VAX or OpenVMS Alpha platforms. The interface provided by the DEC/EDI Application Client is file-based and allows for the Business Application to POST and FETCH files to and from Trading Partners via the DEC/EDI Server. The DEC/EDI Application Clients can be invoked via the Command Line Interface (CLI) or the Application Program Interface (API). The CLI can be run from a suitably coded script file (command file) or invoked interactively. The DEC/EDI Application Client also provides the following functions: o Enables local and remote Business Applications to extract document status information via the TRACK Command, from the DEC/EDI Server. o Enable Business Applications to POST and FETCH files to and from other DEC/EDI Application Clients attached to the same DEC/EDI Server. The information exchanged between DEC/EDI Application Clients is mapped from the input format to the recipient format by using File- Bridge MAPs based on an EDI Message definition. o POST and FETCH documents to and from the DEC/EDI Server and by-pass the Mapping or Mapping and Translation functions, for transmission and receipt to and from trading partners via the DEC/EDI Communi- cation Component. 2 DEC/EDI Server The DEC/EDI Server consists of the following components which reside on the same node: o DEC/EDI FileBridge Component o DEC/EDI Translation Component o DEC/EDI Communications Component o DEC/EDI Operational Management Component FileBridge Component FileBridge is a table-driven "MAPPER" with a set of data manipulation operators for selected classes of commonly encountered EDI applica- tion data. This capability is used to convert data from the existing Business Application file format to that required for Translation into the Trading Partner format as well as formatting data received from the trading partner to the file format expected by the Business Ap- plication. The Mapping Process consists of: o Data Specification The customer defines the application file structure, and parameters for mapping between the application file and the EDI standard through a forms-based user interface. FileBridge then generates a conversion table that is used to map data from/to the application file formats. o User Defined Mapping FileBridge allows fields to be moved directly to the destination or to have built-in mathematical/logical/string operations to be performed upon the fields. The user interface guides the user through this pro- cess. The user can define and add code through "hooks" for more com- plex processing. 3 o Data Definition Extracts FileBridge also allows for the extraction of Application file record definitions from Oracle[R] CDD/Repository. The components of FileBridge are: o FileBridge User Interface (UI) The UI consists of a set of menus and forms that allow users to cre- ate, modify, and compile FileBridge tables. o FileBridge Run-time The Run-time process uses the information in a compiled FileBridge ta- ble to map data between the Business Application file and the format required for transmission and receipt to and from trading partners. Translation Component The Translation Component takes data that has come from the Business Application and transforms it into the standard EDI formats required for transmission to the Trading Partner. It also takes incoming EDI data, that has been received from a Trading Partner by the Communi- cations Component, and converts it into the format that is suitable for the Mapper to decode and pass to the Application Client. The Translation Component provides the following features: o Support for multiple versions of messages (transactions) and EDI standards o Supports the transmission of 8-bit national character sets o Compliance checking at Trading Partner level o Trading Partner specific Code Translation o User-selectable control number generation 4 o Test transmissions o Event and Error logging o Supports the EDIFACT CONTRL message to enable acknowledgment of receipt of messages. An editor is provided to enable users to customise the messages de- livered with the product to create new messages for industry specific and Trading Partner specific messages as well as create new messages based on ANSI X12, TDCC, EDIFACT, ODETTE, and TRADACOMS[TM] syntax rules supported by this version of the product. The editor also allows for the creation of new versions of EDI Standard dictionaries. Trading Partner agreement details, including the message formats be- ing used, are recorded in the Trading Partner Profiles. The Transla- tion Component uses the information in the Trading Partner Profiles and the Message Database to perform compliance checking and to check the validity of the transaction. The Translation Component provides support for the following EDI stan- dards: o EDIFACT - Implements ISO 9735 - Supports character set A, lower-case a-z, and 8-bit national char- acter sets. - Supports industry-specific transactions adhering to the EDIFACT ISO 9735 syntax - Supports the EDIFACT CONTRL message to enable acknowledgment of receipt of messages. 5 o ANSI X12 - Automatic generation of Functional Acknowledgments and recon- ciliation of Functional Acknowledgments - Supports industry-specific transactions adhering to the ANSI X12 syntax o TDCC - Supports all modes including UCS/WINS - Automatic generation of Functional Acknowledgments, 997 and 999 and reconciliation of Functional Acknowledgments - Support for the following types of messages is not provided: * Messages which contain two mandatory instances of the same segment, at the same level, when other segments appear be- tween the two instances (for example, Transaction 994 and its use of the K2 segment) * Messages which use EDIFACT enveloping o ODETTE - Support for Version 2.0 of ODETTE o TRADACOMS - Implements the TRADACOMS (October 1989 Update) syntax and mes- sages Communications Component The Communications Component supports a range of communications op- tions including OSI. It enables users to send EDI transmissions ei- ther through EDI VANs or direct to their Trading Partners. 6 The Communications Component provides the following features: o Flexible scheduling using windows and jobs o Priority processing to override the scheduler o User-definable connection and file-based retry limit o Event and Error logging The Communications Component Options provided with DEC/EDI are: o X.400 Communications Component o OFTP Communications Component o Bisynchronous and CCITT X.25 Components for VAN Communications o Import/Export Communications Component A specific Communications Component license need not be purchased to invoke the Import/Export capability. o X.400 Communication - Supports the CCITT X.435 recommendation, EWOS Kernel Functional Profile (June 1992 /TD 22), for the transmission of EDI messages over the CCITT recommendations for X.400, 1988 - Supports both P0 (NIST Special Publication 500-150) and P2 (TE- DIS meeting November 23, 1989) interim recommendations for the transmission of EDI messages over the CCITT recommendations for X.400, 1984 and 1988 - Supports enabling or disabling Trading Partner specific trans- missions - Supports user-configurable Trading Partner specific record lengths 7 - Provides global connectivity by facilitating EDI transmissions either directly between Private Management Domains (PRMDs) or via an Administrative Management Domain (ADMD) Relay Service - Supports X.400 Acknowledgment processing o OFTP Communication - Fully supports OD.G4/86/090 - Supports Special Logic for incoming transmission - Supports enabling or disabling Trading Partner specific trans- mission - Supports user-configurable Trading Partner specific record lengths - Provides Global connectivity by facilitating EDI transmission directly between Trading Partners over CCITT X.25-based Networks - Supports File Restarts - Recognises Compressed Data o Bisynchronous and X.25 VAN Communication - Provides connections to EDI VANs via the use of 2780/3780, us- ing the CLEO 3780plus product and CCITT X.25 Protocols. - Supports connections to the GEIS[TM] EDI*EXPRESS[TM], and BT TYMNET[R] EDI*NET[R] Services via the use of the 2780/3780 communication protocol. - Supports connections to the INS[TM]- TRADANET[TM] Service via the use of X.25 Communications protocol - User-configurable Trading Partner specific record lengths - Provides pre-defined jobs to interact with the EDI VAN Service and avoid any user programming 8 - Sends and receives all transmission files in the same connec- tion o Import/Export Communication - Enables the user to implement other means of communicating with Trading Partners - Outgoing and incoming Trading Partner specific transmission files written to user-defined directory - Allows insertion of header details to transmission files - A specific Communications Component license need not be purchased to invoke this facility Operational Management Component An extensive set of management functions is provided to enable the user to easily install, configure, and manage an operational EDI system. The Management Component is an integral part of the Application Client, FileBridge, Translation and Communication Components and need not be purchased separately. The Management Service commands are invoked using DCL. The appropri- ate form is then displayed on the screen. The Management Service provides the following facilities: o Access Control o Processing Control o Organisational Control o Error logging and exception reporting 9 o Access Control - Controls user access to the DEC/EDI system - Users assigned two types of privileges, Administrator or Super- visor - Tools are provided to enable the Administrator to manage the op- erational state of the DEC/EDI system - The Supervisor is provided with tools to monitor the status of documents in the DEC/EDI system o Processing Control - Provides end-to-end audit trail of message status within the DEC/EDI system, including status information from the EDI VAN Services - Provides history files with detailed information to help locate and correct errors - Provides message and transmission file status - Time stamps each message status o Organisational Control - Provides facilities to monitor the status of the documents in the DEC/EDI system - Provides facilities to archive and retrieve documents which have either been processed successfully or cancelled - Provides facilities to maintain the list of authorised users - Provides facilities to edit and create message format tables - Provides facilities to edit and create Trading Partner profiles - Provides a Configuration Verification Program (CVP) to test the linkages between the DEC/EDI Server and the DEC/EDI Client com- ponents 10 o Error Logging and Exception Reporting - All events and errors are logged and time stamped. - Exception reporting consists of logging errors, display of er- ror message on the Operator Console, and the dispatch of VMS- mail[TM] to the designated EDI System Administrator. DEC/EDI CommandCenter DEC/EDI CommandCenter, a Graphical User Interface (GUI) running under Microsoft[R]Windows[R], Windows 95[R] or Windows NT[TM], is available as an option and provides a set of configuration and monitoring functions to manage an operational DEC/EDI System. Multiple copies of the CommandCenter can be deployed across the enterprise. The CommandCenter includes the Cockpit functionality and a complete set of on-line DEC/EDI User Documentation. The information entered and managed through the CommandCenter is min- imised through the use of features such as cut/copy/paste, extensive defaults and drop down lists, where selections are made from pre- defined set of options. The CommandCenter can be used to maintain more than one DEC/EDI Server system and allows the transfer of elements of configuration informa- tion between Servers. Some of the editing functions, such as the edit- ing of Mapping Tables, may be carried out even when the CommandCen- ter is not connected to the DEC/EDI Server. The CommandCenter facilitates the creation and maintenance of the fol- lowing configuration information: o User access control information - View business data only (read-only) - View and modify business data (reset, resend, cancel batch, archive mapper events) - View and modify data for a restricted set of applications and/or trading partners 11 - View data for mapper events, documents, batches or trans- mission files - Modify DEC/EDI Cockpit views to enable column titles to be specified - Use the CommandCenter applications o Mapping Table Editor - Allows the user to define how the format of data sent or re- ceived by a Business Application maps to the format of data implied by the selected EDI message/transaction. It also facilitates the compilation of the Mapping Tables prior to storage and use on the DEC/EDI Server. DEC/EDI Cockpit DEC/EDI Cockpit, a Graphical User Interface (GUI) running under Mi- crosoft[R] Windows[R], Windows 95[R] or Windows NT[TM] is available as an option. The Cockpit provides the following functionality: - A "system monitor" function providing graphical display of the status of Messages/Transactions. This display can be updated ei- ther manually or at a pre-defined timing interval - An "access control editor" application enabling the DEC/EDI adminis- trator to restrict access to audit data and files that may be viewed by a particular Cockpit user. - Access to the DEC/EDI Audit trails at the Document and Transmis- sion file levels and cross-referencing between Documents and Trans- mission files. - Access to the data contained within the EDI documents. - The ability to customise the display of the DEC/EDI Audit trails by defining "views". - Access to Error logs. 12 - The ability to select documents based on business references that have been assigned through the application client interface or during the document mapping process. - The ability to access Transaction/Message status information from sev- eral DEC/EDI Servers. - The ability to reset, cancel or resend Documents or Transmission Files that are in certain states. DOCUMENTATION The DEC/EDI documentation set consists of: o DEC/EDI Introduction o DEC/EDI Installation o DEC/EDI OpenVMS User Support Manual - Volume 1 o DEC/EDI OpenVMS User Support Manual - Volume 2 o DEC/EDI Application Development STANDARDS INDUSTRY PRACTICE CONFORMANCE The DEC/EDI product conforms to the following formal industry stan- dards: o ISO 9735 (EDIFACT) o ANSI X12.5 and X12.6 o CCITT Recommendation X.435 (EWOS Kernel Functional Profile, June 1992 /TD 22 ) 13 The DEC/EDI product conforms to the following industry Practice: o TRADACOMS (UN/TDI) o TDCC o UCS/WINS o ODETTE o EDIFICE o EANCOM o CEFIC o ODETTE File Transfer Protocol (OFTP) - OD.G4/86/090 o X.400 P2 (TEDIS meeting Nov. 23, 1989) and P0 (NIST Special Pub- lication 500-150) for CCITT X.400 1984 INSTALLATION Digital recommends that a customer's first purchase of this software product include Digital Installation Services. These services provide for installation of the software product by an experienced Digital Soft- ware Specialist. For subsequent purchases of this product only experienced customers should attempt installation. Digital recommends that all other cus- tomers purchase Digital's Installation Services. Customer Responsibilities Before installation of the software, the customer must: o Previously have installed all requisite software identified in the Software Requirements section above, and hardware including ter- minals. 14 o Make available for a reasonable period of time, as mutually agreed by Digital and the customer, all hardware, communication facili- ties, and terminals that are to be used during installation. o For verification of installation and connectivity in a multi-node network, designate and provide access to the DEC/EDI Client and Server hosts that has previously been installed by Digital. Delays caused by any failure to meet the responsibilities will be charged at the then prevailing rate for time and materials. HARDWARE REQUIREMENTS Processors Supported Any VAX or Alpha system capable of supporting a minimum of 64Mb of memory (128Mb recommended), 2 Disk Drives (4 recommended) and the hardware controllers for the Communication Option (X.25, X.400, OFTP) chosen by the customer. Disk Space Requirements ___________________________________________________________________ Table 1: Disk Space Required for Installation ___________________________________________________________________ DEC/EDI VAX System 81,000 blocks[1] (42 Mbytes) DEC/EDI Alpha System 133,000 blocks[1] (69 Mbytes) DEC/EDI VAX Application 7,000 blocks[1] Client (4 Mbytes) DEC/EDI Alpha Application 9,000 blocks[1] Client (5 Mbytes) ___________________________________________________________________ [1] Block Cluster Size = 1 ___________________________________________________________________ 15 ___________________________________________________________________ Table 2: Disk space required for use (permanent) ___________________________________________________________________ DEC/EDI VAX System 122,000 blocks[1] (63 Mbytes) DEC/EDI Alpha System 165,000 blocks[1] (85 Mbytes) DEC/EDI VAX Application 3,000 blocks[1] Client (2 Mbytes) DEC/EDI Alpha Application 2,000 blocks[1] Client (2 Mbytes) ___________________________________________________________________ [1] Block Cluster Size = 1 ___________________________________________________________________ These counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. Additional disk space is required depending on the number of Mapping tables, performance needs, message size and software options. Memory Requirements The minimum memory supported is 64Mb. However, the use of this soft- ware in conjunction with increased memory and multiple disks improves performance. The memory size suggested for most typical hardware con- figurations is at least 128Mb (especially when the X.25 and/or X.400 products are installed on the same processor). OPTIONAL HARDWARE Any devices supported by the prerequisite/optional software. Bisynchronous Communications for connecting to EDI VANs: 16 The CLEO 3780Plus product is required for use with the DEC/EDI Bi-synch communications capability on VAX and Alpha OpenVMS. Contact the following outlets to purchase CLEO 3780Plus: Contact the Digital EDI Practice Center in Dallas, Texas, for com- plete price and delivery information. Tel: 972-702-4518 e-mail: edi_consulting@sca.mts.dec.com UK: Interface Systems International Telephone: +44 (0)1753 811888 The following Synchronous modems are recommended for use with the CLEO 3870Plus product: o RACAL-datacom 9600 baud modem, V.32 (AT Compatible) o MULTItech Multimodem V.32 (AT Compatible) Contact your EDI Service Provider for advice on the protocol supported in your country. SOFTWARE REQUIREMENTS DEC/EDI Application Client and DEC/EDI Server deployment on the same node: o OpenVMS Operating System Versions V6.1, V6.2, V7.0, V7.1 (SPD 25.01.xx) o DEC TCP/IP Services for OpenVMS, Versions V3.3 (for VAX), V4.1 (for Alpha) Required for the use of the TCP/IP protocol o BEA ObjectBroker for OpenVMS Versions V2.6, V2.7 BEA ObjectBroker is now optional for TCP/IP users, provided all DEC/EDI Application Clients and GUI Applications are at Version 3.2 or higher. BEA ObjectBroker is required for use with remote Application Clients at versions prior to DEC/EDI Version 3.2. 17 o DECforms (Run-time) for OpenVMS VAX V2.1A, V2.2 (SPD 29.90.xx) o Oracle Rdb Versions V6.0 ECO1, V6.1, V7.0 o Oracle SQL Services Versions V6.0 ECO1, V6.1, V7.0 OPTIONAL For remote deployment of DEC/EDI Application Client: o Remote deployment of DEC/EDI Application Client on OpenVMS Alpha System: - OpenVMS Operating System Versions V6.1, V6.2, V7.0, V7.1 (SPD 25.01.xx) - DEC/EDI Application Client for OpenVMS V2.1A through V3.2 (SPD 53.14.xx) and its pre-requisite software. [1] - BEA ObjectBroker for OpenVMS Versions V2.6, V2.7 [2] BEA ObjectBroker is optional for TCP/IP users provided all DEC/EDI Application Clients and GUI Applications are at Version 3.2 or higher. BEA ObjectBroker is required for use with remote Application Clients at versions prior to Version 3.2. - DECnet Plus for OpenVMS Alpha Versions V6.2, V7.0, V7.1 or DEC TCP/IP Services for OpenVMS, Versions V3.3 (for VAX), V4.1 (for Alpha) ____________________ [1] Digital strongly recommends that you upgrade any remote DEC/EDI Application Clients on OpenVMS Alpha. OpenVMS VAX, and Digital UNIX to Version 3.2 [2] BEA ObjectBroker V2.6 or higher is required for DEC/EDI Version 2.1D on OpenVMS Alpha and OpenVMS VAX and for DEC/EDI Version 3.1A on Digital UNIX. BEA ObjectBroker is optional for DEC/EDI V3.2 on OpenVMS and Digital UNIX. 18 o Remote deployment of DEC/EDI Application Client on OpenVMS VAX sys- tem: - OpenVMS Operating System Versions V6.1, V6.2, V7.0, V7.1 (SPD 25.01.xx) - DEC/EDI Application Client for OpenVMS V2.1A through V3.2 (SPD 53.14.xx) and its pre-requisite software. [1] - BEA ObjectBroker for OpenVMS Versions V2.6, V2.7 [2] BEA ObjectBroker is optional for TCP/IP users provided all DEC/EDI Application Clients and GUI Applications are at Version 3.2 or higher. BEA ObjectBroker is required for use with remote Application Clients at versions prior to Version 3.2. - DECnet Plus for OpenVMS VAX Versions V6.2, V7.0, V7.1 or - DEC TCP/IP Services for OpenVMS, Versions V3.3 (for VAX), V4.1 (for Alpha) o Remote deployment of DEC/EDI Application Client on Digital UNIX Alpha system: - DEC/EDI Application Client for Digital UNIX V3.1 to V3.2 (SPD 53.50.xx) and its pre-requisite software. [1] [2] o Remote deployment of DEC/EDI Application Client on HP-UX system: - DEC/EDI Application Client for HP-UX V2.1A through V3.2 (SPD 62.92.xx) and its pre-requisite software. ____________________ [1] Digital strongly recommends that you upgrade any remote DEC/EDI Application Clients on OpenVMS Alpha. OpenVMS VAX, and Digital UNIX to Version 3.2 [2] BEA ObjectBroker V2.6 or higher is required for DEC/EDI Version 2.1D on OpenVMS Alpha and OpenVMS VAX and for DEC/EDI Version 3.1A on Digital UNIX. BEA ObjectBroker is optional for DEC/EDI V3.2 on OpenVMS and Digital UNIX. 19 o Remote deployment of DEC/EDI Application Client on Sun Solaris system: - DEC/EDI Application Client for Sun Solaris V3.1 through V3.2 (SPD 61.38.xx) and its pre-requisite software. For the use of DEC/EDI OFTP Communication: o For an OpenVMS Alpha System: - DEC X.25 for OpenVMS Alpha V1.1, V1.1b - DECnet Plus for OpenVMS Alpha Versions V6.1, V6.2, V7.0, V7.1 o For an OpenVMS VAX System: - DECnet Plus for Open VMS VAX Versions V6.1, V6.2, V7.0, V7.1 and the X.25 Option If the physical connection to the X.25 network is not provided on the same node, then the DEC/EDI server node requires: o For an OpenVMS Alpha System: - DEC X.25 Client for OpenVMS Alpha V1.1, V1.2 o For an OpenVMS VAX System: - DECnet Plus for OpenVMS VAX Versions V6.1, V6.2, V7.0, V7.1 For the use of DEC/EDI Bi-Synch Communication: - The CLEO 3780Plus product is required for use with the DEC/EDI Bi-synch communications capability on VAX and Alpha OpenVMS. Contact the following outlets to purchase CLEO 3780Plus: Contact the Digital EDI Practice Center in Dallas, Texas, for com- plete price and delivery information. Tel: 972-702-4518 e-mail: edi_consulting@sca.mts.dec.com UK: Interface Systems International Telephone: +44 (0)1753 811888 20 - For TRADANET VAN: DECnet Plus for OpenVMS Alpha Versions V6.1, V6.2, V7.0, V7.1 and a remote node providing X.25 Connector Services or DECnet Plus for OpenVMS VAX Versions V6.1, V6.2, V7.0, V7.1 and the X.25 Option For the use of DEC/EDI X.400 Communications, the X.400 Message Transfer Agent (MTA) may be located either on the same node as the DEC/EDI server or on a remote node: If the MTA is located on the same node as the DEC/EDI server, the following software is required: o For an OpenVMS Alpha System: - DECnet Plus for OpenVMS Alpha Versions V6.2, V7.0, V7.1 - MAILbus 400 Message Transfer Agent for OpenVMS Alpha V1.4, V2.0 - DEC X.500 Directory Service (Base Component) for OpenVMS Alpha V2.0A, V3.1 o For an OpenVMS VAX System: - DECnet Plus for OpenVMS VAX Versions V6.2, V7.0, V7.1 - MAILbus 400 Message Transfer Agent for OpenVMS VAX V1.4, V2.0 - DEC X.500 Directory Service (Base Component) for OpenVMS VAX V2.0A, V3.1 If the MTA is located on a remote node, the following software must be installed on the same node as the DEC/EDI Server: 21 o For an OpenVMS Alpha System: - DECnet Plus for OpenVMS Alpha Versions V6.1, V6.2, V7.0, V7.1 - MAILbus 400 Message Transfer Agent (Base Component) for OpenVMS Alpha V1.4, V2.0 o For an OpenVMS VAX System: - DECnet Plus for OpenVMS VAX Versions V6.1, V6.2, V7.0, V7.1 - MAILbus 400 Message Transfer Agent (Base Component) for OpenVMS VAX V1.4, V2.0 The following software is required on the remote node on which the MTA is installed: o On a remote Digital UNIX node: - DECnet Plus for Digital UNIX Versions V3.2, V4.0A - MAILbus 400 Message Transfer Agent for Digital UNIX V1.4, V2.0 - DEC X.500 Directory Service (Base Component) for Digital UNIX V2.0A, V3.1 o On a remote OpenVMS Alpha node: - DECnet Plus for OpenVMS Alpha Versions V6.1, V6.2, V7.0, V7.1 - MAILbus 400 Message Transfer Agent for OpenVMS Alpha V1.4, V2.0 - DEC X.500 Directory Service (Base Component) for OpenVMS Alpha V2.0A, V3.1 22 o On a remote OpenVMS VAX node: - DECnet Plus for OpenVMS VAX Versions V6.1, V6.2, V7.0, V7.1 - MAILbus 400 Message Transfer Agent for OpenVMS VAX V1.4, V2.0 - DEC X.500 Directory Service (Base Component) for OpenVMS VAX V2.0A, V3.1 For the use of DEC/EDI CommandCenter V3.2: o On a PC running Microsoft Windows or Microsoft Windows for Work- groups: - MS-DOS[R] V6.0 or later - Microsoft Windows V3.1 or Microsoft Windows for Workgroups V3.11 - Microsoft Win32s - BEA ObjectBroker for Microsoft Windows, V2.6, V2.7, V2.711 BEA ObjectBroker is now optional for connection to DEC/EDI Version 3.2 or higher servers supporting TCP/IP. - ODBC and SQL Components: - Oracle ODBC Driver for Rdb, Version 2.0.20, 2.10.11 (16-bit driver) - One of the following communications protocol interfaces: - PATHWORKS for DOS and Windows V5.0, V5.1, V6.0 (SPD 55.07.xx) or - Novell[R] LAN Workplace for DOS and Windows V4, V5 or - Microsoft Windows for Workgroups TCP/IP 23 - Adobe Acrobat Reader Version 3.0 for Windows 3.1 as supplied with the CommandCenter - Microsoft Internet Explorer Version 3.01b for Windows 3.1 as supplied with the CommandCenter o On a PC running Microsoft Windows 95: - Windows 95 V1.0, V1.1 - BEA ObjectBroker for Microsoft Windows, V2.6, V2.7, V2.711 BEA ObjectBroker is now optional for connection to DEC/EDI Version 3.2 or higher servers supporting TCP/IP. - ODBC and SQL Components: - Oracle ODBC Driver for Rdb, Versions 2.0.20, 2.10.11 (32-bit driver) - One of the following communications protocol interfaces: - PATHWORKS for Windows 95 V1.0, V1.0A or - Windows 95 TCP/IP (included in Windows 95) or - Windows 95 Dialup networking TCP/IP (PPP) - Adobe Acrobat Reader Version 3.0 for Windows 95/NT as supplied with the CommandCenter - Microsoft Internet Explorer Version 3.01b for Windows 95/NT as supplied with the CommandCenter 24 o On a PC running Microsoft Windows NT: - Windows NT Workstation Versions V3.5.1, V4.0 - BEA ObjectBroker for Microsoft Windows NT Versions V2.6, V2.7, V2.711 BEA ObjectBroker is now optional for connection to DEC/EDI Version 3.2 or higher servers supporting TCP/IP. - ODBC and SQL Components: - Oracle ODBC Driver for Rdb, Versions 2.0.20, 2.10.11 (32-bit driver) - One of the following communications protocol interfaces: - PATHWORKS for Windows NT, V4.1B or - Windows NT TCP/IP (included with Windows NT) or - Windows NT Dialup networking TCP/IP (PPP) - Adobe Acrobat Reader Version 3.0 for Windows 95/NT as supplied with the CommandCenter - Microsoft Internet Explorer Version 3.01b for Windows 95/NT as supplied with the CommandCenter For the use of DEC/EDI Cockpit V3.2: o On a PC running Microsoft Windows or Microsoft Windows for Work- groups: - MS-DOS[R] V6.0 or later - Microsoft Windows V3.1 or Microsoft Windows for Workgroups V3.11 25 - BEA ObjectBroker for Microsoft Windows Versions V2.6, V2.7, V2.711 BEA ObjectBroker is now optional for connection to DEC/EDI Version 3.2 or higher servers supporting TCP/IP. - ODBC and SQL Components: - Oracle ODBC Driver for Rdb, Versions 2.0.20, 2.10.11 (16-bit driver) - One of the following communications protocol interfaces: - PATHWORKS for DOS and Windows V5.0, V5.1, V6.0 (SPD 55.07.xx) or - Novell[R] LAN Workplace for DOS and Windows V4, V5 or - Microsoft Windows for Workgroups TCP/IP o On a PC running Microsoft Windows 95: - Windows 95 V1.0, V1.1 - BEA ObjectBroker for Microsoft Windows Versions V2.6, V2.7, V2.711 BEA ObjectBroker is now optional for connection to DEC/EDI Version 3.2 or higher servers supporting TCP/IP. - ODBC and SQL Components: - Oracle ODBC Driver for Rdb, Versions 2.0.20, 2.10.11 (32-bit driver) 26 - One of the following communications protocol interfaces: - PATHWORKS for Windows 95 V1.0, V1.0A or - Windows 95 TCP/IP (included with OS) or - Windows 95 Dialup networking TCP/IP (PPP) o On a PC running Microsoft Windows NT: - Windows NT Workstation Versions 3.51, V4.0 - BEA ObjectBroker for Microsoft Windows NT Versions V2.6, V2.7, V2.711 BEA ObjectBroker is now optional for connection to DEC/EDI Version 3.2 or higher servers supporting TCP/IP. - ODBC and SQL Components: - Oracle ODBC Driver for Rdb, Versions 2.0.20, 2.10.11 (32-bit driver) - One of the following communications protocol interfaces: - PATHWORKS for Windows NT, V4.1B or - Windows NT TCP/IP (included with OS) or - Windows NT Dialup networking TCP/IP (PPP) For OPTIONAL use with DEC/EDI FileBridge: Oracle CDD/Repository for OpenVMS Versions V6.1,V7.0 27 SOFTWARE LICENSING This software is furnished under the licensing provisions of Digital Equipment Corporation's Standard Terms and Conditions. For more in- formation about Digital's licensing terms and policies, contact your local Digital office. Licenses for the DEC/EDI components can be purchased either individ- ually or as a package. The following three packaged license options are available: o DEC/EDI Bi-Synch Package (includes X.25 based connection to INS- TRADANET) o DEC/EDI OFTP Package o DEC/EDI X.400 Package In addition to the specific Communications Component, each package li- cense option (UPI= YM7 or YM8 or YM9 or 2QY or 2QZ or 2R0 ) also includes the Application Client, FileBridge Run-Time and the Translation Component. All the constituent components of a packaged license option must be installed on the same processor. License Management Facility Support (LMF) This layered product supports the OpenVMS License Management Facil- ity. License units for this product are allocated on an Unlimited System Use basis only. For more information on the License Management Facility, refer to the OpenVMS Operating System Software Product Description (SPD 25.01.xx) or the License Management Facility manual of the OpenVMS Operating Sys- tem documentation set. For more information about Digital's licensing terms and policies, con- tact your local Digital office. 28 CLUSTER ENVIRONMENT This layered product is supported when installed on any single node of valid and licensed VMScluster configurations. If the Application connecting to the DEC/EDI Application Client is in- stalled on a separate node, then an additional DEC/EDI Application Client needs to be installed on the same node as the Application. The HARDWARE REQUIREMENTS sections of this product's Software Prod- uct Description detail any special hardware required by this product. VMSCluster configurations are fully described in the VMScluster Soft- ware Product Description (29.78.xx) and include CI, Ethernet, and Mixed Interconnect configurations. OPTIONAL SOFTWARE The following product versions are recommended for use with DEC/EDI for OpenVMS VAX and Alpha V3.2: o DEC/EDI Cockpit for MS-Windows, Version 3.2 or higher (QB-2YNAA- SA) o DEC/EDI CommandCenter for MS-Windows, Version 3.2 or higher o DEC/EDI Application Client for OpenVMS VAX and Alpha, Version 3.2 or higher (SPD 53.14.xx) o DEC/EDI Application Client for Digital UNIX , Version 3.2 (SPD 53.50.xx) o DEC/EDI Application Client for HP-UX, Version 3.2 or higher (SPD 61.92.xx) o DEC/EDI Application Client for Sun Solaris, Version 3.2 (SPD 61.38.xx) 29 Certain versions of the following products depend upon a specific ver- sion of the Operating System and DECnet Plus. Please refer to the SPD of the product in question to determine which version you need: o MAILbus 400 Message Transfer Agent for Digital UNIX o MAILbus 400 Message Transfer Agent for OpenVMS Alpha o MAILbus 400 Message Transfer Agent for OpenVMS VAX GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. A DEC/EDI system using only the FileBridge Run-Time option may require existing MAPs to re-compiled on a system which includes the FileBridge Development option, with new releases of DEC/EDI. DISTRIBUTION MEDIA This product is available as part of the OpenVMS Consolidated Soft- ware Distribution on CD-ROM. The software documentation for this product is also available as part of the OpenVMS Online Documentation Library on CD-ROM. ORDERING INFORMATION Software Licenses DEC/EDI for OpenVMS VAX Application Client License: QL-YM2A*-AA DEC/EDI Application Client DEC/EDI for OpenVMS Alpha Application Client License: QL-2QTA*-AA DEC/EDI Application Client 30 DEC/EDI Server License: DEC/EDI for OpenVMS VAX QL-23WA*-AA DEC/EDI FileBridge Development Component QL-YM3A*-AA DEC/EDI Translation Component QL-YM4A*-AA DEC/EDI X.400 Communication QL-YM5A*-AA DEC/EDI OFTP Communication QL-YM6A*-AA DEC/EDI Bi-Synch Communication QL-YM7A*-AA DEC/EDI Bi-Synch Package QL-YM8A*-AA DEC/EDI OFTP Package QL-YM9A*-AA DEC/EDI X.400 Package DEC/EDI for OpenVMS Alpha QL-2QJA*-AA DEC/EDI FileBridge Development Component QL-2QUA*-AA DEC/EDI Translation Component QL-2QVA*-AA DEC/EDI X.400 Communication QL-2QWA*-AA DEC/EDI OFTP Communication QL-2QXA*-AA DEC/EDI Bi-Synch Communication QL-2QYA*-AA DEC/EDI Bi-Synch Package QL-2QZA*-AA DEC/EDI OFTP Package QL-2R0A*-AA DEC/EDI X.400 Package 31 Software Media: QA-YM1AA-H* DEC/EDI for OpenVMS VAX QA-2QSAA-H* DEC/EDI for OpenVMS Alpha Software Documentation: QA-YM1AA-GZ DEC/EDI for OpenVMS VAX QA-2QSAA-GZ DEC/EDI for OpenVMS Alpha Software Product Services DEC/EDI for OpenVMS VAX: QT-YM2A*-** DEC/EDI Application Client QT-23WA*-** DEC/EDI FileBridge Development Component QT-YM3A*-** DEC/EDI Translation Component QT-YM4A*-** DEC/EDI X.400 Communications Component QT-YM5A*-** DEC/EDI OFTP Communication QT-YM6A*-** DEC/EDI Bi-Synch Communication QT-YM7A*-** DEC/EDI Bi-Synch Package QT-YM8A*-** DEC/EDI OFTP Package QT-YM9A*-** DEC/EDI X.400 Package DEC/EDI for OpenVMS Alpha: QT-2QTA*-** DEC/EDI Application Client QT-2QJA*-** DEC/EDI FileBridge Development Component QT-2QUA*-** DEC/EDI Translation Component 32 QT-2QVA*-** DEC/EDI X.400 Communications Component QT-2QWA*-** DEC/EDI OFTP Communication QT-2QXA*-** DEC/EDI Bi-Synch Communication QT-2QYA*-** DEC/EDI Bi-Synch Package QT-2QZA*-** DEC/EDI OFTP Package QT-2R0A*-** DEC/EDI X.400 Package DEC/EDI CommandCenter for MS-Windows: QL-4LNAW-AA License QL-4LNAA-H8 Media (CD-ROM Only) DEC/EDI Cockpit for MS-Windows: QB-2YNAA-SA Media and License package Each package license option (VAX: QL-YM7A*-**, QL-YM8A*-** and QL-YM9A*-**; Alpha: QL-2QYA*-**, QL-2QZA*-** and QL-2R0A*-**), also includes the following: o DEC/EDI Application Client o DEC/EDI FileBridge Run-Time o DEC/EDI Translation Component o The specified Communication component for installation on a sin- gle node. * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. The above information is valid at time of release. Please contact your local Digital office for the most up-to-date information. 33 SOFTWARE PRODUCT SERVICES The DEC/EDI Message Updates containing Transactions, Segments, and Data Element Dictionaries for versions of ANSI X12, UCS/WINS, and EDIFACT messages will be made available on a regular basis, to those customers who purchase Layered Product Service for the DEC/EDI. A variety of other service options are also available from Digital. For more information, contact your local Digital office. SOFTWARE WARRANTY The procedures documented in the DEC/EDI documentation must be car- ried out on a regular basis to ensure that DEC/EDI is properly man- aged in a production environment. Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the Software Warranty Addendum to this SPD. The above information is valid at time of release. Please contact your local Digital office for the most up-to-date information. Digital[TM] Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descrip- tions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the de- scriptions. Possession, use, or copying of the software described in this publi- cation is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Acrobat[R] Reader copyright 1987-1996 Adobe Systems Incorporated. [R] Adobe and Acrobat are trademarks of Adobe Systems Incorporated. [R] AT&T Easylink is a registered trademark of AT&T Global Messaging Services Limited. 34 [R] TYMNET and EDI*NET are registered trademarks of British Telecommunications Public Liability Company. [R] CLEO and 3780plus are registered trademarks of CLEO Communications Inc. [R] OSI is a registered trademarks of CA Management, Inc. [R] HP and HP-UX are registered trademarks of Hewlett-Packard Company. [R] IBM and IN are registered trademarks of International Business Machines Corporation. [R] Sun and Solaris are registered trademarks of Sun Microsystems, Inc. [R] Microsoft, MS-DOS, Windows and Windows 95 are registered trademarks of Microsoft Corporation. [R] BEA ObjectBroker is a registered trademark of BEA Systems Inc. [R] Oracle is a registered trademark of Oracle Corporation. [R] UNIX is a registered trademark licensed exclusively by X/Open Company Ltd. [TM] Windows NT is a trademark of Microsoft Corporation. [TM] GEIS and EDI*EXPRESS are trademarks of General Electric Company of USA. [TM] INS and TRADANET are trademarks of International Network Services Limited. [TM] TRADACOMS is a trademark of the Article Numbering Association. [TM] Oracle Rdb, Oracle SQL/Services, Oracle Rdb run-time option and Oracle CDD/Repository are trademarks of Oracle Corporation. [TM] Digital, the DIGITAL logo, CI, DEC, DEC/EDI, DECforms, DECnet, DECwindows, MAILbus, MicroVAX, TK, VAX, VAXcluster, VAXft, VAXserver, VAXstation, VMSmail, and OpenVMS are trademarks of Digital Equipment Corporation. © Digital Equipment Corporation 1990, 1997. 35