Network Deployment (Distributed operating systems), v8.0 > Reference > Sets > OSGi Applications administrative console panels


Web module resource reference bindings [Settings]

For each reference, specify the JNDI name under which the resource is known in the runtime environment. Optionally, set authentication properties and extended data source custom properties, which affect how the resource is accessed at run time.

Binding a resource reference maps a resource dependency of the web application to an actual resource available in the server runtime environment. At a minimum, this can be achieved by using a mapping that specifies the JNDI name under which the resource is known in the runtime environment. By default, the JNDI name is the resource ID specified in the web.xml file during development of the web application bundle (WAB).

The rows only contain the JNDI names of resource mapping targets for your references if you bound them together during application assembly. We can modify those bindings on this administrative console page.

To view this panel in the administrative console, click one of the following paths:

The Web module resource reference bindings option is only visible if the bundle includes a web application.

Parent topic: OSGi Applications administrative console panels

Related tasks:

Add an EBA asset to a composition unit
Add an EBA asset to a composition unit using wsadmin
Modify the configuration of an OSGi composition unit

Related reference:

JSR 250: Common Annotations for the Java Platform

Related information:

Administrative console buttons
Administrative console preferences
Web module message destination and resource environment reference bindings [Settings]


General Properties


Select

To modify the authentication method or set extended data source custom properties, select a single reference then click Modify Resource Authentication Method... or Extended Properties....


Composite bundle identifier

This identifier is only displayed if the EBA asset uses composite bundles. Each composite bundle is identified by a string in the following form: Composite bundle archive (CBA)'composite.bundle.symbolic.name_composite.bundle.version'. Bundles that are part of a composite bundle are listed beneath the composite bundle identifier.

Composite bundle symbolic name

The non-localizable name for this composite bundle.

Composite bundle version

The version of this composite bundle.

The symbolic name, together with the version, identifies a unique composite bundle.


Bundle symbolic name

The non-localizable name for this bundle.


Bundle version

The version of this bundle.

The bundle symbolic name, together with the bundle version, identifies a unique bundle.


Resource Reference

The name of a resource reference used in the application, if applicable, and is declared in the deployment descriptor of the WAB.


Resource Type

The type of the resource reference.

We can use this panel to specify bindings for any resource-ref (resource reference) resource, as defined in the Java specification JSR-250: Common Annotations for the Java Platform. For example:

To specify bindings for a message-destination-ref (message destination reference) resource, or a resource-env-ref (resource environment reference) resource, use the Web module message destination and resource environment reference bindings [Settings] panel.


JNDI name

The JNDI name of the resource that is the mapping target of the resource reference.


Login configuration

The authorization type and the authentication method for securing the resource. Container-managed authorization indicates that the product signs on to the resource rather than the enterprise bean code.


Buttons

Browse... To specify the JNDI name mapping for a specific web module resource reference, use this option to select the resource reference from a list of available resources.
Modify Resource Authentication Method... Specify one of the following authentication methods:

None

Use default method (many-to-one mapping)

For information about the default mapping configuration, see J2EE connector security.

Select this option, then select an authentication alias from the list.

Use trusted connections (one-to-one mapping)

We can use this option if your resource is a data source that has trusted context enabled.

Select this option, then select an authentication alias from the list that matches an alias that is already defined in the data source.

Use custom login configuration

For information about custom JAAS login configurations, see J2EE connector security.

Select this option, then select a JAAS login configuration from the list.
Extended properties... If your resource is a data source, and the backend database supports extended data source custom properties, you can use this option to add, modify or delete these properties. These are custom properties (name/value pairs) that can be used (for example) to obtain a data source for you.

If you use multiple values for an extended data source property, enclose those values in quotation marks.

See Extended data source properties.


Reference topic Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.

+

Search Tips   |   Advanced Search