IBM MDM Error Resolutions: 2016

Saturday, July 9, 2016

Thursday, May 12, 2016

requesterName not going to lastUpdateUser in MDM Tables

our requesterName from xmls was not going to lastUpdateUser in MDM tables. Instead the username from our xmlheader i.e. mdmadmin was going.

Fixed by changing /IBM/DWLCommonServices/Security/TrustedClientMode/enabled to true

Sources Refereed http://www-01.ibm.com/support/docview.wss?uid=swg21639776 :

Snippet :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:port="http://composites.mdm.mycompany.com/XYZComposites/port" xmlns:sch="http://www.ibm.com/mdm/schema">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsse:Security xmlns:wsse="someURL">
<wsse:UsernameToken wsu:Id="UsernameToken-123123" xmlns:wsu="someURL">
<wsse:Username>mdmadmin</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">xxyyzz</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<port:MaintainBusinessXYZCmposite>
<sch:RequestControl>
<sch:requestID>999999</sch:requestID>
<sch:DWLControl>
<sch:requesterName>myRequesterName</sch:requesterName>
.
.
.

Tuesday, May 10, 2016

Lambda expression.in Java 8

In below example we use the usual way of creating lambda expression using arrow syntax and also we used a brand new double colon (::) operator that Java 8 has to convert a normal method into lambda expression.

//Old way:

List<Integer>
  list = Arrays.asList(1, 2, 3, 4, 5, 6, 7);

for(Integer n:
  list) {

System.out.println(n);

}

//New way:

List<Integer>
  list = Arrays.asList(1, 2, 3, 4, 5, 6, 7);

list.forEach(n
  -> System.out.println(n));

//or we can use
  :: double colon operator in Java 8

list.forEach(System.out::println);

by: Suvojeet Pal

Monday, April 25, 2016

PME merge was not created

[4/25/16 17:46:32:388 CDT] 0000010f NativeLog E com.ibm.mdm.mds.log.LogAdapter error MPI_MemNextSect: integrity error (missing mpi_memhead?), getType='ASMEMBER', tabName='mpi_membktd', expected 14010480, found 14010423.

We deleted records from eme_rechead but we I belive somehow some records were missed in eme_recbktd
So, the tables were not in synch i.e. extra records were present in eme_recbktd which were not associated with eme_rechead and hence the error was coming when any Suspect party was getting loaded and PME merge was not created.

Exception Handling in Behavior Extension

Exception Handling in Behavior Extension

DWLStatus status = params.getExtensionSetStatus();

status = addError(theControl, TCRMErrorCode.UPDATE_RECORD_ERROR, ErrorReasonCode.Error_Reason_Code, e.getMessage());

params.setExtensionSetStatus(status);

by Ritwik Sen

Tuesday, April 19, 2016

WebSphere Application Server directory / folder structure

Good link for WebSphere Application Server directory / folder structure

https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/deleting_temporary_files_in_websphere_application_server?lang=en

Monday, April 18, 2016

Below code snippet can be used for throwing error/exception from External rule to Business Proxy..

TCRMExceptionUtils
.throwTCRMException(
new Exception(),
new TCRMInsertException(),
new DWLStatus(),
9L,
WCCICompositesComponentID.ORG_CALCULATION_UTIL_COMPONENT,
TCRMErrorCode.INSERT_RECORD_ERROR,
WCCICompositesErrorReasonCode.ORGCALCULATIONUTIL_NO_RECORD_IN_DUNS_TABLE,
control, this.errHandler);

toXML overloaded Method

XxxBObj.toXML("TCRM", "MDMDomains.xsd", 0,null, false);
//Use cautiously. It does not work well with metadata map. It modifies original object and assigns null to values to one's with empty value.

https://www.ibm.com/developerworks/community/forums/html/topic?id=f6f893b3-8a9a-444a-a5f2-fd7b52f0e452

MDMDomains.xsd | MDMCommon.xsd | Parser Error

