BPM process End-point issue

[Former Member]

Hi All,

I have created a BPM process and after deploying it on CE 7.3 SP02, i found that there are 7 end-points coming under SSO by default. I am not sure why these end-points are coming and causing me problem in calling it through the end-point.

Even i tried creating my own end-point for this service, but on rum time WS Navigator is not picking my service. Can some one please help me in setting this properly and get it running. Some end-to-end document or tutorial will be very helpful.

Regards,

Nishant Singh

[Former Member · Accepted solution]

Converting the service into Asynchronous service served the purpose.

But this is not the exact solution what i am looking for.

What should be the solution when we want to give back some response too from the service ?

Regards,

Nishant Singh

[Former Member · Accepted solution]

Hello Nishant,

The end-points are configured in SOA Configuration of /nwa. You can easily, for synch or asynch services additionally define your own end-points based on other authentication (even no authentication). If you don't assign a profile then the system uses the default.

The default communication profile (SAP_DEFAULT_PROFILE), found in System Connections / Communication Profiles contains all authentication methods.

All these methods have their own end-point which is referenced in the WSDL. wsnavigator will pick the basic auth  enabled end-point unless you specify one yourself. Other tools might pick some other one (seemingly at random) unless, again, you specify the end-point explicitely.

If you want to have an end-point exposed as non-authenticated then you can create a profile (for instance WS_NOAUTH) and only enable 'None' for authentication method. Then you assign that profile to the service and the system won't require any authentication. Keep in mind though that the service interface may have a security profile as defined in the ESR.

regards, Nick

regards, Nick

[Former Member · Accepted solution]

Hi Nicholas,

Thanks for your detailed reply. Its very helpful.

But the problem in my scenarion is:

-when i use SAP DEFAULT PROFILE, system generates 7 end-points. And when i am running this from WSNavigator, it picks some random end-point and that is not required.

- when i use self created profile (as suggested WS_NOAUTH), and removes all authentication. The service is timing-out from WSNavigator. To resolve this issue, i removed the response (as suggested in many other threads).

So, my concern is what if the consumer of this service is expecting a response from this. I hope you understand the problem here.

Regards,

Nishant Singh

[Jocelyn_Dart · Accepted solution]

Hi Nishant,

Suggest you try creating a basic user name/password profile rather than no auth.  That's usually the quickest one to get going when you are getting started as you can control which user you are using to start the process as they need to be a BPM super admin or have the BPM trigger event auth to do that. Once you've worked out your process you can always go back and adjust the endpoints later.

Regards,

Jocelyn

[Former Member · Accepted solution]

Does your process have any manual steps or other long steps that may cause it to take a signficant amount of time?  For me, I suspect the majority of BPM processes will become asynchronous simply because it isn't possible to return a completed response instantly.

I tend to model processes with both a synchronous response at the beginning, to acknowledge to the caller it has been received correctly, and a further asynchronous end later on which marks the proper end of the process.  This can drive further design decisions though if messages are actually needed as part of the response, in terms of where and how those responses are returned.  This may be a case for a separate process maybe?

The point I'm making is that an asynchronous call to a BPM isn't necessarily a bad thing - it really does depend upon the specific scenario.

Gareth.