Administrative console scope settings

 

+

Search Tips   |   Advanced Search

 

Use this page to specify the level at which a resource is visible on the console panel. By changing the value for Scope, you see only the resources that are defined at that scope. The contents of the collection table might change. A resource can be visible in the console collection table at the scopes...

If the list of scopes is less than fifty, the console displays a drop-down list of all the scopes available. To change the scope, select any item from the drop-down list.

If the list is fifty or greater, click Browse next to a field to see choices for changing the scope of the field. If a field is read-only, you cannot change the scope. For example, if only one server exists, you cannot switch the scope to a different server.

All scopes is the default. You cannot select All scopes to create a new resource. You 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 console panel, 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 that are defined at more specific scopes override duplicate resources that are 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 you 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 you 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 you define a resource at a more specific scope, you provide greater isolation for the resource. When you define a resource at a more general scope, you provide less isolation. Greater exposure to cross-application conflicts occur for a resource that you define 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

  • Overridden by any resource factories that are defined within application, server, cluster, and node scopes that are in this cell and have the same JNDI name

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

Cluster

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 that are 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 that are defined within the cell scope are available for this cluster to use, in addition to the resource factories, that are 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 that are 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 that are defined within the cell scope are available for servers on this node to use, in addition to the resource factories that are 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 that are defined within the server scope:

  • Are available for applications that are deployed on this server

  • Override any resource factories that have the same JNDI name defined within the node and cell scopes

The resource factories that are defined within the node and cell scopes are available for this server to use, in addition to the resource factories that are 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. You can additionally use the WebSphere Application Server Toolkit (AST) or the wsadmin tool to view or edit the application scope resource configuration. The resource factories that are defined within the application scope are available for this application to use only. The application scope overrides all other scopes.

You can configure namespace bindings and shared libraries under cell, node, and server scopes only. You can configure resources and the product variables under all five scopes.

 

Related tasks


Specifying console preferences