Dossier. Version 6.2 IT Planning Manual ARSENAULT. Associates. Fleet Asset Maintenance Management Software. Since

Similar documents
IT Planning Manual. Fleet Maintenance Software. Version 6.4

IT Planning Manual. Fleet Maintenance Software. Version 6.6

Installation Manual. Fleet Maintenance Software. Version 6.4

Contents. Microsoft is a registered trademark of Microsoft Corporation. TRAVERSE is a registered trademark of Open Systems Holdings Corp.

B2W Software Resource Requirements & Recommendations

Independent DeltaV Domain Controller

HySecure Quick Start Guide. HySecure 5.0

WHITE PAPER: BEST PRACTICES. Sizing and Scalability Recommendations for Symantec Endpoint Protection. Symantec Enterprise Security Solutions Group

Deploy. Your step-by-step guide to successfully deploy an app with FileMaker Platform

Xytech MediaPulse Equipment Guidelines (Version 8 and Sky)

Privileged Identity App Launcher and Session Recording

imaint/imaint Fleet 3.5 System Requirements

PCI DSS Compliance. White Paper Parallels Remote Application Server

WHITE PAPER Cloud FastPath: A Highly Secure Data Transfer Solution

Sage 300 People & Web Self Service Technical Information & System Requirements

ACT! by Sage Corporate Edition 2010 System Requirements

Hardware and Software Requirements

TECHNICAL WHITE PAPER AUGUST 2017 REVIEWER S GUIDE FOR VIEW IN VMWARE HORIZON 7: INSTALLATION AND CONFIGURATION. VMware Horizon 7 version 7.

App Orchestration 2.0

Microsoft Dynamics AX 2012 Installation Guide

ROYAL INSTITUTE OF INFORMATION & MANAGEMENT

Deployment and User Guide Installing and Configuring WhatsUp Gold Failover Manager

Veeam Cloud Connect. Version 8.0. Administrator Guide

Copyright ATRIL Language Engineering, S.L. All rights reserved.

Xytech MediaPulse Equipment Guidelines (Version 8 and Sky)

About the XenClient Enterprise Solution

Deploy. A step-by-step guide to successfully deploying your new app with the FileMaker Platform

XenApp 5 Security Standards and Deployment Scenarios

IBM BigFix Lifecycle 9.5

McAfee Network Security Platform

Sage ACT! PRO 2011 System Requirements

Cloud FastPath: Highly Secure Data Transfer

CRA Wiz and Fair Lending Wiz. Installation Guide V6.9

Server Software Installation Guide

Microsoft TS: Windows Server 2008 Applications Infrastructure, Configuration

Course 20416B: Implementing Desktop Application Environments Page 1 of 7

Syncplicity Panorama with Isilon Storage. Technote

Enterprise Planning Large Scale

CIS Controls Measures and Metrics for Version 7

Patch Manager INSTALLATION GUIDE. Version Last Updated: September 25, 2017

Pre-installation Guide. Collect v1.0 Technical Installation Guide

Enterprise Planning Large Scale

SuccessMaker. System Requirements SuccessMaker v1.0

20416B: Implementing Desktop Application Environments

HP ProCurve Manager Plus 3.0

Ivanti Service Desk and Asset Manager Technical Specifications and Architecture Guidelines

BlackBerry Enterprise Server for Microsoft Exchange

Migrating from Citrix XenApp (IMA / FMA) to Parallels Remote Application Server

Proficy* Workflow. Powered by Proficy SOA GETTING STARTED

Seagate Info Architecture Planning and Deployment for ASPs

Citrix administator guide

System Requirements and Implementation Options

Cisco Network Admission Control (NAC) Solution

Document Sub Title. Yotpo. Technical Overview 07/18/ Yotpo

Centrix WorkSpace IQ Installation Guide. Version 4.5

SolarWinds. Patch Manager. Evaluation Guide. Version 2.1.2

Surveyor 6 Product Guide

INSTALLATION AND SET UP GUIDE

Diagnostic Manager Advanced Installation Guide

Designing Windows Server 2008 Network and Applications Infrastructure

InventoryControl Quick Start Guide