Problem(Abstract)

When any extension XSD refers to types in the MDMDomains.xsd, all transactions that use the MDMCommon.xsd will fail with the error "Parser DWLTransaction failed. The format of the message is not correct or an application error occurred".

Symptom

All transactions that use the MDMCommon.xsd fail and return the error "Parser DWLTransaction failed. The format of the message is not correct or an application error occurred." The Throwable attribute in the response always says "Cannot resolve the name 'XXXXXX' to a(n) 'element declaration' component." regardless what request is about. An example of such response looks like below:

<DWLError>
<ComponentType>106</ComponentType>
<ErrorMessage>Parser DWLTransaction failed. The format of the message is not correct or an application error occurred.</ErrorMessage>
<ErrorType>READERR</ErrorType>
<LanguageCode>100</LanguageCode>
<ReasonCode>4928</ReasonCode>
<Severity>0</Severity>
<Throwable>com.dwl.base.requestHandler.exception.RequestParserException: src-resolve: Cannot resolve the name 'ProductBObj' to a(n) 'element declaration' component.</Throwable>
</DWLError>

Cause

If the request XML uses the MDMDomains.xsd then the problem won't occur. Batch processor will also fail in such case since it runs transactions internally to maintain its state and these transactions use MDMCommon.xsd.

The entity resolver of the request xml parser collects and combines all the extension XSDs (i.e. xsd-fragements) with no regard for which XSD the request XML uses. When the request XML uses MDMCommon.xsd, however, there is an extension XSD that refers to types in the MDMDomain.xsd, the combined XSD becomes invalid, which causes the problem.

Resolving the problem

If the client runs transactions directly, then changing the request xml to use MDMDomains.xsd instead of MDMCommon.xsd should work.

