The System Administrator Console is a Web-based user interface that is associated with the system administrator responsibility. It is used during the development, implementation, and maintenance phases of an application or deployment. During the development phase, developers and consultants use the System Administrator Console to seed out-of-the-box capabilities and features. These include, but are not limited to, users, permissions, roles, session parameters, page flows, and diagnostic tests. During the implementation phase, consultants or implementation engineers use the System Administrator Console to configure out-of-the-box capabilities and features to meet the particular needs of each customer deployment. During the maintenance phase, IT professionals use the System Administrator Console to troubleshoot deployment problems, tune deployment performance, and monitor system activity.
Features are divided into the following areas for the System Administrator Console:
Users
Settings, including Security, Site Preferences, and System.
Deployment, including System Statistics
Design, including Page Flows, Declarative Components, and Homepage
For information on setting up users, see the Oracle CRM User Management and Spreadtable online help available under Applied Technology in the Contents tab.
In the Security subtab, which is located under the Settings tab, you can control access to application resources and view security-related alerts.
This section offers an introduction to Security Framework concepts. For step-by-step instructions on how to use the Security screens, please see the topic Managing Security.
The following table explains important Security concepts.
| Term | Definition |
|---|---|
| Permission | A permission is a unit of privilege that is granted to a user. It usually serves to grant a certain type of access to a resource. Resources are application elements such as JSP pages, objects, or methods of objects. A resource can have unique permissions for each way that it can be accessed. A permission is implemented as a string. If a resource is protected by a permission, then any user accessing the resource must have the permission required to access it. Permission names are case-sensitive. Permissions cannot be directly assigned to users. Instead, permissions are grouped into roles and roles are then assigned to users. In the Security subtab, you can view, create, and delete permissions. You can also specify which permissions are mapped to each role, and vice versa. |
| Roles | A role is a group of permissions which can be assigned to a user. Like permissions, roles are implemented as strings. Role names are not case-sensitive. For example, let's suppose there is a JSP page "abc.jsp" that requires the permission "PERM_ABC." A user logs in and tries to access abc.jsp, but he or she can't do that unless he or she has permission "PERM_ABC." You want the user to be able to access the page, so you assign the role "ROLE_ABC" (which contains permission "PERM_ABC") to the user. When given the appropriate role, the user is able to access the page. In the Security subtab, you can view, create, and delete roles. You can also specify which roles are mapped to each permission, and vice versa. |
In the Site Preferences subtab, which is located under the Settings tab, you can set up the Interapplication Bar.
This section offers an introduction to Interapplication Bar concepts. For step-by-step instructions on how to use the Interapplication Bar screens, please see the topic Setting Up the Interapplication Bar.
The following table explains important Interapplication Bar concepts.
| Term | Definition |
|---|---|
| Interapplication Bar | The Interapplication Bar (also sometimes referred to as the Application Switcher) allows end users to seamlessly switch between applications within the E-Business Suite. It is a set of customizable links that displays at the top of every page in HTML-based CRM applications. Each customizable link is called a "navigation group." For example, a system administrator might want to create a navigation group called "Sales." In the System Administrator Console, he or she can map sales-related applications such as Sales Online, TeleSales, and Sales Compensation to the navigation group called "Sales." (Similarly, he or she could create a navigation group called "Marketing" and map applications such as Marketing Online, iMarketing, and Campaign Management to it.) When an end user logs in who has responsibilities for sales applications, the end user will see "Sales" as a link in the Interapplication Bar. In the Profile screens, the end user can configure which responsibility he or she wants to associate with the "Sales" navigation group. From then on, when the end user is working in the E-Business Suite, he or she can click the "Sales" link at any time to easily switch to his or her sales responsibility |
| Navigation Group | A navigation group is a customizable group of applications with defined responsibility settings. Each navigation group is represented as a link within the Interapplication Bar. In the Site Preferences subtab, you (as the system administrator) can map CRM applications into navigation groups. Additionally, from the navigation group setup screen, you can create, delete, activate, deactivate, and specify the display order of navigation groups. After you have set up navigation groups for a deployment, based on their granted responsibilities, end users will be able to associate each navigation group with one of their responsibilities. |
For information on using the cache features, see Caching Framework, Oracle E-Business Suite System Administrator's Guide - Configuration.
In the Declarative Page Flow subtab, which is located under the Design tab, you can set up and manage the components of the Declarative Page Flows Framework: Physical Pages, Logical Pages, Rules, and Business Flows.
This section offers an introduction to Declarative Page Flow concepts. For step-by-step instructions on how to use the Declarative Page Flows screens, please see Using Declarative Page Flows.
The Declarative Page Flows Framework enables you to customize, upgrade, and troubleshoot the content and flow of JSPs within an application without making any modifications to actual code. The Declarative Page Flows Framework is based on the abstraction of JSPs into named logical entities. Consequently, you can achieve efficient management of content and flows by utilizing the screens provided in the System Administrator Console.
The following table explains important Declarative Page Flow concepts.
| Term | Definition |
|---|---|
| Physical Page | The name of a JavaServer Page (JSP). In the Declarative Flows subtab, you can view, register, and modify Physical Pages. |
| Logical Page | A named logical entity that has one or more Physical Pages mapped to it. Usually, each Logical Page represents a node within a Business Flow. In the Declarative Flows subtab, you can view, create, and modify Logical Pages. |
| Rule | A rule is defined by parameters and conditions and determines which Physical Page needs to be rendered or which Logical Page needs to display next. Rules evaluate to true when all of their conditions evaluate to true. You can utilize Rules to customize the page-to-page behavior of a Business Flow. In the Declarative Flows subtab, you can view, create, and modify Rules. |
| Business Flow | A sequential set of linked Logical Pages that usually corresponds to a business task. Business Flows can be linear or nonlinear, depending on whether or not there are context-sensitive conditions. Branching conditions are evaluated at each node. In the Declarative Flows subtab, you can view, create, modify, clone, and preview Business Flows. |
| Flow Cloning | In order to facilitate the easy upgrade of business flows which have been customized by a customer, a business flow can be cloned, thus creating a Flow Family of related business flows. In the Declarative Flows subtab, the Clone Flow screen allows you to generate duplicates of a given flow. |
| Flow Families | A flow family consists of an original business flow, a clone of the original business flow, and any customized clones which have been made. In the Declarative Flows subtab, the Flow Families screen allows you to view the contents of a Flow Family and select which flow is active. |
In the Declarative Components subtab, which is located under the Design tab, you can create and manage declarative UI components (Bins, Graphs, Reports, Graph/Report combinations, and LOVs) and their security settings.
This section offers an introduction to Declarative Components concepts. For step-by-step instructions on how to use the Declarative Components screens, please see Using Declarative Components.
The Declarative Components Framework allows you to quickly build UI components that display application-specific data in personalizable Bins, Graphs, Reports, Graph/Reports, or LOVs. The coding requirements are minimal to nonexistent and the components can be published on Oracle applications.
The following table explains important Declarative Components concepts.
| Term | Definition |
|---|---|
| Metadata | The Declarative Components Framework relies on the accurate definition of metadata. The framework uses the metadata to capture information about component headers, footers, columns, and other attributes. In the Declarative Components subtab, you can define the metadata for bins, reports, graphs, graph/report combinations, LOVs, and parameters. |
| Bin | Bins are small reports which display high level summary information in a tabular format. They generally display information regarding a single metric, such as "time period." If enabled and the appropriate security features are assigned, you can choose which bins to display on the home page and also choose the order in which multiple bins are displayed. In the Declarative Components subtab, you can view, create, modify, and remove Bins. |
| Report | Reports are similar to bins. They display information in a tabular format. In the Declarative Components subtab, you can view, create, modify, and remove Reports. Optionally, you can do the same for Graph/Report combinations. |
| Graph | A graph is a diagram that represents data pictorially. In the Declarative Components subtab, you can view, create, modify, and remove Graphs. Optionally, you can do the same for Graph/Report combinations. |
| LOV | The LOVs that you create can be used across applications. LOV means "list of values." It is a UI component that facilitates the completion of a text entry field when there are numerous values that may be assigned. LOVs are a useful alternative to drop-down lists, particularly in cases where displaying a long list of selections in a drop-down list would require excessive scrolling. In short, when using a LOV to complete a text entry field, you type a query into the field and then click a button labeled "Go." This opens a screen where you view a list of values that match the query you submitted. You can then select the value that you desire and return to the original screen, where what you selected will populate the original text entry field. In the Declarative Components subtab, you can view, create, modify, and remove LOVs. |