Venafi Platform. Architecture 1 Architecture Basic. Professional Services Venafi. All Rights Reserved.

CIS Controls Measures and Metrics for Version 7

Copyright 2009 by Scholastic Inc. All rights reserved. Published by Scholastic Inc. PDF0090 (PDF)

Technical Overview. Access control lists define the users, groups, and roles that can access content as well as the operations that can be performed.

Scaling for the Enterprise

Enhancing VMware Horizon View with F5 Solutions

System Requirements. SuccessMaker 3

Parallels Remote Application Server

Sage 300 ERP. Compatibility Guide Version Revised: Oct 1, Version 6.0 Compatibility Guide i

Fundamentals of Windows Server 2008 Network and Applications Infrastructure

ProSystem fx Engagement

Desktop Deployment Guide

Ensure that the server where you install the Primary Server software meets the following requirements: Item Requirements Additional Details

Lasso CDP. Lasso. Administration Tool Guide. August 2005, Version Lasso CDP Administration Tool Guide Page 1 of All Rights Reserved.

Quest Collaboration Services 3.6. Installation Guide

INSTALLATION AND SET UP GUIDE

ClearPath OS 2200 System LAN Security Overview. White paper

BMC Remedyforce Discovery and Client Management. Frequently asked questions

Administering System Center Configuration Manager ( A)

Intel Small Business Extended Access. Deployment Guide

McAfee Network Security Platform 9.1

System Requirements Overview

Server Installation ZENworks Mobile Management 2.6.x January 2013

Networks with Cisco NAC Appliance primarily benefit from:

The power of centralized computing at your fingertips

Xerox. Print Advisor Frequently Asked Questions. General

Administering System Center Configuration Manager

Inmagic Content Server v9 Workgroup Configuration Technical Guidelines

QuickSpecs HP ProCurve Manager Plus 3.1

SuccessMaker Learning Management System System Requirements v1.0


Features. HDX WAN optimization. QoS

Enterprise Services for NFuse (ESN) February 12, 2002

Administering System Center Configuration Manager

ADMINISTERING SYSTEM CENTER CONFIGURATION MANAGER

XLmanage Version 2.4. Installation Guide. ClearCube Technology, Inc.

Sage 200c Professional. System Requirements and Prerequisites

Sage 200c Professional. System Requirements and Prerequisites

VMware AirWatch Recommended Architecture Guide Setting up and managing your on-premises AirWatch deployment

Transcription:

Dossier Fleet Asset Maintenance Management Software Version 6.2 IT Planning Manual ARSENAULT Associates Since 1979 www.arsenault.com

Fleet Maintenance Software Dossier IT Planning Manual Version 6.2 By ARSENAULT Associates 6 Terri Lane, Suite 700 Burlington, NJ 08016 (609) 747-8800 Fax (609) 747-8801 Dossier@arsenault.com www.arsenault.com

Copyright 1986-2012 Arsenault Associates - All Rights Reserved Microsoft, Windows, and Excel are registered trademarks of Microsoft Corporation in the United States and/or other countries. Intel and Pentium are trademarks of Intel Corporation in the U.S. and other countries. Avery is a trademark of Avery Dennison Corporation. Networkfleet is a registered trademark of Networkfleet, Inc. NAPA is a trademark of the National Automotive Parts Association. The GMC trademark and design are registered trademarks of GMC. All other registered and unregistered trademarks are the property of their respective owners.

Contents Introduction 1 Dossier Software Components 1 Dossier Client Software (Required) 1 Pocket Dossier (Optional) 1 Dossier Data Exchange (Optional - Includes Network Fleet and NAPA) 2 Database Server (Required) 2 Reporting Server (Required) 2 Remote Desktop/Terminal Services (Optional) 3 Internet Information Services (Optional) 3 Active Directory (Optional) 3 Email Server 3 Firewalls 4 Dossier Network Architecture 5 Individual User (or Several Users Sharing a Computer) 5 Small Workgroup 5 Small- to Mid-Sized Workgroup 5 Large Workgroup 5 Corporation 5 Dossier Client Software 6 Hardware Requirements 6 Security Considerations 6 Database Server - SQL Server 7 Versions/Editions Supported 7 Hardware Requirements 7 Microsoft SQL Server Licensing Requirements 8 Database Maintenance 8 Disaster Recovery 8 Security Considerations 8 Firewall Requirements 9 SQL Server Reporting Services 9 Versions/Editions Supported 9 Hardware Requirements 10 Dossier IT Planning Manual iii

