TIBCO MDM PRODUCT SUITE The TIBCO MDM product family includes the following software products:

Transcription

1 TIBCO MDM Overview INTRODUCTION TIBCO MDM ensures that your master data is consistent, complete, and accurate throughout your organization and among your partners. It provides four key capabilities to deliver a comprehensive approach to managing and synchronizing your master data: 1 Single Extensible Master Data Repository 2 Business Collaboration Management 3 Real-Time MDM 4 Analytics A multi-domain MDM system, TIBCO MDM is suitable for centralized authoring, collaborative workflows, and real-time transactional scenarios. It is positioned by Gartner, Inc. as a Leader in both 2014 Magic Quadrant for Master Data Management of Customer Data Solutions and 2014 Magic Quadrant for Master Data Management of Product Data Solutions. TIBCO MDM is based on a flexible business process automation framework that employs workflows and user-configurable business rules to streamline enterprise processes such as record modification, security, and new record introduction, synchronization, and publication. It works in conjunction with multiple, heterogeneous systems that affect or use master data information. It also automates global data synchronization with external trading partners through industry standard data pools such as 1Sync. The data stored in databases, text files, XML messages, or any other format used within your organization can be imported as master data that is then stored in user-defined repositories. The repositories define data syntax and semantics, and provide secure access to the data. You can manage master data using the user interface, web services, or asynchronous messages through JMS. You can define business processes and rules to manage information, including publishing information to other systems or trading partners.

2 WHITEPAPER 2 How TIBCO MDM fits within your operational ecosystem TIBCO MDM PRODUCT SUITE The TIBCO MDM product family includes the following software products: TIBCO MDM (MDM SERVER) This is the main engine that implements all of the MDM business functionalities, including user interface, integration, and data governance. TIBCO MDM combines an extensible master data repository and real-time data synchronization with a robust rules-based workflow engine. Out-of-the-box functionality includes support for multi-party, multi-tier collaboration among all parties that need to create, manage, and synchronize master data, enabling organizations to implement and start using the application quickly. TIBCO MDM STUDIO TIBCO MDM Studio delivers powerful process and meta-modeling capabilities that allow collaborative authoring of business processes and rules through a graphical user interface (GUI). This product is based on TIBCO Business Studio and installs as an add-in to Business Studio. MDM Studio comprises of three components: Process Designer, providing a GUI for designing workflow processes Repository Designer, providing a GUI for designing repositories, relationships between repositories, attributes, and attribute groups Rules Designer, providing a GUI for designing validation, cleansing, and governance rules with cross referencing to the repository model. UI builder, providing a GUI for rapid development of custom user interfaces tailored to specific business use cases. All the artifacts designed in the MDM Studio can be exported and managed in a version control system and hot deployed in MDM server. MDM Studio also provides support for importing metadata exported from the MDM server. MDM Studio is packaged as separate, versioned software and is licensed as part of the MDM server.

3 WHITEPAPER 3 TIBCO MDM Studio Repository Model MDM CONFIGURATOR MDM Configurator is a web-based tool used to configure the MDM server and enables centralized configuration for a cluster of servers through an intuitive user interface. This tool supports: Filtering of the configuration by categories Searching of configuration across all servers in the cluster Adding of custom configuration properties Designing wizards for creating and seeding of the new MDM database, configuring of new JMS queues, and migrating from older MDM versions. Configuration changes can be hot deployed. The configurator runs as a standalone application with a bundled web server. Typically, the server and configurator are packaged and installed together. MDM ANALYTICS TIBCO MDM Analytics allows the analysis of data stored in the database and a drill-down to launch the MDM UI to view and edit the master data. With MDM Analytics, users can analyze the operations data and determine the KPIs as well as review and ascertain the quality of master data. Based on TIBCO Spotfire, MDM Analytics retains all the functionalities of Spotfire, and custom applications can be developed. MDM Analytics is packaged as a separately licensed product.

