Suggestions/Recommendations - interface standalone Java App to SAP system

[Former Member]

Hi,

I'm currently working on some customer work where we need to write a client application that will sit on a number of PC's around a factory environment and all interface to a backend SAP system.

At the moment, we are looking at writing the client application as a J2SE application as it only needs to have a simple UI and also work with some serial port interfacing.

We then plan to use XI to send all of the data back to the SAP system. I believe we will be using client and server Java Proxies created out of XI to achieve this. These are then built into an ejbModule project and deployed as a service onto the J2EE SAP engine. Our remote client applications can then access this service in real-time.

Does this sound like a typical/ideal solution to this sort of process? We will have a number of clients all sending data to the central system in real-time.

Anyone who has any ideas or suggestions around this please reply.

Thanks in advance,

Gareth.

[Former Member · Accepted solution]

Hi Gareth,

Just a comment, you wrote

"... deployed as a service onto the J2EE SAP engine."

If that is a standard J2EE application, that will not be a problem. However if you mean that you will deploy your code like the services of the J2EE SAP engine (JMX, HTTP, etc.), then please note that custom services development is not supported. Please see SAP Note 822542.

HTH

Peter

[Former Member · Accepted solution]

Hi Peter,

Thanks for your response.

It will be a standard EJB type application, with the client Java app performing a JNDI lookup to call it.

Thanks for the info anyway.

Gareth.