Microsoft Licensing Requirements (Server and User) 10 Security Considerations 10 Firewall Requirements 11 Dossier Data Exchange (API), Networkfleet and NAPA Integration 11 Local Access vs. Web Service 11 Internet Information Services (IIS) 11 Hardware Requirements 11 Security Considerations 12 Firewall Requirements 12 Pocket Dossier 12 Pocket Dossier Server Hardware Requirements 12 Security Considerations 13 Firewall Requirements 13 Pocket Dossier Desktop Computer 13 Wireless Networking 13 Appendix 14 System Requirements 14 Desktop System Requirements 14 Server, Network, and Router Requirements 15 iv Contents

Introduction The Dossier Fleet Management software has been designed to support a wide diversity of use cases, from the single user running on one computer with limited fleet assets to hundreds of concurrent users and tens of thousands of fleet assets. To support this diverse set of operating requirements, Dossier is designed to be very scalable. Properly planning your computing infrastructure will directly impact your successful utilization of Dossier. Dossier utilizes many different technologies. This manual is not designed as a training document for the various underlying technologies. Its goal is to help you decide how to best utilize these technologies as they apply to Dossier and your use case. Dossier Software Components Prior to a discussion of the various infrastructures Dossier supports, it is necessary to understand the components of Dossier and the underlying technologies they utilize. It is important to remember that while there are a number of supported components and technologies, all of them can be run on a single computer for smaller installations. Dossier Client Software (Required) Dossier requires user interface and logic components that constitute the Dossier Fleet Management Software client application. This application generally runs on the users desktop computers and is the primary interface between users and the application. Although it is comprised of several different components, this is generally what users perceive as Dossier. Pocket Dossier (Optional) Pocket Dossier is an optional component of the Dossier software that runs on a Windows Mobile compatible Personal Data Assistant (PDA). It provides licensed users of the Dossier Fleet Maintenance Software with the ability to operate portions of the software remotely over a wireless network. Pocket Dossier delivers increased productivity by way of immediate access to important fleet information and the ability to perform mobile data entry and lookup. Dossier IT Planning Manual 1

Pocket Dossier is a subset of the full-featured edition of Dossier and it does not contain all of the functionality provided in the full desktop version. It is meant as a mobile tool to help in the general management of the fleet and to perform primary data entry functions to keep your program current in real time. Dossier Data Exchange (Optional - Includes Network Fleet and NAPA) The Dossier Data Exchange component [also referred to as the Dossier Application Programming Interface (API)] is an optional component to Dossier that allows access to Dossier logic and data from external software applications. There are three main components of the Dossier Data Exchange interface: A software component that allows direct access to Dossier logic and data A scheduling component that executes registered applications on a schedule A web service that allows access to Dossier logic and data from another computer, both inside and optionally outside of your company. Database Server (Required) Dossier maintains a significant quantity of information about your fleet assets, their maintenance schedules, warranties, etc. Dossier utilizes Microsoft SQL Server to effectively store and access this information. Microsoft SQL Server is an enterprise class database server that is utilized in thousands of data centers around the globe. Microsoft SQL Server is available in several editions designed to meet your computing requirements and budget. There is an Express Edition designed to support small to midsized installations with minimal database management requirements; a Web Edition designed to support web servers, a Workgroup Edition designed to support mid-sized workgroups, a Standard Edition which can support hundreds of concurrent users; an Enterprise Edition Designed to support up to thousands of users; and Datacenter Editions that can effectively support thousands of concurrent users. Dossier supports each of these Editions except Web Edition and includes and ships with the current version of SQL Server Express Edition. Please refer to the "Appendix" on page 14 to identify the version currently being delivered. Reporting Server (Required) Dossier delivers numerous reports supporting thousands of users reporting on thousands of units, repair orders, etc. To effectively deliver this functionality, Dossier uses Microsoft SQL Server Reporting Services. Microsoft SQL Server Reporting Services is a component of Microsoft SQL Server and, therefore, supports the same editions as SQL Server. As with SQL Server, Dossier supports the various editions of Reporting Services with the exception of Web Edition. Dossier ships with the Express Edition of Microsoft SQL Server Reporting Services. Please refer to the "Appendix" on page 14 to identify the version currently being delivered. 2

