8 System Administration

This chapter describes the following system administration workbooks and wizards:

Auto Workbook Maintenance Wizard
Workbook Batch Category Management
Hierarchy Maintenance Workbook
Security Administration Workbook
Measure Analysis Workbook

These workbooks and wizards are found in the Administration task in the taskflow.

Figure 8-1 Administration Workbooks and Wizards

Note:

The Alert Manager Wizard is described in the Oracle Retail Predictive Application Server User Guide for the Fusion Client.

The Translation Administration workbook is described in the "Internationalization" chapter.

When working with a global domain, the following administration workbooks are available only in the master domain:

Hierarchy Maintenance
Password Policy Administration
Security Administration
Translation Administration
Workbook Batch Category Management

All other administration workbooks are available in both the local and master domains.

Auto Workbook Maintenance Wizard

The Workbook Auto Build feature allows users to have workbooks built by the wbmgr utility. Workbooks built in this way are added to the auto build queue. When workbooks are built in this manner, users do not have to spend time making selections in the wizard and waiting for the workbook to build.

Note that for a global domain environment, users are asked to select a domain to work in before the wizard executes.

The Workbook Auto Build feature works through the Workbook Auto Build Maintenance wizard. This wizard steps the user through the processes of adding and or deleting workbooks from the auto build queue.

Adding a Workbook to the Auto Build Queue

Workbooks in this queue are designated to be built automatically on a specified regular basis as part of the nightly batch run.

On the Activity Taskflow pane, click the Expand icon next to the Administration activity. The Administration activity appears.
In the Administration activity, click the Expand icon next to the Administration task.
Under Administration task, select the Create New Workbook icon next to the Auto Workbook Maintenance step. The Workbook Wizard window appears.
In the Workbook Wizard window, select Add a workbook and click Next.
Select a workbook template type and then click Next.
Select an owner for the workbook and then click Next.
Enter relevant information in the following fields:
- Build Label: Name of the auto build workbook.
- Build Frequency (in days): Frequency in days with which the workbook should be built.
- Next Build Date: Date (in mm/dd/yyyy format) for the next build.
- Category: The category to which the workbook should belong. See "Workbook Batch Category Management" for more information.
In the Please select the saved access for this workbook area, select User, Group, or World to specify the saved access for the workbook.
In the Please select the group that owns this workbook area, select the group that owns the workbook.
Click Next to initialize the wizard for the workbook template selected in step 5. The choices made are saved under the name specified in the Build Label field.

Deleting a Workbook from the Auto Build Queue

To delete a workbook from the Auto Build Queue, complete the following steps:

In the taskflow, click the Expand icon next to Administration. The Administration panel appears.
In the Administration panel, click the Expand icon next to Administration.
Under Administration, select the Create New Workbook icon next to Auto Workbook Maintenance. The Workbook Wizard window appears.
In the Workbook Wizard window, select Delete workbooks, and click Next.
Select the workbook or workbooks to delete from the auto build queue.
Click Finish to delete the workbooks.

Editing a Workbook in the Auto Build Queue

To edit the settings of an auto build workbook, complete the following steps:

In the taskflow, click the Expand icon next to Administration activity. The Administration activity appears.
In the Administration activity, click the Expand icon next to Administration task.
Under the Administration task, select the Create New Workbook icon next to Auto Workbook Maintenance step. The Workbook Wizard window appears.
In the Workbook Wizard window, select Edit workbook settings, and click Next.
Ensure that the OK radio button is selected and then click Finish. The Edit Auto Workbook Settings window appears.
In the Edit Auto Workbook Settings window, make the relevant changes in the following columns:
- Category: The category to which the workbook should belong. See "Workbook Batch Category Management" for more information.
- Frequency (in days): Frequency (in days) with which the workbook should be built.
- Save Group: From the drop-down list, select the group that owns the workbook.
- Workbook Name: Name of the workbook.
- Next Build Date: Date (in mm/dd/yyyy format) for the next build.
- World Access: Select this option to make the workbook accessible to all users.
  
  Note:
  The Owner and Template columns are read-only.
