Hardware and IT Infrastructure Guide PDF

Hardware and IT Infrastructure Guide
Hardware and IT Infrastructure Guide

TMW Systems, Inc.
20486-64th Avenue, Suite 200
Langley, B.C. V2Y 2V5 Canada
Phone: (800) 663-0626
Web Site: www.tmwsystems.com
Trademarks
TruckMate and the TMW Systems logo are registered trademarks of TMW Systems, Inc. ("TMW"). All
other trademarks or registered trademarks are the property of their respective owners.
Disclaimer
The information provided in this document is provided "as is" without warranty of any kind. TMW
Systems, Inc. disclaims all warranties, either express or implied, including the warranties of
merchantability and fitness for a particular purpose. In no event shall TMW Systems, Inc. or its suppliers
be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business
profits or special damages, even if TMW Systems, Inc. or its suppliers have been advised of the possibility
of such damages. Some states do not allow the exclusion or limitation of liability for consequential or
incidental damages so the foregoing limitation may not apply.
Hardware and IT Guide

TruckMate, Hardware, Requirements
8/6/2015
Copyright TMW Systems, Inc.
Document Lifetime
TMW Systems, Inc. may occasionally update documentation between releases of the related software.
Consequently, if this document was not obtained recently, it may not contain the most up-to-date
information.
Document Version
Version
Amendment
By
Date
1.0
Creation based on 2011 document
Mike Petkau
6/18/2012
2.0
Revamped whole document
Mike Petkau
6/27/2012
2.1
Minor updates
Mike Petkau
8/9/ 2012
2.2
Minor updates
Mike Petkau
12/5/2013
2.3
Minor updates
Mike Petkau
3/26/2013
2.4
More detail on SSDs for DB servers and additional

updates to the DB2 server section
Mike Petkau
5/24/2013
2.5
Added DB2 licensing section as well as additional

minor updates
Mike Petkau
6/12/2013
2.6
Updated DB2 licensing information to reflect new

DB2 contract terms
Mike Petkau
9/9/2013
2.7
Updated DB2 HADR section, Supported O/Ss and

other minor updates
Mike Petkau
10/24/2013
2.8
Added Storage Area Network (SAN) specific section
Mike Petkau
1/3/2014
3.0
Document Template Updated
Randy White
4/16/2014
3.1
Added test server requirement, updated supported

OSs and other minor items
Mike Petkau
7/7/2014
3.2
Added DB2 10.5 as a supported DBMS
Mike Petkau
9/11/2014
3.3
Removed WMS section. Product no longer sold.
Mike Petkau
9/25/2014
3.4
Added TMW ContainerSeek Recommendations and

adjusted other minor items.
Mike Petkau
1/30/2015
3.5
Added support for DB2 10.5 FP5 which results in

Windows 2012 R2 DB2 server support.
Mike Petkau
4/23/2015
3.6
Added requirements for D2Link
Mike Petkau
6/2/2015
3.6
Updated DB2 License & Supported OSs Sections

and Added Crystal Reports Version Support Section
Mike Petkau
8/6/2015
This document outlines general requirements for hardware and operating systems when implementing
TruckMate for Windows. The information in this document is current as of 8/6/2015. Contact a TMW
service representative if you have any hardware questions.
This document (.pdf or .doc) is a proprietary design of TMW Systems Inc., and cannot be distributed or
copied by any person or company other than TMW Systems Inc.

8/6/2015
Contents
Introduction ................................................................................................................ 6
Terminology ................................................................................................................................................................ 6
Performance ......................................................................................................................................................... 6
Availability ........................................................................................................................................................... 6
Data Safety and Security ..................................................................................................................................... 6
Servers ................................................................................................................................................................... 6
Clients ................................................................................................................................................................... 6
Hardware Overview and General System Requirements ............................................ 7

Critical Components of a Computer ........................................................................................................................ 7
Processor / Central Processing Unit (CPU) ..................................................................................................... 8
Memory / Random-Access Memory (RAM) ................................................................................................... 8
Drive Storage ........................................................................................................................................................ 9
Data Safety ................................................................................................................................................................. 11
Redundant Array of Independent Drives (RAID) ........................................................................................ 11
Tape Drives ........................................................................................................................................................ 12
DB2 High Availability Disaster Recovery (HADR) ...................................................................................... 13
Disk Drive Layout & Performance ......................................................................................................................... 14
Storage Area Networks / SANs Performance Requirements ............................................................................ 15
Supported Windows Operating Systems and DB2 Versions .............................................................................. 16
Windows Desktop / Screen Settings ..................................................................................................................... 19
SAP Crystal Reports Version Support ................................................................................................................... 19
DB2 Licensing Requirements .................................................................................................................................. 20
DB2 and Core Limitations by Edition ............................................................................................................. 20
DB2 Licensing Types ......................................................................................................................................... 20
DB2 Licensing Types Available by Edition .................................................................................................... 22
Licensing DB2 Test Servers .............................................................................................................................. 22
Licensing DB2 in a Virtual Environment ....................................................................................................... 22
Licensing DB2 HADR and SQL Replication .................................................................................................. 23
Network / System Landscape ................................................................................................................................ 26
Cables and Switches .......................................................................................................................................... 26
Remote Access (RDP/Citrix) ........................................................................................................................... 26
Virtual Private Networks (VPNs) .................................................................................................................... 26
Network Diagram of typical TruckMate System .......................................................................................... 27
Hardware Recommendations .................................................................................... 29

TruckMate User Devices .......................................................................................................................................... 30
Windows Workstation/Laptop ....................................................................................................................... 30
Citrix / RDP Thin Client Terminals ................................................................................................................ 30
Tablets and Smart Phones ................................................................................................................................ 30
TruckMate Required Servers................................................................................................................................... 31
DB2 Server Requirements ................................................................................................................................. 31
Test/DBI pureFeat Server ................................................................................................................................ 34
Mileage Server ................................................................................................................................................... 34
8/6/2015
Active Directory / Domain Controller ........................................................................................................... 34

Email Server ....................................................................................................................................................... 35
TruckMate Optional Servers ................................................................................................................................... 36
Citrix / RDP Server ........................................................................................................................................... 36
EDI Server ........................................................................................................................................................... 37
Mobile Communications Server ...................................................................................................................... 37
TMW D2Link Servers ........................................................................................................................................ 38
TMW ContainerSeek Server ............................................................................................................................. 39
Consolidating Required and Optional Servers .............................................................................................. 39
Imaging Server ................................................................................................................................................... 39
Shop / Maintenance Server .............................................................................................................................. 40
Optimization (Appian / IDSC) Server ........................................................................................................... 40
Other 3rd Party Servers .................................................................................................................................... 40
Web Server ......................................................................................................................................................... 41
FTP Server........................................................................................................................................................... 42

8/6/2015
Introduction
Customers expect TruckMate to run smoothly and without interruptions. This means that they
are looking for good performance, data loss prevention, and continuous system availability. As
a result, servers, clients, and the network have to be set up and configured accordingly.
Terminology
Performance
In software engineering, performance determines how fast some aspects of a system perform
under a particular workload. It can also define other quality attributes of the system, such as
scalability and reliability. Performance testing is performed to verify performance criteria. It can
serve different purposes: It can demonstrate that the system meets performance criteria and it
can compare two systems to find out which performs better. Finally, it can measure what parts
of the system or workload cause the system to not perform to expectations. In the diagnostic
case, software engineers use tools to measure what parts of a device or software contribute most
to poor performance or to establish throughput levels (and thresholds) for maintained
acceptable response time.
Availability
Availability refers to the ability of the user community to access the system, whether to submit
new work, update or alter existing work, or collect the results of previous work. If a user cannot
access the system, it is said to be unavailable. The term downtime is used to refer to periods
when a system is unavailable.
Data Safety and Security

