Support for Signed JARs as Dependencies

InstallAnywhere 2024 R2

InstallAnywhere supports adding signed JARs as dependencies to custom code actions, custom code panels, custom code consoles, and custom rules. Also, InstallAnywhere supports signing JAR and ZIP files that contain custom code.

If your project contains a signed JAR file with your custom code, InstallAnywhere does not extract the contents of the JAR at build time; the contents are left in the execute.zip file. At run time, the signed JARs are extracted to temporary directories and added to the InstallAnywhere classpath. This makes the JAR contents ready to be consumed for the custom code or any relevant actions that require the contents of the signed JAR.

You can designate that a signed JAR is a dependency in various scenarios—for example, a signed JAR can be a dependency for an Execute Custom Code action in your project.

Execute Custom Code Action, Panel, or Console

If you configure an Execute Custom Code action, a Custom Code panel, or a Custom Code console, specify the custom code archive location that contains all the classes that are required for execution, including the fully qualified class name to execute.

In addition, specify the location of the signed JAR archive files on which the custom code depends. When InstallAnywhere builds the installer, InstallAnywhere leaves the signed jar and its signing information intact.

At run time, the installer places the dependant signed JARs on the InstallAnywhere classpath to be consumed while the relevant action execution occurs.

Evaluate Custom Rule

If you configure an Evaluate Custom Rule, you can click Configure Dependencies and select a signed JAR on the Custom Rules Dependencies dialog box.

Maintenance Mode, Instance Management, Plug-Ins

You can also include signed JARs for some maintenance mode options (such as add or repair) and also for instance management. Also, custom code files that are packaged in a signed JAR can be used as plug-ins.