...
The production instance of the ActiveMQ broker for DCT runs on joe.lowell.edu. It should only be connected to while trying to operate a real system at DCT. For testing one should try to connect to sabzi.lowell.edu.
The connection URL for the ActiveMQ Broker is specified in jndi.properties file for the appropriate product. Please refer to the section below for more details.:
| Code Block | ||||
|---|---|---|---|---|
| ||||
java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
# use the following property to configure the default connector
java.naming.provider.url=tcp://sabzi.lowell.edu:61616
# use the following property to embed a broker inside this JVM
useEmbeddedBroker=true
# use the following property to specify the JNDI name the connection factory
# should appear as.
connectionFactoryNames=connectionFactory, queueConnectionFactory, topicConnectionFactry
# property to disable persistence
disablePersistence=true
# machine name where lois is running.
loisMachineName=lemi
|
Log Files
A LOUI product will write to one or more log files during the operation. The location and level of logging is specified in log4j.properties file for the appropriate product. The log files are rotated automatically daily and properly labeled. The timestamp for the log statements is in UT but the log rotation happens based on local time at midnight.
...
- CameraConfiguration.xml
Contains the default values for different modes of operation of a CCD camera - jndi.properties
contains parameters used for connecting to the ActiveMQ broker and/or database - log4j.properties
contains the parameters for log4j framework such as log file location, logging levels, and rotation schedule
Setup
| Anchor | ||||
|---|---|---|---|---|
|
Application | Configuration Path | Required Files | Log File Path |
|---|---|---|---|
ActiveMQ TCS | /opt/LOUI/activemqTCS/ | instrumentConfiguration.xml | ? |
joe | /opt/LOUI/joe/ | instrumentConfiguration.xml | /var/log/LOUI/joe/ |
joeClient | /opt/LOUI/joe/ | instrumentConfiguration.xml | /var/log/LOUI/joe/ |
guider (gcs) | /opt/LOUI/gwaves/ | instrumentConfiguration.xml | ? |
wavefront sensor (wfs) | /opt/LOUI/gwaves/ | instrumentConfiguration.xml | ? |
hipoBlue | /opt/LOUI/hipo/ | instrumentConfiguration.xml | ? |
hipoRed | /opt/LOUI/hipo/ | instrumentConfiguration.xml | ? |
nasa42 | /opt/LOUI/nasa42/ | instrumentConfiguration.xml | ? |
Here are the steps for the first time installation of a LOUI application:
- Create the log file directory
- Copy the appropriate config files into the proper location
- Copy the application (executable code) into the relevant location for your OS (e.g.
/Applicationsfolder for Mac OS X)
Log File Directory
The easiest thing is to create the /var/log/LOUI directory and make it world writable. This way the application can be executed from multiple user accounts on the same machine.
The safer but more difficult way is to set up an Access Control List for the /var/log/LOUI directory.
The logging frame work will rotate the files indefinitely so it is up to the user to delete or archive the old log files.
| Note |
|---|
It is possible to change the names and location of the log files for the applications by editing the |
Configuration Files
As explained earlier and shown above, the location and names are configuration files are not subject to change. The easiest Easiest way to set up the configuration environment is to checkout the whole tree structure .
...
(dev & prod) from the source code repository into a user selected location and use a symbolic link from /opt/LOUI to either dev or prod versions depending on usage.
| Info |
|---|
We use subversion for source control at Lowell. Most operating systems have built in command line client for subversion as part of their development environment. There are also good subversion open source or commercial GUI clients for all major operating systems. |
The following can be used as an example:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ mkdir ~/LOUI_Configuration $ cd ~/ |
...
LOUI_Configuration $ svn checkout svn://jumar.lowell.edu/LOUI_Configuration/trunk |
...
.
$ sudo mkdir /opt
$ sudo ln -s ~/LOUI_Configuration/dev LOUI
|
If the app is not pointing to the right broker, edit
...
the jndi.properties file for the appropriate applications and correct the connection URI to point to the
...
proper broker.
Application Product
The LOUI applications are created as stand alone products and they only need a JVM (version 6 or later) in order to run under the appropriate operating system. We are currently creating products for Windows, Mac OS X, and Linux. The Mac OS X version is the recommended one to use.
The plan is to keep the most recent version of all the products on the C4 network drive:
c4:/mirror2/RCP_Products_Latest