Data safety as a concept optimizes system safety in the design, development, use, and
maintenance of software systems and their integration with hardware systems in an operational
environment. In recent years, the role of the software and hardware has become the command
and control of complex and costly systems upon which human livelihoods may depend. Data
safety addresses the minimization or even elimination of the risk of data loss and unplanned
data manipulation.
Servers
The most important component of the TruckMate system landscape is the server that hosts the
TruckMate database running on IBMs DB2 enterprise database platform. Other servers are
required depending on size of implementation and add-on modules purchased.
Clients
Client PCs are used by individual users in order to access TruckMate. Client computers need to
take into account similar sizing considerations as servers, but do not have to be as powerful as
servers.

8/6/2015
Hardware Overview and General System Requirements

Nearly all TMW clients have preexisting networks and computers prior to purchasing
TruckMate. As a result, new and current clients hardware is continuously aging and needs to
be reviewed and upgraded periodically. The best time to do this review/upgrade is prior to
installing a new version of TruckMate.
This section is intended to describe important components of computer hardware, how to
configure these technologies and what versions of Windows should be installed on the
hardware.
Critical Components of a Computer

Present-day computers actually use a variety of storage technologies. Each technology is geared
toward a specific function, with speeds and capacities to match.
These technologies are:
CPU
RAM
Hard drives
Off-line backup storage (tape, optical disk, etc.)
In terms of capabilities and cost, these technologies form a spectrum.

For example, CPU registers are:
Very fast (access times of a few nanoseconds)
Low capacity (usually 100's of bytes)
Very limited expansion capabilities (a change in CPU architecture would be required)
Expensive (more than one dollar/byte)
However, at the other end of the spectrum, off-line backup storage is:
Very slow (access times may be measured in days, if the backup media must be shipped)
Very high capacity (can be 1000s of terabytes)
Essentially unlimited expansion capabilities (limited only by space needed to store media)
Very inexpensive (fractional cents/byte)
By using different technologies with different capabilities, it is possible to fine-tune system

design for maximum performance at the lowest possible cost. The following sections explore
each technology in the storage spectrum.

8/6/2015
Processor / Central Processing Unit (CPU)

The processor or CPU is the component of the computer that executes programs. It interprets
program instructions and processes data. The main criterion to describe the power of a
processor is the clock rate, which describes the speed of the processor and is measured by
frequency in hertz.
The second criterion is cache size. There can be multiple levels of cache, currently L1, L2 and L3.
Cache is memory sitting on each core or shared by all cores on a CPU. As a consequence, the
more cache on a CPU the faster it will be. Server CPU caches are normally in the 10s of
megabytes (MB). While a CPU is processing, any data not found in cache will be retrieved from
RAM (which is cheaper and larger).
Tip: TruckMate servers should all be running on multi-core 64-bit CPUs with sufficient L2 cache.
Modern processors are 64-Bit architecture and generally have a frequency of 2 to 4 GHz per
core. Older processors had only one processing core per CPU whereas newer multi-core
processors can combine over 10 cores into a single CPU. Multi-core processors are capable of
processing programs or code in parallel and are therefore significantly faster.
Important: Nearly all modern CPUs have hyper-threading technology. When viewing CPU performance
in Windows Task Manager on the Performance tab, the count of cores will be double the physical core
count. Do not use this count.
If you need to check how many cores your CPUs have, please get the model number and check the
manufactures website for its specifications.
Memory / Random-Access Memory (RAM)

Memory or RAM accesses stored data in any order, that is, at random, without the physical
movement of the storage medium. Using RAM in order to process data is faster than physical
storage mechanisms, such as tape or disks, because no physical movement of the data takes
place. RAM is used as the main memory, that is, the working area for loading, displaying, and
manipulating applications and data. RAM size is measured in bytes. The greater the RAM
amount, the more data that can be processed, which allows for faster computer response times.
Tip: TruckMate servers should all be running high speed memory such as DDR3 or greater.

8/6/2015
Drive Storage
Drives are used for long-term storage of digitally encoded data. Unlike memory, the data is not
lost when the computer is switched off. Drives are defined by capacity and access speed.
Capacity is measured in bytes. Currently, most drives have hundreds to thousands of gigabytes
(GB) of capacity. TruckMate needs drives to store the installation of the application as well as to
store data in the database. Unlike RAM and CPU cache memory, it is not possible to execute
programs directly when they are stored on drives; instead, they must first be read into RAM
then into the CPU.
Also different from cache and RAM is the speed of data storage and retrieval; traditional hard
drives (HDD) are an order of magnitude slower than the all-electronic technologies used for
cache and RAM. The difference in speed is due mainly to their electro-mechanical nature. There
are four distinct phases taking place during each data transfer to or from a hard drive. The
following list illustrates these phases:
Access arm movement
Disk rotation
Heads reading/writing data
Data transfer to/from the drive's electronics
These phases can take several milliseconds and when RAM and CPUs can process data in
nanoseconds its easy to see why HDDs are a bottle-neck to performance.
Traditionally, IBM recommended 10 to 15 hard disk drives per processor core to maximize
performance between the disk subsystem and the processing power of the server. This is why
Solid State Drives (SSDs) are revolutionary to computing performance. You can buy fewer
drives for less money and get more performance.
Access time of SSDs is generally a fraction of millisecond. As such, the time for data to move
from disk to RAM is greatly improved. SSDs can be more than 10 times faster than traditional
HDDs.
Important: TMW requires all database servers to utilize SSDs for data storage in order to maximize
performance and user productivity. Consequently, your return on investment (ROI) of the TruckMate
system will be greatly improved.
The SSDs you chose for the DB2 data array will depend on how many users you have, your
desired performance and budget. First off, NAND memory is used in SSD drives and there are
two types of NAND. SLC stands for Single-Level Cell and MLC stands for Multi-Level Cell.
Without going into many details, the SLC type is considered cream of the crop and as a result
is it has the best performance and the best longevity. As one would expect, these SLC drives are
the most expensive type of SSDs, for good reason. On the other end of the spectrum, MLC
drives are consumer grade SSDs found at your local PC supplier, Best Buy, newegg.com, etc.
These MLC drives are cheap but dont have near as much performance or reliability in a
database environment. With that said, there is a happy medium between SLC and MLC for
smaller and more cost conscious customers.

8/6/2015
This cost conscious drive type is called an E-MLC which stands for Enterprise Multi-Level
Cell. What this means is that there is special firmware and other aspects of the physical NAND
memory chips in the drive which mitigate the limitations of the consumer grade MLC memory
by a significant amount. In fact, Samsung E-MLC drives claim to have 100 times the write
endurance longevity over a standard consumer grade MLC drive of the same size. They even
market this E-MLC drive as a data center solution. The extended longevity combined with the
blazing performance of the NAND memory makes it an ideal cost effective solution for small or
medium sized organizations.
As an example, Dell offers both SAS mainstream SLC drives and SATA value MLC drives
in their servers. These are the two different drive types discussed in the above paragraphs.
Although the value drive is listed as an MLC drive, it is in fact an E-MLC drive. Naturally,
Dell wants to sway customers to buy the better and more expensive drives so this is why they
have chosen to label the products in the manner they have.

10
8/6/2015
Data Safety
Data safety and availability is primarily addressed by data backup strategies that allow for the
duplication of system data, which, in case of loss of primary data, can either immediately
replace data without system downtime, called hot swap, or restore lost data at a later point in
time. Three technologies are commonly used. The first is Redundant Array of Independent
Disks technology (RAID). The second is traditional tape drive backup, where the data is
backed up onto tape drives at regular intervals. The third is data replication to another server
on standby.
Redundant Array of Independent Drives (RAID)

The term Redundant Array of Independent Drives (RAID) is used to describe computer data
storage technology that divides and/or replicates data among multiple hard drives. RAID
technology is often used to provide increased data reliability and/or increased input/output
performance.
A number of standard systems have evolved, which are referred to as levels. Five RAID levels
were initially conceived, but several variations have evolved, notably several nested levels and
many non-standard levels (mostly proprietary).
In a RAID system, physical hard disks are combined into a single logical unit by using special
software or hardware. Software solutions are typically implemented at the operating system
level and present the RAID drive as a single drive to any application. These software based
RAID controllers should not be used. Hardware solutions are also designed to present
themselves to the attached system as a single hard drive, but the operating system is unaware of
the hardware details. The hardware-based RAID controllers are much faster and more reliable.

11
8/6/2015
There are two levels of RAID that should be used with TruckMate, RAID 1 or RAID 10.
RAID 1
RAID 1 creates an exact copy (or mirror) of a set of data on two or more
disks. This is useful for where reliability is more important than data
storage capacity. Such an array can only be as big as the smallest member
disk. A classic RAID 1 mirrored pair contains two disks, which increases
reliability geometrically over a single disk.
Since each member contains a complete copy of the data, and can be
addressed independently, ordinary wear-and-tear reliability is raised by the
power of the number of self-contained copies.
RAID 10
RAID 10 is a nested RAID system created by combining RAID 1 and RAID

0. The combination is known as a stripe of mirrors. In this arrangement,
data is striped much as it is in a RAID 0 array. The difference is that each
member of the striped set has its data mirrored. This ensures that if any
drive in the RAID 10 array fails, the data isn't lost. RAID 10 requires a
minimum of four drives and can be expanded in pairs; you can have a
RAID 10 array with 4, 6, 8, 10, 12 or more drives. RAID 10 should be
composed of equal-size drives.
Due to its architecture, RAID 10 benefits from very fast read and write
performance in comparison to RAID levels that use parity such as RAID 3
or RAID 5.
Warning: Although RAID 5 has achieved popularity due to its low cost of redundancy, it has proven to
be much more error prone then RAID 1 or 10. Consequently, RAID 5 can corrupt data and make it
unusable in the event of one or more drive failures. As a result, it is not recommended to use RAID 5 in
any mission critical data storage situation.
Although RAID 10 is more expensive, it ensures your data is safe while also exhibiting better
performance.
Tape Drives
Tape drives are data storage devices that read and write data stored on a magnetic tape. They
are typically used for storage of archived data saved on hard drives. Compared to hard disks,
tape media generally have a favorable unit cost and long archival stability.
Tape drives only allow for sequential-access of data, instead of allowing random-access as hard
disk drives do, hard disk drives can move their read/write heads to any random part of the
disk platters in a very short amount of time. Tape drives, on the other hand, must spend a
considerable amount of time winding tape between reels to access a particular piece of data. As
a result, tape drives can have a significantly slower seek time, but, despite that, can stream data
to tape very quickly. Modern Linear Tape-Open (LTO) drives can deliver continuous data
transfer rates of up to 140 MB/s, which is comparable to high speed hard disks.

12
8/6/2015
DB2 High Availability Disaster Recovery (HADR)

High Availability Disaster Recovery (HADR) offers a high-availability solution by replicating
data from a source database, called the primary, to a target database, called the standby. HADR
provides protection for both partial and complete site failures. Combined with automatic client
reroute capability, HADR provides transparency to the application regardless of the failure type
from hardware, network, or software issues to disaster scenarios like fire. HADR provides
multiple levels of protection allowing flexibility in the environment. Additionally, DB2 provides
an easy to use wizard that allows the entire configuration to be setup in a matter of minutes.
HADR feature is part of all DB2 Editions. You only need to license the standby server for DB2
use. There are more specifics on this in the Licensing DB2 HADR and SQL Replication section
later in this document
Contact your account manager or TruckMate support if HADR is of interest to you.

13
8/6/2015
Disk Drive Layout & Performance

In addition to using SSDs, the drive count and their layout is critical to optimal TruckMate
performance.
All database platforms (DB2, SQL Server, Oracle, etc.) have general rules of thumb when it
comes to hard drive configuration and usage. This general rule of thumb is summed up in the
following warning:
Warning: Hard drives used for the DB2 server should be completely dedicated to DB2 only. This is
especially important in the case of SANs where logical drives called LUNs can conceal what physical
drives make up that LUN. No drive sharing should occur for maximum performance.
To dig a bit deeper on this general rule of thumb, here is how your drive system (internal, DAS
or SAN) should be generally structured:
Server Operating
System (OS)
Should reside on a RAID 1 array of SSDs. 10K or 15K SAS drives are
acceptable for TruckMate systems with 70 users or less. This Array should be
on a dedicated RAID controller channel.
DB2 Data Files
Must reside on a RAID 10 array sitting atop SSDs. This Array should be on a
dedicated RAID controller channel and preferably with its own dedicated onboard cache.
DB2 Active
Transaction Logs
Should reside on a RAID 1 array sitting atop high speed 10K or 15K SAS hard
disks or SSDs, for larger clients. This Array should be on a dedicated RAID
controller channel.
DB2 Archived
Transaction Logs
Should reside on general file storage such as a network file share or central
data store. High speed disk performance is not as important for the archived
logs as they will rarely be accessed; they are saved for backup purposes.
DB2 Backups
Should reside on tape or general SAN file storage in accordance with your
overall companys backup strategy.
Note: The hardware RAID controller(s) should have large amounts of on board cache. Having
1GB or more allocated to the DB2 data file array alone would be ideal.
In essence, the DB2 server will have three storage paths with one more multi-channel RAID
controllers. One channel will be dedicated to DB2 data files which is where all the day to day
read/write activity is occurring. Having this isolated and on SSDs will give maximum
performance. The other storage channels will service the log data and the Windows O/S
installation on two separate RAID 1 arrays.
Finally, in the case of the DB2 data array, the more drives you add the better your performance
will be. Few large drives may cost less than buying more small drives to get the same amount
of storage space. However, performance of the many small drives array will have more
working members thereby enabling more concurrent read/write drive operations per second.
For database data storage, its not about buying a lot of storage space; its about buying fast
storage.

14
8/6/2015
Storage Area Networks / SANs Performance

Requirements
Storage Area Networks (SANs) are particularly tricky. Many customers over the years have
purchased high-end SANs and used them to share all the available storage among many
different machines. Using a SAN in this manner is fine for general file storage but is detrimental
to TruckMate performance as it pertains to the databases on the DB2 server.
If your environment requires the use of a SAN, there is one simple metric that your SAN must
meet in order for TruckMate to perform as well as users expect. The metric is disk latency
which is also sometimes referred to as disk access time. Solid state drives which are configured
as recommend in this document will have a disk latency of around 0 to 5 milliseconds (ms). If
you use a SAN, you must ensure your spindle count and drive speeds will collectively provide
15 ms or less latency at all times. This means that disk access time should never go above 15
ms at any time; no matter how heavy of a user load is on the TruckMate/DB2 system.
The disk latency should be measured on the DB2 server with the Windows Resource
Monitor. Measuring the disk latency at the SAN controller or with the older Windows
Performance Monitor (perfmon) will not provide the disk latency granularity thats required.
Windows Resource Monitor is the best tool to use.
If latency goes over 15 ms your users will be experiencing performance problems due to poor
disk/SAN performance. TruckMate is a large scale ERP system which does OLTP and Data
Warehousing queries at the same time. This can require a very high amount of IOPS in short
bursts. SANs can be problematic in producing the low disk latency required on high IOP
systems if they are not built to handle it. SSDs are recommended, even in SANs with a very
large number of spinning disks.
It is also recommended to keep all your DB2 server and data files in the fastest tier of your
SAN, permanently. Tiered storage can cause random disk performance issues due to relegating
stale data into slower storage tiers. By configuring your DB2 Server LUN(s) to stay in the top
tier of your SAN you will get better and more consistent performance.

15
8/6/2015
Supported Windows Operating Systems and DB2 Versions

The operating system (OS) manages the sharing of the computer resources such as CPUs,
memory and hard disks. TruckMate only supports the Windows operating system. TruckMate
supports the use of several different Windows versions and editions.
DB2 is the Relational Database Management System (RDBMS) used for TruckMate databases.
For upgrades and new installations, DB2 Version 9.7 or 10.5 with most current TMW approved
Service Pack is required.
Please keep in mind that operating systems not supported by Microsoft or IBM DB2 are not
supported by TruckMate. For example, Windows XP, 2000, ME, 98 and NT are not supported.
TMW strives to support versions of Windows right up to Microsofts extended end of support
dates. This is normally years past the initial support end date. Please see the following URL for
the latest Microsoft end of support dates:
http://support.microsoft.com/lifecycle/search/default.aspx
With that said, IBM uses the Microsoft mainstream end of support date as their cutoff to
determine which versions of DB2 support the various Windows operating systems. As a result,
please refer to the dates in the tables below for TruckMate purposes. The dates noted in the
cross-reference tables below take both IBM and Microsofts support policies/dates into
account.
Tip: Contact TruckMate support to verify which current version and service pack of DB2 is supported by
TMW before your installation or upgrade.

16
8/6/2015
TruckMate Servers
Windows Server Version Support1
DB2 Server Support
2008
2012 R1
2012 R2
9.7
10.5
TruckMate
2013
Yes
Yes2
No
Yes
No
TruckMate
2014
Yes
Yes3,5
Yes4,5
Yes
Yes5
TruckMate
2015
Yes
Yes
Yes
No
Yes6
Windows Server Essentials, Windows Small Business Server and Windows Essential
Business Server are not supported.
TruckMate 2013 DB2 servers running on Windows Sever 2012 R1 must install:
DB2 9.7 FP7+
TruckMate 2014 DB2 servers running on Windows Sever 2012 R1 must install either:
DB2 9.7 FP7+
OR
DB2 10.5 FP3+
TruckMate 2014 DB2 servers running on Windows Sever 2012 R2 must install:
DB2 10.5 FP5+
DB2 10.5 is only supported on TruckMate 2014 SP1 or greater
TruckMate 2015 only supports DB2 10.5 FP5+.

17
8/6/2015
TruckMate End-User Workstations

Windows Desktop Version Support1
DB2 Client Version Support
10
9.7
10.5
TruckMate
2013
Yes
Yes3
No
Yes
No
TruckMate
2014
Yes2
Yes2,3
No
Yes
Yes4
TruckMate
2015
Yes2
Yes2
No
No
Yes5
1 Windows
editions must be: Professional, Business or Enterprise
2 TruckMate
3 Windows
2014+ requires the use of 64bit Windows editions
8 requires the use of DB2 9.7 FP7+ for the DB2 client driver
DB2 10.5 is only supported on TruckMate 2014 SP1 or greater
TruckMate 2015 only supports DB2 10.5 FP5+.
Warning: Windows editions listed under TruckMate End-User Workstations above are only supported
for user workstations in a TruckMate environment. Do not attempt to use these workstation editions of
Windows as a DB2 Server.

18
8/6/2015
Windows Desktop / Screen Settings

All users using TruckMate applications should have their Windows desktop configured for:
True Color (32 bit).
Screen resolution of 1024x768 or greater.
Windows Zoom setting of 100% or 125% (DPI setting of 96 or 120).
Tip: Workstations that are intended to be used with the TruckMate Dispatch or Customer Service
software should have at least 19 monitors in order to ensure optimal use of these programs.
SAP Crystal Reports Version Support

SAP Crystal Reports are used extensively in TruckMate. If you wish to modify and create your
own reports, you can do this by purchasing Crystal Reports from a 3rd party provider. Below is
information on what versions are supported by TruckMate and any compatibility limitations
they may have.
Crystal Reports XI R2 is fully supported on all versions of TruckMate.
Crystal Reports 2011 & 2013 are supported on all versions of TruckMate. However, there are
limitations on the use of some Crystal Report features. Below is a non-inclusive list of features
in Crystal Reports 2011 & 2013 that are not compatible with TruckMate:
- Unlimited page sizes
- On screen sorts
- Optional parameters
- XLSX exports
- Password protected reports
- Built in Crystal Reports bar code functions

19
8/6/2015
DB2 Licensing Requirements

DB2 and Core Limitations by Edition
The maximum amounts of RAM, CPUs/Sockets and Cores that each edition of DB2 can utilize
are in the table below.
If you have purchased DB2 from TMW, these limits apply to any currently supported version
of DB2 that a customer has installed. This includes versions 9.7 and 10.5 currently. These limit
exceptions are possible because we have special contractual exemptions compared to other 3rd
party resellers.
Please also note that if your current installation of DB2 does not allow the following limits due
to hard stops in DB2 run-time licensing checks, please contact TMW support to have a DB2
edition installed that meets or exceeds the limit amounts youre entitled to. TMW is authorized
by contract to do this.
DB2 Edition
MAX RAM*
MAX CORES*
MAX SOCKETS*
Express
64 GB
Unlimited
Workgroup
128 GB
16
4 Sockets
Enterprise
Unlimited
Unlimited
Unlimited
* Your Windows Server machine should have more RAM than the above values if you want to
fully maximize RAM usage within DB2. In addition, the Windows operating system that DB2
is installed on also has its own limits. Please ensure you have a Windows edition that supports
the same or better hardware levels as the DB2 edition purchased.
DB2 Licensing Types

Important: Before determining what DB2 license type to purchase, you need to know the exact
hardware you plan to use for your DB2 server. The information you must have before
purchasing is:
CPUs count
Core count per CPU
Total amount of RAM
There are four different ways that TMW sells DB2 licenses for a primary database server. They
are as follows:
Server - A Limited Use Virtual Server (LUVS) is a DB2 license for a physical server and/or
a virtual server.
You can run a standalone physical server or multiple Virtual Machines (VMs) and install
DB2 Express on as many VMs as you want with one or more server licenses. Note that the
total amount of resources allocated to all DB2 database manager instances cannot
collectively exceed 64 GB of memory or 8 processor cores per server license. In the case of
VM environment, multiple LUVS licenses may be purchased to support many databases on
one physical machine that exceeds the single server license limits.

20
8/6/2015
Socket - In IBM terms, a socket is the same as a CPU. Socket pricing is only available for
the DB2 Workgroup edition.
Socket pricing is a flat cost for each CPU in the DB2 server. There are no user limitations
when DB2 is licensed by socket/CPU. Also, there is no limit to the amount of cores each
physical CPU can have.
For example, if you were to buy an 8 core system it would be wise to buy a single CPU with
8 cores rather than 2 CPUs with 4 cores each. The second configuration with 2
CPUs/Sockets would be twice as expensive for DB2 licensing even though both
configurations have 8 cores.
The only caveat is that Socket licenses are only applicable to Workgroup edition which
has a 16 core and 128GB limit.
Authorized User (AU) - The AU license allows you to license DB2 on a per-user basis. With
this license, you have to buy an AU license for each user that wants to connect to a specific
DB2 server (physical standalone or VM). If the same user wants to connect to two different
DB2 servers, that one person needs two AU licenses (unless the VMs are on the same
physical server). In addition, you need to buy at least 5 AU licenses when licensing DB2
using this method. This license type is not for customers who are using or plan to use
TM4Web or other software that connects to DB2 for purposes of retrieving data for a web
interface that non-authorized users can access. The only exception to the TM4Web rule is
licensing a SQL Replication server. This is discussed in detail in the Licensing DB2 HADR
and SQL Replication section of this document.
Processor Value Unit (PVU) - The PVU number that determines the licensing cost is
calculated depending on the number of CPUs and how many cores each of those CPUs
have. Here is a table of how PVUs are calculated for x86 CPUs:
PROCESSOR VENDOR
Total SOCKET/CPUs per SERVER
PVU per CORE
Intel
2 CPUs Maximum
70
4 CPUs Maximum
100
More than 4 CPUs
120
No Limit
50
AMD
Here are a couple of examples using the above information:

1. Say you plan to buy a 150 User DB2 server which we recommend has 10 cores. Since Intel
offers a 10 core CPU your server is under the 2 CPU maximum of 70 PVUs per core. This
configuration, at 70 PVUs per core, is a total of 700 PVUs.
2. If you were to get 4 CPUs with 4 cores each you would be paying 100 PVUs per core on 16
cores for a total of 1,600 PVUs. However, it would be more cost effective to buy 2 CPUs
with 8 cores each to get into the 70 PVU per core bracket; this would be a total of 1,120
PVUs a 480 PVU difference which equates to thousands of dollars of savings.
The PVU values in the table above are current as of September, 2013. Please see the following
IBM webpage on PVU pricing for the most recent PVU calculations:

21
8/6/2015
http://www01.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customer
s.html
DB2 Licensing Types Available by Edition

DB2 Edition
SERVER
SOCKET
PVU
AU
Express
Yes
No
Yes
Yes
Workgroup
No
Yes
Yes
Yes
Enterprise
No
No
Yes
No
Licensing DB2 Test Servers

Test DB2 servers need to be licensed just like primary servers. This is because it is actively
connected to by users and as a result hot. However, the costs associated with getting a test
server licensed are always a fraction of the cost of a primary DB2 server.
Generally speaking, the most cost effective solution is to license test servers with the
Authorized User (AU) licensing type. Normally test database servers have several distinct test
databases and only a handful of people are connected to the server at any one time. This is
precisely what AUs licenses are good for.
Tip: Although it is possible to create a test DB2 instance on a primary database server to act as a test
environment it is still recommended to have a separate test server, especially for clients with more
than 30 users.
Licensing DB2 in a Virtual Environment

Licensing DB2 for a Virtual Machine (VM) is fairly straight forward:
If you will be using 8 cores or less and 64GB of RAM or less in all of your DB2 VMs on one
physical server, you should license DB2 Express with the Server license type.
If you will be using more than 16 cores and 128 GB of RAM in all of your DB2 VMs on one
physical server, you should license DB2 Workgroup with the PVU license type.
If you are currently licensed with PVUs or AUs please consult the definitions in the DB2
Licensing Types section, those rules apply to physical standalone hardware as well as
virtualized hardware.
If youre not in one of the categories above, youll likely be licensing Workgroup edition
with Sockets. Socket/CPU (not core) allocations are important to monitor in VM environments
because the physical hardware is hidden beneath a layer of virtualization software. VMs
focus on cores, not CPUs. This is where the gotcha can crop up on licensing with Sockets.
When using Workgroup socket licenses in a VM environment you need to license the number
of CPUs you plan to allocate to the DB2 VMs. This is up to a maximum of 16 cores and 64 GB of
RAM.
Here are a few examples:
22
8/6/2015
1. If you have a bare metal server with two 8 core CPUs (16 cores total) and you purchased
two Workgroup socket licenses that would fully license the physical machine for DB2. This
means you could create as many DB2 VM servers on that machine as you wanted, as long as
the total sum of memory did not exceed 64 GB and the core count remained at a maximum
of 16 cores.
2. You could purchase four 8 core CPUs (32 cores total) and only buy two Workgroup socket
licenses which would reach the Workgroup maximum of 16 cores on two of the four
physical CPUs. The remaining two CPUs and their cores on the bare metal must be
allocated to different non-DB2 VMs in your hosted environment.
3. You could purchase two 10 core CPUs (20 cores total) and buy two Workgroup socket
licenses. As in the previous example, you would only be allowed to allocate up to 16 cores
and 64GB of RAM total to all VMs running on that machine. The remaining 4 cores out of
the 20 must be allocated to other non-DB2 VMs running on that physical machine.
Naturally, there are several different scenarios that could be possible with CPUs having various
core counts and we havent covered them all here. If you need added guidance on selecting
the right hardware and licenses please contact your account manager or support for a
consultation.
Also note that Authorized User (AU) licenses may be useful in some VM environments where
socket pricing is not cost effective. This would normally apply to test servers.
For example: Say we have a physical server with two 8 core processors and the primary DB2
server VM is licensed with a single socket license (one of the two CPUs). Since that VM is
already using one full CPU/socket, an additional socket license would need to be purchased for
the test server. If buying another socket license isnt cost effective, an AU license scheme for the
test VM will likely be the right price point.
Licensing DB2 HADR and SQL Replication

The HADR function is available in all DB2 Editions at no extra charge for the feature. However,
the DB2 stand-by server itself needs to be licensed.
Before discussing the licensing requirements, lets get some of IBMs terminology straight:
Cold Stand-By The stand-by DB2 server instance(s) are not started until fail-over is
required. This is not applicable in a TruckMate environment, stand-by DB2 servers are
either Warm or Hot.
Warm Stand-By The stand-by DB2 server instance(s) are started and it will receive data
updates via HADR. There is no end user access allowed to the stand-by server until a
failover occurs. Administration tasks are the only usage allowed the stand-by DB2 server
when it is acting as a stand-by to the primary.
Hot Stand-By The stand-by DB2 server instance(s) are started and the stand-by is
actively servicing end user requests. A stand-by DB2 server in a TruckMate environment
will only be hot when SQL Replication is in use. As a result, IBM would normally require
you to license the whole stand-by as you would your primary server. This would be very
costly. However, TMW has negotiated a special contract term with IBM that allows us to sell
our customers a license that makes them fully compliant at a fraction of the cost.

23
8/6/2015
To use DB2 HADR you must purchase the appropriate license for your warm standby server.
This server can be a replica of your primary server hardware or something less powerful, its up
to you. It can even be a Virtual Machine (VM) with the primary server as a dedicated physical
machine. In any case, DB2 on the stand-by server needs to be licensed based on the licensing
type of the primary server.
SQL Replication is an add-on that needs to be licensed as well. SQL Replication is used in
TruckMate to replicate data in near real-time from tables in the live production database to a
standby database. This means the stand-by server can be accessed for reporting and data
mining purposes. This feature enables customers to off-load heavy hitting database queries
from their primary database server. These heavy hitting queries frequently affect users day to
day performance in applications such as Customer Service and Dispatch. Reports and KPIs
which dig deep into old data are well suited for SQL Replication stand-by databases. Think of
SQL Replication as TruckMates live data warehouse.
Both SQL Replication and HADR require either a socket license or 100 PVU license to get
started. As stated before, the type of license depends on what the primary server is licensed
with.
In addition, SQL Replication requires a minimum of 5 Authorized User (AU) licenses to be
purchased to satisfy the Hot server licensing requirement discussed earlier. The number of
AUs that need to be purchased depends on how many active connections you expect will be on
the SQL Replication reporting server at any given time. Generally its a good idea to start with 5
AUs and to purchase more as needed.
Blue fill in the following table indicates that you need to pick the one column that matches
your primary server license type and then purchase the value indicated.
Green fill means it's required if you decided to use SQL Replication, this is in addition to
the choice in blue fill on the same row.
DB2 FEATURE
SERVER
SOCKET
PVUS
MINIMUM AUs
HADR
100
SQL Replication
100
5 (more as needed)
Both HADR and SQL Replication
100
5 (more as needed)
Here are some examples using the previous table:

1. If you wish to use a DB2 stand-by server for HADR only, you would need to purchase an
additional server license OR 100 PVU license OR a single socket license OR 5 AUs,
depending on how your primary server is licensed.
2. If you wish to use a DB2 stand-by server for SQL Replication only, you would need to
purchase an additional server license OR 100 PVU license OR a single socket license OR 5
AUs AND 5 more AUs, depending on how your primary server is licensed.
3. If you wish to use both HADR and SQL Replication and you put them on the same server
you would still only need to purchase an additional server license OR 100 PVU license OR a
single socket license OR 5 AUs AND 5 more AUs, depending on how your primary server
is licensed. By putting both HADR and SQL Replication on one server you can save the
cost of 100 PVUs or 1 socket, this is a significant savings! Since SQL Replication will only be
active when HADR is not, this is great use of hardware as well.
24
8/6/2015
Tip: The HADR and/or SQL Replication server requires only 100 PVU, 1 socket or 5 AU licenses
regardless of how many PVUs, sockets or AU licenses are licensed on the primary server. For example,
the primary server could be licensed for 4 sockets but each stand-by server needs only 1 socket
license. If using SQL Replication, the additional AUs are required to account for the users accessing the
system for reporting purposes. These requirements are on a per machine basis. In other words, if you have
one server for HADR and one for SQL Replication you would need to license both separately.

25
8/6/2015
Network / System Landscape

TruckMate is installed in a client-server environment. In a client-server architecture, the client
and server are separate and implemented on a computer network. Clients and servers
connected to a network are often referred to as nodes. In the most basic type of client-server
architecture, only two node types are used, Clients and Servers.
This type of environment is usually referred to as two-tier architecture. It allows devices to
share files and resources.
Cables and Switches

Install CAT5e or CAT6 cables and use high-speed jacks and patch panel. Also, utilize network
switches (not hubs) due to their superior performance. A switch is a device that connects
individual devices on an Ethernet network so that they can communicate with one another.
Tip: Your Local Area Network should be at least 1 Gbps (1000 Mbps). All servers in the LAN must have
a sustained 1 Gbps switched connection with each other.
Remote Access (RDP/Citrix)

Many companies operate branch offices and have employees who travel or work from home.
These remote and mobile users need the system to perform as fast and dependably as their
colleagues at headquarters, even if they are connecting via the internet. Remote Desktop
Services (formally Terminal Services) from Microsoft and the Citrix Xen Suite from Citrix
Systems allows customers to provide easy, reliable, high performance access to TruckMate for
all users, regardless of their location, or connection.
In addition to the performance benefits received by remote users, using one of these lightweight
remote access infrastructures for both internal and external users lowers the total cost of
ownership (TCO) of TruckMate. This is because the product is installed, processed, maintained,
and supported on central servers instead of each users computer.
Connecting to a remote access server over the network, users view and work with the
application interface, sending keystrokes and mouse clicks and receiving screen refreshes only.
The amount of data transferring between the server and the client is a small fraction of what it
would be with having each users workstation pushing and pulling large data sets to and from
the database directly.
Both Remote Desktop Services and Citrix products offer clustering. This means that multiple
servers can be combined and be presented as one system. These machines can be configured
to balance user load evenly over all available machines. In addition to the performance
implications, having a cluster provides application redundancy. If one machine were to fail the
others would take on the extra load so users work is not interrupted.
Virtual Private Networks (VPNs)

VPNs can be used to secure all data that flows to and from authenticated external users on the
internet to the Citrix/Remote Desktop Servers in your local area network (LAN). VPNs enable

26
8/6/2015
these external users to operate on your network like they are in head-office while being 100s or
1000s of miles away.
Tip: TMW does not provide the physical VPN systems. Contact your network administrator or
Internet Service Provider (ISP) for VPN support.
Network Diagram of typical TruckMate System

The following page is a network diagram of a typical TruckMate system. The diagram contains
three main areas: Local Area Network (LAN), Demilitarized Zone (DMZ) and the Internet.
These three areas contain different user devices and servers. Each of these groups of devices are
labeled for clarity.
Naturally, not every configuration could be accounted for in one diagram but it does cover the
core TruckMate system plus popular add-ons. It should give you an excellent grasp of how
your network is structured when TruckMate is a part of it.

27
8/6/2015
Figure 1: Example of Typical TruckMate System

28
8/6/2015
Hardware Recommendations
This section of the document will follow the network diagram on the previous page. There will
be sections on user devices, required servers and optional servers.
In general, its wise to buy the best hardware you can afford for mission critical servers.
Consider a single tractor/trailer combination which will cost well over $100,000. A very large
number of loads must be completed to cover the initial cost of these assets, let alone the ongoing maintenance. In comparison, critical computer hardware will cost a fraction of this and it
runs your whole company from top to bottom.
Important: Any add-on module or third party product is subject to version changes and/or hardware
requirement changes without prior notice. Always confirm with TMW and 3rd party vendors that the
specific requirements for these products are current.
If you are unsure of anything recommended or documented here, please contact TMW support to clarify
any questions you may have.
Recommendations are based on experience with TruckMate application software and
knowledge of the computer industry. However, due to the rapid changes in server technology
and numerous approaches available today for multi-server processors, RAID technology,
backing up and general network redundancy, there is no single recommendation that any
software company can make as the one best way to configure your systems. Because of this fact,
the enclosed hardware requirements should be considered as general guidelines. Before buying
hardware, consult with a TMW technical specialist to review your configuration.
Tip: Virtual Machine (VM) environments are supported for all TruckMate servers. Take special note to
the warning on virtualizing the DB2 server in its respective section.
If you do choose to run a VM, click the following link for IBM-supported VM environments:
http://www.ibm.com/developerworks/wikis/display/im/DB2+Virtualization+
Support

29
8/6/2015
TruckMate User Devices

Windows Workstation/Laptop
ITEM
MINIMUM
RECOMMENDED
Operating System
See Supported Windows Operating Systems and DB2 Versions
CPU
2 Cores @ 2 GHz
2 Cores @ 3 GHz or greater
RAM
2 GB
4 GB or greater
Hard Disk
SATA
SATA III+
Network Card
100Mbps
1000 Mbps / 1 Gbps
Note that minimum requirements for the workstation / laptop are typical of an aging machine
built over 5 years ago. If your users are using other applications in addition to TruckMate, the
minimum requirements may not be sufficient. It is best to meet or exceed the recommended
requirements to ensure optimal performance and end-user efficiency.
Citrix / RDP Thin Client Terminals

Thin clients can be used in place of workstations or laptops. Thin clients rely on Remote
Desktop Services or Citrix to gain access to TruckMate. Thin Clients do not have hard drives
like traditional computers and they generally have less powerful hardware inside them. As a
result, these terminals can be quite cost effective.
Although thin clients are cheaper on a per machine basis, the Citrix or Remote Desktop
Server(s) need to be powerful enough to handle all users tasks within TruckMate and outside.
For example, using Microsoft Office products would be done though the thin client as well as
using TruckMate. This puts more load on the server(s).
In general, the more applications users run via thin clients the more memory and processing
power the servers will require. To that end, the thin clients themselves do not necessarily have a
recommended hardware size as it pertains to TruckMate. Basically the thin client will need to
support connecting to the remote desktop server which complies with TMW recommendations.
Some popular thin client manufactures are Wyse, Hewlett Packard, VXL and Devon.
Tablets and Smart Phones

Tablets and Smart Phones which have modern web browsers may be able to access select TMW
products. These products offer end users access to your system without using a computer
running Microsoft Windows. These devices do not support the full TruckMate product line.
Please refer to individual products which have website interfaces for browser and device
support.

30
8/6/2015
TruckMate Required Servers

The servers listed in this section would be considered core servers to the TruckMate
system. All these servers are required to get the base TruckMate system operational at your
business.
DB2 Server Requirements

The following is a list of the requirements for DB2 Servers for use with TruckMate, broken
down by number of Users in a Company.
Warning: Due to performance considerations, if you choose to use a Virtual Machine (VM)
environment for the database server you must provision/reserve the recommended hardware. This
means that load balancing on the DB2 Server VM with multiple other VMs on the same server is not
recommended. The DB2 Server VM needs the hardware (Cores, RAM and disks) dedicated to it.
If support is called upon to investigate performance problems in a virtual environment and the
environment or individual VMs are found to be configured incorrectly, TMW will charge back the time at
the standard hourly rate.
It is your responsibility to ensure the VMs in your environment are consistently meeting the
requirements within in this document.
0-30 User Company
ITEM
RECOMMENDED
Operating System
CPU
4 Cores @ 2 to 3 GHz (at least 8 MB L2 Cache per CPU)
RAM
12 GB DDR-3
Drive Configuration
See Disk Drive Layout & Performance
Drive Layout and Capacities
O/S C: Array 60GB+ RAID 1 on 10K or 15K SAS

Data D: Array 250GB+ RAID 10 on E-MLC SSD
Active Logs L: Array 50GB+ RAID 1 on 10/15K SAS
DB2 Edition

Express Server See DB2 Licensing Requirements
31
8/6/2015
31-70 User Company

ITEM
RECOMMENDED
Operating System
CPU
RAM
16 GB DDR-3
Drive Configuration
O/S C: Array 60GB+ RAID 1 on 15K SAS or E-MLC SSD

Data D: Array 700GB+ RAID 10 on E-MLC SSD
DB2 Edition
71-100 User Company

ITEM
RECOMMENDED
Operating System
CPU
RAM
24 GB DDR-3
Drive Configuration
O/S C: Array 60GB+ RAID 1 on 15K SAS or E-MLC SSD

Data D: Array 900GB+ RAID 10 on E-MLC or SLC SSD
DB2 Edition
101-200 User Company

ITEM
RECOMMENDED
Operating System
CPU
RAM
32 GB DDR-3
Drive Configuration
O/S C: Array 60GB+ RAID 1 on E-MLC or SLC SSD

Data D: Array 1.5TB+ RAID 10 on SLC SSD
Active Logs L: Array 150GB+ RAID 1 on SLC SSD
DB2 Edition

1 Workgroup Socket - See DB2 Licensing Requirements
32
8/6/2015

ITEM
RECOMMENDED
Operating System
CPU
RAM
48 GB DDR-3
Drive Configuration
O/S C: Array 60GB+ RAID 1 on SLC SSD

Data D: Array 2.5TB+ RAID 10 on 6 or more SLC SSD
DB2 Edition
2 Workgroup Socket See DB2 Licensing Requirements

ITEM
RECOMMENDED
Operating System
CPU
RAM
64 GB DDR-3
Drive Configuration

Data D: Array 4TB+ RAID 10 on 10 or more SLC SSD
DB2 Edition
2 Workgroup Socket See DB2 Licensing Requirements

ITEM
RECOMMENDED
Operating System
CPU
RAM
128 GB DDR-3
Drive Configuration

Data D: Array 6TB+ RAID 10 on 12 or more SLC SSD
DB2 Edition
1,400 Workgroup PVUs See DB2 Licensing Requirements
800+ User Company

TMW Systems is committed to providing a hardware solution for even the most demanding
requirements. We have conducted TruckMate benchmark performance testing at IBM testing
facilities which simulated 1,000 concurrent users. If the above suggestions do not cover your
user count, you may contact your TMW Representative to discuss a hardware setup that meets
your needs.
33
8/6/2015
Test/DBI pureFeat Server

All clients with 15 users or more should have a Test/DBI pureFeat server. This server or VM
doesnt need to be powerful. The server is not intended for user performance testing but rather
functional feature testing. It doesnt even need to run a Windows Server operating system.
This server will have a test installation of DB2, TruckMate and DBI pureFeat installed on it.
This isolates your testing from your production environments to ensure nothing adversely
effects your production environment.
The DBI pureFeat installation will be monitoring your production server but all the data will
be stored on the test server so no added DB2 and DBI pureFeat workload is put on to your
production server.
ITEM
RECOMMENDED
Operating System
CPU
2 Core @ 2 to 3 GHz or greater
RAM
8 GB
Hard Disk
SATA III+
Mileage Server
The Mileage Server can use various third party Mileage solutions, such as PC*Miler, Rand
McNally MileMaker and/or ProMiles. These must be purchased directly from their respective
companies. TMW suggests upgrading to the most current version of the third party Mileage
software you employ, as well as purchasing 1 user license for every TruckMate user you expect
to have.
Note: The TruckMate Mile Server application is an unattended Windows Service.
ITEM
RECOMMENDED
Operating System
CPU
RAM
4 GB
Hard Disk
SATA III+
Active Directory / Domain Controller

TruckMate installations require a Windows domain be setup. This is to ensure DB2 security
matches your domain users authority. As an added advantage, when a user changes their
domain password their TruckMate password changes at the same time.
Tip: The Windows domain should be operational prior to TMW staff setting up TruckMate. TMW will
not configure your domain for you.

34
8/6/2015
Email Server
Several features in TruckMate utilize email capabilities. For example, reports can be emailed to
clients, vendors or staff. For this functionality to work you require an email server.

35
8/6/2015
TruckMate Optional Servers

The servers listed in this section are considered optional servers to the TruckMate system. All
these servers are only required if you purchase the products which necessitate them.
Citrix / RDP Server

If needed, please refer to Remote Access (RDP/Citrix) to review how these types of servers are
beneficial to you.
Consider the other applications your users will be running in their remote access sessions. If
they are using more than TruckMate you should consider the impact of these additional
applications and whether they will require a more powerful server to ensure overall system
performance remains acceptable.
0-15 User Company
ITEM
RECOMMENDED
Operating System
CPU
RAM
8 GB DDR-3
Drive Configuration
RAID 10 on 15K RPM drives or better
16-30 User Company

ITEM
RECOMMENDED
Operating System
CPU
RAM
16 GB DDR-3
Drive Configuration
31-50 User Company

ITEM
RECOMMENDED
Operating System
CPU
RAM
32 GB DDR-3
Drive Configuration
50+ User Company

If your company requires more than 50 users working via Terminal Services/Citrix, consider
setting up server clustering (recommended) or multiple stand-alone Remote Desktop / Citrix
Servers. Such a setup will improve hardware redundancy and improve overall performance by
load balancing.

36
8/6/2015
Warning: Remote Desktop Services and Citrix cannot be run on the DB2 Server box for end-users. It
can be used for Administrative access. You must have a Terminal Server installed on a separate server
for end-users for TruckMate.
EDI Server
The EDI Server is used to process in-bound and out-bound EDI transmissions between
TruckMate and your trading partners.
Note: The TruckMate EDI Server application is an unattended Windows Service.
ITEM
RECOMMENDED
Operating System
CPU
RAM
4 GB
Hard Disk
SATA III+
Mobile Communications Server

The Mobile Communications Server is used to process inbound and outbound messages
between TruckMate and your drivers with in-cab or mobile handheld communications devices.
Note: The TruckMate Mobile Communication Server application is an unattended Windows
Service.
ITEM
RECOMMENDED
Operating System
CPU
RAM
4 GB
Hard Disk
SATA III+
Tip: If your company is using the Mobile Communications API provided in TruckMate, the
above Mobile Communications Server specifications can be used.

37
8/6/2015
TMW D2Link Servers

If your implementation of TruckMate utilizes TMWs D2Link and you have decided not to use
TMWs D2Link hosting offering, you will need the following server components active in your
infrastructure:
1) Web Server Running Microsoft IIS 7+
2) SQL Server Database Server Running Microsoft SQL Server 2005 to 2012
Web Server Details:
The IIS web server must have version 7 or greater installed
ASP.NET (2.0) must be enabled
Requires public IP or URL address for phones to connect to it via Internet (HTTP)
Should be in a DMZ to maximize network security
Must have connectivity with internal SQL Server database server
Can be on the same server as an Apache web server if desired
Please see the hardware specifications in our Web Server section for details on web server
sizing
SQL Server Database Server Details:
SQL Server Versions 2005 through 2012 are supported

