XI Desing for many client applications

[Former Member]

Hello,

I have the following landscape: SAP System and many Java swing client applications.

The data from SAP system must be replicated into all Java applications.

I see 2 types of architecture:

1. There is standard IDOC that will be sent to XI. XI stores objects(not messages) into a cache.

Cache is Java proxy that works with XI database(new Oracle schema). All Java applications get the data by synch call from cache.

This approach is not standard and not easy. But in this case ABAP developers of SAP System aren't involved.

2. ABAP developers will write Z FM that will get all required data. All java application will just call this FM synchronously.

The first approach seem to be more complicated and error prone. But I have to prove that ABAP developers must write FM.

What do you think is the first approach viable? What are your choice?

[MichalKrawczyk]

Hi,

maybe one more scenario to consider:

r3 sends the stnadard IDOC with all the info to XI

XI stores the IDOC-XML as a file in some folder

- then all the apps access the newest file

to get all the info (no need for Z FM = no abap dev)

- no need for sync calls to the R3 (saves SAP's performance )

- no need for caching the message on the XI (saves XI resources - for BPMs )

- and since you need to write the inferface

from java to Z FM you can write from java to file

it's not "state of the art" interface but you can

also consider it for the reason above:)

what do you think?

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member]

Our customer doesn't like this approach because He want guranteed delivery. Our first design was to use FTP server but there is no guarented delivery for FTP.

It wasn't approved by our customer.