Software Product Description SPD: AE-Q8WVG-TE PRODUCT NAME: DEC/EDI for Tru64(TM) UNIX(R), Version V4.2 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 VAN 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 4.2 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. The implementation of clustering support provides high availability by minimizing system downtime. The support for clustering also ensures scalability by providing as close to a linear improvement in performance as possible when new systems are added on to a cluster. In addition to all this, there is increased functionality built into the product with support for Internet communications, XML mapping and web based management. A complete list of add-on services now available for DEC/EDI is under the section ‘Related Services’. For the latest information about the product as well as services offered, please visit the website at http://www.decedi.com New Features added in this release Overriding "From-address" in PEDI gateway In DEC/EDI V4.20 the sender address of a X400 message is configurable for a given partner. The sender address can be configured using communication editor of DEC/EDI V4.20 CommandCenter. The PEDI gateway connections can now be configured with additional fields in which different originator addresses can be specified. This is an optional feature and can be turned ON or OFF with using the check box provided in the connection details dialog box. Follow these steps to make use of this feature: 1. Start the "communications editor" tool from DEC/EDI V4.20 Command center. 2. Double click on an existing PEDI connection (if no PEDI connections are configured, kindly follow the usual step to create a PEDI connection.) 3. To make use of this new feature, click on the "Over-ride originator address" check box. 4. Using the new tabs "Details 5" & "Details 6", specify the O/R address that should over-ride the originator address specified at the gateway level. 5. Click OK to save the changes. 6. To avoid this over-riding, uncheck the "Over-ride originator address" check box mentioned in step 3. PEDI Address matching is not case sensitive By default address matching in PEDI gateway of DEC/EDI V4.20 is case sensitive. When the environmental variable DECEDI_PEDI_IGNORE_CASE is defined the address matching in PEDI gateway is case insensitive. Generation of CONTRL acknowledgment document In DEC/EDI V40B, by default, CONTRL acknowledgment is generated only when there are errors in the incoming transmission file. In DEC/EDI V4.20 CONTRL acknowledgment is generated even when the incoming transmission file does not have any errors (Positive Acknowledgement).DEC/EDI V4.20 also generates CONTRL acknowledgment when the incoming transmission file has some errors(Negative Acknowledgment).Both Positive and Negative Acknowledgement is generated only if CONTRL document is configured. In DEC/EDI V4.20 Positive acknowledgement can be suppressed by defining an environment variable "DECEDI_SUPPRESS_POSTIVE_ACK". The environment variable DECEDI_SUPPRESS_POSTIVE_ACK can be used along with another environmental variable DECEDI_IGNORE_UNB0031. If the environmental variable DECEDI_IGNORE_UNB0031 is defined, the outgoing documents would not wait for acknowledgement from the trading partner. Accessing of database by Trade Track minimized In DEC/EDI V4.20 Trade Track does not access the database when queries are related to live database. Trade Track will only access the memory queues to provide the necessary information. The reduction of database access results in higher performance of Trade Track. Trade Track will continue to access the database for queries related to archive database. 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 4.2 Application Clients to the DEC/EDI Server using the TCP/IP communication protocol. DEC/EDI Version 4.2 Application Clients are available today for: · Tru64(TM) UNIX(R) · HP OpenVMS(TM) Alpha(TM) · HP-UX(R) · Sun(R) Solaris(R) · RedHat Linux(R) · 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) 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. Application to Application Messaging: 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 Data Transformation maps based on an EDI Message definition. Transport EDI formatted and non-EDI data: Ability to POST and FETCH documents to and from the DEC/EDI Server and by-pass the Mapping and Translation functions, for transmission and receipt from trading partners via the DEC/EDI Communication Component. DEC/EDI Server The DEC/EDI Server consists of the following Services which reside on the same node: · DEC/EDI Mapping Services · DEC/EDI Translation Services · DEC/EDI Communications Services · DEC/EDI Operational Services Mapping Services 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 Services function minimizes the effort required to EDI-enable the Business Application by mapping from any fixed length file format to the EDI format in the outgoing direction and from EDI format to a fixed length file format (i.e. the format in which data should be presented to the Business Application) in the incoming direction. At the simplest level, this might be limited to re-ordering of data. More typically, it also involves calculation of some values and conversion of data between data types. 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: o 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 = apping_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. o 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). o 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 ANSI X12 standard to/from different trading partners). o 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. o Business Data Views Support for business data views to allow the user to specify which items of data can be audited and retrieved. o 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: o Support for multiple versions of messages (transactions) and EDI standards o Supports the pass-through transmission of 8-bit national character sets o Compliance checking at Trading Partner level o User-selectable control number generation o Test transmissions o 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 (UCS) , 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: o EDIFACT -Implements ISO 9735 Version-2 -Supports character sets 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 (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: o Event and Error logging The Communication Services Gateways provided by DEC/EDI are: o X.400/X.435 (Pedi) Communication Gateway o OFTP Communication Gateway o Bisynchronous Gateway for VAN Communications o Internet SMTP/MIME Communication Gateway o Import/Export Communication Gateway o 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. o 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(TM) EDI*Express(TM), INS(TM)-TRADANET(TM), BT(R) EDI*NET(R), IBM IN (Europe) and AT&T Easylink EDI(R). -Supports File Restarts. -Recognizes Compressed Data. o Bisynchronous -Provides connections to EDI VANs via the use of 2780/3780, using the CLEO(R) 3780Plus(R) product. -Supports connections to the GEIS(TM) EDI*EXPRESS(TM) and MCI(R) EDI*NET(R) 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. o Internet SMTP/MIME Gateway -Sends and receives EDI messages via Internet SMTP/MIME protocol. -Supports RFC 1767. -Uses TRU64 UNIX Sendmail capability. -Hooks provided to support pre-and post-processing for functions such as security. o 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 o Access Control o Processing Control o Error logging and exception reporting o Auditing and Archiving o Access Control -Controls user access to the DEC/EDI system by enabling the DEC/EDI Cockpit and CommandCenter to specify whether users may: o View business data only (read-only) o View and modify business data (reset, resend, cancel batch, archive mapper events) o View and modify data for a restricted set of applications and/or trading partners o View data for mapper events, documents, batches or transmission files o Modify DEC/EDI Cockpit views to enable column titles to be specified o Use the CommandCenter applications o 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 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 e-mail to the designated EDI System Administrator. o Auditing and Archiving The DEC/EDI server creates audit trail entries for each document it processes. The parameters which 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(R) Windows(R), Windows 95(R), Windows NT(TM),r Windows 2000(TM) or Windows XP ™, 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: o 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. o 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 (UCS) , ANSI X12 and TRADACOMS syntax. The editing function is carried out in the CommandCenter and then stored in the DEC/EDI Server. o 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. 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. o 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(R) Windows(R), Windows 95(R), Windows NT(TM),r Windows 2000(TM) or Windows XP ™ 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: o DEC/EDI Introduction o DEC/EDI Installation o DEC/EDI Application Development o DEC/EDI Tru64 UNIX User Support Manual All the above documents are also available on-line with the CommandCenter component in Adobe Acrobat STANDARDS AND INDUSTRY PRACTICE CONFORMANCE The DEC/EDI product conforms to the following formal industry standards: o ISO 9735 (EDIFACT), version-2 o ANSI X12.5 and X12.6 o CCITT Recommendation X.435 (EWOS Kernel Functional Profile, June 1992 /TD 22 ) o RFC 1767; Transmission of EDI documents over SMTP/MIME 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 HPGS (Hewlett Packard GlobalSoft Limited) recommends that a customer's first purchase of this software product include HPGS Installation Services. These services provide for installation of the software product by an experienced HPGS Software Specialist. For subsequent purchases of this product only experienced customers should attempt installation. HPGS recommends that all other customers purchase HPGS'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 below, and hardware, including terminals. o Make available for a reasonable period of time, as mutually agreed by HPGS 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 hosts that have previously been installed by HPGS. Delays caused by any failure to meet the responsibilities will be charged at the then prevailing rate for time and materials. HARDWARE REQUIREMENTS Any 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. In a TruCluster Server implementation where a DEC/EDI instance is required to operate on more than one node of the cluster, the Memory Channel cluster interface is also required. If DEC/EDI will run as independent instances on members of the cluster (for example, a production instance on one node and a test instance on a second node) then the Memory Channel hardware is not required. and an IBM-compatible PC (Intel 486 or higher processor) with a minimum of 64Mb of Memory (128Mb recommended), SVGA graphics support and a CD-ROM reader, networked to the Tru64 UNIX system running the DEC/EDI Server software. DISK SPACE REQUIREMENTS Table 1 Disk Space Required for Installation ---------------------------------------------------- DEC/EDI V4.2 Subset Size in KB Base 300 Server 18146 Server Man Pages 70 Client 576 Client Man Pages 146 Translation Services 4953 Mailbus 400 Gateway 433 OFTP Gateway 353 Internet SMTP/MIME Gateway 449 3780 Gateway 442 Message Updates Base 449 Message Updates Man Pages 290 Message Updates EDIFACT IMPDEF Files 13270 Message Updates ODETTE IMPDEF Files 158 Message Updates X12 IMPDEF Files 43516 Message Updates TDCC IMPDEF Files 9866 Message Updates TRADACOMS IMPDEF Files 236 Table 2 Disk space required for use (permanent) ---------------------------------------------------- DEC/EDI V4.2 Subset Size in KB Base 300 Server 18146 Server Man Pages 70 Client 576 Client Man Pages 146 Translation Services 4953 Mailbus 400 Gateway 433 OFTP Gateway 353 Internet SMTP/MIME Gateway 449 3780 Gateway 442 Message Updates Base 449 Message Updates Man Pages 290 Message Updates EDIFACT IMPDEF Files 13270 Message Updates ODETTE IMPDEF Files 158 Message Updates X12 IMPDEF Files 43516 Message Updates TDCC IMPDEF Files 9866 Message Updates TRADACOMS IMPDEF Files 236 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 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. For Bisynchronous Communications for connecting to EDI VANs: o The CLEO 3780Plus product is required for use with the DEC/EDI Bi-synch communications capability on Tru64 UNIX. Contact the following outlet to purchase CLEO 3780Plus: Hewlett Packard EDI Practice Center in Dallas, Texas, for complete price and delivery information. Tel: +1-972-702-4267 SOFTWARE REQUIREMENTS The versions of the required software listed here are the minimum supported versions. DEC/EDI is regularly tested with newer versions of all software. Please contact your local Hewlett Packard or HPGS representative for the latest tested versions: For DEC/EDI Application Client and DEC/EDI Server deployment on the same node or for the DEC/EDI Server alone: o Tru64 UNIX Operating System V5.1 through V5.2 . Note: Tru64 UNIX V5.1 requires the T64V51AS0003-20010521 Aggregate Patch Kit available from the Hewlett Packard Support website, or through your local Customer Support Centre. o Operating System Document Preparation Tools (Text Processing) (setld Subset OSFDCMT510). o TCP/IP (as supplied with the Tru64 UNIX Operating System) o Fortran RTL #388 for Tru64 UNIX Alpha Systems (setld subset DFARTL388; available on your Operating System distribution CD) o Pascal RTL V5.7-23 for Tru64 UNIX Systems (setld subset DPORTL570; available on your Operating System distribution CD) o Database: Support for Oracle 8i / Oracle 9i -For Oracle 8 Oracle 8 Server (RDBMS), Versions 8.1.6.2.0 (i.e., 8.1.6 plus patch kit 8.1.6.2.0) Oracle 8 SQL*NET V2, Versions 8.1.6.0.0 Oracle 8 TCP/IP Protocol Adapter V2 or higher Oracle 8 Server Manager, Version 3.1.6.0.0 or higher o DEC/EDI CommandCenter V4.2 and its pre-requisites. For the use of DEC/EDI CommandCenter V4.2: o On a PC running Microsoft Windows NT: -Windows NT Workstation Version V4.0 -ODBC and SQL Components: -For Oracle Rdb Oracle ODBC Driver for Rdb, Versions 2.0.20, 2.10.11 (32-bit driver) -For Oracle 8 Oracle 8 ODBC driver (32-bit driver) Version 8.00.03.00 or higher Oracle SQL*NET Client Version 2.3.4 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 NT as supplied with the CommandCenter -Microsoft Internet Explorer Version 4.0 for Windows NT as supplied with the CommandCenter OPTIONAL For the remote deployment of the DEC/EDI Client for Tru64 UNIX V4.0 Tru64 UNIX Operating System V5.1 through V5.2. Note that Tru64 UNIX V5.1 requires the T64V51AS0003-20010521 Aggregate Patch Kit available from the Hewlett Packard Support website or through your local Customer Support Center. TCP/IP (as supplied with the Tru64 UNIX Operating System) Fortran RTL #388 for Tru64 UNIX Alpha Systems (setld subset DFARTL388; available on your Operating System distribution CD) Operating system Document Preparation Tools (Text Processing) (setld subset OSFDCMT510). For remote deployment of DEC/EDI Application Clients on other platforms… DEC/EDI Application Client for OpenVMS Alpha V3.2B and its prerequisite software. [1][2] DEC/EDI Application Client for Sun Solaris V3.2B and its prerequisite software. [1][2] DEC/EDI Application Client for HP-UX V3.2B and its prerequisite software. [1][2] DEC/EDI Application Client for RedHat Linux V4.0 and its prerequisite software.[2] DEC/EDI Application Client for Windows NT/2000 V4.0 and its prerequisite software.[2] [1] Although the DEC/EDI V4.2 Server will operate successfully with DEC/EDI V3.2B clients, HPGS recommends that you upgrade any remote DEC/EDI Application Clients to Version 4.2 as rapidly as possible. [2] Please refer to the relevant DEC/EDI Application Clients Software Products Description for details. For the use of DEC/EDI OFTP Communication, X.25 Base Component (X.25 for Digital UNIX Components) Versions V3.21 and its prerequisite software. setld subset name is XXAACC321. 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 MAILbus 400 MTA Server (Digital UNIX) V2.0B (setld subset MTAASRVR202) is required along with its prerequisite software. If the MTA is located on a remote node, the MAILbus 400 API (Digital UNIX) V2.0B (setld subset MTAACLNT202) is required along with its prerequisite software. The DEC/EDI Internet SMTP/MIME Communication requires the installation and configuration of the UNIX sendmail and mailx functions. For the use of DEC/EDI Cockpit V4.2: o On a PC running Microsoft Windows NT: -Windows NT Workstation Versions V4.0 -ODBC and SQL Components: -For Oracle Rdb Oracle ODBC Driver for Rdb, Versions 2.0.20, 2.10.11 (32-bit driver) -For Oracle 7 Oracle 7 ODBC driver, Version 1.13.5.0.0a or higher Oracle SQL*NET Client Version 2.2.2.1.0 or higher Oracle TCP/IP Protocol Adapter Version 2.2.2.1.0 or higher -One of the Communications protocol interfaces: -Windows NT TCP/IP (included with OS) or -Windows NT Dialup networking TCP/IP (PPP) SOFTWARE LICENSING This software is furnished under the licensing provisions of Hewlett Packard's Standard Terms and Conditions. For more information about Hewlett Packard's licensing terms and policies, contact your local Hewlett Packard office. Licenses for the DEC/EDI components can be purchased either individually or as a package. The following packaged license options are available: o DEC/EDI Bi-Synch Package o DEC/EDI OFTP Package o DEC/EDI X.400 Package o 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. For more information on the License Management Facility, refer to the Tru64 UNIX Alpha Software Product Description or the License Management Facility manual of the Tru64 UNIX Operating System documentation set. For more information about Hewlett Packard's licensing terms and policies, contact your local Hewlett Packard office. OPTIONAL SOFTWARE The following product versions are recommended for use with DEC/EDI for Tru64 UNIX V4.0. o DEC/EDI Application Client for Tru64 UNIX, Version 4.2 o DEC/EDI Application Client for HP-UX, Version 4.2 o DEC/EDI Application Client for Sun Solaris, Version 4.2 o DEC/EDI Application Client for Windows NT/2K, Version 4.2 o DEC/EDI Application Client for RedHat Linux, Version 4.2 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. RELATED SERVICES Hewlett Packard Global Services 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 Hewlett Packard Global Services, Professional Services Division, locally or email Surampudi.srinivasrao@hp.com or decedi@digital.com for details and quotations. You can also visit the official DEC/EDI website at www.decedi.com for the latest product information. HPGS's Electronic Commerce EDI solutions are complete, scalable and robust. The cornerstone of this approach is the creation of EDI solutions based on the following key elements. o Hewlett Packard's full line of Alpha processors is supported on OpenVMS and Tru64 UNIX systems. o DEC/EDI Client products cover a wide variety of remote systems, both Hewlett Packard and non-Hewlett Packard. o Solutions are feature rich, client/server implementations. DEC/EDI is a robust electronic commerce product that takes full advantage of the underlying client/server architecture to deliver high quality integration, standards translation, and communications management functionality, including the Internet. -With the base server, system software and EC software in place Hewlett Packard focuses on the customers need for consulting services to address business problems. Hewlett Packard Professional Services provides highly skilled, professional EC consulting talent for customer orientation, training, needs assessment, systems design, and project planning to help a customer identify the business need and to prepare the solution. -Common services have been packaged for ease of purchase and implementation. Startup services build the initial systems. First Trading Partner Services completely implements one fully operational electronic trading relationship in production such that a customer can take over and complete the rest of the project. -Every project seems to need those special, customized services which allow the customer to get exactly what they need in form and functionality -the finishing touch in technical excellence. Custom services also address specialized communications gateways, unique corporate security needs, specialized legacy business application integration and rollouts to trading partners. -Certain applications require prepackaged, certified, interfaces to meet the design requirements of the original applications software provider. A prime example of this is the SAP R/3 product line. HPGS has developed and obtained SAP certification for superior interfaces to SAP's R/3 products. These "Certified" application interfaces round out the complete HPGS EC offering, providing customers with robust, tightly integrated offerings to solve their EC problems. 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 Tru64 UNIX -DEC/EDI Integrator for R/3 -Server Component for HP OpenVMS -DEC/EDI Integrator for R/3 -Client Component for 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/VAX 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 The DEC/EDI Application Clients and Server Components are available as part of the Tru64 UNIX Consolidated Software Distribution on CD-ROM. ORDERING INFORMATION Software Licenses DEC/EDI Application Client License: QL-6V4A9-AA DEC/EDI Application Client QL-6V6A9-AA DEC/EDI SAP R/3 Integrator Client for UNIX 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-6V3AA-H8 EDI CD-ROM / Documentation Kit 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 V4.2: QL-4LNAW-AA License QA-4LNAA-H8 Media (CD-ROM Only) DEC/EDI Cockpit 4.2: QB-2YNAA-SA Media and License package Communications Gateways: For additional DEC/EDI Communication Gateway options , kindly contact srinivasrao.surampudi@hp.com or decedi@digital.com. Each package license option also includes the following: o DEC/EDI Application Client o DEC/EDI Server o 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 HP 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 HP. For more information, contact your local HP 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 HP 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 HP office for the most up-to-date information. HP 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 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) BT 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 ,Windows 95 , Windows NT, Windows 2000 and Windows XP are registered trademarks of Microsoft Corporation. (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 8, Oracle Rdb, Oracle SQL/Services, Oracle Rdb run-time option and Oracle CDD/Repository are trademarks of Oracle Corporation. (TM) SAP and R/3 are trademarks of SAP AG. ® Compaq, the Compaq logo, Alpha Server, DECforms, DECnet, MAILbus, MicroVAX, VMS, VAX, registered U.S. Patent and Trademark Office. (TM) Alpha, OpenVMS and Tru64 are trademarks of Hewlett-Packard Company. © 2006 Hewlett-Packard Company March 2006 53.50.06