COMPAQ Software Product Description PRODUCT NAME: Compaq DEC/EDI for Compaq Tru64TM UNIX(, Version 3.2B SPD 53.50.06 DESCRIPTION Electronic Data Interchange (EDI) enables users to electronically exchange 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 application 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( protocols. DEC/EDI uses a Client/Server architecture to provide EDI services to local and remote Business Applications hosted on multi-vendor platforms 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. A TCP/IP sockets based protocol is used to link the locally or remotely installed DEC/EDI Version 3.2 or Version 3.2B Application Clients to the DEC/EDI Server. DEC/EDI Version 3.2B Application Clients are available today for: * Compaq Tru64( UNIX( * Compaq OpenVMS( Alpha(tm) * Compaq OpenVMS VAX( * HP-UX( * Sun( Solaris( These DEC/EDI Application Clients can interoperate with a DEC/EDI Server running on Compaq Tru64 UNIX, Compaq OpenVMS VAX or Compaq 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: * Document Status Information: Enables local and remote Business Applications to extract document status information via the TRACK Command, from either a local or remote DEC/EDI Server. * 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 mapping tables based on an EDI Message definition. * 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 Communication Component. DEC/EDI Server The DEC/EDI Server consists of the following components that reside on the same node: * DEC/EDI Mapper Component * DEC/EDI Translation Component * DEC/EDI Communications Component * DEC/EDI Operational Management Component Mapper Component This is a table-driven file mapping function with a set of data manipulation operators for selected classes of commonly encountered EDI application 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 Application. The Mapping Services operate using rules which the user specifies in a Mapping Table. The Mapping Table comprises of a detailed description of the format of a particular application file, the definition of the corresponding EDI document, and rules for mapping each element of the data between the two. The Mapping Tables are created interactively using the Mapping Table Editor function provided by the DEC/EDI CommandCenter GUI. Lookup tables can be shared between Mapping Tables. In addition to the simple data mapping services (for example "create destination field y using source field x"), DEC/EDI also provides many other powerful mapping features such as: * Data Manipulation Individual mapping statements can be constructed using a rich mapping language which allows complex expressions to be created of the form "destination_data_field = mapping_expression". A mapping expression can consist of a combination of elements of source data using predefined functions, simple mathematical expressions and constant or computed values. * DataType Conversion The ability to process sections of application file data of many different types (for example: textual, integer numeric, real numeric and date/time). * Handling of Variants The Mapping Services support conditional mapping. This function allows the user to use the same map to communicate the same EDI document type (for example Purchase Orders) with many trading partners even if the format of the EDI document agreed with each partner is different. This difference can also be used when the EDI Standard is different (for example, the sending/receipt of Purchase Orders in EDIFACT and ODETTE standard to/from different trading partners). * Hook Routines The ability to customize individual Mapping Tables by coupling user-defined processing functions at any stage in the mapping process. This can be used, for example, to perform some data manipulation not directly supported within the mapper or to fetch data from an external database. * Business Data Views Support for business data views to allow the user to specify which items of data can be audited and retrieved. * Audit Trail Access Global variables can be used to access enveloping and translation audit log fields from within the mapping process. Translation Services The Translation Services perform the conversion to or translation from data formatted to conform with published EDI standards. In processing outbound data the Translation Services "convert" mapped application data to the EDI standard form. In processing inbound data, the Translation Services "translate" data from the EDI standard format to that required for mapping to the format expected by the Business Application. The Translation Services Component provide the following features: * Support for multiple versions of messages (transactions) and EDI standards * Supports the pass-through transmission of 8-bit national character sets * Compliance checking at Trading Partner level * User-selectable control number generation * Test transmissions * Event and Error logging Users can customize the messages/transactions delivered 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. New versions of EDI Standard dictionaries can also be created. Trading Partner agreement details, including the message formats being used, are recorded in the Trading Partner Profiles. The Translation Services use the information in the Trading Partner Profiles and the Message/Transaction Database to perform compliance checking and to check the validity of the transaction. The Translation Services provides support for the following EDI standards: * EDIFACT * Implements ISO 9735 Version-2 * Supports character set A, lower-case a-z, and 8-bit national character sets. * Supports industry-specific transactions adhering to the EDIFACT ISO 9735 syntax * Supports the EDIFACT CONTRL message to enable acknowledgment of receipt of messages. * ANSI X12 * Automatic generation of Functional Acknowledgments and reconciliation of Functional Acknowledgments * Supports industry-specific transactions adhering to the ANSI X12 syntax * 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 between the two instances (for example, Transaction 994 and its use of the K2 segment) * Messages which use EDIFACT enveloping * ODETTE * Support for Version 2.0 of ODETTE * TRADACOMS * Implements the TRADACOMS (1993 Update) syntax, 1989 and 1993 messages Communications Services The Communications Services support the physical transfer of EDI data between DEC/EDI and the Trading Partners. A range of Gateways are provided to send/receive EDI transmissions either through EDI VANs or direct to/from trading partners. Each Gateway ensures that the EDI transmissions are delivered to the trading partners and the status information is automatically appended to the Document audit trail within DEC/EDI. The Communication Services provide the following features: * Event and Error logging The Communication Services Gateways provided by DEC/EDI are: * X.400/X.435 (Pedi) Communication Gateway * OFTP Communication Gateway * Bisynchronous Gateway for VAN Communications * Internet SMTP/MIME Communication Gateway * Import/Export Communication Gateway * X.400 Gateway * 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 (TEDIS 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 transmissions. * Supports user-configurable Trading Partner specific record lengths. * 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. * OFTP Gateway * Fully supports mandatory components of OD.G4/86/090. * Supports Special Logic for incoming transmission. * Supports enabling or disabling Trading Partner specific transmission. * 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. * Connects to EDI VANs which support the OFTP Protocol. These include GEIS( EDI*Express(, INS(-TRADANET(, BT( EDI*NET(, IBM IN (Europe) and AT&T Easylink EDI(. * Supports File Restarts. * Recognizes Compressed Data. * Bisynchronous * Provides connections to EDI VANs via the use of 2780/3780, using the CLEO( 3780Plus( product. * Supports connections to the GEIS( EDI*EXPRESS( and MCI( EDI*NET( Services via the use of the 2780/3780 communication protocol. * User-configurable Trading Partner specific record lengths. * Sends and receives all transmission files in the same connection. * Internet SMTP/MIME Gateway * Sends and receives EDI messages via Internet SMTP/MIME protocol. * Supports RFC 1767. * Uses Compaq Tru64 UNIX Sendmail capability. * Hooks provided to support pre- and post- processing for functions such as security. * Import/Export Gateway * 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. * Provides Hooks to enable Pre-Import/Post-Export processing of transmission files. * A specific Communications Component license need not be purchased to invoke this facility. Operational Services The Operational Services provide the following functions * Access Control * Processing Control * Error logging and exception reporting * Auditing and Archiving * Access Control * Controls user access to the DEC/EDI system by enabling the DEC/EDI Cockpit and CommandCenter to specify whether users may: * 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 * View data for mapper events, documents, batches or transmission files * Modify DEC/EDI Cockpit views to enable column titles to be specified * Use the CommandCenter applications * Processing Control * Provides end-to-end audit trail of message/transaction 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 * Error Logging and Exception Reporting * All events and errors are logged and time stamped. * Exception reporting consists of logging errors, display of error message on the Operator Console, and the dispatch of e-mail to the designated EDI System Administrator. * Auditing and Archiving The DEC/EDI server creates audit trail entries for each document it processes. The parameters that are audited include Document-id (or Transmission file-id), status, date & time stamp, Document type, Application-id, Trading Partner name and EDI enveloping information. In addition to this, DEC/EDI also maintains, copies of the data itself in each of its different formats. All this information can be viewed from the Cockpit. Successful and cancelled documents are automatically transferred to an archive area. Documents in this archive area may be re-sent if necessary. The user is provided with the ability to archive the information in the archive area to mass storage media. A retrieval procedure is also provided. DEC/EDI CommandCenter DEC/EDI CommandCenter, a Graphical User Interface (GUI) running under Microsoft( Windows 95(, Windows 98(, Windows NT(tm) or Windows 2000(tm), provides an extensive 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 minimized 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 information between Servers. Some of the editing functions, such as the editing of Mapping Tables, may be carried out even when the CommandCenter is not connected to the DEC/EDI Server. The CommandCenter facilitates the creation and maintenance of the following configuration information: * Management Services Editor * Allows the user to register the attributes of the Business Applications authorized to connect to the remote or local DEC/EDI Application Clients. It also facilitates the registration of Services used on the DEC/EDI Server. * Allows the user to maintain the intervals at which EDI Transmission Files are built. * EDI Table Editor * Allows the user to edit EDI messages (transaction sets) supplied with DEC/EDI to conform to their trading agreements. It also allows the user to create new messages, based on the EDIFACT, ODETTE, TDCC, ANSI X12 and TRADACOMS syntax. The editing function is carried out in the CommandCenter and then stored in the DEC/EDI Server. * Trading Partner Editor * Allows the user to define details of the trading partners who can send or receive data, the communications links to be used, the agreement that governs which EDI documents are to be exchanged, and what enveloping (addressing) information is to be used. The resultant information is held in the Trading Partner Tables in the DEC/EDI Server. * Mapping Table Editor * Allows the user to define how the format of data sent or received 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. * Communications Editor * Allows the user to define which communications options are being used (i.e,. OFTP, X.400 etc.) and the parameters of individual communications links, either direct to trading partners or indirectly through third-party EDI Value Added Networks (VANs). DEC/EDI Cockpit DEC/EDI Cockpit, a Graphical User Interface (GUI) running under Microsoft( Windows 95(, Windows 98(, Windows NT(tm) or Windows 2000(tm) is available as an option. The Cockpit enables the user to observe the processing of EDI data within a DEC/EDI Server, and to perform some operational functions. The main features provided by the Cockpit include: * A "system monitor" function providing graphical display of the status of Messages/Transactions. This display can be updated either manually or at a predefined timing interval * An "access control editor" application enabling the DEC/EDI administrator 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 Transmission file levels and cross-referencing between Documents and Transmission files. * Access to the data contained within the EDI documents. * The ability to customize the display of the DEC/EDI Audit trails by defining "views". * Access to Error logs. * 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 several 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: * DEC/EDI Introduction * DEC/EDI Installation * DEC/EDI Application Development * DEC/EDI Tru64 UNIX User Support Manual All the above documents are also available on-line with the CommandCenter component in Adobe( Acrobat( Portable Document File (PDF) format. The free Adobe Acrobat Reader for Microsoft Windows is distributed with the CommandCenter. STANDARDS AND INDUSTRY PRACTICE CONFORMANCE The DEC/EDI product conforms to the following formal industry standards: * ISO 9735 (EDIFACT), version-2 * ANSI X12.5 and X12.6 * CCITT Recommendation X.435 (EWOS Kernel Functional Profile, June 1992 /TD 22 ) * RFC 1767; Transmission of EDI documents over SMTP/MIME The DEC/EDI product conforms to the following industry practice: * TRADACOMS(UN/TDI) * TDCC * UCS/WINS * ODETTE * EDIFICE * EANCOM * CEFIC * ODETTE File Transfer Protocol (OFTP) - OD.G4/86/090 * X.400 P2 (TEDIS meeting Nov. 23, 1989) and P0 (NIST Special Publication 500-150) for CCITT X.400 1984 INSTALLATION Compaq recommends that a customer's first purchase of this software product include Compaq Global Services Installation Services. These services provide for installation of the software product by an experienced Compaq Global Services Software Specialist. For subsequent purchases of this product only experienced customers should attempt installation. Compaq recommends that all other customers purchase Compaq Global Services' Installation Services. Customer Responsibilities Before installation of the software, the customer must: * Previously have installed all requisite software identified in the Software Requirements section below, and hardware, including terminals. * Make available for a reasonable period of time, as mutually agreed by Compaq and the customer, all hardware, communication facilities, and terminals that are to be used during installation. * For verification of installation and connectivity in a multi-node network, designate and provide access to the DEC/EDI Client and Server hosts that have previously been installed by Compaq. 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 Compaq Alpha system capable of supporting a minimum of 64Mb of memory (128Mb recommended), 2 Disk Drives (4 recommended), CD-ROM reader and the hardware controllers for the Communication Option (X.25, X.400, OFTP, SMTP/MIME, Bi-Synch) chosen by the customer. and an IBM-compatible PC (Intel 486 or higher processor) with a minimum of 32Mb of Memory (64Mb recommended), SVGA graphics support and a CD-ROM reader, networked to the Compaq Tru64 UNIX system running the DEC/EDI Server software. DISK SPACE REQUIREMENTS Table 1 Disk Space Required for Installation ___________________________________________ DEC/EDI Application Client 3,500 Kbytes DEC/EDI Server 120,000 Kbytes DEC/EDI CommandCenter 25,000 Kbytes DEC/EDI Cockpit 8,000 Kbytes ___________________________________________ Table 2 Disk space required for use (permanent) ___________________________________________ DEC/EDI Application Client 3,500 Kbytes DEC/EDI Server 120,000 Kbytes DEC/EDI CommandCenter 25,000 Kbytes DEC/EDI Cockpit 8,000 Kbytes ___________________________________________ 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 Server memory supported is 64Mb. However, the use of this software in conjunction with increased memory and multiple disks improves performance. The memory size suggested for most typical hardware configurations 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. For Bisynchronous Communications for connecting to EDI VANs: * The CLEO 3780Plus product is required for use with the DEC/EDI Bi-synch communications capability on Tru64 UNIX. Contact the following outlets to purchase CLEO 3780Plus: Contact Compaq Global Services eBusiness Competency Resource Center in Dallas, Texas, USA for complete price and delivery information. Tel: +1-972-702-4267. A list of recommended modems can be supplied upon request from the above contact. Contact your EDI Service Provider for advice on the protocol supported in your country. SOFTWARE REQUIREMENTS For DEC/EDI Application Client and DEC/EDI Server deployment on the same node: * Compaq Tru64 UNIX Operating System V4.0D through V5.0A (SPD 41.61.xx) * TCP/IP (as supplied with the Compaq Tru64 UNIX Operating System) * Database: * For Informix INFORMIX( OnLine(tm) V7.1, V7.13 and INFORMIX ESQL/C(tm) V7.1, V7.13 or * For Oracle 7 Oracle 7 Server (RDBMS), Version 7.3.4 Oracle 7 SQL*NET V2, Versions 2.1.6 Oracle 7 TCP/IP Protocol Adapter V2 or higher Oracle 7 Server Manager, Version 2.0.3.0.0 or higher * DEC/EDI CommandCenter V3.2B and its pre-requisites. For the use of DEC/EDI CommandCenter or Cockpit V3.2B: * On a PC running Microsoft Windows 95: * Windows 95 V1.1 * ODBC and SQL Components: * For Informix Online Informix CLI Version V2.5 * For Oracle 7 Oracle 7 ODBC driver (32 bit), Version 1.13.5.0.0a or higher Oracle SQL*NET Client Version 2.2.2.1.0a or higher Oracle TCP/IP Protocol Adapter, Version 2.2.2.1.0 or higher * One of the following communications protocol interfaces: * 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. * On a PC running Microsoft Windows 98: * Windows 98 or Windows 98 Second Edition * ODBC and SQL Components: * For Informix Online Informix CLI Version V2.5 * For Oracle 7 Oracle 7 ODBC driver (32 bit), Version 1.13.5.0.0a or higher Oracle SQL*NET Client Version 2.2.2.1.0a or higher Oracle TCP/IP Protocol Adapter, Version 2.2.2.1.0 or higher * One of the following communications protocol interfaces: * Windows 98 TCP/IP (included in Windows 98) or * Windows 98 Dialup networking TCP/IP (PPP) * Adobe Acrobat Reader Version 3.0 for Windows 95/NT. * On a PC running Microsoft Windows NT: * Windows NT Workstation Versions V4.0 with Service Pack 4 or later. * ODBC and SQL Components: * For Informix Online Informix CLI Version V2.5 * For Oracle 7 Oracle 7 ODBC driver (32-bit driver) Version 1.13.5.0.0a or higher Oracle SQL*NET Client Version 2.2.2.1.0a or higher Oracle TCP/IP Protocol Adapter Version 2.2.2.1.0 or higher * One of the following communications protocol interfaces: * 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 * On a PC running Microsoft Windows 2000: * Windows 2000 Professional * ODBC and SQL Components: * For Informix Online Informix CLI Version V2.5 * For Oracle 7 Oracle 7 ODBC driver (32-bit driver) Version 1.13.5.0.0a or higher Oracle SQL*NET Client Version 2.2.2.1.0a or higher Oracle TCP/IP Protocol Adapter Version 2.2.2.1.0 or higher * One of the following communications protocol interfaces: * Windows 2000 TCP/IP (included with Windows 2000) or * Windows 2000 Dialup networking TCP/IP (PPP) * Adobe Acrobat Reader Windows 2000 OPTIONAL For remote deployment of DEC/EDI Application Client: * Remote deployment of DEC/EDI Application Client on OpenVMS Alpha System: * DEC/EDI Application Client for OpenVMS Alpha V3.2 through V3.2B (SPD 53.14.xx) and its pre-requisite software. 1 * Remote deployment of DEC/EDI Application Client on OpenVMS VAX system: * DEC/EDI Application Client for OpenVMS VAX V3.2 through V3.2B (SPD 31.70.xx) and its pre-requisite software. 1 * Remote deployment of DEC/EDI Application Client on Tru64 UNIX system (with/without additional DEC/EDI Application Clients): * Compaq Tru64 UNIX Operating System, V4.0D to V5.0A (SPD 41.61.xx) * DEC/EDI Application Client for Tru64 UNIX V3.2 to V3.2B (SPD 53.50.xx) 1 * Installation of TCP/IP (included with Compaq Tru64 UNIX Operating System) on all DEC/EDI Application Client Platforms running TCP/IP and the DEC/EDI Server. * Remote deployment of DEC/EDI Application Client on HP-UX systems (with/without additional DEC/EDI Application Clients): * DEC/EDI Application Client for HP-UX V3.2 through V3.2B (SPD 62.92.xx) and its prerequisite software. ____________________ 1 Compaq strongly recommends that you upgrade any remote DEC/EDI Application Clients on OpenVMS Alpha, OpenVMS VAX, and Tru64 UNIX to Version 3.2B * Remote deployment of DEC/EDI Application Client on Sun Solaris system (with/without additional DEC/EDI Application Clients): * DEC/EDI Application Client for Sun Solaris V3.2 through V3.2B (SPD 61.38.xx) and its pre-requisite software. For the use of DEC/EDI OFTP Communication: * Wide Area Networking support (formerly known as X.25) for Tru64 UNIX systems Version 2.0A (SPD 42.47.xx) If the physical connection to the X.25 network is not provided on the same node, then the DEC/EDI Server node requires * DECnet Plus for Tru64 UNIX Version 4.0A (SPD 41.92.xx) 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: * DECnet Plus for Tru64 UNIX Version 4.0A * MAILbus 400 Message Transfer Agent for Compaq Tru64 UNIX V2.0 * DEC X.500 Directory Services (Base Component) for Compaq Tru64 UNIX V3.1 (SPD 40.77.xx) If the MTA is located on a remote node, the following software must be installed on the same node as the DEC/EDI Server: * DECnet Plus for Compaq Tru64 UNIX Version 4.0A * MAILbus 400 Message Transfer Agent for Compaq Tru64 UNIX (Base Component) V2.0 The following software is required on the remote node on which the MTA is installed: On a remote Tru64 UNIX node: * DECnet Plus for Compaq Tru64 UNIX Version 4.0A * MAILbus 400 Message Transfer Agent for Compaq Tru64 UNIX V2.0 * DEC X.500 Directory Service (Base Component) for Compaq Tru64 UNIX V3.1 On a remote OpenVMS Alpha node: * DECnet Plus for OpenVMS Alpha Version V7.1 * MAILbus 400 Message Transfer Agent for OpenVMS Alpha V2.0 * DEC X.500 Directory Service (Base Component) for OpenVMS Alpha V3.1 On a remote OpenVMS VAX node: * DECnet Plus for OpenVMS VAX Version 7.1 * MAILbus 400 Message Transfer Agent for OpenVMS VAX V2.0 * DEC X.500 Directory Service (Base Component) for OpenVMS VAX V3.1 For the use of DEC/EDI Internet SMTP/MIME Communication: * Sendmail function on Tru64 UNIX * Wide Area Network connection to an Internet Service Provider or an EDI VAN supplier supporting RFC 1767. SOFTWARE LICENSING This software is furnished under the licensing provisions of Compaq Computer Corporation's Standard Terms and Conditions. For more information about Compaq's licensing terms and policies, contact your local Compaq office. Licenses for the DEC/EDI components can be purchased either individually or as a package. The following packaged license options are available: * DEC/EDI Bi-Synch Package * DEC/EDI OFTP Package * DEC/EDI X.400 Package * DEC/EDI Internet SMTP/MIME Package In addition to the specific DEC/EDI Communications Component, each package license option also includes the Application Client, Mapping Services, Translation Services and Import/Export Gateway Component. It does not include the communication product (X.25, X.400 and X.500). 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 Tru64 UNIX License Management Facility. License units for this product are allocated on an Unlimited System Use basis only for the DEC/EDI Server. License units for the Cockpit and CommandCenter are on a per user basis. License units for Informix OnLine , ESQL, I*NET and INTERSOLV ODBC are sold on a per user basis where a User equates to every copy of Cockpit and/or CommandCenter in use. However, Informix specify a minimum number of licenses for each processor type. For more information on the License Management Facility, refer to the Compaq Tru64 UNIX Alpha Software Product Description (SPD 41.61.xx) or the License Management Facility manual of the Compaq Tru64 UNIX Operating System documentation set. For more information about Compaq's licensing terms and policies, contact your local Compaq office. OPTIONAL SOFTWARE The following product versions are recommended for use with DEC/EDI for Tru64 UNIX V3.2. * DEC/EDI Application Client for Tru64 UNIX, Version 3.2B * DEC/EDI Application Client for HP-UX, Version 3.2B or higher (SPD 61.92.xx) * DEC/EDI Application Client for Sun Solaris Version 3.2B (SPD 61.38.xx) * DEC/EDI Application Client for OpenVMS VAX and Alpha, Version 3.2B or higher (SPD 53.14.xx) Certain versions of the following products depend upon a specific version of the Operating System and DECnet Plus. Please refer to the SPD of the product in question to determine which version you need: * MAILbus 400 Message Transfer Agent for Tru64 UNIX * MAILbus 400 Message Transfer Agent for OpenVMS Alpha * 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. DISTRIBUTION MEDIA The DEC/EDI Application Clients and Server Components are available as part of the Compaq Tru64 UNIX Consolidated Software Distribution on CD-ROM. ORDERING INFORMATION Software Licenses DEC/EDI Application Client License: QL-2Y2A*-AA DEC/EDI Application Client DEC/EDI Server License: QL-2Y4A*-AA DEC/EDI X.400 Gateway QL-2Y5A*-AA DEC/EDI OFTP Gateway QL-2Y6A*-AA DEC/EDI Bi-Synch Gateway QL-5HFA*-AA DEC/EDI Internet SMTP/MIME Gateway QL-2Y7A*-AA DEC/EDI Bi-Synch Package QL-2Y8A*-AA DEC/EDI OFTP Package QL-2Y9A*-AA DEC/EDI X.400 Package QL-5HGA*-AA DEC/EDI Internet SMTP/MIME Package Software Media: QA-2Y1AA-H8 Software Documentation: QA-2Y1AA-GZ Software Product Services: QT-2Y2A*-** DEC/EDI Application Client QT-2Y4A*-** DEC/EDI X.400 Gateway QT-2Y5A*-** DEC/EDI OFTP Gateway QT-2Y6A*-** DEC/EDI Bi-Synch Gateway QT-5HFA*-** DEC/EDI Internet SMTP/MIME Gateway QT-2Y7A*-** DEC/EDI Bi-Synch Package QT-2Y8A*-** DEC/EDI OFTP Package QT-2Y9A*-** DEC/EDI X.400 Package QT-4LNA*-** DEC/EDI CommandCenter QT-2YNA*-** DEC/EDI Cockpit QT-5HGA*-** DEC/EDI Internet SMTP/MIME Package DEC/EDI CommandCenter V3.2: QL-4LNAW-AA License QL-4LNAA-H8 Media (CD-ROM Only) DEC/EDI Cockpit 3.2: QB-2YNAA-SA Media and License package Each package license option also includes the following: * DEC/EDI Application Client * DEC/EDI Server * The specified DEC/EDI Communication Gateway for installation on a single node. It does not include the Communications product (X.25, X.400, X.500). * Denotes variant fields. For additional information on available licenses, services, and media, refer to the appropriate price book. The above information is valid at time of release. Please contact your local Compaq office for the most up-to-date information. SOFTWARE PRODUCT SERVICES The DEC/EDI Message Updates containing Messages (Transaction Sets), Segments, and Data Element Dictionaries for versions of ANSI X12, TDCC (UCS/WINS), TRADACOMS, ODETTE and EDIFACT messages will be made available on a regular basis, to those customers who purchase Layered Product Service for DEC/EDI. A variety of other service options are also available from Compaq. For more information, contact your local Compaq office. SOFTWARE WARRANTY The procedures documented in the DEC/EDI documentation must be carried out on a regular basis to ensure that DEC/EDI is properly managed in a production environment. Warranty for this software product is provided by Compaq with the purchase 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 Compaq office for the most up-to-date information. Compaq Computer Corporation makes no representa-tions that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the descriptions. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. ( Acrobat( Reader copyright 1987-1996 Adobe Systems Incorporated. (Adobe and Acrobat are trademarks of Adobe Systems Incorporated. ( AT&T Easylink EDI is a registered trademark of AT&T Global Messaging Services Limited. ( BT and EDI*NET are registered trademarks of British Telecommunications Public Liability Company. ( CLEO and 3780plus are registered trademarks of Interface Systems, Inc. ( OSI is a registered trademark of CA Management, Inc. ( HP and HP-UX are registered trademarks of Hewlett-Packard Company. ( IBM and IN are registered trademarks of International Business Machines Corporation. ( Sun and Solaris are registered trademarks of Sun Microsystems, Inc. ( Microsoft, Windows 95 and Windows 98 are registered trademarks of Microsoft Corporation. ( Oracle is a registered trademark of Oracle Corporation. ( Informix is a registered trademark of Informix Corporation. ( UNIX is a registered trademark licensed exclusively by X/Open Company Ltd. ( INTERSOLV is a registered trademark of INTERSOLV Inc. ( DataDirect is a trademark of INTERSOLV Inc. ( Windows NT and Windows 2000 are trademarks of Microsoft Corporation. ( GEIS and EDI*EXPRESS are trademarks of General Electric Company of USA. ( INS and TRADANET are trademarks of International Network Services Limited. ( TRADACOMS is a trademark of the Article Numbering Association. ( Oracle 7, Oracle Rdb, Oracle SQL/Services, Oracle Rdb run-time option and Oracle CDD/Repository are trademarks of Oracle Corporation. ( Informix OnLine, ESQL, I*Net and NewEra are trademarks of Informix Corporation. ( Compaq, AlphaServer, DECnet, VAX, and the Compaq logo, registered U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P. (c) Compaq Computer Corporation 2000. July 2000 AE- Q8WVF-TE DEC/EDITM for Compaq Tru64TM UNIX(, Version 3.2B SPD 53.50.06 2