Quantcast
Channel: SCN : Unanswered Discussions - SAP Business Process Management
Viewing all articles
Browse latest Browse all 3160

BRM and BPM integration configuration error

$
0
0

Hello,

 

We integrated a BRM rule into our BPM process using the generated webservice. In the service group that we defined in BPM, we used the "local provider" option. We imported the webservice using the WSDL file location.

When we deploy this process and rule using the NWDI to our development system, everything works fine. When we afterwards tranport this to our test system using the NWDI, the configuration of the webservice call is missing. The error we get is "configuration not found for application". In the NWA under SOA, application communication , the processing status of our consumed service group has the status failed in our test system.

 

Is there a reason why the deployment and generation of the configuration on our test system differs from the one on our dev system?

 

A simular thread was already created BPM Integration with BRM, but there's no solution posted yet.

 

The error we get:

 

 

 

EXCEPTION]

com.sap.esi.esp.lib.esb.exception.ExtendedGenerationException:
No endpoints found. Check if the service is configured and if its endpoints are
available in the . Service: [{http://www.custom.com}SMSApplicationPropertiesReusePortType]
Assigned Provider: [Local System]


Service Group: [ApplicationProperties]

Service Group application:
[custom.com/ringring~wachtdienst]


Service Reference application:
[custom.com/ringring~wachtdienst]


at
com.sap.esi.esp.service.server.esb.WSConfigurationGenerator.createConfigurations(WSConfigurationGenerator.java:170)
at
com.sap.esi.esp.service.server.esb.WSConfigurationGenerator.createConfigurations(WSConfigurationGenerator.java:470)
at com.sap.esi.esp.service.server.mass.AbstractConfigurationsHelper.createConfigurationForServiceReference(AbstractConfigurationsHelper.java:498)
at
com.sap.esi.esp.service.server.mass.AbstractConfigurationsHelper.createConfigurationsForInterfaceGroup(AbstractConfigurationsHelper.java:458)
at
com.sap.esi.esp.service.server.mass.AbstractConfigurationsHelper.createConsumerConfigurations(AbstractConfigurationsHelper.java:311)
at
com.sap.esi.esp.service.server.mass.AbstractConfigurationsHelper.createConfiguration(AbstractConfigurationsHelper.java:197)
at
com.sap.esi.esp.service.server.mass.ConfigurationScenarioHandler.processAsynch(ConfigurationScenarioHandler.java:110)
at
com.sap.esi.esp.service.server.mass.ConfigurationScenarioHandler.processAsynch(ConfigurationScenarioHandler.java:90)
at
com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:486)
at
com.sap.esi.esp.service.server.SOATimeoutListenerImpl.run(SOATimeoutListenerImpl.java:379)
at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:183)
at
com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:83)

at
com.sap.engine.frame.core.thread.Task.run(Task.java:73)

at
com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)

at
com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

 

kind regards,

 

Pieter


Viewing all articles
Browse latest Browse all 3160

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>