GE Healthcare
Technical
Publication
Direction 5138756 -100
Revision 2
AWRA (AW Remote Access)
Installation / Service Manual
Copyrighted © by GE Healthcare, 2006
LEGAL NOTES
TRADEMARKS
All products and their name brands are trademarks of their respective holders.
OMISSIONS & ERRORS
Customers, please contact your GE Sales or Service represenatives.
GE personnel, please use the GEMS iTRAK Process to report all omissions, errors, and defects in this publication.
COPYRIGHTS
All Material Copyrighted(c) 2006 by the General Electric Company, All rights reserved.
COUNTRY OF MANUFACTURE
GE HealthCare – USA
GE HealthCare - France
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
2 of 102
IMPORTANT PRECAUTIONS
LANGUAGE
WARNING
This Service Guide is available in English only.
If a customer’s service provider requires a language other than English, it is
the customer’s responsibility to provide translation services.
Do not attempt to service the equipment unless this service manual has
been consulted and is understood.
Failure to heed this Warning may result in injury to the service provider,
operator or patient from electric shock, mechanical or other hazards.
AVERTISSEMENT
Ce Manuel de maintenance n’est disponible qu’en anglais.
Si le technicien du client a besoin de ce manuel dans une autre langue que
l’anglais, c’est au client qu’il incombe de le faire traduire.
Ne pas tenter d’intervention sur les équipements tant que le manuel Service
n’a pas été consulté et compris.
Le non-respect de cet avertissement peut entraîner chez le technicien,
l’opérateur ou le patient des blessures dues à des dangers électriques,
mécaniques ou autres.
WARNUNG
Dieses Kundendienst-Handbuch existiert nur in englischer Sprache.
Falls ein fremder Kundendienst eine andere Sprache benötigt, ist es
Aufgabe des Kunden für eine entsprechende Übersetzung zu sorgen.
Versuchen Sie nicht, das Gerät zu reparieren, bevor dieses KundendienstHandbuch nicht zu Rate gezogen und verstanden wurde.
Wird diese Warnung nicht beachtet, so kann es zu Verletzungen des
Kundendiensttechnikers, des Bedieners oder des Patienten durch elektrische
Schläge, mechanische oder sonstige Gefahren kommen.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
3 of 102
AVISO
Este Manual de Servicio sólo existe en inglés.
Si algún proveedor de servicios ajeno a GEMS solicita un idioma que no sea
el inglés, es responsabilidad del cliente ofrecer un servicio de traducción.
No se deberá dar servicio técnico al equipo, sin haber consultado y
comprendido este manual de servicio.
La no observancia del presente aviso puede dar lugar a que el proveedor de
servicios, el operador o el paciente sufran lesiones provocadas por causas
eléctricas, mecánicas o de otra naturaleza.
LANGUAGE
ATENÇÃO
Este Manual de Assistência Técnica só se encontra disponível em Inglês.
Se qualquer outro serviço de assistência técnica, quE não a GEMS, solicitar
estes manuais noutro idioma, é da responsabilidade do cliente fornecer os
serviços de tradução.
Não tente reparar o equipamento sem ter consultado e compreendido este
Manual de Assistência Técnica.
O não cumprimento deste aviso pode por em perigo a segurança do técnico,
operador ou paciente devido a‘ choques elétricos, mecânicos ou outros.
AVVERTENZA
Il presente manuale di manutenzione è disponibile soltanto in inglese.
Se un addetto alla manutenzione esterno alla GEMS richiede il manuale in
una lingua diversa, il cliente è tenuto a provvedere direttamente alla traduzione.
Si proceda alla manutenzione dell’apparecchiatura solo dopo aver consultato
il presente manuale ed averne compreso il contenuto.
Non tenere conto della presente avvertenza potrebbe far compiere
operazioni da cui derivino lesioni all’addetto alla manutenzione, all’utilizzatore ed
al paziente per folgorazione elettrica, per urti meccanici od altri rischi.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
4 of 102
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
5 of 102
DAMAGE IN TRANSPORTATION
All packages should be closely examined at time of delivery. If damage is apparent write “Damage In Shipment” on ALL
copies of the freight or express bill BEFORE delivery is accepted or “signed for” by a GE representative or hospital
receiving agent. Whether noted or concealed, damage MUST be reported to the carrier immediately upon discovery, or in
any event, within 14 days after receipt, and the contents and containers held for inspection by the carrier. A transportation
company will not pay a claim for damage if an inspection is not requested within this 14 day period.
Call Traffic and Transportation, Milwaukee, WI (414) 785 5052 or 8*323 5052 immediately after damage is found. At this
time be ready to supply name of carrier, delivery date, consignee name, freight or express bill number, item damaged and
extent of damage. Complete instructions regarding claim procedure are found in Section S of the Policy And Procedures
Bulletins. 14 July 1993
OMISSIONS & ERRORS
Customers, please contact your GE Sales or Service represenatives. GE personnel, please use the GEMS iTRAK
Process to report all omissions, errors, and defects in this publication.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
6 of 102
REVISION HISTORY
REVISON HISTORY
Revision
Date
Reason for change
A
July 13, 2005
Preliminary release for ME
B
Sept 21, 2005
Update of prelim for REVIEW
C
October 14, 2005
HII Review Editions
1
October 18, 2005
Program M3, pilot production release
2
February 14, 2006
Program M4 updates & general release
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
7 of 102
TABLE OF CONTENTS
Legal Notes .................................................................................................................................................. 2
Trademarks .................................................................................................................................................. 2
Omissions & Errors .................................................................................................................................... 2
Copyrights ................................................................................................................................................... 2
Country of Manufacture.............................................................................................................................. 2
Important Precautions ................................................................................................................................ 3
Language ..................................................................................................................................................... 3
Language ..................................................................................................................................................... 4
Revision History.......................................................................................................................................... 7
Table of Contents........................................................................................................................................ 8
1.0
Introduction .................................................................................................................................... 12
! IMPORTANT NOTE ABOUT THE USE OF THIS DOCUMENT !..................................................... 12
1.1
AWRA AW Advanced Application ‘Clinical’ Summary............................................................... 13
1.1.1
Product Requirements:.......................................................................................................... 13
1.1.2
2.0
2.1
2.2
2.3
CTQs /CTSs: ......................................................................................................................... 13
Figure 1 AWRA Overview ................................................................................................................ 14
INSTALLATION Overview .............................................................................................................. 15
AW SERVER Advanced Applications Software Installation Overiew ....................................... 15
Advanced Applications Software Installation Preparation ........................................................ 16
Advanced Applications AW Software ‘GENERIC’ Installation REFERENCES......................... 17
AW4.2, and forward ............................................................................................................................. 17
AW Documentation Links..................................................................................................................... 17
AWRA INSTALLATION................................................................................................................... 18
AWRA System Components and Architecture ........................................................................... 18
Figure 2 AWRA Architecture ............................................................................................................ 18
3.2
AWRA Requirements & CONFIGURATIONS................................................................................ 19
3.2.1
The SERVER requirements for AWRA ................................................................................. 19
3.0
3.1
3.2.2
Uninterruptible Power Supply (UPS) ..................................................................................... 19
3.2.3
Network ................................................................................................................................. 19
3.2.4
The CLIENT requirements for AWRA ................................................................................... 19
3.2.5
CLIENT Software Requirements and Configurations............................................................ 20
3.2.6
Site ‘IT’ and SECURITY Requirements................................................................................. 21
3.2.6.1 Network Security..................................................................................................................... 21
3.2.6.2 Login ....................................................................................................................................... 22
3.2.6.3 Port Usage .............................................................................................................................. 22
3.2.6.4 Summary................................................................................................................................. 22
3.3
SERVICE STEERING – INSTALL & T.S. FLOW ............................................................................ 23
3.4
AW Additional ‘AWRA’ Memory Installation................................................................................ 24
Table 1 – AWRA Memory Information ................................................................................................. 25
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
8 of 102
3.5
3.6
AWRA installation sequence ........................................................................................................ 25
AWRA SERVER installation / un-installation .............................................................................. 26
COMMAND-LINE INSTALL / UN-INSTALL OPTIONS........................................................................ 26
AWRA UN-INSTALLATION ................................................................................................................. 26
AWRA File-System Summary.............................................................................................................. 27
3.7
AWRA stand-alone ‘REMOTE REVIEW’ server tests.................................................................. 28
Stand-Alone SERVER test 1................................................................................................................ 29
Stand-Alone SERVER test 2................................................................................................................ 31
SERVER-to-SERVER test 3 ................................................................................................................ 32
Figure 3
3.8
3.9
AWRA LOGIN SCREEN.................................................................................................... 33
SUGGESTIONS................................................................................................................................... 34
AWRA CLIENT installation ............................................................................................................ 34
AWRA CLIENT tests....................................................................................................................... 35
“VIRTUAL AW” MODE......................................................................................................................... 39
MIP/MPR (REMOTE REVIEW)” MODE .............................................................................................. 41
4.0
Easy Install & AWRA ERRORS ..................................................................................................... 42
“OFFICIAL” AWRA logs Specified by AWRA program requirements.................................................. 42
Additional AWRA errorlog information ................................................................................................. 43
5.0
Installation Finish Tasks & Information ....................................................................................... 44
6.0
FRU’s ............................................................................................................................................... 45
7.0
Trouble-Shooting ........................................................................................................................... 46
Appendix 1 - SERVER MIP / MPR Test.................................................................................................... 47
Opening RemoteBrowserLauncher.jnlp............................................................................................... 47
Figure 4
AWRA Browser .................................................................................................................. 48
Figure 5
MIP/MPR (REMOTE REVIEW) 3D Viewer........................................................................ 49
Figure 5A
application/x-java-jnlp-file ERROR................................................................................. 49
Configure or Create application/x-java-jnlp-file.................................................................................... 50
Appendix 2 - CLIENT Browser Configurations: (JRE, COOKIE & PROXY SERVER) ......................... 51
Figure 6 “IE” Settings: JRE – Java Runtime Environment
& GE SameTime NOTE ............... 51
Figure 7
IE COOKIES Settings ........................................................................................................ 52
Figure 7A
AWRA COOKIES disabled notification .......................................................................... 53
Figure 7B
Un-Supported Browser notification ................................................................................ 53
Figure 8
“IE” PROXY SERVER Settings.......................................................................................... 54
Figure 9
Netscape Settings: JRE – Java Runtime Environment ..................................................... 55
Figure 10
Netscape COOKIES Settings......................................................................................... 56
Figure 11
Netscape PROXY SERVER Settings ............................................................................ 57
Figure 12
MOZILLA/FIREFOX Settings: JRE – Java Runtime Environment................................. 58
Figure 13
MOZILLA/FIREFOX COOKIES Settings........................................................................ 59
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
9 of 102
Figure 14
MOZILLA/FIREFOX PROXY SERVER Settings............................................................ 60
Figure 31
MAC Safari Settings: JRE – Java Runtime Environment .............................................. 61
Figure 32
MAC PROXY SERVER Settings.................................................................................... 62
Appendix 3 - Network PORTS .................................................................................................................. 64
PORTS................................................................................................................................................. 64
AWRA NETWORK & SECURITY RELATED FAQ’s ........................................................................... 66
Appendix 4 - AWRA OVERALL NETWORK Performance ..................................................................... 67
CLIENT Network Settings: ................................................................................................................... 67
Appendix 5 - AWRA VIRTUAL AW Performance.................................................................................... 70
Figure 15
Performance VNC Settings ........................................................................................... 70
Appendix 6 – MIP/MPR (REMOTE REVIEW) Remote 3D Viewer SERVER Errors............................... 71
Figure 16
Connection to server failed ........................................................................................... 71
Figure 16A
Unable to launch Remote MIP/MPR............................................................................. 72
Figure 16B Unable to launch MIP/MPR - DETAILS ....................................................................... 72
Appendix 7 - REMOTE ACCESS MANAGER ......................................................................................... 73
Figure 17
Remote Access Manager Window ................................................................................ 73
Appendix 8 - CLIENT Browser Security & AlertS Examples................................................................. 74
Figure 18
“IE” Security Alerts ........................................................................................................ 75
Figure 19
NETSCAPE Security Alerts........................................................................................... 76
Figure 20
MOZILLA / FIREFOX Security Alerts ............................................................................ 77
Figure 30
MAC Safari Security Alerts............................................................................................ 78
Appendix 9 – Virtual AW UnAvailable..................................................................................................... 79
Virtual AW is currently already in use .................................................................................................. 79
Virtual AW access has been suspended ............................................................................................. 79
The Local AW Console User Has Denied You Access to Virtual AW ................................................. 79
TVA; Tip Virtual Assist is running – cannot connect to Virtual AW...................................................... 79
Unable to launch Virtual AW … ........................................................................................................... 80
Unable to launch Virtual AW … Details ............................................................................................... 80
Appendix 10 – SERVICE & ADMIN TOOL ............................................................................................... 81
Service and Administration Page for AW RemoteAccess ................................................................... 82
Configuration........................................................................................................................................ 84
Virtual AW Connection To SERVER lost – Inactivity Timeout............................................................. 85
Service and Administration Page – View training ................................................................................ 86
Appendix 11 – Max # Of USERS Error .................................................................................................... 87
“BOGUS” Maximum number of Users already connected................................................................... 87
Appendix 12 – PING .................................................................................................................................. 88
PING .................................................................................................................................................... 88
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
10 of 102
Trace Route ......................................................................................................................................... 88
tracert examples .................................................................................................................................. 89
Appendix 13 – WEB START & JNLP ....................................................................................................... 90
Figure 21: To Run this Application … .................................................................................................. 90
Figure 22: Windows cannot open this file ............................................................................................ 91
Figure 23: Would you like to open the file or save it? .......................................................................... 91
Figure 24: Do you want to open or save this file? ............................................................................... 92
Figure 25: Do you want to save this file?............................................................................................. 92
Figure 26: Browser with characters …................................................................................................. 93
Appendix 14 – Connection Issues........................................................................................................... 94
Figure 27: Network Performance Sense / Your network speed .......................................................... 94
Figure 28: Potential PROXY SERVER Problem / Access Denied....................................................... 94
Figure 28A: Operation Timed Out … ................................................................................................... 94
Figure 29: HTTP Status 404 - Generic Connection Error.................................................................... 95
Figure 29A: Communication Problem.................................................................................................. 95
Appendix 15 – The ‘LINUX’ CLIENT ........................................................................................................ 96
Figure 21A: To Run this Application .................................................................................................... 96
Installing Java on Linux ........................................................................................................................... 97
Choose the javaws location to run … ..................................................................................................... 99
Figure 21B Linux Java Configuration .............................................................................................. 99
Appendix 16 – The AWRA Installation ROOT password POP-UP......................................................100
AWRA Installation root password pop-up / PNF Firewall configuration ............................................ 100
Appendix 17 - Interesting ‘NICE-TO-KNOW’ Stuff ...............................................................................101
“Skelleton” login Screen..................................................................................................................... 101
Virtual AW connection timeout on VPN ............................................................................................. 102
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
11 of 102
1.0 INTRODUCTION
The AWRA application is designed to run on the AW4.2 / XW8000 and forward AW platforms. This
guide makes references to all the appropriate standard Advantage Workstation service manuals for more
detailed information about installing an advanced application software option (like AWRA) on the AW. The
current revision of the appropriate AW Service Manual should be used when installing this software.
This IM/SM document is setup around the fundamental service design for AW RemoteAccess, a divide
and conquer plan. The THREE basic components in the AWRA “system” – are all addressed with some
level of stand-alone testing for each, as well as system testing.
1.
2.
3.
The AWRA SERVER
The NETWORK
The CLIENTS
•
The AWRA SERVER component has the most stand-alone tests associated with it.
This includes a Service Administration Page with an automated test using a canned
dataset. The AWRA SERVER is the foundation for the AWRA system, and is the
direct responsibility of GEHC.
•
The NETWORK is covered with basic connectivity testing - mostly in the CLIENT
section - and links to informational possibilities if various issues arise. The
NETWORK is not the direct responsibility of GEHC.
•
The CLIENT tests are essentially the AWRA “SYSTEM” tests. Here there are
configuration suggestions, and informational links on possible issues that could arise
- as well as normal configuration setup suggestions. The CLIENT(S) are not the
direct responsibility of GEHC.
This is the first real network application developed for AW. It is probably not possible to cover ALL the
potential issues that can arise with this type of application, given the nature of networking and the
variability’s inherent in client operating systems and configurations. However, it is hoped that this
document will at least be a good launching point for AWRA installation, and support in the field.
A Service Training ‘Overview’ is available in the AWRA application in the
“Service & Administration Page”
! IMPORTANT NOTE ABOUT THE USE OF THIS DOCUMENT !
This manual details MANY different security, configuration, alert, and information message pop-ups.
You might encounter some, none, or all of these as you configure, test, and use AWRA. The
qualifying words “IF”, “MIGHT” and “MAY” are used on purpose throughout this manual. Because of all
the potential variations in client configurations, browser revisions and settings, cached data, cookies, and
network infrastructures – it is not possible to account for every potential scenario. Hopefully, what you will
encounter is covered in some way somewhere in this document. So, do not get too upset if your results
vary from time-to-time, and from configuration-to-configuration.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
12 of 102
1.1
AWRA AW ADVANCED APPLICATION ‘CLINICAL’ SUMMARY
This program provides MIP-MPR (Web based quick 2D/3D image review) and Virtual AW mode (remote desktop access)
on review workstations and clients using ThinClient technology – Figure 1.
1.1.1 PRODUCT REQUIREMENTS:
• Remote access to all AW functionality through a PC Internet browser – “Virtual AW Mode”
• Remote access to basic MIP/MPR (REMOTE REVIEW) review through a PC Internet browser
• Simplified and more flexible workflow
• Product is targeted towards small to mid size hospitals needing remote 3D review capabilities
1.1.2 CTQS /CTSS:
• Radiologist or Referring Physician will be able to easily learn and use with virtually no training
• Reasonable Performance over the web for remote users with T1 - or like - bandwidth connections
• Minimal impact on AW when remote users access it (<20% slow down)
• Release quickly – to address competitive issues
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
13 of 102
FIGURE 1
AWRA OVERVIEW
Laptop or PC in
Radiologist’s Office
Running Virtual AW
Mode
Laptop or PC
in
Radiologist’s
Home
AW / SERVER
Running
MIP/MPR
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
14 of 102
2.0 INSTALLATION OVERVIEW
2.1
AW SERVER ADVANCED APPLICATIONS SOFTWARE
INSTALLATION OVERIEW
The AWRA “system” consists of the AW SERVER, and whatever Linux or PC CLIENTS that are
connecting to it. The advanced application software loads only on the SERVER – which is an
AW4.2 or forward at this time.
Installing AW advanced applications software - such as AWRA - involves the following activities:
1. Identifying the Global Order Number (GON) for the purchased software option, and
identifying the licenseId of the AW that the option is to be installed on if it is to be enabled
at this time.
a) The option - as well as all purchased AW options - should come with paperwork that will
include one or more 8 to 10 digit license key number(s). These license key numbers
are calculated from the AW system’s licenseId and can only be created if the
following 2 data points exist:
• The Global Order Number for the purchased option.
•
The licenseId of the target Advantage Workstation.
b) The software package may include a portable media (i.e. floppy) with the license key
information on it if the license(s) have already been created. This media might also be
blank - if the license(s) were not able to be created in manufacturing.
Additionally, the license key information will be available online at the eLicense website
link by searching under the Global Order Number or the workstation’s licenseId:
http://egems.gehealthcare.com/elicense/index.jsp
•
At least one of these elements is necessary to enable the software:
i. The paperwork license key information.
ii. The portable media (i.e.floppy) with the license key information.
iii. Website - eLicense license key information.
iv. Website – eLicense order information.
c) If the application’s license key number is in paperwork form, it can be typed in during the
application software installation using the “easy install” installation process that is
outlined within the Advantage Workstation Service Manual.
d) If there is a portable media (floppy) license key that came with the package, it can be
used during the Easy Install software installation to enable the application software. The
media (floppy) should be inserted first - then launch Easy Install – then click on INSTALL
in the Easy Install Graphical User Interface (GUI). The license key pop-up window
should appear with the key string filled in – then click OK.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
15 of 102
•
Note: the media (floppy) can be examined on a PC - or via the AW’s unix/linux
mount floppy commands - and the license key number(s) can be visually read
from the config.txt file (if it is there), and written down for input during the
installation if necessary, and for future system backup.
e) If the license data is found on eLicense, it can be written down and typed in as in bullet
(d) or saved to floppy for use as in bullet (e).
f) If the license data is not found on eLicense, but the order number is – with the option to
select the package for keying – the correct system can be added, and the key can be
generated on the eLicense website with local FE access to the web, or by the OLC.
2. Loading, and Enabling the CDROM application software package.
3. Loading (only) the CDROM application software package to the hard disk for future use. The
load should commence if INSTALL is clicked, the license key pop-up field is not selected
(left as is), no license floppy is installed, and OK is clicked.
2.2
ADVANCED APPLICATIONS SOFTWARE INSTALLATION
PREPARATION
IMPORTANT BEST PRACTICE:
- Informational •
AW up through AW4.0 uses a CONFIGURATION FLOPPY (Informational only).
•
AW4.1, 4.2 and forward use a CDROM CONFIGURATION media, instead of a
floppy.
Create an AW ‘CONFIG’ cdrom NOW and AFTER the application
software installation for use as needed throughout this and other
AW service activities.
Additionally, if there is a config floppy or cdrom onsite - with the package, or freshly
made - the configuration information can be read on a PC or in a command window on
the AW if need be:
To view configuration information on Windows PC –
Simply use a windows based text reader like WORPAD, INTERNET EXPLORER, or
MSWORD – and open the floppy/cdrom config.txt file. (MS NOTEPAD might NOT
work)
To view configuration information on Advantage Windows system –
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
16 of 102
Open a command window, and at the prompt perform the following:
su –
Password ‘operator’
• For a FLOPPY license media – AW4.2:
o mount /mnt/floppy
o cd /mnt/floppy
o more config.txt
o cd /
o umount /mnt/floppy
• For a CDROM configuration media – AW4.2:
o mount /mnt/cdrom
o cd /mnt/cdrom
o cd (“backup directory name”)
o more config.txt
o cd /
o umount /mnt/cdrom
2.3
ADVANCED APPLICATIONS AW SOFTWARE ‘GENERIC’
INSTALLATION REFERENCES
The ‘STANDARD’ AW “Install Package – Easy Install” Advanced Application
Installation Process applies. For ongoing process revision viability, the details
will not be printed here. But, they can be found in the AW Service Manual as
follows:
AW4.2, AND FORWARD
o
Advantage Workstation 4.2 SM (Service Manual)
o
Job Card entitled – Software Options Installation
o
EASY-INSTALL details
AW DOCUMENTATION LINKS
The current revisions for all these Manuals can be viewed ONLINE – following the
‘Documentation’ links at:
HTTP://AW-IB.EURO.MED.GE.COM/
OR
The AW Support Central Community at:
HTTP://SUPPORTCENTRAL.GE.COM/PRODUCTS/SUP_PRODUCTS.ASP?PROD_ID=16107
OR
HTTP://GEIN.EURO.MED.GE.COM/IDM/DOC.HTML
DISCLAIMER: ALL the external links in this document are good places to start looking for
documentation or resources. However, due to organizational, server and website maintenance online links are occasionally moved, removed, and / or modified. The specific document, and / or
link MIGHT change over time. This particular document will not be automatically updated to any
online changes that occur. As is true with ALL online resources – it is up to the user to stay
current with the available online resource, its location, and its use.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
17 of 102
3.0 AWRA INSTALLATION
3.1
AWRA SYSTEM COMPONENTS AND ARCHITECTURE
The AWRA system consists of THREE main components:
3.1.1 The AW SERVER, which contains the images and all data associated with them.
o AW Web Server
o VisServer – Visualization Server – Render Engine
o AW Application – The AWRA Advanced Application software.
o VisPanel – Viewport
o VNC - Virtual Network Computing. This is a protocol that allows remote access
and control a computer over a local network or the Internet.
3.1.2 The NETWORK, which contains the connectivity infrastructure between the SERVER
and the CLIENT
3.1.3 The CLIENT, which communicates with the SERVER.
o Web Browser – I.E, Netscape, Mozilla, and Safari … Firefox is NOT officially
supported, but MIGHT work.
o JavaWebStart – Java Web Start provides a platform-independent, secure, and
robust deployment technology. It enables developers to deploy full-featured
applications to end-users by making the applications available on a standard
Web server. By using any Web browser, end-users can launch the applications
and be confident they always have the most-recent version.
FIGURE 2
AWRA ARCHITECTURE
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
18 of 102
3.2
AWRA REQUIREMENTS & CONFIGURATIONS
3.2.1
THE SERVER REQUIREMENTS FOR AWRA
Advantage Workstation (AW)
software:
Version 4.2 or later
AW hardware:
HP XW8000 or better
AW memory:
4GB minimum
3.2.2
o
For a clinical environment, a UPS is strongly recommended to ensure continuity of
availability of the server in the event of a brief power failure and to provide graceful
shutdown if a power failure persists.
3.2.3
o
o
o
o
o
UNINTERRUPTIBLE POWER SUPPLY (UPS)
NETWORK
Use a 100 Mbps (or faster) network to link the server and clients.
AW SERVER should be on a local network within the site that it is acquiring
data sets from. Internet access should be through the site’s VPN or like
protocol. This product is not designed for direct INTERNET exposure.
Actual available download (server-to-client) bandwidth for each client: 1.5Mbps
minimum, (performance heavily dependent on bandwidth).
o 20Mbps or more recommended for intranet/LAN operation.
Upload (client-to-server) bandwidth should be at least 20% of download bandwidth.
Actual round-trip server-client latency: 50 milliseconds maximum (performance
heavily dependent on latency)
3.2.4
THE CLIENT REQUIREMENTS FOR AWRA
Operating system:
Windows XP, Windows 2000, Linux, and Mac – OS X (10.4 or higher)
Processor:
1.5GHz Pentium 4 minimum (or equivalent)
Memory:
256MB minimum (512MB for MAC)
Disk drive:
50MB free space available
Screen resolution:
1024H x 768V min (1280H x 1024V recommended) w/full color (32 bit)
Network card:
10 Mbps minimum (100 Mbps recommended)
Browser:
Internet Explorer 6 or later, Netscape 7.2 or later, Mozilla 1.7.5 or later,
Safari 2.0.2 or later – (Firefox is NOT officially supported, but might work)
Browser security:
Javascript enabled, Java Virtual Machine enabled & download enabled
Java:
Java Runtime Environ 1.4.2 or above with Java Webstart (downloadable
from Sun)
Internet
connection:
Customer-provided VPN, or equivalent, for internet/WAN operation
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
19 of 102
3.2.5
CLIENT SOFTWARE REQUIREMENTS AND
CONFIGURATIONS
Web Browers
o Internet Explorer, version 6.0 or later
o Netscape, version 7.2 or later
o Mozilla, version 1.7.5 or later
o Safari (MAC) version 2.0.2 or later
If you run an older version of any of these browsers, or a different browser,
you will get a warning about an invalid browser or invalid browser version.
You can continue, if you choose, but the login screen and patient browser may
not work correctly. If you run on a Safari version prior to 2.0.2 – ROI values will
be inaccurate.
JRE
(see APPENDIX 2)
Java Runtime Environment (JRE) version 1.4.2 or later and Webstart are required to
run this application.
Java Runtime Environment - The JRE consists of the Java virtual machine, the Java
platform core classes, and supporting files. It is the runtime part of the Java
Development Kit -- no compiler, no debugger, no tools. The JRE is the smallest set
of executables and files that constitute the standard Java platform.
If you do not have it installed, the web page will prompt you to install it. If you do not
install it, the application will ultimately not run.
Note: You need administrator privileges on our PC to install JRE. If you do not have
that, please have your IT person install this for you.
After installation, the browser must be configured to use JRE. This may happen
automatically, but if the application still does not work after downloading JRE, see
Appendices 2 & 13 for details of what to check.
Webstart
Webstart is installed as part of JRE, and is required for AWRA. If your client has the
Linux operating system, it is likely you will always see a message saying Webstart is
not installed, even when it is. If that occurs, try starting the application, and if it starts
you will know Webstart is installed correctly. Ignore the message in this case.
Screen Resolution
Your screen resolution should be at least 1024 x 768 to run this application.
To see the entire screen for the Virtual AW application, a screen resolution of
1280x1024 is recommended.
Download Manager
Both the MIP/MPR (REMOTE REVIEW) and Virtual AW applications download Java
applications to run. If you have a download manager running, it may interfere with
this download and execution. You may need to disable it while running this
application.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
20 of 102
Spyware/Anti-Virus Programs
(see APPENDIX 2 & APPENDIX 8)
There are many different spyware and Anti-Virus programs in use. Most will work fine
with this software. However, if you are having trouble running this software, you may
want to temporarily disable those programs, or set this site up as a trusted site.
(see APPENDIX 2 & APPENDIX 8)
Cookies
Cookies must be enabled for this application to run correctly.
Download Manager
Both the MIP/MPR (REMOTE REVIEW) and Virtual AW applications download Java
applications to run. If you have a download manager running, it may interfere with
this download and execution. You may need to disable it while running this
application.
Proxy Servers
(see APPENDIX 2 & APPENDIX 14)
You MIGHT need to disable or reconfigure your proxy server, as it may block AWRA.
Security
When you download Virtual AW or the MIP/MPR (REMOTE REVIEW) tool, you will
be downloading a Java application that will reside and run on your PC. Normally,
downloading Java applications from sites on the Internet is not a good idea, since
they have the ability to read and write data to your PC. Therefore, when you do the
download, you will probably see some type of message warning you that this is a
dangerous thing to do - with the assumption that the Internet is involved - and
advising you not to run this application.
There is no way to run “RemoteAccess” without installing these Java applications.
Since this application is an INTRANET intended tool, installing them will not
make your PC vulnerable to viruses or other problems.
Talk to your IT department if you have any questions or issues.
3.2.6 SITE ‘IT’ AND SECURITY REQUIREMENTS
The AW RemoteAccess software is intended to provide remote viewing of DICOM
images over a local private network with the network’s inherent security in place.
More specifically, the "network's inherent security" means that the only web
access to the network should be through an enterprise-grade VPN or similar
firewall, configured to block all unused ports and unused services. With any
transfer of sensitive patient data, it is important to maintain security, only allowing
access to those with appropriate authorization.
3.2.6.1 NETWORK SECURITY
AWRA uses the security already in place in the site’s network enterprise. Access to
the AW should only be given to someone already on the local network. It is
recommended that home users connect to the AW, and AWRA only after connecting
through the site’s VPN (Virtual Private Network) or similar enterprise-grade firewall,
configured to block all unused ports and unused services.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
21 of 102
3.2.6.2 LOGIN
AWRA taps into the login of the AW. It uses the same user names and
passwords. It plugs into the PAM (Pluggable Authentication Module) used by
the Linux OS. Because it already uses PAM it is ready to be integrated into the
EA3 (Enterprise Authenication, Authorization, and Audit) capabilities, giving
HIPAA compliance with regard to knowing who is logged in, what apps and data
they are accessing.
3.2.6.3 PORT USAGE
AWRA uses three servers, each with its own port.
The first is a Web Server that allows browsing of the AW database remotely.
The login uses Https protocol which provides SSL (Secure Socket Layer)
encryption (port 8443), the standard for secure web page transmission. Once
logged in the user has access to the rest of the system over port 8081. Any
attempt to access other URL’s directly will be caught and redirected back to the
login page.
The second is a VNC (Virtual Network Computing) port 5900. This allows a
remote user full access to the Virtual AW. We run a customized VNC server
that only allows one connection at a time, and only after logging in. The
server is started on demand, there is no hanging open port for someone to
snoop into. When the client is done, the port is closed and the server
exits.
The third port is a proprietary port used for the MIP/MPR (REMOTE
REVIEW) application, port 6778. Technically, this is a set of ports (6778,
6779, 6780), depending on the number of users connected, up to three at a
time, each user with their own connection. These ports are used to transfer
commands to the render engine and receive back the rendered images. No
identifying data is sent over this port. All annotation is done on the client
side. The DICOM headers used are passed to the client over Https,
described above.
NOTE: There are only THREE possible MIP/MPR (REMOTE REVIEW)
users allowed at any given time. However, if there are 3 users – one
disconnects, and the port is hung for a few seconds and has not reset
while another request come in – the next port will be used – i.e. 6781,
82, etc …
3.2.6.4 SUMMARY
Any probes of the AW after AWRA is installed will find a single new port open,
the https. The VNC and Render Engine are started on demand, with only the
client who requests the service, after having logged in, able to connect. Any
sensitive data is sent through secure encryption standards.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
22 of 102
3.3
SERVICE STEERING – INSTALL & T.S. FLOW
START
3.4 AWRA SERVER
Additional MEMORY
Installation
FAIL
PASS
AW SM
&
Sec 3.4
3.9 AWRA CLIENT Test
APPX 2 - 9
3.6 AWRA SERVER
Installation
FAIL
PASS
FAIL
APPX 13
&
APPX 14
&
APPX 15
Sec
2,3,4
3.7 AWRA Stand-Alone
SERVER Test
PASS
FAIL
Sec 3.7 Suggestions
&
Sec 3.8 & 3.9
5.0 Installation FINISH
Tasks
SEC 3.7
&
APPX 1
APPX 10
3.8 AWRA CLIENT
Installation
DONE
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
23 of 102
3.4
AW ADDITIONAL ‘AWRA’ MEMORY INSTALLATION
3.4.1 To maximize AWRA performance, the option will come with 2G of additional AW
platform specified memory. In Chapter 8 of the AW Service Manual(s) – the
various platform optional memory installations are detailed. Please follow the
procedure for your particular hardware platform.
Currently AWRA can be installed on AW4.2 & Forward – on XW8000 & XW8200
3.4.2 The AW service manuals indicate that the optional memory upgrade for both
xw8000 and xw8200 is 2 ONE GIG memory sticks, equal to 2G of additional
memory – making the total = 4G. If the system in question already has this extra
2G of memory installed (total of 4G) the extra 2G of AWRA optional memory will
bring the system up to a total of 6G of memory – unless it is an xw8000.
•
Because the xw8000 has a total of 6 memory slots available, and its standard
memory configuration is 2G (4 x 500M) – this will mean that 2 of the 4 x 500M
sticks will need to be pulled out of the middle two slots and replaced with the
2 x 1G sticks sent with the AWRA package. This actually will result in a
total of 5G for the xw8000 – instead of 6G. (If another 2 x 1G memory sticks
are available, the remaining 2 x 500M memory sticks can also be replaced –
which would then result in a total of 6G of memory for the xw8000). See more
information in Table 1 below.
3.4.3 Because the OS used on the AW4.2 is different from the OS used on the AW4.2P
(& forward) in that the AW4.2 OS uses a differentiated MEM Kernel. This means
that the OS sizes the memory in the system, and does not install the BIG
MEMORY KERNEL unless it sees more than 2G of memory present when
the OS is loaded. So, if you install extra memory without doing a load-from-cold,
the system will only use roughly 88% of the expected total memory. If a loadfrom-cold is performed after the extra memory is installed, the percentage goes
up to 94% - a 6% delta. Once the BIG MEMORY KERNEL is installed after doing
a LFC with 4G present, going from 4G to 6G has no more apparent impact on this
issue since the big kernel is already installed.
•
Admittedly, the 6% delta is not a huge difference, and it probably can be
tolerated fairly well if the system is not heavily used. However, along with the
memory kernel issue, there are also “swap partition” configurations that
are done during the LFC which are also dependent on the amount of
memory present at the time of the load.
3.4.4 The AW4.2P & forward OS uses a UNIFIED MEMORY KERNEL, and will not
need a LFC to use the full additional memory. However, again – the swap
partition issue can still be a potential factor.
3.4.5 BOTTOMLINE: Whenever installing additional memory on any of the AW
platforms, a load-from-cold is a good BEST PRACTICE – especially on the
AW4.2 xw8000 platform. If an INFORMED DECISION is made not to do the LFC
or to delay it to a more opportune time for the customer, it should be remembered
that there MIGHT be various system performance hits that arise depending on
how heavily the system is used. DO NOT GET TOO CARRIED AWAY WITH
ANY SYSTEM TROUBLE-SHOOTING until the “new memory / load-from-cold” is
accomplished first. The following table summarizes the various memory factors:
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
24 of 102
TABLE 1 – AWRA MEMORY INFORMATION
AW4.2 on xw8000
Differentiated MEM Kernel
AW4.2P & 4.3 on xw8000
AW4.2P & 4.3 on xw8200
X
Unified MEM Kernel
X
X
2G / 4x500M
2G / 4x500M
2G / 2x1G
6 / 3x2
6 / 3x2
8 / 4x2
Every 2 slots / right-to-left
Every 2 slots / right-to-left
Every 2 slots / right-to-left
Normal MEM upgrade
4G / (4x500M + 2x1G)
4G / (4x500M + 2x1G)
4G / (2x1G + 2x1G)
AWRA MEM upgrade
2G / 2x1G
2G / 2x1G
2G / 2x1G
Normal amount of MEM
MEM slots available
MEM installation
Normal + AWRA MEM upgrade 1
5G / (2x500 + 2x1G + 2x1G) 5G / (2x500 + 2x1G + 2x1G) 6G / (2x1G + 2x1G + 2x1G)
Normal + AWRA MEM upgrade 2
6G / (2x1G + 2x1G + 2x1G)
6G / (2x1G + 2x1G + 2x1G)
-
LFC required - MEM kernel
YES
No
No
LFC suggested - swap space
YES
YES
YES
3.5
AWRA INSTALLATION SEQUENCE
3.7.1
The AW SERVER software gets installed on the AW essentially just like any other AW
Advanced Application – See section 2 of this document for the Easy Install options to
install the application.
•
3.7.1
The “STAND-ALONE” tests in section 3.7 should be used to validate a
successful AWRA/SERVER installation.
The CLIENT is essentially a PC type environment and does not get any formal software
loaded on it for AWRA, other than the “java” components needed for AWRA
functionality. This happens (downloads) when the application is accessed and requested
from the SERVER.
•
The “CLIENT” tests in section 3.9 should be used to validate a successful
“CLIENT/System” installation
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
25 of 102
3.6
AWRA SERVER INSTALLATION / UN-INSTALLATION
The AW RemoteAccess SERVER software gets installed on the AW essentially just like
any other AW Advanced Application.
For remote functionality or for an alternative to the easy install tool, there are commandline installation and un-installation scripts available in /export/home/sdc/install.
NOTE: These install scripts will only exist IF remoteaccess has already been loaded on
the AW at some time, and IF uninstall.remoteacces –all has NOT been executed.
COMMAND-LINE INSTALL / UN-INSTALL OPTIONS
install.remoteaccess –h
Description of install.remoteaccess options
install.remoteaccess KEY
Install with NO POP-UP (for remote use)
• KEY = license number to enable software
o If no KEY, it will try to access it from the license floppy.
•
If no KEY or floppy KEY, it will fail as a bad license key.
installsu.remoteaccess – A script used by install.remoteaccess – do not use.
uninstall.remoteaccess –h
Description of uninstall.remoteacces options.
uninstall.remoteaccess
Un-install & retain files for later install – NO POP-UP.
uninstall.remoteaccess –all
Un-install ALL ‘RA’ FILES (will need cd to re-install).
• -all leaves only the following file on the system:
o /export/home/sdc/logfiles/uninstall.remoteaccess.log
uninstallsu.remoteaccess – A script used by uninstall.remoteaccess – do not use.
AWRA UN-INSTALLATION
The only way to disable AWRA is to UNINSTALL it.
o Uninstall OPTION 1:
Use the ADMIN – INSTALL PACKAGE – EASY INSTALL HARD DISK – UNISTALL
APPLICATION feature. This will remove the application from active availability, but
retain the AWRA installation files for re-installation from the Hard Disk Menu. Of
course, the application could also be re-installed from the AWRA CDROM at any time
also.
o Uninstall OPTION 2:
Command-line /export/home/sdc/install/uninstall.remoteaccess does essentially
the same thing as option 1, only it is a command line, and does not require the Easy
Install GUI. (See above command-line options)
o Uninstall OPTION 3:
If it is desired to TOTALLY remove the AWRA files from the AW :
/export/home/sdc/install/uninstall.remoteaccess –all
(See above command-line options)
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
26 of 102
AWRA FILE-SYSTEM SUMMARY
o /export/home1/sdc_image_pool/appli/RemoteAccess
AWRA system software files
o /export/home1/sdc_image_pool/appli/AWRAInstall
AWRA Installation files
o /export/home/sdc/logfiles/remoteaccess*
AWRA logfiles
o /export/home/sdc/install/description.remoteaccess
AW Easy Install Hard Disk AWRA list item
o /export/home/sdc/install/install.remoteaccess
o /export/home/sdc/install/uninstall.remoteaccess
AWRA command-line install and uninstall
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
27 of 102
3.7
AWRA STAND-ALONE ‘REMOTE REVIEW’ SERVER TESTS
Any ONE or ALL of the following 3 tests can be used to validate an AWRA Server
installation, or trouble-shoot it.
Definitions:
SERVER STAND-ALONE TESTS - the AWRA server testing itself.
1. Automated administrative diagnostic with a “canned” data set.
2. Client simulation using AWRA Server on itself.
SERVER-TO-SERVER TEST –
3. A standard AW or AWRA server connecting to another AWRA
server - to test.
Rationale:
The whole idea for a SERVER stand-alone type test is to be able to verify that
the server - by itself - is functional. This is useful because a failure of the AWRA
system can be related to any number of network and or client configuration
issues. If one can start splitting the “system” into stand-alone pieces, the
trouble-shooting process should be more effective.
3.7.1
Install the AWRA advanced application on the AW per the standard ADMIN – INSTALL
PACKAGE utility and process referred to in section 2 of this document.
3.7.1.1 During the installation, the AW ROOT password will be asked for – See
APPENDIX 16. The installation will FAIL after THREE wrong password
tries. Be careful – if it is not typed in correctly the following content will appear
in the Easy Install GUI scripting:
3.7.2
After a successful installation, SYSTEM - RESTART SOFTWARE.
The AW - Remote Access Server Software will ‘automatically’ be started.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
28 of 102
STAND-ALONE SERVER TEST 1
Automated administrative diagnostic with a “canned” data set
3.7.3
From Applications > More >
• Click on RemoteAccessTest & START Mozilla with the default – or one of the profiles.
Internet Browser will launch – If the browser stays BLANK, and/or does not
respond:
o
From Applications > More -> click on RemoteAccess
o
In the RemoteAccess Manager GUI –
Click on RESTART to restart the web-server (see APPENDIX 7) –
Dismiss the browser –
Re-try 3.7.3
Internet Browser will & should launch with an indication that “You will need to
login as “root” to access the admin page.” If so – skip to 3.7.4
However, if it displays a message with content to the effect:
“The connection was refused (or could not be connected) when attempting to
contact localhost:8081” –
o
Re-visit steps 3.7.1 & 2 again. It is possible that the AWRA installation was not
successful. Make sure there were no errors in the Easy Install GUI during the
install.
Also, be sure to type in the ROOT password correctly when prompted during the
install. The application installation will fail if the password was typed in wrong 3
times – this might have been mistaken for a successful installation?
o
Another reason why the localhost may not be available is if the AW /etc/host file
is not correct. The file should have at least the following content in it for the
localhost to be accessible:
more /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain locahost
If the RemoteAccessTest process still will not connect to the localhost and
display the Service Admin page – skip to the Client Simulation using
AWRA Server test where you will use the actual IP Address in the URL. This
should work. If it does not, there may be an actual problem on your AWRA AW
platform with the web-server software. Trouble-shooting this further might
involve AW service processes unrelated directly to AWRA, like loading software,
and or other hardware issues. Some potential actions that could be taken along with examining the errorlogs in section 4 - might be:
•
•
~sdc/install/install.http – observe feedback
RESTART the SERVER – (see APPENDIX 7)
o
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
29 of 102
3.7.4
3.7.5
If the RemoteAccessTest connects to the localhost, OK the security pop-ups, and the
browser MIGHT come up with the following message content. Click to proceed
with your current configuration –
There is no need to download the JRE components since these have already been
installed on the SERVER during the AWRA software load. Most LINUX platforms
cannot automatically detect Java – so this message gets posted. The option to
DOWNLOAD the JRE is primarily for the CLIENT – as this screen was also primarily
designed for the CLIENT (not for the SERVER testing on itself).
o If you click on the last option “Click here if webstart is already installed”
you will set a COOKIE that will prevent this page from coming up again on
the AW – as long as the COOKIE is set.
o However NOTE: IF Java is then somehow removed from the system, and
the COOKIE is still set – you will not get this alert, and you will not know
why the application does not work. FYI: COOKIE’s are managed in Mozilla
> Preferences > Privacy and Security.
• Another potential reason for this message screen is because of the
version of Mozilla. As you may have noticed, we spec version 1.7.5
or later. The AW4.2 platform comes with an earlier than AWRA
spec version. AW4.2P comes with an earlier than spec version also,
but it works. After you stop laughing, understand that AWRA also
installs a correct version of Mozilla during it’s installation in:
/export/home1/sdc_image_pool/appli/RemoteAccess/mozilla
RemotAccessTest automatically calls this newer mozilla version
installed with AWRA. So, there is a good chance that if you see the
alert message, it is not because of the Mozilla version – but, be
aware.
The LOGIN page will appear – login as root with operator as the password (if it has not
been changed to something else by the owner).
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
30 of 102
3.7.6
The password manager may come up – select NO for this test.
Then the Service and Administration Page for AW Remote Access should display.
There will be several options on this page. Click on Test MIP/MPR with MIP/MPR test
Data Set. This test will have 2 options (See APPENDIX 10 diagram flow)
3.7.6.1 Launch Chest – Sanity Test This will launch the Remote 3d Viewer and
allow manipulation of the test data set as a successful outcome of the test GO TO STEP 3.7.6.3 to complete …
3.7.6.2 Launch Torso – File Read Error Test This is a “FAILURE RECOVERY” test.
Will attempt to launch the Remote 3d Viewer, but will fail on a “File read error.”
The successful completion of this test is that the remote viewer exits, and the
user is cleanly cleared from the RemoteAccess Manager status – under
Connections (See APPENDIX 7) If the user is not cleared, there is a problem
with the MIP/MPR application not exiting correctly, and this could lead to a
bogus “maximum number of users already connected” error later on (See
APPENDIX 11)
3.7.6.3 After clicking on “Launch Chest” (or “Launch Torso”) go to APPENDIX 1, and
continue from STEP 3 to complete the test(s). NOTE: This test is a relatively
automated LOGIN version of the complete MIP/MPR test described in
APPENDIX 1.
STAND-ALONE SERVER TEST 2
Client simulation using AWRA Server on itself
•
•
3.7.7
Test only Remote Review (MIP/MPR)
Virtual AW will not work correctly on itself.
AW4.2P comes with a version of Mozilla that will work for this test. The native AW4.2
platform comes with an older version of Mozilla that may not work for this test. On all
AWRA installations, a version of Mozilla is loaded on the system that will work for
AWRA. It is loaded in a dedicated directory and does not interfere with the native AW
platform Mozilla load.
3.7.7.1 For AW4.2P and forward - Click on Mozilla in the Applications shortcut or pulldown list. The Mozilla internet browser should open up.
3.7.7.2 For AW4.2 – Open a command window, and launch Mozilla manually from
/export/home1/sdc_image_pool/appli/RemoteAccess/mozilla
3.7.8
Click on the AW ADMIN button, and then the Display Configuration button. In the
window that opens, note the internet address line roughly in the middle of the page. This
is the (AWRA) SERVER’S IPA (example 192.169.100.12). Write it down, and or cut and
paste it to the next step.
3.7.9
In the address window field of the Mozilla browser (just right of the Stop button) in place
of whatever is in there, type the following:
http://192.168.100.12:8081/RemoteAccess - 192.168.100.12 is an example only –
use your AW’s IPA - see figure 29 in APPENDIX 14.
IF security pop-ups present, click OK to dismiss them …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
31 of 102
IF the following message content comes up:
•
Click to proceed with your current configuration – There is no need to download
the JRE components since these have already been installed on the SERVER
during the AWRA software load. Most LINUX platforms cannot automatically detect
Java – so this message gets posted. The option to DOWNLOAD the JRE is
primarily for the CLIENT – as this screen was also primarily designed for the
CLIENT (not for the SERVER testing on itself).
o If you click on the last option “Click here if webstart is already installed”
you will set a COOKIE that will prevent this page from coming up again – as
long as the COOKIE is set.
o However NOTE: IF Java is then somehow removed from the system, and
the COOKIE is still set – you will not get this alert, and you will not know
why the application does not work. COOKIE’s are managed in Mozilla >
Preferences > Privacy and Security (example).
3.7.10 After one or more security warning pop-ups - If the SERVER is working correctly, you
will get The AW RemoteAccess Login Screen – see figure 3
Login with the standard aw login for your AW – i.e. (sdc) & (adw4.2), or PREFERABLY)
any valid user account on the AWRA SERVER.
3.7.11 Click on the MIP/MPR (REMOTE REVIEW) button and follow APPENDIX 1 to complete
this test.
3.7.12 If these tests complete successfully, proceed to SERVER-TO-SERVER TEST3.
3.7.13 If you still cannot get to the login screen, or if you get other error messages while trying
– stay on the SERVER and trouble-shoot the error. The CLIENT part of the AWRA
“system” will probably not work until this is corrected. Check the error logs referenced in
section 4, and use section 7 (AWRA AW SERVER - Troubleshooting).
SERVER-TO-SERVER TEST 3
A standard AW or AWRA server connecting to another AWRA SERVER TO TEST
This test is the same as the preceding TEST 2 except:
•
•
•
You use another AW to do the test (with a correct version of Mozilla)
You can TEST MIP/MPR (REMOTE REVIEW) AND/OR Virtual AW
Beginning to touch the NETWORK portion of the system - (See section 7)
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
32 of 102
FIGURE 3
Type Your LOGIN and
PASSWORD
Use the standard AW login
(sdc) and the password of
(adw4.2)
Or (PREFERABLY), any other
valid user account on the
AWRA SERVER
AWRA LOGIN SCREEN
“Choose AW”
If there are other AWRA AW(s)
on the network which are
successfully DICOM configured
on this host, and are running
AWRA software -there will be a
pull-down here to select another
AWRA SERVER. If so - This is
another good opportunity to
stand-alone-test SERVER-toSERVER and verify network /
server functionality all together
Launch Your Application
MIP/MPR: Quick 3D
application. Run this for ServerStand-Alone testing. (See
APPENDIX 1)
Virtual AW: Full remote AW
control. Cannot run this on
Server-Stand-Alone testing. Can
only run Virtual AW on AW-toAWRA SERVER or AWRA
Server-to-Server testing
(AWRA Server can’t run Virtual
AW emulation on itself).
CAN run MIP/MPR on all AW-toAWRA SERVER, SERVER-toSERVER & SERVER-STANDALONE testing.
Help: Link to the Operators
Manual
Version of AWRA currently
installed.
NOTE about available Choose AW (AWRA SERVERS):
You might not have access to all the AWRA servers that you had access to when you logged in.
As you navigate to other servers, the availability of the other servers will be dependent upon
what servers are DICOM configured on the server you are currently connected to - i.e. your list
may not be the same on every server as when or where you first logged in.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
33 of 102
3.7.14 This establishes that the AWRA SERVER by itself is functional. It does not establish the
CLIENT and or total network/system functionality. To do this, one needs to perform the next
section -- AWRA CLIENT INSTALLATION - & - TESTS.
SUGGESTIONS
1. If you are trouble-shooting a potential network issue, it might be advisable to do the
AWRA CLIENT TEST with a PC client or other AW client set-up on the AWRA
SERVER’S local subnet next – meaning a client with an address the same as the server,
except for the last segment – i.e. 192.168.100.13. If the client connects to the login
screen correctly on the same subnet, but will not on another subnet – i.e.
192.168.111.12 – this would indicate that there is a potential network, proxy or routing
issue that the local IT team needs to investigate. This is just a quick example – hopefully
you understand this type of trouble-shooting process. (Remember, these IPA numbers
are EXAMPLES ONLY)
2. If you are testing AWRA specific MIP/MPR (REMOTE REVIEW) manipulations or
performance, you can stay on the SERVER, login and test the MIP/MPR operation. Then
compare your results to your CLIENT results. Again, use the stand-alone testing to your
individual purpose as a divide and conquer or comparison tool.
3.8
o
NOTE: For SERVER STAND-ALONE testing the VIRTUAL AW mode will not
work very well. The SERVER cannot remote Virtual AW mode on itself. It can
only successfully use the SERVER MIP/MPR (REMOTE REVIEW) TEST
(Appendix 1) for stand-alone server tests on itself.
o
NOTE: For AW-to-SERVER or SERVER-to-SERVER testing, both VIRTUAL AW
and MIP/MPR (REMOTE REVIEW) will work. This is a good expansion on the
server stand-alone test if another AW or AWRA Server is available on the
network to use, because you start touching the NETWORK portion of the
system..
AWRA CLIENT INSTALLATION
Configuring the CLIENT environment
The CLIENT is essentially a PC WINDOWS, LINUX or MAC type environment, and does not get any
formal software loaded on it for AWRA - other than the “java” components needed for AWRA
functionality. This happens by downloading j2re1.4.2 or higher with Java Web Start from the AWRA
SERVER or the Internet, and installing it in its default location on the client.
See APPENDIX 2 & APPENDIX 13 for “example” graphics on how to check for this, and make sure it
is configured.
Most of the following CLIENT details are related to a WINDOWS environment. While the
described basic AWRA functionality is true for WINDOWS, LINUX, and MAC clients, the pop-ups and
screen references are primarily windows details – appendices 2 & 8 also show MAC examples. The
pop-ups and functionality for LINUX & MAC will be similar. However, the installation of the JRE on the
LINUX box – if it is not already installed – is significantly different from the WINDOWS & MAC boxes.
Information on how to setup JRE on a LINUX system – can be found in APPENDIX 15
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
34 of 102
3.8.1
If the client PC display is set to 16-bit color, only 32 levels of gray will be available for
displaying monochrome images, which will typically yield poor viewing results. Hence it is
highly recommended to set the display to 24-bit, or ‘true’ color even if you only need to view
monochrome images.
3.8.2
The client screen resolution should be at least 1024 x 768 to run AWRA. To see the entire
screen for the Virtual AW application, a screen resolution of 1280x1024 is recommended.
•
If the client screen resolution is set for 1024 x 768 it will need to use the scroll-bar on
Virtual AW to view BOTH screens on a dual screen AWRA SERVER.
•
If the client has a screen resolution of 1024 x 1280, Virtual AW will show a POP-UP type
window at the bottom of the screen with selectable radio buttons for the RIGHT and
LEFT SCREENS of a dual screen AWRA server.
3.8.3
Both the MIP/MPR (REMOTE REVIEW) and Virtual AW applications download Java
applications to run. If the client has a download manager running, it may interfere with this
download and execution. It MIGHT be necessary to disable the DM while running this
application.
3.8.4
There are many different spyware and Anti-Virus programs in use. Most will work fine with
AWRA. However, if you are having trouble running AWRA, you may want to temporarily
disable those programs, or set the AWRA up as a trusted site.
3.8.5
When the client downloads Virtual AW or the MIP/MPR (REMOTE REVIEW) tool for the first
time, it will be downloading a Java application that will reside and run on the client PC.
Normally, downloading Java applications from sites on the Web is not a good idea, since they
have the ability to read and write data to the client PC. Therefore, when the client downloads,
you will probably see some type of message warning you that this is a dangerous thing to do,
and advising you not to run this application. NOTE: There is no way to run either AWRA
application without downloading/installing these applications. Installing them will not make
your PC vulnerable to viruses or other problems. Talk to your IT department if you have any
questions or issues.
3.8.6
See Appendix 2, APPENDIX 13, and/or APPENDIX 15 (for LINUX) for recommended
CLIENT Browser and Java configurations to prepare for or reference while testing the
CLIENT.
3.9
AWRA CLIENT TESTS
THE VARIOUS CONFIGURATION AND SECURITY SETTINGS THAT CAN EXIST AT ANY
GIVEN TIME ON ANY OF THE VARIOUS SUPPORTED CLIENT BROWSERS CAN CAUSE
GREATER OR LESSER NETWORK SECURITY AS WELL AS IMPACT THE ABILITY OF AWRA
TO FUNCTION CORRECTLY. SOME, NONE OR ALL OF THE POP-UP ALERTS DESCRIBED IN
THE FOLLOWING SECTIONS CAN EXIST (AT ANY GIVEN TIME) DEPENDING ON THE
BROWSER AND ITS SETTINGS AT THE TIME IT IS BEING USED. MANY OF THESE
SETTINGS WILL CHANGE OVER TIME AS THE CLIENT IS USED FOR VARIOUS DIFFERING
APPLICATIONS. THIS MAY REQUIRE RE-VISITING THESE PROCEDURES MORE OR LESS
FREQUENTLY DEPENDING ON HOW THE CLIENT IS USED OVER TIME.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
35 of 102
3.9.1
Once the CLIENT has been configured, verify that its intranet and/or internet connection is
working correctly by successfully accessing other network resources on the intranet or
internet.
If this is verified - the AW AWRA / CLIENT “system” can be tested.
3.9.2
Find out the IPA (Internet Protocol Address) of the AWRA SERVER. Is it the same AW
SERVER you discovered in the Server Stand-Alone tests? This address is assigned by the
site or campus IT department, and will be consistent with a range of addresses that have
been allotted for their network configuration. It is important that you functionally validate the
address that you are given or think you know. One quick way to do this before attempting to
connect to the AWRA server is:
•
•
•
•
•
•
•
On the windows CLIENT click START
Click RUN
In the “run – open” box enter cmd > OK
o On a LINUX box – open a command window.
o On a MAC box – open a Terminal window.
A window will open
At the prompt – type in the ping command and the server IPA
Example: ping 192.168.100.12
IF the server is running, AND IF the network is complete, AND IF your network has not
blocked the PING utility (See APPENDIX 12) - you will see lines of data something like:
Reply from 192.168.100.12: bytes=32 time=2ms TTL=255
Note this is only the example IPA. Also, the time value maybe longer.
•
3.9.3
There will also be “Ping statistics” at the bottom of the printout. Note Packets SENT
versus LOST, and so on. The best result is 0 packets lost. But, be aware that the test
can pass with some lost statistics. This might mean an unstable or busy network, and
“might” be the first sign of performance issues later on.
• If the test fails, you will see something like:
“Request timed out” – or “Network unreachable”
Possible reasons for failure:
•
•
•
Wrong or bad IPA – see local IT
Broken or miss-configured network – see local IT & APPENDIX 12 (tracert)
Server is down or broken – see section 3.7 - stand-alone server tests
o If the SERVER is OK, you will need to get help from the IT department
because you probably have a NETWORK issue to deal with.
Do not continue to the next step until the ping test is a success. If ping is
supported on your network, and the server cannot be pinged, there is a
fundamental failure in the network set-up that will not allow anything further to
work. This would be like trying to make a bank transaction over the phone
when there is no dial tone. All your account, data, and process information
might be perfectly correct – but there is no connection to use them on.
3.9.4
Once the AW SERVER can be pinged successfully or verified network functional by another
means – open the client internet browser and enter the following format in the URL Address
window:
http://192.168.100.12:8081/RemoteAccess
Note: 192.168.100.12 is an EXAMPLE server IPA – enter your server’s IPA
here - see figure 29 in APPENDIX 14
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
36 of 102
3.9.5
3.9.6
3.9.7
If the connection is complete, “Security Alert” pop-up(s) may appear. The type and format of
the pop-up(s) will depend on the browser being used. Click YES or OK to proceed. For more
information and examples - see APPENDIX 8
The AWRA RemoteAccess LOGIN SCREEN should appear – see Figure 3.
If the AWRA RemoteAccess LOGIN SCREEN comes up – You have verified that your
AWRA CLIENT has “BASIC” network functionality.
o
If the AWRA RemoteAceess LOGIN SCREEN does NOT come up, and you are sure
that the AWRA SERVER Stand-Alone tests have passed, and you get the following
message content –
You will most likely need to download and install Java WebStart on the CLIENT PC – see the
information in Appendix 13 or Appendix 15 for a LINUX PC … You Will need
administrative permissions on the PC to do this. Install & Configure Java Runtime
components, then return to step 3.9.4.
o
FYI - If you click on “..proceed …” you might get to the login screen. But, that’s about it.
If you attempt to launch Remote Review or Virtual AW, you will get the notifications
referenced in Appendix 13, figures 22-26.
MAC OSX JAVA NOTE:
The MAC OSX platform MAY or MAY NOT give a Java Alert if JRE is NOT installed.
It MAY just sit there and do nothing when accessing AWRA.
Unlike the WINDOWS and LINUX platforms, the MAC OSX comes with JAVA as
part of its native load. It will only be without Java if Java is manually removed
from it. This should be a relatively rare occurrence in the IB. Reference figure 31 in
APPENDIX 2 for an example of how to check if Java is configured on the MAC - OR
o Use the “FINDER” function to see if a Java folder is installed –
Perhaps under Applications > Utilities > Java ?
o
If Java is not loaded – it can be downloaded and installed from the Internet:
Internet Search for the phrase Java Mac Download
Once you find the Java 1.4.2 or higher package for MAC -The
Download and Install process is relatively automated on the MAC …
Be aware, if multiple versions of Java are installed on the MAC, or you install multiple
packages - it is not automatically true that the most current or recent one is enabled.
The MAC platform must be configured to use whatever Java revision is desired and
resident. This manual does not describe or support how to do that.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
37 of 102
o
If the AWRA RemoteAceess LOGIN SCREEN still cannot be reached after
successfully installing Java – you will need to browse through the links below to
discover what is wrong.
For instance - - -
o
3.9.8
If you are getting message pop-ups asking whether or not to use a PROXY SERVER –
Answer NO to the proxy server question and see the information in Appendices 2 & 14
“as an example” depending on the platform, and browser being used …
o
Appendix 2 Client Browser Configurations – proxy server, cookies, etc…
o
Appendix 3, Network Ports
o
Appendix 4, AWRA CLIENT Overall Network Configuration & Performance
o
Appendix 13, Java Web Start and JNLP file handling
o
Appendix 14 Connection Issues
o
Appendix 15 JRE & linux
o
Appendix 16 The AWRA Installation ROOT password POP-UP
o
Section 7 – Trouble-shooting (SERVER – NETWORK – CLIENT)
When the AWRA RemoteAccess LOGIN SCREEN comes up –
Login with the standard aw login for your AW – i.e. (sdc) & (adw4.2), or (PREFERABLY)
any valid user account on the AWRA SERVER –
Select the SERVER from the pull-down (if there is more than one – or leave the one selected
that you have just logged into).
A comment about USER ACCOUNTS. It is advisable for the user to work with this
product from individual, site managed, USER ACCOUNTS. Using the default AW (sdc)
account is not as secure as individual accounts, and will make it hard for the AWRA
SERVER USER to know who is actually logged in at any given time.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
38 of 102
“VIRTUAL AW” MODE
3.9.9
Click on VIRTUAL AW
3.9.10 A pop-up may appear asking you if you want your login and password to be remembered? If
so, answer as you wish.
3.9.11 “Security Alert” pop-up(s) may appear. The type and format of the pop-up will depend on the
browser being used. Click YES or OK to proceed. For examples - see APPENDIX 8
3.9.12 While the connection is being confirmed, a RemoteAccess “Permision” pop-up will appear on
the AWRA SERVER indicating that a user is attempting to gain “Virtual AW Access”, and in
the Client Browser:
Client Browser
AWRA Server
If the CLIENT USER is using the default AW account “sdc” the AW user will not know
for sure WHO (other than SDC) is attempting to take Virtual AW control. If there are
specific individual accounts setup on the AW – like ‘Dr. Virtual’ or ‘Sandy’ the AW user
will then know specifically who is requesting control - by their login account.
This AWRA Server pop-up will remain on the AW for a pre-configured amount of time, during
which time the AW user can “GRANT” or “DENY” access. The timeout is configured in the
Service & Administration Page under “Configuration (APPENDIX 10).” After timeout - access
is granted by default. The Client Browser indication remains even after the connection is
established.
NOTE – If TVA (Tip Virtual Assist) is running, you will not be able to connect to Virtual
AW. See APPENDIX 9 for example CLIENT screens indicating the various reasons why
Virtual AW may not be available.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
39 of 102
3.9.13 Depending on the CLIENT browser you are using (i.e. Internet Explorer, Netscape, ForeFox,
Mozilla …) you “MAY” get a pop-up box something to the effect:
… you are attempting to open a .jnlp file, and the browser either wants to know what
you want to do with it, or the browser does not have the application to open it …
It might mean that step 3.9.7 (Java installation and configuration) was not successful, or was
not entirely COMPLETED. See APPENDIX 13, read and complete ALL the instructions there
– especially the procedure next to figures 22 & 23 – then try Virtual AW again.
3.9.14 Next, while the connection is being initialized, another POP-UP will come up on the CLIENT
indicating the initiated activity – showing the “VIRTUAL AW mode on the IP Address of the
AW Server”
3.9.15 After a period time - dependent on the network performance – a pop-up MIGHT appear
asking to the effect - if you want to trust the signed application by “GE Healthcare”? If so,
Click YES or START or whatever it requires to continue.
•
If too much time transpires between the “Grant/Deny/Timeout” & the “GE Healthcare
Trust” screen – the Virtual AW screen(s) may not come up. If so, just refresh the
browser, or try again – should come up now. There is an inherent time limit built into
this cycle.
3.9.16 After a period of time – dependent on the network performance – you will have the AW
Server window – allowing full remote control. This confirms AWRA CLIENT VIRTUAL AW
functionality.
•
If the client screen resolution is set for 1024 x 768 or less, you will need to use the scrollbar to view the entire Virtual AW screen – and - to view BOTH screens on a dual screen
AWRA SERVER.
•
If the client has a screen resolution of 1024 x 1280 or greater, there will be a POP-UP
type window at the bottom of the screen with selectable radio buttons for the RIGHT and
LEFT SCREENS of a dual display AW.
o
Also see APPENDIX 5 AWRA Virtual AW Performance“
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
40 of 102
MIP/MPR (REMOTE REVIEW)” MODE
3.9.17 Picking up from the AWRA RemoteAccess LOGIN SCREEN - Login with the standard aw
login for your AW – i.e. (sdc) & (adw4.2), or any valid user account on the AWRA SERVER select the SERVER from the pull-down (if there is more than one).
3.9.18 Click on “REMOTE REVIEW”
3.9.19 A pop-up may or may not appear asking you if you want your login and password to be
remembered? If so - Answer as you wish.
3.9.20 “Security Alert” pop-up(s) may appear. The type and format of the pop-up will depend on the
browser being used. Click YES or OK to proceed. For more information and examples - see
APPENDIX 8
3.9.21 After a period time - dependent on the network performance – a pop-up MIGHT appear
asking to the effect - if you want to trust the signed application by “GE Healthcare”? If so,
Click YES or START …
3.9.22 After a period of time – dependent on the network performance – you will have the AWRA
Remote Browser - See figure 4 in APPENDIX 1.
3.9.23 Choose an exam data set in the Remote Browser and click on MIP/MPR.
The Operator’s Documentation Appendices under “Image Requirements” defines what a valid
data set is for AWRA. This is accessible under the HELP button in the RemoteAccess Login
Screen – see figure 3
3.9.24 Depending on the CLIENT browser you are using you “MIGHT” get a pop-up box something
to the effect:
… you are attempting to open a .jnlp file, and the browser either wants to know what
you want to do with it (SAVE IT, OPEN IT, FIND A PROGRAM TO OPEN IT…)
If so - see APPENDIX 13, read and complete the instructions there – then try again.
3.9.25 After a period time - dependent on the network performance – a pop-up MIGHT appear
asking to the effect - if you want to trust the signed application by “GE Healthcare”? If so,
Click YES or START or whatever it requires to continue.
3.9.26 Once the Remote Viewer has launched (See figure 5 in APPENDIX 1), and displays the
selected exam, the display can then be manipulated with the tools in the remote 3D viewer.
If a message displays indicating that the selected exam is not suitable for viewing –
try another exam.
You have now established basic MIP/MPR (REMOTE REVIEW) functionality.
See APPENDIX 6 for other Remote 3D Viewer SERVER trouble-shooting
information.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
41 of 102
4.0 EASY INSTALL & AWRA ERRORS
If the following window pops up, you probably have selected the wrong media (Floppy
/cdrom), or the concerned drive and or media might be defective:
o
o
Notice - ! Malformed package
Notice - ! Error : Cannot access to media
If the following window pops up, you probably have a wrong or defective license key, and or
media:
o Installation Failed with ERROR CODE 30
AWRA & AW System ERRORS
AWRA and AW System errors can be examined and investigated in either the usual AW error logs –
such as /var/adm/messages, and/or ~sdc/logfiles/EasyInstallLog - and also in the application’s
dedicated logfile(s):
“OFFICIAL” AWRA LOGS SPECIFIED BY AWRA PROGRAM REQUIREMENTS
o
o
o
/export/home/sdc/logfiles/install.RemoteAccess.log
o Installation process information and errors
/export/home/sdc/logfiles/uninstall.remoteaccess.log
o UN-Installation process information and errors
/export/home/sdc/logfiles/remoteaccess.log
o Who logged in and when, including failed logins,
o When they launched MIP/MPR (REMOTE REVIEW) and what data
they looked at
o When they launched Virtual AW
o Any errors caught by the system as outlined in the requirements
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
42 of 102
ADDITIONAL AWRA ERRORLOG INFORMATION
Be careful, some of these logs will not have data UNTIL they throw an error.
o /export/home/sdc/logfiles/remoteaccess.gemsvnc.log
o The VNC server log - Virtual AW process information and errors
o Gives pixel rates and command tracing
Bandwidth and pixel rate reports are not actual snapshot type
measurements. Use these as composite indications of overall functionality –
not as a specific smoking gun type tool. This log will hopefully get reworked
in future releases to be more literally useful.
o /export/home/sdc/logfiles/remoteaccess.servers.log
o Traces and Info from the visserver (Remote Review engine) data loading
o /export/home/sdc/logfiles/remoteaccess.visserver6778.log
o Standard output from the visserver and render engine – one-per-port
remoteaccess.visserver6779.log
remoteaccess.visserver6780.log
remoteaccess.visserver6781.log
remoteaccess.visserver6782.log
NOTE: There are only THREE possible MIP/MPR (REMOTE REVIEW) users
allowed at any given time. However, if there are 3 users – one disconnects, and the
port is hung for a few seconds and has not reset while another request comes in –
the next port will be used. This is why you COULD have more than THREE port logs
in number sequence as shown here.
o /export/home/sdc/logfiles/remoteaccess.visserverdaemon.log
o Output from the VisServerDaemon.pl script that starts the visserver
o Contains the flow and shows the logic for selecting a port, starting and stopping the
visserver, too many users, etc…
o /export/home/sdc/logfiles/remoteaccess.vncdaemon.log
o Output from the VNCDaemon.pl script that starts the gemsvnc
o Contains the flow and shows the logic of deciding if the server is already running or
conflicted
o /export/home/sdc/logfiles/awra_catalina.out
o General session logging and errors. A good log to “tail –f” while using AWRA
o /export/home/sdc/logfiles/awra_localhost.DATE.log
o Web Server general process information and errors
o
/export/home/sdc/logfiles/
o awra_admin.DATE.log
o awar_host-manager.DATE.log
o awra_manager.DATE.log
These logs are tomcat-server logs. For the most part, they are not used by
AWRA. They may or may not be zero length.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
43 of 102
5.0 INSTALLATION FINISH TASKS &
INFORMATION
•
This service manual will be loaded onto the AW platform when this software option is
installed. It can be accessed at anytime via the SERVICE DOCS under the ADMIN pulldown.
•
This service manual can also be viewed on a PC directly off of the application cdrom.
•
The service manual direction number can also be ordered for hardcopy use if
necessary.
•
The AW and the ALL applications must be entered into GIB (Global Installed Base)
database after the initial successful installation in order to fulfill product-tracking
requirements. The AW must have a service-generated system ID to do this.
IF THIS IS NOT THE CASE – PLEASE COMPLETE THIS ASAP AND ENTER THE
AW SYSTEM, AS WELL AS THIS SOFTWARE OPTION’S ICD CARD MODEL AND
SERIAL NUMBER INTO GIB!
FAILURE TO ENTER THE SYSTEM AND ITS SOFTWARE APPLICATIONS INTO GIB
will result in GE Healthcare being in violation of FDA tracking compliance, and
this system will not be in the affectivity list for future upgrades.
The OLC AW Support line can direct you as to how to get GIB updated correctly if you
do not know how. Here is the global GIB link:
GIB : http://egems.gemedicalsystems.com/gib/gib_entry.jsp
•
Additionally, it is more and more advantageous to have the AW Workstation on a broadband
connection to the GE ILINQ CENTER. Remote system and software trouble-shooting, future
software and patch downloads, Tip Virtual Assistant (TVA), and other essential tools are now
available, and are coming available. Please have the AW system ID established, and drive
broadband ILINQ connectivity ASAP if at all possible.
Again, the OLC AW Support line can direct you as to how to get these things correctly
up and running if you do not know how.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
44 of 102
6.0 FRU’S
Following is the FRU list as of program general release (M4).
Because this manual will not be automatically updated for every software cdrom update that
does not change the details of this manual significantly - it is possible that in the future one might
get a newer version part number of the software cdrom when ordering this number, without the
part number in this manual getting updated before or at the exact same time.
All forward revisions of the application cdrom(s) will be setup to replace the old cdrom(s) and
purge them from availability.
As of program general release (M4) – End of 2005 - these are the FRU numbers:
FRU - AWRA SW & Docs on CD
5148586-2
FRU – AW Memory:
o HP XW8000 2.0GB DIMM DDR 266 DATARAM
2 X 1G modules
2390156
o ADD L 2GB RAM HP XW8200 Memory Package
2 X 1G modules
5127969
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
45 of 102
7.0 TROUBLE-SHOOTING
There are THREE basic hardware/software configurable components in the AWRA environment.
Below is a graphical example of what a typical AWRA environment might look like. There are
many variations on this theme that can and will exist – this is only an example:
1. The AWRA AW SERVER
2. The NETWORK(s) infrastructure(s)
Sec 3.4
Sec 3.7
Sec 4
Appendix 1
Appendix 6
Appendix 7
Appendix 10
Appendix 16
Sec 3.2.3
Sec 3.2.6
Sec 3.7 Suggestions
Appendix 3
Appendix 4
Appendix 12
Appendix 14
Appendix 17
Internet
Local Network
3. LOCAL and/or
Internet/VPN PC
CLIENT(s)
Sec 3.1.3
Sec 3.2.4
Sec 3.2.5
Sec 3.8 & 3.9
Appendix 2
Appendix 4
Appendix 5
Appendix 8
Appendix 9
Appendix 10
Appendix 13
Appendix 14
Appendix 15
Appendix 16
GE Healthcare is not ULTIMATELY responsible for supporting the configuration, and
operation of the CLIENT and or its NETWORKS, GATEWAYS, or SWITCHES. GEHC’s
DIRECT responsibility is the AWRA Server.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
46 of 102
APPENDIX 1 - SERVER MIP / MPR TEST
Java Web Start is
normally located in TWO
places on the AW Linux
Platform:
Testing the SERVER STAND-ALONE - OR - the SERVER-to-SERVER functionality
with the MIP/MPR function on the AW “LINUX” platform.
1) From the RemotAccess Login Screen - login and select REMOTE REVIEW.
2) The Password Manager may pop-up asking if you would like to have it remember your
logon. For testing purposes, answer NO.
3) Next, you “MAY” get a pop-up box something to the effect of the following:
OPENING REMOTEBROWSERLAUNCHER.JNLP
This “default” is generally
correct, but will not work
because it does not show
the javaws file complete
path.
You can select “Open
With” /usr/java/j2re
…/javaws/javaws to
cpmplete the path.
This is the Java
loaded with the native
AW platform.
Use the “Choose”
button to navigate
to and select this
path if this AW IS
NOT an AWRA
Server.
- Preferably Select “Open With”
/export/home1/sdc_imag
e_pool/appli/RemoteAcc
ess/jdk…/Linux/jre/java
ws/javaws
This is the Java
loaded with AWRA.
Use the “Choose”
button to navigate
to and select this
path if this AW IS
an AWRA Server.
4) After –
1. Dismissing the “Choose” Helper Application box by clicking “OPEN”
Either one will run AWRA
2. Clicking “OK” in the “Opening …jnlp” box –
The AWRA REMOTE BROWSER should come up – see Figure 4
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
47 of 102
FIGURE 4
AWRA BROWSER
5) Choose an appropriate exam data set in the Remote Browser and click on MIP/MPR.
For details on what an appropriate exam is - See the Operator’s Documentation Appendices
(Image Requirements) – accessible under the HELP button in the RemoteAccess Login
Screen – figure 3
6) “Security Alert” pop-up(s) may appear. Click YES or OK to proceed if they do.
7) The system will build the MIP/MPR study – may take a couple of seconds or minutes.
The REMOTE 3D VIEWER window should come up with the rendered exam.
(See Figure 5)
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
48 of 102
FIGURE 5
MIP/MPR (REMOTE REVIEW) 3D VIEWER
FIGURE 5A APPLICATION/X-JAVA-JNLP-FILE ERROR
See the next page …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
49 of 102
NOTE about the “Opening RemoteBrowserLauncher” pop-up in step 3:
o If you are using Mozilla (like on the AW), you can set the browser to automatically open the
MIP/MPR application correctly.
o Click on EDIT and PREFERENCES
o Select HELPER APPLICATIONS
CONFIGURE OR CREATE APPLICATION/X-JAVA-JNLP-FILE
If the
“application/xjava-jnlp-file”
application
configuration does
not exist – or is
faulty – the system
will present a popup indicating a
“Download Error”
See Figure 5A
This is the “EDIT”
or “New Type”
pop-up.
This is where the
process can be
automated – or –
not.
This is the
“Choose – Open it
with:” pop-up.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
50 of 102
APPENDIX 2 - CLIENT BROWSER
CONFIGURATIONS: (JRE, COOKIE & PROXY SERVER)
•
One of the points of variability with this type of application is related to the different
CLIENT web browsers that can be used, and the their different versions.
•
Also, as the CLIENT might be used for other web based applications and purposes,
there is the likelihood that browser and CLIENT configurations might change from
session to session making AWRA functional, NON-functional, and functional again at
any given time.
•
GE Healthcare is not directly responsible for supporting the ultimate
configuration of the CLIENT and or its NETWORKS, GATEWAYS, or SWITCHES
with all the potential service issues that can arise from them. However, following
are several generic CLIENT browser configuration information sets that can be used as
references and or suggestions
•
Administrative privileges MIGHT be needed. See the IT admin IF - for instance - the
“Advanced” tab is not available for access. GROUP policies might be set on the network
- and / or domain - that will not allow access to some of these features.
FIGURE 6
“IE” SETTINGS: JRE – JAVA RUNTIME ENVIRONMENT
& GE SAMETIME NOTE
Tools - Internet Options – Advanced
JAVA configuration options and
“Typical” Settings
It might be necessary at any given
time to experiment with these in order
to get functionality.
Other applications are also impacted
& impact these same settings.
GE SAMETIME NOTE
One impact example has to do with
the GE SameTime Client. It has been
experienced that these ‘typical’
settings may prevent access to
SAMETIME.
It has been noticed that if ALL
Microsoft VM boxes are DESELECTED – OR - if Java (Sun) &
ALL the Microsoft VM boxes are
DE-SELECTED – SameTime AND
AWRA will work fine. Apparently, as
long as JRE is installed, AWRA is OK.
You may need to experiment…
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
51 of 102
FIGURE 7
IE COOKIES SETTINGS
Tools - Internet Options - Privacy
Cookies need to be enabled
for this application to run
properly.
You have 2 options for doing
this:
The less secure method is to
set the security to Medium
for all sites – OR - use the
‘Advanced’ option to
OverRide Automatic Cookie
handling & BLOCK or
ALLOW
To be more secure, you can
allow cookies only from our
(your AW) site by pressing
the sites button.
Enter the IP address of your
AW and press the allow
button.
It will then appear in the
managed web site box below.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
52 of 102
FIGURE 7A AWRA COOKIES DISABLED NOTIFICATION
If cookies are disabled on the CLIENT - this screen will come up when accessing AWRA.
FIGURE 7B UN-SUPPORTED BROWSER NOTIFICATION
This example is when FireFox is used, but the same type of message will come up if an unsupported revision of IE, Netscape, Mozilla, or Safari is used. NOTE – Even though officially unsupported, FireFox MIGHT work anyway – to try – “click to proceed …”
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
53 of 102
You may have to turn off or
reconfigure your proxy server
setting(s) for this application to work
FIGURE 8
Here are a few “potential” actions that
you can do:
“IE” PROXY SERVER SETTINGS
TOOLS - INTERNET OPTIONS - CONNECTIONS
Select LAN Settings
1. First, try just selecting the bottom
checkbox – Bypassing the proxy
server for local addresses.
2. The use proxy server selection could
be turned off - unselected. However,
with this choice, you will need to turn
the proxy server back on again before
accessing external web sites.
3. The AWRA server could be entered
into the client's do not use proxy
server table in ADVANCED... (if the
browser version supports this?)
A DNS Alternative?
4. Even though the AW does not use
DNS, the network DNS network server
can potentially be configured for it. The
details are left to the local network admin.
But, the idea is to assign a hostname to
the AWRA in the network DNS server
which points to the IPA of the AWRA.
Then when the CLIENT(s) hit their proxy
server(s) – they in turn hit their DNS
server(s) – which in turn direct to the
configured AWRA server. You will need to
work with the IT / Network admin …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
54 of 102
FIGURE 9
NETSCAPE SETTINGS: JRE – JAVA RUNTIME ENVIRONMENT
Edit – Preferences
JAVA
configuration
options and
“Typical”
Settings
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
55 of 102
FIGURE 10 NETSCAPE COOKIES SETTINGS
On Netscape, you will
need to set your AW
Remote Access Server to
be a trusted site.
Start on any web page on
the AW – even an error
page.
Then, click on the site
controls icon in the tab
bar.
Select “I trust this site”
You can also do this from
Tools → Options.
Select the Site Controls
tab
Then select the AW
server web address, and
Allow cookies, Enable
Javascript, and Enable
Java.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
56 of 102
FIGURE 11 NETSCAPE PROXY SERVER SETTINGS
Tools – Options - General Tab - Connection Settings
Enter your AW Server’s IP
address into the “No Proxy
for” list.
There can be multiple
entries …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
57 of 102
FIGURE 12 MOZILLA/FIREFOX SETTINGS: JRE – JAVA RUNTIME
ENVIRONMENT
Tools – Options – Web Features
JAVA
configuration
options and
“Typical”
Settings
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
58 of 102
FIGURE 13 MOZILLA/FIREFOX COOKIES SETTINGS
Edit – Preferences - Privacy and Security - Cookies
Set to allow cookies or
allow them based on
your property settings
(which you set from the
“view” button next to it.
Or, select the Cookie
Manager, and then the
cookie sites tab, and
set it to allow cookies
on you’re AW server.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
59 of 102
FIGURE 14 MOZILLA/FIREFOX PROXY SERVER SETTINGS
Edit - Preferences – Advanced - Proxies
Select manual proxy configuration, and enter your AW server into
the “No Proxy For” line.
Can have multiple entries …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
60 of 102
FIGURE 31 MAC SAFARI SETTINGS: JRE – JAVA RUNTIME
ENVIRONMENT
Set to enable java
Set to allow cookies or
allow them based on a
“per site” configuration.
These are windows that
MIGHT come up as you
navigate to the AW
RemoteAccess server.
Notice that the Console
window displays the
java revision (must be
1.4.2 or later for
AWRA).
Also, note the LOG
location – might be
useful if issues arise?
FYI - Download window
– these are the java
files that AWRA sends
to the CLIENT.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
61 of 102
FIGURE 32 MAC PROXY SERVER SETTINGS
To access the PROXY
SERVER settings:
Click on “System
Preferences” on the
MAC Desktop.
Click on “Network”
Select your active
network port.
Click on “Configure”
Next Page …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
62 of 102
You MIGHT have to turn off or reconfigure your proxy server setting(s) for this application to work.
Here are a few “potential” actions that you can do:
1. The proxy server selection could be turned off - unselected. However, with this choice, you will
need to turn the proxy server back on again for accessing external web sites.
2. The AWRA server could be entered into the “Bypass proxy settings for these Hosts & Domains.”
“OR” A DNS Alternative?
3. Even though the AW does not use DNS, the network DNS server can potentially be configured for
it. The details are left to the local network admin – But, the idea is to assign a hostname to the AWRA
in the network DNS server which points to the IPA of the AWRA. Then when the CLIENT(s) hit their
proxy server(s) – they in turn hit their DNS server(s) – which in turn direct to the configured AWRA
server. You will need to work with the local Network IT/Admin to get this accomplished.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
63 of 102
APPENDIX 3 - NETWORK PORTS
PORTS
•
One of the points of variability with this type of application is related to the fact that the CLIENT(s) can and will
be used on various networks and sub-networks. Some of these will be accessed remotely via a VPN (Virtual
Private Network). Whatever the case, there will be network configuration, administration, and security issues
that could cause the AWRA system to be non-functional at times.
•
GE Healthcare is not directly responsible for supporting the ultimate configuration of the CLIENT and
or its NETWORKS, GATEWAYS, or SWITCHES with all the potential service issues that can arise from
them
•
One of the potential problems that could involve network, sub-network, or intranet hardware and or
administration, is the fact that AWRA requires certain network ports to be opened over the network on the
AWRA SERVER. If any of these ports are blocked or disabled by the network due to firewall rules,
network security policies, or network hardware configuration(s), AWRA functionality will suffer
PORT 8081 / 8443 - Web Server - this allows browsing of the AW database remotely.
•
If this port is blocked or disabled, you will not be able to access the AWRA RemoteAccess LOGIN
SCREEN. Your particular browser will determine the error message, for example:
Problem
Report
There was a communication problem.
Message ID TCP_ERROR
Problem
The system was unable to communicate with the server.
Description
Possible
Problem
Cause
Possible
Solution
•
The Web server may be down.
•
The Web server may be too busy.
•
The Web server may be experiencing other
problems, preventing it from responding to clients.
•
The communication path may be experiencing
problems.
Try connecting to this server later.
GE Healthcare CSE IB/NPI
Author
LSK
ONE, ANY or ALL of these
causes may be valid. Use
the SERVER Stand-Alone
test to eliminate the first 3.
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
64 of 102
PORT 5900 - VNC (Virtual Network Computing) - allows a remote user full access to the Virtual AW.
•
If this port is blocked or disabled, you WILLbe able to access the AWRA RemoteAccess LOGIN
SCREEN, but the VIRTUAL AW mode will not be able to be logged into. You will get some error
message indicating that the application is not available, or could not be reached.
PORT 6778 - is a proprietary port used for the MIP/MPR (REMOTE REVIEW) application. Technically, this is a
set of ports (6778, 6779, 6780), depending on the number of users connected, up to three at a time, each user
with their own connection. These ports are used to transfer commands to the render engine and receive back the
rendered images.
•
If this port is blocked or disabled, you WILL be able to login, and you WILL be able to select an exam
from the remote browser, and you WILL get the remote 3D viewer when you click on MIP/MPR at the
bottom of the remote browser. However, the 3D viewer will not return any rendered image display. It
will TIME-OUT, and / or display the following error pop-up in the remote 3D viewer:
Also see Appendix 6, Remote 3D Viewer SERVER Errors
•
Or, if only ONE remote user can run MIP/MPR – or TWO, but the THIRD cannot, and get the server
connection error – it might mean that one or more of the MIP/MPR ports (6778, 6779, and 6780) is
functional, and the other(s) could be blocked. You get the idea…
If it is determined that any of these problems exists in your installation – you will need to
contact the network IT person or persons for help in determining the availability of these
ports on your network, and potential remedies if they are blocked.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
65 of 102
AWRA NETWORK & SECURITY RELATED FAQ’S
o
What is the recommended access process for “remote” users of AWRA?
AWRA uses the security already in place in the site’s network enterprise. Access to the AW
should only be given to someone already on the local network. It is recommended that home
users connect to the AW, and AWRA only after connecting through the site’s VPN (Virtual Private
Network) or similar enterprise-grade firewall, configured to block all unused ports and unused
services. With any transfer of sensitive patient data, it is important to maintain security, only
allowing access to those with appropriate authorization.
o
When a VNC session is running, the port is open. Does it allow others to connect besides whom it was opened
for?
No, only the user who has logged in and kicked off the Virtual AW from the web page can connect.
o
What do you do about audit trails?
All logins are logged: who logged in and when. Any access to data is logged. Failed logins are
also logged. These logs are placed in the standard AW log directory.
o
If I run a security sniffer on the AW box what will I see?
You will see the port needed for the web server, on a secure socket layer.
o
Are images downloaded to the client? Where are they stored?
DICOM images are not downloaded to the client. Header information needed for annotation is
downloaded but not stored, only cached in the application. When the application exits, the header
information is erased from memory.
o
What user names are allowed to log in?
Any users that have been added to the AW user / account list are allowed to log in. AW
RemoteAccess uses the same login as the Linux OS.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
66 of 102
APPENDIX 4 - AWRA OVERALL NETWORK
PERFORMANCE
CLIENT NETWORK SETTINGS:
•
GE Healthcare is not directly responsible for supporting the ultimate configuration of the CLIENT and
or its NETWORKS, GATEWAYS, or SWITCHES with all the potential service issues that can arise from
them
•
However, this application is dependent upon network performance characteristics. So, following are few
things to consider when testing the CLIENT to determine if it is setup optimally
•
The particular CLIENT PC or Laptop has a particular NIC (Network Interface Card), or it may be referred to as
a Network Adaptor. Physically, it might take the form of a plug-in device or card, an externally connected
device, or an integral part of the computer’s motherboard. Either way, the device will have some level of
configuration involved with it depending on how it was designed to perform. The obvious parameters that are
of interest have to do with the network interface speed and data transmission characteristics.
o
o
•
Speed is the inherent ability of the your network interface to transmit a set amount of data in a set
amount of time. It is usually expressed in MB/S – Mega Bits per Second.
A device that is set for 10MB/S is transmitting data at a rate of 10,000,000 Bits per Second
Duplex refers to a signaling or transmission method where transmission directions are established.
Full Duplex is the ability to transmit data in both directions at the same time. It allows for
greater information transfer, but also demands higher performing system components.
Half Duplex conversely refers to data transmission in one direction at a time.
Most network communication applications – including AWRA - will obviously perform best at Full Duplex, and
a HIGH transmission speed. Most network interface devices or cards (NIC’s) can be configured for these
parameters or can be set to AUTO-DETECT the appropriate setting for the devices currently on the network.
While it is sometimes desirable to set – or force - the NIC to a particular setting, it is usually best to set it to
AUTO-DETECT.
o
AUTO-DETECT will generally negotiate the best network performance. It senses what the other
devices on the network segment are running and matches - if it is capable. For example, if all devices
on a segment are capable of running at GBS (gigabit per sec), and one device can only run at 100
MBS – all the devices will default to 100 MBS if they are set to AUTO DETECT. This is the best
performance for those devices on that network segment. If one or more of the GBS devices are
forced to GBS, there will most likely be excessive collisions on the network, and overall network
performance will suffer.
See the next pages for typical CLIENT NETWORK SETTINGS for a client running Windows XP.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
67 of 102
WINDOWS XP
EXAMPLE
Control Panel
Network
Connections
Find your
‘active’ Local
Area Network
connection
Right CLICK for
Properties
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
68 of 102
WINDOWS XP
EXAMPLE cont…
Your ‘active’ Local
Area Connection
Properties – right
click - properties
CLICK on
CONFIGURE
CLICK on
ADVANCED
SELECT “Speed &
Duplex”
CHOOSE “AUTO”
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
69 of 102
APPENDIX 5 - AWRA VIRTUAL AW
PERFORMANCE
Within the VIRTUAL AW (VNC) there is a VNC Settings Tool that can be adjusted if there is a
need to try and adjust the performance of the connection.
The tool is initiated from the VIRTUAL AW Mode by –
o
Clicking on “Settings” in the Virtual AW Window FILE PULL-DOWN
OR
o
Clicking on “Settings” in the “Virtual AW” POP-UP / BOX
If you have a screen resolution of 1024 x 1280 you will have a POP-UP type window
at the bottom of the screen with selectable radio buttons for the RIGHT and LEFT
SCREENS & SETTINGS.
There 3 settings:
Best Quality – this refers to display characteristics
Medium Q/P – this refers to display versus network performance
Best Performance – this refers to the network performance
There is no obligation to adjust this, and there are no established baselines to adjust to. The use
of these settings is strictly per your individual network experimentation if you feel you have a
need to try it.
FIGURE 15
PERFORMANCE VNC SETTINGS
VIRTUAL AW Mode - Settings
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
70 of 102
APPENDIX 6 – MIP/MPR (REMOTE REVIEW)
REMOTE 3D VIEWER SERVER ERRORS
For trouble-shooting purposes, if the remote 3D viewer comes up at all - it means:
• You were able to login
• You were able to contact the server
• You were able to access the MIP/MPR (REMOTE REVIEW) remote browser
o So, the basic connectivity and functionality of AWRA is OK.
o The problem is most likely on the AWRA SERVER or its network.
FIGURE 16
CONNECTION TO SERVER FAILED
In Figure 16, the remote viewer
comes up – BUT – it cannot
connect to the MIP/MPR
SERVER:
The MIP/MPR network
port might be blocked –
see Appendix 3.
If not sure about this – run
the SERVER-STANDALONE Test(s) – see
Section 3.7 & Appendix 1
If it passes, check with IT
about the network ports.
OR
There is a problem with
the Render Engine on the
“AW” SERVER
Check:
~sdc/logifles/remoteacce
ss.servers.log
~sdc/logfiles/remotacces
s.visserver#.log
Reboot the AW or Re-Load
the AWRA application
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
71 of 102
FIGURE 16A
UNABLE TO LAUNCH REMOTE MIP/MPR
In Figures 16A & B, the remote
viewer does NOT come up:
As you notice here, this is a
“JAVA” error report.
This TYPE of error is not an
AWRA generated error
sequence. It is past the AWRA
design code.
This TYPE of error means
that java webstart found a
problem, and it is most likely
due to one of its JAR files in
the AWRA file structure.
FIGURE 16B
UNABLE TO LAUNCH MIP/MPR - DETAILS
In the DETAILS you can see
that this particular error was
caused by a corrupted .jar
file.
When this TYPE of error comes
up, it can be for a number of
reasons – here are some
potential actions to follow:
Look at the DETAILS
Follow the clues if they are
actionable
Check:
~sdc/logifles/remoteacce
ss.servers.log
~sdc/logfiles/remotacces
s.visserver#.log
Re-Load the AWRA
Application to replace the
jar files.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
72 of 102
APPENDIX 7 - REMOTE ACCESS MANAGER
FIGURE 17
REMOTE ACCESS MANAGER WINDOW
IF & WHO is currently
logged into V-AW
DISCONNECT current VAW User (If “local” user
decides)
IF & WHO is currently
logged into Remote
Review
User configurable Virtual
AW Access - ALLOW or
SUSPEND parameters
AWRA RESTART
SERVER
To Manually RESTART the
server remotely – via a
command line:
/export/home1/sdc_image_pool/
appli/RemoteAccess/scripts/stop
Tomcat.sh
/export/home1/sdc_image_pool/
appli/RemoteAccess/scripts/start
Tomcat.sh
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
73 of 102
APPENDIX 8 - CLIENT BROWSER SECURITY
& ALERTS EXAMPLES
Although AWRA is not designed to be used directly on the internet - but is designed to be
used only on a local intranet - all of the inherent security features of the internet browsers are
still the same.
On the following pages are a few screen captures of what some of the various browser security
alerts look like. You will encounter some or all of these while using AWRA, and while using
network applications in general.
A FEW IMPORTANT THOUGHTS TO KEEP IN MIND when using any network application:
Be Cautious: Use the Trust Factor
Stick to web sites you trust with published privacy policies. Avoid any site or activity that seems
suspicious or questionable. The directions in this manual lead you to assumed “safe” local
intranet resources at your institution. Even so, make sure you understand why these security
alerts come up.
Download Smartly
Downloads can bring security threats directly onto your PC. Only download from sites you trust.
The assumption is that the IP Addresses you use to access the AWRA SERVER(s) on your
site’s intranet are “safe.” Even so, if you get a security warning, do not click "Yes" unless you
trust the source. Always read any user license agreements carefully prior to download.
Use Browser Security Tools
Your browser or security software may include special tools designed to help protect you on the
Internet, such as custom security levels for different sites, popup blockers, and content filters.
Sections 3.2.5, 3.2.6, and APPENDIX 2 discuss some of this within the context of using AWRA
on your local intranet.
Make sure you have the latest tools and learn how to use them effectively.
NOTE: THE VARIOUS SECURITY SETTINGS THAT CAN EXIST AT ANY GIVEN TIME ON
ANY OF THE VARIOUS BROWSERS CAN CAUSE GREATER OR LESSER SECURITY AS
WELL AS IMPACT THE ABILITY OF AWRA TO FUNCTION CORRECTLY. SOME, NONE OR
ALL OF THE POP-UP ALERTS IN THIS MANUAL CAN EXIST DEPENDING ON THESE
SETTINGS.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
74 of 102
FIGURE 18
“IE” SECURITY ALERTS
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
75 of 102
FIGURE 19
NETSCAPE SECURITY ALERTS
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
76 of 102
FIGURE 20
MOZILLA / FIREFOX SECURITY ALERTS
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
77 of 102
FIGURE 30
MAC SAFARI SECURITY ALERTS
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
78 of 102
APPENDIX 9 – VIRTUAL AW UNAVAILABLE
VIRTUAL AW IS CURRENTLY ALREADY IN USE
Virtual AW can only
support ONE connection
at a time. If the port is in
use – this is the
message that will
appear on the
requesting CLIENT.
VIRTUAL AW ACCESS HAS BEEN SUSPENDED
If the SERVER has
refused Virtual AW
connectivity via the
settings in the
RemoteAccess
Manager (See
APPENDIX 7) – this is
the message that will
appear on the
requesting CLIENT.
THE LOCAL AW CONSOLE USER HAS DENIED YOU ACCESS TO VIRTUAL AW
If the AW USER
“DENYs” Virtual AW
Access via the pop-up
that appears during the
CLIENT’s request – this
is the message that will
appear on the
requesting CLIENT.
TVA; TIP VIRTUAL ASSIST IS RUNNING – CANNOT CONNECT TO VIRTUAL AW
If TVA is running, you
will not be able to
connect to Virtual AW
until it is ended. Both
use VNC. This is the
message the CLIENT
will see.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
79 of 102
UNABLE TO LAUNCH VIRTUAL AW …
As you notice here, this is a
“JAVA” error report.
This TYPE of error is not an AWRA
generated error sequence. It is past
the AWRA design code.
This TYPE of error means that
java webstart found a problem,
and it is most likely due to one of
its JAR files in the AWRA file
structure.
In the DETAILS you can see that
this particular error was caused
by a problem with one of the .jar
files.
When this TYPE of error comes up, it
can be for a number of reasons –
here are some potential actions to
follow:
UNABLE TO LAUNCH VIRTUAL AW … DETAILS
Look at the DETAILS
Follow the clues if they are
actionable
Check:
~sdc/logifles/remoteaccess.ge
msvnc.log
~sdc/logfiles/remotaccess.log
Re-Load the AWRA Application
to replace the jar files.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
80 of 102
APPENDIX 10 – SERVICE & ADMIN TOOL
You need to log in as “root” to access the admin page
In Applications > More pulldown click on
“RemoteAccessTest”
You will see this window and
the obligatory security warning
pop-ups – like this.
After clicking OK to dismiss
the pop-ups, you “MIGHT” see
something like this window. If
so - Disregard the information
and click on the selection to
“proceed with your current
configuration.” Linux cannot
automatically detect Java. If
you click on the last option,
a COOKIE will be set, and
you will not see this alert
again. Remember though, IF
Java is subsequently
REMOVED – you will not see
this Java ALERT.
WebStart not Installed. The Application may not run adequately.
o
After dismissing the next
security warning pop-up,
you will get a
RemoteAccess Login
Screen.
o
Login with the AW root
login.
After logging in as root and
answering the question to
have the system remember
your password or not, and
dismissing the next security
warning pop-up – you will get
the Service and
Administration Page.
Next Page …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
81 of 102
SERVICE AND ADMINISTRATION PAGE FOR AW REMOTEACCESS
Service & Administration Page
Test the MIP/MPR application
with a canned data set:
Test MIP/MPR (REMOTE REVIEW)
Stand-Alone Functional Test
Click - This will test the
MIP/MPR application on the
server.
See APPENDIX 1 – step 3
Remote 3D Viewer will come
up with a pop-up message
about some images being
discarded – click OK
MIP/MPR of the test data
should display and allow
manipulation
Server Failure Test
Click - This will test that the
server exits gracefully after a
failure.
See APPENDIX 1 – step 3
Remote 3D Viewer will come
up with a pop-up message
“File read error. MIP/MPR will
exit”
Click OK – 3D Viewer should
dismiss and user should be
cleared from the
RemoteAccess Manager – see
APPENDIX 7
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
82 of 102
Service and Administration Page for AW RemoteAccess continued …
Service & Administration Page
List Current Users - Allows the ability to LIST and/or
DISCONNECT Current Users. Disconnect only applies
to MIP/MPR here.
Service Training – This is a service training overview
presentation on AWRA.
Configuration – Various AWRA configurable
parameters – see the next page …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
83 of 102
CONFIGURATION
Virtual AW access Login
Delay setup. When a
remote user attempts to
access V-AW, there is a
POP-UP on the AWRA
SERVER, which allows the
AW user to GRANT or
Deny. If no response Access is granted after a
delay.
Define WORK WEEK
Set delay for 15 sec – to –
5 minutes for Work Week.
Set delay for 5 sec – to – 5
minutes for Non Work
Week.
Remote AW Auto-Logoff
If no Virtual AW activity
after 15 – to – 60 minutes,
the AWRA session is
disconnected.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
84 of 102
VIRTUAL AW CONNECTION TO SERVER LOST – INACTIVITY TIMEOUT
This is an EXAMPLE screen of what will be viewed on the PC CLIENT if
the Virtual AW “Inactivity” Auto-Logoff kicks in – or the network connection
to the AW SERVER is lost for some reason:
Notes about this example:
•
Other connection termination reasons can also cause this
notification.
•
The “color bars” background may or may not present.
•
The pop-up message will simply be an “OK” acknowledgement.
After it dismisses the session can be re-tried via the normal login
process again.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
85 of 102
SERVICE AND ADMINISTRATION PAGE – VIEW TRAINING
Click on “Service Training”
Mozilla will want to know
what to do with this file?
You can open the file with
the default ggv utility.
OR Preferably
You can open the file
with “acroread” by filling
in this path …
usr/bin/acroread
In Mozilla - Pull down EDIT
and select Preferences…
You can also set Mozilla to
use this “acroread” setting
profile in the future for this
file.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
86 of 102
APPENDIX 11 – MAX # OF USERS ERROR
“BOGUS” MAXIMUM NUMBER OF USERS ALREADY CONNECTED
When the AWRA SERVER senses that all 3 MIP/MPR ports are
being used, it returns this “normal” message to any additional
attempted users – On the AWRA server, the RA Manager shows
the reason for the message – 3 users … this is the normal limit.
However, this COULD happen even if there are no MIP/MPR
users actually connected.
This could result from 3 UNSUCCESSFUL attempts to launch the
MIP/MPR analysis application. For instance, if the Windows “File
Types” application (detailed in APPENDIX 13 ) is not set correctly:
This COULD cause the MIP/MPR Server to NOT disconnect the
failed users cleanly on the error, or at all.
To clear this - either reboot the AWRA SERVER and then refresh the RA Manager – OR – access the
RemoteAccessTest ADMIN page to disconnect users – see APPENDIX 10
Also, see section 3.7.6.2 for discussion on how to test MIP/MPR Server disconnections with the AWRA
MIP/MPR Service/Admin. Diagnostics.
Under normal conditions, the current user is disconnected as soon as the MIP/MPR 3D Viewer is exited.
The Refresh button should “normally” update this.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
87 of 102
APPENDIX 12 – PING
PING
First of all, what exactly is Ping?
Ping is actually an acronym for the words 'Packet INternet Groper'.
The Ping utility is essentially a system administrator's tool that is used to see if a computer is
operating and also to see if network connections are intact. Ping uses the Internet Control
Message Protocol (ICMP) Echo function. A small packet is sent through the network to a
particular IP address. This packet contains 64 bytes - 56 data bytes and 8 bytes of protocol
reader information. The computer that sent the packet then waits (or 'listens') for a return packet.
If the connections are good and the target computer is up, a good return packet will be received.
PING can also tell the user the number of hops that lie between two computers and the amount
of time it takes for a packet to make the complete trip. Additionally, an administrator can use
Ping to test out name resolution. If the packet bounces back when sent to the IP address but not
when sent to the name, then the system is having a problem matching the name to the IP
address. The time it takes for the packet to get to the target computer and back again is known
as the round trip time. If this takes an extended period of time, it is indicative that something may
be wrong.
Blocking ICMP packets on a network at an Internet access point is a common network
administration security policy. PING can be used to flood a network as well as discover network
resources by malicious Internet entities. Blocking PING within an intranet is more rare, but is
also a potential reality.
If your particular AWRA intranet has blocked the PING ICMP Echo function, you will not
be able to complete ping test sections of the CLIENT TESTS – section 3.9. You will need
to either:
o
Continue with the next steps in section 3.9 and see if the CLIENT can connect to
the AWRA SERVER – if so, the PING test is irrelevant.
o Contact and work with the network / IT admin to allow PING or help you establish
the network connection via another method to discover the connectivity status.
TRACE ROUTE
There is another useful tool that can be employed if the ping connection test shows problems,
and IF YOUR WINDOWS VERSION SUPPORTS IT - tracert (TRACEROUTE). The tracert
command is used to trace a network packet being sent and received and the amount of hops
required for that packet to get to its destination. The functionality of TRACERT is essentially the
same under all versions of windows.
Tracert uses the IP TTL field and ICMP error messages to determine the route from one host to
another through a network. Care must be taken with tracert as it shows the optimal route, not
necessarily the actual route. To be accurate, it is possible to ping from a UNIX machine back to
the PC using the -R option to record the route taken - but only if the particular network devices
support it.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
88 of 102
It is not the purpose of this document to completely describe and support the use of tracert, or
any other network analysis tool. It is merely to suggest possible actions to discover network
functionality within the AWRA set-up and test phase. Additionally, there are other similar tools
available in the network analysis community with GUI features and automated functions that can
be used for this purpose also…
Here is an EXAMPLE tracert instance for reference:
TRACERT EXAMPLES
This tracert host has an IPA
of 3.70.205.###
Here is an example tracert
SUCCESS for a device on the
same local subnet. Note: there
are no hops or gateways to
this device.
Here is an example tracert
SUCCESS for a device on
another subnet. Note: there is
an intermediate gateway used.
Here is an example tracert
FAILURE for a device on
another distant subnet. Note:
intermediate gateways and
paths. The failure could mean:
Device is down
Device is broken
Network 3.231.35.190 is
broken
Some other missconfiguration or
malfunction on the
network or the network
devices?
Here is an example tracert
SUCCESS for a device on a
distant subnet.
Remember: tracert shows the
optimal route, not necessarily
the actual route. The network
connection might be fine, but
there could still be a network
loop preventing your AWRA
connection from working.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
89 of 102
APPENDIX 13 – WEB START & JNLP
If Java WebStart – jre1.4.2
or higher is not installed on
the LINUX CLIENT you will
get this page.
FIGURE 21: TO RUN THIS APPLICATION …
A WINDOWS PC will automatically detect if JRE is installed when it accesses the AWRA
SERVER. So, if it reports the above message – either JRE is not installed, or the wrong
version is installed.
A LINUX PC cannot automatically detect if JRE is installed. So, it will post this message
each time it accesses the AWRA SERVER. See APPENDIX 15 for LINUX JRE install.
If it is a WINDOWS PC,
this screen will be without
this option.
This option is a workaround
for linux systems that have
JRE installed, and do not
want to encounter this
screen each time AWRA is
accessed. This option sets a
cookie so that the Linux
browser knows that JRE is
installed next time.
Java Web Start provides a platform-independent, secure, and robust deployment technology. It
enables developers to deploy full-featured applications to end-users by making the applications
available on a standard Web server. By using any Web browser, end-users can launch the
applications and be confident they always have the most-recent version. The CLIENT PC
environment needs to have these “java” components loaded on it for AWRA to work. This
happens by downloading j2re1.4.2 or higher Java Web Start from the AWRA SERVER per the
above “Download …” option link - OR - from the Internet, and installing it in its default location on
the PC windows environment.
WARNING: It is possible that the ACCOUNT PERMISSIONS on the CLIENT will not allow the
download or install of Java, or any other application. The administrator of these permissions will
need to be consulted.
Some of the typical notifications that might come up - apart from the above example if Java Web
Start is not installed on the CLIENT or is not set to handle the AWRA JNLP file downloads
during AWRA functionality - are displayed here – Figures 22 - 25. These are examples from
Windows Internet Explorer. Be aware that other browsers will have various different notifications.
The important factor for trouble-shooting is to understand the content and the timing:
o THE MESSAGE COMES UP AFTER LOGGING INTO AWRA
o THE JNLP FILE IS BEING DOWNLOADED FROM THE AWRA SERVER
o THE CLIENT EITHER:
o DOES NOT KNOW WHAT TO DO WITH IT
OR
o DOES NOT HAVE THE WEB START SOFTWARE TO DO IT WITH
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
90 of 102
These types of messages mean that you need to check that Java Web Start is installed, and or
check that it is being used to handle the downloaded JNLP file from the AWRA server. The only
immediately useful selection when these messages appear is to click on OPEN, and see if
it works. Saving the jnlp file is of no value. See the following pages …
These messages mean that windows is not configured to open this type of file, or does not have
the software to do it. Selecting from the program list might find the java web start application or it
might not. Using the web service to search sounds nice, but usually goes nowhere. Either way see the following examples and procedure …
FIGURE 22: WINDOWS CANNOT OPEN THIS FILE
PROCEDURE
If Java Web Start – jre1.4.2 or higher - is
already downloaded on the CLIENT, it will
show up as a selectable item in:
IE – Internet Options – Advanced
(See Appendix 2)
If not, or if you are not sure, or if you
suspect a problem with it, or if you need a
newer version:
1. Download and install it from the
AWRA SERVER as in the option link in
Figure 21 - OR - Find Java Web Start on
the Internet.
2. Download and install on the CLIENT
FIGURE 23: WOULD YOU LIKE TO OPEN THE FILE OR SAVE IT? 3. Exit and Restart the IE browser
4. Make sure the new download shows up
in IE – Internet Options – Advanced and
is selected (See Appendix 2)
5. Go to My Computer and select Tools Folder Options - File Types
6. Scroll down to the JNLP File Type (or
create it if it does not exist – see step 8)
and click on "change" to change the
program it opens with.
7. Select “Java™ Web Start Launcher” or
“javaws” or whatever the designation for
the Java software that was just installed,
and click OK.
8. To create the JNLP file extension if it
does not exist in the File Types list:
9. Click New
10. Enter JNLP in the File Extension Field
11. Click OK
12. Go back and complete step 6
Example screens continued on next
page …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
91 of 102
FIGURE 24: DO YOU WANT TO OPEN OR SAVE THIS FILE?
FIGURE 25: DO YOU WANT TO SAVE THIS FILE?
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
92 of 102
FIGURE 26: BROWSER WITH CHARACTERS …
In addition to the Download/Save/Open
message pop-ups described in figures
22-25, another IE Browser window might
open with various extraneous
characters in it.
In this case, in:
My Computer – Tools – Folder
Options – File Types – JNLP –
Change
There is most likely an application
selected to open this file other than the
java web start application.
Select the java web start application and
try again
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
93 of 102
APPENDIX 14 – CONNECTION ISSUES
FIGURE 27: NETWORK PERFORMANCE SENSE / YOUR NETWORK SPEED
Network perf /
speed sense
notification – self
explanatory …
FIGURE 28: POTENTIAL PROXY SERVER PROBLEM / ACCESS DENIED
If the internet
browser is setup to
use a “proxy
server” this is the
type of message
that MIGHT present
when you attempt to
connect.
It is also possible
that the browser will
just remain active,
but blank – as
though it cannot
find the resource –
and eventually
TIMEOUT.
FIGURE 28A: OPERATION TIMED OUT …
See APPENDIX 2 for
example browser
configurations.
NOTE: These are
general browser
errors and MIGHT
have other root
causes also…
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
94 of 102
FIGURE 29: HTTP STATUS 404 - GENERIC CONNECTION ERROR
Figure 29: HTTP 404
This error could come up –
• If there is an incorrect entry in
the BROWSER ADDRESS
BAR – URL.
OR
• If the resource (i.e. RemoteAccess) does not exist.
Another “potential” CONNECTION issue that could present as an
‘HTTP 404 Resource Not Available’ error, ‘Operation Timeout’, or
TCP_ERROR error, is related to the AW Firewall (PNF) – if the AW
supports it. During the AWRA installation, it SHOULD automatically
configure the PNF so that AWRA will work. If the FireWall is turned off,
it will still configure it, but leave it off (as it finds it). The point is, if something
goes wrong during this process (the installation fails, the firewall fails, the
configuration fails, etc…) it could result in connection problems (that’s what
firewalls do – block connections). See APPENDIX 16.
Also see APPENDIX 3
ONE, ANY or ALL of these causes
may be valid. Use the SERVER
Stand-Alone tests to eliminate
the first 3.
There was a communication problem.
Message ID TCP_ERROR
The system was unable to communicate with the server.
Problem
Description
Possible
Problem
Cause
•
•
•
•
Possible
Solution
The Web server may be down.
The Web server may be too busy.
The Web server may be experiencing other
problems, preventing it from responding to clients.
The communication path may be experiencing
problems.
Try connecting to this server later.
GE Healthcare CSE IB/NPI
Author
LSK
Communication Path type errors
can be network and/or
CONFIGURATION errors. For
instance – IF the failing client is
NOT on the local subnet of the
AWRA SERVER, and IF the AWRA
SERVER is NOT configured for a
default gateway, (or is configured
incorrectly) – this is one of the
errors that could present. Make
sure to understand and complete
the default gateway
configuration for the AW/AWRA
SERVER – see the AW Service
Manual.
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
NOTE: These are all general
browser errors and MIGHT have
other root causes also…
Figure 29A: TCP_ERROR
FIGURE 29A: COMMUNICATION PROBLEM
Problem
Report
In this example, even though the
UPPER CASE R and A in
RemoteAccess was not observed –
the software should still
automatically re-direct to
RemoteAccess. However, if
RemoteAccess actually does not
exist – like it was uninstalled or not
installed successfully – this could
still come up.
2
Date
Feb. 14, 2006
Sheet
95 of 102
APPENDIX 15 – THE ‘LINUX’ CLIENT
In most cases, you will get
this page if Java WebStart –
jre1.4.2 or higher is installed
or not on the LINUX
CLIENT. MOST linux
platforms cannot
automatically detect if Java
is installed or not.
FIGURE 21A: TO RUN THIS APPLICATION
Reference Figure 21
1. Click here to proceed if
you think or know JRE is
installed.
A WINDOWS PC will automatically detect if JRE is installed when it accesses the
AWRA SERVER. So, if it reports the above message – either JRE is not installed,
or the wrong version is installed.
MOST LINUX PC platfroms cannot automatically detect if JRE is installed.
So, it will likely post this message each time it accesses the AWRA SERVER, unless
a cookie is set.
o
If you click on option 1 (Click here to proceed with your current unsupported
configuration) and JRE is really not installed – you will get to the screen in
Figure 21B and have no javaws to navigate the browser to - to open the
requested application file. The application will not work.
o
If you click on option 2 (Click here if webstart is already installed) after
confirming that JRE is really installed – you will get the same Figure 21B
screen requiring you to point the browser to the javaws file. The next time
you access AWRA, you will likely not get the screen in figure 21A, but go
directly to 21B again.
o
If you click on option 2 and JRE was somehow removed between the last
successful time and now – you will still get the screen in 21B. Only this time,
there will be no javaws on the system to point the browser to. The application
will not work.
o
In this last scenario, you are at the point where you will have to install JRE
– see the rest of this appendix 15…
GE Healthcare CSE IB/NPI
Author
LSK
2. This option is a
workaround for linux
systems that have JRE
installed, and do not want
to encounter this screen
each time AWRA is
accessed. This option sets a
cookie so that the Linux
browser knows that JRE is
installed next time.
However, IF Java is
subsequently removed –
you still will no longer get
this warning - while the
cookie is set.
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
96 of 102
INSTALLING JAVA ON LINUX
While linux is a viable PC OS, it is admittedly not nearly as prevalent as the
windows environment. Even so, AWRA does support the linux client platform.
The problem comes in that the revisions of linux in the IB are potentially many
and varied. So, this manual cannot establish with absolute certainty what
revisions of linux will or will not work correctly with AWRA. Theoretically, all linux
platforms should work, as long as the Internet browser type and revision are
correct for AWRA, and as long as the correct version of JRE (Java Runtime
Environment) and Java WebStart are installed – see section 3.2.4.
The primary issue that needs to be overcome on the Linux platform has to do
with installing the JRE and Java Web start application on the Linux system when
it does not exist. The process to correctly place, execute, and install the Java
application files can be dependent on the version of Linux on the CLIENT:
o The Linux PC user is encouraged to discover the details for JRE
installation for their particular Linux platform.
o The following is a suggested process to install JRE on a Linux PC.
o It is based on our experience with using the Linux AW as an
AWRA CLIENT.
o
IF JRE IS NOT INSTALLED, the user will be confronted with the
notification – similar to Figure 21 – with a link to click - to download
& install JRE 1.4.2 …
Next page …
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
97 of 102
PROBLEM:
On a windows environment, the installation of the JRE files and environment is automatic once
the RUN or INSTALL is clicked after or during the download – referenced in APPENDIX 13.
On a linux system, the download retrieves a *.bin file - it does not install automatically.
SOLUTION:
When the linux CLIENT accesses the AWRA SERVER, but does not have JRE installed, or the
wrong revision of JRE is installed – the user is prompted to Click on a link to DOWNLOAD the
JRE files and application. After the user is asked to accept the licensing agreement, the next
pop-up window is as below. The JRE BIN file needs to be saved to disk.
The actual location to save the file is only
critical in that it should be saved somewhere
that the user has executable permissions in.
A location could be created that makes some
logical sense – perhaps a directory called
JREDownload or JavaDownload, etc …
Here again NOTE – If the PC user does not
have administrative privileges to
download, the IT contact or PC managing
entity will need to help with all of this.
After successfully downloading the JRE .bin
file, perform the following:
o
On the Linux PC open a command
window, and navigate to the location of
the downloaded file.
o
Using the change attributes command –
chmod – make the file executable:
chmod +x j2re-1_4_2_08-linux-i586.bin
o
Execute the file now by typing it in and
hitting ENTER – in this case:
j2re-1_4_2_08-linux-i586.bin > ENTER
o
o
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
Read and accept the licensing agreement
– at which time the JRE files should be
expanded and placed in a corresponding
file structure within the directory that the
user created.
Now, when AWRA is accessed and the
.jnlp file is downloaded –
as in Figure 21B on the next page, and in
Appendix 1 – the path to …/javaws can
be selected and the application will be
able to run.
2
Date
Feb. 14, 2006
Sheet
98 of 102
CHOOSE THE JAVAWS LOCATION TO RUN …
Scenario ONE
This example screen
represents what might come
up when using an AW linux
box as the AWRA CLIENT.
This javaws path shown is
the AW platform javaws
location.
FIGURE 21B
LINUX JAVA CONFIGURATION
If the AW happens to be an
AWRA SERVER, javaws will
also reside in
/export/home1/sdc_image_poo
l/appli/RemoteAccess/jdk…/Lin
ux/jre/javaws/javaws
For the purposes of this
procedure, we are installing
the JRE .bin package on an
unspecified LINUX PC.
So, the path to select javaws
will be determined by what
was created or selected while
downloading and installing the
JRE .bin file on the previous
page.
In this case, as an example the Choose button would be
used to navigate to –
/export/home/sdc/JREDown
load/../.. (or whatever was
used …)
Hopefully, you get the idea …
Scenario TWO
It is also possible (especially if the Linux client is not an AW) that instead of the above
Box, you might get the pop-up in Appendix 1 – Figure 5A, or something similar… This means
that the browser (in this case MOZILLA) is not correctly configured to know what HELPER
APPLICATION to use to open this *.jnlp file. Use the information in Appendix 1 to “Configure or
Create application/x-java-jnlp-file” Helper Application in the Mozilla Preferences. Note – the
information in Appendix 1 uses the AW as the example platform. If the Linux Client is NOT an
AW, your path to the Helper Application (Java Web Start / javaws) will not be
/export/home/sdc/…, but rather whatever the path is that was selected when Java was installed
on the Linux Client – for example what is shown in figure 21B above.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
99 of 102
APPENDIX 16 – THE AWRA INSTALLATION
ROOT PASSWORD POP-UP
AWRA INSTALLATION ROOT PASSWORD POP-UP / PNF FIREWALL
CONFIGURATION
This is an example of
the AWRA ROOT
password pop-up
window. If the
command-line
installation script is
used, the information is
the same – only in the
command-line.
If there is a PNF – here
is the status. AWRA will
automatically configure
the PNF to allow AWRA
to work. If the PNF is
OFF, AWRA will still
configure it, but also
leave it OFF. You will
not see this on PNF-less
platforms.
AWRA will automatically
cleanup log-files from
the PILOT version of
AWRA that tended to
grow out of control. The
issue is resolved, but
this will eliminate it going
forward as the PILOT
versions are all
replaced.
NOTE: This a typical “example.”
Pay attention to the feedback – it might alert you to an issue?
If you need more time to view the script feedback, or need to capture it, run the command-line
installation script (See Section 3.6), and or examine the installation log (See Section 4).
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
100 of 102
APPENDIX 17 - INTERESTING ‘NICE-TOKNOW’ STUFF
“SKELLETON” LOGIN SCREEN
This is the result of a CLIENT attempting
to connect to an AWRA SERVER
immediately after the AWRA
Application had been UN-INSTALLED
on the SERVER. In this case, the “IE”
browser somehow manufactured a
“skeleton” login screen – presumably from
its cache and/or other settings. Further
attempts to connect display the “HTTP
STATUS 404 – RemoteAccess not
available message” – as it normally should
when AWRA is not available.
This appears to be a “perfect storm” type
occurrence – timing, settings, and actions
all lining up just right … or wrong?
FYI – this sort of thing (“perfect
timings/settings storm”) is not uncommon
with a network application like this.
Be aware – try things over again – close
browser / re-open browser – restart
application – go get a cup of coffee - etc …
Don’t get too upset – work the problem.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
101 of 102
VIRTUAL AW CONNECTION TIMEOUT ON VPN
Disclaimer: This one is a bit nebulous – not completely understood.
It has been noticed - in at least one AWRA installation - that AWRA appears to lock up over a
VPN session. It was discovered in this particular case that there was the ability to operate within
the VPN session at a couple of different levels. The default level apparently used a "Juniper
Systems Secure Network Manager Application." I did a little investigating about this, and it is a
VPN solution that allows centralized management of Firewall, Encryption, and User access.
Anyway, when logged into this VPN with this application running by default, AWRA would run
well for a time, and then appear to lock-up (actually disconnect). In this case, this was also
consistent with other issues on this VPN – for instance, the Centricity PACS also was
experiencing similar problems when accessed remotely over the VPN.
Some experimentation revealed that when the "network manager" session was ended, or
dismissed – which apparently this VPN allows the user to do – and the session is just run on the
native VPN connection - AWRA and Centricity connection sessions work just fine, for as long as
the connection is desired.
The information that was somewhat meaningful in the AWRA AW remoteaccess.gemsvnc.log
(See Section 4) was the following:
19/01/2006 19:55:39 rfbProcessClientNormalMessage: read: Connection
timed out
19/01/2006 19:55:39 Closing client connection 192.168.210.5
While investigating the origin of this particular error posting, the presumption in this particular
case was that the TCP/IP socket was broken for this session, and will not be able to recover.
This would be interpreted as a basic network problem (imagine that?).
In this case, it would have been interesting to capture the client side logs, to see what they
pointed at – the network manager software perhaps?
While not implying any in-depth level of network expertise, and not being able to get any detailed
information from this site’s IT experts - this issue MIGHT have something to do with the following
speculation:
Perhaps this site has an SSL based VPN rather than an IPSEC based VPN. Some SSL based
VPN’s have issues supporting non-HTTP applications. Non-Web applications require a client
program to run on the clients, usually ActiveX control or Java applet that redirects network traffic
from its intended destination to the SSL VPN gateway. Thus, this is where the network timeout
MIGHT occur?
Take this information for what it is worth. This sort of thing will probably be relatively common
with this type of application. The take-away is – use the divide-and-conquer idea:
AWRA worked fine as stand-alone & fine on the local network > AWRA fails when on the
VPN (so does centricity pacs) > AWRA worked fine when the network manager was
turned off on the VPN session > Problem is most likely a site VPN issue > Hand off to IT >
Keep customer informed > DONE.
GE Healthcare CSE IB/NPI
Author
LSK
AWRA Installation / Service Manual
Rev.
5138756-100_rev2
2
Date
Feb. 14, 2006
Sheet
102 of 102