Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

High-Assurance design for Interoperability scenarios

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Cliff.,

What is your suggestion for achieving H-A when a J2EE application interoperates with Microsoft .NET using SOAP based Web services ? How Security, reliability and other capabilities can be applied ?

Thanks

Vijay
[ January 19, 2006: Message edited by: Ilja Preuss ]
 
Author
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Vijay,

It is late here, so I might not have time to answer your other questions tonight. I will try to get to them tomorrow.

It sounds like you are discussing a server-to-server scenario, e.g., an EJB or servlet making real-time requests to a .NET web service. In that case, you need to consider all of the issues in constructing a communication between a service request handler (which is what an EJB or a servlet is) and another service. The assurance considerations are no different than for any application, but some of the design characteristics of this scenario that come to mind are that the originaing object (EJB, servlet, etc.) might have transient state, that is, it might not have a session, and so it should not create a session-oriented request to a web service; or if it must, it should be done through a robust pool. I have seen people make this mistake and it can go undetected and cause problems. Another consideration that pops into my head is that your scenario must ensure that the web service specification versions are synchronized between the two endpoints. A third consideration is accessibility of schema, since the servers might be in different security domains. A fourth consideration is entitlement management or user role management across the two domains. There is also the issue of what user identity should be used to make the web service request, since the originating server object will have to have those credentials when it makes the request. Finally, transactional integrity is an issue if the web service succeeds but the calling EJB/servlet request then fails. And you know that anything that can go wrong will....

- Cliff
 
Vijay Pratap Singh
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Cliff,

Thanks, I am bit confused.

Your suggestion sound more like a Shrink Wrap solution, that would kill the extensibility of the application at both end-points. If I choose to use XML Web services standards that allows Interoperability between these endpoints...what are are standards available that helps enabling High-Assurance and also guarantees Interoperability ?

-V
 
Yes, of course, and I accept that blame. In fact, i covet that blame. As does this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic