Install4j Manual

[Dawnell Sechler]

Theinstall4j UI is delivered as a desktop application. Building installers is not only possible in the IDE, but also with the command line compiler as well as the plugins for Gradle, Maven and Ant.

The "Concepts" section is intended to be read in sequence, with later help topics building on the content of previous ones. The sections at the end are optional readings that should be consulted if you need certain features.

We appreciate your feedback. If you feel that there's a lack of documentation in a certain area or if you find inaccuracies in the documentation, please don't hesitate to contact us at [email protected].

If you are using the keyboard for navigation, press F4 to switch between the index and the content area. The keys j and k move between help topics and the keys u and d move up and down when there is a hierarchy of chapters.

I am testing version 8 and trying to figure out jre bundles. I think I have successfully created a jre bundle for java8 on Windows. However, how do I do that for the Mac version since I don't have a Mac jre on my Windows build machine that can be referenced.

They are generated automatically based on your project definition, there is actually less manual work involved than in install4j 7. You just specify the JDK provider and the release on the "General settings->JRE bundles" step and each new build machine will generate and cache the bundles.

I created the install4j install script on my laptop using the local laptop login say X. Then I joined company's domain and logged in from my account to same laptop. When I ran the script from my new login, the bundled JRE was not found. Attempts to bundle the same again failed for some reason. I then manually located the bundled JRE from C:\Users\X.install4j5\jres and copied to corresponding folder and overwrote the one that was of 0 size. Now we are moving the scripts to a build machine where builds will be made in future. Do I have to follow same procedure or I can edit the script in notepad to point to the jre stored somewhere else?The main requirement i have is I want to keep this bundled jre in SVN folder and not in its default location of C:\Users\X.install4j5\jres. The script should take the JRE from the SVN folder.

You can define a compiler variable (General Settings/Compiler Variables tab), say myBundledJre, whose value is the path to your JRE bundle. Then in the Media Wizard's Bundled JRE options, select "Manual entry" from the drop down menu and choose your variable ($compiler:myBundledJre) as the value.

You can use either an absolute path or a path relative to your project's .install4j file. If you build via the command-line or Ant task, you can change the compiler variable using build-time arguments.

Dear Sir:

I have an question on installing the SNAP on windows 10. The installing Error is like this:

instll4j Wizard

ESA SNAP is preparing the install4j Wizard which will guide you through the rest of the setup process.

install4j Wizard

The installation file is corrupted .If it is a download please try it again.

When you say that Confluence is gone, can you confirm what you mean by that? Are you just looking for the installer folder, or is your Confluence home gone, and you're not able to access Confluence by the same URL as before?

In my last question, I asked how the upgrade on the staging environment had gone, and if you were able to make a manual backup of the installer, home, and database in case you need to roll back. Could you confirm that?

I'm terribly sorry that I hadn't seen Pratik's response to this earlier. The case I created for Doug was actually a duplicate of one he raised earlier on our support forum, so I hadn't received any updates on it.

I've looked into this for you, but we didn't end up finding the root cause of the error. Doug's instance was restored to the original state, and we attempted an upgrade one more time, this time using the .zip method instead of the installer method.

This is a simple matter.

If the location of the upgrade file is the same as your Confluence installation location, uncompress the files for upgrade in the Confluence folder. Then, when deleting the data of existing confluence installation file, the problem is caused by deleting the file for upgrade.

Placing the upgrade installation file outside of the confluence installation folder seems to fix the problem.

We ran into this when trying to move from 6.13 to 6.14, when we moved from our older LTS version 6.4.2 to 13 and directly to 14 we did not see the issue so not sure what changes in the later versions with that package....but, I digress.

The work-around that worked for us was doing a "silent install" using the response.varfile, basically we just had to update our installation/home directory value in this file and set the value of this property,sys.confirmedUpdateInstallationString=, to true.

We ran into this same problem when upgrading from version 6.8.3 to 6.8.5. In our case the root cause was that we ran out of free disk space during the upgrade process. After we made sure there was enough free disk space the upgrade was successful.

Starting Installer ...

Error: Could not find or load main class com.install4j.runtime.launcher.UnixLauncher

Caused by: java.lang.ClassNotFoundException: com.install4j.runtime.launcher.UnixLauncher

There is a RPM kit available but there have been problems reported with these kits in recent times and I do not know if the problems have been resolved. It has been a while since I used a RPM based distribution.

I think we removed the RPM link a while ago because it wasn't working on most systems. Our compiler still generates it, but we haven't been able to fix all of the issues. The install script seems to work for most systems that don't support DEB files.

FHAES is free and open source software. While you are free to download and use FHAES we do ask that you cite the software where ever you use it. The continued development of FHAES relies upon being able to demonstrate that it is widely used in the community. Instructions for how to cite FHAES are available in chapter 1 of the user manual.

Please download the installation package for your operating system. If your operating system is not listed, you should download the Java executable. See user manual for install assistance, especially for MacOSX. Please note that certain antivirus tools now warn users when installing software that is not widely used. Such warnings are unhelpful for specialist scientific applications such as FHAES. Packages were produced using the Install4J multi-platform installer builder.

This section provides descriptions of problems commonly encountered when using the application and guidance for dealing with them. If you do need to contact Technical Support, this section will help you gather the information that Support needs to assist you.

If you are encountering problems with the Security Console or Scan Engine, you may find it helpful to consult log files for troubleshooting. Log files can also be useful for routine maintenance and debugging purposes.

When reading through a log file to troubleshoot major issues, you may find it useful look for ERROR- and WARN-level messages initially.Thread identifies the process that generated the message.

By default, all log files display messages with severity levels of INFO and higher. This means that they display INFO, WARN, ERROR messages and do not display DEBUG messages. You can change which severity levels are displayed in the log files. For example, you might want to filter out all messages except for those with WARN and ERROR severity levels. Or, you may want to include DEBUG messages for maintenance and debugging purposes.

The Security Console and the embedded Scan Engine log levels can be controlled using console commands. For steps to configure log levels for a distributed Scan Engine, see the Using the file system section of this article. For more information on console commands, see Using the command console.

The Insight Support Application is an optional remote log retrieval feature that allows Support to access your log files. With the Insight Support Application, you do not need to attach logs to support cases or send logs manually.

If your scans are producing inaccurate results, such as false positives, false negatives, or incorrect fingerprints, you can use a scan logging feature to collect data that could help the Technical Support team troubleshoot the cause. Enhanced logging is a feature that collects information useful for troubleshooting, such as Windows registry keys, SSH command executions, and file versions, during a scan.

Enhanced Logging is enabled by default on the Asset Configuration Export scan template. You may, however, want to scan with a custom template which has been tuned to perform better in your specific environment. To enable Enhanced logging on a custom scan template:

After performing the requested diagnostics, the Security Console displays a table of results. Each item includes a red or green icon, indicating whether or not an issue exists with the respective system component.

The application may fail to restart in maintenance mode in case of extremely critical failures if the maintenance Web server does not have the default port 3780 available. This may happen if there is already an instance of it running, or if one or more of the key configuration files is invalid or missing. These files have extensions such as .nsc, .xml, and .userdb.

When the Web interface session times out in an idle session, the Security Console displays the logon window so that the user can refresh the session. If a communication issue between the Web browser and the Security Console Web server prevents the session from refreshing, a user will see an error message. If the user has unsaved work, he or she should not leave the page or close the browser because the work may not be lost after the communication issue is resolved.

3a8082e126