The TMSSLite.cfg file allows TapeTrack administrators to customize the end-user experience for Lite users. You can insert, remove, and change the names of the tasks in the Tape Management Task Menu, limit functions of a Repository, and manage how log files are created and archived.

Any modifications made in the config file have only local effects not global. If you have multiple installations of Lite any modifictions will need to be done on each computer.

//
// Sample TapeTrack Lite Configuration File
//
options=
{
   menu= 
   (
      { 
          filter="*Guide*";
          hidden=true;
      },
      { 
          filter="*Users*";
          hidden=true;
      },
      { 
          filter="*Upload*";
          hidden=true;
      },
      { 
          filter="*Outlook*";
          hidden=true;
          // text="Alternate iCalendar text";
      },
      {
             hidden=true; 
             text="Custom Command 1";
             //sequence=100;
             command="echo hello > out.txt";
             filters=( "*this string will be excluded*", "*So will this string*" );
      }
   );

   //
   // When exporting data to email send to the following addresses
   //
   email = [ "emailto1@tapetrack.com", "emailto2@tapetrack.com" ];

   //
   // If you specify a valid logfile value the logfile dialog will not be displayed 
   //
   // logfile="%HOMEDRIVE%HOMEPATH\\Documents";

   //
   // If you would like to pickup your list files somewhere else then uncomment this.
   //
   // setlistdirectory="%USERPROFILE\Documents";
   
   //
   // The localrepositoryfilter value determines which Repositories are show and local to the current user
   //
   // localrepositoryfilter="*";
   
   //
   // You can route all log file data to a syslogd service too...
   //
   // syslogd = { facility="local1"; server="192.168.10.1"; port=514; }; 

   //
   // If you're a little put off by a computer telling you about your mistakes you can set disablespeech to true.
   //
   // disablespeech=true;

/*
   variables = {
       TMSSLEVELNAMES = "A,B,C";
   };
*/

};

/*
servers =
{
   Server1 = { host = "odpapi-test.tapetrack.com"; }; 
   Server2 = { host = "odpapi-test.tapetrack.com"; port=433; proxy=true; };
};
*/

//*
//* The Allocation table allows you to automatically assign tapes to a container.
//*
//* The allocation process works like this:
//*
//* 1. If you have an allocation section the following logic will occur
//* 2. If a tapes has no container assigned the program will loop through each element looking for a volume scope match
//* 3. If you get a match the program will then look through each available Container looking for a scope match (and looking at container capacity)
//* 4. If you get a match the tape will be automatically assigned to that container
//* 5. If you don't get a match the program will try and look for a container with capacity that has no data cluster. If a Container is found-
//*    the container will be assigned that data cluster and the tape will be assigned to that container.
//*
//* Notes: that the datacluster value in the volume and container sections are filters, the value in the assignment is a literal data cluster value -
//*          for a datacluster than must pre-exist.
//*

/*       
allocation =
(
   { 
       volume = { barcode="*"; datacluster="WEEKLY_TAPES"; };
       container = { barcode="*"; datacluster="WEEKLY_TAPES"; };
       assignment = { barcode="*"; datacluster="WEEKLY_TAPES"; };
   },
   { 
       volume = { barcode="*"; datacluster="YEARLY_TAPES"; };
       container = { barcode="*"; datacluster="YEARLY_TAPES"; };
       assignment = { barcode="*"; datacluster="YEARLY_TAPES"; };
   },
   { 
       volume = { barcode="*"; datacluster="*"; assignment=false; };
   }
);


routing =
(
   { 
       volume = { source="OFFS"; target="RACK"; };
   }
);
*/

//*
//* You can preprocess barcodes locally before they are sent to the Server for parsing.
//* This allows you to convert a Volume to a fully qualified barcode.
//* You can add as many filter/values as you like. The list will be searched in the order they appear in this file
//*

/*
barcodes=
{
   translations=
   (
      { filter="GAZ*L1"; value="GAZ.LT1.*"; },
      { filter="GAZ*L2"; value="GAZ.LT2.*"; cleanup={volume="0000*";}; }
   );
};
*/

//*
//* If you want to disable specific popup notifications you can use uncomment the notifications section
//* 


notifications = 
{
   filters= 
   (
      { 
    	    title="Library Health Warning"; line1="*"; line2="*"; disable=true;
      }
   )
};

The menu = command in the TMSSLite.cfg file can be used to customize the Tape Management Task Menu.

Tasks can be added, hidden, reordered, and renamed to address the specific needs of an organization or individual.

There are several commands that can be used under the menu command:

• // - a double forward slash indicates a comment. Because of this, anything following a double slash will not be included in the script and will not modify Lite.
• filter - filter is used to isolate the pre-existing command that you would like to alter. TapeTrack Filters can be used in this section. For example, the above script uses “ filter=“*Outlook*”; ” to isolate any variable in the Tape Management Task Menu that has the String “Outlook” in it. Due to the fact that “Outlook Integration” is the only Tape Management Task Menu item that has “Outlook” in it, it is the only menu item that will be isolated and changed.
• hidden - hidden can either be true or false and will dictate whether or not a Tape Management Task Menu appears in the menu.
• text - text indicates what will be displayed in the Tape Management Task Menu in TapeTrack Lite.
• sequence - sequence indicates where in the Tape Management Task Menu the task be displayed. The native sequence numbers are in tens. For example:

In this example, Scan-In would be the first option. It thus has a sequence number of 10. Likewise, List is the sixth option and thus has a sequence number of 60. To put a custom command between Recall and Manage, you could use the number “45” in the TMSSLite.cfg file to indicate that it is between the 4th and 5th option.

• command - command can be used to add a command line function to the Tape Management Task Menu. The most popular of these is TMSS10Ping.

Example

The following script was used to alter the displayed Tape Management Task Menu:

      menu= 
   (
      { 
          filter="*Guide*";
          hidden=true;
      },
      { 
          filter="*Users*";
          hidden=true;
      },
      { 
          filter="*Upload*";
          hidden=true;
      },
      { 
          filter="*Outlook*";
          hidden=true;
          // text="Alternate iCalendar text";
      },
      {
             hidden=true; 
             text="Custom Command 1";
             //sequence=100;
             command="echo hello > out.txt";
             filters=( "*this String will be excluded*", "*So will this String*" );
      },
       {
           filter="*Send*";
           hidden=false;
           text="Transmit to Offsite Vault";
           sequence=01;
       },
       {
           filter="*Recall*";
           hidden=false;
           text="Return from Offsite Vault";
           sequence=02;
       },
       {  
           hidden=false;
           text="Ping TapeTrack Server";
           command="TMSS10Ping localhost";
           sequence=100;
       }
   );
 
   //
   // If you specify a valid logfile value the logfile dialog will not be displayed 
   //
 
   logfile="%HOMEDRIVE%HOMEPATH\\Documents";
 
 

The above script provides the necessary components to:

• Hide any command with the String Guide, Users, Upload or Outlook.
• Change the displayed name of the Send function to Transmit to Offsite Vault.
• Place the Send function at the top of the drop-down list.
• Change the name of the Recall function to Return from Offsite Vault.
• Place the Recall function second in the drop-down list.
• Add a command to the Tape Management Task Menu that runs TMSS10Ping for the local TapeTrack Server with the text Ping TapeTrack Server. Replace the server address localhost with your TapeTrack Framework Server address (dotted IP or DNS) to run the command against your server.
• Place that command at a low location in the Tape Management Task Menu.
• Change the Save Location for Log Files.

Note: the sequence numbers 01 and 02 were used to indicate that they came before the default first sequence number of “10” that is typically assigned to Scan-In.

Log files create a .txt read -file of all of the actions that are performed during a session. Using the TMSSLite.cfg file, you can change the location of where these files are saved. The default save location is “ %HOMEDRIVE%HOMEPATH\\Documents ”;

To change where the log file is saved uncommented (remove // at the start of line) and set directory path where you want the file written to. The directory specified must exist before running TapeTrack Lite.

 logfile="C:\Users\GazillaByte\Documents\TapeTrack Log Files";

Once the log file directory is specified in the configuration file, the log file location screen will no longer be displayed when selecting tasks in TapeTrack Lite.

Changing the localrepositoryfilter variable will limit Lite users to only see a specific Repository within their Customers.

For example, if you added the script:

     localrepositoryfilter="*LIBR*"; 

TapeTrack Lite will only display Repository-ID's containing the String LIBR.

If you have a syslogd service setup, you can configure the TMSSLite.cfg file to have Lite send log files to your syslogd Server using the syslogd = command.

The TMSSLite.cfg sample file has the following example:

syslogd = { facility="local1"; server="192.168.10.1"; port=514; };

You can stop TapeTrack Lite verbalizing scanning errors by uncommenting (remove // at the start of line) the line

Change code

   //
   // If you're a little put off by a computer telling you about your mistakes you can set disablespeech to true.
   //
   // disablespeech=true;
   

to

   //
   // If you're a little put off by a computer telling you about your mistakes you can set disablespeech to true.
   //
   disablespeech=true;