Remote Desktop/Terminal Services (Optional) Depending on your existing IT infrastructure and needs, larger installations of Dossier can benefit from the use of terminal servers. A terminal server farm can reduce the overhead of deploying and maintaining the Dossier client on your desktop computers. For customers with several hundred users, this can offer an appreciable benefit and savings. Dossier supports running in the full desktop modes of Microsoft Terminal Services, Microsoft Remote Desktop Services (not RemoteApp), and Citrix XenApp (Hosted Apps - Web or Desktop). Internet Information Services (Optional) Pocket Dossier and certain features of the Dossier Data Exchange (API) require the use of Microsoft Internet Information Services (IIS). The IIS version that comes with the supported Microsoft operating system that you are running is supported for use with Dossier. For a list of supported operating systems, please refer to the "Appendix" on page 14. Active Directory (Optional) Depending on your security requirements, Dossier supports two different access methods to the Microsoft SQL Server database: SQL Server Authentication and Windows Authentication (formerly Integrated Security). If you opt to use Windows Authentication for access to your Microsoft SQL Server Database, you will use Microsoft Windows Server Active Directory to define your users and groups and their access to the Dossier database. This security model is supported only in networks that employ Active Directory. Please note that this is different than the Dossier user name and password. Dossier maintains its own internal security separate from that provided by Microsoft Windows. Email Server Certain reporting features in Dossier require configuration of an accessible SMTP email server to function. Editions of Microsoft SQL Server Reporting Services other than Express require configuration of an SMTP email server to deliver scheduled reports via email. Additionally, emailing ad-hoc reports from within Dossier also requires that an email server is configured within Dossier options. If user authentication is required by the SMTP server, Dossier and Microsoft SQL Server Reporting Services must be configured to use a security account with sufficient rights to send email using the specified SMTP server. For further Dossier configuration information, refer to the Dossier Planning and Configuration Manual. For further configuration information about Microsoft SQL Server Reporting Services, refer to Microsoft documentation or contact your SQL Server administrator. Dossier IT Planning Manual 3

Firewalls Although not directly used by Dossier, the use of firewall software can impact your Dossier installation. Microsoft SQL Server, Microsoft SQL Server Reporting Services, Terminal Services, and Internet Information Services all have their own requirements related to firewalls and making certain ports available. Please refer to the documentation for each of the servers mentioned for specific information. 4

Dossier Network Architecture In the case of the single user, all of the components of Dossier can run on a single computer. However, most installations will have a least a few users who will need shared access to the Dossier database. This is accomplished by running Dossier over a network infrastructure. Individual User (or Several Users Sharing a Computer) The Dossier client, database server, and reporting server all run on a single computer. No network connections or servers are required. However, as your need for access to your fleet information increases, different network configurations can be utilized to scale the application along with those needs. Small Workgroup The Dossier client, database server, and reporting server all run on a single computer. Additional desktop computers in the network run the Dossier client and connect to the first computer for access to the database server and report server. Although this configuration is supported, it is not recommended. If the computer running the database server and report server crashes or is rebooted, connection issues and possible data loss can result. Small- to Mid-Sized Workgroup The database server and reporting server run on a single server computer. Desktop computers in the network run the Dossier client and connect to the server for access to the database server and report server. Large Workgroup The database server and reporting server each run on their own server computer. Desktop computers in the network run the Dossier client and connect to both the database report servers. Corporation The Dossier transaction database runs on a single server. A copy(ies) of the transaction database runs on additional database servers for reporting use. SQL Server replication is utilized to synchronize the transaction and reporting database(s). Multiple Report servers are utilized. Ad-hoc and custom reports run from one report server. Microsoft Remote Desktop Services is used for the Dossier client and users utilize Remote Desktop Connection to access the Dossier client. Dossier IT Planning Manual 5

