Problem with two instances on XI server

[Former Member]

Hello Experts,

We are planning to have 2 instances on XI server, on 01 and 02, for load balancing.

Our target is to make 01 as central instance, so even if instance 02 will go down, the critical interfaces pointed to 01 should work.

We have most of scenarios through proxy, but some of them are from soap to soap or jdbc and etc.

Web is calling critical interfaces with instance 01 and noncritical interfaces with 02 instance. But how can i make sure that that interface with go throught 01 and not through 02?

I tried to check log of one interface, Web is calling this interface from 02 instance.

See the below log:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Inbound Message

-->

- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Date>20090210</SAP:Date>

<SAP:Time>135420</SAP:Time>

<SAP:Host>sapxiq02</SAP:Host>

<SAP:SystemId>XIQ</SAP:SystemId>

• <SAP:SystemNr>01</SAP:SystemNr> *

<SAP:OS>AIX</SAP:OS>

<SAP:DB>ORACLE</SAP:DB>

<SAP:Language />

<SAP:ProcStatus>000</SAP:ProcStatus>

<SAP:AdapterStatus>000</SAP:AdapterStatus>

<SAP:User>PIAFUSER</SAP:User>

<SAP:TraceLevel>1</SAP:TraceLevel>

<SAP:Logging>1</SAP:Logging>

<SAP:LogSeqNbr>000</SAP:LogSeqNbr>

<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>

<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>

<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>

<SAP:PipelineElementId />

<SAP:PipelineService />

<SAP:QIdInternal />

<SAP:CommitActor>X</SAP:CommitActor>

<SAP:SplitNumber>0</SAP:SplitNumber>

<SAP:NumberOfRetries>0</SAP:NumberOfRetries>

<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>

<SAP:TypeOfEngine client="110">CENTRAL</SAP:TypeOfEngine>

<SAP:PlsrvExceptionCode />

<SAP:EOReferenceRuntime type="TID" />

<SAP:EOReferenceInbound type="TID" />

<SAP:EOReferenceOutbound type="TID" />

<SAP:MessageSizePayload>335</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>4934</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>335</SAP:PayloadSizeRequest>

<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>

<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>

<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>

<SAP:Reorganization>INI</SAP:Reorganization>

<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>

<SAP:InterfaceAction>INIT</SAP:InterfaceAction>

<SAP:RandomNumber>55</SAP:RandomNumber>

<SAP:AckStatus>000</SAP:AckStatus>

<SAP:SkipReceiverDetermination />

<SAP:Sender_Agreement_GUID>E91C2397DEFB3DF4BEEEC8B0BFF0C5B0</SAP:Sender_Agreement_GUID>

</SAP:RunTime>

Does this mean that it is still going through 01 instance?

Please help me out in this.

Thanks,

Hetal

[JoelTrinidade · Accepted solution]

Hi Hetal,

Refer the SAP Notes 734931 & 825116.

Regds

joel

Rwd points any how.

[Former Member]

hi,

In abap platform with message server (port 36xx) , I suggest you check your port.

rgz

Eric

[Former Member]

Do any one have any other solution?

[Former Member]

Hai Hetal

Normally if we want to go more than one instance then we will use Logon Load balancing

This techniqe is very userful for performance of the server (Transaction SMLG)

Thanks&Regards,

Praveen Kondabala

[Former Member]

Thanks Praveen.

We have already created 2 instances.

But we forcibly want to decide that 1 interface should go through instance number 1 and the second one should go through instance number 2.

Which is not happening.

How to do that?

Thanks,

Hetal

[Former Member]

Hello Hetal

Generally we have the Transaction SMLG

in that we can assingn the groups to the partiaculr instances

user groups can create in SUGR transaction

Please try if possible then it will work

Thanks &Regards,

Praveen Kondabala.