We're in the process of evaluating SAP XI as our enterprise middleware standard. Most of the answers to my questions were there in the documentation, however I didn't get the answers to the below questions.
1. Does XI use SOAP natively or or is it a TCP/IP call for inter-component communication?
2. When XI sends async messages, are they sent to a JMS Topic kind of a thing? Is there a concept of database persistence for them?
2. Can we have multiple instances of XI(same installation but multiple integration servers) in the same hardware?
3. Does one BPM engine run all process models or can we partition them to run on different BPM engines?
4. Can we call custom java classes end-to-end from an XI solution to do the work instead of using SAP XI's API's etc?
5. Can we version deployable objects, can there be more than one version in the central repository, but only one version running?
6. Can I inject a message to trigger off a business process from an admin console?
7. Can we write our own exception handlers for the adapter exceptions and also specify actions like stop/restart/abort/skip the transaction?
Any help would be appreciated. Thanks in advance,
Nilabja Guha
1 Answer
-
Former MemberPosted on Dec 08, 2004 at 09:40 AM1. Does XI use SOAP natively or or is it a TCP/IP call for inter-component communication?
- XI uses SOAP with attachments natively.
2. When XI sends async messages, are they sent to a JMS Topic kind of a thing? Is there a concept of database persistence for them?
- XI has its own persistence mechanism for
asynchronous messages It does not use JMS topics. However, you can use XI JMS adapter to publish a message to the topics.
4. Can we call custom java classes end-to-end from an XI solution to do the work instead of using SAP XI's API's etc?
No. But some of the standard fucntionality can be
enhanced by custom java classes (for example java user
exits for adapters).
6. Can I inject a message to trigger off a business process from an admin console?
- Yes, you can inject a test message from the RWB
(RuntimeWorkBench)
7. Can we write our own exception handlers for the adapter exceptions and also specify actions like stop/restart/abort/skip the transaction?
- not sure........mostly no.....
5. Can we version deployable objects, can there be more than one version in the central repository, but only one version running?
The versioning can be done at the software component level. There can be multiple software component version in the repository and all are available during configuration time. By configuring only the objects from a particular SWCV, you can restrict.
Add a comment
Add a comment