Blog

Truncation errors while importing data

You may find that the default column widths configured by the Analytics for FusionReactor application (e.g. fusionreactor-fadc-1.0.5-DCAPP.zip) are not long enough for the data supplied by your server. If a value is too big to fit into the belonging target column the value will be truncated before it is inserted and an error message is written to the fusionanalytics-datacollector.log and fusionanalytics-datacollector-error.log files as shown below:

...
2011-11-03T10:59:45.135-0400 [FADC-importer-3] ERROR [com.intergral.fusionanalytics.dc.evt.FileMonitorEventHandler] myApp/myDC/request.log: 2011-11-03 10:59:45,135 [LINE] 6578 [ERROR] "myApp/myDC/request.log (ID=3c8ffa2a-413f-472b-b0cc-fab9c277854f): Truncated value of column JSESSIONID from 54 to 50 characters: Original value: d4309ef9d92a84dfeddc5e364d59535b6b26,+cftoken=13194335: Truncated value: d4309ef9d92a84dfeddc5e364d59535b6b26,+cftoken=13194335" [INPUT] "2011-11-03 10:57:01.692 1320332221692 4 1320259710907 98327 COMPLETED "" jrpp-124 10.10.37.249 GET http://10.0.0.10/index.cfm 93 15 8108992 1221932 8108992 6887059 "fuseaction=lms.enterClassSection&classSectionId=48506" 302 78 "" d4309ef9d92a84dfeddc5e364d59535b6b26,+cftoken=13194335 387467 85523722 0 0 0 0 0 0 0 0 93"
...

In this case you can change the column size as follows:

1. Stop the FusionAnalytics Service/Daemon
2. Open the DCML file of the application you want to change (e.g. C:FusionAnalyticsServerdatafadcApplicationsmyApplicationmyApplication.dcml) in an editor.
3. Search all columns definitions you want to update and replace their column size with the new value.

Example: Changing the size of the JSESSIONID column from 50 to 100

<FadcConfig version="1.0" xmlns="https://www.fusion-analytics.com/datacollector">
  <DataOutput dbType="mssql">
    ...
    <Table name="request_status" engine="InnoDB">
      ...
      <Column type="varchar(50)" required="false" name="jsessionid"/>
    </Table>
    ...
    <Table name="request" engine="InnoDB">
      <Column type="varchar(50)" required="false" name="jsessionid"/>
    </Table>
    ...
    <Table name="crashprotection" engine="InnoDB">
      <Column type="varchar(50)" required="false" name="jsessionid"/>
    </Table>
    <Table name="request_status_report" engine="InnoDB">
      <Column type="varchar(50)" required="false" name="jsessionid"/>
    </Table>
    ...

becomes

<FadcConfig version="1.0" xmlns="https://www.fusion-analytics.com/datacollector">
  <DataOutput dbType="mssql">
    ...
    <Table name="request_status" engine="InnoDB">
      ...
      <Column type="varchar(100)" required="false" name="jsessionid"/>
    </Table>
    ...
    <Table name="request" engine="InnoDB">
      <Column type="varchar(100)" required="false" name="jsessionid"/>
    </Table>
    ...
    <Table name="crashprotection" engine="InnoDB">
      <Column type="varchar(100)" required="false" name="jsessionid"/>
    </Table>
    <Table name="request_status_report" engine="InnoDB">
      <Column type="varchar(100)" required="false" name="jsessionid"/>
    </Table>
    ...

4. Save the updated DCML file
5. Update the columns in the database

Following the example above, you should now execute the following SQL statements:

-- MySQL
ALTER TABLE CRASHPROTECTION MODIFY JESSESIONID VARCHAR(100); 
ALTER TABLE REQUEST MODIFY JESSESIONID VARCHAR(100); 
ALTER TABLE REQUEST_STATUS MODIFY JESESSIONID VARCHAR(100); 
ALTER TABLE REQUEST_STATUS_REPORT MODIFY JESSESIONID VARCHAR(100); 