Note: SQL Server 2014 and greater are not supported at this time. If you have 2014 media,
simply install 2012 in downgrade mode
SQL Server Express editions are not supported
See below for a general hardware recommendation for a basic SQL Server running only
D2Link SQL Server databases:
ITEM
RECOMMENDED
Operating System
Dependent on your edition of SQL Server
CPU
RAM
4 GB
Hard Disk
SATA III+
Tip: Please see Microsoft SQL Servers guideline for hardware and software for additional
details: https://msdn.microsoft.com/en-us/library/ms143506.aspx

38
8/6/2015
TMW ContainerSeek Server

If your implementation of TruckMate utilizes TMW ContainerSeek, you will need the following
server allocated to your infrastructure. This server handles the communication and data storage
of the container tracking information.
ITEM
RECOMMENDED
Operating System
CPU
RAM
4 GB
Hard Disk
SATA III+
Consolidating Required and Optional Servers

Depending on the add-on modules you are using, you are able to consolidate some of the
previously specified servers on to one server. The only stipulation is that the server used to host
multiple TMW server applications needs to be more powerful than previously specified.
The following TruckMate server applications can be consolidated on to one or more
machines:
Mileage Server Service
EDI Communications Service
Mobile Communications Service
Mobile Communications API Service
TMW ContainerSeek
Scheduler (used mostly for DAWG, TM4Web and RP3)
Status Changer (used mostly for TM4Web Carrier functionality)
The following hardware recommendation would be sufficient to host all of the above services
and applications:
ITEM
RECOMMENDED
Operating System
CPU
RAM
12 GB DDR-3
Drive Configuration
Imaging Server
The Imaging Server is required whether you use a TMW Imaging product or another 3rd party
imaging system. TMW sells two imaging products, TMW-Synergize and TMW Imaging. Please
contact your project manager or your account manager for the latest hardware
recommendations on these TMW products.
39
8/6/2015
Shop / Maintenance Server

