Suggestion on Migration of JAVA based webservice written in NWDS (.JAR files) to SAP PO JAVA Stack

[Former Member]

Hello All we need your advice on below approach-

AS-IS :

As of now our client has one JAVA server (called GJS)  which is used for hosting JAVA Web services written in NWDS  i.e. first JAVA Web services/Methods code is written along with business logic in  NWDS and using JCO connector for connecting with SAP ECC and then they are deploying it as a .JAR file on this  SAP Netweaver JAVA Server(GJS).

Expected To-Be:

As  SAP PO(7.4) is single stack  and have JAVA  Stack only , so now client is proposing to migrate these  Web services  .JAR files to SAP PO7.4 JAVA Stack, Team has done a POC as well and  POC Web services is working fine i.e. in the same way they are working  as o now.

So we want to know your  suggestion on this – “Will it be a good approach to move business logic written JAVA code web services to SAP PO 7.4 JAVA Stack  from stability /performance /best practice point of view”?   OR   what is other best way to migrate these approx. 80 Web services   to PO7.4 as  client doesn’t want to have a separate server just for these JAVA code based  Web services(Written by JAVA developer in NWDS).

[vadimklimov]

Hi Abdullah,

From design best practices perspective, application integration and business application logic shall be segregated and decoupled: application integration logic is to be implemented in PO, whereas business application logic shall be avoided in middleware systems like PO and shall be hosted by corresponding application systems (SAP ECC, etc.).

It is still fine to orchestrate business logic calls within PO - for example, by means of BPM, PO can execute sophisticated multi-step conditional processes calling multiple application systems, but the service / business application logic provider is still application system, PO only orchestrates calls to it.

Having written so, I suggest thinking about redesign of these interfaces and moving application logic out of the service hosted on PO, and implementing it in respective application system, which is then called from PO.

In your described scenarios, PO may expose services which are currently called by consumer systems, perform routing and technical mapping operations, and then make calls to receiver system that implements application logic. For example, if application logic is to be implemented in ECC, then the most straightforward and simple solution might be web service (SOAP/REST/WS) sender to IDoc/proxy receiver scenario, unless you require advanced orchestration or other dedicated and specific communication techniques.

Regards,

Vadim