After you make your selection, for the changes to take effect, click the Commit icon on the global toolbar. You can also choose to click Commit in the File menu.

You can choose to save this workbook by clicking the Save icon on the global toolbar or clicking the Save option from the File menu.

Workbook Batch Category Management

A category is defined as a group of related workbooks for batch processing purposes. As an administrator, you can create new categories that auto workbook queue entries and batch workbook refresh entries can be assigned to. Each entry can be assigned to only one category. By default, each entry is assigned to a master category called Default. If a category is deleted, the entries assigned to that category are reassigned to the Default category.

When setting up auto workbooks, users can assign a category to an auto workbook and then run the build of a category that a group of entries have been assigned to. This is useful because it allows users to build only the workbooks they need to work with. These categories can also be used when entering workbooks into the refresh queue with the wbbatch utility. Just as with building workbooks, users can refresh select workbooks based on the defined category. These categories are created with the Workbook Batch Category Management wizard or with the wbbatch utility. For more information about the assignment of categories, see the "Auto Workbook Maintenance Wizard" and "Managing the Workbook Batch Queue Using wbbatch" sections.

In a global domain, the workbook batch category collection is global and stored in the master domain. It is shared by all local domains.

Workbook Batch Category Management Wizard

The Workbook Batch Category Management wizard allows users to add and delete categories as well as edit the labels of the categories. To access this wizard, complete the following steps:

Click the New Workbook icon in the Workbook Batch Category Management step.

Figure 8-2 Workbook Batch Category Management Wizard

The Workbook Batch Category Management Wizard opens.

Adding a Category

To add a category, select Add Category and enter a name and label for the category.

Name: The category name is restricted to standard alphanumeric characters. It cannot contain spaces. This name is used when specifying the category in the wbbatch utility. After a category has been created, this name cannot be changed.
Label: The category label is displayed on the workbook template wizard pages. It can be in any language and can contain spaces. Category labels are case sensitive and must be unique.

After you have entered a name and label, click Finish. The category is created.

Figure 8-3 Adding a Category

Deleting a Category

To delete a category, select Delete Category and select the category you want to delete from the list. Click Finish.

Figure 8-4 Deleting a Category

Changing a Category Label

To change the category label, select Change Category Label. Select the label you want to change and enter the new one. Click Finish.

Note:

Category names cannot be changed.

Figure 8-5 Changing a Category Label

Hierarchy Maintenance Workbook

RPAS can be used to set up and maintain user-named and user-defined dimensions within hierarchies. Hierarchy Maintenance is the means by which custom-created dimensions within a hierarchy can be established and maintained through the application interface in order to meet individual business needs.

When RPAS is installed, implementation scripts define the dimensions and hierarchical structures specific to the customer's organization. For example, the system can be built to recognize that SKUs roll up into styles, styles roll up into product classes, and so on within the product hierarchy. Occasionally, you might want to group products according to some ad hoc personal design to suit a particular business need. You can group arbitrary items in a hierarchy to use in functions such as forecasting, replenishment, and measure analysis. These user-defined groupings act as normal dimensional levels. In other words, they allow the user to roll data up from lower levels of aggregation along the hierarchical paths that you define.

For example, suppose experience has shown that the accuracy of forecasts for your top 50 products (A products) reflects the relative accuracy of all forecasts. Therefore, you would like to group elements within a user-defined dimension as the top 50 products by designating them 'A Products.' Then, when you select products in a wizard or look at data in a view, you can change the rollup to your user-defined dimension to see your top 50 products grouped together.

Note:

Your collection of 50 products may comprise elements from a wide range of product classes or departments, and your grouping scheme may have little to do with the normal dimensional relationships of these items in the product hierarchy.

The group of items you designate as 'A Products' may change over time as consumer preferences change. From this example, you can see that user-defined dimensions can be used to create any ad hoc groupings to provide additional support in analyzing, selecting, or summarizing data in Demand Forecasting. The Hierarchy Maintenance interface allows you to change the nature of the groupings as required.

