AS300 Upgrade and DAA Consolidation Guide IMPAX 6.2 or 6.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 6.2 or 6.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 DAA consolidation.................................................................................
Staging the new IMPAX 6.5.3 Database Server....................................................................29 Installing the IMPAX 6.5.3 AS300 packages on a new SQL Database Server......................30 Backing up the SQL 2000 database.......................................................................................32 Backing up the SQL 2005 or SQL 2008 database.................................................................32 Restoring the database on the new SQL Database Server................
Xerces C++ Parser, version 1.2.............................................................................................77 Log4Net..................................................................................................................................77 Zlib..........................................................................................................................................77 Glossary............................................................................................
Getting started 1 Understanding what has changed in IMPAX and the upgrade strategy to follow helps ensure a successful upgrade 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.
Different methods exist of transitioning the legacy IMPAX cluster to the new archiving method. Tools are available to aid in the effort. Parallel migration and DAA consolidation overview (Topic number: 123508) The following diagram depicts a parallel migration with DAA consolidation scenario that does not require a traveling server. Using this method, the downtime of the production system is reduced to the time required to do a cold backup.
IMPAX 6.2 or later DAA consolidation with existing hardware (Topic number: 125319) The following diagram depicts an IMPAX 6.2 or later DAA consolidation scenario. With this method, additional hardware is required to function as the Database Server of a temporary DAA cluster. The estimated downtime is the time required for the cold backup and the upgrade of the existing production system to IMPAX 6.5.3. Note: The IMPAX 6.5.3 AS300 server platform is Windows Server 2008 R2 SP1.
5. Perform de-referencing tasks (removing DAA references) on both the IMPAX 6.5.3 and the temporary DAA clusters. 6. Attach an HSM server to the IMPAX 6.5.3 cluster and use Volume Migration Tool to migrate archive data from DAA to HSM. This is the upgrade method documented for IMPAX AS300 and IMPAX AS3000 6.2 or later clusters using DAA.
Purpose of the Parallel and Volume Migration Tools (Topic number: 123298) With any IMPAX upgrade, you must use some of the tools and scripts included with the IMPAX 6.5.3 Migration Toolbox to extract relevant database information and upgrade the database schema. The IMPAX migration tools are in a dedicated Migration CD ISO. When having to convert DAA entries—no longer supported in IMPAX 6.5.3—to PACS Store and Remember and HSM archiving (which is supported), two additional tools are required: 1.
Preparing to upgrade 2 Important! Before proceeding with the upgrade of the AS300 server components, ensure that you have completed the tasks outlined in the AS300 Preparing to Upgrade Guide—IMPAX 6.2 or Later to IMPAX 6.5.3. You must perform certain preparatory tasks before upgrading to an IMPAX 6.5.3 AS300 configuration. These tasks include taking a system snapshot, stopping the transmission of data to the previous release of IMPAX, and halting and emptying queues. 1.
6. Make note of the installed packages. 7. When done, to avoid changing the packages, click Cancel. To record the names of previously installed IMPAX 6.2 or 6.3 AS300 software packages 1. On the IMPAX 6.2 or 6.3 Windows server to upgrade, select Start > Run. 2. In the Open field, type regedit and click OK. 3. In the Registry Editor, select HKEY_LOCAL_MACHINE\SOFTWARE\Mitra Imaging Inc. and HKEY_LOCAL_MACHINE\SOFTWARE\Mitra and make note of the installed packages (refer to page 59). 2.
The temporary DAA cluster will need an Application Server, so move an existing one to this cluster, install a new server with the Application Server software from the same version of IMPAX as the production cluster, or if supported, install the Application Server software on the temporary DAA Database Server. For instructions, refer to the appropriate installation guide: IMPAX 6.2 Application Server Installation and Upgrade Guide, IMPAX 6.3 Application Server Installation and Upgrade Guide, or IMPAX 6.
The status of each selected interface changes to Stopped. 6. Stopping Connectivity Manager queues (Topic number: 67550) If the Connectivity Manager’s inbound devices have not been stopped, stop the IMPAX outbound DM Out and impax_report_server queues prior to shutting down IMPAX for the upgrade. Messages in stopped queues are not processed and remain in the queue until the queue is restarted.
9. Select each Transmit queue and click Halt Queue. 10. To confirm that you want to halt the queue, click Yes. 8. Archiving remaining unarchived studies (Topic number: 7742) Use the information from the latest report on archiving studies to identify remaining unarchived studies (for details, refer to the appropriate version of the IMPAX Preparing to Upgrade Guide). You must store these studies to the archive. 1.
The Location column on the results list shows the current location of the study, and indicates which studies are only in cache (C for system cache, L for local station cache, W for web cache) and not also in an archive location (such as P for PACS archive). 6. Click Store to Archive. 7. To update the status of the selected studies, click Refresh. 8. Ensure that all studies are archived. Tip: To store unarchived studies, you could also use the Migration Toolbox and run the study_archive_report tool.
10. Emptying all queues (Topic number: 7702) Monitor the Job Manager to make sure that all the queues are empty and that all jobs are completed prior to the upgrade. To empty all queues 1. In the 6.2 or later Administration Tools, on the Daily tab, select Job Manager. 2. If an archive job remains in any of the queues, select the job and click Expedite Selected Job(s). 3. If any other job remains in any of the queues, select the job and click Delete selected job(s). 11.
13. Clearing the archive Logical Volume (Topic number: 7734) To avoid conflicts when upgrading, clear the archive Logical Volume. IMPAX re-creates the Logical Volume folders and files afterward. (If replacing the existing server with a new one, this task is not required.) CAUTION! Ensure that the Logical Volume is empty before deleting it. If it is not empty, create a store job to archive the images in the Logical Volume. To clear the archive Logical Volume 1. In the 6.
CAUTION! If you are running Oracle on Windows, do not delete the C:\mvf\data\logs\oracle directory. AS300 Upgrade and DAA Consolidation Guide—IMPAX 6.2 or 6.3 to IMPAX 6.5.
Assembling the temporary DAA cluster 3 To upgrade rather than replace the existing Database Server but also perform the tasks necessary to transition from a direct attached archive (DAA) to an archive method supported in IMPAX 6.5.3, use the temporary IMPAX Database Server that was staged earlier (refer to page 16). You then back up the existing SQL Server database, restore that onto the temporary DAA Database Server, then move the DAA server from the production cluster to the temporary DAA cluster. 1.
isqlw 7. When prompted, type sa as the user name and type the sa password. 8. To back up the database, type backup database mvf to disk = 'file_path:\mssql\backup\oldserver.dat' with stats where file_path is the location of the database files. For example backup database mvf to disk = 'C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\oldserver.dat' with stats, init 9. At the next command prompt, type backup log mvf to disk = 'file_path:\mssql\backup\oldserver.dat' with stats The oldserver.
a. To stop the IMPAX services, on all servers in the cluster, open a command prompt and type stopall.bat b. Shut down all applications that usually connect to the SQL Server database. Under Services, stop the SQL Server agent. Also, shut down the SQL Server Query Analyzer when not using it as part of the restore process. c. On the Application Server, open the Windows Administrative Tools and select Services.
f. Execute the procedures_mvf.sql and recreate_user_mvf.sql scripts as well. 14. To update the statistics for performance reasons, open a SQL Server Management Studio query window and type use mvf exec sp_updatestats 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.
f. Close the Administration Tools. The IMPAX 6.2 or later cluster can remain stopped as this system will be upgraded to IMPAX 6.5.3. AS300 Upgrade and DAA Consolidation Guide—IMPAX 6.2 or 6.3 to IMPAX 6.5.
Upgrading the existing cluster to IMPAX 6.5.3 4 You can now upgrade the production servers to IMPAX 6.5.3, starting with the Database Server. Note: The IMPAX 6.5.3 AS300 server platform is Windows Server 2008 R2 SP1. Existing servers can be restaged with this operating system, assuming that the hardware is 64-bit compatible. All Database Server upgrades are forklift upgrades, involving fresh installations onto restaged or new hardware. 1. Staging the new IMPAX 6.5.
2. Install SQL Server 2008 R2 SP1. For details, see “Installing SQL Server 2008 R2” (topic number 141825) in the AS300 Preparing to Upgrade Guide—IMPAX 6.2 or Later to IMPAX 6.5.3. After installing SQL Server 2008 R2 SP1, confirm through SQL Server Management Studio that the version is SQL Server 10.50.2500. 3. Install the Migration Toolbox. For details, see “Installing the Migration Toolbox on a Windows server” (topic number 11493) in the AS300 Preparing to Upgrade Guide—IMPAX 6.2 or Later to IMPAX 6.5.3.
6. Select the Database Packages label. 7. Clear the Oracle Server Extension checkbox and select the SQL Server Extension checkbox. 8. For a dedicated Database Server (no archive), or if using PACS Store and Remember archiving only, clear the Archive Packages checkbox. 9. Select the Optional Packages label, then select the checkboxes of any optional packages that should be installed.
14. On the Summary screen, to continue the installation, click Next. 15. After all the packages have been installed, click Yes, I want to restart my computer now. If you are not prompted to restart the computer, manually restart it. After the server restarts, log into Windows as an administrator-level user. 3. Backing up the SQL 2000 database (Topic number: 11497) Back up the existing SQL Server database so that you can restore it onto the new IMPAX 6.5.3 Database Server.
Note: Before backing up the database, confirm that you have stopped the IMPAX services, emptied and halted all queues, and shut the database down. More details are available in Preparing to upgrade (refer to page 15). Ensure that you are logged in using the AgfaService account; you cannot log into SQL Server Management Studio or back up the database from the command line using the Administrator account. To back up the SQL database using SQL Server Management Studio 1.
5. Restoring the database on the new SQL Database Server (Topic number: 7627) CAUTION! Perform this task only when replacing an existing server with a new server. Be very careful not to delete any live database files. Perform this procedure only on a new server that has not had any clinical use, even as a training server. Do not perform this procedure on any production, training, or traveling servers. When replacing the existing server with a new server, you first install the IMPAX 6.5.
g. To close the Properties dialog, click OK. 4. If you are restoring from tape, insert the backup tape into the tape drive. 5. In the Explorer window of the SQL Server Management Studio, expand server > Databases where server is the name of the SQL Server that IMPAX is running under. 6. Right-click Database and select Restore Database. 7. In the Destination for restore section, in the To database field, type mvf. 8.
f. World Wide Web Publishing 6. Upgrading the IMPAX database schema to IMPAX 6.5.3 (Topic number: 60244) Important! Only specific IMPAX upgrade paths are supported and it may not be possible to upgrade certain versions or SUs. More information is provided in the IMPAX 5.x–6.x Service Update and Hot Fix Migration Paths spreadsheet in the Additional documents section of the IMPAX Knowledge Base > Main Knowledge Base Page. Upgrading the database schema to 6.5.3 requires the IMPAX Migration Tools.
6. When prompted for a report source, if the Connectivity Manager query you ran previously returned a single value, use that value as the report source. If the query returned multiple values for the requesting_service field, consult a Connectivity Manager integrator, as mappings may also need to be changed. If this Connectivity Manager receives data from multiple report sources, then a few requesting_service values may exist that match each report source. 7.
8. Updating the SQL Server registration (Topic number: 7604) To correctly register SQL Server with the Database Server software and set up permissions within SQL Server, update the SQL Server registration. To do so, you must be logged into Windows as an administrator-level user. To update the SQL Server registration 1. Select Start > All Programs > Microsoft SQL Server 2008. 2. Right-click SQL Server Management Studio and select Run as. 3. In the Run as dialog, select The following user. 4.
2. If not already started, start the SQL Server Agent service through the SQL Server Configuration Manager. 3. Open the SQL Server Management Studio. 4. In the Object Explorer window of the Management Studio, expand server > SQL Server Agent > Jobs where server is the name of the SQL Server that the program is running under. 5. Right-click schedule_backup and choose Properties. 6. In the Properties dialog, switch to the Schedules tab. 7. Click New. 8.
11. Upgrading Application Servers to IMPAX 6.5.3 (Topic number: 134882) Upgrade all Application Servers (except the one being used in the temporary DAA cluster) to IMPAX 6.5.3. Note: The IMPAX 6.5.3 Application 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 new hardware. For more details, refer to the IMPAX 6.5.
To restart antivirus software 1. On a Windows server where scanning was stopped, launch the antivirus software. 2. Start the scan operation according to the vendor’s instructions. 14. Testing the installed software (Topic number: 61185) After installing the new version of IMPAX, perform certain tests to verify that the installation was successful. To test the installed software 1. On the IMPAX Database Server, run the Administration Tools and ensure that you can log in using the administration password.
2. In the Queue List table, select the checkbox beside the queue of any system device or real world device with a DM Out or impax_report_server Component. The Status of the queue should be Stopped. 3. Click start. The Status of the queue changes to Started. 17. Taking a post-upgrade system snapshot (Topic number: 6845) After upgrading to IMPAX 6.5.3, use the migration_inventory tool to capture the state of the system to compare it with the previous IMPAX system.
Migrating the archive 5 If you are using a temporary DAA cluster to manage the migration of studies previously archived in direct attached archives to HSM archives, convert the DAA entries to PACS Store and Remember initially, then to HSM. 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.
5. Verify that the external archive is listed in the hosts file of the temporary DAA system. 6. To confirm that the external archive can be accessed, ping the external archive using the host name or IP address. 2.
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.exe -A PACS_AE_title [-R retrieve_PACS_AE_title] [-S source_archive_AE_title] where PACS_AE_title refers to the external Store and Remember archive configured on the IMPAX 6.5.3 system and source_archive_AE_title refers to the DAA system to be replaced. Tip: You can also specify a log file by including -l debug -f logfile in the command. 6.
To remove references to old caches and archives from the new servers 1. On the IMPAX 6.5.3 Database Server, open a command prompt and change to the C:\mvf\bin directory. 2. To remove image caches and locations of DAA archives that are no longer applicable, type bash mvf-remove-caches -a DAA_archive_AE_title After removing caches, the is_cached flag in the dosr_study may not be accurate. 3.
4. Removing references from the database running the previous version of IMPAX (Topic number: 123355) Important! Before removing the old AE titles from the new system, determine whether to maintain the Task Scheduler settings. This is especially important if they have been changed from the default settings. The Primary Task Scheduler is normally the one running on the Database Server. Remove all references to caches and archives of the old cluster that are not part of the temporary DAA cluster.
select * from map_ini where ini_section = ‘MVF_TASK_SCHEDULER’ and ini_key = ‘PRIMARY_SERVER’ . 8. To copy the Task Scheduler settings from the 6.5.3 Database Server to the temporary DAA server, open CLUI and type Update map_ini set ini_value = 'new_Database_Server_AE_title' where ini_section = 'MVF_TASK_SCHEDULER' and ini_key = 'PRIMARY_SERVER' If this entry does not exist, insert it instead of updating. 9.
5. Query the system and confirm that, as expected, studies in the old system with a DAA location (for example, T) now have a PACS location (P). 6. To validate retrieval from the archives, perform the following tests: a. In the IMPAX 6.5.3 Administration Tools, open the Study Manager and select some studies marked as PACS archived (P). In the IMPAX Client, view the studies. A study is retrieved from the PACS archive (the old DAA archive) only if it does not exist in any cache. b. In the IMPAX 6.5.
To delete the PACS Store and Remember archive locations 1. Open a command prompt and change to the C:\mvf\bin directory. 2. To delete the archive locations, type mvf_remove_archive.exe -a PACS_archive_AE_reference Optionally include options -l for the log level and -f for the log file name. Note: De-referencing the archive location might take between 4 to 8 hours, depending on the system and the size of the archive being removed.
Post-upgrade checking and stabilization 6 Some tasks are performed after the 6.5.3 upgrade is complete. 1. Migrating a cache volume from a flat to a hierarchical structure (Topic number: 102251) Important! If upgrading from IMPAX 6.5 or later, the caches may have already been migrated to a hierarchical structure; this task can then be skipped. Before starting the migration, verify the condition of the caches: 1. Install the MVFcachecheck package. 2. Run the mvf-clean-cache tool. 3.
Note: The cache migration tool is included in the MVFCache (Windows) and IMPAXmvfc (Solaris) packages, which are part of the standard IMPAX install packages. To migrate a cache volume from a flat to a hierarchical structure 1. At a command prompt on the system where the cache volume is local, type cache_migration.
Tip: Use the -? parameter to view usage or help information. Example: cache_migration.exe -F 500 -T 4 -I 2 -f migration.log List of eligible cache volumes 1000 : /cache/mvfcache 1001 : /cache/vcacheRSNA2003 1002 : /cache/newcache Source volume_ref? 1000 Destination volume_ref? 1000 Delete original files (Y/N)? y How long to wait to delete (sec)? 10 After the migration, verify the condition of the caches: 1. Run the mvf-clean-cache tool. 2.
3. Uninstalling the Cross-Cluster Dictation Interlock tool (Topic number: 60396) If you no longer have to synchronize the dictation status of studies between the previous version 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.
Upgrade and installation tool reference A Reference information is available for some of the tools and programs used when upgrading. IMPAX AS300 installation programs (Topic number: 7684) IMPAX 6.5.3 AS300 includes two installation programs for Windows Server 2008 R2 servers. Program Purpose setup.bat (Oracle for 64-bit Windows DVD) Install the appropriate version of Oracle Server for Windows Server 2008 R2 as300-installer.
AS300 installer packages reference (Topic number: 7682) The standard IMPAX AS300 installer groups the packages to install under four sections: default, database, archive, and optional. The following tables explain each package. Default Depending on the configuration of IMPAX being implemented, certain packages may not be supported. Default packages Purpose MVFCore Installs the DICOM services for IMPAX and contains several core Windows services and database tables used by IMPAX.
Database packages Purpose Oracle Server Extension Contains the files necessary to build an Oracle Server database to be used by IMPAX. SQL Server Extension Contains the files necessary to build a SQL Server 2008 R2 database to be used by IMPAX. For upgrades only. Archive Depending on the configuration of IMPAX being implemented, an archive package may not be supported. Archive packages Purpose MVFhsm Installs the HSM package.
Optional packages Purpose MVFchangeaccepter Installs a package related to the processing of change context (cc) objects. This feature is not required and we recommend that this package not be installed. MVFpap Installs the PAP package. A PACS Archive Provider (PAP) acts like a Service Class Provider (SCP) by receiving studies and allows sites to have their studies mirrored at another site through PACS Store and Remember archiving.
Archive packages Location in HKEY_LOCAL_MACHINE\SOFTWARE\ MVFjdlt * Mitra Imaging Inc.\MVF JDLT vnumber MVFjdvd * Mitra Imaging Inc.\MVF JDVD vnumber MVFscdr * Mitra Imaging Inc.\MVF SCDR vnumber MVFhsm Mitra Imaging Inc.\MVF HSM Archive vnumber MVFsdlt * Disregard if found Optional packages Location in HKEY_LOCAL_MACHINE\SOFTWARE\ MVFCompressor Mitra Imaging Inc.\MVF Compressor vnumber MVFScavenger * Mitra Imaging Inc.\MVF Archive Scavenger vnumber MVFCurator Mitra Imaging Inc.
PMTS tool Function convert_to_remote_archive Converts DAA entries to PACS Store and Remember entries. AS300 Upgrade and DAA Consolidation Guide—IMPAX 6.2 or 6.3 to IMPAX 6.5.
External software licenses B 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. Log4Net (Topic number: 7648) 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.
Glossary A B Administration Tools backing up Administration Tools control the configuration and management of the entire IMPAX cluster. The Administration Tools are a Java-based application that run in a web browser. The activity of copying a database to preserve it in case of a software or hardware failure.
images into the Mitra Wavelet format and storing them in the web cache. These studies can be accessed by remote or local clients. D database A collection of data that is organized so that its contents can easily be accessed, managed, and updated. DICOM Digital Imaging and Communications in Medicine. The standard communication protocol used by a PACS, HIS, or modality to exchange information or images with other systems.
coming into the cluster from an acquisition station, validates these incoming studies against information from the HIS or RIS, and routes the validated studies to cache or archive. particular role have access to. Permissions are made up of a set of operations. S SCP non-jukebox archive Functions much like a jukebox archive, except that it has no mailslots or changer.
Index .NET Framework installing................................................40 32-bit installer..............................................30 64-bit Windows............................................56 A accounts Client administration............................41 adding PACS Store and Remember archive......44 Administration Tools...................................41 installing package..................................57 setting up PACS Store and Remember archive......................................
script reference......................................60 copyright information.............................2, 62 Core package installation.............................57 creating database.................................................30 report files........................................16, 42 Cross-Cluster Dictation Interlock tool uninstalling............................................55 Curator.........................................................57 upgrading........................................
J Java SE Platform software license................70 jobs expediting..............................................21 monitoring............................................18 L licenses external software...................................62 PACS Store and Remember archive......44 Log4Net license............................................77 logging..........................................................22 database upgrade...................................37 installation activity.........................
Client administration............................41 PMTS............................................................14 converting DAA entries.........................45 removing references........................46, 48 scripts.....................................................60 ports external PACS archive...........................44 post-upgrade system snapshot....................42 post-upgrade tasks.......................................52 prerequisites.................................................
T Task Scheduler copying from old cluster.......................46 temporary DAA cluster assembling.............................................24 moving DAA server to..........................27 staging Database Server........................16 using in migration.................................12 testing installed software...................................41 times database backups...................................38 tools, Migration database-upgrade-script.......................36 migration_inventory...
