Posted: Sun Apr 16, 2006 5:31 pm Post subject: some further differences
Master
Joined: 26 Oct 2004 Posts: 235
some further comments
MB has cobol handling capabilities as well as with either the MB file extender or pm4data can be used to integrate with files. MB also has the ability to handle complex non-xml data types such as EDI/SWIFT/HL7 where-as ICS requires you to build datahandlers. Dynamic Pub/Sub capabilities as well exist in MB.
ICS is being rolled into the process server with concepts such as cross-referencing, compensation (long running processes), adapter verbs etc... which need to be built into the MB and is a non-trivial task...
Posted: Wed May 10, 2006 8:25 am Post subject: MB Vs ICS
Newbie
Joined: 01 Jun 2005 Posts: 1
As mentioned in previous MB should be the choice in case of asynchronous/bulk operations. MB interfaces are stateless and ICS has stateful nature. Also consider Following points -
1. Transactional integrity. If the sender and receiver applications need to be co-ordinated in a transaction the full state nature of WICS allows for a process oriented synchronisation of systems.
2. Dynamic relationships. WICS is able to build indexes of related information that is held by different keys. It is able to build these indexes ‘on the fly’.
3. Roll back functionality. WICS is able to create compensating transactions to reset data to it’s original value should part of a transaction fail. Whilst WICS does support XA rollback facilities, this is only available in direct database access, rather than through an adapter.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum