Feedback in regards to SAP Gateway OData consumed by JAVA environment

[wouter_peeters]

Hello experts,

We are doing Gateway development of OData services so these can be consumed by our JAVA development team.

Can anyone share any best practices how you approach this?

- As SAP, Do you do anything specific to do a handover of the 'contract' to the java team?

- AS Java, how do you implement OData services? Custom JAVA, Apache Olingo or SAP Cloud SDK

- AS Java, could you share any lessons learned when evaluating one of the above options ( Custom Java, Apache Olingo or SAP Cloud SDK )

Thanks in advance!

Regards,

Wouter

[gregorw]

In a Hybris (AKA C/4HANA Commerce Cloud) the Hybris Team used Apache Olingo to call the OData Services that where implemented from the ABAP Team. We've used the Subscription and Notification Flow in the pull scenario to send Events to Hybris when business objects where updated in ERP. The Java team used the Metadata that the OData service provided.

As a lesson learned I would suggest to start directly with JSON as the payload and use descriptive, plain english Entity and Attribute names.

When starting today it might be worth looking into the SAP Cloud SDK instead of Apache Olingo as it also allows you to create the API's for your own OData services.