Software Product Description SPD: 53.14.06 _____________________________________________________________________ PRODUCT NAME: DEC/EDI for OpenVMS Alpha, Version 5.0 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 Client/Server architecture to provide EDI services to local and remote Business Applications hosted on multi-vendor platforms within an enterprise. DEC/EDI Version 5.0 represents the latest release, and provides increased performance, high availability and scalability over the earlier versions. Enhanced performance is brought about by removing identified bottlenecks present in the earlier versions, and streamlined database access resulting in improvements in throughput. DEC/EDI V5.0 comes with clustering support on OVMS V7.2-1. DEC/EDI processes communicate cluster-wide with each other using the Intra Cluster Communication (ICC) calls. Access to common resources shared by these processes is managed using the Distributed Lock Manager (DLM) calls. DEC/EDI can now be selectively started on each node in the cluster. When DEC/EDI shutdown is performed on a node "A" the other instance of DEC/EDI running on node "B" automatically takes over the load from node "A". This ensures high availability of the system for maintenance and up-gradation activities. New features available in DEC/EDI V5.0 is: o OFTP/IP gateway support The OFTP/IP gateway uses TCP/IP protocol to send and receive EDI documents between trading partners. This can be used by defining the OFTP/IP gateway as DECEDI$OFTPIP logical. However, OFTP/IP and OFTP/X.25 cannot co-exist. Please refer to technical documentation for details. DEC/EDI V5.0 provides for the support of traditional EDI standards as well as industry standard XML document definitions. The XML support available in DEC/EDI V5.0 is as follows: o Ability to create user-defined XML tag names. The default being the element/segment description removing the spaces & special characters and converting the first letter of each word to uppercase alphabet. o Generation of XML schemas based on EDIFACT/ODETTE, X12/TDCC, TRADACOMS, trading partner specific and private document definition. o Ability to post and fetch the XML documents directly from DEC/EDI using the BYPASS facility A complete list of add-on services now available for DEC/EDI is under the section "Related Services" in this SPD. For the latest information on DEC/EDI and related services, please visit the website at www.decedi.com, or email us at srinivasrao.surampudi@hp.com. 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. Sockets based protocol is used to link the locally or remotely installed DEC/EDI Version 5.0 Application Clients to the DEC/EDI Server using the TCP/IP communication protocol. DEC/EDI Version 5.0 Application Clients are available today for: o Tru64(TM) UNIX(R) o OpenVMS(TM) Alpha(TM) o HP-UX(R) o Sun(R) Solaris(R) o Red Hat Linux(R) o Windows NT(R) These DEC/EDI Application Clients can interoperate with a DEC/EDI Server running on Tru64 UNIX, 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) and 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 mapper 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 Communication Component. DEC/EDI Server The DEC/EDI Server consists of the following components which reside on the same node: o DEC/EDI Mapper Component o DEC/EDI Translation Component o DEC/EDI Communications Component o DEC/EDI Operational Management Component Mapper Component Mapper component is a table-driven "MAPPER" with a set of data manipulation operators for selected classes of commonly encountered EDI application data. The Mapping services provide the ability to transform data formats (in either direction) between the data format as supported by each Business Application and the EDI format exchanged with Trading Partners. 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. The Data Transformation mapper then generates a conversion table that is used to map at a from/to the application file formats. o User Defined Mapping Mapper 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 process. The user can define and add code through "hooks" for more complex processing. o Data Definition Extracts Mapper also allows for the extraction of Application file record definitions from Oracle CDD/Repository. The components of the Data Transformation Mapper are: o Mapper User Interface (UI) The UI consists of a set of menus and forms that allow users to create, modify,and compile Mapping tables. o Mapper Run-time The Run-time process uses the information in a compiled Mapping table 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 Communications 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 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 customize the messages 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 (UCS), 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 being used, are recorded in the Trading Partner Profiles. The Translation 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 standards: o EDIFACT - Implements ISO 9735 - Supports character set A and B, 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. o ANSI X12 - Automatic generation of Functional Acknowledgments and reconciliation of Functional Acknowledgments - Supports industry-specific transactions adhering to the ANSI X12 syntax o TDCC (UCS) - 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 o ODETTE - Support for Version 2.0 of ODETTE o TRADACOMS - Implements the TRADACOMS (October 1989 Update) syntax and messages o XML Schema - Implements the Schema and XML formats as per W3C March 2001 specifications Communications Component The Communications Component supports a range of communications options including OSI. It enables users to send EDI transmissions either through EDI VANs or direct to their Trading partners. 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 (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 o FTP Communication - Fully supports 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 - Supports File Restarts - Recognizes Compressed Data o Bisynchronous and X.25 VAN Communication - Provides connections to EDI VANs via the use of 2780/3780, using 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 - Sends and receives all transmission files in the same connection 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, Mapper, Translation and Communication Components and need not be purchased separately. The Management Service commands are invoked using DCL. The appropriate form is then displayed on the screen. The Management Service provides the following facilities: o Access Control o Processing Control o Organizational Control o Error logging and exception reporting o Access Control - Controls user access to the DEC/EDI system - Users assigned two types of privileges, Administrator or Supervisor - Tools are provided to enable the Administrator to manage the operational 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 and locate and correct errors - Provides message and transmission file status - Time stamps each message status o Organizational 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 authorized 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 components o 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 VMSmail (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 NT(TM) or Windows 2000(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 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: 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 - View data for mapper events, documents, batches transmission files - Modify DEC/EDI Cockpit views to enable column or titles to be specified - Use the CommandCenter applications o 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. DEC/EDI Cockpit DEC/EDI Cockpit, a Graphical User Interface (GUI) running under Microsoft(R) Windows(R),Windows NT(TM), Windows 2000(TM), or Windows XP is available as an option. The Cockpit provides the following functionality: - A "system monitor" function that provides graphical display of the status of Messages/Transactions. This display can be updated either manually or at a Pre-defined 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: 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 standards: o ISO 9735 (EDIFACT) o ANSI X12.5 and X12.6 o CCITT Recommendation X.435 (EWOS Kernel Functional Profile, June 1992/TD 22) The DEC/EDI product conforms to the following industry Practice: o TRADACOMS (UN/TDI) o TDCC (UCS) 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 Publication 500-150) for CCITT X.400 1984 INSTALLATION HP GlobalSoft recommends that a customer's first purchase of this software product include services for installation of the software by an experienced HP Software Specialist. 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 terminals. o Make available for a reasonable period of time, as mutually agreed by HP GlobalSoft and the customer, all hardware, communication facilities, 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 host that has previously been installed by HP GlobalSoft. 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 HP Alpha system capable of supporting a minimum of 256 MB of memory, 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. Disk Space Requirements Table 1 Disk Space Required for Installation ___________________________________________ DEC/EDI Alpha System 140,000 blocks[1] (70 Mbytes) DEC/EDI Alpha Application 9,000 blocks[1] Client (4.5 Mbytes) ___________________________________________ [1]Block Cluster Size = 1 ___________________________________________ Table 2 Disk space required for use (permanent) ___________________________________________ DEC/EDI Alpha System 120,000 blocks[1] (60 Mbytes) DEC/EDI Alpha Application 1,000 blocks[1] Client (0.5 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 users 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 256 MB. However, the use of this software in conjunction with increased memory and multiple disks improves performance. OPTIONAL HARDWARE Any devices supported by the prerequisite/optional software. Bisynchronous Communications for connecting to EDI VANs: The CLEO 3780Plus product is required for use with the DEC/EDI Bi-synch communications capability on Alpha OpenVMS. SOFTWARE REQUIREMENTS DEC/EDI Application Client and DEC/EDI Server deployment on the same node: o OpenVMS Operating System Versions V7.2-1, V7.2, V7.3 o DEC TCP/IP Services for OpenVMS, Versions V5.0A for Alpha Required for the use of the TCP/IP protocol: o DECforms (Run-time) for OpenVMS V3.0 o Oracle Rdb Versions V7.0.3 to 7.0.6 o Oracle SQL Services Versions 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 V7.2-1, V7.2, V7.3 - DEC/EDI Application Client for OpenVMS V5.0 - DECnet OSIs for OpenVMS Alpha Versions V7.2-1 Or - DEC TCP/IP Services for OpenVMS, Versions V5.0A for Alpha o Remote deployment of DEC/EDI Application Client on Tru64 UNIX Alpha system: - DEC/EDI Application Client for Tru64 UNIX V5.0 o Remote deployment of DEC/EDI Application Client on HP-UX system: - DEC/EDI Application Client for HP-UX V5.0 o Remote deployment of DEC/EDI Application Client on Sun Solaris system: - DEC/EDI Application Client for Sun Solaris V5.0 For the use of DEC/EDI OFTP Communication: o For an OpenVMS Alpha System: - DEC X.25 for OpenVMS Alpha V1.4 - DECnet OSI for OpenVMS Alpha Versions V7.2-1 For the use of DEC/EDI PEDI Communication: o For an OpenVMS Alpha system: - Mailbus 400 MTA for OpenVMS Alpha V2.0C - DECnet OSI for OpenVMS Alpha Version V7.2-1 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.4 ____________________ [1] HP GlobalSoft strongly recommends you to upgrade any remote DEC/EDI Application Clients on OpenVMS Alpha to Version 5.0 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 Alpha OpenVMS. - For TRADANET VAN: DECnet OSI for OpenVMS Alpha Versions V7.2-1 and a remote node providing X.25 connector Services 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 V7.2-1 - MAILbus 400 Message Transfer Agent for OpenVMS Alpha V2.0C - DEC X.500 Directory Service (Base Component) for OpenVMS Alpha 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: o For an OpenVMS Alpha System: - DECnet OSI for OpenVMS Alpha Versions V7.2-1 - MAILbus 400 Message Transfer Agent (Base Component) for OpenVMS Alpha V2.0C The following software is required on the remote node on which the MTA is installed: o On a remote Tru64 UNIX node: - DECnet OSI for Tru64 UNIX Versions V5.0A - MAILbus 400 Message Transfer Agent for Tru64 UNIX V2.0B - DEC X.500 Directory Service (Base Component) for Tru64 UNIX V3.1 o On a remote OpenVMS Alpha node: - DECnet ISO for OpenVMS Alpha Versions V7.2-1 - MAILbus 400 Message Transfer Agent for OpenVMS Alpha V2.0C - DEC X.500 Directory Service (Base Component) for OpenVMS Alpha V3.1 For the use of DEC/EDI CommandCenter V4.0: o On a PC running Microsoft Windows NT: - Windows NT Workstation Version V4.0 - ODBC and SQL Components: Oracle 8 ODBC driver (32-bit driver) Version 8.00.03.00 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 4.0 for Windows NT - Microsoft Internet Explorer Version 4.0 for Windows For the use of DEC/EDI Cockpit V4.0: o On a PC running Microsoft Windows NT: - Windows NT Workstation Version V4.0 - ODBC and SQL Components: Oracle 8 ODBC driver (32-bit driver) Version 8.00.03.00 or higher - One of the following communications protocol interfaces: * Windows NT TCP/IP (included with OS) Or * Windows NT Dialup networking TCP/IP (PPP) For OPTIONAL use with DEC/EDI Mapper: Oracle CDD/Repository for OpenVMS Versions V7.0 SOFTWARE LICENSING This software has been developed by HP GlobalSoft Ltd (A wholly owned subsidiary of Hewlett-Packard Co.) and is furnished under the licensing provisions of Hewlett-Packard Standard Terms and Conditions. For more information about HP's licensing terms and policies, contact your local HP office. Licenses for the DEC/EDI components can be purchased either individually 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 license option (UPI= YM7 or YM8 or YM9 or 2QY or 2QZ or 2R0) also includes the Application Client, Mapper 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 Facility. 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 System documentation set. For more information about Compaq's licensing terms and policies, contact your local HP office. CLUSTER ENVIRONMENT This layered product is supported when installed on any node of valid and licensed VMScluster configurations. If the Application connecting to the DEC/EDI Application Client is installed 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 Product Description details the special hardware required by this product. VMSCluster configurations are fully described in the VMScluster Software 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 Alpha V5.0: DEC/EDI Cockpit for MS-Windows, Version 5.0 or higher o DEC/EDI Application Client for OpenVMS Alpha, Version 4.0 o DEC/EDI Application Client for Tru64 UNIX, Version 4.0 o DEC/EDI Application Client for HP-UX, Version 4.0 o DEC/EDI Application Client for Sun Solaris, Version 4.0 o DEC/EDI Application Client for Windows NT / 2K, Version 4.0 o DEC/EDI Application Client for RedHat Linux, Version 4.0 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: o MAILbus 400 Message Transfer Agent for Tru64 UNIX o MAILbus 400 Message Transfer Agent for OpenVMS Alpha 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 Mapper Run-Time option may require existing MAPs to be recompiled on a system which includes the Mapper Development option, with new releases of DEC/EDI. RELATED SERVICES HP GlobalSoft offers a complete selection of services offerings to cover all phases of installation and configuration of a robust EDI solution to provide for the exchange of business-related documents such as purchase orders, invoices, payment remittances and shipping notices between an enterprise and a trading partner. Contact HPGlobalSoft for product or service related queries at srinivasarao.surampudi@hp.com Available Service Offerings: o Project Implementation - DEC/EDI Startup Service - DEC/EDI First Trading Partner Service o SAP(R) R/3(TM) Integration - DEC/EDI Integration Service for R/3 - DEC/EDI Integrator for R/3 - Server Component for HP Tru64 UNIX - DEC/EDI Integrator for R/3 - Server Component for HP OpenVMS - DEC/EDI Integrator for R/3 - Client Component for HP Tru64 UNIX - DEC/EDI Integrator for R/3 - Client Component for HP-UX - DEC/EDI Integrator for R/3 - Client Component for Sun Solaris - DEC/EDI Integrator for R/3 - Client Component for HP OpenVMS Alpha - DEC/EDI Integrator for R/3 - Client Component for HP OpenVMS/OVMS o Communications - DEC/EDI 3780 Implementation Service - DEC/EDI X.25 Installation Service - DEC/EDI X.400 Installation Service - DEC/EDI OFTP Implementation Service - DEC/EDI X.400/X.435 Implementation Service - DEC/EDI Mailbox Implementation Services - DEC/EDI FTP Gateway Implementation Service - DEC/EDI Secure FTP Implementation Service - DEC/EDI SMTP Implementation Service - DEC/EDI Secure SMTP Implementation Service o Support - DEC/EDI Application Support and Performance (ASAP) Service - DEC/EDI Performance and Tuning Services - DEC/EDI Outsourcing Services o Systems Integration Workshops - DEC/EDI Implementation Workshop - DEC/EDI Mapping Concepts Workshop - DEC/EDI Advanced Mapping Concepts Workshop - DEC/EDI Production Operations Workshop - DEC/EDI Integration for R/3 Workshop DISTRIBUTION MEDIA This product is available as part of the OpenVMS Consolidated Software 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 Application Client License QL-6V4A9-AA DEC/EDI Application Client QL-6V5A9-AA DEC/EDI SAP R/3 Integrator Application Client DEC/EDI Server License: DEC/EDI for OpenVMS Alpha 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 Software Media QA-6V3AA-H8 DEC/EDI CD ROM / Documentation Kit Software Product Services DEC/EDI for OpenVMS Alpha QT-2QTA*-** DEC/EDI Application Client QT-2QUA*-** DEC/EDI Translation Component 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 QA-4LNAA-H8 Media (CD-ROM Only) DEC/EDI Cockpit for MS-Windows: QB-2YNAA-SA Media and License package Communication Gateways For additional DEC/EDI communication gateway options, please contact srinivasarao.surampudi@hp.com 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 Mapper Run-Time o DEC/EDI Translation Component o The specified Communication component for installation on a single node. * 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 HP GlobalSoft at srinivasrao.surampudi@hp.com for the most up-to-date information. SOFTWARE PRODUCT SERVICES The DEC/EDI Message Updates containing Trans- actions, 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. 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 HP GlobalSoft with the purchase of a license for the product as defined in the Software Warranty Addendum to this SPD. HP GlobalSoft 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 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 HP GlobalSoft or an authorized sublicensor. (C) Acrobat(R) Reader copyright Adobe Systems Incorporated. (R)Adobe and Acrobat are trademarks of Adobe Systems Incorporated. (R)AT&T Easylink EDI is a registered trademark of AT&T Global Messaging Services Limited. (R)TYMNET and EDI*NET are registered trademarks of British Telecommunications Public Liability company. (R)CLEO and 3780plus are registered trademarks of Interface Systems, Inc. (R)OSI is a registered trademark 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 Windows95 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 of The Open Group in the US and other countries. [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. ® Compaq, the Compaq logo, AlphaServer, DECforms, DECnet, MAILbus, VMS, registered U.S. Patent and Trademark Office. [TM]Alpha, OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group,L.P. [TM]SAP and R/3 are trademarks of SAP AG. (C) November 2005 Hewlett-Packard GlobalSoft Limited AE-Q8WKE-TE Hewlett-Packard GlobalSoft Limited 2006