MDM Implementation styles

Implementation styles

Custom transactions can be implemented in two different ways, either as a business proxy transactions or as component transactions. These styles correspond to adding the custom logic at different points in the InfoSphere MDM request handling process.

Business proxy transactions add logic just before the controller level. They call other transactions at the controller level, but they cannot call other business proxies. Business proxy transactions can only call other transactions at the controller level and cannot call other business proxies.

Business proxy transactions have the following properties:

• They can add logic just before the controller level.
• They only call other transactions at the controller level.
• They cannot call other business proxies

Component transactions are called at the component level. Component transactions can only call other transactions at the component level and can call other custom component transactions.

Component transactions:

• are called at the component level
• can only call other transactions at the component level
• can call other custom component transactions

The distinction between calling transactions at the controller level and the component level is important when calling the out-of-the-box transactions since some of them have different semantics at the controller level. In general, for transactions with both coarse-grained and fine-grained variants, the coarse-grained variant is only available at the controller level.

Naming Unresolved Binding Exception

[4/16/15 19:35:13:628 EDT] 0000000b EJBInjectionB W   CWNEN0033W: The com.ibm.mdm.admin.services.batch.management.controller.BatchDaemonTxnLocal interface, which is specified for the <ejb-ref> or <ejb-local-ref> tags, cannot be found.
[4/16/15 19:35:13:631 EDT] 0000000b EJBInjectionB W   CWNEN0033W: The com.ibm.mdm.admin.services.batch.management.controller.BatchDaemonTxnLocalHome interface, which is specified for the <ejb-ref> or <ejb-local-ref> tags, cannot be found.
[4/16/15 19:35:13:631 EDT] 0000000b WSServerImpl  E   WSWS1000E: Error: Service ref's already bound to Web service client!
[4/16/15 19:35:13:633 EDT] 0000000b WebServiceRef E   WSWS7238E: Web service references specified in the DWLCommonServicesEJB.jar module in the MDM application could not be correctly processed due to the following error com.ibm.ws.webservices.configuration.WASWebServicesBindException: WSWS1000E: Error: Service ref's already bound to Web service client! .
[4/16/15 19:35:13:673 EDT] 0000000b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files (x86)\IBM\SDP\runtimes\base_v7\profiles\AppSrv03\logs\ffdc\server1_4e274e27_15.04.16_19.35.13.6336307149237009717693.txt com.ibm.ws.injectionengine.InjectionEngineImpl.processAnnotations 300
[4/16/15 19:35:13:675 EDT] 0000000b InjectionEngi E   CWNEN0009E: The injection engine failed to process the XML code from the deployment descriptor.
[4/16/15 19:35:13:677 EDT] 0000000b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files (x86)\IBM\SDP\runtimes\base_v7\profiles\AppSrv03\logs\ffdc\server1_4e274e27_15.04.16_19.35.13.6767248495002423845469.txt com.ibm.ws.util.ComponentNameSpaceHelper.populateJavaNameSpace 640
[4/16/15 19:35:13:678 EDT] 0000000b ComponentName E   CNTR0125E: Unable to process injection information for class: [class com.dwl.base.requestHandler.beans.DWLServiceControllerBean].
[4/16/15 19:35:13:997 EDT] 0000000b FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files (x86)\IBM\SDP\runtimes\base_v7\profiles\AppSrv03\logs\ffdc\server1_4e274e27_15.04.16_19.35.13.6793129411498434226304.txt com.ibm.ws.metadata.ejb.EJBMDOrchestrator.finishBMDInit 810
[4/16/15 19:35:13:999 EDT] 0000000b EJBMDOrchestr E   CNTR0035E: EJB container caught com.ibm.wsspi.injectionengine.InjectionConfigurationException: Failed to process xml from Deployment Descriptor
at com.ibm.ws.injectionengine.InjectionEngineImpl.processXML(InjectionEngineImpl.java:456)
at com.ibm.ws.injectionengine.InjectionEngineImpl.processInjectionMetaData(InjectionEngineImpl.java:313)
at com.ibm.ws.util.ComponentNameSpaceHelper.populateJavaNameSpace(ComponentNameSpaceHelper.java:806)
at com.ibm.ws.util.ComponentNameSpaceHelper.populateJavaNameSpace(ComponentNameSpaceHelper.java:519)
at com.ibm.ws.metadata.ejb.EJBMDOrchestrator.finishBMDInit(EJBMDOrchestrator.java:1864)
at com.ibm.ws.runtime.component.EJBContainerImpl.finishDeferredBeanMetaData(EJBContainerImpl.java:5036)
at com.ibm.ws.runtime.component.EJBContainerImpl.initializeDeferredEJB(EJBContainerImpl.java:4845)
at com.ibm.ejs.container.HomeOfHomes$1.run(HomeOfHomes.java:406)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:403)
at com.ibm.ejs.container.HomeOfHomes.internalCreateWrapper(HomeOfHomes.java:991)
at com.ibm.ejs.container.EJSContainer.createWrapper(EJSContainer.java:5024)
at com.ibm.ejs.container.WrapperManager.faultOnKey(WrapperManager.java:545)
at com.ibm.ejs.util.cache.Cache.findAndFault(Cache.java:498)
at com.ibm.ejs.container.WrapperManager.keyToObject(WrapperManager.java:489)
at com.ibm.ejs.oa.EJSOAImpl.keyToObject(EJSOAImpl.java:553)
at com.ibm.ejs.oa.EJSRootOAImpl.keyToObject(EJSRootOAImpl.java:271)
at com.ibm.rmi.corba.ObjectManager.lookupServant(ObjectManager.java:104)
at com.ibm.CORBA.iiop.ServerDelegate.getServant(ServerDelegate.java:312)
at com.ibm.rmi.iiop.ORB.lookupLocalObject(ORB.java:601)
at com.ibm.CORBA.iiop.ORB.lookupLocalObject(ORB.java:1468)
at com.ibm.rmi.iiop.CDRReader.newObjRef(CDRReader.java:1307)
at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:1147)
at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:1111)
at com.ibm.rmi.corba.IorURL.iorbytesToObjref(IorURL.java:105)
at com.ibm.rmi.corba.IorURL.resolve(IorURL.java:93)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3748)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3262)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3649)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolveUnresolvedBinding(WsnOptimizedNamingImpl.java:1927)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolve_binding(WsnOptimizedNamingImpl.java:1681)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:583)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:2163)
at com.ibm.WsnOptimizedNaming._NamingContextImplBase._invoke(_NamingContextImplBase.java:286)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)
at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: com.ibm.wsspi.injectionengine.InjectionException: WSWS7238E: Web service references specified in the DWLCommonServicesEJB.jar module in the MDM application could not be correctly processed due to the following error com.ibm.ws.webservices.configuration.WASWebServicesBindException: WSWS1000E: Error: Service ref's already bound to Web service client! .
at com.ibm.ws.websvcs.annotations.injection.WebServiceRefProcessor.processXML(WebServiceRefProcessor.java:280)
at com.ibm.ws.injectionengine.InjectionEngineImpl.processXML(InjectionEngineImpl.java:446)
... 42 more
 and is throwing com.ibm.ejs.container.ContainerException: Failed to initialize BeanMetaData instance; nested exception is:
com.ibm.wsspi.injectionengine.InjectionConfigurationException: Failed to process xml from Deployment Descriptor.
[4/16/15 19:35:14:000 EDT] 0000000b EJBContainerI E   WSVR0068E: Attempt to start EnterpriseBean MDM#DWLCommonServicesEJB.jar#DWLServiceController failed with exception: com.ibm.ejs.container.ContainerException: Failed to initialize BeanMetaData instance; nested exception is:
com.ibm.wsspi.injectionengine.InjectionConfigurationException: Failed to process xml from Deployment Descriptor
at com.ibm.ws.metadata.ejb.EJBMDOrchestrator.finishBMDInit(EJBMDOrchestrator.java:1903)
at com.ibm.ws.runtime.component.EJBContainerImpl.finishDeferredBeanMetaData(EJBContainerImpl.java:5036)
at com.ibm.ws.runtime.component.EJBContainerImpl.initializeDeferredEJB(EJBContainerImpl.java:4845)
at com.ibm.ejs.container.HomeOfHomes$1.run(HomeOfHomes.java:406)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:403)
at com.ibm.ejs.container.HomeOfHomes.internalCreateWrapper(HomeOfHomes.java:991)
at com.ibm.ejs.container.EJSContainer.createWrapper(EJSContainer.java:5024)
at com.ibm.ejs.container.WrapperManager.faultOnKey(WrapperManager.java:545)
at com.ibm.ejs.util.cache.Cache.findAndFault(Cache.java:498)
at com.ibm.ejs.container.WrapperManager.keyToObject(WrapperManager.java:489)
at com.ibm.ejs.oa.EJSOAImpl.keyToObject(EJSOAImpl.java:553)
at com.ibm.ejs.oa.EJSRootOAImpl.keyToObject(EJSRootOAImpl.java:271)
at com.ibm.rmi.corba.ObjectManager.lookupServant(ObjectManager.java:104)
at com.ibm.CORBA.iiop.ServerDelegate.getServant(ServerDelegate.java:312)
at com.ibm.rmi.iiop.ORB.lookupLocalObject(ORB.java:601)
at com.ibm.CORBA.iiop.ORB.lookupLocalObject(ORB.java:1468)
at com.ibm.rmi.iiop.CDRReader.newObjRef(CDRReader.java:1307)
at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:1147)
at com.ibm.rmi.iiop.CDRReader.read_Object(CDRReader.java:1111)
at com.ibm.rmi.corba.IorURL.iorbytesToObjref(IorURL.java:105)
at com.ibm.rmi.corba.IorURL.resolve(IorURL.java:93)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3748)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3262)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3649)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolveUnresolvedBinding(WsnOptimizedNamingImpl.java:1927)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolve_binding(WsnOptimizedNamingImpl.java:1681)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:583)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:2163)
at com.ibm.WsnOptimizedNaming._NamingContextImplBase._invoke(_NamingContextImplBase.java:286)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)
at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: com.ibm.wsspi.injectionengine.InjectionConfigurationException: Failed to process xml from Deployment Descriptor
at com.ibm.ws.injectionengine.InjectionEngineImpl.processXML(InjectionEngineImpl.java:456)
at com.ibm.ws.injectionengine.InjectionEngineImpl.processInjectionMetaData(InjectionEngineImpl.java:313)
at com.ibm.ws.util.ComponentNameSpaceHelper.populateJavaNameSpace(ComponentNameSpaceHelper.java:806)
at com.ibm.ws.util.ComponentNameSpaceHelper.populateJavaNameSpace(ComponentNameSpaceHelper.java:519)
at com.ibm.ws.metadata.ejb.EJBMDOrchestrator.finishBMDInit(EJBMDOrchestrator.java:1864)
... 38 more
Caused by: com.ibm.wsspi.injectionengine.InjectionException: WSWS7238E: Web service references specified in the DWLCommonServicesEJB.jar module in the MDM application could not be correctly processed due to the following error com.ibm.ws.webservices.configuration.WASWebServicesBindException: WSWS1000E: Error: Service ref's already bound to Web service client! .
at com.ibm.ws.websvcs.annotations.injection.WebServiceRefProcessor.processXML(WebServiceRefProcessor.java:280)
at com.ibm.ws.injectionengine.InjectionEngineImpl.processXML(InjectionEngineImpl.java:446)
... 42 more



