In the following, you will learn how to set up a remote connection to a JVM for as a function test via jconsole.
Safety aspects are deliberately left unconsidered. For this and more in-depth information, please refer to the linked information.

1. Prepare JVM
   Digression for Sign Live! C.C.C/ PDFA Live! /Sign Live! cloud suite bridge:
   A complete JRE is required on the client side (where the intarsys product is operated) to use JMX.
   The above products are delivered with reduced JREs. Therefore, it must first be ensured that the intarsys product starts with a complete JRE.
   You can find information on this in this FAQ Starting SLCC with “my” JVM.
   
   Configuration of the JVM for remote access
   A port must be defined for remote access to the JVM and, for the sake of simplicity, security mechanisms must be switched off.
   Add the following definitions to your Java configuration (any free port can be used as a port)

   -Dcom.sun.management.jmxremote.port=50999 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

   For z. B. Sign Live! C.C.C put this data in the file C:\Program Files\Sign Live CC 7.1.7\bin\SignLiveCC.exe.vmoptions and restart the application.
   Your JVM is now configured for remote access via JMX.
   
2. Establish a connection to the JVM with jconsole
   Start the Java tool jconsole on the client.
   You can find it in your Java installation (JDK) e.g. B. in the path C:\Program Files\Java\zulu11.48.21-ca-jdk11.0.11-win_x64\bin\jconsole.exe
   
   Select the JVM to be monitored via the defined connection data:

acknowledge the warning

... and you get access to the JVM. After switching to the MBeans tab, read e.g. B. the current license status:

More information

1. The version of the client JDK is independent of the one used in the intarsys product.
   It must be a JDK.
2. When accessing from localhost, there is no need to define a port and switch off security.

More detailed information

1. https://docs.oracle.com/javase/1.5.0/docs/guide/management/index.html
   therein
   • https://docs.oracle.com/javase/1.5.0/docs/guide/management/jconsole.html
   • https://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html#remote
2. https://www.oracle.com/technical-resources/articles/javase/jmx.html

Should several Windows services from Sign Live! C.C.C are operated in parallel, a name must be specified when installing the service. To do this, customize the bin/SignLiveCC_service_install.bat file by specifying a name after the /install option.

Example:

……./install MySLCCService

The same name must be specified in the bat files for starting, stopping and uninstalling the Windows service.

Parameters for use in Sign Live! C.C.C Windows services are passed using the "bin/SignLiveCC_service.exe.vmoptions" file. You can find more information on this here.

How to install the software on a Linux system:

1. Download the file with the extension ".tar.gz".
2. If you have already installed the application in a previous version or if you are installing a patch:
   • Quit the application if it has started.
   • If you have configured the software as a Linux service, stop the Linux service.
3. Unzip the downloaded file as follows, using the file name of the downloaded file plus the version number as the name for the installation directory:
   tar -xf signlivecc_*.tar.gz -C /var/signlivecc-7.1.11/
4. Check your installation.
5. Start the installed application.

Note: You should also unzip an update into a new directory in order to avoid the contents of different versions in the installation. Specific adjustments must be carried out again or adopted after the installation.

Note: Depending on the product, the file name of the downloaded file is different. For the example in point 3, the product 'Sign Live! C.C.C, used.