Custom JAR files no longer in EAR file, after applying Impact 5.1.1 fixes
Any custom JAR files, which are embedded in their Impact server's EAR file, will no longer be present in this EAR file after applying Fix Pack 1 or any Interim Fix on Impact 5.1.1.
Custom JAR and/or library JAR files can be added to Impact server's EAR file, as these JAR files are often needed for various applications, such as JMS, WebServices, and databases.
In order to ensure that these JAR files are available and loaded into the EAR file immediately after applying Fix Pack 1 or any subsequent Interim Fix, take the following steps:
- Place the desired JAR file into your $NCHOME/impact/lib3p directory before installing Fix Pack 1 or Interim Fix.
- Run the Fix Pack 1 or Interim Fix installer as instructed in the patch's readme.
The process of adding and deploying custom JAR files (after FP1 or an IF has already been applied) can be found at the following URL:
Note: You will need to perform the above steps on every cluster member, as these EAR files are not included in the files that are routinely resynched between cluster members.
More support for:
Software version: 5.1.1
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Software edition: All Editions
Reference #: 1439258
Modified date: 26 July 2010