Data Interchange plc. Issued: 14 March Copyright Data Interchange Plc Peterborough, England, September 2005.

Transcription

1 Data Interchange plc Issued: 14 March 2006 Copyright Data Interchange Plc Peterborough, England, September All rights reserved. No part of this document may be disclosed to third parties or reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written permission of Data Interchange Plc.

2

3 Table of Contents ODEX Enterprise... 1 Introduction...1 Key Features...1 Workflow Management and Automation...1 Communications...1 Translation...2 Integration...2 Logging and Visibility...2 Architecture and Scalability...2 Supported Standards and Formats...2 EDI functionality...3 On-line Help...3 Security and backup...3 Feature Details...3 Multi-user Client/Server...3 Workflow Management and Automation...3 Communications...5 Xe Mapping...5 File encoding conversion...6 Back Office Integration...6 Traceability and Visibility...7 Clustering...7 Scalability...7 EDI functionality...7 On-line Help...7 Security and backup...8 Product Architecture...8 System Requirements...9 Hardware...9 Software...9

4

5 ODEX Enterprise Introduction Businesses in almost every market sector need an efficient system which enables them to exchange business documents and achieve complete internal system integration. ODEX Enterprise is the solution that integrates with internal systems and offers flexible and secure communications, enabling business documents to flow reliably between trading partners and back office applications. ODEX Enterprise delivers substantial cost savings by freeing up human resources, removing the need for paper documents and cutting out inefficient and time-consuming manual processes. The flexibility of ODEX Enterprise ensures that it can be customised to fit into existing operations, no matter how complex, allowing internal systems to share information reliably and allowing outbound files to be routed, with or without translation, to trading partners. High-level automation allows ODEX Enterprise to run unattended and its high-performance, automated front-end capabilities enable seamless integration with production systems. A key feature of ODEX Enterprise is its support of several communication protocols, communication sub-systems and message standards which allow the user complete flexibility when deciding which standards to adopt with different trading partners. The supported sub-systems and protocols enable OFTP communication over TCP/IP or ISDN, and secure EDI over the Internet in the form of AS2. Key Features Workflow Management and Automation Dark room environment File Routing Error Workflows Automated file transmission System events Event scheduling Automatic execution of external applications Communications Protocols OFTP, AS2, FTP Subsystems TCP/IP, XOT, HTTP, ISDN via CAPI 2 and R-CAPI EDI and non-edi data e.g. CAD/CAM ODEX Enterprise 1

6 Direct and VAN communications Translation File encoding conversion Xe Mapping Engine Multi-document support Trading Partner-dependent mapping Integration Integration with third party MRP/ERP systems Client/server API (Batch interface) Windows system service SAP R/3 integration Integration with other DI products Logging and Visibility Real-time communications monitoring Real-time system statistics Configurable tracing levels Audit trails of Workflow activities User-definable retention periods notifications Architecture and Scalability Multi-user client/server architecture Scalable database from MSDE to SQL Server Windows 2003 Server clustering Integration with Windows NT security Supported Standards and Formats ANSI X12 CSV EANCOM EDIFACT ODETTE SAP IDocs TRADACOMS VDA XML 2 ODEX Enterprise

7 EDI functionality On-line Help Detailed EDI file analysis and interchange-level extraction Files analysed, split, forwarded and processed according to EDI addressing and/or message type Full context-sensitive help Security and backup Supports a flexible user and user groups environment Software functionality restrictions based on user privileges Password protected access Automated database backup Feature Details Multi-user Client/Server The heart of ODEX Enterprise is the Server. The three clients can be installed in as many locations as required for full multi-user functionality. Workflow Management and Automation In common with all members of the ODEX product family, ODEX Enterprise operates in a dark room environment. This means that manual intervention is not necessary under normal circumstances and there is therefore no requirement for IT staff to be on-site 24 hours a day. If any event occurs which does require manual intervention, ODEX Enterprise can be configured to trigger the sending of an alarm pager call to the appropriate person. ODEX Enterprise analyses the properties of a file before deciding which Workflow to perform on it. A Workflow is a sequence of jobs ODEX Enterprise 3

