Page History

...

For a quick setup guide, please refer to the #Setup section below.

ActiveMQ Broker

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 instrument at DCTHJ. For testing one should try to connect to jumar.lowell.edu.

...

.

...

lowell.edu

...

.

The connection URL for the ActiveMQ Broker is specified in jndi.properties file for the appropriate product. Below is the production version of the file for LMI:

java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
 
# use the following property to configure the default connector
java.naming.provider.url=failover://(tcp://jumarjoe.lowell.edu:61616)?startupMaxReconnectAttempts=1&initialReconnectDelay=1

# 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

##my 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.

By default, the main log file for each application is app.log and they are located under /var/log/LOUI/ directory:

/var/log/LOUI/
├── cat
├── gwaves
├── joe
├── joeClient
├── lmi
└── observerTargetlist

6 directories

...

All the config files for the LOUI applications should be in the proper directory under /opt/LOUI/ directory. This path is built into the applications and has to exist on the installation computer:

/opt/LOUI/
├── MasterInstrumentConfiguration.xml
├── activemqTCS
│  │   ├── instrumentConfiguration.xml
│  │   └── jndi.properties
├── cat
│  │   ├── CubeGeometry.xml
│   ├── jndi.properties
│  │   └── log4j.properties
├── gwaves
│  │   ├── CameraConfiguration_GDR.xml
│  │   ├── CameraConfiguration_WFS.xml
│  │   ├── DefaultUserButtonScripts_GDR.tcl
│   ├── DefaultUserButtonScripts_WFS.tcl
│   ├── Jndi_GDR.properties
│  │   ├── Jndi_WFS.properties
│  │   ├── log4j_GDR.properties
│  │   └── log4j_WFS.properties
├── hipo
│  │   ├── CameraConfigurationBlue.xml
│  │   ├── CameraConfigurationRed.xml
│  │   ├── instrumentConfigurationBlue.xml
│  │   ├── instrumentConfigurationRed.xml
│  │   ├── jndiBlue.properties
│  │   ├── jndiMCCS.properties
│   └── jndiRed.properties
├── joe
│  │   ├── jndi.properties
│  │   └── log4j.properties
├── joeClient
│  │   ├── jndi.properties
│  │   └── log4j.properties
├── lmi
│  │   ├── CameraConfiguration.xml
│  │   ├── DefaultUserButtonScripts.tcl
│   ├── MasterFilterListConfiguration.xml
│   ├── jndi.properties
│  │   └── log4j.properties
├── nasa42
│  │   ├── instrumentConfiguration.xml
│  │   └── jndi.properties
├── nihts
│  │   ├── CameraConfiguration.xml
│  │   ├── jndi.properties
│  │   └── log4j.properties
└── observerTargetlist
    ├── jndi.properties
    └── log4j.properties

10 directories, 3137 files

The config files are either xml or java property files. There is main config file that is used by most applications /opt/LOUI/MasterInstrumentConfiguration.xml. Each application's specific configuration is under a separate subdirectory and the names of these subdirectories cannot be changed. Depending on the application, there are 2 or 3 config files:

...

As explained earlier and shown above, the location and names are of configuration files are not subject to change. The 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.

...

The following can be used as an example:

$ 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 can create 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 a network drive:
c4:/mirror2/RCP_Products_Latest. For now it is on (login as guest)
mh-dct-archive-cifs:/RCP_Products/latest

Windows Additional Setup

In order to configure LOUI properly in windows, you need to follow some special steps.

Because LOUI is run mostly on mac machines, the configuration files are in different locations. You will need to set up a symbolic link that points LOUI to the windows file locations.

Symbolic links can be created by running a command line as an administrator. In your C:/ drive (or in whichever drive you've stored your workspace) create a folder named opt. Then, navigate to it in the command line, and type:

mklink LOUI <to workspace>\LOUI_Configuration\dev\

This should set LOUI to retrieve configuration files from the proper location.

You may also need to switch your clock to synchronize with lowell's. To do so, right-click your date and time and press Adjust Date and Time. Click the Internet Time tab, then "change settings". Change the time server to gps1.lowell.edu