Type topic text here.
Prerequisites: Your PC must have osImageManagerApp (v1.0.0.17 or later) installed and be able to access the server(s) that host the production databases. It is assumed the Patient database is already in production and the server that will host the Image database has the required database engine installed.
Caution: You should perform user acceptance testing of the URA system in a system test environment before attempting to use it in a new production environment. However, deinstall the URA Feature of osImageManagerApp before using the system for production purposes.
Editing the osImageManagerApp Configuration File
Setting-up the URA databases for a New Production System
Note: Installation Troubleshooting provides information about resolving any problems that result from running the scripts in following procedure:
Start osImageManagerApp and logon using a SysAdmin name and password for your database engine(s)
Open the Database Admin dialog box and run the following scripts
CreateUsersImage - creates Security Logins for URA-Admin, URA-Operator and URA-Guest on the database engine used for the Image database
CreateUsersPatient - creates Security Logins for URA-Admin and URA-Operator on the database engine used for the Patient database. You don't need to run this script if the URA databases are hosted on the same machine, but doing so has no adverse affects.
CreateImageDb - creates the Image database on the server defined by the osImageManager configuration file
CreateImageTables - creates the tables required for UAT (or Production) on the Image database and makes URA-Admin a db_owner
Close the Database Admin dialog box and Logoff
Open the Database Admin dialog box and run the following scripts
SetupImageDb - creates the stored procedures, users and permission required for the Image database
SetupPatientDb - creates the stored procedures, users and permission required for the Patient database
TestImageDb - checks that the Image database is correctly installed and configured for use by osImageManager. At this stage there are no records in the Image database so you should just see the column names of the Image table in the Results box.
Check your access to the Patient database by entering a Volunteer Reference number into the appropriate text box and then clicking the TestPatientDb button. The output of the query should then appear in the Results box.
Close the Database Admin dialog box
Check the URA System to confirm it is operating correctly
Install osImageManager on the PCs belonging to other users and edit their osImageManagerApp configuration files as described above
Allow other users to access the URA production system and draw their attention to the new features and changes in osImageManager
Removing URA from a Production Database