Unanet Property Files

In the Unanet Home Directory (C:\Unanet), there will be a subdirectory called \properties.  Inside the properties directory, there may be up to five property files: 

(1) license.properties

(2) unanet.properties - View all Unanet property definitions and default values.

(3) database.properties

(4) menu.properties

(5) text.properties  - View all text property definitions and default values.

Each is explained below.  To edit these files, open the file using any text editor. Any changes to any of these files will require that you stop and restart the Servlet Engine service  (e.g. JRun) in order for the changes to take effect. 

license.properties file

This file is provided by Unanet Technologies and should look similar to this (depending on the products you have purchased and installed).   Make sure you copy the license.properties file that you received from Unanet Technologies into this directory: [Unanet Home Directory]\properties.

# UnaTime License  <<Key to access the timesheet>>
unatime.license.name= <<Your Company Name>>
unatime.license.users= <<number you purchased>>
unatime.license.expires=
unatime.license.key=4ac45fb95722b39219f808285b469a75
  
# Una$ense License  <<Key to access the expense sheet>>
unasense.license.name= <<Your Company Name>>
unasense.license.users= <<number you purchased>>
unasense.license.expires=
unasense.license.key=01761113b6a42faffea045dd39243663

unanet.properties file

This file is used to change parameter settings within Unanet.  Below are some examples of some of the parameters you can change and what they mean.  Remember, if you make any changes to this file, you must stop and re-start your servlet engine for the changes to take effect.

Below are some of the common unanet properties described.  You can also view all unanet property definitions and default values.

E-Mail Section

If you want to use the E-mail feature of Unanet to automatically send E-mail when a timesheet or expense report  is submitted, approved, disapproved, etc., then add or modify these lines in the unanet.properties file:  (NOTE:  You also must have the mail.jar and activation.jar files in your servlet engine ClassPath.   See E-mail Setup, for an example).

Example:

unatime.email=true
mail.host=mail.yourdomain.com    (this is the name of your SMTP server)
unatime.email.default_from_address=admin@abc.com

Display Company Logo on Reports

To setup this default, edit your unanet.properties file on your web server in the ..\Unanet\properties directory. You should see a list of the fields similar to the ones shown below. If not create them.

Set up and select different Company Logos:

Note: In order to be able to have multiple logos, use "," as the delimiter.  IMPORTANT: do not use a comma within any entries, the comma can only be used as a delimiter.

Create Your Own Splash Image

You can override the Unanet Logo Splash image displayed on the opening screen of Unanet.  Below is an example of how to replace the image.  The only parameter that is required is the unanet.splash.src field.  This field must be the full URL to the image you want displayed. 

Example of how it would be placed in the unanet.properties file:

# Splash Screen Image

unanet.splash.src=http://machine.domain.com/unanet/image.gif
unanet.splash.url=http://www.randomhouse.com/seussville/
unanet.splash.alt=I will not eat green eggs and ham!
unanet.splash.target=_blank

Above are some of the common unanet properties described.  You can also view all unanet property definitions and default values.

database.properties file

Open the database.properties file using any text editor. This file is located in your [Unanet Home Directory]\properties directory.   Below are examples depending on the JDBC Driver you are using. 

# i-Net Driver for SQL*Server: (Default Driver included with Unanet)
#
# host = "myname.thedomain.com"
# port = "1433"
#
# Syntax: unatime.database.url=jdbc:inetdae:<<host>>:<<port>>?database=unanet
# Example 1: unatime.database.url=jdbc:inetdae:myname.thedomain.com:1433?database=unanet
# Example 2: unatime.database.url=jdbc:inetdae:localhost:1433?database=unanet
#
# Change unatime.database.url below if database is on a different machine or port:

unatime.database.driver=com.inet.tds.TdsDriver
unatime.database.url=jdbc:inetdae:localhost:1433?database=unanet
unatime.database.username=unanet
unatime.database.password=unanet
unatime.database.maxconnections=16
unatime.database.idletimeout=600000
unatime.database.activetimeout=7200000

# =======================================================================================
#
# WebLogic Driver for SQL*Server: (Driver is purchased separately).
#
# host = "myname.thedomain.com"
# port = "1433"
#
# Syntax: unatime.database.url=jdbc:weblogic:mssqlserver4:<<host>>:<<port>>?db=unanet
# Example 1: unatime.database.url=jdbc:weblogic:mssqlserver4:myname.thedomain.com:1433?db=unanet
# Example 2: unatime.database.url=jdbc:weblogic:mssqlserver4:localhost:1433?db=unanet
#
# Change unatime.database.url below if database is on a different machine or port:

unatime.database.driver=weblogic.jdbc.mssqlserver4.Driver
unatime.database.url=jdbc:weblogic:mssqlserver4:localhost:1433?db=unanet
unatime.database.username=unanet
unatime.database.password=unanet
unatime.database.maxconnections=16
unatime.database.idletimeout=600000
unatime.database.activetimeout=7200000

# =======================================================================================
#
# ORACLE JDBC-THIN Driver:
#
# host = "myname.thedomain.com"
# port = "1521"
# sid = "orcl"
#
# Syntax: unatime.database.url=jdbc:oracle:thin:@<<host>>:<<port>>:<<sid>>
# Example 1: unatime.database.url=jdbc:oracle:thin:@myname.thedomain.com:1521:orcl
#
# Change unatime.database.url below and add in your <<host name>> where oracle resides
# Also change <<port>> and/or <<sid>> if different from these defaults

unatime.database.driver=oracle.jdbc.driver.OracleDriver
unatime.database.url=jdbc:oracle:thin:@<<host name>>:1521:orcl
unatime.database.username=unanet
unatime.database.password=unanet
unatime.database.maxconnections=32
unatime.database.idletimeout=600000
unatime.database.activetimeout=7200000

menu.properties file

The menu is a hierarchical construct, starting with the root (e.g., "menu") and continuing with all descendents. The format for each line is:

<identifier>=<sorter>,<name>[,<url>[,<target>[,<permissions>]]]

identifier: A unique identifier for this menu item, which indicates the parent of this item.
sorter: An integer value used to sort items with the same parent. Items with the same parent and the same sorter are sorted with the name.
name: The text displayed on the menu for this item (if it starts with '&' then look for a resource bundle element with that name).
url: The URL for this item (if it starts with '?' then prepend the url for the application).
target: The window/frame where this URL should be loaded.
product: A boolean expression defining the products that enable this option.
permissions: A boolean expression defining the permissions required to see this item.

Below is an example:  (To view all the menu properties and settings, open your unanet.jar file using winzip and view the file:  com\unanet\unatime\menu.properties).   Don't make any changes to this file.  Leave the jar file the way it is.   Use the menu.properties file in your Unanet Properties directory to override these settings.  If the file doesn't exist, then create it yourself, leaving line 1 blank  at the top, adding your parameters starting on line 2.  Use any text editor.

menu=0,Menu,,,,
menu.user=10,User,,,unatime|unasense,administrator|manager|projectManager|timesheetUser|expenseUser
menu.user.timesheet=10,&timesheet.singular,?action=my_timesheet,main,unatime,timesheetUser
menu.user.timesheet.add=10,Add,?action=timesheet_add,main,unatime,timesheetUser
menu.user.timesheet.active=20,Active,?action=my_timesheet_active,main,unatime,timesheetUser
menu.user.timesheet.history=30,History,?action=my_timesheet_history,main,unatime,timesheetUser

Example 1: Removing an item from the Unanet Menu

To remove an item from the Unanet Menu, simply replace the permissions parameter with the word [remove].

For example, if under the Expense Menu, you do not want the Request Sub Menu to appear, you would change the existing property from:

menu.user.expense.authorize=10,&request.label.singular,,,unasense,expenseUser

to

menu.user.expense.authorize=10,&request.label.singular,,,unasense,remove

If that line does not exist in your menu.properties file, or that file does not exist in your properties directory, then simply create the file and add that line to the file.    The only requirement is that the file must start with 1 blank line and any additional parameters you are overriding start on line 2.   Stop and re-start your servlet engine.

Example 2: Custom email address on Help -- Support

Adding the following entry to the menu.properties file located in your Unanet Properties directory, would provide allow a user to launch an email window -- pre-populated with the email address of your choice:

menu.help.support=20,Support,mailto:youremail@yourcompany.net,,,

text.properties file

Certain aspects of the system can be changed by editing the  text.properties file. If this file does not exist in the properties directory on the web server, then it must be created. The only requirement is that the file must start with one blank line and that the parameters start on the second line. 

Note: In order for the changes to take effect, it is required to stop and restart the servlet engine. 

User Defined Fields

A number of the tables within Unanet have additional fields available that are referred to as "User Defined Fields".  The tables that currently include user defined fields are:

• Organization

• Project

• Person

• Task (tasks have user defined fields -- but they currently can not be activated and used via the user interface)

• Contact

Each of these tables contains 10 additional fields named "user01, user02..... user10".  By default, these fields are not available via the user interface, but can be made so by setting an appropriate text.properties values.  Check out each of the links above for additional information about setting up user defined fields.

Even without making these fields available via the user interface, these fields do exist on the database tables, and are supported in the Import and Export functionality.

In addition, text.properties entries can be used to control some additional behavior.  You can also view all text property definitions and default values.

Back to Installation Table of Contents

Copyright © 1998-2002 Computer Strategies, Inc., All Rights Reserved.
Last revised: September 13, 2002 .