Financial Management Compliance System

FINANCIAL MANAGEMENT COMPLIANCE SYSTEM
Installation Guide
September 2014
NIG-MNL-v3.2.2
CONTENTS
Introduction ......................................................................................................................................... 4
Implementation Checklist........................................................................................................... 4
Component ................................................................................................................................ 4
Details........................................................................................................................................... 4
Responsible ................................................................................................................................ 4
Best Practice Approach ............................................................................................................... 5
IIS Server Configuration .................................................................................................................. 6
Before you begin........................................................................................................................... 6
Server Pre-requisites ............................................................................................................... 6
Installation Requirements ...................................................................................................... 6
Application Installation................................................................................................................ 6
IIS Configuration ........................................................................................................................... 7
Proxy & Firewall Configuration (Optional) ............................................................................ 9
Database Installation ...................................................................................................................... 10
Before you begin......................................................................................................................... 10
Server Requirements ............................................................................................................. 10
Installation Requirements .................................................................................................... 10
Initial System Configuration ..................................................................................................... 11
Automatic Database Creation ............................................................................................. 11
Manual Database Creation.................................................................................................. 12
Post-Implementation Configuration ......................................................................................... 13
Scheduled Task ............................................................................................................................ 13
Server Requirements ............................................................................................................. 13
Installation Requirements .................................................................................................... 13
Scheduled Task Configuration ........................................................................................... 13
Branch & User Update via Spread Sheet (Optional) ....................................................... 13
Branch & User Update via Web Services (Optional) ....................................................... 13
System Updates ............................................................................................................................... 15
Troubleshooting............................................................................................................................... 16
2 / 18
System Responsiveness ............................................................................................................ 16
Required permissions cannot be acquired ......................................................................... 16
Users are able to see data/info from another user’s session ....................................... 17
3 / 18
INTRODUCTION
The purpose of this document is to provide installation instructions for the Financial
Management and Compliance System (FMCS) developed and supplied by Torque
Software.
This document describes all aspects of the installation process.
Note: see the FMCS Technical Guide for further information, including application
schematics, architecture and security.
Implementation Checklist
A number of skills and pieces of information are required to install the FMCS;
following is a breakdown of the tasks involved, the information required (and from
whom) as well as the skills required to perform those tasks.
Component
Details
Responsible
Implementation
Coordination
Coordinate implementation
of FMCS as per this guide
FMCS Implementation
Project Manager
IIS Configuration
Application installation on
IIS server, configuration of
IIS and Windows
Components
IIS Administrator;
Providing FMCS with
technical resources, e.g.
SQL Server details and
SMTP Server credentials
SQL Database
Administrator (DBA);
Access to SQL Server to
create database;
SQL Database
Administrator (DBA)
FMCS System
Configuration
Database Configuration
Windows Server
Administrator
Windows Server
Administrator
Running SQL Server scripts
FMCS Administrator
Training
Training FMCS Users in how
to administer and maintain
the FMCS
FMCS Administrators;
Torque Software
Installation requires that the user have expertise in Windows Server, Microsoft IIS
and SQL Server configuration and management, with a working knowledge of
deploying ASP.NET applications.
4 / 18
If you do not have access to the required level of skill or require assistance, please
contact Torque Software to arrange technical resources and implementation
support.
Best Practice Approach
As per information technology best practice, Torque Software strongly
recommends implementation of two FMCS instances: one for testing and training
and one for the production system.
The Test instance of the FMCS should not have any access to the production
environment to ensure that implementation and new version testing does not
interfere with the production instance.
5 / 18
IIS SERVER CONFIGURATION
Before you begin
The FMCS runs on Microsoft’s Internet Information Services (IIS) platform. IIS
administration requires expert knowledge; if you do not have access to the
necessary skillset please contact Torque Software.
Server Pre-requisites

Windows Server 2005 or later running IIS7 or later

CPU: Minimum: 1GHz (x86 processor) or 1.4GHz (x64 processor)
(recommended: 2GHz or faster)

Memory: Minimum: 1024MB RAM (recommended: 2GB RAM or greater)

