How can I check if a login is possible?
werner.flamme at ufz.de
Tue Mar 1 10:26:54 MET 2011
-----BEGIN PGP SIGNED MESSAGE-----
I use the SAPNWRFC module from Piers Harding as well :-) It is provided
for several languages, I use the PHP version (download from
<http://www.piersharding.com/download/php/sapnwrfc/>) since I provide
some modules for our intranet (budget control, CATS fillout etc).
Again: it is not a problem to contact the SAP servers. I need a reliable
indicator whether it is possible to log in interactively or not. I
already check several aspects of the CCMS, but I don't know which (if
any) of them (6500+) tell me it it is possible to login.
You say that you send an SMS when "SAP servers are not responding or is
not possible to login." How do you check that login is not possible?
That is exactly the information I'm looking for! :-)
Palazzoni,Michele,MILANO,NBSI [28.02.2011 17:50]:
> I don't use Nagios so I can't help you with it : I use a PHP script
> to send an alert by SMS/mail if SAP servers are not responding or is
> not possible to login.
> PHP is very simple and use RFC module to take some info from SAP
> system, like server process, memory, and other useful performance
> data for report purpose.
> Technically in any language if you use RFC to execute a login you
> check if it is possible.....
> Da: linux.general-bounces at listserv.sap.com
> [mailto:linux.general-bounces at listserv.sap.com] Per conto di Derek
> Colley Inviato: lunedì 28 febbraio 2011 16.23 A:
> linux.general at listserv.sap.com Cc: Werner Flamme Oggetto: Re: How can
> I check if a login is possible?
> It seems we are approaching this from different angles...
> I've tried to answer your questions below. If you would like me to
> help further I suggest to take this offline as your question appears
> generic and doesn't have much specifically to do with Linux.
> On Mon, Feb 28, 2011 at 2:51 PM, Werner Flamme <werner.flamme at ufz.de>
> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> Derek Colley [28.02.2011 15:40]:
>> I would suggest you get one of the ABAPers to show you how function
>> modules work. E.g. if you don't enter the RFC destination in SE37,
>> then the function executes on the local server.
> That is perfectly clear to me.
> I do not want to execute a function on the local server. I want to
> check if the local server can connect to another one. Hence I search
> a way to tell the function which server to contact.
> ...'local' to me is the SAP system... calling the RFC_SYSTEM_INFO
> from Nagios without populating the DESTINATION would cause Nadios to
> execute the function on the target SAP system. If you actually enter
> a DESTINATION this could allow you to test through SAP system 1 to
> another [destination] SAP system...
> > Following Alan's advice, I would wrap RFC_SYSTEM_INFO into a SOAP
> call - > help from a developer may be needed - and then call it from
> Nagios. If you > get the expected system info then all is well. If
> you get HTTP 401 or > something similar, then raise an alert. > >
> Rgds, > Derek
> No one here ever works with SOAP calls, so there is no SOAP
> And why would it be better to wrap RFC_SYSTEM_INFO into a SOAP call
> instead of calling /usr/sap/rfcsdk/bin/sapinfo ashost=myhost
> ... because: - I don't believe the command line util requires
> authentication to get SAP system info [could be wrong] - RFC/DIAG
> protocol is not as firewall friendly as SOAP/HTTP is
> I still do not know if this checks for the possibility to login. I'm
> not interested in a check that only looks if the system is running -
> I've got a lot of those... The DB connection wasn't lost during the
> incident, you just couldn't connect.
> In order to execute any RFC function remotely SAP [normally] needs to
> perform authentication [and should perform authorisation]. By calling
> *ANY* RFC function and getting a result - this should tell you the
> system is functioning.
> > On Mon, Feb 28, 2011 at 2:26 PM, Werner Flamme
> <werner.flamme at ufz.de> wrote: >
> > Derek Colley [28.02.2011 15:06]: >>>> You could expose RFC_PING via
> web service/SOAP. Perhaps it would be > easier >>>> for you to
> connect without using the RFC SDK... > > Hi Derek, > > I already test
> a webservice, the WEBGUI logon "window" on >
> https://myhost/sap/bc/gui/sap/its/webgui. It should tell me when the
> > host refuses a login via web service. How reliable is RFC_PING in
> that > respect? > > In SM59, I can start a "test login". Can I call
> this functionality via a > function call inside SAP? RFC_LOGIN is a
> nice function - but how do I > tell it to log onto a remote system?
> Interactively, the RFC destination > can be entered, but it is no
> parameter of the function itself. How can I > tell the function on
> system C11 to try to logon to system C12? > > I'm looking for
> something that tells me if I still can login via SAP GUI > (e.g.
> Windows GUI, or PLATIN). And I look "into" the system via various >
> RFC calls. For example, I look for the number of users being logged
> in, > but this number was not zero while no login was possible, so it
> is not > usable for my purpose. > > Regards, > Werner > >>>> On Mon,
> Feb 28, 2011 at 1:29 PM, Alan Pope <alan at popey.com> wrote: >>>> >>>>>
> On 28 February 2011 12:17, Werner Flamme <werner.flamme at ufz.de>
> wrote: >>>>>> I never knew that rfcping checks that logging in is
> available :-). I >>>>>> thought it is like niping and just checks
> whether a system is alive. > And >>>>>> since all of our RFC checks
> succeeded... >>>>>> >>>>> >>>>> I may be wrong, but combined with the
> second level RFC_PING via >>>>> function module, that should be
> sufficient to know if the system is up >>>>> or not. >>>>> >>>>>> And
> thank you for the idea of using RFC_PING inside a system to connect
> >>>>>> to another one, this was completely out of sight for me. But I
> still do >>>>>> not know how to tell RFC_PING (or RFC_SYSTEM_INFO)
> which system to ping >>>>>> (or to connect to). Can you please give
> me some coding advice? >>>>>> >>>>> >>>>> Sadly not, it was ~4 years
> ago, a few contracts passed and I don't >>>>> have the notes :(
> >>>>> >>>>> I'd have to rummage around in the function module and SDK
> again to >>>>> remember. It wasn't that hard to figure out tbh.
> >>>>> >>>>> Al.
> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
> fHcAn2lPcPyPBKJgMXid7R8BBIMW9zmz =3UJf
> -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the linux.general