PACS. User Guide. Installing PACS on a Peer to Peer Network. pacs1.6

Transcription

1 PACS Installing PACS on a Peer to Peer Network User Guide pacs1.6

2 Human Edge Software Corporation Pty Ltd 427 City Road South Melbourne Vic 3205 Support Centre: Web: Tel: (calls from Australia) or Human Edge Software Corporation Pty Ltd, Melbourne 2008 Updated June 2008 Screen Images from version

3 Table of Contents Overview... 2 Other related Documents... 2 Summary... 2 On Server... 3 Microsoft Dot Net Framework... 3 Install SQL Express... 4 Configure SQL express for multiple users... 7 Further Requirements... 8 To enable TCP/IP:... 8 To enable the firewall:... 9 Open Firewall Ports for SQL... 9 Install PACS On the server machine Setup the database Share the INI File At each workstation Identify path to parish.ini on server Install PACS Connect to the database PACS P2P Network Installation Guide Page 1 Copyright: Human Edge: June, 2008

4 Overview Networking PACS requires a number of configuration changes associated with Microsoft SQL Server in the small parish peer to peer network Microsoft SQL server express. It is recommended that this be done by an experienced network professional. The tasks required are Other related Documents PACS Installation and Going Live. Summary On Server: 1. Microsoft Dot Net Framework 2.0 Windows XP - Install if not already done 2. (a) Install SQL Express & configure for Peer to Peer network OR (b) Configure existing SQL Express for Network 3. Create users 4. Enable TCP/IP 5. Enable Firewall and open ports 6. Install PACS 7. Start PACS & create the shared database 8. Relocate & Share Parish.ini 9. Point DB to relocated parish.ini file On each Workstation: 1. Identify path to parish.ini on server 2. Install PACS 3. Point DB to Parish.ini

5 On Server Microsoft Dot Net Framework (Windows Vista has this already installed) To identify if this has been installed at the start menu, select control panel and then Add remove programs Scroll down (its alphabetical) and you should see something similar to If you can t find it then an installation copy is available on the PACS install CD at Drive:\extra\dotnetfx20.exe where Drive is the letter assigned to the CD ROM

6 Install SQL Express This is available on the PACS installation CD The installation process has a number of screens accept default except for the following when they appear Un-tick the Hide advanced configuration options

7 Install all components Set both services to start

8 Select both authentication modes Specify the Server Administrator (SA) password * Add user to SA role Step through and complete the install * See Username & password in setting up database

9 Configure SQL express for multiple users If already installed change using Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration Choose Surface area configuration for Services and Connections

10 Select Remote Connections Set local and remote connections and use TCP/IP Click APPLY and OK Further Requirements For SQL Server Express, the Local System Account is Network Service Account. SQL Server Express listens on local named pipes and shared memory. With a default installation, you cannot remotely connect to SQL Server Express. You will need to enable TCP/IP and check if the firewall is enabled. To enable TCP/IP: 1. From the Start menu, choose All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager. Optionally, you can open Computer Manager by right-clicking My Computer and choosing Manage. In Computer Management, expand Services and Applications, expand SQL Server Configuration Manager. 2. Expand SQL Server 2005 Network Configuration, and then click Protocols for InstanceName. (This is normally SQL 3. In the list of protocols, right-click the protocol you want to enable, and then click Enable. The icon for the protocol will change to show that the protocol is enabled.

11 To enable the firewall: 1. Click Start, click Control Panel, and then click Network Connections. 2. From the navigation bar on the left, click Change Windows Firewall settings 3. On the Exceptions tab, in the Programs and Services box, you will probably see that SQL Server is listed, but not selected as an exception. If you select the check box, Windows will open the 1433 port to let in TCP requests. Alternatively, if you do not see SQL Server listed, do the following: a. Click Add Program. b. Click Browse. c. Navigate to drive:\program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BINN d. Add the file sqlservr.exe to the list of exceptions. Open Firewall Ports for SQL e. Click Add Port Enter Name as TCP 1433 and the Port Number to 1433 Ensure the radio button is in TCP Click Change Scope Select the radio button My network (subnet) only

12 Click OK f. Repeat the above process Click Add Port Enter Name as UDP1433 and the Port Number to 1433 Ensure the radio button is in UDP Again Click Change Scope Select the radio button My network (subnet) only

13 Install PACS On the server machine The instructions for this are as in the document PACS installation and Going Live. It is strongly suggested that each installation on a peer to peer network is Local. This ensures that the program is run locally but the data is stored centrally & shared. Peer to peer sharing of the program will degrade the performance of both server and workstation. Setup the database When starting PACS for the first time a blank profiles screen is displayed. Click on the New button A Create Database form is displayed. Ensure that the radio button shared is selected Untick trusted connection and enter the username sa and the password you entered when establishing the Authentication mode on page 6

14 Share the INI File When PACS installs on the Host Machine it creates a parish.ini (or configuration file). It normally places this in the c:\program files\humanedge\pacs directory. Since this is a nonsharable folder the following steps need to be completed. On the local disk - C Drive of the host machine 1. Create a folder HE 2. Once created, right click and Share 3. Move the parish.ini file to this location 4. Start PACS and choose File > open Select Setup

15 In path for shared databases change to C:\HE\ as created above Click SAVE

16 At each workstation Identify path to parish.ini on server It is not strictly necessary to create a formal mapping. UNC path is valid. Install PACS The instructions for this are as in the document PACS installation and Going Live. It is strongly suggested that each installation on a peer to peer network is Local. Peer to peer sharing of the program will degrade the performance of both server and workstation. Connect to the database When starting PACS for the first time a blank profiles screen is displayed. Click on the Setup button and enter the path to the Parish.ini file Click Save and the database should be displayed in the profile Click Select Repeat for any other workstation.