1

PASTE EVOLUTION SYSTEM REQUIREMENTS

and

INTERNET CONNECTIVITY RECOMMENDATIONS & TROUBLE-

SHOOTING

Contents Pastel Evolution System Requirements .................................................................................................. 2

Recommendations on Synchronisation Setup ........................................................................................ 4

Determining the root of the communication problem when working with branch accounting ............ 6

2

Pastel Evolution System Requirements

AREA MINIMUM RECOMMENDED DOES CLIENT ACTUAL MEET MINIMUM OR

RECOMMENDED? (Y/N)

HARDWARE: [Please Note: 32-bit (x86) and 64-bit (x64) processors are supported]

Single User Single-core 1 Ghz Dual-core or more 2 Ghz or faster

Workstation Single-core 1 Ghz Dual-core or more 2 Ghz or faster

Server (Less than 10 users)

Dual-core 2 Ghz Quad core or more 2 Ghz or faster

Server (11 - 20 users)

Dual-core 2 Ghz Quad core or more 2 Ghz or faster

OPERATING SYSTEM: [Please Note: Windows XP Home, Windows 7 Starter and Windows 7 Home Premium editions are not supported by Sage Evolution.]

Single User Microsoft Windows XP Professional Edition Service Pack 3 or later

Microsoft Windows 7 Professional Edition Service Pack 3 or later

Workstation Microsoft Windows XP Professional Edition Service Pack 3 or later

Microsoft Windows 7 Professional Edition Service Pack 3 or later

Server (Less than 10 users)

Windows Server 2003 R2 Standard Edition Service Pack 2 or later

Windows Server 2008 R2 Standard Edition Service Pack 2 or later

Server (11 - 20 users)

Windows Server 2003 R2 Standard Edition Service Pack 2 or later

Windows Server 2008 R2 Standard Edition Service Pack 2 or later

RAM:

Single User 2GB 4GB or more

Workstation 2GB or more 4GB or more

Server (Less than 10 users)

4GB or more 6GB or more

Server (11 - 20 users)

4GB or more

8GB or more

SCREEN RESOLUTION:

Single User 1024 x 768 1024 x 768

Workstation 1024 x 768 1024 x 768

Server (Less than 10 users)

1024 x 768 1024 x 768

Server (11 - 20 users)

1024 x 768 1024 x 768

DATABASE SERVER: Microsoft (TM) SQL Server 2008 R2 - Service Pack 1 or later.

FTP (FILE TRANSFER PROTOCOL) SERVER:

Microsoft FTP running IIS 6.0 or later (for Branch Accounting environments).

OTHER SYSTEM REQUIREMENTS:

Microsoft Excel 2007 or later (for the Sage Pastel

3

Intelligence Reporting module).

DVD-Rom.

256 Colour VGA or SVGA Video Graphics.

The on-line help requires Internet Explorer version 6 or higher, or a compatible browser.

Up-to-date network drivers, service packs and updates for your network and operating systems.

Windows 7 personal computers/notebooks need to ensure that the recommended RAM memory requirements and Video Graphics adapter are met.

The above serves as a guideline. Hardware requirements may differ depending on the operating system and the version of SQL Server.

For Microsoft SQL Server 2012, please note that there are additional software requirements to adhere to. Please refer to the SQL Server documentation for more information.

4

Recommendations on Synchronisation Setup Branch

Line Speed Synch Interval (Assuming 60% availability due to line shaping.)

128kpbs Not recommended for Branch Accounting

256kbps 120 + minutes

384kbps 90 - 120 minutes

512kpbs** 60 - 90 minutes

1mpbs 30 - 60 minutes

4mbps 15 - 30 minutes

**Recommended base line

Head Office

Line Speed Synch Interval

128kpbs Not recommended for Branch Accounting

256kbps 120 - 240 minutes

384kbps 90 - 120 minutes

512kpbs** 60 - 90 minutes

1mpbs 30 - 60 minutes

4mbps 15 - 30 minutes

**Recommended base line

In the event of multiple branches staggered synchronisation is recommended

please see example below.

Example : Head Office with 5 branches

Branch Using 384kbps line

Head Office Using 1mbps line

Synch Interval at Branch 90 minutes (business day from 8am until 6pm)

Synch Interval at Head Office 30 minutes (business day from 8am until 6pm)

First Synch Second Synch Third Synch

Branch 1 08:00 09:30 11:00

Branch 2 08:02 09:32 11:02

Branch 3 08:04 09:34 11:04

Branch 4 08:06 09:36 11:06

Branch 5 08:08 09:38 11:08

Head Office 08:00 08:30 09:00

5

Should a scenario then occur where Branch 1 sends an IBT to Branch 2, with the above synch setup,

the transactions would be received and processed as per the table below. It is important that proper

consideration is given to the operational requirements of a business in order to determine the best

synch interval. Should the synch intervals be too great for business requirements then a line upgrade

is recommended.

Scenario:

Branch 1 sends an IBT to Branch 2

08:00 08:30 09:00 09:30 10:00

Branch 1 Synch Runs, IBT is synched to HO

HO IBT received at HO

Branch 2 IBT received at Branch 2 at 9:32 synch

Other important factors that could impact the performance of the

synchronisation tool

1) All of the above recommendations are calculated using the benchmark synch file size of 500kb.

Should there be a greater file size sent on a regular basis this would then need to be looked at

on an individual basis.

2) Set up is critical and at all times only duly certified and authorised personnel should have access

to the synch monitor. Should any of the settings be changed this could result in the

synchronisation not happening.

3) The synch monitor must be open and running on both the Branch and Head Office servers at all

time in order for the synchronisation to work. This will mean that the server machines must also

be booted up and running.

4) The internet connection must be running in order for the synchronisation to work. If users are

unable to access the internet or e-mail and this line is shared with the synch tool then the

synchronisation will more than likely also be affected.

5) The FTP folder is the domain of the clients IT service provider. Should any changes be made to

the FTP it must be tested to ensure that the synch tool is able to connect to the FTP from all

locations.

6) The above recommendations have been determined based on a typical Branch Accounting

environment. There may be additional external factors which affect the performance of the

synchronisation and are unique to a site. These will need to be investigated and further

recommendations made thereafter.

6

Determining the root of the communication problem when working

with branch accounting

The command below will need to be executed from a branch that is trying to access the ftp site.

1) Open a Dos session ( Start => run => CMD )

2) In the dos application type the following : Tracert public_IP_address > c:\BranchA.txt

Note: The Public_IP_Adress must the one being used for the ftp site

3) Wait for about 3 minutes, as the results are copied to C:\BranchA.txt or the name you will

have used.

4) Share the results file with an IT person who will be able to interpret it.

This will show the route to the destination, and where the bottleneck is.