Dossier Client Software Hardware Requirements Dossier client software hardware requirements vary depending on the network architecture employed (refer to "Dossier Network Architecture" on page 5). The requirements for running the Dossier client in the simplest configuration are greater than that of the other network configurations due to the fact that Dossier will be running on a computer alongside the database server and report server components. Please refer to the "Appendix" on page 14 for the minimum and recommended requirements. While the software will run with the defined minimum requirements, it is strongly recommended that a computer meeting the recommended requirements be used. When running the Dossier client software in other configurations, the desktop computer running the Dossier client requires a less capable hardware platform. Using a system that meets the minimum system requirements should suffice for a baseline desktop configuration. These recommendations are based on a computer running the minimum required operating system. The recommendation should be scaled up along with the operating system for later releases of Microsoft Windows. Dossier supports running within Microsoft Remote Desktop Services (formerly Terminal Server). Remote Desktop Services server hardware requirements differ from that of a standard desktop as multiple users can be connected and running Dossier simultaneously. Please refer to Microsoft s recommendations for Remote Desktop Services servers and for the desktops connecting to Remote Desktop Services servers. Dossier also supports Citrix XenApp. If you plan to operate Dossier within XenApp, please refer to the XenApp documentation for requirements and recommendations or contact Citrix. Security Considerations Dossier can be used to track information that can be considered sensitive, such as employee data, etc. Additionally, the data stored in Dossier can represent a significant amount of man hours to create. As such, planning security for the computer(s) on which Dossier runs is an important planning step and warrants thoughtful consideration. Dossier has its own integrated security model. Please refer to the Dossier Planning and Configuration Manual for further information. Microsoft Windows employs several features that allow you to enhance the security of the computers running Dossier. Windows screen savers should be set to initiate after a period of inactivity and to require a password upon waking up. Safeguard the Windows and Dossier credentials used for computer access, especially those accounts with administrative rights. 6

Furthermore, ensure that the computer on which the Dossier database and software is stored is secure from network intrusion. Run a commercial firewall on any computers directly connected to the Internet. In addition to software and network security, you should consider the physical security of the computer. Provide a location that is secured from users who should not have access to the information stored within Dossier. It should be a location that is free from excessive dirt, dust, vibration, etc. Database Server - SQL Server Versions/Editions Supported Microsoft SQL Server ships in several editions designed to support various levels of scalability. It is important to note that Dossier is not tested against and does not support all SQL Server editions. For a list of the versions and editions supported for the current Dossier version, please refer to the "Appendix" on page 14. Dossier ships with and can install Microsoft SQL Server Express Edition. This edition is generally sufficient for individual users and small workgroups. However, this can vary depending on your use case. If you have a large number of units and/or activity on your units, a more capable version might be required even for a relatively small set of connected users. Hardware Requirements The specific hardware requirements for SQL Server vary dramatically based on the edition of SQL Server that you are using, the number of concurrent users, and the size and composition of your Dossier database. Microsoft publishes minimum and recommended hardware and software requirements, which are available on their website at http://www.microsoft.com/sqlserver. We recommend starting your hardware configuration with the recommended configuration for your SQL Server edition as a baseline and then scaling up as required. When planning your database server hardware configuration, there are several factors to consider. Microsoft SQL Server Reporting Services requires its own separate database to function. Its hardware requirements vary dramatically depending on your reporting needs. This can impact your hardware needs if your organization requires significant use of adhoc and/or scheduled reports. Dossier can be configured to use a single database for both transactional data and reporting, or it can be configured to use one or more separate databases for reporting (on most reports). Although it supports running disparate transactional and reporting databases, Dossier does not manage the process of keeping the data synchronized. SQL Server Replication is a function of SQL Server used to manage replicating databases and can effectively maintain a near real-time copy of your transactional data for reporting purposes. Other database replication software can also be utilized as long as it supports Microsoft SQL Server. In any case, if you intend to separate transactional and reporting database activity, you should also plan for the overhead that replication adds. Dossier IT Planning Manual 7