Space required for install: 100mb

Server must be on the AD domain to allow single sign-on (if not on domain,
users will be prompted to log in with Logon ID and FMCS password)
Installation Requirements

.NET 3.51 SP1 installed on the server

Internet Information Services must be installed via Control Panel / Programs
and Features / Windows Features with the following components:

Web Management Tools / IIS Management Console

World Wide Web Services (including all sub options)
Optional: to use the Branch & User Update via Web Services, please ensure the
following components are also installed:

Microsoft .NET Framework 3.5.1 / Windows Communication Foundation
HTTP Activation

Microsoft .NET Framework 3.5.1 / Windows Communication Foundation
Non-HTTP Activation
Application Installation
Unpack the provided .zip file to the c:\inetpub\wwwroot folder on the web server,
ensuring that the folder structure and filenames are retained when unzipping.
6 / 18
IIS Configuration
Note: these instructions assume configuration of the FMCS as
the default IIS web site.
1.
Go to Start  Control Panel  Administrative Tools and open Internet
Information Services (IIS) Manager
2. Expand the server name and the Sites folder, then select Default Web Site in
the list
3. Double click the Default Document icon
4. Move default.aspx to the top of the list, then click back into Default Web
Site.
5. Double click the Authentication icon
6. Enable Windows Authentication and disable Anonymous Authentication,
then click back into Default Web Site
7. Click Basic Settings, you will see a dialog like the one below:
7 / 18
8. Ensure the Physical path is pointing to the same location you unzipped the
application files (typically c:\inetpub\wwwroot).
9. Note the Application Pool name and close the dialog.
10. Click on Application Pools in the tree on the left, right click the name of the
application pool noted in the last step and ensure that the .NET Framework
version is v.2.0.x:
8 / 18
Proxy & Firewall Configuration (Optional)
If you wish to use the automatic error reporting and update checking functionality
available in the FMCS, ensure that the IIS_IUSRS group on the IIS Server and all
FMCS-user client PCs, have access to https://manage.fmcs.com.au/ in order to use
the automatic error reporting and update services. If this URL is inaccessible, these
functions will not work.
9 / 18
DATABASE INSTALLATION
Before you begin
The FMCS database runs on Microsoft’s SQL Server platform. SQL Server
administration requires expert knowledge; if you do not have access to the
necessary skillset please contact Torque Software.
Server Requirements

SQL Server 2005 or later

Expect the database to increase in size by approximately 200-500mb per
year (attachments to breaches and applications are the primary source of
database growth)
Installation Requirements

IIS Configuration and application setup complete; site should be accessible
via nominated URL

SQL Server administrative access

Details of initial FMCS administrator

FMCS License (provided by Torque Software)

SMTP Server configuration, including account to be used by the FMCS
10 / 18
Initial System Configuration
Once you have deployed the FMCS application files and configured IIS, access the
site by its URL and you will be presented with the New Instance Setup screen:
Step through the New Instance Setup ensuring you have access to the information
identified in the Installation Requirements above. For help at any time during the
initial setup process, click the Help icon in the top right.
Once all the relevant information has been entered in the New Instance Setup
screen, you are presented with the option of automatically creating the FMCS
database or generating the script required to create it.
Automatic Database Creation
The FMCS has the capability to connect to your SQL Server and create its own
database, ensuring correct implementation without the need to run any scripts
manually.
11 / 18
1.
Select the Authentication Mode to connect to the SQL Server – the
nominated security context (integrated or the SQL user) must be a member
of the sysadmin role on the server.
2. Click Create Database, the FMCS will run the appropriate scripts and notify
you of the outcome.
Note: no security information is retained from this step – it is
only used to create the database at this time.
Manual Database Creation
1.
To generate the script required to create and configure the FMCS database,
change to the Manual tab:
2. Click Generate Script and you will be presented with a screen containing the
script:
3. Copy and run the script on your SQL Server then click the link to restart the
system and log in.
Note: the FMCS is now operational.
12 / 18
POST-IMPLEMENTATION CONFIGURATION
Scheduled Task
Server Requirements

