Month: June 2012

These are the install instructions for a mac. This needs some technical expertise. Most of these instructions have commands that can be run from the terminal.

Pre requisites:

1. The usage tracker needs Java runtime version > 1.6 (Java 6 or higher) to be installed and under PATH. This can be checked using the terminal command : java -version
2. Download the tracker configuration file (tracker.conf) from the iLab application. (Please contact your IA for instructions on how to do this)

Installation Steps:

1. Download the Mac usage tracker from the application:
2. Delete the quarantine attribute from the file.
3. Un-archive the contents of any directory.
4. Move UsageTracker.app to applications to install the tracker
5. Copy the tracker.conf file to /Applications/UsageTracker.app/Contents/Resources/Java. Ensure that this file is readable by all users.
6. Copy the com.ilabsolutions.UsageTracker.plist file to /Library/LaunchAgents.
   Optional: Use PlistEdit Pro to edit the plist file and specify the parameters you want it to launch with. Ensure that this file is owned by root and has permissions 644.
7. Log out and log back on to start the Tracker.

 

Post Installation:

1. If the tracker has been installed in the online mode, you should see the equipment show up as “online” in the ilab application.
2. We process the usage logs nightly, so the events will show up in the equipment calendar the day after the usage was recorded.

Pre requisites:

• The usage tracker needs Java runtime version > 1.6 (Java 6 or higher) to be installed and under PATH.

Installation Steps:

• Download the Linux usage tracker from : https://content.ilabsolutions.com/wp-content/uploads/2013/01/iLab_tracker_linux_1.4.56649.tar.gz (get latest from iLab)
• Un-archive the contents of any directory accessible by all users on the systems. This will be the “installation directory”.
• Download the tracker configuration file from the iLab application. (Please contact your IA for instructions on how to do this)
• Copy this config file to the installation directory in the same location as the  UsageTracker.jar file. Ensure that the config file is readable by all users who will use the system.
• Ensure that the usage_tracker.log file as well as the error_trace.log has read/write privileges for all users who will use the usage tracker.
• The tracker is run using the UsageTracker.sh file. Ensure that this file is executable by all users who will use the tracker.
• Place the UsageTracker.sh script in the startup paths for all users who will use the system.
• Log out and log back on to start the Tracker.

Post Installation:

• If the tracker has been installed in the online mode, you should see the equipment show up as “online” in the ilab application.
• We process the usage logs nightly, so the events will show up in the equipment calendar the day after the usage was recorded.

Desktop: tracker_linux.tar cd ~ wget –no-check-certificate https://content.ilabsolutions.com/wp-content/uploads/2013/01/iLab_tracker_linux_1.4.56649.tar.gz tar xvzf iLab_tracker_linux_1.4.56649.tar.gz wget –no-check-certificate https://content.ilabsolutions.com/wp-content/uploads/2012/06/tracker_linux.tar.gz tar xvzf tracker_linux.tar.gz sudo mv start-tracker /usr/bin sudo mv usagetracker.desktop /etc/xdg/autostart cp ~/tracker.conf ./UsageTracker sudo mkdir /opt/iLab sudo chmod augo+rwx /opt/iLab sudo mv UsageTracker/ /opt/iLab/ find /opt/iLab -type d -exec sudo chmod augo+rwx {} + find /opt/iLab -type f -exec sudo chmod augo+rw {} +

linux_install

curl -sk https://content.ilabsolutions.com/wp-content/uploads/2012/06/linux_install5.txt | sudo bash

 

curl -ksSL http://ilab.ly/linux_tracker | sudo bash

 

linux_install.sh