4 WHITEPAPER 4 Sample visualization using TIBCO MDM Analytics TIBCO MDM ADMINISTRATION AGENT TIBCO MDM Administration Agent (TEA Agent) monitors MDM server(s) and reports status to TIBCO Enterprise Administrator (TEA) so that operators can view all servers, its associated components in a solution view within TEA. The data reported includes critical server health and performance indicators. TIBCO ACTIVEMATRIX BUSINESSWORKS PLUGIN FOR MDM This plug-in provides out-of-the-box integration with TIBCO Activematrix BusinessWorks(TM), making integration with other systems a snap. The plug-in supports common services for master data manipulation and status inquiry. TIBCO MDM ADD-ON FOR GLOBAL DATA SYNCHRONIZATION TIBCO MDM provides out-of-the-box connectors for 1Sync and SA2 data pools for product data synchronization. The plug-in provides for input data source configurations, repositories, classification schemes, validation rules, workflows, synchronizations profiles, and JMS queue configurations for out-of-the-box connectivity with the datapools. The TIBCO MDM Add-on for Global Data Synchronization supports supply-side as well as buy-side synchronization functionalities. The out-of-the-box templates can be easily extended to suit enterprise needs and support additional datapools. The Add-In also provides an out-of-the-box configuration for data synchronization between independent MDM instances. TIBCO CLOUD MDM TIBCO Cloud MDM is TIBCO MDM offered as a hosted service managed by TIBCO. It comes complete with templates for various data domains and integration with TIBCO Clarity and TIBCO Spotfire Cloud. For more details, visit cloudmdm.tibco.com.

5 WHITEPAPER 5 TECHNOLOGY TIBCO MDM is a pure Java application suitable for deployment on all the major application servers, including WebSphere, JBoss, and WebLogic. The following functions and technologies are supported by TIBCO MDM: Users interact with the application using a browser-based thin client. Supported browsers include Internet Explorer and Firefox. MDM manages all master data in a relational database (Oracle, SQL Server, or PostgreSQL) and is architected to allow concurrent read/write access to the same entity by multiple threads or users using the isolation level of READ_COMMITTED. UI screens are implemented using Enhydra XMLC, GWT, JQuery, and servlets. MDM can be accessed through either HTTP/HTTPS or SOAP WebServices; HTTP proxy servers are supported. MDM supports SSL for communication between the MDM server, browser/web service clients, JMS, and databases. MDM embeds a distributed cache, which allows the sharing of cached master data between multiple MDM instances. JMS is used to implement durable queues for asynchronous tasks and load distribution between multiple instances. It is also used for communication with other applications. TIBCO Enterprise Message Service and IBM WebSphere MQ are supported. Other JMS providers can be supported through a JNDI interface. Web Service Proxy Web Page JMS Managers (Listeners & Senders) Web Service Brokers (POJO) JAVA Servlets 2.3 XMLC Class HTML Sessions Beans EBJ 2.0 Distributed Cache Plain Old Java Object Data Access DAO Technologies used in TIBCO MDM

6 WHITEPAPER 6 MAJOR COMPONENTS The following diagram shows some of the major components of TIBCO MDM. MDM Server/Runtime Queues Message Brokers Web Services User Interface Operational Management MDM Analytics Messages Design Tools Configurator Workflow Engine Directory, Security, Authentication Core Engine Meta Data Management Workflow Activities Business Validation Engine Repository Management Engine TIBCO Enterprise Administrator Agent JMX Console Tools MDM Studio Routing Rule Engine Data Quality and Search Engine Caching Engine TIBCO ActiveMatrix BusinessWorks plug in TIBCO MDM Application Architecture METADATA MANAGEMENT The meta-model management component allows for the creation and maintenance of data model for master data repositories. The metadata changes are automatically reflected into the underlying physical data model to create or alter the tables and keys. The repository management engine uses the meta-model to dynamically create master data views and provide maintenance functions. The models can be built incrementally and changes can be hot deployed. The engine manages versions of master data and relationships of objects, snapshots of repository, and mappings of master data to external systems. A repository consists of attributes, which are logically grouped in attribute groups. Attributes can be of any of the following data types: Integer String Decimal and customized decimal File Timestamp Date Boolean Additionally, an attribute can also be defined as multivalued which means that it can have more than one value for a record. Attributes can also be defined as category specific, which means that they apply only when a record is classified in certain categories.