Microsoft SQL Server Licensing Requirements Each edition of Microsoft SQL Server except Express Edition imposes licensing requirements for the server running SQL Server and potentially each user connected to that server. The software license for Dossier does not include any licenses or fees for any edition of Microsoft SQL Server. Please contact Microsoft for questions concerning SQL Server licensing. Database Maintenance All database server programs require some amount of database maintenance to continue to run optimally. SQL Server is no exception. A maintenance plan should be developed, executed, and monitored to ensure that these activities are performed on a routine basis. For further information, please refer to Microsoft SQL Server documentation. Disaster Recovery It is extremely important to employ a backup plan for Dossier. Your options and plan for backing up your Dossier database will vary depending on the version of SQL Server deployed, your usage characteristics, and how much time and effort you are willing to risk. A backup plan requires time, effort, and an investment in hardware. As you increase the backup frequency, reliability, and level of protection, you increase those investments. You should balance the cost of losing the information you store in Dossier against the investment in backup solutions. At a minimum you should manually perform a backup of Dossier once a week to external computer media (such as a USB drive or external hard disk), and keep a copy off-site. For further information regarding SQL Server database backups, please refer to the Dossier Installation Manual and to Microsoft s documentation and website (www.microsoft.com/sqlserver). Security Considerations During installation, Dossier creates a user account, d32admin, and a SQL Role, Dossier, with which to control security. Dossier then uses d32admin to connect to SQL Server and perform all of its operations. Since Dossier depends solely on this account to perform all of its functions, the account is fairly privileged within the Dossier database (but not SQL Server or the computer it is running on). 8

Dossier s default configuration is generally sufficient for most customers. However, if your organization requires a greater level of security, Dossier also fully supports the Windows Authentication SQL Server security mechanism (formerly called Integrated Security). Windows Authentication allows you to specify database permissions based on the user logged into Windows on the machine where Dossier is running. Using this model of security, it is typical practice to utilize user groups to administer permissions and assign individual users to the appropriate user group. For further information regarding SQL Server security, please refer to the Microsoft SQL Server documentation and website (www.microsoft.com/sqlserver). Firewall Requirements In its default configuration, Microsoft SQL Server requires TCP port 1433 to communicate. Although it is not recommended to run, SQL Server browser requires UDP Port 1434. Please refer to Microsoft knowledge base article 287932 and the MSDN article at http://msdn.microsoft.com/en-us/library/ms175043(v=sql.100).aspx for further information on SQL Server and firewall requirements. SQL Server Reporting Services Dossier uses at least one Microsoft SQL Server Reporting Services instance to provide reporting capabilities within Dossier. The Dossier Installer can setup and configure a SQL Server Reporting Services instance running alongside Dossier and SQL Server. This installation is sufficient for small customers with a relatively low amount of usage. Midsize and large customers as well as small customers with heavy Dossier usage should consider installing SQL Reporting Services on a separate server. For all but the largest customers, a server housing both SQL Server and SQL Server Reporting Services should suffice as long as the hardware is scaled sufficiently to accommodate both. However, customers with a large number of users or heavy Dossier utilization should consider running at least one separate server for SQL Server Reporting Services. Although scheduled and user-defined reports must run from a common server, Dossier supports an unlimited number of ad-hoc report servers. Versions/Editions Supported As part of the Microsoft SQL Server product offering, Microsoft SQL Server Reporting Services (SSRS) is included in and scales with the various editions as SQL Server. As with SQL Server, Dossier is not tested against and does not support all SQL Server Reporting Services editions. For a list of the versions and editions supported for the current Dossier version, please refer to the "Appendix" on page 14. Dossier ships with and can install Microsoft SQL Server Express Edition, Advanced Services, which includes the Express edition of SSRS. Dossier IT Planning Manual 9

