Altova is well known for it's flagship product XMLSpy - as anyone who has worked extensively with XML data can tell you. However, they have an entire suite of product offerings, one of which is MapForce. As described on it's website:
If you are a web services developer and you build a new SOA system, you probably choose HTTP as a transport. However, sometimes you should support legacy systems that use other protocols for information exchange, for example, FTP. There are several technical nuances to be addressed in this case.
If client sends data over HTTP, you may analyze it and reply with error code if it’s incorrect. If client uploads data by FTP, how will you notify him that you can’t accept it?
Okay, this is my first post and I want to jump straight in with a neat little method of authentication which is often used when Intel® SOA Expressway is deployed as a Service Gateway. It also gives you the ability to be agnostic to whether you’re dealing with SOAP or REST XML patterns in your messaging.
Generally in these blogs I’m going to assume a little bit of familiarity with Intel® SOA Expressway and Intel® Services Designer but if you’re curious to know more or a noob then drop me a comment and I’ll fill you in on the extra detail.
A typical Healthcare Information Exchange (HIE) accepts data from an array of disparate sources. Often the data it accepts is semantically and syntactically altered by a providing system to satisfy interfacing requirements. However, there are also cases where data from different sources need to be properly merged before reaching the HIE's interface.
One of the cool features of Intel® SOA Expressway is its ability to easily handle token bridging with just a few clicks. What is token bridging you ask? With the increased need for Enterprises to talk outside their perimeter to other Enterprises or cloud services, we need an easy way to morph message level credentials into the proper form as they move across the dynamic perimeter of the Enterprise.
It is always good to come across a situation where you have an easy solution to a customer problem. It's even better when the customer thinks the problem is a hard one!
So a project manager walks up to you and tells you, “Hey, we just bought a company that creates purchasing order software. The PO system uses a Linux based implementation of Oracle Access Manager (OAM). We need to integrate this technology’s authentication mechanism with our implementation of Kerberos and Microsoft Active Directory. Unfortunately, their PO system doesn’t support any of the Windows Integrated Authentication solutions. We aren’t even sure if the system can handle SPNEGO. While OAM may handle SAML assertions, it definitely can’t deal with Kerberos tokens.
For the past 7 weeks I worked on my first Proof-Of-Concept (POC) for a financial system corporation. The initial scope of the work revolved around using SOA Expressway primarily as rapid & high performance secure integration product.
I am back with another customer use case that is recently moved to production. Happens to be in mortgage industry (yes, it still exists!)