hairlessupportmonkey
IS-IT--Management
In two flavours / packages:
RPM both 32 and 64bit
Deb both 32 and 64bit
I currently have it running on Fedora 18 (KDE) and its working sweet.
It should work in your Apps server under Centos.
The nice thing is running this in Linux is a cost saving and it works well as the overheads to run it are less.
You can now also run the wallboard outside the browser in both Windoze and Linux versions, and have it startup when your machine boots should you desire.
We added in a new feature that will be deployed with the next maintenance release (early next week). It is the ability to run the Chronicall user interface outside of the browser. This may come in handy for any of the following reasons:
• You need the Realtime Stats (canvas) to open up automatically and go full screen when your computer starts up
• The browser Java plugin is misbehaving
• The browser Java plugin for Linux is really crappy and hard to install
So here is how it works...
On the server you can just double click the chronicallApplet.jar file in Windows and it will launch the Chronicall user interface. By the same token you can launch the Chronicall user interface from the command line or from a short cut using the Java executable like this:
Windows:
java.exe -jar "C:\Program Files (x86)\Xima Software\Chronicall\tomcat\webapps\ROOT\WEB-INF\lib\chronicallApplet.jar"
You can also add a few parameters when you launch it:
• useAdminLogin=true
o This will attempt to log in automatically using the default username and password
• username=nate password=secret
o These two parameters will attempt to log you in automatically using the indicated credentials
• fullScreenCanvas=true
o This will launch the canvas and automatically make it full screen (if you have appropriate log in credentials)
Here is an example of using these parameters together.
Linux:
Make a new Launcher on your desktop and add
java -jar /var/lib/Xima\ Software/Chronicall/tomcat/webapps/ROOT/WEB-INF/lib/chronicallApplet.jar useAdminLogin=true fullScreenCanvas=true
On a network computer you have to have all of the client side jar files in the same directory as chronicallApplet.jar. This is no problem if you are running this on the Chronicall server because they are already there in the lib directory. If you need to do this on a remote work station then you will need to copy the following jars into a directory on the PC:
• chronicallApplet.jar
• xima1.jar (only if you have legacy reports)
• r2xima1.jar
• r2xima2.jar (only if you have custom reports)
• xima4.jar (only if you have recording library)
• xima8.jar (only if you have realtime)
Making this work on a PC other than the Chronicall Server is not super hard but it can be problematic because they will need to manually recopy these jar files if they update Chronicall. Once the new Dashboard module is deployed we will tap into its boot loader system which will take care of pulling down the updated jars automatically. Until then you will probably want Mark's help if you need to set this up for someone.
Last point, if you want the canvas to open up automatically when the computer starts then you will want to create an appropriate shortcut and put it in the Start Up folder.
ACSS - SME
General Geek
RPM both 32 and 64bit
Deb both 32 and 64bit
I currently have it running on Fedora 18 (KDE) and its working sweet.
It should work in your Apps server under Centos.
The nice thing is running this in Linux is a cost saving and it works well as the overheads to run it are less.
You can now also run the wallboard outside the browser in both Windoze and Linux versions, and have it startup when your machine boots should you desire.
We added in a new feature that will be deployed with the next maintenance release (early next week). It is the ability to run the Chronicall user interface outside of the browser. This may come in handy for any of the following reasons:
• You need the Realtime Stats (canvas) to open up automatically and go full screen when your computer starts up
• The browser Java plugin is misbehaving
• The browser Java plugin for Linux is really crappy and hard to install
So here is how it works...
On the server you can just double click the chronicallApplet.jar file in Windows and it will launch the Chronicall user interface. By the same token you can launch the Chronicall user interface from the command line or from a short cut using the Java executable like this:
Windows:
java.exe -jar "C:\Program Files (x86)\Xima Software\Chronicall\tomcat\webapps\ROOT\WEB-INF\lib\chronicallApplet.jar"
You can also add a few parameters when you launch it:
• useAdminLogin=true
o This will attempt to log in automatically using the default username and password
• username=nate password=secret
o These two parameters will attempt to log you in automatically using the indicated credentials
• fullScreenCanvas=true
o This will launch the canvas and automatically make it full screen (if you have appropriate log in credentials)
Here is an example of using these parameters together.
Linux:
Make a new Launcher on your desktop and add
java -jar /var/lib/Xima\ Software/Chronicall/tomcat/webapps/ROOT/WEB-INF/lib/chronicallApplet.jar useAdminLogin=true fullScreenCanvas=true
On a network computer you have to have all of the client side jar files in the same directory as chronicallApplet.jar. This is no problem if you are running this on the Chronicall server because they are already there in the lib directory. If you need to do this on a remote work station then you will need to copy the following jars into a directory on the PC:
• chronicallApplet.jar
• xima1.jar (only if you have legacy reports)
• r2xima1.jar
• r2xima2.jar (only if you have custom reports)
• xima4.jar (only if you have recording library)
• xima8.jar (only if you have realtime)
Making this work on a PC other than the Chronicall Server is not super hard but it can be problematic because they will need to manually recopy these jar files if they update Chronicall. Once the new Dashboard module is deployed we will tap into its boot loader system which will take care of pulling down the updated jars automatically. Until then you will probably want Mark's help if you need to set this up for someone.
Last point, if you want the canvas to open up automatically when the computer starts then you will want to create an appropriate shortcut and put it in the Start Up folder.
ACSS - SME
General Geek
