AS300 Upgrade and DAA Consolidation Guide IMPAX 5.2 or 5.3 to 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 and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
Contents 1 Getting started 8 Valid IMPAX upgrade paths.....................................................................................................8 About this guide........................................................................................................................9 Supported Windows and database versions..........................................................................10 New IMPAX concepts and functionality..............................................................
Upgrading the restored database schema to IMPAX 6.5.3....................................................34 Checking the status of SQL Server upgrades........................................................................35 Taking a post-upgrade system snapshot...............................................................................36 Comparing pre- and post-upgrade snapshots........................................................................37 Restarting antivirus software.......................
IMPAX AS300 Server: Hardware requirements............................................................66 Additional AS300 hardware requirements: Storage requirements................................67 IMPAX AS300 Server: External software requirements................................................68 IMPAX Client hardware and software requirements..............................................................68 IMPAX Client: Hardware requirements.................................................................
Getting started 1 Understanding parallel migration and Direct Attached Archive (DAA) consolidation helps ensure faster and more successful migrations to IMPAX 6.5.3. 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.
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.
Criteria Cluster currently using (For details on supported SUs, refer to 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.
• Platform updates include support for Windows Server 2008 R2 SP1, SQL Server 2008 R2 SP1 (upgrades only), and the retirement of several database and operating system platforms including Windows Server 2003 (32-bit and 64-bit), Windows Server 2008 (32-bit), SQL Server 2005, SQL Server 2008 (32-bit), and Oracle 11g for Windows (32-bit). As well, the standalone configuration on Windows XP is no longer supported. For a more detailed list of new IMPAX 6.5.
• Additional support for free-text study and voice comments • Enhanced scheduled worklist functionality • Enhanced breast imaging It also included IMPAX Results Viewer, a browser-based IMPAX client designed to enable efficient distribution of medical images and reports for referring physicians and other healthcare professionals. Platform updates included support for Windows 7, Windows Server 2008, SQL Server 2008, and Solaris Live Upgrade.
Understanding parallel migration (Topic number: 123301) With a serial migration, upgrades from one version of IMPAX to another have two distinct phases: 1. A preparing to upgrade period, which can last weeks, during which initial installations are performed, some data is migrated in advance, and users are trained on the new system. 2. An upgrade period, typically performed over a weekend, during which the IMPAX software and database are upgraded from the previous to the new version.
After the new IMPAX 6.5.3 cluster is installed, the following high-level tasks are performed: 1. Restore a cold backup from the previous-version production system to the new IMPAX 6.5.3 system. 2. Upgrade Oracle and the database schema on the IMPAX 6.5.3 system. 3. Convert the DAA entries to PACS Store and Remember on the IMPAX 6.5.3 cluster and confirm that DAA studies are accessible. 4. Perform de-referencing tasks (remove reference to DAA locations) on the IMPAX 6.5.3 and previous IMPAX clusters. 5.
(upgrades to IMPAX 6.5.3) After the temporary DAA cluster is installed with IMPAX 6.2 or later software (the IMPAX version currently being used in production), the following high-level tasks are performed: 1. Restore a cold backup from IMPAX 6.2 or later production system to the temporary DAA cluster. 2. Detach the DAA server from the IMPAX 6.2 or later production system and make it part of the temporary DAA cluster. 3. Upgrade the database, schema, and IMPAX software on the IMPAX 6.
is refreshing the entire production hardware, a traveling server may not be required. If using a traveling server, the estimated downtime is the time to transition to the traveling server and back to the migrated IMPAX 6.5.3 system. IMPAX production system running earlier version IMPAX 6.5.3 with new hardware for Database Server After the new IMPAX 6.5.3 cluster is installed, the following high-level tasks are performed: 1.
Communicating upgrade plans (Topic number: 9924) Upgrading a site to IMPAX 6.5.3 from IMPAX 5.3 or earlier is a big undertaking. Ensure that the site personnel understand the major architectural differences between IMPAX 6.5.3 and IMPAX 5.3 and earlier.
Setting up the IMPAX 6.5.3 cluster 2 To begin the upgrade process, install the new IMPAX 6.5.3 cluster that will later run in parallel with the existing IMPAX cluster. 1. Prerequisite software installations (Topic number: 59235) Note: For each package, ensure that the most current Service Update (SU) packages available at the time of upgrade are also installed. Before proceeding with the migration to IMPAX 6.5.3, migrate or install the following software. • If currently running PACS Broker 1.5.3, 1.5.
• Report viewing in the IMPAX Client Text area • IHE workflows • MPPS communication from modalities • Audit messaging • Language support for Latin 4 character sets Full instructions on migrating your Broker data to Connectivity Manager are provided in the appropriate version of the Connectivity Manager Migration Guide. Note: To continue to use PACS Broker 1.5.3, 1.5.4, or 1.5.5—and if the preceding circumstances do not apply—install the PACS Broker DICOM Interface SU2.
The MAC address of all Ethernet cards installed on the station are listed. You can use any of these to generate the license from. 2. Copy one of the returned MAC addresses to a secure place. Ensure that you copy down the address exactly as it appears, including leading zeroes. The MAC addresses contain only the alphanumeric characters 0-9 and A-F. 3. To obtain a license key for the server, send the MAC address information to licensekey@agfa.
Oracle for Windows is the recommended database for new AS300 installations. However, if SQL Server 2005 or 2008 was previously used, you must install a new IMPAX Database Server with SQL Server 2008 R2 SP1 as part of the upgrade to IMPAX 6.5.3, and select the SQL Server Extension package when installing the Database Server (refer to page 24). To install SQL Server 2008 R2 1. Log into Windows as an administrator-level user. CAUTION! If the .
12. On the Installation Rules screen, ensure that no failures have occurred. Click Next. 13. On the Instance Configuration screen, select Default instance. Click Next. 14. On the Disk Space Requirements screen, ensure that sufficient disk space exists for the features you have selected. Click Next. 15. On the Server Configuration screen, on the Service Accounts tab, click Use the same account for all SQL Server services. 16.
2. Stopping SQL Server services (Topic number: 109422) Before proceeding with the next task, stop the Windows SQL Server services, if they have been started. To stop SQL Server services 1. Open the Windows Administrative Tools. 2. Select Services. 3. Select each of the following services in turn and click Stop Service, if needed: a. SQL Server Browser b. SQL Server Integration Services 10.0 4. Close the Services window. You can now install SQL Server 2008 R2 SP1. 3.
2. Switch to the Computer Name tab. The server name is listed as the full server name. To check the server name registered in SQL Server 1. In a SQL Server query window, type select @@servername To update the server name registered in SQL Server 1. In the SQL Server query window, type: sp_dropserver old_server_name go sp_addserver server_name_as_in_Windows, local go 5. Installing the IMPAX 6.5.
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. AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
Upgrading the database 3 Once the new IMPAX 6.5.3 cluster is staged, you must install the Migration Toolbox on the following servers: • IMPAX 5.3 or earlier Database Server • IMPAX 6.5.3 Database Server • IMPAX 6.5.3 Application Server You can then use those tools to assist in the process of upgrading the database on the new Database Server, using backup and restore. 1.
4. On the Select Features screen, select the checkboxes of the features that you want to install, and clear the rest. When migrating a SQL Server database, select all the features except the Oracle on Windows Migration Tools. 5. Click Next. 6. To continue, click Install. 7. If you selected the Worklist and Report Migration Tools on the Select Features screen, when prompted, press any key to continue. 8. On the Setup Complete screen, click Finish.
3. Type the following: build-impax-mig-schema.bat sa sa mvf 4. At the Do you want to proceed? prompt, type y. The pre-migration database schema and data are created. 4. Setting up a connection to a previous-version AS300 database (Topic number: 6627) Use this procedure to connect the Application Server to an IMPAX 4.5, 5.2, or 5.3 AS300 Database Server. To set up a connection to a previous-version AS300 database 1. To use the 32-bit version of the ODBC Data Sources tool, run C:\Windows\SysWOW64\odbcad32.
You can now run Migration Tools user commands against this 4.5, 5.2, or 5.3 server. 5. 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. 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 system snapshot 1. At a command prompt, change to the C:\mvf-mig6\bin directory. 2.
To identify the report source 1. On the Connectivity Manager, open osql and type use mcf; select distinct requesting_service from mcf_service_request; 2. To prepare for upgrading the database, note the value stored in the requesting_service field. The requesting_service value is case-sensitive. 3. If multiple values are returned in the requesting_service field, consult a Connectivity Manager integrator, as data and mappings may need to be updated.
9. At the next command prompt, type backup log mvf to disk = 'file_path:\mssql\backup\oldserver.dat' with stats The oldserver.dat produced contains two files: the database backup and the transaction log backup. 10. From the C:\mvf\bin directory, type installall.bat This restores the services removed earlier. 11. To start up IMPAX, type startall.bat After the cold backup is taken, the IMPAX 5.3 or earlier system can continue to function as the production system until the transition to the new IMPAX 6.5.
c. On the Application Server, open the Windows Administrative Tools and select Services. Right-click each of the following and select Stop: IMPAX App Server Data Manager, IMPAX Audit Event Log Manager, IMPAX Dicom Object Sender, IMPAX Distributed License Manager, IMPAX Messaging Service, and World Wide Web Publishing. 3. Before starting the restore, confirm that the directory that will contain the mvf database file has the correct permission: a.
go 15. In a command prompt, change to the C:\mvf\bin directory. 16. Type clui and confirm that you can successfully query the database. 17. On the Application Server, open the Windows Administrative Tools and select Services. Right-click each of the following services and select Properties. From the Startup type list, select Automated. Click Start, then click OK. a. IMPAX App Server Data Manager b. IMPAX Audit Event Log Manager c. IMPAX Dicom Object Sender d. IMPAX Distributed License Manager e.
migrate-mi-server-database.bat c. Then run the associated script by typing migrate-it-ws-database.bat 3. Change to the C:\mvf-mig6\bin directory. 4. If upgrading from IMPAX 5.2, type database-upgrade-script.bat -U sa -P sapwd -v 52 or, if upgrading from IMPAX 5.3, type database-upgrade-script.bat -U sa -P sapwd -v 53 where sapwd is sa in this case. 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.
Important! We recommend checking the migration log file after each leg of an upgrade before moving on to the next leg. To check the status of SQL Server upgrades 1. Open the log file C:\mvf-mig6\data\logs\migrate_database_to_IMPAX6.5.3.log. 2. If the following warning appears in the log file, you can safely ignore it: Warning: The table 'CHANGE_CONTEXT_DETAIL' has been created but its maximum row size (8095) exceeds the maximum number of bytes per row (8060).
13. 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. 14. Restarting antivirus software (Topic number: 9916) If you have antivirus software installed and have halted any scan jobs, restart the antivirus services. To restart antivirus software 1.
Migrating the archive 4 The studies previously managed in a direct attached archive need to be made accessible in the new IMPAX 6.5.3 cluster. Do this initially using PACS Store and Remember. These can then gradually be converted to HSM archive entries. 1. Installing PACS Store and Remember on the IMPAX 6.5.3 cluster (Topic number: 132671) To convert DAA entries to PACS Store and Remember, install and configure a PACS Store and Remember AE title on the IMPAX 6.5.
1. Adding a PACS Store and Remember archive (Topic number: 9215) To configure an external PACS archive as a PACS Store and Remember archive, set up the external PACS archive in Network Management in the IMPAX Administration Tools. To add a PACS Store and Remember archive 1. Launch and log into the IMPAX Administration Tools. 2. On the Setup tab, click Network Management. 3. To set up a new destination, click New. 4. Type the AE title of the external PACS archive.
4. Add the IMPAX 6.5.3 system. Save the settings. 5. Verify that the external archive is listed in the hosts file of the IMPAX 5.3 or earlier system. 6. To confirm that the external archive can be accessed, ping the external archive using the host name or IP address. Important! The PACS Store and Remember archive functionality requires that an SCP be running on the new system. If not available, add the Network Gateway package to one of the IMPAX 6.5.3 servers. 2.
b. Log into the Administration Tools and select Study Manager. Ensure that all DAA archived studies are marked off-line. c. Launch CLUI, run the following statement, and ensure that studies are listed as offline: select count(*) from dosr_study_location where volume_type = 'O' 5. To convert the DAA entries to PACS Store and Remember, on the PACS Store and Remember server, open a command prompt and type convert_to_remote_archive.
3. Removing references to old caches and archives from the IMPAX 6.5.3 servers (Topic number: 123352) The upgraded IMPAX 6.5.3 database may contain references to caches and archives from the old cluster that are no longer part of the IMPAX 6.5.3 cluster. Once the caches and archive locations themselves are removed, you can use a tool to remove references to them. Important! Before removing the old AE titles from the new system, determine whether you want to maintain the Task Scheduler settings.
7. To maintain the old settings for the Primary Task Scheduler, delete the new ones by typing Delete from mvf_ts_module_config where ae_ref = new_Database_Server_AE_reference Delete from mvf_ts_config where ae_ref = new_Database_Server_AE_reference 8.
Note: The IMPAX 6.5.3 AS300 server platform is Windows Server 2008 R2 SP1. If necessary, existing servers can be restaged with this operating system, assuming that the hardware is 64-bit compatible. All upgrades are forklift upgrades and involve fresh installations onto restaged or new hardware. Refer to the IMPAX 6.5.3 AS300 Installation and Configuration Guide for more details.
This bash script has no log files. All of the information is output to the screen. 4. To remove references to the HSM server archive locations, type mvf_remove_archive_pre6.exe -A HSM_AE_title -d mvf -U mvf -P mvf -Q -l debug –f logfile Important! De-referencing HSM server archive location may take between 4 and 8 hours, depending on the system and the size of the archive being removed. 5.
3. To allow IMPAX 6.5.3 Client interaction, on the Application Server, open the Windows Administrative Tools. 4. Select Services. 5. Start the World Wide Web Publishing Service (IIS). 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.
2. To change the synchronization server to NTP, in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type subkey, change the REG_SZ value from NT5DS to NTP. 3. To specify if the local machine is a local time server, in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags subkey, change the REG_DWORD value to 5. 4.
CAUTION! Serious problems might occur if you modify the registry incorrectly. These problems might require that you reinstall your operating system and we cannot guarantee that these problems can be solved. 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.
Synchronizing with a time server when the IMPAX computer is not a member of a domain (Topic number: 58572) To ensure that image data streaming operates correctly when the IMPAX computer is not 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 not a member of a domain 1. Open Control Panel. 2. Select Date and Time. 3. Switch to the Server Internet Time tab. 4.
Managing the parallel migration 5 Certain tasks are performed while both the old and new systems are running in parallel. This permits a more gradual transition to the new version. 1. Enabling cluster linking (Topic number: 10689) Cluster linking refers to linking multiple sites so that users can query and retrieve studies from all of these sites. To enable cluster linking 1. On the Setup tab, click Network Management. 2. Switch to the Configuration tab. 3.
Checkbox When selected performed using a proprietary syntax and can only update clusters that use the same proprietary syntax. Link Prefetching Allows studies in the linked clusters to be included in the list of relevant prior studies so they can be prefetched to the local cluster. 6. Click Save. 7. Perform an IIS reset on the Application Server.
3. Manually upgrading the IMPAX Client from IMPAX 5.2 or 5.3 (Topic number: 51453) Before upgrading the IMPAX Client, ensure that IMPAX 5.2 or 5.3 Select wizards information is exported to the users.xml file. For more details, consult 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. Perform the following steps when upgrading an IMPAX 5.2 or 5.3 Client workstation to IMPAX 6.5.3.
training server, when using a traveling server (AS3000 sites), or if planning to run the upgraded IMPAX cluster alongside the previous-version IMPAX cluster for a transition period. Note: Do not confuse CCDI with Dual Cluster Claim and Assign (DCCA), which allows two active clusters of the same version (IMPAX 6.5.2 or later), running in parallel, to synchronize study status notifications and claim and assign messages between the two clusters as though they were one.
2. Copying the 5.2 or 5.3 Cross-Cluster Dictation Interlock components (Topic number: 48082) To communicate dictation status with the IMPAX 6.5.3 system, Cross-Cluster Dictation Interlock components must be added to a Windows-based computer in the IMPAX 5.2 or 5.3 cluster. To copy the 5.2 or 5.3 Cross-Cluster Dictation Interlock components 1. On the 6.5.3 Application Server where the zip file was extracted, from the mvf-signal-relay directory, copy the mvf_signal_relay.exe and install_signal_relay.
where remote_port_value is the TCP port where the Application Server listens for signals. a. By default, the port number is 6000. To confirm the port number, navigate to the folder where study-status-relay.bat is installed (for example, C:\Program Files\Agfa\Impax Business Services\study-status-signal-relay) and open the Study.Status.Relay.exe.config file in a text editor. b.
This creates a Study Status Relay role. 5. Configuring the Study Status Relay role (Topic number: 48223) The newly created Study Status Relay role requires a user called remote-dictation, and an appropriate license. Perform this task on the IMPAX 6.5.3 Application Server. To configure the Study Status Relay role 1. Launch an IMPAX Client connected to the Application Server where the Study Status Relay role was created. 2. Log into the Client as an Administrator user. 3.
where license_type is an appropriate and available license for this role. (Dictation is not a license-controlled feature.) The changes are saved automatically when you switch context. 6. Configuring the Study Status Relay service (Topic number: 48230) You can now configure the communication service between the previous version of IMPAX and IMPAX 6.5.3. The goal is to transmit relevant study status changes between these two clusters. To configure the Study Status Relay service 1. On the 6.5.
8. Update the value of RemoteSignalHost with the host name or IP address of the computer in the previous-release version of IMPAX that is running the study-status-relay service. 9. Save and close the file. 10. In the command prompt, type install_study_status_relay_service.bat If a log4net error is returned, you can safely ignore this message. To diagnose other errors or check status, consult the Study.Status.Relay.log file located in the study-status-signal-relay folder.
5. Validating the archives in the IMPAX 6.5.3 system (Topic number: 125072) Verify that the DAA consolidation was successful and that all archives are functioning properly in the new IMPAX 6.5.3 system. To validate the archives in the IMPAX 6.5.3 system 1. Log into the IMPAX Administration Tools. 2. On the Daily tab, click Job Manager. 3. Ensure that a PACS Archive queue exists. 4. Click Study Manager. 5.
To migrate image data 1. Install and configure the VMT software on both IMPAX systems. 2. If applicable, migrate studies from the Network Gateway caches on the old IMPAX system to the new IMPAX 6.5.3 system. 3. If the old IMPAX system has a DAA archive, migrate the archived studies from the legacy archive to the new IMPAX 6.5.3 HSM archive. 4. Check the migration results. 7. Transitioning to the new IMPAX 6.5.
If the script fails with a Failed to remove archiver queue or similar error, rerun the script. 3. To update the entry in mvf_scu_service for the PACS Archive ae_ref to disable PACS Store and Remember archiving, type update mvf_scu_service set pacs_archive_ae_ref = 0 where ae_ref = PACS_archive_AE_reference 4. If you are not using the PACS Store and Remember archive any longer, delete the associated caches by typing bash mvf-remove-caches -a PACS_archive_AE_title 5.
10. Uninstalling the Cross-Cluster Dictation Interlock tool (Topic number: 60390) If you no longer have to synchronize the dictation status of studies between the 5.3 or earlier and the 6.5.3 IMPAX systems, you can uninstall the components of the Cross-Cluster Dictation Interlock tool. To uninstall the Cross-Cluster Dictation Interlock tool 1. On the computer where the 5.3 or earlier Cross-Cluster Dictation Interlock components were copied, open the Windows Administrative Tools and select Services. 2.
19. From Windows Explorer, navigate to and delete the study-status-signal-relay folder (possibly from C:\Program Files\Agfa\Impax Business Service). 20. Log into an IMPAX 6.5.3 Client as an administrator user. 21. From the Configure area > Users and Roles section, delete the remote-dictation user from the Study Status Relay role, then delete the Study Status Relay role. All components of the Cross-Cluster Dictation Interlock tool are now removed. AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.
IMPAX hardware and software requirements A 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.
B Migration tool references More information about some of the tools used in the upgrade process are available in reference topics. 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.
PMTS tool Function mvf-offline-vols (bash script) Sets DAA library volumes as OFFLINE. convert_to_remote_archive Converts DAA entries to PACS Store and Remember entries. Common parameters in Migration Tool commands (Topic number: 6720) These command-line parameters are common to most of the executables in the IMPAX 6.5.3 Migration Toolbox. Parameters Values Additional information -d database_name DNS name for ODBC connection. Required for the migration_inventory.
SQL Server databases For a SQL Server database, on a computer supporting user ID sa, password sa, and ODBC name mvf, the batch file can be run directly. Otherwise, you must specify the mvf user, mvf password, ODBC name, in that order. Examples: build-impax-mig-schema.bat sa pwd new Runs the command for user sa, password pwd, and ODBC name new. build-impax-mig-schema.bat Runs the command for user sa, password sa, and ODBC name mvf.
Parameters Values Default value -a None; runs the command in audit mode, which means that it tests the Not applicable upgrade script without actually upgrading the database. No longer recommended for use. -v {52 | 53 | 62 | 63 | 64 | 65}; refers to the version being upgraded from. If Not applicable upgrading from IMPAX 6.5.x, the version parameter can be omitted. Examples: database-upgrade-script.bat -v 62 Migrate the database from IMPAX 6.2 to IMPAX 6.5.3. mig_reporter.
Parameters Values Default value -s None; generates system snapshot Not applicable -c None; generates cluster summary for client and Not applicable server machines Example: migration_inventory.exe -d mvf_52 -U sa -P -sa -c -D 52_server Produces a full cluster summary of client and server machines connected to the specified database. AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
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. 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 Connectivity Manager all-in-one configuration A middleware component in the integration between hospital information systems and other hospital imaging departments. Connectivity Manager also provides connectivity to each modality and the PACS. A configuration in which the Database, Archive Server, Network Gateway, and Curator Server components are all installed on a single Windows server, along with the Application Server software. Curator APIP Agfa Proprietary Imaging Protocol.
mainly used on the Internet for translating host names into Internet addresses. Also refers to the style of host name used on the Internet, though such a name is properly called a fully qualified domain name. H HSM Hierarchical Storage Management. An HSM archive system provides long-term storage of data and access to data. Studies archived with HSM are stored to a file system. A mount point and subdirectory to store studies to is specified. The HSM system handles data storage.
PAP PACS Archive Provider. A PACS Archive Provider (PAP) acts like a Service Class Provider (SCP) in that it receives studies. However, it 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.
uncompressed only by systems that support that proprietary algorithm. AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.
Index .NET system requirements.............................70 32-bit installer..............................................24 64-bit Windows............................................72 A adding ODBC data source.................................29 PACS Store and Remember archive......39 addresses, MAC............................................19 AD LDS requirements..........................................65 Administration Tools installing package..................................
avoiding conflicts..................................58 Clients upgrading..............................................52 clocks synchronizing.......................46, 47, 48, 49 CLUI updating map_ini..................................54 cluster summary................................................78 cluster linking enabling.................................................50 common parameters, Migration Tools.......76 communication plan....................................17 comparing snapshots.............
dot NET Framework....................................70 down time, informing site about.................17 DVD burners................................................67 E editing build-impax-mig-schema.bat...............28 Editline software license..............................85 email documentation feedback........................3 licenses...................................................19 enabling cluster linking........................................50 expectations...................................
mammography monitor requirements.......69 manually upgrading Clients........................52 manufacturer’s responsibility........................2 map_ini values, updating............................54 MDAC Application Server.................................65 memory requirements, Application Server.........64 requirements, AS300 servers.................66 mig_reporter.exe..........................................78 migrate-it-ws-database.bat script...............34 migrate-it-ws-database script.........
connecting.............................................39 converting DAA to................................40 deleting..................................................60 installing in new cluster........................38 setting up in Administration Tools......39 PAP installing package..................................73 parallel migration...................................13, 50 overview.................................................13 Parallel Migration Tools Set See PMTS parameters, Migration Tools..
site upgrade....................................................8 snapshot of system...........................30, 36, 37 software requirements.................................64 Application Server.................................65 AS300 servers.........................................68 Client.....................................................70 SP1 SQL Server.............................................23 SQL Server....................................................20 authentication...................
mvf.........................................................32 signal-relay.............................................54 V VaultAgfa package installation....................73 verifying access to PACS Store and Remember....39 server upgrade.......................................35 versions supported.........................................9 SQL Server and Windows.....................10 VMT.............................................................16 using................................................