7 WHITEPAPER 7 Relationships can be defined between records in the same or different repository. Defined as both many-to-many and peer-to-peer, relationships can have attributes associated with them. A repository may be associated with one or more classifications that allows the records to be classified according to business needs. Attributes can be defined as category-specific, which means that they apply only if the records are categorized under certain classifications. As data models become complex with dozens of repositories and relationships, a perspective allows users to define a slice of the model relevant to the use case. Perspectives simplify the user interface and allow users to focus on the data model relevant to the task at hand. The mapping of a logical data model to a physical data model can be managed as part of the metadata by specifying the table and column names. REPOSITORY MANAGEMENT ENGINE The repository management engine supports all of the functionalities required to manage master data including: Data import and export Enhancements to data, including transformations, cleansing, and validations Functions to query, search, and view Capabilities to edit records, compare versions, view version history, reinstate older versions, and mass update All changes to data are versioned and audited, allowing inquiries of snapshot views over a certain period. Optionally, changes can be tagged with an effective date; such future dated versions become golden copy when the effective date arrives. Note that there can be more than one future-dated version that can be deleted or updated to reflect different future dates. As records can be browsed using classifications, they can be classified either automatically based on record data or manually assigned to a classification by the user. Data custodians can be assigned to review the changes based on their functional responsibility within the organization. Visibility and change control rules can be assigned at the record, attribute group, or attribute level. As data models can be changed at any time, all the master data management functions automatically adopt the changes in the meta-model without IT intervention. Data can be imported into MDM by defining data mapping from external data sources to repositories and relationships. The DBLoader mode allows very large sets of clean data to be imported quickly to seed the repositories. Data can be exported from MDM using synchronization profiles that use repository mappings in a format required by external systems. MDM can optionally maintain the data synchronization history and export only changed data. The data extractor framework allows the quick export of repository data through custom-defined criterion.

8 WHITEPAPER 8 BUSINESS VALIDATION ENGINE Users can design business rules to customize MDM according to their business requirements. MDM captures and consistently applies these rules using the Business Validation Engine. The rules are designed using MDM Studio Rule Designer, which uses a business user-friendly rule language and is integrated with meta-model and workflows. A rich vocabulary is provided to implement common rules as rule functions. Rules are organized in rule sets which can be nested for modularization and reused. Priorities, the ordering of rules, and the ability to execute SQL and links to other repositories, records, or datasources, are supported. The rule engine s capabilities can be extended by defining custom functions. Business rules can be hot deployed directly from the MDM Studio. Some use cases include: Validation and cleansing of records Rule-driven mass updates Rule-driven classification of records Enforcement of value-based security Fine-grain access control Message choreography Each repository is associated with various rulebases, which are comprised of a collection of rules that are invoked automatically depending on the use case (for example, adding a new record or modifying a record). Rulebases inherit context from the use case; for example, a rulebase has access to the user session, user roles, attributes of the task being performed, and steps in the workflow. Note that these rules can manipulate data across record hierarchies and relationships. Rulebases can also contain decision tables. Decision tables allow the specification of a large number of simple rules through an Excel-like user interface. A large number of workflow activities accept rulebase as input and apply it to the records being processed. CACHING ENGINE TIBCO MDM uses distributed cache for the following functions: Keeping the master data in memory for faster manipulation Distributed locking to synchronize data across multiple instances Remote invocation of object methods Temporary store for ephemeral objects, such as intermediate workflow state and work files To further optimize cache latency and network load, the caching engine implements three types of caches: Local cache, an on-heap cache designed for caching objects that do not have to be synchronized across other servers. Local cache is used for frequently updated objects that are updated on only one node in the cluster and are not required by other nodes in the cluster. Near cache, an on-heap cache that stores data that does not change often and does not require a lot of memory. A change to the data results in an update to all other copies of that data stored on other nodes. Used for infrequently updated objects that are read very frequently, near cache provides optimal read-time to negate a network hop and the overhead of data deserialization. Distributed cache, a non-transactional side cache to implement highperformance, shared distributed cache. Distributed cache is used for objects that: 1) can be updated and read from any node; and 2) require fault tolerance. Single cache is accessed from all the nodes in the cluster.