-- Microsoft SQL Server
ALTER TABLE CRASHPROTECTION ALTER COLUMN JESESSIONID VARCHAR(100);
ALTER TABLE REQUEST ALTER COLUMN JESESSIONID VARCHAR(100);
ALTER TABLE REQUEST_STATUS ALTER COLUMN JESESSIONID VARCHAR(100);
ALTER TABLE REQUEST_STATUS_REPORT ALTER COLUMN JESESSIONID VARCHAR(100);

6. Restart the FusionAnalytics Service/Daemon

This completed the procedure. You can now insert data with JESESSIONID values up to 100 characters long without truncation errors.

Resetting the password for the FADC and FADS admin login

Description

During the Setup you are asked to provide a password for the admin user used by FADC and FADS. If you can’t remember the password you have entered in this step you can follow the procedure described below to set a new password. This requires access to the file system of the computer where FusionAnalytics Server is installed.

Resetting Passwords

To reset the password used for the admin user first stop the FusionAnalytics Server.
Next create the two files fadc.pwd and admin.txt as described below defining the new password you want to use. For FADC remove the FADC-SDB directory. Start the FusionAnalytics Server again. During startup these files will be processed, the passwords updated and a new version of the FADC-SDB directory created. Once the passwords have been updated successfully the fadc.pwd and admin.txt files are deleted.

In the following we assume FusionAnalytics is installed in the default directory. Change the path shown below if you have installed it to a different directory.

We recommend to use the same password for the admin user in FADC and FADS.

FADC

Remove the directory

C:\FusionAnalytics\Server\bin\FADC-SDB

Create a new text file

C:\FusionAnalytics\Server\webapps\fadc\fadc.pwd

with the following content:

password=myNewPassword

Replace ‘myNewPassword’ with the password you want to use. The length of the password must be at least 1 and not exceed 16 characters.

FADS

Create a new text file

C:\FusionAnalytics\Server\webapps\fads\WEB-INF\classes\admin.txt

with the following content:

myNewPassword

Replace ‘myNewPassword’ with the password you want to use.

Restart the FusionAnalytics server and then login to FADC/FADS to check that the new passwords have been applied.

This technote provides access to the FusionAnalytics 1.0 Documentation as a single PDF to download and read offline. Please note that the PDF is generated periodically and may not reflect the latest changes to the online documentation.

FA10-191011-2148-6.pdf

Creating a new database for FusionAnalytics

INTRODUCTION

FusionAnalytics requires a Microsoft SQL Server database to work. We recommend version 2008 R2 which can be downloaded as free Express Edition limited to a maximum database size of 10GB. Check the installation options and make sure that you download at least a version which includes the Database and the Management Tools.

CONFIGURING NETWORK CONNECTIONS

FusionAnalytics uses JDBC to connect to the Microsoft SQL Server database. To allow FusionAnalytics to communicate to the database the network settings of the database server must be configured appropriately. To configure the network connections of the database server start SQL Server Configuration Manager

then select Protocols for SQLExpress and double click the line with the TCP/IP protocol shown below

In the TCP/IP Properties dialog set Enabled to Yes

then click on the IP Addresses tab and at the bottom of the property list enter 1433 as value for TCP Port.

To apply the configuration changes the SQL Server must be restarted. This can be done from the SQL Server Configuration Manager shown below.

CREATING A DATABASE LOGIN

Although not required we recommend to create a dedicated database login to be used with FusionAnalytics. To create a new database login start SQL Server Management Studio

and connect to the database server.

Use the Object Explorer to drill down to the Logins node and from the context menu select New Login.. as shown below.

In the Login – New dialog provide a name for the new login. Change the authentication mode from Windows authentication to SQL Server authentication and define a password for the new login. Disable the Enforce password policy option and click the OK button to commit your settings.

CREATING A NEW DATABASE

Using the Object Explorer of Management Studio select the Database node and from the context menu select New Database.. as shown below:

In the New Database dialog provide a name and owner for the new database.

Next click on the little button with the three dots underneath the Autogrowth column in the first line. In the Change Autogrowth for FADB dialog change the setting for Autogrowth from its default value In Megabytes to In Percent as shown below

Back in the New Database dialog change the Recovery Model of the database from Full to Simple mode

and enable the database to automatically shrink its size by setting the Auto Shrink property to True.

Your new database is now ready for use with FusionAnalytics.

