|
Question |
When updating an application, you might need to add new
information to the information included in the EAR. By default, merge
the new and existing bindings is selected in the Specify bindings
to use box in the administrative console. Unfortunately, when updating
the application, the only JNDI references automatically used are those
provided in the EAR files. |
|
|
|
Cause |
The merge new keep existing option takes into
account only the new references and those that currently exist in the EAR
file when binding fields are left blank in the administrative console
during deployment. |
|
|
Answer |
Follow these installation steps to merge binding
information from the new version and the old versions.
Scenarios
- If the new version has bindings for application artifacts
such as EJB™ JNDI™ names, EJB references, or resource references, those
bindings are part of the merged binding information.
- If new bindings are not present, bindings are taken from
the installed (old) version.
- If bindings are not present in the old version and the
default binding generation option is enabled, the default bindings
are part of the merged binding information.
Example
If an existing application has a reference for JNDI1 and is updated with
an application that has this reference changed to JNDI2 and also a new
reference to NEW_JNDI, the following occurs if the default of merge new
and existing bindings is used:
- Only the references within the new EAR display in the
administrative console.
- JNDI1 is used if the reference to JNDI2 is removed during
the deployment.
- JNDI2 is used if it is left as is during the deployment.
- NEW_JNDI is added.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|