topic Re: checking ADS server down programatically in Application Development and Automation Discussions

checking ADS server down programatically

Former Member — Mon, 12 May 2014 10:44:47 GMT

Hello Experts,

Is there any FM or static method where i can check ADS server is down or not ?

Please provide your inputs.

ADS connection is configured already. Just need to put a check in one Function module as this connection will be down manier times and causing lot of issues.

If there is any FM or static method to check ADS server connection is up or not, then i am planning to raise an error message.

BR,

Nikhil Kulkarni

Re: checking ADS server down programatically

Former Member — Mon, 12 May 2014 11:25:59 GMT

Hi,

There's a standard program to make this check, FP_PDF_TEST_00 you could check if this has any code you could reuse.

Regards,

Nick

Re: checking ADS server down programatically

Former Member — Mon, 12 May 2014 11:38:01 GMT

Hello Nick,

Thanks alot for your Quick reply.

I found the following code in this standard report.

p_dest = cl_fp=>get_ads_connection( ).

   TRY.
*     Get version information.
      gv_version = cl_fp=>get_reference(
                       )->create_pdf_object( connection = p_dest
                           )->get_version_info( ).

CATCH cx_fp_runtime INTO gx_fpex.
PERFORM error USING gx_fpex.
ENDTRY.

What is this GV_VERSION. If the ADS server is UP and running what will be the value inside this gv_version ?

DOes this suffice to check for ADS connection is up and running ?

BR,

Nikhil Kulkarni

Re: checking ADS server down programatically

Former Member — Mon, 12 May 2014 12:03:41 GMT

The program I mentioned is fairly simple, in order to determine if ADS is running it needs to ask it a question. The question is 'what version?' and the answer (or lack of answer) is used to define if ADS is available.

Program FP_CHECK_DESTINATION_SERVICE is also available and seems to have more detail, but essentially works on the same principle of asking ADS to do something and checking the reply.

Regards,

Nick