Skip to Content
0

SOAP adapter - XI 3.0 message protocol - SAP PI 7.1

Jun 15, 2017 at 12:38 PM

206

avatar image

Hi Experts,

We are on PI 7.1 version of PI.

We are trying to build a scenario using AAE and trying to bypass Integration Engine altogether.

But while using SOAP adapter i couldn't able to find XI 3.0 in the message protocol.

(Attached is the screenshot: soap-no-xi-30.png)

Could someone please tell me on how can I get this add-on functionality in PI 7.1 version?

Regards,

Aayush Aggarwal

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Evgeniy Kolmakov Jun 15, 2017 at 01:45 PM
2

Hi Aayush!

As far as I remeber the mentioned functionality is added with EHP1 for PI 7.1. Ask your Basis team to upgrade your system.

Regards, Evgeniy.

Share
10 |10000 characters needed characters left characters exceeded
Raghuraman S Jun 15, 2017 at 01:18 PM
1

I don't think soap adapter of 7.1 has this functionality, You can use XI adapter.

Share
10 |10000 characters needed characters left characters exceeded
Aayush Aggarwal Jun 27, 2017 at 07:00 AM
0

Hi Raghuraman,

But XI adapter is Integration Engine Based adapter, here we are trying to bypass the IE, therefore will not be able to use it.

Is there any other scenario i can create, in which i can bypass IE (other than SOAP)??

Regards,

Aayush Aggarwal

Show 5 Share
10 |10000 characters needed characters left characters exceeded

Hi Aayush,

AFAIK in PI 7.1 these connectivities are not supported in AAE:

- HTTP.

- IDOC

- Proxy.

The other adapters was supported.

Regards.

0

Hello Aayush,

what is the end-end scenario?

And what is the specific reason to avoid IE?

If your using proxy in X 3.0 AFAIK it will by pass AE(channel) so performance should be good.

0
Former Member

I don't think performance is the concern here. As clients are preparing for a migration from PI dual stack to PO single stack, they are typically imposing policies banning new developments that leverage ABAP components to avoid having to migrate them at a later point.

0
Yep.But with XI 3.0 this is not possible and moving later to soap with XI 3.0 should not be a big concern.
0

Hi Raghuraman,

There is no particular requirement, it is as Patrick is saying.

Its an idea that will be used, therefore to implement it we need to show certain features and benefits like performance enhancement.

Regards,

Aayush Aggarwal

0
Aayush Aggarwal Jun 27, 2017 at 07:01 AM
0

Hi Evgeniy,

I guess a lot of approvals would be required in this case.

Also, same question to you: Is there any other scenario i can create, in which i can bypass IE (other than SOAP)??

Regards,

Aayush Aggarwal

Show 5 Share
10 |10000 characters needed characters left characters exceeded
Former Member

You could expose a vanilla SOAP service on your ECC backend. To that you would be able to connect using the PI 7.1 SOAP adapter without XI message protocol.

0

Yes, it would be required.

But it's the best way to solve it. Otherwise, next time when you face another issue you'll start searching for workarounds again and again.

Regards, Evgeniy.

0

Hi Patrick,

"You could expose a vanilla SOAP service on your ECC backend.", could you please explain this in detail.

Regards,

Aayush Aggarwal

0
Former Member
Aayush Aggarwal

There are dozens of blog posts out there on how to create a web service in ABAP. The first one I found is here:

https://blogs.sap.com/2012/10/24/how-to-create-web-services-abap-based/

If you don't necessarily have to use SOAP, you could think about using the RFC adapter adapter to connect to an RFC enabled function module. The RFC adapter is part of the Java stack and would thus not fall under the restriction you appear to have.

0

Hi Evgeniy,

I am not sure this would be possible, because it will be a kind of project in itself for the security team. i.e. implementing an enhancement package.

Regards,

Aayush Aggarwal

0