SOA: Difference between revisions
From DataFlex Wiki
Jump to navigationJump to search
mNo edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Service oriented architecture == | == Service oriented architecture == | ||
Service oriented architectures allow for easy system integration. Today , when we talk about Service oriented architectures , then we typically talk about systems that allow for integration using [[Web Services]] using [[SOAP]] and [[WSDL]] - but other scenarios also apply - more modern systems apply techniques of [[REST]] architectures and facilitate data exchange using [[JSON]]. | |||
== Using it from [[Visual DataFlex]] == | |||
Do you need an easy way to expose your [[Visual DataFlex]] code to another system? | Do you need an easy way to expose your [[Visual DataFlex]] code to another system? | ||
Then create a [[Web Service]] , that exposes your functionality. | |||
== Frequent issues == | |||
*[[XML Logging]] | |||
*[[XML Replay]] | |||
[[Category:Web Services]] | [[Category:Web Services]] | ||
[[Category:System Integration]] | [[Category:System Integration]] | ||
Latest revision as of 11:10, 20 September 2008
Service oriented architecture
Service oriented architectures allow for easy system integration. Today , when we talk about Service oriented architectures , then we typically talk about systems that allow for integration using Web Services using SOAP and WSDL - but other scenarios also apply - more modern systems apply techniques of REST architectures and facilitate data exchange using JSON.
Using it from Visual DataFlex
Do you need an easy way to expose your Visual DataFlex code to another system? Then create a Web Service , that exposes your functionality.
