Hi Holger,
I have checked for the following:
BPO’s - enabled
log file path - correct(in log4j properties file)
Broker - connected(in IS page)
extended settings - correct(in IS page wsel etc. files)
webservice - configured (in IS page)
remote servers - connected and configured (in IS page)
PRT - present and enabled (in IS page)
jdbc pools - connected(in IS page)
Please let me know, where could be the problem. When the request is getting triggered successfully in interface server, why it is not reaching implementation server and in MWS process instance is not getting created.
Is there any possibility of issue lying with the broker.
Please let me know for broker settings what are all the things I need to check in the server, IS , MWS.
Providing success log sample from Interface server:
2017:07:24 20:30:25:365,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,START - WSEL TrackingId: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - MSISDN: 447528055123 - UserId: pay_dd - Use Case: SubscribeEvent - Channel Code: JT - Enduser Code: JT - ddBundleId: JT_DD_005 - PaymentsMessageType: DD_PAYMENT_SUCCESSFUL - BacsReference: 129597742-2017179
2017:07:24 20:31:18:185,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,START - WSEL Request ID: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - BusinessProcessState Id: NOT_AVAILABLE - BusinessProcessState UpdateStatus: SUBMITTED - ChannelCode: JT EnduserCode: JT - UsecaseName: SubscribeEvent Key: 447528055123
2017:07:24 20:32:41:240,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,FINISH - WSEL Request ID: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - BusinessProcessState Id: NOT_AVAILABLE - BusinessProcessState UpdateStatus: SUBMITTED - ChannelCode: JT EnduserCode: JT - UsecaseName: SubscribeEvent Key: 447528055123
2017:07:24 20:32:56:237,INFO ,deployer,INFO,null,wm.server.flow:stepFlow,FINISH - WSEL TrackingId: %soapHeaders/HDRDOC1:trackingHeader[0]/requestId% - Request ID: JT - MSISDN: 447528055123 - UserId: pay_dd - Use Case: SubscribeEvent - Channel Code: JT - Enduser Code: JT - ddBundleId: JT_DD_005 - PaymentsMessageType: DD_PAYMENT_SUCCESSFUL - BacsReference: 129597742-2017179
Regards
Priya
#Integration-Server-and-ESB#webMethods#Flow-and-Java-services