EAI, WSDL, SOAP or some thing else?

[Fouad Fahim]

Hi all,

My issue is that I'm working on a project that should play the role of an
adaptor between internal and external application.

Each change done in the internal application should be known by the external
one. I know thank is so heavy for performance but should exist a solution.

My question is what problem I must handle in my requirement document?

and which technology can I use in this case?

Please let me know if you have any question,

Regards,

 

[Nicholas Paldino [.NET/C# MVP]]

Fouad,

It depends on the machines, and the technologies involved. If they are
both .NET apps, then I would recommend using remoting, perhaps (depending on
your security requirements). If they are both windows apps, then MSMQ or
enterprise services might be a good call.

If the apps are not both on windows machines, or one is external to your
organization (the machine hosting the app), then web services are the way to
go, in which case, you are going to use SOAP and WSDL (this is by default).

Hope this helps.

 

[Fouad Fahim]

The internal application are built on C++ and Delphe for the moment and
there is an other on C# but it will be used in this concept next year.

That's one of the requirement but the main one that we change nothing in the
internal application so we should build some tool allow as to informe the
external applications about any change in data (Pruduct, Article, customer
....) in other to keep the same data between all applications.
I hope that's more clear,
Thanks for any idea,
Fouad,

Fouad,

It depends on the machines, and the technologies involved. If they are
both .NET apps, then I would recommend using remoting, perhaps (depending
on your security requirements). If they are both windows apps, then MSMQ
or enterprise services might be a good call.

If the apps are not both on windows machines, or one is external to
your organization (the machine hosting the app), then web services are the
way to go, in which case, you are going to use SOAP and WSDL (this is by
default).

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Hi all,

My issue is that I'm working on a project that should play the role of an
adaptor between internal and external application.

Each change done in the internal application should be known by the
external one. I know thank is so heavy for performance but should exist a
solution.

My question is what problem I must handle in my requirement document?

and which technology can I use in this case?

Please let me know if you have any question,

Regards,

 

[Nicholas Paldino [.NET/C# MVP]]

That's going to suck, that you can't change the internal application.
Ideally, if you were changing data in the internal application, you would
want to wrap that in a transaction, and then try to commit changes in the
other data sources that need to store this data as well (the assumption
being that they need to be kept in sync at all times).

If you don't have to be strict about keeping the data in sync (it is an
update done at the end of the day), then you could have another app expose a
webservice, which would take a timestamp of the last time the data was
updated, and then it would return any changes that have occured.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

The internal application are built on C++ and Delphe for the moment and
there is an other on C# but it will be used in this concept next year.

That's one of the requirement but the main one that we change nothing in
the internal application so we should build some tool allow as to informe
the external applications about any change in data (Pruduct, Article,
customer ...) in other to keep the same data between all applications.
I hope that's more clear,
Thanks for any idea,
Fouad,

Fouad,

It depends on the machines, and the technologies involved. If they
are both .NET apps, then I would recommend using remoting, perhaps
(depending on your security requirements). If they are both windows
apps, then MSMQ or enterprise services might be a good call.

If the apps are not both on windows machines, or one is external to
your organization (the machine hosting the app), then web services are
the way to go, in which case, you are going to use SOAP and WSDL (this is
by default).

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Hi all,

My issue is that I'm working on a project that should play the role of
an adaptor between internal and external application.

Each change done in the internal application should be known by the
external one. I know thank is so heavy for performance but should exist
a solution.

My question is what problem I must handle in my requirement document?

and which technology can I use in this case?

Please let me know if you have any question,

Regards,

 

[Fouad Fahim]

For updating the data periodeclly you right but in my case all changer
should be send in the RealTime (Civil Security Application) so about
security, it's so mandatory....
Fouad

That's going to suck, that you can't change the internal application.
Ideally, if you were changing data in the internal application, you would
want to wrap that in a transaction, and then try to commit changes in the
other data sources that need to store this data as well (the assumption
being that they need to be kept in sync at all times).

If you don't have to be strict about keeping the data in sync (it is an
update done at the end of the day), then you could have another app expose
a webservice, which would take a timestamp of the last time the data was
updated, and then it would return any changes that have occured.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

The internal application are built on C++ and Delphe for the moment and
there is an other on C# but it will be used in this concept next year.

That's one of the requirement but the main one that we change nothing in
the internal application so we should build some tool allow as to informe
the external applications about any change in data (Pruduct, Article,
customer ...) in other to keep the same data between all applications.
I hope that's more clear,
Thanks for any idea,
Fouad,

Fouad,

It depends on the machines, and the technologies involved. If they
are both .NET apps, then I would recommend using remoting, perhaps
(depending on your security requirements). If they are both windows
apps, then MSMQ or enterprise services might be a good call.

If the apps are not both on windows machines, or one is external to
your organization (the machine hosting the app), then web services are
the way to go, in which case, you are going to use SOAP and WSDL (this
is by default).

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)


Hi all,

My issue is that I'm working on a project that should play the role of
an adaptor between internal and external application.

Each change done in the internal application should be known by the
external one. I know thank is so heavy for performance but should exist
a solution.

My question is what problem I must handle in my requirement document?

and which technology can I use in this case?

Please let me know if you have any question,

Regards,