The Shop / Maintenance Server is required whether you use a TMW maintenance product such
as TMT Fleet Maintenance or another 3rd party maintenance system. Please contact your project
manager or your account manager for the latest hardware recommendations on the TMW TMT
Fleet Maintenance product.
Optimization (Appian / IDSC) Server

The Optimization Server is required whether you use a TMW optimization product or another
3rd party optimization system. TMW sells two optimization product lines, Appian Logistics
and IDSC. Each product line contains multiple sub-products. Please contact your project
manager or your account manager for the latest hardware recommendations on the TMW
products of interest to you.
Other 3rd Party Servers

If your implementation of TruckMate requires other servers for integration to 3rd party data
providers such as fuel cards, e-checks, load boards or others, please contact your vendor(s) for
their latest hardware requirements.

40
8/6/2015
Web Server
The Web Server is your client, vendors and employees gateway into TruckMate via internet
web browsers such as Internet Explorer, Chrome or FireFox. Different web enabled products
from TMW provide web users with functionality such as:
Mobile communications
Rate quotes
Pickup requests
Direct order entry
Load tracking
Status updates
Driver pay
Settlements
Reporting
Web Products from TMW which can be hosted on a single Web Server are:
TruckMate for Web (TM4Web)
DriverSEAT
D2Link Host
TruckMate API (only if it needs internet exposure)
0-100 Concurrent Web Users