9 WHITEPAPER 9 The data that is stored in the database is not required to be present in the cache. If data is not in the cache, it will be loaded into the cache when needed. However, warm caching can be configured to preload most of the required data at startup. Depending on the available memory, parts or all of the data can be quickly loaded using multithreaded loading. Once the data is loaded in cache, MDM will attempt to retain it in cache and update it when the data has changed. MDM embeds TIBCO ActiveSpaces to implement distributed cache and supports various ActiveSpaces configurations, such as replication and eviction policies. MDM JVM 1 MDM JVM 2 Near Cache P2 Object P2 Distributed Cache P2 P3 Near Cache P2 Object P2 Local Cache Local Cache P1 Object P1 P1 Object P1 Database Different types of caches used in TIBCO MDM A typical cache interaction works as follows: Clears any previously cached image when data is being modified Inserts/updates data into database and commits the data Either caches data immediately or when requested for the first time USER INTERFACE (UI) A comprehensive UI is provided to manage all aspects of MDM, supported by functionalities that allow system administrators to see every aspect of the system and for the business user to define, find, view, and approve master data. The UI can be customized based on the roles assigned to users. The UI supports all of the functions for application administration related to users, roles, permissions, event logs, etc. It also supports the functions of work supervisors who are able to assign work to other users and review their work. As the data models are created as per the enterprise needs, the UI adapts to the data model, and any change to the data model is automatically reflected in the UI. The UI can also be customized by changing the look-and-feel and by replacing some of the screens and terms. XML-based specifications allow for further customization and the grouping of the UI elements. Using the UI Builder module in MDM Studio, fully functional customized screens can be designed and hot deployed to the MDM server.

10 WHITEPAPER 10 Design your own customized user interface in MDM Studio Customized user interface for Add/Edit Customer information Implemented using MVC pattern, the user interface is localized and supported in multiple languages. WORKFLOW ENGINE The workflow engine provides full-featured workflow capabilities including failover and load balancing and is integrated with repositiory management engine s event-based architecture to track changes to the master data. An MDM event is a significant change that could create one or more processes. Each process in turn can have one or more sub-processes which can create more events and so on. Each process is mapped to a workflow, and subflows are independent workflow units that inherit context from the parent workflow and run synchronously. Workflows allow for human intervention by creating work items and can execute synchronously or asynchronously. The workflow engine supports timeouts, fork-and-join, exception handling using error transitions, sub-flows, and the chaining with and spawning of other workflows. From the UI, users can view all of the workflows, the steps in the workflow, and the input and output of each step.

11 WHITEPAPER 11 Any of the workflows can be configured to run as a single transaction, commit after each activity, or commit at designated checkpoints. Workflows can also run in-memory with no or delayed state persistence and with user-defined checkpoints after a set of activities to provide high throughput. Workflow definitions are created using MDM Studio and exported as XML to the MDM server, then hot deployed directly from MDM Studio. MDM workflow supports: Automatic workflow selection based on request parameters Integration of workflow engine with routing rules based on workflow context Predefined activities to perform operations on master data with inclusion of custom activities Work items assigned to users, work item locking, timeouts based on various algorithms, reassignment, delegation profiles, and role of work supervisor Selection of work item participants using various algorithms including contextaware rules Customizable work item forms and a large number of pre-defined forms and templates Suspend, resume, and restart based on external event, timeout, or user intervention Resubmit, undo, forced restart, and cancel Fork-and-join Spawning of new workflows and subflows initiation Running workflows in various degrees of persistence and caching (in-memory, partially in memory, or commit after each activity) Automatic load balancing across cluster and handling of subsystem failure without loss of data (for example, database failure) Configurable priority for workflows initiated for different tasks and from different sources WORKFLOW ACTIVITIES Large numbers of pre-defined workflow activities implement various business functions that manipulate the master data. For technical tasks such as send , or execute a script, many technical activities are also provided. Custom activities can also be added. Most of the activities are coarse-grained and perform a business function such as validating and confirming records and importing data. Each activity is an atomic operation unless the workflow itself is configured to run as a single transaction. Activities that process batches of data typically split the batches into smaller batches to process the data in parallel, with JMS being used to distribute the workload across the cluster. The output of all batches is collated by the activity. DATA QUALITY AND MATCHING ENGINE TIBCO MDM detects duplicate records based on automated duplicate detection policies or through human intervention and allows such duplicates to be merged to create master records. The duplicate detection is through fuzzy or exact query supported by a matching engine based on the TIBCO Patterns technology. The matching is done by selecting attributes to match and by assigning weights to each attribute. The matching and de-duplication of records can be done in bulk and through scheduled jobs.

