[51688] in SAPr3-news
SAProuter string, IP-address for SAProuter, load balancing
daemon@ATHENA.MIT.EDU (Peter Van Avermaet)
Tue Oct 5 08:14:12 2004
To: sapr3-news@mit.edu
Date: 5 Oct 2004 05:14:09 -0700
From: Peter.VanAvermaet@advalvas.be (Peter Van Avermaet)
Message-ID: <85a502d.0410050414.3936bb6c@posting.google.com>
We are using the classic chain of two SAProuters for our connection to
SAP Walldorf (OSS-connection):
One on our side and one at SAP.
On both SAProuters we use service 99 - the default.
Our SAProuter runs on AS/400 aka iSeries.
RFC-destination SAPOSS uses a "SAProuter string" of the form
/H/x.y.z.w/H/i.j.k.l/H/oss002
In other words, both SAProuters are specified by their IP-address, not
by their hostname.
All this worked very well until we started moving machines and
re-organising our network.
When using the RFC-destination, the system complained about not being
able to resolve the hostname -
but the hostname given in the error message was blank or some funny
character.
I pinged, checked routes etc. but I could not find any cause.
In the end, I discovered that I could avoid the problem by specifying
the first SAProuter (x.y.z.w in my example) by hostname (not by
IP-address).
This work-around worked, but I'd like to understand why.
In addition, we implemented OSS-note 766505 "OSS1: Changes to SAPOSS
RFC connection". It affects the way transaction OSS1 writes/updates
the definition of RFC-destination SAPOSS. Whenever we do that from
OSS1, we have to correct the definition manually. The new code of OSS1
insists on using a load-balancing feature - but I wonder whether that
works on OS/400. I remember that there has been a note 60856 "AS/400:
OSS1 and Hot Packages", which says that LGTST does not exist on OS/400
- this may be related.
