as3000 traveling server guide impax 6.2 or later to impax 6.5 · this guide is intended for service...

AS3000 Traveling Server Guide

IMPAX 6.2 or Later to IMPAX 6.5.3

Using a Traveling Server to Upgrade

An AS3000 Cluster to IMPAX 6.5.3

Copyright information© 2012 Agfa HealthCare N.V., Septestraat 27, B-2640, Mortsel, Belgium. All rights reserved. Noparts of this document may be reproduced, copied, translated, adapted or transmitted in any formor by any means without prior written permission of Agfa HealthCare N.V.

Trademark creditsAgfa and the Agfa rhombus are trademarks or registered trademarks of Agfa-Gevaert N.V., Belgiumor its affiliates. IMPAX, Connectivity Manager, Audit Manager, WEB1000, IDCV XERO, TalkStation,Heartlab, and HeartStation are trademarks or registered trademarks of Agfa HealthCare N.V. or itsaffiliates. All other trademarks are held by their respective owners and are used in an editorial fashionwith no intention of infringement.

Agfa HealthCare N.V.

Septestraat 27, 2640 Mortsel, Belgium

www.agfahealthcare.com

Documentation warranty statementCharacteristics of the products described in this publication can be changed at any time withoutnotice.

The information contained in this document is subject to change without notice. Agfa HealthCareN.V. and its affiliates make no warranties or representations, express, implied or statutory, withregard to this material, including, but not limited to, the implied warranties of merchantability andfitness for a particular purpose.

Agfa HealthCare N.V. and its affiliates shall under no circumstances be liable for any damage arisingfrom the use or inability to use any information, apparatus, method or process described in thisdocument. Agfa HealthCare N.V. and its affiliates shall not be liable for errors contained herein orfor incidental or consequential damage in connection with the furnishing, performance, or use ofthis manual.

2012 - 9 - 17

Manufacturer’s responsibilityThe manufacturer, installer, or importer will be responsible for the safety, reliability, and performanceof the equipment only if:

• Installation, modifications, adjustments, changes, or repairs are performed by suitably qualifiedservice personnel.

• The electrical installation of the site in which the equipment is used is according to an applicablesafety standard (UL, CSA, or IEC/CDE).

• The equipment is used according to the instructions provided in the operation manuals.

AS3000 Traveling Server Guide—IMPAX 6.2 or Later to IMPAX 6.5.3 2Agfa Company Confidential—Subject to Non-Disclosure Obligation

http://www.agfahealthcare.com

Giving feedback on the documentation(Topic number: 122201)

Thank you for taking the time to provide feedback. Your comments will be forwarded to the groupresponsible for this product’s documentation.

If you have a request for changes in the product, please contact your product sales representative orthe product’s technical support channel.

To give feedback on the documentation

1. In an email subject line or body, list which product, version, and publication you arecommenting on.

For example, “IMPAX 6.4 SU01 Client Knowledge Base: Extended”. (You can find thisinformation in the footer of the publications.)

2. Describe the incorrect, unclear, or insufficient information. Or, if you found any sectionsespecially helpful, let us know.

3. Provide topic titles and topic numbers where applicable.

Including your personal contact details is optional.

4. Send the email to [email protected].


mailto:[email protected]?subject=Documentation feedback

Contents

Getting started 61

Upgrading IMPAX with a traveling server: Overview................................................................6Resolving differences between the production and traveling server........................................8Related documentation: IMPAX upgrades...............................................................................9

Preparing the traveling server 102

Configuring the traveling Database Server............................................................................10Preventing Autopilot from prematurely deleting studies................................................11Checking the tablespace sizes on the traveling server.................................................12Configuring the maximum number of concurrent move and non-move jobs.................13

Configuring the traveling Application Server..........................................................................13Synchronizing clocks on Windows-based IMPAX systems...........................................15Configuring Windows Explorer to show all files.............................................................18Accepting the Java Runtime download and granting security permissions..................19Disabling IIS logging on Windows Server 2008 R2.......................................................20Checking web services on the Application Server........................................................20Backing up ADAM or AD LDS from the production Application Server.........................22

Establishing communication between Connectivity Manager and the Network Gateway......22Adding IMPAX DICOM devices.....................................................................................23

Exporting mappings and layouts to the traveling server.........................................................23Creating a temporary study data repository...........................................................................25

Routing to the traveling server and preparing modalities for the upgrade....................25Enabling cluster linking on the production server..........................................................25

Updating study status between servers.................................................................................26Stopping Connectivity Manager queues.................................................................................27

Using the traveling server during the upgrade 293

Enabling cluster linking on the traveling server......................................................................29Redirecting studies to the traveling server.............................................................................30

Transitioning to the upgraded production server 314

Restarting Connectivity Manager queues..............................................................................31Redirecting studies to the production server..........................................................................32


Handling updates to old studies.............................................................................................32Deleting studies from the production server..................................................................32Transmitting or sending studies from the traveling server.............................................33

Updating the status of production studies after the upgrade..................................................34Cleaning up the traveling server after the upgrade................................................................35

Appendix A: Traveling server checklist: Upgrading from IMPAX 6.2 or later 37

Appendix B: Installing and running the Cross-Cluster Dictation Interlock tool 42

Cross-Cluster Dictation Interlock installation prerequisites: IMPAX 6.2 or later upgrades.....43Copying the 6.2 or later Cross-Cluster Dictation Interlock components.................................43Configuring a firewall exception for the Cross-Cluster Dictation Interlock tool.......................44Configuring the Study Status Relay role for upgrades from 6.2 or later.................................45Configuring the Study Status Relay service...........................................................................46Running the Cross-Cluster Dictation Interlock tool.................................................................47

Glossary.......................................................................................................................................49

Index............................................................................................................................................51


1Getting started

IMPAX AS3000 sites have the option of bringing in a staged AS3000 server. This traveling server isinstalled as a Database Server and Network Gateway and acts as the production system when theexisting system is taken down during the upgrade weekend. A traveling server minimizes anydowntime and allows a site to continue to function during the upgrade.

Upgrading IMPAX with a traveling server: Overview(Topic number: 141749)

The following is a high-level overview of the set-up and use of a traveling server during an IMPAXupgrade.

Before the upgrade1. The traveling server is usually shipped to the production site about two to four weeks prior to

the upgrade weekend.

2. The traveling server is staged as a Database Server and Network Gateway (refer to page 10).(Ideally, it is staged with the version of IMPAX being upgraded to, so that it can also be usedas a training server.)


3. Because the traveling server cluster lacks a physical Archive Server, and to prevent studies frombeing deleted prematurely by Autopilot (refer to page 11), the Archive Server component canbe installed on the traveling server.

4. A temporary Application Server is also needed (refer to page 13) so that the traveling servercluster can function properly during the upgrade weekend.

5. The traveling server can be configured to HIS verify against the production ConnectivityManager (refer to page 22).

6. Prior to the upgrade, incoming studies are routed (refer to page 25) from the productionserver to the traveling server, creating a temporary study data repository (refer to page 25).Cluster linking is also enabled (refer to page 25) on the production server to the travelingserver. This repository allows the traveling server to act as the interim production system duringthe upgrade weekend and allows the site to continue to function. The studies routed duringthis time reside on both the traveling and production servers.

7. Before shutting down the production system and redirecting all studies to the traveling server,the status of studies between the two systems is synchronized (refer to page 26).

8. Connectivity Manager queues are halted (refer to page 27) so that RIS or Connectivity Managerupdates are sent after the production system is brought back online.

During the upgrade1. After the production system is shut down for the upgrade, more studies may be acquired by

the traveling server.

2. Cluster linking is enabled (refer to page 29) on the traveling server to the production serverso that any new studies and some study updates can be captured after the production systemis brought back online.

3. During the upgrade weekend, the RIS console must be used to view any reports residing onthe production system. For new studies sent directly from the modalities to the traveling server,reports are held in the Connectivity Manager queues.

After the upgrade1. After the upgrade is completed and the production system is brought back online, updates are

propagated back to the production system. Some changes may need to be captured (refer topage 32) by manually transmitting studies from the traveling server to the production server.For more details, see Resolving differences between the production and traveling server (refer topage 8).

2. All studies sent to the newly upgraded production system are HIS verified against theConnectivity Manager. Connectivity Manager is re-configured to send report updates to theupgraded IMPAX 6.5.3 Application Server.

3. The traveling server is removed from the site. Post-upgrade tasks and checks are completed(refer to page 35).


Resolving differences between the production andtraveling server(Topic number: 146084)

After upgrading the production system to IMPAX 6.5.3, the temporary study repository on thetraveling server consists of the following:

1. Old studies that reside on both the production and traveling servers, due to the routing ruleused in the period prior to the actual upgrade—usually two to four weeks worth.

2. New studies acquired during the upgrade that come directly from modalities to the travelingserver while the production server is down and being upgraded. These studies reside only onthe traveling server.

The key cutoff point is when the production server is brought down to be upgraded and the travelingserver is brought online as the interim production system.

Handling updates of old and new studiesDuring the upgrade, while the traveling server is being used as the interim production system, therecould be updates to either the old or new studies.

The following tasks capture these updates and propagate them to the newly upgraded productionserver.

