Shared Libraries
Example shared library setting - Static shared library not updated at deploy time
#--------------------------------------------------- # Shared Libraries #--------------------------------------------------- installSharedLibs="true" sharedLibsScope = "SERVER" sharedLibName_1="MidVision WPS Libraries SysTst01APP" sharedLibClassPath_1="/usr/websphere6/MVProdEnv/AppServer/optionalLibraries/jdom-1.0.jar" sharedLibNativePath_1="" classloaderForSharedLibrary = "PARENT_FIRST"
Note that this points to a shared library in optionalLibraries. This is the simplest case.
Variable | Description | Default Value | Required |
sharedLibsScope | The scope at which the shared libraries will be created. Possible values: CELL, NODE, CLUSTER, or SERVER. | SERVER | N |
Mapping Web Module shared libraries at deploy time
In this case you need to use the AdminApp function exposed by app_options in the Jython properties file:
################################################################################################# # Resource 7: Map Shared Libraries to Modules ################################################################################################# # # Fields:- module:URI:SharedLibrary: # res7_1 = ["InternetBankingWEB", "InternetBankingWEB.war,WEB-INF/web.xml", sharedLibName_1] res7_2 = ["myear", "META-INF/application.xml", sharedLibName_2] app_options.append("-MapSharedLibForMod") app_options.append([res7_1, res7_2])
The above shows a mapping for Web Module (7_1) and application (7_2).
Shared Library Jvm association
By default, the created shared libraries are bound to the jvm. This can be switched off by setting:
bindLibraryToJvm = "false"