ITEM
RECOMMENDED
Operating System
CPU
RAM
4 GB DDR-3
Drive Configuration

ITEM
RECOMMENDED
Operating System
CPU
RAM
8 GB DDR-3
Drive Configuration

41
8/6/2015

ITEM
RECOMMENDED
Operating System
CPU
RAM
16 GB DDR-3
Drive Configuration
Network Cards
2 NICs or more (load balanced)
600+ Concurrent Web User Company

If your company requires more than 600 web users working via your Web Server, setting up
server clustering is recommended. Such a setup will improve hardware redundancy and
improve overall performance by load balancing.
Tip: Some products use Apache Web Server and others use Microsoft IIS. If you have purchased different
products be aware that they can be configured to run on the same web server host by running on different
TCP/IP ports (default is port 80 for both).
FTP Server
The FTP Server can be used for EDI flat file transmissions rather than using a Value Added
Network (VAN). FTP servers are also useful for general purpose file transfers between the
internet and LAN. This adds a level of security to your network.
If desired, the FTP Server can be hosted on the same machine as the Web Server.

42
8/6/2015

Hardware and IT Infrastructure Guide PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Hardware and IT Infrastructure Guide PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Hardware and IT Infrastructure Guide

Hardware and IT Infrastructure Guide

Hardware and IT Guide