1. Before bringing the production server down, stop the Connectivity Manager queues (refer topage 27). Messages in the stopped queues are not processed and remain in the queues untilthey are restarted. (Do not restart the Connectivity Manager services or the queues restart.)When the production server is brought back online after being upgraded, the updates are thentransmitted to the production server. This captures any RIS or Connectivity Manager updatessuch as demographic changes (not done through the Administration Tools), or study andreport updates.

2. After the production server is brought down, enable cluster linking on the traveling server(refer to page 29) to the production server, using the Link Cluster Updates option. This allowsupdates to the traveling cluster to be relayed to the production cluster when the productionserver comes back online. (Transit jobs for the updates build up in the traveling server queueuntil the production server comes back online.) This captures any new studies acquired duringthe upgrade, as well as study status and comment changes to old studies.

Note:

If possible, during the upgrade weekend, avoid doing any structural changes such assplits and merges to the old studies on the traveling server so that this third task can beavoided altogether.

3. Any structural changes to old studies that exist on both the production and traveling serversrequire that these studies be deleted from the production server and then manually transmittedfrom the traveling server to the production server (refer to page 32). These include any study


changes made through the Administration Tools, or directly using CLUI or sqlplus. The cutofftime referred to previously must be noted so that the list of studies to be deleted and transmittedcan be identified.

Related documentation: IMPAX upgrades(Topic number: 60109)

This guide is intended for service and administrative personnel who are upgrading an IMPAX 6.2or later AS3000 cluster to IMPAX 6.5.3, using a traveling server.

It is a companion volume to the AS3000 Preparing to Upgrade Guide—IMPAX 6.2 or Later to IMPAX6.5.3, which describes all tasks leading up to the upgrade weekend.

Information on performing the actual upgrade is available in the following guides:

Applicable upgrade guideArchive typeDatabase

AS3000 Upgrade Guide—IMPAX 6.2 or Laterto IMPAX 6.5.3

HSM or PACS Store andRemember

Oracle

AS3000 Upgrade and DAA ConsolidationGuide—IMPAX 6.2 or 6.3 to IMPAX 6.5.3

Any direct attached archive(DAA)

Oracle

If installing and initially configuring a new AS3000 cluster, rather than upgrading an existing cluster,refer to the IMPAX 6.5.3 AS3000 Installation and Configuration Guide.

For information about using the IMPAX 6.5.3 software once it is installed, refer to the IMPAX 6.5.3Server Knowledge Base, IMPAX 6.5.3 Application Server Knowledge Base, and IMPAX 6.5.3 ClientKnowledge Base: Extended.


2Preparing the travelingserver

Before using a traveling server to upgrade to IMPAX 6.5.3, certain preparatory tasks must becompleted.

Configuring the traveling Database Server(Topic number: 146096)

1.

After unpacking the traveling server and completing the pre-upgrade checks detailed in the Travelingserver checklist: Upgrading from IMPAX 6.2 or later (refer to page 37), such as obtaining the IPaddress, subnet mask and gateway information for the traveling server from the site administrator,perform these initial configurations.

Note:

To install and configure the traveling Database Server, refer to the IMPAX 6.5.3 AS3000Installation and Configuration Guide. Ideally, the traveling server is staged with the versionof IMPAX being upgraded to, so that it can also be used as a training server.

To configure the traveling Database Server

1. Log into the traveling Database Server as the root user.

2. Edit the hosts file and populate it with the production system's IMPAX and networkinformation: servers, clients, modalities, and any other network devices communicated with.

For more details about the hosts file, see “The /etc/hosts file” (topic number 9090) in theIMPAX 6.5.3 Server Knowledge Base.

3. Test network connectivity and verify hostname resolution by pinging the hostnames.


4. To obtain an IMPAX mvf license key, Agfa must know the Ethernet MAC (Media AccessControl) address of the traveling server Network Gateway.

a. To retrieve the address, type ifconfig -a.

b. To obtain a license key, send the MAC address information to [email protected],along with the type of component being installed on the server.

5. To check the network connection, type

dmesg | grep -i up

At minimum, a 100 Mbps full-duplex system is required; a 1 GB full-duplex system is preferred.

6. Check the traveling server's date and time. To set the date, type

date -u mmddHHMM.

For example, type date -u 03151029.

7. Confirm that the Network Gateway package has been installed. Open the /install_info file andlook for GATEWAY='y'.

8. Using CLUI or sqlplus, confirm that the database is clean and that all data from another siteor upgrade has been cleared from it.

9. If necessary, clean the main database. As the mvf user, type

/usr/mvf/bin/build-database

10. Ensure that the Application Server schema has been extended. This should be done while thetraveling Application Server is being configured.

11. In the IMPAX log file, confirm that there is a valid license for the Network Gateway. Type

cat /data/logs/IMPAX.log | grep -i valid

You should see a license key is valid message.

Preventing Autopilot from prematurely deleting studies(Topic number: 146345)

Autopilot transfers images to long-term storage and flushes them from the cache.

To prevent studies from being deleted prematurely by Autopilot before they are transmitted to theupgraded production system, one of two options is possible.

• Install the Archive Server component on the traveling server and, through Source Manager,set all stations to archive. As the traveling server cluster has no physical archive, no study canbe archived and, as a result, Autopilot will not delete any studies from cache.

In the log file, to confirm the Archive Server has a valid license, type cat /data/logs/IMPAX.log| grep -i valid. You should see a license key is valid message.

For more details, see “Automatically archiving incoming images” (topic number 8976) in theIMPAX 6.5.3 Server Knowledge Base.

or


mailto:[email protected]

• Set up the production server as a PACS Store and Remember archive for the traveling server.This allows easy tracking of the studies not transmitted to the production system by checkingfor archived versus unarchived studies in the traveling server.

For more details, see “Adding a PACS Store and Remember archive” (topic number 9215) inthe IMPAX 6.5.3 Server Knowledge Base.

Checking the tablespace sizes on the traveling server(Topic number: 146105)

On the traveling server, confirm the Oracle tablespace sizes and, if necessary, increase them.

To check the tablespace sizes on the traveling server

1. Log into the traveling server as the service user.

2. If necessary, to start the database, type

dbstartmvf

3. To start the listener, type

lsnrctl start

4. Change to the /usr/mvf/bin directory.

5. Type

/usr/mvf/bin/monitor_update

/usr/mvf/bin/monitor_stats

Recommended sizeTablespace

1 x 2000 MBMVF

1 x 2000 MBMVFINDX

3 x 2000 MBMVFL

3 x 2000 MBMVFLINDX

1000 MBTEMP

1000 MBUNDO

250 MBSYSTEM

6. If additional space is needed, to run the monitor_add script, type

/usr/mvf/bin/monitor_add

7. To continue, type

C

8. Type the appropriate tablespace name.

For example, type


MVFINDX

9. Type the path name for the data file.

10. Type the size of the file in megabytes.

For example, type

2000

The file is created.

11. Repeat these steps as necessary, substituting the appropriate tablespace name and size eachtime.

Configuring themaximum number of concurrent move and non-movejobs(Topic number: 146160)

Configure the maximum number of concurrent move jobs and concurrent non-move jobs that canbe handled for the same destination. For both move jobs and non-move jobs, the default is 1.

To configure the maximum number of concurrent move and non-move jobs

1. Log into the traveling server as the service user.

2. Launch CLUI.

3. Type

update map_ini set ini_value ='3' where ini_key = 'MAX_MOVE_JOBS_PER_DEST'

update map_ini set ini_value ='2' where ini_key = 'MAX_NON_MOVE_JOBS_PER_DEST'

Configuring the traveling Application Server(Topic number: 146163)

2.

A temporary Application Server is needed so that the traveling server cluster can function properlyduring the upgrade weekend. The Application Server should have already been staged with the sameversion of IMPAX as the traveling Database Server.

Note:

To install and configure the traveling Application Server, refer to the IMPAX 6.5.3 ApplicationServer Installation, Upgrade, and Configuration Guide. The traveling Application Server isstaged with the version of IMPAX being upgraded to, so that it can also be used as a trainingserver.

Use the Traveling server checklist: Upgrading from IMPAX 6.2 or later (refer to page 37) whileperforming these configurations.


To configure the traveling Application Server

1. Open Control Panel and select System.

2. Switch to the Advanced tab.

3. Change the paging file setting:

a. Under Performance, click Settings.

b. Switch to the Advanced tab.

c. Under Virtual memory, click Change.

d. Under Paging file size for selected drive, select System managed size.

e. Click Set.

f. Click OK.

4. Enable Data Execution Prevention:

a. Under Performance, click Settings.

b. Switch to the Data Execution Prevention tab.

c. Select Turn on DEP for essential Windows programs and services only.

d. Click OK.

5. Change the startup and recovery settings:

a. Under Startup and Recovery, click Settings.

b. Select the Time to display list of operating systems checkbox.

c. Set the time to 5 seconds.

6. If C:\TEMP does not exist, create the folder, then edit the user variables:

a. Click Environment Variables.

b. Select the TEMP user variable and click Edit.

c. In the Variable value field, type C:\TEMP.

d. Click OK.

e. Select the TMP user variable and click Edit.

f. In the Variable value field, type C:\TEMP.

g. Click OK.

h. Click OK again.

7. Add the AgfaService user as a remote user:

a. Switch to the Remote tab.

b. Under Remote Desktop, select the Allow users to connect remotely to this computercheckbox.

c. Click Select Remote Users.

d. Click Add and add the AgfaService user.

8. Configure date and time properties:


a. Open Control Panel and select Regional and Language Options.

b. Switch to the Regional Options tab.

c. Click Customize.

d. Switch to the Date tab.

e. Under Short date, change the Short date format to MM/dd/yyyy.

f. Click OK.

a. Open Control Panel and select Date and Time.

b. Switch to the Time Zone tab.

c. Select the appropriate time zone.

d. Click OK.

9. Apply software registry updates by double-clickingC:\SOFTWARE\REGISTRY_UPDATE\modify.login.reg.

10. Confirm that sufficient free space exists on all drives.

11. Set the Start menu and Control Panel to classic views.

12. Check the Event Viewer and fix any errors, if possible. Clear all events and restart the systemto confirm that the errors do not reappear.

13. Stop and disable Windows Firewall in Windows Services.

14. Disable Recycle Worker Processes:

a. Open the IIS Manager.

b. Select Application Pools.

c. Right-click DefaultApp Pool and select Properties.

d. Clear the Recycle worker processes (in minutes) checkbox.

15. Change the startup type to Automatic for the Task Scheduler, Background Intelligent Transferand PACS Client Updater services.

16. To improve the stability and reliability of the web services, split the web services into separateapplication pools. Follow the procedure detailed in the IMPAX 6.x—Splitting and RecyclingWeb Services Application Pools on the Application Server Information Bulletin (Livelink NodeID 26813149). If you do not have access to this bulletin, contact Agfa Professional Services.

Synchronizing clocks on Windows-based IMPAX systems(Topic number: 6752)

If the system time on the Application Server and the image server (ASPFTP server) differs, theauthentication tickets provided by the IMPAX Client are rejected by the ASPFTP server and imageretrieval fails. You must configure the IMPAX systems to automatically synchronize their systemtime with a common server and remain synchronized.


https://livelink.agfa.net/Livelink/livelink.exe/overview/26813149


Note:

Also ensure that the time zone for the computer is set correctly to indicate the time zone wherethe system is located.

The instructions that follow use the synchronization feature built into the operating system. Whenconfigured, Windows Time Service sets and synchronizes the system time with a standard timeserver.

Synchronizing Windows servers to an external time source(Topic number: 58717)

Synchronize the Windows Server 2008 R2 servers on your network to an external time source toensure that image data streaming operates correctly.

CAUTION!

Serious problems might occur if you modify the registry incorrectly. These problems mightrequire that you reinstall your operating system and we cannot guarantee that these problemscan be solved.

We recommend that you back up the registry before you change it, so that you can back outthe changes, if necessary.

To synchronize Windows servers to an external time source

1. To open Registry Editor, select Start > Run, type regedit, and click OK.

2. To change the synchronization server to NTP, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Typesubkey, change the REG_SZ value from NT5DS to NTP.

3. To specify if the local machine is a local time server, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlagssubkey, change the REG_DWORD value to 5.

4. To enable the NTPServer, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer\Enabled subkey, change the REG_DWORD value to 1.

5. To specify where the computer obtains time stamps, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer subkey, enter the list of DNS names or IP addresses.

If you use DNS names, append ,0x1 to the end of each DNS name.

6. To set the poll interval, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval subkey, change the REG_DWORD value to the number ofseconds between each poll.

The recommended value is 900 Base Decimal, which polls the time server every 15 minutes.


7. To specify the maximum positive difference that triggers a synchronization, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection subkey, change the REG_DWORD value to the maximum numberof seconds.

The recommended value is 3600 Base Decimal.

8. Similarly, to specify the maximum negative difference that triggers a synchronization, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection subkey, change the REG_DWORD value to the maximum numberof seconds.

9. Exit the Registry Editor.

10. To stop and restart the Windows Time server, at a command prompt, type net stop w32time&& net start w32time.

It may take up to an hour for this to take effect.

