These best practices papers present advice on ways you can leverage IBM® InfoSphere™ MDM Server to satisfy key business requirements of master data management solutions. These articles are authored by leading experts in IBM's MDM development and services teams.

Each best practice paper is designed to provide practical guidance for the most common InfoSphere MDM Server implementation scenarios. By applying these recommendations, you may improve the value of your MDM solution and align yourself with IBM's technical direction for InfoSphere MDM Server.

Additional best practices articles are in development and will be published as they become available. To suggest a new best practices topic, please send your request to mdmsbp@ca.ibm.com.

• Integrate InfoSphere MDM Server for PIM with InfoSphere QualityStage to standardize product data (June 2011)
  by Amit Malla and Manasa Rao
  

  InfoSphere QualityStage is a component of IBM InfoSphere Information Server that can profile and standardize data, eliminate duplicates from data sources, and ensure survival of the best-of-breed records from a duplicate set. This article looks at a real-time integration between MDM Server for PIM and QualityStage to ensure quality of product data through standardization processes implemented in QualityStage.

• Implementing InfoSphere MDM Server for high performance (April 2011)
  by David Borean
  

  InfoSphere MDM Server was originally architected with performance and scalability as key requirements given the demands of the various styles of master data management implementations and specifically the centralized (or transactional) style. It is also important that implementations address performance proactively. This article details best practices on how to implement InfoSphere MDM Server for high performance and low CPU cost.

• Achieving high availability with IBM InfoSphere Master Data Management Server (October 2010)
  by Nick Kanellos and Dennis Shi
  

  Learn about strategies you can use to ensure that InfoSphere Master Data Management Server is available when it is needed. This article describes various IBM components that you can use together to ensure that InfoSphere MDM Server remains available to meet its commitments to provide timely, accurate, mission-critical data within an organization.

• InfoSphere Master Data Management Server installation (October 2010)
  by Dennis Shi
  

  Get all the details on best practices for installing InfoSphere Master Data Management Server in an environment with AIX® WebSphere® Application Server, and DB2® for Linux®, UNIX®, and Windows®. Learn how to make the installation go smoothly from preparing the environment, to installing all the components of the solution, to verifying the installation.

• InfoSphere Master Data Management Server security (October 2010)
  by Alex Jia and Miguel Ortiz
  

  InfoSphere Master Data Management Server stores or publishes a company's most important and sensitive data. The loss, corruption, or theft of this data can be devestating. Learn the best practices for securing the InfoSphere Master Data Management Server data and environment. This article provides guidelines and recommendations on topics you will encounter when you establish your security strategy.

• InfoSphere Master Data Management Server suspect duplicate processing (SDP) (October 2010)
  by John Baldwin, Stephanie Hazlewood, Charles Jia, and Lena Woolf
  

  Suspect duplicate processing is the process for searching, matching, and creating associations, or suspects, between existing parties in the system. These associations are made based on how well the parties match. At times you may want to merge these suspects into what has been termed a "single view" or the "golden record" for a party in InfoSphere MDM Server. This article provides considerations, recommendations, and strategies that you can use to put an effective suspect duplicate processing (SDP) solution in place in order to create a single, trusted record for a party in InfoSphere Master Data Management Server.

• Managing and promoting software changes in an InfoSphere Master Data Management Server team development environment (October 2010)
  by Karim Ladha, Lee McCallum, and Cristian Gheorghe
  

  This article presents best practices on how an InfoSphere Master Data Management server implementation team should manage the source of their solution and all artifacts derived from the source, such as generated code and deliverables. The term source refers to anything authored by team members that contribute to the difference between the default MDM Server solution and that which is installed in the production environment. That can include Java code, rule definitions, required configuration, and manual and automated scripts and processes.

• Monitor and tune InfoSphere Master Data Management Server, Part 1: Tune the MDM Server environment for high performance access to master data (October 2010)
  by Jesse Chen, Yongli An, and Adam Muise
  

  This article series provides guidelines on how to effectively monitor and properly tune each layer of the infrastructure in Infosphere Master Data Management Server by focusing on an IBM "Blue stack." The blue stack includes MDM Server, WebSphere Application Server, DB2 on AIX, and AIX operating system resources. For each layer, the article discusses a list of key parameters and variables that affect performance. It also offers detailed instructions on how to monitor, and it provides general recommendations on how to tune each layer.

• Monitor and tune InfoSphere Master Data Management Server, Part 2: Monitor the DB2 layer and learn about different monitoring tools (October 2010)
  by Jesse Chen, Yongli An, and Adam Muise
  

  Part 2 of this article series includes practical examples of monitoring MDM Server, along with a summary of all the recommended tools for your reference.

• MDM system performance testing: Guidelines and instructions (June 2011)
  by Yongli An
  

  Meet or exceed performance and scalability requirements for your InfoSphere MDM Server implementation. This article brings you the best methods for testing to prepare for a successful deployment.

Back to top