cancel
Showing results for 
Search instead for 
Did you mean: 

BRM and BPM integration configuration error

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (2)

Answers (2)

junwu
Active Contributor
0 Kudos

1. remove the local system assignment, and assign again to see if any change.

Former Member
0 Kudos

Hello,

also that we tried, but this has no effect.

kind regards,

Pieter

vijay_kumar49
Active Contributor
0 Kudos

Pieter,

Just try undeploy and redeploy the DC which provides the web service (e.g. Process DC)



Regards

Vijay Kalluri

former_member191044
Active Contributor
0 Kudos

Hi Pieter,

it looks like that you have transported your SG with a reference that is not available in your test system. Please check if "custom.com/ringring~wachdienst" is deployed on the test system.

Or remove this reference from sg and transport it again.

Regards,

Tobias

Former Member
0 Kudos

Hello,

we already tried to deploy again, but it didn't help. The BRM is deployed, because the webservice is working fine in the wsnavigator.

The BPM is also deployed, because the process goes in error when trying to call the BRM webservice. The other steps previous on this step are executed.

kind regards,

Pieter