Technical Overview Enterprise Server 2.0
Enterprise Server Architecture The Enterprise Server (ES) platform addresses the HVTO business challenges facing today s enterprise. It provides robust, flexible and highly scalable solutions that optimize an organization s information supply chain by integrating enterprise systems and data. Line of Business Applications ES enables organizations to achieve their strategic objectives by supporting enterprise information extraction, transformation, repurposing, personalization and delivery for both structured and unstructured data and documents. Enterprise Server provides a scalable architectural framework on an integrated Enterprise Java platform simplifying integration with third-party applications and technology solutions. With its Java-based, multi-threaded architecture, ES is designed to process millions of transactions each with sub-second performance. Enterprise Server HVTO Document Composition IDARS/ERM ECM CRM/BPM Legacy/ERP Trading Partners Events SOAP ebxml Messaging Services Processes Transformation Engines Print Stream Documents Structured Data Process Flow Engine Process Flow Custom Components Process Flow components Routing Job Scheduling Clustering Job Monitoring Axess TM PDF Accessibility Enterprise Server Engine Integration Components Command line process Document composition ERM/ECM loaders Print services Process flow components Custom integration API Engine Monitoring Logging CEVAs ES Developer Studio ES Administrator Console Configuration Repository Check-in/Check-out Solution Promotion Application Server Repository Services Interface IBM Content Manager OnDemand IBM Net Image Services IBM Net P8 EMC Documentum Repository Adapter API ES Engine: provides scheduling, logging, monitoring, clustering, failover, load balancing and error-handling to ensure reliability, fault tolerance and high availability. Job Scheduling: allows for process flows, components and events to be scheduled to run during specific times. Businesses that run nightly batch jobs can allow jobs to queue up during the day and then get executed in a lights-out operation. Job Monitor: initiates a process flow if a component or process flow hasn t run within a specific time period, notifying users that an event that should have processed has not and should be reviewed. Logging System: provides the option of either a single log for all messages or granular logging for each component in the process flow. Multiple logging levels allow control of the amount of detail needed for debugging with streamlined logs for use once in production. Page 2
Clustering: enables ES to run either on a single server or within a cluster to provide high availability, failover and load balancing. Failover: provides built-in failover capabilities independent of the application server it is running on. This ensures jobs will continue to be processed in the event of a catastrophic failure of a ES server either on its own or within a cluster. Load Balancing: delegates jobs across the cluster for even distribution of work among the ES servers. The monitoring system collects statistics for use within the Administration Console thin-client, the Developer StudioTM dashboard or a custom application through web services. Statistics are collected for each node of the server and include: Cluster load Memory usage per server Job run times Currently running jobs Job failure rate Enterprise Server Input Events Enterprise Server eliminates the challenges of integrating data and documents between multiple disparate applications. It provides the interfaces required to enable communication between incompatible technologies and systems. Input events can be configured to initiate a process or process flow. This in turn runs through a series of processes and components that implement the required business logic. The input events include: / Microsoft Message Queue () ES ES ebxml Messaging Services The ES ebxml Messaging Service is a set of components within ES built on OASIS open standards. It enables the consistent, reliable and secure point-to-point exchange of data over the Internet with non-repudiation. Driven by industry standards, these components make secure data transport a straightforward business operation, not a service-based, high-priced, complex chore. Process Flow Engine The ES Process Flow Engine allows business logic and technical functions to be executed within a process flow that can contain components and other process flows as sub-processes. There are six different types of components, or processes: 1. Transformation Engines: used to manipulate data and documents 2. Routing: used to determine the course of action to take based on conditions such as the value of job variables or content types Page 3
3. EDI: Used for Electronic Data Interchange (EDI) processing and messaging 4. Processes: used for communicating with external systems 5. Integration Components: Used for integrating with external systems 6. Custom: used to create Java components to perform specific business and technical functions Error Handling There are several ways to handle an error that may occur in a process flow. They include: Catching the error within a subset of your business logic and invoking a process flow to handle it. Catching the error within the whole of your business logic and invoking a process flow to handle it Catching the error within the individual components and handling it Transformation Engines Built upon technology used in production by hundreds of customers worldwide, the Transformation Engines offer the extraction, transformation and repurposing of both structured and unstructured data as an enterprise service for SOA environments. Print Stream Documents Enterprise Server Document Transformation Service transforms and repurposes documents from print streams into electronic formats. High volumes of documents are indexed, transformed and repurposed into a variety of business-critical applications for enterprise report management (ERM) and enterprise content management (ECM) archiving, retrieval, presentment and delivery. Structured Data Enterprise Server Data Transformation Service efficiently transforms, translates, and intelligently routes a variety of structured data formats over the Internet and between disparate systems and applications. This enables the real-time, high-volume exchange of electronic data with greater adaptability to changing business requirements between internal systems and external trading partners. Integration Services With Integration Services, functionality within external applications can be leveraged within a process flow. This can be achieved by components written by Professional Services, a Java developer or out-of-the-box components including: Command line process Any native application that can be started from the command line Document Composition EMC Document Sciences xpression ERM/ECM loaders infoweb for secure report delivery or online presentment. It can also be used within the Integrated Document Solution Page 4
IBM Net P8 Loader component to load high volumes of content, documents and images along with their associated metadata/indexes into IBM Net P8 Print Services Levi, Ray & Shoup, Inc. (LRS) VPSX Print Process to send print requests to the LRS VPSX Server for routing to printers, fax and email. Java Print Service to send print requests to a printer or print server Process flow components Any components used within a process flow Custom integration API Write your own integration component using the Repository Services Interface Request Enterprise Server IBM Content Manager OnDemand IBM Net Image Services IBM Net P8 EMC Documentum Other repositories The ES Repository Services layer provides a common way of accessing content residing in external repositories. Process flows can access content through Repository Service Adaptors; external applications can also access content stored in repositories through a. The actual communication with the various repositories is performed through Repository Services adapters which enable: Searching repositories Querying index names and types of folders Getting hit lists from repositories Retrieving content from repositories Loading content into repositories Retrieving and caching resources ES Repository Services can connect to various industry-leading ECM systems such as: IBM Content Manager OnDemand IBM Net P8 IBM Net Image Services EMC Documentum Additional repository adapters can be developed through the ES API for any database, archive or IDARS/ERM/ECM system by a Java developer or Professional Services. Enterprise Server Output Processes In addition to the repository services connectors and integration components, ES also has output processes that use standard communication protocols. These output processes are typically used for sending resultant data, archiving original data and for notification should something go wrong. The interfaces included are: ES / Microsoft Message Queue () ES Page 5
Configuration Repository The ES Configuration Repository enables organizations to store all of their Process Flows, project configurations and resources in a single place to be used by ES or a cluster of ES instances. This information can then be easily deployed across multiple systems from within the Developer Studio for development, testing, staging and final production. The configuration repository enables the collaboration between team members on a project with a single point of deployment to an entire cluster. The version control allows versioning of project resources and the ability to rollback to a previous version or label across the entire repository. To migrate from a testing environment to a production environment, migration options are available to pull all resources of a specific version to another configuration repository. With the click of a button, an entire solution can be promoted from one environment be it development, testing or staging to any other environment. Solutions can be demoted or rolled back just as easily. The configuration management functions are accessible within Enterprise Server Developer Studio or from within your own custom application using web services. Axess for PDF Accessibility The Axess solution is built on Enterprise Server to produce high-volume PDF documents that are accessible, using assistive technology, and usable by visually-impaired customers. Axess integrates with an organization s existing enterprise content management (ECM) infrastructure to capture high-volume print streams, identify tables, sections, fields and images and add alternate text and the appropriate tags to output them as accessible PDF documents for online presentment. With this solution, organizations can ensure that any statement or transaction-oriented document generated can be accessible on demand to every customer, reducing the need for outsourced document accessibility services. Developer Studio Developer Studio is a platform-independent Configuration, Deployment and Control Graphical User Interface (GUI), simplifying the process of defining and maintaining process flows, components and projects. It is the single user interface to configure, create and administer all aspects of a ES environment, including data and document transformation. With its drag-and-drop interface, Developer Studio eliminates the need to hand-code unique business logic while reducing reliance on developers with domain expertise. Rapid deployment of complex projects is enabled with the following features: Ability to test as you build process flows or components Process flow debugger Custom component builder Embedded Java IDE Server deployment, configuration and monitoring Page 6
Business Overview - Enterprise Server Administration Console Enterprise operations need to be able to monitor systems without having to log on to the server or having Developer Studio installed. From a thin-client interface, administrators can: Start and stop events on a server or in a cluster View server information Monitor the running jobs, the cluster load, memory usage, and job statistics. Job statistics can be exported to an MS Excel spreadsheet for reports, tracking or trend analysis. s Interface Developers can also perform a number of tasks outside of the Administration Console or Enterprise Server through the s Interface.Through the s Interface, developers can: Perform all activities of the Administration Console Perform all of the communication with the Configuration Repository Access any of the functions on any of the repositories defined within the Repository Services Interface Server Requirements Operating Systems: Windows (32 and 64-bit) Linux (32 and 64-bit) Solaris AIX HP-UX IBM z/os (running USS) Minimum server configuration: Multi-CPU Application Server 2GB RAM JDK 1.5 required DB Support for Configuration Repository: MySQL 5 Oracle 11g MS SQL Server 2005 Recommended server configuration: Multi-CPU Application Server 4GB RAM JDK 1.5 required Database ES can be deployed to: JBoss 4.2.2 and 5.0 IBM WebSphere 5.x, 6.x and 7.0 WebLogic 8.1, 9.0 and 10.x Oracle Application Server 10g Clustering is supported on: JBoss 4.2.2, 5.0 IBM WebSphere 6.x and 7.0 WebLogic 9.0 and 10.x Minimum desktop configuration: Single CPU 1.5GHz 1GB of RAM JDK 1.5 required Learn more about the Business and IT solutions delivered by Enterprise Server www.xenos.com tel: 1 (888) 242-0692 email: info@xenos.com Copyright 2011 Actuate Corporation. All rights reserved. Actuate and the Actuate logo are registered trademarks of Actuate Corporation and/or its affiliates in the U.S. and certain other countries. All other brands, names or trademarks mentioned may be trademarks of their respective owners. UK & Europe North tel: +44 (0) 1932 252 299 www.xenos.com/xe/europe France & Europe South tel: +33 1 47 14 00 96 www.xenos.com/xe/france