The scope level determines which applications or application servers will see and use that configuration. The scope setting is available for all resource types, WebSphere variables, shared libraries, and name space bindings.
Configuration information is defined at the following levels: cell, cluster, node, server, and application. Here, we list these scopes in overriding sequence. Because you see application scope first, anything defined at this scope overrides any conflicting configuration you might find in the higher level scopes.
Resources and variables scoped at the application level apply only to that application. Resources and variables are scoped at the application level by defining them in an "Enhanced EAR". They cannot be created from the WebSphere administrative tools, but can be viewed and modified (in the administrative console, navigate to the details page for the enterprise application and click "Application scoped resources" in the "References" section).
Resources scoped at the server level apply only to that server. If a node and server combination is specified, the scope is set to that server. Shared libraries configured in an "Enhanced EAR" are automatically scoped at the server level.
Resources scoped at the node level apply to all servers on the node.
Resources scoped at the cluster level apply to all application servers in the cluster. New cluster members automatically have access to resources scoped at this level. If you do not have any clusters defined, you will not see this option.
Resources scoped at the cell level apply to all nodes and servers in the cell.
Configuration information is stored in the repository directory that corresponds to the scope. For example, if you scope a resource at the node level, the configuration information for that resource is in:
If you scoped that same resource at the cell level, the configuration information for that resource is in: