BatchProcessor not working

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

CORBA OBJECT_NOT_EXIST 0x4942fc14 No; nested exception is:
org.omg.CORBA.OBJECT_NOT_EXIST:
>> SERVER (id=f4cf56f, host=q2lchbap02) TRACE START:
>>    org.omg.CORBA.OBJECT_NOT_EXIST: SERVANT_NOT_FOUND (4) for key 0x49454a5002010b8d62a80d4d444d436c75737465725f514103454a4200000096acac00020001218b000000636f6d2e69626d2e6d646d2e6875622e7365727665722d453030312e2e31312e352e302e2e636f6d2e69626d2e6d646d2e7365727665722e64776c636f6d6d6f6e73657276696365732e656a6223636f6d2e69626d2e6d646d2e7365727665722e64776c636f6d6d6f6e73657276696365732e656a622344574c53657276696365436f6e74726f6c6c6572  vmcid: IBM  minor code: C14  completed: No
>> at com.ibm.rmi.corba.ObjectManager.lookupServant(ObjectManager.java:107)
>> at com.ibm.CORBA.iiop.ServerDelegate.getServantForRequest(ServerDelegate.java:390)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:448)
>> at com.ibm.rmi.iiop.ORB.process(ORB.java:607)
>> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1583)
>> at com.ibm.rmi.iiop.Connection.doRequestWork(Connection.java:3166)
>> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:3030)
>> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:64)
>> at com.ibm.ws.giop.threadpool.WorkQueueElement.dispatch(WorkQueueElement.java:174)
>> at com.ibm.ws.giop.filter.GiopFilterChain.processMessage(GiopFilterChain.java:203)
>> at com.ibm.ws.giop.threadpool.PooledThread.handleRequest(PooledThread.java:81)
>> at com.ibm.ws.giop.threadpool.PooledThread.run(PooledThread.java:102)
>> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
>> SERVER (id=f4cf56f, host=q2lchbap02) TRACE END.
  vmcid: IBM  minor code: C14  completed: No



Strange thing was transactions were working from SOAPUI but not from BatchProcessor.


MDM was not installed properly. Reinstall it. 

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>
                 .
                 .
                 .

Lambda expression.in Java 8

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

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