Tuning Admin Cache Initialization

Waveset provides two different queries that you can use to determine which Waveset users have Administrative rights. One of these queries can be slow to execute when there are lots of users in the Oracle Waveset repository. Waveset executes this slow query during AdminCache initialization, which occurs during Waveset startup.

Waveset now uses the faster query by default; resulting in much faster server start-up times for installations with large numbers of users in the repository. However, under certain conditions the faster query may not produce the correct results. If you upgraded your installation from version 5.0, some Administrative users may not have the attribute used by the new query correctly set.

• Refresh all Administrative users by importing the following XML, which sets the new query attribute properly:

  <ImportCommand type='refreshType' targetType='User'> <List> <AttributeCondition attrName='MemberAdminGroups' operator='isPresent' operand=''/> <AttributeCondition attrName='ControlledObjectGroups' operator='isPresent' operand=''/> <AttributeCondition attrName='AdminRoles' operator='notPresent' operand=''/> </List> </ImportCommand> <ImportCommand type='refreshType' targetType='User'> <List> <AttributeCondition attrName='AdminRoles' operator='isPresent' operand=''/> </List> </ImportCommand>

• Disable the new query, and continue to use the old query by adding the following line to Waveset.properties on each Waveset server: admincache.fastinit=false.