Creation based on 2011 document

Revamped whole document

More detail on SSDs for DB servers and additional

Added DB2 licensing section as well as additional

Updated DB2 licensing information to reflect new

Updated DB2 HADR section, Supported O/Ss and

Added Storage Area Network (SAN) specific section

Document Template Updated

Added test server requirement, updated supported

Added DB2 10.5 as a supported DBMS

Removed WMS section. Product no longer sold.

Added TMW ContainerSeek Recommendations and

Added support for DB2 10.5 FP5 which results in

Added requirements for D2Link

Updated DB2 License & Supported OSs Sections

Hardware and IT Guide

Hardware Overview and General System Requirements ............................................ 7

Hardware Recommendations .................................................................................... 29

Active Directory / Domain Controller ........................................................................................................... 34

Hardware and IT Guide

Data Safety and Security

Hardware and IT Guide

Hardware Overview and General System Requirements

Critical Components of a Computer

Off-line backup storage (tape, optical disk, etc.)

In terms of capabilities and cost, these technologies form a spectrum.

Very fast (access times of a few nanoseconds)

Low capacity (usually 100's of bytes)

Very limited expansion capabilities (a change in CPU architecture would be required)

Expensive (more than one dollar/byte)

Very high capacity (can be 1000s of terabytes)

Very inexpensive (fractional cents/byte)

By using different technologies with different capabilities, it is possible to fine-tune system

Hardware and IT Guide

Processor / Central Processing Unit (CPU)

Memory / Random-Access Memory (RAM)

Hardware and IT Guide

Access arm movement

Heads reading/writing data

Data transfer to/from the drive's electronics

Hardware and IT Guide

Hardware and IT Guide

Redundant Array of Independent Drives (RAID)

Hardware and IT Guide

RAID 10 is a nested RAID system created by combining RAID 1 and RAID

Hardware and IT Guide

DB2 High Availability Disaster Recovery (HADR)

Hardware and IT Guide

Disk Drive Layout & Performance

DB2 Data Files

Hardware and IT Guide

Storage Area Networks / SANs Performance

Hardware and IT Guide

Supported Windows Operating Systems and DB2 Versions

Hardware and IT Guide

DB2 Server Support

DB2 10.5 is only supported on TruckMate 2014 SP1 or greater

TruckMate 2015 only supports DB2 10.5 FP5+.

Hardware and IT Guide

TruckMate End-User Workstations