Locally on WPS 6.2 invoke the “local” EJBs from Business Flow Manager and Human Task Manager.

You CAN use Web Service version of BFM and HTM. I personally found it too cumbersome to configure than the EJB. Which is a testament to how difficult IBM makes its solutions.

Best.

I have a scenario where in I have a web application on was 7.0 and WPS server 6.2 is on other sytem.I want to invoke process from the client .to use EJB interface I will have to install WPS client 6.2 on my client side i.e over was 7.0 .I dont think it is going to work and for this kind of scenario I will have to use webservices api for invoking the process ?Please suggest if I am right on this ?
Thanks,
Runa

In any event, my basic problem is that IBM solution are unnecessarily complicated. I have to live with their products. But I would like to believe I don’t have to live with their remoting solutions. I earned my stripes in distributed computing. I learned – as someone else has so eloquently put – the effort spent in designing something is inversely proportional to the simplicity of the result. A fact lost on IBM, conveniently, because if they make things simple, they lose consulting dollars. But I’m digressing.

I love, like and understand Web Service technology very well. After getting things to work using the EJB route, I delved into exactly what was happening. Without going into too much details, 3 types of “tokens” aka credentials are getting serialized over the wire through the EJB Proxy. I figured out how to do the same thing manually, confirmed that the serialized payload was identical to what was being generated by the EJB proxy. I then proceeded to ASCII encode it as a SOAP Header and send it over the wire using a CXF service. The idea was to deserialize and get the credentials back.

When I tried to deserialize the payload over the wire, I got a serializeVersionUID error. Fact of the matter is I know I got the security credentials right. I know because I dumped them into a file, read them at the other end of the wire, and was able to invoke the BFM session bean on behalf of whatever user I wanted.

Sorry for the long drawn out response. I’m sorry but WebSphere Process Server sucks. Someday, maybe I’ll start my own blog. I’m sure I’ve bored yawl enough.

Best.

The solution I used was EJB/RMI security. It is easier to explain through code than in English

LoginContext context = new LoginContext(“system.RMI_INBOUND”,
WSCallbackHandlerFactory.getInstance().getCallbackHandler(userId, (String)null));
context.login();
WSSubject.setRunAsSubject(context.getSubject());

We execute this code BEFORE I create instance of BFM or HTM session bean. The thread of invocation transfers the necessary credentials over the wire, effectively “trusting” the caller. Notice, no password for creating the login context. Not that I have it anyways. Needless to say, communication between my Web Application (deployed in WebSphere) and my Process Model (deployed in WebSphere Process Server) happens in the “trusted” layer.

We muddled through configuration of RMI security on both WebSphere and WebSphere Process Server to get this working. Perhaps you or someone else will create a guide for mere mortals in simple English (IBM documentation is Greek, maybe Latin, certainly French, all of which I don’t speak).

Best Regards.
P.S. I did keep my job. For now

I do not think LTPAToken is going to work for you as JBoss does not understand what an LTPAToken is. You may need to write a JAAS module for making this happen. or you can even think about different alternates like SAML or certificate based SSO.

Please let me know if this helps.