Creating and configuring your SQL Server database using a script instead of Server Management Studio

If you are unable to create your database using Microsoft SQL Server Management Studio as explained in our quick start guide, it is possible to use a script to replicate the process. Simply use search & replace to configure the script below with the values you would like to use.

Ensure you have sufficient permissions to create and edit users and databases.

/*
 * This script will create a new database with the correct configuration for FusionAnalytics 
 * as well as a user as the database owner.
 *
 * # Replace all occurences of "yourDatabaseName" with the name you wish to use. There cannot be an existing database with this name.
 * # Replace all occurences of "yourDirectory" with the directory you with to use without a trailing slash. This must already exist.
 *
 * # Replace "yourUsername" with the username you wish to use
 * # Replace "yourPassword" with the password you wish to use
 *
 * # Set the maximum server memory near the bottom of the script
 *
 */ 


USE Master
GO

--Create a new user
CREATE LOGIN [yourUsername] WITH PASSWORD=N'yourPassword', DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[English], CHECK_EXPIRATION=OFF, CHECK_POLICY=ON
GO

--Create the database. The database must not already exist.
CREATE DATABASE yourDatabaseName ON PRIMARY
( NAME = 'yourDatabaseName',
  FILENAME = 'yourDirectoryyourDatabaseName.mdf',
  SIZE = 25mb,
  MAXSIZE = UNLIMITED,
  FILEGROWTH = 10% )
  
--Create log file
LOG ON
( NAME = 'yourDatabaseName_log',
  FILENAME = 'yourDirectoryyourDatabaseNamelog.ldf',
  SIZE = 7mb,
  FILEGROWTH = 10%  )
GO

USE yourDatabaseName
GO

--Set recommended parameters
EXEC sp_dboption N'yourDatabaseName', N'autoshrink', N'true'
GO
EXEC sp_configure 'show advanced options', 1
RECONFIGURE WITH OVERRIDE

EXEC sp_configure 'max server memory (MB)', 4000 --***SET THIS NUMBER TO YOUR CHOSEN MEMORY LIMIT (MB)***
RECONFIGURE WITH OVERRIDE

ALTER DATABASE yourDatabaseName SET RECOVERY SIMPLE

-- Set the db owner
USE yourDatabaseName
EXEC sp_changedbowner 'yourUsername'

The problem

If a scheduled task is given an end-date that pre-dates the start date, the task will bypass the end-date (ignoring it) and continue to run.
For example:

• Start Date: 01-Aug-2011
• End Date: 01-Feb-2011

How can I stop this from happening?

Please ensure the end-date comes after the start-date to avoid this issue.
For example:

• Start Date: 01-Jan-2011
• End Date: 01-Apr-2011

Problem Description

If an installation of FusionAnalytics has been started and cancelled before it can happen that not all files have been removed afterwards. If the Setup is then executed again a message is displayed

informing the user that the target directory is not empty.

If the user decides to continue with the installation anyway it can happen that the resulting installation is not working.

Recommended Workaround

To prevent this to happen please make sure that the destination directory does not already exist when installing a new version of FusionAnalytics.

FusionAnalytics for FusionReactor Third Party License Agreements and Additional Notices

Intergral Information Solutions GmbH

Schickardstr. 32 – 71034 Boeblingen – Germany

FusionAnalytics for FusionReactor

These notices and/or additional terms and conditions are made a part of and incorporated by reference into such product’s End User License Agreement

THIRD-PARTY LICENSES AND NOTICES FOR INCLUDED SOFTWARE

FusionAnalytics for FusionReactor APML

FusionAnalytics for FusionReactor DCML

Much of the JavaScript enhanced functionality of the FusionAnalytics DataServices / DataCollector administrator web interface appears disabled / non-functioning in Internet Explorer. The reason for this is Enhanced Security Configuration (IE ESC) is enabled for your user.

To use the disabled functionality, we recommend accessing the web administration interface remotely from your own machine. Alternatively (but not recommended for best security practice), disable IE ESC for that user. For details on how to disable IE ESC, please see the Microsoft website (linked below):

IE ESC on Windows 2003
IE ESC on Windows 2008 / 2008 R2