Hardware Requirements The specific hardware requirements for SQL Server Reporting Services vary depending on the edition of SQL Server that you have licensed and your reporting usage. Microsoft publishes minimum and recommended hardware and software requirements, which are available on their website at http://www.microsoft.com/sqlserver. We recommend sizing your hardware with the recommended configuration for your SQL Server edition as a baseline and sizing up as required. Microsoft Licensing Requirements (Server and User) Although it ships as a component of Microsoft SQL Server product, a single license for SQL Server allows you to run SQL Server and SSRS on a single machine only. If your plans include running SSRS on an isolated server, a separate license will be required to do so. The software license for Dossier does not include any licenses or fees for any edition of Microsoft SQL Server, including SQL Server Reporting Services. Please contact Microsoft for questions concerning SQL Server licensing. Security Considerations By default, the Dossier server installation option creates a Windows user during the install process with a random password on the machine that is running Reporting Services. This is a privileged user in Reporting Services, with access to create, delete, run, and administer running reports. However, it is an underprivileged user account in Windows. Dossier also supports running using Trusted security. With Trusted security, the user account used to run reports is the user account with which the Dossier user is logged onto Windows. Utilizing this security model can provide a more secure operating environment at the cost of simplicity. You can manage Reporting Services security at a user level. However, in this configuration it is more common to employ user groups to manage Reporting Services security and assign users to those groups as required. Depending on your organization s security requirements, you might want to enforce security in this manner. With additional licensing, Dossier also supports creating and importing user-defined reports. It is possible to use user-defined reports for malicious purposes or to circumvent Dossier security. You should consider limiting the ability to author and inventory userdefined reports to a select group of trusted users. Never inventory or run a custom report that is from an unknown or untrusted source. 10

Firewall Requirements SQL Server Reporting Services utilizes an HTML web service/site to deliver reports to end user desktops. Any firewall software should allow both HTTP (TCP port 80) and HTTPS (TCP Port 443) traffic. Additionally, SQL Server installations on Windows XP or Windows Server 2003 are configured, by default, to use TCP port 8080 instead of port 80 for HTTP communication. Dossier Data Exchange (API), Networkfleet and NAPA Integration Local Access vs. Web Service The Dossier Data Exchange component runs in two methods: as a software component that can be directly referenced by other software installed on the same computer (API) or as a web service (Web API), allowing access to Dossier information from other computers (inside or outside your company s network). Internet Information Services (IIS) Installing the web service component of Dossier Data Exchange requires that Internet Information Services (IIS) be installed on the installation computer prior running install. IIS versions from each of the supported operating systems are supported by Dossier. Hardware Requirements A computer meeting the minimum requirements specified in the "Appendix" on page 14should be sufficient to run Dossier Data Exchange API. When installing the Dossier Data Exchange Web API, please refer to Microsoft s documentation on the operating system on which you are installing the API for the hardware requirements for IIS. Although it is possible to run Dossier Data Exchange on the same computer that on which Dossier is running, this is not recommended. Dossier Data Exchange conduits might have scheduling and availability needs that a user s workstation might not be able to reliably fulfill. Dossier Data Exchange allows execution of third-party applications (conduits) against Dossier data. If installed alongside Dossier Data Exchange, these third-party applications might have additional hardware requirements. Please refer to the software manufacturer s documentation. Dossier IT Planning Manual 11

