Can ESB satisfy these publish / subscribe requirements?

Question

I have some requirements that I thing ESB should be able to help me to achieve.
I effectively have a central system that needs to update some other systems, depending on the data it could be 1 system or 5 systems to be updated.
The requirements I think ESB should be able to meet are:
1)     Ability to queue any data if an integration component is offline for any reason
2)     Reduce the concurrent dependency between applications
3)     To ensure data changes are only applied once
4)     Transaction support to ensure that any remote data has been synced
5)     Visibility for monitoring to see where updates are and whether they are occurring
6)     Ability to handle interaction with Oracle and non Oracle databases and web services
I intend to use the Heterogeneous data services Generic and Transparent to provide connections to datasources.
Can anyone comment on whether these needs will be satisfied by ESB or do we need to investigate BPEL which I am trying to avoid to minimise the initial complexity.
Thanks
Chris

Answer 1

Many thanks for your input Martin,
1) With regards to the sync / async question in an ideal situation a local key from the subscriber system could be returned to the master (publisher) which would could double up to confirm the operation was successful. Although the messaging system should handle the case of the subscriber not being available, when it became available I would expect a callback result such as the local key to be returned as a result of the operation.
2) Reducing the dependency - with this I just mean that the ESB should be able to store the message if the subscriber is unavailable, meaning that both publisher and subscriber do not have to be available at the same time
3) Good
4) Transaction support - I mean from a connection point of view that the operation is part of a transaction. I guess this depends on whether I am able to use a transparent gateway for the Heterogeneous services or whether the subscriber system only provides a generic data adapter.
5) Visibility of the state of updates - for this I just want to be able to visualise if the updates are occurring, or failing, and can be relatively crude as long as it gives an accurate picture. Any idea of where I should look to find out some more information about what this interface offers? What is it called?
6) Thanks