Shared library relationship and mapping settings
Use the Shared library relationship and Shared library relationship mapping pages to specify relationship identifiers and composition unit names for shared libraries that modules in your enterprise application reference. When installing your enterprise application, the product creates a composition unit for each shared library relationship in the business-level application that you specified on the Select installation options page of the application installation wizard.
To view this console page in a wizard, click .
After installation, click .
To map library files used in a business-level application to an application or web module, use the Shared library relationship mapping page:
- Click Reference shared libraries.
- Note the application or module in Map libraries to the application or module listed. You are associating library files with that application or module.
- From the Available list, select one or more libraries that the application or module uses.
- Click >> to add them to the Selected list.
- To remove an association, select one or more libraries in the Selected list and click <<.
- Click OK.
Module
Specifies the name of the module associated with the shared libraries.
URI
Specifies the location of the module relative to the root of the application EAR file.
Relationship identifiers
Specifies an identifier for a module shared library relationship. The product assigns an identifier to the composition unit that it creates for the shared library relationship in the business-level application.
Composition unit names
Specifies a composition unit name for the shared library relationship. The product uses this value to name the composition unit that it creates for the shared library relationship in the business-level application that you specified on the Select installation options page of this wizard.
This setting is only in the application installation and update wizards.
Match target
Specifies whether the product maps the composition unit for the shared library relationship to the same deployment target as the business-level application.
避免困難: If you later change the deployment target
of the business-level application or its modules, you must manually
update the shared library target to match the target of the application
and modules. The targets of shared library composition units are not
automatically updated. Not updating the target of the shared library
composition unit might cause java.lang.ClassNotFoundException errors
and prevent the application or its modules from starting. To prevent
these error conditions, also ensure that shared libraries upon which
other modules or applications depend have a lower starting weight
than dependent applications and modules.gotcha
參照主題