AS300 Upgrade Guide IMPAX 6.2 or later to IMPAX 6.4 Upgrading the Components of an IMPAX 6.2 or 6.3 AS300 Cluster to IMPAX 6.
Copyright information © Copyright 2009 Agfa HealthCare N.V., Septestraat 27, B-2640, Mortsel, Belgium. All rights reserved. No parts of this document may be reproduced, copied, translated, adapted, or transmitted in any form or by any means without prior written permission of Agfa HealthCare N.V. Trademark credits Agfa and the Agfa rhombus are trademarks or registered trademarks of Agfa-Gevaert N.V., Belgium or its affiliates.
• The electrical installation of the site in which the equipment is used is according to an applicable safety standard (UL, CSA, or IEC/CDE). • The equipment is used according to the instructions provided in the operation manuals. • No software other than that which is distributed with this package or is sanctioned by Agfa will reside on the IMPAX 6.4 computers. Additional documentation: Upgrades from IMPAX 6.
Contents 1 Preparing to upgrade 8 Valid IMPAX upgrade paths .............................................................................. 8 Gathering information and equipment .............................................................. 9 IMPAX 6.2 or later upgrades: Necessary information and equipment .... 9 Running the Cross-Cluster Dictation Interlock tool ........................................... 9 Taking a system snapshot .........................................................................
Generating the portable password file ............................................................ 29 Updating the SQL Server registration ............................................................. 30 3 Replacing an existing Database Server with a new station 31 Upgrading the IMPAX database schema to IMPAX 6.4 ................................. 31 Checking the upgrade status .......................................................................... 32 Backing up the AS300 SQL database .................
Comparing pre- and post-migration snapshots .............................................. 57 Synchronizing clocks on Windows-based IMPAX systems ............................ 57 Allowing time synchronization on a hardened IMPAX system ............... 57 Synchronizing a Windows 2003 server to an external time source ....... 58 Synchronizing a Windows 2003 server to an internal time source ........ 59 Synchronizing with a time server when the IMPAX computer is not a member of a domain ........................
Index ..................................................................................................................... 84 AS300 Upgrade Guide—IMPAX 6.2 or later to IMPAX 6.
Preparing to upgrade 1 Important! Before proceeding with the upgrade of the AS300 server components, ensure that you have completed the pre-migration tasks outlined in the Pre-Migration Guide—IMPAX 6.2 or later to IMPAX 6.4. You must perform certain preparatory tasks before upgrading to an IMPAX 6.4 AS300 configuration. These tasks include taking a system snapshot, stopping the transmission of data to the previous release of IMPAX, and halting and emptying queues. 1.
Note: If upgrading an IMPAX 5.2 or 5.3 AS3000 server on Solaris 10, contact the national or regional representative at Agfa HealthCare’s Global Services for additional information and assistance. A site running IMPAX 4.5 can migrate its user data—passwords, IDs, and most preferences—to IMPAX 6.4. However, database data cannot be upgraded directly from IMPAX 4.5 to IMPAX 6.4. The IMPAX 4.5 database must first be upgraded to IMPAX 5.2.5, then to IMPAX 6.4. 2.
3. Exit the command prompt. 4. Taking a system snapshot Before migrating to IMPAX 6.4, use the migration_inventory tool to capture the current state of the system for later comparison. Perform this task on any computer that has access to the AS300 database to be migrated and on which the Migration Tools have been installed. To take a pre-migration system snapshot 1. At a command prompt, change to the directory containing the migration_inventory tool. 2.
To stop transmitting data to IMPAX 6.2 or 6.3 1. Open the Windows Administrative Tools and select Services. 2. Right-click the DICOM Service Class Provider service and select Properties. 3. To change the Service status, click Stop. 4. From the Startup type list, select Disabled. 5. To close the Properties dialog, click OK. 6. Launch the 6.2 or 6.3 Administration Tools and log in as user service. 7. On the Daily tab, select Job Manager. 8. Monitor each Transmit queue and wait for all outgoing jobs to finish.
Storing unarchived studies When no studies are returned by the Failed verification query, archive all remaining studies. To store unarchived studies 1. In the 6.2 or 6.3 Administration Tools, on the Daily tab, click Study Manager. 2. From the location list, select Cached (or another value that will return the unarchived studies). 3. Set other search criteria to Any value (or set to appropriate values). 4. Click Refresh. 5. In the search results, select the studies to archive.
6. Check the Delivery Date Time column for jobs that are not scheduled to run until later. If any exist, schedule these jobs to complete now, using the Set Delivery Date and Time option at the top. 9. Emptying all queues Monitor the Job Manager to make sure that all the queues are empty and that all jobs are completed prior to migration. To empty all queues 1. In the 6.2 or 6.3 Administration Tools, on the Daily tab, select Job Manager. 2.
12. Deleting old log files Important! This topic applies only when upgrading an existing server. On the server being upgraded, remove any old log files to ensure that all future log information is a result of the migration procedure. To delete old log files 1. On the server to be upgraded, open a command prompt. 2. Change to the C:\mvf\bin\ directory. 3. Run stopall.bat. 4. For future reference, copy all files in C:\mvf\data\logs\ to a backup location. 5. Delete all the files from C:\mvf\data\logs\. 13.
Upgrading an existing AS300 Database Server to IMPAX 6.4 2 When keeping the existing Database Server and upgrading it to IMPAX 6.4, the upgrade and migration procedure is more complex, but you do save on the cost of new hardware. If you are replacing the existing Database Server with a new server, instead perform the Replacing an existing Database Server with a new station (refer to page 31) tasks. 1.
4. Open a command prompt. 5. To extract the files, type the following: WindowsServer2003-KB914961-SP2-XXX-LLL.exe /X:[Path] If the distribution folder is local, you do not have to specify the path. 6. To install the service pack from a remote shared distribution folder, run Update.exe. If the distribution folder is local, Update.exe starts automatically. 7. Follow the instructions in the Setup Wizard. 8. When the installation process is complete, restart the computer.
2. Change to the C:\mvf-mig6\bin directory. 3. Type database-upgrade-script.bat -v {62 | 63} 4. At the prompt Ready to upgrade database from current system version . Do you want to proceed [q to quit]? Verify that the version_number listed is correct—for example, that it says 62 if upgrading from IMPAX 6.2. If so, press Enter to continue. If the version is incorrect, type q and press Enter, then repeat the previous step with the correct version number specified. 5.
Upgrading SQL Server 2000 to SQL Server 2005 Before starting the upgrade from SQL Server 2000 to SQL Server 2005, ensure that you know what the SQL Server 2000 sa database password is, as you must enter it as part of the upgrade. Also ensure that you are logged into Windows as an administrator-level user. Upgrading to SQL Server 2005 requires running the same installer used for a new install of SQL Server 2005. To upgrade SQL Server 2000 to SQL Server 2005 1.
10. On the Existing components screen, select the checkbox of your currently installed version of SQL Server. Click Next. 11. On the Upgrade Logon Information screen, select SQL Server Authentication Mode. 12. In the Username field, type sa. 13. In the Password field, type the sa password. Click Next. 14. On the Service Account screen, select Use the built-in System account. This screen may vary, depending on the installed instances and components. 15.
19. On the Ready to Install screen, review the components to be installed and ensure that they are correct. The following components should be listed: • SQL Server Database Services (Upgrade) • Integration Services • Client Components 20. If the listed components are not correct, return to the Components to Install screen and select the correct items. Once the components are correct, click Install. 21. Wait while the components are upgraded or installed, then click Next. 22.
3. On the Welcome screen of the Setup window, click Next. 4. On the License Terms screen, select I accept the agreement and click Next. 5. On the Feature Selection screen, accept the default selections and click Next. 6. On the Authentication screen, select the Apply selection to all instances checkbox. 7. From the Authentication list, select SQL Authentication. 8. In the User Name field, type sa. 9. In the Password field, type the sa password. Click Next. 10.
6. Recording the names of previously installed IMPAX AS300 software packages Before uninstalling the AS300 server packages for the previous release of IMPAX, record the package names. It is useful to know these before installing IMPAX 6.4. To record the names of previously installed IMPAX AS300 software packages 1. On the Windows server to upgrade, select Start > Run. 2. In the Open field, type regedit and click OK. 3. In the Registry Editor, select HKEY_LOCAL_MACHINE\SOFTWARE\Mitra Imaging Inc.
Optional packages Location in HKEY_LOCAL_MACHINE\SOFTWARE\ MVFpap Mitra Imaging Inc.\MVF PACS Archive Provided vnumber Make note of the installed packages so that you can select the same ones when installing IMPAX 6.4. 7. Uninstalling the previous IMPAX software packages If you are upgrading an existing server, before installing the IMPAX 6.4 AS300 server packages, uninstall the previous-version IMPAX packages. To uninstall the previous IMPAX software packages 1. Open Control Panel. 2.
9. 32-bit AS300 installer packages reference The standard (32-bit) IMPAX AS300 installer groups the packages to install under four sections: default, database, archive, and optional. The following tables explain each package. Default package names Purpose MVFCore Installs the DICOM Services for IMPAX and contains several core Windows services and database tables used by IMPAX. MVFCache Installs the DICOM SCU and autopilot services used by IMPAX and spftpd services.
Only one of the two Database Packages can be installed. Install these only on single-host servers or dedicated Database Servers. Archive package names Purpose MVFjdlt Installs the jukebox DLT (digital linear tape) package. For upgrades only. Not supported for new installations. MVFjdvd Installs the jukebox CD-R/DVD-R package. MVFhsm Installs the HSM package. MVFsdlt Installs the non-jukebox DLT or single DLT package. For upgrades only. Not supported for new installations.
Optional package names Purpose This feature is not required and we recommend that this package not be installed. MVFpap Installs the PAP package. A PACS Archive Provider (PAP) acts like a Service Class Provider (SCP) by receiving studies and allows sites to have their studies mirrored at another site through PACS Store and Remember archiving. This mirroring protects against data loss and enables studies at one PACS to be viewed at another.
For a single-host server, install all default packages except, potentially, the MVFocr package. For a dedicated Database Server, the MVFNetworkGateway package is not required, but can be installed. 6. Select the Database Packages label. Because Oracle is not supported for upgrades, clear the Oracle Server Extension checkbox and select the SQL Server Extension checkbox. 7.
8. Select the Optional Packages label, then select the checkboxes of any optional packages that should be installed. • Select the MVFCurator and MVFcdexport checkboxes only if intending to install the Curator and CD Export server components on the Database Server rather than on a dedicated Curator server. • Select the MVFScavenger and MVFpap packages only if the server is being used for archiving. • Clear the MVFchangeaccepter checkbox. • Do not select the MVForadg checkbox. 9. Click Next.
10. If a Network Gateway package was installed, browse to the location of the MVF license file and click OK. If the mvf.lic file is not located in C:\mvf, the file is copied to that location. A dialog informs you of the success of the copy task. 11. If an Archive package was installed, browse to the location of the archive license file and click OK. If the mvfarch.lic file is not located in C:\mvf, the file is copied to that location. A dialog informs you of the success of the copy task. 12.
CAUTION! The mvf.portable.psd file contains sensitive information. To ensure that the security of the system is maintained, delete the password file after all required components are installed. 12. Updating the SQL Server registration To correctly register SQL Server with the Database Server software and set up permissions within SQL Server, update the SQL Server registration. To do so, you must be logged into Windows as an administrator-level user. To update the SQL Server registration 1.
Replacing an existing Database Server with a new station 3 When replacing the existing Database Server with a new one, you install all external and IMPAX 6.4 software in advance, during the pre-migration period, saving you considerable time during the migration weekend. 1. Upgrading the IMPAX database schema to IMPAX 6.4 Upgrading the 6.2 or later database schema to 6.4 requires the IMPAX Migration Tools. For Migration Tools installation instructions, refer to the “Installing the IMPAX 6.
Ready to upgrade database from current system version . Do you want to proceed [q to quit]? Verify that the version_number listed is correct—for example, that it says 62 if upgrading from IMPAX 6.2. If so, press Enter to continue. If the version is incorrect, type q and press Enter, then repeat the previous step with the correct version number specified. 5. Respond appropriately to other prompts that appear. The database is upgraded. 2.
4. Configure the General and Options tabs according to your preferences for items such as the type of backup, the destination, and whether to overwrite or append to the media. 5. To start the backup, click OK. 6. Exit the SQL Server Enterprise Manager. 4. Restoring the upgraded database on a new Database Server CAUTION! Perform this task only when replacing an existing server with a new server. Be very careful not to delete any live database files.
b. Open a new query window. c. Select File > Open and browse to C:\mvf\etc. d. Select recreate_user_mvf.sql and click Open. e. To execute the script, press F5 or click Execute. 5. Generating the portable password file To install the other components, you must generate a password file from the Database Server to synchronize passwords between the components. The file contains all of the user IDs and passwords for all default IMPAX users.
Upgrading AS300 Network Gateway and Archive packages to IMPAX 6.4 4 These procedures are relevant when: • Upgrading the site in a multi-host or mixed-configuration. and • Upgrading existing AS300 Archive Server or Network Gateway server stations to IMPAX 6.4, rather than replacing them with new stations. Note: If upgrading the site in a single-host configuration or replacing existing stations with new ones (on which IMPAX 6.
2. In the Open field, type regedit and click OK. 3. In the Registry Editor, select HKEY_LOCAL_MACHINE\SOFTWARE\Mitra Imaging Inc. and HKEY_LOCAL_MACHINE\SOFTWARE\Mitra and make note of the installed packages (refer to page 22). 2. Uninstalling the previous IMPAX software packages If you are upgrading an existing server, before installing the IMPAX 6.4 AS300 server packages, uninstall the previous-version IMPAX packages. To uninstall the previous IMPAX software packages 1. Open Control Panel. 2.
10. Select the SQL Server Authentication option. 11. In the Login ID and Password fields, type the username and password for the mvf user. Ensure that all systems have the same username and password for the Database Server. 12. Click Client Configuration. 13. In the Add Network Library Configuration dialog, select TCP/IP. Click OK. 14. Click Next. 15. Select the Change the default database to checkbox. 16. From the list, select mvf. Click Next. 17. Clear the Perform translation for character data checkbox.
6. Clear the Database Packages checkbox. 7. For Archive Servers, select the Archive Package label, then select the checkbox of the archive package to install. MVFhsm is selected by default. For dedicated Network Gateway servers, clear the Archive Packages checkbox. 8. Select the Optional Packages label. 9. Select any optional packages that should be installed, and clear the other checkboxes. AS300 Upgrade Guide—IMPAX 6.2 or later to IMPAX 6.
Unless intending to use this station as a Curator and CD Export server, clear the MVFCurator and MVFcdexport checkboxes. MVFCompressor, MVFScavenger and MVFPap may be useful on an Archive Server. Clear the MVFchangeaccepter checkbox. Do not select the MVForadg package. This is only for Database Servers using Oracle Data Guard. 10. Click Next. 11. If installing a Network Gateway or Archive Server/Network Gateway combination, browse to the location of the MVF license file and click OK. If the mvf.
After the server restarts, log into Windows as an administrator-level user. 5. Installing and configuring Store and Remember archiving Important! This topic applies only to an Archive Server or to the Archive component of a single-host server (including standalone with archive and single-server configurations). Some sites may want to have their studies mirrored at another site through PACS Store and Remember archiving.
Upgrading the other IMPAX 6.4 components 5 To complete the migration to IMPAX 6.4, the Application Server, Curator, and Clients must be upgraded, and a few configurations are required. 1. Upgrading the Application Server All Application Servers must be upgraded to IMPAX 6.4. For AS3000 (Solaris server) sites, before upgrading the Application Server, ensure that you have uninstalled the previous version of the Oracle Client and installed and configured the Oracle 10g Client.
9. On the Items to Backup screen, select the folder containing the ADAM data as well as the World Wide Web Publishing Service folder. Click Next. The default location for the ADAM database is C:\Program Files\Microsoft ADAM\AgfaHealthcare. 10. If backing up to a tape drive, under Backup media type, select the tape drive, and in the backup media area, click New media. Click Next. or If backing up to any other media type, select the location where the backup is to be saved, and type a name for the backup.
13. In the Confirmation dialog, click OK. 14. In the Maintenance Complete dialog, click Finish. 15. Under Currently installed programs, select IMPAX Server Knowledge Base. 16. Click Change/Remove. 17. In the Confirmation dialog, click OK. 18. In the Maintenance Complete dialog, click Finish. Uninstalling IMPAX 6.3 documentation All IMPAX 6.3 documentation can be uninstalled at once. To uninstall the IMPAX 6.3 Knowledge Bases and guides 1. Open Control Panel. 2. Select Add or Remove Programs. 3.
2. Navigate to the appserver folder, which contains the Business Services software. 3. Run agfa impax business services setup.exe. 4. On the Installing Visual JSharp page, click OK. Tip: If Visual JSharp package is already installed on the machine, the installation package skips the installation. In this case, this step does not apply. 5. On the Welcome screen, click Next. 6. On the license agreement screen, select I accept the terms in the license agreement. Click Next. 7.
Installing the IMPAX documentation The IMPAX 6.4 documentation is installed on the Application Server. CAUTION! Before installing the IMPAX 6.4 documentation, ensure that you have uninstalled any past IMPAX documentation. The 6.4 documentation installer will not prompt you to uninstall the old documentation, and having both sets installed will prevent the 6.4 documentation from working correctly. IMPAX is shipped with three sets of documentation: the IMPAX 6.
Running Healthcheck to check the status of web services Healthcheck checks the status of each web service running on the Application Server. When you run Healthcheck, it attempts to connect to each of the web services. If it succeeds, Healthcheck sets the status to Passed. If Healthcheck fails, the status is set to Failed. The comment field indicates where the failure occurred. Note: Healthcheck verifies only installed services, and it does not indicate if a service is not installed.
6. To check the status of the web services again, in Internet Explorer, click Refresh. 2. Configuring the Audit Record Repository database connection After installing or upgrading the database and adding an Audit Record Repository (an audit server such as Audit Manager), you must update certain entries in the database to ensure that auditing functions correctly. If not using an Audit Record Repository, this task is not required. To configure the Audit Record Repository database connection 1.
3. Under Currently installed programs, select Agfa IMPAX 6.2 version or Agfa IMPAX 6.3 version . 4. Click Change/Remove. 5. When prompted, type your name (minimum three characters). 6. In the Confirmation dialog, click OK. 7. In the Maintenance Complete dialog, select Yes, I want to restart my computer now, then click Finish. When the server restarts, log into Windows as an administrator-level user.
8. Select the Optional Packages label and select the appropriate packages. MVFCurator must stay selected. MVFcdexport is also required except, perhaps, on slave Curators. Normally, no other optional packages are required, so you can clear other selected checkboxes. In particular, clear the MVFchangeacceptor checkbox and do not select the MVForadg checkbox. 9. Browse to the location of the portable password file and click OK. 10.
UPDATE mvf_ts_config SET execution_time = 'NEVER' WHERE module_name = 'CREATE_CC_CONFLICT_JOB' 4. To refresh cached data, type UPDATE map_ref_count SET ref_count = ref_count + 1 WHERE name = 'DATABASE_UPDATE_REF' 5. Disabling tx object creation Important! This topic applies only when the IMPAX site archives to an IMPAX Data Center. When IMPAX 6.
6. Changing the SQL Server administrator (sa) password Important! This topic applies only to Database Servers (including single-host, standalone, and single-server configurations). The IMPAX installation changes the default sa password to a randomly generated string of characters. This greatly increases the security of the system; however, the password can still be obtained through other methods.
To uninstall the IMPAX 6.2 or later Client software 1. If running, log out of the IMPAX Client and close the Login window. 2. Open Control Panel. 3. Select Add or Remove Programs. 4. Under Currently installed programs, select AGFA IMPAX Client build_number . 5. Click Remove. 6. When asked to confirm the removal, click Yes. A Preparing to remove dialog opens, then the IMPAX Client software is uninstalled.
Note: If you do not have a live Internet connection, the downloading will not work. Instead, install the Microsoft .NET Framework 1.1 and MDAC 2.8 from the Client Installer server (https://install_server_name/clientinstaller/redist/dotnetfx.exe and mdac_typ.exe). For the .NET Framework 1.1 SP1 install, after the download, if prompted to start the installation, click OK. If prompted, restart the computer. For the Hotfix install, after the download, if prompted to start the installation, click OK.
13. On the InstallShield Wizard Completed screen, click Finish. The IMPAX Client software is installed. You do not have to restart the computer. 8. Restarting antivirus software If you have antivirus software installed and have halted any scan jobs, restart the antivirus services. To restart antivirus software 1. On a Windows server where scanning was stopped, launch the antivirus software. 2. Start the scan operation according to the vendor’s instructions. AS300 Upgrade Guide—IMPAX 6.
Post-migration checking and stabilization 6 Some tasks are performed after the 6.4 migration is complete. 1. Testing the installed software After installing the new version of IMPAX, perform certain tests to verify that the installation was successful. To test the installed software 1. On the IMPAX Database Server, run the Administration Tools and ensure that you can log in using the administration password. 2. On the Application Server, open a web browser and connect to http://localhost.
3. Restarting Connectivity Manager queues If Connectivity Manager is currently deployed, and you have stopped any queues, use the Queue Manager to restart them. Messages in a queue that is stopped are not processed and sit in the queue. Once the queue is restarted, messages are processed. To restart Connectivity Manager queues 1. In the Connectivity Manager Service Tools, click Queue Manager. 2.
5. Comparing pre- and post-migration snapshots Open the report file that contains the pre- and post-migration snapshot information. Compare the preand post-migration information. Ensure that all expected studies, objects, stations, and DICOM printers are still listed. 6.
12. Select Impax Permit Action and click Apply. Click Close. 13. In the Impax Server Policy Properties dialog, scroll down and verify that you see the Time Synch policy. Click OK. Synchronizing a Windows 2003 server to an external time source Synchronize the Windows 2003 servers on your network to an external time source to ensure that image data streaming operates correctly. CAUTION! Serious problems might occur if you modify the registry incorrectly.
9. Exit the Registry Editor. 10. To stop and restart the Windows Time server, at a command prompt, type net stop w32time && net start w32time. It may take up to an hour for this to take effect. For more information, refer to the Microsoft Knowledge Base article KB 816042. Synchronizing a Windows 2003 server to an internal time source Synchronize the Windows 2003 servers on your network to ensure that image data streaming operates correctly.
2. Select Date and Time. 3. Switch to the Server Internet Time tab. 4. In the list, type or select the time server to synchronize with. Synchronizing with a time server when the IMPAX computer is a member of a domain To ensure that image data streaming operates correctly when the IMPAX computer is a member of a domain, use the synchronization feature built into the operating system. To synchronize with a time server when the IMPAX computer is a member of a domain 1. Open a command prompt. 2.
8. Remove the IMPAX AS300 CD. 8. Running PSARMT to mark studies as PACS archived Note: If the site does not use an external PACS, you can skip this topic. The PACS Store and Remember Migration Tools enable a site to migrate from an external PACS system to IMPAX by allowing the external system to act as an archive server to IMPAX. Run these commands on the migrated IMPAX Database Server.
Checking the integrity and identity of cache files against the IMPAX AS300 database You can use the cache check and repair tools to check the integrity and identity of cache files against the IMPAX AS300 database. To check the integrity and identity of cache files against the IMPAX database 1. In a command prompt, change to the location of the cache check and repair tools. 2.
A report and additional diagnostic messages are written to the log file. For example, run: mvf-clean-cache -m move_cmds.sh /cache4/mvfcache Moving images from a cache directory You can move the images identified by the mv_command_file, used to identify problem files. To move images from a cache directory 1. Run the mv_command_file . For example, run move_cmnds.bat.
10. Uninstalling the IMPAX Migration Tools from a Windows computer Once all migration tasks and post-migration checks are completed, you must uninstall the IMPAX Migration Tools from all Windows-based computers on which they are installed. This is a legal requirement. To uninstall the IMPAX Migration Tools from a Windows computer 1. Open Control Panel. 2. Select Add or Remove Programs. 3. Under Currently installed programs, select IMPAX 6.
12. Log into an IMPAX 6.4 Client as an administrator user and follow step 11 on it. All components of the Cross-Cluster Dictation Interlock tool are now removed. AS300 Upgrade Guide—IMPAX 6.2 or later to IMPAX 6.
Troubleshooting IMPAX A As you install or upgrade IMPAX servers, you may encounter various installation and configuration problems. Troubleshooting: IMPAX Client slow and erratic post-upgrade Issue After upgrading, IMPAX Client display is very slow at a site using McAfee Antivirus software. Details A McAfee Antivirus setting called Buffer Overflow Protection (BOP) can cause this behavior. Solution Disable BOP in McAfee.
Solution To back out of the Application Server upgrade 1. Back up the web.config files and note the location of the current web.config files. 2. On the Application Server, open Control Panel. 3. Select Add or Remove Programs. 4. Remove AGFA IMPAX Business Services and IMPAX Installation Server. Do not remove ADAM. 5. Install the IMPAX 6.2 or 6.3 version of the Server, Application Server, and Client Installation Server software.
Troubleshooting: How do I determine which ADAM instance is the Schema Master? Issue How do I determine which ADAM instance is the Schema Master? Solution If the site uses other dedicated Application Servers, you can determine which one is running the master ADAM instance to find out which is the Schema Master: 1. Select Start > Run and type mmc. 2. In the Console dialog, select File > Add/Remove Snap-in. 3. In the Add/Remove Snap-in dialog, click Add. 4.
Cache check tools reference B IMPAX 6.4 includes four tools designed to ensure the integrity of the IMPAX cache directory. These tools check the cache directory, repair the cache directory, and then provide a 'Loss Report' for files missing from the cache. mvf-check-cache This command checks that all the DICOM object files registered in the database for a particular cache volume actually exists in the cache.
may be high but mvf-clean-cache displays the amount of memory required and the operator can add more virtual memory if necessary. mvf-clean-cache does not access the contents of the cache files. It works by examining the file names and reporting the problem. A copy of the report and additional diagnostic messages are written to the log file. Since mvf-clean-cache may be run on a live system, new files (less than one hour old) are skipped. Thus, temporary files created by the SCP are ignored.
Marking mode The default mode for the tool. In marking mode, the tool checks all the caches on the local server for the presence of the DICOM object files that the database says should be present. For missing files, the "visible" field in the database osr_location table is set to 'C'. (Normally this field contains the value 'T' for true, or 'F' for false). Changing this field makes these file locations invisible to the product software.
External software licenses C Some of the software provided utilizes or includes software components licensed by third parties, who require disclosure of the following information about their copyright interests and/or licensing terms. Sonic Solutions Contains AuthorScript™ DVD creation technology licensed from Sonic Solutions®. © 1999-2004 Sonic Solutions. All rights reserved. Monotype Imaging, Inc. End User License Agreement Read this license agreement carefully before using your Agfa software product.
of such static graphic image or embedded document. Internal Use shall not include any use of this Agfa software product by entities that are neither your authorized employees nor your authorized agents. All such employees and agents shall be notified by you as to the terms and conditions of this End User License Agreement and shall agree to be bound by it.
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3.
• Tar. To view the Tar source code, refer to http://www.cygwin.com. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1.
machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, 3. Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.
reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. Sun Microsystems Sun, Sun Microsystems, the Sun Logo, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Oracle Corporation Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Glossary A C Administration Tools cache Administration Tools control the configuration and management of the entire IMPAX cluster. The Administration Tools are a Java-based application that run in a web browser. Temporary storage area for data on a computer’s local or external hard drives. APIP Agfa PACS Interface Protocol. archive A physical device for long-term storage and retrieval, such as DVD-R or DLT. An archive can be set up in a jukebox or non-jukebox configuration.
exchange information or images with other systems. H high availability With a high-availability solution, a site is protected against system downtimes, either planned or unplanned. Redundant servers are put in place that can take over functionality should the primary server become unavailable. HIS Hospital Information System. The database used by a hospital to manage patient information and scheduling.
modality An imaging discipline, such as CT, or a device that gathers digital information, such as digitizers for X-ray film, MRI scanners, and CR devices. differs from an SCP in that the PAP can automatically register a study as PACS archived if the study originates from a source that the PACS stores to and remembers from, without having to queue the study for archiving back to the source. The PAP can also parse the private tags of the incoming DICOM objects to determine HIS verification and study status.
permissions, licenses, and preferences from their role. V volume A volume refers to the division of data on the media. For example, if a tape has two sides, each side is referred to as a separate volume. W wizard Wizards are used to automate processes. Wizards perform a predetermined sequence of actions after they are selected and applied. AS300 Upgrade Guide—IMPAX 6.2 or later to IMPAX 6.
Index .NET installing Framework .......................... 52 A accounts Client administration .......................... 55 ADAM administrators .................................... 67 ADSI ................................................... 67 backing up .......................................... 41 upgrading data ................................... 43 adding SQL Server entry ................................ 36 Administration Tools ................................. 55 installing package ..................
uninstalling software .......................... 51 upgrading ........................................... 41 clocks synchronizing .................... 57, 58, 59, 60 closing archive volume ................................... 12 comparing snapshots ............................................ 57 compressor package installation ............... 25 configuring caches .................................... 48 connecting Audit Record Repository to database ... 47 components to database .....................
hardened IMPAX system ............................ 57 Healthcheck .............................................. 46 HIS verification ......................................... 11 Hotfix, .NET Framework ........................... 52 HSM archives installing package ............................... 25 I IE See Internet Explorer images lost ..................................................... 61 importing password file ...................................... 37 internal time source synchronizing to ............
upgrading Client ................................. 41 P packages, AS300 installing on Archive Server or Network Gateway ............................................. 37 recording ...................................... 22, 35 uninstalling ............................. 23, 36, 47 upgrading ........................................... 26 PACS Archive Provider See PAP PACS Store and Remember archives .......... 40 running PSARMT ................................ 61 PAP installing and configuring ................
supported migration paths ................... 8 Service Pack .NET Framework ................................ 52 See SP services stopping SQL Server ........................... 20 Study Status Relay .............................. 64 setting up See configuring site migration .............................................. 8 slave Curators ........................................... 47 Snap-in ..................................................... 68 snapshot of system .........................
synchronizing to internal time source .. 59 Time Service, configuring ....... 57, 59, 60 upgrading browser ............................. 16 upgrading Windows 2003 ................... 15 Windows authentication ........................... 52 AS300 Upgrade Guide—IMPAX 6.2 or later to IMPAX 6.