12 WHITEPAPER 12 MDM maintains the matching, merging history, and linkage(s) of the merged data with their source records. Records can be searched from the UI using parametric search or Google-like text search that is powered by an embedded TIBCO Patterns search engine. As records are added or modified to MDM, the system automatically creates indexes in the search engine. Interfaces with external data quality tools, including Trillium, are supported. WEB SERVICES A large number of web services are available to expose the MDM functionalities as APIs. The web services that initiate workflows can execute either: 1) asynchronously, in which case the web service is returned as soon as an event is created and the workflow has been submitted; or 2) synchronously in which case the web service waits the for workflow to complete. Using MDM Studio, CRUD web services for a repository or perspective can be generated to provide a tight schema specific to the repository model. Such generated web services can be hot deployed. ROUTING RULES ENGINE Approval and workflow routing rules to assign work items can be defined using the UI and hot deployed. These rules, which can be defined based on workflow context, allow the customization of workflows by business users without requiring changes to the workflow configuration. MESSAGE BROKERS Message brokers support the processing of messages as they are received or sent by MDM. This pipeline is flexible and extensible to support any message format and destination and can be used if other EAI tools are available. ADMINISTRATION AGENT Administration agent allows MDM server to be managed through TIBCO Enterprise Administrator by an operator or system administrator. Using TIBCO Enterprise Administrator user interface, users can see all MDM servers, its database(s), TIBCO Patterns servers, caching engines, and JMS servers used in the MDM solution. User can start, stop, suspend, or resume the MDM server, check critical performance indicators like cache hit ratio, workflow execution stats, and various configurations. TIBCO ACTIVEMATRIX BUSINESSWORKS PLUGIN FOR MDM The MDM plug-in makes adding MDM to an enterprise services bus (ESB) as simple as drag and drop. Using the plug-in, application designers can invoke MDM services through Activematrix BusinessWorks no-coding designer and speed up integration with the rest of the enterprise. Key services supported are import and upload, read and add/modify master data, get event status, and others. FUNCTIONALITY Additional functionalities provided by the server include: MULTI TENANCY A single MDM instance can support more than one enterprise, which is typically one independent organization with its own set of workflows, rules, metadata, and master data. There is very little sharing of information between enterprises except by messages since strict data isolation is enforced between enterprises. Users are defined for one enterprise and can access only one enterprise. Multiple enterprises can be defined within a single MDM instance with all the enterprises sharing the same JVM instance.

13 WHITEPAPER 13 AUTHENTICATION, USERS, AND ROLES Users can be defined within MDM or through other systems that are linked to MDM. Out-of-the-box integration is provided with LDAP and many single sign-on products. The integration with external authentication managers is implemented using plug-in login modules. Integration with new authentication managers may need the development of a new plug-in; in most cases, however, an existing plug-in can be configured to work with a variety of systems. In all cases, comprehensive user profiles are managed in MDM. The mapping of external roles to MDM roles is supported with options to automate the synchronization of assigned roles and user information. MDM also supports the auto-creation of users on first login and flexible configuration-driven integrations with various industry standard security managers. Users, roles, and permissions can be exported from one instance and imported into another. META-MODEL MANAGEMENT Though MDM provides some pre-defined meta-models as implementation accelerators, most of the implementations custom-build their meta-model. Metamodel is a combination of objects that define: Repository structure and relationships between data entities Validation, cleansing, and matching rules Data sources to represent external input sources Catalog formats to represent external consumers Synchronization profiles to define how data should be synchronized with external consumers MDM Studio is the main tool for managing metadata and includes repositories, attributes, attribute groups, perspectives, data sources, synchronization formats, and input and output maps. All metadata changes are versioned and can be hot deployed without requiring any outage. An export wizard allows the export from an MDM instance to be imported in other instances with fine-grain control over which objects to export or import. This is how most TIBCO MDM customers manage metadata in their production systems. The underlying data model is published to allow various reporting and data extraction tools to read data from the database. INBOX AND WORKFLOW The inbox is the starting point for most users as it presents their work items and lets them manage their assigned work. Users can view, close, submit, reassign, or cancel work items and reserve a work item by locking it when it is assigned to more than one user. Work items can be categorized by user-defined hierarchies ( preferences ). Work supervisor functions allow a user to balance the workload for other users and to override user actions. The inbox can be customized for each user and custom work item forms can also be added. Workflow templates for most common tasks (such as a new record introduction) are provided. DATA GOVERNANCE All changes to records are versioned, and unless exempted for a user, require a workflow to be executed. Workflows implement organizational data governance policies, and changes go through various states including draft and unconfirmed, before becoming confirmed. Confirmed records are immutable and are considered the golden copy. Data governance includes security, approvals, validation and cleansing, synchronization with external systems, and tracking of all changes. Regardless of how a change is initiated via UI, batch file, web services, JMS messages the same data governance policies can be applied.

