The MIMIC WEBUI is an optional browser-based web interface to control MIMIC Simulator. It is an alternative to the MIMICview desktop-based graphical user interface (GUI), or the multitude of scripting interfaces in different programming languages.
The WEBUI server is installed by the MIMIC administrator as an optional Update Wizard package, and needs to run either on the same system as the MIMICD simulator daemon, or a system that can connect to it. See Installation section below.
Once you have installed it, users can consult it's user guide on how to use it to control MIMIC.
Linux or Windows 64-bit Java
Java 8, 9, Java 11 SE
Install the WEBUI packages in Update Wizard.
Once the WEBUI packages have been installed on your MIMIC system, you need to run the WEBUI server. You can run it on the same system as MIMICD, but if you want more CPU power to be available to both, you should run it on a different system.
Since WEBUI is implemented as a MIMIC client serving the web-based user interface, if run on a different system, then all the same rules apply as all other MIMIC clients, as detailed in this FAQ entry. In particular, you want the MIMIC install area and private area(s) accessible at the same absolute paths on both MIMIC and WEBUI system, eg. via NFS and/or symbolic links.
The webui.sh shell script is a convenience front-end script to invoke the Java-based WEBUI server. It is designed to run in 2 modes:
It takes these command line options:
Temporary files (output from scripts, etc) will be placed in the specified path. If this is not specified, then temporary files will be placed in the folder specified by the MIMIC_TMPDIR environment variable, and if this is not specified, then in /tmp.
Files will accumulate, and the system administrative scripts, eg. via crontab should periodically remove old files.
To create the PKCS12 keyfile:
cd /tmp openssl genrsa -out key.pem 2048 openssl req -new -sha256 -key key.pem -out csr.csr openssl req -x509 -sha256 -days 365 -key key.pem -in csr.csr -out certificate.pem
and type the password in the Password prompt, then convert to PKCS12 format:
openssl pkcs12 -export -out mimicwebui.p12 -inkey key.pem -in certificate.pem chmod 755 mimicwebui.p12Then copy the keyfile to a subfolder in the MIMIC install area:
mkdir /usr/local/mimic/java/webui/ssl cp /tmp/mimicwebui.p12 /usr/local/mimic/java/webui/ssl
then the -kf argument would be ssl/mimicwebui.p12.
Note : Both HTTP and HTTPS can coexist in single server instance using different port numbers
Admin web service is available only in cloud based lab server mode.
The WEBUI server is not intended to be a public-facing server, instead running on a protected intranet just like the MIMIC daemon. The current modes of protection are
Once the server is running, you can restrict it's CPU usage by setting it's CPU affinity on Linux, eg. like this
[root@fc28 ~]# ps ax | grep java 1304 pts/0 Sl 0:11 java -cp .:..:../akka/*:../Apache-Oro/*:webui.jar WebUI.WebUIServer -sd ../../ -mh 220.127.116.11 -mp 9797 [root@fc28 ~]# taskset -c -p 0 1304 pid 1304's current affinity list: 0,1 pid 1304's new affinity list: 0