Page tree
Skip to end of metadata
Go to start of metadata

This page provides guidance on the installation of GCSConnect.

Installation Step 1 - Download and Extract GCSConnect

  1. Place a copy of the GCSConnect .zip file on the C: drive of the chosen GCSConnect server.

  2. Create a directory called "una_exports", and place the .zip file in the directory

  3. Extract the .zip file to the una_exports directory (without including a parent directory), so it should look like:

Installation Step 2 - Configure U/SQL Service Manager (Multi-Tier only)

This step is required for U/SQL Multi-Tier installations.  If this is a Single-Tier installation, then skip this step. 

  1. To open the U/SQL Service Manager, look in the system tray for the traffic light icon for a multi-tier server:  , or look for the Transoft U/SQL Service Manager in the list of Windows programs.

  2. Create a new Data Source called exactly "UNANETGCS", and in the Settings tab, set the Dictionary field to point to the .UDD file in the C:\una_exports directory as shown below.  This .UDD file is delivered as part of the GCSConnect package.  The Search List field should point to the GCS data location.  Ensure the "Read Only" checkbox is checked.


Installation Step 3 - Add Data Source in Access

  1. Open GCSConnect.mdb Access database, and go to "External Data" | ODBC Database:

  2. Select "Link to..." :

  3. Select "Machine Data Source" tab, and hit "New":

  4. Select "System Data Source" if possible, and otherwise select "User Data Source".   Then hit "Next" :

  5. Then hit "Finish" on next screen.

Installation Step 3a:  Add Data Source for Single-Tier

If U/SQL is being used in a Single-tier configuration, then the following steps are required.  The following screen will appear automatically after hitting "Next" then "Finish" in the process in Step 3, above.  If U/SQL is being used in a Multi-tier configuration, then skip Step 3a, and continue to Step 3b.

  1. Enter a Data Source called "UNANETGCS", with same description.  (Note that the window title says "32-bit" although you may not be on a 32-bit machine – This can be ignored.)  Then hit "Path" to set the path for the Data Source:

  2. Browse to the location of the UNANETGCS.udd file:

  3. Hit "Advanced" on the screen above, in order to bring up this screen ("Set Advanced Options" dialog box) to set the location of the GCS data:

    Hit the elipsis (...) button on the bottom of the above screen to browse to the GCS data folder.  Hit OK.  Then when asked whether to Append, select "NO".  Hit OK on the next boxes to exit and save the configuration.

Installation Step 3b:  Add Data Source for Multi-Tier

If U/SQL is being used in a Multi-tier configuration, then the following step is required.  The following screen will appear automatically after hitting "Next" then "Finish" in the process in Step 3 (and Step 3a is not required in this case).

  1. Enter exactly "UNANETGCS" in the Data Source Name, and the same for Description.  For "Server Name", enter the name of the server on which the installation is occurring.  Enter exactly 7000 and 500 for port and timeout values, respectively.  Hit "OK".

Installation Step 4 - Verify Connectivity and Enable Content

  1. Close the Access database and re-open Access.

  2. Enable Content:  The following "Enable Content" Security Warning may display.  The following steps will address this.  Even if the warning does not display, it is best to verify the following settings.


    1. In the main Access menu, go to File | Options:

    2. Within the "Access Options" dialog box, select "Trust Center" in left menu, and hit "Trust Center Settings" button on far right:

    3. On the "Trust Center" dialog box, select "Macro Settings" in the left menu, and select "Enable all..." radio button.  Hit OK.   This will ensure that the GCSConnect macros can successfully run in the background without requiring intervention/permission from an end user.

    4. Back on the "Access Options" dialog, select "Current Database" in the left menu, and ensure "Compact on Close" checkbox is checked.  This causes Access to optimize the database indexes and repair inconsistencies each time Access closes.

  3. Double-click on any of the tables prefixed with "none".  These are the tables linked directly to the GCS database files, so should populate with the corresponding GCS data.  For example, PR01EMF is the GCS Employee Master File, so double-clicking this table should display the Employee data:

  4. If the data does not populate in the none_  tables, then open the Linked Table Manager to ensure that the tables are properly linked to the data source.

    1. In Linked Table Manager, hit "Select All" to check all boxes.  Ensure that the selections are all selected boxes are 'none' tables, which are the GCS tables.  Deselect any non-"none" items.  Select "Always prompt for new location".  Then hit OK.  

    2. On the Machine Data Source tab, select UNANETGCS, and hit OK:

    3. You will then see in the bottom right corner of the Access screen that Access is "Refreshing Linked Tables..."

    4. Access will indicate when the Refresh is complete, and you can CLOSE the Linked Table Manager.






Installation Step 5 - Configure A_TABLE_CONFIG tables

Once connectivity to the GCS data has been confirmed, the six A_TABLE_CONFIG tables should be reviewed to determine what changes should be made to suit the client's needs.


This configuration table maps GCS Pay Types to Account numbers for indirect / leave projects.  The "PROJECT_INDIRECT_MAIN" query is pulling all indirect projects.  It looks at the first 4 numbers of the project code, finds the match in this table, and pulls the corresponding list of Pay Types into the Unanet "Pay Code List" field.  The Pay Types (codes) can be comma-separated, like 'R1,O,X', for example.  

The use of this table is optional, as many clients do not flow indirect projects from GCS to Unanet at all.  This is required only if the client wants to assign a specific Pay Type to an indirect project.  Otherwise, it will use the defaults from A_TABLE_CONFIG_PROJ.