14 WHITEPAPER 14 MULTI-DOMAIN REPOSITORY ENGINE The repository management engine supports multi-domain master data management by interconnecting repositories through relationships. Relationship hierarchies can be accessed from any node and traversed along relationships. All MDM functions including workflow and validation rules are aware of multi-domain metadata and can act on it. The multi-data domain support is enabled by the horizontal MDM platform that is agnostic to any vertical. For example, the same MDM instance manages customers, vendors, products, banks, addresses, accounts, and all the relationships between them. This capability differentiates TIBCO from other MDM solutions that support only a single data domain (for example, customer). RELATIONSHIPS MANAGEMENT Records are bundled together through relationships and the hierarchies between relationships allow for data validation and cleansing across the hierarchy and the propagation of data between records. Bundles can optionally be manipulated together through import, export, validation, modification, creation, and deletion, among other functions. This allows data governance rules to be enforced for the entire record hierarchy. Between master data records, MDM supports many-to-many relationships, and they can be between the records in the same repository (customer to customer) or between records in another repository (customer to bank). The relationships are managed as peer-to-peer or bi-directional and in both forward and reverse directions. Relationship attributes are maintained and manipulated similar to record attributes by all functions including the import and export of attributes. Note that relationships can have attributes that apply to a relationship instance. The record search capabilities allow for the searching of records across repositories based on the values in the records across a relationship and/or values in relationship attributes. INPUT AND OUTPUT METHODS Data input and output can occur through any of the following channels: Batch file upload/export UI Web services JMS messages Message Incoming Message Queue JMS Web Services Workflow Queue Listeners Data Process Bulk Load Receivers Outgoing Message Queue Bulk Load User Interface Messages Work Items Input and output methods of TIBCO MDM

15 WHITEPAPER 15 INSTANCE-TO-INSTANCE SYNCHRONIZATION An MDM instance can be configured to synchronize data with other MDM instances, allowing remote instances to sync with each other s data and support any data segregation mandated by local laws. WEB SERVICES MDM allows all master data to be searched and manipulated using web services such as: Create, modify, validate, delete, and search record hierarchies Import records using various methods Search records using fuzzy search Metadata management services support the inquiry of metadata, export, and import of metadata and obtain lists of deployed workflows and rulebases. Any work items assigned to users can also be manipulated using the following web services: Close one or more work items Lock, unlock, or relock work item Search and retrieve a list of work items Reassign work items Get a summary of work items Administrative web services include: Inquiry of event status and associated details Inquiry of entitlements to user Creation, modification, and inquiry of a list of users Creation of a new company or lists of companies Login and logout SECURITY MDM supports multiple security models, including: Role-based security. Coarse-grained function access can be controlled by defining and granting appropriate roles to users. ACL-based. Access control lists (ACLs) can be attached to most of the objects (repositories, records, and attribute groups, among others) to secure the operations on objects. Rule-based. Rules can be defined to apply security based on context, including workflow activities (for example, which activity is executing), user actions (add, modify, delete), and attribute values (such as, price > $1,000). AUDITING AND LOGGING All changes to master data are logged by creating events. For each event, detailed audit trace is maintained to allow a full review of all changes. All eventrelated information can be viewed and searched from the UI. Control is provided to manage the amount of data being logged for tracing and debugging. JMX interface allows for the inquiry and control of cache, HTTP sessions, configuration, and workflows. MDM can be configured to run in debug mode with a penalty of a ~15% decrease in throughput. Debug information is logged using Log4J.

