on 03-18-2015 12:28 PM
Hi Experts,
we have a SAP R3 4.7 ( WAS 620) system which has never been connected to any PI system.
We have SAP PI 7.31 EPH 5 system ( Dual Stack)
We have interfaces running from SAP ECC 6.0 with SAP PI 7.3 .
Can anyone let me know if i can connect R3 with just java stack of PI or it will support only ABAP stack?
Also can you please send me the list of steps for proxy connectivity?
Regards
Biplab
Hi Biplab
I can confirm that proxy is possible from Web AS 6.20 onwards. I was involved in a project long time back integrating an R/3 4.7 system with XI 3.0 and we were using proxies.
Both Inaki's link above and the one below also mentions Web AS 6.20 as a minimum prerequisite.
Proxies in SAP - Netweaver Technology - SCN Wiki
As this was so long ago, I can't remember if the R/3 system had the XI2.0 add-on installed on it in order to generate the proxies. I'd suggest you try generating a proxy, and if it does not work, then get the add on installed.
One thing I do remember is for inbound proxies (XI -> R/3), the path for the target URL is slightly different and needs to be as listed below. The type needs to be "receiver" instead of "entry" which is what is commonly used now from Web AS 6.40 and above.
As for connectivity using SOAP on Java stack only (ICO), I am unsure of this as this was long before Java only processing was available. An R/3 4.7 system does not seem to meet the prerequisites mentioned in the document Hareesh provided above. I guess there is no harm trying it out. I am sure that connectivity is supported on ABAP stack via the XI adapter, so you can always fall back on a classical scenario if ICO does not work.
Well, as the saying goes "you'll never know if you never try"
Rgds
Eng Swee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Biplab,
Hope you are doing good.
Are you are that you have dual stack; they more or less ceased to exist after 7.00 release.
Most likely you have a standalone j2ee as PI or separate abap and java stacks .
Regarding ports:
Hope this helps
_ _ _ _ _ _ _ _ _
Kind Regards,
Hemanth
SAP AGS
_ _ _ _ _ _ _ _ _
Hi Biplab
Note that the "type=receiver" part only applies to PI -> R/3 connection. For that connection, you will be accessing the service on the R/3 side so it needs to be the ABAP port. The port value depends on the instance number of the R/3 system. Therefore it will be 80xx where xx is the instance number.
You can always verify the port by going to SICF in R/3 to test the service:-
SICF -> Execute -> Navigate to "default_host/sap/xi/engine" -> Right click and test service
Rgds
Eng Swee
Hi Biplab,
Hope you are doing good. The 401 Unauthorized error means the page you were trying to access can not be loaded until you first log on with a valid user ID and password. If you have just logged on and received the 401 Unauthorized error, it means that the credentials you entered were invalid for some reason. Please try with a "Administrator" user for testing purpose and see if this helps;
This will help us in isolating the issue.
_ _ _ _ _ _ _ _ _
Kind Regards,
Hemanth
Biplab
Your screenshot above didn't show which user you have configured for the RFC. Usually we would use user PIAPPL<SID> which is created during the post installation wizard in PI. This user would have the role that Praveen mentioned above. Refer SAP library link below:-
Standard Users (AEX) - SAP Process Integration Security Guide - SAP Library
Rgds
Eng Swee
But you should not get unauthorized exception for this.
However, does your password has combination of upper&lower case.
AFAIK - password's are not case sensitive in R3 4.7.
If that is the case then you might want to define your password in lower case and maintain the same in RFC to see if that helps..
>>>Can anyone let me know if i can connect R3 with just java stack of PI or it will support only ABAP stack?
Also can you please send me the list of steps for proxy connectivity?
You can use soap adapter to enable proxy communication which will bypass ABAP stack(integration engine). Instead of creating a classical scenario, you should create Integrated Configurations.
Refer to below blog for setup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Biplab,
I can confirm Hareesh Gampa assumption in this SAP.help documentation Proxy Generation - Enabling Application-to-Application Processes - SAP Library
You will need to use the RFC adapter to do your integration.
Regards.
Hi Biplab,
Porxy is possible with 6.20 onward, if not with your patch level. Then try upgrading the patch as per sap note http://service.sap.com/sap/support/notes/721160
Although a similar question answered here
http://scn.sap.com/thread/3254101
and I second Eng "you'll never know if you never try".
Regards,
Sachin Dhingra
User | Count |
---|---|
89 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.