For more information, refer to the Microsoft Knowledge Base article KB 816042(http://support.microsoft.com/kb/816042).

Synchronizing Windows servers to an internal time source(Topic number: 58720)

Synchronize the Windows Server 2008 R2 servers on your network to ensure that image data streamingoperates correctly. To configure the Primary Domain Controller (PDC) master without using anexternal time source, change the announce flag on the PDC master. Choose either the ApplicationServer or the AS300 server as the PDC master and sync the other servers to it.

CAUTION!

Serious problems might occur if you modify the registry incorrectly. These problems mightrequire that you reinstall your operating system and we cannot guarantee that these problemscan be solved.

We recommend that you back up the registry before you change it, so that you can back outthe changes, if necessary.

To synchronize Windows servers to an internal time source

1. To open Registry Editor, select Start > Run, type regedit, and click OK.

2. To specify if the local machine is a local time server, in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlagssubkey, change REG_DWORD to A.

3. Exit the Registry Editor.

4. To stop and restart the Windows Time server, at a command prompt, type net stop w32time&& net start w32time.

It may take some time for this to take effect.


http://support.microsoft.com/kb/816042

Note:

Do not configure the PDC master to synchronize with itself.

Synchronizing with a time server when the IMPAX computer is not a member of adomain(Topic number: 58572)

To ensure that image data streaming operates correctly when the IMPAX computer is not a memberof a domain, use the synchronization feature built into the operating system.

To synchronize with a time server when the IMPAX computer is not a member of a domain

1. Open Control Panel.

2. Select Date and Time.

3. Switch to the Server Internet Time tab.

4. In the list, type or select the time server to synchronize with.

Synchronizing with a time server when the IMPAX computer is a member of a domain(Topic number: 58569)

To ensure that image data streaming operates correctly when the IMPAX computer is a member ofa domain, use the synchronization feature built into the operating system.

To synchronize with a time server when the IMPAX computer is a member of a domain

1. Open a command prompt.

2. Type

w32tm /config /syncfromflags:manual /manualpeerlist:time_server

where time_server is the DNS name or IP address of the time server. The time_server can beany Windows- or Solaris-based server.

3. To update Windows Time Service to use the new configuration, type

w32tm /config /update

4. To synchronize the clock, type

w32tm /resync

Configuring Windows Explorer to show all files(Topic number: 47547)

We recommend that you display all available files in Windows Explorer.


To configure Windows Explorer to show all files

1. Open Windows Explorer.

2. Select Organize > Folder and search options.

3. In the Folder Options dialog, switch to the View tab.

4. In the Advanced settings pane, under Files and Folders, select Show hidden files, folders anddrives.

5. Clear the Hide extensions for known file types checkbox.

6. To save the changes, click OK.

Accepting the Java Runtime download and granting securitypermissions(Topic number: 8210)

The first time you launch the Administration Tools from a web browser, a security warning appears.This warning is to confirm that you want to launch the application and to indicate that you trustthe content from the web is safe.

Note:

If prompted, you must accept the security certificate. If you click No, you cannot log into theAdministration Tools.

If it is not already installed, you may be asked to download the corresponding version of the JavaRuntime Environment. If you download the Java Runtime Environment, you must disable the Javaautomatic update feature.

To grant security permissions

1. In the Address field of the browser, type

http://server_name/service

where server_name is the name or IP address of the server where the Administration Tools areinstalled.

2. If the Java plug-in security warning appears, click Grant always.

The message does not appear the next time you log in.

To disable automatic updates of the Java Runtime

1. Open Control Panel.

2. Select Java.

3. Switch to the Update tab.

4. Clear the Check for Updates Automatically checkbox.

5. Click Apply. Click OK.

6. Close Control Panel.


Disabling IIS logging on Windows Server 2008 R2(Topic number: 116039)

IIS logging is enabled by default in Windows Server 2008 R2, and the default path for the log filesis on the C:\ drive. Over time, the drive becomes full, which creates a serious downtime risk on theserver. To prevent this, disable IIS logging.

Tip:

If you prefer to keep IIS logging active, change the location of the IIS log files.

To disable IIS logging on Windows Server 2008 R2

1. Open the Windows Administrative Tools and select Server Manager.

2. Expand Roles > Web Server (IIS).

3. Select Internet Information Services (IIS) Manager.

4. Under Connections, expand Sites.

5. Select Default Web Site.

6. In the pane to the right of Connections, under Default Website Home, scroll down to the IISsection and double-click Logging.

7. In the Actions pane, select Disable.

IIS logging is disabled.

8. Close Server Manager.

Checking web services on the Application Server(Topic number: 146187)

Check the status of each web service running on the Application Server by running Healthcheck.Create a shortcut or favorites link to the Healthcheck URL.

Running Healthcheck from a URL to check the status of web services(Topic number: 11405)

Healthcheck checks the status of each web service running on the Application Server. When yourun Healthcheck, it attempts to connect to each of the web services. If it succeeds, Healthcheck setsthe status to Passed (green). If Healthcheck fails, the status is set to Failed (red). The comment

field indicates where the failure occurred.

Run Healthcheck on the Application Server at the following times:

• After performing an IISreset

• After running the Business Services Configuration Tool (for any reason)


Note:

Healthcheck verifies only installed services. It does not indicate when a service is not installed.

To run Healthcheck from a URL to check the status of web services

1. Ensure that the Healthcheck web.config file has been configured to the site’s needs.

2. On the Application Server, launch Internet Explorer.

3. In the address bar, if Healthcheck has not been configured to automatically log in, type

https://fully_qualified_domain_name/AgfaHC.Healthcheck.Escrow

or

If Healthcheck has been configured to automatically log in, type

https://fully_qualified_domain_name/AgfaHC.Healthcheck.Escrow/EscrowForm.aspx

ExampleAppendTo

https://appserver.hospital.com/AgfaHC.Healthcheck.Escrow/EscrowForm.aspx?format=html

?format=html to the endof the URL

View the results inHTML

https://appserver.hospital.com/AgfaHC.Healthcheck.Escrow/EscrowForm.aspx?refresh=60

?refresh=seconds to theend of the URL

Add a refresh frequency

https://appserver.hospital.com/AgfaHC.Healthcheck.Escrow/

?format=html&refresh=seconds to the end of theURL

View the results inHTML and add a refreshfrequency in the sameURL

EscrowForm.aspx?format=html&refresh=60

CAUTION!

Setting the refresh interval below five seconds impacts performance.

4. If Healthcheck has not been configured to automatically log in, type an IMPAX Administratorusername and password, select the login domain, and click Log in.

On the Agfa Web Services: Healthcheck page, all web services are listed with a status of Passed (green) or Failed (red).

5. To determine what the problem is for any web services with the status Failed, review theComments.

6. To check the status of the web services again, in Internet Explorer, click Refresh.


Backing up ADAM or AD LDS from the production Application Server(Topic number: 146324)

Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Service (ADLDS) is installed on the IMPAX Application Server and is responsible for maintaining the IMPAXClient user login and privilege information.

Larger sites may want to replicate or back up ADAM or AD LDS from the production ApplicationServer and restore it onto the traveling Application Server.

For complete instructions on how to migrate ADAM/AD LDS data to the traveling ApplicationServer's AD LDS database, refer to “Migrating an Application Server to Windows Server 2008 R2”(topic number 109634), and its subtopics, in the IMPAX 6.5.3 Application Server Installation, Upgrade,and Configuration Guide.

Establishing communication betweenConnectivity Manager and the Network Gateway(Topic number: 48669)

3.

Connectivity Manager facilitates the flow of information between IMPAX and the HIS/RIS. Patientand study information is forwarded to Connectivity Manager in HL7 messages, and ConnectivityManager makes the information available to IMPAX using detached management (DM). ConnectivityManager also receives queries for information and information feeds from IMPAX using the DICOMreal world device.

Add the traveling server IP addresses and hostnames to the Connectivity Manager hosts file. Thedefault location of the hosts file is C:\windows\system32\drivers\etc.

For each separate IP address of the traveling server cluster, ensure that an IMPAX real world deviceexists on Connectivity Manager:

• One IMPAX DICOM device for the Network Gateway. Enable and configure DM Out, MWLIn, and C-FIND Report In interfaces.

• One IMPAX DICOM device for the Database Server (if a separate IP address). Enable andconfigure MWL In and C-FIND Report In interfaces.

• One IMPAX DICOM device for the Application Server. Enable and configure MWL In andC-FIND Report In interfaces.

Copy the configuration that Connectivity Manager uses to interface with the production system,modifying the Called Title and host information to match that of the traveling server. If otherproduction system device interfaces are configured on Connectivity Manager, enable those interfaceson the traveling server device. The DICOM SR interfaces are an example of this.

Reports should already be in the production system database. During the production systemdowntime, report updates are saved in the RIS (or Connectivity Manager) queues until the production


system can receive the updates. When the downtime starts, configure theimpax_report_server_interface system device on Connectivity Manager to store reports to the newproduction Application Server.

Alternatively, all reports may be copied to the traveling server, and report updates sent to the travelingserver during the production system downtime. At the point that the traveling server becomes theproduction system, configure the impax_report_server_interface system device on ConnectivityManager to store reports to the traveling server. After the report data has been migrated from thetraveling server to the new production system, configure Connectivity Manager to store reports tothe new system.

For more information about configuring, integrating, and maintaining Connectivity Manager, seethe Connectivity Manager 2.4 Knowledge Base.

Adding IMPAX DICOM devices(Topic number: 30377)

Add IMPAX DICOM real world devices on Connectivity Manager so that the traveling server canquery worklists and HIS verify.

To add IMPAX DICOM devices

1. In the Managers list, hover the pointer over Device Manager.

2. When the submenu appears, select Add Real World Device.

3. In the Add New Device window, from the Class list, select IMPAX DICOM Device.

4. In the Device Name/AE Title field, type the name of the IMPAX Server.

Limit names to alphanumeric characters and hyphens (do not use spaces, special characters,or other punctuation).

5. Select Configure New Device so you can configure the device properties immediately afteradding the new device.

6. Click Add.

The device properties window for the IMPAX DICOM device is displayed.

Exporting mappings and layouts to the travelingserver(Topic number: 146238)

4.

It may be necessary to export body part mappings, specialty mappings, or demographic layouts,from the production server to the traveling server. Confirm whether any other site-specific mappingsare needed.


To export mappings and layouts to the traveling server

1. On the production Database Server, open a console window as the oracle user.

2. To create a backup directory, type

mkdir /usr/mvf/backup

cd /usr/mvf/backup

3. Export the necessary tables. For example, type

exp userid=dbadmin/dbadmin file=/usr/mvf/bodypart.txt.dmp tables=DOSR_BODY_PART

exp userid=dbadmin/dbadmin file=/usr/mvf/specialty.txt.dmp tables=DOSR_SPECIALTY

exp userid=dbadmin/dbadmin file=/usr/mvf/dosr_av.txt.dmptables=DOSR_AVAIL_DEMOG_LAYOUT_FIELD

exp userid=dbadmin/dbadmin file=/usr/mvf/dosr_de.txt.dmptables=DOSR_DEMOG_LAYOUT_FIELDS

4. On the traveling Database Server, open a console window as the oracle user.

5. Type

md /usr/mvf/backup

cd /usr/mvf/backup

6. Launch CLUI.

7. Delete the applicable data. For example, type

delete mvf_dosr_body_part

delete mvf_dosr_specialty

delete mvf_dosr_avail_demog_layout_field

delete mvf_dosr_demog_layout_fields

quit

8. FTP all the files from the production server to the traveling server. On the traveling server,type

ftp host_name_of_production_server

cd backup-directory

bi

mget *

bye

9. On the traveling Database Server, import the necessary tables. For example, type

cd /usr/mvf/backup

imp userid=dbadmin/dbadmin file=/usr/mvf/bodypart.txt.dmp tables=DOSR_BODY_PARTignore=y

imp userid=dbadmin/dbadmin file=/usr/mvf/specialty.txt.dmp tables=DOSR_SPECIALTYignore=y


imp userid=dbadmin/dbadmin file=/usr/mvf/dosr_av.txt.dmptables=DOSR_AVAIL_DEMOG_LAYOUT_FIELD ignore=y

imp userid=dbadmin/dbadmin file=/usr/mvf/dosr_de.txt.dmptables=DOSR_DEMOG_LAYOUT_FIELDS ignore=y

10. Use the Body Part Manager, Specialty Manager, or Demographic Layout Manager in theAdministration Tools to update the IMPAX database as necessary. For more details, see theIMPAX 6.5.3 Server Knowledge Base.

Creating a temporary study data repository(Topic number: 146277)

5.

Prior to the upgrade, incoming studies are routed from the production server to the traveling server,creating a temporary study data repository. Cluster linking is also enabled on the production serverto the traveling server, using the Link Cluster Updates option.

The repository allows the traveling server to act as the interim production system during the upgradeweekend and allows the site to continue to function. The studies routed during this time reside onboth the production and traveling servers.

Note:

The traveling server should HIS verify against the production Connectivity Manager; on thetraveling server, the HIS verification for each station should match that of the productionserver.

Routing to the traveling server and preparing modalities for theupgrade(Topic number: 146286)

As studies come into the production system, they must be directed from the production server tothe traveling server. In the Administration Tools, enable routing through the Routing Manager toachieve this.

In preparation for the upgrade, also ask site personnel to add the traveling server AE title and IPaddress to the modalities that will still be used to carry out examinations during the upgrade.

Enabling cluster linking on the production server(Topic number: 146360)

Cluster linking refers to linking multiple sites so that users can query and retrieve studies from all ofthese sites.


To enable cluster linking on the production server

1. Launch the production server Administration Tools.

2. On the Setup tab, click Network Management.

3. Switch to the Configuration tab.

4. From the list at the bottom of the tab, select the traveling server.

For example, select OS1TEMP.

5. Select the Cluster Linking checkbox.

6. Select the Link Cluster Updates option and clear all other options.

This allows updates to one cluster to be relayed to the other cluster (for example, a change toa study’s status). Cluster updates are performed using a proprietary syntax and can only updateclusters that use the same proprietary syntax.

7. Click Save.

Updating study status between servers(Topic number: 51514)

6.

When studies are dictated on the production server, a delay occurs before the traveling server isupdated with the new status. Due to this delay, when switching to the traveling server during theupgrade, some studies that have already been dictated switch back to a New status. To avoid thisproblem, synchronize the study status before redirecting studies to the traveling server.

To update study status between servers

1. Log into the production Database Server as the oracle user.

2. Log into sqlplus as dbadmin and type

create public database link travel connect to dbadmin identified by admin_password using'traveling_server_name';

where admin_password is the password for the dbadmin user on the traveling server andtraveling_server_name is the name of the traveling server.

3. In a text editor such as vi, edit the /var/opt/oracle/tnsnames.ora file and add the traveling server.

traveling_server_name.world = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = impax.world) (PROTOCOL = TCP) (Host = traveling_server_name) (Port = 1521) ) ) (CONNECT_DATA = (SID = MVF)


))

4. To perform the report status update, type the following into sqlplus:

declare

the_counter number := 0;

cursor study_cursor is

select t.study_ref, s.status from dosr_study s, dosr_study@travel t

where s.patient_id = t.patient_id and s.accession_number = t.accession_number

and s.status <> t.status;

begin

for study_record in study_cursor LOOP

update dbadmin.dosr_study@travel set status = study_record.status where study_ref =study_record.study_ref;

the_counter := the_counter +1;

if mod (the_counter, 100) = 0 then

commit;

end if;

end loop;

commit;

end;

/

5. To drop the link to the traveling server database, type the following in sqlplus:

drop public database link travel;

Stopping Connectivity Manager queues(Topic number: 67550)

7.

If the Connectivity Manager’s inbound devices have not been stopped, stop the IMPAX outboundDM Out and impax_report_server queues prior to shutting down IMPAX for the upgrade. Messagesin stopped queues are not processed and remain in the queue until the queue is restarted. Outboundqueues are restarted automatically if the Agfa Connectivity service is restarted, or if the ConnectivityManager server is restarted.

To stop Connectivity Manager queues

1. In Connectivity Manager, open Service Tools and click Queue Manager.

2. In the Queue List table, select the checkbox beside each queue belonging to a device with a DMOut or impax_report_server component.


3. Click Stop.

The status of the queues changes to Stopped.

Connectivity Manager outbound message queues must be configured with the new server settingsbefore messages are added to the queues. Consult a Connectivity Manager integrator to create adevice for the destination IMPAX server. Report updates can be sent to only one IMPAX server,after all reports have been copied to that server.


3Using the travelingserver during theupgrade

After the traveling server has been staged and configured, the production system can be shut downand upgraded. Refer to the AS3000 Upgrade Guide—IMPAX 6.2 or Later to IMPAX 6.5.3 for detailedinformation on performing the actual upgrade.

Enabling cluster linking on the traveling server(Topic number: 146363)

1.

After the production system is shut down, enable cluster linking on the traveling server to theproduction server, using the Link Cluster Updates option.

This allows traveling cluster updates to be relayed to the production cluster when the productionserver comes back online. (Transit jobs for the updates build up in the traveling server queue untilthe production server comes back online.) This captures any new studies acquired during the upgrade,as well as some changes to old studies such as study status and comment changes.

To enable cluster linking on the traveling server

1. Launch the traveling server Administration Tools.

2. On the Setup tab, click Network Management.

3. Switch to the Configuration tab.

4. From the list at the bottom of the tab, select the production server.

5. Select the Cluster Linking checkbox.

6. Select the Link Cluster Updates option and clear all other options.


This allows updates to one cluster to be relayed to the other cluster (for example, a change toa study’s status). Cluster updates are performed using a proprietary syntax and can only updateclusters that use the same proprietary syntax.

7. Click Save.

Redirecting studies to the traveling server(Topic number: 60448)

2.

Configure the modalities to redirect studies to the traveling server, so that the studies remain accessiblewhile the upgrade progresses. How studies are redirected is modality-specific and is not documentedin this publication.


4Transitioning to theupgraded productionserver

After the production server has been upgraded to IMPAX 6.5.3, new studies and updates of oldstudies can be propagated to the production system, and the traveling server can be shut down. Anumber of tasks must be performed to achieve this.

Restarting Connectivity Manager queues(Topic number: 67610)

1.

If Connectivity Manager is currently deployed, and you have stopped any queues, use the QueueManager to restart them. Once the queue is restarted, messages sitting in them are processed.

To restart Connectivity Manager queues

1. In the Connectivity Manager Service Tools, click Queue Manager.

2. In the Queue List table, select the checkbox beside the queue of any system device or real worlddevice 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.


Redirecting studies to the production server(Topic number: 10180)

2.

If necessary, you can now configure the modalities to redirect studies to the production server, ratherthan the traveling server. How studies are redirected is modality-specific and is not documented inthis publication.

Because cluster linking was enabled on the traveling server to the production server, updates arenow relayed to the production cluster as soon as the production server comes back online. Any newstudies acquired during the upgrade are captured and propagated to the production server, as wellas some changes to old studies such as study status and comment changes.

Handling updates to old studies(Topic number: 146315)

3.

During the upgrade weekend, if all structural changes (such as splits and merges) to the old studieson the traveling server were avoided, this procedure can be skipped. For more details, see Resolvingdifferences between the production and traveling server (refer to page 8).

Any structural changes to old studies that exist on both the production and traveling servers requirethat these studies be deleted from the production server and then manually transmitted from thetraveling server to the production server. These include any study changes made through theAdministration Tools, or directly using CLUI or sqlplus.

CAUTION!

To avoid losing studies from both clusters, perform this task only if absolutely necessary. Bevery careful not to delete any studies from the production server unless they reside on thetraveling server as well.

To handle updates to old studies

1. Delete the identified subset of studies (refer to page 32) from the production server.

2. Transmit these studies (refer to page 33) from the traveling server to the production server.

Any updates to these studies on the traveling server are propagated to the production server.

Deleting studies from the production server(Topic number: 147184)

Using the Administration Tools or CLUI, you can delete the identified subset of studies from theproduction server.


CAUTION!

You cannot recover a deleted study. Use extreme caution when deleting studies—particularlywhen deleting all instances of a study.

Ensure that the studies reside on the traveling server prior to deleting them from the productionserver.

Deleting studies from all caches and archives(Topic number: 8354)

To delete studies from the production server, you can use the Administration Tools.

To delete studies from all caches and archives

1. On the Daily tab, click Study Manager.

2. Find the studies to delete.

3. From the list, select the studies to delete.

4. Click Delete completely.

5. Confirm that you want to delete the selected studies completely.

Deleting studies from all locations using CLUI(Topic number: 147181)

To delete studies from the production server, you can use CLUI.

To delete studies from all locations using CLUI

1. Launch CLUI.

2. To switch to menu mode, type go menu.

3. Select 1 for Study Manager, then 11 for Delete Studies Menu.

4. Select 10 for Delete study from all locations.

Transmitting or sending studies from the traveling server(Topic number: 10188)

Using the Administration Tools or CLUI, you can send the studies on the traveling server to theproduction server.


Transmitting studies using the Administration Tools(Topic number: 58342)

Use the Administration Tools to send the studies on the traveling server to the production server.

To transmit studies using the Administration Tools

1. In Administration Tools, on the Daily tab, click Study Manager.

2. Search for studies, and from the results list, select the studies to transmit.

3. Click Transmit.

4. In the dialog, select the station you want to transmit the study to.

5. Click Transmit.

Creating SEND jobs using CLUI(Topic number: 58345)

Use CLUI to send the studies on the traveling server to the production server.

To create SEND jobs using CLUI

1. In CLUI, specify the list of studies to transfer with the following command:

study send study_ref_1 study_ref_2... study_ref_n destination

or

Generate the list of studies to transfer with the following query:

save_refs a select study_ref from dosr_study where column = constraint

2. To switch to menu mode, type go menu.

3. Select 1 for Study Manager, then 9 for Send.

4. At the prompt for the list of studies to process, type a to reference the save_refs list of studies.

5. At the prompt for the destination, type the destination.

Updating the status of production studies afterthe upgrade(Topic number: 146289)

4.

After the upgrade, identify any studies that do not have a status of New on the traveling server. Alist of these files is transferred to the production server where their status is updated to reflect thatof the traveling server, synchronizing the two servers.

To update the status of production studies after the upgrade

1. Log into the traveling Database Server as the service user.


2. Using FTP or SCP, copy the update_statuses.pl script to the /usr/mvf directory on the travelingserver.

The update_statuses.pl script is available on MedNet athttp://ftp.agfa.be/HE/software/PACS/Enterprise_Core_Software/R6_Upgrades/

If you cannot access the script, contact Agfa Professional Services.

3. The file should not contain any ^M control characters (carriage returns) or other non-printingcharacters. To verify this, type

cat -v

4. To convert the file to a UNIX format and remove any extraneous control characters, type

dos2unix update_statuses.pl update_statuses.pl

5. To change the permissions of the file to read, write, and execute for all, type

chmod 777 update_statuses.pl

6. To run the script, type

./ update_statuses.pl

A SQL statement file, study_statuses.sql, is created.

7. FTP or SCP the study_statuses.sql file to the /usr/mvf directory on the production DatabaseServer.

8. On the production Database Server, to update the status of the studies, type

clui -I study_statuses.sql

For all studies in the file, the status of the study is updated in the production database.

Cleaning up the traveling server after the upgrade(Topic number: 146321)

5.

After the upgrade has been completed successfully and the production system is up and runningagain, you must perform the following post-upgrade tasks and clean up the traveling server.

To clean up the traveling server after the upgrade

1. Log into the traveling Database Server as the service user.

2. Delete the hosts file (/etc/hosts), or create a blank one pointing to the IP address 127.0.0.1.

