[FNS-37] Removing the requirement for SQL sysadmin permission on FA 2.0.1 and earlier

Description

Description
The Data Volume Management job in FADC goes through the process of updating indices and stats.
In previous versions of FusionAnalytics (2.0.1 and earlier), a command called sp_updatestats was used to do this.
However, this command requires the database user to have the sysadmin server role enabled.

You may feel that it is too much of a risk to enable the sysadmin role. If so, you can download an alternate Data Volume Management script, which uses a different command and does not require the sysadmin server role.

Before Starting Please Note
As an alternate to the sysadmin server role, the user will require the db_owner database role enabled for the FusionAnalytics database. This is the minimum that is required for FADC to run all of it’s jobs correctly.

To enable the db_owner role:

1. Open Server Management Studio.
2. Login as an existing user with system administrator privileges.
2. Navigate to Your DB -> Security -> Logins.
4. Right-click the user you wish to update permissions for and select Properties.
5. Select the “User Mapping” page.
6. Select the Database you wish to map the user to
7. Ensure ‘db_owner’ is checked in the list of database roles.
8. Press OK to save the changes.

Instructions
1. Download this script
2. Navigate to the folder: FusionAnalyticsServerdatafadcApplicationsmyApplication
3. Replace the “manageDataVolume.groovy” file in this folder with the downloaded script.
4. Restart the FusionAnalytics server.

After this, whenever the Data Volume Managment job runs, the alternate script will be used.

Issue Details

Type: Technote
Issue Number: FNS-37
Components: DataCollector
Environment:
Resolution: Fixed
Added: 25/01/2013 16:25:36
Affects Version:
Fixed Version: 2.0.2
Server:
Platform:
Related Issues: None

[FNS-32] Cleanup obsolete request data from database

Description

Cleanup obsolete request data from database

Description
Due to a bug in the Data Volume Management job shipped with FusionAnalytics 1.0.4, parts of the request data in tables REQUEST_AMF and REQUEST_PARAM are not deleted from the database.
To cleanup your database and remove the obsolete data you can download this script and run it on your FusionAnalytics database server.

Before Starting Please Note

  • You will require full access to your FusionAnalytics Database Server and all permissions such as create and delete tables.
  • You will need to specify the database name that is used by FusionAnalytics in the script (see instructions below)
  • This script might take a long time to execute. This is dependent on the following factors:
    • The size of your database.
    • The performance of the hardware where the database is installed.
    • The number of rows that became obsolete.

Example: It will take between 10 to 20 minutes on an environment that has a 200GB database that is installed on a standard HDD and has 40 Million (40,000,000) obsolete rows

Instructions

  1. Download this script
  2. Open SQL Management Studio
  3. Login as an existing user with system administrator privileges.
  4. Navigate to File -> Open -> File
  5. Navigate to the folder where the script is located and select it
  6. At the top of the script enter your FusionAnalytics database name into the square brackets “[]”
    If your database name is “FADB” then it should look like this:

    USE [FADB]
    GO
    
    declare @totalRows int, @rowsToKeep int
    ...
  7. Click the Execute button

When the script has finished you should see the following messages:

(_n_ row(s) affected)
Caution: Changing any part of an object name could break scripts and stored procedures.

(_n_ row(s) affected)
Caution: Changing any part of an object name could break scripts and stored procedures.

Where n is some number of rows

Issue Details

Type: Technote
Issue Number: FNS-32
Components: DataCollector
Environment:
Resolution: Fixed
Added: 15/11/2012 17:19:23
Affects Version: 1.0.4
Fixed Version: 2.0.0
Server:
Platform:
Related Issues: None

[FNS-34] FusionAnalytics 2.0 Documentation (PDF)

Description

This technote provides access to the FusionAnalytics 2.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.

FA20-170113-1139-7.pdf

Issue Details

Type: Technote
Issue Number: FNS-34
Components: Documentation
Environment:
Resolution: Fixed
Added: 17/01/2013 11:55:39
Affects Version:
Fixed Version: 2.0.0
Server:
Platform:
Related Issues: None

[FNS-23] “User does not have permission to perform this action” when running application jobs.

Description


“User does not have permission to perform this action” when running application jobs.


This error can occur when attempting to perform FADC application jobs on your database without sufficient permissions. FADC requires ‘sysadmin’ permission on the database to be able to perform its jobs correctly.

To edit the permissions of an existing user with Microsoft SQL Server Management Studio, you can:

  1. Open Server Management Studio.
  2. Login as an existing user with system administrator privileges.
  3. Navigate to Your DB -> Security -> Logins.
  4. Right-click the user you wish to update permissions for and select Properties.
  5. Select the “Server Roles” page and ensure ‘sysadmin’ is checked.
  6. Press OK to save the changes.

Issue Details

Type: Technote
Issue Number: FNS-23
Components: DataCollector
Environment:
Resolution: Fixed
Added: 28/11/2011 14:16:38
Affects Version:
Fixed Version: 1.0.1
Server:
Platform:
Related Issues: None

[FNS-33] Security Settings for FusionAnalytics E-Mail Reports

Description

When viewing FusionAnalytics reports which have been delivered via email, you may see a request to log in to your FusionAnalytics Data Services server.

This happens because the images which comprise part of the reports are served directly from the FADS system itself.

If you are seeing a request to log in, you have not obtained a cookie for the FADS server on the address from where images are being served.

There are three solutions to this problem.

Log in.

When the login dialog appears, log in as a FADS user who is able to view the images.

Adjust the security settings of the application

You can set your FADS application not to require authentication to view images.

Warning: If you disable this protection, anyone will be able to view these report images, regardless of whether they are a valid FADS user or not.

  1. Navigate on your server to FusionAnalyticsServerwebappsfadsWEB-INFclassesApplicationsYOUR_APP_NAME and open application.xml with a text editor. This editor must be capable of reading and writing UTF-8 Unix files. Windows Notepad is not able to do this – we recommend Notepad++.
  2. In this file, locate the ApplicationWebServer block and carefully remove the Path whose path attribute is /_Persistent.



    You should be left with:

        <ApplicationWebServer>
           <PathRules>
              <Path path="/configuration">
                 <Protected/>
              </Path>
           </PathRules>
        </ApplicationWebServer>
    


  3. Restart the application by logging in to the Data Services webapp (usually located on port 8400), and restarting the data service itself using the Restart button.

Caveat: If the application is upgraded or reinstalled, this procedure must be repeated.

Change the domain name used to serve image links

The problem can also be solved by changing the host name used to serve image links. If you ordinarily log in to the FusionAnalytics Data Service webapp using – for example – http://fred.foo.com:8400/, then you should already have an authentication cookie for this domain. If the system has several aliases, images may be being served from a different domain name and the login dialog will appear. If this is the case, the domain name used in links can be changed:

  1. Log in to the Data Services webapp (usually located on port 8400). Open the System section and click on the Server Settings entry.
  2. Under the settings HTTP Server Host and HTTPS Server Host, change the value to the domain name you usually use.
  3. Click Update Server Settings
    • This will cause generated links to use the new domain name, for which you already have an authentication cookie, and the login dialog should no longer appear.

Issue Details

Type: Technote
Issue Number: FNS-33
Components: DailyStatus Report
Environment:
Resolution: Fixed
Added: 10/01/2013 13:01:27
Affects Version:
Fixed Version: 1.0.4
Server:
Platform:
Related Issues: None