Admin account in CMC XI 3.1

[Former Member]

Hi guys,

I have created a new backup admin account in CMC BO XI 3.1 and added it to Administrators group so it can inherit the access levels, but when try to login to CMC with this account, I get blank screen...?!

When I login as administrator to CMC, I can see in Sessions that the new user is in - has a session.

Anyone with such an experience?

Cheers

Oto

[Former Member · Accepted solution]

Hi Oto,

I tried to replicate the issue that you are facing i.e created a test Emterprise user and made it a member of the Administrators group but I do not get a blank screen when I login using this test user. You can try using a different browser.

As far as the other issue is concerned i.e session being occupied by this test user even after logging off thus consuming licenses. For this you need to do some settings.

In XIR2, the setting <session Timeout>20</session Timeout> and enabling the listener will invalidate the enterprise session and will decrease the license count on CMC.

BUT THIS WILL NOT WORK IN XIR3 & 3.1 i.e. even after 20 min timeout, your session count doesnu2019t drops on BOE causing major issues.

This is how it works on XIR3 & 3.1:

Regarding to session on XIR3 & 3.1, there are four main components

1] Logon Token:- an entry in web.xml created by the application (CMC/InfoView)when the users first log into the system. Lifetime is 8 HRS.

2] HTTP Session:- i.e Your application server session. 20 min configurable in web.xml

3] Enterprise Session:- A newly added registry entry called at HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\CMS\Instances\ningli.cms, set IdleSessionTimeout=600000 default 10 min . InfoView will ping the Central

Management Server (CMS) every two to three minutes. The enterprise session will stay active for 10 minutes past the last ping from the client.

4] CMS Failover Token:- The default time-out is 30 minutes can be configured by setting u2013failovertimeout parameter on CMS command line form CMC

So in order to release license count do the following steps:

1] In web.xml set logontoken.enable=false, session-timeout=5 (YOU NEED TO DO IT IN ALL WEB.XML OF INSTALLED APPLCATIONS).

Note: If you are using .net then you need to make these changes in the web.config files and in case of Java the changes need to be done in the web.xml files.

2.] In Registry set HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\CMS\Instances\ningli.cms, set IdleSessionTimeout=60000 (1min)

Note: Please take a back up of the registry before making any changes to the same

3] Add -failovertimeout 1 to the command line parameter of CMS form CMC

4] Login to InfoView and wait for 6 min to get web session and enterprise session timeout

5] Go to CMC > session count decreased and license count is released.

[Former Member · Accepted solution]

Venkat,

thanks for your answer, though helpful it doesn't resolve my issue. I have tried dif. browser (Firefox), but with same problem...:(

[BasicTek · Accepted solution]

the symptoms indicate you are not a member of the administrators built in group. Could someone have renamed it or is it possible the user wasn't added properly?

When logging into the CMC when not a member of administrators you would receive a blank screen in XI 3.x

Regards,

Tim

[Former Member · Accepted solution]

Thank you Tim,

the user was added to the administrators group, but what I suspect here that the administrators group rights are not correctly set since we imported it from BIAR file of previous XI r2 deployment and the security in that version works differently. My problem now is that I can't find the differences between administrator and the new user who I want to become backup administrator with all rights as the original one.

Cheers

Oto

[BasicTek · Accepted solution]

Have you tried the built in administrator? It should be difficult to block access to that user as it has special rights. In XI 3 the new delegated administrator function allows other administrators to fall under the same rules as regular users.

After that I'm thinking you should open a case and have an admin engineer take a look.

Regards,

Tim

[Former Member · Accepted solution]

Hi Venkat,

thanks for your answer, your solution fixed my issue.

Anyway, I think this configuration-fix should be part of the official BO/SAP documentation, because in a concurrent-license installation the problem of the license release at the end of the related http session might be a major issue.

[Former Member · Accepted solution]

Venkat Patnaik you are the best! Finally a post that works. Your process for fixing the timeout period for InfoView works great. With your numbers I find that the session times out after about 3 minutes. I am going to play around with the numbers to see if I can get things closer to five minutes. I also want to narrow down which web.xml files need to be edited specifically for InfoView only.

Thanks a lot!

[BasicTek · Accepted solution]

Just as an FYI trying to manipulate the session timeouts this way has caused other issues for customers that have longer running reports. If you have random error messages, reports that end for no reason, and customers complaining about sessions timing out, you may want to revert these settings and verify if they are causing the issue.

To manage sessions in 3.x there are some bugs that leave them open too long, BOE customers are urged to use CPU or named user licenses, Edge 3.x and CRS2008 customers can use SDK code to terminate the sessions while waiting for patches.

Regards,

Tim