3. Delete the subnet mask (/etc/netmasks), or point it to 255.255.255.0, and the gateway(/etc/defaultrouter).

4. Remove the traveling server AE title from the Connectivity Manager and production systemhosts files.

5. Rebuild the traveling server database. As the mvf user, type

/usr/mvf/bin/build-database

6. To remove any stray images or DICOM files from the traveling server caches, type


http://ftp.agfa.be/HE/software/PACS/Enterprise_Core_Software/R6_Upgrades/

cd /cache/mvfcache

ls -l

rm -r *

7. Using the packing list, pack up the traveling server. Verify that everything that came with it isincluded.


ATraveling serverchecklist: Upgradingfrom IMPAX 6.2 or later

This checklist provides qualified Agfa personnel with a high-level and efficient overview of theinstallation, configuration, and verification of a traveling server. Retain this checklist on site forfuture reference.

Customer information

__________________________________________________________Site name:

__________________________________________________________Street address:

__________________________________________________________City, state, zip:

__________________________________________________________Contact name / title:

__________________________________________________________Contact phone:

__________________________________________________________Contact email:

__________________________________________________________Purchase order:

Network connectivityObtain the IP address, subnet mask, and gateway information for the traveling server (DatabaseServer and Application Server) from the site administrator.

Application ServerDatabase Server

IP address:

Subnet mask:

Gateway:


Pre-upgrade checksInform your project manager that a traveling server license is required.

Identify display stations to point to the traveling server.

Obtain IP address for the traveling server.

Confirm location for the traveling server. Verify that you have adequate power, network drops,and ventilation.

Traveling server (Database Server) tasksUnpack the traveling server and check packing list. Create a packing list if one is not included.Check the traveling server for loose cables, box damage. Check the tilt and shock indicators.Report any damage to Staging.

Configure the IP address (/etc/hosts), subnet mask (/etc/netmasks), and gateway(/etc/defaultrouter).

Include the hostname and IP address of the traveling server on the master hosts file. Copy thehosts file to the entire IMPAX cluster including Connectivity Manager and DS3000 clients thatwill be configured to point to the traveling server. Ping the traveling server and ping otherdevices from the traveling server using the assigned hostnames; for example, ping os1temp.

Check the network connection by running dmesg | grep -i up. Ensure you are running at least100 Mbps full-duplex; 1 GB full-duplex is preferred.

Check the date and time. To change the date, type date -u mmddHHMM.

Confirm that the Network Gateway package has been installed in the /install_info file. Youshould see: GATEWAY='y'.

Check the license: cat /data/logs/IMPAX.log | grep -i valid.

If the traveling server came from another site, to create a clean database, run/usr/mvf/bin/build-database.

To verify database connectivity, run CLUI.

Check the Oracle tablespaces. Log in as the service user and run monitor_update andmonitor_stats. For additional space, run monitor_add. Size recommendations:

1 x 2000 MBMVF

1 x 2000 MBMVFINDX

3 x 2000 MBMVFL

3 x 2000 MBMVFLINDX

1000 MBTEMP

1000 MBUNDO

250 MBSYSTEM


UPDATE map_ini SET ini_value =’3’ WHERE ini_key ='MAX_NON_MOVE_JOBS_PER_DEST’

UPDATE map_ini SET ini_value =’3’ WHERE ini_key = 'MAX_MOVE_JOBS_PER_DEST’

Check the traveling server caches for leftover images/DICOM files:

cd /cache/mvfcache

ls -l

rm -r *

Launch the Administration Tools.

Add the modalities that will transmit to the traveling server using Network Management.

Add the IMPAX core Network Gateways on the traveling server using Network Management.

Add the traveling server to the IMPAX site cluster using Network Management.

Confirm a successful DICOM association test.

Update the Connectivity Manager hosts file to include the traveling server IP address andhostname. On Connectivity Manager, add a real world device for the traveling server. StartMWL, DM Out and C-Find.

On the production Database Server, enable cluster linking for the traveling server only: Launchthe Administration Tools. In Network Management, select TS (OS1TEMP). Switch to theConfiguration tab. Select Cluster Linking. Select Link Cluster Updates. Clear all other options.Click Save.

Create users and, if possible, generic users. Test functionality on the traveling server.

Create body part and specialty mappings as needed. Confirm with site if any other mappingsare necessary.

Route studies from the IMPAX cluster to the traveling server.

Ask site personnel to add the AE title and IP address of the traveling server to the modalitiesthat will continue to perform examinations during the upgrade.

Traveling Server (Application Server) tasksIf necessary, create the AgfaService user in the Administrators group.

Verify the computer name and FQDN.

Join the IMPAX workgroup or the site domain.

Right-click My Computer and select Properties. Switch to the Advanced tab and, underPerformance, click Settings. Switch to the Advanced tab. Under Virtual memory, click Change.Under Paging file size for selected drive, select System managed size.


Right-click My Computer and select Properties. Switch to the Advanced tab and, underPerformance, click Settings. Switch to the Data Execution Prevention tab and select Turn onDEP for essential Windows programs and services only.

Right-click My Computer and select Properties. Switch to the Advanced tab and, under Startupand Recovery, click Settings. Select Time to display list of operating systems and set the timeto 5 seconds.

If C:\TEMP does not exist, create the folder. Right-click My Computer and select Properties.Switch to the Advanced tab and click Environment Variables. Change the TEMP and TMPuser variables to C:\TEMP.

Right-click My Computer and select Properties. Switch to the Remote tab and, under RemoteDesktop, select Allow users to connect remotely to this computer. Click Select Remote Usersand add the AgfaService user.

In Windows Explorer, select Tools > Folder Options. Switch to the View tab. Under Files andFolders, select Show hidden files and folders. Clear Hide extensions for known file types.

Open Control Panel. Select Regional and Language Options. Switch to the Regional Optionstab. Click Customize. Switch to the Date tab and set the short date format to MM/dd/yyyy.

Open Control Panel. Select Date and Time. Switch to the Time Zone tab and select theappropriate time zone for the the traveling server location.

Synchronize the time of the Application Server to a default gateway or a time server. In acommand prompt:

net time /setsntp:IP-address-of-default-gateway-or-time-server

net time /querysntp

Double-click C:\SOFTWARE\REGISTRY_UPDATE\modify.login.reg.

Confirm that sufficient free space exists on all drives.

Set the Start menu and Control Panel to classic views.

Check the Event Viewer and fix any errors, if possible. Clear all events and restart the systemto confirm that the errors do not reappear.

Stop and disable Windows Firewall in Windows Services.

Launch the Administration Tools to install Java on the Client. Open Control Panel. Select Java.Switch to the Update tab and clear the Check for Updates Automatically checkbox.

Disable IIS logging. Right-click My Computer and select Manage. In the Computer Managementwindow, select Services and Applications > Internet Information Services > Web Sites >Default Web Site. Right-click Default Web Site and select Properties. Switch to the Web Sitetab and clear the Enable Logging checkbox.

Disable Recycle Worker Processes. On the Application Server, open the IIS Manager. SelectApplication Pools. Right-click DefaultApp Pool and select Properties. Clear the Recycleworker processes (in minutes) checkbox.


Change the startup type to Automatic for the Task Scheduler, Background Intelligent Transferand PACS Client Updater services.

Complete the IMPAX 6.x—Splitting and Recycling Web Services Application Pools on theApplication Server Information Bulletin (Livelink Node ID 26813149).

Perform an Application Server Healthcheck. Create a Healthcheck shortcut or favorites link:https://fully_qualified_domain_name/AgfaHC.Healthcheck.Escrow/EscrowForm.aspx.

Production Connectivity Manager tasksAdd real world devices for the traveling server (Database Server/Network Gateway andApplication Server).

Start services: MWL, DM Out and C-Find.

HIS verify a study from the traveling server.

Post-upgrade checksDelete the hosts file (or create a blank one with the traveling server pointing to 127.0.0.1),subnet masks and gateway.

Delete all backed up files on the traveling server.

Delete all site-specific items used during and needed only for the upgrade.

Remove the traveling server from the IMPAX site network and Connectivity Managerconfiguration.

Clean the main database: /usr/mvf/bin/build-database.

Remove leftover images/DICOM files from the traveling server caches:

cd /cache/mvfcache

ls -l

rm -r *

Pack up the traveling server. Using the packing list, verify that everything that came with thetraveling server is included.




BInstalling and runningthe Cross-ClusterDictation Interlock tool

The Cross-Cluster Dictation Interlock tool synchronizes the dictation status of studies between oldand new IMPAX systems when these are running in parallel—such as may happen when using atraining server, when using a traveling server (AS3000 sites), or if planning to run the upgradedIMPAX cluster alongside the previous-version IMPAX cluster for a transition period.

Note:

Do not confuse CCDI with Dual Cluster Claim and Assign (DCCA), which allows two activeclusters of the same version (IMPAX 6.5.2 or later), running in parallel, to synchronize studystatus notifications and claim and assign messages between the two clusters as though theywere one. For details, see “Understanding Dual Cluster Claim and Assign” (topic number128193) in the IMPAX 6.5.3 Application Server Knowledge Base.