8 that ODEX is configured to perform on a file upon receipt. ODEX Enterprise includes over 20 jobs that can be performed on a file including Schedule, Copy, , Construct and Run Application. Once the appropriate Workflow has been selected, then the sequence of jobs in that Workflow is performed on the file. This concept of Workflows allows ODEX Enterprise to deliver an extremely flexible solution, for example to enable the dynamic routing of messages to different internal systems based on the type of file ODEX receives. Should a problem be encountered during the processing of a file, ODEX can automatically switch to an Error Workflow, which in turn will automatically generate an to a system administrator or attempt to send the file using an alternative communications method. Figure 1- File processing within ODEX Enterprise ODEX offers further automation with the ability to respond to system events and perform actions against predefined time schedules. System events such as Call Ended, Connection Failed or Call Retry 4 ODEX Enterprise

9 Limit Reached can all automatically trigger actions such as Send E- mail or Run Application. For example, in a time-critical process, such as the sending of files to the Inland Revenue, ODEX would immediately detect if the ISDN line were to go down and alert the appropriate person to take action. For frequent, re-occurring actions, such as Call Network and Poll Monitored Directory, ODEX can be configured to run the events against a time Schedule, for example to call a trading partner every morning at 9am, or to poll a monitored directory every 5 minutes. Communications ODEX Enterprise offers several communications protocols, each of which can be used to transmit both EDI and non-edi data. None of them is concerned with the content or validity of the data, but simply with the means to transport the data. OFTP OFTP is the protocol used by the major European motor manufacturers and their suppliers. It is currently being adopted by many other business sectors. OFTP provides a method of transferring files across X.25, X.25 over ISDN and over TCP/IP. An OFTP communications session does not require any interaction from the user. The 2 machines involved control the session, taking turns to send data until the session is closed by mutual agreement. AS2 Xe Mapping AS2 is promoted in America as a way to avoid the traditional cost of VANs. In the UK it is mainly used by US-owned companies, such as ASDA, and their suppliers. AS2 is a draft specification for the secure exchange of business documents and business-to-business (B2B) transactions over the Internet using HTTP as its transport protocol. AS2 provides an envelope for the data, allowing transactions to be sent and received securely and directly over the Internet instead of via the more traditional VAN. N.B. The Drummond Group is an American company which seeks to encourage AS2 solution suppliers to acquire their accreditation, at considerable cost. Although Data Interchange, in common with other UK-based AS2 solution suppliers, has not sought such certification from the Drummond Group, we can assure users that ODEX Enterprise uses certified components in its AS2 solution. ODEX Enterprise offers a powerful any-to-any mapper that allows for the translation of documents into the correct format for the target system, removing the issue of incompatible file formats between internal systems and trading partners. ODEX Enterprise 5

10 Xe translates files by mapping fields from one file to another and can handle any format of file, including EDI, flat file, csv and SAP formats. The Xe Mapping component can also perform conditional mapping, arithmetic operations and hierarchy changes. File encoding conversion ODEX Enterprise can also convert files from one character format to another, using the Workflow Manager. Unlike ODEX on other platforms, ODEX Enterprise recognises the supported formats and will therefore carry out the requested conversion only if the file is in the expected format. Formats handled include ASCII, EBCDIC, Unicode, Big Endian Unicode, UTF7 and UTF8. Back Office Integration Accessibility ODEX Enterprise enables the complete integration of internal systems, allowing for the seamless exchange of business documents between multiple internal systems and external trading partners. In the event of incompatible message formats between internal systems and trading partners, XLATE Evolution (Xe) can be utilised to facilitate message translations and mappings. ODEX Enterprise also offers specialised SAP integration, which delivers EDI capability to SAP systems. The integration offered by ODEX Enterprise enables EDI data to flow between SAP and trading partners, whilst also allowing SAP to monitor the status of outgoing files. ODEX can be configured to pass files to and receive files from DARWIN 3 (our complete order processing solution), thus avoiding the need to re-key data. When receiving files from internal systems, ODEX relies on Windows notifications to tell it when a file has been copied to a monitored directory. If the directory is an NFS share (on a non-windows system), or a Novell share, these notifications are not generated. Therefore, if an NFS share or a Novell share is being used, an alternative to monitoring is offered in the form of ODEX Event Actions, which provide the ability to poll a directory at regular user-specified intervals. Any directory can be monitored or polled, using one of these two methods, providing it is accessible from the ODEX Server and uses UNC (Universal Naming Convention) addressing. Likewise, when ODEX sends received files to specified directories, such directories may be in any location, providing they are accessible from the ODEX Server and use UNC addressing. 6 ODEX Enterprise

