• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Supply Chain Management Lawson S3 Supply Chain

MSCM install - sync errors

 0 Replies
 0 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
12/18/2015 5:51 PM
Anyone get MSCM 10.1.6.0 with a Secured LSF Websphere to actually synchronize OK? I've installed MSCM, but the secured LSF WAS piece is apparently causing an issue in the synchronization, as seen as an error in the mscm_error.log. (Server and cluster names removed below). Have already checked and reviewed mscm.filter.properties

12-18-2015 13:40:52,862] WARN  [com.lawson.mscm.platform.adapter.ios.data.DMEManagerIOSImpl] Exception occurred during creation of LSF Client Factory. The configuration for this is the following: 
 Server Type: WEBSPHERE
Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Server Name(s): ,
Server IIOP port(s): 2811,2812
Server Namespace: cell/clusters/
com.lawson.ios.client.LSFClientException: Exception occurred during creation of LSF Client Factory. The configuration for this is the following: 
 Server Type: WEBSPHERE
Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Server Name(s): ,
Server IIOP port(s): 2811,2812
Server Namespace: cell/clusters/
at com.lawson.ios.client.LSFClientFactory.processConstructionFailure(LSFClientFactory.java:246)
at com.lawson.ios.client.LSFClientFactory.getInstance(LSFClientFactory.java:197)
at com.lawson.mscm.platform.utilities.LSFClientFactoryUtilityImpl.initLsfClientFactory(LSFClientFactoryUtilityImpl.java:314)
at com.lawson.mscm.platform.utilities.LSFClientFactoryUtilityImpl.createDataService(LSFClientFactoryUtilityImpl.java:120)
at com.lawson.mscm.platform.adapter.ios.data.DMEManagerIOSImpl.runDme(DMEManagerIOSImpl.java:73)
at com.lawson.mscm.platform.adapter.dme.DMEManagerLHCImpl.executeInboundDME(DMEManagerLHCImpl.java:319)
at com.lawson.mscm.platform.adapter.dme.InboundDeltaProcessSchedulable.runDme(InboundDeltaProcessSchedulable.java:300)
at com.lawson.mscm.platform.adapter.dme.InboundDeltaProcessSchedulable.perform(InboundDeltaProcessSchedulable.java:450)
at com.lawson.mscm.platform.adapter.dme.InboundDeltaProcessSchedulable.perform(InboundDeltaProcessSchedulable.java:318)
at com.lawson.mscm.platform.manager.scheduler.BaseInboundDeltaProcessSchedulable.doSchedulerAction(BaseInboundDeltaProcessSchedulable.java:128)
at com.lawson.mscm.platform.manager.schedulertask.InboundDeltaProcessSchedulableTask.perform(InboundDeltaProcessSchedulableTask.java:109)
at com.lawson.mscm.platform.manager.schedulertask.InboundDeltaProcessSchedulableTask.process(InboundDeltaProcessSchedulableTask.java:90)
at com.ibm.websphere.scheduler.EJSRemoteStatelessInboundDeltaProcessSchedulableTa_e32c9fff.process(Unknown Source)
at com.ibm.websphere.scheduler._TaskHandler_Stub.process(_TaskHandler_Stub.java:269)
at com.ibm.ws.scheduler.tasks.BeanTaskInfoWork.doWork(BeanTaskInfoWork.java:126)
at com.ibm.ws.scheduler.AlarmListener.executeTaskWithNotification(AlarmListener.java:807)
at com.ibm.ws.scheduler.AlarmListener.access$700(AlarmListener.java:124)
at com.ibm.ws.scheduler.AlarmListener$TaskWork.doWork(AlarmListener.java:436)
at com.ibm.ws.scheduler.AlarmListener$TaskWork.run(AlarmListener.java:222)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:811)
at com.ibm.ws.asynchbeans.ExecutionContextImpl.go(ExecutionContextImpl.java:86)
at com.ibm.ws.scheduler.AlarmListener.fireTask(AlarmListener.java:1416)
at com.ibm.ws.scheduler.AlarmListener.fired(AlarmListener.java:1334)
at com.ibm.ws.asynchbeans.AlarmImpl.callListenerMethod(AlarmImpl.java:427)
at com.ibm.ws.asynchbeans.timer.GenericTimer.run(GenericTimer.java:228)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1178)
at com.ibm.ws.asynchbeans.AlarmImpl.runListenerAsCJWork(AlarmImpl.java:249)
at com.ibm.ws.asynchbeans.am._Alarm.fireAlarm(_Alarm.java:340)
at com.ibm.ws.asynchbeans.am._Alarm.run(_Alarm.java:237)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
Caused by: com.lawson.ios.client.BadConfigurationException: None of the specified servers are accessible or are responding. Please check the servers and the values on the configuration file or the getInstance call parameters.


I've already reviewed and checked the mscm.ios.properties file several times. Reinstalled MSCM, recycled server, and still error exists. Have a case with support open too.

LSF Webshere is secured, and LSF App servers are clustered. I've added the configuration for one of the lsf app servers in the MSCM Websphere security set up. (I can't add both of them since an error message saying "Certificate already exists in key store. May be under a different alias name." Recycled/rebooted MSCM but still the error message in mscm_server.log exists.
MSCM: Windows
LSF: AIX 

Thanks for your help.