Overview of OSGi migration

If you have customized InfoSphere® MDM without using the MDM Workbench, this content will help you migrate your InfoSphere MDM customizations to use OSGi.

Introduction to migrating InfoSphere MDM customizations to work with OSGi
InfoSphere MDM has numerous places where alternative implementations for a capability can be plugged in.
Parse request
When you invoke InfoSphere MDM, you must supply a java.util.Map type object describing the transaction context.
Response constructors
The final stage in any typical InfoSphere MDM transaction is to construct the response.
Get XSDs
The following is a description of the changes to how InfoSphere MDM uses and handles XSD files.
Construct business object (BObj)
During parsing, a business object is constructed and populated.
Code Types
Code type business objects have two parts: 1) The metadata business object which defines the database table and columns, which consist of the code type. 2) The business object (BOBJ) which represents a value (row) of a code type.
Business proxies
Business proxies are constructed based on the name of the transaction or its type (for example, persistent, inquiry, or search).
Get controllers and finders
The following is a description of the changes to how InfoSphere MDM uses and handles get controllers and finders.
External validators
The following is a description of the changes to how InfoSphere MDM uses and handles external validators.
Components - query and persistence factories
The following is a description of the changes to how InfoSphere MDM uses and handles query and persistence factories.
Spec Value Search
InfoSphere MDM enables you to customize spec search value capabilities with your own custom operators.
SearchResultSetProcessor customization
The following is a description of the changes to how InfoSphere MDM uses custom SearchResultSetProcessor.
Behavior extensions
The following is a description of the changes to how InfoSphere MDM uses and handles behavior extensions.
Service activity monitoring (SAM) extensions
OSGi affects some aspects of extending service activity monitoring (SAM) with a custom implementation in InfoSphere MDM.
External rules
This topic describes how InfoSphere MDM uses and handles external rules.
Suspect processing - searching and matching engines
The following is a description of the changes to how InfoSphere MDM uses and handles searching and matching engines.
Suspect processing: entity suspect processors
The following is a description of the changes to how InfoSphere MDM uses and handles entity suspect processors.
Custom object handlers for changed data detection
The following is a description of the changes to how InfoSphere MDM uses and handles custom object handlers for changed data detection.
Pluggable keys
The following is a description of the changes to how InfoSphere MDM uses and handles pluggable keys.
Phonetic key generators
InfoSphere MDM supports both NYSIIS and Soundex phonetic generators.
Notification types
Notifications are messages passed across the enterprise that can be used by one or more applications or consumers.
Notification channels
Each notification type is associated with one or more notification channels.
Response broadcasting
In addition to being able to receive each transaction response directly, the transaction responses can also be broadcast to any system that is listening.
Pluggable request response logger
The following is a description of the changes to how InfoSphere MDM uses and handles the request response logger.
Standardizers
You can configure your own party standardizers.
Security and transaction authorization providers
The following is a description of the changes to how InfoSphere MDM uses and handles security and transaction authorization providers.
Business key validators
The following is a description of the changes to how InfoSphere MDM uses and handles business key validators.
Guardium logging
The following is a description of the changes to how InfoSphere MDM uses and handles Guardium® logging.
Additions and extensions
Additions and extensions represent the most common type of customization that you can do with InfoSphere MDM.
Properties
InfoSphere MDM uses and manages properties in the OSGi framework.
Probabilistic Matching Engine object converters
The package com.ibm.mdm.eme.party.converter is no longer exported. The following is a description of the changes to how InfoSphere MDM uses Probabilistic Matching Engine object converters.

Parent topic: Platform and core feature overview

Related information

Upgrade of existing InfoSphere MDM development projects

Last updated: 19 November 2023