Hello All,

We are using API's to create a ticket in Remedy & have been able to create the ticket successfully.
Now our problem is we want to implement Fail-over means in case 1 server is down it should automatically connect to other (back up server).
We have done below :
1) Call ARInitialization API & in the control Structure specify - .
2) Now we stopped Remedy Services on this .
3) Then we again called ARInitialization API & in the control Structure specify - .
4) But something strange is happening - We store the result of step 1 in temp variable & though server1 is down still it is showing value of temp as 0(means successful).

Can anyone please suggest if we are doing something wrong or is there any another way through which we can check this ?

Thanks & regards,
Charu

On Mon, 8 Dec 2003 21:40:01 +0530, Charu MAHAJAN wrote:

>Hello All,
>
>We are using API's to create a ticket in Remedy & have been able to create the ticket successfully.
>Now our problem is we want to implement Fail-over means in case 1 server is down it should automatically connect to other (back up server).
>We have done below :
> 1) Call ARInitialization API & in the control Structure specify - .
> 2) Now we stopped Remedy Services on this .
> 3) Then we again called ARInitialization API & in the control Structure specify - .
> 4) But something strange is happening - We store the result of step 1 in temp variable & though server1 is down still it is showing value of temp as 0(means successful).
>
>Can anyone please suggest if we are doing something wrong or is there any another way through which we can check this ?

Just a thought - but how are all the user tools going to know to use
the other server? All the failover setups I have seen use a common
server name and a DNS switch to do the failover - so nothing is in
need of changing anywhere else.

--
Regards

Dave Saville

Charu,

The ARInitialization()-call do not connect to the server, it just
initializes the API on the client side.

You need to do something more, like an ARVerifyUser()-call to actually
login and verify the connection to the server.

Good Luck - Misi, RRR AB, http://www.rrr.se

> Hello All,
>
> We are using API's to create a ticket in Remedy & have been able to
> create the ticket successfully. Now our problem is we want to implement
> Fail-over means in case 1 server is down it should automatically
> connect to other (back up server). We have done below :
> 1) Call ARInitialization API & in the control Structure specify
> - . 2) Now we stopped Remedy Services on this
> .
> 3) Then we again called ARInitialization API & in the control
> Structure specify - . 4) But something strange is
> happening - We store the result of step 1 in temp variable &
> though server1 is down still it is showing value of temp
> as 0(means successful).
>
> Can anyone please suggest if we are doing something wrong or is there
> any another way through which we can check this ?
>
> Thanks & regards,
> Charu
>
>


> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com

Misi,

But I checked its definition in the documenst ,it says it tells whether user
is registered with current server or not ?
So it won't check for the Remedy services.
Is there any other thing we can impelement ?

Thanks & regards,
Charu


-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Misi Mladoniczky
Sent: Tuesday, December 09, 2003 1:06 PM
To: ARSLIST@ARSLIST.ORG
Subject: Re: [ARSLIST] [ARSLIST ] C API - Fail Over Mechanism


Charu,

The ARInitialization()-call do not connect to the server, it just
initializes the API on the client side.

You need to do something more, like an ARVerifyUser()-call to actually login
and verify the connection to the server.

Good Luck - Misi, RRR AB, http://www.rrr.se

> Hello All,
>
> We are using API's to create a ticket in Remedy & have been able to
> create the ticket successfully. Now our problem is we want to
> implement Fail-over means in case 1 server is down it should
> automatically connect to other (back up server). We have done below :
> 1) Call ARInitialization API & in the control Structure specify
> - . 2) Now we stopped Remedy Services on this
> .
> 3) Then we again called ARInitialization API & in the control
> Structure specify - . 4) But something strange is
> happening - We store the result of step 1 in temp variable &
> though server1 is down still it is showing value of temp
> as 0(means successful).
>
> Can anyone please suggest if we are doing something wrong or is there
> any another way through which we can check this ?
>
> Thanks & regards,
> Charu
>
>


> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX
> SUPPORT SERVICES at www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com

Charu,

In order for ARVerifyUser()-to do what it does, it connects to the ARServer.

If the ARServer is down, it will fail.

The ARInitialization() will not fail if the server is down as it do not
connect to the server.

You could use almost any API-call except the ARInitialization()-call to
verify that a server is up and running.

You could use the ARCreateEntry() to do this, and on failiure try to
connect to the backup server instead.

You should probably traverse the ARStatusList returned by the API-call to
see that you get one of the error messages indicating that the server may
be down.

Best Regards - Misi, RRR AB, http://www.rrr.se

> Misi,
>
> But I checked its definition in the documenst ,it says it tells whether
> user is registered with current server or not ?
> So it won't check for the Remedy services.
> Is there any other thing we can impelement ?
>
> Thanks & regards,
> Charu
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Misi Mladoniczky
> Sent: Tuesday, December 09, 2003 1:06 PM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: [ARSLIST] [ARSLIST ] C API - Fail Over Mechanism
>
>
> Charu,
>
> The ARInitialization()-call do not connect to the server, it just
> initializes the API on the client side.
>
> You need to do something more, like an ARVerifyUser()-call to actually
> login and verify the connection to the server.
>
> Good Luck - Misi, RRR AB, http://www.rrr.se
>
>> Hello All,
>>
>> We are using API's to create a ticket in Remedy & have been able to
>> create the ticket successfully. Now our problem is we want to
>> implement Fail-over means in case 1 server is down it should
>> automatically connect to other (back up server). We have done below :
>> 1) Call ARInitialization API & in the control Structure specify
>> - . 2) Now we stopped Remedy Services on this
>> .
>> 3) Then we again called ARInitialization API & in the control
>> Structure specify - . 4) But something strange is
>> happening - We store the result of step 1 in temp variable &
>> though server1 is down still it is showing value of
>> temp as 0(means successful).
>>
>> Can anyone please suggest if we are doing something wrong or is there
>> any another way through which we can check this ?
>>
>> Thanks & regards,
>> Charu
>>
>>
>

>
>> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
>> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX
>> SUPPORT SERVICES at www.QMXS.com
>
>

>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com
>
>


> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com