Behavior extensions

The following is a description of the changes to how InfoSphere® MDM uses and handles behavior extensions.

Before OSGi

Before the implementation of OSGi, you simply needed to package your behavior extensions in the InfoSphere MDM EAR and registered the extensions in the extension set tables in the database.

With OSGi

You must still configure the InfoSphere MDM Extensions database as you did before. However, using the OSGi framework, you cannot alter the EBA. You must include your custom extensions in your bundles. You must also register your extensions so the extension framework in InfoSphere MDM is aware of them. For each bundle containing extensions you’ve written, you must also supply the following OSGi blueprint:

<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" >
	<service id="Extension.Service.Factory"
		interface="com.dwl.base.extensionFramework.ExtensionServiceFactory" >
		<bean
			class="com.dwl.base.extensionFramework.ExtensionServiceFactoryImpl">
			<argument ref="blueprintBundle"/>
			<argument>
				<list >
					<bean class="your.extension.class_1" />
					<bean class="..." />
					<bean class="your.extension.class_N" />
				</list>
			</argument>
		</bean>
	</service>
</blueprint>

If you have generated your extensions through the MDM Workbench, this will be done for you.