SAP GUI 7.20 connecting through directaccess.
-
Tuesday, October 26, 2010 1:14 PM
I have SAP GUI 7.20 trying to connect to the SAP application servers. Inside the LAN it works fine, on the DA connection it fails with hostname not found. Our SAPLOGON.INI is configured using hostnames(FQDN) and not IP address' so I'm not sure where to go from here. I have had no love searching for various combinations of directaccess & SAP GUI so I am asking for some direction here. Thanks.
Edit:
So theres no one that can point me in the direction of an article or anything to help me get SAP GUI working through DA?
Answers
-
Monday, November 01, 2010 10:11 AM
Jam.Dav and RyanM_H: Using the client system environment variable SAP_IPv6_ACTIVE=1 is the first step. To be able to do load balancing you need to install SAPRouter. The client will connect over DA to the SAPRouter on the LAN, and SAPRouter will connect to the SAP servers over IPv4. This enables load balancing to work.
- Marked As Answer by Jam.Dav Monday, November 01, 2010 6:17 PM
-
Monday, November 01, 2010 2:04 PM
Noam, thanks again for your tip. We have added the necessary permissions to the route permissions table in our SAPRouter instance and added the SAPRouter entry into the SAPlogin.ini on our local machines and the connections to the load balanced SAP application servers work as required.
Now to work out either load balancing or HA of the SAPRouter.....
- Marked As Answer by Jam.Dav Monday, November 01, 2010 6:17 PM
All Replies
-
Friday, October 29, 2010 11:36 AMThe only way i've been able to get SAP to work so far is to use a terminal server with RemoteApps on it and give the users the SAP GUI from there. I'd love to get it to work through DA normally though and would love to know if you find an alternative way.
-
Friday, October 29, 2010 2:21 PM
RemoteApp is the route I have been recommending but I recently found some documentation about enabling IPv6 for SAP. If you are using UAG then IPv6 should matter only to the client side, bit it might be worth looking in to.
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/d280d334381d21e10000000a1553f6/frameset.htm
Excerpt: "Establishing the connection from the IPv6-enabled system to the IPv4 system. Since the IPv4 system can only accept IPv4 connections, the connection must be established using IPv4. Note that with an IPv6-enabled system the host name of the target system is resolved to an IPv4 address. Thus a host name that has not defined any IPv6 address must be used for the target. Alternatively, the IP address can be entered as the target system instead of the host name."
You might consider doing End-to-End instead of End-to-Edge for SAP so you can keep IPv6 over the entire route and see if that helps.
MrShannon | TechNuggets Blog | Concurrency Blogs -
Friday, October 29, 2010 2:27 PM
Currently I have had success by adding a system environment variable on the client of SAP_IPv6_ACTIVE=1 as per http://blog.beanylan.co.uk/ and connecting directly to server connections. The group connections (load balanced) are the ones im trying to work through now.
At least I know it will work now.
- Proposed As Answer by RyanM_H Sunday, October 31, 2010 8:06 PM
-
Sunday, October 31, 2010 8:07 PMThis worked great for me and is a heck of a lot better than using the RemoteApps i was getting ready do use. Thank you so much for this info.
-
Monday, November 01, 2010 10:11 AM
Jam.Dav and RyanM_H: Using the client system environment variable SAP_IPv6_ACTIVE=1 is the first step. To be able to do load balancing you need to install SAPRouter. The client will connect over DA to the SAPRouter on the LAN, and SAPRouter will connect to the SAP servers over IPv4. This enables load balancing to work.
- Marked As Answer by Jam.Dav Monday, November 01, 2010 6:17 PM
-
Monday, November 01, 2010 11:20 AMGlad to hear that this info worked and helped someone else.
-
Monday, November 01, 2010 11:22 AM
That makes sense. Thanks for sharing, now to get the SAP team to understand what I need. I will post back any interesting bits if I get any.
-
Monday, November 01, 2010 2:04 PM
Noam, thanks again for your tip. We have added the necessary permissions to the route permissions table in our SAPRouter instance and added the SAPRouter entry into the SAPlogin.ini on our local machines and the connections to the load balanced SAP application servers work as required.
Now to work out either load balancing or HA of the SAPRouter.....
- Marked As Answer by Jam.Dav Monday, November 01, 2010 6:17 PM
-
Monday, November 01, 2010 2:45 PMModerator
Hi Noam,
Great info!
Thanks!
Tom
MS ISDUA/UAG DA Anywhere Access Team Get yourself some Test Lab Guides! http://blogs.technet.com/b/tomshinder/archive/2010/07/30/test-lab-guides-lead-the-way-to-solution-mastery.aspx -
Monday, November 01, 2010 2:46 PMModerator
Hi Jam,
Very helpful!
Thanks!
Tom
MS ISDUA/UAG DA Anywhere Access Team Get yourself some Test Lab Guides! http://blogs.technet.com/b/tomshinder/archive/2010/07/30/test-lab-guides-lead-the-way-to-solution-mastery.aspx -
Thursday, December 16, 2010 12:37 PM
In case you haven't seen it there is a technet blog article on getting SAP to work. It covers SAP GUI 7.1 and the SAPRouter for load balancing.
MrShannon | TechNuggets Blog | Concurrency Blogs -
Thursday, December 16, 2010 4:11 PMModerator
Hi Shannon,
Thanks for bubbling up the blog post to the forum!
Tom
MS ISDUA/UAG DA Anywhere Access Team Get yourself some Test Lab Guides! http://blogs.technet.com/b/tomshinder/archive/2010/07/30/test-lab-guides-lead-the-way-to-solution-mastery.aspx