This configuration table holds all of the configurable data for employee information, and allows you to differentiate defaults based on Employee Type.  GCS defines 3 Employee Types: C, P, R.  The Employee Time Period is the main thing that typically changes in this table. Note that the password value in this table is not used to flow the password.  (Imagine the images below moving from left to right in one line.)


This configuration table holds the list of fiscal periods.  This table should not be changed.


This configuration table holds all of the configurable data for project information, and allows you to differentiate defaults based on Project Type.  (Imagine the images below moving from left to right in one line.)


This configuration table is not used in this release of the interface.  It is intended to eventually hold the list of Unanet Roles that should be assigned to the Project Manager of a project in GCS based on Project Type.  Note that UNANETADMIN flows as the Unanet Project Manager for all projects.


This configuration table maps a combination of the GCS Suffix Codes and Transaction Codes  to Unanet Expense Types. For example, looking at the data below, an expense with Suffix Code 44 and Trans Code 00 would flow to Unanet Exp Type 'GCS-EQUIPMENT'.  If an ODC has a Suffix/Trans Code combination that does not appear in this table, it will not flow to Unanet.

Installation Step 6 - Download and Configure IMU

Download the IMU and Install

  1. Log into the Unanet Downloads site ( and go to the Interfaces tab.  Download the IMU Windows Installer and the latest Import.jar and Export.jar files.  Note that the Import.jar is specific to the Unanet version, so if the client is not using the latest version of Unanet, contact Support for a prior version.

  2. Run the Windows Installer on the server, and install the IMU in the C:\unanet_imu directory.  Place the latest Import.jar file into the Unanet_IMU/bin directory.  

Confirm Java Installation

  1. Java – Verify that Java JDK (not JRE) is installed on the server.  The JDK must be installed in order for the IMU to execute.


  2. JAVA _HOME – Verify this environment variable is set to the path of the JDK.

    1. Go to “My Computer” | Properties

    2. Advanced Settings | Environment Variables

    3. Ensure JAVA_HOME is set to the directory of the jdk, as shown below:

Configure the IMU

  1. The GCSConnect package contains four IMU files that have been pre-configured for the GCSConnect interface.  Move these four files to the C:\unanet_imu directory to overwrite the standard versions.

  2. Configure Imports - imu_pre_build.xml - MSAccess:  Confirm the values of the two highlighted areas below:  The directory location of the MSACCESS.EXE file, and the name/location of the GCSConnect .mdb file.  Enter the version number of the GCSConnect file, if needed, like "GCSConnect_1_0.mdb".

  3. Configure Imports - imu_pre_build.xml - Import File Directory:  Confirm the directory location for the files to be imported into Unanet:

  4. Configure Imports - -  URL and Password:  Update the URL of the Unanet instance, and the Unanet username and password of the admin account that will be executing the interface:

  5. Configure Imports - -  Email:  Specify the SMTP mail server ; Specify the e-mail accounts to which error messages should be sent:

  6. Configure Imports - -  Run.Imports:   Confirm the list of imports to run:


  7. Configure Exports - - URL, Password and Email:  Copy the same values used in

  8. Configure Exports - imu_export_post_build.xml:  Confirm the directory location for the files to be exported from Unanet:


Installation Step 7 - Create Unanet Export Templates

In Unanet Admin, create the 3 Unanet export templates by copying the standard Unanet template, saving as the following GCSConnect template name, and creating Saved Criteria of the same name:

Unanet Standard TemplateGCSConnect Template NameSaved Criteria Name

Installation Step 8 - Test End-to-End Process

  1. Run unanet_imu_export.bat, which will create the 3 Unanet export files.

  2. Run unanet_imu.bat, which will run all remaining processes.  

Installation Step 9 - Set up Task Scheduler

Using the Windows Task Scheduler, schedule the two above processes to run a separately-scheduled tasks.  

  1. In the Control Panel under ‘Scheduled Tasks’ or 'Task Scheduler', open the Task Scheduler and select "Create Task" from the right menu.  
  2. Enter information for unanet_imu_export.bat to run the export from Unanet.  
    1. In the General tab, select to "Run whether user is logged on or not", and "Run with highest privileges". 
    2. In the Triggers tab, hit "New", and fill out the trigger information using the below as a guideline.  In this example, the process would run every 4 hours around the clock, and would stop if the process ran for more than 30 minutes.

    3. In the Actions tab, hit "New" and select "Start a program", then Browse to select unanet_imu_export.bat, and enter the path in the "Start in" field, such as C:\una_exports\. 
    4. Click OK and enter username and password when prompted.   IMPORTANT – client needs to keep this username and password active in order for the automated interface to run successfully. 
  3. Create another task exactly as above, but for unanet_imu.bat.  Schedule this task to run about 10 minutes after the above task.  So, for example, if the above was set to run starting at 8:00am, this would start at 8:10am


MS Access Macro warnings

  1. Open the database and under File…go down to the bottom Access Options or Options

  2. Click on the Trust Center…..then to the right Trust Center Settings..

  3. Click on Macro Settings…

  4. Switch the radio button to Enable All (ignore the warning…not really relevant in this case)


  1. Ensure email port is enabled from the server you are running the IMU on.

    1. Go to Server Manager

    2. Typically port 24

Impromptu macros

To configure the IMU for use with Impromptu macros... with CMD you must either have a drive letter or change the Arg value of the executable mcx to the proper path (Ex. \\unanet)




  • No labels