+

Search Tips   |   Advanced Search

Java EE default resource settings

Specify the resource to which a Java EE default resource is bound.

From the admin console, click...

        Resources > Java EE default resources.


Scope

Scope of the configured resource. This value indicates the location for the configuration file.

Each Java EE default resource has a binding configurable at each of the cell, node, and server scopes. By default, bindings are set for each default resource at the cell scope only. We can configure default resource bindings at all, some, or none of the configurable scopes.

If multiple bindings exist for a default resource, the product resolves the bindings with the following priority:

  1. Server scope
  2. Node scope
  3. Cell scope


Default Datasource

Specifies a JDBC datasource to bind to the default datasource.

The default data source in the default configuration is a Derby Embedded data source, which is not supported in a production environment. To use a supported default data source in a production environment, we must reconfigure the bindings for the default data source to reference a data source supported.


Default ContextService

Specifies a work manager resource to bind to the default ContextService resource, which provides methods for creating dynamic proxy objects with a context, typically for applications running in a Java EE environment.


Default ManagedExecutorService

Specifies a work manager resource to bind to the default ManagedExecutorService resource, which provides methods for submitting tasks running in a Java EE environment.


Default ManagedScheduledExecutorService

Specifies a work manager resource to bind to the default ManagedScheduledExecutorService resource, which provides methods for submitting delayed or periodic tasks running in a Java EE environment.


Default ManagedThreadFactory

Specifies a work manager resource to bind to the default ManagedThreadFactory resource, which provides a method for creating threads running in a Java EE environment.


Default JMS ConnectionFactory

Specifies a JMS connection factory resource to bind to the default connection factory resource.

The default JMS connection factory is available only at the cell scope, and references the SIBus named defaultBus. To use the default JMS connection factory, either create the Service Integration Bus named defaultBus or modify the default JMS connection factory Bus name property in the administrative console to reference the intended SIBus. In either case, we must add the members (application servers) to the bus, and choose the type of messageStore (FileStore or DataStore) for the persistence, to get the messaging engine run time.

  • Configure Java EE default resources