AS300 Preparing to Upgrade Guide IMPAX 4.5, 5.2, 5.3, or WEB1000 to IMPAX 6.5.3 Preparing to Upgrade an AS300 Cluster or to Migrate a WEB1000 Site 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.
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).
Contents 1 Getting started 8 About this IMPAX Preparing to Upgrade Guide.......................................................................8 New IMPAX concepts and functionality....................................................................................9 Key differences between WEB1000 and IMPAX 6.5.3...........................................................11 Valid IMPAX upgrade paths...................................................................................................
2 Performing initial installations 40 Evaluating system requirements............................................................................................40 Obtaining Server license keys................................................................................................40 Obtaining Server licenses for Windows stations...........................................................41 Installing IMPAX 6.5.3 on new servers..........................................................................
Migrating reports to the training server..........................................................................75 Collecting information on IMPAX clients, servers, stations, and printers...............................77 Running an initial report on study archiving status.................................................................77 Running a report on study archiving status on a Windows station................................78 Checking the operating system...........................................
Generating a report of lost images..............................................................................109 Appendix A: Migration Tools commands and parameters 110 Common parameters in Migration Tool commands.............................................................110 Windows Migration Tools and parameters...........................................................................111 block_named_pipes.exe..........................................................................................
1 Getting started IMPAX 5.3 and earlier versions are quite different from IMPAX 6.0 and later versions. WEB1000 and IMPAX 6.5.3 also have a number of differences. These are important to understand. Various software packages must be installed before IMPAX can be upgraded. Other documentation is available to provide details.
Information on performing the actual upgrade is available in the AS300 Upgrade and Migration Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.3. If the cluster meets the first two criteria listed in the table but is using a direct attached archive—such as CD-R, DVD-R, MOD, or DLT—then upgrade that cluster according to the procedures documented in the AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.3. If upgrading from IMPAX 6.2.1 or later, refer to the AS300 Upgrade Guide—IMPAX 6.
IMPAX 6.5.1 included: • Improved speech synchronization in IMPAX Reporting • Instant Messaging to easily connect with colleagues • Validation of new speechmikes with IMPAX 6.5.1 • The ability to control local configuration of stations in various locations (such as home or work) • The introduction of the Agfa Web Service Portal (Service Portal), a web-based tool used to support, maintain, and monitor the IMPAX system IMPAX 6.
IMPAX 6.2 built on the IMPAX 6.0 foundation to deliver new mammography and user administration features, along with some Image area enhancements. IMPAX 6.0 and later were introduced as next-generation PACS systems. Compared with previous versions of IMPAX (5.
For a complete list of differences, see “WEB1000 and IMPAX 6.5.3 feature comparison” (topic number 55002) in the IMPAX Migrations Reference Guide. 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.
• To migrate an IMPAX cluster from Oracle for Solaris to Oracle on Windows, contact Agfa Professional Services for assistance. This migration process is not documented in this guide. • If performing a forklift upgrade, ensure that you install the same Oracle edition as the existing production system or else the database migration will fail. For example, if the database on the production system is Oracle Standard Edition, install Oracle Standard Edition when staging 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 upgrade period, users switch over to using the new version exclusively. With a parallel migration, by contrast, both the previous and the upgraded versions of IMPAX run simultaneously for a period of time, which could last weeks or months. Cluster linking is deployed to keep the two clusters in synchronicity with each other.
When a DAA consolidation involves two IMPAX clusters (in a parallel migration), the DAA library serves as the legacy archive, while the Hierarchical Storage Management (HSM) server functions as the new archive. The DAA entries are converted to PACS Store and Remember on the new IMPAX 6.5.3 system, and the Volume Migration Tool (VMT) is used to perform the archive migration from the DAA to HSM. Any new hardware must be staged with the latest version of IMPAX 6.5.3 for the upgrade to work.
• Image area wizards • Hanging protocols • Comparative review modes • Teaching file folders Key items that are not migrated include: • Worklists • Select wizards • Search and transmit locations • Tools and toolbar settings • Screen formats • Modality preferences • Window level presets • Permissions to teaching file folders • Markup for key images, only the original images retain the markup Details are available in IMPAX 5.2 preferences migrated to IMPAX 6.5.3 (refer to page 118).
Valid WEB1000 migration paths and transition strategy (Topic number: 6606) A site running WEB1000 or a combination of WEB1000 and IMPAX can transition its WEB1000 users to IMPAX 6.5.3. You can migrate from the following versions of WEB1000: • WEB1000 4.1 • WEB1000 5.0 • WEB1000 5.
For a more detailed list of the differences between WEB1000 and IMPAX, refer to “WEB1000 and IMPAX 6.5.3 feature comparison” (topic number 55002) in the IMPAX Migrations Reference Guide. WEB1000 transition strategy (Topic number: 6610) In most cases, the process of moving WEB1000 users to IMPAX 6.5.3 is a gradual one, taking place over months. The WEB1000 Server itself is never upgraded to an IMPAX 6.5.3 Server.
Phase 3: IMPAX 6.5.3 and WEB1000 coexistence (Topic number: 6642) IMPAX 6.5.3 and WEB1000 run as separate systems, but with image routing based on IMPAX routing rules. However, data currency does not exist, so data does not remain synchronized between IMPAX 6.5.3 and WEB1000. WEB1000 users start to be trained on the IMPAX 6.5.3 system. Phase 4: Initial set of WEB1000 users switch to IMPAX 6.5.
Also consider site performance—measure the time to acquire the first image. If current performance is inadequate or borderline, this may be another reason to replace some of the equipment. Note: If upgrading a site using direct attached archives, refer to the AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.3. If upgrading a WEB1000-only site, you must install all IMPAX 6.5.3 software on new (or redeployed) servers. You cannot upgrade WEB1000 servers to IMPAX 6.5.3 servers.
and earlier. Hold a kick-off meeting for the key stakeholders in the upgrade to explain this and to identify: • Site requirements • Preparations required for success • Expectations and responsibilities • Upgrade project milestones Document the decisions made at the kick-off meeting and deliver these to the site’s primary project sponsor.
• Study comments Related documentation (Topic number: 6634) IMPAX includes documentation for IMPAX Client, IMPAX Application Server, and IMPAX Server. The documentation is released on its own DVD. This DVD includes the Upgrade Guides along with the IMPAX 6.5.3 Knowledge Bases, Installation and Configuration Guides, and Quick References. The documentation eventually must be installed on an IMPAX 6.5.3 Application Server.
Opening the Client Knowledge Base from the List, Text, or Configure area (Topic number: 57440) Once the IMPAX documentation is installed, you can access it from the IMPAX Client application. To open the Client Knowledge Base from the List, Text, or Configure area 1. Press F1. or From the List or Configure area bar, click Help. The home (or main) page of the Client Knowledge Base opens in a browser window.
Opening the IMPAX 6.5.3 Server Knowledge Base (Topic number: 11528) The IMPAX 6.5.3 Server Knowledge Base is a reference tool for PACS IT specialists and clinical coordinators, field engineers, and technical launch team members, primarily to help them understand and use the components of the IMPAX cluster. The Understanding IMPAX Server section provides a basic understanding of the IMPAX system and introduces users to key components and concepts.
Opening a PDF guide from the documentation DVD (Topic number: 57808) All IMPAX guides can be viewed directly from the IMPAX documentation DVD. To open a PDF guide from the documentation DVD 1. Insert the IMPAX documentation DVD. 2. Navigate to /docs/{server | appserver | client}/guides. 3. Double-click the file name of the PDF guide.
IMPAX Application Server guide (Topic number: 6683) Title File name IMPAX 6.5.3 Application Server Installation, Upgrade, and Configuration Guide impax_application_server_ install.pdf Provides instructions on • Installing the operating system, IMPAX documentation, and IMPAX Application Server software • Upgrading the Application Server to IMPAX 6.5.
Title File name Provides instructions on servers. This guide covers single-server, all-in-one, single-host, and multi-host configurations. IMPAX 6.5.3 Curator and CD Export Server Installation Guide impax-curator-install.pdf Installing and initially configuring the Curator and the CD Export server. IMPAX 6.5.3 Standalone Installation and Configuration Guide impax-standalone-install.pdf Installing and initially configuring an IMPAX standalone station.
IMPAX Quick References (Topic number: 54853) Quick References are intended for clinical users. These abbreviated publications provide instructions for commonly performed tasks and frequently required references. For ease of access, Quick References can printed (double-sided if possible) and posted at Client workstations. Note: To view the IMPAX Quick References on a computer, Adobe Reader must be installed.
IMPAX Client Quick References (Topic number: 54856) Title File name Describes common IMPAX procedures and references for IMPAX 6.5.3 Quick Reference: Breast Imaging breast_imaging.pdf Radiologists who specialize in breast imaging. IMPAX 6.5.3 Quick Reference: Clinicians clinicians.pdf Clinicians and surgeons. IMPAX 6.5.3 Quick Reference: CT-MR ct-mr.pdf CT/MR navigation tasks. IMPAX 6.5.3 Quick Reference: Emergency (ER) emergency.pdf Emergency room clinical staff. IMPAX 6.5.
IMPAX Server Quick References (Topic number: 54859) Title File name Describes common IMPAX procedures and references for IMPAX 6.5.3 Quick Reference: Administration Tools admin_tools.pdf Configuring IMPAX Server using the Administration Tools. IMPAX 6.5.3 impax-cached-workstation-home-vpn-quick-ref.pdf Configuring the Quick Reference: IMPAX Cached Configuring the Workstation Virtual Cached Private Network (VPN) Workstation VPN at home.
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.4 or 1.5.5, you must migrate to Connectivity Manager 2.2.
• If intending to use the IMPAX Reporting integration with the IMPAX Client, IMPAX RIS must be upgraded to version 5.7 or later. For upgrade instructions, refer to the IMPAX RIS InstallShield Technical Manual. • TalkStation must be upgraded to TalkStation 4.0 SU4 or later. For instructions on upgrading TalkStation, refer to the appropriate TalkStation Upgrade Guides. • Audit Manager. For installation instructions, refer to the Audit Manager 1.2 Installation, Upgrade, and Configuration Guide.
Component Requirements 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 Application Server: Software requirements (Topic number: 6621) The following tables list the required software for Application Servers using Windows Server 2008® R2 (64 bit only) platforms.
IMPAX AS300 Server: Hardware requirements (Topic number: 6690) The following hardware configuration is recommended for IMPAX AS300 servers (including single-server configurations). Component Requirements Example systems Preferred: HP ML370, DL380 (may be deployed with VMware ESXi 4.1.
Additional AS300 hardware requirements: Storage requirements (Topic number: 6733) Additional hardware can be used to meet archive requirements. IMPAX AS300 Server: Non-SCSI CD/DVD burners and controller cards (Topic number: 58044) OEM-supplied CD/DVD writer IMPAX AS300 Server: HSM storage requirements (Topic number: 6686) Direct attached libraries are not supported in IMPAX 6.5.3.
Component Requirements • Upgrades only: Microsoft SQL Server 2008 R2 SP1 (64-bit), Standard Edition. Database software (for separate Network Gateway, Archive Server) Oracle Instant Client 11.2.0.1.0 including Basic, ODBC, and SQLPlus ODAC 11.2.0.2.1 for .NET 2.0 Browser Internet Explorer 8.0 Java Version 1.6 u31 Documentation Latest version of Adobe® Reader® Remote access (optional) Symantec pcAnywhere version 12.5 SP3 with TECH179960 hotfix Antivirus Norton Antivirus 6.
Component Requirements System The Agfa preferred supplier is HP. HP xw4400, xw4600, xw6400, xw6600, z400, or z600 Dell Precision™ 490 or 690, T5400, T7400, or T7500 CPU 2 x 2.0GHz or higher 1 x Dual/Quad Core 2.8GHz or higher 1 x Intel® Pentium® M 1.
Component Requirements MXRT200 and 7300 (high-end board for IMPAX Clinical Applications such as Oasis for IMPAX) RIS/Administrator stations Windows 7 (WDDM): and Clinical review NVIDIA FX 1700, FX 1800, FX stations 4800 ATI 3700, 3750, V3800 (third monitor board) Windows XP and Vista: NVIDIA FX 1700, FX 1800, FX 4800 ATI 3700, 3750, V3800 (third monitor board) MXRT 1150/2150 (third monitor MXRT 1150/2150 (third monitor board) board) *Windows 7 and WDDM drivers do not support the BarcoMed and older MXRT
The IMPAX Client will run on 64-bit operating systems in 32-bit compatibility mode. The IMPAX Client is not a 64-bit application and therefore does not take advantage of 64-bit processing or memory addressing. AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3,or WEB1000 to IMPAX 6.5.
Performing initial installations 2 Only some IMPAX installations can be performed during the preparing to upgrade period. In many cases, installation details are provided in one of the IMPAX 6.5.3 guides listed in IMPAX installation, configuration, and upgrade guides (refer to page 24). 1. Evaluating system requirements (Topic number: 6701) We recommend specific hardware and software for the various IMPAX 6.5.3 cluster components.
Obtaining Server licenses for Windows stations (Topic number: 10699) To obtain new license keys, if this is required, email licensekey@agfa.com. To generate the license keys, Agfa must know the Ethernet MAC (Media Access Control) address of the server. To obtain Server licenses for Windows stations 1. For each Windows server, open a command prompt and type ipconfig /all. 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.
In the IMPAX 6.5.3 AS300 Installation and Configuration Guide, Oracle for Windows is the recommended database for new AS300 (Windows) installations. However, when installing a new IMPAX AS300 Database Server as part of the upgrade, if SQL Server was previously used, then you must install SQL Server 2008 R2 (refer to page 42) as part of the IMPAX 6.5.3 upgrade, and select the SQL Server Extension package when installing the Database Server (refer to page 45).
6. On the Product Key screen, enter the product key. Click Next. 7. On the License Terms screen, read the license agreement and select the I accept the license terms checkbox. Click Next. 8. On the Setup Support Files screen, click Install. 9. On the Setup Support Rules screen, ensure that no significant errors exist and investigate any warnings. Click Next. 10. On the Setup Role screen, select SQL Server Feature Installation. Click Next. 11.
19. On the next two screens, Error Reporting and Installation Configuration Rules, accept the default values by clicking Next. 20. On the Ready to Install screen, click Install. 21. On the Installation Progress screen, after the installation completes, click Next. 22. On the Complete screen, click Close. 23. Close the SQL Server Installation Center. 24. Restart the computer and log into Windows as an administrator-level user.
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. Details This discrepancy may happen if you use a ghost image when installing the third-party applications. Solution To check the server name registered in Windows 1. Right-click My Computer and select Properties. 2. Switch to the Computer Name tab.
3. Type your name (minimum three characters). This information is recorded in the installer log file. 4. On the Welcome screen, click Next. 5. On the Select features screen, all Default Packages are selected. Clear the checkboxes of any packages that should not be installed. For a dedicated Database Server, normally clear the MVFNetworkGateway and MVFocr checkboxes. For a single-host server, normally all Default Packages are required except, potentially, MVFocr. 6. Select the Database Packages label. 7.
If the mvf.lic file is not located in C:\mvf, the file is copied to that location. A dialog informs you of the success of the copy task. 12. If an Archive package was installed, browse to the location of the archive license file and click OK. If the mvfarch.lic file is not located in C:\mvf, the file is copied to that location. A dialog informs you of the success of the copy task. 13. At the Confirm: Your existing database is compatible with this version prompt, click Yes. 14.
Windows Server 2008 Order Installation or configuration task 1 Installing Windows Server 2008 2 Setting the primary DNS suffix 3 Configuring Windows Server 2008 5 Partitioning disks on the Application Server on Windows Server 2008 R2 6 Adding roles and role services in Windows 7 Configuring IIS logging 8 Installing AD LDS 9 Installing and configuring pcAnywhere 12.5 11 Installing and configuring antivirus software 12 Installing Adobe Reader 6.
3. Setting up one or more IMPAX Client stations, connected to this Application Server, to use for training and configuration. For instructions, refer to the IMPAX 6.5.3 Client Installation, Upgrade, and Configuration Guide. Other configurations are also possible. The key is installing the Application Server software on the station designated for that purpose, but using a temporary IMPAX 6.5.3 AS300 Database Server.
Installing external hardware and software Action Install Windows Server 2008 R2 software followed by Windows Server 2008 R2 Service Pack 1 Activate Windows Configure the Windows Control Panel to display in Classic mode To avoid memory allocation problems, change the page file setting Change the Windows Event viewer to overwrite events as necessary Create a temp directory Configure Internet Explorer to support security certificate validation Partition disks appropriately for database, volumes, logs, and cach
To install the IMPAX documentation 1. Insert the IMPAX Documentation DVD or access the ISO file. 2. Double-click IMPAXDocumentationSetup.exe. A Preparing to install message appears. 3. On the Welcome screen, click Next. 4. On the Setup Type screen, select the appropriate option and click Next. • To install all documentation in all available languages, select All Documentation. • To install all English-language documentation, select All English Documentation. This is the default.
• .NET Framework 3.5 SP1 (installed with AD LDS) • Visual C++ 2008 Redistributable If any of these packages are listed in the InstallShield Wizard dialog, select them. If any of these packages do not appear in the list, those packages are already installed. 5. Click Install. 6. On the Welcome screen, click Next. 7. At the license agreement, select the I accept the terms in the license agreement checkbox. Click Next. 8. On the Setup Type screen, click Custom. Click Next. 9.
Verifying the Business Services installation (Topic number: 7598) You can verify the IMPAX Business Services installation by checking whether IIS works. To verify the Business Services installation 1. Open a web browser and connect to http://localhost. 2. Verify that the IMPAX Documentation page is displayed. or If the IMPAX Documentation has not been installed on the server, that the Welcome to IMPAX 6.5.3 page is displayed.
Preparing a training plan (Topic number: 55171) Without the full participation of the entire radiology staff, the upgrade from IMPAX 5.2 or 5.3 to IMPAX 6.5.3 will not run smoothly. Clinicians need to be trained as well. We therefore recommend that a formal training plan be put in place. Before preparing the plan, determine: • Which users get one-on-one training and which can be trained in groups. Radiologists and key clinicians and technologists are normally trained one-on-one.
Installing the Migration Toolbox on a Windows server (Topic number: 11493) To install the Migration Toolbox, you must be logged into Windows as an administrator-level user. The migration tools are on a dedicated Migration CD. To install the Migration Toolbox on a Windows server 1. From the IMPAX Migration CD ISO, navigate to the win32 directory and double-click impax_65_migration-winpkg-6.5.3.xxx.exe where xxx is the build number. 2. In the InstallShield Self-extracting EXE dialog, click Yes.
If the production system is not using DAA, you do not have to install these tools. To install the PMTS package on the IMPAX production system 1. Copy the MVFdact.exe to the IMPAX system and run the file. 2. To exit the installer, click Finish. The PMTS installation is complete. 9. Setting up a connection to the 4.5, 5.2, or 5.3 database (Topic number: 6626) To migrate IMPAX user data from the 4.5, 5.2, or 5.3 mvf database to the 6.5.
9. If necessary, select the Connect to SQL Server checkbox and supply a Login ID and Password. 10. If necessary, change the network library by clicking Client Configuration. Under Network libraries, select the protocol used to communicate with the SQL server at your site: either TCP/IP (the default) or Named Pipes. Click OK. 11. Click Next. 12. Change the default database to mvf (lowercase). Click Next. 13. Click Finish. Click OK. You can now run Migration Tools user commands against this 4.5, 5.2, or 5.
9. If necessary, change the network library by clicking Client Configuration. Under Network libraries, select the protocol used to communicate with the SQL server at your site: either TCP/IP (the default) or Named Pipes. Click OK. 10. Click Next. 11. Change the default database to mvf (lowercase). Click Next. 12. Click Finish. Click OK. You can now run Migration Tools user commands against this server. 11.
minutes and, although staggered, performance issues have been reported when many Clients are downloading the new IMPAX Client software. Therefore, we recommend: • Using a third-party software distribution application (for example, Microsoft SMS or Altiris) to avoid saturation of the Application Server. Consult your regional Agfa representative for options. or • Placing the Installation Server on a dedicated server.
To run the IMPAX Installation Server package 1. From the IMPAX Client CD or a network location, run IMPAXInstallationServerSetup.exe. A Preparing to install message appears. 2. On the Welcome to the InstallShield Wizard for IMPAX Installation Server screen, click Next. 3. To install the application into C:\Inetpub\wwwroot\ClientInstaller, on the Destination Folder screen, click Next. or To install the application to another location, click Change.
the site’s off-hours, as downloading and installing the Microsoft .NET framework can take over 30 minutes, depending on network speed. To run the installer package on a dedicated server that does not already have the IMPAX Installation Server installed, when using https mode, you must use the Web Server Certificate Wizard to create a certificate request to submit to a trusted certificate authority, and install the certificate.
To enable automated installation of the IMPAX Client software from a command prompt 1. At a command prompt, type ImpaxClientSetup.exe /S /v"setting=value… /quiet" where /S suppresses the initial InstallShield Wizard screen, and /v allows for the specification of installation settings and their values, and /quiet suppresses all the installation screens.
Spacing rules for installation settings (Topic number: 7757) When specifying installation settings values using the /v flag, certain rules regarding spacing of the settings must be followed. • Leave no spaces between the /v flag and its settings. For example: /v"ALLUSERS=2" (valid) /v "ALLUSERS=2" (invalid) • Separate each setting and value pair by a space from another setting and value pair.
Installation type All users, if person installing has administrative privileges; otherwise, current user Installation directory C:\Rad Tools\Agfa\IMPAX Client Application server radserver.radnet.healthorg.com Authentication mode IMPAX authentication ImpaxClientSetup.exe /S /v"APPSERVER=radserver.radnet.healthorg.
the new. It uses native components within IMPAX to send signals between the two systems that a study’s dictation status has changed. During the installation and configuration, a new role and a service called Study Status Relay are created to convey and receive the messages.
5. Open the Windows Administrative Tools and select Services. 6. Start the service. The install_signal_relay.bat file installs the mvf_signal_relay.exe as a Windows service, inserts default values into the map_ini, and creates a radiologist and a trainee radiologist user. These users are used by the service to change status when appropriate. The radiologist user is called signal-relay and the trainee radiologist is called sig-relay-train.
INI_SECTION INI_KEY signal-relay trainee_user INI_VALUE Description a radiologist. The default value is signal-relay. the IMPAX 5.2 or 5.3 Service Tools. The user name used when changing the study status as a trainee radiologist. The default value is sig-relay-train. If you change this value, you must also configure this user in the IMPAX 5.2 or 5.3 Service Tools. Copying the 6.5.3 Cross-Cluster Dictation Interlock components (Topic number: 59189) Perform the following task on the IMPAX 6.5.
5. In the Name field, type a name for the exception; for example, Study Status Relay or something similar. 6. In the Port field, type the number of the TCP port to listen for signals from the remote cluster. 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.
9. In the navigation pane, select the Study Status Relay role again. 10. In the details pane, expand the Licensing bar. 11. In the navigation pane, right-click the Study-Status Relay role and select Add License > Add license_type 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.
Tip: If it is too difficult to copy the string from the command-line interface, output the result to a text file, then copy the string from that file. 5. Open the Study.Status.Relay.exe.config file in a text editor. 6. Under StudyStatusRelayConfiguration, between the and tags, paste the long string. For example: ...
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. For details, see “Understanding Dual Cluster Claim and Assign” (topic number 128193) in the IMPAX 6.5.3 Application Server Knowledge Base. To run the Cross-Cluster Dictation Interlock tool 1. On the 6.5.
Taking system inventory 3 Install and run key Migration Tools during the preparing to upgrade phase. You must complete these initial tasks when preparing for the migration and upgrade of an IMPAX 5.2 or 5.3 cluster or a WEB1000 site to IMPAX 6.5.3. Some of these commands cannot be run against an IMPAX 4.5 server. More information on these Tools is available in Migration Tools commands and parameters (refer to page 110). 1.
Creating the pre-migration schema on an AS300 or WEB1000 server (Topic number: 57475) These steps assume that the Migration Tools have been installed on the Database Server that you are running the commands on, and that you are logged into Windows as an administrator-level user. To create the pre-migration schema on an AS300 or WEB1000 server 1. Open a command prompt. 2. Change to the C:\mvf-mig6\bin directory. 3. Type the following: build-impax-mig-schema.bat sa sa mvf 4.
2. Migrating reports to the training server (Topic number: 119286) Migrating reports from the production server to the training server allows users to work with reports while using the IMPAX 6.5.3 training cluster. Perform the following tasks to migrate reports to the training server: 1. Install the Oracle 10.2.0.1 OLE Driver (refer to page 74). 2. Set up the connection to the Oracle database (refer to page 75). 3. Migrate the reports (refer to page 75). Installing the Oracle 10.2.0.
Setting up the connection to the Oracle database (Topic number: 119284) The Oracle 10g Client software installs the drivers and programs required to communicate with the Oracle Server. Ensure that the network and TCP/IP are properly installed and configured. To set up the connection to the Oracle database 1. On the Application Server component of the training server cluster, navigate to the C:\Program Files (x86)\oracle\network\admin directory. 2. Using a text editor, open the tnsnames.
b. In the Data Link Properties dialog, select Microsoft OLE DB Provider for SQL Server. Click Next. c. In the Data Source field, type mvf_ts.world or the name of the tns entry that was created in tnsnames.ora. d. Select Use a specific name and password and type the database user name—normally sa. Do not specify the password at this time. e. In the Select the database on the server field, type mvf. f. Click OK. 4. In the Migrate training/traveling server data dialog, under Source, type the database password.
3. Collecting information on IMPAX clients, servers, stations, and printers (Topic number: 6721) 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 with access to the IMPAX 5.2 or 5.3 database and on which the Migration Tools have been installed, or on the IMPAX Database Server itself. The tool produces two different reports, depending on the parameters used.
on the IMPAX Database Server itself. The studies to be identified can be moved to archive prior to migration. The Study Archive Report tool uses various criteria to determine if a study is eligible for the report. For example: • A study is not eligible if the archive_flag is not set to 'T'. • A study is considered fully archived if all objects—with the exception of ignored objects—are archived. (Objects may need to be ignored if a remote PACS cannot handle certain objects.
mig_reporter.exe -d mvf_version_number -t mig-study-archive-report where version_number is either 52 or 53. The report file is created in the C:\mvf-mig6\reports folder.
• Windows firewall rules are created and applied to block external access to unused ports. • The Administrators group is automatically created by Windows; however, the list of files and registry keys that this group has access to is modified during the IMPAX installation. • The ImpaxServerGroup account is created and the list of files and registry keys that this group has full access to is configured. • The following user accounts are created: ImpaxSQLUser, ImpaxAdminUser, ImpaxServerUser, and AgfaService.
Preparing for user migration 4 The following information outlines the steps for preparing the IMPAX 4.5, 5.2, or 5.3 and WEB1000 user data for migration to the IMPAX 6.5.3 AD LDS database. Note: If the IMPAX 4.5, 5.2, or 5.3 site is using LDAP user authentication, user data is typically not migrated, so these tasks may not apply. 1. Collecting data on the WEB1000 or IMPAX user base (Topic number: 57497) Use the Migration Tools to generate a summary list of all WEB1000 and IMPAX user types on the system.
mig_reporter.exe -d mvf_version_number -U IMPAX_4.5_5.2_or_5.3_database_user -P IMPAX_4.5_5.2_or_5.3_database_password -t user_base_summary Viewing the report on the WEB1000 or IMPAX user base (Topic number: 57500) After the data is generated, you must run another command to view it. To view the report on the WEB1000 or IMPAX user base 1. On the Application Server, navigate to C:\mvf-mig6\reports. 2.
• Run the command to map the Client station names to machine identifiers • Verify that all Client station names have been mapped Details on each of these tasks follows. Getting a list of IMPAX Client station names (Topic number: 57503) Before you can map multiple IMPAX Client station names to machine identifiers, you must gather a list of all the names. To get a list of IMPAX Client station names 1. On the Application Server, open a command prompt and change to the C:\mvf-mig6\bin directory. 2.
If the administrator usernames and passwords are the same for all the IMPAX Client machines, do not include that information in the host_list file. 4. Save the host_list file. Modifying the Windows XP network access settings (Topic number: 57509) Windows XP Home computers and Windows XP Professional computers not on a domain default to Guest for network access. The Guest configuration assumes a number of access policies that prevent the run_psexec.bat script from running effectively.
Note: If you are logged into the server with a domain username and password that is the same as the username and password on a remote station, error messages appear while run_psexec.bat is executing. You can ignore these error messages. Verifying that all IMPAX Client station names have been mapped (Topic number: 57515) After you have run the command to map Client station names to machine identifiers (refer to page 84), you can verify that everything worked correctly.
Retrieving the IMPAX Client station name (Topic number: 57532) Once the appropriate Migration Tools are available on the Client station, you can use them to retrieve the station name. To retrieve the IMPAX Client station name 1. On the Client station, open a command prompt. 2. Change to the location of the get_station_mapping.exe file. 3. Type the following: get_station _mapping.exe -m List -d mvf_version_number -U IMPAX_database_user -P IMPAX_database_password 4. Type the following: mig_reporter.
3. Exporting user data (Topic number: 9920) Follow this procedure to export all IMPAX 4.5, 5.2, or 5.3 or WEB1000 user information. For IMPAX, this exported data includes access controls, privileges, preferences, and station configurations. For WEB1000, it includes information such as user IDs, privilege levels, access control groups and features, and team information. The XML file created by this procedure can be used for reference, and some of the user data is later imported into the IMPAX 6.5.
Information about other parameters supported by this tool is available in migrate-users.exe (refer to page 114). Deleting special characters in user names (Topic number: 60402) IMPAX 6.5.3 is more restrictive on what constitutes a valid user name than IMPAX 5.3 and earlier and WEB1000 were. To avoid problems in exporting user profiles into AD LDS, delete invalid characters from the exported user names in advance. To delete special characters in user names 1. Open the users.xml file in a text editor. 2.
2. Define which preferences will be getting migrated at the user level, therefore overriding role inheritance, by consulting the exported user data (refer to page 87) and the list of IMPAX 5.2 preferences migrated to IMPAX 6.5.3 (refer to page 118). 3. Pinpoint areas where the migrated preferences would interfere with the preferred inheritance model. Depending on how many preference groups would be affected, and how many users need migrating, you can then manage the problem one of two ways: 1.
For additional information on standard worklists, refer to the “Managing studies using worklists” section (topic number 8430) in the IMPAX 6.5.3 Client Knowledge Base: Extended. To find the exported IMPAX Select wizards 1. In a text editor such as Notepad, open the users.xml file. 2. Search for the text . All the Select wizards for a single user are grouped together under this heading.
To ease the process, try the following: • Simple text editors such as Notepad or Wordpad do not handle large files very well. You will get better results by using a dedicated Text or XML editor such as XMLpad or Ultraedit. • Use CLUI to parse the list.
Migrating user data 5 The following information outlines the steps required to successfully migrate WEB1000 and IMPAX 4.5, 5.2, or 5.3 user data into the IMPAX 6.5.3 AD LDS database. Note: If the IMPAX 4.5, 5.2, or 5.3 site is using LDAP user authentication, however, user data is typically not migrated, so this information may not apply. 1.
Password policy settings (Topic number: 6646) Password policy Setting Enforce password history Maximum password age Minimum password age Minimum password length Password must meet complexity requirements Store password using reversible encryption for all users in the domain Account lockout policy settings (Topic number: 58212) Account lockout policy Setting Account lockout duration Account lockout threshold Reset account lockout counter after Disabling the password and account lockout policies (Topi
3. To modify the Password Policy information, double-click the policy to be changed. Change each password policy to have the following settings: Password policy Setting Enforce password history 0 Maximum password age 0 Minimum password age 0 Minimum password length 0 Password must meet complexity requirements Disabled Store password using reversible encryption for all users in the domain Disabled 4. Under Account Policies, click Account Lockout Policy. 5.
9. On the Items to Backup screen, select the folder containing the ADAM data as well as the World Wide Web Publishing Service folder. Click Next. The default location for the ADAM database is C:\Program Files\Microsoft ADAM\AgfaHealthcare. 10. If backing up to a tape drive, under Backup media type, select the tape drive, and in the backup media area, click New media. Click Next. or If backing up to any other media type, select the location where the backup is to be saved, and type a name for the backup.
The next task is to define what IMPAX or WEB1000 privileges this new role inherits. 4. Mapping IMPAX or WEB1000 privileges to custom roles (Topic number: 6662) If custom roles have been created, then any appropriate IMPAX Client or WEB1000 privileges must be mapped to these custom roles. To map IMPAX or WEB1000 privileges to custom roles 1. In the UserMigration folder where the Migration Tools are installed, locate and open the configuration file called migrate-users.exe.config. The migrate-users.exe.
2. Compare the privileges in the database with the role mapping in the migrate-users.exe.config file. 3. To map an IMPAX or WEB1000 privilege to a custom IMPAX 6.5.3 role, add additional map entries. For example, to map a user with RADIOLOGIST privileges to a custom role called Pediatric Radiologist in IMPAX 6.5.3, add the following line before the default privileges_level line: 4. Save the file.
into XML (as described in Exporting user data (refer to page 87)), then transformed into LDF (Layered Data Format). Perform this task on the configured IMPAX 6.5.3 Application Server. To convert the user data to LDF 1. Open a command prompt. 2. Change to the C:\mvf-mig6\UserMigration directory. 3. To convert only IMPAX 4.5, 5.2. or 5.3 user information, type migrate-users.exe -m xml2ldf -I users.xml -d mvf_version_number -U IMPAX_4.5_5.2_or_5.3_database_user -P IMPAX_4.5_5.2_or_5.
To successfully migrate user data into AD LDS, the user currently logged into the IMPAX 6.5.3 Application Server component must have AD LDS administrative rights. (To check, launch AD LDS Edit and select Role > member. The logged-in user must belong to the Administrator group.) To migrate user data to AD LDS 1. On the Application Server, open a command prompt. 2. Change to the C:\mvf-mig6\UserMigration directory. 3.
3. At the dsdbutil prompt, type activate instance AgfaHealthcare 4. At the dsdbutil prompt, type ifm 5. At the ifm prompt, type create full location where location is the path to the folder where you want the installation media to be created. You can save the installation media to a network shared folder or to any other type of removable media. For example: ifm: create full C:\Backup\AgfaHealthcare 6. At the ifm prompt, type quit 7. At the dsdbutil prompt, type quit The AD LDS instance is backed up. 9.
10. Adjusting default toolbars, screen formats, and window level presets (Topic number: 6732) You can now customize the toolbars, screen formats, and window level presets used in the IMPAX 6.5.3 Client as required for specific roles and users. For instructions, refer to the IMPAX 6.5.3 Client Knowledge Base: Extended topics listed in the table that follows.
Preparing the IMPAX database and archive for the upgrade 6 You must perform certain tests and backup tasks to prepare the IMPAX 5.2 or 5.3 Database and Archive Servers for the upgrade. IMPAX 4.5 sites cannot upgrade directly to IMPAX 6.5.3; they must first upgrade to IMPAX 5.2, then update the study comments (refer to page 102), then perform the other tests and backup tasks. If migrating a WEB1000 site, no particular WEB1000 Server tasks are required. 1.
To update study comments after upgrading to IMPAX 5.2 from IMPAX 4.5 1. Launch CLUI. 2. Type Update DOSR_STUDY set study_comments_utf8=study_comments where study_comments is not null The study comments in the database are updated, reducing the amount of time required to later upgrade this database to IMPAX 6.5.3. 2.
On Solaris, launch CLUI. 2. Type select count(*) from map_event. 3. On Windows, click Execute. 4. Type select count(*) from map_event_audit. 5. On Windows, click Execute. Note: The count(*) command returns a result with five decimal places. If the tables are large (they could run to millions of records), you can optionally first export the data to file by following the “Exporting auditing information to a file” procedure (topic number 9342) in the IMPAX Server Knowledge Base.
5. Identifying the report source (Topic number: 68030) When upgrading the database, you will be prompted for the report source. When prompted, supply the value stored in the requesting_service field in the Connectivity Manager database. To prepare for the upgrade, identify this value in advance. To identify the report source 1. On the Connectivity Manager, open osql (refer to page 123) and type use mcf; select distinct requesting_service from mcf_service_request; 2.
6. To start the backup, click OK. 7. Exit the SQL Server Enterprise Manager. 7. Saving the map_event_audit tables from an AS300 SQL Server database (Topic number: 106543) When upgrading an IMPAX AS300 system running SQL Server, follow this procedure. To save the map_event_audit tables from an AS300 SQL Server database 1. Start the SQL Server Query Analyzer and log in as the sa user. 2. From the drop-down database list in the top toolbar, select mvf. 3.
8. Backing up critical AS300 server files (Topic number: 147687) Prior to a forklift upgrade of an IMPAX AS300 Network Gateway, Archive Server, or Curator, any critical files should be backed up to an appropriate location. During the upgrade itself, the files on the new server can be compared with that of the old server. 9. Detecting and correcting IMPAX cache corruption (Topic number: 6710) The Cache Check and Repair Tools are used to identify missing cache files and to repair or remove damaged ones.
mvf-check-cache -q d:\cache (Windows) A report and additional diagnostic messages are written to the log file. Note: If the cluster has only one local cache, you can invoke the tool without arguments. If the cluster has multiple caches, you must specify the path to the cache on the command line. If a cache is not specified and multiple caches exist, the tool lists the cache paths and exits. Cache files that do not have locations registered in the database are not detected.
For example: move_cmds.sh (Solaris) move_cmds.bat (Windows) Generating a report of lost images (Topic number: 58357) This procedure is designed to be run on a server that has suffered damage to one or more cache file systems. This procedure generates a report of studies that contain DICOM object files that have been lost from a server’s cache and deregisters the missing files from the database. To generate a report of lost images 1.
A Migration Tools commands and parameters The IMPAX 6.5.3 Migration Toolbox relies on parameters to configure the command line applications to suit a particular migration instance. While many of the parameters are common to all of the Migration Tools, some parameters are specific to Windows or Solaris migrations. 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 -R database_reconnection_attempts -s None -U database_user -? None Additional information Output to stdout. Differs for migration_inventory.exe (refer to page 115) and migration_inventory. Usage/help screen Windows Migration Tools and parameters (Topic number: 6605) Some of the migration tools and parameters are specific to Windows (AS300) migrations. block_named_pipes.exe (Topic number: 10609) Removes the registry entry that allows Named Pipe access to the SQL Server.
build-impax-mig-schema.bat database-upgrade-script.bat (Topic number: 10613) Upgrades the IMPAX 5.2 or later SQL Server database schema to IMPAX 6.5.3. This is a batch file that the user runs, which calls the executable file that handles the main part of the database upgrade. The database-upgrade-script requires a report source.
Parameters Values Default value -m {list | add} add MigrateTRServer.exe (Topic number: 10617) Utility that migrates worklist or report data or both from the training or traveling server to the production server. This is not a command-line utility; it has a user interface. When using the MigrateTRSserver utility to migrate Connectivity Manager report data from the IMPAX 5.2 or 5.
migrate-users.exe (Topic number: 10621) Not required for IMPAX 6.2 or later migrations. Exports user IDs, preferences, and privileges and migrates this data from MVF to AD LDS when migrating to the Windows Server 2008 R2 platform. Also exports Select wizards and other information that will not be migrated to IMPAX 6.5.3. Parameters Values Default value -m None {mvf2xml | xml2ldf | postimport} where: • mvf2xml—Read MVF and output in XML intermediate format • xml2ldf—Transform XML format to importable .
• To extract user data for user1 and user2 from IMPAX to default XML file (users.xml): -m mvf2xml -d myDB -U myDBUser -P myDBPass -uid user1,user2 • To extract all user data from WEB1000 to default XML file (webusers.xml): -m mvf2xml -d myDB -U myDBUser -P myDBPass -ud myWebDB -uU myWebDBUser -uP myWebDBPass • To transform all user data from IMPAX and WEB1000 XML files to default importable LDF file (users.ldf): -m xml2ldf -I users.xml,webusers.
Parameters Values Default value -o None; output unarchived studies to a file which may be Not applicable used by CLUI to initiate a store job. The file is not created by default. -x separator—Item separator for report data bar (|) -y None; include listing for partially archived studies Not applicable -z None; include studies cached only on a disabled AE Not applicable Example: mig-study-archive-report.
PMTS scripts overview B The following table shows an overview of the PMTS scripts included in the IMPAX DAA package. PMTS script names Function migrate-mi-server-database and migrate-it-ws-database Upgrades schema from IMPAX 4.5 to 5.2. mvf-remove-caches (bash script) Removes image cache and cached locations from the database. mvf-remove-web-caches (bash script) Removes web cache and cached locations from the database. mvf-remove-archive Removes archive and archive locations from the IMPAX 6.
IMPAX 5.2 preferences migrated to IMPAX 6.5.3 User preferences C Migrated? Details List area User Keywords Yes The keywords created to drive workflows continue to be used in IMPAX 6.5.3. Worklists No The worklist architecture changed significantly. Standard worklists are used in IMPAX 6.5.3. Scripts (Select wizards) No The Select Wizard is no longer available in IMPAX 6.5.3. This functionality has been replaced by standard worklists. Columns No IMPAX 6.5.
User preferences Migrated? Details Patient name format No (single-byte, phonetic, and so on) The implementation of patient name has changed. IMPAX 6.5.3 can provide single-byte, phonetic, and ideographic versions of patient names. Search Locations No Cannot migrate this user setting to an IMPAX 6.5.3 role. Search locations are set and configured within the Configure > Preferences area. Transmit Locations No This user setting cannot be migrated to an IMPAX 6.5.3 role. In IMPAX 6.5.
User preferences Migrated? Details Formats Yes Formats are consistent between IMPAX 5.2 and IMPAX 6.5.3. LUTs Yes LUTs are consistent between IMPAX 5.2 and IMPAX 6.5.3. Comparative Review Sequences Yes Comparative review sequences functionality is consistent between IMPAX 5.2 and IMPAX 6.5.3. New sequences have been added, however. Wizards Yes Operations such as DELETE and EDIT apply only to user-defined wizards and not those inherited from a role.
User preferences Migrated? Details Configurable Study Save No Configurable Study Save tool settings are controlled in the user profiles in IMPAX 6.5.3 and must be redefined. Markup Statistics No Markup Statistics are controlled in the user profile in IMPAX 6.5.3 and must be redefined. Modality Preferences No User preferences for a specific modality are controlled by user profiles in IMPAX 6.5.3 and must be redefined.
User preferences Migrated? Details Magnification Yes Magnification is consistent between IMPAX 5.2 and IMPAX 6.5.3. Geometry Yes Geometry is consistent between IMPAX 5.2 and IMPAX 6.5.3. Image Calibration Yes Image Calibration is consistent between IMPAX 5.2 and IMPAX 6.5.3. Rearranged Images Yes Rearranged Images are consistent between IMPAX 5.2 and IMPAX 6.5.3. Summary Series Yes Summary series created in IMPAX 5.2 are migrated to IMPAX 6.5.
Running osql to access SQL Server data D The osql utility can be used to access and change data in instances of SQL Server. This command prompt utility can execute one or more SQL statements and can either display the results of a query, or save the results in a text file. Use the osql utility to enter Transact-SQL statements, system procedures, and script files. The utility uses ODBC to communicate with the server. As of SQL Server 2005, osql replaced the isql utility entirely.
3. After you have run the last batch of SQL statements, to terminate the utility, type exit or quit at the start of a new line. For more information about this utility, refer to Command Prompt Utilities on the Microsoft site (http://msdn.microsoft.com/en-us/library/aa246885(v=SQL.80).aspx). AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3,or WEB1000 to IMPAX 6.5.
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 ADAM Active Directory Application Mode. Directory services for an individual application that controls user login and privilege information. AE Application Entity. In DICOM, the AEs are different stations in the enterprise that communicate with one other. Each requires a unique identifier known as the AE title.
containers In the navigation pane of the Configure area - Stations section, containers hold station containers. Much like a file folder, containers organize station containers into logical groupings. The container itself cannot be configured. Note that containers are surrounded by [square brackets]. Curator Curator is an IMPAX MVF server component. It is responsible for compressing incoming images into the Mitra Wavelet format and storing them in the web cache.
installed on Application Servers and are assigned to roles. log file A file or set of files containing a record of the actions and modifications made in an application. Service teams use log files during setup and configuration of the system or its components. Logs are also used to diagnose problems. Logging can typically be set to record varying levels of detail. M MAC address Media Access Control address. The unique physical address of each device’s network interface card.
permissions, IMPAX role Permissions define the available IMPAX features and types of studies that users in a particular role have access to. Permissions are made up of a set of operations. A collection of users or other roles that holds IMPAX Client permissions and preferences as well as licensing options. For example, a role can represent the enterprise, the institution, a department, or a team.
Configure area - Stations section. Stations are organized under station containers. You can set configuration options, such as diagnostic monitor settings, memory usage, and so on, for a specific station, or the station can inherit its configuration from the station container. T W wavelet compression Compression method using a proprietary compression algorithm that can be uncompressed only by systems that support that proprietary algorithm.
Index .NET and SQL Server 2008 R2.......................42 installing Framework.................51, 59, 60 system requirements.............................38 32-bit installer..............................................45 A access controls, WEB1000................17, 18, 87 accounts policies.............................................92, 93 ADAM backing up.............................................94 machine identifiers................................84 migrating users into.............................
AD LDS..................................................99 critical server files................................107 SQL 2000 database..............................105 Barco monitors.............................................36 block_named_pipes.exe.............................111 Broker migrations..................................9, 113 preparing database for........................104 browsers requirements....................................33, 38 build-impax-mig-schema....................
requirements..........................................32 speed......................................................34 creating.........................................................78 ADAM schema backup.........................94 custom roles...........................................95 database.................................................45 pre-migration schema.............72, 73, 111 report of unarchived studies.................77 SQL Server client connections........56, 57 standard worklists......
duplicate user IDs................................97, 114 DVD burners................................................35 E editing build-impax-mig-schema.bat...............73 Editline software license............................130 email documentation feedback........................3 licenses...................................................41 enabling automated installation..........................61 EPR WEB1000...............................................17 examples Client installation settings......
I IBM server....................................................32 ICU software license..................................130 IDs duplicate................................................97 user.........................................................88 iisstart.htm...................................................53 Image area..................................................118 IMPAX Clients See Clients IMPAX Reporting integration.................9, 31 importing user data into AD LDS..................
MigrateTRServer.exe...........................113 migrate-users...........................87, 97, 100 migration_inventory.............................77 station mapping.........................83, 85, 86 study archive........................................103 user_base_summary.............................81 user migration.......................................96 mig-reporter.........................................83, 112 mig-study-archive-report..........................115 milestones.....................
parallel migration.........................................13 parallel migration tools.............................117 installing................................................55 Parallel Migration Tools Set See PMTS parameters, Migration Tools.....................110 parent roles...................................................88 passwords age..........................................................93 creating................................................100 disabling policies........................
hanging protocols..................................89 inheritance.............................................88 mapping WEB1000 privileges..............17 Study Status relay............................67, 68 routing studies....................................................18 rules for spacing of installation settings.....63 run_psexec.bat................................84, 85, 116 S saving audit tables...........................................106 schema backing up ADAM................................
storage requirements....................................35 HSM.......................................................35 storing passwords...............................................93 studies setting status of......................................69 updating comments............................102 study_archive_report...................................78 study data...................................................118 suggestions for documentation.....................3 summary database information.......
exporting....................................15, 18, 97 gathering data........................................81 hanging protocols..................................89 inheriting preferences...........................88 migrated preferences...........................118 migrating IDs...................................15, 18 migrating to AD LDS....................98, 114 migrating WEB1000..............................17 Migration Tools parameter.................110 secure accounts.............................