Any server (can be the same as the IIS server) from which to run the
scheduled task

Configuring user must have administrative access to server
Installation Requirements

The FMCS must be pre-configured and running correctly
Scheduled Task Configuration
In order to ensure that the FMCS runs its maintenance tasks, such as emailing out
the periodic breach reports to your defined schedule and sending survey
reminders, a Windows Scheduled Task must be set up to access the following URL
at least once an hour: http://<FMCS_URL>/RunMaintenance.aspx
Branch & User Update via Spread Sheet (Optional)
1.
Login to the FMCS as an FMCS administrator
2. Go to Settings  Upload Settings
3. Configure your upload settings (for more information, click the help icon in
the top right at any time)
4. Click Save
Note: The spread sheet upload requires a very specific file
format which cannot be deviated from. For more information
see Online Help within the Upload Settings screen.
Branch & User Update via Web Services (Optional)
The web services are SOAP-based, and allow updating of the organisation structure
and system users within the FMCS. Updates can be performed at any frequency,
however overnight is recommended.
13 / 18
To enable the web service functionality within the FMCS, please ensure that the
Windows Communication Foundation Activation Components subcomponent of
the .NET Framework is installed on the IIS server, managed via Control Panel 
Programs and Features  Add/Remove Windows Components.
For more information on integrating with the FMCS web services, open the FMCS
via its URL then navigate to /help/WebService.aspx. The online help has
comprehensive support for the URL for your service, its WSDL, and code examples.
14 / 18
SYSTEM UPDATES
Updates are available to Administrators within the FMCS by going to Settings 
Check for Updates.
The FMCS will report available updates to administrators only at the bottom of
each screen:
Clicking the link in the overlay will log you in to the Management Portal and
provide you with the instructions on how to update.
Note: when Check for Updates Automatically is turned on in
Settings  System Settings the system will check each time the
FMCS application pool is spun up on the IIS Server.
15 / 18
TROUBLESHOOTING
Following are examples of problems encountered and their suggested solutions.
System Responsiveness
IIS’s default behaviour is to “put sites to sleep” after a specified idle period (typically
30 minutes). After this time, the next user to hit the site will cause the application
to be loaded into memory and cached, resulting in a sometimes-significant lag
while loading depending on the capabilities of the IIS server.
If you wish to avoid this behaviour, the suggested approach is to change the
application pool timeout duration to a period longer than your business hours, and
set up a scheduled task to “ping” the website just prior to the start of the work day
to “wake up” the FMCS.
Note: Microsoft and Torque Software do not recommend
disabling application pool timeouts – we strongly recommend
allowing the application pool to recycle at least once a day.
Required permissions cannot be acquired
If you see this message after installation and configuration of the FMCS, see
http://stackoverflow.com/questions/1846816/iis7-failed-to-grant-minimumpermission-requests for a possible solution.
16 / 18
Users are able to see data/info from another user’s session
This problem can present itself as a user being able to see data they are not
entitled to (such as the “known breaches” for a survey question), and can occur
when IIS7+ kernel caching is turned on. As a general rule, we recommend kernel
caching be switched off for the FMCS.
1.
Run Internet Information Services (IIS) Manager under Control Panel 
Administrative Tools
2. Select the FMCS site instance.
3. In the Feature View, double-click “Output Caching”.
4. If there is a rule there already for the .aspx extension double click it.
Otherwise right click and select “Add…” and enter .aspx for the “File name
extension”.
5. Check “User-mode caching”
6. Select “Prevent all caching”
7. Check “Kernel-mode caching”
8. Select “Prevent all caching”
9. Click OK
10. Close the Console
17 / 18
We comprise a team of highly skilled and experienced consultants focusing on high quality
customised software development. All of our team are senior consultants, and we have all
worked together for many years, so we can bring you expertise and synergy.
To learn more about Torque Software, contact us on 1300 795 581 or visit
www.torquesoftware.com.au.
© 2014 Torque Software, All Rights Reserved.
Download PDF
Similar pages