Software Product Description ___________________________________________________________________ PRODUCT NAME: DEC/EDI FileBridge for OpenVMS for VAX, SPD 05.70.00 Version 1.1 DESCRIPTION DEC/EDI FileBridge provides an optional file based interface for DEC/EDI. It is typically delivered in conjunction with Digital provided ser- vices as a building block in the implementation of an EDI system. The capabilities of FileBridge are: o A sequential flat file interface for DEC/EDI o A table-driven "MAPPER" with a basic set of data manipulation op- erators for selected classes of commonly encountered EDI applica- tion data. This capability is used to convert data from the appli- cation file format to the DEC/EDI Application Programming Inter- face (API). FEATURES FileBridge table development: o Data Specification - During development of Mapping tables, the cus- tomer defines the application file structure, and parameters for mapping between the application file and the EDI standard through a forms-based user interface. From this information, FileBridge gen- erates a conversion table that is used to map data from/to the ap- plication file formats. o User Defined Mapping - For a variety of source data structures and types, FileBridge allows fields to be moved directly to the des- tination or to have built-in mathematical/logical/string operations to be performed upon the fields. The user interface guides the user through this process. Further flexibility is available. The user DIGITAL March 1994 AE-Q5QFA-TE can define and add code through "hooks" for more complex process- ing. o Data Definition Extracts - FileBridge extracts EDI standards doc- ument definition information from DEC/EDI and, as an option, ap- plication file record definitions from CDD/Repository. FileBridge Run-time: o Run-time Invocation - FileBridge document processing may be invoked either by simple changes to application code (the Callable Inter- face) or by using the DCL interface. o DEC/EDI interfacing - For outbound EDI transactions, the applica- tion passes a file to FileBridge which reads the file and gener- ates the DEC/EDI API calls. For inbound EDI transactions, FileBridge reads EDI messages from DEC/EDI and generates the appropriate file for the application to access. o Application file I/O - FileBridge accepts/generates customer-defined sequential files made up of records containing fixed length fields. Each record must contain a record-type field that can be used to identify it. (The software documentation notes additional restric- tions.) o Data tracking - Messages are tracked between FileBridge and DEC/EDI. Tracking identification information may be supplied by the appli- cation, either by parameters to the Callable interface or by in- cluding it in the customer file records. Components of FileBridge: o FileBridge User Interface (UI) - The UI consists of a set of menus and forms that allow users to create, modify, and compile FileBridge tables. o FileBridge Run-time - The Run-time process uses the information in a compiled FileBridge table to map data between the application file and the DEC/EDI API. The Run-time process is the core processing function within FileBridge. 2 o Callable File-level Interface - This interface allows users to ini- tiate FileBridge processing on a file from within a user written program. The program can be written in any language that supports the VAX procedure calling conventions. o DEC/EDI Extract - This is a utility that must be run during devel- opment of the FileBridge tables to extract DEC/EDI document def- initions. o FileBridge Recovery - This process uses the information in the au- dit log database to support manual restarting of FileBridge in case of an unexpected system shutdown. o FileBridge Tracking - This process generates listings of events from the audit database and history files. DOCUMENTATION The following documents are provided with FileBridge: o Installing o Using o Reference o User Interface Description STANDARDS INDUSTRY PRACTICE CONFORMANCE There are no established conformance standards for EDI Mappers. INSTALLATION Digital recommends that a customer's first purchase of this software product include Digital Installation Services. These services provide for installation of the software product by an experienced Digital Soft- ware Specialist. 3 For subsequent purchases of this product only experienced customers should attempt installation. Digital recommends that all other cus- tomers purchase Digital's Installation Services. Customer Responsibilities Before installation of the software, the customer must: o Previously have installed all requisite software and hardware in- cluding terminals. o Make available for a reasonable period of time, as mutually agreed by Digital and the customer, all hardware, communication facili- ties, and terminals that are to be used during installation. 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 - Fault Tolerant VAXft Model 110 VAXft Model 310 VAXft Model 410 VAXft Model 610 VAXft Model 612 PROCESSORS SUPPORTED - VAX VAX 4000 Model 200 VAX 4000 Model 300 VAX 4000 Model 50 VAX 4000 Model 600 VAX 6000 Model 200 Series VAX 6000 Model 300 Series VAX 6000 Model 400 Series VAX 6000 Model 500 Series VAX 6000 Model 600 Series VAX 8200 VAX 8250 4 VAX 8300 VAX 8350 VAX 8500 VAX 8530 VAX 8550 VAX 8600 VAX 8650 VAX 8700 VAX 8800 VAX 8810 VAX 8820 VAX 8830 VAX 8840 VAX 9000 Model 110 VAX 9000 Model 210 VAX 9000 Model 300 Series VAX 9000 Model 400 Series VAX-11/750 VAX-11/780 VAX-11/785 PROCESSORS SUPPORTED - MicroVAX MicroVAX II MicroVAX 2000 MicroVAX 3100 Model 10/10E MicroVAX 3100 Model 20/20E MicroVAX 3100 Model 30 MicroVAX 3100 Model 40 MicroVAX 3100 Model 80 MicroVAX 3300 MicroVAX 3400 MicroVAX 3500 MicroVAX 3600 MicroVAX 3800 MicroVAX 3900 5 PROCESSORS SUPPORTED - VAXstation VAXstation II VAXstation 2000 VAXstation 3100 Model 30 VAXstation 3100 Model 38 VAXstation 3100 Model 40 VAXstation 3100 Model 48 VAXstation 3100 Model 76 VAXstation 3200 VAXstation 3500 VAXstation 3520 VAXstation 3540 VAXstation 4000 Model 60 VAXstation 4000 VLC PROCESSORS SUPPORTED - VAXserver VAXserver 3100 VAXserver 3300 VAXserver 3400 VAXserver 3500 VAXserver 3600 VAXserver 3602 VAXserver 3800 VAXserver 3900 VAXserver 4000 Model 200 VAXserver 4000 Model 300 VAXserver 4000 Model 500 VAXserver 6000 Model 210 VAXserver 6000 Model 220 VAXserver 6000 Model 310 VAXserver 6000 Model 320 VAXserver 6000 Model 410 VAXserver 6000 Model 420 VAXserver 6000 Model 510 VAXserver 6000 Model 520 VAXserver 6000 Model 610 VAXserver 6000 Model 620 6 VAXserver 6000 Model 630 PROCESSORS NOT SUPPORTED MicroVAX I VAX-11/725 VAX-11/730 VAX-11/782 VAXstation I VAXstation 8000 PROCESSOR RESTRICTIONS A TK50 Tape Drive is required for standalone MicroVAX 2000 and VAXs- tation 2000 systems. DISK SPACE REQUIREMENTS ___________________________________________________________________ Table 1: DISK SPACE REQUIREMENTS (Block Cluster Size = 1) ------------------------------------------------------------------- Disk space required for in- 40,500 blocks (20,736K bytes) stallation: Disk space required for use 33,000 blocks (16,896K bytes) (permanent): ___________________________________________________________________ These counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. Additional disk space is required depending on the number of Mapping tables, performance needs, message size and software options. The minimum memory supported is 32 MB. However, the use of this soft- ware in conjunction with increased memory capability improves perfor- mance. The memory size suggested for most typical hardware configu- rations is at least 64 MB. 7 SOFTWARE REQUIREMENTS For Systems Using Terminals (No DECwindows Interface): o OpenVMS VAX Operating System V5.5-2 o DEC/EDI V1.2-03 - V1.3 (SPD 31.70.XX) o DECforms Run-time Only System V1.3 - V1.4 (SPD 29.90.xx) o DEC Rdb Run-time Option for OpenVMS VAX V4.2 - 5.1 (SPD 25.59.xx) During development of the FileBridge tables: the extract utility must run on the same node as the DEC/EDI Translation Service to extract the DEC/EDI tables. The DEC/EDI Application Services are not required dur- ing development. At run-time: FileBridge must run on the node running the DEC/EDI Ap- plication Service. The users application and FileBridge must run on the same node if the FileBridge Callable interface is used. OPTIONAL SOFTWARE CDD/Repository V5.1 is supported but not required.(SPD 25.53.XX) SOFTWARE LICENSING This software is furnished under the licensing provisions of Digital Equipment Corporation's Standard Terms and Conditions. For more in- formation about Digital's licensing terms and policies, contact your local Digital office. License Management Facility Support (LMF) This layered product supports the OpenVMS License Management Facil- ity. License units for this product are allocated on an Unlimited System Use basis only. 8 For more information on the License Management Facility, refer to the OpenVMS Operating System Software Product Description (SPD 25.01.xx) or the License Management Facility manual of the OpenVMS Operating Sys- tem documentation set. For more information about Digital's licensing terms and policies, con- tact your local Digital office. CLUSTER ENVIRONMENT This layered product is fully supported when installed on any valid and licensed VMScluster configuration. The HARDWARE REQUIREMENTS sec- tions of this product's Software Product Description detail any spe- cial hardware required by this product. VMScluster configurations fully described in the VMScluster Software Product Description (29.78.xx) and include CI, Ethernet, and Mixed In- terconnect configurations. OpenVMS Tailoring Classes For OpenVMS V5.x systems, the following OpenVMS classes are required for full functionality of this layered product: o VMS Required Saveset o Network Support o Programming Support o System Programming Support o Secure User's Environment o Utilities o Example Files For more information on OpenVMS classes and tailoring, refer to the OpenVMS Operating System Software Product Description (SPD 25.01.xx). 9 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 9-track 1600 BPI Magtape, TK50 Streaming Tape This product is also available as part of the OpenVMS Consolidated Soft- ware Distribution on CD-ROM. The software documentation for this product is also available as part of the OpenVMS Online Documentation Library on CD-ROM. ORDERING INFORMATION Software Licenses: QL-23WA*-AA FileBridge Development License for VAX/VMS. QL-24HA*-AA FileBridge Migration License for VAX/VMS (for File- Bridge Version 1.0 customers upgrading to FileBridge Version 1.1). Software Media: QA-23WAA-H* Software Documentation: QA-23WAA-GZ 10 Software Product Services: QT-23WA*-** * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. The above information is valid at time of release. Please contact your local Digital office for the most up-to-date information. SOFTWARE PRODUCT SERVICES A variety of other service options are also available from Digital. For more information, contact your local Digital office. SOFTWARE WARRANTY The procedures documented in DEC/EDI FileBridge: Using must be car- ried out on a regular basis to ensure that FileBridge is properly man- aged in a production environment. Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the Software Warranty Addendum to this SPD. © 1994 Digital Equipment Corporation. All rights reserved. [TM]The DIGITAL Logo, CI, DEC, DECforms, DECnet, DECstation, DECsystem, DECwindows, MicroVAX, OpenVMS, TK, VAX, VAXft, VAXserver, VAXstation, and VMS are trademarks of Digital Equip- ment Corporation. 11