Miscellaneous

The chapter Concepts > Extensions > Rich Dialog Clientside Libraries > Provide custom ULC Widgets in the Axon.ivy Designer Guide explains how to provide Custom ULC Widgets.

If a client starts the first time a Rich Dialog a security information dialog box pops up showing information about the publisher of Axon.ivy and its certificate. For some clients it may be confusing that a certificate from the provider of Axon.ivy is displayed instead of the certificate of the web site or the company they working for.

The chapter Extensions > Rich Dialog Clientside Libraries > Provide Customer Certificate in the Axon.ivy Designer Guide explains how to provide customer Rich Dialog client certificate.

The normal session timeout has no effect to Rich Dialogs because they send recurring requests to the server in shorter intervals than the session timeout. Therefore you can configure a special timeout feature for Rich Dialogs. It detects if an open Rich Dialog was not touched for the configured time and stops that Rich Dialog application. The user will receive a message so that he knows why the Rich Dialog has been closed. You can choose whether you want to have a Rich Dialog message box or if you want to see the message in your browser. With the former, the Rich Dialog and the session is closed only after the user confirmed the message. With the latter, the Rich Dialog and the session is closed immediately when the timeout happens thus freeing the server side memory. In this case you can even adapt the HTML file that is used. It is the file webapps/ivy/info/time_out.jsp.

To configure the Rich Dialog session timeout just go to the file configuration/jnlpconfig.any and adapt the settings for it.

The look and feel that is used for Rich Dialogs can be configured per applications. To change it open in the AdminUI the application and change the configuration property ria.lookandfeel.

Rich Dialog clients download many jars during the first startup. If the network connection of the client is poor, it is possible to speed-up the download by sending compressed pack200 jars. It will speed-up the download time, but the client will require more resources to unpack the downloaded jars.

In order to send compressed jars they must be provided within the /clientlib directory of the engine. The following sample script will create these pack.gz files. The script must be run within the engines clientlib directory. Note that the pack200 binary comes from a JRE or JDK.

On Windows:

for /R %f in (.\*.jar) do pack200 "%f.pack.gz" "%f" 

On Linux:

for f in `find signed -name '*.jar'`; do
  echo "packing $f"
  pack200 $f.pack.gz $f
done

If the script runs successfully the clientlib directory contains files ending with pack.gz next to the normal jars.

ULC Load is a product from Canoo Engineering AG to make load tests on ULC Applications (such as Rich Dialogs are). This chapter describes how to use ULC Load together with an Axon.ivy Engine.

<Context antiResourceLocking="false" privileged="true">

<Context antiResourceLocking="false" privileged="true" useHttpOnly="false">

The default Primefaces theme that is used in Html Dialogs can be configured in the web.xml. It can also be configure per application. To change it open in the AdminUI the application and change the configuration property jsf.primesface.theme. Moreover, the theme can also be set per session. See Java class ch.ivyteam.ivy.jsf.primefaces.theme.IvyPrimefacesThemeResolver in Public API for details.

Axon.ivy Engine program. This program starts an instance of the Axon.ivy Engine.

Axon.ivy Engine Configuration program. The program is used to configure the Axon.ivy Engine. The program supports two modes:

Axon.ivy Engine Windows Service. This program is the implementation of the Axon.ivy Engine Windows Service. But it can also be used to register, unregister, start and stop Axon.ivy Engine as Windows Service.

The console program is used to configure the Axon.ivy Engine. E.g. configure, create or convert the database.

The Control Center program. With Control Center program you can start and stop the different Axon.ivy Engine types. The Control Center allows you to change the configuration of the Axon.ivy Engine and on Windows even the configuration of Axon.ivy Engine Windows Service.

The install service program helps to install the Axon.ivy Engine as a systemd Linux daemon. To install the service:

All windows program launchers can be reconfigured with an additional ivy launch control file (*.ilc). The ivy launch control file must have the same name like the launcher itself but instead of the extension *.exe it must use an extension *.ilc.

The ivy launch control file is a text-based property file. The file has the following format:

# comment line
property=value
property=value

Open the file with a text editor to reconfigure it. Most properties found in the ivy launch control file are used to modify java virtual machine options. The following list shows all available options and explains them:

The properties that are bold are the most used properties.

The Java virtual machine (JVM) options for the Engine are configured in the AxonIvyEngine.conf file. For all other helper programs the JVM options are configured in the control.conf file.