I
need to develop a web based application wherein the data would be
retrieved from Mainframes and other legacy apps. I know that there
would be a limit in connections that I can open to connect to this
legacy systems. Even though my web application on the top would be able
to take that load but internally when request get queued up at the
legacy end things go for a toss.
Trouble is I
can change the interface to the legacy application. So taking all this
into consideration can anyone share some thoughts into what can
be done at the architecture to address the same
Architectural considerations when developing a .Net solution with intergaration to Legacy apps
Hot Topic
- Exception Management in N-Tier architecture
- Designing Databases for SOA
- rule->Code generation
- Message vs Service.
- The IASA Foundation Reference Model
- N-tier layer separations and connection/interaction
- Microsoft Certifications- Good, Bad, or Ugly?
- Have you tried NHibernate?
- Databinding vs Multi-tier
- Design Patterns & Best Practices
Architecture
- standards of rule engine
- Dependency between Business and DAL - Problems with unit testing
- Design consulting
- Layered Architecture across Boundaries
- Biztalk server 2004 Data Access
- Session Management for Distributed Remote Application in C#
- Lazy linking pattern
- Who needs Architecture?
- Design Patterns & Best Practices
- N-tier layer separations and connection/interaction
Architectural considerations when developing a .Net solution with intergaration to Legacy apps
Bob Tabor
Have you checked on http://www.microsoft.com/mainframe or http://www.mainframemigration.org for any info or contacts Or the Host Integration Server site
If you share some more details about your problems, I am sure we can find some guidance.
betz
-Sai
clinicalcom
Hi Spyros,
We've done a lot of mainframe integration here. The approach that has worked fine for us is to use Host Integration Server (HIS) to provide access to the transactions on the Server. HIS provides either COM or Web Services interfaces that are then easily accessible. You will strike issues with buffering requests and responses and possibly with synchronising between applications. MSMQ is the answer for this, or BizTalk Server would be even better if you want the gold-plated solution. MSMQ has worked fine for us in the past.
IBM also have a solution that provides Web Services interfaces to CICS transactions, but you will still need to look to some form of queuing (MSMQ, MQSeries) solution to provide buffering.
Regards,
Kevin
twiggy
Thanks for the guidance
-Sai
Chandan Jhalani
I am assuming you ment "Can't" rather than Can
You would probably want to add a queue in between the component that handles the requests from the web and the component that is responsible to establish the connection with the legacy side.
This way you can control both the interaction with the user (for example return an initial response immidiatly after you queue the request and then use AJAX-like methods to return the result once it is available) and the "connection pooling" working aginst the legacy app.
Arnon
peterxz
MonkeyZa
You should take a look at our good friend "ABE" Applied Integration Baseline Reference Implementation from patterns & practices. This architecture features a web application with connections to a mainframe and remote data centers. The one challenge that is similar to yours in this case was that the remote data center call could take a very long time. They used a pattern known as Half-sync/Half-Async to make an Async call to this remote data center through a message broker using the pub/sub pattern. Whew! that's a mouthful of patterns!
At any rate - the source is available with this and there is good documentation to study along with a flash version of the narrator that walks you through the architecture voiced over by yours truly.
Good luck!