Go to DWLCommonServicesEJB and in that open ejb-jar.xml

Check if the EAR is running properly in the admin console. Rebuild and reinstall application

java.lang.SecurityException: Signers of 'org.eclipse.core.runtime.IExtensionRegistry' do not match signers of other classes in package

Looking up com/dwl/base/requestHandler/beans/DWLServiceController ...
java.lang.SecurityException: Signers of 'org.eclipse.core.runtime.IExtensionRegistry' do not match signers of other classes in package
at java.lang.ClassLoader.checkPackageSigners(ClassLoader.java:322)
at java.lang.ClassLoader.defineClass(ClassLoader.java:264)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:69)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:540)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:451)
at java.net.URLClassLoader.access$300(URLClassLoader.java:79)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1038)
at java.security.AccessController.doPrivileged(AccessController.java:284)
at java.net.URLClassLoader.findClass(URLClassLoader.java:429)
at java.lang.ClassLoader.loadClass(ClassLoader.java:653)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:358)
at java.lang.ClassLoader.loadClass(ClassLoader.java:619)
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:275)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:69)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:540)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:451)
at java.net.URLClassLoader.access$300(URLClassLoader.java:79)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1038)
at java.security.AccessController.doPrivileged(AccessController.java:284)
at java.net.URLClassLoader.findClass(URLClassLoader.java:429)
at java.lang.ClassLoader.loadClass(ClassLoader.java:653)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:358)
at java.lang.ClassLoader.loadClass(ClassLoader.java:619)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:139)
at com.ibm.ws.extension.ExtensionRegistryFactoryImpl.<clinit>(ExtensionRegistryFactoryImpl.java:66)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.ibm.wsspi.extension.ExtensionRegistryFactory.<clinit>(ExtensionRegistryFactory.java:53)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.ibm.ws.util.ImplFactory.parseExtensionPoint(ImplFactory.java:197)
at com.ibm.ws.util.ImplFactory.access$000(ImplFactory.java:80)
at com.ibm.ws.util.ImplFactory$1.run(ImplFactory.java:107)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.util.ImplFactory.<clinit>(ImplFactory.java:104)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.ibm.ws.uow.UOWManagerFactory$1.run(UOWManagerFactory.java:54)
at java.security.AccessController.doPrivileged(AccessController.java:251)
at com.ibm.ws.uow.UOWManagerFactory.<clinit>(UOWManagerFactory.java:48)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.ibm.ws.naming.util.TransactionUtil.suspend(TransactionUtil.java:69)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:873)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:574)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.dwl.verification.DWLServiceControllerTester.<init>(DWLServiceControllerTester.java:68)
at com.dwl.verification.DWLServiceControllerTester.main(DWLServiceControllerTester.java:132)
javax.naming.NameNotFoundException: Context: svcq3as01Cell01/clusters/MDM-CL01-Q3, name: com/dwl/base/requestHandler/beans/DWLServiceController: First component in name requestHandler/beans/DWLServiceController not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
at com.ibm.ws.naming.jndicos.CNContextImpl.mapNotFoundException(CNContextImpl.java:4365)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1794)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1749)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1500)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:637)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.dwl.verification.DWLServiceControllerTester.<init>(DWLServiceControllerTester.java:68)
at com.dwl.verification.DWLServiceControllerTester.main(DWLServiceControllerTester.java:132)
Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:95)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(_NamingContextStub.java:506)
at com.ibm.ws.naming.jndicos.CNContextImpl$2.run(CNContextImpl.java:2797)
at com.ibm.ws.naming.jndicos.CNContextImpl$2.run(CNContextImpl.java:2793)
at com.ibm.ws.naming.util.CommonHelpers.retry(CommonHelpers.java:763)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:2791)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1790)
... 8 more

If you get this error, check your corba:iiop URL 

MDM - How to enable performance tracking

Performance monitoring is disabled by default. To enable the performance tracking, you need to switch on the feature setting itself, then stipulate the level of monitoring that you want, and configure the performance statistics output file.

At minimum, you must make changes to two settings in the Configuration and Management Components:

• Set the configuration value for /IBM/DWLCommonServices/PerformanceTracking/enabled to true
• Provide a configuration value for /IBM/DWLCommonServices/PerformanceTracking/level (See Performance tracking levels for the available values).

Also in order to enable the logger to commence recording of performance statistics, you must specify the logging level using the IBM® WebSphere® Application Server logs and trace console. To commence logging you must set the following logging level:com.dwl.base.performance.internal.PerformanceMonitorLog=info in the IBM WebSphere Application Server logs and trace console.

Because the performance statistics are captured by the Logging component, the performance statistic output can be configured based on IBM WebSphere Application Server JDK Logging capabilities. It helps to configure logging optimally to get the correct size and rollover window for theperformancemonitor.log. To ensure proper capture of an elusive problem or to simply get a large statistical sample, we recommend dedicating about 2 GB to the rolling performancemonitor.log. This is typically enough to capture an hour of workload on an InfoSphere MDM in complicated and high-volume implementations. Find the following entries in the jdklog.properties file in the InfoSphere MDM properties.jar archive:

com.dwl.base.performance.internal.PerformanceMonitorLog.handlers=com.dwl.base.logging.handlers.PerfMonitorFileHandler
com.dwl.base.performance.internal.PerformanceMonitorLog.useParentHandlers=false
com.dwl.base.logging.handlers.PerfMonitorFileHandler.formatter=com.dwl.base.logging.formatters.PerformanceLogFormatter
com.dwl.base.logging.handlers.PerfMonitorFileHandler.encoding=UTF-8
com.dwl.base.logging.handlers.PerfMonitorFileHandler.limit=10000000
com.dwl.base.logging.handlers.PerfMonitorFileHandler.count=2
com.dwl.base.logging.handlers.PerfMonitorFileHandler.pattern=<LOG_PATH>/performancemonitor.n%g.log
com.dwl.base.logging.handlers.PerfMonitorFileHandler.append=true 

A special logger handler has been written to format performance monitor output. This iscom.dwl.base.logging.handlers.PerfMonitorFileHandler and is accompanied by a dedicated formatter,com.dwl.base.logging.formatters.PerformanceLogFormatter. Normally you do not alter these in any way.

After both the CONFIGELEMENT and IBM WebSphere Application Server Logs and Trace changes, a IBM WebSphere Application Server recycle for the InfoSphere MDM instance will be required to enable InfoSphere MDM Performance Tracking. Once the server has recycled, any transactions sent to that InfoSphere MDM will be logged by InfoSphere MDM Performance Tracking.

Publish Failed error while deploying MDM

Publishing failed
deployFailure
Deploying BusinessServicesEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying DWLCommonServicesWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying CrossDomainServicesWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying CrossDomainServicesWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying DWLCommonServicesWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying BusinessServicesWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying BusinessServicesWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying DWLMessagingAdapter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying DWLBusinessServicesEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying TAILMessagingEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying DWLAdminServicesEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying DWLBusinessServicesWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying DWLBusinessServicesWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying EventManagerEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying DWLAdminServicesWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying DWLAdminServicesWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying ProductEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying MDMWSProvider
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying ProductWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying ProductWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying ProductServicesWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying ProductServicesWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying DataServicesEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying FinancialServicesEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying PartyEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying FinancialServicesWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying FinancialServicesWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying CrossDomainServicesEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying PartyWS_HTTPRouter
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying PartyWSEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer had errors:  

Some files are read-only.
Deploying DWLCommonServicesEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying ManagementAgent
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying DWLBatchFramework
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deploying ECHDataAdditionEJB
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
Deploying CacheMDBBean
Deployment from com.ibm.ast.ws.jaxws.deployer.JAXWSDeployer completed successfully
Deployment from com.ibm.ast.ws.deployer.WSDeployer completed successfully
Deployment from com.ibm.etools.ejbdeploy.EJBDeployer completed successfully
OK
OK
OK
WebSphere Application Server Error
Unable to retrieve product version via JMX connection.
OK

It looks like some files are read-only. Right click workspace in Windows explorer and remove read only to the root folder.