16 WHITEPAPER 16 CONFIGURATION To allow extensive customization, a large number of configuration properties can be defined and MDM Configurator allows all such properties to be managed using a UI. Most of the configuration changes are hot deployable, with the configuration of whole clusters managed centrally. Changes are automatically backed up and can be restored to an older state. Multiple wizards simplify complex tasks, such as setting up an integration queue with an external system. FAILOVER, CLUSTERING, AND LOAD BALANCING Clustering is supported, while load balancing of HTTP requests can be implemented using the web server s round robin DNS lookup or some other load balancing software or hardware. Fine-grain control of load balancing is enabled by the ability to configure the number of dedicated processing threads for each channel per server. Failover for workflows and background processes is supported by shared message queues and workflow queues. The queues are shared by all members in a cluster so that failure by one member of the cluster does not affect the processing of queued tasks. Temporary failures of databases, JMS, file systems, networks, and other subsystems are gracefully handled without any loss of messages/data and do not require server restart. Permanent failures are detected, and processing is transferred to other members in the cluster. APPLICATION PARTITIONING To support large numbers of users and records, the MDM cluster can be partitioned along with database partitions, allowing the application to scale linearly. Application partitioning is currently supported for Oracle databases only. OPERATIONS Extensive JMX MBeans provides information about the configuration, alerts, and status of various components including the performance of workflows, rules, and message processing. The MDM server can be configured to generate notifications over JMS for changes to records, work items, and repository structure. These notifications allow an external monitor to listen to the changes in metadata and records. MDM also captures information about the execution time for various components and can log to a file for later analysis. Data purge allows for a clean-up of history or records that are no longer required as per the retention policy of the organization. A bundled scheduler can be used to schedule periodic tasks including purge. The undo function lets users undo changes to the master data.

17 WHITEPAPER 17 DEPLOYMENT A typical high-end production deployment is illustrated below. Depending on the throughput requirements and SLA, one or more of the software products can be co-located, reducing the hardware footprint. Application Server Disk Array MDM Application Server Cluster MDM Cache Servers BW Engine (with MDM plug in) TIBCO Enterprise Administrator MDM Webserver MDM JMS Cluster MDM Database Cluster Database Disk Array Advanced Search Engines TIBCO MDM: Typical high-end deployment topology UPGRADE Upgrading from one MDM version to another typically requires upgrading the database schema and configuration. The configuration and database wizard integrated with the MDM Configurator simplifies and automates the upgrade process. Backward compatibility is maintained from previous versions including workflows, XML schema, rules, and features. SUPPORTED PLATFORMS OPERATING SYSTEMS Solaris Red Hat Linux Microsoft Windows HP UX APPLICATION SERVERS WebSphere WebLogic Application Server JBoss MESSAGE SERVERS TIBCO Enterprise Messaging Service IBM WebSphere MQ DATABASES Oracle PostgreSQL Microsoft SQLServer

18 WHITEPAPER 18 WEB SERVERS IBM HTTP Server Apache Server Any other compatible web server WEB BROWSERS Internet Explorer Firefox Chrome Safari For a complete list of all supported platforms and combinations, please contact TIBCO Support at FOOTPRINT Development can be done on a laptop that has all the components installed, including the database. The minimal requirements for a low-end production environment include a single dual-core Intel box running Windows or Linux. The minimum JVM heap requirement is 256 MB for development, 512 MB for user acceptance testing, and 1 GB for production. Additional memory is required for caching and search engines; more may be needed depending on the number of records. Capacity planning worksheets are provided. Depending on the OS platforms, the installation disk image size ranges between 150 to 220 MB for the MDM server and approximately 450 MB for MDM Studio. Global Headquarters 3307 Hillview Avenue Palo Alto, CA TEL FAX TIBCO Software Inc. is a global leader in infrastructure and business intelligence software. Whether it s optimizing inventory, cross-selling products, or averting crisis before it happens, TIBCO uniquely delivers the Two-Second Advantage the ability to capture the right information at the right time and act on it preemptively for a competitive advantage. With a broad mix of innovative products and services, customers around the world trust TIBCO as their strategic technology partner. Learn more about TIBCO at , TIBCO, TIBCO Software, ActiveSpaces, and TIBCO Business Studio are trademarks or registered trademarks of TIBCO Software Inc. in the United States and other countries. All other product and company names and marks in this document are the property of their respective owners and mentioned for identification purposes only. 01/06/15