LdapAdapter getDateString(Object) WIMSystemException CWWIM1998E Unparseable date

By Mirsa Mohammed -
After LDAP integration in toolkit environment while testing integration we came across following exception.

com.ibm.ws.wim.adapter.ldap.LdapAdapter getDateString(Object)
                                 com.ibm.websphere.wim.exception.WIMSystemException: CWWIM1998E  Durante l'elaborazione si รจ verificato il seguente errore di sistema: 'java.text.ParseException: Unparseable date: "20190610101654.793-0000Z"'.
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.getDateString(LdapAdapter.java:4000)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.setPropertyValue(LdapAdapter.java:4047)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.populateEntity(LdapAdapter.java:3906)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.createEntityFromLdapEntry(LdapAdapter.java:1527)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.get(LdapAdapter.java:1629)
at com.ibm.ws.wim.ProfileManager.getImpl(ProfileManager.java:1756)
at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(ProfileManager.java:374)
at com.ibm.ws.wim.ProfileManager.get(ProfileManager.java:427)
at com.ibm.websphere.wim.ServiceProvider.get(ServiceProvider.java:410)
at com.ibm.websphere.wim.client.LocalServiceProvider.get(LocalServiceProvider.java:364)
at com.ibm.commerce.member.syncbeans.VMMProxy$3.run(VMMProxy.java:1080)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5487)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5613)
at com.ibm.commerce.member.syncbeans.VMMProxy.getMemberByDNWithRoot(VMMProxy.java:1089)
at com.ibm.commerce.member.syncbeans.VMMProxy.getMemberByDN(VMMProxy.java:908)
at com.ibm.commerce.member.syncbeans.SyncBeanBase.createInLDAP(SyncBeanBase.java:804)
at com.ibm.commerce.member.syncbeans.SyncBeanBase.refresh(SyncBeanBase.java:1338)
at com.ibm.commerce.member.syncbeans.OrganizationSyncBean.<init>(OrganizationSyncBean.java:435)
at com.ibm.commerce.member.syncbeans.OrganizationSyncBean.findByMemberId(OrganizationSyncBean.java:596)'

Found the solution mentioned at this link: https://www-01.ibm.com/support/docview.wss?uid=swg1PM54864 but the timestamp format to use was not clear.

We executed the following command to fix the issue:

$AdminTask setIdMgrCustomProperty {-id <LDAP_REPO_ID> -name ldapTimestampFormat  -value "yyyyMMddHHmmss.SSSZ" }
$AdminConfig save

where <LDAP_REPO_ID> we can find from
WAS console -> Security -> Global security -> Federated repositories
check the 'Repository Identifier'.
OR we can also check wimconfig.xml 'config:repositories' tag id value corresponding to config:LdapRepositoryType.

and yyyyMMddHHmmss.SSSZ you can use if you are getting error for the timestamp in the same format as in the above error, otherwise you may have to use different value as per LDAP's date format.

Comments

Post a Comment

Popular posts from this blog

Creating and adding elements to a list in JSTL

By Mirsa Mohammed -
There are plenty of places in WebSphere Commerce out-of-the-box code where we can see code to iterate over a list in JSTL. But I feel that code to create and add items to list in JSTL are rare and hence lot of developers (atleast beginners) do not know how to do that. I recently came across and used this code to create and add items to an arraylist in JSP using JSTL. And I thought I need to note it down somewhere so I can refer in future. Sample code below: <wcf:useBean var="sampleList" classname="java.util.ArrayList"/> ... <c:set var="sampleVar" value="val"/> <wcf:set target="${sampleList}" value="${sampleVar}"/> Once you created the list, you can iterate through and process it as required. <c:forEach items="${sampleList}" var="eachVal"> <c:out value="${eachVal}" /> </c:forEach> Hope this help someone. Feel free to share t...
Read more

IBM WebSphere Commerce - Payment related debugging - AEDPPIEditCtrlCmdImpl getOrderIdByEDPPIID

By Mirsa Mohammed -
Here I am going to share my recent experience in debugging a payment related issue. This issue started occurring all of a sudden without any recent changes to the code. All the orders were failing after entering the payment information. Error log for the issue was as below. [9/27/17 0:31:23:137 EST] 0000002e CommerceSrvr A AEDPPIEditCtrlCmdImpl getOrderIdByEDPPIID Object of type payment instruction with primary key 79,172 could not be found in the database. [9/27/17 0:31:23:139 EST] 0000002e ExtendedInfo I CWXFR9010I: Extended information : [URL=http://localhost/webapp/wcs/stores/servlet/webapp/wcs/stores/servlet/XPaymentProcessCmd] [parameters=signature=+Yuun7p7fwRo6hgHvdf4CBz2lNvrKUN/BtKbQZgFsue= encryptedparameters=2SDSwUkztXgotmmLbKuB+P2ZoiX1Rd65ai3932yezsdHLI2wb1deUvHoNKzaP9KvXsedZd0SgLBWjv+COHyZXTLyFEDXBcfCcYBFzkgTc2JdTl3XAjKai4KbGp0sJ8haesjbeZKIavF6AK7LjdsF05guWvsEkQ6ymn7OvK9UvLrIQDTT1/UNW4i9G/qXJ3WIYp3H8E1BCHS+HfFj/1wS/ORpartRTNxwYCloHwT4qjPVr/toH2LWtzNTICMEdgJ4We+SzSS...
Read more

Fetching PIs (Payment Instructions) for an order - IBM WebSphere Commerce

By Mirsa Mohammed -
Payment instructions of an order is stored in PPCPAYINST database table. This post is about the usage of QueryPIsCmd task command which can be used to fetch all the payment instructions for an order. The default implementation of this command is QueryPIsCmdImpl. Below is a sample code snippet to fetch already added PIs for an order. QueryPIsCmd queryPICmd = (QueryPIsCmd) CommandFactory.createCommand("com.ibm.commerce.edp.commands.QueryPIsCmd", storeId); queryPICmd.setCommandContext(commandContext); queryPICmd.setOrderId(new Long(orderId)); queryPICmd.execute(); ArrayList pis = queryPICmd.getPIs(); Hope this help someone. Feel free to share this page with your friends and colleagues. Thanks..!
Read more