Installation Environment and Network Requirements
|Newton User Guide: Installation|
At Agency Systems, we strive to provide the best possible experience for our end users. This is why we test, validate, and endorse particular setup types for our application. While there are potentially many solutions, we have identified and support the environments best suited to run Newton by Agency Systems. Our application is designed to run on Microsoft Windows Operating Systems.
Deviation from these supported setup types may result in reduced functionality or features. Please have your technician contact us to answer any questions you may have.
- Single user, single PC
- Peer-to-Peer workgroup using TCP/IP and DNS (five or less users)
- Microsoft Windows Server/Client (five or more users)
- Remote Desktop to RDP server acting as the PSQL server or client (Terminal Server)
- Hardware Recommendations
- Not Recommended
- Running Microsoft Exchange or other database applications on the same server; competition for server resources may lead to degraded performance.
- Not Supported
- Microsoft Remote Web Application - (This is not the same as Microsoft Remote Desktop.)
- Thin clients and VPN - (Thin Clients and VPN may be supported by using Microsoft Remote Desktop inside your session.)
- Network Attached Storage (NAS) - (SAN devices can work, however require local IT support.)
- External Hard Drive for database storage.
Agency Systems is a network dependant application. In a typical setup the programs and data are located on a dedicated server or master workstation. This means that your network is an important piece for the performance and sustainability to run Agency Systems. Below are some key items and requirements for Agency Systems to run properly.
Verify that all workstations on the network are on the proper Workgroup or Domain
Each Windows computer belongs either to a workgroup or a domain. Typically small smaller offices use workgroups, and larger business networks operate with domains. Membership in a workgroup or domain is essential to avoiding technical problems in networking Windows computers. Whenever possible, ensure all computers on the LAN use the same workgroup/domain name.
Verify that the network type is set to Domain or Work network
If the network type is set to public there will be sharing limitations and insufficient permissions to read and write data to the database.
Make sure that you can ping the server by name
A ping test determines whether your computer can communicate with another computer over the network by name and the functionality of your DNS server. You can use a ping test to troubleshoot connectivity problems within your local network.
Configure your Firewall / Anti-Virus Software
Exclude the entire Empire directory through the mapped network drive (workstation/server), and using the local disk path (server).
Add the following Pervasive PSQL components to your global exception list:
- ntdbsmgr.exe = Pervasive PSQL Server
- w3dbsmgr.exe = Pervasive PSQL Workgroup
Additionally the following ports may need to be opened for Pervasive PSQL communication:
- 3351 = PSQL Transactional Interface
- 1583 = PSQL Relational Interface
- 139 = Named Pipes
Note that opening a port opens it for all access, not just for Pervasive PSQL.
- Wireless networks are not recommended because of latency and dropped connections.
- Disable power saving on the NIC.
- Disable the sleep, hibernate and power down of the hard drive.
- It may be necessary to disable IPV6 on the host machine and workstations if unsupported by your network.