Versions Compared

Old Version 8

changes.mady.by.user Alanna Connolly (Unlicensed)

Saved on

compared with

New Version 9

changes.mady.by.user Samuel Allingham (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Unzip the file

  2. Click on the bat file named DOUBLE CLICK HERE TO INSTALL.bat. Multiple installers will pop-up and install the prerequisites before starting the installation of epiCentrepalCentre.

    Note

    Please note, you can skip over the SQL Server Compact Edition installer as this is not required when placing the database on an SQL server (4th installer) – just click cancel when the installer appears.

  3. You will be prompted for an install folder.  palCentre will work when installed in C:\Program Files (x86)\AHSRI\palCentre\ (the default) or any other folder that is available to the machine.

  4. You will be prompted for a folder in which to store the configuration file.  This path should be a location where ordinary users have read and write access.  We recommend C:\palCentre\, however we have allowed this as a configuration option in order to support different partitioning configurations, or even installation of the software and configuration to a network drive.

...

  • Server: the name of the instance of SQL Server installed on the service, will be pre-filled from the previous page
  • Database: the name of the database you want to create in SQL Server
  • Authentication: the Active Directory option can be chosen for those SQL installs that don’t have any explicit accounts, as long the account of the person installing has access to create databases within SQL Server
  • Username prefix: epiCentre palCentre relies on 3 SQL logins.  So that you can conform to your own naming standards, epiCentre palCentre asks for a prefix to use for these logins.  The default is ahsri_eppoc – please change this to ahsri_pcoc. ePPOC is a sister centre of PCOC and this name should be reserved if ePPOC databases are ever installed on your server. This will create logins ahsri_pcoc_dbo, ahsri_pcoc_user and ahsri_pcoc_reader.  You can use any prefix you like which would result in a valid SQL login.
  • DBO password, User password and Reader password:  you may use the same password for all 3 logins or different passwords.  For higher security we recommend using a different password for each SQL login.  For each login, there is a password and confirm password textbox.  Note that these passwords are encrypted before being saved in the configuration file, ensuring your password security.  Make a note of these passwords because you will need to use them again in the ‘Client Configuration Wizard’.  Ordinary users will never need to use or know these passwords.
  • Database path: this is the path on the SQL Server (not on the client machine) where the database .MDF and .LDF files will be created.  The default is C:\ePPOC\ but you will probably have a specific folder where SQL Database files are kept. This path must already exist to correctly work.

...

Info

palCentre will use the built-in database create SQL scripts and the database administrator login details provided on the previous step to connect to the SQL Server and create the palCentre database. 

Steps palCentre uses to create and configure the database

The database is created and configured in 3 steps:

  1. Create database and SQL logins - This is the step that is most likely to have an issue (such as the ones described below).  If it fails, the most likely outcome is that the database won’t be created in SQL Server. However, you should check in SQL Server to see if any part of the database or logins were processed
  2. CREATE TABLE IF NOT EXISTSs and database users - Creates the data structures of the palCentre database.  If this first step succeeded it is highly unlikely there will be any problems with this step.  It also creates the users with database-level roles based on the logins created by the previous step
  3. Create records - Populates the tables created in the previous step with structural records (constants, status lookups, and PCOC codesetscode sets)

Potential Errors when trying to create and configure the database

If there were any problems with the data you entered, or with executing the database create scripts, the items which caused the problem will be highlighted and/or an appropriate error message will be displayed.  A few errors you may encounter here:

  • Not entering matching passwords for dbo, user, and reader SQL logins - palCentre will catch this error, highlight the problem items and display an appropriate error

  • Entering a database path that does not exist - If the path you enter in ‘Database path’ doesn’t exist, the create database script will ‘fail’ cleanly and report an error message.  If it reports this error, correct the database path and try again

  • Entering a ‘user prefix’ that results in illegal login names - If your prefix contained an illegal character, the create database script will again ‘fail’ cleanly and report an error message.  If it reports this error, correct the user prefix and try again

If you successfully created the database

If the create and configure step was successful, a message will be displayed indicating success and you will be moved to the next step.  You should also check that the database and SQL logins were created in SQL Server and that the .MDF and .LDF files were written to the expected location. 


If you see any problems in SQL Server, you should manually delete the database and logins in SQL Server, click Previous on the Wizard, and try again.

...

As part of your installation email, you should have recieved received an email with your site specific details below. If you did not recieve receive this, please contact Alanna Connolly on (02) 4221 5640 or Sam Burns on (02) 4298 1141.

...