Services and Support
FIT Tracking Solutions support team offers a wide range of services and support tools to enable flexible solutions and prompt technical support to our valued customers.
In an effort to improve our product line and take it in a new and exciting direction, Alcea has launched FIT.
FIT is the latest tracking solution from Alcea, which will replace the prior Fast IssueTrack and Fast BugTrack product lines as Version 7.0.
FIT is built behind the same software foundation as its predecessors but it adds the following advantages :
- allows the integration of multiple systems (including links between them) with a different or common user base.
- allows multiple TRACK objects to exist in separate templates with their own fields and workflow.
- allows customers to add an additional template at half the cost of a new system.
- includes a new drop-down interface.
- includes a revamped website with updated documentation.
The new product is called and installed as FIT. We suggest that you leave your existing system installation as it is, since your users are used to it and you may have services created to use the existing program files. This means that you will start “Fast BugTrack” or “Fast IssueTrack” as normal, but this migration process will cause the programs to start up FIT using the new fit.jar file.
Please note that the migration will configure your existing system with the FIT|BugTrack or FIT|IssueTrack templates accordingly, and you should see no difference unless you decide to use the new Templating features to create a new TRACK.
If you wish, you can install the new FIT product and copy the existing system over top of the new installation, once you have done a proper migration and a few files are upgraded as described below.
Step 1: As always, you should create a backup of your existing system!
Step 2: Check that you have a valid registration key. Please check:
- All customers must have a current support agreement with a recent reg.bin key. (Creation date of registration key must be less than 1 year from release date)
- All Database Module customers must obtain a new key to upgrade. Please email email@example.com to get an updated key.
Step 3: If you are a database customer, make sure that you have made all prior schema changes to your system, prior to Version 7.0. All changes are carefully listed on the product upgrade pages, immediately under the links for each version. The upgrade pages are listed at the bottom of this page. When your old product is upgraded, you must then make the following schema changes to your database tables for the new FIT product :
Step 4: Copy the latest fit.jar from the FIT upgrades page.
These are actually extremely small code files which actually run the migration process for you, rather than contain the old products.
Step 6: You product should be converted properly, and you can now run it as a FIT process. If there are any problems, please contact us right away!
In case you are interested, the following changes should have been made by the migration code.
- changed .lax file to reference fit.jar, rather than the old bugserver.jar or issueserver.jar
- enterprise customers will notice a new “ActiveModules=enterprise” entry in the server.cfg
- an initial “Template0FileName=[bug|issue]template.jar” entry is added to the server.cfg to reference your existing template from the old product.
Step 7: If you have a non-standard installation, you will need to use the new fit.jar, AFTER you have migrated and successfully created a migrate.out file. The new command line should be “java -classpath fit.jar Fit” to start FIT with version 7.0
Old Look: If you want to get back to the old look after the migration, that is not a problem :
- the logo can be changed by setting the rLogo string to “com/other/newlogo.gif” (FBT) or “com/other/fit.gif” (FIT)
- sTitle will look after the title in the browser window.