cancel
Showing results for 
Search instead for 
Did you mean: 

ERP 2005 Dialog instance in MSCS cluster

ThomasKjelsrud
Participant
0 Kudos

Hi,

We have installed ERP 2005 SR2 on a HA cluster environment (MSCS) on Windows 2003 with MSSQL 2005. The CI is installed locally on node A and the DI is installed locally on node B. The database is setup to run on node B as well.

We figured that both the CI and the DI should be running at the same time, but this seems to cause some issues with the processing of background jobs and RFC communication to one external system. I could not find anything about this in the installation guide for ERP 2005.

When we stopped the DI on node B, this problem disappeared.

<b>Update:</b> We have 4 DI's (application servers) installed outside the cluster, so the DI in question is the DI which is installed on node B.

<b>Can anyone confirm if the CI and DI is intended to run simultaneously, or if the DI should be brought online ONLY when node A (the CI) fails?</b>

Thanks!

Best Regards,

Thomas

PS: useful help will be rewarded.

Message was edited by:

Thomas Kjelsrud

Accepted Solutions (1)

Accepted Solutions (1)

vincentlim826
Employee
Employee
0 Kudos

Hi,

My understanding is that CI doesn't need to care because CI has nothing to do

with DI, because CI is not dependent of DI, but DI is dependent of CI.

If CI failed, DI will be affected. If DI fails, CI will not be affected

unless DI has critical services like updates.

My guess is they are ok to run simultaneously.

cheers,

Vincent

Former Member
0 Kudos

Thomas,

As long as SCS and ASCS are clustered, they will take care of the fail over and send the message to all application servers. CI and DI can run simultaneously. Even CI dies, SCS and ASCS will redirect the traffic to the application server. If you dont want CI to take the traffic, use logon group and include only the application servers. Once done, setup a group in the SAPGUI thru which the users will login.

Hope this helps.

Regards,

Ramesh Rajamohan

Answers (1)

Answers (1)

ThomasKjelsrud
Participant
0 Kudos

We figured that since we issues with having both instances running at the same time, we are going with the DI offline untill we figure this on out.

Thanks.