+

Search Tips   |   Advanced Search

Administrative console scope settings

Specify the level at which a resource is visible on the administrative console page. By changing the value for Scope, we see only the resources defined at that scope. The contents of the collection table might change. A resource can be visible in the administrative console collection table at the cell, node, or server scope. For multiple-server products, a resource also can be visible at the cluster scope.

For WebSphere Application Server, Network Deployment, if we select Show scope selection drop-down list with the all scopes option, the console displays a drop-down list of all the scopes available. To change the scope, select any item from the drop-down list. The drop-down list contains only those scopes that we have the authority to view.

For WAS ND, if you clear Show scope selection drop-down list with the all scopes option, we do not receive the drop-down list. Instead, click Browse next to a field to see choices for changing the scope of the field. If a field is read-only, we cannot change the scope. For example, if only one server exists, we cannot switch the scope to a different server.

The value for the Show scope selection drop-down list with the all scopes option checkbox is saved on a per-user and per-resource basis. For example, user 1 might select the checkbox while user 2 clears the checkbox. The values for the checkbox are saved for each user separately. Different resources, for example Java Database Connectivity (JDBC) Providers and data sources, can have different values for the checkbox.

All scopes is the default unless we enable the Use default scope setting on the Console preferences page to make the administrative console node the default. Whatever the default is the first time that you view a console page that has scope settings, that is the default for the page on subsequent visits that we make to the page. The default for the page does not change even if we modify the Use default scope setting.

We cannot select All scopes to create a new resource. We must select one of the available scopes from the drop-down list to create a new resource.

You always create resources at the current scope that is selected in the administrative console page, even though the resources might be visible at more than one scope.

Resources such as JDBC providers, namespace bindings, or shared libraries can be defined at multiple scopes. Resources defined at more specific scopes override duplicate resources defined at more general scopes:

Despite the scope of a defined resource, the resource properties apply at an individual server level only. For example, if we define the scope of a data source at the cell level, all the users in that cell can look up and use that data source, which is unique within that cell. However, resource property settings are local to each server in the cell. For example, if we define the maximum connections as 10, then each server in that cell can have 10 connections.

The cell scope is the most general scope and does not override any other scope. The recommendation is that you generally specify a more specific scope than the cell scope. When defining a resource at a more specific scope, we provide greater isolation for the resource. When defining a resource at a more general scope, we provide less isolation. Greater exposure to cross-application conflicts occur for a resource defined at a more general scope.

Cell

Limits the visibility to all servers on the named cell. The resource factories within the cell scope are:

  • Defined for all servers within this cell

  • For WAS ND, overridden by any resource factories defined within application, server, cluster, and node scopes in this cell and have the same JNDI name

The resource providers required by the resource factories must be installed on every node within the cell before applications can bind or use them.

Cluster

Clusters are used in WAS ND. This scope limits the visibility to all the servers on the named cluster. All cluster members must at least be at v6 to use cluster scope for the cluster. The resource factories defined within the cluster scope:

  • Are available for all the members of this cluster to use
  • Override any resource factories that have the same JNDI name that is defined within the cell scope

The resource factories defined within the cell scope are available for this cluster to use, in addition to the resource factories, defined within this cluster scope.

Node

Limits the visibility to all the servers on the named node. The node scope is the default scope for most resource types. The resource factories defined within the node scope:

  • Are available for servers on this node to use
  • Override any resource factories that have the same JNDI name defined within the cell scope

The resource factories defined within the cell scope are available for servers on this node to use, in addition to the resource factories defined within this node scope.

Server

Limits the visibility to the named server. The server scope is the most specific scope for defining resources. The resource factories defined within the server scope:

  • Are available for applications deployed on this server
  • Override any resource factories that have the same JNDI name defined within the node and cell scopes

The resource factories defined within the node and cell scopes are available for this server to use, in addition to the resource factories defined within this server scope.

Application

Limits the visibility to the named application. Application scope resources can be viewed and edited from the console, but not created. We can additionally use the Rational Application Developer or the wsadmin tool to view or edit the application scope resource configuration. The resource factories defined within the application scope are available for this application to use only. The application scope overrides all other scopes.

We can view the application scope resources from the console by selecting Applications from the console navigation, and then navigating to the appropriate application. The application scope resources are unavailable from the Resources section of the console navigation.

We can configure namespace bindings and shared libraries under cell, node, and server scopes only. For WAS ND, we can configure resources and the product variables under all five scopes.

  • Specify console preferences