The number and names of user-definable dimensions are set by your company when an RPAS-based solution is initially installed. The positions within each dimension and their associated labels can be altered and maintained through the hierarchy maintenance process.

Remember that any hierarchy in RPAS can have user-defined dimensions within it as long as they are set up by your company at the time of installation. The examples in this section refer to the Product hierarchy, but other hierarchies could be maintained in the same way.

Hierarchy Maintenance Example

Suppose you want to designate SKUs in your product hierarchy as either A, B, or C products so that you can group these items together when you view information such as forecasting, replenishment, or measure analysis reports.

To do this, you need to maintain a user-defined dimension that allows you to map the SKUs to the various positions of your classification scheme (A, B, or C). The user-defined dimension used in the following example is named Product Status. To maintain this user-defined dimension, use the Hierarchy Maintenance Wizard.

Hierarchy Maintenance Wizard

The first step in maintaining hierarchies is to access the Hierarchy Maintenance Wizard. In this wizard, select the SKUs that are mapped to the various positions of the user-defined dimension. Responses to prompts in the wizard are used to format a new Hierarchy Maintenance workbook.

Hierarchy Maintenance View

The Hierarchy Maintenance view displays the position assignment fields for the selected custom dimension. Edit the cells associated with the custom dimension as required.

Returning to the example dimension Product Status: You want to classify each selected SKU in your workbook as either an A Product, a B Product, or a C Product. This example provides only three positions, or values, in the Product Status dimension; however, you can enter any character string in an individual SKU's Product Status cell. This new string is treated as a separate user-defined grouping. If this is the first time a particular SKU has been mapped to the Product Status dimension, the label assigned to that SKU will not yet be defined. The Product Status field is automatically filled with 'Unassigned.'

Assign labels to each product with regard to the Product Status dimension. In the following example, products that were previously 'Unassigned' are now designated as A, B, or C Products.

Figure 8-6 Hierarchy Maintenance View

Note:

The RPAS system is case sensitive when a new position label is entered in the Hierarchy Maintenance workbook. After the workbook is committed, the typing of the group name is not case sensitive. For example, "B Product" can later be entered as "b product" after the "B Product" group label has been committed.

After making the A, B, or C Product designations for the selected SKUs, you must commit the workbook for any changes to take effect.

For this example, labels have now been assigned to the various positions within the Product Status dimension, and selected products in the product hierarchy have been classified with regard to the custom dimension. Demand Forecasting treats Product Status, a user-defined dimension, as a normal dimensional level within the product hierarchy.

Figure 8-7 displays the results when you access a quick menu in a wizard and change the rollup to the Product Status dimension. The products shown here are classified according to the position values (A Product, B Product, or C Product) that were assigned while maintaining the Product Status dimension.

Figure 8-7 Product Status Dimension Results

Maintaining a User-Defined Dimension Within a Hierarchy

Use this procedure to assign product or location items to custom-defined positions within a specialized dimension. Custom-created dimensions are distinct from those in the standard hierarchical roll-ups configured in the system implementation. You can use these dimensions in the same way that you use normal Demand Forecasting levels, aggregating data along these new hierarchical paths.

In the taskflow, click the Expand icon next to Administration activity. The Administration activity appears.
In the Administration activity, click the Expand icon next to Administration task.
Under the Administration task, select the Create New Workbook icon next to Hierarchy Maintenance step. A Workbook Wizard window appears.
Select the hierarchy to specify a user-defined dimension (for example, Product or Location). Only the hierarchies that have been set up to contain user-defined dimensions appear here.
Click Next.
Select the user-defined dimension to be updated. The number and names of available custom dimensions are set at installation.
Click Next.
From the Available Items in the selection wizard, select the items to be mapped to positions within the custom dimension.
Use the Add, Add All, Remove, and Remove All buttons or the drag and drop action to move your selection to the Selected Items section.
After all items to appear in your workbook have been selected, click Finish. The Hierarchy Maintenance workbook appears.
In the position assignment field for the custom dimension, assign a value to each product or location position in the workbook. Enter any text string in a cell. Each unique string is treated as a separate user-defined position within the custom dimension.
After you make your selection, for the changes to take effect, click the Commit icon on the global toolbar. You can also choose to click Commit in the File menu.