If the client runs transactions through batch processor, then both the request xmls in the batch input file or request xml templates and the batch processor internal transaction templates (all files in <batch_home>/templates/* folders) need to be changed to use MDMDomains.xsd instead of MDMCommon.xsd.

Good one for troubleshooting IBM Infosphere MDM

http://www-01.ibm.com/support/docview.wss?uid=swg27045725

Error initializing Configurations.[Exception_Deployment_NotFindInstance:] CDKCR2005E:The instance was not found. Instance: MDMQA01

The issue is with APPINSTANCE table. Due to DB copy from Prod the QA app instance values got changed to Prod. Due to this the configurations were not getting loaded properly.

System.out.log

[4/4/16 14:01:27:038 CDT] 0000007c SystemOut O WSWS3185I: Info: Parsing XML file: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/qalchbap01Cell01/applications/MDM-old-web-services-E001.ear/deployments/MDM-old-web-services-E001/PartyWSEJB.jar/META-INF/wsdl/PartyBusinessService.wsdl

[4/4/16 14:01:27:541 CDT] 0000008c ConfigManager I MDM Server Application found: com.ibm.mdm.hub.server-E001 Version: 11.0.0

[4/4/16 14:01:27:542 CDT] 0000008c ConfigManager I Initializing MDM Server Configurations...

[4/4/16 14:01:27:614 CDT] 0000008c Deployment I [Error_Deployment_NotFindInstance:] CDKCR2004E:The instance was not found. Instance: MDMQA01

[4/4/16 14:01:27:615 CDT] 0000008c ConfigManager E Error initializing Configurations.[Exception_Deployment_NotFindInstance:] CDKCR2005E:The instance was not found. Instance: MDMQA01

[4/4/16 14:01:27:616 CDT] 0000008c ConfigManager E com.dwl.management.config.repository.ElementNotFoundException: [Exception_Deployment_NotFindInstance:] CDKCR2005E:The instance was not found. Instance: MDMQA01

at com.dwl.management.config.repository.Deployment.getInstance(Deployment.java:125)

at com.dwl.management.config.client.Configuration.<init>(Configuration.java:365)

at com.dwl.management.config.client.Configuration.getConfiguration(Configuration.java:390)

at com.ibm.mdm.server.config.ConfigManagerImpl.init(ConfigManagerImpl.java:74)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

at java.lang.reflect.Method.invoke(Method.java:611)

at org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:238)

at org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:955)

at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:708)

at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:820)

at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:783)

at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:71)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)

at java.util.concurrent.FutureTask.run(FutureTask.java:149)

at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:79)

at org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:62)

at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:98)

at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)

at org.apache.aries.blueprint.container.BlueprintRepository.createInstance(BlueprintRepository.java:230)

at org.apache.aries.blueprint.container.BlueprintRepository.create(BlueprintRepository.java:145)

at org.apache.aries.blueprint.container.ServiceRecipe.createRecipe(ServiceRecipe.java:435)

at org.apache.aries.blueprint.container.ServiceRecipe.createExplicitDependencies(ServiceRecipe.java:424)

at org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:161)

at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:675)

at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:339)

at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:242)

at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:450)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)

at java.util.concurrent.FutureTask.run(FutureTask.java:149)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:217)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931)

at java.lang.Thread.run(Thread.java:773)

--------------------------------------------------------------------------------------------------------------------------------------------------------

Error while running txn :-

[4/4/16 14:29:58:255 CDT] 00000101 Configuration I ConfigManager finished initalization...

[4/4/16 14:29:58:256 CDT] 00000101 DWLServiceCon E java.lang.NullPointerException

at com.dwl.base.DWLControl.retrieveConfigContext(DWLControl.java:1492)

at com.dwl.base.requestHandler.DWLServiceControllerBase.handleTail(DWLServiceControllerBase.java:383)

at com.dwl.base.requestHandler.DWLServiceControllerBase.processRequest(DWLServiceControllerBase.java:276)

at com.dwl.base.requestHandler.beans.EJSRemote0SLDWLServiceController_2c54996d.processRequest(EJSRemote0SLDWLServiceController_2c54996d.java)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

at java.lang.reflect.Method.invoke(Method.java:611)

at com.ibm.CORBA.iiop.ClientDelegate$3.run(ClientDelegate.java:1262)

at java.security.AccessController.doPrivileged(AccessController.java:280)

at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:1259)

at com.sun.proxy.$Proxy103.processRequest(Unknown Source)

at com.dwl.base.requestHandler.beans._MDMServiceControllerRemote_Stub.processRequest(_MDMServiceControllerRemote_Stub.java:1)

at com.ibm.mdm.webservice.provider.MDMDefaultProvider.invoke(MDMDefaultProvider.java:116)

at sun.reflect.GeneratedMethodAccessor232.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)

at java.lang.reflect.Method.invoke(Method.java:611)

at org.apache.axis2.jaxws.server.dispatcher.JavaDispatcher.invokeTargetOperation(JavaDispatcher.java:113)

at org.apache.axis2.jaxws.server.dispatcher.ProviderDispatcher.invoke(ProviderDispatcher.java:138)

at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:111)

at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:161)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:208)

at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)

at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis2Servlet.java:1570)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1225)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:775)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:457)

at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)

at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1032)

at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)

at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:908)

at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)

at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:459)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:526)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:312)

at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:283)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)

at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)

at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)

at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)

at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)

at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)

at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1815)

[4/4/16 14:29:58:257 CDT] 00000101 DWLServiceCon I ###########################

[4/4/16 14:29:58:257 CDT] 00000101 DWLServiceCon I [Info_DWLServiceControllerBase_ProcessRequestTotalTime:] DWLServiceController : processRequest : total time in milliseconds 8

[4/4/16 14:29:58:257 CDT] 00000101 DWLServiceCon I ###########################

[4/4/16 14:29:58:260 CDT] 00000101 AxisEngine E org.apache.axis2.engine.AxisEngine receive An error was detected during JAXWS processing

org.apache.axis2.AxisFault: An error was detected during JAXWS processing

at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:208)