AS300 Upgrade Guide IMPAX 5.2 or 5.3 to IMPAX 6.5.3 Upgrading an IMPAX 5.2 or 5.3 Cluster to an IMPAX 6.5.
Copyright information © 2012 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. CAUTION! U.S. Federal law restricts this device to sale by or on the order of a physician. Trademark credits Agfa and the Agfa rhombus are trademarks or registered trademarks of Agfa-Gevaert N.V., Belgium or its affiliates.
The information in this publication is subject to change without notice. 2012 - 9 - 17 Manufacturer’s responsibility The manufacturer, installer, or importer will be responsible for the safety, reliability, and performance of the equipment only if: • Installation, modifications, adjustments, changes, or repairs are performed by suitably qualified service personnel. • The electrical installation of the site in which the equipment is used is according to an applicable safety standard (UL, CSA, or IEC/CDE).
. Send the email to doc_feedback@agfa.com. AS300 Upgrade Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
Contents 1 Getting started 9 Valid IMPAX upgrade paths.....................................................................................................9 Related documentation: IMPAX upgrades.............................................................................10 2 Preparing to upgrade 11 Gathering information and equipment....................................................................................11 IMPAX 5.2 or 5.3 upgrades: Necessary information and equipment......................
Migrating data from the training server...................................................................................32 Taking the training server offline...................................................................................32 Backing up the training server database.......................................................................33 Installing Oracle 10.2.0.1 OLE drivers on the Application Server.................................33 Migrating worklist and report data....................
Installing the archive license key on a Windows server................................................64 Testing the installed software.................................................................................................64 Restarting an archive queue...................................................................................................65 Restarting Connectivity Manager queues..............................................................................
IMPAX Client: Hardware requirements.........................................................................96 IMPAX Client: External software requirements.............................................................97 Appendix E: External software licenses 99 Cygwin....................................................................................................................................99 Editline 1.2-cstr..........................................................................................
Getting started 1 To successfully upgrade IMPAX, servers must meet certain hardware and software requirements. Valid IMPAX upgrade paths (Topic number: 6607) Sites can upgrade to IMPAX 6.5.3 from any of these versions of IMPAX (supported versions include any applicable SUs): • IMPAX 5.2.5—hereafter referred to as IMPAX 5.2 • IMPAX 5.3.1 and 5.3.2—hereafter referred to as IMPAX 5.3 • IMPAX 6.2.1—hereafter referred to as IMPAX 6.2 • IMPAX 6.3.1—hereafter referred to as IMPAX 6.3 • IMPAX 6.4 • IMPAX 6.
Important! We recommend checking the migration log file after each leg of an upgrade before moving on to the next leg. For AS300 (Windows) upgrades, also consider the following: • Since all IMPAX 6.5.3 AS300 servers and Application Servers must be installed on Windows Server 2008 R2 SP1, all upgrades to IMPAX 6.5.3 require forklift upgrades to new or restaged hardware. All AS300 servers and Application Servers in a cluster must use the same operating system.
Preparing to upgrade 2 Important! Before proceeding with the upgrade of the AS300 server components, ensure that you have completed the tasks outlined in the AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3. You must perform certain preparatory tasks before upgrading to an IMPAX 6.5.3 AS300 configuration. These tasks include taking a system snapshot, stopping the transmission of data to the previous release of IMPAX, and emptying and halting queues.
Equipment and information for upgrading existing IMPAX 5.2 or 5.3 stations Notes As upgrading IMPAX AS300 servers to IMPAX 6.5.3 necessitates forklift upgrades, the new or restaged servers should be prepared accordingly. If having to upgrade to SQL Server 2008 R2 SP1, you must obtain the SQL Server 2008 R2 software and service pack. (SQL Server 2008 R2 is not distributed with IMPAX but is available from the Agfa Parts Center.
To run the Cross-Cluster Dictation Interlock tool 1. On the 6.5.3 Application Server where the Relay service is running, open a command prompt. 2. Type the following command: net start StudyStatusRelayService 3. Exit the command prompt. 3. Taking a system snapshot (Topic number: 7613) Before upgrading to IMPAX 6.5.3, use the migration_inventory tool to capture the current state of the system for later comparison.
5. Stopping Connectivity Manager interfaces (Topic number: 113766) During the IMPAX upgrade, you can prevent the loss of clinical patient updates from hospital information systems by stopping data bound for the Connectivity Manager, or by stopping the Connectivity Manager’s outbound queues. The preferred method is to stop inbound interfaces, which prevents the Connectivity Manager from receiving incoming messages.
Connectivity Manager outbound message queues must be configured with the new server settings before messages are added to the queues. Consult a Connectivity Manager integrator to create a device for the destination IMPAX server. Report updates can be sent to only one IMPAX server, after all reports have been copied to that server. 7.
9. Archiving remaining unarchived studies (Topic number: 7742) Use the information from the latest report on archiving studies to identify remaining unarchived studies (for details, refer to the appropriate version of the IMPAX Preparing to Upgrade Guide). You must store these studies to the archive. 1. Verifying unverified studies (Topic number: 58295) Before archiving studies, verify all unverified studies. To verify unverified studies 1. In the Service Tools, on the Daily tab, click Study Manager. 2.
6. Click Store to Archive. 7. To update the status of the selected studies, click Refresh. 8. Ensure that all studies are archived. Tip: To store unarchived studies, you could also use the Migration Toolbox and run the study_archive_report tool. For details, see “Running an initial report on study archiving status” (topic number 6630) in the AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3 or the AS3000 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3.
12. Deleting cache locations for studies (Topic number: 7707) If you are replacing the 5.2 or 5.3 servers and are not restoring the files in the cache directory after the upgrade, to prevent database inconsistencies, remove all database references to images in cache. You must also do this for studies in Client caches, because IMPAX 6.5.3 no longer supports cached Clients—only cacheless and standalone Clients.
13. Stopping antivirus software (Topic number: 7616) If you have antivirus software installed on any Windows-based servers, ensure that no scan jobs are running that would interfere with the upgrade process. Stop the antivirus services. To stop antivirus software 1. On a Windows server to upgrade, launch the antivirus software. 2. Halt the scan operation according to the vendor’s instructions. 14.
15. Deleting old log files (Topic number: 7706) Important! This topic applies only when upgrading an existing server (in-place upgrade). On the server being upgraded, remove any old log files to ensure that all future log information is a result of the upgrade 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.
2. Select Add or Remove Programs. 3. Select IMPAX Client Knowledge Base 5.2 or IMPAX Client Knowledge Base 5.3 and click Change/Remove. 4. In the Confirmation dialog, click OK. 5. If also uninstalling the IMPAX Server Knowledge Base, in the Maintenance Complete dialog, select No, I will restart my computer later. Otherwise, select Yes, I want to restart my computer now and click Finish. 6. If you restarted the computer, log into Windows as an administrator-level user. 7.
Performing a forklift upgrade of an AS300 SQL Database Server to IMPAX 6.5.3 3 When replacing the existing Database Server with a new one, you install all external and IMPAX 6.5.3 software in advance, during the preparing to upgrade period, saving you considerable time during the upgrade weekend. For more details, refer to the AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3. 1. Staging the new IMPAX 6.5.
To stage the new IMPAX 6.5.3 Database Server 1. Install Windows Server 2008 R2 SP1. For details, see “ Installing and configuring Windows Server 2008 R2” (topic number 141323) in the IMPAX 6.5.3 AS300 Installation and Configuration Guide. 2. Install SQL Server 2008 R2 SP1. For details, see “Installing SQL Server 2008 R2” (topic number 141825) in the AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3.
6. Select the Database Packages label. 7. Clear the Oracle Server Extension checkbox and select the SQL Server Extension checkbox. 8. For a dedicated Database Server (no archive), or if using PACS Store and Remember archiving only, clear the Archive Packages checkbox. 9. Select the Optional Packages label, then select the checkboxes of any optional packages that should be installed.
14. On the Summary screen, to continue the installation, click Next. 15. After all the packages have been installed, click Yes, I want to restart my computer now. If you are not prompted to restart the computer, manually restart it. After the server restarts, log into Windows as an administrator-level user. 3. Backing up the SQL 2000 database (Topic number: 11497) Back up the existing SQL Server database so that you can restore it onto the new IMPAX 6.5.3 Database Server.
4. Restoring the database on the new SQL Database Server (Topic number: 7627) CAUTION! Perform this task only when replacing an existing server with a new server. Be very careful not to delete any live database files. Perform this procedure only on a new server that has not had any clinical use, even as a training server. Do not perform this procedure on any production, training, or traveling servers. When replacing the existing server with a new server, you first install the IMPAX 6.5.
g. To close the Properties dialog, click OK. 4. If you are restoring from tape, insert the backup tape into the tape drive. 5. In the Explorer window of the SQL Server Management Studio, expand server > Databases where server is the name of the SQL Server that IMPAX is running under. 6. Right-click Database and select Restore Database. 7. In the Destination for restore section, in the To database field, type mvf. 8.
f. World Wide Web Publishing 5. Upgrading the IMPAX database schema to IMPAX 6.5.3 (Topic number: 60244) Important! Only specific IMPAX upgrade paths are supported and it may not be possible to upgrade certain versions or SUs. More information is provided in the IMPAX 5.x–6.x Service Update and Hot Fix Migration Paths spreadsheet in the Additional documents section of the IMPAX Knowledge Base > Main Knowledge Base Page. Upgrading the database schema to 6.5.3 requires the IMPAX Migration Tools.
If running this command on a server that will be replaced, and that does not have .NET installed, you will get a block_named_pipes.exe: not finding the dynamic link library mscoree.dll error. Ignore this error and continue with the upgrade, since the replacement server will be running Windows 2008, which installs .NET automatically. 5. At the prompt Ready to upgrade database to version 6.5.3. Do you want to proceed [y, n]? Type y to continue. 6.
3. Ensure that Migration Complete Successful appears at the end of the log file. If this message does not appear, review the rest of the log file to see where the upgrade failed. Solve the problem, then rerun the upgrade script. 7. Backing up the SQL Server 2008 R2 database (Topic number: 147840) After upgrading SQL Server, to guard against information loss, manually back up the database again.
backup database database_name to device_name where database_name is the name of the database to back up and device_name is the logical or physical name of the tape or disk device. 8. Scheduling additional SQL database backup jobs (Topic number: 46983) Note: Ensure that you are logged in using the AgfaService account; you cannot log into SQL Server Management Studio using the Administrator account. This procedure applies to SQL Server 2008 R2.
10. To apply the changes, click OK. 11. If you are configuring a disk backup: a. Switch to the Steps tab. b. Select Edit. c. In the Command field, type exec sp_backup_database @dump_device_name='disk_backup1'. d. To apply the change, click OK. 12. To close the Job Properties dialog, click OK. 13. Exit the SQL Server Management Studio. 9.
e. Exit the command prompt. 9. To prevent Client interaction, open the Windows Administrative Tools and select Services. Stop the World Wide Web Publishing Service (IIS). 2. Backing up the training server database (Topic number: 10241) Before migrating data from the training server system, back up the database.
7. In the Available Product Components dialog, select Oracle Objects for OLE 10.2.0.1.0, Oracle ODBC Driver 10.2.0.1.0, and Oracle Provider for OLE DB 10.2.0.1.0 only. 8. Click Next. 9. Click Next again, then click Install. After installation, create a tnsnames.ora file in the C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN directory and add the following code to the file: mvf_ts.world = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = impax.
To migrate worklist and report data 1. On the Application Server, launch the Migrate training/traveling server data tool by running the C:\mvf-mig6\MigrateTRServer\MigrateTRServer.exe file. 2. If migrating worklist data, select the Migrate Worklist Data checkbox. 3. If migrating report data, select the Migrate Report Data checkbox. CAUTION! This utility overwrites reports on the destination server.
A DTSResults dialog opens showing the result of the data migration from the training to the production server. Scan it for any ERROR messages that you need to resolve. 8. When the migration is complete, close the DTSResults dialog. The Application Server caches the ref for the worklists. To update the refs from the migrated worklists, perform an IISRESET of the Application Server; otherwise, when creating worklists, failures will occur.
Upgrading the other IMPAX 6.5.3 components 4 To complete the upgrade to IMPAX 6.5.3, other components in the cluster such as the Network Gateway and Archive Server must be upgraded. 1. Upgrading AS300 Network Gateways and Archive Servers (Topic number: 60463) If using AS300 (Windows-based) Network Gateways or Archive Servers at your site, these must be upgraded to IMPAX 6.5.3 as well. Note: The IMPAX 6.5.3 AS300 server platform is Windows Server 2008 R2 SP1.
2. Installing and configuring Store and Remember archiving (Topic number: 15546) Some sites may want to have their studies mirrored at another site through PACS Store and Remember archiving. This mirroring protects against loss of data and allows studies from one PACS to be viewed at another. This can be achieved effectively using the PACS Archive Provider (PAP).
Reconfiguring the Application Server and Curator 5 After the Server components are upgraded, you must configure the Application Server to work with the production server instead of the training server and possibly convert the training server into a Curator. 1. Reconfiguring the Application Server (Topic number: 6809) During the preparing to upgrade period, the station intended to serve as the new Application Server for the site is connected to a temporary AS300 single-host station.
User migrations and configurations are performed on the Application Server (as described in the AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3) and worklist and report data can be migrated from the training server (described in Migrating data from the training server (refer to page 32)). After all these migrations are complete, reconfigure the Application Server to connect to the production database instead of the training server. Several steps are required: 1.
To connect to the IMPAX 6.5.3 SQL Server database 1. On the Application Server, select Start > All Programs > Agfa Healthcare > Business Services > Configuration Tool. 2. In the IMPAX Business Services Configuration tool, switch to the Database tab. 3. Under Database Type, select SQL Server. 4. Under Database Connection Settings, type the SQL Server Database Server name. 5. Click Configure ODBC. 6. In the ODBC Data Source Administrator dialog, switch to the System DSN tab. 7. Click Add. 8.
3. Importing the portable password file to the Application Server (Topic number: 6877) You must now import the portable password file generated from the migrated IMPAX 6.5.3 Database Server to the Application Server. To import the portable password file to the Application Server 1. Select Start > All Programs > Agfa Healthcare > Business Services > Configuration Tool. 2. In the IMPAX Business Services Configuration tool, switch to the Security tab. 3. Click Import Password. 4. Navigate to the mvf.portable.
Note: To connect to another type of RIS (local or remote IMPAX RIS or a queryable RIS), refer to instructions in the IMPAX 6.5.3 Application Server Knowledge Base. To connect the Application Server to a non-queryable non-IMPAX RIS 1. Configure the custom RIS mappings in Connectivity Manager. 2. Open the Business Services Configuration Tool. 3. Switch to the Web Services tab. 4. In the Report Info Sources area, click Add. 5.
2. Reconfiguring the Curator (Topic number: 10172) For IMPAX 5.2 or 5.3 upgrades, the Curator station has likely been set up as a single-host station, for use as part of the training server cluster during the preparing to upgrade period. In this case, you must update the AS300 software to remove the packages specific to a single-host server and add the packages needed by a Curator server.
Directory File Description dr2mvf1.dat Oracle Data Guard configuration file (when Data Guard is configured) dr1mvf2.dat Oracle Data Guard configuration file (when Data Guard is configured) dr2mvf2.dat Oracle Data Guard configuration file (when Data Guard is configured) C:\oracle\product\11.2.0\db_1\network\admin tnsnames.ora Oracle naming configuration listener.ora Oracle listener configuration sqlnet.ora Oracle SQL*Net configuration 2.
2. Modifying the IMPAX 6.5.3 AS300 installation packages (Topic number: 7605) If the Curator station was initially staged as an IMPAX 6.5.3 AS300 single-host station during the pre-upgrade period, change the AS300 software installation to remove the database packages and add the Curator packages. To modify the IMPAX 6.5.3 AS300 installation packages 1. Ensure that the training server (the future Curator station) is offline (refer to page 32). 2. Open Control Panel. 3.
Although multiple Curators may be installed, each Curator places web representations of objects into the same web cache. This web cache is owned by the master Curator and is managed by the Autopilot running on the master Curator. 1. Creating a web cache volume (Topic number: 7069) You must manually create cache folders on the system. You can then configure the cache volume in Administration Tools on the Database Server. To create a web cache volume 1.
2. Change to the C:\mvf\bin (Windows) or /usr/mvf/bin/ (Solaris, logged in as root user) directory. 3. To obtain the password for the ImpaxServerUser, type passkey -M QUERY -u ImpaxServerUser (Windows) or ./passkey -M QUERY -u ImpaxServerUser (Solaris) This password is used for the ImpaxServerUser account on the remote machine. 4. If the remote web cache is hosted on a Windows-based system, log into the machine as an administrator-level user.
9. If the names are not found, click Advanced, and click Find Now. Select the ImpaxServerGroup account and click OK. 10. To close the Select Users, Computers, Service Accounts, or Groups dialog, click OK. 11. In the Permissions for Cache Folder dialog, select ImpaxServerGroup. 12. Select the Allow checkbox for the Full Control, Change, and Read permissions. 13. Click OK. 4.
5. Performing other Curator configurations (Topic number: 60423) Depending on site requirements, other Curator configurations may be required, or slave Curators may need to be installed. For details on these, refer to the IMPAX 6.5.3 Curator and CD Export Server Installation Guide and the Curator component of the IMPAX 6.5.3 Server Knowledge Base. AS300 Upgrade Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
Completing the upgrade and migration 6 To complete the migration, Clients need upgrading, and various other configurations must be performed. 1. Configuring the Audit Record Repository database connection (Topic number: 32237) After installing or upgrading the database and adding an Audit Record Repository, you must update certain entries in the database to ensure that auditing functions correctly. To configure the Audit Record Repository database connection 1.
The Application Server must also be connected to the Audit Record Repository. For details, see “Connecting IMPAX Application Server to Audit Manager” (topic number 11444) in the IMPAX 6.5.3 Application Server Installation, Upgrade, and Configuration Guide. 2. Configuring Data Execution Prevention (DEP) (Topic number: 7192) Data Execution Prevention (DEP) is on by default for all Windows programs.
9. Restart the system. When the server restarts, log into Windows as an administrator-level user. 3. Migrating a cache volume from a flat to a hierarchical structure (Topic number: 102251) Before starting the migration, verify the condition of the caches: 1. Install the MVFcachecheck package. 2. Run the mvf-clean-cache tool. 3. If the mvf-clean-cache output indicates that there are problems, resolve them.
Parameters Values Default value To close the cache volume, start the CLUI tool and type cache close volume_ref The cache volume to migrate to. It can be -D destination_cache_volume the same as the source volume. There should be enough space in the destination volume for all the studies in the source volume. Not applicable. If not specified, you are prompted to choose from a list. -X delay_in_seconds The amount of time in seconds before the Not applicable original files are deleted.
4. Changing the SQL Server administrator (sa) password (Topic number: 7738) 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.
5. Synchronizing clocks on Windows-based IMPAX systems (Topic number: 6752) If the system time on the Application Server and the image server (ASPFTP server) differs, the authentication tickets provided by the IMPAX Client are rejected by the ASPFTP server and image retrieval fails. You must configure the IMPAX systems to automatically synchronize their system time with a common server and remain synchronized.
4. To enable the NTPServer, in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\ NtpServer\Enabled subkey, change the REG_DWORD value to 1. 5. To specify where the computer obtains time stamps, in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ NtpServer subkey, enter the list of DNS names or IP addresses. If you use DNS names, append ,0x1 to the end of each DNS name. 6.
We recommend that you back up the registry before you change it, so that you can back out the changes, if necessary. To synchronize Windows servers to an internal time source 1. To open Registry Editor, select Start > Run, type regedit, and click OK. 2. To specify if the local machine is a local time server, in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags subkey, change REG_DWORD to A. 3. Exit the Registry Editor. 4.
2. Type w32tm /config /syncfromflags:manual /manualpeerlist:time_server where time_server is the DNS name or IP address of the time server. The time_server can be any Windows- or Solaris-based server. 3. To update Windows Time Service to use the new configuration, type w32tm /config /update 4. To synchronize the clock, type w32tm /resync 6. Upgrading Clients to IMPAX 6.5.3 (Topic number: 10176) IMPAX Clients, both local and remote, are used to view study images.
8. After the computer has restarted, verify that the C:\mvf directory has been deleted. If the directory is still present, delete it. 2. Removing the IMPAX 5.2 or 5.3 Client Knowledge Base (Topic number: 58578) If the IMPAX 5.2 or 5.3 Client Knowledge Base is installed, you must uninstall it before upgrading. To remove the IMPAX 5.2 or 5.3 Client Knowledge Base 1. Open Control Panel. 2. Select Add or Remove Programs. 3. Select IMPAX Client Knowledge Base 5.2 or IMPAX Client Knowledge Base 5.
to IMPAX 6.5.3, or the AS3000 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3. 2. If a File Download dialog appears, click Open or Run. A Preparing to Install message appears. If on Windows Vista, a cscript.exe prompt may appear. To run it, click OK. 3. If a prompt appears about downloading and installing missing components, click OK. 4. Follow the prompts to download and install Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.
network domain called radnet, and radnet is within the healthorg.com domain, the name to type would be radserver.radnet.healthorg.com. 9. On the IMPAX Login Type screen, select the appropriate authentication method: Windows, IMPAX, or Smart Card. • Windows Authentication—Logs into IMPAX using the Windows session credentials after launching the IMPAX Client or logging in with a Windows smart card. • IMPAX Authentication—Logs into the IMPAX Client separately from Windows.
Post-upgrade checking and stabilization 7 Some tasks are performed after the 6.5.3 upgrade is complete. 1. Installing Server license keys on an upgraded AS300 server (Topic number: 10245) Note: IMPAX 5.2 and 5.3 server license key files cannot be reused with IMPAX 6.5.3 software. For information on obtaining license keys, refer to the AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3. If you have not already installed the appropriate license keys on the servers, do so now.
2. Open Windows Explorer. 3. Copy the license key file to C:\mvf. 4. Rename the license key file to mvf.lic. Installing the archive license key on a Windows server (Topic number: 15609) Using PACS Store and Remember archiving (or any other type of archiving) requires that an archive license key be installed on the server. To install the archive license key on a Windows server 1. Match up the correct license key with the server’s MAC address. The license key file name is the MAC address with a .
d. To close the Connection Settings dialog, click OK. e. Expand application server node. f. Expand distinguished name. g. Select CN=users. h. Verify that the list of original IMPAX 5.2 or 5.3 migrated users is displayed. 2. Ensure that you can log into the IMPAX 6.5.3 software. a. On the IMPAX Database Server, run the Administration Tools and ensure that you can log in using the administration password. b. On the Application Server, open a web browser and connect to http://localhost.
To restart an archive queue 1. Log into the IMPAX 6.5.3 Administration Tools. 2. On the Daily tab, select Job Manager. 3. In the queue list, select the archive queue. 4. Click Restart. 4. Restarting Connectivity Manager queues (Topic number: 67610) If Connectivity Manager is currently deployed, and you have stopped any queues, use the Queue Manager to restart them. Once the queue is restarted, messages sitting in them are processed. To restart Connectivity Manager queues 1.
This command writes the output of the migration_inventory command to a report file in the /usr/mvf-mig6/reports or C:\mvf\mig6 directory. 6. Comparing pre- and post-upgrade snapshots (Topic number: 6895) Open the report file that contains the pre- and post-upgrade snapshot information. Compare the pre- and post-upgrade information. Ensure that all expected studies, objects, stations, and DICOM printers are still listed. 7.
8. Running PSARMT to mark studies from an external PACS as PACS archived (Topic number: 6629) Important! 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.
9. Uninstalling the IMPAX Migration Tools from a Windows computer (Topic number: 47239) 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. On Windows 2003 servers, select Add or Remove Programs. On Windows 2008 servers, select Programs and Features. 3. Select IMPAX 6.5.
7. Type clui. 8. In CLUI, type delete from map_ini where ini_section='signal-relay' 9. To exit CLUI, type exit. 10. In Windows Explorer, navigate to C:\mvf\bin and delete the mvf_signal_relay.exe and the install_relay-signal.bat files. 11. Optionally, you can delete the signal-relay and sig-relay-train users from the IMPAX 5.3 or earlier Service Tools User Manager. 12. On the IMPAX 6.5.3 Application Server where the 6.5.
Stopping the exhibitSyncNotifier service (Topic number: 58418) Once a site is migrated to IMPAX 6.5.3, the exhibitSynchNotifier service is no longer supported. You must therefore stop the exhibitSyncNotifier service, if it is still running on an upgraded station. To stop the exhibitSyncNotifier service 1. On the AS300 server, navigate to C:\mvf\sync\bin. 2. Double-click stopExhbitSyncNotifier.bat. The exhibitSyncNotifier service is stopped. You can also uninstall Data Currency.
12. Removing Client queues from Job Manager (Topic number: 11640) IMPAX 6.5.3 no longer supports cached Clients—only cacheless and standalone Clients. You must therefore remove previous Client queues, which are now obsolete, from the Job Manager. To remove Client queues from Job Manager 1. Retrieve the AE_REF of each cached 5.2 or 5.3 Client station. In CLUI, type select ae_ref from map_ae where ae_title = 'DISPLAY_STATION_AE' 2. Generate a list of cache volumes for that AE.
Troubleshooting IMPAX A As you upgrade IMPAX servers, you may encounter various problems. Troubleshooting: Error finding uninstall information for the previous version of IMPAX (Topic number: 121194) Issue During an IMPAX AS300 upgrade, the following message is received: Error finding uninstall information for the previous version of Impax. Please manually uninstall. Details The IMPAX 6.5.3 installer looks for certain IMPAX 6 registry keys and, if they are not found, an error message is displayed.
d. Click Change. e. At the prompt, type your name. Click Next. f. On the Welcome screen, select Modify. Click Next. g. Clear the checkboxes of all installed packages. Click Next. h. On the Maintenance Complete screen, select Yes, I want to restart my computer now. Click Finish. 2. Log into Windows as the AgfaService user. 3.
4. To test Cygwin, type the following commands to see whether a help message or an error is displayed: bash -help grep -help sed -help tr -help gawk -help 5. If you see an error message similar to the following after one or more of the -help commands: This application has failed to start because cygwin1.dll was not found. Re-installing the application may fix this problem. Perform the clean-up task described in the following section, then reinstall Cygwin, as described in the section after that.
Troubleshooting: AgfaService user not created by the installer (Topic number: 140394) Issue The installer did not create the AgfaService user. Details You can manually create the AgfaService user and update the password file. You must do this before the file is exported to other systems in the cluster. Solution 1. Open a command prompt. 2. Type C:\mvf\bin\passkey -M SET -u AgfaService -P "password" where password is the password you want for the AgfaService user.
3. Switch to the Web Services tab. 4. If the Report Sources Info field contains entries, double-click one of the entries. or If the Report Sources Info field is empty, click Add. 5. In the Report Source Provider field, type a name for the report source. 6. From the RIS type list, select the appropriate RIS type. 7. If you selected either Connectivity Manager Queryable RIS or Remote IMPAX RIS in the previous step, in the URL field, enter the URL for the queryable RIS or the remote RIS. 8.
Troubleshooting: IMPAX Client slow and erratic post-upgrade (Topic number: 10210) Issue After upgrading, IMPAX Client display is 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. Alternatively, use McAfee EPO or Protection Pilot to reconfigure the BOP to run only at fixed intervals, such as every five minutes.
Note: In IMPAX, other domain_id values may exist for the global or alternate domains. Updates may be required to match the domain_id for the primary domain patient_ids to the Connectivity Manager’s issuer_of_patient_id values for the PRIMARY use_of_patient_id. b. select requesting_service from dosr_study where accession_number='xxxxxxx' = site_ identifier The requesting_service value should match the Connectivity Manager site_identifier.
Solution To unlock the mvf user account 1. Log into SQL Server 2008 using the Administrator account. 2. In the SQL Server Management Studio, open a new query window. 3. Type ALTER LOGIN mvf ENABLE; ALTER LOGIN mvf with PASSWORD = 'mvf ' UNLOCK; GO 4. Click Execute. Troubleshooting: Server name registered in SQL Server is incorrect (Topic number: 7625) Issue If the server name registered in SQL Server is not the same as the server name registered in Windows, you must update the server name in SQL Server.
Upgrade and installation tool reference B Reference information is available for some of the tools and programs used when upgrading. IMPAX AS300 installation programs (Topic number: 7684) IMPAX 6.5.3 AS300 includes two installation programs for Windows Server 2008 R2 servers. Program Purpose setup.bat (Oracle for 64-bit Windows DVD) Install the appropriate version of Oracle Server for Windows Server 2008 R2 as300-installer.
AS300 installer packages reference (Topic number: 7682) The standard IMPAX AS300 installer groups the packages to install under four sections: default, database, archive, and optional. The following tables explain each package. Default Depending on the configuration of IMPAX being implemented, certain packages may not be supported. Default packages Purpose MVFCore Installs the DICOM services for IMPAX and contains several core Windows services and database tables used by IMPAX.
Database packages Purpose Oracle Server Extension Contains the files necessary to build an Oracle Server database to be used by IMPAX. SQL Server Extension Contains the files necessary to build a SQL Server 2008 R2 database to be used by IMPAX. For upgrades only. Archive Depending on the configuration of IMPAX being implemented, an archive package may not be supported. Archive packages Purpose MVFhsm Installs the HSM package.
Optional packages Purpose MVFchangeaccepter Installs a package related to the processing of change context (cc) objects. 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.
If there are multiple caches, the path name of the cache to be checked must be specified. Memory usage may be high if there are a large number of files, but mvf-check-cache displays the amount of memory required so that the operator can add more virtual memory if needed Performance of mvf-check-cache is hardware dependant. For example, on a Sunfire 280R, mvf-check-cache can check about 130 files per second.
The reporting tool may be rerun after further recovery work has been completed (more files restored to cache). In these cases the tool also checks locations with visible value C. If any files have been restored to cache since the last run of the tool, it sets those locations' visible values back to T to indicate that they are now valid. After the missing DICOM object file locations are marked, a report is generated for the studies that contain lost objects.
C IMPAX 5.2 tables obsolete in IMPAX 6.5.3 Some of the entries in the IMPAX 5.2 and 5.3 database tables have become obsolete in the IMPAX 6.5.3 database.
Table name Module name mitra_display_site_hanging display-sql mitra_display_toolbar_buttons display-sql mitra_display_format display-sql mitra_display_user_wizards display-sql mitra_display_wizards display-sql mitra_display_site_wizards display-sql mitra_display_priv_wizards display-sql mitra_lut_tables display-sql mitra_display_snapshot display-sql mitra_display_mpr_vr_presets display-sql mitra_display_ordering display-sql mitra_display_study_sorting display-sql mitra_display_xml_
Table name Module name mitra_select_rond_link mvf-select-sql mitra_select_rond_holidays mvf-select-sql mitra_select_user_toolbar mvf-select-sql mitra_study_arrive_rule_xml mvf-select-sql cd_burn_wizard mvf-select-sql cd_export_service mvf-select-sql mitra_window_positions mvf-select-sql mitra_select_avail_context mvf-select-sql mitra_select_user_context mvf-select-sql mitra_select_status_macros mvf-select-sql mitra_user_enumerated_attr mvf-select-sql mitra_avail_study_list_columns m
Table name Module name mf_location mtk mtk_query_constraints mtk mtk_user_source mtk mtk_user_destination mtk mtk_user_layout mtk dosr_team dosr dosr_user_team dosr dosr_user_history dosr dosr_password_history dosr dosr_privileges dosr dosr_wl_presets dosr dosr_user dosr AS300 Upgrade Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
IMPAX hardware and software requirements D For optimal performance, Agfa recommends particular hardware and software for each component of the cluster. IMPAX Application Server hardware and software requirements (Topic number: 6682) Application Servers have specific hardware and software requirements. Where a specific manufacturer is identified, only that manufacturer’s device is supported.
Component Requirements RAID Embedded Tape backup DAT 72/160 tape drives (if required for backup). For Oracle and larger SQL installs, a network backup is preferred. Modem N/A DVD-ROM Yes Network interfaces 100/1000 Mbps Video KVM or Integrated video Power supplied Redundant Peripherals KVM or mouse and keyboard * The use of four-CPU socket servers for IMPAX is supported but not recommended.
IMPAX AS300 Server hardware and software requirements (Topic number: 6674) IMPAX AS300 Servers (including single-server configurations and dedicated Curator and CD Export servers) have specific hardware and software requirements. Where a specific manufacturer is identified, only that manufacturer’s device is supported. IMPAX AS300 Server: Hardware requirements (Topic number: 6690) The following hardware configuration is recommended for IMPAX AS300 servers (including single-server configurations).
Component Requirements Floppy No Network interfaces 100/1000 Mbps Video Integrated video Power supplies Redundant Peripherals Mouse, keyboard, monitor * The use of four-CPU servers for IMPAX is supported but not recommended. Additional AS300 hardware requirements: Storage requirements (Topic number: 6733) Additional hardware can be used to meet archive requirements.
IMPAX AS300 Server: External software requirements (Topic number: 6695) The following software is required for most IMPAX AS300 servers. Unless otherwise indicated, Agfa does not provide the software as part of the IMPAX AS300 Server installation package. Component Requirements Operating system Windows Server 2008 R2 SP1 (64-bit) Database software One of the following: • Enterprise Edition, Standard Edition, or Standard Edition One of Oracle 11.2.0.
IMPAX Client: Hardware requirements (Topic number: 7793) The following hardware configuration are intended as a guide for IMPAX 6.5.3 Clients used primarily for viewing large volume image sets (such as 64 slice CT) and using third-party applications such as Voxar 3D, TalkStation, Orthopaedic planning tools, and so on. These Clients are typically used inside a hospital environment, such as a radiology reading area by radiologists.
Component Requirements Peripherals Scroll mouse and keyboard For North America, the Logitech MX518 is used with the MA3000.
Component Requirements Operating system Windows 7 Professional 64-bit (single language support) SP1 or Windows 7 Ultimate 64-bit (multi-language support) SP1 for Diagnostic review stations Microsoft Windows XP Professional SP3 may be used for non-diagnostic Client upgrades but is no longer available for shipment Note that other versions of Windows 7 SP1 can be used for non-diagnostic review stations. Other software Microsoft Internet Explorer 8.0 .NET 3.
External software licenses E 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. Cygwin (Topic number: 121758) Copyright 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Red Hat, Inc.
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it.
2. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
b. Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete 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, c. Accompany it with the information you received as to the offer to distribute corresponding source code.
through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
2.
RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS”' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
(eay@cryptsoft.com)" The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-). 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgment: “This product includes software written by Tim Hudson (tjh@cryptsoft.
libraries, source files, header files, and data files), any updates or error corrections provided by Oracle, and any user manuals, programming guides and other documentation provided to you by Oracle under this Agreement.
PARTY, WHETHER IN AN ACTION IN CONTRACT OR TORT, EVEN IF ORACLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ORACLE'S ENTIRE LIABILITY FOR DAMAGES HEREUNDER SHALL IN NO EVENT EXCEED ONE THOUSAND DOLLARS (U.S. $1,000). 6. TERMINATION. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Oracle if you fail to comply with any provision of this Agreement.
inconsistent or conflicting terms in the Binary Code License Agreement, or in any license contained within the Software. A. COMMERCIAL FEATURES. You may not use the Commercial Features for running Programs, Java applets or applications in your internal business operations or for any commercial or production purpose, or for any purpose other than as set forth in Sections B, C, D and E of these Supplemental Terms.
of any and all Programs and/or Software. The license set forth in this Section D does not extend to the Software identified in Section G. E. DISTRIBUTION BY PUBLISHERS. This section pertains to your distribution of the JavaTM SE Development Kit Software (“JDK”) with your printed book or magazine (as those terms are commonly used in the industry) relating to Java technology ("Publication").
I. SOURCE CODE. Software may contain source code that, unless expressly licensed for other purposes, is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement. J. THIRD PARTY CODE. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME file accessible at http://www.oracle.com/technetwork/java/javase/documentation/index.html.
License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Xerces C++ Parser, version 1.2 (Topic number: 121761) This product includes software developed by The Apache Software Foundation (http://www.apache.org/). Please read the LICENSE files present in the Help > About dialog of the IMPAX Client. Zlib (Topic number: 7595) zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.2, October 3rd, 2004 Copyright (C) 1995-2004 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty.
Glossary A IMPAX MVF. CLUI allows you to execute SQL statements. APIP Agfa Proprietary Imaging Protocol. Used to receive the proprietary format, reformat the images to DICOM, and redirect them to the SCP. An APIP SCP is used specifically to receive images from certain older Agfa image sources. cluster A networking solution combining two or more otherwise independent computers, enabling them to work together in managing hospital data.
H are combinations of series or images for a single patient. HIS Hospital Information System. The database used by a hospital to manage patient information and scheduling. IP address The Internet Protocol address is a numeric address that identifies the station to other TCP/IP devices on the network. HIS verification An option that forces the PACS to verify all incoming images from an acquisition station or modality against specific criteria, such as the patient ID and accession number.
coming into the cluster from an acquisition station, validates these incoming studies against information from the HIS or RIS, and routes the validated studies to cache or archive. Snapshot tool and saving the snapshots in a scheduled worklist. O Service Class Provider. A DICOM server that receives requests from an SCU. The DICOM SCP accepts images for processing, processes find and retrieve requests, and handles storage commitment requests and replies.
U UNC Universal Naming Convention. A convention for identifying servers and other resources on a network. UNC uses the format \\servername\resource. AS300 Upgrade Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
Index .NET installing Framework............................60 system requirements.............................97 32-bit installer..............................................23 64-bit Windows............................................81 A accounts Client administration............................64 lockout policies, resetting.....................42 mvf, unlocking.......................................79 adding Audit Record Repository.......................51 AD LDS requirements...........................
deleting location references..................18 directory structure................................53 installing package..................................82 reporting problem files.........................85 cc objects......................................................82 CD/DVD burners.........................................94 cdexport package installation......................82 changing SQL Server password............................55 choosing See selecting claim status avoiding conflicts...........
See Curator default report source missing......................76 deinstalling Oracle Server.........................................44 deleting Client job queue....................................72 log files...................................................20 Logical Volume......................................19 portable password file...........................42 references to cached images..................18 Dell server...............................................91, 93 Dell workstation.............
migrating to...........................................53 HIS verification............................................16 Hotfix, .NET Framework.............................60 HP server................................................91, 93 HP workstation............................................96 HSM archives...............................................94 installing package..................................82 I IBM server....................................................91 ICU software license.......
mvf-check-cache..........................................84 mvf-clean-cache...........................................85 mvf-report-loss............................................85 N names Application Server.................................11 Application Servers...............................60 AS300 Database Server.........................25 current AS300 server.............................33 database.................................................30 SQL Server..........................................
removing................................................72 restarting................................................65 stopping...........................................15, 17 retrieving studies..........................................46 RIS connecting.............................................42 R S RAM requirements......................................96 Application Server.................................91 AS300 servers.........................................93 references.......................
connecting to production database......39 disabling connections to.......................40 installing package..................................82 migrating worklist and report data......34 requirements..........................................95 restoring database.................................26 supported versions..................................9 upgrading database...............................22 staging servers..............................................22 standard monitors requirements...........
mvf.........................................................26 V Z Zlib software license...................................114 VaultAgfa package installation....................82 verifying server upgrade.......................................29 studies....................................................16 Visual C++ 2008 Redistributable................60 volumes references...............................................18 W warranty statements.......................................