A dictation interlock already exists within a single IMPAX cluster, preventing two users from dictatingthe same study. This tool extends that interlock to two IMPAX clusters: the previous version andthe new. It uses native components within IMPAX to send signals between the two systems that astudy’s dictation status has changed. During the installation and configuration, a new role and aservice called Study Status Relay are created to convey and receive the messages.

Study statuses that are synchronized are the following:

• DICTATION_STARTED

• TRAINEE_DICTATION_STARTED

• INTERPRETATION_TRANSCRIBED

• INTERPRETATION_APPROVED

• DICTATION_COMPLETED


• TRAINEE_DICTATION_COMPLETED

Cross-Cluster Dictation Interlock installationprerequisites: IMPAX 6.2 or later upgrades(Topic number: 59202)

The IMPAX 6.5.3 Cross-Cluster Dictation Interlock components are placed on the IMPAX 6.5.3Application Server when the Business Services software is installed. You will find the componentsin the Tools sub-directory; for example, in C:\Program Files\Agfa\Impax BusinessServices\Tools\Cross-Cluster Dictation Interlock\Cross.Cluster.Dictation.Interlock_6.5.3.0.zip. Youmust extract the zip file. Note that it contains components for IMPAX 5.2 or 5.3, along with the6.5.3 components, but does not contain the components for IMPAX 6.2 or later.

You must separately acquire the Cross-Cluster Dictation Interlock components released for theversion of IMPAX you are upgrading from. For example, if upgrading from IMPAX 6.2.1 and wantingto enable cross-cluster dictation interlock with IMPAX 6.5.3, you must acquire the 6.2.1 Cross-ClusterDictation Interlock components and place them on the 6.2.1 Application Server. These will thencommunicate with the 6.5.3 Cross-Cluster Dictation Interlock components on the 6.5.3 ApplicationServer.

Note:

The IMPAX 6.4 or later Cross-Cluster Dictation Interlock components were placed on theIMPAX Application Server when the Business Services software was installed.The IMPAX 6.2and 6.3 Cross-Cluster Dictation Interlock components were packaged separately from IMPAX.The components would have likely been placed on the Application Server, so look for theappropriately named zip file. If you cannot locate the components, contact Agfa ProfessionalServices.

Copying the 6.2 or later Cross-Cluster DictationInterlock components(Topic number: 48220)

You must make the appropriate version of the Cross-Cluster Dictation Interlock components availableon the IMPAX 6.2 or later Application Server and on the IMPAX 6.5.3 Application Server.

To copy the 6.2 or later Cross-Cluster Dictation Interlock components

1. On the IMPAX 6.5.3 Application Server, copy the study-status-signal-relay folder from theCross-Cluster Dictation Interlock zip in the Tools subdirectory to an appropriate folder, suchas to C:\Program Files\Agfa\Impax Business Services.

The service will run from anywhere, but you should place it in a folder that is unlikely to bedeleted.


2. Open a command prompt.

3. Change to the directory containing the copied files.

4. Type import-study-status-relay.bat.

5. In the Apply Study Status Relay ADAM Schema dialog, click OK.

This creates a Study Status Relay role.

6. On the 6.2 or later Application Server, install the 6.2 or later version of the Cross-ClusterDictation Interlock components.

For instructions, refer to the documentation delivered with the 6.2 or later Cross-ClusterDictation Interlock tool.

CAUTION!

Do not copy the 6.5.3 Cross-Cluster Dictation Interlock components onto a 6.2 or laterApplication Server. The 6.5.3 components will not work correctly on older versions of theApplication Server.

Configuring a firewall exception for theCross-Cluster Dictation Interlock tool(Topic number: 111054)

The Windows firewall filters and blocks unsolicited incoming network traffic. To use the Cross-ClusterDictation Interlock tool, you must define an exception in the Windows firewall to allow the TCPport to listen for signals coming in from the remote cluster.

To configure a firewall exception for the Cross-Cluster Dictation Interlock tool

1. On the IMPAX 6.5.3 Application Server, open Control Panel.

2. Select Windows Firewall.

3. Switch to the Exceptions tab.

4. Click Add Port.

5. In the Name field, type a name for the exception; for example, Study Status Relay or somethingsimilar.

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 folderwhere study-status-relay.bat is installed (for example, C:\Program Files\Agfa\ImpaxBusiness Services\study-status-signal-relay) and open the Study.Status.Relay.exe.configfile in a text editor.

b. The port number value can be found under <StudyStatusRelayConfiguration> andbetween the <SignalListenerPort> and </SignalListenerPort> tags.


7. Click OK.

8. To close the Windows Firewall dialog, click OK.

9. Configure a firewall exception on the Windows machine in the remote cluster as well.

The new firewall exception takes effect immediately. You do not have to restart the server.

Configuring the Study Status Relay role for upgradesfrom 6.2 or later(Topic number: 59181)

The newly created Study Status Relay role requires a user called remote-dictation, and an appropriatelicense. You must set up this role twice: once on the 6.2 or later Application Server, then again onthe 6.5.3 Application Server.

To configure the Study Status Relay role for upgrades from 6.2 or later

1. Launch an IMPAX Client connected to the 6.2 or later Application Server.

2. Log into the Client as an Administrator user.

3. From the Configure drawer menu , select Users and Roles.

4. In the navigation pane, right-click the Study Status Relay role and select Add User.

5. In the details pane, under the User bar, switch to the Information tab.

6. Type a Name for the user, such as Remote Dictation Automated User.

7. In the Login field, type remote-dictation.

8. Type a Password and note what this password is.


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 > Addlicense_type

where license-type is an appropriate and available license for this role. (Dictation is not alicense-controlled feature.)

The changes are saved automatically when you switch context.

12. Launch an IMPAX Client connected to the 6.5.3 Application Server.

13. Repeat steps 2 to 11 on that Client.

Configuring the Study Status Relay service(Topic number: 48230)

You can now configure the communication service between the previous version of IMPAX andIMPAX 6.5.3. The goal is to transmit relevant study status changes between these two clusters.

To configure the Study Status Relay service

1. On the 6.5.3 Application Server, open a command prompt.

2. Change to the C:\Program Files\Agfa\Impax Business Services\study-status-signal-relaydirectory.

3. Type

Study.Status.Relay.EncryptionTool.exe password_for_remote-dictation_user


where password_for_remote-dictation_user is the password you defined and noted for theremote-dictation user.

4. Copy the long string that is returned from this command.

Tip:

If it is too difficult to copy the string from the command-line interface, output the resultto 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 <UserPassword> and </UserPassword>tags, paste the long string.

For example:

...<UserPassword>AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAABbkEiV/jjUWSVOOgdR9RYQQAAAACAAAAAAADZgAAqAAAABAAAACiWdpGofmXAMqUZ5YsA5lkAAAAAASAAACgAAAAEAAAAMWx8NfIDRPiPIV+727lgQgQAAAA5wKiHz2sKwU4IlvifPm02BQAAAD5upFcxlJes1vaYnwvF5WMJo/6lQ==</UserPassword>...

7. Update the values of LoginServiceUrl, StudyInfoServiceUrl, and MessagingServiceUrl withthe local Application Server’s fully qualified domain name.

8. Update the value of RemoteSignalHost with the host name or IP address of the computer inthe previous-release version of IMPAX that is running the study-status-relay service.

9. Save and close the file.

10. In the command prompt, type

install_study_status_relay_service.bat

If a log4net error is returned, you can safely ignore this message.

To diagnose other errors or check status, consult the Study.Status.Relay.log file located in thestudy-status-signal-relay folder.

If ready to use the service, proceed to the next topic, Running the Cross-Cluster Dictation Interlocktool (refer to page 47).

Running the Cross-Cluster Dictation Interlock tool(Topic number: 47379)

The Cross-Cluster Dictation Interlock (CCDI) tool synchronizes both the dictation status and theclaim status of studies between the previous version of IMPAX and IMPAX 6.5.3, when these are

running in parallel—such as may happen when using a training server, when using a traveling server,or if planning to run the upgraded IMPAX cluster alongside the previous-version IMPAX clusterfor a transition period.

Synchronization of the claim status of studies occurs only between versions of IMPAX that supportshared workflows from which radiologists can then claim ownership of studies.

Note:

Do not confuse CCDI with Dual Cluster Claim and Assign (DCCA), which allows two activeclusters of the same version (IMPAX 6.5.2 or later), running in parallel, to synchronize studystatus notifications and claim and assign messages between the two clusters as though theywere one. For details, see “Understanding Dual Cluster Claim and Assign” (topic number128193) in the IMPAX 6.5.3 Application Server Knowledge Base.

To run the Cross-Cluster Dictation Interlock tool

1. On the 6.5.3 Application Server where the Relay service is running, open a command prompt.

2. Type the following command:

net start StudyStatusRelayService

3. Exit the command prompt.


AApplication Server

Intermediary server between IMPAX Clientand IMPAX Server machines. LDAP,Documentation, and other Business Servicesreside on the Application Server.

Autopilot

Service that removes old and expired datawhen the cache starts to get full. Thismaintenance function keeps the database to amanageable size.

Ccache

Temporary storage area for data on acomputer’s local or external hard drives.

cluster linking

Links more than one system on a site ormultiple systems between sites.You can searchand retrieve studies from all the clusters as ifthey are one, regardless of physical location.

Connectivity Manager

A middleware component in the integrationbetween hospital information systems andother hospital imaging departments.Connectivity Manager also providesconnectivity to each modality and the PACS.

