Login into CMC keep switching between production and test servers

[Former Member]

We are using BO XI R2, and we have a production server (cms=sfbo) and test server (cms=sfqbo). We are having an issue after restarting cms server for the test server. Now when we tried to login to the CMC using the administrator login, it keeps getting mixup between the two servers.

Can anyone shed some lights on this as I am a newbie.

Thanks,

Tim

[denis_konovalov · Accepted solution]

Could you please clarify what you mean by "geting mixed up" ?

If Sergver A points to CMS A and server B points to CMS B - there should not be any mix ups.

[Former Member · Accepted solution]

The web page that you log into CMC through keeps the last server used in a cookie (I believe), so it is remembering the last server used. The server shows on the logon page, so just make sure it has the right server name. They are quite similar, so I can understand how that could be confused or missed!

HTH,

Carl

[Former Member · Accepted solution]

Hi Denis and Carl

Thanks for your time and sorry for the late reply,

When I said that the it's getting mixed up was that when I login into the production server (SFBO), it will connect to it successfully the first time, but when I logout and login again, it will point to test server (SFQBO). Sometimes I have to logout/login a few times to get to the production, but there is no definite pattern for this. Could this issue happened due to the Cluster setting?

This is our cluster setting in test server (SFQBO)

CMS Name: SFQBO.cms (SFQBO.SFAU.LOCAL)

Cluster Name: @SFQBO.SFAU.LOCAL

Cluster Members: SFQBO.cms (SFQBO.SFAU.LOCAL)

sfbo.cms (SFBO.SFAU.LOCAL)

Data Source: CMS

Database Name: sfdwdev;cms;microsoft sql server;09.00.3054

and the in production is

CMS Name: sfbo.sfau.local (SFBO.SFAU.LOCAL)

Cluster Name: @SFBO.SFAU.LOCAL

Cluster Members: sfbo.sfau.local (SFBO.SFAU.LOCAL)

sfbo.sfau.local (SFBO.SFAU.LOCAL)

Data Source: cms

Database Name: sfqdocs;cms;microsoft sql server;08.00.0760

I managed to overcome this issue by disabling all the related servers for SFBO in SFQBO using CCM --> Central Management Server -->disable/enable servers and the opposite in SFQBO.

Is it a right solution?

Edited by: TIM BALABAN on Apr 7, 2009 9:50 AM

[Former Member · Accepted solution]

Maybe this is a typo, but it seems one of the cluster members has the same name in test and production: SFBO.SFAU.LOCAL

Could it get mixed up there?

Caroline

[Former Member · Accepted solution]

Hi Caroline,

This setup has been working until recently when I need to restart the test server and it mixed up. Does this mean that I have to remove the sfbo.sfau.local (SFBO.SFAU.LOCAL) from the test server? If it is, how can this be done?

Thanks,

Tim

[denis_konovalov · Accepted solution]

At some point somehow you had one environment or the other pointing to each other CMS DB , that's how it got mixed up.

Now you need to make sure following :

1. Each CMS points to it's own CMS DB

2. Cluster names are different

3. Cluster members regisry entry on both servers only lists correct clusters and servers

4. web.xml or web.config files on each server has correct information.

[Former Member · Accepted solution]

Hi Denis,

Thank you for your tips.

I have checked point 1 & 2 of tips and they are pointing to the right DB with the right cluster names. But I need some advise on Point 3

3. Cluster members registry entry on both servers only lists correct clusters and servers

I have looked registry entry on both server with the following results:

On the SFBO (Production), the cluster members for @SFBO.SFAU.LOCAL contains the correct cluster (sfbo.sfau.local),

But on the SFQBO(Test), the cluster member for @SFQBO.SFAU.LOCAL contains both the test and production cluster (sfbo.sfau.local & sfqbo.sfau.local).

Does this mean that I need to remove the production cluster name from the test or could this setup for fail over purpose?

Currently with this setup, it works fine, but if we restarted our test server, then the mix-up will occur.

Could anyone please shed some more ideas on this issue.

Thanks,

Tim

[denis_konovalov · Accepted solution]

Yes , you need to remove prod server listing from test server registry.

also, search your machine for .businessobjects directory inside which is a file called clusterinfo.1200.properties edit it and make sure on test it only has test server info and on prod only prod server info.

[Former Member · Accepted solution]

Hi Denis,

Thank you for your help. I have removed the server list from the registry and it works for now even though I didn't manage to edit the clusterinfo file as I could not locate the file. I'll keep this mind in case if I need to edit it in the future.

Cheers