11 Traceability and Visibility Clustering Scalability ODEX Enterprise provides high visibility of active and recent communication sessions and allows critical business files to be traced as they progress through the system. No file can ever get lost in the system and each file is always visible throughout its life, finally being archived after processing is complete. The progression of a file through a Workflow is constantly monitored and its status updated as each job within the Workflow is completed. Should a problem occur within a workflow then s and other system alerts can be triggered to actively alert system administrators. This also ensures that any operational issue can be traced back to the cause and resolved before business is impacted. The resulting audit trail of all the actions that have been carried out by the workflow manager on a file can be viewed at any time. In addition, the file itself can be viewed retrospectively, as it existed at any stage in its passage through the Workflow. For example a file can be viewed in both its pre- and post-translation state, if necessary. Clustering allows two or more independent ODEX Enterprise servers to be connected together, making them appear to network clients as a single system. Such a system is then known as a cluster environment. Running ODEX Enterprise in a cluster environment means that the application will continue running even when one of the servers is out of action owing to planned or unplanned downtime. Clustering is thus an ideal solution for disaster recovery and provides an extremely robust system. Clustering is available via MSCS (Microsoft Cluster Server). The ODEX Enterprise servers in the cluster environment must be based on a Windows Server (NT, 2000 or 2003) operating system. ODEX Enterprise utilises a high-performance and fully scalable database, allowing it to handle the most demanding of high-volume scenarios. EDI functionality On-line Help Although ODEX Enterprise, in common with all members of the ODEX product family, can handle any type of file, it has been designed with EDI in mind. This allows EDI files to be analysed, split or merged, forwarded and processed according to EDI addressing and/or message type. ODEX Enterprise recognises all major EDI standards, including EDIFACT, EDIFACT v4, ANSI X12, UNGTDI and VDA. Every page and every dialog in ODEX Enterprise has a Help button, providing full context-sensitive on-line help. Generated using ODEX Enterprise 7

12 ComponentOne Doc-To-Help 6.5, the Help also provides full Index and Search facilities, navigation buttons and print function. Security and backup Besides integration with Windows NT security, ODEX Enterprise also offers its own security. This permits the setting up of a flexible user and user groups environment and the provision of passwordprotected access to ODEX Enterprise. The functionality available to each user is then based on the user privileges they have been allocated. For added data security, an automated database backup facility is provided. Product Architecture ODEX Enterprise makes use of an MSDE database to store details of business data. The files themselves are held in separate folders within the Data subdirectory of the ODEX installation directory. MSDE has been chosen for its robust, high-performance qualities. MSDE is also fully scalable to SQL Server for even greater performance, if necessary, and can then be incorporated into existing corporate back-up routines. 8 ODEX Enterprise

13 System specific-data, such as client settings, are held in configuration files. Database, file folders and configuration files should all be backed up regularly. System Requirements Hardware Pentium II 400 Mhz or equivalent 128 Mb RAM 50 Mb disk space for installation, but at least 200 Mb or more depending on the volume of file traffic. Software For ODEX communications, one of the following is required: CAPI 2-compliant ISDN card/router XOT-capable router Internet connection or dial-up modem To install and run ODEX, the following are required: Internet Explorer 6 or above (to be already installed) And one of the following: Windows XP and associated Service Packs Windows 2000 Windows 2000 Server Windows 2003 Server Other pre-requisites, such as the.net framework, are included on the installation disk and will be installed automatically if necessary. ODEX Enterprise 9