on 2025 Jan 09 9:44 PM
Hi community
we use REST (sender) to ABAP proxy (receiver) interfaces via SAP PI.
Inside server ABAP proxy we access content of SAP PI / ABAP Proxy dynamic configuration parameters aka Adapter Specific Message Attributes (ASMA).
This is a very flexible way of interface design which enables handling generic parameters required by different interfaces independent from specific interface message (payload)
code snippet read dynamic configuration parameters of ABAP Proxy
TRY.
DATA(lo_srv_context) = cl_proxy_access=>get_server_context( ).
DATA(lr_msg_id_protocol) = CAST if_wsprotocol_message_id( lo_srv_context->get_protocol( if_wsprotocol=>message_id ) ).
me->mv_msg_id = lr_msg_id_protocol->get_message_id( ).
* Auslesen Aufruf-URL
DATA(li_internal) = CAST if_wsprotocol_internal( lo_srv_context->get_protocol( 'INTERNAL' ) ).
DATA(lo_header) = CAST cl_xms_inbound_proxy_plsrv( li_internal->get_framework( ) )->xmb_message->get_dynamic_header( ).
me->mt_dyn_conf_table = lo_header->get_records( ).
CATCH cx_ai_system_fault cx_sy_move_cast_error INTO DATA(lx_system).
RAISE SHORTDUMP lx_system.
ENDTRY.In terms of migration to SAP IntegrationSuite we are looking for a way of reusing the existing ABAP proxy implementation.
Is there a way to provide dynamic configuration parameters with XI receiver adapter in SAP Integration Suite (Cloud Integration) or an alternative way to provide header parameters to SAP ERP backend.
If possible we want to avoid redesign backend interface approach. If unavoidable REST interface would be allow flexible header parameters, wright?
Any advise welcome
cheers
Jochen
Request clarification before answering.
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.