Pocket Dossier Security Considerations At a minimum, any computer running Dossier Data Exchange should practice the same security protocols defined for the Dossier client software (refer to "Security Considerations" on page 6. There are additional concerns if you are running the Dossier Data Exchange Web API. The Web API functions similar to a web site except that it can expose Dossier data to computers outside those with Dossier components installed. In addition, unless additional measures are employed, the data sent to and from the web service is not encrypted and could be intercepted by a third party. Generally, if you are potentially exposing this web service outside your corporation, you should follow Microsoft s recommendations for securing IIS and web services in general. This includes obtaining an SSL certificate and employing HTTPS, as well as utilizing web authentication other than anonymous in your IIS configuration. Please refer to the Microsoft documentation for your operating system for further information. Firewall Requirements The Dossier Data Exchange Web API utilizes an HTML Web Service to deliver reports to end user desktops. Any firewall software should allow both HTTP (TCP port 80) and HTTPS (TCP Port 443) traffic. Unless the Web API is installed, there should be no firewall needs for Dossier Data Exchange. Pocket Dossier Server Hardware Requirements Pocket Dossier requires a server to operate. This is the computer with which the handheld units will communicate to interface with the Dossier data. Pocket Dossier employs the use of a web service and requires a version of Internet Information Services (IIS) to be installed. Please refer to the "Appendix" on page 14 for a list of supported operating systems. Refer to Microsoft s documentation for the operating system on which you are installing the Pocket Dossier server for IIS hardware requirements. IIS is not installed by the default installation of Microsoft operating systems. Please refer to Microsoft s documentation for information on installing IIS. The Pocket Dossier server also requires the installation of Microsoft.NET Framework 3.5 prior to Pocket Dossier installation. Again, please refer to Microsoft s documentation for information on installing this component. 12

Security Considerations If you will be using Pocket Dossier over an Internet connection using a PDA cell phone, the HTTP protocol must be enabled between the Internet and the Pocket Dossier Service on the web server. Also, the service must be accessible from the Internet (i.e., your network must be configured such that packets from the cell phone can reach the Pocket Dossier Service). As with any application that requires opening a port to the Internet, appropriate security measures should be taken into consideration with your IT Department to prevent vulnerabilities within your internal network. Firewall Requirements Pocket Dossier server utilizes an HTML web service to deliver data to handheld devices. Any firewall software should allow both HTTP (TCP port 80) and HTTPS (TCP Port 443) traffic. Pocket Dossier Desktop Computer The Pocket Dossier application provides a scaled-down version of the full Dossier application designed to run on certain mobile devices. It is most useful in environments where desktop computer equipment is not practical. Your handheld device will require a desktop computer with Microsoft ActiveSync installed to install software updates. Please refer to the documentation for the Pocket device for desktop computer hardware and software requirements. Wireless Networking Pocket Dossier devices require a wireless network to communicate with the Pocket Dossier server. You will need to have a reliable wireless network available at the location you plan to use the mobile devices. The supported network protocols supported vary depending on the model of Pocket Dossier mobile device used. Please refer to the documentation for the mobile device for information on the protocols supported as well as instructions for connecting to the wireless network. NOTE: If you require assistance setting up the wireless access network, please Dossier Technical Support at 800-525-5256, ext. 6 or at support@arsenault.com. Our support staff will be happy to connect you with our wireless network provider for a complete analysis of your wireless needs. Dossier IT Planning Manual 13

Appendix System Requirements Dossier will operate on a stand-alone PC or over a network with multiple users. It can also be run in an application server environment using Citrix or Microsoft Terminal Services. The following are general requirements. More detailed specifications can be developed based on your specific needs (functionality, optional features, fleet size, network topology, number of users, etc.). Operating Systems and SQL Database should use the latest Service Pack level available from Microsoft. Desktop System Requirements Minimum Recommended CPT Intel Pentium 4 or equivalent Intel Core i5 or equivalent Operating System Windows XP Professional (32 bit) Windows Vista (32 bit) Windows 7 Professional (32 bit) Windows 7 Professional (64 bit) Windows Server 2003 R2 (32 bit) Windows Server 2008 (32 bit) Windows Server 2008 (64 bit) Windows Server 2008 R2 (64 bit) Windows 7 Professional (64 bit) Windows Server 2008 R2 (64 bit) RAM Memory 1 GB 4 GB Disk Memory 5 GB Free Space 6 GB Free Space Video 1024 x 768 1280 x 1024 Optical Drive Network DVD-ROM Required if connecting to server 100 Mbps 1 Gbps Database Microsoft SQL Server 2008 Express Microsoft SQL Server 2008 Standard** Microsoft SQL Server 2008 R2 Express* Microsoft SQL Server 2008 R2 Standard** * The Express editions of SQL Server are available free from Microsoft. SQL Server 2008 R2 Express is included on the Dossier install DVD. ** Microsoft SQL Server Standard provides better performance and capacity than SQL Server Express. SQL Server Standard is not provided as part of Dossier and must be supplied by the customer. 14

Server, Network, and Router Requirements As each installation s data server, topology, and network requirements are different, please contact Dossier Technical Support at 800-525-5256, ext. 6 or at support@arsenault.com for network deployment discussions. The only requirement that can be simply stated is that all interconnected Dossier nodes must have communications throughput of 100 Mbps or greater. If this throughput cannot be achieved (typical of WAN installations), Dossier must be deployed using Citrix or MS Terminal Services technologies. Dossier IT Planning Manual 15