DDatabase Server

Server that hosts the Oracle or SQL database.

Ffirewall

On a local area network (LAN) connected toa larger network, the security system thatprevents outside intrusion and that keepsinternal information from getting out.Typically, all traffic must pass through themachine on which the firewall is implemented.

HHIS verification

An option that forces the PACS to verify allincoming images from an acquisition stationor modality against specific criteria, such asthe patient ID and accession number. ThePACS sends a message through the RISGateway to verify the criteria against what iscontained in the HIS. If the criteria match,then the images can be stored permanently.

IIP address

The Internet Protocol address is a numericaddress that identifies the station to otherTCP/IP devices on the network.

JJava

An object-oriented programming language.

Glossary


NNetwork Gateway

The Network Gateway is part of the IMPAXMVF cluster. Essentially, this is the workflowmanager of the IMPAX 6.0 and later system.The Network Gateway controls the studiescoming into the cluster from an acquisitionstation, validates these incoming studiesagainst information from the HIS or RIS, androutes the validated studies to cache or archive.

Pproduction server

The permanent IMPAX Server—the one thatremains in place after the training server isreconfigured and the traveling server removed.

RRIS

Radiology Information System. Responsiblefor scheduling exams and for reportmanagement in the Radiology department.

SStore and Remember archiving

Also called PACS Store and Rememberarchiving. A configuration in which an IMPAXsystem is set up as a PACS Store andRemember Archive, and used for archivingstudies to an archive external to the IMPAXsystem.

Ttraining server

A system used to train users on IMPAX 6.5.3as well as migrate user accounts, passwords,and preferences from previous versions ofIMPAX. When a traveling server is not used,this server may also be used as a temporaryreport repository. The training server isintended to operate in non-clinical mode.

traveling server

An AS3000 server running a version ofIMPAX, shipped to the site approximately twoto four weeks prior to the upgrade weekend.Incoming studies are routed to this server tocreate a temporary study data repository. Itcan also house reports migrated from PACSBroker. This server becomes the productionserver during the upgrade weekend, greatlyreducing site down time.


AADAM

backing up.............................................22adding

IMPAX DICOM devices.......................23AD LDS

backing up.............................................22Administration Tools

transmitting studies..............................34AgfaService

adding as a remote user........................13application pools

splitting..................................................13Application Servers

backing up.............................................22location of Cross-Cluster DictationInterlock.................................................43running Cross-Cluster DictationInterlock...........................................43, 46

archivedeleting studies from.............................33

Archive Serverinstalling..........................................10, 11

automatingsoftware updates....................................19

Autopilot deletionspreventing..............................................11

BBackground Intelligent Transfer service.....13BITS

See Background Intelligent Transferservice

body part mappingsexporting...............................................23

browsers

security warning....................................19build-database script....................................10build-IMPAX-workstation-databasescript.............................................................10

Ccaches

deleting images from.............................33removing files from...............................35

CCDI toolSee Cross-Cluster Dictation Interlock tool

checklist for traveling server........................37choosing

See selectingclaim status

avoiding conflicts..................................47cleaning database.........................................35clocks

synchronizing.......................15, 16, 17, 18CLUI

creating SEND jobs...............................34deleting studies......................................33

cluster linkingenabling............................................25, 29

concurrent jobsconfiguring............................................13

configuring roles..........................................45connecting

servers....................................................25Connectivity Manager

adding devices.......................................23configuring............................................22starting queues......................................31stopping queues.....................................27

copying6.2 or later Cross-Cluster DictationInterlock components...........................43

Index


copyright information...................................2creating

temporary study data repository..........25users.......................................................45

Cross-Cluster Dictation Interlock toolcopying 6.2 or later components..........43firewall exception..................................44installation prerequisites.......................43installing................................................42running..................................................47

cutoff pointidentifying................................................8

DDatabase Server

configuring............................................10synchronizing with traveling..........26, 34

Data Execution Preventionturning on..............................................13

date and timeconfiguring............................................13setting.....................................................10

deletingfrom production server.........................32studies..............................................32, 33studies using CLUI................................33

demographic layoutsexporting...............................................23

DEPSee Data Execution Prevention

Device Managerconfiguring............................................23

DICOM devices............................................22DICOM IMPAX devices..............................23dictating

avoiding conflicts.............................42, 47synchronizing status..............................26

disablingIIS logging..............................................20Java automatic updates.........................19

documentationgiving feedback........................................3related......................................................9warranty statement.................................2

domaintime synchronization............................18

downloading Java Runtime.........................19

Eemail

documentation feedback........................3enabling

cluster linking..................................25, 29environment variables

editing....................................................13Event Viewer

fixing errors...........................................13exceptions

firewall...................................................44extensions

showing files..........................................18external study references

deleting..................................................33external time source

synchronizing to....................................16

Ffiles

extensions, showing..............................18firewall

configuring for Cross-Cluster DictationInterlock tool.........................................44exceptions..............................................44

foldersshowing..................................................18

full-duplex system........................................10

Ggetting started.................................................6guides

related......................................................9

HHealthcheck..................................................20hiding files....................................................18hostnames

pinging...................................................10hosts file

editing....................................................10


IIIS

disabling logging...................................20IMPAX DICOM devices

workflow communication....................22IMPAXwsql package

adding....................................................10interim production system..........................29internal time source

synchronizing to....................................17

JJava Runtime

downloading..........................................19updates of..............................................19

KKnowledge Bases

related......................................................9

Llicense keys

obtaining................................................10licenses

assigning Client.....................................45Link Cluster Updates option.................25, 29logging

disabling IIS...........................................20

MMAC address

retrieving...............................................10manufacturer’s responsibility........................2maximum concurrent jobs..........................13modalities

preparing for upgrade...........................25redirecting studies.................................32

monitor_add script......................................12monitor_stats script.....................................12monitor_update script.................................12move jobs

configuring............................................13

Nnames

tablespace...............................................12network connection

checking.................................................10Network Gateway

package..................................................10workflow communication....................22

new studies.............................................26, 34non-move jobs

configuring............................................13

Oold studies

handling updates...................................32old versus new studies

resolving differences................................8operating systems list

setting display time...............................13overviews

upgrading with traveling server..............6

Ppacking up traveling server..........................35PACS Client Updater service.......................13PACS Store and Remember archive

adding..............................................10, 11paging file setting

changing................................................13passwords

remote dictation....................................46ports

firewall exceptions.................................44post-upgrade tasks.......................................35preparatory tasks..........................................10prerequisites

Cross-Cluster Dictation Interlock toolusage......................................................43

production serverdeleting from.........................................32studies, moving..........................................transitioning to......................................31transmitting to..........................................


Qqueues

Connectivity Manager.....................27, 31

Rreal world devices

adding....................................................23Recycle Worker Processes

disabling.................................................13redirecting studies..................................30, 32registered trademarks....................................2remote desktop

configuring............................................13reports

avoiding conflicts..................................42avoiding dictation conflicts..................47synchronizing study status....................26

restartingqueues....................................................31

rolesStudy Status relay............................43, 45

routing studiesto traveling server..................................25

Ssecurity

browser access........................................19selecting

time server.............................................18SEND jobs

creating..................................................34services

Study Status Relay.................................46showing

file information.....................................18software registry

updating.................................................13speciality mappings

exporting...............................................23starting

Connectivity Manager queues..............31startup type

changing................................................13stations

enabling cluster linking...................25, 29

setting to archive...................................11status of studies

relaying to older clusters.......................46synchronizing after upgrade.................34synchronizing during upgrade.............26

status of web services...................................20stopping

Connectivity Manager queues..............27Store and Remember archive

adding....................................................11structural changes

avoiding...................................................8capturing................................................32

studiesdeleting..................................................33deleting from all caches and archives....33migrating...............................................34moving.............................................32, 34redirecting to traveling server...............30setting status of......................................46synchronizing after upgrade.................34synchronizing during upgrade.............26

suggestions for documentation.....................3summary

traveling server upgrades......................37upgrading with traveling server..............6

synchronizingserver clocks.........................15, 16, 17, 18studies after upgrade.............................34studies during upgrade.........................26

Ttables

database.................................................12tablespace sizes

increasing...............................................12Task Scheduler service.................................13temporary study repository

creating..................................................25time server

selecting.................................................15synchronizing.......................15, 16, 17, 18

time zoneselecting.................................................13

Tools, Migrationmonitor_add and monitor_stats..........12


topics in guides and Knowledge Basesgiving feedback on..................................3

trademarks......................................................2transmitting studies.....................................34traveling server

adding to modalities.............................25checklist.................................................37configuring............................................10overview...................................................6redirecting studies to.............................30redirecting studies to productionserver......................................................32synchronizing study status on..............26transmitting from..................................33

Uupdating

study status between servers...........26, 34URL

running Healthcheck............................20users

configuring roles...................................45editing variables....................................13

Wwarranty statements.......................................2web services

checking.................................................20Healthcheck status................................20splitting..................................................13

Windowssynchronizing to external timesource.....................................................16synchronizing to internal time source..17time server

configuring.....................................15Time Service, configuring.....................18

Windows Explorerconfiguring............................................18

Windows Firewalldisabling.................................................13


as3000 traveling server guide impax 6.2 or later to impax 6.5 · this guide is intended for service...

Documents