cancel
Showing results for 
Search instead for 
Did you mean: 

SXMB_ADM Subparameter as prefix

rvanhoof
Explorer
0 Kudos

Hi,

I am currently looking for a way to send XI messages from S4 to a number of CPI endpoints (configured as XI sender adapters in CPI) using the Integration Engine. I have set up 1 general RFC destination (type G) to CPI in SM59 (<CPI hostname>/cxf/MCS):

I assumed that it would be possible to dynamically determine the specific iFlow endpoint at runtime by configuring a subparameter (for example, "MANAGE_MCS_ADDURL") in SXMB_ADM and checking the "Prefix" checkbox so that it would append the subparameter name to the connection URL referenced in SM59 (the complete endpoint would then be <CPI hostname>/cxf/MCS/MANAGE_MCS_ADDURL).

In other words, I am looking for a way to create a dynamic interface-specific integration server URL. Unfortunately, when sending a testrequest, the subparameter isn't taken into account and the integration server tries to send it to the general /cxf/MCS endpoint. Looking at the trace of a similar request using MANAGE_MCS_FEEDBACKEQ, it appears the subparameter is being detected properly, but as only the /cxf/MCS/MANAGE_MCS_FEEDBACKEQ endpoint is available in CPI and the request is being sent to the destination endpoint (cxf/MCS), a 404 is sent back as response.

Is it possible to set up such a configuration? If not, what is the actual use of configuring a subparameter as prefix? I'd like to avoid defining a separate RFC destination per iFlow in SM59 or creating a main flow in CPI wherein a router sends the messages to their specific iFlows using Process Direct adapters.

Accepted Solutions (1)

Accepted Solutions (1)

VijayKonam
Active Contributor

You can do this by maintaining separate Sender IDs. In SXMB_ADM you can see the option to create separate unique sender ids based on sender interface name and namspace. You can then rout them to different IS_URLs which will point to different RFC destinations.

Instead, you could have one IS_URL, and one RFC destination on S4 and then receive all of them in a routing CPI iFlow, where you could use a value mapping lookup table to direct them to various child iflows using process direct.

I would prefer CPI option.

Answers (0)