You can choose to save this workbook by clicking the Save icon on the global toolbar or clicking the Save option from the File menu.
To close the workbook, click Home on the top-right corner of the screen.
The Hierarchy Maintenance workbook is displayed. In the position assignment field for the custom dimension, assign a value to each product or location position in the workbook. Enter any text string in a cell. Each unique string is treated as a separate user-defined position within the custom dimension.
Select Commit Now from the File menu to commit the changes to the master database. If desired, you may also save the workbook by selecting Save from the File menu.
To close the workbook, select Close from the File menu.

Security Administration Workbook

The security model in RPAS includes workbook templates, workbooks, measures, and positions. The levels of security are defined as measure level, position level, and workbook level.

Security Overview

This section provides the basic information on the security model in RPAS.

User and Group Security

During Fusion Client installation one or more user groups are specified via the input.security.group property. These groups are required to be created in the LDAP directory that the customer has associated with the Weblogic Server for authentication. It is not necessary for these groups to be present before the installation. They can be created after the installation also.

Users created as members of these groups gain access to the Fusion Client UI, as long as they are also present in the RPAS domains. For example, say that the group rpasusers is specified during installation. Users A and B are members of rpasusers, whereas user C is not. This means that A and B can access the application whereas C while logging in will receive an ”unauthorized” error message. (A and B must also be present in the RPAS domains; otherwise they will receive a "no solutions found" message.)

In course of time, it may be necessary to add and remove users. This can be done simply adding and removing them from the LDAP directory. It is not essential to remove them from the RPAS domains as well, but it is a good housekeeping practice.

An unusual need may arise where a user has to be provided access to the application even though the user is not a member of any of the groups configured for access during installation. Or, a whole new group needs to be provided access. This can be arranged for by one of the following methods:

Basic: Re-install the Fusion Client after adding the users and groups to the input.security.user and input.security.group properties, respectively. (It is assumed that the customer has kept the ant.install.properties file used in the previous install in a safe place, so that it can be used in the new install.)
Complex: Use Enterprise Manager Fusion Middleware Control web application hosted on the Weblogic Server (and accessed via URL http://<host>:<port>/em). Go to the Security Roles section of the Fusion Client application and add the new users and groups as members of the application role atlantis-users.

See Fusion Middleware Security Guide for information on how to use the Enterprise Manager Fusion Middleware Control application.
Restart application or WebLogic Server after this step.

If using second approach, you must remember to re-do the Enterprise Manager settings after a Fusion Client re-install. Otherwise, they will be lost.

Measure Level Security

Measures have access rights; these are read-write, read-only, or denied. Measures that are read-write or read-only may be selected in the extra measures and insert measure dialogs. RPAS ensures that read-only measures are not editable by the user, and the presence of read-only measures does not affect the ability to commit a workbook.

Measure security can be specified and changed through the Security Administration workbook. The Measure Rights view allows Read Only, Deny, or Read/Write access to a measure to be specified for each user.

A workbook template can override the security of a measure, but it can only narrow the security of that measure. For example, a measure can have read-write access for a user and a template can specify that all users have read-only access to the measure when a workbook is built. However, if the measure security is read-only, the template cannot expand the security of that measure to read-write. Measures that are explicitly made read-only by a workbook template are not expanded to read-write access by RPAS.

Note:

Refer to the Oracle Retail Predictive Application Server User Guide for the Fusion Client from more information on the Measure Analysis workbook.

Position Level Security

Position Level Security allows access control for dimensions on a position-by-position basis. This capability is completely optional. If position level security is not explicitly defined and configured, all users in a domain have access to all positions in all hierarchies. After the position level security is defined, access to a position can be granted or denied for individual users, users in a group, or for all users.

Position level security can be defined at levels (dimensions) at or above base (such as class in the product hierarchy) in any hierarchy other than calendar. As positions are added at a level/dimension lower in the hierarchy than where the position level security is maintained, access to those positions is automatically granted if a user has access to the parent position. For example, if security is maintained at the subclass level, users are automatically granted access to all the SKUs in a given subclass if they have access to that subclass. This includes those that were added after security was established.

Exactly one dimension in each hierarchy can be defined as the security dimension for the hierarchy. If a security dimension is defined for the hierarchy, all dimensions in the hierarchy have position level security enabled, but position security is set at or above the designated dimension. For example, if the class dimension is designated as the security dimension, an administrator can maintain access to positions in the class dimension or at any level above class.

To specify the security dimension for a hierarchy, use the RPAS Configuration Tools or the hierarchyMgr utility.

After a security dimension is defined for a hierarchy, all users in the domain default to having access to all positions in any dimension in the hierarchy. Additionally, users automatically have access to newly added positions to a domain. Views in the Security Administration workbook are used to control position access for individual users, user groups, or all users (referred to as world or default access). Three views are provided in this workbook for each hierarchy with a defined security dimension. The default view controls access to positions for all users (for instance, Prod Security Default); one view controls access to positions by user group (for instance, Prod Security Group); and the last view controls access to positions by individual users (for instance, Prod Security User).

Access must be granted at all levels for a user to have access to a position. This means that a position must have a value of true at the levels default/world, group, and user. Table 8-1 demonstrates how access is granted or denied based on all combinations of settings.

In the table, security is set by Position. Denied = False and Granted = True. Based on the settings for User, User Group, and World, the user is either granted or denied access, as shown in the Resulting Access column.

Table 8-1 Grant or Denial of Access by a Combination of Settings

User	User Group	World	Resulting Access
Denied	Denied	Denied	Denied
Denied	Denied	Granted	Denied
Denied	Granted	Denied	Denied
Granted	Denied	Denied	Denied
Denied	Granted	Granted	Denied
Granted	Denied	Granted	Denied
Granted	Granted	Denied	Denied
Granted	Granted	Granted	Granted

Position-level security is used when a user selects positions in the wizard process before building a workbook. Only positions to which a user has access are available for selection in the 2-tree, which are then included in the build of the workbook.

Note that position-level security, when used for a global domain environment on the same dimension on which it is partitioned, is used to guide a user to the domain or domains that user has access to. If a user only has access to positions within a single local domain, that user will be guided there on New Workbook. If a user has access to more than one, that user will be asked and can choose based on partition-level positions.

Similarly, Open by default only lists workbooks from those domains, and a user is only shown alert counts from those domains.

Workbook Security

Currently, workbook access is either granted or denied. If users have been granted access to a workbook, they can open, modify, and commit the workbook. No distinction is made between read-write-commit, read-write, and read-only access. Workbook access is automatically granted to the user that built it, and it may be shared with multiple groups or the world.

Note:

A user must have access to the workbook template in order to access the workbook, even if the workbook has world or group access rights.

Users with administrator status automatically have access to all workbook templates. By default, administrators have access to all workbooks that are saved with world access. If a workbook is saved with group access, administrators can only access the workbook if they are members of the default user group of the user who saved the workbook.

Note that the Open dialog initially shows only workbooks owned by the current user and in domains for which the user has position level security access. This is not the same as workbook access, however, and a user may have access to workbooks saved by others in other domains by using View > Other Domains in the Open dialog by others Word or Group.

Another aspect of workbook security is the ability to set limits for the number of workbooks that a user can have saved at any given time. Limits can be set for a user per template, for a user group per template, or for a template for all users. The limits are evaluated in the above order, which means that a limit defined at user-template overrides any values defined at group-template or template. If the above limits are not defined, the default value is one billion.

The limits are checked when the workbook build process is initiated. When the limit is reached, an error message displays informing the user that the workbook build process cannot complete because the limit has been reached. The message also lets the user know what that limit is. The wizard process then terminates.

Administrative users have full access to all workbook templates, regardless of the access rights that other admin users may assign to them in the Security workbook. The administrative user can build the Security workbook to change the access right back, so the nominal assignment does not matter for administrative users.

Non-administrative users do not have access to Security template and User Administration template groups even if the administrator inadvertently assigns them access rights.

Security Administration Workbook

The Security Administration workbook is only available to system administrators. After users and user groups are created, the administrator may set up and maintain access permissions to workbook templates and measures within those workbook templates. This workbook allows the administrator to determine which templates individual users can access, as well as the measures that users can access while manipulating workbooks in the system. The user can also specify and restrict the measures that are available to be added to a given workbook template. Setting access permissions in this way provides a high degree of measure security because users can be restricted to viewing and editing only certain relevant measures.

All administrative users have full access to all workbook templates, regardless of the access rights that they were assigned in the Security workbook by other administrative users. The administrative user can build the Security workbook to change the access right back, so the nominal assignment does not matter for admin users.

The Security Administration workbook has the following views:

Workbook Template Rights View
Workbook Template Measure Rights View
Measure Rights View
Dimension Modification Rights View
Position Level Security Views
Workbook Template Limits Views
Max Domain Session Limit View
Max User Session Limit View

Security Template Administration also allows the administrator to modify the label, Admin status, and default workbook template associated with each user. The administrator can also access this workbook template to modify the labels associated with user groups, workbook templates, and workbook template groups. Using this workbook, the administrator can:

Assign and modify access rights of each user to all workbook templates. User/template permissions are set in the Workbook Template Rights view.
Determine which optional measures are to be accessible through individual workbook templates. Template/measure permissions are set in the Workbook Template Measure Rights view.
Assign and restrict user access to individual measures. User/measure permissions are established in the Measure Rights view.

Workbook Template Rights View

The Workbook Template Rights view is used for setting and maintaining the access permissions of each user to specific workbook templates.

The view contains a drop-down list for each available workbook template and user combination. To grant a user access rights to a workbook template, select one of the following options from the drop-down list for that workbook template:

DeniedRead OnlyFull Access

After a user's profile is changed, those changes must be committed to the database in order for them to take effect.

The Read-Only permission on a template applies only to actual workbooks created by the template. For templates that do not generate a workbook, but only run through a wizard process for other purposes, the Read-Only permission for a user on that template does not prevent the user from running through the wizard. This applies to standard RPAS templates, such as Add User and Delete User, but it may also apply to various application-specific templates.

Workbook Template Measure Rights View

The Workbook Template Measure Rights view allows administrators to determine which registered measures are available for optional inclusion in newly built workbooks.

When a measure is initially registered as a public measure, all templates default to having access to that measure. This means that it is possible for this measure to be added to a workbook template, even if it is not one of the standard measures displayed when a workbook of that type is built. Some new workbook wizards include a dialog that prompts users to select any additional measures to be included in the workbook build. By default, all newly registered measures are included on this list of available additional measures. The other method of inserting new measures into a workbook is through the Insert Measure command.

The Workbook Template Measure Rights view is used to modify template/measure permissions, which allow only certain templates to optionally include specified measures in new workbook builds.

This view contains a check box for each available workbook template and registered measure combination.

Measure Rights View

The Measure Rights view allows the administrator to restrict user access to individual measures on a user-by-measure basis. User/measure permissions are initially determined by the system by integrating the current user/template and template/measure settings and applying the following rule: "A user cannot have access to any measure that is not available in at least one template to which the user has access."

Permissions can be made even more restrictive on a user-by-measure basis by using the Measure Rights view to deny users access to measures that they would normally be permitted to edit.

The view contains a drop-down list for each available user and registered measure combination. Three security options are available: Denied, Read-only, Read/Write. Denied prevents the user from viewing data. Read-only allows the user to view the data. Read/Write allows the user to edit data values. However, a commit rule must be configured for a measure for data to be committed to the RPAS data store.

A measure has the security rights it had when it was inserted in the workbook. The change in measure security rights is only reflected in new workbooks when that measure is inserted.

Note:

If a measure that has dependent measures is inserted into a view, those dependent measures will also be inserted into the view. If the dependent measures have denied measure access, they are still inserted into the view, but they are hidden by default. These measures can be made visible on the Show/Hide dialog box.
The Measure Rights view contains only public measures, that is, measures that can be optionally included in a view, depending on choices made in a new workbook wizard. Measures that are registered as private measures do not appear in this view. If there are no public measures available to be displayed in this view, the view will not be built.

Dimension Modification Rights View

The Dimension Modification Rights view allows the administrator to determine which dimensions, if any, a user can modify. The view contains a check box for each available user and dimension combination. A check mark in the cell indicates that the user is permitted to modify the specified dimension.

After changes are made to a user's dimension modification rights, they must be committed before they take effect.

Position Level Security Views

The position-level security views are used to grant or deny access to positions for individual users, user groups, or all users. Position-level security is set for a specific dimension of a hierarchy (other than calendar). See the Oracle Retail Predictive Application Server Configuration Tools User Guide for more information on setting position-level security dimensions.

For each hierarchy/dimension that has position-level security enabled (normally just a single hierarchy/dimension), there are three views: one each for user, user group, and world/all users.

After changes are made to position-level security, they must be committed before they take effect.

Workbook Template Limits Views

The Workbook Template Limit views are used to limit the number of workbooks that the user can have saved. Limits can be set for a user per template, for a user group per template, or for a template for all users. The limits are evaluated in the above order, which means that a limit defined at user-template overrides any values defined at group-template or template. If the above limits are not defined, the default value is one billion, but it is not displayed in the workbook.

The limits are checked when the user begins the workbook build process. If the limit has been reached, an error message appears that informs the user that the workbook build process cannot complete because the limit has been reached. The wizard process then terminates.

Max Domain Session Limit View

The Max Domain Session Limit view is used to limit the number of user sessions that can be attached to a single domain by all users of that domain. The limit is set at the domain level. In a global domain environment, the same limit is applied individually to each local domain and the master domain.

This limit is checked during user login. If the limit has been reached, an error message appears to inform the user that the login has failed because this limit has been reached.

Max User Session Limit View

The Max User Session Limit view is used to limit the number of concurrent user sessions that can be attached to a single domain by the same user at the same time. The limit is set per user so that the administrator can control the maximum number of concurrent sessions that are allowed for an individual user. In a global domain environment, the same limit is applied individually to each local domain and the master domain.

This limit is checked during user login. If the limit has been reached, an error message appears to inform the user that the login has failed because this limit has been reached.

Using the Security Administration Workbook

Note:

These tasks are performed through the Security Administration workbook. This workbook is only available to system administrators.

Accessing Security Administration

On the Activity Taskflow pane, click the Expand icon next to Administration. The Administration panel appears.
In the Administration panel, click the Expand icon next to Administration.
Under Administration, select the Create New Workbook icon next to Security Administration.

Setting or Modifying Users' Access to Workbook Templates

The Workbook Template Rights view enables you to set one of the following access privileges to each workbook template for a user:

Denied
Read-only
Full Access

To set or modify a user's access to workbook templates:

On the Activity Taskflow pane, click the Expand icon next to Administration. The Administration panel appears.
In the Administration panel, click the Expand icon next to Administration.
Under Administration, select the Create New Workbook icon next to Security Administration.
On the Workbook Template Rights view, for each workbook template, select one of the access privileges for the users you want.
After you make your selection, for the changes to take effect, click the Commit icon on the global toolbar. You can also choose to click Commit in the File menu.

You can choose to save this workbook by clicking the Save icon on the global toolbar or clicking the Save option from the File menu.