COMPAQ Software Product Description ___________________________________________________________________ Product Name: MAILbus 400 Message Router Gateway SPD 53.65.05 for OpenVMS, Version 1.2C PRODUCT DESCRIPTION MAILbus 400[TM] Message Router Gateway (XMR) for OpenVMS[TM] VAX[TM] is one of the specialised tools and services required to facilitate the migration of users of the DIGITAL[TM] MAILbus[TM] (Message Router) based E-Mail systems to MAILbus 400 Message Transfer Agent (MTA) based X.400 messaging environment. The Gateway is a layered software product that resides on an OpenVMS VAX system. XMR provides a direct connection between an X.400 mail sys- tem served by a MAILbus 400 Message Transfer Agent (MTA) and a MAIL- bus network served by Message Router. It enables MAILbus based appli- cations, such as ALL-IN-1[TM] Integrated Office System (IOS), to ex- change mail with MAILbus 400 based applications, such as MailWorks[TM] Server for UNIX[R]. The Gateway normally performs address translation between MAILbus and O/R addresses using information held in the DIGITAL X.500 Directory Service, which is used by the MTA. XMR is also able to deliver a mes- sage to a recipient when the originator has supplied, in the recip- ient's address, information specific to the receiving mail system; this address information being supplied in address attribute extensions avail- able to the sending system. If this information is not supplied, the Gateway will use the supplied address information to search the DIG- ITAL X.500 Directory Service for the address translation for the re- ceiving mail system. If XMR is unable to find a translation, the mes- sage will be non-delivered. When the Gateway is processing non-actionable April 1999 AE-Q8QTF-TE addresses, if a translation is not found in the Directory, the Gate- way will generate a repliable address based on the Gateway's own ad- dress. The Gateway maps bodypart contents between the outbound bodypart type and the associated type in the receiving system. The mapping is based on a bodypart mapping table, which is customisable to allow the pre- ferred mappings to be modified, or added to, according to the types present in the mail system. XMR does not perform any conversion of the actual content data. MAILbus bodyparts with contents such as WPS-PLUS[TM], DECdx[TM], RMS (tagged as DDIF[TM]) or a PC format (for example, Word- Perfect[TM] or Microsoft[R] Word) are transferred to the MAILbus 400 MTA as tagged Externally Defined bodyparts. Conversions are initiated by the MTA, which calls the appropriate CDA[TM] converter library, if required. In the reverse direction, the X.400 bodyparts are mapped into MAILbus bodyparts and tagged so that the appropriate viewer or con- verter can be automatically invoked by the receiving user agent or gate- way. The Gateway communicates with the MAILbus 400 MTA using the X/Open[TM] XAPI interface, allowing access to all the features of the X.400 stan- dard. XMR communicates only with the MAILbus 400 MTA and not X.400 MTAs from other vendors. The Gateway communicates with Message Router us- ing the Message Router interface as documented in the Message Router Programmer's Kit. The Gateway may be located either remotely or lo- cally to Message Router. The Gateway may be located either remotely or locally to the MAILbus 400 MTA but where it is necessary to have the MAILbus 400 MTA convert WPS-PLUS, DECdx or DDIF bodyparts received from the Gateway, the Gateway and the MAILbus 400 MTA should be colo- cated on the same OpenVMS VAX node. The Compound Document Architecture (CDA) Converter Library is required for the MAILbus 400 MTA to convert the content of Message Router WPS-PLUS bodyparts, from ALL-IN-1 IOS, and DECdx bodyparts (for example, from the Message Router/S Gateway (MRS) and the Message Router/P Gateway 2 (MRP)) to an X.400 bodypart type; the required CDA converter is cur- rently only available on OpenVMS VAX. The DEC[TM] ODA Compound Doc- ument Architecture Gateway is required for the MAILbus 400 MTA to con- vert the content of Message Router RMS bodyparts when they contain DDIF data. To communicate with MAILbus and MAILbus 400 environments, the Gate- way uses DECnet[TM]-Plus for OpenVMS (formerly DECnet/OSI[R] for Open- VMS) and DIGITAL X.500 Directory Service for directory services. Management XMR is managed according to the DIGITAL model Enterprise Management Architecture (EMA), in the same way as the MAILbus 400 MTA. It can be managed from any DECnet-Plus node equipped with a suitable Director, such as NCL. Conformance to Standards The Gateway communicates with the MAILbus 400 MTA using the X/Open XAPI interface which is conformant to the X/Open CAE Specifications. YEAR 2000 COMPLIANCE (Y2K) MAILbus 400 Message Router Gateway also becomes Year 2000 Ready with its Version 1.2B release.Any two digit dates received by the Gateway are interpreted as follows: - Years "81" to "99" (inclusive) as "1981" to "1999" and - Years "00" to "80" (inclusive) as "2000" to "2080" MAILbus 400 Message Router Gateway is specified as Year 2000 Ready and will correctly process, calculate, compare and sequence date data from, into and between the twentieth and the twenty-first centuries and the years 1999 and 2000, including leap year calculations, when used in accordance with the associated DIGITAL Product documentation and pro- vided that all hardware, firmware and software used in combination with 3 such DIGITAL Products properly exchange date data with the DIGITAL Prod- ucts. SOFTWARE REQUIREMENTS One of the following software configurations is required on the Gate- way node: o OpenVMS Operating System, V6.1 or V6.2 DECnet/OSI V6.3 MAILbus 400 Message Transfer Agent for OpenVMS, V2.0 or later, Base component o OpenVMS Operating System V7.1 DECnet-Plus for OpenVMS V7.1 with ECO 1, including the DECnet Ap- plication Interface component (formerly known as the OSI Applica- tions Kernel or OSAK[TM]) MAILbus 400 Message Transfer Agent for OpenVMS, V2.0A or later, Base component For Y2K Readiness, the Y2K Kit (Part Number VAXY2K0n_071)for the OpenVMS V7.1 operating system should be added and the MAILbus 400 MTA V2.0B installed. o OpenVMS Operating System V7.2 DECnet-Plus for OpenVMS V7.2 including the DECnet Application In- terface component (formerly known as the OSI Applications Kernel or OSAK[TM]) MAILbus 400 Message Transfer Agent for OpenVMS, V2.0C or later, Base component NOTE: The license for the MAILbus 400 Message Router Gateway includes the use of the Base component of the MAILbus 400 Message Transfer Agent for OpenVMS. Depending on connectivity requirements the following software may be installed either locally, that is, on the same node as the Gateway, or remotely: o VAX Message Router, V3.3A 4 o MAILbus 400 Message Transfer Agent for OpenVMS, V2.0 or later Where the Gateway is required to connect to a MAILbus 400 Message Trans- fer Agent running on DIGITAL UNIX, the following is required on the DIGITAL UNIX node: o MAILbus 400 Message Transfer Agent for DIGITAL UNIX V2.0 or later. NOTE: MAILbus 400 Message Transfer Agent V2.0 or later requires the use of the DIGITAL X.500 Directory Service V3.0. See the MAILbus 400 Message Transfer Agent V2.0 or later Software Product Description (SPD 42.83), for details of its required software and configuration. OpenVMS Tailoring: The following OpenVMS classes are required for full functionality of this layered product: o OpenVMS Required Saveset o Network Support o Programming Support For more information on OpenVMS classes and tailoring, refer to the OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx). OPTIONAL SOFTWARE To initiate the appropriate WPS-PLUS, DECdx and DDIF conversions, MAIL- bus 400 MTA requires access to the following CDA Libraries : o CDA Converter Library V2.2 is required for conversion of WPS-PLUS and DECdx format bodyparts o DEC ODA Compound Document Architecture (CDA) Gateway for OpenVMS V1.0-007 is required for conversion between DDIF and ODIF format bodyparts 5 CLUSTER ENVIRONMENT This layered product may be installed on each node in any valid and licensed VMScluster[TM]* configuration. Each node of a VMScluster can run one instance of the MAILbus 400 Message Router Gateway. Each Gate- way is independent and does not share workspace and operates as it would on an individual system. * VMScluster configurations are fully described in the VMScluster Soft- ware Product Description (29.78.xx) and include CI[TM], Ethernet, and Mixed Interconnect configurations. HARDWARE REQUIREMENTS The Gateway is only supported on OpenVMS VAX. Processors Supported MAILbus 400 Message Router Gateway is supported on all valid OpenVMS VAX Configurations supported by DECnet-Plus, with the exception of those listed below. Refer to DECnet-Plus for OpenVMS VAX Software Product Description (SPD 25.03.xx) for further information on supported hard- ware configurations. Processors Not Supported MicroVAX[TM] I, VAXstation [TM] I, VAX-11/725, VAX-11/782, VAXstation 8000, MicroVAX 2000, VAXstation 2000. Disk Space Requirements (Block Cluster Size = 1): Disk space required for 7100 blocks installation: 6 Disk space required for 6600 blocks use (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. GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. ORDERING INFORMATION Software Licenses: QL-342A9-AA Software Documentation: QA-342AA-GZ.1.2C Software Product Services: QT-342A9-L9 NOTE: The license for the MAILbus 400 Message Router Gateway includes the use of the Base component of the MAILbus 400 Message Transfer Agent for OpenVMS. DISTRIBUTION MEDIA This product is available as part of the DIGITAL CD-ROM Software Li- brary for OpenVMS VAX Consolidated Layered Products. The software documentation for this product is available as part of the OpenVMS VAX Online Documentation Library on CD-ROM. SOFTWARE LICENSING This software is furnished only under a license. For more information about COMPAQ's licensing terms and policies, contact your local COM- PAQ office. 7 License Management Facility Support: This layered product supports the OpenVMS License Management Facil- ity. License units for this product are allocated on an Unlimited System Use plus Personal Use and Concurrent Use basis. For more information on the License Management Facility, refer to the OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx) or the License Management Facility manual of the OpenVMS VAX Operat- ing System documentation set. SOFTWARE PRODUCT SERVICES The Gateway can participate in large distributed messaging networks, which may involve multiple vendors' systems in multiple locations. COM- PAQ offers a number of consulting services to assist customers in the planning, installation, management, and integration of these messag- ing networks. COMPAQ Consulting also offers specialised tools and ser- vices that are tailored to assisting the customer migrate from the MAIL- bus environment to the MAILbus 400 environment. A variety of service options are available from COMPAQ. For more in- formation, contact your local COMPAQ office. SOFTWARE WARRANTY Warranty for this software product is provided by COMPAQ with the pur- chase of a license for the product as defined in the Software Warranty Addendum of this SPD. The above information is valid at time of release. Please contact your local COMPAQ office for the most up-to-date information. Warranty Limitations Absolute fidelity between an original document and the resulting doc- ument as printed or displayed by the receiving system is not guaran- teed. 8 Due to the differences in capabilities between the NIST (National In- stitute of Science & Technology) and X.400 messaging systems, not all features may be fully preserved when transferring messages across the disparate systems. [R] OSI is a registered trademark of CA Management, Inc. [R] Microsoft is a registered trademark of the Microsoft Corpora- tion. [R] UNIX is a registered trademark licensed exclusively by X/Open Company Ltd. [TM] X/Open is a trademark of the X/Open Company Limited. [TM] WordPerfect is a trademark of the WordPerfect Corporation. [TM] The COMPAQ Logo, ALL-IN-1, CDA, CI, DDIF, DEC, DECdx, DECnet, DIGITAL, MAILbus, MailWorks, MAILbus 400, MicroVAX, OpenVMS, OSAK VAX, VMScluster, VAXstation, WPS-PLUS are trademarks of Compaq Computer Corporation. Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not in- fringe 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 description. Possession, use, or copying of the software described in this publi- cation is authorized only pursuant to a valid written license from DIG- ITAL or an authorized sublicensor. © Compaq Computer Corporation 1994,1999. All rights reserved. 9