There are many situations when in order to test an inbound ABAP proxy message we want to do it from the SPROXY transaction without building a complete scenario in SAP PO (attention new name – SAP PRO) nor we want to use any other tool for testing the message (SOAP UI, web Service Navigator, etc.). There main issue however is that the inbound proxy message tested from transaction SPROXY will not be visible in ABAP proxy monitoring transaction (SXMB_MONI) neither will it be shown in Error and Conflict Handler mointoring transaction (ECH_MONI_SEL) in case of any error. Fortunately as of Netweaver 7.31 on which the backend system can be installed we have a new possibility of testing those kinf of messages directly from transaction SPROXY. The new feature is called – Config less shortcut and you will see it once you run a test of an inbound proxy message from transaction SPROXY as shown in the Figure below.

/wp-content/uploads/2015/06/sproxy_krawczyk_1_717835.png

How does it work?

Basically it simplifies the local use of the provider service so it’s no longer required to create an endpoint nor a logical port for local communication as a generic endpoint for all provider services is generated during the intial customizing (SRT_ADMIN) of WS runtime.

What does it do?

1. With this new feature you will be able to monitor test cases initiated from SPROXY as shown in the Figure below:

/wp-content/uploads/2015/06/sproxy_krawczyk_2_717833.png

2. In case of an error (we assume that the inbound proxy is correctly developed so it’s utilising ECH/FEH frameworks) you will be able to see the errors directly from the transaction ECH_MONI_SEL.

/wp-content/uploads/2015/06/sproxy_krawczyk_3_717834.png

3. It also simplifes a lot the use of calling local WS runtime directly from ABAP – please have a look at the article’s reference for examples

4. Other use cases: This new feature can also be used with other frameworks which are utilising proxy messages tested from SPROXY like for example Application and Interface Framework (AIF) testing of ABAP proxy messages.

Reference:


Configuration-less Shortcut and Generic Consumer Proxy – ABAP Connectivity – SCN Wiki

SOA monitoring – my book on monitoring proxy messages

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Iñaki Vila

    Hi Michal,

    Always a pleasure to read your new blogs.

    May be i am a bit confused today 🙂 , but i have a few questions.

    This new tool can be used with ABAP service providers that they are exposed without PI development, isn’t it?

    Could be use to test with service provider developed from PI service interface?

    Regards.

    (0) 
    1. Michal Krawczyk Post author

      Hi Iñaki Vila

      It’s not a new tool – it’s just a new mode for using the old tool – sproxy “test” mode 🙂

      but answering your question – this can be used for all types of inbound proxies – in test mode (so very useful during blueprint, etc.) – and the general functionality in development also (for example calling a WS from within local system and monitoring it via SXMB_MONI) – without PO/PRO in this case. With PO/PRO during the runtime messages are persisted by default but if you just create a Service Interface in PO/PRO and generate an inbound proxy from it and code it you can still use this new function to test it without doing the test via PO/PRO – so without doing the ID part of the interface.  

      Does that clarify a bit ? 🙂

      Thank you for your question and interest in the blog 🙂

      Regards,

      Michal Krawczyk

      (0) 
  2. M. Verhoef

    Hi Michal.

    In line with this sproxy testing I would like to know if in HCI we can still use the ABAP client and/or server proxies (i.e. the XI adapter).

    Thanks in advance,

    Marco

    (0) 

Leave a Reply