AW Distributed Applications - Enterprise

Server™
AW Server 3.2 Installation and Service Manual
Class A

5719443-1EN
Revision 8
US English
© 2015 - 2020 General Electric Company
All rights reserved.
Legal Notes
Trademarks
All products and their name brands are trademarks of their respective holders.
• GE and the GE Monogram are trademarks of General Electric Company.
• Advantage Workstation is a trademark of General Electric Company or one of its subsidiaries.
• AW Server and InSite are trademarks of General Electric Company or one of its subsidiaries.
• Microsoft, Windows, the Windows logo and Internet Explorer are either registered trademarks
or trademarks of Microsoft Corporation in the United States and/or other countries.
• Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
• Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
• Mozilla and Firefox are registered trademarks or trademarks of Mozilla Foundation in the United
States and/or other countries.
• Intel, Core, Pentium, and Xeon are trademarks are trademarks of Intel Corporation.
• Sun, the Sun logo, Sun Fire, Java and Javascript are trademarks or registered trademarks of
Oracle, Inc. in the U.S. and certain other countries.
• HP, HEWLETT-PACKARD and the HP Logo (shown below) are registered trademarks that belong
to Hewlett-Packard Development Company, L.P.
• VMware and VMware vSphere are registered trademarks or trademarks of VMware, Inc. in the
United States and/or other countries.
• DICOM is the registered trademark of the National Electrical Manufacturers Association for its
standards publications relating to digital communications of medical information

Copyrights
All Material Copyrighted (c) by the General Electric Company, All rights reserved.

Important Precautions
Language Precautions
ПРЕДУПРЕЖ Това упътване за работа е налично само на английски език.
ДЕНИЕ • Ако доставчикът на услугата на клиента изиска друг език, задължение на клиента е да
(BG) осигури превод.
• Не използвайте оборудването, преди да сте се консултирали и разбрали упътването за
работа.
• Неспазването на това предупреждение може да доведе до нараняване на доставчика
на услугата, оператора или пациентa в резултат на токов удар, механична или друга
опасност.
警告 本维修手册仅提供英文版本。
(ZH-CN) • 如果客户的维修服务人员需要非英文版本，则客户需自行提供翻译服务。
• 未详细阅读和完全理解本维修手册之前，不得进行维修。
• 忽略本警告可能对维修服务人员、操作人员或患者造成电击、机械伤害或其他形式的伤
害。

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server i

 警告 本服務手冊僅提供英文版本。
(ZH-HK) • 倘若客戶的服務供應商需要英文以外之服務手冊，客戶有責任提供翻譯服務。
• 除非已參閱本服務手冊及明白其內容，否則切勿嘗試維修設備。
• 不遵從本警告或會令服務供應商、網絡供應商或病人受到觸電、機械性或其他的危險。
警告 本維修手冊僅有英文版。
(ZH-TW) • 若客戶的維修廠商需要英文版以外的語言，應由客戶自行提供翻譯服務。
• 請勿試圖維修本設備，除非 您已查閱並瞭解本維修手冊。
• 若未留意本警告，可能導致維修廠商、操作員或病患因觸電、機械或其他危險而受傷。
UPOZORENJE Ovaj servisni priručnik dostupan je na engleskom jeziku.
(HR) • Ako davatelj usluge klijenta treba neki drugi jezik, klijent je dužan osigurati prijevod.
• Ne pokušavajte servisirati opremu ako niste u potpunosti pročitali i razumjeli ovaj servisni
priručnik.
• Zanemarite li ovo upozorenje, može doći do ozljede davatelja usluge, operatera ili pacijenta
uslijed strujnog udara, mehaničkih ili drugih rizika.
VÝSTRAHA Tento provozní návod existuje pouze v anglickém jazyce.
(CS) • V případě, že externí služba zákazníkům potřebuje návod v jiném jazyce, je zajištění překladu do
odpovídajícího jazyka úkolem zákazníka.
• Nesnažte se o údržbu tohoto zařízení, aniž byste si přečetli tento provozní návod a pochopili
jeho obsah.
• V případě nedodržování této výstrahy může dojít k poranění pracovníka prodejního servisu,
obslužného personálu nebo pacientů vlivem elektrického proudu, respektive vlivem
mechanických či jiných rizik.
ADVARSEL Denne servicemanual findes kun på engelsk.
(DA) • Hvis en kundes tekniker har brug for et andet sprog end engelsk, er det kundens ansvar at
sørge for oversættelse.
• Forsøg ikke at servicere udstyret uden at læse og forstå denne servicemanual.
• Manglende overholdelse af denne advarsel kan medføre skade på grund af elektrisk stød,
mekanisk eller anden fare for teknikeren, operatøren eller patienten.
WAARSCHU Deze onderhoudshandleiding is enkel in het Engels verkrijgbaar.
WING • Als het onderhoudspersoneel een andere taal vereist, dan is de klant verantwoordelijk voor de
(NL) vertaling ervan.
• Probeer de apparatuur niet te onderhouden alvorens deze onderhoudshandleiding werd
geraadpleegd en begrepen is.
• Indien deze waarschuwing niet wordt opgevolgd, zou het onderhoudspersoneel, de operator of
een patiënt gewond kunnen raken als gevolg van een elektrische schok, mechanische of andere
gevaren.
WARNING This service manual is available in English only.
(EN) • 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.
HOIATUS See teenindusjuhend on saadaval ainult inglise keeles.
(ET) • Kui klienditeeninduse osutaja nõuab juhendit inglise keelest erinevas keeles, vastutab klient
tõlketeenuse osutamise eest.
• Ärge üritage seadmeid teenindada enne eelnevalt käesoleva teenindusjuhendiga tutvumist ja
sellest aru saamist.
• Käesoleva hoiatuse eiramine võib põhjustada teenuseosutaja, operaatori või patsiendi
vigastamist elektrilöögi, mehaanilise või muu ohu tagajärjel.
VAROITUS Tämä huolto-ohje on saatavilla vain englanniksi.

ii AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 (FI) • Jos asiakkaan huoltohenkilöstö vaatii muuta kuin englanninkielistä materiaalia, tarvittavan
käännöksen hankkiminen on asiakkaan vastuulla.
• Älä yritä korjata laitteistoa ennen kuin olet varmasti lukenut ja ymmärtänyt tämän huolto-
ohjeen.
• Mikäli tätä varoitusta ei noudateta, seurauksena voi olla huoltohenkilöstön, laitteiston
käyttäjän tai potilaan vahingoittuminen sähköiskun, mekaanisen vian tai muun vaaratilanteen
vuoksi.
ATTENTION Ce manuel d'installation et de maintenance est disponible uniquement en anglais.
(FR) • Si le technicien d'un client a besoin de ce manuel dans une langue autre que l'anglais, il
incombe au client de le faire traduire.
• Ne pas tenter d'intervenir sur les équipements tant que ce manuel d'installation et de
maintenance 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 Diese Serviceanleitung existiert nur in englischer Sprache.
(DE) • Falls ein fremder Kundendienst eine andere Sprache benötigt, ist es Aufgabe des Kunden für
eine entsprechende Übersetzung zu sorgen.
• Versuchen Sie nicht diese Anlage zu warten, ohne diese Serviceanleitung gelesen und
verstanden zu haben.
• Wird diese Warnung nicht beachtet, so kann es zu Verletzungen des Kundendiensttechnikers,
des Bedieners oder des Patienten durch Stromschläge, mechanische oder sonstige Gefahren
kommen.
ΠΡΟΕΙΔΟΠΟΙ Τοπαρόν εγχειρίδιο σέρβις διατίθεται στα αγγλικά μόνο.
ΗΣΗ • Εάν το άτομο παροχής σέρβις ενός πελάτη απαιτεί το παρόν εγχειρίδιο σε γλώσσα εκτός
(EL) των αγγλικών, αποτελεί ευθύνη του πελάτη να παρέχει υπηρεσίες μετάφρασης.
• Μηνεπιχειρήσετε την εκτέλεση εργασιών σέρβις στον εξοπλισμό εκτός εάν έχετε
συμβουλευτεί και έχετε κατανοήσει το παρόν εγχειρίδιο σέρβις.
• Εάν δεν λάβετε υπόψη την προειδοποίηση αυτή, ενδέχεται να προκληθεί τραυματισμός στο
άτομο παροχής σέρβις, στο χειριστή ή στον ασθενή από ηλεκτροπληξία, μηχανικούς ή
άλλους κινδύνους.
FIGYELMEZTE Ezen karbantartási kézikönyv kizárólag angol nyelven érhető el.
TÉS • Ha a vevő szolgáltatója angoltól eltérő nyelvre tart igényt, akkor a vevő felelőssége a fordítás
(HU) elkészíttetése.
• Ne próbálja elkezdeni használni a berendezést, amíg a karbantartási kézikönyvben leírtakat
nem értelmezték.
• Ezen figyelmeztetés figyelmen kívül hagyása a szolgáltató, működtető vagy a beteg áramütés,
mechanikai vagy egyéb veszélyhelyzet miatti sérülését eredményezheti.
AÐVÖRUN Þessi þjónustuhandbók er aðeins fáanleg á ensku.
(IS) • Ef að þjónustuveitandi viðskiptamanns þarfnast annas tungumáls en ensku, er það skylda
viðskiptamanns að skaffa tungumálaþjónustu.
• Reynið ekki að afgreiða tækið nema að þessi þjónustuhandbók hefur verið skoðuð og skilin.
• Brot á sinna þessari aðvörun getur leitt til meiðsla á þjónustuveitanda, stjórnanda eða sjúklings
frá raflosti, vélrænu eða öðrum áhættum.
AVVERTENZA Il presente manuale di manutenzione è disponibile soltanto in lingua inglese.
(IT) • Se un addetto alla manutenzione richiede il manuale in una lingua diversa, il cliente è tenuto a
provvedere direttamente alla traduzione.
• Procedere alla manutenzione dell'apparecchiatura solo dopo aver consultato il presente
manuale ed averne compreso il contenuto.
• Il mancato rispetto della presente avvertenza potrebbe causare lesioni all'addetto alla
manutenzione, all'operatore o ai pazienti provocate da scosse elettriche, urti meccanici o altri
rischi.
警告 このサービスマニュアルには英語版しかありません。
(JA) • サービスを担当される業者が英語以外の言語を要求される場合、翻訳作業はその業者
の責任で行うものとさせていただきます。

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server iii

 • このサービスマニュアルを熟読し理解せずに、装置のサービスを行わないでくださ
い。
• この警告に従わない場合、サービスを担当される方、操作員あるいは患者 さんが、感
電や機械的又はその他の危険により負傷する可能性があります。
경고 본 서비스 매뉴얼은 영어로만 이용하실 수 있습니다.
(KO) • 고객의 서비스 제공자가 영어 이외의 언어를 요구할 경우, 번역 서비스를 제공하는 것은 고
객의 책임입니다.
• 본 서비스 매뉴얼을 참조하여 숙지하지 않은 이상 해당 장비를 수리하려고 시도하지 마십
시오.
• 본 경고 사항에 유의하지 않으면 전기 쇼크, 기계적 위험, 또는 기타 위험으로 인해 서비스
제공자, 사용자 또는 환자에게 부상을 입힐 수 있습니다.
BRĪDINĀJUM Šī apkopes rokasgrāmata ir pieejama tikai angļu valodā.
S • Ja klienta apkopes sniedzējam nepieciešama informācija citā valodā, klienta pienākums ir
(LV) nodrošināt tulkojumu.
• Neveiciet aprīkojuma apkopi bez apkopes rokasgrāmatas izlasīšanas un saprašanas.
• Šī brīdinājuma neievērošanas rezultātā var rasties elektriskās strāvas trieciena, mehānisku vai
citu faktoru izraisītu traumu risks apkopes sniedzējam, operatoram vai pacientam.
ĮSPĖJIMAS Šis eksploatavimo vadovas yra tik anglų kalba.
(LT) • Jei kliento paslaugų tiekėjas reikalauja vadovo kita kalba – ne anglų, suteikti vertimo paslaugas
privalo klientas.
• Nemėginkite atlikti įrangos techninės priežiūros, jei neperskaitėte ar nesupratote šio
eksploatavimo vadovo.
• Jei nepaisysite šio įspėjimo, galimi paslaugų tiekėjo, operatoriaus ar paciento sužalojimai dėl
elektros šoko, mechaninių ar kitų pavojų.
ADVARSEL Denne servicehåndboken finnes bare på engelsk.
(NO) • Hvis kundens serviceleverandør har bruk for et annet språk, er det kundens ansvar å sørge for
oversettelse.
• Ikke forsøk å reparere utstyret uten at denne servicehåndboken er lest og forstått.
• Manglende hensyn til denne advarselen kan føre til at serviceleverandøren, operatøren eller
pasienten skades på grunn av elektrisk støt, mekaniske eller andre farer.
OSTRZEŻENIE Niniejszy podręcznik serwisowy dostępny jest jedynie w języku angielskim.
(PL) • Jeśli serwisant klienta wymaga języka innego niż angielski, zapewnienie usługi tłumaczenia jest
obowiązkiem klienta.
• Nie próbować serwisować urządzenia bez zapoznania się z niniejszym podręcznikiem
serwisowym i zrozumienia go.
• Niezastosowanie się do tego ostrzeżenia może doprowadzić do obrażeń serwisanta, operatora
lub pacjenta w wyniku porażenia prądem elektrycznym, zagrożenia mechanicznego bądź
innego.
ATENÇÃO Este manual de assistência técnica encontra-se disponível unicamente em inglês.
(PT-BR) • Se outro serviço de assistência técnica solicitar a tradução deste manual, caberá ao 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.
• A não observância deste aviso pode ocasionar ferimentos no técnico, operador ou paciente
decorrentes de choques elétricos, mecânicos ou outros.
ATENÇÃO Este manual de assistência técnica só se encontra disponível em inglês.
(PT-PT) • Se qualquer outro serviço de assistência técnica solicitar este manual 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 colocar em perigo a segurança do técnico, do operador
ou do paciente devido a choques eléctricos, mecânicos ou outros.
ATENŢIE Acest manual de service este disponibil doar în limba engleză.

iv AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 (RO) • Dacă un furnizor de servicii pentru clienţi necesită o altă limbă decât cea engleză, este de
datoria clientului să furnizeze o traducere.
• Nu încercaţi să reparaţi echipamentul decât ulterior consultării şi înţelegerii acestui manual de
service.
• Ignorarea acestui avertisment ar putea duce la rănirea depanatorului, operatorului sau
pacientului în urma pericolelor de electrocutare, mecanice sau de altă natură.
ОСТОРОЖНО Данное руководство по техническому обслуживанию представлено только на английском
! языке.
(RU) • Если сервисному персоналу клиента необходимо руководство не на английском, а на
каком-то другом языке, клиенту следует самостоятельно обеспечить перевод.
• Перед техническим обслуживанием оборудования обязательно обратитесь к данному
руководству и поймите изложенные в нем сведения.
• Несоблюдение требований данного предупреждения может привести к тому, что
специалист по техобслуживанию, оператор или пациент получит удар электрическим
током, механическую травму или другое повреждение.
UPOZORENJE Ovo servisno uputstvo je dostupno samo na engleskom jeziku.
(SR) • Ako klijentov serviser zahteva neki drugi jezik, klijent je dužan da obezbedi prevodilačke usluge.
• Ne pokušavajte da opravite uređaj ako niste pročitali i razumeli ovo servisno uputstvo.
• Zanemarivanje ovog upozorenja može dovesti do povređivanja servisera, rukovaoca ili pacijenta
usled strujnog udara ili mehaničkih i drugih opasnosti.
UPOZORNENI Tento návod na obsluhu je k dispozícii len v angličtine.
E • Ak zákazníkov poskytovateľ služieb vyžaduje iný jazyk ako angličtinu, poskytnutie
(SK) prekladateľských služieb je zodpovednosťou zákazníka.
• Nepokúšajte sa o obsluhu zariadenia, kým si neprečítate návod na obluhu a neporozumiete mu.
• Zanedbanie tohto upozornenia môže spôsobiť zranenie poskytovateľa služieb, obsluhujúcej
osoby alebo pacienta elektrickým prúdom, mechanické alebo iné ohrozenie.
ATENCION Este manual de servicio sólo existe en inglés.
(ES) • Si el encargado de mantenimiento de un cliente necesita un idioma que no sea el inglés, el
cliente deberá encargarse de la traducción del manual.
• 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.
VARNING Den här servicehandboken finns bara tillgänglig på engelska.
(SV) • Om en kunds servicetekniker har behov av ett annat språk än engelska, ansvarar kunden för att
tillhandahålla översättningstjänster.
• Försök inte utföra service på utrustningen om du inte har läst och förstår den här
servicehandboken.
• Om du inte tar hänsyn till den här varningen kan det resultera i skador på serviceteknikern,
operatören eller patienten till följd av elektriska stötar, mekaniska faror eller andra faror.
OPOZORILO Ta servisni priročnik je na voljo samo v angleškem jeziku.
(SL) • Če ponudnik storitve stranke potrebuje priročnik v drugem jeziku, mora stranka zagotoviti
prevod.
• Ne poskušajte servisirati opreme, če tega priročnika niste v celoti prebrali in razumeli.
• Če tega opozorila ne upoštevate, se lahko zaradi električnega udara, mehanskih ali drugih
nevarnosti poškoduje ponudnik storitev, operater ali bolnik.
DİKKAT Bu servis kılavuzunun sadece ingilizcesi mevcuttur.
(TR) • Eğer müşteri teknisyeni bu kılavuzu ingilizce dışında bir başka lisandan talep ederse, bunu
tercüme ettirmek müşteriye düşer.
• Servis kılavuzunu okuyup anlamadan ekipmanlara müdahale etmeyiniz.
• Bu uyarıya uyulmaması, elektrik, mekanik veya diğer tehlikelerden dolayı teknisyen, operatör
veya hastanın yaralanmasına yol açabilir.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server v

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.
The following process is for North America only (US + Can)
Note damage on the carrier’s delivery paperwork
Take pictures of damage
For Equipment damage: Follow Process & Complete Damage / Loss Claim Form
Timing: No more than 7 days after delivery
For Property damage: Complete Delivery Incident Form
Timing: No more than2 days after delivery
Email with supporting pictures and all paperwork to @HEALTH Claims-Traffic (Claims-
[email protected]) or Fax to 262.312.1183 Att: Claims.
Delivery issues: Complete Delivery Incident Form
Timing: No more than 2 days after delivery

Omissions & Errors

Customers, please contact your GE Sales or Service representatives.
GE personnel, please use the GEHC TrackWise Process to report all omissions, errors, and defects in
this publication.

Electrical Contractors
Certified Electrical Contractor Statement
All electrical installations that are preliminary to positioning of the equipment at the site prepared
for the equipment shall be performed by licensed electrical contractors. In addition, electrical feeds
into the Power Distribution Unit shall be performed by licensed electrical contractors.
Other connections between pieces of electrical equipment, calibrations, and testing shall be
performed by qualified GE Medical personnel. The products involved (and the accompanying
electrical installations) are highly sophisticated, and special engineering competence is required. In
performing all electrical work on these products, GE will use its own specially trained field engineers.
All of GE’s electrical work on these products will comply with the requirements of the applicable
electrical codes.
The purchaser of GE equipment shall only utilize qualified personnel (i.e., GE’s field engineers,
personnel of third–party service companies with equivalent training, or licensed electricians) to
perform electrical servicing on the equipment.

vi AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

WEEE Directive

This logo applied on GEHC hardware marks it as WEEE compliant according to the EU WEEE
directive
(2012/19/EU).
This information (product disassembly instructions) is posted on the Hewlett Packard web site at:
http://www.hp.com/hpinfo/globalcitizenship/environment/productdata/disassemblyservers.html
These instructions may be used by recyclers and other WEEE treatment facilities as well as HP OEM
customers who integrate and re-sell HP equipment

Revision History
Engineering revisions and master for this document are archived in the MyWorkshop system as
DOC1723464.
Release of this document is referenced and archived in TechPub as 5719443-1EN.

Revision Version TechPub Revision Date Reason for change

1 1 N/A November 27, Initial DRAFT release
2016
1 2 5719443-1EN Rev1 October 15, 2015 Initial release after Hii review DOC1744932 rev1
2 1 5719443-1EN Rev2 June 8, 2016 Update for AW Server 3.2 Ext.1.0 release: SPR
HCSDM00394148
3 1 5719443-1EN Rev3 October 21, 2016 Update for AW Server 3.2 Ext.1.2 release: SPR
HCSDM00427232
4 1 5719443-1EN Rev4 July 25, 2017 Update for AW Server 3.2 Ext.2.0 and HP DL360
Gen9 introduction, and document renaming:
SPR HCSDM00454616
5 1 5719443-1EN Rev5 May 24, 2018 Update for AW Server 3.2 Ext.3.0 release
introduction: SPR HCSDM00495264
Change Manufacturing Site address: SPR
HCSDM00495317
Fix wrong installer path for Window Client: SPR
HCSDM00492964
Guest OS shall support SSE 4.1 instructions: SPR
HCSDM00488063
6 1 5719443-1EN Rev6 February 6, 2019 Update for AW Server 3.2 Ext.3.2 release
introduction: SPR HCSDM00529630
Add NanoCloud description: SPR
HCSDM00531905
7 1 5719443-1EN Rev7 March 9, 2020 Silent client install method is not correctly
documented: SPR HCSDM00566761
Update for AW Server 3.2 Ext.3.4 release
introduction: SPR HCSDM00591860

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server vii

 Revision Version TechPub Revision Date Reason for change
Recommand to restart AWS after Preprocessing
configuration: SPR HCSDM00586364
7 2 5719443-1EN Rev7 March 19, 2020 Update commands to create and deploy the VM
for AWS integrated in Console: SPR
HCSDM00601087
8 1 5719443-1EN Rev8 August 4, 2020 Update for HPE ProLiant DL360 Gen10 Server
introduction: SPR HCSDM00608746
Update procedures to create and deploy the VM
for AWS integrated in Console: SPR
HCSDM00608178
Update enterprise user accounts procedure due
to LDAP authentication issue with SSL: SPR
HCSDM00611066
Network performance degradation when
switching off and on the PNF (firewall): SPR
HCSDM00618092
Update commands for VM creation and
deployment on CT Nano-Cloud with MEP USB:
SPR HCSDM00601992

viii AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

Contents
Chapter 1 Getting Started......................................................................................................... 1
1.1 Conventions...................................................................................................................................................................1
1.1.1 Intent of Information ....................................................................................................................................1
1.1.2 Safety Terminology........................................................................................................................................1
1.1.3 Data Entry Formatting Conventions......................................................................................................2
1.1.4 Use of numbered lists in this document ..............................................................................................2
1.1.5 Use of bulleted lists in this document...................................................................................................2
1.1.6 Information Disclaimer ................................................................................................................................2
1.1.7 Contents of this document ........................................................................................................................2
1.2 Access to Documentation and Service links ...................................................................................................3
1.2.1 Documentation ...............................................................................................................................................3
1.2.1.1 Access the AW Server 3.2 Service Documentation............................................................3
1.2.1.2 Navigating back and forth though cross-reference links in PDF files .........................3
1.2.2 Service Web links ...........................................................................................................................................4
1.3 Software Kit...................................................................................................................................................................4
1.4 Identification of Software releases .....................................................................................................................6
1.5 LOTO Warning...............................................................................................................................................................6

Chapter 2 Installation of a new AW Server ............................................................................. 7

2.1 Overview .........................................................................................................................................................................7
2.2 AW Server - Product Description .........................................................................................................................7
2.2.1 GEHC delivered AW Server hardware ...................................................................................................7
2.2.1.1 The low-tier rack-mount version ................................................................................................7
2.2.1.2 The high-tier rack-mount version...............................................................................................7
2.2.2 Virtual AW server ...........................................................................................................................................8
2.2.3 The AW Server – system components..................................................................................................8
2.2.4 Software Changes..........................................................................................................................................8
2.2.5 Before you start ..............................................................................................................................................9
2.2.6 Software preload by Manufacturing ......................................................................................................9
2.2.6.1 GEHC delivered Physical servers ................................................................................................9
2.2.6.2 Virtual AW Servers on customer’s physical servers........................................................ 10
2.3 Quick Start Installation Guide - Physical System....................................................................................... 10
2.4 Quick Start Installation Guide - Virtual AW Server ................................................................................... 13
2.4.1 Virtual Machine characteristics per integration mode ............................................................... 14
2.4.2 Virtual AW Server Installation steps overview............................................................................... 15
2.4.3 Quick Start Installation Guide - Scalable Virtual servers........................................................... 18
2.5 Job Card IST001A - Hardware Installation Verification........................................................................... 22
2.5.1 Time Reporting for Installation and Warranty................................................................................ 22
2.5.2 Hardware Installation validation .......................................................................................................... 23
2.5.3 HPE ProLiant DL360 Gen10 Server High Tier and Low Tier ...................................................... 23
2.5.4 HPE ProLiant DL360 Gen9 Server High Tier and Low Tier......................................................... 28
2.6 Job Card IST001AB - Hypervisor Configuration.......................................................................................... 33
2.6.1 Overview ......................................................................................................................................................... 33
2.6.2 Ethernet ports Allocation ........................................................................................................................ 35
2.6.2.1 Foreword ............................................................................................................................................ 35

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server ix

 2.6.2.2 Procedure........................................................................................................................................... 35
2.6.3 Create a GEHC service user account .................................................................................................. 39
2.6.4 Setup a NTP server for the Hypervisor .............................................................................................. 43
2.7 Job Card IST001B - Virtual Machine creation .............................................................................................. 44
2.7.1 Overview ......................................................................................................................................................... 44
2.7.2 Virtual machine creation.......................................................................................................................... 46
2.7.2.1 OS Template (OVF) Installation ................................................................................................ 47
2.7.2.2 Steps to upgrade / downgrade a Virtual Machine............................................................ 51
2.7.2.3 Disconnect the second Network Adapter ........................................................................... 52
2.7.2.4 Image data disk creation for Standalone (Non-Integrated) virtual AW Server ...53
2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps............................................................. 56
2.8.1 Foreword ......................................................................................................................................................... 56
2.8.1.1 Pre-requisites for setup............................................................................................................... 56
2.8.1.2 Pre-requisites for Cluster operation ...................................................................................... 56
2.8.2 Preliminary Steps ........................................................................................................................................ 57
2.8.2.1 Virtual machine resources for AW Server ........................................................................... 57
2.8.2.2 Physical Network configuration ............................................................................................... 58
2.8.3 Installation and configuration Steps................................................................................................... 60
2.8.3.1 Hypervisor pre-requisites ........................................................................................................... 61
2.8.3.2 Ethernet ports allocation ............................................................................................................ 61
2.8.3.3 GE Service account setup ........................................................................................................... 61
2.8.3.4 NTP server setup for the Virtual AW Servers / HAPS servers..................................... 61
2.8.3.5 Virtual Machine (VM) creation .................................................................................................. 61
2.8.3.6 AW Server / HAPS server installation and configuration .............................................. 61
2.8.4 Scalability Installation Checklist........................................................................................................... 61
2.8.4.1 Under Site IT administrator responsibility .......................................................................... 61
2.8.4.2 Under GEHC FE responsibility................................................................................................... 62
2.9 Job Card IST002B - Virtual Machine Installation Verification............................................................... 63
2.9.1 Retrieve the MAC address ....................................................................................................................... 64
2.9.2 Virtual machine verification.................................................................................................................... 66
2.10 Job Card IST003 - Installation of Platform Software ............................................................................. 67
2.10.1 AWS Platform software load preparation...................................................................................... 67
2.10.1.1 Physical AW servers ................................................................................................................... 67
2.10.1.2 Virtual AW Server ........................................................................................................................ 67
2.10.2 AWS platform software load ............................................................................................................... 69
2.10.3 HAPS Server installation........................................................................................................................ 80
2.10.3.1 First HAPS server setup ............................................................................................................ 80
2.10.3.2 Second HAPS server setup ...................................................................................................... 81
2.11 Job Card IST004A - HPE R/T3000 UPS drivers setup ............................................................................ 82
2.11.1 HPE R/T3000 UPS drivers installation verification ..................................................................... 82
2.11.2 Configuring the HPE R/T3000 UPS using HPPP Software ....................................................... 82
2.12 Job Card IST004B - Installation of VMware Tools.................................................................................... 86
2.13 Job Card IST005 - Network and Time Configuration ............................................................................. 88
2.13.1 Network Configuration........................................................................................................................... 88
2.13.1.1 Important information about Hostname .......................................................................... 89
2.13.1.2 Network Configuration Procedure ....................................................................................... 89
2.13.2 Date and Time Configuration .............................................................................................................. 91
2.13.3 Reboot the AW Server ............................................................................................................................ 93
2.14 Job Card IST006 - Changing the Passwords .............................................................................................. 93
2.14.1 Process Overview ..................................................................................................................................... 94

x AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.14.2 Passwords Change Procedure ............................................................................................................ 94
2.14.2.1 Customer Consultation............................................................................................................. 95
2.14.2.2 Identify New Password(s) ........................................................................................................ 95
2.14.2.3 Change system (root / insite / sdc) passwords....................................................... 96
2.14.2.4 Test the new passwords (AW and AW Server) ............................................................... 96
2.14.2.5 Change AW Server Users Password(s)............................................................................... 97
2.14.2.6 Change the default iLO User name and Password........................................................ 98
2.14.3 Update Password(s) in Connectivity Database........................................................................ 100
2.14.4 Communicate New Password(s)..................................................................................................... 101
2.14.5 Perform a System Backup.................................................................................................................. 101
2.14.6 Password Form....................................................................................................................................... 102
2.15 Job Card IST007 - Service Tools Login....................................................................................................... 102
2.15.1 Service Tools Login................................................................................................................................ 102
2.15.2 HealthPage Examples.......................................................................................................................... 104
2.15.2.1 HealthPage Status example- HP server ......................................................................... 104
2.15.2.2 HealthPage "Status" example- Virtual server .............................................................. 104
2.15.2.3 HealthPage "System Configuration" example.............................................................. 105
2.15.2.4 HealthPage "Version Information" example ................................................................. 106
2.15.2.5 HealthPage "Configuration & Status" display............................................................... 106
2.15.2.6 HealthPage "Software Subsystem" example................................................................ 107
2.15.3 Service Tools Menus for installation / setup .............................................................................. 108
2.16 Job Card IST008 - Initial Configuration ..................................................................................................... 108
2.16.1 Configuration - Cluster case ............................................................................................................. 109
2.16.2 Remote Service....................................................................................................................................... 109
2.16.2.1 InSite Remote Service (GEHCS only) ................................................................................ 110
2.16.2.2 EDS Remote Service ................................................................................................................ 112
2.16.3 Device Data .............................................................................................................................................. 112
2.16.4 Contact Data............................................................................................................................................ 113
2.16.5 Service Tools Language (for Administrator)............................................................................... 114
2.16.6 Time Settings........................................................................................................................................... 114
2.16.6.1 Date and Time menu............................................................................................................... 114
2.16.6.2 Time Server menu..................................................................................................................... 115
2.16.7 Database Deletion Settings .............................................................................................................. 115
2.16.7.1 Auto Delete settings................................................................................................................ 116
2.16.7.2 Delete option for worklist browser................................................................................... 117
2.16.8 SNMP Configuration ............................................................................................................................. 117
2.16.9 Platform Configuration........................................................................................................................ 118
2.16.9.1 Licensing Preparation ............................................................................................................. 118
2.16.9.2 Configuration Steps Summary............................................................................................ 119
2.16.9.3 Platform configuration menu .............................................................................................. 120
2.16.9.4 Scalability setup menu ........................................................................................................... 121
2.16.9.5 Integration configuration menu.......................................................................................... 122
2.16.10 Licensing Configuration.................................................................................................................... 123
2.16.10.1 Preprocessing configuration menu................................................................................. 123
2.16.10.2 MailSender ................................................................................................................................ 123
2.16.10.3 CoLA License server.............................................................................................................. 124
2.16.10.4 Floating License configuration menu ............................................................................ 128
2.16.11 Scalability- Clustered Servers........................................................................................................ 128
2.16.12 Audit Trail (EAT).................................................................................................................................... 128
2.16.13 Prodiag configuration ........................................................................................................................ 130
2.16.14 GIB Data .................................................................................................................................................. 131
2.17 Job Card IST009 - External Application(s) Installation....................................................................... 132

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server xi

 2.17.1 Foreword ................................................................................................................................................... 132
2.17.1.1 Applications delivery and installation management changes.............................. 132
2.17.1.2 Product Hold warning notice example ............................................................................ 133
2.17.1.3 Information about registration of installed configuration ...................................... 134
2.17.1.4 Applications Software package content......................................................................... 134
2.17.2 License Server(s) installation ........................................................................................................... 134
2.17.3 Application(s) Licensing setup ......................................................................................................... 134
2.17.4 Enter the Maintenance mode........................................................................................................... 136
2.17.5 Load the Application(s) from media .............................................................................................. 137
2.17.5.1 Using the Physical (hardware) server’s DVD drive...................................................... 138
2.17.5.2 iLO media drive mapping - Remote installation on Physical Hardware Server.....
.................................................................................................................................................................... 139
2.17.5.3 Virtual server and physical Hardware server remote installation case............ 139
2.17.5.4 Loading/installing Advanced Applications from USB device - eDelivery .......... 143
2.17.6 Install the Application(s)..................................................................................................................... 143
2.17.7 Activate the Application(s) ................................................................................................................ 146
2.17.8 Applications Profile ............................................................................................................................... 147
2.17.8.1 Volume Viewer applications ................................................................................................ 147
2.17.8.2 Other Applications supported............................................................................................. 147
2.18 Job Card IST010 - Administrative Configuration .................................................................................. 148
2.18.1 DICOM Hosts Configuration.............................................................................................................. 149
2.18.2 Configuring DICOM Printers and Filmers .................................................................................... 151
2.18.3 Configuring PostScript Printers....................................................................................................... 153
2.18.4 Users (EA3) (User account configuration) ................................................................................... 154
2.18.4.1 Local User(s) Account Configuration................................................................................ 155
2.18.4.2 Configuring Enterprise User(s) Accounts ....................................................................... 157
2.18.4.3 Assigning User Roles ............................................................................................................... 159
2.18.5 Smart Card configuration................................................................................................................... 160
2.18.6 Client Timeout......................................................................................................................................... 164
2.18.7 Preprocessing Configuration ............................................................................................................ 165
2.18.8 MailSender Settings.............................................................................................................................. 167
2.18.8.1 Configure the contact/recipient ......................................................................................... 169
2.18.9 End of Review .......................................................................................................................................... 170
2.18.10 AW Server declaration on DICOM images sources .............................................................. 171
2.18.11 Administrative Utilities..................................................................................................................... 172
2.19 Job Card IST011 - Integration ....................................................................................................................... 172
2.19.1 Foreword ................................................................................................................................................... 172
2.19.1.1 Integration modes supported with AW Server............................................................ 172
2.19.1.2 Pre-requisite for Integration ................................................................................................ 174
2.19.2 Full front end integration (Hybrid): (3rdPartyIntegration) ................................................... 175
2.19.2.1 Configuration steps on the AW Server............................................................................ 175
2.19.2.2 Configuration steps on the Universal Viewer............................................................... 177
2.19.2.3 Configuration steps on the Client PC............................................................................... 179
2.19.3 Seamless Integration ........................................................................................................................... 179
2.19.3.1 Pre-requisites summary ........................................................................................................ 179
2.19.3.2 Seamless integration - configuration steps on Universal Viewer Server......... 180
2.19.3.3 Seamless integration - configuration steps on AWS................................................. 183
2.19.3.4 Seamless integration - configuration steps on AWS, Service Tools ................... 184
2.19.3.5 Seamless integration - configuration steps on Universal Viewer Client PC ... 188
2.19.3.6 Seamless integration - configuration steps on Image Sources ............................ 188
2.19.3.7 Seamless Integration - configuration checklist ........................................................... 188
2.19.4 DICOM Direct Connect integration ................................................................................................ 190

xii AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19.4.1 Pre-requisites ............................................................................................................................. 190
2.19.4.2 Configuration steps on AWS................................................................................................ 191
2.19.4.3 Configuration steps on AWS, Service Tools................................................................... 192
2.19.4.4 Configuration steps on the PACS/VNA/DICOM Remote Host ............................... 194
2.19.4.5 Configuration steps on the Client PC............................................................................... 195
2.20 Job Card IST012 - Virtual Servers Cluster Configuration.................................................................. 196
2.20.1 Foreword ................................................................................................................................................... 196
2.20.2 Scalability setup procedure............................................................................................................... 196
2.20.2.1 NTP server availability checks............................................................................................. 196
2.20.2.2 Scalability setup ........................................................................................................................ 196
2.21 Job Card IST013 - Service Tools Configuration...................................................................................... 200
2.21.1 System Configuration Registration................................................................................................ 200
2.21.1.1 Configuration registration steps ........................................................................................ 200
2.21.1.2 Process in case of issue at Registration time ............................................................... 203
2.22 Job Card IST014A - Standard Client PC installation & Tests ........................................................... 204
2.22.1 Client Installation Procedure ............................................................................................................ 205
2.22.1.1 Windows TM Client PC installation Procedure ............................................................ 205
2.22.1.2 Linux Client installation Procedure................................................................................... 209
2.22.2 Server and Client Installation Validation Tests......................................................................... 211
2.22.2.1 HealthPage Test ........................................................................................................................ 211
2.22.2.2 Server Diagnostic Test............................................................................................................ 215
2.22.3 Client (System) Test.............................................................................................................................. 216
2.22.3.1 Client Checker Tool .................................................................................................................. 218
2.22.3.2 Network Test (summary and client information) ....................................................... 221
2.22.3.3 Validation Test Failure – What to do ................................................................................ 223
2.22.3.4 Printing tests............................................................................................................................... 224
2.22.3.5 Client Monitor screen resolution setup .......................................................................... 225
2.22.3.6 AWS Client configuration for CPACS integration ........................................................ 225
2.22.3.7 AWS Client configuration for upgrade from AW Server 2.0 ................................... 226
2.23 Job Card IST014B - Seamless Client PC installation and Tests...................................................... 226
2.23.1 Client Installation Procedure ............................................................................................................ 226
2.23.1.1 Pre-requisites - Universal Viewer Client installation ................................................ 226
2.23.1.2 AW Server Client Installation Procedure........................................................................ 226
2.23.1.3 Linux Client installation Procedure................................................................................... 229
2.23.2 Server and Client Installation Validation Tests......................................................................... 230
2.23.2.1 HealthPage Test ........................................................................................................................ 230
2.23.2.2 Server Diagnostic Test............................................................................................................ 234
2.23.3 Client (System) Test.............................................................................................................................. 235
2.23.3.1 Client Checker Tool .................................................................................................................. 235
2.23.3.2 Client Test (summary and client information) ............................................................. 238
2.23.3.3 Validation Test Failure – What to do ................................................................................ 238
2.23.3.4 Printing tests............................................................................................................................... 239
2.23.3.5 Client Monitor screen resolution setup .......................................................................... 239
2.24 Job Card IST015 - Final Settings .................................................................................................................. 240
2.24.1 SNMP setup in iLO Service processor........................................................................................... 240
2.24.1.1 Pre-requisite for using with Prodiag................................................................................. 240
2.24.1.2 SNMP setup in the iLO 5 service processor................................................................... 240
2.24.1.3 Service Workflow ...................................................................................................................... 242
2.24.2 Anti-Virus setup...................................................................................................................................... 242
2.24.3 Scalability (cluster) mode operation verification..................................................................... 242
2.24.4 Hard disks serial numbers ................................................................................................................. 243
2.24.4.1 At installation time................................................................................................................... 243

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server xiii

 2.24.4.2 After hard disk drive replacement..................................................................................... 243
2.24.5 PNF Firewall setting.............................................................................................................................. 243
2.24.6 Media Creator.......................................................................................................................................... 244
2.24.7 Volume Viewer performances on VM ........................................................................................... 244
2.24.8 For China only - CFDA Registration documents....................................................................... 245
2.24.8.1 Installation on server .............................................................................................................. 245
2.24.8.2 Upgrade......................................................................................................................................... 246
2.25 Job Card IST016 - System Handover to Customer .............................................................................. 246
2.25.1 Installation handover tasks - Handover Checklist .................................................................. 246
2.25.2 Backup Parameters and Settings ................................................................................................... 249
2.25.2.1 Network and UPS configuration Backup ........................................................................ 249
2.25.2.2 Configuration Backup.............................................................................................................. 251
2.25.3 Final steps................................................................................................................................................. 253
2.25.3.1 AW Server User and IT Administration Training.......................................................... 253
2.25.3.2 GIB / SIEBEL update and paperwork................................................................................. 253
2.25.3.3 Register High Tier Server with Genpact.......................................................................... 254
2.25.3.4 Capture the UDI number in Service Records ................................................................ 254
2.25.3.5 Print the AWS Configuration................................................................................................ 255
2.25.3.6 Customer Release Note and information ...................................................................... 256
2.25.3.7 HP Care Pack Warranty extension .................................................................................... 256
2.25.3.8 PSI code verification ................................................................................................................ 256
2.25.3.9 Site Cleanup ................................................................................................................................ 256

Chapter 3 Upgrade ................................................................................................................ 257

3.1 Foreword ................................................................................................................................................................... 257
3.2 Quick Start Installation Guide - Hardware Upgrade .............................................................................. 258
3.3 Quick Start Installation Guide - Software Upgrade................................................................................ 259
3.4 Scalability Upgrade............................................................................................................................................... 262
3.4.1 Adding an AW Server to an existing AW Servers Cluster ....................................................... 262
3.4.2 Removing an AW Server from an AW Servers Cluster............................................................. 263
3.4.3 Upgrading an AW Server 3.0 Cluster to AW Server 3.2 release ........................................... 263
3.4.4 Software Upgrade within an AW Servers Cluster ...................................................................... 264
3.5 Hardware Upgrade................................................................................................................................................ 264
3.6 Applications Upgrade .......................................................................................................................................... 264
3.7 System Configuration Restore Matrix .......................................................................................................... 266
3.8 Job Card UPG001 - Software Upgrade ........................................................................................................ 269
3.8.1 Upgrade Preparation - One week before the upgrade............................................................. 270
3.8.1.1 Upgrade preparation - Perform Filesystem check ........................................................ 270
3.8.1.2 Upgrade preparation - Contact the IT Admin of the site............................................ 271
3.8.1.3 Floating License Server............................................................................................................. 272
3.8.1.4 Software Changes....................................................................................................................... 272
3.8.1.5 Patients Image data backup ................................................................................................... 272
3.8.2 Verify that AW Server is operational ............................................................................................... 272
3.8.2.1 Check the hardware indicator LEDs (hardware server only).................................... 272
3.8.2.2 Check the iLO Service processor (hardware server only) .......................................... 273
3.8.2.3 Connect to the AW server ....................................................................................................... 273
3.8.2.4 Important information about Hostnames........................................................................ 274
3.8.3 Backup the configuration...................................................................................................................... 274
3.8.3.1 Backup the Network configuration...................................................................................... 275
3.8.3.2 Backup the UPS configuration ............................................................................................... 276

xiv AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8.3.3 Backup the Site configuration................................................................................................ 277
3.8.3.4 Backup the PACS Integration configuration..................................................................... 280
3.8.3.5 Backup the existing exams status configuration........................................................... 281
3.8.3.6 Backup the End of Review configuration........................................................................... 281
3.8.4 HP ProLiant ML350 G6 Server Hardware Upgrade.................................................................... 281
3.8.4.1 Upgrade memory to 24GB (or 64GB) .................................................................................. 282
3.8.4.2 BIOS Hyperthreading setup to OFF ..................................................................................... 282
3.8.5 Software upgrade..................................................................................................................................... 282
3.8.5.1 OS loading...................................................................................................................................... 283
3.8.5.2 AWS Platform software loading............................................................................................ 290
3.8.5.3 Loading the HPE R/T3000 UPS drivers and restoring the configuration (if
applicable) ............................................................................................................................................. 290
3.8.5.4 Reinstall the VMware Tools..................................................................................................... 291
3.8.6 Reload and reinstall the Advanced Applications........................................................................ 291
3.8.6.1 Information about Volume Viewer Applications ........................................................... 292
3.8.6.2 Information about other Applications................................................................................ 292
3.8.6.3 Applications re-installation process ................................................................................... 292
3.8.7 Restore the Server configuration and licenses............................................................................ 292
3.8.7.1 Preliminary steps before restoration.................................................................................. 292
3.8.7.2 Restoration steps ........................................................................................................................ 293
3.8.7.3 Licenses restoration................................................................................................................... 296
3.8.7.4 CardIQ Xpress Process (CXP) application reinstallation............................................. 296
3.8.7.5 Internal Applications restoration ......................................................................................... 297
3.8.7.6 Passwords restoration .............................................................................................................. 297
3.8.8 InSite connectivity re-installation..................................................................................................... 297
3.8.9 Integration restoration........................................................................................................................... 297
3.8.10 Scalability restoration.......................................................................................................................... 298
3.8.11 Register System configuration......................................................................................................... 298
3.8.12 Upgrade AW Clients after AW Server Upgrade ........................................................................ 298
3.8.13 Final tests and system handover to customer ......................................................................... 298
3.8.13.1 Final settings and System handover to customer...................................................... 298
3.8.13.2 GIB / SIEBEL update and paperwork................................................................................. 299
3.8.13.3 Secure Media Destruction procedure .............................................................................. 299
3.9 Job Card UPG002 - Scalability Upgrade ...................................................................................................... 300
3.9.1 Adding an AW Server to an existing AW Servers Cluster ....................................................... 300
3.9.2 Removing an AW Server from an AW Servers Cluster............................................................. 301
3.9.3 Software Upgrade within a Cluster .................................................................................................. 302
3.9.3.1 Pre-requisite for AW Server 3.0 upgrade case................................................................ 302
3.9.3.2 AW Server 3.0 High Level Upgrade Procedure................................................................ 303
3.9.3.3 AW Server 3.2 High Level Upgrade Procedure................................................................ 307
3.10 Job Card UPG003 - Hardware Upgrade .................................................................................................... 309
3.10.1 Foreword ................................................................................................................................................... 309
3.10.2 Old hardware checks............................................................................................................................ 310
3.10.3 Old hardware configuration backup .............................................................................................. 310
3.10.4 New hardware installation - High level steps............................................................................ 310
3.10.5 System Configuration restoration.................................................................................................. 311
3.10.6 Patient data transfer............................................................................................................................ 311
3.10.6.1 Check with customer what images can be deleted and proceed to deletion 312
3.10.6.2 De-activation of Auto-delete on the old AW Server ................................................. 312
3.10.6.3 Change the IP address of the older AW server ............................................................ 312
3.10.6.4 Prepare the old AW Server for image transfer............................................................. 314
3.10.6.5 Image transfer from old to new AW Server................................................................... 314

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server xv

 3.10.6.6 Check installation of images on the new AW Server ................................................ 316
3.10.6.7 Final steps on the new AW Server .................................................................................... 316
3.10.6.8 Final steps on the old AW Server - Delete Patient data .......................................... 317
3.10.7 Old hardware return procedure ...................................................................................................... 319

Chapter 4 Service Tasks........................................................................................................ 321

4.1 Overview ................................................................................................................................................................... 321
4.2 Job Card SV001 - Preventive Maintenance (PM)..................................................................................... 321
4.2.1 Recommended PM Schedule............................................................................................................... 321
4.2.2 PM Access.................................................................................................................................................... 322
4.2.3 PM Time ........................................................................................................................................................ 322
4.2.4 PM Tasks....................................................................................................................................................... 322
4.2.4.1 PM Software Tasks...................................................................................................................... 322
4.2.4.2 PM Hardware Tasks .................................................................................................................... 324
4.2.5 PM Completion.......................................................................................................................................... 326
4.2.6 Preventive Maintenance tasks summary ...................................................................................... 326
4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list .......................................................................... 327
4.3.1 AW Server 3.2 Software FRU’s............................................................................................................ 328
4.3.2 Volume Viewer Applications Software FRU’s............................................................................... 329
4.3.3 Other Application Software FRU’s .................................................................................................... 329
4.3.4 HPE ProLiant DL360 Gen10 Server High Tier – Hardware FRU's......................................... 330
4.3.5 HPE ProLiant DL360 Gen9 Server High Tier – Hardware FRU’s............................................ 330
4.3.6 HPE ProLiant DL560 Gen8 Server High Tier – Hardware FRU’s............................................ 330
4.3.7 HPE ProLiant DL580 G7 Server High Tier – Hardware FRU’s................................................. 331
4.3.8 HPE ProLiant DL360 Gen10 Server Low Tier – Hardware FRU’s.......................................... 331
4.3.9 HPE ProLiant DL360 Gen9 Server Low Tier – Hardware FRU’s ............................................ 331
4.3.10 HPE ProLiant ML350p Gen8 Server Low Tier – Hardware FRU’s ...................................... 331
4.3.11 HP ProLiant ML350 G6 Server Low Tier – Hardware FRU’s ................................................. 332
4.4 Job Card SV003 - Service Procedures .......................................................................................................... 333
4.4.1 Break-Fix Processes ................................................................................................................................ 334
4.4.1.1 Roles.................................................................................................................................................. 334
4.4.1.2 Hardware Vendor Service Support Model ........................................................................ 334
4.4.1.3 Service Support Procedures ................................................................................................... 335
4.4.1.4 HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8 Server Hardware -
Break-Fix Process............................................................................................................................... 335
4.4.1.5 HP ProLiant ML350 G6 Server / HPE ProLiant ML350p Gen8 Server Hardware -
Break-Fix Process............................................................................................................................... 336
4.4.2 HPE ProLiant DL360 Gen10 Server and HPE ProLiant DL360 Gen9 Server Hardware
Disassembly/Reassembly Procedures ............................................................................................... 337
4.4.2.1 Electrical Precautions for HPE ProLiant DL360 Gen10 Server and HPE ProLiant
DL360 Gen9 Server ........................................................................................................................... 337
4.4.2.2 De-racking the HPE ProLiant DL360 Gen10 Server and the HPE ProLiant DL360
Gen9 Server.......................................................................................................................................... 338
4.4.2.3 Replacing HPE ProLiant DL360 Gen9 Server Low Tier Components .................... 338
4.4.2.4 Re-configuring the network after a network card replacement............................. 338
4.4.3 HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8 Server Hardware
Disassembly/Reassembly Procedures ............................................................................................... 339
4.4.3.1 Electrical Precautions of the HPE ProLiant DL580 G7 Server / HPE ProLiant
DL560 Gen8 Server ........................................................................................................................... 339
4.4.3.2 De-racking the HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8
Server ...................................................................................................................................................... 340

xvi AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4.3.3 Replacing HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8 Server
components.......................................................................................................................................... 340
4.4.3.4 Re-configuring the network after a network card replacement............................. 340
4.4.4 HP ProLiant ML350 G6 Server / HPE ProLiant ML350p Gen8 Server Disassembly/
Reassembly Procedures ........................................................................................................................... 341
4.4.4.1 LOTO Procedure for HP ProLiant ML350 G6 Server / HPE ProLiant ML350p Gen8
Server ...................................................................................................................................................... 341
4.4.4.2 Replacing the "hot-plug" power supplies.......................................................................... 343
4.4.4.3 Replacing the "hot-plug" hard disk(s).................................................................................. 343
4.4.4.4 Powering down the server ...................................................................................................... 344
4.4.4.5 Opening the side cover ............................................................................................................. 344
4.4.4.6 Replacing the DVD drive........................................................................................................... 344
4.4.4.7 Replacing the air flow baffles.................................................................................................. 344
4.4.4.8 Replacing a cooling fan.............................................................................................................. 344
4.4.4.9 Replacing the DIMM memory modules.............................................................................. 344
4.4.4.10 Replacing the RAID Flash Backed Write Cache module(s) ..................................... 345
4.4.4.11 Replacing the Real time clock lithium coin battery ................................................... 345
4.4.4.12 Swapping the HP ProLiant ML350 G6 Server CPU box............................................. 346
4.4.5 HP Escalation and Communication Flow....................................................................................... 348
4.4.5.1 HP Support Center Web site .................................................................................................. 348
4.4.5.2 HP supported countries telephone list.............................................................................. 350
4.4.6 Hardware Vendor Information Links................................................................................................ 356
4.4.6.1 HP Hardware Vendor Information Links............................................................................ 356
4.4.6.2 Note about the HP Serial number........................................................................................ 356
4.5 Job Card SV004 - Renewal of Digital Certificate ..................................................................................... 357
4.5.1 Purpose of this procedure .................................................................................................................... 357
4.5.1.1 How to determine if an AW Server needs certificate renewal ................................ 357
4.5.1.2 Instructions to renew AW Server digital certificate..................................................... 358

Appendix A Appendices ........................................................................................................ 361

A.1 Overview................................................................................................................................................................... 361
A.2 Specific field - Characters rules and limitations...................................................................................... 361
A.3 eLicensing ................................................................................................................................................................ 362
A.3.1 Foreword...................................................................................................................................................... 362
A.3.2 eLicense operation.................................................................................................................................. 363
A.4 Maintenance Mode .............................................................................................................................................. 369
A.4.1 Entering the Maintenance mode ...................................................................................................... 369
A.4.2 Exiting the Maintenance mode.......................................................................................................... 371
A.5 Using the ClamAV Anti-Virus Tool ................................................................................................................. 373
A.5.1 Overview...................................................................................................................................................... 373
A.5.2 ClamAV tool activation procedure ................................................................................................... 374
A.5.2.1 Activation Procedure................................................................................................................. 374
A.5.2.2 Checking ClamAV Scan Results ............................................................................................ 377
A.5.2.3 Further Information ................................................................................................................... 378
A.6 VMware Support .................................................................................................................................................. 378
A.6.1 VMware Hypervisor Installation........................................................................................................ 379
A.6.2 vSphere Client installation................................................................................................................... 384
A.6.3 vSphere Client startup - Enter the VMware license ................................................................. 386
A.6.4 vSphere Client Case................................................................................................................................ 389
A.6.4.1 Ethernet ports Allocation........................................................................................................ 390
A.6.4.2 OS Template (OVF) Installation............................................................................................. 392

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server xvii

 A.6.4.3 Steps to upgrade the Low Tier VM to the High Tier VM ............................................. 397
A.6.4.4 Image data disk creation for Standalone (Non-Integrated) virtual AW Server 398
A.6.4.5 Create a GEHC service user account.................................................................................. 400
A.6.4.6 Setup a NTP server for the ESXi server ............................................................................. 405
A.6.4.7 Virtual machine verification ................................................................................................... 407
A.6.4.8 Map an ISO file.............................................................................................................................. 408
A.6.4.9 Disconnect an ISO file ............................................................................................................... 408
A.6.4.10 Upgrade guest OS .................................................................................................................... 408
A.6.4.11 Display the Virtual Machine Console and start the virtual machine................. 409
A.6.4.12 Ensure VMware Tools are installed and running ........................................................ 409
A.7 Software Loading Through iLO ....................................................................................................................... 410
A.7.1 Foreword...................................................................................................................................................... 410
A.7.1.1 Pre-conditions.............................................................................................................................. 410
A.7.1.2 Before you start ........................................................................................................................... 410
A.7.2 Starting the software load................................................................................................................... 411
A.7.2.1 Software load preparation with iLO 5................................................................................ 411
A.7.2.2 Software load preparation with iLO 4, iLO 3 or iLO 2.................................................. 414
A.7.2.3 Server reboot ................................................................................................................................ 417
A.7.2.4 Load From cold steps ................................................................................................................ 418
A.7.2.5 Applications loading steps...................................................................................................... 418
A.7.2.6 Final step ........................................................................................................................................ 418
A.8 SNMP setup in the iLO service processor .................................................................................................. 418
A.9 Useful Commands and Tools ........................................................................................................................... 419
A.9.1 Accessing the Terminal and login as root...................................................................................... 419
A.9.2 Shutting down or rebooting the server.......................................................................................... 420
A.9.2.1 Through the Service Tools menu.......................................................................................... 420
A.9.2.2 Through command lines .......................................................................................................... 421
A.9.3 Checking the routing table .................................................................................................................. 421
A.9.4 Checking the Network settings ......................................................................................................... 421
A.9.5 Checking the AWS configuration ...................................................................................................... 421
A.9.6 Checking the OS release....................................................................................................................... 421
A.9.7 Launching the Internet Navigator from the Server’s KVM..................................................... 421
A.9.8 DNS server(s) setup - Alternate method....................................................................................... 425
A.9.8.1 Enter the Maintenance mode................................................................................................ 425
A.9.8.2 Setup the DNS server(s)........................................................................................................... 425
A.10 Filesystem Check ............................................................................................................................................... 426
A.10.1 Filesystem Check feature description ......................................................................................... 426
A.10.2 Filesystem check Side-effect "issue" description ................................................................... 427
A.10.3 Solutions to minimize the impact.................................................................................................. 427
A.11 Hardware Return Procedure ......................................................................................................................... 430
A.11.1 Old hardware removal ........................................................................................................................ 430
A.11.2 Old hardware return process ........................................................................................................... 430
A.11.2.1 Return Procedure for Americas.......................................................................................... 431
A.11.2.2 Return Procedure for ASIA ................................................................................................... 431
A.11.2.3 Return address for Korea...................................................................................................... 431
A.11.2.4 Return address for Australia / New Zealand ................................................................ 432
A.11.2.5 Return address for GEMS...................................................................................................... 432
A.11.2.6 Return address for East Asia countries .......................................................................... 432
A.11.2.7 Return procedure for other GEHC–Asia countries. ................................................... 432
A.11.2.8 Return Procedure for Europe .............................................................................................. 432
A.12 AW Server Integration in CT/MR Console Environment.................................................................... 433

xviii AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12.1 AW Server Integration in CT/MR Smart Subscription on Edison HealthLink............... 433
A.12.1.1 FE Laptop Setup........................................................................................................................ 434
A.12.1.2 AW Server Installation ........................................................................................................... 434
A.12.1.3 Software Upgrade .................................................................................................................... 445
A.12.1.4 AW Server Client installation.............................................................................................. 445
A.12.2 AW Server Integration in CT Nano-Cloud................................................................................... 447
A.12.2.1 AW Server Installation ........................................................................................................... 447
A.12.2.2 Software Upgrade .................................................................................................................... 456
A.12.2.3 AW Server Client installation.............................................................................................. 457
A.13 Physical Servers - Installed Base................................................................................................................. 461
A.13.1 AW Server - Product Description ................................................................................................... 461
A.13.1.1 The low-tier workstation type version............................................................................ 461
A.13.1.2 The high-tier rack-mount version ..................................................................................... 461
A.13.2 Hardware Installation Verification................................................................................................. 462
A.13.2.1 HP Low Tier server hardware deliverables.................................................................... 462
A.13.2.2 HP High Tier server hardware deliverables................................................................... 468

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server xix

Page intentionally left blank
 1
Chapter 1 Getting Started

1.1 Conventions

1.1.1 Intent of Information

This manual intends to address the following purposes:
Chapter 2: New System Installation
This chapter describes all the steps that the GEHC FE needs to do to install a new low-tier or high-
tier AW Server system. It also describes how to install AW server(s) in a virtual environment. It is not
intended to describe in detail the service tools, or any other process or tools used during installation.
Chapter 3: Upgrade
This chapter describes all the steps that the GEHC FE needs to do, to upgrade an AW Server to the
latest current validated release.
It also describes how to add an AW Server to a cluster of AW servers.
It also describes how to upgrade an older AW Server hardware to a new AW Server hardware.
Chapter 4: Service Tasks
This chapter describes the basic service tasks, such as Preventive maintenance, FRU list and
Disassembly/Reassembly procedures that the GEHC FE may have to do, for servicing an AW Server.
Chapter 5: Appendices
These sections provide more detailed information about specific topics for reference

1.1.2 Safety Terminology

The terms “danger”, “warning”, and “caution” are used throughout this manual to point out hazards
and to designate a degree or level of seriousness. Hazard is defined as a source of potential injury to
a person. The terms “important” and “note” are used to indicate other information you should be
aware of. Familiarize yourself with the following terminology descriptions:

DANGER

Indicates an imminently hazardous situation which if not avoided, will result in death
or serious injury.

WARNING

Indicates a potentially hazardous situation, which if not avoided, could result in death
or serious injury.

CAUTION

Indicates a potentially hazardous situation, which if not avoided, may result in a minor
or moderate injury.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 1

1.1 Conventions

NOTICE
Indicates information where adherence to procedures is crucial or where your
comprehension is necessary to apply a concept or effectively use the product.
NOTE
Provides additional information that is helpful to you. It may emphasize certain
information regarding special tools or techniques, items to check before proceeding, or
factors to consider about a concept.

1.1.3 Data Entry Formatting Conventions

Certain text formats are used to indicate things such as commands that you type in or keys that you
press on the keyboard, etc. For example:

Example Type Explanation

Login as root Command prompt This means you should type in the command, “root” (without
the command quotation marks), then press and release the
“Enter” key. Unless otherwise noted, commands that are typed
in must be followed by pressing the “Enter” key.
Press Enter This means you should press and release the “Enter” key on the
or keyboard.
Press <Enter>
Press <a> This means you should press the "A" key on the keyboard in
lowercase.
Press Alt+C This means you should simultaneously press the “Alt” key and
or the “C” key on the keyboard, then release them both. Do NOT
press the “+” key; the “+” symbol only shows that both keys
Press <Alt> <C> should be pressed at the same time.

1.1.4 Use of numbered lists in this document

This document will use numbered lists when there is a need to describe procedural steps, list
numbered features or concepts, and/or prioritized listed items.

1.1.5 Use of bulleted lists in this document

This document will use bulleted lists to convey informational data-points or concepts where no
priority or process steps are necessarily involved.

1.1.6 Information Disclaimer

The information in this document is accurate at the time of the writing of this document. However,
in the future hardware, BIOS, and software revisions may change making some details inaccurate or
making the coverage of some details missing. This document may or may not get updated when
these changes occur, and may or may not get updated at the exact time of such changes.

1.1.7 Contents of this document

This document covers the installation and upgrade procedures of the AW Server 3.2 software.
It is not intended to cover the service procedures which are addressed in the AW Server 3.2
Advanced Service Manual 5771771-1EN, nor to cover the hardware installation which is addressed
by the AW Server 3.2 Hardware Installation Manual 5719442-1EN.

2 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 1.2 Access to Documentation and Service links

The following guide intends to summarize the installation instructions of a new AW Server 3.2
system, instructions that will be detailed all along this manual in the different sections / job cards of
this chapter.
The installation / configuration instructions are applicable to the forward production physical servers
delivered by GEHC (HPE ProLiant DL360 Gen9 Server and HPE ProLiant DL360 Gen10 Server) and to 1
the Virtual servers (the customer/client delivers and supports the hardware).

Getting Started
NOTE
For installed based physical servers deliverables, refer to A.13 Physical Servers - Installed
Base on page 461.
NOTE
Installation and Configuration of the Hypervisor environment for Virtual AW Server is
under the customer/client’s responsibility. It is described for a VMware hypervisor (ESXi)
and is addressed in Appendix A.6 VMware Support on page 378.

1.2 Access to Documentation and Service links

1.2.1 Documentation

1.2.1.1 Access the AW Server 3.2 Service Documentation

The AW Server 3.2 Service Documentation is available online on:
• Customer Documentation Portal for basic Service Documentation:
https://www.gehealthcare.com/documentationlibrary
• SIMS Content Viewer for basic and advanced Service Documentation.
This information is available from the AWS Service Tools interface under the Documentation link.
It opens one new window with Service Documents information.
NOTE
For Chrome web browser user: A security setting blocks the opening of 2 new tabs
simultaneously. It is an issue for ST Documentation part, because service guides and the
user guides open on different pages. To allow the multiple page openings in Chrome, the
FE should turn of pop up blocker.
NOTE
To view application documentation on a PC, you need Adobe® Reader® X or later. To
download Adobe Reader, please visit Adobe System's website at www.adobe.com.

1.2.1.2 Navigating back and forth though cross-reference links in PDF files
To navigate through the previously/next visited page, you can use the following functionalities:
• You can use keyboard shortcuts as follows:
• For previous view: Press simultaneously <Alt> and <Left arrow> keys.
• For next view: Press simultaneously <Alt> and <Left arrow> keys.
OR
• You can add Previous View and Next View buttons to your Adobe Reader toolbar:
• Click View > Show/Hide > Toolbar Items > Page Navigation > Previous View / Next
View.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 3

1.3 Software Kit

• Use the Previous View and Next View buttons to navigate back and forth in the
document.

NOTE
These functionalities work for most web browsers (FE Laptop or Client PC).
However, they don't work for the Evince (AW/AWS pdf viewer) version installed
on our platforms.

1.2.2 Service Web links

Service Web links are accessible under the Documentation menu:

1.3 Software Kit

This section describes the content of the Software Kit.
This section describes the content of the Software Kit. Refer to the following tables to know which
media you need to install,upgrade or update a Physical AW Server or a Virtual AW Server.

4 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 1.3 Software Kit

Table 1-1 Physical AW Server

Media name Part Type Content Purpose

Number
Operating System 5720621 OS Helios Upgrade/Update:
1
AWS3.2_OS Rev 5.1 for OS loading for the Physical AW

Getting Started
AW Server 3.2 Server
AW Server 3.2 Ext. 3.4 SW 5720631 AWS software Upgrade/Update:
and Docs AWS loading for the Physical AW
Server

NOTE
The Physical AW Servers are preloaded by Manufacturing with OS and AW Server
software. So there is no media for initial installation.
Table 1-2 Virtual AW Server

Media name Part Type Content Purpose

Number
Operating System 5720625 OVF template: OS Helios Initial installation:
Template AWS3.2_OS Rev Virtual Machine creation and OS
5.1 for Virtual AW Server loading for the Virtual AW Server
3.2
AW Server 3.2 Ext. 3.4 SW 5720634 AWS software Initial installation & Upgrade/
and Docs for Virtual Update:
Machine AWS loading for the Virtual AW
Server
Operating System 5720635 OS Helios Upgrade/Update:
AWS3.2_OS Rev 5.1 for OS loading for the Virtual AW
Virtual AW Server 3.2 Server
AW Server 3.2 Ext. 3.4 SW 5818084 • qcow2 image Initial installation & Upgrade/
and Docs for Virtual template: OS Helios + Update:
Machine AWS software Virtual Machine creation and OS +
• Kindler manifest: AWS loading for the Virtual AW
Describes Virtual Server on the CT/MR Console
Machine Environment (Edison HealthLink
characteristics or CT Nano-Cloud)

Table 1-3 Media common to Physical and Virtual AW Server

Media name Part Type Content Purpose

Number
AW Server 3.2 User Docs 5720636 AWS user documentation User documentation for AW
Server

AW Server Demo Exams 5694797 Demo Exams To test that applications can run
after installation

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 5

1.4 Identification of Software releases

Table 1-4 Other

Media name Part Type Content Purpose

Number
Open Source SW for AW 5720637 Open source license Compliance with open source
Server 3.2 agreements license terms

1.4 Identification of Software releases

Changes for CFDA rules
Identification of software releases shall comply with the CFDA regulations. Only the CFDA registered
release number (I.e: aws-3.2- for AW Server 3.2) shall be displayed on the User Interface and on the
software media (CD/DVD) art-work.
However, there is no change in the “conf” file and the SW media contains a "release.txt" file that
displays the version in the usual way.
I.e: Platform version aws-3.2-3.4 shall display:
aws-3.2
Ext. 3.4
This change also impacts the Applications and all the future products.

1.5 LOTO Warning

CAUTION
Field Engineers must always adhere to the Lock Out Tag Out (LOTO) procedure when
installing or servicing an AW Server. (Normally GEHC FEs are only responsible for
servicing the ML350 (low tier) server; other server models are the responsibility of
engineers from the respective hardware vendor).
Refer to the AW Server 3.2 Advanced Service Manual for the LOTO procedure.

6 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2
Chapter 2 Installation of a new AW Server

2.1 Overview
This chapter contains all information necessary for a GEHC field engineer (FE) to install a new AW
Server hardware at a customer site
Pre-installation:
• All preinstallation work must be completed before installing an AW Server system. Refer to the
AW Server 3.2 Pre-Installation Manual 5719441-1EN for complete instructions.
GEHC hardware delivered AW Server:
• All hardware installation work must be completed before loading and configuring a physical AW
Server (hardware delivered by GEHC). Refer to the AW Server 3.2 Hardware Installation Manual
5719442-1EN for complete instructions.
Virtual AW Server:
• All Hypervisor installation work must be completed by the IT administrator of the site before
loading and configuring a virtual AW Server.

2.2 AW Server - Product Description

AW Server is a software package delivered with off-the-shelf, server-class hardware that allows easy
selection, review, processing and filming of multiple-modality DICOM images from a variety of PC
client machines via LAN or WAN networks. It also allows the user to choose lossless or lossy
compression schemes to make a trade-off between speed and quality.
AW Server is intended to be used in a manner similar to the current GE Health Care AW workstation
product. It will be used to create and review diagnostic evidence related to radiology procedures by
trained physicians in General Purpose Radiology, Oncology, Cardiology and Neurology clinical areas.

2.2.1 GEHC delivered AW Server hardware

Two hardware types of AW Server are currently available:

2.2.1.1 The low-tier rack-mount version

Based on the HPE ProLiant DL360 Gen10 Server and the HPE ProLiant DL360 Gen9 Server. It
supports up to 40,000 slices at a time, depending upon which license is purchased.

2.2.1.2 The high-tier rack-mount version

Based on the HPE ProLiant DL360 Gen10 Server and the HPE ProLiant DL360 Gen9 Server.
It supports up to 16,000, 40,000, 80,000 or up to 160,000 slices at a time, depending upon which
license is purchased.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 7

2.2 AW Server - Product Description

Figure 2-1 HPE ProLiant DL360 Gen10 Server

Figure 2-2 HPE ProLiant DL360 Gen9 Server

The customer’s user interface is identical for all Low Tier or High Tier versions.

2.2.2 Virtual AW server

The virtual AW Server application can be installed in the following hypervisor environments:
• VMware vSphere Hypervisor 5.5 (ESXi 5.0)
• VMware vSphere Hypervisor 5.5 (ESXi 5.1)
• VMware vSphere Hypervisor 5.5 (ESXi 5.5)
• VMware vSphere Hypervisor 6.0 (ESXi 6.0)
• VMware vSphere Hypervisor 6.5 (ESXi 6.5)
• VMware vSphere Hypervisor 6.7 (ESXi 6.7)
The hypervisor environment is not supplied by GEHC and installation / support is under the full
responsibility of the customer.

2.2.3 The AW Server – system components

The three basic components in the AW Server system are:
1. The AW SERVER. This is the hardware foundation for the AW SERVER system, and is the direct
responsibility of GEHC, including repair and/or replacement by vendors (HP) acting as agents of
GEHC.
2. The NETWORK, which connects the AW Server to the clients, PACS, etc. The network is NOT the
responsibility of GEHC.
3. The CLIENTS, which are provided by the customer. Other than installing client software on ONE
customer PC, the clients are NOT the responsibility of GEHC.

2.2.4 Software Changes

The AW Server software may change from the time of this writing. If there is a discrepancy between
this document and the screens you see, use your best judgment to complete this procedure as it
was originally intended.

8 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.2 AW Server - Product Description

2.2.5 Before you start

Before starting the installation, verify that at minimum, the following system information is
available.
It can be obtained from the site’s network administrator, or from the Site Survey information
documented by the vendor FE during pre-installation. 2
• Hostname

Installation of a new AW Server

• Server IP address
• Gateway IP address
• Service processor IP address and password (if applicable)
• Proxy configuration
• LDAP server configuration, if EA3 authentication server is used for the site
• Domain name (if applicable for the site)

NOTICE
In Seamless integration with the GE PACS, the AW Server and the Universal Viewer
PACS server must be on a trusted network. If encryption is required for client-server
communication using HTTPS, set it at system level via the Universal Viewer Site
Configuration Tool. Refer to the Universal Viewer Installation Manual.

2.2.6 Software preload by Manufacturing

2.2.6.1 GEHC delivered Physical servers

The Physical AW Servers (hardware delivered by GEHC) are preloaded by Manufacturing with Linux
Operating System (OS), AW Server Platform software, UPS drivers (if applicable) and Advanced
Applications currently supported (See NOTICE next page for potential limitations).
The hardware types currently preloaded are:
• HPE ProLiant DL360 Gen10 Server High Tier and HPE ProLiant DL360 Gen10 Server Low Tier
• HPE ProLiant DL360 Gen9 Server High Tier and HPE ProLiant DL360 Gen9 Server Low Tier

NOTICE
Due to the frequency of introduction of new Volume Viewer Apps releases, the
Forward Production AW Server 3.2 High Tier and Low Tier systems MAY NOT BE fully
preloaded with software, but partially preloaded with OS, AWS Platform and
Applications except Volume Viewer Applications. In that case, this will be indicated
by the below label stuck on the AW Server packaging.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 9

2.3 Quick Start Installation Guide - Physical System

2.2.6.2 Virtual AW Servers on customer’s physical servers

Virtual AW Servers cannot be preloaded by Manufacturing.
The AW Server platform software and the Applications shall be loaded on the Virtual Machine (VM),
once it has been created by the IT administrator of the site through the OS Template (OVF) delivered
by GEHC.

2.3 Quick Start Installation Guide - Physical System

The following guide intends to summarize the installation instructions of a new AW Server 3.2
system, instructions that will be detailed all along this manual in the different sections / job cards of
this chapter.
• The following installation / configuration instructions are applicable to physical servers delivered
by GEHC (Forward Production HPE ProLiant DL360 Gen10 Server and HPE ProLiant DL360 Gen9
Server).
• The following instructions are not applicable to virtual servers (the customer delivers and
supports the hardware). For virtual server installation, refer to 2.4 Quick Start Installation Guide
- Virtual AW Server on page 13.

NOTICE
In case the physical server would not have been preloaded in Manufacturing (I.e:
due to manufacturing no able to proceed at that time), jump to sections 2.5 Job
Card IST001A - Hardware Installation Verification on page 22 and 3.8 Job Card
UPG001 - Software Upgrade on page 269 to perform a load from cold. Bypass
backup and restore related sub sections.
NOTE
This manual does not address the hardware installation which is covered by the AW
Server 3.2 Hardware Installation Manual 5719442-1EN.
Preloaded AW server case - Section Installation / Configuration flowchart for preloaded physical AW
Server.
Physical servers (HPE ProLiant DL360 Gen10 Server and HPE ProLiant DL360 Gen9 Server hardware
delivered by GEHC) are preloaded in Manufacturing. The summarized installation/configuration tasks
are as follows:
• Physically install and setup the server hardware and accessories (see AW Server 3.2 Hardware
Installation Manual 5719442-1EN).
• Perform hardware installation validation - (Turn on and boot the AW Server)
• Configure Network and Time Zone

10 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.3 Quick Start Installation Guide - Physical System

• Configure UPS for auto-shutdown (if applicable)

• Load from their respective media, the Applications that have not been preloaded.
• Configure the AW Server, site parameters, licenses, integration (if applicable) and the
Applications
• Product registration
• System hand-off to customer
2

Installation of a new AW Server

• Install / configure the Client
Installation / Configuration flowchart for preloaded physical AW Server:

Refer to AW Server 3.2

Hardware Installation
Manual5719442-1EN
Chapter 2, Job Cards IST001 Is hardware already No
to IST005 Install the hardware
physically installed?

Yes

Hardware setup
• Apply power to the system
• Check/setup BIOS parameters
• Check/setup RAID parameters
• Setup the iLO service processor
parameters

System completes bootup and displays

login prompt

2.5 Job Card IST001A - Hardware

Installation Verification on page 22
• Type in: root <Enter> and enter the
password
• Check hardware characteristics
through OS

2.13 Job Card IST005 - Network and Time

Configuration on page 88
• Enter the Network parameters
• Enter the Date & Time parameters
• Reboot the AWS

2.11 Job Card IST004A - HPE R/T3000

UPS drivers setup on page 82, Section
2.11.2 Configuring the HPE R/T3000 UPS
using HPPP Software on page 82

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 11

2.3 Quick Start Installation Guide - Physical System

• Configure the HP UPS SW

2.14 Job Card IST006 - Changing the

Passwords on page 93
• Change the AWS system passwords
for security

2.15 Job Card IST007 - Service Tools

Login on page 102
• Connect to the AWS Service Tools UI

2.16 Job Card IST008 - Initial

Configuration on page 108
• Configure Device and Contact Data,
Time Settings…
• Configure Remote access: HCS
InSite / EDS remote
• External Licenses server(s) setup:
Install/configure licenses server(s)

2.17 Job Card IST009 - External

Application(s) Installation on page 132
• 2.17.6 Install the Application(s) on
page 143
• 2.17.7 Activate the Application(s) on
page 146

2.18 Job Card IST010 - Administrative

Configuration on page 148
• Configure DICOM hosts and printers
• Configure Users, Pre-processing, End
of review, etc…
AW Server
declaration on other
Hosts: Image
sources, other
hosts.
2.19 Job Card IST011 - Integration on
page 172
• Integration setup procedures

2.21 Job Card IST013 - Service Tools

Configuration on page 200
• 2.21.1 System Configuration
Registration on page 200

2.22 Job Card IST014A - Standard Client

PC installation & Tests on page 204

12 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.4 Quick Start Installation Guide - Virtual AW Server

• Client SW download and install for

standalone and basic integration
modes.

2.24 Job Card IST015 - Final Settings on

page 240
• Final configuration 2
• System configuration backup

Installation of a new AW Server

2.25 Job Card IST016 - System Handover
to Customer on page 246
• Final instruction before handoff to
customer

AWS System is ready for the customer

2.4 Quick Start Installation Guide - Virtual AW Server

NOTE
For the AW Server integrated within the CT/MR Console Environment (Edison HealthLink
or CT Nano-Cloud), refer to A.12 AW Server Integration in CT/MR Console Environment on
page 433.
For virtual AW servers, the customer delivers and supports the hardware, and creates the VM
(virtual machine) on which the virtual AW Server is hosted).
• Section 2.4.2 Virtual AW Server Installation steps overview on page 15 : Installation of a
virtualized AW server (AW Server is installed on a customer’s server as a virtual machine).
• Section 2.4.3 Quick Start Installation Guide - Scalable Virtual servers on page 18 : Installation
of a cluster of virtualized AW server (scalability)
A cluster of Virtual AW servers (also called Scalability) is a set of several AW Servers (currently up to
30), which form a "bigger - more powerful" AW Server, that can be accessed with appropriate
performances by more AW Server Clients (PCs).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 13

2.4 Quick Start Installation Guide - Virtual AW Server

NOTICE
Installation and Configuration of the Hypervisor environment for Virtual Servers is
under the Customer’s responsibility. It is described for a VMware hypervisor (ESXi) and
is covered in Appendix A.6 VMware Support on page 378.
NOTE
Hyperthreading needs to be turned off on the Hypervisor to optimize the
performances of the AW Server and the 3D applications. Indeed, the software is
optimized for CPU settings with Intel Xeon architecture and without hyperthreading. So, it
is recommended to deactivate the Hyperthreading on AW Server. Therefore, it is not
appropriate to have other customer’s VMs running on the same Hypervisor, if these other
VMs require Hyperthreading to be activated, otherwise it could impact the AW Server
performances.

2.4.1 Virtual Machine characteristics per integration mode

Minimum resources to run each AW Server Node:

14 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.4 Quick Start Installation Guide - Virtual AW Server

No- Hybrid Seamle DICOM DDC in DDC in

Integ ss Direct Edison CT
Process Virtual Slice count
RAM NIC Conne Health Nano-
or HDD license
ct Link Cloud
(DDC)
8 vCPUs 70GB** 24 GB 8K slices 2
1 (SdC_Server_Two_S X X
eats)

Installation of a new AW Server

8 vCPUs 70GB 24/32 16K slices
GB* 2 (SdC_Server_Four_ X
Seats)
8 vCPUs 70GB 64 GB 40K slices
1 (SdC_Low_Tier_Pre X X X
mium)
24 70GB** 64 GB 40K slices
vCPUs 1 (SdC_Server_Eight_ X X
Seats)
8 vCPUs 70GB** 12 GB 4K slices
2 X
(Sdc_Nano_4K)
8 vCPUs 70GB** 26 GB 12K slices
2 X
(Sdc_Nano_12K)
8 vCPUs 70GB** 32 GB 16K slices
2 X
(Sdc_Nano_16K)

*For Seamless integration 32GB RAM is recommended.

**For No-Integ and Hybrid integration, an additional disk for image/backup is required: At least
100GB.

2.4.2 Virtual AW Server Installation steps overview

Section performed by the IT Administrator of the site.

Hardware installation
Environmental pre-requisites Is customer hardware No
already installed? Installing the hardware is under
(Customer's responsibility)
customer's responsibility

Yes

Hypervisor installation
(Customer's responsibility) Hypervisor installation
Is the hypervisor No
For reference only, see already installed? Installing the Hypervisor is
A.6.1 VMware Hypervisor under customer's responsibility
Installation on page 379.

Yes

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 15

2.4 Quick Start Installation Guide - Virtual AW Server

Hypervisor configuration GEHC FE delivers the instructions and the

Virtual Machine creation OVF Template (OS) media to the IT
(IT Admin / GE FE responsibility) Administrator

IST001AB - Hypervisor Configuration on

page 33
• 2.6.2 Ethernet ports Allocation on page
35
• 2.6.3 Create a GEHC service user
account on page 39
• 2.6.4 Setup a NTP server for the
Hypervisor on page 43

IST001B - Virtual Machine

creation on page 44
• 2.7.2.1 OS Template (OVF)
Installation on page 47
• 2.7.2.2 Steps to upgrade / OS Template
downgrade a Virtual
Machine on page 51
• 2.7.2.3 Disconnect the
second Network Adapter on
page 52
• 2.7.2.4 Image data disk
creation for Standalone
(Non-Integrated) virtual AW
Server on page 53

VM is ready for GEHC installation

Section performed by the GEHC FE.

2.9 Job Card IST002B -

Virtual Machine Installation
Verification on page 63
• FE verifies that the VM
created by the IT Admin
has the right
characteristics

2.10 Job Card IST003 -

AWS Platform
Installation of Platform
Software on page 67
• Load the AWS SW from
media
• Enter the Network
parameters
• Enter the Date & Time
parameters
• Reboot the AWS

16 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.4 Quick Start Installation Guide - Virtual AW Server

2.12 Job Card IST004B - Installation of VMware

Tools on page 86
• Install and configure the VM tools

2.14 Job Card IST006 - Changing the

Passwords on page 93
2
• Change the AWS system passwords for
security

Installation of a new AW Server

2.15 Job Card IST007 - Service Tools Login on
page 102
• Connect to the AWS Service Tools UI

2.16 Job Card IST008 - Initial Configuration on

page 108
• Configure or check configuration of: Device,
Contact Data, Time Settings, Remote
access (HCS InSite / EDS remote), External
Licenses server(s) setup (Install/configure
licenses server(s)), etc…

2.17 Job Card IST009 - External

Application(s) Installation on page
132 Applications
• 2.17.5 Load the Application(s)
from media on page 137
• 2.17.6 Install the Application(s) on
page 143
• 2.17.7 Activate the Application(s)
on page 146

2.18 Job Card IST010 - Administrative

Configuration on page 148
• Configure or check configuration of: DICOM
hosts, printers, Users, Pre-processing, End
of review, etc…

AW Server declaration on
other Hosts: Image sources,
other hosts.

VM created from OVF (OS +

AWS) Template USB for AWS
VM created from OVF (OS)
in Standalone (Non-
Template DVD
Integrated) and DDC
integrated mode

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 17

2.4 Quick Start Installation Guide - Virtual AW Server

2.19 Job Card IST011 -

Integration on page 172
• Integration setup
procedures
2.20 Job Card IST012 -
Virtual Servers Cluster
Configuration on page 196
• For AWS placed into a
cluster, setup cluster
configuration procedures

2.21 Job Card IST013 - Service Tools

Configuration on page 200
• 2.21.1 System Configuration Registration
on page 200

2.22 Job Card IST014A - Standard Client PC

installation & Tests on page 204
• Client SW download and install for
standalone (Non-Integrated) and basic
integration modes.
2.23 Job Card IST014B - Seamless Client PC
installation and Tests on page 226
• Client SW download and install for
Seamless integration

2.24 Job Card IST015 - Final Settings on page

240
• Final configuration
• System configuration

2.25 Job Card IST016 - System Handover to

Customer on page 246
• Final instruction before handoff to
customer

AWS System is ready for the customer

2.4.3 Quick Start Installation Guide - Scalable Virtual servers

AW Servers scalability overview

18 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.4 Quick Start Installation Guide - Virtual AW Server

Figure 2-3 Example of a cluster of 3 virtual AW Servers using 2 customer’s hardware servers

Installation of a new AW Server

The virtual AW Server system provides a scalability function:
Several virtual AW Servers can be grouped in a Cluster. An AW Server which is part of a cluster is
called a node. In a cluster, the AW Servers can be connected and thus more computing power is
provided for the users. For the end user the same experience will be provided as a single AWS
provides.
NOTE
Hyperthreading needs to be turned off on the Hypervisor to optimize the
performances of the AW Server and the 3D applications. Indeed, the software is
optimized for CPU settings with Intel Xeon architecture and without hyperthreading. So, it
is recommended to deactivate the Hyperthreading on AW Server. Therefore, it is not
appropriate to have other customer’s VMs running on the same Hypervisor, if these other
VMs require Hyperthreading to be activated, otherwise it could impact the AW Server
performances.

NOTICE
Two HAPS (High Availability Preferences Sharing) servers VM shall be created through
the OVF Template OS and the AWS Platform software.
Current Scalability Limitations
• Scalability is currently only supported on Virtual AW servers and limited to a maximum of thirty
(30) virtual AW Servers 16K slices (AW Server 40K slices is supported in cluster mode only for
DICOM Direct Connect integration).
• Each virtual AW Server must be linked to one dedicated physical 1Gb network card.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 19

2.4 Quick Start Installation Guide - Virtual AW Server

• For proper Scalability operation, all AW Servers in the cluster must be linked to the Hospital
network to ensure communication with the DICOM hosts, the Universal Viewer / AWS
Client and the PACS, etc.), and to ensure communication between the nodes of the cluster
(each virtual AW server).

NOTICE
To ensure high availability, the two HAPS servers shall preferably be hosted
on two different hypervisors.
Scalable AW Servers Installation steps overview
Section performed by the IT Administrator of the site.

Hardware installation
Environmental pre-requisites Is customer hardware No
already installed? Installing the hardware is under
(Customer's responsibility)
customer's responsibility

Yes

Hypervisor installation
(Customer's responsibility) Hypervisor installation
Is the hypervisor No
For reference only, see already installed? Installing the Hypervisor is
A.6.1 VMware Hypervisor under customer's responsibility
Installation on page 379.

Yes

Hypervisor configuration GEHC FE delivers the instructions and the

Virtual Machine creation OVF Template (OS) media to the IT
(IT admin / GE FE responsibility) Administrator

IST001AB - Hypervisor Configuration on

page 33
• Section 2.6.2 Ethernet ports Allocation
on page 35 (2 for each VM)
• Section 2.6.3 Create a GEHC service
user account on page 39
• Section 2.6.4 Setup a NTP server for
the Hypervisor on page 43

2.8 Job Card IST001C - Virtual Servers

Cluster Installation Steps on page 56
• Create a cluster of AW Servers

IST001B - Virtual Machine

creation - #1 for HAPS on page
44

20 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.4 Quick Start Installation Guide - Virtual AW Server

• VM creation from the OVF

Template media for the High
Availability Preference
Sharing server #1

IST001B - Virtual Machine

creation - #2 for HAPS on page 2
44

Installation of a new AW Server

• VM creation from the OVF
Template media for the High
Availability Preference
Sharing server #2
OS Template
IST001B - Virtual Machine
creation - #1 for AWS on page
44
• VM creation from the OVF
Template media for the AW
server #1

IST001B - Virtual Machine

creation - #2 for AWS on page
44
• VM creation from the OVF
Template media for the AW
server #2

IST001B - Virtual Machine

creation - #n for AWS on page
44
• VM creation from the OVF
Template media for the AW
server #n

VM are ready for GEHC

installation

Section performed by the GEHC FE.

To do for each virtual HAPS server:

2.9 Job Card IST002B - Virtual Machine

Installation Verification on page 63
• FE verifies that the VM created by the IT
Admin has the right characteristics

2.10 Job Card IST003 - Installation of AWS Platform

Platform Software on page 67
• Load the HAPS SW from the AWS media
• Enter the Network parameters
• Enter the Date and Time parameters

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 21

2.5 Job Card IST001A - Hardware Installation Verification

• Reboot the AWS

2.12 Job Card IST004B - Installation of

VMware Tools on page 86
• Install and configure the VM tools

HAPS servers are ready

To do for each virtual AW server:

Proceed as described in 2.4.2 Virtual AW Server Installation steps overview on page 15, Section
performed by the GEHC FE. on page 16.

AWS System is ready for the customer

2.5 Job Card IST001A - Hardware Installation

Verification
This Job Card applies to all GEHC hardware delivered servers.

NOTICE
*** IMPORTANT PROCESS REQUIREMENT ***
Any deficiencies or hardware failures found while executing the following verification
process must be IMMEDTIATELY reported to the GEHC OLC support team, and the
Vendor PMI (Installation Manager) and or Vendor FE to be resolved prior to GEHC
Service accepting ownership of the system, and installing the AW Server software!!!
Training time can be logged if the GEHC FE desires to observe – but not actual
installation time until the hand-off is successful.
NOTE
This Job Card describes the installation verification for the forward production server
(HPE ProLiant DL360 Gen10 Server and HPE ProLiant DL360 Gen9 Server).
For installed based physical servers deliverables, refer to A.13 Physical Servers - Installed
Base on page 461.

2.5.1 Time Reporting for Installation and Warranty

The AW Server TOTAL installation is designed to be completed within roughly one work shift -
approximately:
• HP High Tier server- 8 to 11 hours, with:
• 5 to 6 hours for the PHYSICAL installation
• 3 to 5 hours for the AWS Software / Configuration (GEHC) installation.
• HP Low Tier server- 4 to 7 hours, with:
• 1 to 2 hours for the PHYSICAL installation
• 3 to 5 hours for the AWS Software / Configuration (GEHC) installation.

22 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.5 Job Card IST001A - Hardware Installation Verification

Charge any additional time to the appropriate service class. Examples include: “TRAINING” (87),
"Installation Support" (04) and Customer Courtesy Call (90).
Charge any system malfunction / troubleshooting and repair time to the appropriate
warranty service class (10 or 11).
The business intent is to accurately measure product quality by having reliable service installation
and warranty records and metrics. 2
2.5.2 Hardware Installation validation

Installation of a new AW Server

1. Supplies
• High Tier Server or Low Tier Server
• UPS option (if applicable)
• KVM option (if applicable) or Monitor, Keyboard and Mouse
• Power cables, Network cables and video cable for KVM
• Network switch option (if applicable)
• PDU (Power Distribution unit) option (if applicable)
2. Tools and parts required
• AW Server platform software DVD.
• AW Server OS DVD: To be used at time of first installation (or needed if load-from-cold is
required), if the system has not been Preloaded by Manufacturing.
• UPS drivers CD (for UPS option if applicable): (needed if load-from-cold is required).
• GEHC service (FE) laptop and network cable.
3. Pre-requisites
The High Tier server and accessories may have been physically installed by the IT department of the
site. Verify that all of the following steps have been completed correctly:
• Server securely mounted in rack (if applicable).
• If applicable, PDU option is securely mounted in rack.
• If applicable, UPS option is securely mounted in rack.
• If applicable, KVM option is securely mounted in rack.
• If applicable, Network Switch option is securely mounted in rack.
• All necessary power cables are installed.
• All necessary network cables are installed.
• If applicable, the UPS shutdown line USB cable is installed between the server and the UPS.
• If applicable, KVM option connected or Monitor, Keyboard and Mouse.
For HPE ProLiant DL360 Gen10 Server Low Tier and High Tier, see 2.5.3 HPE ProLiant DL360 Gen10
Server High Tier and Low Tier on page 23.
For HPE ProLiant DL360 Gen9 Server Low Tier and High Tier, see 2.5.4 HPE ProLiant DL360 Gen9
Server High Tier and Low Tier on page 28.

2.5.3 HPE ProLiant DL360 Gen10 Server High Tier and Low Tier
1. Verify that the Server hardware inventory (provided within server documentation) includes the
items below:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 23

2.5 Job Card IST001A - Hardware Installation Verification

• For HPE ProLiant DL360 Gen10 Server High Tier:

Description Quantity
HP DL360 chassis 1
300GB 15K SAS 2.5" HDD 2
1.8TB 10K SAS 2.5" HDD 6
Internal DVD+/-RW drive 1
Internal RAID controller 1
Redundant hot-swappable AC power supply 2
Tool-less slide rail kit 1

• For HPE ProLiant DL360 Gen10 Server Low Tier:

Description Quantity
HP DL360 chassis 1
300GB 15K SAS 2.5" HDD 2
600GB 10K SAS 2.5" HDD 6
Internal DVD+/-RW drive 1
Internal RAID controller 1
Redundant hot-swappable AC power supply 2
Tool-less slide rail kit 1

2. Verify that the server slides out and in the rack enclosure easily, and do not bind or cause
disconnected cables. This means that the cables, and cable arm harness (if installed) must be
dressed and strain-relieved properly.
3. Inspect all units to insure that there is no visible chassis damage.
4. Verify that the server has two 300GB drives and six 1.8TB drives (High Tier) or six 600GB drives
(Low Tier), as shown in the picture below:

5. Verify that the Server is connected to a PDU (either data center PDU or rack mount) and/or
connected to a UPS (either data center UPS or rack mount).
6. If rack mount UPS is installed, verify that UPS is powered on, and that the KVM, Network switch,
server and DAS are connected to UPS and PDU as shown below.

24 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.5 Job Card IST001A - Hardware Installation Verification

Installation of a new AW Server

7.
• HPE ProLiant DL360 Gen10 Server High Tier: Verify that the High Tier server is connected to
the network with one cable set on port P1 of the additional Ethernet controller (1) and one
cable set on the iLO port (2).

• HPE ProLiant DL360 Gen10 Server Low Tier: Verify that the Low Tier server is connected to
the network with one cable set on port 1 of the Ethernet controller (1) and one cable set on
the iLO port (2).

8. Verify that the KVM (or monitor) is connected to the VGA output and that the keyboard and
mouse inputs are connected to the USB port(s).
9. Verify that the UPS auto-shutdown USB input is connected to the one of the USB ports of the
server.
10. Apply power to the system. Apply power to the mains inputs of PDU and UPS (if applicable).
• The UPS utility green LED should blink. The KVM turns on.
• The Server on/off button LED should be steady yellow.
11. Power up the UPS (if applicable) by pressing on the On button.
• The Network switch option turns on.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 25

2.5 Job Card IST001A - Hardware Installation Verification

• The UPS Utility LEDs should display steady green as shown.

Figure 2-7 HPE R/T3000 UPS front panel

12. Power up the server by pressing on the Power On button.

• The Server power on/off button light turns from yellow to green.
• There will be LED activity on the Server HDDs / SSDs and the LEDs shall be green.
• The Network 1 LED should be ON (if the network is configured).
• Hardware initialization sequence takes several minutes to complete. Please be patient.
Then after a while, the screen unblanks and will display the HP ProLiant logo and boot up
messages.
13. Verify that the following parameters are setup correctly, referring to the AW Server 3.2
Hardware Installation Manual 5719442-1EN:
a. BIOS parameters (press <F9> to enter BIOS setup).
NOTE
The BIOS parameters can be checked without having to reboot the system and
enter the BIOS menu as follow:
• In a terminal, login as root.
• Type the following command: /sbin/conrep -s <Enter>.
• The BIOS parameters are save locally in the file conrep.dat, and can be
viewed using the command cat conrep.dat <Enter> or the command
more conrep.dat <Enter>.
b. iLO Service Processor parameters (press <F8> to enter iLO setup).
c. RAID controllers / RAID levels parameters (press <F8> to enter RAID setup).
• P440ar RAID controllers / RAID levels parameters
• 2 x 300GB HDDs in RAID 1
• 6 x 600GB HDDs (Low Tier) in RAID 6 OR

26 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.5 Job Card IST001A - Hardware Installation Verification

• 6 x 1.8TB HDDs (High Tier) in RAID 6

14. Quit the BIOS setup.
Once initialization is complete, the boot sequence will restart and complete as the AW Server
has been preloaded by Manufacturing.
NOTE
When booting the AW Server, Helios progress bar is displayed for OS boot. However 2
details of other operations are not provided. To display the details, hit any of the

Installation of a new AW Server

arrow keys or the <Esc> key. This will display of OS boot messages including
filesystem check progress. Hitting any of the arrow keys or the <Esc> key again
displays the previous OS boot screen progress bar.
15. When boot sequence has completed, login as root.
16. If home1 is not properly mounted you may get the following messages:

ERROR: Image partitions are not mounted!!

Press <Enter> to abort reconfiguration.
a. In that case, press <Enter>.
The server will shutdown with the following messages:

INFO: Backup copies not removed, boot sequence intact.

Ghost configuration as preload has failed.
Check RAID and disks are operational and correctly configured.
Config service will run again at next platform boot.
Press <ENTER> to shutdown.
b. Check that no HDDs of the RAID are failed, before pressing the <Enter> key and
attempting to boot again.
c. When done, press <Enter> to boot.
17. Verify that the OS sees the correct CPUs are installed with the following command levels, and
corresponding results:

Command Result
cat /proc/cpuinfo | more <Enter> Complete information
cat /proc/cpuinfo | grep -i processor <Enter> Filtered on ordered Processor numbers
cat /proc/cpuinfo | grep -i CPU <Enter> Filtered on CPU info

There are 32 (2 x Sixteen-core) processors with a model name of “Intel(R) Xeon(R) CPU".
18. Verify that the OS sees the correct amount of memory with the following command:
cat /proc/meminfo | grep -i memtotal <Enter>
26440444 kB (256GB) total memory.
19. Verify the partitioning after the AWS load with the following command: df -k <Enter>.
NOTE
Alternatively, you can use the df -h command for a display in GBytes.
NOTE
System filesystem defaults to sda, backup and image filesystems to sdb.
NOTE
The Used and Available values may differ from those displayed in the examples
below.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 27

2.5 Job Card IST001A - Hardware Installation Verification

The example below is for a HP High Tier server.

The example below is for a HP Low Tier server.

20. Check the OS version, with the following command and results:
cat /etc/aweos <Enter>
For AWS3.2 Ext.3.4 release:

OS: AWS3.2_OS_5.1
OS Build ID: yyyymmdd I.e: 20190626
21. Check the AWS Platform version, with the following command and results:
cat /etc/aweconfig <Enter>
For AWS3.2 Ext.2.0 release:

AWE_HOME=/usr/share/awe
AWE_VERSION=aws-3.2-2.0-1728.2
AWE_BUILDID=aws-3.2-2.0-1728.2
AWE_BUILDDATE=20170713
AWE_UDI='(01)00840682102384(10)AWS3D2E002D0'
AWE_REF='5719780'
AWE_LOT='AWS3D2E002D0'
AWE_USER=sdc
AWE_GROUP=sdc
HTDOCS=/var/www/html
APACHE_CONFDIR=/etc/httpd
AWE_JVMARGS="-Xmx1000m -Xss128k -server -Dtap.dm.ImageMemory=200 -
XX:+UseParallelGC -XX:+AggressiveHeap"
NOTE
This is an example result. The actual values on your screen may differ at time of
release of the software.
22. Setup now the Network parameters and the Date & Time parameters for you AW Server.
Factory Preloaded AW Server: Proceed to 2.13 Job Card IST005 - Network and Time
Configuration on page 88.

2.5.4 HPE ProLiant DL360 Gen9 Server High Tier and Low Tier
1. Verify that the Server hardware inventory (provided within server documentation) includes the
items below:
• For HPE ProLiant DL360 Gen9 Server High Tier:

Description Quantity
HP DL360 chassis 1

28 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.5 Job Card IST001A - Hardware Installation Verification

Description Quantity
300GB 15K SAS 2.5" HDD 2
1.8TB 10K SAS 2.5" HDD 6
Internal DVD+/-RW drive 1
Internal RAID controller 1
2
Redundant hot-swappable AC power supply 2

Installation of a new AW Server

Tool-less slide rail kit 1

• For HPE ProLiant DL360 Gen9 Server Low Tier:

Description Quantity
HP DL360 chassis 1
300GB 15K SAS 2.5" HDD 2
600GB 10K SAS 2.5" HDD 6
Internal DVD+/-RW drive 1
Internal RAID controller 1
Redundant hot-swappable AC power supply 2
Tool-less slide rail kit 1

2. Verify that the server slides out and in the rack enclosure easily, and do not bind or cause
disconnected cables. This means that the cables, and cable arm harness (if installed) must be
dressed and strain-relieved properly.
3. Inspect all units to insure that there is no visible chassis damage.
4. Verify that the server has two 300GB drives and six 1.8TB drives (High Tier) or six 600GB drives
(Low Tier), as shown in the picture below:

5. Verify that the Server is connected to a PDU (either data center PDU or rack mount) and/or
connected to a UPS (either data center UPS or rack mount).
6. If rack mount UPS is installed, verify that UPS is powered on, and that the KVM, Network switch,
server and DAS are connected to UPS and PDU as shown below.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 29

2.5 Job Card IST001A - Hardware Installation Verification

7.
• HPE ProLiant DL360 Gen9 Server High Tier: Verify that the High Tier server is connected to
the network with one cable set on port P1 of the additional Ethernet controller and one
cable set on the iLO port.

• HPE ProLiant DL360 Gen9 Server Low Tier: Verify that the Low Tier server is connected to
the network with one cable set on port 1 of the Ethernet controller and one cable set on the
iLO port , as shown in the picture below:

8. Verify that the KVM (or monitor) is connected to the VGA output and that the keyboard and
mouse inputs are connected to the USB port(s).
9. Verify that the UPS auto-shutdown USB input is connected to the one of the USB ports of the
server.
10. Apply power to the system. Apply power to the mains inputs of PDU and UPS (if applicable).
• The UPS utility green LED should blink. The KVM turns on.
• The Server on/off button LED should be steady yellow.
11. Power up the UPS (if applicable) by pressing on the On button.
• The Network switch option turns on.
• The UPS Utility LEDs should display steady green as shown.

30 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.5 Job Card IST001A - Hardware Installation Verification

Figure 2-5 HPE R/T3000 UPS front panel

Installation of a new AW Server

12. Power up the server, by pressing on the Power On button.

• The Server power on/off button light turns from yellow to green.
• There will be LED activity on the Server HDDs / SSDs and the LEDs shall be green.
• The Network 1 LED should be ON (if the network is configured).
• Hardware initialization sequence takes several minutes to complete. Please be patient.
Then after a while, the screen unblanks and will display the HP ProLiant logo and boot up
messages.
13. Verify that the following parameters are setup correctly, referring to the AW Server 3.2
Hardware Installation Manual 5719442-1EN:
a. BIOS parameters (press <F9> to enter BIOS setup).
NOTE
The BIOS parameters can be checked without having to reboot the system and
enter the BIOS menu as follow:
• In a terminal, login as root.
• Type the following command: /sbin/conrep -s <Enter>.
• The BIOS parameters are save locally in the file conrep.dat, and can be
viewed using the command cat conrep.dat <Enter> or the command
more conrep.dat <Enter>.
b. iLO Service Processor parameters (press <F8> to enter iLO setup).
c. RAID controllers / RAID levels parameters (press <F8> to enter RAID setup).
• P440ar RAID controllers / RAID levels parameters
• 2 x 300GB HDDs in RAID 1
• 6 x 600GB HDDs (Low Tier) in RAID 6 OR
• 6 x 1.8TB HDDs (High Tier) in RAID 6

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 31

2.5 Job Card IST001A - Hardware Installation Verification

14. Quit the BIOS setup.

Once initialization is complete, the boot sequence will restart and complete as the AW Server
has been preloaded by Manufacturing.
NOTE
When booting the AW Server, Helios progress bar is displayed for OS boot. However
details of other operations are not provided. To display the details, hit any of the
arrow keys or the <Esc> key. This will display of OS boot messages including
filesystem check progress. Hitting any of the arrow keys or the <Esc> key again
displays the previous OS boot screen progress bar.
15. When boot sequence has completed, login as root.
16. If home1 is not properly mounted you may get the following messages:

ERROR: Image partitions are not mounted!!

Press <Enter> to abort reconfiguration.
a. In that case, press <Enter>.
The server will shutdown with the following messages:

INFO: Backup copies not removed, boot sequence intact.

Ghost configuration as preload has failed.
Check RAID and disks are operational and correctly configured.
Config service will run again at next platform boot.
Press <ENTER> to shutdown.
b. Check that no HDDs of the RAID are failed, before pressing the <Enter> key and
attempting to boot again.
c. When done, press <Enter> to boot.
17. Verify that the OS sees the correct CPUs are installed with the following command levels, and
corresponding results:

Command Result
cat /proc/cpuinfo | more <Enter> Complete information
cat /proc/cpuinfo | grep -i processor <Enter> Filtered on ordered Processor numbers
cat /proc/cpuinfo | grep -i CPU <Enter> Filtered on CPU info

There are 32 (2 x Sixteen-core) processors with a model name of “Intel(R) Xeon(R) CPU".
18. Verify that the OS sees the correct amount of memory with the following command:
cat /proc/meminfo | grep -i memtotal <Enter>
26440444 kB (256GB) total memory.
19. Verify the partitioning after the AWS load with the following command: df -k <Enter>.
NOTE
Alternatively, you can use the df -h command for a display in GBytes.
NOTE
System filesystem defaults to sda, backup and image filesystems to sdb.
NOTE
The Used and Available values may differ from those displayed in the examples
below.
The example below is for a HP High Tier server.

32 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.6 Job Card IST001AB - Hypervisor Configuration

The example below is for a HP Low Tier server. 2

Installation of a new AW Server

20. Check the OS version, with the following command and results:
cat /etc/aweos <Enter>
For AWS3.2 Ext.3.4 release:

OS: AWS3.2_OS_5.1
OS Build ID: yyyymmdd I.e: 20190626
21. Check the AWS Platform version, with the following command and results:
cat /etc/aweconfig <Enter>
For AWS3.2 Ext.2.0 release:

AWE_HOME=/usr/share/awe
AWE_VERSION=aws-3.2-2.0-1728.2
AWE_BUILDID=aws-3.2-2.0-1728.2
AWE_BUILDDATE=20170713
AWE_UDI='(01)00840682102384(10)AWS3D2E002D0'
AWE_REF='5719780'
AWE_LOT='AWS3D2E002D0'
AWE_USER=sdc
AWE_GROUP=sdc
HTDOCS=/var/www/html
APACHE_CONFDIR=/etc/httpd
AWE_JVMARGS="-Xmx1000m -Xss128k -server -Dtap.dm.ImageMemory=200 -
XX:+UseParallelGC -XX:+AggressiveHeap"
NOTE
This is an example result. The actual values on your screen may differ at time of
release of the software.
22. Setup now the Network parameters and the Date & Time parameters for you AW Server.
Factory Preloaded AW Server: Proceed to 2.13 Job Card IST005 - Network and Time
Configuration on page 88.

2.6 Job Card IST001AB - Hypervisor Configuration

2.6.1 Overview
This section applies to the Hypervisor configuration on a customer’s physical server.
It allows installing and configuring the Hypervisor environment for the creation and the
management of the virtual machine(s) hosting the virtual AW Server.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 33

2.6 Job Card IST001AB - Hypervisor Configuration

All sections are performed and completed by the IT Administrator of the site.

Make sure the physical server has the required characteristics and the minimal resources to support
the Virtual AW Server installation, defined in the and summarized below:
Physical server (host) characteristics:
• Intel Xeon CPUs supporting SSE 4.1 instructions
• 2 Ethernet devices (minimum 1Gb/s)
• Data store to store all VM data with thick provisioning, including provision for Windows and VM
swap files (70GB).
• Data store to store images (6TB max)
• Enough RAM to satisfy virtual RAM requirements without RAM over commit
NOTE
Hyperthreading needs to be turned off on the Hypervisor to optimize the
performances of the AW Server and the 3D applications. Indeed, the software is
optimized for CPU settings with Intel Xeon architecture and without hyperthreading. So, it
is recommended to deactivate the Hyperthreading on AW Server. Therefore, it is not
appropriate to have other customer’s VMs running on the same Hypervisor, if these other
VMs require Hyperthreading to be activated, otherwise it could impact the AW Server
performances.
Virtual Machine (hosted) characteristics:

AWS Low Tier AWS High Tier HAPS server

processor: 8 vCPUs processor: 24 vCPUs processor: 1 vCPUs
disk: one 70GB vHDD disk: one 70GB vHDD disk: one 40GB vHDD
memory: 24GB* memory: 64GB* memory: 4GB
network: 2 x Ethernet network: 2 x Ethernet network: 2 x Ethernet

*RAM depends on integration mode, see table in Section 2.4.1 Virtual Machine characteristics per
integration mode on page 14
NOTE
As the host, the Virtual Machine shall support the SSE 4.1 instructions. If it is not the case,
it could lead to Applications start failure.
If not, you shall configure the hypervisor EVC mode to a level which supports SSE 4.1
instruction.

Hypervisor configuration process summary:

1. The IT admin installs, configures and connects to the Hypervisor.
NOTE
Installation and Configuration of the Hypervisor environment for Virtual AW Server is
under the Customer’s responsibility.
For VMware hypervisor (ESXi) it is addressed in Appendix A.6 VMware Support on
page 378 VMware Hypervisor Installation Steps.
2. The IT admin allocates the physical network port(s) of the Hypervisor necessary for the virtual
AW Server. - 2.6.2 Ethernet ports Allocation on page 35
3. The IT admin creates a "service" account so that the GE FE will be able to administrate the
virtual AW Server. - 2.6.3 Create a GEHC service user account on page 39

34 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.6 Job Card IST001AB - Hypervisor Configuration

4. The IT admin makes sure a NTP server is setup for the Hypervisor - See 2.6.4 Setup a NTP server
for the Hypervisor on page 43
NOTE
The steps are described for VMware hypervisor (ESXi) with VMware vSphere Web
Client. To have the equivalent steps using VMware vSphere Client, refer to Appendix
A.6 VMware Support on page 378. And if needed, refer to VMware documentation for 2
more details.

Installation of a new AW Server

2.6.2 Ethernet ports Allocation

2.6.2.1 Foreword
Requirement on physical network card
The minimum requirement to install a virtual AW Server is to have one physical network card
dedicated to the AW Server VM. This requirement applies to each hypervisor that will host the
virtual AW Server.
For a cluster of AW Server VMs, a second physical network card is required on each host.
The Virtual machine containing the virtual AW Server will have 2 virtual network card. This is defined
in the settings of the OVF Template.
Requirement on port groups and virtual switch
For the first virtual network card of the VM, the minimum requirement is to have one port group
connected to one 1GB/s physical network card. The port group contains only the AW Server Virtual
Machine. This way the physical network card is dedicated to the virtual AW Server.
It is also possible to have other Virtual Machines using the same port group. However in this case, it
is needed to have the same number of physical network card and of Virtual Machines in the virtual
switch.
For the second virtual network card of the VM, there are 2 cases:
• If the VM is part of a cluster (Low-Tier VM only).
• If the VM is not part of a cluster, the second virtual network card can be associated to the same
port group as the first virtual network card. Another valid configuration is to associate the
second virtual network card to a port group with no physical network card
Resource preparation for Virtual Machine
It is important to check that enough resources are available for the AW Server Virtual Machine:
• CPU (no hyperthreading)
• Memory
• Storage
Also, if several AW Server Virtual Machines are going to be installed, the minimum requirements
have to be multiplied by the number of VM.
Also keep in mind that CPU and RAM should not be over committed for the AW Server. The AW
Server VMs always need access to the resources described in minimum requirements.

2.6.2.2 Procedure
NOTE
The steps below are provided as an example to configure the network on one single
hypervisor with 4 physical network cards that will host one virtual AW Server. For details

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 35

2.6 Job Card IST001AB - Hypervisor Configuration

on the network configuration for more advanced configuration and clusters, refer to the
related documentation.
The following example is based on the use of a physical server equipped with a Network controller
fitted with 4 Ethernet ports. In our example, the physical server will be used to host Virtual
machine(s) (virtual AW Server(s)).
Using bigger physical servers with higher capacity and a greater number of Ethernet controllers and/
or Ethernet ports allows hosting of a higher number of virtual machines, however the settings of
these servers follow the same philosophy.
Always make sure that the Virtual AW Servers will have the necessary bandwidth.
Necessary Networking Hardware resources:
The virtual AW Server needs two 1GB/s physical network cards (Ethernet port) dedicated only to the
AW Server.
The first 1 GB/s physical network card is dedicated to communication with the other hosts on the
Hospital network.
The second 1 GB/s physical network card dedicated to the AW Server is used within a cluster of AW
Servers for the private scalability network. It is not used for a single Virtual Machine.
NOTE
It is recommended to use a separate NIC for the Management network of the Hypervisor,
in order to ensure that enough bandwidth will be available during template deployment
or other similar operations.
Below are the instructions to configure vSphere networking for virtual AW Server(s).
1. Login to the vSphere Web Client:
a. Enter the URL for the vSphere Web Client in your web browserinfo:
https://<client-hostname>/vsphere-client
b. Select LAUNCH VSPHERE WEB CLIENT (FLEX).
c. Enter the administrator login and password. Check with the IT admin for the login/
password.
2. In the vSphere Web Client page that displays:

a. Select the Hypervisor and click on Configure.

b. Expand Networking sub-menu and click on Physical adapters to see the available
Ethernet ports and their status.
The Physical adapters panel displays. You can read information about the different adapters
such as their speed and the virtual switch they are linked to.
c. Check how many network cards are available and which one you plan to attribute to the
Virtual machines that are going to be created.

36 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.6 Job Card IST001AB - Hypervisor Configuration

3. Create a virtual switch for the virtual AW Server:

Virtual switches are entities used by vSphere to link virtual network card of a Virtual Machine to
physical network card of the server hardware.

a. Click on the icon.

The Add Networking wizard displays. 2
b. Select the Virtual Machine Port Group for a Standard Switch radio button and click on

Installation of a new AW Server

Next.
c. In the panel that displays, select New standard switch radio button and click on Next.
d. In the panel that displays, click on the + icon.
e. In the sub-screen that displays, select the next available Network Adapter and click on
OK.
NOTE
In case of private network (see Step 5 below) select a network adapter that is
not connected to the hospital network.
f. Click on Next.
NOTE
In case of private network (see Step 5 below) acknowledge the popup that
displays.
g. In the panel that displays, type in the Network label (AWS3 Hospital Network, for
example) and click on Next.
The Ready to Complete panel displays.
h. Click on Finish.
4. Follow the same procedure to setup other Network adapters if needed and create the vSphere
standard switches that will be attributed to the Virtual machines (AW Servers) once they have
been created.
5. If the AW Server is part of a cluster of virtual AW Servers, an additional network (AW Server
Private Network) needs to be configured to ensure communication between the nodes of the
cluster.
6. Follow the same procedure to setup the Network adapter for the AW Server Private Network.
NOTE
Two or more virtual AW Servers hosted on the same physical server can share the
same physical Network adapter for the AW Server Private Network.
7. Display the configuration of the virtual switch by clicking on Virtual switches then on the
switch previously created.
The Standard switch panel displays. This view displays the current configurations of the virtual
switches for this Hypervisor.
8. When complete, the configuration should display as follows:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 37

2.6 Job Card IST001AB - Hypervisor Configuration

NOTE
In our example above, the virtual network switch vmnic5 is not connected (red cross)
to the Hospital network as it will be used for the AW Server Private network (in case
of cluster mode), and therefore separated from the Hospital network (Broadcast is
used on the AW Server Private network).
9. There is also a virtual switch that contains the Management network. This virtual switch is used
to indicate what physical network card is used for communication between the Hypervisor and
the vSphere clients.

It is recommended to keep a dedicated virtual switch for Management Network.

10. Optional: if the VM Network displays as linked to the Management Network, as in the example
above, you need to remove it:
a. Select the switch containing the Management Network.
b. Select the Management Network and click on the red cross in the Standard switch part of
the panel.

38 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.6 Job Card IST001AB - Hypervisor Configuration

c. Click on Yes to acknowledge the confirmation message that pops up.

This completes the Network ports allocation.
Proceed to 2.6.3 Create a GEHC service user account on page 39.

2.6.3 Create a GEHC service user account

2
In order to allow the GEHC FE to complete the installation of the virtual AW Server (virtual console
access, virtual DVD drive usage…), it is needed to provide him/her an "hypervisor" account with the

Installation of a new AW Server

sufficient permissions on the AW Server Virtual Machine.
Below are the steps to configure a role and a local user on one single hypervisor. For more advanced
configuration, refer to the related documentation.
1. Connect to the ESXi Web Interface.
In a web browser enter the URL or IP address of the ESXi:
https://<ESXi URL or IP>/
The ESXi Web Interface login screen displays.
2. Enter the root login and password. Check with the IT admin for the password.
The vSphere Web Client page displays.
3. Create a GE Service role with appropriate permissions. As a first step, a new GE Service role
shall be created with the necessary permissions to administrate a Virtual machine.
a. In the Navigator panel, expand Host and click on Manage.
b. Click on the Security & Users tab and select Roles.

c. Click on the Add role icon.

The Add a role screen displays.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 39

2.6 Job Card IST001AB - Hypervisor Configuration

d. Name the new role GE Service.

e. Give the following permissions by checking the boxes:
• System
• Datastore
• Virtual machine
f. Click on Add.
The new GE Service role displays in the list of existing Roles.
4. Create a service user:
a. In the Security & Users tab, select Users.

b. Click on the Add user icon.

The Add a user screen displays.

40 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.6 Job Card IST001AB - Hypervisor Configuration

Installation of a new AW Server

c. Name the new user service.
d. Type the password twice in the Password and Confirm password fields
e. Click on Add.
A new user service displays in the list of Users.
5. Assign the GE Service role permissions to the service user:
a. In the Navigator panel, right click on Manage and select Permissions.
The Manage permissions wizard displays.

b. Click on the Add user icon.

The Add user for Host panel displays.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 41

2.6 Job Card IST001AB - Hypervisor Configuration

c. On the second drop-down menu, select the newly created GE Service role.
d. Click on the Add user button.
e. The user service displays in the list of users with the GE Service role.

f. Click on Close.
The service user gets linked to the GE Service role with the appropriate permissions.
6. Logout from ESXi Web Interface and login again with the service user credentials in order to
check that the account is operational and addresses the virtual machine created to host the
virtual AW Server:
User: service
Password: the password you specified in Step 4.d.
This completes the installation of the GE Service account.
Proceed to 2.6.4 Setup a NTP server for the Hypervisor on page 43.

42 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.6 Job Card IST001AB - Hypervisor Configuration

2.6.4 Setup a NTP server for the Hypervisor

It is recommended to configure a NTP server on each Hypervisor that will host the AWS Virtual
Machine.
Below are the instructions to configure a NTP server on a single Hypervisor.
2
The correct time is essential to your Hypervisor, you will need it for a variety of reasons (syslog, iscsi
authentication and Security) and your Virtual Clients.

Installation of a new AW Server

1. Make sure you are logged on the vSphere Web Client as administrator.
2. In the main vSphere Web Client screen:

a. Select the Hypervisor and click on the Configure tab.

b. Expand the System sub-menu and click on Time Configuration.
c. Click on the Edit button.
3. Configure and start the NTP server on the Edit Time Configuration screen:
a. Select the Use Network Time Protocol (Enable NTP client) radio box.

b. In the NTP Servers field, enter the site’s NTP server name (I.e: ntp.pool.org) or NTP server’s
IP address.
c. Set the NTP Service Startup Policy to Start and stop with host
d. Start the NTP service by clicking on the Start button.
e. Click on OK to complete the NTP server installation.
4. Verify that the NTP service has been started and is running.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 43

2.7 Job Card IST001B - Virtual Machine creation

5. The GEHC FE shall be provided with the IP address of the NTP server that was used, so that he
will be able to set it in the Virtual AW Server once installed.
This completes the installation of a NTP server for the Hypervisor.
This completes the Hospital IT Admin Hypervisor installation and configuration steps.
Proceed to 2.7 Job Card IST001B - Virtual Machine creation on page 44.

2.7 Job Card IST001B - Virtual Machine creation

2.7.1 Overview
NOTE
For the AW Server integrated within the CT/MR Console Environment (Edison HealthLink
or CT Nano-Cloud), refer to A.12 AW Server Integration in CT/MR Console Environment on
page 433.
This section applies to the Virtual Machine creation on a customer’s physical server.
All sections are performed and completed by the IT Administrator of the site.
Pre-requisite:
The Hypervisor is installed and configured. See section 2.6 Job Card IST001AB - Hypervisor
Configuration on page 33.
Preliminary Steps:
1. The GEHC FE makes sure what type of Virtual AW Server has been purchased by the site and
delivers the following information to the IT administrator of the site.
• Low Tier or High Tier virtual AW Server (needs additional step to upgrade the default Low
Tier VM to High Tier VM - See section 2.7.2.2 Steps to upgrade / downgrade a Virtual
Machine on page 51).
• Integrated or Standalone (Non-Integrated) virtual AW Server (Standalone or Hybrid
integration AW Server needs additional step to create hard disk for Image data - see section
2.7.2.4 Image data disk creation for Standalone (Non-Integrated) virtual AW Server on page
53)
• AW Server part of a cluster of virtual AW Servers (Scalability).
It is necessary to also create two VMs to host the HAPS (Preferences Sharing) servers.
• See section 2.7.2.2 Steps to upgrade / downgrade a Virtual Machine on page 51 to
downgrade the Low Tier VM to HAPS server VM

44 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.7 Job Card IST001B - Virtual Machine creation

• Virtual servers in cluster mode need two dedicated physical network ports (1 for
hospital network communication and 1 for AW Server Private network communication
between the AW Servers and HAPS). See 2.8 Job Card IST001C - Virtual Servers Cluster
Installation Steps on page 56 for Scalability network setup.
2. The GEHC FE delivers the media necessary for VM creation and OS installation and the media
necessary for AW Server installation to the IT administrator of the site.
2
Prepare the OVF Template software media that will be needed for installation:

Installation of a new AW Server

Refer to the Software Kit content in section 1.3 Software Kit on page 4.
NOTE
When installing from electronic files, always refer to AW eDelivery Service Guide
5761599-8EN for detailed instructions.
AW Server VM creation process summary:
NOTE
Hyperthreading needs to be turned off on the Hypervisor to optimize the
performances of the AW Server and the 3D applications. Indeed, the software is
optimized for CPU settings with Intel Xeon architecture and without hyperthreading. So, it
is recommended to deactivate the Hyperthreading on AW Server. Therefore, it is not
appropriate to have other customer’s VMs running on the same Hypervisor, if these other
VMs require Hyperthreading to be activated, otherwise it could impact the AW Server
performances.
1. The GE FE gives the site IT administrator, the OVF template software media (5720xxx USB key
or 5720625 DVD) that is needed for creating the Virtual machine, aimed to host the virtual AW
Server.
The GE FE also delivers the following installation instructions to the site IT administrator. The
OVF Template creates the Low Tier Virtual machine with the required characteristics to host the
virtual AW Server, and loads the Linux OS and the AW Server (in case of USB key) at the same
time.
2. The IT admin connects to the Hypervisor.
3. The IT admin installs and configures the Hypervisor environment. See section 2.6 Job Card
IST001AB - Hypervisor Configuration on page 33.
4. The IT admin loads the OVF template and creates the virtual machine (Low Tier) - Section
2.7.2.1 OS Template (OVF) Installation on page 47
5. If the site has purchased a High Tier virtual AW Server, the GE FE notifies the IT admin that
section 2.7.2.2 Steps to upgrade / downgrade a Virtual Machine on page 51 shall be performed,
in order to upgrade the Low Tier VM into a High Tier VM.
If not, proceed to next step.
6. If the site has purchased a virtual AW Server cluster solution, the GE FE notifies the IT admin
that, in addition to the AW Servers VMs, two HAPS server VMs shall be created from the
Template, and that section 2.7.2.2 Steps to upgrade / downgrade a Virtual Machine on page 51
shall be performed, in order to downgrade the Low Tier VM into a HAPS server VM.
If not, proceed to next step.
7. The GE FE notifies the IT admin that section 2.7.2.3 Disconnect the second Network Adapter on
page 52 shall be performed, so that the second Network Adapter, used to ensure
communication between the nodes (virtual AW Server) that are part of a cluster, is not be
connected at the power on.
8. If the site has purchased a Standalone (Non-Integrated) virtual AW Server, the GE FE notifies the
IT admin that section 2.7.2.4 Image data disk creation for Standalone (Non-Integrated) virtual

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 45

2.7 Job Card IST001B - Virtual Machine creation

AW Server on page 53 shall be performed, in order to create a virtual Hard disk to store the
image data.
NOTE
The steps are described for VMware hypervisor (ESXi) with VMware vSphere Web
Client. To have the equivalent steps using VMware vSphere Client, refer to Appendix
A.6 VMware Support on page 378. And if needed, refer to VMware documentation for
more details.

2.7.2 Virtual machine creation

The IT Administrator of the site is responsible for installing, and configuring on-site a fully-functional
Virtual machine with the appropriate characteristics for hosting the virtual AW Server. The IT
Administrator of the site is also responsible for providing an "hypervisor" account for GE service, so
that the GEHC FE is able to administrate (load software, configure, etc..) the virtual machine which
will host the virtual AW Server.
Pre-requisite:
Ask the IT administrator of the site for the network parameters necessary for your virtual AW Server
and its environment.
• IP address of the Hypervisor.
• IP addresses and netmasks/network prefix to be used for the virtual AW Server.
• IP addresses used for the PACS.
• IP addresses used for the remote hosts (if applicable).
• IP addresses used for the printers (if applicable).
IP address checklist:

Description IP address Netmasks / Hostname AE Title DICOM Port

Network
prefix
Management network N/A N/A N/A N/A
(Hypervisor)
vAW Server eth0 4006
(hospital network)
vAW Server eth1
optional: private network for
Cluster of AWS
PACS (hospital network) N/A N/A
PACS (hospital network) N/A N/A N/A
(Storage commitment)
External License N/A N/A N/A N/A
server #1
External License N/A N/A N/A N/A
server #2
Remote Host #1
Remote Host #2
Remote Host #3
Remote Host #4

46 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.7 Job Card IST001B - Virtual Machine creation

Remote Host #5
DICOM printer #1
PostScript printer #1

2.7.2.1 OS Template (OVF) Installation

The OVA/OVF Template allows creating a VM (virtual machine) with the required characteristics 2
(virtual memory, number of virtual CPUS, etc...) for the Low Tier AW Server, and install at the same

Installation of a new AW Server

time the Linux OS.
1. Insert the OS Template media into the PC.
2. Make sure you are logged on the vSphere Web Client as administrator.
3. Right click on the Hypervisor and select Deploy OVF Template...

The Deploy OVF Template wizard displays.

4. Select Local file and click on the Browse button to locate the .OVA file from the OVF Template
media, then click on the Open button to select.

5. Click on Next.
NOTE
The identification of the release that you want to install may be different from the
one shown in the example.
The Select name and location panel displays.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 47

2.7 Job Card IST001B - Virtual Machine creation

6. Enter a name for the Virtual Machine: I.e: AWS3_VM01 (for first VM) ; AWS3_VM02 (for next) , etc.
7. Select the datacenter where you want to deploy the OVF template.
8. Click on Next.
The Select a resource panel displays.
9. Select the Hypervisor where you want to run the deployed template.
10. Click on Next.
The Review details panel displays.

11. Click on Next.

The Select storage panel displays.
12. AW Server / HAPS server VM creation: Accept the default virtual disk format settings (Thick
Provision Lazy Zeroed).
13. Select Show datastores from Storages DRS clusters check box, to be able to choose
individual datastores.
14. Click on Datastores.
15. Choose a Datastore that will host the VM (see example below):

48 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.7 Job Card IST001B - Virtual Machine creation

NOTE
For information about Disk Format, see: https://pubs.vmware.com/vsphere-50/
index.jsp?topic=
%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-4C0F4D73-82F2-4B81-8AA7-1D
D752A8A5AC.html
16. Click on Next.
2
The Select networks panel displays. It allows to map the destination network for each source
network.

Installation of a new AW Server

17. On the Hospital Network line, select the Destination network from the scroll-down menu. The
name of the destination network corresponds to the port group you have created or identified in
2.6.2 Ethernet ports Allocation on page 35 Section. As a reminder, this port group has to be
associated with at least one physical network card dedicated to AW Server VM
18. On the Private AWS Network line, select the Destination network from the scroll down menu.
• For a single virtual AW Server, select the same destination network as for Hospital
Network. This network will not be used by the VM.
• Alternatively, you can also associate this second virtual network card to a port group with
no physical network card.
• For a virtual AW Server part of a cluster, select the destination network that corresponds to
the virtual switch you created for private network.
19. NOTE
You can change these parameters at a later time by editing the VM settings if needed.
Click on Next.
The Ready to complete panel displays with the Virtual Machine details.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 49

2.7 Job Card IST001B - Virtual Machine creation

20. Click on Finish to accept and start the VM creation.

The Deploying OVF Template task appears in the Recent Tasks section at the bottom of the
page. A status bar lets you know about the deployement progress.
It will take several minutes to complete.
21. After the task status displays as Completed, eject the DVD from the drive and store it in a safe
place.
22. Check that the Virtual Machine has been associated to the right physical network card:
a. Select the Hypervisor if not already done.
b. Click on the Configure tab.
c. Expand the Networking sub-menu.
d. Click on Virtual switches.
The configuration should be similar to the following:

Proceed to section 2.7.2.2 Steps to upgrade / downgrade a Virtual Machine on page 51.

50 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.7 Job Card IST001B - Virtual Machine creation

2.7.2.2 Steps to upgrade / downgrade a Virtual Machine

Depending on the type of virtual AW Server purchased by the site you may have to upgrade or
downgrade the virtual AW Server.
The upgrade / downgrade of a Virtual Machine consists of updating the VM memory and/or CPU.
Refer to 2.4.1 Virtual Machine characteristics per integration mode on page 14 to update the VM 2
memory and/or CPU to the right values.

Installation of a new AW Server

The below steps are performed for the upgrade of a Low tier VM into a High Tier VM. For the
downgrade of a VM, the steps are similar.
1. Display the Edit Settings panel:
Right click on the Virtual Machine you have created under the Hypervisor, and that you want to
upgrade / downgrade, and select Edit settings.
2. Update the VM memory:
In the Virtual Hardware tab select Memory from the list and set the memory size to 64GB.

3. Update the VM CPU:

In the Virtual Hardware tab select CPU from the list and set the CPU number to 24.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 51

2.7 Job Card IST001B - Virtual Machine creation

NOTE
To achieve the proper CPU number necessary to set core numbers to 24, select 3
virtual sockets and 8 core per sockets.
4. Click on OK.
Proceed to section 2.7.2.3 Disconnect the second Network Adapter on page 52.

2.7.2.3 Disconnect the second Network Adapter

A second Network Adapter has been configured. This Network Adapter is used to ensure
communication between the nodes (virtual AW Server) that are part of a cluster, through the AW
Server Private network.
This second Network Adapter should not be connected at the power on of the Virtual Machine.
1. Display the Edit Settings panel:
Right click on the Virtual Machine and select Edit settings.
2. Disconnect he second Network Adapter:
In Virtual Hardware tab select Network adapter 2 from the list and uncheck the Connect At
Power On check-box.

52 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.7 Job Card IST001B - Virtual Machine creation

Installation of a new AW Server

NOTICE
DO NOT disconnect Adapter 1
3. Click on OK.
Proceed to section 2.7.2.4 Image data disk creation for Standalone (Non-Integrated) virtual AW
Server on page 53.

2.7.2.4 Image data disk creation for Standalone (Non-Integrated) virtual AW

Server
Perform this section if the site has purchased a Standalone (Non-Integrated) virtual AW Server. The
purpose is to create a virtual hard disk partition to store the image data.
If the site has purchased an "integrated" virtual AW Server, it does not need a disk partition to store
image data.
In this case, proceed to 2.9 Job Card IST002B - Virtual Machine Installation Verification on page 63.
1. Create a new SCSI controller. The new image data disk will have a separate SCSI controller.
a. Right click on the Virtual machine and select Edit settings.
The Edit Settings screen displays.
b. In the Virtual Hardware tab, set New device to SCSI Controller and click on Add.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 53

2.7 Job Card IST001B - Virtual Machine creation

The New SCSI controller item appears.

2. Configure the new SCSI controller:
a. Expand the New SCSI controller item.
b. Set Change Type of SCSI controller to LSI Logic SAS.
c. Verify the setting and click on OK.
3. Create a new hard disk:
a. Right click on the Virtual machine and select Edit settings.
b. The Edit Settings screen displays.
c. In the Virtual Hardware tab, set New device to New Hard Disk and click on Add.

54 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.7 Job Card IST001B - Virtual Machine creation

Installation of a new AW Server

The New Hard disk item appears.
4. Configure the new hard disk:
a. Expand the New Hard disk item.
b. Set the Disk size to:
• 1TB (minimum recommended size)
• 6TB (recommended and maximum supported size)
c. Set the Location of disk image by selecting Store with the virtual machine (default
setting) or select Browse to specify a datastore or datastore cluster (see next step).
d. Set Disk Provisioning to Thick Provision Lazy Zeroed (default setting).
e. Set Disk Mode to Independent - Persistent.
f. Set Virtual Device Node to SCSI controller 1 and SCSI (1:0). The image data disk will
have a separate SCSI controller.
g. Verify the setting and click on OK.
h. Apply the datastore recommandations in the screen that displays.
NOTE
To help for proper choice see: https://pubs.vmware.com/vsphere-50/index.jsp?topic=
%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-4C0F4D73-82F2-4B81-8AA7-1D
D752A8A5AC.html.
5. When selecting a different datastore (select Browse in Location), you will get the following
screen:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 55

2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps

a. Select the Disable Storage DRS for this virtual machine check box.
b. Select the appropriate datastore.
c. Click on OK.
6. Right click on the Virtual machine and select Edit settings.
In the Virtual Hardware tab, now you can see a new SCSI Controller and a new Hard Disk. This
completes the installation of the Virtual machine.
Proceed to 2.9 Job Card IST002B - Virtual Machine Installation Verification on page 63.

2.8 Job Card IST001C - Virtual Servers Cluster

Installation Steps

2.8.1 Foreword
Scalability mode (or cluster mode) is the ability to have several AW Servers working as one more
powerful AW server (currently limited to a maximum of 30 “virtual” AW Servers). The behavior is
“transparent” for the user, who will be automatically directed to the appropriate server (less loaded)
when logging in.
If your site is going to have a cluster of two or more virtual AW servers, you need to set up each of
the servers in the "Cluster mode". Proceed as follows and repeat this operation on each of the other
virtual AW servers.
Currently, the Scalable mode is only supported with virtual AW Servers.

2.8.1.1 Pre-requisites for setup

The second Ethernet port/card shall be available to allow network Broadcast traffic through the
“Private” network.
If this condition is not met, you will get the message "Could not set Cluster mode" while attempting
to setup the Cluster mode.

2.8.1.2 Pre-requisites for Cluster operation

The following are pre-requisites for proper operation of Scalability. However the AW Servers can be
setup for Scalability before the pre-requisites are met, but will not behave as so until the pre-
requisites are met.
• Two HAPS (High Availability Preferences Sharing) nodes shall be created within the cluster, in
order to host and share between the AW Servers, the Preferences created by the users.
• The AW Servers shall be fully licensed.
• All AW Servers in the cluster must run the same SW version for both:
• The AWS platform software
• The Applications software

56 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps

These conditions are checked by the "Golden set" feature, and cluster operation will not be
permitted if those conditions are not met.
• The same Applications are installed and licensed on all AW servers of the cluster. Refer to
2.17 Job Card IST009 - External Application(s) Installation on page 132.
• Pre-processing is optional. If it has been purchased for the site, it shall be available and
configured for each AW Server in the cluster (same pre-processing configuration for all AW 2
Servers).

Installation of a new AW Server

• All AW Servers in the cluster must share the same Image database. Therefore, the AW Servers
shall be setup for Seamless and DICOM Direct Connect integration with the PACS. Refer to
2.19 Job Card IST011 - Integration on page 172.
• The License server(s) is/shall be configured and alive - preferably use external license servers to
avoid using one of the AW Servers as License server.
NOTE
It is not necessary that each AW Server in the cluster is declared to the other nodes
as a DICOM host.

2.8.2 Preliminary Steps

The GEHC FE delivers the media necessary for installation to the IT administrator of the site.
All along this section, you will refer to 2.7 Job Card IST001B - Virtual Machine creation on page 44 -
to setup each virtual servers (AW Servers + 2 HAPS servers) that constitute the cluster.

2.8.2.1 Virtual machine resources for AW Server

2.8.2.1.1 High Availability Preferences Server (HAPS)

Thanks to the OVF Template OS DVD, a standard virtual machine for AW Server Low Tier will be
created, from which the virtual machine for HAPS Server will be downgraded in order to meet the
necessary resources to run HAPS Node:
• processor: 1 vCPUs
• disk: one 40GB virtual HDD (min)
• memory: 4GB
• network: Two physical Ethernet ports (1 Ethernet used for Hospital network, one Ethernet used
for AWS Private network)

2.8.2.1.2 AW Server
Thanks to the OVF Template OS media, the standard virtual machine for AW Server Low Tier will be
created with the necessary resources to run AWS Node:
• processor: 8 vCPUs
• disk: one 70GB virtual HDD
• memory: RAM depends on integration mode, see table in section 2.4.1 Virtual Machine
characteristics per integration mode on page 14
• network: Two physical Ethernet ports (1 Ethernet used for Hospital network, one Ethernet used
for AW Server Private network)

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 57

2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps

2.8.2.2 Physical Network configuration

WARNING
AW Servers within the cluster use "Broadcast" to communicate between each other. Therefore,
they must do this broadcast communication on a separate "private" network from the Hospital
network.
Each virtual AW Server as well as each virtual HAPS Server must be linked to two 1Gbps physical
network card (Ethernet port) to ensure proper operation.
• The first 1GB/s physical network card is dedicated to the AW Server, for communication with
the other hosts on the Hospital network (VM Hospital Network).
• The second 1 GB/s physical network card is dedicated to the AW server private scalability
network. It is necessary to connect the virtual AW server to the other virtual AW server(s)
within the same cluster (VM Private AWServer Network).
If there are not enough switches, VMs can share the same switch for the AWS Private network.
NOTE
For the "Private AWS" network, you can use "default standard" Class C network IP
addresses such as 192.1.1.1 - 192.1.1.2 - 192.1.1.3 - etc..., as the Private AWS network
is not connected to the "external world".
NOTE
All virtual AW Servers hosted on the same physical server can share one physical
network port (card) for the AWS private network as in the example below.
NOTE
It is recommended to use a separate NIC for the Management network of the Hypervisor,
in order to ensure that enough bandwidth will be available during template deployment
or other similar operations.

58 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps

Figure 2-6 Example of cluster of 3 virtual AW Servers hosted on the same physical server

Installation of a new AW Server

NOTICE
Two HAPS (High Availability Preferences Sharing) servers VM shall be created through
the OVF Template OS and the AWS Platform software.

NOTICE
In order to ensure proper hardware redundancy, it is strongly recommended that the
two HAPS servers are hosted on different Hypervisor hardware (see hereafter).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 59

2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps

Figure 2-7 Example of a cluster of 3 virtual AW Servers hosted on two different servers
hardware

NOTE
A network switch (or equivalent), isolated from the Hospital network, is necessary to link
the Private AWS network of AW server 1 and 2 with the private AWS network of AW
server 3.
NOTE
Hyperthreading needs to be turned off on the Hypervisor to optimize the
performances of the AW Server and the 3D applications. Indeed, the software is
optimized for CPU settings with Intel Xeon architecture and without hyperthreading. So, it
is recommended to deactivate the Hyperthreading on AW Server. Therefore, it is not
appropriate to have other customer’s VMs running on the same Hypervisor, if these other
VMs require Hyperthreading to be activated, otherwise it could impact the AW Server
performances.

2.8.3 Installation and configuration Steps

The following sections are already described in details in the Job Cards 2.6 Job Card IST001AB -
Hypervisor Configuration on page 33 and 2.7 Job Card IST001B - Virtual Machine creation on page 44
Therefore all the steps are not repeated hereafter, but you will be directed to the appropriate section
of these Job Cards which contains the necessary information for the setup.

60 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps

2.8.3.1 Hypervisor pre-requisites

One Hypervisor must be installed per server hardware aimed to host the virtual machines.
All hypervisors must run the same software version.
Refer to Appendix A.6 VMware Support on page 378 to setup the Hypervisor(s).
2
This step is under the full responsibility of the IT administrator of the site.

Installation of a new AW Server

2.8.3.2 Ethernet ports allocation
For each hypervisor that will host the virtual AW Server, there is one physical network card
dedicated to the AW Server VM.
For a cluster of AW Server VMs, a second physical network card is required on each host.
This step is under the full responsibility of the IT administrator of the site.
Refer to 2.6.2 Ethernet ports Allocation on page 35.

2.8.3.3 GE Service account setup

A GE Service account must be created so that the GEHC FE has all necessary permissions to
administrate each virtual machine hosting a virtual AW Server and/or a HAPS server.
This step is under the full responsibility of the IT administrator of the site.
Refer to 2.6.3 Create a GEHC service user account on page 39.

2.8.3.4 NTP server setup for the Virtual AW Servers / HAPS servers
Time synchronization through a NTP server is a “must” for scalability. The NTP server must be setup
for each virtual machine hosting a virtual AW Server or a HAPS server.
This step is under the full responsibility of the IT administrator of the site.
Refer to 2.6.4 Setup a NTP server for the Hypervisor on page 43.

2.8.3.5 Virtual Machine (VM) creation

Each VM aimed to host one virtual AW Server must be created from the OS (OVF) Template media.
This step is under the full responsibility of the IT administrator of the site.
Refer to 2.7 Job Card IST001B - Virtual Machine creation on page 44.

2.8.3.6 AW Server / HAPS server installation and configuration

Once each virtual machine has been created by the IT administrator of the site, and a GE Service
account is available to administrate each virtual machine, the GEHC FE will load and configure (if not
already done during VM creation) either the HAPS server software or the AW Server. Then he/she
will verify the VMs created and finally load the Applications software.
These steps are under the full responsibility of the GEHC FE.

2.8.4 Scalability Installation Checklist

2.8.4.1 Under Site IT administrator responsibility

1. Allocate the Network resources.
Refer to section 2.6.2 Ethernet ports Allocation on page 35.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 61

2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps

Make sure one physical network port is available for each VM (AW Server and HAPS server for
the Private AWS network).
Make sure one physical network port is available for each VM (AW Server and HAPS server for
the hospital network).
NOTE
If the VMs are on the same Hypervisor, they can share one single physical network
port for the AWS private network.
2. Setup a GE Service account with appropriate permissions to administrate the HAPS and AW
Server VMs.
Refer to 2.6.3 Create a GEHC service user account on page 39.
3. Make sure the NTP server is up and running.
Refer to 2.6.4 Setup a NTP server for the Hypervisor on page 43.
4. Virtual Machines creation.
Refer to 2.7 Job Card IST001B - Virtual Machine creation on page 44.
a. Create the HAPS Server 1 VM from the OVF template.
b. Downgrade the VM to match HAPS VM characteristics.
c. Create the HAPS Server 2 VM from the OVF template.
d. Downgrade the VM to match HAPS VM characteristics.
e. Create the AW Server 1 VM from the OVF template.
f. Create the AW Server 2 VM from the OVF template.
g. Create the AW Server n VM from the OVF template.

2.8.4.2 Under GEHC FE responsibility

1. VM creation verification:
Refer to 2.9 Job Card IST002B - Virtual Machine Installation Verification on page 63.
a. Login with the GE service account credentials.
b. Start and verify the AW Server and HAPS VMs.
2. HAPS Platform software installation:
Refer to 2.10 Job Card IST003 - Installation of Platform Software on page 67.
a. From the AWS platform DVD, install HAPS server 1 and setup Network and Time
parameters.
b. From the AWS platform DVD, install HAPS server 2 and setup Network and Time
parameters.
3. AWS platform software installation:
Refer to 2.10 Job Card IST003 - Installation of Platform Software on page 67.
a. From the AWS platform DVD, install AW Server #1 and setup Network and Time
parameters.
b. From the AWS platform DVD, install AW Server #2 and setup Network and Time
parameters.
c. From the AWS platform DVD, install AW Server #n and setup Network and Time
parameters.
4. VM Tools install:

62 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.9 Job Card IST002B - Virtual Machine Installation Verification

Refer to 2.12 Job Card IST004B - Installation of VMware Tools on page 86.
For each VM (2 x HAPS VM + n AW Server VMs), install the VM Tools.
5. Login to and configuration of the AW Servers.
• For Seamless Integration: Dakota plugin loading: Refer to 2.19 Job Card IST011 - Integration
on page 172.
• Initial Configuration: Refer to 2.16 Job Card IST008 - Initial Configuration on page 108.
2

Installation of a new AW Server

6. Load and install the Applications:
Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132.
Load and install the VV Apps Applications from media.
7. Integration configuration:
Refer to 2.19 Job Card IST011 - Integration on page 172
a. Configure integration on the AW Server side.
b. For Seamless Integration: Configure integration on the UV side.
8. Administrative configuration:
Refer to 2.18 Job Card IST010 - Administrative Configuration on page 148.
a. Configure remote hosts and printers (if applicable).
b. Configure Users.
c. Configure Pre-processing and End Of Review.
9. Service Tools configuration:
Refer to 2.21 Job Card IST013 - Service Tools Configuration on page 200.
a. Register Configuration and obtain the registration key.
b. Exit the Maintenance mode.
10. Scalability configuration:
Refer to 2.20 Job Card IST012 - Virtual Servers Cluster Configuration on page 196.
a. Check the cluster configuration and that the HAPS are up and running.
b. Configure the Goldenset.
11. Client install:
Refer to 2.23 Job Card IST014B - Seamless Client PC installation and Tests on page 226.
a. Download and Install the Solomini client.
b. Launch the Universal Viewer and create a 3D Apps button (for Seamless integration).
c. Launch the AW Server Client / 3D applications.
12. Final steps:
• Refer to 2.24 Job Card IST015 - Final Settings on page 240.
• Refer to 2.25 Job Card IST016 - System Handover to Customer on page 246.

2.9 Job Card IST002B - Virtual Machine Installation

Verification
This Job Card only applies for Virtual servers installed by the IT administrator of the site.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 63

2.9 Job Card IST002B - Virtual Machine Installation Verification

It DOES NOT apply for the hardware based AW Server (refer to 2.5 Job Card IST001A - Hardware
Installation Verification on page 22).
The steps described in this Job Card shall be completed under the full responsibility of the
GEHC FE for each Virtual machine created.

NOTICE
*** IMPORTANT PROCESS REQUIREMENT ***
• Any deficiencies or hardware failures found while executing the following verification process
must be IMMEDIATELY reported to the GEHC OLC support team and the site IT admin, to be
resolved prior to GEHC Service accepting ownership of the system, and installing the AW Server
software!!!
• Additionally, the GEHC FE is required to overlap with the IT administrator of the site during
these final checks to also observe and ensure proper hardware readiness.
• In an event requiring the IT administrator of the site to resolve an installation hand-off problem,
the GEHC FE should "break off "and not log the IT administrator resolve time against the GEHC
installation. Training time can be logged if the GEHC FE desires to observe – but not actual
installation time until the hand-off is successful.
Time Reporting for Installation & Warranty
The business intent is to accurately measure product quality by having reliable service installation
and warranty records and metrics.
The AW Server TOTAL installation is designed to be completed within roughly one work shift -
approximately:
Virtual AW server - 5 to 8 hours, with:
• 1 to 2 hours for the VIRTUAL machine creation (incl. OS load) by the IT admin of the site
• 4 to 6 hours for the AWS Software / Configuration (GEHC) installation.
This includes one hour of overlap time for the GEHC FE to engage the IT admin, and to acquire site
readiness and installation status information.
• Charge any system malfunction / troubleshooting and repair time to the appropriate warranty
service class (10 or 11).

NOTICE
When a Virtual Machine (VM) is created, a MAC address is automatically created for
this VM. From this MAC address, the "LicenseId" is created, that will be used to
calculate from the eLicense web site the license keys for the AW Server platform,
Integration, Pre-processing option, Applications, etc...
This VM and MAC address creation happened while loading the OS from the OS OVF Template
media. Therefore the VM must never be deleted, otherwise the MAC address will be lost, and
consequently the keys for all AWS applications.
That is the reason why you are provided with the OS DVD media for Virtual machine - To be used to
reload the OS in case it will be necessary to do so.

2.9.1 Retrieve the MAC address

This section describes the ways to retrieve the MAC address of a Virtual Machine.
A MAC address shall be of the form XX:XX:XX:XX:XX:XX. I.e: 00:01:0c:07:ac:88

64 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.9 Job Card IST002B - Virtual Machine Installation Verification

NOTE
The steps are described for VMware hypervisor (ESXi) with VMware vSphere Web
Client. To have the equivalent steps using VMware vSphere Client, refer to Appendix
A.6 VMware Support on page 378. And if needed, refer to VMware documentation for
more details.
1. Get the MAC address from a terminal: 2
a. Open a terminal, login as root.

Installation of a new AW Server

b. Type in: ip addr show eth0 <Enter>

2. Get the MAC address from the ESXi Web Interface (when the VM is not started):
a. Connect to the ESXi Web Interface. In the ESXi Web Interface login screen (https://<ESXi URL
or IP>/), login as service.
b. Display virtual machine’s MAC address.
• Click on Virtual Machines on the left side of the page and click on your virtual machine
name in the list of virtual machines that displays.

• Then select the icon.

• In the Edit settings screen, expand the Network Adapter 1 item to display the MAC
address.

Note the MAC address. Indeed, it is requested to:

• Enter the eLicense web site and calculate the keys associated to your GON (Global Order
Number). Refer to A.3 eLicensing on page 362 for more information on eLicense, or wait until
the AW Server platform software has been loaded, so that you can get access to the HealthPage
and/or use the command licenseId that will display the license ID.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 65

2.9 Job Card IST002B - Virtual Machine Installation Verification

2.9.2 Virtual machine verification

NOTE
The steps are described for VMware hypervisor (ESXi) with VMware vSphere Web
Client. To have the equivalent steps using VMware vSphere Client, refer to Appendix
A.6 VMware Support on page 378. And if needed, refer to VMware documentation for
more details.
The following steps shall be done at the Client PC.
1. Connect to the ESXi Web Interface. In the ESXi Web Interface login screen (https://<ESXi URL or
IP>/), login as service.
The ESXi Web Interface page displays.
2. Display the virtual machine’s characteristics:
a. Click on Virtual Machines on the left side of the page.
b. Click on your virtual machine name in the list of virtual machines that displays.

The IT admin may have changed the default VM name to any name at their convenience,
especially if there are several virtual AWS on the same server hardware.
If needed, right click on the virtual machine name and select Rename to change the VM name.
3. Check that the virtual machine’s characteristics are as shown in the example below:
• Red Hat 6 (64-bit ) OS
• Virtual CPU: 8 vCPU (low tier VM) or 24vCPU (high tier VM) or 1vCPU (HAPS VM)
• Memory: 24GB (low tier VM) or 64GB (high tier VM) or 4GB (HAPS VM)
• Check that there are 1 or 2 virtual hard disks
• At least 70GB storage (for system)
• Maximum 6TB storage (for image filesystem - Standalone (Non-Integrated) virtual AW
Server only)
Memory overhead and Storage parameters values change from one configuration to another.
This completes the Virtual machine installation verification.

66 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

Proceed to 2.10 Job Card IST003 - Installation of Platform Software on page 67.

2.10 Job Card IST003 - Installation of Platform

Software
2
2.10.1 AWS Platform software load preparation

Installation of a new AW Server

2.10.1.1 Physical AW servers
The steps are done at the Server side. Alternatively, software loading can also be done at the Client
PC, through the iLO service processor. Refer to A.7 Software Loading Through iLO on page 410.
At time of release of this manual, the AWS platform media is as follows:
• 5720631 (or up) - AW Server SW & Docs DVD >>> Media part number: 5719780-20 (or up)

2.10.1.2 Virtual AW Server

The steps are done at the Client PC.
At time of release of this manual, the AWS platform media is as follows:
• 5720634 (or up) - AW Server SW & Docs DVD for VM >>> Media part number: 5719780-30 (or
up)
NOTE
The steps are described for VMware hypervisor (ESXi) with VMware vSphere Web
Client. To have the equivalent steps using VMware vSphere Client, refer to Appendix
A.6 VMware Support on page 378. And if needed, refer to VMware documentation for
more details.
Map the AWS Platform ISO file from the AWS Platform DVD (or the USB media) to the virtual CD/DVD
drive and display the Virtual Machine Console.
1. Insert the AWS platform DVD into Client PC DVD drive, or insert the USB media containing the
AWS Platform software into a USB port of the PC (if not already done).
2. Connect to the ESXi Web Interface:
a. Open a Web browser and enter the URL or IP address of the ESXi:
https://<ESXi URL or IP>/
The ESXi Web Interface login screen displays:

b. Login as service.
The ESXi Web Interface page displays.
3. Display the list of Virtual Machines:
Click on Virtual Machines on the left side of the page.
The list of Virtual Machines displays on the right side of the page.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 67

2.10 Job Card IST003 - Installation of Platform Software

4. Map the iso file to the virtual CD/DVD drive from the Virtual Machine Console:

a. Select your Virtual Machine, then click on the icon.

The Edit settings screen displays.

b. In the Virtual Hardware tab select CD/DVD Drive 1 (or the corresponding name for your
VM) from the list.
c. If not already selected, select Datastore ISO file from the dropdown list. Otherwise, click
on the Browse button.
d. In the screen that displays:

68 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

Installation of a new AW Server

• If the iso file is not already uploaded:
• Select the datastore where you want to copy the iso file and click on Upload.
• Browse to the DVD drive or the USB device of the Client PC. Select the iso file, then
select Open.
• Once uploaded, select the iso file and click on the Select button.
e. In the Edit settings screen check the Connect radio button.
f. Click on Save button.
5. Start the Virtual Machine and/or display the Virtual Machine Console by clicking on the Console
screen shot (here the white arrow if the Virtual Machine is not already started).

The virtual AW Server OS starts booting up (if not already started) and the Virtual Machine
Console opens.
NOTE
When the Virtual Machine is started, you can also display the Virtual Machine
Console by clicking on Console > Open browser console or directly on the Console
screen shot.
NOTE
To work with the Virtual Machine Console, simply click into the console field.
If the screen is black or locked press <Ctrl> .
To display the boot sequence while booting press <Ctrl> and <-> simultaneously.

2.10.2 AWS platform software load

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 69

2.10 Job Card IST003 - Installation of Platform Software

1. When the boot sequence has completed, click into the console field and login as root.
The following screen pops up:

2. Mount the platform DVD:

Press <Enter>
3. When the Platform DVD mounted successfully a messsage displays, press <Enter> again.
The platform installation utility interface should display, as shown below:

4. Press <Enter> to continue with the installation.

The following screen displays:

5. Network configuration: Obtain all necessary network configuration information from the site IT
Admin.
Refer to A.2 Specific field - Characters rules and limitations on page 361 for characters rules and
limitations.
a. Keep <Setup> selected and press <Enter>
b. Enter the network information in the screen that displays:

70 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

Installation of a new AW Server

• Enter the Hostname (followed by "dot" Domain_name if applicable).
(I.e: aws-DL560.euro.health.ge.com )
• Press arrow down to the IP address, Netmask and Default Gateway fields to enter
the parameters.
• Scalability case: Cluster of virtual AW servers. If applicable, enter the parameters for
the second Ethernet (AWS Private network). This shall be done for both the AW Server
VML and the HAPS server VM. For more information on scalability, refer to 2.20 Job
Card IST012 - Virtual Servers Cluster Configuration on page 196.

• If applicable, enter the parameters for the DNS server(s).

• When done, tab down to select <OK> and press <Enter> to save the configuration.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 71

2.10 Job Card IST003 - Installation of Platform Software

c. The following message pops up again:

If you are done with the Network configuration, now select <Skip> and press <Enter>
6. Date and Time Configuration.

a. Keep <Setup> selected and press <Enter>

b. Enter the date and time information in the screens that display:
• Type the number corresponding to the region where your AW Server will be installed,
and press <Enter>:

• For instance, after selecting 2 for Americas the following screen displays:
Type the number corresponding to the country where your AW Server will be installed,
and press <Enter>:

72 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

Installation of a new AW Server

• For instance, after selecting 50 for US the following screen displays:
Type the number corresponding to the Time zone region where your AW Server will be
installed, and press <Enter>:
Check with the IT admin of your site what Time zone shall be configured.

NOTE
This step is required for countries having several Time zones.
• When done, the following screen will display to let you modify the Date and Time if
necessary:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 73

2.10 Job Card IST003 - Installation of Platform Software

• Check or modify the date accordingly.

• Press arrow down to check or modify the time accordingly.
• When done, tab down to select <OK> and press <Enter> to save the
configuration.
c. The following message pops up again:

If you are done with the Time zone configuration, now select <Skip> and press <Enter>
7. When done, the system continues the software loading.
The message Image partition must be checked may display briefly.
The Image partition configuration screen displays.

8. Image partition configuration:

• Select Keep and press <Enter> to preserve existing images (upgrade / reinstallation case).
In this case the image filesystem will be kept as "Ext3" type (upgrade case).

74 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

• OR

NOTICE
Preferably select Erase and press <Enter> (new installation case or
upgrade / reinstallation case when the customer agrees that existing images
can be deleted). In this case the image filesystem will be created as the new
"Ext4" type (faster than Ext3 filesystem) -------- Recommended setting !!! 2
--------

Installation of a new AW Server

NOTE
If the following screen displays, it means that there were already some data on the
image disks array that cannot be used. In this case, acknowledge the message by
selecting <OK> and pressing <Enter> to return to the previous menu, then choose
Erase to delete image data from the disks and recreate the partitions.

9. If you choose to erase the Image partition, the following confirmation screen displays. Select
Yes and press <Enter> to confirm image partition deletion and re-creation as Ext4 filesystem
type.

10. Virtual machines only:

The following menu ONLY SHOWS when you install a virtual machine to let you choose between
an AW Server installation or a Preference Storage server.
Highly Available Preference Storage servers (HAPS) are aimed to serve Preferences between the
virtual AW servers within a cluster (Scalability).

• To install an AW Server, select AW Server and press<Enter>, then continue with the next
installation steps. OR

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 75

2.10 Job Card IST003 - Installation of Platform Software

• To install a HAPS server, select HA Filesystem Server using the keyboard arrow key, then
press<Enter> and jump to HAPS Server installation.
11. AWS Platform software installation starts. Various progress screens display with self-
explanatory status indicators of the installation progress.

NOTE
Installation of the 090.os package may take several minutes when the image
partition is not empty. Please be patient.
12. When all packages are installed, the following message displays:

"Installation completed ...

All packages installed with success.
Please press <Enter> to continue"
Press <Enter> to continue.
13. When the load process completes, the Status Result box (shown in the following illustration)
displays.

76 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

Use the keyboard arrow keys or the <Space> bar to scroll through all the package installation
results and verify that all the packages were installed successfully.
14. If any package reports as Failed, reload the AWS software as a first step (restart at Step 1). If it
fails again, reload the Operating System (OS), then reload the AWS software.
15. After you check all packages are successfully installed, press <Enter> to continue.
A EA3 password change window pops up informing that you need to change passwords for the 2
standard, admin and limited users.

Installation of a new AW Server

16. Press <Enter>.
A prompt asks you to type the new password for the admin user.

17. Refer to 2.14 Job Card IST006 - Changing the Passwords on page 93 for the password change
guidelines.
• Enter the new admin user password and press <Enter> to continue.
• NOTE
If the customer wants to keep the default passwords, select the Cancel button
and press <Enter> to quit.

Then, select Yes and press <Enter> to confirm.

A prompt asks you to type again the new password for the admin user.

18. Enter again the new admin user password and press <Enter> to confirm.
If the password is successfully updated, a notification appears.

If the password does not comply with the password policy, the rules display and you have to
enter a new password.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 77

2.10 Job Card IST003 - Installation of Platform Software

19. Repeat the procedure (from Step 16 to Step 18) for the standard and limited users.
Unmounting media followed by Installation Completed messages display.
20. Press <Enter>.
21. If the system doesn't reboot, type reboot and press <Enter>.
NOTE
Once you have pressed <Enter> to exit, YOU CANNOT GO BACK TO SCROLL
THROUGH THE RESULTS LIST!
The AW Server reboots.
22. When the AW Server completes the reboot sequence, login as root.
23. Details of the installation results can be viewed in the Service Tools in Diagnostic > Log Viewer
or with the following commands in the command prompt:

Command Result
cat /var/tmp/AweResults.out <Enter> Synthesized list of results of AWS platform software
installation
cat /var/tmp/awe_out.log <Enter> Detailed list of results of AWS platform software
installation
cat /var/tmp/awe_error.log <Enter> List of errors during AWS platform software
installation

24. Verify the partitioning after the AWS load. Note that the Used and Available values may
slightly differ from those displayed below, valid at the time of release of this manual.
df -k <Enter>
Example 1 below is for the HPE ProLiant DL360 Gen9 Server High Tier or HPE ProLiant DL360
Gen10 Server High Tier.
It is similar for a Standalone (Non-Integrated) virtual AW Server (smaller /export/home1
filesystem)

It is also similar for the HP Low Tier servers, but with a smaller image filesystem size (/export/
home1).
For an integrated virtual AW Server, it will slightly differ as there is no image data disk (no image
filesystem: /export/home1).

78 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

25. Virtual server case only: Disconnect the iso file from the CD/DVD virtual drive:

a. Select the Virtual Machine, then click on the icon.

The Edit settings screen displays.
b. In the Virtual Hardware tab, in front of CD/DVD Drive 1 (or the corresponding name for
your VM) uncheck the Connect radio button. 2
c. Click on the Save button.

Installation of a new AW Server

d. The following message may displays:

The guest operating system has locked the CD-ROM door...

Select the Yes check box then click on the Answer button.
26. Physical server case only:
a. Verify that the iLO and the default gateway have been configured with the site-assigned
static IP address designated by the site admin, with the following command:
/sbin/hponcfg -w /tmp/asd <Enter>
grep IP /tmp/asd <Enter>
I.e: <IP_ADDRESS VALUE = "3.249.14.205"/> This is the iLO IP address.
<GATEWAY_IP_ADDRESS VALUE = "3.249.15.254"/> This is the default gateway IP
address.
NOTE
If using iLO 3, there is a firmware minor display issue when setting the Default
Gateway IP address, as shown above. The Default Gateway IP address can be
entered and successfully saved, but when exiting and returning to the setup
menu, it will keep on displaying as 0.0.0.0, even though the entry is properly
taken into account by the system.
b. Check that the Default Gateway IP address has effectively been taken into account by
pinging the iLO or connecting to the iLO.
• Open a command prompt and type: ping 3.249.14.205 <Enter>.
• Open a navigator window and enter: http://3.249.14.205 <Enter>
27.
• Eject the DVD from the drive and store it in a safe place for future use.
• Or extract the USB device and keep it aside for next installation steps.
This completes the AWS software load.
• Physical hardware AW Servers:
Proceed to 2.11 Job Card IST004A - HPE R/T3000 UPS drivers setup on page 82
• Virtual AW Servers:
Proceed to 2.12 Job Card IST004B - Installation of VMware Tools on page 86
• Virtual HAPS Servers:
Proceed to HAPS Server installation
• Software upgrade: Go to the section 3.8.5.2 AWS Platform software loading on page 290 for
reference, before proceeding to:
• Physical servers: 2.11 Job Card IST004A - HPE R/T3000 UPS drivers setup on page 82
• Virtual servers: 2.12 Job Card IST004B - Installation of VMware Tools on page 86

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 79

2.10 Job Card IST003 - Installation of Platform Software

2.10.3 HAPS Server installation

NOTICE
The NTP (Network Time Protocol) server must be up and running, prior to install the
HAPS servers.
For Virtual AW Servers in a cluster (Scalability), in order to achieve high availability, it is mandatory
to setup two HAPS (High Availability Preference Sharing) servers.
The following steps detail the installation of the HAPS servers.

2.10.3.1 First HAPS server setup

1. At the AW Server / HAPS Install choice screen, select HA Filesystem Server and press
<Enter>.

2. Setup the first HAPS server:

a. Leave the HAPS server address field blank (for the first HAPS server).
b. Enter the NTP server address.
c. Select OK and press <Enter>.
When installation of the first HAPS server completes, the following message displays:

3. Press <Enter>.
NOTE
If installation has failed (I.e: the NTP server is not responding), you will have to restart the
procedure at 2.10.2 AWS platform software load on page 69, in order to relaunch the
installation script.

80 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.10 Job Card IST003 - Installation of Platform Software

2.10.3.2 Second HAPS server setup

Make sure the 2nd HAPS VM has been properly installed and configured, and launch the install
procedure at 2.10.2 AWS platform software load on page 69.
1. At the AW Server / HAPS Install choice screen, select HA Filesystem Server and press
<Enter>. 2

Installation of a new AW Server

2. Setup the second HAPS server:

a. Enter the IP address (eth1 - Private Network IP address) of the first HAPS server in the
HAPS server address field.
b. Enter the NTP server address.
c. Select OK and press <Enter>.
When installation of the second HAPS server completes, the following message displays:

3. Press <Enter>.
4. Unmount the media and eject it with the following command:
cd <Enter>
umount /mnt/media <Enter>
This completes the HAPS servers software load.
Proceed to 2.12 Job Card IST004B - Installation of VMware Tools on page 86.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 81

2.11 Job Card IST004A - HPE R/T3000 UPS drivers setup

2.11 Job Card IST004A - HPE R/T3000 UPS drivers

setup
This section applies to the optional HPE R/T3000 UPS drivers loading on Physical AW Server High
Tier (GEHC delivers the hardware). It is not applicable to Virtual AW Server.
Bypass this step if NO UPS option.

NOTICE
Your new AW Server 3.2 hardware system has been preloaded with OS and AWS
platform software, UPS drivers (if applicable) and with Advanced Applications by GEHC
Manufacturing.

2.11.1 HPE R/T3000 UPS drivers installation verification

The Operating System and the AW Server platform software shall be loaded.
The UPS utility driver is part of the AWS Platform software and is automatically loaded and installed
when loading the AWS software from media. Check that the UPS driver has been properly installed
on the system.
1. Login as root.
2. Type the following:
cd /usr/local/HP/PowerProtector <Enter>ls -la <Enter>
3. Verify that the folder contains the following files and folders:
• bin
• configs
• db
• desktop
• HP-HPPP
• install.log
• mc2
Proceed to configuration. Go to 2.11.2 Configuring the HPE R/T3000 UPS using HPPP Software on
page 82.

2.11.2 Configuring the HPE R/T3000 UPS using HPPP Software

1. Verify that all server equipment options are connected to power ports on the UPS rear panel.
2. Make sure that the USB cable (or Serial) connecting the UPS to the server is properly installed.
3. Launch a supported Internet browser:
Locally:
a. Apply the mandatory KVM setup update (for HP LCD8500 prior to Ext1.0 release).
Refer to A.9.7 Launching the Internet Navigator from the Server’s KVM on page 421, for
instructions.

82 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.11 Job Card IST004A - HPE R/T3000 UPS drivers setup

NOTE
The setup update is optional for the older HP TFT7600G2 KVM and for HP
LCD8500 KVM from Ext1.0 release.
b. Launch the server’s GUI using the command: startx <Enter>.
c. Launch the Firefox Internet browser from the desktop.
d. In the URL field, enter the address: 2
localhost:4679

Installation of a new AW Server

From a remote host:
a. Setup the Network parameters.
Refer to 2.13 Job Card IST005 - Network and Time Configuration on page 88.
b. Open the Terminal from Service Tools > Tools and login as root.
c. Disable the firewall with the command:
service pnf off <Enter>
d. Open an Internet browser, and in the URL field, enter:
http://<ip_address>:4679 (for a standard connection)
or http://<ip_address>:4680 (for a secure connection)
where <ip_address> is the IP address of the server hosting HPPP.
4. Close the HP Power Protector Notification window that sticks in the foreground of other
windows.
5. Read and accept the HP End User License Agreement (click on the Accept button)
6. Log into HP Power Protector (HPPP) using the default credentials user/password.
The message You are using the default password ... displays.
7. Click on OK.
The HP Power Protector Configuration screen opens.
8. Select Administrator and click on Save.

The Main window of HPPP HP Power Protector - Administrator opens.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 83

2.11 Job Card IST004A - HPE R/T3000 UPS drivers setup

This screen allows an administrator to:

• discover attached UPS’s,
• edit the UPS or application information,
• configure the power source and redundancy,
• manage users accounts.
9. Change the admin password to increase security:
a. Select Users Accounts (1).
b. Click on the admin account (2).
c. Click on Edit user (3).
d. In the popup that displays, enter and confirm the new password.
Refer to Job Card 2.14 Job Card IST006 - Changing the Passwords on page 93 for choosing
a secure password.
e. Click on the Save button.

10. Discover the power source on the Device Discovery screen:

a. Click on Device Discovery (1) to display the Device Discovery screen. You can use this to
identify and connect to UPS’s connected to the server via serial and USB.
b. Click on Quick scan (2).

84 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.11 Job Card IST004A - HPE R/T3000 UPS drivers setup

After a moment, the menu displays a list of the UPS found (only one in our case).

Installation of a new AW Server

11. Select the HPE R/T3000 UPS Device (3).
12. Select the device that powers the server:
a. Click on Configure Power source (4).
The Powersource Configuration screen opens:

b. Select Entire UPS in the pull-down menu of the Load Segment field.
c. Click on Save.
13. Logout from the HP Power Protector - Administrator by clicking on the Logout 'admin' button at
the upper right of the window and on Yes at the confirmation popup message.
14. Verify that the UPS auto-shutdown feature is operational:
a. Power off the UPS (unplug it from the AC Mains supply).
The HP Power Protector Notifications window shall pop up and display the time remaining
before shutdown. The default delay before starting shutdown is set to 10 minutes.

b. Verify that the server shuts down after 10 minutes if the AC is not restored before.
15. When the shutdown is completed, restore power to the UPS.
16. Turn on the AW server and check that the boot up sequence completes normally.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 85

2.12 Job Card IST004B - Installation of VMware Tools

17. If you have previously disabled the PNF firewall to allow connection from a remote host, enable
it back:
a. Open the Terminal and login as root.
b. Re-enable the Firewall with the command:
iptables -F <Enter>
service pnf on <Enter>
The HPE R/T3000 UPS configuration is complete.
Proceed to 2.14 Job Card IST006 - Changing the Passwords on page 93.

2.12 Job Card IST004B - Installation of VMware Tools

You need to complete the 2.9 Job Card IST002B - Virtual Machine Installation Verification on page 63
before installing VMware Tools.
The following shall only be done for Virtual AW server. In order to provide a way to do a graceful
shutdown of the AW Server Virtual Machine, VMware tools need to be installed on the VM. It gives
the possibility to the IT admin to use the Shut Down Guest button.
NOTE
The steps are described for VMware hypervisor (ESXi), with vSphere Client and vSphere
Web Client.
1. Connect to the Hypervisor hosting the AWS VM, using vSphere (Web) Client.
2. Select the VM hosting your virtual AW Server, then right click on it.
3. Select Guest/Guest OS > Install VMware Tools.
4. In the Virtual Machine console, mount the DVD.
NOTE
As you mount the VMware tools installer file in the Virtual Machine virtual CD/DVD
drive, this virtual CD/DVD drive cannot be accessed or used for other purposes.
a. Login as root.
b. If needed, create the directory /mnt/dvd with the command:
mkdir /mnt/dvd <Enter>
c. Mount the DVD with the command:
mount /dev/sr0 /mnt/dvd <Enter>
5. Go to the /mnt/dvd directory:
cd /mnt/dvd <Enter>
6. List the content:
ls <Enter>
You should see something similar to the following (the version may vary):
VMwareTools-9.4.0-1280544.tar.gz
7. Go to the /tmp directory:
cd /tmp <Enter>
8. Extract the installation files:
tar xvf /mnt/dvd/VMwareTools*.tar.gz <Enter>

86 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.12 Job Card IST004B - Installation of VMware Tools

9. Once the extraction is complete, change directory:

cd vmware-tools-distrib <Enter>
10. Execute the installation script:
./vmware-install.pl <Enter> (manual installation)
or ./vmware-install.pl -d <Enter> (automatic installation) 2
If you choose the automatic installation, the script runs to completion without needing any

Installation of a new AW Server

action.
11. If you choose the manual installation, answer to the following setup questions asked by the
script by hitting <Enter>:
a. For each question, keep the default value by hitting <Enter>

b. Execute the configuration script by hitting <Enter>.

Lots of outputs display on the screen.

c. Hit <Enter> for all choices displayed.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 87

2.13 Job Card IST005 - Network and Time Configuration

The following message displays:

d. Hit <Enter>.
e. Close the console.
12. Ensure that VMware Tools are installed and running. Do not skip this step, otherwise you can't
use the Shut Down Guest button (graceful shutdown):
vSphere Client case:
a. Select the Virtual Machine and, in the summary panel, check that the VMware Tools are
indicated as Running.
NOTE
If it is not the case, install the VMware Tools prior to continue with the next
steps.

b. Click on the Shut Down Guest button.

The following message should display:
Shut down the guest operating system of the virtual machine
'AWS3_VM01'?
c. Click on No unless you want to shutdown your Virtual Machine.
vSphere Web Client case:

a. Select the Virtual Machine and check that the Shut Down button is available.
NOTE
If the button is not available, contact the site IT admin to install the VMware
Tools prior to continue with the next steps.

13. You can now gracefully shut down the VM by clicking on the Shut Down button.
14. If the check is done on the console and not on the vSphere client UI, close and re-open the
console to take in account the Vmware Tools installation and the configuration of the Shut
Down Guest button.
The VMware Tools installation is complete.
Proceed to 2.13 Job Card IST005 - Network and Time Configuration on page 88 (if not done yet).

2.13 Job Card IST005 - Network and Time

Configuration

2.13.1 Network Configuration

88 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.13 Job Card IST005 - Network and Time Configuration

2.13.1.1 Important information about Hostname

For hostname characters rules and limitations, refer to A.2 Specific field - Characters rules and
limitations on page 361.
NOTE
If the rules and limitations are not respected, the script /root/sys-net-conf doesn't 2
allow to set the hostname. The procedure has to be run again with a correct value for

Installation of a new AW Server

hostname.
1. Once the network parameters have been setup, you can see the result by typing:
cat /etc/hosts <Enter>
Example of /etc/hosts file:
192.0.4.25 aws-06 aws-06
or 192.0.4.25 aws-06.euro.health.ge.com aws-06.euro.health.ge.com
Where aws-06 is the hostname of the NIC card, euro.health.ge.com is the domain name
and 192.0.4.25 the IP address of the AW Server.

2.13.1.2 Network Configuration Procedure

This section describes how to setup the Network configuration manually.
1. Obtain all necessary network configuration information from the site IT Admin.
2. Launch the Network configuration tool:
For factory preloaded hardware servers, at boot up time for a factory preloaded AW Server (see
2.5 Job Card IST001A - Hardware Installation Verification on page 22), you can launch it:
• locally, at the server's KVM.
• remotely, using the iLO service processor and the remote console (see next steps).
For other cases:
a. Open a remote console/terminal.
b. Login as root.
c. Type the command:
sh /root/sys-net-conf <Enter>
The following screen displays:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 89

2.13 Job Card IST005 - Network and Time Configuration

3. Enter the Hostname (followed by "dot" Domain_name if applicable).

(I.e: aws-DL560.euro.health.ge.com )
4. Press arrow down to the IP address, Netmask and Default Gateway fields to enter the
parameters.
5. Scalability case: Cluster of virtual AW servers. If applicable, enter the parameters for the
second Ethernet (AWS Private network). This shall be done for both the AW Server VML and the
HAPS server VM. For more information on scalability, refer to 2.20 Job Card IST012 - Virtual
Servers Cluster Configuration on page 196.

6. If applicable, enter the parameters for the DNS server(s).

7. Tab down to select <OK> and press <Enter> to save the configuration.
8. If you need to access the Service Tools, reboot the AW Server (see 2.13.3 Reboot the AW Server
on page 93).
NOTE
You can check the domain name by opening a Terminal and using the commands:
dnsdomainname or hostname -d.

90 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.13 Job Card IST005 - Network and Time Configuration

NOTICE
The Network configuration is not part of the backup/restore configuration feature
of the Service Tools. Upon installation, record all Network parameters in the
Maintenance logbook so you are able to retrieve them in case future reinstallation
would be needed. Record parameters for both the AW Server(s) and the HAPS
server(s).
2
The Network configuration is complete.

Installation of a new AW Server

Proceed to 2.13.2 Date and Time Configuration on page 91.

2.13.2 Date and Time Configuration

This section describes how to setup the Time zone configuration manually.
1. Launch the Date and Time configuration tool:
For factory preloaded hardware servers, at boot up time for a factory preloaded AW Server (see
2.5 Job Card IST001A - Hardware Installation Verification on page 22), you can launch it:
• locally, at the server's KVM.
• remotely, using the iLO service processor and the remote console (see next steps).
For other cases:
a. Open a remote console/terminal.
b. Login as root.
c. Type the command:
sh /root/sys-times-conf <Enter>
The following screen displays to let you choose the Time Zone:

2. Type the number corresponding to the region where your AW Server will be installed and press
<Enter>.
For instance, after selecting 2 for Americas the following screen displays:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 91

2.13 Job Card IST005 - Network and Time Configuration

3. Type the number corresponding to the country where your AW Server will be installed and press
<Enter>.
For instance, after selecting 50 for US the following screen displays:

4. NOTE
This step is required for countries having several Time zones.
Check with the IT admin of your site what Time zone shall be configured (where your AW Server
will be installed) and type the number corresponding to the Time zone region, and press
<Enter>.
The following screen displays:

92 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.14 Job Card IST006 - Changing the Passwords

Installation of a new AW Server

5. Check the Date and Time fields and, if necessary, modify them.
6. Tab down to select <OK> and press <Enter> to save the configuration.
7. If you need to access the Service Tools, reboot the AW Server (see 2.13.3 Reboot the AW Server
on page 93).
8. NOTICE
If your site has NTP server(s), you must configure it (them). This is a mandatory
step if your AW Server is going to be part of a cluster of virtual AW server systems.
Configure NTP Time server(s) with the Service Tools interface (refer to 2.16.6.2 Time Server
menu on page 115).

2.13.3 Reboot the AW Server

NOTICE
After any configuration or configuration change of the Network parameters and/or the
Date & Time parameters, it is necessary to reboot the AW Server. If the AW Server is
not rebooted after network configuration change, the Service Tools cannot be
accessed.
To reboot the server, proceed as follows:
1. Make sure you are still logged as root or login as root.
2. Type in the reboot command:
reboot <Enter>
3. Wait for boot completion before proceeding to the next setup steps.

2.14 Job Card IST006 - Changing the Passwords

The account default passwords that come with the native hardware and software should be
changed during the installation procedure in order to increase security. This applies to both the Linux
OS passwords and the AW Server passwords.
The default passwords are provided in the Advanced Service Manual, chapter 1 section 1.3.1 System
Default Passwords.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 93

2.14 Job Card IST006 - Changing the Passwords

NOTE
The platform installer requires the following default password for local users to be
changed during installation: admin, limited and standard. If the customer wants to
keep the default passwords, you can skip this step but it is not recommended.
Some customer environments also require passwords to be changed at regular intervals. When
passwords are changed, it is essential that the correct process and policy be followed – both from
the customer’s standpoint, and from a GEHC service support standpoint.
To make the AW Server system as secure as possible, GEHC recommends that the server's root
password be changed at this point in the installation process, before doing the InSite checkout.
Changing to a password other than the default password will help minimize the chance of
unauthorized users accessing the system.
When any passwords are created or changed, it is very important to involve both GEHC and
the customer’s IT admin person, and that the new passwords are recorded correctly for
Remote service needs.
If the site is Insite-connected
It is MANDATORY to change the site’s system passwords BEFORE proceeding to the InSite checkout
in order to increase security of the system. You must communicate the new passwords to your OLC
and Checkout team at the time of InSite Checkout.
DO NOT CHANGE the passwords unless notifying the Checkout and OLC representatives. Failing to
do so would no longer allow access to your system from the OLC support teams. Changing
passwords after "Checkout" means that a new Checkout will be necessary, to allow remote
connectivity.
If the site is NOT Insite-connected
If the system is not InSite-connected, the new passwords must be recorded locally and
communicated to the customer.

2.14.1 Process Overview

For reference - “System Password Change” service note (SNAW3049) is focused on the password
change details for both the Advantage Workstation product line and the AW Server product line.
Refer to it for your information on SIMS Content Viewer.

2.14.2 Passwords Change Procedure

94 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.14 Job Card IST006 - Changing the Passwords

2.14.2.1 Customer Consultation

Before initiating the password change process, the GE FE is to coordinate a customer consultation to
discuss password provisions. As a result of that meeting the following process must be followed to
complete the password change accurately.

2.14.2.2 Identify New Password(s) 2

Installation of a new AW Server

The customer may request specific passwords. If this is the case, get the passwords from the
customer and move on to Change system (ROOT / INSITE / SDC) passwords. Make sure that the
passwords chosen by the customer comply with the rules listed below.
If a new password is to be created, the FE should do so in the following ways:
• If required, use customer rules and guidelines for password creation.
• If the FE is free to choose the password, use the following guidelines:
• Must be 15 characters min.
• Must contain 1 digit
• Must contain 1 upper-case letter
• Must contain 1 lower-case letter
• Must contain 1 special character
• May contain the system ID with at least 1 more character
• Must not be blank or left as the default
• Must not be made up solely of dictionary words
• Must not contain 3 consecutive identical characters
• Must not contain a blank space
• Must not include your logon name
• Should not be the same value at different sites

Good password examples: Bad password examples:

!414585MR5test$ 414555AWS5

4$42CTAWServer32 operator

big996622LS16ct* 123456789a

The following characters (which the system may assign a special meaning) should be avoided:
@ ; # ; <Tab> ; <Esc> ; etc .... However, # can be used for the root password.

NOTICE
Each account on a single system should have a unique password. For example, the
root and insite accounts should have different password values from each other.
Using the same password for multiple accounts on a system will remove roll-based
access and decrease the level of security on a system.
For productivity, the same password value for a single account can be used on multiple systems at a
site or customer. For example, the insite user could have the same non-default password value on
3 different systems in a hospital. However, make sure not to use the same value over multiple sites
or across a region, because that would essentially duplicate the original default value problem this
service note attempts to resolve. For this reason, procedures are given below for alternative AW
platform releases.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 95

2.14 Job Card IST006 - Changing the Passwords

2.14.2.3 Change system (root / insite / sdc) passwords

The passwords can be changed either through the KVM or remotely through the iLO service
processor.
1. Open a command window:
• via the Service Tools > Tools > Terminal,
• or via the telnet InSite connection,
• or via a local subnet SSH connection.
2. Login as root, using the current root password.
3. To change the current password, type:
passwd <Enter>
4. Type the new password and press <Enter>.
5. To confirm the new password, type it again and press <Enter>.
In the example below, the new password entered is too simple (insecure) but it is accepted
anyway.

Changing password for root

New Password: <<< Type your password here and press <Enter>
Bad password : too simple
Reenter New Password <<< Type your password here again and press <Enter>
Password changed
6. Logout and login again to apply the change.
7. To change the insite/sdc password (the sdc account is only used by the system):
a. Switch user with the command:
su - insite <Enter>
or su - sdc <Enter>
b. Enter the current insite/sdc password and press <Enter>.
c. Use the passwd command (repeat the procedure from Step 3 to Step 6).

NOTICE
Be sure to test that the password was indeed set. Open another command-
line window – without closing this one – and test the root login. If connected
remotely, you can use the telnet tool command window, and the Service
Tool > Tools > Terminal option to work. When verified, logout and login again to
re-check new password.

2.14.2.4 Test the new passwords (AW and AW Server)

It is STRONGLY RECOMMENDED to test the new passwords before turnover to customer, in order to
make sure that there was no typo or mix-up with the local keyboard when the password was
changed.
To make sure that the passwords have been properly changed, try to login with each user login and
enter the new password(s).
Make sure that the <Caps–Lock> Key is not engaged before entering the password.

96 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.14 Job Card IST006 - Changing the Passwords

2.14.2.5 Change AW Server Users Password(s)

NOTE
The platform installer requires the following default password for local users to be
changed during installation: admin, limited and standard. If the customer wants to
keep the default passwords, you can skip this step but it is not recommended. 2
The default passwords are provided in the Advanced Service Manual, chapter 1 section 1.3.1 System

Installation of a new AW Server

Default Passwords.
After the password is identified, the FE should make the password changes on the device.
There are essentially five default passwords on the AWS system that may require changing:
• System ROOT account (see section 2.14.2.3 Change system (root / insite / sdc) passwords on
page 96)
root (Permanent account)
• FOUR built-in accounts
service (Permanent account)
admin (Removable account)
standard (Removable account)
limited (Removable account)

NOTICE
When changing passwords in a cluster of AW Servers (Scalability case), make sure
to use the same password for root and same password for service for all the
servers within the cluster for ease of use.
1. Launch the Service Tools.
Refer to 2.15 Job Card IST007 - Service Tools Login on page 102 for details.
2. Go to Administrative > Configuration > Users (EA3):

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 97

2.14 Job Card IST006 - Changing the Passwords

3. In the Local users menu, select the user whose password you want to change (admin in our
example) and click on the Change Password button.
A Change Password window appears.
4. Enter the new password in the Password and in the Confirm Password fields.
5. To confirm the new password, click on Confirm Change.
6. To change another user's password, repeat the procedure (from Step 3 to Step 5).

2.14.2.6 Change the default iLO User name and Password

The procedure is described through the iLO 5 service processor’s setup menus. It is similar for
theiLO 4, iLO 3 and iLO 2 setup procedure.
The HP server’s iLO Service Processor User account shall be factory set and delivered by HP for
GEHC to root.
The HP servers are also delivered with the iLO user name set to Administrator.
We recommend that you change the default root account or that you add a default user and
password (in case default user account and password would not have been properly customized for
GEHC).
1. At the Client PC, or at the FE laptop, open an Internet navigator and connect to the iLO service
processor:
http://<IP_address_iLO-processor> i.e: http://3.249.15.122
NOTE
In case you do not have yet access to any of the Client PC, or to the hospital network
with your FE laptop, it is possible to use the KVM (keyboard, monitor and mouse) of
the server to launch an Internet navigator. Refer to A.9 Useful Commands and Tools
on page 419 for details.
2. Login as root or as Administrator and enter the password written on the paper tag (if
applicable):

NOTE
Use capital A for Administrator if login as so.
The Information - iLO Overview window appears.
3. Go to Administration > User Administration.

98 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.14 Job Card IST006 - Changing the Passwords

The Administration - User Administration window appears.

Installation of a new AW Server

Only the root or Administrator users should be displayed at this time in the Local Users
window.
4. To change the root password:
a. Tick the checkbox next to root and click on Edit.
b. Tick the Change password checkbox.
c. Enter the new password twice.
d. Click on Update User.
5. To create a new user, click on the New button into the Local Users table.
The Add/Edit Local User window appears.

6. Enter the following information:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 99

2.14 Job Card IST006 - Changing the Passwords

• Login Name. I.e: service.

• User Name. I.e: service.
• Password.
• Password Confirm.
7. In the User Privileges panel, tick the select all checkbox.
8. Click on the Add User button.
The new service user is created. It allows to login to the iLO service processor.
9. Logout from the iLO Service processor.
10. Login to the iLO Service processor using the newly created service user.
11. If login to the iLO Service processor using the newly created service user is successful, you
may delete the original default root or Administrator user account.
12. Logout from the iLO Service processor.

2.14.3 Update Password(s) in Connectivity Database

To checkout the system password select the most appropriate procedure for your region:
AMERICAS (US, Canada)
• Call the USCAN toll-free Connectivity Support/Checkout direct Number: 877-842-1132
LATAM
• Argentina: 0800-6662503 or +54-1159842256
• Brazil: 0800-167702
• Chile: 0800-368000 or +56-229381628
• Mexico: 1-800 9043600 or +52-5550809017
• Peru: 80055302 or +51-17071380
• Puerto Rico: 0800-4434471 or +1-787-15009381
For all unlisted countries, please make an international call to the more convenient country.
EU and EMEA
• Connectivity Support (OLC support line): +33 1 30 83 13 00
Then select from menu: Connectivity, and Broadband & checkout
APAC
• Japan - Connectivity Support: 042-648-2940
ROA – contact OLE or connectivity champion for re-checkout for that area.
China
• You can reach at 800-810-8188 /400 812-8188 to get either connectivity team support on
connectivity issue or OLE for system checkout/re-checkout.
India
• You can reach at 1800 102 7750 (India Call Center) ext 4 for support or for system checkout/re-
checkout.
• Contact the checkout team (see the above information).
• Inform the technician you are making password changes. Provide the System ID, and ask
them to do a re-checkout with all the new password values.

100 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.14 Job Card IST006 - Changing the Passwords

• The checkout technician will verify the system ID and new password values. To reduce
miscommunication of the password verbally, consider using the phonetic alphabet listed
below.
The technician will run a checkout and password verification procedure to update the
password(s) and inform you when the process is complete.

NOTICE 2
DO NOT CHANGE the passwords later unless notifying the Checkout and OLC

Installation of a new AW Server

representatives. Failing to do so would no longer allow access to your system
from the OLC support teams.

A - Alpha B- Bravo C - Charlie D - Delta

E - echo F - Foxtrot G - Golf H - Hotel
I - India J - Juliet K - Kilo L - Lima
M - Mike N - November O - Oscar P - Papa
Q - Quebec R - Romeo S - Sierra T - Tango
U - Umbrella V - Victor W - Whiskey X - X-ray
Y - Yankee Z - Zulu

2.14.4 Communicate New Password(s)

1. Follow your customer’s guidelines for password communication and storage. Inform the
customer of the new passwords with the exception of those used for remote service only (e.g.
insite).
2. If the customer approves, write down the new passwords and store them in a secure location on
site.
The 2.14.6 Password Form on page 102 includes a sample form to place in a logbook or tape
inside a cabinet.
3. In the situation where a customer wants to know more about what GE does with passwords,
escalate to the service security team at:
http://supportcentral.ge.com/products/sup_products.asp?prod_id=295163

2.14.5 Perform a System Backup

Once you have changed the system passwords, you must perform a new backup of the system as
the passwords are part of the configuration that is saved.
To perform a backup of the system configuration, follow the instructions given in this Manual and/or
in the AW Server 3.2 Advanced Service Manual 5771771-1EN.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 101

2.15 Job Card IST007 - Service Tools Login

2.14.6 Password Form

The passwords configuration is complete.

Proceed to 2.15 Job Card IST007 - Service Tools Login on page 102.

2.15 Job Card IST007 - Service Tools Login

The following Configuration steps shall be done from the Client PC, or from the FE laptop connected
and configured for the Hospital network. In case none of them is available at this time, the Internet
navigator can be launched at the KVM. See A.9 Useful Commands and Tools on page 419.

2.15.1 Service Tools Login

1. At the Client PC or FE laptop, open a browser (Firefox or Internet Explorer) and type in the AW
Server’s IP address : http://<server_IP_address>
NOTE
The only version of Firefox supported is the version contained in the AWS OS.
2. When the page loads, click on the Service and Administrative Tools Launch button shown in the
following illustration.

102 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.15 Job Card IST007 - Service Tools Login

Installation of a new AW Server

3. Acknowledge the security messages displayed when launching the Service Tools. Accept the
default certificate, unless otherwise specified by the IT admin of your site.
NOTE
In case of problems with the certificate blocking startup (reinstallation case with
Firefox navigator for example), refer to the AW Server Service Manual for instructions.
The login screen displays.

4. Login as service. If the password doesn’t work, contact GE service and/or the site’s IT admin to
get the current password.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 103

2.15 Job Card IST007 - Service Tools Login

NOTE
From AW Server 3.2 release, only the "Secure connection" mode is available.

NOTICE
If the Internet browser proposes to remember the password for service account,
and the FE is using a PC shared by other users, do not remember the password!
5. The Service Tools HealthPage opens.

2.15.2 HealthPage Examples

The following examples show the different sections of the HealthPage displayed for the HP High Tier
server, the HP Low Tier server, and for the Virtual server.
The HealthPage also displays the "license ID" of your AW server, necessary to calculate the licenses
corresponding to the "GON" for the site from the eLicense Internet site at:
http://elicense.gehealthcare.com/
It is important to make sure that the Hardware subsystems status, as well as the Memory and Disks
status DO NOT display in RED, that would mean reporting an error condition.
NOTE
Display in Yellow can have two different meanings: Warning or information not
available.For the HP Low Tier and HP High Tier servers, the Fan, Power, UPS status and
Voltage information may not be fully available, so this information will not be displayed in
green but in yellow. However, when any of these device fails, status will display in RED.

2.15.2.1 HealthPage Status example- HP server

Fan, Voltage and Power status can display in "Yellow" for HP servers, in normal working conditions.

2.15.2.2 HealthPage "Status" example- Virtual server

In a Virtual environment, all Status shall display in green provided that the appropriate resources
have been setup on the physical server, for hosting the Virtual AW Server.

104 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.15 Job Card IST007 - Service Tools Login

Installation of a new AW Server

In case some of the status would display in red, as in the following example, contact the IT Admin of
the site to fix the issue and get the appropriate physical resources granted to your Virtual AW Server.
• Click on Status details button for more information on the issue.

NOTE
After the upgrade of a Seamless Integrated AW Server, the storage temporarily
appears as failed in Healthpage, until the configuration (seamless integration) has
been restored.

2.15.2.3 HealthPage "System Configuration" example

The following example shows the System configuration status page for a physical AW Server before
setup. Therefore the Registration status shows as "Invalid" and displays in red. As long as the
registration status will not be complete, the AW Server will not be able to quit the Maintenance
mode.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 105

2.15 Job Card IST007 - Service Tools Login

2.15.2.4 HealthPage "Version Information" example

The following example shows the version of the different "SW components" running on the AW
server. The versions displayed in this example may be different at time of release of the AW Server
3.2

2.15.2.5 HealthPage "Configuration & Status" display

To display or pull from system the Configuration page, click on the Display or Pull from system
buttons.

106 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.15 Job Card IST007 - Service Tools Login

It will take a few moments for the system to gather the information and either display the
configuration information into and additional window (click on the Hide button when done to close
the window), or to propose downloading the configuration into a Zip file. 2
The result displayed by the two buttons Pull from system and Display is the same as the output of

Installation of a new AW Server

the conf -long command.

2.15.2.6 HealthPage "Software Subsystem" example

The Software Subsystem is divided into two categories. Software subsystems used by the AWS
Plaftorm and Application, and those essentially used for Service Tools.
In the example below, an external License server is used (the site is not using the internal license
server).

NOTE
The Restart button is provided to restart the services, in case some of them would report
an error condition. You may use this feature to avoid rebooting the server.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 107

2.16 Job Card IST008 - Initial Configuration

Using the Restart button should be used cautiously when the AW Server is in use, as it
may disconnect the Users.

2.15.3 Service Tools Menus for installation / setup

NOTE
Diagnostic and Tools are not used for installation/setup.
Administrative > Utilities is not used for installation/setup.
Proceed to 2.16 Job Card IST008 - Initial Configuration on page 108.

2.16 Job Card IST008 - Initial Configuration

The following Configuration steps shall be done from the Client PC, or from the FE laptop connected
and configured for the Hospital network. In case none of them is available at this time, the Internet
navigator can be launched at the KVM. See A.9 Useful Commands and Tools on page 419.
Launch Initial Configuration menu
1. Connect to the Service Tools. Refer to 2.15 Job Card IST007 - Service Tools Login on page 102 for
details.
2. In the menu on the left side of the page, click on Initial Configuration to expand the menu.

108 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

Installation of a new AW Server

2.16.1 Configuration - Cluster case
1. In case of cluster mode, speed up the current node (AW Server) configuration by:
• Backing up the configuration of the first node fully configured and licensed.
Refer to section 3.8.3.3 Backup the Site configuration on page 277.
• Restoring the backup previously created on the current node.
Refer to section 3.8.7.2 Restoration steps on page 293.
NOTE
During the restoration, a message will popup mentioning that the license ID of the
system does not match with license ID in the back up file, as the backup has been
done from another AW Server.
NOTE
Most of the Initial configuration (this Job Card) and Administrative configuration
(2.18 Job Card IST010 - Administrative Configuration on page 148) will be restored.
2. When the restoration is complete, set the correct System ID (System ID of the current node) in
Initial Configuration > Device Data.
3. Proceed to the Platform Configuration.
4. Proceed to the 2.17 Job Card IST009 - External Application(s) Installation on page 132.
5. Proceed to the 2.16.10 Licensing Configuration on page 123.
6. Continue the node (AW Server) installation/configuration as for the first node.
NOTE
Platform configuration is not restored as well as the platform license and applications
licenses as the backup has been done from another AW Server.

2.16.2 Remote Service

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 109

2.16 Job Card IST008 - Initial Configuration

2.16.2.1 InSite Remote Service (GEHCS only)

InSite connectivity is ONLY available for GE HCS systems.
Remote access setup for EDS - See next section.

2.16.2.1.1 Remote service setup

1. NOTICE
Make sure that passwords have been changed (if applicable for your site) prior to
proceed to the InSite Checkout. The Checkout process will "link" the root, the
insite and the sdc passwords to the System ID.
Refer to Job Card 2.14 Job Card IST006 - Changing the Passwords on page 93 for password
change guidelines.
2. From the Service Tools, select Initial Configuration > Remote Service.
The Configure InSite IiP tool displays.

3. In the Gateway IP address field, enter the site’s VPN Tunnel Gateway for InSite. (This address
can be acquired from the site IT admin and/or the existing GEHC connectivity database for this
site.)
4. Click on Check IP to check the IP address. The message Success (on a green background)
displays briefly next to the button. If the check is not successful, do not proceed until the correct
address is acquired and entered, or the connectivity problem is resolved.
5. Configure DNAT:
Sites using DNAT do not see the GE backoffice on the IPs that are statically set up in the PNF
(150.2.0.0/16, 10.190.64.0/24, 82.136.152.0/24). Service user can configure the DNAT IP range
that is used to access GE on the Remote Service page. This step shall be completed before the
checkout process is started.

110 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

Installation of a new AW Server

a. Click the Enable DNAT check box to enable.
b. Enter the GE Subnet DNAT IP range (format example displayed on the tool).
c. Click on Apply to save the configuration.
The DNAT IP is saved and the firewall rules are updated.
6. Configure IIP: After a successful Check IP result, click on Activate IIP.
The message Success (on a green background) should display briefly next to the Deactivate
IIP button.
The IIP status should change from Not configured to Configured. If it does not, there is a
problem. Pay attention to the error message and the log files it references. You might need to do
a load from cold. The IIP software is embedded in the platform software, and so to reload it
requires reloading the OS and platform software.
Your system needs to be checked out after completing this procedure. Proceed to 2.16.2.1.2 InSite
checkout on page 111 now with the Checkout team.

2.16.2.1.2 InSite checkout

NOTICE
It is important to proceed with the InSite checkout now, so that your system will be
able to upload its configuration to the AWCCT website and automatically receive in
return the Registration Configuration key, necessary to enable the AW Server.
NOTE
Registration will have to be done manually if InSite is not available.
NOTE
Without the Registration key, the AW Server will not allow exiting from the Maintenance
mode and therefore be accessible to the Clients.
1. Contact your local InSite checkout team, to get the checkout of your system done.
a. Make sure they use the right model type: _AWS32 for AW Server 3.2 product.
b. Proceed with the Checkout team to the connection tests, to make sure the system is ready
to be accessed remotely.
2. When checkout is done, refresh the Service tools page and check that the Checkout finished
turns to green and displays Configured.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 111

2.16 Job Card IST008 - Initial Configuration

2.16.2.2 EDS Remote Service

This must be done for EDS systems only.
1. Open the SSH port to allow remote access.
a. Select Tools > Terminal button.
b. Click on the SSH ON button.
c. Check the message Enabled displays.

2. Alternate step: Click on New modal Terminal and on Connect. Login as root and type in the
terminal:
ssh_enabler -enable <Enter>

NOTICE
It is recommended that GE HCS sites connected to InSite keep the SSH button set
to OFF in order to disable SSH for increased security.
SSH can be turned on later at anytime when needed.

2.16.3 Device Data

All site information must be available for remote use and for other system tools to query. Obtain the
required information from the site IT administrator.
1. From the Service Tools, click Initial Configuration to expand the menu. Click on Device Data.
The Set device and hospital specific data interface will display.
The System ID implementation only allows the following characters:
Refer to A.2 Specific field - Characters rules and limitations on page 361 for characters rules and
limitations.
2. Enter the site information:

112 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

Installation of a new AW Server

All mandatory fields (the ones marked with an asterisk (*)) must be filled out. They will be
needed to obtain the Configuration Registration key.
NOTE
Service Area field:
APAC: Asia / Pacific - EU: Europe - LA: Latin America - CH: China - IN: India - USCAN:
US / Canada - EAGM: Eastern & Africa
3. When you are done, click on the Apply button.

2.16.4 Contact Data

You must enter customer contact data for the site.
1. From the Service Tools, select Initial Configuration > Contact.
The Set up contact info interface displays with three default contact names: Hospital IT, GE
Contact and Hospital admin.

2. Select each contact from the above list and enter as much of this contact information as
possible in their form. Enter at least their Name and Phone number. The contact information is
critical for remote service.
3. Click on Apply to save the information.
4. To add additional contacts, click on the Add button, then fill in the necessary information. This
information will also be retained with the Administrative Backup / Restore tools.
5. Click on Apply to save the additional contacts.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 113

2.16 Job Card IST008 - Initial Configuration

2.16.5 Service Tools Language (for Administrator)

You must enter the Interface language for the "Administrator" and the "Standard" users of the site.
Note that for the GEHC Service user, the Interface remains in English only.
1. From the Service Tools, select Initial Configuration > ST Language.
2. Use the drop-down menu to select the Service Tools language for the site.
Default is English. The site order should specify which Service Tools language is to be set.

3. Click on Apply to save configuration.

2.16.6 Time Settings

You must verify that the time was set correctly during the installation of the system, and make
corrections if needed.

NOTICE
Consult with the site’s IT administrator before changing any data for time settings!

2.16.6.1 Date and Time menu

1. From the Service Tools, select Initial Configuration > Time Settings.
The Date/Time and Time Server tabs display.

2. In the Date/Time tab, verify that each field has been set correctly. If any field is incorrect, change
it to the correct value.
3. Click on Apply to save the information.

114 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

2.16.6.2 Time Server menu

NOTICE
NTP is not aimed to correct an invalid time but to keep a basically correct date/time in
sync with the NTP server. First make sure Date and Time have been correctly setup for
your site. You must have performed steps described in previous section.
2

Installation of a new AW Server

NOTICE
Using a Time Server is a "MUST" for Scalability. If your virtual AW server is going to be
part of a cluster of AW servers, you need to setup a NTP server.
1. If your site is going to use a Time Server, select the Time Server tab.

2. To add a NTP server to the List of configured NTP servers, enter the NTP server’s IP address in
Server IP address.
NOTE
For virtual AW Server, use the same NTP server IP address than the one which was
set in the hypervisor. Refer to 2.8.3.4 NTP server setup for the Virtual AW Servers /
HAPS servers on page 61.
3. Check the NTP server’s IP address:
a. Click on Check address.
b. Click on Add.
After a few seconds, the Status window should report Running.
NOTE
If DNS servers have been previously configured, it is possible to enter the
Hostname(s) instead of the IP address(es) of the NTP Server(s).
NOTE
Use the Remove button to remove a NTP server, then click on the Refresh button on
the HealthPage to refresh the Service Tools information.

2.16.7 Database Deletion Settings

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 115

2.16 Job Card IST008 - Initial Configuration

2.16.7.1 Auto Delete settings

Check with the customer or the IT administrator if they would like the Auto Delete feature to be
turned on.
The Auto Delete feature is disabled by default but you must enable it for Full, Seamless or DICOM
Direct Connect Integration (GE-PACS case).
NOTE
Exam can be auto-deleted when (criteria and order):
1. Storage commitment flag is set for that exam at study level (whole exam archived),
2. Or exam has derived images but storage commitment flag has been set,
3. Or exam does not have any derived images
4. Or exam has derived images but are older than the specified age.
1. From the Service Tools, select Initial Configuration > Database Deletion Settings.
The Set Auto delete Policy / Delete Option interface displays.

NOTE
Do not be alarmed to see that the bar graph shows that there is already some space
utilized in the Current % of image database utilized by system, even though
there are not yet patient data stored. The space available for images is less than the
space allocated for images. This is due to the AW Server software reserving some
space for internal management (e.g: database storage, temporary files…).
2. Check the On radio button.
3. Select the age (in months and/or days and/or hours) of data candidate for deletion
For example: 0 month ; 15 days : 12 hours.
4. Chose the Auto Delete Scheduling Mode: either set the start time of the auto-delete process,
or set the frequency of the auto-delete process.
5. Keep the other settings to the factory default values unless otherwise specified. For sites using
the AW Server intensively, preferably set the High watermark lower than 90% (80% is
recommended), to avoid exceeding the high watermark limit and filling up the disks before auto-
delete is started.
6. Click on Apply to save the configuration.

116 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

NOTE
For Seamless and DICOM Direct Connect integration, all exams are on the PACS. Only
processed images are stored on the AW Server then automatically sent to the PACS.

2.16.7.2 Delete option for worklist browser

Check with the customer or the IT administrator if they would like the Delete option for worklist
2
browser feature to be turned on.

Installation of a new AW Server

This feature is set to disabled by default. When this option is enabled, all users (except limited
user) are able to delete selected studies or series from the worklist browser.
NOTE
This does not apply to integrated systems, where the database is at the PACS side.
1. From the Service Tools, select Initial Configuration > Database Deletion Settings.
The Delete option for worklist browser interface will display at the lower side of the menu.

2. To enable the Delete option, check the On radio button.

3. Click on Apply to save the configuration.

2.16.8 SNMP Configuration

Simple Network Management Protocol (SNMP) is a widely used protocol for monitoring the health
and welfare of network equipment (eg. routers), or computer equipments.
This application works in the background and has neglectable effect on available resources.
In case of GEHC PACS, it is used to send SNMP traps from AWS to the SNMP Trap Receiver. If Prodiag
is used (NO GEHC PACS case), then the AWS doesn't send SNMP traps but uses Prodiag messages
instead.
• Software SNMP traps are sent immediately as soon as generated.
• iLO hardware traps when generated, are only sent once a day.
NOTE
For Physical servers, SNMP must also be setup in the iLO Service processor, prior to
be able to use the feature. This will be done later during 2.24 Job Card IST015 - Final
Settings on page 240 steps.
1. From Service Tools, select Initial configuration > SNMP Configuration.
2. On the Simple Network Management Protocol page, click on the Enabled radio button to
monitor SNMP traps from the AW Server.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 117

2.16 Job Card IST008 - Initial Configuration

NOTE
If you chose Disabled, skip the next steps and jump to the next section.
3. Enter the IP address of the SNMP monitoring server in Monitoring server IP address. Unless
otherwise specified, the monitoring server is the AW server itself.
The monitoring server can be either:
• The IP address of the AW server itself (case no GEHC PACS : Support, through InSite and
Prodiags).
• SNMP Trap Receiver server (case GE PACS: EDS support): Refer to the PACS integration
documentation. You can obtain the address from the IT admin.

4. Click on Check IP to verify the TCP/IP connection.

5. Click on Apply to save the configuration.

2.16.9 Platform Configuration

2.16.9.1 Licensing Preparation

The system licenses are not created by GEHC manufacturing and need to be created by the GEHC FE
or by the OLC for the FE.

118 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

The licenses are created at installation time based on the license ID of the AW Server, which is
calculated by the Platform Floating License Client Configuration tool, and displayed under Platform
Configuration.
1. Write down the license ID & the site GON (Global Order Number).
The license ID is available from the HealthPage or from Initial Configuration > Platform
Configuration. 2
The GON is listed on the site's paperwork from GEHC.

Installation of a new AW Server

2. Access the GEHC eLicense website (see Chapter 5, A.3 eLicensing on page 362 for details).
http://elicense.gehealthcare.com/elicense/ OR http://elicense.gehealthcare.com/ - this URL is
available via the Internet, and via the GEHC VPN connectivity model.
NOTE
If you can't connect to eLicense, contact the OLC and ask them to obtain the licensing
information for you.
3. Query the GON, and create the license keys for the catalog entries in the GON that show up as
license key enablers –
• AWS Primary is the correct model type for AW Server 3.2 hardware or virtual server.
• AWS Node for the other virtual AW Servers in the cluster.
• AWS is for AW Server 2.0
Platform Enabler – this is the 8,000/16,000/40,000/80,000/160,000 slices specific catalog
node-locked server license.
Server Enabler – node-locked AW Floating License Manager license (CoLA License Server - if
applicable). The Server Enabler key licenses the AW Server to run a “built-in” Floating License
Server for itself. This does not exist or is not needed if the server is configured to use “external”
floating license server(s) at other IP address(es).
4. Copy or download the licenses and/or config.txt file from eLicense.
For the initial platform software installation, you must manually enter the license numbers into
the Platform Enabler and Server Enabler fields.

2.16.9.2 Configuration Steps Summary

The platform configuration is composed of three steps corresponding to three tabs. To be able to
save the configuration, you must complete each tab in the following order:
• The Platform Configuration tab to select the number of slices supported by the hardware
platform and enter the corresponding license key.
• The Scalability tab to setup whether or not the system is to be placed within a cluster of other
AW Server (only applicable to virtual AW Server). It is not intended to configure Scalability. This
is done later through the Scalability menu and is covered by Job Card 2.20 Job Card IST012 -
Virtual Servers Cluster Configuration on page 196.
• The Integration tab to setup the Integration mode.
The PACS/RIS Integration configuration is covered by Job Card 2.19 Job Card IST011 -
Integration on page 172.
The platform configuration settings are saved only after going through the Scalability tab and
Integration tab by clicking on the Next button of each tab.
Pre-requisite for Seamless integration

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 119

2.16 Job Card IST008 - Initial Configuration

NOTICE
If your site is going to be integrated to the Universal Viewer (Seamless integration),
proceed with the Dakota plugin loading prior to proceed with the Platform
Configuration steps. Refer to section 2.19.3.4 Seamless integration - configuration
steps on AWS, Service Tools on page 184. When done, proceed with next section:

2.16.9.3 Platform configuration menu

NOTICE
For DICOM Direct Connect integration, make sure you have configured the DICOM
PACS/VNA remote host prior to proceed. Refer to 2.18 Job Card IST010 -
Administrative Configuration on page 148.

NOTICE
Make sure you are under the Maintenance mode before proceeding.

1. From the Service Tools, select Initial Configuration > Platform Configuration.
The Enabler, Scalability, Integration settings page displays similar to the example below:

2. If the server is not in Maintenance mode, the following message displays:

Click on OK to acknowledge and place the server in Maintenance mode before resuming.
3. NOTICE
In case the server would not be fitted with the appropriate size of memory, or in
case some part of the memory would be defective, installation can be allowed, but
the issue should be fixed as soon as possible, and the customer warned that
performances could be degraded. A message such as the following example will
display:

120 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

Installation of a new AW Server

Click on OK
to allow the installation or Cancel to abort and fix the issue first.
4. Choose the correct Platform Enabler description (8000, 16,000, 40,000, 80,000 or 160,000
slices) based on the following information.
• The HP Low Tier server hardware uses the 8,000 or 40,000 slice (Low tier with 64GB
memory) descriptions.
• The HP High Tier server hardware uses either the 16,000, 40,000, 80,000 or 160,000 slice
description. The hardware is the same for either licenses, but 80,000 and 160,000 slices are
available with 256GB memory systems only.
• The virtual AW Server uses either the 8,000 or 40,000 slice description, or 16,000 (See table
in section 2.4.1 Virtual Machine characteristics per integration mode on page 14).
The system’s GON (Global Order Number) should identify whether the system has an 8,000,
16,000, 40,000, 80,000 or 160,000 slice license.
NOTE
DO NOT use the license keys shown in the illustration. They are shown only as an
example.
• Additionally, a 160,000 slices DEMO license can be set for demo systems for all hardware
and Virtual servers types.
NOTE
The AW Server 160,000 slices DEMO entry is dedicated for demo units. These demo
units do not require to be registered. However, they permanently display a banner
mentioning that the system shall not be used for diagnostic.The 160,000 slices DEMO
entry is supported on all Virtual or Hardware servers.
NOTE
The reference to Seats is rather a functional limitation related to the number of slices
available to be processed by all users, than a number of users limitation.
5. Record the License ID number for future use.
6. Enter the Platform License Key for your AW server.
Click on the Next button to display the Scalability tab.

2.16.9.4 Scalability setup menu

1. In the Scalability tab, select whether or not your AW Server (virtual AW Server only) is placed
into a cluster of virtual AW Servers by clicking on the Cluster Mode or Single Mode radio
buttons.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 121

2.16 Job Card IST008 - Initial Configuration

NOTICE
The Cluster mode is not available for physical hardware AW Server.
2. Enter the AWS Private network IP address for each HAPS server.
For more detailed information, refer to 2.20 Job Card IST012 - Virtual Servers Cluster
Configuration on page 196.
Click on the Next button to display the Integration tab.

2.16.9.5 Integration configuration menu

1. In the Integration tab, select whether or not your AW Server is integrated to a RIS or PACS and
what type of integration is used by clicking on one of the following radio buttons:
• No integration (standalone)
• Full front end integration (Hybrid): (3rdPartyIntegration)
• DICOM Direct Connect
• Seamless integration: Seamless_Integration
Depending on the type of AW Server (physical, virtual, etc ..), all choices may not display.

NOTE
Configuration of Integration is an important step consisting on several configuration
steps, both on the AW Server and on the PACS. As an alternative, if you are not yet
sure of all the Integration configuration parameters, we recommend that you
temporarily keep the No integration button selected, and setup integration later on,
as detailed in 2.19 Job Card IST011 - Integration on page 172. However, if the
software detects that you are installing a 16K slices key on a virtual AW Server, you
will be prompted to setup the Seamless integration at this time (the 16K slices key on
vAW Server is only commercialized for Seamless Integration).
2. Click on the Apply button to save the settings.
NOTE
You do not need to reboot the server at this time, as prompted in the message.
Reboot is only necessary when you have completed all Integration setup steps.

122 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

2.16.10 Licensing Configuration

2.16.10.1 Preprocessing configuration menu
1. In Service Tools, select Initial Configuration > Licensing > Preprocessing.
The Preprocessing Configuration panel displays: 2

Installation of a new AW Server

2. Click on the Preprocessing (AutoLaunch) checkbox to enable the feature.
3. Enter the Preprocessing License Key for your AW server.
NOTE
This license key is required for the client to access the Autolaunch advanced
application..
4. Click on the Apply button to save the configuration.

2.16.10.2 MailSender
This license key is required to allow applications to send email reports to predefined recipients.
1. In Service Tools, select Initial configuration > Licensing > MailSender.
The MailSender License page displays:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 123

2.16 Job Card IST008 - Initial Configuration

2. Enter the MailSender License Key.

3. Click on the Apply button to save.

2.16.10.3 CoLA License server

Physical (GEHC delivered hardware) or Virtual AW Server are shipped with one Floating License (FL)
server license key.
AW server has an internal License server feature, so it can be used as License server for
Applications.
It is recommended whenever possible to use external license server(s), as any potential downtime of
the AW Server would mean downtime of the internal FL server. Any Client PCs and other system
requiring to be served with floating licenses would be impacted in that case.
External license servers are recommended when the site has several devices using Floating License.
If it is an AW Server alone, then it is recommended to use the internal CoLA server.

NOTICE
No CoLA software package is provided to load any external FL server. If the customer
wants to install an external Floating license server, he/she has to order the software
package CAT # M81171SW, and purchase CAT # M80171LS pulling the AW Floating
License Manager license key. In case of upgrade, the following shall be purchased:
CAT# M81171SV AW Floating License SW Upgrade.
High Availability option:
This option provides a secondary license server for the AW Server in order to create a highly
available licensing solution. Connect to the eLicense web site http://elicense.gehealthcare.com,
select the User Guide section and open the AW-eLicense Service Manual.
You will have to look at the instructions related to the High Availability Option in the AW-eLicense
Service Manual.
Also refer to 5724192-1EN - AW Server High Availability Read Me First, for details.

124 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

2.16.10.3.1 CoLA License server installation

If the Floating License Server(s) is (are) not already installed on your site, you must install it (them)
now.
New License servers can be installed either on Physical hardware platforms or on Virtual Machine
platform. 2
The OS supported are Windows 7, Windows Server 2008 and Windows Server 2012.

Installation of a new AW Server

Refer to 5537368-1EN - Floating License 3.3.x Installation Manual for details.
1. Insert the documentation CD into the DVD drive of the customer’s PC that is used as License
Server PC.
2. Drag and drop the Floating License 3.3.x Installation Manual PDF file on the PC desktop.
3. NOTE
The following information may change depending on any eventual update of the
Floating License 3.3.x Installation Manual.
Read Section 1 - Introduction and Section 2 - Installation overview Sections 2.1 and 2.2 of the
Floating License 3.3.x Installation Manual.
4. Eject the documentation CD and insert the Software CD instead.
5. Proceed with the Floating license software installation following Section 3 up to Section 3.4.
NOTE
Bypass Sections 3.5 to 3.8 of the Floating License Installation Manual. They are only
applicable to the Advantage Workstation, not to the AW Server.
6. Follow steps described in Section 3.9 to access the eLicense site and enter the licenses in the
Floating License server(s).

2.16.10.3.2 CoLA License server configuration menu

• To use the built-in server, you need the license key.
• To use External License Server(s), you need the IP address(es) and port number from the IT
admin.
NOTE
The status of the built-in Floating License server is also indicated on the Service Tools
HealthPage in Built-in License Server (cola).

• The green OK message means the Server Enabler is valid and is running.
• A red message means it is failing in some way.
• The grey Unused message means it is not selected and not being used.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 125

2.16 Job Card IST008 - Initial Configuration

1. In Service Tools, select Initial configuration > Licensing > CoLA Server.
The CoLA Server Configuration panel displays.
2. For Internal License Server case, follow Step 3 to Step 7. For External License Server case, follow
Step 8 to Step 14.
Internal License Server case:
3. If you have received a license key for the built-in server and do not have a cluster of virtual AW
Servers, check on the Built-in checkbox.

4. Enter the Server Enabler license key in Server Enabler.

5. Keep the other default settings:
Primary License Server IP: 127.0.0.1
Server Port: 17767
6. If applicable for your site, configure the Secondary License Server.
7. Click on the Apply button to save the configuration.
External License Server(s) case:
8. Uncheck the Built-in checkbox.

126 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

Installation of a new AW Server

9. Enter the Primary License Server IP address.
10. Enter the Server Port number if it is different from the default 17767 value.
11. Check the Primary Server by clicking on Check Server IP.
12. If applicable, enter the Secondary License Server IP address.
NOTE
The Secondary License Server can be either the AW Server internal License Server
(buil-in) or an external License Server. The Second License Server shall only be
configured if your site has purchased the CoLA High Availability option.

NOTICE
It is NOT ALLOWED to combine Primary license server and Secondary license
server, that is to say, all AW Servers of the site (or in the Cluster) must use the
same license server as Primary server, and the other server as Secondary. It is
under the GEHC FE full responsibility not to mix the License servers.
13. Check the Secondary Server by clicking on Check Server IP.
Scalability case:
Preferably install External (CoLA) License Servers on physical machines different from those
hosting a VM (virtual machine). If it is not possible, one of the AW Server’s VM built-in (CoLA)
server can be used as Primary License Server, and another AW Server’s VM built-in (CoLA)
server can be used as Secondary License Server, but this is not recommended.
There are two model types in eLicense: AW_primary and AW_Node.
You receive the license keys for the External CoLA License Server only with one AW Server
considered as AW_Primary. All the other servers in the same cluster are considered as AW_Node
and do not receive license keys for External CoLA License Server.
14. Click on the Apply button to save the configuration.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 127

2.16 Job Card IST008 - Initial Configuration

2.16.10.4 Floating License configuration menu

Applications licensing is described in 2.17 Job Card IST009 - External Application(s) Installation on
page 132.
All of the supported Advanced Applications require a license key.

NOTE
Also refer to A.3 eLicensing on page 362 for more information on eLicensing tool.

2.16.11 Scalability- Clustered Servers

The Scalability configuration is covered by 2.20 Job Card IST012 - Virtual Servers Cluster
Configuration on page 196.

2.16.12 Audit Trail (EAT)

Audit Trail recording is enabled by default. Leave the settings to the factory default values unless
otherwise specified by the IT admin of the site.
1. In Service Tools, select Initial configuration > Audit Trail (EAT).
The Audit Message Settings panel displays:

2. Enter the Audit Source ID.

NOTE
The Audit Source ID is mandatory and shall contain either the AW Server Hostname
or the Serial Number of the physical AW Server or a value indicated by the site
administrator.

128 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

NOTE
The Serial Number of the physical AW Server should be available on the chassis or in
the documentation provided by the vendor.
3. Patient Name is anonymized by default.
4. Click on Save.
5. If your site uses an Entreprise Repository (remote log server), follow Step 6 to Step 14. If your 2
site does not use an Entreprise Repository, follow Step 15 to Step 17.

Installation of a new AW Server

Entreprise Repository case:
6. Click on the Enterprise Repository tab.
The Entreprise Repository panel displays:

7. Click on the On radio button to select Enterprise Repository.

8. Enter the Enterprise Repository network information: Host Name / IP and Port Number and
select the Protocol. Ask the IT admin for the appropriate information.
NOTE
It is recommended to use an encrypted communication protocol (Transport Layer
Security (TSL) protocol) if available, to avoid data to be sent in clear. To enable the TLS
protocol, refer to AW Server 3.2 Advanced Service Manual 5771771-1EN, chapter 3
Section Enterprise Repository. Check with the site’s IT admin or contact the OLC for
help.
9. Click on Save.
10. Make sure you are in Maintenance mode.
11. Restart all services from the HealthPage by clicking on the Restart button.
NOTE
All users are disconnected when you restart the services.
12. Exit the Maintenance mode.
13. In Service Tools, select Initial configuration > Audit Trail (EAT) and return to the Entreprise
Repository panel.
14. To check the Entreprise Repository is alive, click on Send Test Message.
Local Repository case:
15. Click on the Local Repository tab.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 129

2.16 Job Card IST008 - Initial Configuration

The Local Repository panel displays:

16. Click on the On radio button.

17. To review an Audit Trail event, click on it.

2.16.13 Prodiag configuration

NOTE
Bypass this step if the site is a GE PACS (CPACS, IW/Universal Viewer, EA) site. GE PACS
does not use InSite and Prodiag needs an operational InSite connection to work.
Prodiag (Proactive Diagnostics) is already configured to be used with the AW server. It
does not require additional configuration. It is recommended to keep the Prodiag tasks to
their default and not to change the default configuration. The indication below is provided
for reference.
1. Bypass this procedure unless you want to schedule tasks specifically.
2. NOTE
Prodiag menu cannot be accessed when using directly the AW Server KVM.
NOTE
Some versions of Java may consider the Prodiag page as untrusted.
See AW Server 3.2 Advanced Service Manual 5771771-1EN chapter 3, section Troubleshooting
AW Server Platform / Application Error Messages and search Java.
3. In Service Tools, select Initial configuration > Prodiag.
After a few seconds of initialization, the Proactive Diagnostics panel displays:

130 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.16 Job Card IST008 - Initial Configuration

Installation of a new AW Server

NOTE
If the Proactive Diagnostics panel does not display properly, and a message such as
This plugin is disabled displays, click on Manage plugins to authorize Java
to display the Proactive Diagnostics panel.
4. NOTE
Sending the HW log to the backoffice is a recurrent Prodiag task, running every day. It
can be rescheduled by the service user on the Prodiag page (task is called
pd_awe_trap), if the timing is not fine. It sends the HW log (/var/log/snmptraps
.log) to the backoffice if the HW log contains captured SNMP traps. Otherwise the
log is not sent to the backoffice.
If applicable, reschedule a task or add a new task.
5. To save and exit, click on Apply.

2.16.14 GIB Data

This information is used to populate the Global Installed Base repository.
Perform the following steps for each piece of equipment in the AW Server system.
1. In Service Tools, select Initial configuration > GIB Data.
The Set Global Installed Base data panel displays:

2. Click on the Add button.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 131

2.17 Job Card IST009 - External Application(s) Installation

3. In the form that displays, fill all the fields whenever possible.
4. Click on Apply.
5. Repeat Step 2 to Step 4 for the next piece of equipment until all the equipment is documented.
6. If Service Tools is opened remotely from the FE laptop with access to the GE Intranet, click on
Send via PC to send the GIB data by email.
NOTE
If you attempt to send the GIB data directly by email through the Client PC and no
email account is configured, the following message displays: The email will be
generated by your mail program (like Outlook).
Click on OK to acknowledge. When the email displays, click on the Send button.
7. If Service Tools is opened from the Client PC (usual case), use Pull from system to save the data
first (for example, on a USB key). Access to the GE Intranet and send the data through the FE
laptop.

2.17 Job Card IST009 - External Application(s)

Installation

2.17.1 Foreword
In order to address the new Quality requirement for handling safety issue with Applications running
on AW Server, the following processes have been put in place.

2.17.1.1 Applications delivery and installation management changes

2.17.1.1.1 AW Server 3.2 Forward Production

The Advanced Applications are NO LONGER embedded in the AW Server platform software media.
However, they are factory preloaded in Forward production hardware systems.
• Whenever a safety issue is identified with a single Application on its dedicated SW media, it will
be put "on-hold" until the issue is fixed and the new software release is ready to be put into
Forward Production.
• Whenever a safety issue is identified with an Application on a multi-applications software
media (i.e: Volume Viewer Apps), the multi-Apps SW media will be put on-hold and the
Application impacted by the safety issue removed from the media.
• When it is done, the updated multi-Apps media will be introduced in Forward Production
(without the Application impacted by the safety issue) and its package will bear a warning
notice mentioning the name of the Application missing.
• When it is done, the updated AW Server platform SW media will be introduced in Forward
Production (without the Application impacted by the safety issue) and its package will bear a
"Product Hold" warning notice mentioning the name of the Application missing.
How to handle the missing Application issue:
• When installing the Applications, warn your customer about the current unavailability of the
impacted application, which will become available again when the issue is corrected and the
product-hold lift, through FMI delivery.

132 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

2.17.1.1.2 New Application purchased and/or Applications upgrade

When a site has purchased a new Application or an upgrade (i.e: Volume Viewer applications), the
Application(s) SW media is delivered.
• Whenever a safety issue is identified with a single Application on its dedicated SW media, it will
be put "on-hold" until the issue is fixed and the new software release is ready to be put into 2
Forward Production.

Installation of a new AW Server

• Whenever a safety issue is identified with an Application on a multi-applications software
media (i.e: Volume Viewer Apps), the multi-Apps SW media will be put on-hold and the
Application impacted by the safety issue removed from the media.
• When it is done, the updated multi-Apps media will be introduced in Forward Production
(without the Application impacted by the safety issue) and its package will bear a bear a
"Product Hold" warning notice mentioning the name of the Application missing.
How to handle the missing Application issue:

NOTICE
When you install the new application (of a multi-application software) purchased by
the site, it will also update all applications within this package, and potentially disable
an Application currently installed on the site, if this application is not contained into
the new software media, because it is impacted by a safety issue.
What shall you do before installing / updating applications ?
• Identify if any application concerned by the Product Hold is installed/licensed on the system
• If yes, you need to contact your customer and ask him/her to decide whether:
• He/she agrees that you install the new purchased Application, but this will disable an
application already installed on the system (can be acceptable if the application currently
installed is not regularly used by the customer) OR
• He/she does not agree to lose temporarily the access to an application that is regularly
used and prefers to postpone the new application installation and/or upgrade of
applications.
• When the issue is solved and the Product hold is lift, an updated Applications package will be
delivered through FMI, so you can upgrade the site with the new release.

2.17.1.2 Product Hold warning notice example

The following warning notice will be placed on front cover of the Applications media box jacket,
whenever one or several Applications of the package would have been disabled, as containing a
safety issue.

The following warning notice will be placed on back cover of the Applications media box jacket,
whenever one or several Applications of the package would have been disabled, as containing a
safety issue.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 133

2.17 Job Card IST009 - External Application(s) Installation

2.17.1.3 Information about registration of installed configuration

The configuration of your AW Server system and of the installed Applications MUST BE registered to
the AW CCT site upon AW Server installation and configuration completion.
By sending the configuration of your AW Server system to the AW CCT web site, if it is appropriate,
you will receive a configuration software key that will allow you to unlock the AW Server system and
exit the Maintenance mode.
• InSite checkout: If your AW Server is to be connected through InSite (HCS case), it is strongly
recommended to proceed with the InSite installation and checkout prior to installing the
Advanced Applications. Doing so will allow the automatic sending of your system configuration
to the AW CCT site and receiving of the configuration key.
• If your AW Server cannot be connected through InSite (EDS case), the automatic sending of your
system configuration to the AW CCT site and automatic receiving of the configuration key
cannot be achieved. You will have to proceed with a manual registration of the configuration to
the AW CCT site.
This step will have to be done once the AW Server configuration has been completed (platform,
applications installation and activation, ...).Refer to 2.21.1 System Configuration Registration on page
200.

2.17.1.4 Applications Software package content

NOTICE
Applications packages contain several media containing software and documentation.
Use the appropriate media for your server type.
• Application software and docs DVD for PHYSICAL AW Server
• Application software and docs DVD for VIRTUAL AW Server
• Application software and docs USB key for PHYSICAL or VIRTUAL AW Server

2.17.2 License Server(s) installation

Make sure the Cola License server is properly installed and configured, prior to proceed to the
following steps. Refer to section 2.16.10.3 CoLA License server on page 124.

2.17.3 Application(s) Licensing setup

The AW Server can be its own (built-in) Floating License Server or it can use an (external) Floating
License server when installed at the customer site.

134 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

The Floating License Manager tool does the following:

• Displays the “Target Server” information:
• License ID - Name/IP Address - Hostname - Version
• Server Enabler license key string and license key
• Displays licenses on the FL Server, and number of users
2
When using the built-in FL server, the listed licenses are on the AW Server. They can be entered

Installation of a new AW Server

manually or read from a portable media or file location (eLicense config.txt file) to UPDATE the
server.
When using an external server, the listed licenses are read from the external server.

1.) Make sure the internal Floating License server has been properly setup with its license. or that the External
license server(s) is operational and populated with the appropriate licenses. Refer to section 2.16.10.3 CoLA
License server on page 124.
If the Cola license has not been installed yet, you will not be able to setup the Applications licenses, that will
report an error upon installation.
2.) • Click on Floating License link under Licensing menu
The GEMS Floating License Manager menu displays as in the example below:

NOTE
If many application licenses are to be installed, you may have to scroll up and down
to see the entire list of licenses.
NOTE
The actual image you get on the screen may differ from this example, depending on
the Applications loaded on the AW Server, and their software version.
3.) • Copy the config.txt file to your PC or a portable storage device (e.g., a USB flash drive or a CD), so you can
Choose File and upload all available licenses at once on the AW server.
In some occasions, it may be necessary to enter the license and the corresponding keystring of one
application before you can upload all other licenses from your media (USB disk, etc..)
**** OR ****
• Browse for the config.txt license file acquired from eLicense:
• Manually type in the exact license string, and the exact license key.
Example License String: VesselIQ_Xpress
Example License Key: JW776XBU4EUA2J98

NOTICE
The media shall be inserted into the same system as where the Service Tools is started. (i.e:
If Service Tools is started on the GEHC FE laptop, insert the media in the GEHC FE laptop).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 135

2.17 Job Card IST009 - External Application(s) Installation

4.) If not possible, manually enter the License keys delivered for your site, in the Applications corresponding
fields, as shown in the example above.
• Once the Update Server button becomes available, select it and the application(s) should populate into
the “Licenses On Server” column. You might need to click in or navigate around in the license key field
before it senses the data and activates the UPDATE button.

NOTICE
When entering the license keys, be careful about the difference between the numeral zero
and the letter ”O”. Use a text editor application with a large font to visually verify the
difference if necessary.

2.17.4 Enter the Maintenance mode

Place the AW Server in the Maintenance mode, if not already done, in order to load and install the
Applications.
NOTE
By default, a new AW Server is automatically placed in the Maintenance mode.
NOTE
By default, an AW Server that has just been loaded/reloaded with software is
automatically placed in the Maintenance mode.

1.) □ Enter the Maintenance mode

• Click on Maintenance menu then select Maintenance
The Maintenance menu opens and displays warning messages.

• Read the messages carefully and make sure to understand them before proceeding.
NOTE
If your AW Server InSite connection is operational (checkout done) you will
only see the first message.
2.) □ • Click on the Start Maintenance button to start the Maintenance mode (if not done yet).
The Maintenance is in progress banner will display.
• Refer to Chapter 5, A.4 Maintenance Mode on page 369, for more details on the Maintenance mode.

136 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

2.17.5 Load the Application(s) from media

NOTICE
Forward Production physical servers: Applications are factory preloaded for
Forward Production high tier and Low tier server. They do not need to be loaded from 2
the media delivered in the Application packages. However, FE shall verify at
installation time that the Applications packages received with the delivery are of the

Installation of a new AW Server

same version as those preloaded. If later version, FE shall upgrade to the new version
through the media delivered in the Applications packages. Always use the latest
version received for Applications.

NOTICE
Due to the frequency of introduction of Volume Viewer releases, AW Server 3.2 High
Tier and Low Tier systems may not be fully preloaded with the Volume Viewer
Applications. In that case, this will be indicated by the below label stuck on the AW
Server packaging.

Foreword
There are different ways to load the Applications from the media delivered.
Use the one applicable to your system (physical / virtual) and that better fits your needs (local /
remote)
1. Hardware servers local process- Locally at the Server’s hardware DVD drive
NOTE
DOES NOT APPLY to Virtual AW Server loading or Apps Refresher DVDs collector
loading
• Use the standard Application SW media DVD dedicated to physical (hardware) server.
• Insert the DVD media into the server’s DVD drive
• Proceed to section 2.17.5.1 Using the Physical (hardware) server’s DVD drive on page
138
2. Hardware servers remote process- Remotely at the Client PC.
NOTE
DOES NOT APPLY to Virtual AW Server loading or Apps Refresher DVDs collector
loading.
• Use the standard Application SW media dedicated to physical server.
• Insert the media into the client PC

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 137

2.17 Job Card IST009 - External Application(s) Installation

• Proceed to section 2.17.5.2 iLO media drive mapping - Remote installation on Physical
Hardware Server on page 139
3. Virtual servers process - Remotely at the Client PC.
Also applicable to physical hardware servers, using media dedicated to Virtual server.
Also applicable to Apps Refresher DVDs collector
NOTE
Standard Application SW media dedicated to physical server cannot be used
• Use the Application SW media dedicated to Virtual server or DVD collector
• Insert the media into the client PC
• Proceed to section 2.17.5.3.1 Applications loading procedure on page 140 - Applications
• Proceed to section 2.17.5.3.2 AWS SW Apps DVDs collector loading procedure on page 141 -
Applications Refresher DVDs collector
NOTE
Section 2.17.5.4 Loading/installing Advanced Applications from USB device -
eDelivery on page 143 gives an alternate method to load using the File transfer
tool.
4. Installing from electronic files
When installing from electronic files, always refer to 5761599-8EN: AW eDelivery Service
Guide for detailed instructions

2.17.5.1 Using the Physical (hardware) server’s DVD drive

Use the standard Application SW media DVD dedicated to physical (hardware) server.
1. At the physical server hardware:
Insert now the Application DVD media you want to install into the Server’s DVD drive.
2. At the Client PC or FE laptop:
Launch the Version Management tool under Maintenance sub-menu.

Carefully read the warning message and make sure you understand it prior to click on OK
button to close the message.
3. Make sure the Install/Uninstall tab is selected or select it.
Wait for a few seconds for the media to be mounted, then select CD/DVD (dev/sr0) and click on
Contents (DVD drive of the server hardware).

138 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

The "Available for installation on Hard disk" section will get populated with the new package
available for installation. Make sure the version you are about to install is appropriate (I.e:
Version is not older than the one currently installed - upgrade case).
4. Install the Application now. Goto 2.17.6 Install the Application(s) on page 143.

2.17.5.2 iLO media drive mapping - Remote installation on Physical Hardware

2
Server

Installation of a new AW Server

Loading Applications software from the Application SW media dedicated to physical (hardware)
server can be done at the Client PC, if you map the Client media via the iLO Service Processor.
• Use the standard Application SW media dedicated to physical (hardware) server

1.) □ At the Client PC or FE laptop:

• Insert now the Application media you want to install into the Client PC’s.
2.) □ Refer to Chapter 5, A.7 Software Loading Through iLO on page 410 for details on iLO UI startup and
mapping a media drive.
• Open an Internet Explorer and launch the iLO interface: http://<iLO_IP_address>
• Login as root.
• Start the "Console redirection"
• Map the media drive of the Client PC
3.) □ Under the Service Tools / Maintenance menu:
• Launch the Version Management tool under Maintenance sub-menu.

NOTICE
Carefully read the warning message and make sure you understand it prior to
click on OK button to close the message.
• Make sure the Install/Uninstall tab is selected or select it.
• Wait for a few seconds for the media to be mounted, then select CD/DVD (dev/sr1) and click
on Contents (media drive of the server hardware).
4.) □ The "Available for installation on Hard disk" section will get populated with the new package
available for installation. Make sure the version you are about to install is appropriate (I.e: Version
is not older than the one currently installed - upgrade case).
• Install the Application now. Go to 2.17.6 Install the Application(s) on page 143

2.17.5.3 Virtual server and physical Hardware server remote installation case
The following procedure shall be used to remotely load Applications from the PC’s media drive, for
Virtual AW Server, and/or can also be used for the Physical Hardware AW Server, for example when
you do not have access to the servers room, In this case, you may have previously loaded the OS and

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 139

2.17 Job Card IST009 - External Application(s) Installation

AWS platform software remotely through the iLO of your server (refer to procedure in
A.7.1 Foreword on page 410.
• For both cases, use the Application SW media dedicated to Virtual server.

2.17.5.3.1 Applications loading procedure

The following steps are done at the Client PC or FE laptop

1.) □ • Insert now the Application media (dedicated to Virtual server) you want to install into the Client PC.
The PC Autostart feature may start opening the Windows Explorer and display the media content.
2.) □ • Locate the Application_name ".ISO" file that you will need for loading the application.
• Also locate the "md5sum" text file that will allow you to check the ISO file once transferred.
3.) □ • Launch the Version Management tool under Maintenance sub-menu.

4.) □ NOTICE
Carefully read the warning message and make sure you understand it prior to click on
OK button to close the message

5.) □ • Make sure the Install/Uninstall tab is selected or select it.

• Wait for a few seconds for the media to be mounted, then click on Upload ISO
The following window pops up:

• Click on the Choose File button and choose the ISO file stored on the dedicated Applications
media.
6.) □ You may copy/paste the md5sum into the dedicated field for security.
• Click on Send to system button.
7.) □ The "Available for installation on Hard disk" section will get populated with the new package available
for installation. Make sure the version you are about to install is appropriate (I.e: Version is not older
than the one currently installed - upgrade case).
• Install the Application now. Jump to 2.17.6 Install the Application(s) on page 143

140 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

2.17.5.3.2 AWS SW Apps DVDs collector loading procedure

The AWS SW Apps DVDs collector (also known as Applications Refresher DVD collector) is ONLY
delivered with the software upgrade kit to AW Server 3.2.
It is not delivered with Forward Production AW Server. The procedure detailed hereafter is applicable
for loading the Applications from the AWS SW Apps DVDs collector: 2
• 5720641 (or up): AWS SW Apps - DVD 1 - CT Apps for AW Server 3.2

Installation of a new AW Server

• 5720642 (or up): AWS SW Apps - DVD 2 - PET Apps for AW Server 3.2

NOTICE
Multiple file upload using the Upload DVD collector button process is NOT
supported with Internet Explorer. It is only supported with Firefox and Chrome.For
Internet Explorer (IE8 ...IE11), the upload of files contained in the DVD collector will
have to be done using the standard Upload ISO button process, by selecting both
the ISO and relative md5sum files, as explained in the previous section
2.17.5.3.1 Applications loading procedure on page 140

1.) □ • Make sure you are still under Maintenance mode and in the Version Management menu.
• Insert the Apps Refresher DVD into the Client PC DVD drive.
• Wait for a few seconds for the media to be mounted, then click on Upload DVD Collector.

2.) □ The following window pops up:

.
3.) □ • Click on the Choose Files button.
• Select all the ISO files and md5sum files stored on the dedicated Applications media as in our
example below:.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 141

2.17 Job Card IST009 - External Application(s) Installation

4.) □ • Click on Open.

• A message displays to advise that the selected files will be stored under /var/lib/
Service_Tools_AWS/install/upload directory.
• Click on Send to system button
The Send files to system window gets populated with the selected Application’s ISO file and
md5sum files.

NOTE
The tool checks the md5 files with the corresponding ISO files during the
DVD collector upload. If the ISO file is corrupted the warning message
pops up:
NOTE
"Checksum mismatch. Uploaded file deleted."
NOTE
and the Version Management page will not contain the corrupted ISO file.
NOTE
Firefox or Chrome browsers:
NOTE
Multiple Applications installation at one time is possible using these
browsers.
NOTE
Internet Explorer browser:

142 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

Install the first application, and when successful installation message has
displayed, proceed with the installation of the next application.
5.) □ When all files have been uploaded, a message window pops up and displays:
Upload successfully finished
• Click on OK to close the popup.
The Available for installation on Hard disk section gets populated with all the successfully
uploaded applications, that are now ready to be installed. 2

Installation of a new AW Server

2.17.5.4 Loading/installing Advanced Applications from USB device - eDelivery
eDelivery is a new delivery method which allows to provide AW application products as electronic
files. The electronic files are manually downloaded from a download server and installed through
USB device.
NOTE
At the time of release of this manual, eDelivery process may not be fully available for all
AW applications. Refer to eDelivery process documentation for details.
NOTE
Verify that the USB file system is supported in eDelivery, before installing applications
from USB device.
The list of applications supporting eDelivery process will be regularly communicated.
You will also be able to refer to AW eDelivery Service Guide 5761599-8EN / DOC1888559 for
detailed instructions about:
• Connection to eDelivery server and download of application digital kit.
• Application installation from USB device using Version Management (refer to section
2.17.5.3.1 Applications loading procedure on page 140 - Upload ISO procedure).
• Demo exams loading from USB device.
• Troubleshooting."

2.17.6 Install the Application(s)

See 2.17.8 Applications Profile on page 147 for the list of supported Applications.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 143

2.17 Job Card IST009 - External Application(s) Installation

1.) • Use the Version Management tool to select and install the Preloaded Applications (physical servers) or to
install the Applications loaded in 2.17.5 Load the Application(s) from media on page 137 .

Applications will not show up in the "Available for installation on hard disk" until they have been loaded from
their media. However, Applications that are Preloaded by manufacturing for the Forward production physical
servers are showing in the "Available for installation on hard disk".
2.) After successful completion of Applications software loading, the "Available for installation on Hard disk"
section gets populated with the new package available for installation.
• Make sure the version you are about to install is appropriate (I.e: Version is not older than the one
currently installed - upgrade case).
• Click the radio button to select the Application(s) for installation.
NOTE
You can select several applications to be installed one after one in the same
shot.
• Click on the Install button. The Application(s) start(s) loading..
3.) • Acknowledge the information message by clicking on OK..
Do you really want to install the following packages:
Appl 1
Appl 2
Appl n
It takes time to extract and install the packages. Please be patient. When the Application(s) is (are) loaded, a
message will say so and they will appear in the "Currently installed" section.
• When done, proceed with the next Application(s) installation.
NOTICE
Pre-requisite for CardIQ Xpress Process v2.3 installation: Volume Viewer, CardIQ
Xpress Reveal and Pre-processing must be installed and licensed. CXP license must also be
set before installing the CXP package.

4.) When done, the Install/Uninstall finished successfully message displays.

• Click on OK to acknowledge the message.
• Select again the Install/uninstall tab.

144 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

Application now show in the "Currently installed" section as in the example below:.

Installation of a new AW Server

5.) • If you have installed the Advantage SIM and/or Advantage 4D application(s), check now that new menus
have been added to the service tools under the Maintenance menu - You may need to refresh the service
tools before these new entries appear:

NOTE
Informational step: Application uninstallation:
• To uninstall an application, click to select the radio button corresponding to the application and click on
the Uninstall button.
• To remove a package, click to select the radio button corresponding to the package you want to remove
from the AW Server hard disk and click on the Remove package button..

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 145

2.17 Job Card IST009 - External Application(s) Installation

2.17.7 Activate the Application(s)

Applications shall be activated in order to be available once they have been installed and licensed.
They can be de-activated if necessary, for instance when an application shall not be left running on
site.
Applications are not activated by default. Make sure to perform the following steps to activate
applications. This is also necessary when upgrading from AWS2.0 release.
NOTE
Only activated licenses and the related applications are listed (shortcuts are filtered out)
in the configuration file.

1.) □ • Click on the License Activation tab.

The following menu (example) displays:

2.) □ • Scroll down to see all listed applications

• Click on Select available button to automatically check the boxes of all licensed application
available on the Floating License Server
OR
• Select the Application(s) to be activated.
• Also make sure to uncheck all licensed Applications that are should not be activated.
• Click on Apply when done. You may also have to click on the Refresh button to display
NOTE
License Information column:
• Not licensed - There is no license available for the application
• A license is displayed - There is a Floating license available for the application
Application Name column:
• Not installed - You need to load the Application first from its media

146 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.17 Job Card IST009 - External Application(s) Installation

NOTE
"Conf "output lists the applications which has at least one activated license.
Only the activated licenses are listed.

2.17.8 Applications Profile

Applications currently supported with the AW Server 3.2 release are: 2

Installation of a new AW Server

2.17.8.1 Volume Viewer applications
NOTE
Unlike earlier versions of Volume Viewer Applications 11.x for AW Server 2.0 platform, the
basic Volume Viewer application 12.3 (or up) or the Volume Viewer application 13.0 (or
up) needs a license key to be enabled for AW Server 3.2. The AW Server 3.2 platform
license key does not include the Volume Viewer license.
The Volume Viewer license is required as a pre-requisite to launch all other Volume Viewer
Applications.
All Volume Viewer Applications use the same logfile: Voxtool.log.
All Volume Viewer Applications use Floating license mode, except AutoLaunch (pre-processing)
which uses Node-Locked license mode.
NOTE
Refer to the Volume Viewer Applications Service Note (SNAW3090) and to the
Applications dedicated RMF to get the supported Applications and Integration Mode(s).
NOTE
All the Volume Viewer Applications in release 12.X / 13.X (or up) are compatible with
single and dual monitor configurations.
Whenever there is an Installation Manual and/or a ReadMeFirst document delivered with
the application (e.g: VV 12.3, CardIQ Xpress Process, etc..), refer to the supplied document
for more details.

2.17.8.2 Other Applications supported

NOTE
Whenever there is an Installation Manual and/or a ReadMeFirst document delivered with
the application, refer to the supplied document for more details.

Application Applicatio License License Keystring legacy Shortcuts (in AW Logfile

Name in n version Modes keystring AW Server name
Version supported supported client desktop)
Management
CardIQ Xpress 2.3 Ext. 6 Floating CardIQ_Xpress_Proce N/A N/A cardiqproces
Process (or up) ss (launched via s.log
Prerequisites: CardIQ Xpress
Volume_Viewer Reveal of via
AutoLaunch)
CardIQ_Xpress_Revea
l
AutoLaunch
CortexID Suite 2.1 Ext. 6 Floating CortexID_Suite N/A CortexID Suite cortexidsuite
(or up) log
CortexID Suite 2.1 Ext. 6 Floating CortexID_Suite_PIB N/A CortexID Suite cortexidsuite
PIB (or up) log

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 147

2.18 Job Card IST010 - Administrative Configuration

SmartScore 4.0 4.0 Ext. 200 Floating SmartScore_40 N/A SmartScore 4.0 sscorelog
(or up)
GSI Viewer 2.2 Ext. 5 Floating GSI_Viewer N/A GSI Viewer gsiviewerlog
(or up) GSI Curved
GSI General...
Advantage 4D 2.3 Ext. 5 Floating Advantage_4D_CT N/A Advantage 4D See
(or up) Advantage
4D manual
AdvantageSim 9.0 Ext. 4 Floating AdvantageSim N/A AdvantageSim See
MD (or up) SimMD_MultMod4D MD AdvantageSi
SimMD_Opt_CT_Atlas m MD
RePlan manual
SimMD_Opt_MR_Pelvi
sSeg
Quantib Brain 1.2 Floating Quantib_Brain N/A N/A See Quantib
Brain manual
CVI42_CMR42 5.3 Ext. 4 Floating cvi42_cmr42 N/A CVI42_CMR42 See cvi42
(or up) cvi42_mitral manual

Pre-requisite for CardIQ Xpress Process (CXP) installation:

• Volume Viewer, CardIQ Xpress Reveal and Pre-processing must be installed and licensed.
• CXP license must also be set before installing the CXP package.
Applications installation and configuration is complete
Proceed to 2.18 Job Card IST010 - Administrative Configuration on page 148

2.18 Job Card IST010 - Administrative Configuration

1. From the Service Tools menu, click on Administrative to expand the menu.
2. From the Administrative menu, click on Configuration to expand the menu.

148 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

2.18.1 DICOM Hosts Configuration

The following procedure describes how to configure one or more DICOM hosts to allow data
exchange between them and the AW Server.
NOTE
For Seamless integration, the only necessary DICOM host declaration is the Universal 2
Viewer PACS server. The DICOM port of the Universal Viewer is 104.

Installation of a new AW Server

1.
Obtain all necessary DICOM hosts configuration information from the site IT Admin. You need
the data to complete this procedure.
2. Click on DICOM Hosts.
The Perform DICOM hosts configuration interface displays.
3. Click on Add new.
The DICOM hosts configuration page displays.
4.
All mandatory fields (the ones marked with an asterisk(*)) must be filled out to configure a host.
Other fields are optional.
Refer to A.2 Specific field - Characters rules and limitations on page 361 for characters rules and
limitations.
Refer to the DICOM remote hosts configuration rules highlighted in example below.
NOTE
The DICOM Hosts file is part of Nuevo.
The file is /export/home/sdc/nuevo/resources/network/network-cfg.xml.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 149

2.18 Job Card IST010 - Administrative Configuration

5. You can check if the host is reachable:

a. Click the Check IP button to test the IP Address of the host with a standard ping.
b. Click the Check DICOM button to perform a DICOM ping.
6. For DICOM Direct Connect integration:
a. The Preferred compression format can be set to one of the following options:
• Automatic (default)

150 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

• JPEG Lossless
• JPEG 2000 Lossless only
• RLE
• Uncompressed
NOTE
2
The FE needs to check which compression mode the PACS/VNA supports, and
select option accordingly.

Installation of a new AW Server

b. The C-FIND query strategy can be set to one of the following 3 options:
• Relational C-FIND
• Multi-values UIDs for C-FIND (default)
• None
NOTE
The FE needs to check if the PACS/VNA supports Relational C-FIND or Multi-
value C-FIND, and select option accordingly.
c. The Allow early response for C-STORE option speeds up retrieval of images.
7. NOTE
The C-FIND tags are used when NUEVO sends C-FIND commands to the remote host
in order to build the Remote Worklist in NoInteg, Hybrid or DDC integration mode.
Check or uncheck the box(es) to enable or disable the two optional DICOM tags: Institution and
Reading Physician.
NOTE
By default, they are disabled, because, according the IHE standard, remote hosts are
not “required” to support them, but many host do (e.g. EA, AWS).
The other C-FIND tags cannot be changed from Service Tools, because, according the IHE
standard, remote hosts are “required” to support them. However, if it is really necessary, they
can be changed to false in the appropriate section in the network-cfg.xml configuration
file. This configuration file is located in /export/home/sdc/nuevo/resources/network/ne
twork-cfg.xml. Every DICOM host has a "node" tag structure in the configuration file.
8. Click Apply to complete the host configuration.
9. Proceed to the next Host configuration.
NOTE
All configured DICOM hosts can be saved when the Maintenance > Backup tool is
run, and correspondingly restored when the Maintenance > Restore tool is run.

NOTICE
Each time that you configure a DICOM Host, do not forget to configure also End of
Review to set up the types of processed image series that will be automatically
sent to the host when exiting an application. Refer to 2.18.9 End of Review on
page 170.

2.18.2 Configuring DICOM Printers and Filmers

This feature is not available with Seamless integration
1. • Click DICOM Printers.
The "Perform DICOM printers configuration" interface displays.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 151

2.18 Job Card IST010 - Administrative Configuration

• Ask your customer what hospital name shall be displayed on the films.
Use only the ISO-8859-1 English character set for DICOM printer configuration. Other character
sets are not supported. If you do not enter the Hospital name for Filmer, you will not be
authorized to setup the DICOM printer parameters.
• Enter the Hospital name for Filmer and click on Apply button
2. • Click on Add button
The "Perform DICOM printers configuration" interface expands.

3. All mandatory fields (the ones marked with an asterisk(*)) must be filled out to configure a
printer or a filmer. Other fields are optional.
Refer to A.2 Specific field - Characters rules and limitations on page 361 for characters rules and
limitations.
Following the rules and limitations, enter or select all available information for the printer.
Do these steps for each DICOM printer or filmer to be added.
4. • Enter the first set of parameters as specified by the IT admin or the printer Vendor FE
(Label, Hostname, AE Title, IP address, Port, and Layouts).
• You can check that the Printer is alive by clicking on the Check IP button then check that
the AE Title and the Port are OK by clicking on the Check DICOM button.
5. • Scroll down to access the next set of parameters
• Enter the next set of parameters as specified by the IT admin or the printer Vendor FE.

152 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

Installation of a new AW Server

6. • When done, click the Apply button.
7. • Proceed with the next printer declaration.

2.18.3 Configuring PostScript Printers

This feature is not available with Seamless integration
1. • Click PostScript Printers.
The "Perform PostScript printers configuration" interface displays.

2. • Click on Add button

The "Perform PostScript printers configuration" interface expands.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 153

2.18 Job Card IST010 - Administrative Configuration

3. Refer to A.2 Specific field - Characters rules and limitations on page 361 for characters rules and
limitations.
Following the rules and limitations, enter all available information for the printer. Note that all
fields are mandatory.
Do these steps for each PostScript printer to be added.
4. • Enter the parameters as specified by the IT admin or the printer Vendor FE (Name, IP
Address, Port, and Paper size).
5. • When done, click the Apply button.
6. • Proceed with the next printer declaration.

2.18.4 Users (EA3) (User account configuration)

Follow the guidelines hereafter to manage the Service, Admin and/or Standard users.
For Full or Seamless Integration with the PACS, Client Users are defined at the Universal Viewer
level, not at the AW Server level so you can bypass the following steps.

NOTICE
EA3 configuration page may not be properly working in IE9 and IE10 web browsers.
Preferably use IE8, IE11, Chrome and Firefox to load and use the EA3 configuration
page.
The USER ACCOUNT configuration utility is used to create and modify user accounts, server
information for an existing enterprise user account network, establish groups for the user accounts,
and assign levels of access or roles for the user groups.
There are TWO ways to establish user accounts:
• Local user accounts
• Active Directory or enterprise user accounts
The site IT administrator should make this decision. Use only one method or the other, NOT both, to
avoid potential group permission conflicts and unnecessary administrative complexity.
You will now create two local accounts, including one account for the site IT administrator.
NOTE
Involve the site IT admin when setting up local user or enterprise accounts, since they will
administer these accounts after system handoff.
• If the site IT admin wants to use local user accounts, perform the “Local User Account
Configuration” procedure.
• If the admin wants to use Enterprise user accounts, perform the “Enterprise User Account
Configuration” procedure.

154 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

Do NOT perform both procedures.

1.) □ Click on Users (EA3).

The “Perform Enterprise Authentication, Authorization and Audit configuration” page will display at
the Local Users tab.

Installation of a new AW Server

2.18.4.1 Local User(s) Account Configuration
There are four built-in “local” accounts, and corresponding built-in groups. The assigned role of each
account corresponds to the account name.
• Admin account = Admin Role (Almost ALL service tools access)
• Limited account = Limited Role (No service tool access)
• Service account = Service Role (ALL service tools access)
• Standard account = Standard Role (Few service tools access)
Keep these accounts and their logins for the use of GE Service Support, if possible! If the customer
objects to all of these accounts, remove the standard and limited accounts, but NOT the service and
admin accounts.
NOTE
THE “SERVICE” ACCOUNT cannot be removed. It is permanent, and is essential for GEHC
service access!
Create an IT admin user account.
You will now create a local account for the person who will be responsible for managing site
accounts.This is typically the IT admin

1.) Select the Local Users tab at the top of the page.
2.) If possible, have the IT Admin or User Account Administrator observe this procedure to learn how to create
and modify users.
3.) Click on Add Local User.
The Add User window will pop-up.
4.) Enter the IT admin’s User ID. This will be the “Username” that displays for login and administrative purposes.
DO NOT CREATE A USER ID NAME WITH SPACES IN IT.
5.) Enter the IT admin’s Full Name.
6.) Have the IT admin enter the desired password twice (once in “Password” and again in “Confirm Password”. If
the IT admin is not there, create a password for them and make a note of it.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 155

2.18 Job Card IST010 - Administrative Configuration

The password may be refused by the system if too short. Make sure to choose a password with a minimum
of 8 characters, including letters and numbers.
Refer to the guidelines given in 2.14 Job Card IST006 - Changing the Passwords on page 93 for choosing a
secure password.
7.) After completing the user information and password creation, click Add User. The new user Username (User
ID) and Full Name should now appear in the middle frame area.

Adding the New User to a Group

You will now add the new user to one of the existing groups – admin, limited, service, or standard.
The group they are assigned to determines their access privileges

1.) Click Add To Groups. The Add Membership For User (name) should pop up with a window area listing the
four built-in groups.
2.) Select the appropriate group for this new user account.
• If this user account is for the site IT or user admin person, select the admin group.
• If the user account is for a standard site physician or site user, select the standard group.
User/role access rules are described in detail in the Service Tools Section of the AW Server Service Manual.
3.) Click Add Membership. The user will be added to the selected group, and the group name will appear in the
Groups window.
4.) Click on Apply Configuration at the bottom of the page.
The message “Configuration Applied”, with a green background, will be displayed momentarily beneath the
“Restore Configuration” buttons if the apply action is successful.
If it is not successful, there could be a problem with the data entered, or with the system in general. Attempt
another account creation, and see if it works, or, remove the new account and try the “Apply Configuration”
again.
5.) If the IT admin wants you to add another user, repeat the above steps of this procedure. Do not add more
than two users. Additional users must be added by the customer, NOT by the GEHC FE.
Once this procedure is demonstrated to the IT or User Account admin, the admin should take over
configuring and managing the site's user accounts.

“Restore Configuration” button

The Restore Configuration button restores the last successfully-applied user/group configuration. It
does NOT restore “system” configuration.

NOTE
If you have configured a new user, but have not successfully applied it yet, the Restore
Configuration button will reload the current or last configuration, thus deleting the new
user. A new user will not be available for Restore until Apply Configuration is
successfully applied.
Default Passwords
The default passwords are provided in the Advanced Service Manual, chapter 1 section 1.3.1 System
Default Passwords.

156 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

NOTICE
Keep these passwords for the built-in accounts for GEHC knowledge and use only.
Setup the Admin account above with its own dedicated password. If there are site IT
Admin rules that require knowledge of the built-in account information, and perhaps
require the passwords to be changed – this should be complied with as long as the
service center or online center process for documenting these changes is adhered
to.There should NEVER be a case where the OLC cannot access the tools because a
2
built-in account change was not communicated.

Installation of a new AW Server

2.18.4.2 Configuring Enterprise User(s) Accounts
Do this procedure only if the site IT Admin or site User Admin has Enterprise Server information for
use. If there is no Enterprise Server data in the Site Survey, and /or IT does not have the data, only
Local User Accounts can be configured.
1. Click on Enterprise at the top of the page.
The following screen displays.

2. At the top of the page, enter the following settings:

• Enable Enterprise Authentication: This must be enabled (checked) to allow enterprise
users to access the server.
• Cache Enterprise Users: (The site’s IT admin should make this decision.) Checking this box
allows users who have previous successful logins to access the server during temporary
authentication-server outages.
• Enterprise Authentication Latency (Seconds): Set this to 10 seconds unless the IT
admin wants a different value. (This determines how long before timeout.)
3. Configure the enterprise server by entering all information needed for the right-hand column
(the Server Configuration and LDAP Configuration areas). There are two ways to do this:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 157

2.18 Job Card IST010 - Administrative Configuration

• Semi-Automatic Configuration: Follow the steps in the Configuration Instructions panel on

the left side of the page. This will automatically enter configuration data into the right-hand
column. If this method does not complete successfully, use manual configuration.
• Manual Configuration: Enter all configuration data manually, using information from the site
survey document and/or the IT admin.
NOTE
It is recommended to use an encrypted communication protocol (SSL protocol) if
available, to avoid passwords to be sent in clear, and a certificate validation to
avoid Enterprise Server to trust any available server certificates. To enable the SSL
protocol and use certificate validation, refer to AW Server 3.2 Advanced Service
Manual 5771771-1EN Appendix Enterprise Tab. Check with the site’s IT admin or
contact the OLC for help.
4. If the site survey document contains only the IP address or the Parent Domain Name of the
Active Directory and the authentication with SSL connection fails:
• Ask the IT admin to supply the Active Directory Server certificate Common Name (also
called FQDN (Fully Qualified Domain Name)) and use it as Server Name / IP.
• Or proceed to the following:
a. Open a Terminal tool on the AW Server and login as root.
b. Type the command:
openssl s_client -connect <Parent Domain Name>:636 | grep -i
CONTROLLER
Find <Parent Domain Name> from the site survey document and/or the IT admin.
The following lines appear:

0 s:/CN=<FQDN>/OU=DOMAIN-CONTROLLER/OU=MULTI-ALLOWED
subject=/CN=<FQDN>/OU=DOMAIN-CONTROLLER/OU=MULTI-ALLOWED

For instance:

0 s:/CN=DCCINOHP0103.logon.ds.ge.com/OU=DOMAIN-CONTROLLER/OU=MULTI-
ALLOWED
subject=/CN=DCCINOHP0103.logon.ds.ge.com/OU=DOMAIN-CONTROLLER/
OU=MULTI-ALLOWED
c. Copy the Active Directory Server certificate Common Name (CN), from the <FQDN> into
the Server Name / IP field.
d. In the Configuration Instructions panel, follow instructions from Step 1 to Step 5.
5. Click on Apply Configuration (at the bottom of the right-hand column), no matter which
configuration method you used.
6. To verify that the enterprise configuration was successful, do the following steps from the
Configuration Instructions panel:
a. Click on Test Connection. If the connection is successful, the message CONNECTION OK
(on a green background) appears briefly next to the button.
b. Enter an enterprise Username and Password, then click the Login button.
For example:

158 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

Installation of a new AW Server

If both tests are successful, the enterprise configuration is correct.
Proceed to 2.18.4.3 Assigning User Roles on page 159.

2.18.4.3 Assigning User Roles

Assigning roles to new enterprise users determines their access privileges for AW Server
applications and/or tools. This is done by mapping the enterprise user account group to one of the
existing built-in roles: Administrator, Limited User, GE Service, or Standard User.
1. Acquire group/role information for the enterprise user(s) setup in the site IT Domain. There are
at least two ways to do this:
• Get the information from the site IT Admin or site User Account Admin.
• Get the information from the Users (EA3) > Enterprise > Login test utility. After a
successful enterprise login test, the Login Results window will show the information. You
may have to scroll down to see the complete information set.
The data of interest in this example is the information starting with “Group Membership”. The
data is set up by the administrator of the enterprise server.
NOTE
In the Login Results window, some browsers might not let you scroll down far enough
to see the entire data list if the list extends “below” the bottom of the window. One
workaround is to use your left mouse button to select the text and drag the cursor
down until the “hidden” information is visible.
2. Click on Groups > Add Enterprise Group.
The Add Enterprise Group window appears on the top of the Groups tab window:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 159

2.18 Job Card IST010 - Administrative Configuration

3. Enter the group information acquired from the Enterprise Login Results window.
4. Click on Add Group.
The added group appears in the Enterprise Groups list in the lower left window frame.
5. Click on Apply Roles.
A green Configuration Applied box briefly appears next to the apply button. If so, the group
and role configuration was successful.
Make sure the site IT or account administrator knows how to use these processes to add, delete, and
manage their accounts.

2.18.5 Smart Card configuration

This feature is only available for sites allowing “two-factor authentication” authentication
method and with a specific agreement, as it requires specific integration on site.
A two-factor authentication method is a two-step verification method using two pieces of evidence
(or factor) to authenticate.
AW Server supports client certificate authentication. The client certificate and its private key can
originate from the certificate store of the operating system or from tamper-resistant physical
devices, such as smart cards or USB tokens, providing two-factor authentication in the latter case.
Thus, Smart Card is a two-factor authentication method which improves the security of user login.
NOTE
Please contact your GE Sales or Service representatives to check if this feature is
available on site.

160 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

1.) Make sure the AW Server is in Maintenance mode or place it under Maintenance. Refer to A.4 Maintenance
Mode on page 369 for details.
2.) Make sure that the network configuration is correct:
• From the Service Tools menu, click on Maintenance to expand the menu.
• Then click on Network.
• Select DNS settings tab.
2
The DNS configuration page displays:

Installation of a new AW Server

In case the site’s DNS server(s) have not been set up during the early installation steps (see 2.13 Job Card
IST005 - Network and Time Configuration on page 88), you can configure it (them) through the Service Tool,
as described in A.9.7 Launching the Internet Navigator from the Server’s KVM on page 421.
3.) Make sure the Time configuration is correct.
Date and time setting and NTP server can be configured from the Service Tools on Initial configuration
menu and Time Settings sub-menu. Refer to Sections 2.16.6.1 Date and Time menu on page 114 and
2.16.6.2 Time Server menu on page 115.
4.) Return to the Administrative menu and Configuration sub-menu.
Click on Smart Card Configuration. The Smart card login configuration page displays.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 161

2.18 Job Card IST010 - Administrative Configuration

5.) At the top of the page, enter the following settings:

• Enable Smart Card Login – This must be enabled (checked) to allow Smart card authentication.
6.) You will now configure the Active Directory Settings.
Smart card login uses an Active Directory (LDAP server) to query user attributes and user groups.
To execute queries against the Active Directory server, a dedicated bind user with read privileges is needed.
The service will use the bind user's username (specified in DN or domain format) and password to look up
the user's record in the Active Directory.
NOTE
It is possible to use an LDAP server which is not an Active Directory. In this case the
below fields must be properly configured from information supplied by the site’s IT
Admin.
NOTE
For the fields below, refer to the site’s IT Admin to get the right values and confirm
that the pre-populated values are correct.
• Use SSL – If secure LDAP is supported, check the Use SSL check box. Please refer to the site’s IT Admin
for more details
NOTE
If you use LDAP authentication without SSL, user credentials will be sent in
clear.

162 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

• Server name / IP - Enter the name or IP of the Active Directory server (LDAP server).
• Port - This is the port on which the LDAP server is listening. Leave empty, except if it is different from 389
for plain LDAP or 636 for secure LDAP.
• User - This is the bind user DN, used to bind the actual user and password. It can be specified using an
LDAP DN (CN=John Smith,CN=Users,DC=logon,DC=example,DC=com) or using account name and realm
name ([email protected], LOGON\john).
• Password - The password for the user name specified in the User field. 2
• DN - This is the base DN for LDAP search; it is the point in the LDAP tree from where the service will
search for users.

Installation of a new AW Server

The directory subtree from this node should contain all user records.
If EA3 enterprise authentication is configured, you can use the value as the DN field there.
Specify an LDAP DN such as DC=logon,DC=example,DC=com.
• Login Name Attribute, First Name Attribute, Last Name Attribute, Group Attribute, UPN
Attribute - These are the Active Directory attributes. They are pre-populated. If not contact your site’s IT
Admin.
7.) JSON Web Token (JWT) Settings:
JWT Secret - Click the Generate button to generate a JSon Web Token secret.
8.) Proxy settings:
This is used to obtain the revocation of the certificates. By default, Direct (No Proxy) is checked.
If the AW Server needs a proxy to address that, check Manual Proxy Configuration and enter the following
settings (contact the site’s IT Admin for the values):
• Set the HTTP Proxy (IP or name).
• Set the Port (HTTP Proxy port).
9.) Set up trusted CA certificates:
This is the bottom part of the Smart card login configuration page..

For a client certificate chain to be considered valid, the issuing certificates must be trusted. Public
certificates of root Certificate Authorities and subordinate issuing Certificate Authorities must be uploaded
to the AW Server. The files must have a .cer extension and be PEM-encoded.
• Download the client CA certificates and upload them to the AW Server using the Choose Files and Send
To System buttons.
The certificates are displayed in the Certificates on Server field.
10.) You can remove a certificate as follows:
• Select he certificate you want to remove in the Certificates on Server field.
• Click on the Remove Selected Certificates button.
The certificate is removed from the Certificates on Server field.
11.) Click on Save Configuration at the bottom of the page to save the Smart Card login configuration.

Assigning Smart Card User Roles

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 163

2.18 Job Card IST010 - Administrative Configuration

Next, you will assign the new Smart Card user a ROLE, which will determine their access privileges
for AW Server applications and/or tools. This is done by mapping the Smart Card user account group
to one of the existing built-in roles – Administrator, Limited |User, GE Service, or Standard User.
Acquire GROUP/ROLE information for the Smart Card user(s) setup in the site IT Domain:
• Get the information from the site’s IT Admin or site User Account Admin.

1.) Assigning Smart Card User Roles is performed using EA3 Enterprise Groups Configuration:
• Click on Users (EA3).
• Click the Groups Tab, then click on Add Enterprise Group.
The Add Enterprise Group window displays.
2.) Enter the group information acquired from the site’s IT Admin:
• Click on Add Group.
The added group should now appear in the Enterprise Groups list in the lower left window frame.
3.) With the new enterprise group selected, click the appropriate ROLE check box in the Roles frame. Most
normal physician or technologist-type users could be assigned to Standard User role (as an example):
• Click on Apply Roles.
A GREEN “Configuration Applied” box should briefly display next to the apply button. If so, the group and
role configuration was successful.
4.) Make sure the site IT or account administrator knows how to use these processes to add, delete, and
manage their accounts.

Setting up Smart Card reader and Windows driver

Smart Card has been tested with
• SITHS cards and the NetID driver supplied by SecMaker
• YubiKey and its Windows driver
Check with your site’s IT Admin if ones of the above technology can be used to set up Smart Card
reader and Windows driver.

2.18.6 Client Timeout

This feature is not available with the Seamless integration.
Managing Clients is done through both Administrative Configuration and/or Administrative
Utilities.
Client timeout allows to set up the time limit for inactive client(s) before they are disconnected.
When a client is inactive for the specified period of time, the AW Server will send it a warning
message that it is about to be disconnected. If the warning period expires with no acknowledgment
from the user, the client will be logged out.
Client timeout is enabled by default. However, it can be disabled or updated by the IT administrator
of the site.
The warning message (broadcast message) can be set by the IT administrator of the site through
2.18.11 Administrative Utilities on page 172.
Client timeout settings
Use this to set up the time limit for inactive client(s).
1. From the Service Tools menu, click on Administrative to expand the menu, then click on
Configuration, and then select Client Timeout.

164 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

Installation of a new AW Server

2. Enable Inactivity Timeout is checked to automatically disconnect inactive client(s) after the
specified time. Because the AW Server only allows a certain number of slices to be processed,
disconnecting inactive client(s) allows other users to have access to the AW Server. If you do not
want inactive client(s) to be disconnected, un-check this box.
3. Enter the Minutes to wait before displaying message value.
The default is 15 minutes. After this amount of time, a default disconnection warning message
will be sent to the inactive client(s).
4. Enter the Minutes to wait before automatically logging out the user value. The default is 5
minutes. After sending the disconnection message, the Client will wait for this amount of time,
and will then automatically auto-disconnect.
NOTE
Note for Integration: If your site is going to be integrated with RIS or PACS, we
recommend to use the following settings for the Client timeout:
• Minutes to wait before displaying message = 20’
• Minutes to wait before automatically login out the User = 30’
5. When you have configured the timeout settings, click the Apply button.

2.18.7 Preprocessing Configuration

NOTE
Entering the pre-processing license is a pre-requisite to configuration.
This shall be done through Initial configuration/Licensing. See section
2.16.10.1 Preprocessing configuration menu on page 123
NOTE
To properly configure Preprocessing, it is necessary that the Volume Viewer applications
have been previously installed. See 2.17 Job Card IST009 - External Application(s)
Installation on page 132.
This page is used to configure preprocessing. When new instances become available, the AW Server
will search the Series Descriptor of the new series for the Series Descriptor words configured in the
Service Tool Preprocessing configuration screen.
If a match is found, the corresponding application will start automatically and save the results in a
save state series.
For example, if you enter "CTA head" in the descriptor field for Head-AutoBone Xpress, the AutoBone
Xpress application will start without user intervention and save the results in a "save state" series.
AW Server becomes aware that new data are available in different ways, depending on the
integration mode:
• No-Integ or Hybrid: When new data are sent to the AW Server

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 165

2.18 Job Card IST010 - Administrative Configuration

• Seamless: When AW Server receives Notification from PACS (Universal Viewer Server).
• DICOM Direct Connect: When AW Server receives a DICOM Instance Availability Notification
(IAN) notification from the PACS/VNA.
PACS/VNA must be configured to send IAN notification to AW Server AE-title: <AWS_AE-
title>_ds (do not forget the "_ds").
Refer to the EA administrator to configure the IAN notification.
NOTE
In cluster configuration, the AW Server AE-title of the first node can be used. If this node is
in maintenance or shutdown, preprocessing will not work.
1. From the Service Tools menu, click Administrative, then click Configuration, then click
Preprocessing.
What you actually get on the screen may differ from the example below, depending on the
Applications installed.

2. Click the box next to an application to make the text box active. See example above.
3. Type in a series descriptor that the AW server will use to search.
If the series description of the new series contains the words entered in the series descriptor
box, processing on that series will automatically begin and the results will be saved to a “save
state” series.
NOTE
If the series description of a new series contains words matching multiple configured
words, then only the first corresponding application will be launched.
4. After configuring the preprocessing, it is recommended to reboot the AW Server to take into
account this functionality. You can also wait and continue with the other configuration steps
and reboot later to avoid multiple reboot.
5. After configuring the preprocessing, it is recommended to test the full functionality to ensure
configuration is successful:
• In No-Integ / Hybrid integration mode push new series to the AW Server.

166 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

• In Seamless integration mode, select a dataset in Universal Viewer browser and click
Verified.
• In DICOM Direct Connect integration mode, push new series to the PACS/VNA and make
sure “IAN” notification is configured on the PACS.
Test that the new "Auto Save State" series created by preprocessing arrives at the destination
via the End of Review feature. 2
NOTE

Installation of a new AW Server

The End of Review shall be configured prior to testing preprocessing.

2.18.8 MailSender Settings

You will now configure the MailSender service. This service allows applications, which use email
service, to send email reports to predefined contacts/recipients.
NOTE
Entering the MailSender license is a pre-requisite to configuration.
This shall be done through Initial configuration / Licensing. See section
2.16.10.2 MailSender on page 123.

WARNING
It remains the responsibility of the user to configure the send by email functionality
with a secure mail server and ensure compliance with regulations for email delivery to
IT administrative configured recipients.

WARNING
The send by email functionality is intended to help facilitate communication between
clinicians. Patient management should not be dependent on receipt of email
communication.

WARNING

Email content contains limited PHI such as a unique exam identifier and time of scan.

1. Display the MailSender Settings page:

From the Service Tools / Administrative menu, click on Configuration then on MailSender.
The MailSender service page displays:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 167

2.18 Job Card IST010 - Administrative Configuration

2. Enable the MailSender service:

• Check the Enable MailSender chek box.
3. Configure the local SMTP mail server:
• Enter the mail sender address in the Sender Address field.
NOTE
You only need to enter the domain name of the hospital’s mail address, the part
after @.
NOTE
This is the email address of the sender of the email. It will contain the name of
the application and the name of the host corresponding to the application/host
from which the report will be sent. The user will not be able to reply to this
address.
• Enter the mail server address (enter IP address or fully qualified domain name) in the SMTP
Server Address field.

168 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

NOTE
Refer to the site’s IT Admin to obtain the local mail server address.
• Enter the mail server port number in the SMTP Server Port field.
NOTE
Refer to the site’s IT Admin to obtain the actual port number.
• Select the mail server security level (TLS protocol with usually port 587 or No for plain
2
SMTP with usually port 25) in SMTP Security Level field.

Installation of a new AW Server

WARNING

For security reasons, use of plain SMTP mail sending is highly discouraged.
Using a TLS service is strongly advised for security purposes.

4. Upload the SMTP Server CA Certificate:

• Click on Choose File and select the CA certificate in the window that opens.
NOTE
Refer to the site’s IT Admin to obtain the CA certificate.
• Click on Upload to upload the CA certificate to the AW server.
NOTE
You can remove the CA certificate by clicking on the Remove button.
• Enter the Notification Address email to notify the customer on certificate expiration.
NOTE
This is not the address on which emails generated by applications will be sent to.
Refer to the site’s IT Admin to obtain the email address.
The following messages will display in the Service Tools when the certificate expire soon or
has expired.

Click on Click here for details to open the MailSender configuration page.
5. Test the connection:
Click on Test Connection button to check that the SMTP server accepts SMTP connection with
the selected security level.
The Success label highlighed in green displays momentarily if the connection is successful.
6. Click on Apply button to save the information entered.

2.18.8.1 Configure the contact/recipient

Each application using the email service shall configure the email address of the recipient(s) to which
it will send the reports.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 169

2.18 Job Card IST010 - Administrative Configuration

NOTE
Perform this steps when installing the applications which uses the email service. This is
described in the corresponding application service documentation. Below is an
example for FastStroke application.
1. From the Service Tools / Initial Configuration menu, click on Contact to display the Set up
contact info page.
2. Select Add button to configure an email application contact.

3. In the fields that displays, enter the Type, the Name and the E-mail address of the recipient.
NOTE
E-mail is the address to which generated email will be sent.
NOTE
You can enter several email addresses separated by a comma.
NOTE
Refer to the site’s IT Admin to get the email address(es).
NOTE
Check the spelling and the format of the email address(es) you enter. A mistype
address may lead to a failure of the MailSender functionality as the recipients may
not receive the letters.
4. Click on Apply button to save the information entered.

2.18.9 End of Review

This page is used to configure "End of Review" processes. When enabled, the End Of Review feature
automatically sends processed images to a DICOM host when exiting the application (at tab closure).
It is configurable to send which image: "all" or "generated".
After completing a processing procedure, when the Users exit from the feature, they will be
prompted to choose whether you want to end review. If you choose yes, the AW Server
automatically forwards the processed series to any DICOM host connected to the server.

170 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.18 Job Card IST010 - Administrative Configuration

End Of Review must be configured for PACS integration, so that processed data is automatically
pushed to the remote system (PACS). Note that only generated data will be sent.

NOTICE
The Seamless Integration must be fully configured prior to configure End Of Review.
1. From the Service Tools menu, click Administrative, then click Configuration, then click End of 2
Review.

Installation of a new AW Server

2. In the Manage End Of Review page, under the Status heading, click the box next to the host
name to enable the “End of Review” process.
3. Use the drop-down menu under Type to select which series (generated, or all) will be
automatically sent to a networked host upon exiting an application.
4. Click the button under Modality to view all modality choices.
5. Click Select All or any combination of individual modalities that you want to be automatically
sent and click Apply.
6. Click Apply to save the changes.
NOTE
When the End Of Review configuration is changed, the change does not become
instantly effective for users that are logged-in, but will become effective starting from
the next login session.

2.18.10 AW Server declaration on DICOM images sources

The following is given for information only.
To declare your AW Server system to all the DICOM hosts (Image sources (i.e: CT, MR, etc.) which will
send images to the AW server proceed as follows. Note that the AWS HealthPage displays the host
name and AET.
• Host name: Enter AW Server host name
• Application Entity Title (AET) = Must be same as the host name
If the Host name of the AW Server is longer than 16 characters, the first 16 characters of the Host
name will be used as AE Title for the AW Server
• Port number = 4006 for AW Server

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 171

2.19 Job Card IST011 - Integration

• Query/Retrieve = supported
NOTE
Bypass this step for Full or Seamless integration. This step is not necessary, as a fully
integrated AW Server does not host an image database. The image data is only
resident on the PACS.

NOTICE
For DICOM Direct Connect integration, the AW Server shall be declared twice in
the DICOM hosts (PACS, VNA, etc.) which will send images to the AW server:
NOTE
One entry with the <host name>/<AET>, IP and port 4006 (as described above) for
standard DICOM functions.
The second entry with <host name>_ds/<AET>_ds, same IP and port 4010 for
DICOM Direct Connect.

2.18.11 Administrative Utilities

NOTE
Administrative Utilities menu does not contain tools or steps necessary at installation
time.
Administrative Utilities are described in the Advanced Service Manual, as well as in the
Administrator’s documentation.
The Administrative configuration is complete
Proceed to 2.19 Job Card IST011 - Integration on page 172.

2.19 Job Card IST011 - Integration

2.19.1 Foreword

2.19.1.1 Integration modes supported with AW Server

There are currently 6 different modes of PACS/RIS/DICOM Remote Host integration that can be met
on AW Server.
1. Standalone (No integration):
In this "non-integrated" mode, the AWS system will be totally independent from the PACS.
GEHC HCS will ensure sales, configuration and service of AW Server.
2. Full front end integration (Hybrid): (3rdPartyIntegration)
• 3rd Party integration and Hybrid integration share the same license key and setup menu.
• 3rd Party integration will only be accessible for upgraded AW Server 2.0 that were using
this mode.
In this integration mode, the AWS system hosts its own database. Selection synchronization will
be maintained between the remote host and AWS. No other synchronization will be available.
In Hybrid mode, the integrated AW Server client pulls the images DIRECTLY from the AW Server
database and REQUIRES them to ALREADY be present in the AW Server database PRIOR to

172 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

launching the integrated AWS client from the PACS client, otherwise the AWS client launch will
fail.
There is no automatic Query/Retrieve of the images from PACS in Hybrid mode. Images must be
pushed from the modality or from PACS ahead of launching the integrated AWS client. Most
likely the site will configure the CT and MR scanners to automatically push each series to the
AW Server.
2
• The target remote systems are the RIS, the competitor PACS (3rd Party PACS) and any other
systems (like CT acquisition console for instance).

Installation of a new AW Server

• GEHC HCS will ensure sales, configuration and service of AW Server.
• See 2.19.2 Full front end integration (Hybrid): (3rdPartyIntegration) on page 175
3. Seamless integration with the GE PACS
In seamless integration mode the image database is on the PACS only. There is nevertheless an
internal database for AW Server, intended to store the data generated on AW Server, before the
data is automatically sent to the GE PACS.
In addition, the Seamless integration will add a "3D Apps" button to the GE PACS Client
Universal Viewer, and when selecting an exam and clicking on the 3D Apps button, this will
propose a choice of currently supported 3D applications (purchased by the customer) and
launch the AW Server Client window.
Moreover, the viewer events and actions of the GE PACS system in Universal Viewer are
synchronized with the AWS application (e.g. mouse modes, paging, lights on/off).
• The targeted remote system is the GE PACS
• EDS will ensure sales, configuration and service of AW Server.
• See 2.19.3 Seamless Integration on page 179
Scalability:
• Multiple AW Server nodes can be configured in a cluster (scalable solution).
4. DICOM Direct Connect integration
In the DICOM Direct Connect integration mode, the image database is on the configured DICOM
storage providers (PACS/VNA/DICOM Remote Host) only. Nevertheless, the AW Server has also a
local database (which is not visible to the user) to store generated data. Using the End Of
Review feature, generated data can be sent to the PACS/VNA/DICOM Remote Host.
Two user workflows are supported:
a. Without 3rd party front-end integration – using the AW Server client
In this mode, the user selects the remote data in the AW Server client using the remote
host worklist, then launches the application.
b. With 3rd party front-end integration – using an integrated PACS/VNA client
In this mode, the user selects the data in the PACS/VNA's client and launches the
application. The PACS/VNA client passes the selection to the AW Server, and the AW Server
retrieves and loads the data from the remote system. (Here we need a reference for front-
end integration configuration).
Configuration:
• The PACS/VNA/DICOM Remote Host(s) must be declared on the AW Server as a DICOM
host.
• The End Of Review feature must be configured to send generated data to the PACS/VNA/
DICOM Remote Host.
• AW Server must be declared on the PACS/VNA/DICOM Remote Host twice:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 173

2.19 Job Card IST011 - Integration

• AE_title_AWS, port 4006

• AE_title_AWS_ds, port 4010
Scalability:
• Multiple AW Server nodes can be configured in a cluster (scalable solution).
See 2.19.4 DICOM Direct Connect integration on page 190 for full integration details.
NOTE
VNA stands for “Vendor Neutral Archive”. It is a DICOM images archiving system.
5. DICOM Direct Connect in CT/MR Smart Subscription on Edison HealthLink environment
The AW Server in DICOM Direct Connect integration mode can run on the Edison HealthLink of
the CT/MR Console environment and retrieves the data from the CT/MR Console database.
The AW Server client is integrated within the CT Console Client or on customer desktop for MR
Console.
• Refer to A.12 AW Server Integration in CT/MR Console Environment on page 433 for full
description
• See 2.19.4 DICOM Direct Connect integration on page 190
6. DICOM Direct Connect in CT Nano-Cloud environment
CT Nano-Cloud is a simplified version of the Edison HealthLink. in this case the AW Server VM is
hosted by the CT Console OS.
• Refer to CT documentation for full description
• See 2.19.4 DICOM Direct Connect integration on page 190

2.19.1.2 Pre-requisite for Integration

Database
• Full front end integration (Hybrid): (3rdPartyIntegration) mode: All patient and Study data
must reside on the AW Server and the 3rd party PACS prior to performing integration. The
DICOM patient and study data can be sent from the PACS system to the AW Server, or the user
needs to query and retrieve the data. Since in Full front end integration it is a prerequisite to
have all exam data available on AWS at application launch time, AWS database could be pre-
populated from the PACS. AW Server may query and retrieve the data.
• Front end & backend integration (Seamless and DICOM Direct Connect mode): Image data
are in the PACS database. They do not need to be in the AW Server database, which only
contains reconstruction images prior to send them to the PACS database.
• Modality devices shall be configured to send images (auto-push) to both the AW Server and the
PACS to ensure the databases contain the same information.Note that this is not necessary in
the Seamless integration (using the PACS database).
Software license key
• A software license key is required to enable Integration between the AW Server and a RIS, 3rd
Party PACS or GE PACS. License key is different for the different types of integration.
DICOM configuration
• The RIS or PACS system shall be properly declared as a DICOM Host in AW Server
• When configuring DICOM information for PACS Query Retrieve - Allow Query, Allow Retrieve,
Allow Store shall be enabled.
• PACS systems supporting Storage Commitment shall be configured on the AW Server.
End Of Review

174 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

• End of Review configuration is mandatory for Full front end integration and Front end & backend
integration. It is optional, but recommended for Basic front end integration..
• The TYPE of images to be sent to the PACS system when configured shall be set to "generated".
• All modality image types shall be enabled, unless the receiving PACS system does not support a
particular image type, then do not select this type of image.
Pre-processing 2
• Pre-processing is not mandatory to be configured when integrating to PACS, but would improve

Installation of a new AW Server

the perceived performance.
• AW Server requires a software license key to enable the Pre-processing feature.
AW Server Client
• AW Server Client must be downloaded and installed on the RIS/PACS workstations where
integration will be used by the customer.
• The directory path and executable (if not configured differently) are located on a client in:
C:\Program files\GE\AWS_3.2\solo\integration.exe
PACS Connector Plugin
• This is a piece of software delivered with the GE PACS, that shall be loaded on the AW Server for
full front end & back end integration with the GE PACS. Currently, for the Enterprise Archive (EA)
PACS, it is delivered on a CD media. Refer to the GE PACS documentation for installation
instructions.
PACS Integration Guide
• As part of an AW Server and RIS/PACS integration, provide the AW Server 3.2 PACS Integration
Guide document - 5535310-1EN to the RIS/PACS person so that they may configure the RIS/
PACS for the AW Server.

2.19.2 Full front end integration (Hybrid): (3rdPartyIntegration)

2.19.2.1 Configuration steps on the AW Server

1.) □ • Make sure the AW Server is still in Maintenance mode or place it under Maintenance.Refer to
A.4 Maintenance Mode on page 369 for details.
2.) □ • From the Service Tools menu, click on Initial Configuration to expand the menu.
3.) □ • Click on Platform Configuration.
The following menu displays:

Refer to 2.16 Job Card IST008 - Initial Configuration on page 108 at Platform Configuration for details.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 175

2.19 Job Card IST011 - Integration

4.) □ • Make sure the “Platform Enabler” license has been entered. If not, enter it now.
• When done, click on the Next button to change to the Scalability tab
5.) □ Scalability: Virtual AW Server to be placed into a cluster of virtual AW servers:
Scalability is only supported for Seamless and DICOM Direct Connect integration and with virtual AW
Server.

• Keep Single mode selected and click on the Next button to change to the Integration tab
6.) □ Full Front-End Integration(Hybrid): (3rd Party integration) option:
NOTE
Hybrid integration is available for new installations, basic 3rd Party integration
is only supported for AW Server 2.0 upgrades to AW Server 3.2..
Both types use the same license key.
• If your site has purchased the option, and you have a "3rd Party integration license" key, click on
Full Front-End Integration(Hybrid): (3rd Party integration).

• Enter the License key

• Enter the Authentication URL:
The "Authentication URL" is the URL link to the Web services of the remote system (subject to change.
Refer to the PACS documentation):
• Web service for CPACS: http://IMS_IP_address:9001/AWS/pacs/services
• Web service for Universal Viewer: http://IUV_IP_address/services/PacsWebService
• Web service for 3rd Party PACS - Leave the field blank.
NOTE
You can click on Check address button to check that the PACS system is alive.
NOTE
"3rd Party" PACS can be "synchronized" by the AW Server through Command
lines. The "3rd Party" PACS vendor can use these Command lines to

176 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

synchronize the AWS database with the PACS, referring to the AW Server 3.2
PACS Integration guide: 5535310-1EN
7.) □ Optional step
• Click on the Keep me logged in check box.
• Select a number of days before connection is closed - typically 1 day.
• Click on Generate button to automatically generate a Passphrase for connection security, or type
in the Passphrase chosen by the user.. 2
8.) □ • Click on the Apply button.

Installation of a new AW Server

The message "Please reboot" will display.
• You must reboot the AW Server now if you want to check that the integration is operational, or wait
and continue with the other configuration steps and reboot later.
NOTE
To reboot, use the Reboot button from Service Tools/Utilities, or open a
Terminal from Service Tools/Utilities, login as root and type in: reboot <Enter>

2.19.2.2 Configuration steps on the Universal Viewer

NOTE
Below are the steps to configure Hybrid integration with the Universal Viewer. This
procedure is subject to change. Refer to the Universal Viewer documentation.
For other PACS systems, refer to the PACS documentation.

2.19.2.2.1 Install the Universal Viewer Server

1.) □ • Install the appropriate software release of Universal Viewer Server (PACS system).
• Get the UV Installation/Upgrade Manual for the installed version at your site.
• Also check GEHC Documentation Portal for the late version of that doc for that release.

2.19.2.2.2 Edit the integrations.ini file on the Client PC

1.) □ It is necessary to indicate in the integrations.ini file the place where the AW Server Client is located.
• Go to the UV Client folder : C:\Program Files\Integrad.3\MIV
• Edit the file integrations.ini
• Find the section called "[HAWAII]"
• Modify the line SOLO_CLIENT_PATH to look as follows: SOLO_CLIENT_PATH=C:\Program Fil
es\GE\AWS_3.2\solo

NOTE
Path might be different depending on the Windows configuration (32-bit/64-
bit).
NOTE
When upgrading from AW Server 2.0 release, the path to integration.exe
changes from AWS_2.0 to AWS_3.2

2.19.2.2.3 Configure Site Configuration Tool

1.) • Connect to the Universal Viewer Server and launch the Site Configuration Tool.
2.) • In "AW integration" menu, configure AW Configuration" tab as follows
• Check "AWS 2.x Enable"

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 177

2.19 Job Card IST011 - Integration

• Check "Notification Enable" if preprocessing is installed and licensed on AWS (optional)

NOTE
If encryption is required for client-server communication using HTTPS, set it by
checking "Secure communication between solomini and AWS" is reserved
for Seamless integration.
• Fill the URLs with the Universal Viewer Server IP address
• IW WebService URL: http://<UV_IP_address>/services/PacsWebService
• AW Client URL: http:// <UV_IP_address>/services/AWWebService
• IIS Download URL: http://<UV_IP_address>:85
Configuration example.

3.) • In "AW integration" menu, click on "AW 2.x Servers" tab and configure as follows:
• Fill in IP address of the AW Server, and webservice :
AW field: http://<AW Server_IP-address>/proxyservice/awservice
CPACS field: http://IMS_IP_address:9001/AWS/pacs/services (only applicable if CPACS backend)
Configuration example.

4.) • "Apply" site configuration parameters (nothing displays in red)

• "Restart all "Integrad" services except the 2 SQL services

2.19.2.2.4 Configuration of Universal Viewer users

UV users should have ADM group = AWS 2.
Refer to PACS documentation for details.

178 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

2.19.2.3 Configuration steps on the Client PC

The AW Server Client and the Universal Viewer Client must be installed on the PC.
Refer to the Universal Viewer documentation and to 2.22 Job Card IST014A - Standard Client PC
installation & Tests on page 204 for the AW Server Client.
2
NOTICE

Installation of a new AW Server

Do not select the Client for Universal Viewer (reserved for Seamless integration). Use
Client for Windows.

2.19.3 Seamless Integration

This section details all the steps needed to configure the Seamless integration, in case of fresh
installation, re-installation or upgrade.
For your information:
AW Server 3.2 Installation Manual refers to the current Universal Viewer Installation and service
documentation for integration details on the UV side.
Get the UV Installation/Upgrade Manual for the installed version at your site.
NOTE
Also check GEHC Documentation Portal for the latest version of the docs for that release.
NOTE
In this document, the expression Universal Viewer Server refers to the Universal Viewer
Workflow Manager. Other components of Universal Viewer are explicitly mentioned when
needed.

2.19.3.1 Pre-requisites summary

Database
Seamless integration is using the PACS database, so AW Server does not contain images (apart from
reconstruction images generated on the AW Server that will be pushed to the PACS by the End of
Review feature).
Software license key
A software license key is required to enable Integration between the AW Server and the GE PACS.
The license key is based on the following keystring: Seamless_Integration.
Seamless connector plugin media (Dakota plugin media)
This client software library is delivered with the Universal Viewer / GE PACS for "Seamless"
integration. It must be loaded on the AW Server to enable "Seamless" integration with the PACS.
Currently, for the Universal Viewer, it is delivered as a RPM file on a media.
For information:
A similar plugin is delivered with the CPACS to enable "Full Frontend & Backend" integration with the
CPACS.
The installation and setup procedure of this seamless connector plugin is explained in the section
2.19.3.4 Seamless integration - configuration steps on AWS, Service Tools on page 184 Seamless
integration configuration steps on AWS, Service Tools" below.
Universal Viewer Server
The Universal Viewer Server shall be installed and configured. See 2.19.3.2 Seamless integration -
configuration steps on Universal Viewer Server on page 180

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 179

2.19 Job Card IST011 - Integration

2.19.3.2 Seamless integration - configuration steps on Universal Viewer

Server

Install the Universal Viewer Server

1.) □ • Install the appropriate software release of Universal Viewer Server (PACS system).
• Get the UV Installation/Upgrade Manual for the installed version at your site.
• Also check GEHC Documentation Portal for the late version of that doc for that release.
2.) □ • On the Universal Viewer Server, check that there is a file FetchUpNewAWSClient.vbs in the folder
C:\Integrad\Current\bin .

Configure Site Configuration Tool

1.) □ • Connect to the Universal Viewer Server and launch the Site Configuration Tool.
2.) □ • In "AW integration" menu, configure AW Configuration" tab as follows
• Check "AWS 3.x Enable"
• Check "Notification Enable" if preprocessing is installed and licensed on AWS (optional)
• If encryption is required for client-server communication using HTTPS, set it by checking
"Secure communication between solomini and AWS" .
• Fill the URLs with the Universal Viewer Server IP address
• IW WebService URL: http://<UV_IP_address>/services/PacsWebService
• AW Client URL: http:// <UV_IP_address>/services/AWWebService
• IIS Download URL: http://<UV_IP_address>:85
Configuration example.

• AW User: Indicate a user and its password in "User Id" and "Password". For example, the
recommended login/password in Universal Viewer Install Manual is: AWDakota .
(In our example snapshot, we used "AWUSER")
3.) □ • In "AW integration" menu, click on "AW 3.x Servers" tab and configure as follows:
• Fill in IP address of the AW Server, port 80 and webservice :

180 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

<AW Server_IP-address>/proxyservice/awservice
• If several AW Servers are integrated with the Universal Viewer Server, indicate each AW Server
in a separate row.
Configuration example.

Installation of a new AW Server

4.) □ • "Apply" site configuration parameters (nothing displays in red)
• "Restart all "Integrad" services except the 2 SQL services

Create an AW Server user

1.) • Connect to the administration of Universal Viewer Server in an internet browser by entering the
following IP address: http://<IP of the Universal Viewer Server>/admin
2.) • Create an AW User named for example AWDakota.
3.) • Configure ADM Group with Digital Imaging, Administrator and AWS 3, and configure Institution for this
user.
4.) • If the site has purchased the Pre-processing option, create an Pre-processing user named for example
AWPreProc with same password as AWDakota.

Configuration of Universal Viewer users

UV users should have ADM group = AWS 3.
Refer to PACS documentation for details.

Add Virtual Drive and Create MIME Type

1.) □ In the Server Manager

• Add a virtual drive named "storage" with path "C:\Integrad\Current\Data"
• Add two MIME types "dcm" and "jp2"
Refer to the Universal Viewer Installation Manual for more details.

Install the Universal Viewer Server

1.) □ • Install the appropriate software release of Universal Viewer Server (PACS system).
• Get the UV Installation/Upgrade Manual for the installed version at your site.
• Also check GEHC Documentation Portal for the late version of that doc for that release.
2.) □ • On the Universal Viewer Server, check that there is a file FetchUpNewAWSClient.vbs in the folder
C:\Integrad\Current\bin .

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 181

2.19 Job Card IST011 - Integration

Configure Site Configuration Tool

1.) □ • Connect to the Universal Viewer Server and launch the Site Configuration Tool.
2.) □ • In "AW integration" menu, configure AW Configuration" tab as follows
• Check "AWS 3.x Enable"
• Check "Notification Enable" if preprocessing is installed and licensed on AWS (optional)
• If encryption is required for client-server communication using HTTPS, set it by checking
"Secure communication between solomini and AWS" .
• Fill the URLs with the Universal Viewer Server IP address
• IW WebService URL: http://<UV_IP_address>/services/PacsWebService
• AW Client URL: http:// <UV_IP_address>/services/AWWebService
• IIS Download URL: http://<UV_IP_address>:85
Configuration example.

• AW User: Indicate a user and its password in "User Id" and "Password". For example, the
recommended login/password in Universal Viewer Install Manual is: AWDakota .
(In our example snapshot, we used "AWUSER")
3.) □ • In "AW integration" menu, click on "AW 3.x Servers" tab and configure as follows:
• Fill in IP address of the AW Server, port 80 and webservice :
<AW Server_IP-address>/proxyservice/awservice
• If several AW Servers are integrated with the Universal Viewer Server, indicate each AW Server
in a separate row.
Configuration example.

182 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

4.) □ • "Apply" site configuration parameters (nothing displays in red)

• "Restart all "Integrad" services except the 2 SQL services

Create an AW Server user

1.) • Connect to the administration of Universal Viewer Server in an internet browser by entering the
2
following IP address: http://<IP of the Universal Viewer Server>/admin

Installation of a new AW Server

2.) • Create an AW User named for example AWDakota.
3.) • Configure ADM Group with Digital Imaging, Administrator and AWS 3, and configure Institution for this
user.
4.) • If the site has purchased the Pre-processing option, create an Pre-processing user named for example
AWPreProc with same password as AWDakota.

Configuration of Universal Viewer users

UV users should have ADM group = AWS 3.
Refer to PACS documentation for details.

Add Virtual Drive and Create MIME Type

1.) □ In the Server Manager

• Add a virtual drive named "storage" with path "C:\Integrad\Current\Data"
• Add two MIME types "dcm" and "jp2"
Refer to the Universal Viewer Installation Manual for more details.

2.19.3.3 Seamless integration - configuration steps on AWS

DNS
DNS must be configured to fit the site's parameters. Refer to 2.13 Job Card IST005 - Network and
Time Configuration on page 88 and/or A.9 Useful Commands and Tools on page 419. This is
necessary to ensure that the AW Server will be able to connect to the different Universal Viewer
systems.
Auto Delete
Configure the Auto Delete feature so that local images are purged, for example after one day.
Refer to 2.16.7 Database Deletion Settings on page 115: Auto Delete.
DICOM Host
The RIS or PACS system shall be properly declared as a DICOM Host in AW Server. Detailed
instructions are available in 2.18 Job Card IST010 - Administrative Configuration on page 148.

NOTICE
The Universal Viewer can have 2 different type of back-end: IW back-end or CPACS
back-end.IW back-end case: for single server installation, declare the Workflow
Manager (which is also the back-end). For large installation, declare the IW back-end
as a DICOM host.CPACS back-end case: declare the CPACS DAS as a DICOM host.
• When configuring DICOM information for PACS Query Retrieve, Allow Query, Allow Retrieve,
Allow Store shall be enabled.
• PACS systems supporting Storage Commitment shall be configured on the AW Server.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 183

2.19 Job Card IST011 - Integration

End Of Review
End of Review must be configured with the DICOM host declared in the previous step "DICOM host
configuration". Detailed instructions are available in 2.18.9 End of Review on page 170
• The Seamless Integration (if applicable to your site) shall be fully configured before configuring
End of Review.
• The TYPE of images to be sent to the PACS system when configured shall be set to "generated".
• All modality image types shall be enabled, unless the receiving PACS system does not support a
particular image type, then do not select this type of image.
Pre-processing
It is not mandatory to configure Pre-processing when integrating to PACS, but it would improve the
perceived performance. Refer to 2.16.10 Licensing Configuration on page 123
• AW Server requires a software license key to enable the Pre-processing feature.
• If used in cluster mode, all AW servers shall have enabled and licensed Preprocessing.
Additionally, the same setup must be configured on each server (enable preprocessing for the
same set of applications, use the same series descriptor).
Seamless connector plugin (Dakota plugin)
See next section.

2.19.3.4 Seamless integration - configuration steps on AWS, Service Tools

By default the Server is in Standalone (Non-Integrated) mode. Only execute the following procedure
if you have to configure the Seamless Integration.
Please refer to the PACS documentation for detailed information on the UV’s settings.

2.19.3.4.1 Dakota plugin installation steps

1.) • Make sure the AW Server is still in Maintenance mode or place it under Maintenance. Refer to
A.4 Maintenance Mode on page 369 for details.
2.) Dakota plugin installation.

184 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

• From Service Tools /Tools menu, open the Terminal and login as root.
• Check for the eventual presence of an older Dakota package, and if present, remove it prior to load the
one delivered with your PACS system.
• Check for a Dakota package
rpm -qa | grep Dakota <Enter>
• If a package is present, remove it now
rpm -e Dakota* <Enter> 2
3.) • If the Dakota plugin is delivered as part of a media (CD or USB device for example), insert the media

Installation of a new AW Server

containing the Dakota plugin package into the DVD drive or a USB port of the Client PC.
4.) • Load the PACS Connector "Dakota" Plugin from the SW media (or link) delivered with the PACS.
• From the Tools menu, select the File Transfer tool in order to load the DakotaClient-X.X_xx.rpm
package to the server. I.e: DakotaClient-5.x86_64.rpm
• Select the To system tab
• Browse to the DVD drive or USB device of the Client PC or local repository where you have previously
stored the plugin.
• Select the Dakota client
• Select the standard Service Tools Upload directory /var/lib/ServiceTools/upload as target.

5.) • Click the 'Browse' button and choose the rpm to deploy from your local machine, for example:
• Click on Send to system button:

A message confirms the successful upload.

6.) • Install the PACS "Dakota" Connector plug-in on the AW Server:
• From the Service Tools menu, select Tools > Terminal, if not done yet.
• Login as root and execute the following commands to double-check the upload is present:
cd /var/lib/ServiceTools/upload <Enter>
ls -ltr <Enter>
I.e: -rw-r--r-- 1 tomcat tomcat 85259662 Jul 24 15:20 DakotaClient-5.x86_64.rpm
• Enter the following command in the Terminal window to install the package:
rpm -Uvfh DakotaClient-X.X_xx.rpm <Enter> (where X.X_xx is the package release number)
I.e: rpm -Uvfh DakotaClient-5.x86_64.rpm
NOTICE
Always use the latest available Dakota plugin. Refer to the PACS documentation for the
latest available plugin.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 185

2.19 Job Card IST011 - Integration

2.19.3.4.2 Seamless Integration setup steps

1.) • From the Service Tools menu, click on Initial Configuration to expand the menu.
2.) • Click on Platform Configuration.
The following menu displays:

Refer to Platform Configuration for details.

3.) • Make sure the “Platform Enabler” license has been entered. If not, enter it now.
• When done, click on the Next button to change to the Scalability tab
4.) Scalability: Virtual AW Server to be placed into a cluster of virtual AW servers:
• If your AW Server shall be part of a cluster of virtual AW Servers, the Cluster mode radio button must be
checked.
You will be prompted to enter the IP address of the two HAPS server nodes.

If applicable for your site, Scalability configuration shall be done as part of 2.20 Job Card IST012 - Virtual
Servers Cluster Configuration on page 196
• When done, click on the Next button to change to the Integration tab
5.) Now you can setup integration
• Go back to the Service Tools / Platform Configuration menu:
Refer to Platform Configuration for details.
• Click on Platform Configuration sub-menu, and directly click on the Next button
• Click on Scalability sub-menu, and directly click on the Next button
The Integration sub-menu displays:

186 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

Installation of a new AW Server

• Integration Enabler:
Select Seamless integration check box and enter the parameters as shown hereafter:
6.) • Connector plugin:
Select the Dakota Client Library plugin from the pull down menu
• License key:
Enter the license key for Seamless Integration
(keystring : Seamless_Integration)
• Source:
http://<IP address of UniversalViewer_server>/services/PacsWebService
NOTE
Enter the IP address of the Universal Viewer Workflow Manager Controller
(regardless of the type of back-end used: IW or CPACS)
• Preprocessing user:
It is an Universal Viewer user (in our example, we use the default AWPreProc user). For the preprocessing
User and Password, enter valid values for a Universal Viewer Database preprocessing.
• Institute Name: Enter the hospital name or any other suitable information.
• If you are using CPACS integration, leave this field blank.
• If you are not using CPACS integration, enter the institution name of the Universal Viewer Database
server.
7.) • Now click on Apply to enable the Seamless integration configuration.
The following confirmation messages display when the integration mode is applied:
All the DICOM data stored in the database will be deleted !
It is strongly recommended to transfer the data to a remote system.
Please contact the IT Admin and check which images need to be saved on PACS. Do you want to
continue the configuration now ?

NOTICE
If this is a new installation, no images are present in the AW Server database.In case of
upgrade, make sure with your customer that all image data has previously be stored on
another system prior to continue.
• Click OK to acknowledge.
The following popup message displays:
All the DICOM data stored in the database will now be deleted !
Do you want to proceed with the configuration now ?
• Click OK to acknowledge.
Please reboot the system

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 187

2.19 Job Card IST011 - Integration

• Click on OK to acknowledge the message.

8.) • Prior to reboot your system, verify that Exam series images will be loaded using the Dakota client plugin:.
In the Terminal window type:
• cd /export/home/sdc/integration/plugindata <Enter>
• ls -ltr <Enter>
The softlink 'current' should point to Dakota Client as shown in the example below.

9.) • Reboot the server now

OR
proceed to the other features configuration steps first, then you will shutdown and reboot when the
other configuration steps are done.
• When done, in the Terminal window type:
• reboot <Enter>
10.) • Now you can configure the End Of Review feature.
Refer to 2.18.9 End of Review on page 170

2.19.3.5 Seamless integration - configuration steps on Universal Viewer Client

PC
AWS Integrated Client will be installed later as part of 2.23 Job Card IST014B - Seamless Client PC
installation and Tests on page 226
Do not install it now.

2.19.3.6 Seamless integration - configuration steps on Image Sources

Image Database:
Modalities shall be set to auto-push images to the PACS.

2.19.3.7 Seamless Integration - configuration checklist

This section intends to provide a high level checklist of all steps required for seamless integration on
each system: AW Server, Universal Viewer Server, Universal Viewer Client PC. This can be used as a
troubleshooting help to ensure that no steps were missed during the configuration.

2.19.3.7.1 On the AW Server side

Step Check Action On Further details, refer to:

1.) □ DNS is configured as part of Network AW Server AWS IM, 2.13 Job Card IST005 -
configuration Network and Time Configuration
on page 88
2.) □ Auto-delete is enabled AW Server AWS IM, 2.16 Job Card IST008 -
Initial Configuration on page 108
3.) □ The Universal Viewer Server is AW Server AWS IM, 2.18 Job Card IST010 -
properly declared as a DICOM Host in Administrative Configuration on
AW Server (2 cases: IW back-end and page 148
CPACS back-end)

188 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

Step Check Action On Further details, refer to:

4.) □ Optional step: Pre-processing is AW Server AWS IM, 2.16 Job Card IST008 -
configured. Preprocessing license is Initial Configuration on page 108
entered.
5.) □ The "Dakota" Integration plugin has AW Server AWS IM, 2.19 Job Card IST011 -
been loaded from the media and is Integration on page 172 ; 2.16 Job
installed on AWS Card IST008 - Initial Configuration 2
on page 108

Installation of a new AW Server

6.) □ The "Seamless" software license key AW Server AWS IM, 2.19 Job Card IST011 -
is entered to enable the Integration Integration on page 172 ; 2.16 Job
mode Card IST008 - Initial Configuration
on page 108
7.) □ The Dakota Library item is selected AW Server AWS IM, 2.19 Job Card IST011 -
in the Connector plugin drop-down Integration on page 172 ; 2.16 Job
list. Card IST008 - Initial Configuration
on page 108
8.) □ The PACS web service URL is entered AW Server AWS IM, 2.19 Job Card IST011 -
in the Source field. Integration on page 172
9.) □ Preprocessing parameters are AW Server AWS IM, 2.19 Job Card IST011 -
entered (user, password, Institution) if Integration on page 172
applicable
10.) □ AW Server has been rebooted to take AW Server AWS IM, 2.19 Job Card IST011 -
into account the Integration Integration on page 172 ; 2.16 Job
configuration. Card IST008 - Initial Configuration
on page 108
11.) □ End of Review is configured AW Server AWS IM, 2.18 Job Card IST010 -
Administrative Configuration on
page 148,

2.19.3.7.2 On Universal Viewer Server

Step Check Action On Further details, refer to:

1.) □ Universal Viewer Server is installed Universal Viewer Universal Viewer IM and
Server AWS IM, 2.19 Job Card IST011 -
Integration on page 172
2.) □ In Site Configuration Tool / AW Universal Viewer Universal Viewer IM and
Configuration tab is configured Server AWS IM, 2.19 Job Card IST011 -
Integration on page 172
3.) □ In Site Configuration Tool / AW Universal Viewer Universal Viewer IM and
Servers tab is configured with one or Server AWS IM, 2.19 Job Card IST011 -
several servers. Integration on page 172
4.) □ An AW Server user is created in Universal Viewer Universal Viewer IM and
Universal Viewer (e.g "AWDakota") Server AWS IM, 2.19 Job Card IST011 -
Integration on page 172
5.) □ A preprocessing user is created in Universal Viewer Universal Viewer IM and
Universal Viewer (e.g "AWPreproc") Server AWS IM, 2.19 Job Card IST011 -
Integration on page 172
6.) □ Universal Viewer users have the AWS Universal Viewer Universal Viewer IM and
3 group. Server AWS IM, 2.19 Job Card IST011 -
Integration on page 172
7.) □ Virtual Drive is added and 2 MIME Universal Viewer Universal Viewer IM and
Types are created Server

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 189

2.19 Job Card IST011 - Integration

Step Check Action On Further details, refer to:

AWS IM, 2.19 Job Card IST011 -
Integration on page 172

2.19.3.7.3 On Universal Viewer Client PC

Step Check Action On Further details, refer to:

1.) □ Universal Viewer (IW) Client is Universal Viewer Universal Viewer IM and
installed on the RIS/PACS Client PC 2.23 Job Card IST014B - Seamless
workstations where integration will Client PC installation and Tests on
be used by the customer. page 226
2.) □ AWS Client is installed on the Universal Viewer Universal Viewer IM and
Universal Viewer Server. Client PC 2.23 Job Card IST014B - Seamless
Client PC installation and Tests on
page 226
3.) □ In Universal Viewer Client, 3D Universal Viewer Universal Viewer IM and
applications button is configured Client PC 2.23 Job Card IST014B - Seamless
Client PC installation and Tests on
page 226
4.) □ AWS Client is installed on the Universal Viewer Universal Viewer IM and
Universal Viewer Client workstations Client PC 2.23 Job Card IST014B - Seamless
where integration will be used by the Client PC installation and Tests on
customer. page 226

2.19.3.7.4 On the Image sources

Step Check Action On Further details, refer to:

1 □ Modalities are set to auto-push Image Sources Image Source documentation
images to the PACS.

2.19.4 DICOM Direct Connect integration

This section details all the steps needed to configure the DICOM Direct Connect integration, in case
of new installation, re-installation or upgrade.
DICOM Direct Connect is currently supported on Virtual AW Server Low Tier only (40K slices) only.
The clustering mode (Scalability) is also supported.
NOTE
For DICOM Direct Connect in CT Nano-Cloud environment, refer to the current Modality
console Installation and service documentation for integration details on the Modality
console side.
NOTE
Also check the Documentation Portal for the latest version of the docs for that release.

2.19.4.1 Pre-requisites
Database
DICOM Direct Connect integration is using the PACS, VNA or any DICOM Remote Hosts database, so
AW Server does not contain images (apart from images generated on the AW Server that will be
pushed to the PACS/VNA/DICOM Remote Hosts by the End of Review functionality).
Software license key

190 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

A software license key is required to enable integration between the AW Server and the PACS/VNA/
DICOM Remote Hosts. The license key is based on the following keystring: DICOM_Direct_Connect.
DICOM Host definition
The AW Server shall be declared twice in the PACS/VNA/DICOM Remote Hosts system.Refer to
section 2.19.4.4 Configuration steps on the PACS/VNA/DICOM Remote Host on page 194.
2
2.19.4.2 Configuration steps on AWS

Installation of a new AW Server

DNS
DNS must be configured to fit the site's parameters. Refer to 2.13 Job Card IST005 - Network and
Time Configuration on page 88 and/or A.9 Useful Commands and Tools on page 419. This is
necessary to ensure that the AW Server will be able to connect to the different PACS/VNA/DICOM
Remote Host systems.
Auto Delete
Configure the Auto Delete feature so that local images are purged, for example after one day.
Refer to 2.16.7 Database Deletion Settings on page 115: Auto Delete.
DICOM Host
The PACS/VNA/DICOM Remote Host system shall be properly declared as a DICOM Host in AW
Server. Detailed instructions are available in 2.18 Job Card IST010 - Administrative Configuration on
page 148.
Refer to PACS/VNA/DICOM Remote Host documentation for host characteristic.
• Allow Query, Allow Retrieve, Allow Store shall be enabled if the DICOM Host supports the
Query Retrieve function.
• Storage Commitment shall be enabled if the DICOM Host is a PACS supporting this function.
End Of Review
End of Review must be configured with the DICOM hosts declared in the previous step “DICOM host”.
Detailed instructions are available in 2.18.9 End of Review on page 170
• The DICOM Direct Connect Integration shall be fully configured before configuring End of Review.
• The TYPE of images to be sent to the PACS/VNA system when configured shall be set to
“generated”.
• All modality image types shall be enabled, unless the receiving PACS/VNA system does not
support a particular image type, then do not select this type of image.
Preprocessing
Preprocessing is not mandatory, but it improves productivity by preprocessing data before the user
opens an exam. Refer to 2.16.10 Licensing Configuration on page 123.
AW Server requires a software license key to enable the Preprocessing feature.
In cluster mode, Preprocessing shall be licensed and enabled on all AW server nodes and the
preprocessing protocols shall be configured (Service Tools/Administrative/Configuration/
Preprocessing) with the same series descriptors.
NOTE
In DICOM Direct Connect integration mode, the PACS/VNA/DICOM Remote Host system
must be configured to send DICOM Instance Availability Notifications (IAN) to the AW
Server (to the first node in case of a cluster). Refer to 2.18.7 Preprocessing Configuration
on page 165.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 191

2.19 Job Card IST011 - Integration

2.19.4.3 Configuration steps on AWS, Service Tools

By default the Server is in Standalone (Non-Integrated) mode.
Only execute the following procedure if you have to configure the DICOM Direct Connect Integration.

2.19.4.3.1 DICOM Direct Connect Integration setup steps

1. If not already done, put the AW Server in Maintenance mode.Refer to chapter 4,
A.4 Maintenance Mode on page 369 for details.
2. From the Service Tools menu, click on Initial Configuration to expand the menu.
3. Click on Platform Configuration.
The Platform configuration tab displays:

Refer to Platform Configuration for details.

4. Platform Configuration:
• Select the Platform Enabler license AW Server 40,000 slices (SdC_Low_Tier_Premium)

192 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

NOTE
In CT Nano-Cloud environment select one of the SdC_Nano_nk license and
enter the corresponding Platform License Key. Refer to the current Modality
console Installation and service documentation.
• Enter the Platform License key for SdC_Low_Tier_Premium in the text field.
• Click Next button to change to the Scalability tab. 2
5. Scalability: Virtual AW Server to be placed into a cluster of virtual AW servers:

Installation of a new AW Server

• If your AW Server shall be part of a cluster, select the Cluster Mode.
In that case, enter the IP address of the two HAPS (High Availability Preference Server)
nodes.

If applicable for your site, Scalability configuration shall be done as part of 2.20 Job Card IST012
- Virtual Servers Cluster Configuration on page 196
• When done, click on the Next button to change to the Integration tab
6. The Integration sub-menu display:

7. Integration steps:
• Integration Enabler:
Select the DICOM Direct Connect radio button.
• Connector plugin:
DICOM Direct Connect plugin is selected.
• License key:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 193

2.19 Job Card IST011 - Integration

Enter the license key for DICOM Direct Connect Integration

(keystring : DICOM_Direct_Connect)
• Authentication URL:
The “Authentication URL” is only needed if PACS/VNA front-end client integration is used.
Refer to the PACS/VNA/DICOM Remote Host documentation.
8. Optional steps:
• Click on the Keep me logged in check box.
• Select a number of days before connection is closed - typically 1 day.
• Click on Generate button to automatically generate a Passphrase for connection security,
or type in the Passphrase chosen by the user.
9. Now click on Apply to enable the DICOM Direct Connect integration configuration.
The following confirmation messages display when the integration mode is applied:
All the DICOM data stored in the database will be deleted !
It is strongly recommended to transfer the data to a remote system.
Please contact the IT Admin and check which images need to be saved on PACS. Do you
want to continue the configuration now ?

NOTICE
If this is a new installation, no images are present in the AW Server database.In
case of upgrade, make sure with your customer that all image data has previously
been stored on another system before continuing.
• Click OK to acknowledge.
The following popup message displays:
All the DICOM data stored in the database will now be deleted !
Do you want to proceed with the configuration now ?
• Click OK to acknowledge.
Please reboot the system
• Click on OK to acknowledge the message.
10. Reboot the server now
OR
proceed to the other features configuration steps first, then you will shutdown and reboot when
the other configuration steps are done.
To reboot, from the Service Tools menu:
• Click on Tools to expand the menu.
• Then click on Reboot.
• In the left panel, click on the Reboot AW Server button.

2.19.4.4 Configuration steps on the PACS/VNA/DICOM Remote Host

For each AW Server node you have to declare the AW Server host twice in the PACS/VNA/DICOM
Remote Host:
• One entry with the <host name>/<AET>, IP and port 4006 for standard DICOM functions.

194 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.19 Job Card IST011 - Integration

• The second entry with <host name>_ds/<AET>_ds, same IP and port 4010 for DICOM Direct
Connect.

2.19.4.4.1 Configuration steps on Enterprise Archive (EA)

This section describes the steps to declare the AW Server in the Enterprise Archive (EA).
1. Connect to the Enterprise Archive Server Web page URL with: 2
EA Web Service URL: http://<EA_IP_address>/eaconsole

Installation of a new AW Server

NOTICE
Enterprise Archive Server Web page may not be properly working in Chrome and
Firefox web browsers. Preferably use IE.
2. From the Enterprise Archive Server Web main page, login as Administrator. Refer to the EA
administrator for more details on how to require EA access.
3. On the left hand side menu, click on Communication to expand the menu. Then select DICOM
clients.
4. Click on the New button. The right part of the interface allows you to declare the AWS.

5. Fill in the fields as follow (note that the AWS HealthPage displays the needed information):
• Enter the host name in the Name, field.
• Enter the Application Entity Title (AET) in the AE titles field.
• Enter the IP Address in the Host name field.
• Enter the port number in the Port field.
NOTE
Refer to the EA administrator if other fields need to be addressed.

2.19.4.5 Configuration steps on the Client PC

The AW Server Client and the PACS Client must be installed on the PC.
Refer to the PACS documentation and to 2.22 Job Card IST014A - Standard Client PC installation &
Tests on page 204 for the AW Server Client.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 195

2.20 Job Card IST012 - Virtual Servers Cluster Configuration

NOTE
For DICOM Direct Connect in CT Nano-Cloud environment, AWS Client will be integrated
within the CT Console Client. Refer to CT documentation for full description
DICOM Direct Connect Integration configuration is complete.
For additional information to setup the whole cluster, refer to 2.20 Job Card IST012 - Virtual Servers
Cluster Configuration on page 196
OR
Proceed to 2.21 Job Card IST013 - Service Tools Configuration on page 200

2.20 Job Card IST012 - Virtual Servers Cluster

Configuration

2.20.1 Foreword
Scalability mode (or cluster mode) is the ability to have several AW Servers working as one more
powerful AW server (currently limited to a maximum of 30 “virtual” AW Servers). The behavior is
“transparent” for the user, who will be automatically directed to the appropriate server (less loaded)
when logging in.
If your site is going to have a cluster of two or more virtual AW servers, you need to set up each of
the servers in the "Cluster mode". Proceed as follows and repeat this operation on each of the other
virtual AW servers.
Currently, the Scalable mode is only supported with virtual AW Servers.

NOTICE
Pre-requisite to performing this Job Card is the successful completion of: 2.8 Job Card
IST001C - Virtual Servers Cluster Installation Steps on page 56 and 2.19 Job Card
IST011 - Integration on page 172.

2.20.2 Scalability setup procedure

2.20.2.1 NTP server availability checks

1.) Time synchronization through a NTP server is a "must be" for scalability.
• Check on each AW Server that the NTP server is operational.
• Open the Terminal from the Tools menu and login as root.
• Type in the Terminal:
service ntpd status <Enter>
ntpd (pid 4658) is running...
2.) If no NTP server displays, ask the IT admin of the site to provide you with a NTP server IP address, and refer
to section 2.16.6.2 Time Server menu on page 115 to setup the NTP server.

2.20.2.2 Scalability setup

2.20.2.2.1 Scalability mode setup

1. From the Service Tools / Initial Configuration menu:

196 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.20 Job Card IST012 - Virtual Servers Cluster Configuration

• Click on Platform configuration.

The configuration tool opens on Platform configuration tab.
• Make sure the Platform License key has been entered. If not done, refer to 2.16 Job Card
IST008 - Initial Configuration on page 108 to set it up.
• Click on Next to move to Scalability tab.
2. Scalability mode setup
2
• Check that the Cluster Mode radio button is selected, or select it if not done.

Installation of a new AW Server

• Enter the Private Network (eth1) IP address of HAPS Preferences server 1# and Private
Network (eth1) IP address of HAPS Preferences server #2.
DO NOT ENTER THE HOSPITAL NETWORK IP ADDRESSES !!!.

• Click Check IP to check the IP address. The message “Success” (on a green background)
should display briefly next to the button.
3. When done, click on Next to move to Integration tab.
The integration menu displays.
• Check that Integration parameters are properly setup, as part of 2.19 Job Card IST011 -
Integration on page 172, then click on Apply.

2.20.2.2.2 Nodes setup

1.) □ From the Service Tools / Initial Configuration menu:

• Click on Scalability.
• The "Manage and display scalability setting" interface will display
2.) □ After a moment, the Nodes table will be populated with the information of the AW Server, as in the
example below.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 197

2.20 Job Card IST012 - Virtual Servers Cluster Configuration

• Click on VERSION information to display the version of the Applications installed.

The Version information may display in red, as the "Golden set" has not been defined yet.
• Use the Refresh button to display the other servers of the cluster, if they have already been setup
in the cluster mode and are ready for operation.

NOTICE
Applications must be installed and activated prior to setting the Goldenset. Skip next
step if Applications are not yet installed (in which case the Golden Set will be done as
part of Applications Installation job card). Refer to 2.17 Job Card IST009 - External
Application(s) Installation on page 132.

2.20.2.2.3 Golden Set setup

1.) □ NOTICE
To setup the Goldenset, the node MUST NOT be in Maintenance mode.
• Bypass this step upon initial installation of the system, as you are not allowed to exit the
Maintenance mode as long as the Configuration registration key has not been obtained, as a result
of sending the Configuration file to the AWCCT web site.
• Proceed to 2.21 Job Card IST013 - Service Tools Configuration on page 200 completion, exit the
Maintenance mode and return to this step when done.
• Click on the Set as Golden set button, to setup these versions as the reference versions.

The Goldenset only shows Applications that are active.

• When done, click on Hide button to close the window
2.) □ When the Goldenset has been set, the nodes will display OK in the Version column, as shown in the
example below:.

198 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.20 Job Card IST012 - Virtual Servers Cluster Configuration

Installation of a new AW Server

NOTE
When the Golden has not been set up (version status red), be careful to set it
only after all applications have been installed. If the Golden Set has a
mismatch (version status red), analyze the cause of the mismatch, identify the
correct configuration and make the appropriate changes to the non-compliant
server.
3.) □ In our example above, with 2 nodes in the cluster, we can see the following:
• bucaw71-37 is the node we are currently connected on. It is in Maintenance mode (see symbol as in
the list below)
• bucaw71-38 is accessible through a link.
Clicking on the link will launch the Service Tools web page of those AW servers.
• The Goldenset has been set.
• The Version and the installed Applications versions are compatible (the same on each server of the
cluster, so they display OK.
• CPU usage, memory usage, Disk usage are OK and do not report a problem.
NOTE
Moving the arrow over the NODE IP ADDRESS title field to display the colors
and Icon codes table as follows:

4.) The HAPS nodes display the Private network IP address and the status of both HAPS nodes. See
example hereafter.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 199

2.21 Job Card IST013 - Service Tools Configuration

NOTE
When a HAPS node is not available, it just shows the IP address, empty cells
for disk space and preference directory and "N" status for the Available
column.
5.) □ Reboot is necessary for Scalability to be fully operational for the Clients.
You may do it now or proceed with the next configuration steps and wait until the server is fully
configured.
• If you want to reboot now, click Reboot

NOTICE
From AW Server 3.2 release, the Users Preferences in Scalability mode are no longer
stored on the virtual AW servers, but on two additional redundant HAPS nodes.

The Scalability configuration is complete.

Proceed to 2.21 Job Card IST013 - Service Tools Configuration on page 200.

2.21 Job Card IST013 - Service Tools Configuration

• System Configuration Registration - See 2.21.1 System Configuration Registration on page 200

2.21.1 System Configuration Registration

NOTICE
Proceed with the following steps to register your AW Configuration and obtain in
return the Registration key allowing you to exit from the Maintenance mode, when all
the installation and configuration tasks are completed.

2.21.1.1 Configuration registration steps

1.) • Under Service Tools / Maintenance menu, click on the Register Configuration link to launch the
Configuration Registration tool.

NOTICE
Device Data in Initial configuration must be configured. Otherwise the Register Configuration
menu will not open.
The Register Configuration menu opens.

200 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.21 Job Card IST013 - Service Tools Configuration

Installation of a new AW Server

2.) CASE 1: If your AW Server is connected via InSite and that the checkout has been done, you can use the
"Auto Registration" process.
• Click on the Perform Auto Registration button, to automatically send the Site configuration file to the
AWCCT Web site.
If the configuration is compliant, messages will say so in the Connectivity Status and Registration Status
windows and you will automatically receive in return within a few seconds the Registration key, while the
"Request in progress" message will change to "Operation success ! The registration key has been successfully
installed".
3.) • Bypass the next steps. They are dedicated to manual registration when remote connection via InSite is
not available.
You are now able to exit the Maintenance mode when desired.
AW Servers in Cluster mode - You are now able to configure the Golden Set.
Refer to 2.20 Job Card IST012 - Virtual Servers Cluster Configuration on page 196
4.) CASE 2: If your AW Server is NOT connected via InSite, you are NOT able to use the "Auto Registration"
process. Use the "Download configuration (Manual Registration)" process.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 201

2.21 Job Card IST013 - Service Tools Configuration

• Click on the Export configuration button to export the configuration file (in the form
licenseID_systemID_date_Configuration.txt) to your PC or to a media (e.g. USB stick).
Nothing may seem to happen for a short moment. Do not click again on Export configuration.
• Select to save the LicenseID_systemID_date_Configuration.txt file.
The System ID implementation only allows alphanumeric characters:
[A-Z], [a-z] and [0-9]
Make sure you did not enter inadvertently any of the non-allowed characters when typing in the SystemID.
5.) • Launch an Internet Navigator and connect to https://awcct.gehealthcare.com.
• If you cannot properly reach or display the site, right click on the Internet Navigator icon and select "Start
in Private Browsing" that will open a new Navigator window.
NOTE
If you cannot connect from the AW Server, try from a PC with Internet access.

NOTICE
Currently, only the Windows TM Internet Explorer navigator is supported.

6.) The following AW Configuration Collection Tool screen displays.

• Click on the Browse button of the AW Service Tools Register Configuration page, then select your AW
Server’s Configuration file.
• Click on the Submit button
7.) The AW Configuration Collection Tool screen displays the Summary of uploaded Configurations.
If the configuration is compliant, you will get your system Registration key.

• Click on Save registration Key button, and choose the location where to save the key on your AW
Server (if applicable) or on your PC.

202 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.21 Job Card IST013 - Service Tools Configuration

NOTE
For more information about the Configuration Registration tool, refer to the
AWCCT User Guide available on AWCCT web site in Documentation section (Part
number: 5589257-1EN)
8.) • Copy/paste or type in the Registration Key in the Install Registration Key field and click on the Register
button.
The "Request in progress" message displays, followed by "Operation success" message. 2

Installation of a new AW Server

NOTE
In certain situations, the upload of the Registration key on the AW Server may
result in "not configured".
To avoid this, just copy/paste or type in the Registration Key in the Install
Registration Key field and click on the Install Registration Key Button
9.) Final step: Exit from the Maintenance mode
NOTE
If download of the Configuration file does not succeed, it is possible to send it by
email to the [email protected] address. You will receive in return by email the
Registration key.
System Configuration Registration is complete.
You can exit from the Maintenance mode when desired.
NOTE
The Registration status field in the HealthPage should display as "Standard" in
green (It used to display as "Permanent" prior to AW Server 3.2 Ext1.2 release).
AW Servers in Cluster mode - You are now able to configure the Golden Set.
Refer to 2.20 Job Card IST012 - Virtual Servers Cluster Configuration on page 196

2.21.1.2 Process in case of issue at Registration time

2.21.1.2.1 In case of issue to access the AWCCT Website.

Please follow the rules below:
Context:
• The AWCCT web site is down
• No SSO available (No GEHC personal - I.e: Distributor)

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 203

2.22 Job Card IST014A - Standard Client PC installation & Tests

Action: use registration process via email process

• Save AW Server Configuration to hardware or USB key.
• Send it by mail to [email protected]
Registration key and Configuration Registration Report will be returned by mail within 1 hour.

2.21.1.2.2 In case of issue to get the registration key or to install it

In case of issue to get the registration key for your AW Server at installation time or to install it,
please follow the rules below in order to get assistance:
Context:
• AW Server Configuration file not recognized on AWCCT
• Process via email at [email protected] did not return timely.
• Configuration uploaded fine, but returns with non-valid key, or no key returned
• Issue at Registration key installation on AW Server
Action:
• Contact the Service L3 (RTE/OLE/RSE) team with the following:
• AW Server's License ID (minimum)
• AW Server's configuration file (preferably)
• To close the Service case, the Configuration File will have to be uploaded on AWCCT web site as
soon as possible.
NOTE
For any question about the Configuration Registration process, FE can call the
Configuration Registration Call Center number at:
(+1) 855-741-3136 (toll free number from US only)
(+1) 262-524-5660 (if the first phone number does not work)
Call center support will be done in English language only
The Service Tools configuration is complete.
Proceed to 2.22 Job Card IST014A - Standard Client PC installation & Tests on page 204 OR
Proceed to 2.23 Job Card IST014B - Seamless Client PC installation and Tests on page 226

2.22 Job Card IST014A - Standard Client PC

installation & Tests
This Job Card applies to the installation of Clients for Standalone (Non-Integrated) AW Server or for
all integrated AW Server other than the Seamless integration.
For installation of Clients in Seamless integration, please refer to:
2.23 Job Card IST014B - Seamless Client PC installation and Tests on page 226
Foreword
Windows Client:
The GEHC FE is responsible for installing at one Client PC and to discuss with the IT administrator
that all other client PCs must be installed as well. It is normally the responsibility of Customer to
install all the rest of their existing client PCs. Provide the Clients installation procedure to the IT
Admin.

204 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

Windows Client - Mass Installation:

It is under the Hospital responsibility to install all other Client PCs. If the hospital decides to use the
Microsoft MSI mass deployment software, they will do it under their responsibility.
The MSI package is available in the AW Server SW & Docs DVD.
Linux Client:
Installation of the Linux Clients is under the GEHC FE responsibility For Linux Client installation.
2

Installation of a new AW Server

See section 2.22.1.2 Linux Client installation Procedure on page 209
NOTE
The Linux Client support is limited to certain GE consoles. Please see the corresponding
console User guide for further details.

NOTICE
Installation on Linux Client is no more supported from AW Server 3.2 Ext.3.0.

2.22.1 Client Installation Procedure

2.22.1.1 Windows TM Client PC installation Procedure

2.22.1.1.1 System Requirements

The minimum hardware and software requirements for the client are listed on the AW Server main
page, as shown in the following illustration of the AW Server main screen.

NOTICE
DO NOT install client software on more than one client PC per customer! NO
EXCEPTIONS!

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 205

2.22 Job Card IST014A - Standard Client PC installation & Tests

The GEHC customer contract specifies that GEHC will install AW Server software on only ONE client,
for the purposes of testing the AW Server system upon installation. If a GEHC FE installs and/or
configures the software on more than one client per customer, IT CAN CREATE SERIOUS LEGAL AND
REGULATORY PROBLEMS FOR GEHC. Except for the first client (which is set up by the GEHC FE), THE
CUSTOMER MUST INSTALL AND CONFIGURE THEIR OWN CLIENTS.

2.22.1.1.2 Installation requirements

NOTICE
You need administrative permissions on the client PC to download and/or install the
AW Server client software. If you don’t have it, ask the site IT Admin to change the
permissions temporarily, or have the IT Admin install the client software as the Admin
user. Make sure you have current contact information for the site’s IT administrator, in
case you need his/ her help during this procedure.

2.22.1.1.3 Client Installation Errors/Problems

It is not possible to anticipate ALL potential site security, filters, and firewall rules for this product.
Make a note of any errors in the client installation process, because they might be related to PC
and/or network security / firewall configuration.
Client problems are the responsibility of the customer!
NOTE
The AW Server Client program must be downloaded and installed on the client PC to use
the AW Server as a product. If you are unable to do this, ask the site IT Admin to help you
find the reason.

2.22.1.1.4 Downloading the AW Server Client Software installer

1. • On the PC that will be used as the client, launch a web browser (e.g. Internet Explorer 10.x,
11.x, Firefox, Chrome).
NOTE
Different AW Server Client releases can reside on a Client PC (e.g. your site has an AW
Server 2.0 that is in use and must be kept operating, and has purchased a new AW
Server 3.2). To uninstall an older AWS Client, you can select the option “Yes, remove
older versions”. If the shortcut remains on the desktop, delete it manually.

NOTE
In certain cases, you may also need to remove an older Client, prior to installing the
new one. In those cases, first remove the older client on your Windows TM PC using:
Control Panel > Programs > Programs and Feature > Uninstall or change a
program to uninstall the older Client.
2. • Enter the AW Server’s IP address (for example, http://3.70.211.201) into the browser’s
address bar, then press <Enter>.
• The AW Server main page displays a page similar to the example shown below:

206 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

Installation of a new AW Server

3. • Click the Download button next to “Client for Windows” to download the installer file for
the AW Server client.
4. • When the client installer file has downloaded completely, save it to the desktop.

2.22.1.1.5 Installing the AW Server Client

1. • When the installer file has downloaded completely and is saved on your desktop, double-
click the corresponding icon to run it.
2. • If a security warning such as “publisher of the setup software could not be verified”
displays, click on Run. (The exact wording of the warning will depend on which browser you
are using).
3. • The Windows setup wizard interface will display. Click Next.
4. • The Select Installation Folder interface will display. Keep the default path (e.g. C:\Program
Files\GE\AWS_3.2) or use the Browse button to select a custom path.
• Click Next when done.

NOTICE
When "remove older version" message is display, and when accepting removal,
pay attention that it will remove all major versions as well (AWS2.0, AWS3.1).
When updating AWS3.2 on existing AWS3.2 version, a manual uninstall may be
necessary first.
5. • The Ready to install interface will display. Click Install
6. • The Completing the Setup Wizard interface will display. Click Finish.
7. • Verify that the new AW Server client program is listed in the Windows Start Menu.
The AW Server Client software is now installed on this client PC
NOTE
If the site is running a Chinese, Japanese or Korean UI in a Windows 64 environment,
you must change the Language and Regional settings on the Client PC.
• Open the Control Panel
• Select Regional and Language options
• Click the boxes next to "Install files for complex script and right-to-left
languages" and "Install files for East Asian languages".
• Open the Control Panel
• Select Regional and Language options
• Click the boxes next to "Install files for complex script and right-to-left languages" and
"Install files for East Asian languages".

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 207

2.22 Job Card IST014A - Standard Client PC installation & Tests

8. AWS Client configuration for CPACS integration

• In case of hybrid integration between AWS and CPACS, it is necessary to modify the AWS
Client files. This is needed because CPACS might be blocking specific processes like
solo.exe. Refer to section 2.22.3.6 AWS Client configuration for CPACS integration on page
225 for detailed procedure.
9. AWS Client configuration for upgrade from AW Server 2.0
• To enable the Close button on the User Interface (instead of the usual Logout button that
can be seen in the Standalone (No-integration) mode), you need to modify the solo.ini
file.Refer to section 2.22.3.7 AWS Client configuration for upgrade from AW Server 2.0 on
page 226 for detailed procedure.
10. Silent install
When launching the AW Server Client for the first time, the user has to manually enter the IP
address(es) of the AW Sever(s) he/she wants to reach. And that for every AW Server Client. To
avoid this waste of time, the AW Server Client can be installed in “Silent” mode from a
Command Prompt using the Windows installer as follow:
• When the installer file has downloaded completely and is saved on your desktop.
• Open a Command Prompt as administrator.

• In the Command Prompt enter the following command:

msiexec /i C:\Users\<user>\Desktop\AWS-3.2-SoloInstaller.msi /l*vx %TEMP%
\install.log IPLIST="3.249.70.237,3.249.70.238" /qn <Enter>
<user>: Is your Windows username
IPLIST: Contains the list of the IP addresses of the AW Severs you should be able to reach.
Here as an example there are 2 IP addresses corresponding to 2 AW Servers.
NOTE
The IP address can be replaced by the hostname if the hospital uses a Domain
Name system.
install.log: After the installation process, the install.log file will be created in the specified
folder (here \tmp), which contains information about valid or invalid IPLIST items.
NOTE
The command returns immediately but works in the background for several
seconds.
• Finish the installation with step 7) above.

208 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

NOTE
The AW Server Client installation in "Silent" mode is not available for Seamless
integration

2.22.1.2 Linux Client installation Procedure

2
2.22.1.2.1 System requirements

Installation of a new AW Server

The Linux Client support is limited to certain GE consoles. Please see the corresponding console
User guide for further details.

2.22.1.2.2 Installation requirements

• The Linux Client must be installed as root.
• Prior to upgrade a Linux Client, you must uninstall the previous version of the AW Server Client
Software if applicable.
NOTE
The following example has been written using the Linux system of an AW4.7 workstation.
However, the Linux Client installation is no more supported on the AW4.7 workstation.
The Linux Client installation is similar for other Linux hosts, validated as AW Server
Clients.
Remove any older AWE package at your LINUX console (I.e: AW4.7 workstation)
1. Open a terminal and login as root or switch user to root (su - root).
2. Search for the AWE package name:
rpm -qa | grep AWE <Enter>
The package should be of the form AWE-solo_2.0_4.XX.
3. Remove the AWE-solo package:
rpm -e AWE-solo <Enter>
4. Also remove the installation package (if applicable).
If the older installation package was downloaded to the /tmp directory, it has most probably be
erased since.
If it was downloaded to the Downloads directory, you have to remove it from the Downloads
directory.
5. Check if an older package exists:
ls /export/home/sdc/Downloads/AWE-solo-install.rpm <Enter>
6. If the older package exists, remove it:
rm /export/home/sdc/Downloads/AWE-solo-install.rpm <Enter>
Download the Linux Client Software installer
On the AW Server, the Linux Installer package is available under the /var/lib/tomcat6/webapps
/awe/client directory.
7. Open a Terminal and login as root.
8. Check the Linux package name:
ls -al /var/lib/tomcat6/webapps/awe/client <Enter>

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 209

2.22 Job Card IST014A - Standard Client PC installation & Tests

-rw-r--r-- 1 tomcat tomcat 137847461 Sep 25 05:18 AWE-3.2-solo.i386.rpm

-rw-r--r-- 1 tomcat tomcat 133029700 Sep 25 05:18 AWE-3.2-
solomini.i386.rpm
-rw-r--r-- 1 tomcat tomcat 142495744 Sep 25 05:18 AWS-3.2-
SoloInstaller.msi
-rw-r--r-- 1 tomcat tomcat 117202944 Sep 25 05:18 AWS-3.2-
SolominiInstaller.msi
-rw-r--r-- 1 tomcat tomcat 88 Sep 25 05:18 release.txt
9. Upload the AWE-3.2-solo.i386.rpm package to the Linux console.
10. On the Linux Client console, save the file to the /export/home/sdc/Downloads directory.
11. NOTE
If you get a message in Mozilla that the Proxy server is refusing connections, proceed
as follows:
Click on Edit > Preferences > Advanced > Settings.
12. Add the AW Server IP address in the No Proxy For field. If other addresses are already present
in this field, separate this new IP address from the previous by a comma (,).
Install the Linux Client
The following example is for installing the Linux Client on an AW workstation. It may slightly differ
when installing the Linux client on another GEHC product.
13. When the client installer file has downloaded completely, open a Command Window (Terminal
tool) and type:
su - <Enter>
14. Enter the root password.
15. Type:
cd /export/home/sdc/Downloads <Enter>
rpm -ihv <package_name>.rpm <Enter>
(I.e: rpm -ihv AWE-solo-install.rpm <Enter>)
16. When the package is installed, reboot the AW workstation.
17. On the AW UI, in Programs > More, you should see two new links:
• AW Server 3 Client
• AW Server 3 Screen Sharing
18. Click on the AW Server 3 Client link.
The AW Server starts in the Navigator window of the AW workstation.
Silent install
As for the Windows Client, the AW Server Client can be installed on Linux in Silent mode. And so,
when login in the AW Server Client, the user does not have to manually enter the IP address(es) of
the AW Sever(s) he/she wants to connect to.
19. When the client installer file has downloaded completely, open a Command Window (Terminal
tool) and type:
su - <Enter>
20. Enter the root password.
21. Type:
cd /usr/share/solo3/scripts <Enter>

210 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

./install.solo -iplist=3.249.70.237,3.249.70.238 <Enter>

-iplist: Contains the list of the IP addresses of the AW Severs you should be able to connect
to. Here, as an example there are 2 IP addresses corresponding to 2 AW Servers.
NOTE
The IP address can be replaced by the hostname if the hospital uses a Domain Name
system. 2
The result is stored in the install.log file located in the installation directory /usr/share/s

Installation of a new AW Server

olo3, the log file contains information about valid or invalid -iplist items.
22. Finish the installation following Step 16 to Step 18 above.

2.22.2 Server and Client Installation Validation Tests

You will now perform some basic tests to validate the AW Server system installation.
NOTE
This is a test of functionality, not relative performance. Noticeable “hangs” or delays
(beyond a reasonable time) might indicate a test failure.
Two test procedures are required to validate the installation of the AW Server:
• Server standalone test
• Client connectivity test
The server standalone test is a diagnostic test of the server only, without the network and client.
It uses two tools from the AW Server Service Tools:
• The system HealthPage
• The server diagnostic test
The client connectivity test is a system test. It attempts to run an AW Server application from a
client PC via the site’s network. This tests the AW Server as a system.
If both tests pass, the AW Server system is ready for customer demonstration and site
handover.
You will now perform the server standalone test.
This test uses the Service Tools HealthPage and the Server Diagnostic Test to determine whether
the server is working properly, independent of the rest of the system.
If both parts of the Server StandAlone Test pass, the server is working as expected.

2.22.2.1 HealthPage Test

This is the first part of the Server StandAlone Test. The HealthPage evaluates the system hardware
and platform software sub-systems.

2.22.2.1.1 Required Tools

This test requires to connect from the PC on which AW Server client software is installed.

2.22.2.1.2 Procedure
1. Make sure the Client PC is properly connected to / accessible from the site’s local network for
the AW Server.
2. Open a web browser (e.g., Internet Explorer or AW Server OS supported Firefox).
3. Enter the AW Server’s IP Address in the address bar, then press <Enter>.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 211

2.22 Job Card IST014A - Standard Client PC installation & Tests

Example of address bar IP address: http://3.70.211.201.

The AW Server’s main page displays.
4. In the Configuration area of this page, click on the Launch button next to Service and
Administrative Tools.

The Service Tools login page displays.

5. Login as service.
The Service Tools HealthPage displays as shown in the following illustration examples.

212 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

Installation of a new AW Server

Each right-hand column on this page shows color-coded status information indicated by a
GREEN, YELLOW or RED background.

• Green means that the status or value of that item is OK.

• Yellow means not critical (i.e: Mount count for fsck is highlighted in Yellow if the values are
close to max values)
• Red indicates a problem. Any item with a red background indicates a failure which must be
investigated and fixed.
• A white background indicates that “status” is not applicable for that item.
• Not applicable for the image partition fields means that the system is integrated to the
PACS and does not manage the image database.
6. Check the Hardware Subsystem area:
a. Click on the Sensor Details button (GEHC delivered hardware) to display all available
hardware sensor data. Verify that there are no problems.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 213

2.22 Job Card IST014A - Standard Client PC installation & Tests

b. Or click on the Status Details button (virtual AW Server) to display the virtual hardware
resources. Verify that there are no problems.
GEHC delivered hardware:
• A RED indicator in the Hardware Subsystem table or on the Sensor Details page
indicates a failure in the server hardware. (Click on the Sensor Details button to view
the details page.)
• Not all hardware failures will cause the server to be down completely. A few examples
are: Fans that are in the process of failing, disk drives that have failed-over in the RAID,
and correctable memory errors. It is IMPORTANT to catch the failures that the system
can temporarily withstand, before they cause the server to go down!
• Any hardware failure is a standalone test failure, and requires investigation and
resolution by the hardware vendor. Contact the GEHC Online Center to dispatch the
hardware vendor.
• If the system is not functioning, or is having some other issues that have caused a
request for service, and the Health Page is accessible, any hardware sensor failure
should be treated as the immediate cause of the system failure(s), and dispatched to
the vendor for resolution before any further troubleshooting is done.
Virtual Machine:
• A RED indicator in the Hardware Subsystem for Virtual Machine status may mean
incorrect hardware resources: Contact IT admin of the hospital to update the virtual
resources provided to the Virtual Machine.
7. Check the System Configuration area:
a. Check the basic server parameters. The previous illustration shows normal values for the
AW Server as of this writing.
b. Hover your mouse cursor over each green or red item in System Configuration to see
additional information.
8. Check the Software Subsystem area.
This area shows the status of various software subsystems. Investigate details of any error
conditions by analyzing the corresponding error logs in the Diagnostic – Log Viewer tool
selection.
NOTE
The names in parentheses after each software subsystem service name also appear
after the log names in the log viewer. Use this name to select the log(s) that contain
information about that particular software subsystem service. For example, for the
“Firewall” service, the log name is “pnf”.
NOTE
The Software Subsystem area also has a Restart button. This button is NOT part of
this procedure.
9. Check the Software Subsystems essential for Service Tools area.
• This area shows the status of services which must be running in order for Service Tools to
work.
• A RED indicator in the Software Subsystems Status table indicates a failure in the server
software subsystem.
NOTE
Some of these failures (e.g., filmer subsystem, firewall, Secure Direct Connect,
printing service) will probably not make the server fail. But, they are still failures,
and must be resolved due to their potential impact on the user.

214 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

“Potential” resolution process flow for Software Subsystem failures:

• Investigate the corresponding software error log(s) in the Diagnostic – Log Viewer the
service tools to attempt to understand the nature of the failure, and design appropriate
action.
• The parenthetical (name) after the software subsystem component is also in parenthesis
after the log file name in the Log Viewer. 2
• Examples: Software Subsystem – Super Server (aweservice)

Installation of a new AW Server

Example: Log File – Platform: AWE install log (aweservice)
• Restart the software subsystem by clicking on Restart

NOTICE
Remember though, that restarting the software subsystem is just like
rebooting the server – it will disconnect all users!
• Restarting the software can also be done from command line:
/usr/share/ServiceTools/scripts/healthpage/restart_st.sh
/usr/share/ServiceTools/scripts/healthpage/restart_all.sh
(the Restart button is mapped to this script)
• Reboot of the server – disconnects all users.
• Re-installation of the application software package(s).
• Load From Cold (OS software and system rebuild)
If ALL items in the STATUS columns for Hardware Subsystem (and Sensor Details page), Software
Subsystem, and Software Subsystem essential for Service Tools are GREEN, the first stage of the
standalone test has passed.

2.22.2.2 Server Diagnostic Test

The second stage of the server standalone test is a diagnostic designed to test the server’s
advanced applications services and data.
NOTE
This test must be executed from a network PC. It will not display correctly - or at all -
using the local keyboard and display via the Linux desktop (“X”) environment.

1.) □ • In the Service Tools menu, click on Diagnostic to expand that menu. Then click the arrow next to
Test to expand the menu.
2.) □ • Click on Server.
The Platform server test interface should display as shown.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 215

2.22 Job Card IST014A - Standard Client PC installation & Tests

3.) □ After a brief pause, the results for each test in the “Result” column should list the status of each test as
“Passed” (all results should be GREEN).
NOTE
If there is a failure, use the same resolution process as with the HealthPage
Software subsystem status described previously: Log Files analysis -->
possible restart --> software reload, etc.
4.) □ • If the health-page software subsystem status indications are all GREEN, and the platform server
tests both pass – then the AW Server StandAlone Diagnostic has passed, and the server is now
ready for system/client testing.
This concludes the AW Server standalone test. The procedure in the next section will test the entire
AW Server system – the server, the client, and the network.

2.22.3 Client (System) Test

The final validation test of the server installation tests the AW Server as a system by connecting to a
client PC via the site’s network. This includes a basic test of the client itself

1.) • On the client PC, start AW Server by double-clicking on the AW Server icon on the desktop.
The AW Server Splash Screen should display briefly, followed by the AW Server Login screen after a few
moments.

NOTICE
If a banner like in our example pops up displaying the message "Not For Clinical Use", it
means that the release installed is not a supported release.FE should warn the customer
that upgrade shall be done immediately, as the installed release is not validated/supported.

2.) • Click on the Show settings link to show/hide additional connection information.

216 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

3.) • Optional: If necessary, see the AW Server Service Manual for information about the Extra Security Layer,
click on the “Secure Mode” check box. Basically, you shouldn’t need this when connecting from the site’s
internal network.
4.) Now you can launch the Measure Network Connection tool.
• Keep the Connection type: Automatic
• Set the measurement time to any suitable value, or keep the default 10 seconds time.
• Click on the Measure button 2
5.) When the Network Connection measurement has completed, you will get the following result window.

Installation of a new AW Server

The suggested Connection type will also be displayed.
• You can click on Apply results to the connection type check-box, then click on the Close button to
apply the suggested connection type to your Client PC.
6.) Now you can login to the AWS Client.
• Enter a valid local server account name and password (e.g., service), or a valid enterprise account name
and password. If the enterprise account server configuration is complete, see the Enterprise Accounts
Configuration section of this document.
NOTE
If you have selected the secure mode, and that the account is valid and the server
is reachable, the AWS client will login to the AW Server. An "Invalid Certificate"
window will pop-up at first login (as shown in the following illustration) if the site
has not purchased an authentication certificate controlled by a third party. This
"Invalid Certificate" window means that the AW Server is using a self-signed
certificate. If the customer does not want to use self-signed certificate, he/she will
have to purchase a certificate validated by a CA on its own.
7.) The Certificate window pops up.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 217

2.22 Job Card IST014A - Standard Client PC installation & Tests

• Click YES to accept.

2.22.3.1 Client Checker Tool

Client Checker is not launched automatically anymore. It has to be started manually. It is not found
in the AWS Client. User has to connect to the AWS home page with an Internet browser, then click
on the "Launch" button next to Client Checker Tool. PC characteristics will be displayed in different
ways on different operating systems
It is important to perform Client Checker before using the AWS Client, in order to make sure the
display has the appropriate quality.The Client Test tool evaluates the client hardware, and network
status, and provides basic information about the PC.
• Java 1.7 minimum release is required to use Client Checker tool.
• Setup in Control Panel / Java / security must be set to "medium security level".
• For latest releases, it is necessary to add the IP address of the server to the exception site's list
in Control Panel to get the tool working. (I.e: https://<AW Server IP_address>)
Monitor (display) quality check

NOTICE
If the system fails either the initial system compatibility or monitor quality test, the
system should not be used to support a medical diagnosis. It may require different
settings or hardware upgrade.
This check evaluates the monitor and graphics card based on the user’s answers to visual tests.
When possible, suggestions are made on how to adjust the monitor. It evaluates the monitor’s
ability to display:
• subtle variations in contrast
• objects without distortion or artifacts
It does not run diagnostic tests on the hardware or replace normal PC quality assurance checks.
Follow the directions displaying on the screen, to run the test.

1.) • In the AW Server main menu, click to launch the Client Checker tool.

218 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

Installation of a new AW Server

2.) • Follow the directions displaying on the screen to run the test.
• When the monitor quality check is done, you can record the results by clicking the Email Summary
button:

When clicking on Email Summary button, and not email account configured, you will get the following error
message:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 219

2.22 Job Card IST014A - Standard Client PC installation & Tests

"This file does not have a program associated with it to perform this action. Please install a program or, if one
is already installed, create an association in the Defaults program control panel"
• Click OK to acknowledge.
• The same message will display in the screen below, when clicking on Email Configuration button, if no
email account configured.
• Click OK to acknowledge.
NOTE
In these cases, use the Save function to create a file that can be copied on a USB
key and sent later on through an operational email box.
3.) • To gather the PC’s hardware configuration details, click the Client Information button.
The results display in the tool’s right-hand panel, as in our example:

• To record a summary of these results, click Email configuration.

• Otherwise, to save the detailed results, click Save. By default, a file called ClientConfiguration.txt is saved
to the PC’s \My Documents folder.
• You can copy and paste the content from the Client Configuration Window, either to an email or to a
text editor by using Ctrl+C, Ctrl+V.
• To close the Client Checker, click Close.
NOTE
For further information about the Client Checker Tool, see the AW Server 3.2
Service Manual.
After running the Client Checker, run the Network test. (Service Tools / Diagnostic / Test / Network). See the
following section.

Monitor (display) tests log file

User access information and test results for this check are stored on the server in the /export/
backup/clientcheckerlog. It can be viewed with Service Tools Log Viewer.
When the monitor quality check is done, run the Network test. (Service Tools / Diagnostic / Test/
Network).

220 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

2.22.3.2 Network Test (summary and client information)

This test displays client bandwidth information for up to ten recent tests.
The client-checker tool does not do a port analysis of the PC. There are no special ports that need to
be opened or managed for AW Server.
If the PC can access network resources, and download the AW Server Application, it is network 2
functional for AW Server purposes.

Installation of a new AW Server

NOTICE
This tool evaluates the client configuration and monitor to determine if they meet the
basic requirements for the AW Server client application. This check is only an initial
evaluation of the operating system and hardware specifications. It is NOT meant to
replace normal QA procedures.
Client Worklist Browser Test
This procedure is a basic “launch-and-go test” to validate basic server operation.

1.) After the client checker tool is complete and closed, launch the AW Server Client Worklist Browser. It should
display as shown in the following illustration example..

2.) The browser displays exam datasets, advanced applications launch buttons (when applicable), and remote
DICOM host queries, among many other functions.
• Select an exam from the list of exams in the browser.
You must have an exam source (a PACS, etc.) configured before any exams will be listed. For detailed
information on this tool, see the User Guide Document from the AW Server UI.
3.) • Select a series image-set in the Series List. The Image preview window (at lower right should display an
image from the selected series, similar to the example shown:.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 221

2.22 Job Card IST014A - Standard Client PC installation & Tests

4.) • From the "Open with" menu, click 2D Viewer. The 2D Viewer application should launch with images in
the right two-thirds of the frame, and tools in the left third as shown:

5.) • Experiment briefly with some of the tools and controls and verify that they respond as expected. (See the
User Manual for details.)
6.) • Click on the tab (at the upper left) “X” to close the 2D Viewer. The display should go back to the exam list
and series image display.
7.) • Click the 3D Viewer button near the bottom right of the screen. The Volume Viewer launch splash screen
should display, then the protocol selection and tool frame should come up as shown in the following
illustration.

222 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

Installation of a new AW Server

8.) • Click on one of the protocols (for example, “Reformat”. Verify that the screen displays and changes as
selected.
9.) • Close the 3D Viewer tab.
10.) • Click the Worklist Browser tab in the upper left corner of the browser. The original browser patient list
should display again.
11.) • Exit the browser, either by clicking the Logout button at upper right, or by clicking on the upper right
corner “X”.
This completes the basic operational validation test. If all steps passed successfully, the AW Server system is
operating correctly.

NOTICE
If any of the preceding steps produced error messages or made the display hang or display
artifacts, this system validation test has failed, and the AW Server is NOT ready for customer
use. Read the “Validation Test Failure – What to do” and “Troubleshooting Tips” in the
following paragraphs.

2.22.3.3 Validation Test Failure – What to do

In the event of system validation test failure:
• Examine error(s) and corresponding error logs using the Log Viewer in Service Tools.
• Re-run the StandAlone diagnostic process.
• If it passes, there could be network-related or client-related issues.
• If it fails, pursue the suggestions in the standalone diagnostic section of the AW Server
Service Manual.
Other suggestions in the event of system validation failure:
• Remove and then re-install the advanced application(s) package(s) using the Version
Management tool in Service Tools. (Reference the Service Tools section of the AW Server Service
Manual.)
• Reload both the OS and platform software (Load From Cold).
Validation Test Troubleshooting Tips
If you cannot perform the “Installation Validation Tests” successfully, troubleshoot the component
that is failing. See examples below:
• If you cannot connect to the server web page, troubleshoot connectivity-related issues:
• Can the PC access other resources on the local network (LAN)?

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 223

2.22 Job Card IST014A - Standard Client PC installation & Tests

• Can the PC access the Internet?

• Is the PC configured correctly on the network with a valid IP address, netmask/network
prefix, and gateway?
• Is there an Internet proxy configured in the browser?
• Does this PC require a proxy to be configured?
• Remember, a proxy allows an internal network PC a gateway to an external network (like the
Internet). If the browser attempts to use this proxy to access an internal network resource – like
the AW Server – it will not be able to find it. Conversely, if the PC needs a proxy to get from the
network it is on, to a remote network (like the Internet), and there is no proxy configured, the PC
will not be able to connect.
• Proxy configurations should be discussed with the site IT admin. For test purposes, they can be
turned off or on to see what the effects are. BUT, doing so could result in other network
resources becoming non-functional until the proxy settings are returned to normal.
• Use “ping” and “traceroute” to test and verify the network functionality. The Service Tools -->
Diagnostic --> Test --> Network tool does some of this for you, as well as a network client
checker test log results table from the server side.
• Try to narrow the connectivity issue down to either a CLIENT issue or a NETWORK issue. A good
way to do this is to test multiple clients on the same subnet. If they all act the same on the
same subnet, chances are there is a network issue. If only one has the problem, focus on it.
• IT IS ALSO VERY HELPFUL TO PERFORM A SIDE-BY-SIDE TEST USING A DUAL-CORE PC, SUCH AS
A GEHC SERVICE/SALES LAPTOP. This is especially useful for “performance” issues, to determine
whether or not the client PC is the problem, and to validate the server.
• Remember, the NETWORK and the CLIENT (other than installing AW Server client software on
ONE customer client as specified in the contract) are NOT the responsibility of GEHC. Once the
server is proved to be working correctly, and that the problem resides with the network or the
client, the AW Server service model is validated, and the final resolutions for issues related to
the network or client belong to the customer.
This completes the AW Server Installation process.
Once the system passes these validation tests, it is ready to be turned over to the customer for
applications training and/or normal use. This is described in the next Job Card.

NOTICE
Please remember to log only actual installation time against the server’s installation
dispatch. Use TRAINING (or another appropriate account) to log ‘observation’ or ‘non-
installation’ site AW Server activities. Also make sure to include in the installation
dispatch the “completion” comments: "HW verification complete prior to software
install”

2.22.3.4 Printing tests

2.22.3.4.1 DICOM printer(s) tests

If you have installed one or several DICOM printers, make sure they are correctly setup by printing
some demo images under AW application.

2.22.3.4.2 Printing with a site’s Postscript printer

On a Client’s Windows PC, if requested by the customer, it is possible to use the declared Postscript
printer(s) together with the AW Server application, by pressing simultaneously on the <Ctrl> <P>
keys.

224 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.22 Job Card IST014A - Standard Client PC installation & Tests

However, this may not be directly achievable, depending on the version of the Postscript printer’s
drivers.
If Postscript printing does not work, here are the recommendations to forward to the IT
administrator:
• Retrieve the latest drivers for the printer from the Internet
• Manually declare the printer on the PC from Start/Settings/Control panel/Printers & Faxes, using 2
the downloaded drivers.

Installation of a new AW Server

2.22.3.5 Client Monitor screen resolution setup
By default, the Client software is setup for standard 1600x1200 pixels screen resolution monitor.
Your customer may be using larger monitors for their Client PCs (2MP or 3MP monitors).

NOTICE
The 1600x1200 limitation is for performance reasons. Performance will heavily drop if
these values are changed for 2MP or 3MP displays.
Pre-requisite
• The Network must be performing well (min 100Mbps)
• This setup must be done for each Client PC using a "non-standard" screen resolution.
•
Procedure for Windows Client PC running Windows
Use the Windows Explorer to edit the "solo.ini" file.. Go to C:\Program Files\GE\AWS_XX-x\solo\
(where AWS_XX-x is the AWS release)
• Make a backup copy of the "solo.ini" file: cp solo.ini solo.ini.save <Enter>
• Edit the solo.inifile, add the following lines, then save and quit the editor:

Resolution Add these lines in "solo.ini" file

2MP monitors DmaxNXWidth=1920
(1920x1200)- DmaxNXHeight=1200
3MP monitors DmaxNXWidth=2048
(2048x1536) DmaxNXHeight=1536

2.22.3.6 AWS Client configuration for CPACS integration

In case of hybrid integration between AWS and CPACS, it is necessary to modify the AWS Client files.
This is needed because CPACS might be blocking specific processes like solo.exe.
On the Client PC where AWS Client is installed, go to the solo folder:
(e.g. C:\Program Files\GE\AWS_3.2\solo) and do the following:
1. Rename "solo.exe" file as "solo32.exe". Ensure that there is no more solo.exe file.
2. In solo.vbs file, edit with Notepad the line:
cmd = chr(34) & "solo.exe" & chr(34)
and replace it by:
cmd = chr(34) & "solo32.exe" & chr(34)
3. Save the file solo.vbs before closing Notepad.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 225

2.23 Job Card IST014B - Seamless Client PC installation and Tests

2.22.3.7 AWS Client configuration for upgrade from AW Server 2.0

1. To enable the Close button on the User Interface (instead of the usual Logout button that can
be seen in the Standalone (No-integration) mode), edit the solo.ini file with Notepad and add
the following line:
-Dtaskbar.closebutton=true
2. Save the file solo.ini before closing Notepad.
3. Warn the IT Admin that this shall be done for each Client PC
The Client configuration is complete.
Proceed to 2.24 Job Card IST015 - Final Settings on page 240

2.23 Job Card IST014B - Seamless Client PC

installation and Tests
This Job Card applies to the installation of Clients for the Seamless integration.
For installation of Clients for Standalone (Non-Integrated) AW Server or for all other
integrated AW Server, please refer to 2.22 Job Card IST014A - Standard Client PC installation &
Tests on page 204.

2.23.1 Client Installation Procedure

2.23.1.1 Pre-requisites - Universal Viewer Client installation

Prior to be able to install the AWS Client, the Universal Viewer must be installed.
Refer to the PACS documentation for detailed installation steps.
Refer to the Universal Viewer Installation Manual.
Installation of the U.V. PACS client consist of:
• Launching an Internet navigator as Administrator. The detailed list of Internet Explorer
compatible with UV client is provided in UV manuals. For information, the IE currently
compatible for UV 6.0 SP3 are: IE8 32 & 64bit, IE9 32 & 64bit, IE10 32 & 64bit, IE11 32 & 64bit,
and IE12 32 & 64bit (compatibility mode only).
• Making sure Active X settings are correctly configured in Internet Explorer.
• Connecting to the U.V. PACS server Web page URL (I.e: http://3.70.211.201) and accepting the
security message by clicking on "Continue to this website (not recommended)".
• At the Centricity PACS Universal Viewer login page, log in.
• Clicking OK at Update in progress message. The message window "Update: downloads
\X;X.X.XXXX\MivSetup" displays and when done, the Universal Viewer patient list displays
• Opening an exam and check that images are displayed.

2.23.1.2 AW Server Client Installation Procedure

2.23.1.2.1 System requirements

Minimum hardware and software requirements for the client are listed on the AW Server login page.

226 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.23 Job Card IST014B - Seamless Client PC installation and Tests

2.23.1.2.2 Installation rules

NOTICE
DO NOT install client software on more than one client pc per customer! NO
EXCEPTIONS!
2
The GEHC customer contract specifies that GEHC will install AW Server software on only ONE client,

Installation of a new AW Server

for the purposes of testing the AW Server system upon installation. If a GEHC FE installs and/or
configures the software on more than one client per customer, IT CAN CREATE SERIOUS LEGAL AND
REGULATORY PROBLEMS FOR GEHC. Except for the first client (which is set up by the GEHC FE), THE
CUSTOMER MUST INSTALL AND CONFIGURE THEIR OWN CLIENTS.

2.23.1.2.3 Installation requirements

You need to have access to the Universal Viewer server

2.23.1.2.4 Client Installation Errors/Problems

It is not possible to anticipate ALL potential site security, filters, and firewall rules for this product.
Make a note of any errors in the client installation process, because they might be related to PC
and/or network security / firewall configuration.
Client problems are the responsibility of the customer!

2.23.1.2.5 Standard Installation procedure

The installation of AWS Client shall be done in two steps :
First step - Universal Viewer Server (PACS):
We will use a script to move all files to the necessary locations to ensure automatic SoloMini client
installation.
This will need to be done on the Universal Viewer Server only once. Only repeat this step when the
AW Server has to be upgraded, as the AWS client has to be upgraded too.

1.) • Login to the Universal Viewer Workflow Manager.

(Refer to the Universal Viewer Installation Manual).
2.) • Verify that the file C:\Integrad\Current\bin\FetchNewAWSClient.vbs exists.
• If not, locate and execute the file called ServerSolominiSetup.exe in the Universal Viewer components
folder for the release.
3.) • Open a Windows command prompt.
4.) • Go to the folder C:\Integrad\Current\bin by entering:
cd C:\Integrad\Current\bin <Enter>
5.) • Execute the script FetchNewAWSClient, with the IP address of an AW Server as a parameter. As a
precaution, refer to an AW Server that is integrated with the Universal Viewer Server you are connected
to. This is needed to ensure you install the correct release of AWS Client.For example:
FetchNewAWSClient /i :3.10.10.15 <Enter>
NOTE
If the UV is not running version 6.0 SP2 (or up), the FetchNewAWSClient script will
report an error (AWS3.0 client). This is normal as UV version below 6.0 SP2 are not
currently supported with AW Server 3.2 and higher.
6.) A confirmation message displays, indicating the AWS client version as in the example snapshot below.:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 227

2.23 Job Card IST014B - Seamless Client PC installation and Tests

• Check that the version of the client is the one you plan to install.
• Select OK if appropriate OR
• Select Cancel otherwise and redo all steps with the IP address of the appropriate server.
7.) Optional :
• If a previous version of AWS Client is installed, the following message displays:

• Select Yes.
• A confirmation message displays. Select OK.
NOTE
If the following message displays, check that the AW Server is on-line by accessing
its home page in an Internet browser. Power on the AW Server if it is currently
down.

Second step - Universal Viewer Client:

We will login to the Universal Viewer Client PC. Then the AWS will be automatically downloaded and
installed if needed. To be done on one Client by the FE. (It will have to be done once for each Client
PC. This will be the responsibility of the customer)

1.) • Close any open Universal Viewer Client session.

2.) • Open an Internet browser and connect to the IP address of the Universal Viewer
I.e: http://3.70.211.201
3.) • Login to the Universal Viewer Client (example account: image / IMAGE)
4.) Configure the 3D Applications button if needed.

228 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.23 Job Card IST014B - Seamless Client PC installation and Tests

The following has to be done for each type of exam (CT, MR, etc...) that will be associated with the AW Server
3D viewer.
• From the Worklist, open a CT exam
• Click on Layout >> Create / Edit in the upper panel
• Click on Menu >> select Modality >> Click Edit button
• Scroll up to "3D Applications" in the list and click on the "<<" sign to add in "Menu Content" window
• Click on Save button 2
• Repeat the steps for other supported modalities (MR, PET and potentially XA).This will add a "3D Apps"

Installation of a new AW Server

button in the upper panel of the U.V. PACS Client for each exam type previously customized.
NOTE
If the "3D Apps" button in the upper panel of the U.V. PACS is greyed, it means that
there were problems at installation or that the Integration configuration
parameters are not appropriate.
5.) • Close the configuration menu
6.) • Select a protocol from the 3D applications drop-down list.
The download of AWS client installer automatically begins and a progress bar is displayed.
When download starts, a Firewall popup window is displayed asking to allow access, then a "certificate
accept" window is displayed.
Once download is finished, the installation of AWS Client proceeds in background.
Then the AWS client starts.
7.) • Check that the AW Server Client is properly installed:
• In the Windows Explorer, open the Folder C:\Program Files (x86)\Integrad.3\MIV\
• Verify that there is a Solomini folder
• Double click to open the Solomini folder
• Check that there is a folder with the AW Server release name (I.e: 3.2-X.Y-Z where X is the Extension
number, Y is the sub extension number, Z is the build number)
NOTE
If you cannot find this folder, proceed with the workaround described in the
following workaround step.
8.) Workaround Step (optional step if folder with AW Server release name does not exist)
• In the client workstation, you need to change the Admin rights of the following folder:
C:\Program Files (x86)\Integrad.3\MIV\
• Right-click on the folder in Windows Explorer to display its Properties
• Select the Security Tab
• Select Edit > Add
• Depending on your Windows TM language settings, enter the correspondence to "Everyone" (I.e: for
France = "Tout le monde") in text box on the Groups page
• Click OK
• Check Full Control
• Click OK
9.) • When done, exit from the Universal Viewer client.

2.23.1.3 Linux Client installation Procedure

NOTICE
Installation on Linux Client is NOT currently supported with Seamless Integration.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 229

2.23 Job Card IST014B - Seamless Client PC installation and Tests

2.23.2 Server and Client Installation Validation Tests

You will now perform some basic tests to validate the AW Server system installation.
NOTE
This is a test of functionality, not relative performance. Noticeable “hangs” or delays
(beyond a reasonable time) might indicate a test failure.
Two test procedures are required to validate the installation of the AW Server:
• Server standalone test
• Client connectivity test
The server standalone test is a diagnostic test of the server only, without the network and client.
It uses two tools from the AW Server Service Tools:
• The system HealthPage
• The server diagnostic test
The client connectivity test is a system test. It attempts to run an AW Server application from a
client PC via the site’s network. This tests the AW Server as a system.
If both tests pass, the AW Server system is ready for customer demonstration and site
handover.
You will now perform the server standalone test.
This test uses the Service Tools HealthPage and the Server Diagnostic Test to determine whether
the server is working properly, independent of the rest of the system.
If both parts of the Server StandAlone Test pass, the server is working as expected.

2.23.2.1 HealthPage Test

This is the first part of the Server StandAlone Test. The HealthPage evaluates the system hardware
and platform software sub-systems.

2.23.2.1.1 Required Tools

This test requires to connect from the PC on which AW Server client software is installed.

2.23.2.1.2 Procedure
1. Make sure the Client PC is properly connected to / accessible from the site’s local network for
the AW Server.
2. Open a web browser (e.g., Internet Explorer or AW Server OS supported Firefox).
3. Enter the AW Server’s IP Address in the address bar, then press <Enter>.
Example of address bar IP address: http://3.70.211.201.
The AW Server’s main page displays.
4. In the Configuration area of this page, click on the Launch button next to Service and
Administrative Tools.

230 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.23 Job Card IST014B - Seamless Client PC installation and Tests

Installation of a new AW Server

The Service Tools login page displays.

5. Login as service.
The Service Tools HealthPage displays as shown in the following illustration examples.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 231

2.23 Job Card IST014B - Seamless Client PC installation and Tests

Each right-hand column on this page shows color-coded status information indicated by a
GREEN, YELLOW or RED background.

• Green means that the status or value of that item is OK.

• Yellow means not critical (i.e: Mount count for fsck is highlighted in Yellow if the values are
close to max values)
• Red indicates a problem. Any item with a red background indicates a failure which must be
investigated and fixed.
• A white background indicates that “status” is not applicable for that item.
• Not applicable for the image partition fields means that the system is integrated to the
PACS and does not manage the image database.
6. Check the Hardware Subsystem area:
a. Click on the Sensor Details button (GEHC delivered hardware) to display all available
hardware sensor data. Verify that there are no problems.

232 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.23 Job Card IST014B - Seamless Client PC installation and Tests

b. Or click on the Status Details button (virtual AW Server) to display the virtual hardware
resources. Verify that there are no problems.
GEHC delivered hardware:
• A RED indicator in the Hardware Subsystem table or on the Sensor Details page
indicates a failure in the server hardware. (Click on the Sensor Details button to view
the details page.) 2
• Not all hardware failures will cause the server to be down completely. A few examples

Installation of a new AW Server

are: Fans that are in the process of failing, disk drives that have failed-over in the RAID,
and correctable memory errors. It is IMPORTANT to catch the failures that the system
can temporarily withstand, before they cause the server to go down!
• Any hardware failure is a standalone test failure, and requires investigation and
resolution by the hardware vendor. Contact the GEHC Online Center to dispatch the
hardware vendor.
• If the system is not functioning, or is having some other issues that have caused a
request for service, and the Health Page is accessible, any hardware sensor failure
should be treated as the immediate cause of the system failure(s), and dispatched to
the vendor for resolution before any further troubleshooting is done.
Virtual Machine:
• A RED indicator in the Hardware Subsystem for Virtual Machine status may mean
incorrect hardware resources: Contact IT admin of the hospital to update the virtual
resources provided to the Virtual Machine.
7. Check the System Configuration area:
a. Check the basic server parameters. The previous illustration shows normal values for the
AW Server as of this writing.
b. Hover your mouse cursor over each green or red item in System Configuration to see
additional information.
8. Check the Software Subsystem area.
This area shows the status of various software subsystems. Investigate details of any error
conditions by analyzing the corresponding error logs in the Diagnostic – Log Viewer tool
selection.
NOTE
The names in parentheses after each software subsystem service name also appear
after the log names in the log viewer. Use this name to select the log(s) that contain
information about that particular software subsystem service. For example, for the
“Firewall” service, the log name is “pnf”.
NOTE
The Software Subsystem area also has a Restart button. This button is NOT part of
this procedure.
9. Check the Software Subsystems essential for Service Tools area.
• This area shows the status of services which must be running in order for Service Tools to
work.
• A RED indicator in the Software Subsystems Status table indicates a failure in the server
software subsystem.
NOTE
Some of these failures (e.g., filmer subsystem, firewall, Secure Direct Connect,
printing service) will probably not make the server fail. But, they are still failures,
and must be resolved due to their potential impact on the user.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 233

2.23 Job Card IST014B - Seamless Client PC installation and Tests

“Potential” resolution process flow for Software Subsystem failures:

• Investigate the corresponding software error log(s) in the Diagnostic – Log Viewer the
service tools to attempt to understand the nature of the failure, and design appropriate
action.
• The parenthetical (name) after the software subsystem component is also in parenthesis
after the log file name in the Log Viewer.
• Examples: Software Subsystem – Super Server (aweservice)
Example: Log File – Platform: AWE install log (aweservice)
• Restart the software subsystem by clicking on Restart

NOTICE
Remember though, that restarting the software subsystem is just like
rebooting the server – it will disconnect all users!
• Restarting the software can also be done from command line:
/usr/share/ServiceTools/scripts/healthpage/restart_st.sh
/usr/share/ServiceTools/scripts/healthpage/restart_all.sh
(the Restart button is mapped to this script)
• Reboot of the server – disconnects all users.
• Re-installation of the application software package(s).
• Load From Cold (OS software and system rebuild)
If ALL items in the STATUS columns for Hardware Subsystem (and Sensor Details page), Software
Subsystem, and Software Subsystem essential for Service Tools are GREEN, the first stage of the
standalone test has passed.

2.23.2.2 Server Diagnostic Test

The second stage of the server standalone test is a diagnostic designed to test the server’s
advanced applications services and data.
NOTE
This test must be executed from a network PC. It will not display correctly - or at all -
using the local keyboard and display via the Linux desktop (“X”) environment.

1.) □ • In the Service Tools menu, click on Diagnostic to expand that menu. Then click the arrow next to
Test to expand the menu.
2.) □ • Click on Server.
The Platform server test interface should display as shown.

234 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.23 Job Card IST014B - Seamless Client PC installation and Tests

3.) □ After a brief pause, the results for each test in the “Result” column should list the status of each test as
“Passed” (all results should be GREEN).
NOTE
If there is a failure, use the same resolution process as with the HealthPage
Software subsystem status described previously: Log Files analysis -->
possible restart --> software reload, etc.
2
4.) □ • If the health-page software subsystem status indications are all GREEN, and the platform server
tests both pass – then the AW Server StandAlone Diagnostic has passed, and the server is now

Installation of a new AW Server

ready for system/client testing.
This concludes the AW Server standalone test. The procedure in the next section will test the entire
AW Server system – the server, the client, and the network.

2.23.3 Client (System) Test

2.23.3.1 Client Checker Tool

Client Checker is not launched automatically anymore. It has to be started manually. It is not found
in the AWS Client. User has to connect to the AWS home page with an Internet browser, then click
on the "Launch" button next to Client Checker Tool. PC characteristics will be displayed in different
ways on different operating systems
It is important to perform Client Checker before using the AWS Client, in order to make sure the
display has the appropriate quality.The Client Test tool evaluates the client hardware, and network
status, and provides basic information about the PC.
• Java 1.7 minimum release is required to use Client Checker tool.
• Setup in Control Panel / Java / security must be set to "medium security level".
• For latest releases, it is necessary to add the IP address of the server to the exception site's list
in Control Panel to get the tool working. (I.e: https://<AW Server IP_address>)
Monitor (display) quality check

NOTICE
If the system fails either the initial system compatibility or monitor quality test, the
system should not be used to support a medical diagnosis. It may require different
settings or hardware upgrade.
This check evaluates the monitor and graphics card based on the user’s answers to visual tests.
When possible, suggestions are made on how to adjust the monitor. It evaluates the monitor’s
ability to display:
• subtle variations in contrast
• objects without distortion or artifacts
It does not run diagnostic tests on the hardware or replace normal PC quality assurance checks.
Follow the directions displaying on the screen, to run the test.

1.) • In the AW Server main menu, click to launch the Client Checker tool.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 235

2.23 Job Card IST014B - Seamless Client PC installation and Tests

2.) • Follow the directions displaying on the screen to run the test.
• When the monitor quality check is done, you can record the results by clicking the Email Summary
button:

When clicking on Email Summary button, and not email account configured, you will get the following error
message:

236 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.23 Job Card IST014B - Seamless Client PC installation and Tests

"This file does not have a program associated with it to perform this action. Please install a program or, if one
is already installed, create an association in the Defaults program control panel"
• Click OK to acknowledge.
• The same message will display in the screen below, when clicking on Email Configuration button, if no
email account configured.
• Click OK to acknowledge.
NOTE 2
In these cases, use the Save function to create a file that can be copied on a USB

Installation of a new AW Server

key and sent later on through an operational email box.
3.) • To gather the PC’s hardware configuration details, click the Client Information button.
The results display in the tool’s right-hand panel, as in our example:

• To record a summary of these results, click Email configuration.

• Otherwise, to save the detailed results, click Save. By default, a file called ClientConfiguration.txt is saved
to the PC’s \My Documents folder.
• You can copy and paste the content from the Client Configuration Window, either to an email or to a
text editor by using Ctrl+C, Ctrl+V.
• To close the Client Checker, click Close.
NOTE
For further information about the Client Checker Tool, see the AW Server 3.2
Service Manual.
After running the Client Checker, run the Network test. (Service Tools / Diagnostic / Test / Network). See the
following section.

Monitor (display) tests log file

User access information and test results for this check are stored on the server in the /export/
backup/clientcheckerlog. It can be viewed with Service Tools Log Viewer.
When the monitor quality check is done, run the Network test. (Service Tools / Diagnostic / Test/
Network).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 237

2.23 Job Card IST014B - Seamless Client PC installation and Tests

2.23.3.2 Client Test (summary and client information)

Client Worklist Browser Test
This procedure is a basic “launch-and-go test” to validate basic server operation.

1.) □ • Start the Universal Viewer Client and open an exam from the list of exams.
2.) □ • Select the 3D applications button, then select one of the available protocol, for example "Reformat"
The AWS Client Window should open.
3.) □ • Experiment briefly with some of the tools and controls and verify that they respond as expected.
(See the User Manual for details.)
4.) □ • Click on Review steps and select Protocol List, then Protocol Page.
5.) □ • Select another Protocol and check that it is correctly displayed.
6.) □ • Exit the AWS Client Window by clicking the button in the left-bottom part of the window
7.) □

Exit the Universal Viewer Client. Click on the icon as shown.

This completes the basic operational validation test. If all steps passed successfully, the system is
operating correctly.
NOTICE
If any of the preceding steps produced error messages or made the display hang or
display artifacts, this system validation test has failed, and the system is NOT ready for
customer use. Read the “Validation Test Failure – What to do” and “Troubleshooting
Tips” in the following paragraphs.

2.23.3.3 Validation Test Failure – What to do

In the event of system validation test failure:
• Examine error(s) and corresponding error logs using the Log Viewer in Service Tools.
• Re-run the StandAlone diagnostic process.
• If it passes, there could be network-related or client-related issues.
• If it fails, pursue the suggestions in the standalone diagnostic section of the AW Server
Service Manual.
Other suggestions in the event of system validation failure:
• Remove and then re-install the advanced application(s) package(s) using the Version
Management tool in Service Tools. (Reference the Service Tools section of the AW Server Service
Manual.)
• Reload both the OS and platform software (Load From Cold).
Validation Test Troubleshooting Tips
If you cannot perform the “Installation Validation Tests” successfully, troubleshoot the component
that is failing. See examples below:
• If you cannot connect to the server web page, troubleshoot connectivity-related issues:
• Can the PC access other resources on the local network (LAN)?
• Can the PC access the Internet?
• Is the PC configured correctly on the network with a valid IP address, netmask/network
prefix, and gateway?

238 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.23 Job Card IST014B - Seamless Client PC installation and Tests

• Is there an Internet proxy configured in the browser?

• Does this PC require a proxy to be configured?
• Remember, a proxy allows an internal network PC a gateway to an external network (like the
Internet). If the browser attempts to use this proxy to access an internal network resource – like
the AW Server – it will not be able to find it. Conversely, if the PC needs a proxy to get from the
network it is on, to a remote network (like the Internet), and there is no proxy configured, the PC 2
will not be able to connect.

Installation of a new AW Server

• Proxy configurations should be discussed with the site IT admin. For test purposes, they can be
turned off or on to see what the effects are. BUT, doing so could result in other network
resources becoming non-functional until the proxy settings are returned to normal.
• Use “ping” and “traceroute” to test and verify the network functionality. The Service Tools -->
Diagnostic --> Test --> Network tool does some of this for you, as well as a network client
checker test log results table from the server side.
• Try to narrow the connectivity issue down to either a CLIENT issue or a NETWORK issue. A good
way to do this is to test multiple clients on the same subnet. If they all act the same on the
same subnet, chances are there is a network issue. If only one has the problem, focus on it.
• IT IS ALSO VERY HELPFUL TO PERFORM A SIDE-BY-SIDE TEST USING A DUAL-CORE PC, SUCH AS
A GEHC SERVICE/SALES LAPTOP. This is especially useful for “performance” issues, to determine
whether or not the client PC is the problem, and to validate the server.
• Remember, the NETWORK and the CLIENT (other than installing AW Server client software on
ONE customer client as specified in the contract) are NOT the responsibility of GEHC. Once the
server is proved to be working correctly, and that the problem resides with the network or the
client, the AW Server service model is validated, and the final resolutions for issues related to
the network or client belong to the customer.
This completes the AW Server Installation process.
Once the system passes these validation tests, it is ready to be turned over to the customer for
applications training and/or normal use. This is described in the next Job Card.

NOTICE
Please remember to log only actual installation time against the server’s installation
dispatch. Use TRAINING (or another appropriate account) to log ‘observation’ or ‘non-
installation’ site AW Server activities. Also make sure to include in the installation
dispatch the “completion” comments: "HW verification complete prior to software
install”

2.23.3.4 Printing tests

Printing tests are not applicable for Seamless Integration, as the AW Server Client is part of the
Universal Viewer Client

2.23.3.5 Client Monitor screen resolution setup

Client Monitor screen resolution setup is not applicable for Seamless Integration, as the AW Server
Client is part of the Universal Viewer Client
The Client configuration is complete.
Proceed to 2.24 Job Card IST015 - Final Settings on page 240

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 239

2.24 Job Card IST015 - Final Settings

2.24 Job Card IST015 - Final Settings

You will now go through the final settings prior to handover the AW Server to the customer. It is
advisable that one person representing the customer (preferably an IT administrator) go through this
Job Card with you.

2.24.1 SNMP setup in iLO Service processor

In order to have the Hardware related traps caught in a log file on the AWS side (/var/log/
snmptraps.log), it is necessary to configure SNMP in the iLO service processor of the AW Server.

2.24.1.1 Pre-requisite for using with Prodiag

Not applicable for Seamless integration
• InSite is checked out (see 2.16.2 Remote Service on page 109)
• SNMP is configured in the AW Server (see 2.16.8 SNMP Configuration on page 117)
• The iLO service processor is configured and operational
• It is mandatory to have declared the Gateway for iLO.
• The IP address of the iLO must be in the same subnet as the server IP address.
NOTE
Prodiag is configured by default to check on the existence of the /var/log/snm
ptraps.log file once a day. If the file has a content (other than the default
opening line), then Prodiags sends the log file to GE backoffice. Prodiag can only
send the log file if the system is inSite checked out. Also note that Prodiag is
configured by default to send with no delay any software reported issue.Prodiag
is configured by default. (For more information, see 2.16.13 Prodiag configuration
on page 130)

2.24.1.2 SNMP setup in the iLO 5 service processor

This procedure details the steps for iLO 5. For iLO 4, iLO 3 and iLO 2, refer to A.8 SNMP setup in the
iLO service processor on page 418.
1. At the Client PC or FE laptop, open a browser (Firefox or Internet Explorer) and type in the AW
Server’s iLO Service processor IP address.
I.e: https://3.249.14.161/
2. When the login page loads, login as root.
3. When the iLO page loads, select Management > SNMP Settings.

240 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.24 Job Card IST015 - Final Settings

Installation of a new AW Server

4. Scroll down to SNMP Alerts and check that iLO SNMP Alerts and Cold Start Trap Broadcast
are enabled. If they are not enabled, enable them then click on Apply.

5. To enter the SNMP Alert Destination, scroll down to SNMP Alert Destinations and click on New.

6. Enter the SNMP Alert Destination:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 241

2.24 Job Card IST015 - Final Settings

• No GE PACS case : Enter the AW Server IP address

• GE PACS case: Enter the SNMP Trap Receiver server IP address
• Site’s SNMP server case: Enter the Site’s SNMP server IP address
7. Click on Add.
8. To send a test alert to the setup destination logfiles, click on Send Test Alert in SNMP Alerts.
9. Launch the Terminal from the Service Tools > Tools and check the /var/log/snmptraps.lo
g file.
10. Logout from the iLO Service processor.

2.24.1.3 Service Workflow

The following is given for your information only, in order to point out the main differences between
the DI and IT organizations workflow for SNMP traps management.

2.24.2 Anti-Virus setup

If your site requires that you set up the ClamAV anti-virus, refer to A.5 Using the ClamAV Anti-Virus
Tool on page 373 for instructions.

2.24.3 Scalability (cluster) mode operation verification

If applicable to your site, verify now that all the virtual AW Servers setup for cluster mode operation
show up as "mode is active" in the cluster, that one of them is setup as "preference server for the
cluster" and is active, and that none of them has been left in Maintenance mode for instance.
Also check that the "node has some problem" icon does not show up, unless only one external
license server has been setup for your site.

242 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.24 Job Card IST015 - Final Settings

Installation of a new AW Server

2.24.4 Hard disks serial numbers
The /var/tmp folder contains a disk_sn.out file created at time of installation, containing the serial
numbers of the disks of the server and of the DAS (if applicable).
This list is aimed to collect at time of installation, or at later time upon replacement of any of the
hard disks, information on the serial numbers of all the hard disks while they are operational and
able to send information. It is recommended to save this list of serial numbers for future use.
If at a later time, your system gets one or more defective hard drive(s), the hard drive(s) may no
longer be able to reply to a request and send information on their serial number.
When contacting HP support center for getting replacement hard disk drive under warranty, the
serial number of the defective disk(s) will be requested by HP support.
Having the serial number on a list will allow you to know the serial number of the disk(s) that are no
longer able to send a reply, so you can communicate it to HP support.

2.24.4.1 At installation time

Open a Terminal tool and type in:
cd /var/tmp <Enter>
cat disk_sn.out | grep Serial > /export/backup/HDDSerial<Date> <Enter>
I.e: cat disk_sn.out | grep Serial > /export/backup/HDDSerial20150813 <Enter>
You may also copy the file on the Client PC, or FE laptop, and/or any USB device, especially if the
system has no DAS, and therefore does not have the /export/backup directory.
You may also want to write down in the Site’s maintenance logbook those serial numbers.

2.24.4.2 After hard disk drive replacement

You must update the /var/tmp/disk_sn.out file with the replaced HDD(s) serial number(s).
• Open a Terminal and type in to generate the new list of serial numbers:
/usr/local/bin/gener_list_diskSN <Enter>
• Proceed with steps described in 2.24.4.1 At installation time on page 243 to store the updated
HDD serial numbers list for future use.

2.24.5 PNF Firewall setting

The Server is exposed to a Security Risk if the PNF Firewall is turned Off.
Malicious users can login via SSH and access, corrupt, or delete sensitive files.
The AW Server PNF (Product Network Filters) software and configuration is automatically installed
with the platform software load.
It is automatically configured in a "default" configuration for the AW Server environment, and should
not require any service intervention. For this reason, it does not have a tool interface

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 243

2.24 Job Card IST015 - Final Settings

• To check the status of the PNF Firewall from the Service Tools, connect to the Server’s Service
Tools Web page. Check the Firewall (pnf) status in the Health Page:

The status should appear as “OK” on a green background.

• If the Firewall is not active, contact the local IT to see if it was intentionally turned Off. If not, you
must turn it On:
• In the Service Tools, go to Tools > Terminal menu.
• Click the New modal Terminal button to open a command window.
• In the Terminal Window, login as user root.
• Type in the following command to enable the Firewall:
service pnf on <Enter>
• Go back to the Server Healthpage and make sure that the Firewall is now ON.
NOTE
A mechanism has been implemented which keeps PNF Firewall turned ON. A daemon
process check the PNF status and, if needed, switch it to ON on a daily basis. However, if
you find that the PNF Firewall is not active, apply the above manual procedure.

2.24.6 Media Creator

Media Creator allows you to write exams/series/images to a selected USB key or CD/DVD.
It is automatically configured in a "default" configuration for the AW Server environment and should
not require any service intervention. For this reason, it does not have a tool interface.
To check the status of the Media Creator from the Service Tools, connect to the Server’s Service
Tools Web page. Check the Media Creator (mediacreator-app) status in the Health Page:

The status appears as OK on a green background.

2.24.7 Volume Viewer performances on VM

This section only concerns AW Server running on virtual machine.
NOTE
Hyperthreading needs to be turned off on the Hypervisor to optimize the
performances of the AW Server and the 3D applications. Indeed, the software is
optimized for CPU settings with Intel Xeon architecture and without hyperthreading. So, it
is recommended to deactivate the Hyperthreading on AW Server. Therefore, it is not
appropriate to have other customer’s VMs running on the same Hypervisor, if these other
VMs require Hyperthreading to be activated, otherwise it could impact the AW Server
performances.

244 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.24 Job Card IST015 - Final Settings

NOTE
In that case, Volume Viewer 3D performances may be improved by configuring the
number of active threads as follows.
• To do this setup, open a Terminal, login as root and edit the file with the "vi" editor or any
suitable editor such as "nano":
vi /export/home/sdc/vxtl/bin/start_volan <Enter> 2
• Add the following line at 3rd position in the file:

Installation of a new AW Server

setenv VXTL_NUMCPUS XXX (where XXX is either 4 or 12)
I.e: setenv VXTL_NUMCPUS 4
where XXX is the number of physical cores available for the Virtual machine. This number XXX is
usually half the number of cores available for the Virtual Machine:
• For Low Tier virtual machine (8 virtual CPUs) >>> set XXX= 4
• For High Tier virtual machine (24 virtual CPUs) >>> set XXX= 12
• Save the file and quit the editor
NOTE
This configuration must be re-applied each time the Volume Viewer application is re-
installed.

2.24.8 For China only - CFDA Registration documents

In China, a regulatory requirement states that Platform/Applications CFDA Registration documents
shall
be available on client site.When appropriate, they will be delivered with the product, either in paper
format or electronically on the CFDA Doc addendum media.
• If CFDA Registration documents are delivered on paper, they must be given to the client and be
securely stored on site in case of an audit.
• If they are delivered on a media, they must be installed on the AW Server, following the
procedure described below.

2.24.8.1 Installation on server

Each time the AW Server platform will be installed or reinstalled (Load From Cold), the CFDA Doc
addendum will have to be installed as well.
If the platform/applications release changes (in case of Upgrade), the CFDA Doc addendum will have
to be updated. Make sure to always install the latest available version.
• Refer to Job Card IST009 2.17.5 Load the Application(s) from media on page 137 instructions, to
install the CFDA Docs addendum from its media, in the same way you install an Application,
through the Version Management tool.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 245

2.25 Job Card IST016 - System Handover to Customer

1. Insert the media into the CD/DVD drive of the Client PC (or insert the USB device into the USB
port) and click Upload ISO button. Select the file (Browse) and click Send to system button.
2. When the package is uploaded, it shows up in the "Available for installation on Hard disk"
section. Select the package (click on the radio button) and click on the Install button.
3. When done, check under the Documentation / Documentation tab, that the CFDA addendum
doc(s) are available in the User documentation section (select language = Chinese)

2.24.8.2 Upgrade
• To upgrade the documents to a newer version, you shall first uninstall them and then install the
new revision following the procedure described in 2.24.8.1 Installation on server on page 245
• To remove the document package from the disk, proceed as follows:
• Remove the documents: Click on the Radio button in the Currently installed section, then
click on the Uninstall button.
• Remove the package: Click on the Radio button in the Available for installation on Hard disk
section, then click on the Remove package button.
NOTE
Other countries: Discard the CFDA doc addendum media.
The final configuration is complete.
Proceed to 2.25 Job Card IST016 - System Handover to Customer on page 246

2.25 Job Card IST016 - System Handover to Customer

You will now go through the procedure to handover the AW Server to the customer.
It is REQUIRED that at least one person representing the customer (preferably an IT administrator)
go through this Job Card with you.
Explaining these items correctly and thoroughly to the customer is crucial to a smooth handover.
As a final step, you will also show the customer how to do a configuration backup.

2.25.1 Installation handover tasks - Handover Checklist

When transferring the AW Server system to the customer, it is important to inform the customer –
especially the site IT administrator person(s) – what their expectations should be regarding the
following items, and where to find certain information.

246 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.25 Job Card IST016 - System Handover to Customer

Discuss the following points with the site's IT admin and/or CUSTOMER.
Handover information outline reference.
• DICOM Demo exams
• Administrator guide (part of the User’s guide)
• User Account Management
2
• DICOM Hosts management

Installation of a new AW Server

• Failure / Repair process
• iLO information and capabilities
• Failure discovery process
• Open Source Software for AW Server
• Warranty
• Preventive Maintenance
• Applications training (see 2.25.3.1 AW Server User and IT Administration Training on page 253)
• 3rd Party certificate
1. DICOM Demo exams
NOTE
Bypass this step for Full, Seamless or DICOM Direct Connect Integration.The DICOM
demo exams installation is not applicable to Full, Seamless or DICOM Direct Connect
Integration, as no image data can be loaded to the AW Server image database.
For the purpose of system testing, demonstration, and training there is a demo exam/image
data loaded during the platform software installation. This image dataset is embedded in and
part of the platform software package. Once removed, the demo images cannot be re-imported
directly from the AWS software DVD.
However, they can be re-imported from the AWS Demo Exams DVD, together with more demo
exams, from the Client User Interface, using the Tools/Free Image Importer. Refer to the AWS
User guide for more precise details.
High level workflow:
• Launch the AWS Client from the Client PC
• Insert the AWS Demo Exams DVD into the drive of the Client PC
• Click on Tools tab
• Click on Free Image Importer.
• Click on Import more images
• Select CDROM
• Search for the compressed diagnostic images file and click open to start importing images.
2. Administrator guide
• Go to Service Tools > Documentation > Documentation, click on Documentation button. 2
tabs open. In the tab containing the User guides, the AW Server Administrator Guide is
available.
• Another way to obtain the Administrator Guide is to go to the AW Server home page in an
internet browser, then click on "Open" next to "Operator Manuals" and "AW Server/3D
Viewer/2D Viewer/Volume Viewer".
User Account Management

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 247

2.25 Job Card IST016 - System Handover to Customer

• The GEHC FE will help the IT admin to configure one or two accounts or the Enterprise
server configuration during system turnover. But, the complete or ongoing user account
creation and management is owned by the customer’s site IT ADMIN or equivalent
operative.
DICOM Hosts Management
• The GEHC FE will help the IT admin to configure one or two DICOM hosts during system
turnover. But, the complete and ongoing DICOM hosts creation and management tasks are
owned by the customer’s site IT admin or equivalent operative.
Preferences Management
• The GEHC FE will help the IT admin to configure the Preferences User-share menu under
Service Tools / Tools sub-menu.
3. AW Server Failure / Repair Process
Refer to the AW Server Service Manual for details on Break/Fix process.
All requests for service should be through the GEHC service request process.
The GEHC failure and repair model covers two basic points, hardware and software:
Hardware
• GEHC has the wing-to-wing service responsibility to support and repair all hardware
failures (or via the hardware vendor - High Tier server case).
• If needed, GEHC will dispatch the hardware vendor to repair or replace the hardware issue.
• The hardware vendor will complete the hardware repair, then turn the service call over to
GEHC for follow-up and turnover to the customer.
• To maintain security and confidentiality, all replaced system IMAGE / PATIENT DATA disk
drives will be left on-site or if not, use a Disk Wipe Tool - to permanently remove data.
Refer to 3.10 Job Card UPG003 - Hardware Upgrade on page 309- Section 6-8.
• All other NON-PATIENT-DATA components will be exchanged, or disposed of per the
vendor’s Hardware Replacement Policy for that particular part.
Software
• GEHC has the wing-to-wing service responsibility to support and repair all software
failures.
4. iLO information and capabilities
The iLO (HP) service processor has many service capabilities. General information for these
capabilities can be found in the service manual and the vendor’s technical publications
referenced there. GEHC is not responsible for the full support of the iLO, or its functionality.
5. Failure discovery process
The AW Server hardware has redundant components that can and will fail-over to a back-up
state when one of these components fails. End users will not automatically know if this
happens. GEHC will not automatically be alerted. The only way the failure will be noticed is
when someone accesses the system service tools and / or inspects the fault LED’s on the
SERVER or DAS chassis. Whenever a fault LED or FAULT ALARM is observed, GEHC should be
notified immediately through the GEHC service request process.
6. Open Source Software for AW Server
Discuss with customer’s IT and or Customer Admin designee:
Portions of this product are subject to various open source license agreements that require re-
distribution of source code contributions. These contributions may be found on the media
labeled "Open Source Software for AW Server."

248 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.25 Job Card IST016 - System Handover to Customer

This is a data media containing no documentation or executables that apply to the usage or
service of this product. The media is included in the product structure in order to comply with
open source license terms. Depending on individual site requirements, you may either store this
CD/DVD with other AW Server media or provide it to the customer’s system administrator.
7. Warranty
Discuss with IT and or Customer Admin designee: 2
The AW Server is under a ONE-YEAR warranty by GEHC. All service requests must be directed to

Installation of a new AW Server

GEHC service during this period. There will be a service contract offering(s) after the ONE-YEAR
warranty period. If the site decides not to purchase a service contract, the on-going service of
the AW Server will be handled on a time-and-materials-and-availability model if directed to
GEHC.
HP hardware warranty is THREE years. Refer to section 2.25.3.7 HP Care Pack Warranty
extension on page 256 for details.
8. Planned Maintenance (P.M.)
Discuss with IT and or Customer Admin designee:
The hardware has no PM requirements specified by the vendor. However, some basic PM tasks
such as dust cleaning are described in the Service Manual.
It is recommended that the site’s IT department periodically inspect the SERVER for fault LED
indications.
If a fault LED or FAULT ALARM is observed, GEHC should be notified immediately through the
GEHC service request process.
9. 3rd Party certificate
3rd Party certificate acquisition and maintenance is under the full responsibility of the
customer.
Upon request to install a customer’s owned certificate, FE shall refer to the AW Server 3.2
Advanced Service Manual, Appendix A.23 for instructions.

2.25.2 Backup Parameters and Settings

2.25.2.1 Network and UPS configuration Backup

The network configuration is performed via AWS network configuration script, and IS NOT saved by
the AW Server Service Tools backup process. The network configuration is considered a prerequisite,
and is separate to the AW Server remote configuration and service tools.
The important information to record in the site log book (or some similar permanent record) - or
access from the existing site IT records - are the following data points:
• Server IP address
• Server hostname
• Server Netmask/Network prefix
• Gateway IP address
• Site network DNS IP address(s)
The network configuration for the system was already recorded as part of the site survey process.
Alternatively, ALL of this information can be retrieved from the site's IT department, in case this
information is missing, not available via the system tools, or undergoing site changes.
We recommend that you backup the following files and that you also write down the
information in the Site’s maintenance logbook if not already done.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 249

2.25 Job Card IST016 - System Handover to Customer

The Network and UPS parameters will be saved in the /export/backup directory, which is used to
store the System and Users parameters.

NOTICE
For system with an external disks array for images (DAS), the /export/backup/ directory
is preserved in case of OS re-installation.
• This is not the case for Full, Seamless or DICOM Direct Connect Integration as there is NO DAS
disks array. In this case, the backup directory is created on the system disks and will not be
saved at OS reinstallation.
• This is also not the case for AWS2.0 / AWS3.0 upgrade to AW Server 3.2 release, as the
filesystems will be upgraded from EXT3 to EXT4 filesystems, and consequently erased.
Therefore, ALSO write down ALL the information in the Site’s Maintenance logbook.

1.) • From the Service Tools, open the Terminal (Tools sub-menu).
• Login as root:
root <Enter>
Password : Enter the root password
2.) Network configuration
• Save the Network configuration (create a "network.txt" file) :
ip addr > /export/backup/network.txt <Enter>
cat /export/backup/network.txt <Enter>
(to check if the appropriate info was saved)
• Save the hosts file configuration (create a "hostname.txt" file) :
cat /etc/hosts > /export/backup/hostname.txt <Enter>
cat /export/backup/hostname.txt <Enter>
(to check if the appropriate info was saved)
• Save the Routers configuration (create a "routers.txt" file) :
ip route > /export/backup/routers.txt <Enter>
cat /export/backup/routers.txt <Enter>
(to check if the appropriate info was saved)
• Save the file containing DNS parameters:
cat /etc/resolv.conf > /export/backup/dns.txt <Enter>
cat /export/backup/dns.txt <Enter>
(to check if the appropriate info was saved
3.) UPS configuration (High tier server only)
For the HP High Tier server. Save the UPS configuration (if applicable):
• Create the UPS directory
mkdir /export/backup/ups <Enter>
• Stop the HPPP service:
service HP-HPPP stop <Enter>
• Copy the configuration files
cp /usr/local/HP/PowerProtector/configs/config.js /export/backup/ups/config.js <Enter>
cp /usr/local/HP/PowerProtector/db/mc2.db /export/backup/ups/mc2.db <Enter>
• Restart the HPPP service:
service HP-HPPP start <Enter>
• NOTE
The UPS configuration can be restored by reversing the above scripts:

250 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.25 Job Card IST016 - System Handover to Customer

service HP-HPPP stop <Enter>

cp /export/backup/ups/config.js /usr/local/HP/PowerProtector/configs/config.jps <Enter>>
cp /export/backup/ups/mc2.db /usr/local/HP/PowerProtector/db/mc2.db <Enter>
service HP-HPPP start <Enter>

2.25.2.2 Configuration Backup 2

You will now show the customer, how to create a configuration backup.

Installation of a new AW Server

To minimize the chance of file corruptions during configuration backup, the backup will be performed
in Maintenance Mode.

NOTICE
Frequent configuration backups are CRITICAL for service and troubleshooting.

1.) □ From the Service Tools, click on Maintenance to expand the menu.
2.) □ Click on Maintenance.
The Server Maintenance Tasks page will display the Maintenance Guide tab. Refer to Chapter 4,
A.4 Maintenance Mode on page 369 for details.
3.) □ Send a broadcast message
NOTE
This step is optional as no users should be connected yet (new installation).
• Read the page, then click the Broadcast Message tab.
• In the Broadcast message field, type a message stating that you will temporarily disconnect all
clients to perform maintenance at (the time three minutes from now). (Example: “The AW Server
will be shut down at 10:35 a.m. Save your work and logout.”)
• When your message is complete, click Set Message to send the message. This will warn all
connected clients of your intentions to disconnect them.
NOTE
The Query Message button displays the last message entered.The Clear
Message deletes all text in the message box. Always click Clear Message
when done so that the last message is not inadvertently re-sent.
4.) □ Click the Start Maintenance tab. This tab shows which clients (if any) are connected. (None are likely
at this point in the installation process.)
5.) □ In the Disconnect message field, you can type a message stating that the client is being disconnected
now. This message will display at the clients when they are actually disconnected. If you do not enter
anything, the default message “Your session has been closed by Administrator/Service” will be sent.
6.) □ Start maintenance
• When the warning time (3 minutes) has expired, click the Start Maintenance button.
The following warning will pop up.

7.) □ Click “Yes”.

Another popup will state that you are now in maintenance mode.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 251

2.25 Job Card IST016 - System Handover to Customer

8.) □ AW Server configuration backup

• Click on Backup to expand the menu.
• Click System configuration.
The system configuration backup interface will display as shown below:

• Select a recurrence for future backups. You may choose daily, weekly or monthly.
• Choose a starting time. Use a time where the server is supposed to be on (i.e: 12:00), in case it
would be regularly turned off in the evenings.
• Click on the Activate button to save.
The message “success” will display.
NOTE
Recurrent automated backups are performed in normal mode, not under
maintenance mode, that is to say, depending on the time of the day they are
scheduled, they may not contain the latest changes done by the Users.
Up to 3 Recurrent automated backups will be kept a long time. The removal of the older backup file will
be automatic when the latest backup is performed.
Manual backup is not concerned and will be kept a long time, until it is intentionally deleted.
9.) □ Then proceed to the immediate backup:
• Make sure all “Available configurations” boxes are checked,
• Check the “Select as last known good configuration” checkbox,
• Click on Save on System button.
This will save the configuration on the backup partition of the server. When done, the message
“successful” displays.

NOTICE
For Full, Seamless or DICOM Direct Connect Integration, the backup must be made on
the Client PC and/or FE laptop, as there is no external disks array (DAS), and reloading
the software (OS + AWS) deletes all files on the system hard disk.

252 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.25 Job Card IST016 - System Handover to Customer

• Also click on Pull from system button

This will allow saving the configuration as a ".tar.gz" zipped file on the Client PC (or your laptop), and
transfer it later on your USB key for example.
• The following window will popup. Click on the Save button.

Installation of a new AW Server

A new window will popup, to let you select the destination.
• Select the place where you want the file to be saved and click on Save.
10.) □ Finally, save the backup on a media like a USB key, for future use.
NOTE
As mentioned in the previous section, Network parameters are not part of the
backup tool. These parameters must be saved manually. In order to ease
getting this information, a link to the Network menu is provided on the
Backup and Restore tools, as shown in the illustration below.

2.25.3 Final steps

2.25.3.1 AW Server User and IT Administration Training

Applications training will be scheduled shortly after the installation. User/Client browser
functionality, workflow, tools, and user account management will be topics covered by the training.
The IT admin can be trained on advanced Applications.
Refer to the Sales Team, to train the radiologists on Advanced applications.

NOTICE
Also recommend that the "Hibernation" feature should be turned out on Windows TM
Client PCs used (also for Universal Viewer), to avoid entering into blocking timeout.

2.25.3.2 GIB / SIEBEL update and paperwork

Send the customer’s Global Installed Base data to GEHC. Send all paperwork from the installation to
the appropriate recipient (i.e., GEHC or the customer)
COMPLETE THE PRODUCT LOCATOR INSTALLATION CARDS (ICD CARDS DELIVERED WITH THIS
PRODUCT) AND RETURN THEM TO YOUR PRODUCT LOCATOR ADMINISTRATION. OTHERWISE, YOUR
SYSTEM UPGRADE WILL NOT BE REGISTERED IN THE GLOBAL INSTALLED BASE DATABASE (GIB)!!!

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 253

2.25 Job Card IST016 - System Handover to Customer

Global Installed Base database may be directly updated using the following link:
http://gib.gehealthcare.com
• GEHC Global Install Base database web site is available from any outside web enabled PC.
• The FE can enter the model/serial into the Service Tools interface and send the GIB data up to
GIB via email. So, make sure to fill-in all the information in the service tools Initial Configuration
> Device Data & User Data.

NOTICE
USCAN System ID / Assets are no longer found in eGib and are now located in the
CRM Siebel / Assets database.

• "Installs: Follow MyWorkshop document DOC1701877, Job Card IB Verification

• "Upgrades: Follow MyWorkshop document DOC1618060, Job Card FE Upgrade
Instructions
• "Asset Swaps: Follow MyWorkshop document DOC1589267 Job Card FE Asset Swap
NOTE
EDS US remains on GIB until further notice
.

2.25.3.3 Register High Tier Server with Genpact

Make sure you have completed this step described in the 5719442-1EN : AW Server 3.2 Hardware
Install Manual, chapter 3, Section 3, in order to send the hardware details. ( GON Number, GE
Server Part Number , Vendor Server Serial Number, Customer Site Name, etc..) to the Genpact
organization.

2.25.3.4 Capture the UDI number in Service Records

Regulatory agencies are requiring a Unique Device Identification (UDI) system to adequately
identify medical devices through their distribution and use.
AW Server Medical Device UDI is available for each platform Software release.
NOTE
There is no UDI for Advanced Applications when installed on AW Server. There is no UDI
for standalone Hardware.
1. Capture the AW Server 3.2 UDI, REF and LOT numbers in the Service Records, according to the
process in place in your pole.
The UDI is available from the AW Server 3.2 Main page.
The UDI, REF and LOT are available from the HealthPage and are contained in the Configuration
file.

254 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 2.25 Job Card IST016 - System Handover to Customer

Installation of a new AW Server

NOTICE
A distribution UDI value and bar code are printed on the AW Server SW & Docs
media. It is not the Medical Device UDI. Do not scan or record this value in the
Service Records.
Configuration file output example showing UDI information:
2. To avoid transcription errors, extract the UDI value from the Configuration file. This allows you to
copy it from the file and paste it in the Service Records.
Click on the Display button under the Configuration and status section.

Under the STATION CONFIGURATION section, the UDI, REF and LOT numbers display.
For example:
• UDI : (01)00840682102384(10)AWS3D2E000
• Medical Device Item number [REF] : 5719780
• Medical Device Production [LOT] : AWS3D2E001D0

2.25.3.5 Print the AWS Configuration

Display the HealthPage and under the Configuration & status tab:
• Click on Pull from system button. This will save the AWS configuration as a zipped file.
• You can copy it to your USB key for example.
• Unzip the file and print it with one of the Postscript printers setup for the Client PC you are
using at the moment.
• Leave the print attached to the Maintenance logbook or to the paper copy of the Installation
Manual.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 255

2.25 Job Card IST016 - System Handover to Customer

2.25.3.6 Customer Release Note and information

Deliver the CRN (customer release note) if any, to the customer.

2.25.3.7 HP Care Pack Warranty extension

To be done for HP High Tier server only:
Notify the customer that the HP Care Pack warranty will expire in 3 years, and that they will directly
receive notification from HP, to ask if they wish to pursue the support contract from HP for the
hardware.

NOTICE
The customer is responsible for renewing the Care Pack contract with HP after the
warranty period. Refer to the AW Server 3.2 Hardware Installation Manual
5719442-1EN at chapter 3, Section 3.3.6,

2.25.3.8 PSI code verification

Check that the PSI code in the database is appropriate, and if not, contact your Support Center to
have it corrected:
• I for EDS
I.e: IAWV32for virtual AW Server 3.2
• C or W for HCS
I.e: CAWH01or CAWH02for High tier physical server
CAWL01or CAWL02for Low tier physical server
CAWV32for virtual AW Server 3.2

2.25.3.9 Site Cleanup

Clean up any debris left from the installation and testing process.
Make sure to appropriately dispose/recycle the useless cables.

256 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3
Chapter 3 Upgrade

3.1 Foreword
NOTE
For the AW Server integrated within the CT/MR Console Environment (Edison HealthLink
or CT Nano-Cloud), refer to A.12 AW Server Integration in CT/MR Console Environment on
page 433.
Section 3.3 Quick Start Installation Guide - Software Upgrade on page 259
This section gives an overview of the main steps to upgrade the software of an existing AW Server.
When appropriate, it references the information detailed at chapter 2, for installation of a new AW
Server. The steps described in this section for upgrading the software can also be used to simply
reload the same software release.

NOTICE
AW Server 3.1 / AW Server 3.2 release introduces the Ext. 4 filesystem that is faster
than the Ext. 3 filesystem currently used by AW Server 2.0 and AW Server 3.0 releases.
When upgrading from AW Server 2.0 to the AW Server 3.2 release, you will have to make the
following choice:
• The customer agrees that all images currently stored on AW Server are archived on another
system (I.e: PACS) and that they can be erased from the AW Server.
It is therefore possible to upgrade the Image filesystem from Ext. 3 to Ext. 4.
The filesystem check (fsck) time will be faster than for AW Server 2.0 / AW Server 3.0 products.
• The customer DOES NOT agree that all images currently stored on AW Server can be deleted
from the AW Server. It is therefore NOT possible to upgrade the Image filesystem from Ext. 3 to
Ext. 4 and the filesystem will remain as Ext. 3. The filesystem check (fsck) time will be identical
to what it was for AW Server 2.0 / AW Server 3.0 products, that is to say quite longer.

NOTICE
EDS - Hardware upgrade for Seamless Integration:AW Server 2.0 / AW Server 3.0
upgrades to AW Server 3.2 Seamless Integration consist on a complete upgrade/
swap to Virtual hardware. The GEHC delivered HP hardware (HPE ProLiant DL580
G7 Server / HPE ProLiant DL560 Gen8 Server) is no longer supported for AW
Server 3.2 Seamless integration with the Universal Viewer. Only virtual hardware
is supported with the AW Server 3.2 release / Seamless integration.

NOTICE
POTENTIAL ISSUE LOADING HELIOS OS TO DL580G7 WHEN DOING AW SERVER
2.0 TO AW SERVER 3.2 UPGRADE: THERE CAN BE RARE CASES WHERE AN ISSUE
OCCURS WHILE LOADING THE HELIOS OS TO THE OLDER HPE PROLIANT DL580
G7 SERVER DURING AW SERVER 2.0 TOAW SERVER 3.2 UPGRADE. THE
FOLLOWING MESSAGE CAN DISPLAY:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 257

3.2 Quick Start Installation Guide - Hardware Upgrade

If the message above displays:

Your HPE ProLiant DL580 G7 Server is most probably running an older Firmware version.
You must update it prior to attempt to load the new Helios OS again.
• Click on Reboot button to reboot.
Your AW server will reboot with the AW Server 2.0 release which has been preserved.
• You can possibly give the system back to the user until you are able to upgrade the
Firmware, then proceed to the upgrade to AW Server 3.2 release. OR
• You can proceed to the Firmware download from the HP service side and upgrade it.
• In both cases, refer to the AW Server 3.2 Advanced Service Manual 5771771-1EN,
Appendix A.17 for instructions.
Note that the HP hardware is not considered itself as a Medical Device, so you can upgrade the
server’s firmware to the latest Firmware release available on the HP web site.
Section 3.4 Scalability Upgrade on page 262
This section gives an overview of the main steps to:
• Add an AW Server in the cluster.
• Remove an AW Server from the cluster.
• Upgrade an AW Server 3.0 release cluster to AW Server 3.2 release.
• Upgrade the software to a more recent release within a AW Server 3.2 cluster.
Section 3.5 Hardware Upgrade on page 264
This section gives an overview of the main steps to upgrade the hardware.
Currently, hardware upgrade consists on replacing the older hardware by a new hardware preloaded
with OS, AWS Platform and Applications software or by a virtual AW Server (no preload).
Section 3.6 Applications Upgrade on page 264
This section gives an overview of the steps to add new or to upgrade Applications.
Section 3.7 System Configuration Restore Matrix on page 266
This section gives an overview of the System Configuration restoration rules.

NOTICE
When installing from electronic files, always refer to AW eDelivery Service Guide
5761599-8EN for detailed instructions.

3.2 Quick Start Installation Guide - Hardware Upgrade

258 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.3 Quick Start Installation Guide - Software Upgrade

3.8.2 Verify that AW Server is operational on

page 272
Proceed with old hardware checks

3.8.3 Backup the configuration on page 274

New hardware installation: Refer to

Installation of a new AW Server on page 7 3

Upgrade
3.8.7 Restore the Server configuration and
licenses on page 292

3.10.6 Patient data transfer on page 311

Do you transfer
Yes
patient data from
old server?

No

A.11.2 Old hardware return process on page

430

AWS System is ready for the customer

3.3 Quick Start Installation Guide - Software Upgrade

The following guide intends to summarize the installation steps to upgrade AW Server software. The
upgrade instructions will be detailed along this manual in the different sections of 3.8 Job Card
UPG001 - Software Upgrade on page 269
Upgrade preparation, one week before the upgrade.

Start
!!! DO NOT MISS THIS UPGRADE PREPARATION ONE WEEK BEFORE THE UPDATE !!!

3.8.1.1 Upgrade preparation - Perform Filesystem check on page 270

• Remotely connect to the AW Server and check the Filesystem properties (physical server
only). If no remote access is available, ask the IT Admin to run the properties check.

3.8.1.2 Upgrade preparation - Contact the IT Admin of the site on page 271
• IT Admin will force a Filesytem check over the weekend preceding the upgrade, if deemed
to be necessary by the properties check result (physical server only), unless image data is

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 259

3.3 Quick Start Installation Guide - Software Upgrade

also stored on another system (E.G: PACS) and does not need to be preserved and
reinstalled.
• IT Admin will arrange the server’s room availability (if applicable).
• IT Admin will inform the Users that the server will be unavailable during the upgrade.
• IT will ensure the Clients PCs are running a supported Windows version.

3.8.1.5 Patients Image data backup on page 272

Contact the IT Administrator and:
• Ask for authorization to delete the existing images.
• Explain the benefits of upgrading the filesystem to EXT4 (faster filesystem) versus the
inconvenience of deleting the existing images that are stored on the EXT3 filesystem used
on AW Server 2.0 / 3.0.

Proceeding to the upgrade.

3.8.2 Verify that AW Server is operational on

page 272 prior to perform the upgrade.
• Connect to the AW Server and check the
HealthPage and sensors status
• Backup (write down) the network and the
UPS (if applicable) configurations
• Turn the auto-delete feature “off”
• Connect to the iLO service processor (if
applicable) and check the event logs and
other status

3.8.3 Backup the configuration on page 274

• Enter the Maintenance mode
• Backup the site configuration
• Disconnect users and shutdown server

3.8.4 HP ProLiant ML350 G6 Server Hardware

Upgrade on page 281
• 3.8.4.1 Upgrade memory to 24GB (or 64GB)
on page 282
• 3.8.4.2 BIOS Hyperthreading setup to OFF
on page 282

3.8.5 Software upgrade on page 282

• Prepare the software kit

3.8.5.1 OS loading on page 283 OS Template

• Load OS from media

260 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.3 Quick Start Installation Guide - Software Upgrade

3.8.5.2 AWS Platform software

loading on page 290 AWS media
• AWS platform software load
• Setup Network parameters
• Setup Date/Time parameters

3.8.5.4 Reinstall the VMware 3.8.5.3 Loading the HPE R/

Tools on page 291 T3000 UPS drivers and 3
• Check if VM tools restoring the configuration
Yes Is it a Virtual No (if applicable) on page 290
operational

Upgrade
AW Server?
• Reinstall VM tools if Note: UPS drivers already
necessary installed.
• Setup UPS parameters

3.8.6 Reload and reinstall the Applications media

Advanced Applications on page 291
• Applications software load from
media
• Applications setup
• Applications activation

3.8.7 Restore the Server configuration and

licenses on page 292

3.8.8 InSite connectivity re-installation on page

297

3.8.9 Integration restoration on page 297

3.8.10 Scalability restoration on page 298

3.8.11 Register System configuration on page

298

3.8.12 Upgrade AW Clients after AW Server

Upgrade on page 298

3.8.13 Final tests and system handover to

customer on page 298
• Final settings & Configuration backup
• System hand-over to customer

AWS System is ready for the customer

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 261

3.4 Scalability Upgrade

3.4 Scalability Upgrade

The following guide intends to summarize the installation steps for an AW Server Cluster upgrade,
instructions that will be detailed all along this manual in the different sections of 3.9 Job Card
UPG002 - Scalability Upgrade on page 300

3.4.1 Adding an AW Server to an existing AW Servers Cluster

You have a cluster of AW Servers and you want to add a new AW Server to the cluster.
See 3.9.1 Adding an AW Server to an existing AW Servers Cluster on page 300.

NOTICE
If the new virtual AW Server to be added to the cluster is NOT hosted on the same
Hypervisor, it is mandatory that the IT Admin also creates a similar GE Service account
on the other Hypervisor, so that the GE FE is able to "administrate" the new virtual AW
Server.(See example below)

NOTICE
In order to ensure proper hardware redundancy, it is strongly recommended that the
two HAPS servers are hosted on different Hypervisor hardware (see after).
Example of a cluster of 3 virtual AW Servers hosted on two different servers hardware

262 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.4 Scalability Upgrade

Upgrade
3.4.2 Removing an AW Server from an AW Servers Cluster
You have a cluster of AW Servers and you want to remove an AW Server from the cluster.
See 3.9.2 Removing an AW Server from an AW Servers Cluster on page 301

3.4.3 Upgrading an AW Server 3.0 Cluster to AW Server 3.2 release

You have a cluster of AW Server 3.0 and you want to upgrade the servers to AW Server 3.2 release.
See 3.9.3 Software Upgrade within a Cluster on page 302

NOTICE
AW Server 3.2 release introduces the Preferences Sharing servers for Scalability. Two
HAPS (High availability Preferences Sharing) servers must be created and added to the
cluster.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 263

3.5 Hardware Upgrade

Figure 3-1 AW Server 3.0 cluster example - before upgrade

Figure 3-2 AW Server 3.0 cluster example - during upgrade

3.4.4 Software Upgrade within an AW Servers Cluster

You have a cluster of AW Server 3.2 and you want to upgrade to a more recent release, the
software of the AW Servers and/or Applications.
See 3.9 Job Card UPG002 - Scalability Upgrade on page 300 - 3.9.3 Software Upgrade within a
Cluster on page 302

3.5 Hardware Upgrade

You have an older AW Server hardware that shall be upgraded.
Currently, hardware upgrades consist of a complete hardware replacement.
See 3.10 Job Card UPG003 - Hardware Upgrade on page 309

3.6 Applications Upgrade

You have Applications that shall be upgraded, or the site has purchased new Applications.
Proceed as shown in the flow chart below, referring to 2.1 Overview on page 7.

264 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.6 Applications Upgrade

Upgrade

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 265

3.7 System Configuration Restore Matrix

3.7 System Configuration Restore Matrix

Prior to software reload or hardware swap, the System configuration should be saved.
(See 3.8.3 Backup the configuration on page 274)
Upon software reload or hardware swap, the System configuration or part of it can be restored.
(See 3.8.7 Restore the Server configuration and licenses on page 292)
The System configuration Restore matrix below addresses the following cases:
1. AW Server 3.2to AW Server 3.2software re-installation or upgrade.
a. All parameters are automatically restored except for passwords.
2. AW Server 3.1to AW Server 3.2software re-installation or upgrade.

266 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.7 System Configuration Restore Matrix

a. Items marked OK are automatically restored.

b. Items marked To be unchecked have to be unchecked in the restore sys config menu
3. AW Server 2.0/ AW Server 3.0 to AW Server 3.2software upgrade.
a. Items marked OK are automatically restored.
b. Items marked Not restored have to be configured manually.
4. Hardware upgrade to new hardware or to Virtual hardware.
a. Items marked OK are automatically restored. 3
b. Items marked Not restored have to be configured manually.

Upgrade
c. Items marked To be unchecked have to be unchecked in the restore sys config menu.

Restoration matrix

Legend Automatically restored - No action needed

Not automatically restored - Configuration needed
Not applicable
To be unchecked in restore menu before restoring.

ITEM SUB-ITEM AWS3.2 AWS3.1 AWS2.0/3. HW upgrade

to to 0 SW to AWS3.2
AWS3.2 AWS3.2 upgrade to new HW /
SW SW AWS3.2 VM
reinstall upgrade
Platform /etc/cups OK N/A N/A N/A

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 267

3.7 System Configuration Restore Matrix

/etc/ntp.conf OK OK OK OK
/var/lib/ServiceTools_AWS/conf OK OK not restored not restored
platformConfig.xml
/export/home/sdc/icm/resources/ OK OK not restored not restored
config/.icmregkey
Nuevo /export/home/sdc/nuevo/resources/ OK OK OK OK
network/network-cfg.xml
/export/home/sdc/nuevo/resources/ OK OK OK OK
browser/sessions.properties
/export/home/sdc/nuevo/resources/ OK OK OK OK
printerManager/printer-cfg.xml
/export/home/sdc/nuevo/resources/system/ OK OK OK OK
auto_delete_preference.properties
Licensing /usr/share/CoLA/Cola_config.txt OK OK OK OK
/usr/share/CoLA/GemsLicense OK OK OK not restored
/usr/share/FL_Server/GemsLicense OK OK OK not restored
/var/lib/ServiceTools_AWS/install/installed/ OK OK not restored not restored
activatedLicenses.txt
EA3 /usr/share/gehc_security/ea3/configs/ OK OK OK OK
/usr/share/gehc_security/ea3/userdb/ OK OK OK OK
EAT /usr/share/gehc_security/eat/configs/ OK OK OK OK
Smart Card /var/lib/ServiceTools/conf/ OK N/A N/A N/A
smartCardAuth.properties
/etc/pki/tls/certs/client_cas OK N/A N/A N/A
ServiceTool /var/lib/ServiceTools/conf/contact-list.xml OK OK OK OK
/var/lib/ServiceTools/conf/device-cfg.xml OK OK OK to be
unchecked
/var/lib/ServiceTools/conf/GIB.xml OK OK OK to be
unchecked
/var/lib/ServiceTools/conf/cmd- OK OK N/A N/A
logging.properties
/var/lib/ServiceTools/conf/rmiserver- OK OK N/A N/A
logging.properties

ITEM SUB-ITEM AWS3.2 AWS3.1 AWS2.0/3. HW upgrade

to to 0 SW to AWS3.2
AWS3.2 AWS3.2 upgrade to new HW /
SW SW AWS3.2 VM
reinstall upgrade
/var/lib/tomcat6/webapps/ServiceTools/ OK OK N/A N/A
WEB-INF/classes/logging.properties
/var/lib/ServiceTools/conf/SNMPConfig.xml OK OK OK OK
/var/lib/ServiceTools/conf/stlanguage.xml OK OK OK OK
/var/lib/ServiceTools/conf/backup-recur- OK N/A N/A N/A
list.xml
/tmp/recurrent_backup OK OK not restored OK
AW Server /export/home/sdc/UserPrefs/ OK OK OK OK
/export/home/sdc/Prefs/ OK OK OK OK

268 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

/export/home/sdc/server/prefs/ OK OK OK OK
AllUser /export/home/sdc/users/ OK OK OK OK
Preference
s
/export/home/sdc/client/prefs/ OK OK OK OK
Insite /tmp/insite_backup.tar.Z OK not not restored not restored
restored
/var/lib/ServiceTools_AWS/iip_conf OK not not restored not restored 3
restored

Upgrade
Software /export/home/sdc/Prefs/swd/ OK OK OK OK
Download
AWS /var/lib/ServiceTools_AWS/conf/cmd- OK OK N/A OK
Service logging.properties
Tools
/var/lib/ServiceTools_AWS/conf/ OK OK N/A OK
rmiserver_aws-logging.properties
/var/lib/tomcat6/webapps/ OK OK N/A OK
ServiceTools_AWS/WEB-INF/classes/
logging.properties
/var/lib/ServiceTools_AWS/conf/ OK OK OK OK
PreprocessingConf.xml
/var/lib/ServiceTools_AWS/conf/ OK OK OK OK
PACSConfig.xml
UPS Config /tmp/upsconfig OK OK OK OK

3.8 Job Card UPG001 - Software Upgrade

Manpower requirement:
One Field Engineer for 5 hours. This time includes the upgrade of one client only.
If the Customer requests additional Clients to be upgraded by GE then FE will bill the GE FMI
account.
This may require additional scheduling and coordination.

NOTICE
The SUN X4450 hardware based AW Server is not supported with AW Server 3.2
release.
Summary of tasks
The GEHC Field Engineer is responsible for the following:
• Section 3.8.1 Upgrade Preparation - One week before the upgrade on page 270: Prior to go to
the site - !!! DO NOT MISS THIS STEP !!!
• Contact IT administrator - Remotely connect to the site and launch the Filesystem Check.
• Contact the IT administrator of the site for any change needed to the current
implementation
• Section 3.8.2 Verify that AW Server is operational on page 272:
• Verify that the AW Server is fully operational before proceeding to the reload/upgrade
• Section 3.8.3 Backup the configuration on page 274:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 269

3.8 Job Card UPG001 - Software Upgrade

• Save the network configuration

• Save the UPS (if applicable to your site) configuration
• Properly disconnect any connected Users prior to do the upgrade
• Backup of the site configuration prior to do the upgrade
• Section 3.8.4 HP ProLiant ML350 G6 Server Hardware Upgrade on page 281:
• 4.1 ML350 G6 server - Memory upgrade to 24GB / 64GB
• 4.2 ML350 G6 server - Hyperthreading setup to OFF
• Section 3.8.5 Software upgrade on page 282:
• 5.1.1 Load the Linux Operating system (Load From Cold)
• 5.1.2 Load the AW Server platform software (Load From Cold)
• Configure Network and Time zone
• 5.2 Reinstall the UPS drivers and configure (if applicable)
• 5.3 Reinstall the VM tools (Virtual AW Server case only)
• Section 3.8.6 Reload and reinstall the Advanced Applications on page 291:
• Section 3.8.7 Restore the Server configuration and licenses on page 292:
• Section 3.8.8 InSite connectivity re-installation on page 297 : Restore / reinstall InSit
e connectivity
• Section 3.8.9 Integration restoration on page 297 Restore / reinstall Integration (if
applicable)
• Section 3.8.10 Scalability restoration on page 298(if applicable).
• Section 3.8.11 Register System configuration on page 298
• Section 3.8.12 Upgrade AW Clients after AW Server Upgrade on page 298
• Section 3.8.13 Final tests and system handover to customer on page 298

3.8.1 Upgrade Preparation - One week before the upgrade

3.8.1.1 Upgrade preparation - Perform Filesystem check

NOTICE
DO NOT MISS THIS STEP
About one week before going to the site, the system must be rebooted and Filesystem check must
be performed. Worst case scenario could be 8 hours for a Filesystem check for a full database.
We recommend scheduling it overnight, starting Friday evening for example.
Note that very long Filesystem check time is not applicable for Full or Seamless integration - The
main Image database is on the PACS - Only a reduced image database remains on the AW Server for
reconstructed images, so the AW Server unavailability during FSCK time is not significant.
1. Launch the Service Tools.
2. Login as service.
3. Select Maintenance tab then Maintenance in the sub menu.
4. Click on Start maintenance button and check if there is any connected Clients.
• If yes, click on Broadcast message to send a message to connected Clients.

270 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

The purpose of this step is to make sure that no clients are connected while performing this
shutdown procedure. You want to make sure they are notified that the system is going to be
shutdown. This could mean contacting them and waiting until they are done.
1. Click on Utilities (AWS2.0) or Tools (AWS3.x) then Terminal in the sub menu.
2. Click on Connect button to open a Terminal window.
3. Login as root.
4. Reboot the server forcing the filesystem check
3
touch /forcefsck <Enter>

Upgrade
reboot <Enter>
Filesystem check can take several hours depending on the number of images stored on the system.
You can monitor the progress on the terminal (KVM) in the server room or with the console
redirection of the iLO. When Welcome to Helios screen displays, press the <Esc> key to view the
progress message.

NOTICE
Do not interrupt the fsck (filesystem check) process. Risk of data loss.

3.8.1.2 Upgrade preparation - Contact the IT Admin of the site

Prior to going on site to perform the FMI tasks, you should ensure proper training as well as contact
the site IT administrator so that they can make the necessary arrangements:
• IT Admin should inform all users of the scheduled FMI date, and that.
• The AW Server will be unavailable for several hours during the upgrade.
• DICOM image transfer from modalities to the AW Server will not be possible during the
upgrade.
• IT Admin should ensure that all Client PC’s (needing to be upgraded to the AW Server 3.2
release or any new PCs to be used) are running the appropriate Windows supported version.
Refer to AW Server 3.2 login page for supported OS’s.
• IT Admin should arrange access to the Server Room if applicable.
• IT Admin should confirm if configuration changes are needed (i.e: IP address change, Default
gateway, etc ...)
• IT Admin should confirm that all image data stored on the AW Server are also stored on
other DICOM hosts such as PACS, in case of damage to the database.
• IT Admin should be prepared to upgrade all clients upon completion of the FMI. The IT
Admin should be aware that the FE will upgrade and validate the AWS Client software only on
one Client PC.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 271

3.8 Job Card UPG001 - Software Upgrade

3.8.1.3 Floating License Server

NOTICE
If AW Server is acting as a Floating License Server for AW Workstations as well, then
the users will lose access to their floating applications during this time. Please plan the
upgrade while considering the impact on all AW standalone Users, not just AW Server
users.

3.8.1.4 Software Changes

The AW Server software may change from the time of this writing. If there is a discrepancy between
this document and the screens you see, use your best judgment to complete this procedure as it
was originally intended.

3.8.1.5 Patients Image data backup

Patient Images data can be preserved during software reload and be reinstalled when software load
is complete.

NOTICE
However, for AW Server 2.0 / AW Server 3.0 upgrade to AW Server 3.2, we strongly
recommend to proceed to Ext3 to Ext4 filesystem upgrade in order to benefit of a
faster filesystem, but consequently, you will have to accept that the image data shall
be deleted. In this case, make sure to get customer agreement prior to proceed to
image deletion.
NOTE
Unless your AW Server 3.1 system is an upgrade from AW Server 2.0 release that was
done without image deletion, it is already running Ext4 filesystem, so images from AW
Server 3.1 can be preserved during upgrade to AW Server 3.2

NOTICE
Make sure that your customer has properly saved the patients image data on another
system (PACS, DVDs) prior to perform the software upgrade.

3.8.2 Verify that AW Server is operational

Verify that the AW Server is operational prior to proceed with the software upgrade.
Sections 3.8.2.1 Check the hardware indicator LEDs (hardware server only) on page 272 and
3.8.2.2 Check the iLO Service processor (hardware server only) on page 273 are not applicable to
virtual AW Servers.

3.8.2.1 Check the hardware indicator LEDs (hardware server only)

These actions shall be performed in the Server room
• Make sure that no errors are reported, both on the server and the disks array (if applicable).
• Check for any yellow LED that would report an error condition.
• Make sure the keyboard, mouse and monitor are connected and operational.
• At the keyboard, login as root.
• Check that the system responds to command lines

272 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

df -k <Enter>

3.8.2.2 Check the iLO Service processor (hardware server only)

These actions shall be performed on the Client PC or FE laptop
• Connect to the HP iLO Service processor
• http://<iLO_IP_address>
• Login as root.
3
NOTICE

Upgrade
If hardware errors are reported by the system, they should be fixed prior to
upgrading the software.

Figure 3-3 Example with the iLO 5 Service Processor (it is similar for iLO 4 and iLO 3)

• Click on System Information tab, and navigate through the Fans, Temperatures, Memory... to
make sure no error conditions are flagged.

3.8.2.3 Connect to the AW server

These actions shall be performed on the Client PC or FE laptop
• Open an Internet Navigator
• Connect to the AW Server IP address
http://<AW server_IP_address>
• Login as service.

3.8.2.3.1 Check the HealthPage

The Healthpage is displayed. Check that no errors are reported in the Healthpage.
Any reported issue should be investigated prior to do the upgrade.
Refer to the AWS Service Manual.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 273

3.8 Job Card UPG001 - Software Upgrade

3.8.2.3.2 Turn auto-delete feature OFF

NOTICE
The auto-delete feature may not have the exact same low mark and high mark limits
between the Gen2 and Gen3 releases. To avoid the risk of unintentionally deleting
images, turn the auto-delete OFF prior to proceed with the upgrade.
• AW Server 1.0: No upgrades from Gen 1 are supported for AW Server 3.2
• AW Server 2.0 and AW Server 3.x:
• The Auto-delete feature can be turned off directly from the Service Tools / Initial
Configuration menu.

3.8.2.3.3 Verify Preferences ownership

Verify the Preferences ownership before performing the AW Server shutdown.
At the FE Laptop or Client PC that is connected by the network to the AW Server.
• Open a Terminal from the Service Tools / Tools (or Utilities - AW Server 2.0) menu.
• Log as root (if not already done).
• Type:
cd /export/home/sdc <Enter> (AW Server 2.0)
OR
cd /var/prefs <Enter>
ls -al users <Enter>
If Preferences do NOT belong to sdc users and sdc group, type the following command line:
chown -R sdc:sdc users <Enter>

3.8.2.4 Important information about Hostnames

If the hostname has been properly chosen for the previous AW Server release, you should not have
to change it for the upgrade, and we recommend that you keep the same.
For hostname characters limitations, refer to A.2 Specific field - Characters rules and limitations on
page 361.

3.8.3 Backup the configuration

274 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

3.8.3.1 Backup the Network configuration

NOTICE
The System configuration backup utility from AW Server Service Tools does not include
the Network parameters. You must SAVE THE NETWORK SETTINGS CONFIGURATION
BY WRITING DOWN THE DATA FOR ONGOING USE. THE NETWORK CONFIGURATION
MUST ALWAYS BE CONFIGURED AFTER AN OS SOFTWARE LOAD AND IS NOT SAVED
BY THE AW SERVER SERVICE TOOLS BACKUP. 3

Upgrade
NOTE
In case of Full, Seamless or DICOM Direct Connect Integration (configuration without the
DAS disks array) or Image Database re-partition, all the backups shall be done on another
system (PACS, Client PC, etc.), as no attached DAS or re-partition means that there is no
built-in"backup" partition on the AW Server.
Before performing the site configuration backup, you must write down: Hostname, IP address, and
AE Title from AW Server HealthPage screen – and also the Subnet Mask by running ifconfig eth0
command line from a terminal window, and the Default Routers by running ip route command line.
From a network connected PC or laptop
1. Display the AW Server HealthPage.
2. Login to Service Tools as service.
3. From AW the Server HealthPage:
a. Write down: Hostname, IP address and AE Title.
• Hostname : ____________________
• IP address : ____________________
• DICOM hostname / AE Title (This is the DNS Hostname):______________________
Figure 3-4 Example of AW Server HealthPage

b. Open a Terminal from the Service Tools / Tools menu, login as root.
• To display the Netmask
i. type:
ifconfig eth0 <Enter>
ii. Write down the Subnet Mask value (Subnet Mask is 255.255.252.0 in example
below).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 275

3.8 Job Card UPG001 - Software Upgrade

• Subnet Mask:___________________
Figure 3-5 Example of ifconfig screen

• To display the Default Gateway:

i. type:
ip route <Enter>
ii. Write down the Default Gateway value (Gateway is 3.249.15.254 in example
below).
• Default Gateway:________________
Figure 3-6 Example of route screen

• To display the DNS servers (if any):

i. type:
cat /etc/resolv.conf <Enter>
ii. Write down the DNS server(s) value (2 servers in example below).
• DNS servers :____________________________________________________
• Domain names :__________________________________________________
Figure 3-7 Example of resolv.conf screen

The Hostname, IP Address, AE Title (DNS Hostname) and Netmask/Network Prefix will be used later
during the software installation process.
Alternatively, all this information can be obtained from the IT department of the hospital.

3.8.3.2 Backup the UPS configuration

The System configuration backup utility from AW Server Service Tools does not include the UPS
parameters. If applicable to your site, backup the UPS configuration.

3.8.3.2.1 Backup the HP UPS setup

• Stop the HPPP service:
service HP-HPPP stop <Enter>

276 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

• Connect to the Service Tools as service.

• Launch the File Transfer utility from the Utilities menu.
• Select From system tab:

Upgrade
• Scroll down and lick to move to usr directory, then click to move to local directory, then to HP
directory, then to PowerProtector directory.
• Move to configs directory and transfer the configuration files to the Client PC or FE laptop, by
clicking on Pull from system button.
• Acknowledge the popup message mentioning the file size to be transferred, and choose the
location on your PC where to save the file.
• When done, move back to PowerProtector, then move to db directory and transfer the
configuration files to the Client PC or FE laptop.
• Restart the HPPP service:
service HP-HPPP start <Enter>

3.8.3.2.2 Backup the customer’s UPS setup

In case your DL580 is connected to a customer’s UPS (DL580 installed in a servers bay of the site)
and the IT administrator of the site has provided drivers and configuration settings for this UPS, you
should backup the configuration as specified for your site / UPS.

3.8.3.3 Backup the Site configuration

In this section, we will select the Maintenance mode, send a Broadcast message to any connected
User in order to let them know that the server is about to be shutdown, then place the AW server
under maintenance mode, backup the site configuration and finally shutdown the AW server.
NOTE
The System configuration backup also embeds backup of the User Preferences.
First, make sure you are still logged as "service" (see section 3.8.2.3 Connect to the AW server on
page 273)

3.8.3.3.1 Enter the Maintenance mode

Select the Maintenance mode under the Maintenance menu:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 277

3.8 Job Card UPG001 - Software Upgrade

The Maintenance menu window opens:

NOTE
Refer to A.4 Maintenance Mode on page 369 Send a broadcast message
Warn the connected user that you are going to shutdown the system and that they will be
disconnected. Allow a few minutes grace delay so that they can save their work before you
disconnect them.
• Select the Broadcast message tab
• Post a message warning the Users that the server will be shutdown in 15 minutes, for example,
and that they should save their work before exiting.
• Type in your message in the text field and click on Set message
NOTE
For AW servers in cluster, you may also indicate in the shutdown message that
users can reconnect a few minutes later, and that they will be automatically re-
directed to another server.

3.8.3.3.2 Start the Maintenance Mode

• Click now on Start Maintenance tab.
• Allow the 15 minutes warning delay and start maintenance by clicking on the Start
Maintenance button

278 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

• The users will be disconnected.

3.8.3.3.3 Backup the site configuration

• On physical AW servers with an Image disks array, the backup partition is on the image disks
array, so it is normally not affected by the software Load From Cold.
• However for AW Server 2.0 or AW Server 3.0 upgrades, if the customer allows deletion of the
existing images, you will choose to upgrade the filesystem from Ext3 to Ext4 for better
performances, and consequently, both the Image partition and the Backup partition will be 3
deleted then recreated.

Upgrade
• On physical AW server without DAS (image disk array) - HP DL580 high tier, there is no separate
backup partition as there is no external disk array.
• For Full, Seamless or DICOM Direct Connect Integration, the backup must be made on the Client
PC and/or FE laptop, as there is no external disks array (DAS), and reloading the software (OS +
AWS) deletes all files on the system hard disk.

NOTICE
In all cases, it is strongly recommended to proceed to a double backup, in
order to save the configuration, both on the AW Server by selecting Save on
System (if applicable), and to a remote location (Client PC and/or FE laptop) by
selecting Pull from system. You can also copy it to an external media such as
USB key for extra security.
• Click on Backup arrow, to expand the menu and select System configuration tab.
The Backup system configuration menu displays:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 279

3.8 Job Card UPG001 - Software Upgrade

• Check the “Select as last known good configuration” radio button.

• Proceed with a double backup:
• Click Pull from system - This will allow saving the configuration on a USB key, via the
Client PC or FE laptop. Follow the instructions on the screen
• Click Save on System - This will allow saving the configuration on a dedicated "backup"
space on the Server hard disks, which is not erased by the SW load process, unless upgrade
from Ext3 to Ext4 filesystem is chosen.

3.8.3.4 Backup the PACS Integration configuration

Bypass this step if your AW Server is not integrated.
The integration mode will not be automatically restored after the software load process. However,
there is a "Prefill" utility that can be used. In any case, it is highly recommended to manually backup
the Integration configuration parameters.
Refer to 2.19 Job Card IST011 - Integration on page 172 and write down the following information
that you will need to reinstall the Integration configuration:
I.e: For Seamless integration
• Integration mode : Seamless Integration

280 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

• Connector plugin : Dakota Client Library plugin

• License key : license key for Seamless Integration
• Source : http://<IP address of Universal_Viewer_server>/services/PacsWebService
• Preprocessing user: It is an Universal Viewer user (in our example, we use the default
"AWPreProc" user).
• Institute Name: Your site information displayed here.

3.8.3.5 Backup the existing exams status configuration 3

Upgrade
Bypass this step if your AW Server is fully integrated (Full, Seamless or DICOM Direct Connect
Integration).
If the customer requires that part (or all) of the existing patient data is preserved and reinstalled
after the upgrade, take a snapshot of the Patients List before proceeding to the upgrade, in order to
note which of the exams are locked and/or what is their Post-treatment status.
The database implementation may discard the 'auxiliary tags' or 'meta-data' during a database
recover so any configuration done prior to database recovery is lost.
1. Exit from the Maintenance mode.
2. Launch the AW Server Client (login as service).
3. Page through the Patients List and write down or make a snapshot of the processed / protected
exams.
• They are flagged with a status symbol and/or a locker symbol.
• You may need to reset the status and/or re-lock them manually once the upgrade has been
done.

3.8.3.6 Backup the End of Review configuration

For AW Server 2.0 / AW Server 3.1 upgrades to AW Server 3.2 release, it is strongly recommended
not to restore the ServerPreferences.xml file to avoid potential issue with the Viewer, and this file
contains the End of Review configuration. Therefore, backup the EOR configuration as follows:
• Under Administrative / Configuration menu, click on End Of Review sub-menu and write
down the configuration that you will re-create after the software has been upgraded.

3.8.4 HP ProLiant ML350 G6 Server Hardware Upgrade

NOTE
The HPE ProLiant DL580 G7 Server is not impacted by these changes. Jump to
3.8.5 Software upgrade on page 282

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 281

3.8 Job Card UPG001 - Software Upgrade

Prior to perform the software upgrade steps to AW Server 3.2 release, it is necessary to proceed to
the following upgrade steps for the HP ProLiant ML350 G6 Server. Refer to the AW Server 3.2
Hardware Installation Manual 5719442-1EN for detailed upgrade steps.
Preliminary steps
Shutdown the AW Server referring to instructions given in the previous release of the AW Server
Installation Manual, or to this manual at A.9 Useful Commands and Tools on page 419 (Using the
Terminal tool and command lines).

3.8.4.1 Upgrade memory to 24GB (or 64GB)

The HP ProLiant ML350 G6 Server can be upgraded to the AW Server 3.2 release, but needs the
memory to be upgraded from 12GB to 24GB at minimum (or 64GB), in order to meet the
performance requirements.
• Locate the 24GB memory upgrade kit (6 x 4GBytes DIMM modules) or the 64GB kit (8 x 8GB
DIMM modules - Starting Q2 2016), that has been delivered, part of the Upgrade Order.
The upgrade consists on swapping the existing 6 x 2GBytes DIMM modules by the 6 x 4GBytes (or 8 x
8GBytes) modules delivered within the upgrade kit.
• Perform steps described in AW Server 3.2 Hardware Installation Manual 5719442-1EN,
Appendix A.6, in order to replace the basic 6 x 2GB (12GB) memory modules by the 6 x 4GB
(24GB) or the 8 x 8GB (64GB) memory modules of the upgrade kit.
• Store the older 6 x 2GB memory modules that you have removed in a safe place.

NOTICE
DO NOT install both the 6 x 4GB (or 8 x 8GB) modules and the older 6 x 2GB
modules in the HP ProLiant ML350 G6 Server.This configuration has not been
validated.

3.8.4.2 BIOS Hyperthreading setup to OFF

The HP ProLiant ML350 G6 Server can be upgraded to the AW Server 3.1 release, but need the
BIOS Hyperthreading parameter to be set to OFF, in order to meet the performance requirements.
• Power up or reboot the server.
• Perform steps described in AW Server 3.2 Hardware Installation Manual 5719442-1EN,
Appendix A.4 in order to enter the BIOS and setup the Hyperthreading parameter to OFF.
• Take profit that you are in the BIOS to check that the serial number corresponds to the serial
number of the chassis, and to make sure the BIOS date and time is accurate. Refer to other
sections of the AW Server 3.2 Hardware Installation Manual 5719442-1EN, Appendix A.4.
Once done with the BIOS setup the server will reboot.
Be prepared to insert the OS DVD into the DVD drive, as described hereafter in next Section.

3.8.5 Software upgrade

Prepare the media that you will use for loading the server with the new version.
Refer to the Software Kit content in section 1.3 Software Kit on page 4.
NOTE
For the AW Server integrated within the CT/MR Console Environment (Edison HealthLink
or CT Nano-Cloud), refer to A.12 AW Server Integration in CT/MR Console Environment on
page 433.

282 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

NOTE
When installing from electronic files, always refer to AW eDelivery Service Guide
5761599-8EN for detailed instructions.
NOTE
The Advanced Applications are no longer included in the AW Server Platform software
DVD media. They must be loaded from their own media.

3.8.5.1 OS loading 3
3.8.5.1.1 Physical AW Server

Upgrade
The steps are done at the Server side. Alternatively, software loading can also be done at the Client
PC, through the iLO service processor. Refer to A.7 Software Loading Through iLO on page 410.
At time of release of this manual, the OS media is as follows:
• 5720621 (or up) - HELiOS OS for AW Server DVD
1. Power up the system:
After a while, the screen unblanks and displays the HP ProLiant logo. Next the boot up messages
are displayed. It takes some time for the system to initialize. Please be patient.
2. Insert the HELiOS OS DVD into the DVD drive (or insert the USB device if applicable).
3. Reboot the AW server:
At the KVM, or at the Client PC when loading through the iLO, login as root.
Type:
reboot <Enter>
The server reboots. After a while, the screen unblanks and displays the HP ProLiant logo,
followed by other boot up messages.

NOTICE
If hardware security has been activated on this hardware, the system will directly
attempt to boot from the hard disk. Therefore you should first press on the <F11>
key when prompted, to enter the boot device selection. You will be prompted to
enter the BIOS Administrator password (if you have setup one) for the server
hardware security (see AW Server 3.2 Hardware Installation Manual
5719442-1EN , Appendix A.4 and Appendix A.9) to gain access to the boot menu.
It will take a few moments before you get to the boot selection menu screen. Please be patient.
When done, select One time boot to CD-ROM or USB.
NOTE
If you lost the BIOS Administrator password, refer to AW Server 3.2 Advanced Service
Manual 5771771-1EN, Chapter 9, Appendix A.24.
4. HELiOS menu displays:
The message Attempting to boot from CD-ROM will display, followed after a moment by
the Welcome to HELiOS menu screen:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 283

3.8 Job Card UPG001 - Software Upgrade

Use the <Up arrow> and <Down arrow> keys to select Install AW Server 3.2 (VS7) and
press <Enter>.
NOTE
If you do not select anything, within about 10 seconds, it would result to boot from
the local drive. In this case cycle power to the AW Server in order to reboot, and
select Install AW Server 3.2 (VS7).
5. Lots of messages display followed by the installation start screen:

6. Then the packages installation will start:

It takes about 10 to 15 minutes to install the packages.

7. When that is done, system starts rebooting.
The server will initialize, then the HELiOS menu will display. After a few seconds, the system will
automatically boot up from the hard disks.
When the boot up sequence has completed you will be prompted to login and enter the login
password.
8. Eject the OS DVD (if applicable) and store it in a safe place.

284 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

Operating System (OS) load is complete.

9. Insert the AWS platform DVD or insert the USB media containing the AWS Platform software.
Go to section 3.8.5.2 AWS Platform software loading on page 290.

3.8.5.1.2 Virtual AW Server

The steps are done at the Client PC.
At time of release of this manual, the OS media is as follows:
3
• 5720635 (or up) - HELIOS OS DVD for VM, to be used for virtual servers re-installation only.

Upgrade
NOTE
The steps are described for VMware hypervisor (ESXi) with VMware vSphere Web
Client. To have the equivalent steps using VMware vSphere Client, refer to Appendix
A.6 VMware Support on page 378. And if needed, refer to VMware documentation for
more details.
1. Preliminary step for upgrade from AW Server 3.0 release ONLY:
The Guest Operating System information must be changed in vSphere / Virtual Machine
Propertiesfrom SUSE Linux Enterpriseto Red Hat Enterprise Linux 6 (64-bit) prior to proceed to
OS upgrade.
• Make sure that the AW Server 3.0 VM is powered off, or power it off.
• Open a Web browser and enter the URL or IP address of the ESXi URL.
• Login with the GE Service account created by the IT Admin (service).
• In the Virtual Machines panel, select the VM.
• Select Edit. The screen below opens.
• Select the VM Options tab. Select General Options line.
• In Guest OS, click on the drop-down list.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 285

3.8 Job Card UPG001 - Software Upgrade

• The current value should be SUSE Linux Enterprise 11 (64-bit)

Select Red Hat Enterprise Linux 6 (64-bit).
• Select Save to apply the new setting.
2. Insert the OS DVD into Client PC DVD drive.
For OS re-installation on Virtual AW server, be sure to use the right OS: 5720635(or up) -
HELIOS OS for AW Server DVD for VM -

NOTICE
DO NOT USE: 5720625 (or up) - HELIOS OS OVFTpl-e-vAW which is for initial
installation as it creates the virtual machine at the same time than it loads the OS.
3. Display the Virtual Machine Console and start the virtual machine:
• Click on the Console screen shot (here the white arrow if the Virtual Machine is not already
started).
The virtual AW Server OS starts booting up (if not already started) and the Virtual Machine
Console opens.

286 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

NOTE
Once the virtual machine is started, you can also display the Virtual Machine
Console by clicking on Console > Open browser console or directly on the
Console screen shot.
NOTE
To work with the Virtual Machine Console, simply click into the console field.
If the screen is black or locked press <Ctrl> .
To display the boot sequence while booting press <Ctrl> and <-> 3
simultaneously.

Upgrade
4. Map the iso file to the virtual CD/DVD drive:

• Select your Virtual Machine, then click on the icon.

The Edit settings screen displays.

• In the Virtual Hardware tab select CD/DVD Drive 1 (or the corresponding name for your
VM) from the list.
• If not already selected, select Datastore ISO file from the dropdown list. Otherwise, click
on the Browse button.
• In the screen that displays:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 287

3.8 Job Card UPG001 - Software Upgrade

• If the iso file is not already uploaded:

• Select the datastore where you want to copy the iso file and click on Upload.
• Locate the iso file and select it, then select Open.
• Once uploaded, select the iso file and click on Select button.
• In the Edit settings screen check the Connect at power on and the Connect radio buttons.
• Click on Save button.
The virtual CD/DVD drive of the Virtual Machine is now mapped to the iso file.
5. Reboot the AW server:
Log into the Console as root.
Type:
reboot <Enter>

NOTICE
IMPORTANT - To force boot from the CD rather than from the Hard Disk, when
proceeding to software Load from Cold, at the start of the boot sequence, quickly
press "Esc" when the VMware logo briefly displays at the Console. This will launch
the boot menu, from were you can choose to boot from "CD-Rom Drive" and select
"Connect to ISO image on local disk".
6. HELiOS menu displays:
The message Attempting to boot from CD-ROM will display, followed after a moment by
the Welcome to HELiOS menu screen:

288 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

Upgrade
Use the <Up arrow> and <Down arrow> keys to select Install AW Server 3.2 (VS7) and
press <Enter>.
NOTE
If you do not select anything, within about 10 seconds, it would result to boot from
the local drive. In this case cycle power to the AW Server in order to reboot, and
select Install AW Server 3.2 (VS7).
7. Lots of messages display followed by the installation start screen:

8. Then the packages installation will start:

It takes about 10 to 15 minutes to install the packages.

9. When that is done, the system starts rebooting.
The server will initialize, then the HELIOS menu will display. After a few seconds, the system will
automatically boot up from the hard disks.
When the boot up sequence has completed you will be prompted to login and enter the login
password.
10. Eject the OS DVD (if applicable) and store it in a safe place.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 289

3.8 Job Card UPG001 - Software Upgrade

Operating System (OS) load is complete.

11. Insert the AWS platform DVD or insert the USB media containing the AWS Platform software.
12. Disconnect the iso file from the CD/DVD virtual drive:

• Select the Virtual Machine, then click on the icon.

The Edit settings screen displays.
• In the Virtual Hardware tab, in front of CD/DVD Drive 1 (or the corresponding name for
your VM) uncheck the Connect radio button.
• Click on the Save button.
• The following message displays:

"The guest operating system has locked the CD-ROM door..."

Select the Yes check box then click on the Answer button.
• Go to section 3.8.5.2 AWS Platform software loading on page 290.

3.8.5.2 AWS Platform software loading

Proceed with the AWS platform loading steps described at chapter 2, 2.10 Job Card IST003 -
Installation of Platform Software on page 67.
You will be prompted to choose between preserving the existing images (and potentially remaining
in Ext3 filesystem type: AW Server 2.0 / 3.0 case), or allowing deletion of the existing images and
upgrading to Ext4 filesystem (faster type).
When done, continue with the following steps

3.8.5.3 Loading the HPE R/T3000 UPS drivers and restoring the configuration
(if applicable)
The HPE R/T3000 UPS utility driver is part of the AWS Platform software, and is automatically loaded
and installed when loading the AWS software from media.
The following steps are normally performed by connecting to the server locally, from the server KVM.
If you remotely connect from another computer, disable the server’s PNF firewall before connecting.
NOTE
Customer’s owned UPS configuration case: If applicable for your site, restore the
customer’s UPS configuration as specified by the IT administrator of the site.
1. Open a terminal window from the Tools > Terminal menu option and login as root.
2. Disable the firewall:
service pnf off <Enter>
3. Check that the HPE R/T3000 UPS driver has been properly installed on the system as described
in HPE R/T3000 UPS drivers installation verification:
4. If you did NOT modify the default HPE R/T3000 UPS configuration:
Proceed with 2.11.2 Configuring the HPE R/T3000 UPS using HPPP Software on page 82, to
reconfigure the HPE R/T3000 UPS auto-shutdown parameters.
5. If you have modified the default HPE R/T3000 UPS configuration (I.e: you changed the default
10mn delay time before shutdown to any other value), restore the configuration from the HPE R/
T3000 UPS backup file:
a. Restore the HPE R/T3000 UPS configuration (if applicable):

290 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

• service HP-HPPP stop <Enter>

cp /export/backup/ups/config.js /usr/local/HP/PowerProtector/
configs <Enter>
cp /export/backup/ups/mc2.db /usr/local/HP/PowerProtector/db
<Enter>
• Or use the File Transfer tool if you have saved the configuration on Client PC or FE
laptop (Load From Cold case). Select the To system tab to transfer the configs.js
and the mc2.db files to the configs and db directories as shown above. 3
service HP-HPPP start <Enter>

Upgrade
b. To test the shutdown utility and make sure it is operational, refer to Step 14 in
2.11.2 Configuring the HPE R/T3000 UPS using HPPP Software on page 82.
6. Enable the firewall back:
iptables -F <Enter>
service pnf on <Enter>

3.8.5.4 Reinstall the VMware Tools

VMware tools are for Virtual AW server only. Bypass this step for Physical AW servers.
1. Check that the VMWare tools are still available.
• Click on the Virtual Machine in vSphere client or vSphere Web Client.
• In the virtual machine characteristic's summary panel check the VMware tools status.
2. If VMWare tools are not available,
reinstall the VMware tools. Refer to Chapter 2, 2.12 Job Card IST004B - Installation of VMware
Tools on page 86 for instructions.
When reinstalling, VMware Tools considers reinstallation as an upgrade and may display the
following popup message.

• If available select Automatic Tools Upgrade or (Automatic Upgrade). In this case the
VMware Tools will automatically install/upgrade and you can skip the manual VMware Tools
install/upgrade in 2.12 Job Card IST004B - Installation of VMware Tools on page 86.
• Click OK to accept.
NOTE
If there is no popup message the VMware Tools will be upgraded automatically.

3.8.6 Reload and reinstall the Advanced Applications

The Applications currently supported by the AW Server 3.2 release are:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 291

3.8 Job Card UPG001 - Software Upgrade

3.8.6.1 Information about Volume Viewer Applications

See 2.17.8 Applications Profile on page 147 for the list of supported Volume Viewer Applications.

3.8.6.2 Information about other Applications

See 2.17.8 Applications Profile on page 147 for the list and version of the other supported
Applications.
Refer to the dedicated documentation of the Applications for details.
For SW upgrade to AW Server 3.2 release, the other applications are delivered through the
Applications Refresher DVD Collector as:
• 5720641 (or up) : AWS SW Apps refresh – DVD 1 – CT Apps for AW Server 3.2
• CardIQ Xpress Process
• GSI Viewer
• Smartscore
• Advantage 4D
• Advantage SIM MD
• 5720642 (or up): AWS SW Apps refresh – DVD 2 – PET Apps for AW Server 3.2
• CortexID Suite

3.8.6.3 Applications re-installation process

NOTE
When installing from electronic files, always refer to 5761599-8EN: AW eDelivery
Service Guide for detailed instructions.
After a Load From Cold, the Applications purchased by the site shall be reloaded and reinstalled from
their media DVD/USB media or from the Applications Refresher DVD Collector.
Perform the steps described in 2.17 Job Card IST009 - External Application(s) Installation on page
132, but bypass 2.17.1 Foreword on page 132 to 2.17.3 Application(s) Licensing setup on page 134,
and 2.17.7 Activate the Application(s) on page 146 as the system configuration has not been
restored yet.
NOTE
Bypass CardIQ Xpress Process (CXP) reinstallation, as the Pre-requisite for CardIQ Xpress
Process installation are that Volume Viewer, CardIQ Xpress Reveal and Pre-processing are
installed and licensed. This is not the case yet.CXP license must also be set before
installing the CXP package.

3.8.7 Restore the Server configuration and licenses

3.8.7.1 Preliminary steps before restoration

1. Applications reinstallation

NOTICE
Make sure all Applications purchased by the site have been reloaded prior to
restore the configuration. Perform steps described in 3.8.6 Reload and reinstall the
Advanced Applications on page 291 of this Job Card.

292 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

• CardIQ Xpress Process (CXP) application shall be reloaded later, after all CXP install pre-
requisites are complete and the licenses have been restored. See section 3.8.7.4 CardIQ
Xpress Process (CXP) application reinstallation on page 296
2. Seamless Integration plugin reinstallation

NOTICE
Prior to restore the configuration, if your system is in Seamless Integration with
the Universal Viewer, it is necessary to reload the latest Dakota plugin. 3
• Refer to section 2.19.3.4 Seamless integration - configuration steps on AWS, Service Tools

Upgrade
on page 184
3. User passwords restoration

NOTICE
It is not possible to restore the User passwords from AWS2.0 / AWS3.0 to AW
Server 3.2 The algorithm used for /etc/shadow file is different between SuSE OS
and HELIOS OS.
• If you have previously changed the system user passwords (e.g. sdc, root, insite) for your site,
they will not be restored (upgrade case) and therefore you will have to change them again

3.8.7.2 Restoration steps

Restore now the system configuration files and user preference files.
This is done through the Restore tool in the Maintenance menu. This is one of the server
maintenance activities locked into the Maintenance Mode – to ensure corruption-free configuration
files – and CAN BE PERFORMED ONLY IN MAINTENANCE MODE
1. • If not done yet, select Maintenance in the Maintenance Menu, and initiate the
Maintenance mode – refer and follow the information about Maintenance Mode in the
preceding sections of this document. Refer to A.4 Maintenance Mode on page 369for more
information on Maintenance mode.
You will know that you are in the Maintenance Mode by the RED indication at the top of the
service tools interface Maintenance is in progress, and the Restore tools page will display.
2. • Click on Maintenance/ Restore to expand the menu then click on System Configuration.
NOTE
If you click on the Restore link - without first initiating the Maintenance Mode - the
“Restore configuration or preferences” interface will only display a Refresh button.
Click Refresh and a message in RED letters will display– The system is not in
maintenance mode operation is not permitted
3. • Select the Source for restoring. Use either the configuration file saved on the "/export/
backup" partition (source = System) then select the file to upload,
OR
• Use the configuration file you saved on your USB key or the Client PC (source = Upload),
click on Upload configuration button, then on the popup window that displays, click on
the Browse button, choose the file to upload and click on Send to system button.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 293

3.8 Job Card UPG001 - Software Upgrade

• If several configurations are stored on the "/export/backup" partition of the server, or on

your USB key, select the latest one if more recent and valid, or the "Last known good"
configuration if you have previously selected it as reference backup.
• If the name of a backup file has been changed from the original name (I.e:
"AWSBackupSyst_xxxxx"), the Upload configuration will appear to be successful, but the file
will then not be available to Select for restore.
Same issue may for "UserPreferences" restore if backup file has been renamed.
4. • In the example above, the "candidate for restore" configuration file is:
/export/backup/system/AWSBackupSyst_20140226-130554.tar.gz
• Select the configuration to restore, then click on Restore Selected button
5. The backup feature of AWS2.0 or AWS3.0 did not store the License ID. The restore feature of AW
Server 3.2is now doing a check on the License ID.
Therefore, when upgrading from a previous AWS2.0 or AWS3.0 release to AW Server 3.2, you will
get the following warning message:

• Click on OK button to accept. (Click on Cancel if you do not want to restore the licenses).
NOTE
If the license ID stored on the backup file is different from the License ID of the
system you are reinstalling, the licenses will not be restored.
6. Parameters not restored
• Passwords: All passwords are restored to the default value.

294 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

• Certain items cannot be restored due to incompatibility between the AWS2.0 / AWS3.0
platform and the AW Server 3.2platform. Therefore you will get the following message to let
you know that these items will not be restored.

Upgrade
• Click on OK button to accept.
• Click again on Restore Selected button
A progress indication will display next to the “Restore selected” button, and then a GREEN
successful indication if the restore was successful.
• The backup feature of AW Server 2.0 or AW Server 3.0 did not store the Hospital name
and the backup recurrence parameters. Therefore they cannot be restored and shall be re-
entered manually.
• InSite parameters from AWS2.0, AWS3.0 or AWS3.1 are not restored, as the Model type is
different.. InSite will have to be reinstalled via the InSiteCheckout process.

Another message may display at the end of the restore process, to let you know that the
Integration configuration (if applicable) will not been restored:
"The integration mode stored in the backup (seamless_integ) has not been restored. Please
configure it manually."
However, there is a "Prefill" utility allowing to populate the Integration fields with data that was
saved, as part of the backup process. See next step.
7. Platform configuration:
The Platform configuration has been restored, but needs to be applied to be effective.
• Click on Initial Configuration/Platform Configuration, check that the Platform license
key displays, click Next to Scalability and check that the cluster mode is selected and
HAPS server IP’s are entered (if applicable), then click on Next, and use the Prefill button to
populate Integration parameters (if applicable). Finally click on the Apply button.
Integration is addressed by 3.8.9 Integration restoration on page 297.
Scalability is addressed by 3.8.10 Scalability restoration on page 298 and 3.9.3 Software
Upgrade within a Cluster on page 302.
8. Database Deletion Settings
• Finally, make sure "Database Deletion Settings" have been properly restored, or proceed to
setup (if applicable).
Refer to chapter 2, 2.16 Job Card IST008 - Initial Configuration on page 108
Informational step

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 295

3.8 Job Card UPG001 - Software Upgrade

If the restoration takes much longer time and ends up with the message below, you may have
done a mismatch between the network parameters you have entered through the tool, and
those that you have just restored.

DO NOT reboot your system at this time !!!!

• Follow the steps "Repair the mismatched hostnames" described below.
• Logout from the service tools session or quit the Internet Navigator
• Launch a new Internet navigator if necessary and http://to the AW Server IP address
• Launch a new Service tools session and login as service.
The system should still be in Maintenance Mode. If not, start the Maintenance mode.
• Go to Maintenance tab
• Start the Maintenance mode (if not done)
• Go to Network sub-menu
• Click on the Hostname tab
• Modify the hostname so it reflects the DNS/Hostname (also AE Title) that your AW Server
had before the upgrade.
• Click on Apply button.
The system will reboot

3.8.7.3 Licenses restoration

Refer to Chapter 2, 2.17 Job Card IST009 - External Application(s) Installation on page 132 in order to
check that Applications licensing is properly restored.

1.) □ 2.17.3 Application(s) Licensing setup on page 134- Install / license the Application(s)
AW Server 2.0 release upgrade: As it was not necessary to run the Volume Viewer basic application
on AWS2.0, there was no license key for it. Therefore the Volume Viewer key cannot not be restored.
• The Installation of the Volume Viewer key is a prerequisite for running the VV Apps on AW Server
3.2. This license key must have been delivered to you with the upgrade. If not, contact your Sales
department.
2.) □ 2.17.7 Activate the Application(s) on page 146 - Activate the Application(s)

NOTICE
In case of upgrade from AWS2.0 / AWS3.0 release, this step is very important, since
Applications are not activated by default, and if not activated, they would not be
available on the Client.

3.) □ Then check that Pre-processing has been properly restored referring to 2.18.7 Preprocessing
Configuration on page 165

3.8.7.4 CardIQ Xpress Process (CXP) application reinstallation

It is possible to reinstall now from its own media or from the hard disk (if available), the CXP
application, as the VV Apps have been reloaded and the license have been restored.

296 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

3.8.7.5 Internal Applications restoration

AW server software has some internal application: They are part of the AWS platform software and
most of them will be restored part of the Backup/Restore process.
Verify that they have been properly restored.
• Prodiag - (Not applicable for Seamless integration) - Refer to chapter 2, 2.16 Job Card IST008 -
Initial Configuration on page 108
• SNMP traps - Refer to chapter 2, 2.16 Job Card IST008 - Initial Configuration on page 108
3
• End Of Review - Check that EOR has been properly restored or recreate it if it has not been

Upgrade
restored. Refer to chapter 2, 2.18 Job Card IST010 - Administrative Configuration on page 148
for details.

3.8.7.6 Passwords restoration

• Upon upgrade, passwords have been reset to the default values. Re-entered the passwords
changed for your site (if applicable). Refer to 2.14 Job Card IST006 - Changing the Passwords on
page 93

3.8.8 InSite connectivity re-installation

If applicable for your site, you shall reinstall the InSite connectivity.
• Upon upgrade, passwords have been reset to the default values. Make sure you have re-entered
the passwords changed for your site (if applicable) prior to proceed with the InSite checkout.
• Perform the steps described in chapter 2 2.16.2 Remote Service on page 109

NOTICE
The AW Server 3.2 InSite Model Type is _AWS32
• InSite connectivity can be restored for AWS3.2 to AWS3.2 later release upgrade.
• InSite connectivity cannot be restored for AWS 2.0 or AWS3.1 upgrade, as the AWS2.0
model type is _AWE2and AWS3.1 model type is _AWS31. In this case, proceed with a new
Checkout with the Checkout team using model type _AWS32.
NOTE
InSite is not supported for EDS system (Seamless integration).

3.8.9 Integration restoration

If applicable for your site, you shall restore the Integration configuration.

NOTICE
PACS integration is NOT restored automatically, part of the Backup/Restore process.
You must reinstall it manually.
Perform the steps described Chapter 2 2.19 Job Card IST011 - Integration on page 172, using the
"Prefill" utility:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 297

3.8 Job Card UPG001 - Software Upgrade

• Make sure the plugin has been reloaded first (Seamless integration).
• Click on the Prefill button to pre-populate the fields with the parameters

3.8.10 Scalability restoration

If applicable for your site, you shall restore the Scalability configuration.
• Perform the steps described in Chapter 2 2.20 Job Card IST012 - Virtual Servers Cluster
Configuration on page 196

3.8.11 Register System configuration

You shall now register the System configuration, in order to obtain the Activation key to unlock the
AW Server. Perform the steps described in Chapter 2 2.21 Job Card IST013 - Service Tools
Configuration on page 200 section 2.

NOTICE
Repeat this procedure after any intervention that changes the server’s configuration,
for instance when installing a new application or after an upgrade.
Ensure you exit the Maintenance mode after System Registration.

3.8.12 Upgrade AW Clients after AW Server Upgrade

In case of a simple software re-installation of AW Server, the Client re-installation/upgrade is not
required. In case of an upgrade of AW Server, the Client upgrade is required.
• To upgrade the "Standard" AW Server client, perform the sections of chapter 2, 2.22 Job Card
IST014A - Standard Client PC installation & Tests on page 204.
Standard stands for Standalone (no-integration) or any other modes of integration than the
Seamless integration.
• To upgrade the "Seamless" AW Server client, perform the sections of chapter 2, 2.23 Job Card
IST014B - Seamless Client PC installation and Tests on page 226.
The first step consists on reconfiguring the Universal Viewer Server and the second step consists on
upgrading a Client PC. Note that for seamless integration, the Universal Viewer Server must be
reconfigured (see step 1 of the section / Job card referenced above).

3.8.13 Final tests and system handover to customer

3.8.13.1 Final settings and System handover to customer

• Perform the steps described in Chapter 2, 2.24 Job Card IST015 - Final Settings on page 240

298 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.8 Job Card UPG001 - Software Upgrade

• Perform the steps described in Chapter 2, 2.25 Job Card IST016 - System Handover to Customer
on page 246.

NOTICE
If the AW Server you are upgrading has a large amount of patient data, image re-
installation (database recovery) may not be complete before giving back the
system to the user.Warn the user that all patient data may not be available
yet, and that they shall preferably use the system for processing new exams, or be
careful if they have to process existing exams. 3

Upgrade
3.8.13.2 GIB / SIEBEL update and paperwork
Send the customer’s Global Installed Base data to GEHC. Send all paperwork from the installation to
the appropriate recipient (i.e., GEHC or the customer).
Global Installed Base database may be directly updated using the following link:
EGIB @ http://gib.gehealthcare.com
• GEHC Global Install Base database web site is available from any outside web enabled PC.
• The FE can enter the model/serial into the Service Tools interface and send the GIB data up to
GIB via email. So, make sure to fill-in all the information in the service tools Initial Configuration
> Device Data & User Data.

NOTICE
USCAN System ID / Assets are no longer found in eGib and are now located in the
CRM Siebel / Assets database.

• "Installs: Follow MyWorkshop document DOC1701877, Job Card IB Verification

• "Upgrades: Follow MyWorkshop document DOC1618060, Job Card FE Upgrade
Instructions
• "Asset Swaps: Follow MyWorkshop document DOC1589267 Job Card FE Asset Swap
NOTE
EDS System remains on GIB until further notice.

NOTICE
Repeat this procedure after any intervention that changes the server’s
configuration, for instance installing a new application.

3.8.13.3 Secure Media Destruction procedure

When you install software upgrades on a system, it is a Best Practice to destroy the installation
media corresponding to previously installed versions. This reduces the risk that obsolete versions
(which may contain software with safety or other issues) could be re-installed.
• Delete any corresponding ISO files that you may have stored on your GE laptop or other storage
devices.
• Use the Version Management tool to Remove any old package from the Server.
• Retain installation media only for currently installed versions of software.
• Properly dispose of older installation media by destroying the media.
• If you need to reinstall an old version of software (perform a downgrade) at a later date on any
given system you should re-order an up to date installation kit.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 299

3.9 Job Card UPG002 - Scalability Upgrade

3.9 Job Card UPG002 - Scalability Upgrade

3.9.1 Adding an AW Server to an existing AW Servers Cluster

You have a cluster of AW Servers and you want to add a new AW Server to the cluster.
Figure 3-8 Example of a cluster of 2 virtual AW Servers - Adding a new AW server.

It is possible to add a new AW Server node to an existing Cluster, in order to extend the number of
concurrent users managed by the cluster. The new AW Server node can be installed on a new
Hypervisor or on a Hypervisor that already hosts AW Server nodes.
The new node is installed by following the same steps as for the initial cluster installation. The only
difference is that there is only one virtual AW Server to install.
To install a node, follow the workflow described in Section 2.4.3 Quick Start Installation Guide -
Scalable Virtual servers on page 18.
To summarize the installation steps:
• The IT Admin has to perform 2.7 Job Card IST001B - Virtual Machine creation on page 44 to
create the VM.
• The GEHC FE has to perform 2.9 Job Card IST002B - Virtual Machine Installation Verification on
page 63 to 2.21 Job Card IST013 - Service Tools Configuration on page 200, to setup the virtual
AW Server.
NOTE
When cluster mode is activated on the new Virtual Machine, it will be automatically
added to the existing cluster of AW Servers, provided that the network configuration
is correct, i.e. the second network card of the Virtual Machine is connected to the
AWS private network, and it is part of the same network subnet.

300 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.9 Job Card UPG002 - Scalability Upgrade

3.9.2 Removing an AW Server from an AW Servers Cluster

You have a cluster of AW Servers and you have to remove one AW Server from the cluster.
Figure 3-9 Example of a cluster of 3 virtual AW Servers - Removing an AW Server node

Upgrade
Node removal procedure:
1. Launch an Internet navigator and connect to the URL of the AW Server you want to disconnect:
I.e: http://3.24.45.12.
2. Start the Service and Administrative Tools interface:
a. Click on the Launch button.
b. Login as service.
3. Enter the Maintenance mode: Click on the Maintenance menu then select Maintenance.
4. NOTICE
DO NOT forget to broadcast a message to the users, prior to disconnect them.
Refer to A.4 Maintenance Mode on page 369, for details on the Maintenance
mode.
Click on the Broadcast Message tab, type in a message and click on the Set message button
to let the users know they are going to be disconnected.
Allow a grace delay of a few minutes to let them save their work and exit.
5. Click on the Start Maintenance tab. Click on the Start Maintenance button to place the
server into maintenance and disconnect the users.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 301

3.9 Job Card UPG002 - Scalability Upgrade

NOTE
Only the users currently connected to the AW Server that is being removed will be
disconnected. When they attempt to reconnect, they will be automatically redirected
to one of the other AW Servers of the Cluster.
6. From the Service Tools / Initial Configuration menu, click on Scalability.
The Manage and display scalability setting interface will display.
7. Shutdown the AW Server.
8. Launch an Internet navigator and connect to the URL of one of the other AW Servers of the
cluster: I.e: http://3.24.45.11.
9. Start the Service and Administrative Tools interface, and login as service.
10. From the Service Tools / Initial Configuration menu, click on Scalability.
11. Click on the radio button of the AW Server node to be removed, then click on the Delete
selected nodes button.

12. Acknowledge the confirmation screen. Click on OK.

The AW Server node is removed from the cluster.

3.9.3 Software Upgrade within a Cluster

The following procedures are high level procedure, and refer to procedures already detailed in
different sections of this manual.

3.9.3.1 Pre-requisite for AW Server 3.0 upgrade case

NOTICE
There is an important change for Preferences Sharing management brought by the AW
Server 3.2 release. It is mandatory to add two HAPS (High Availability Preference
Sharing) nodes to the cluster, prior to upgrade the AWS3.0 nodes to AWS3.2 nodes.

Figure 3-10 AW Server 3.0 cluster example - before upgrade

302 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.9 Job Card UPG002 - Scalability Upgrade

Figure 3-11 AW Server 3.0 cluster example - during upgrade

Upgrade
• Refer to 2.8 Job Card IST001C - Virtual Servers Cluster Installation Steps on page 56 to create
the HAPS virtual machine.
• Refer to 2.10 Job Card IST003 - Installation of Platform Software on page 67 to create the HAPS
server.
• Refer to 2.12 Job Card IST004B - Installation of VMware Tools on page 86 to install the graceful
shutdown utility.

3.9.3.2 AW Server 3.0 High Level Upgrade Procedure

NOTICE
Prior to Software upgrade from AW Server 3.0 release case.
Make sure you have created/configured two new virtual machines for the HAPS (High Availability
Preferences Sharing) servers. See 3.9.3.1 Pre-requisite for AW Server 3.0 upgrade case on page 302.
Three examples of high level upgrade are described in the following sections.

3.9.3.2.1 Cluster of 2 Virtual AW Servers

You have a cluster of 2 AW Servers and you want to upgrade the software of the AW Servers and/or
the Applications.
1. Place the AW Server 1 into Maintenance:
a. Enter the Maintenance mode.
b. Click on the Maintenance menu then select Maintenance.
NOTE
Refer to A.4 Maintenance Mode on page 369 for more details on the
Maintenance mode.
c. Click on the Broadcast Message tab, type in a message and click on the Set message
button to let the users know they are going to be disconnected.
Allow a grace delay of a few minutes to let them save their work and exit. Also write at
what time they can reconnect, and they will be automatically re-directed to the next Server.
See example message below:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 303

3.9 Job Card UPG002 - Scalability Upgrade

d. Click on the Start Maintenance tab.

e. Click on the Start Maintenance button to place the Server into maintenance and
disconnect the users.
NOTE
Only the users currently connected to the AW Server that is being shutdown will
be disconnected. When they reconnect, they will be redirected automatically to
one of the other AW Servers of the Cluster. The IT admin of the site may want to
warn the users of slightly degraded performances of the cluster, setting a
Broadcast message from the operational AW Server.
2. Choose one of the following case:
• If you want to upgrade applications only, refer to 2.1 Overview on page 7, 2.17 Job Card
IST009 - External Application(s) Installation on page 132 for the applications upgrade
procedure, then continue this procedure at Step 8.
• If you want to upgrade AWS platform, proceed to next steps. Refer to 3.8 Job Card UPG001
- Software Upgrade on page 269.
3. If you want a full software upgrade (Load From Cold - OS + AWS platform SW), first, save (write
down) the Network parameters.
4. Save the Site configuration - See section 3.8.3.3 Backup the Site configuration on page 277 for
details.
5. If you load from cold, reload the OS from the DVD for AW Server for VM - To be used for virtual
Servers reinstallation.
See section 3.8.5.1.2 Virtual AW Server on page 285 for details.

NOTICE
DO NOT USE the OS OVF Template for virtual AW which is for initial installation
and creates at the same time the virtual machine.
6. If you want to load from cold, re-enter all network parameters.
7. Reload the AWS platform SW from the AW Server SW & Docs DVD for VM - To be used for virtual
Servers.
See section 3.8.5.2 AWS Platform software loading on page 290 for details.
8. Reload the Applications from their respective media or upgraded Applications from the new
media you have received.
See section 3.8.6 Reload and reinstall the Advanced Applications on page 291 for details.
9. Reload the PACS integration plugin. Refer to section 2.19 Job Card IST011 - Integration on page
172 for details.
10. Restore the System configuration except for AllUserPreferences. Uncheck the
AllUserPreferences checkbox before restoring.

304 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.9 Job Card UPG002 - Scalability Upgrade

See section 3.8.7 Restore the Server configuration and licenses on page 292 for details on
restore process.
11. Restore the Platform configuration, the Scalability configuration and the Integration
configuration. Use the Prefill button to reload the Integration parameters.
See section 3.8.7 Restore the Server configuration and licenses on page 292 for details on
restore process.
12. When done with the Platform Configuration restoration, you will have to restore the User
Preferences, as they now must be stored on the HAPS Servers. Restore the User Preferences 3
only.

Upgrade
13. Register the System configuration for the upgraded AW Server, and obtain a new Activation key,
to exit the Maintenance mode.
See section 3.8.11 Register System configuration on page 298 for details.
14. If it is an AW Server platform SW upgrade, the Client must be upgraded too. Proceed with one
Client upgrade.
See section 3.8.12 Upgrade AW Clients after AW Server Upgrade on page 298 for details.
Note that this step would not be necessary if simply reloading the same SW release.
15. Shutdown the AW Server 1 and do not restart it yet!
16. When you are done with the upgrade of the AW Server 1, place the AW Server 2 in Maintenance
(refer to Step 1).
17. Restart the AW Server 1. Make sure it is operational and that the integration mode is
operational.
18. Set the Scalability mode on.
19. If AW Server platform SW upgrade, warn the IT admin of the site to proceed to the other Clients
upgrade.
20. Proceed with the AW Server 2 upgrade, referring to previous steps, make sure Applications have
been upgraded too (if applicable), that the PACS plugin has been reinstalled (if applicable), then
put the Server back in the cluster when fully operational.

NOTICE
In the above and below mentioned cases, you shall register the new System
configuration for each AW Server, and obtain a new Activation key, to exit the
Maintenance mode.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 305

3.9 Job Card UPG002 - Scalability Upgrade

3.9.3.2.2 Cluster of 3 Virtual AW Servers

You have a cluster of 3 AW Servers and you want to upgrade the software of the AW Servers and/or
Applications.
The challenge is to keep 2 of the 3 AW Servers available as much as possible while doing the
upgrade.
Referring to 3.9.3.2.1 Cluster of 2 Virtual AW Servers on page 303, proceed with the following high
level sequence.
1. Place the AW Server 1 in Maintenance mode.
2. Upgrade the AW Server 1.
3. Restore the configuration and put the AW Server 1 back in operation.
NOTE
As the AW Server 1 does not have yet the Golden set, it will not be accessible to the
users yet.
4. Place the AW Server 2 in Maintenance mode.
5. Upgrade the AW Server 2.
6. Restore the configuration and put AW Server 2 back in operation.
The AW Server 1 and AW Server 2 are now upgraded to the new version. They are ready to
takeover and AW Server 3 can be disconnected now.
7. Place the AW Server 3 in Maintenance mode.
All Clients will be disconnected for a while, time to set the Golden set on the newly upgraded
AW Server 1 and AW Server 2.
8. Set the Golden set for AW Server 1 or AW Server 2.
Now the AW Server 1 and AW Server 2 are taking over. Clients can reconnect.
9. Upgrade the AW Server 3.
10. Restore the configuration, set the Golden set and put the AW Server 3 back in operation.

3.9.3.2.3 Cluster of 4 Virtual AW Servers

You have a cluster of 4 AW Servers and you want to upgrade the software of the AW Servers and/or
Applications. Referring to 3.9.3.2.1 Cluster of 2 Virtual AW Servers on page 303, proceed with the
following high level sequence.
1. Place the AW Server 1 in Maintenance mode.
2. Upgrade the AW Server 1.
3. Restore the configuration and put the AW Server 1 back in operation.
NOTE
As the AW Server 1 does not have yet the Golden set, it will not be accessible to the
users yet.
4. Place the AW Server 2 in Maintenance mode.
5. Upgrade the AW Server 2.
6. Restore the configuration and put AW Server 2 back in operation.
AW Server 1 and AW Server 2 are now upgraded to the new version. They are ready to take over
and AW Server 3 can be disconnected now.

306 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.9 Job Card UPG002 - Scalability Upgrade

7. Place the AW Server 3 and AW Server 4 in Maintenance mode.

All Clients will be disconnected for a while, time to set the Golden set on the newly upgraded
AW Server 1 and AW Server 2.
8. Set the Golden set for the AW Server 1 or AW Server 2.
Now the AW Server 1 and AW Server 2 are taking over. Clients can reconnect.
9. Upgrade the AW Server 3 and AW Server 4.
10. Restore the configuration, set the Golden set and put the AW Server 3 and AW Server 4 back in 3
operation.

Upgrade
3.9.3.3 AW Server 3.2 High Level Upgrade Procedure
When upgrading a cluster of AW Server 3.2 to the latest release, it is necessary to upgrade each AW
server within the cluster, as well of upgrading the two HAPS (High Availability Preference) servers.

3.9.3.3.1 Upgrade case 1

The customer agrees that all the AW Servers within the cluster will be unavailable to the users, and
can be placed in maintenance mode during the time necessary to upgrade the AW Servers and the
HAPS servers.
1. Backup the system configuration:
a. Place all AW Servers in Maintenance mode.
b. Proceed to the upgrade of the system configuration (including preferences) for each AW
Server.
2. Upgrade the HAPS servers:
a. Proceed to the upgrade of the OS and AWS platform software for the two HAPS VMs. DO
NOT use the OVF Template media for OS upgrade, but use the OS for VM media. Refer to
2.10 Job Card IST003 - Installation of Platform Software on page 67 to load the AWS / HAPS
platform software.
b. Select HA Filesystem server.
3. Upgrade the AW servers:
a. Proceed to the upgrade of the OS, AWS platform software, and Applications for each of the
AW Server VMs and install the Dakota client for Seamless integration.
b. DO NOT use the OVF Template media for OS upgrade, but use the OS for VM media. Refer to
2.10 Job Card IST003 - Installation of Platform Software on page 67 to load the AWS / HAPS
platform software. Select AW server.
c. Restore the configuration (including Preferences) for each AW Server.
d. Setup the Golden Set.
e. Register the configuration for all servers then quit the maintenance mode.
4. Upgrade the AW server Clients: Proceed to the upgrade of the AW Server Client software.

3.9.3.3.2 Upgrade case 2

NOTICE
This procedure requires that two new HAPS servers are created, so that the
Preferences can be copied to those new servers. When done, the old HAPS
servers will be deleted.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 307

3.9 Job Card UPG002 - Scalability Upgrade

The customer request that as many AW Servers as possible are left up and running as long as
possible, during the whole time necessary to upgrade the AW Servers and the HAPS servers.
Example: Cluster of 3 virtual AW Servers
Below is the example of a 3 nodes cluster AW Server 3.2 with 2 HAPS nodes, to be upgraded to the
latest AW Server 3.2 release.
1. Create two new HAPS servers:
a. Ask the IT administrator of the site to create two new virtual machines from the new OVF
Template OS in order to host the two new HAPS servers.
For these new HAPS servers, two new IP addresses on the Hospital network are needed (IT
Admin responsibility), as well as two IP addresses on the AWS Private network matching
the current IP addresses of the AW Servers (GEHC responsibility).
NOTE
In order to achieve high availability of the Preferences, the two HAPS servers
shall preferably be hosted on two different Hypervisors. Refer to 2.7 Job Card
IST001B - Virtual Machine creation on page 44 for VM creation instructions.
b. When done with the VM creation, proceed to steps described in 2.10 Job Card IST003 -
Installation of Platform Software on page 67 to load the AWS / HAPS platform software.
c. Select HA Filesystem server.
2. Upgrade the AW Server 1:
a. Shutdown the AW Server 1.
b. Install new OS release (do not use the OVF template, but use the new OS for VM), the new
AWS release, the up to date Dakota client (for Seamless integration), and applications and
the licenses.
c. Configure the server in cluster mode.
d. Connect to the new HAPS nodes.
The AW Server 1 is out of the cluster, the AW Server 2 and AW Server 3 are still in the cluster
and can be used by the radiologists.
3. Upgrade the AW Server 2:
a. Inform users to save all new preferences.
b. Create a preferences backup.
c. Shutdown the AW Server 2.
d. Install the new OS, AWS version, Dakota client (for Seamless integration), applications and
licenses (keep backup partition or save backup file to any removable media).
e. Configure the server in cluster mode.
f. Connect to new HAPS nodes.
g. Restore the preferences backup on the AW Server 2.
h. Verify that all preferences were restored properly.
After the installation of the AW Server 2, only the AW Server 3 is available to the users.
4. Finish the maintenance of the AW Server 1 and AW Server 2, and set a new Golden set to one of
these AW Server.
As the Golden set is selected, the AW Server 1 and AW Server 2 become available to the users.
Users on the AW Server 3 are warned to save their work, exit then log in again.

308 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.10 Job Card UPG003 - Hardware Upgrade

NOTE
Users shall upgrade AWS client before the new login.
5. Upgrade the AW Server 3:
a. Shutdown the AW Server 3.
b. Install the new OS, AWS version, Dakota client (for Seamless integration), applications and
licenses.
c. Configure the server in cluster mode.
3
d. Connect to new HAPS nodes.

Upgrade
After the installation of the AW Server 3, the whole cluster is up and running.
6. Shut down the old AWS 3.2 HAPS nodes and delete them.
7. Notify the IT admin of the site that the IP addresses of the old HAPS servers are no longer
needed.
8. Upgrade the AWS Clients.
9. Notify the IT admin of the site to make sure that all the AWS Clients have been upgraded to the
new AWS 3.2 release.

3.10 Job Card UPG003 - Hardware Upgrade

3.10.1 Foreword
This section outlines the various steps necessary to upgrade an older AW Server hardware to the
latest AW Server hardware. The hardware upgrade offerings currently consist on a complete
hardware swap.
The upgrade steps are summarized hereafter:
• Install your new AWS system following instructions given at 2.1 Overview on page 7.
Preferably use the IP address of the old AW Server for the new server (you will not have to
change the settings on the other DICOM hosts), making sure that the old server is disconnected
from the network or that you have changed its IP address to a temporary one, if you need to
transfer image data from old to new server.
• Contact your On-Line Support so that the licenses available on the old AW Server are
transferred (adapted) to the License ID of the new AW Server.
• Perform a quick check on the old hardware
• Save the system configuration of the old hardware
• Check with the customer IT admin if the patient data is already stored on another system (PACS
for instance) and can be deleted from the older system.
• Optional step: If patient data shall be transferred to the new hardware:
• Warn the IT admin that this operation may take several hours depending on the number of
images/patients data to be transferred.
• Check with IT admin how much patient data shall be reinstalled, and how much data can be
deleted in order to save time.
• Ask the IT admin for a temporary IP address to be used for the older AW server, time to
transfer the patient data.
• Make sure clients are no longer connected on the older AW server

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 309

3.10 Job Card UPG003 - Hardware Upgrade

• Change the IP address of the older server to the temporary IP address.

• Proceed with image data transfer from older AW server to new AW Server
• Declare the images/patients into the new AW server database.
• When done, proceed with image data deletion of the older AW server
• Proceed with disassembly and packaging of the older server, using the packaging of the new
server
• Proceed with old server shipment to recycling center

3.10.2 Old hardware checks

• Proceed with old hardware checks referring to 3.8.2 Verify that AW Server is operational on page
272.

3.10.3 Old hardware configuration backup

• Login to the Service Tools interface and select Maintenance / Maintenance
• Enter the Maintenance mode referring to 3.8.3 Backup the configuration on page 274.
• Proceed with old hardware configuration backup referring to 3.8.3 Backup the configuration on
page 274.

3.10.4 New hardware installation - High level steps

New AWS hardware or new AWS Virtual hardware installation must be complete prior to perform
the following steps, and it is necessary that the minimum configuration steps have been completed.
Make sure the new hardware or Virtual hardware installation and minimum necessary configuration
are complete, referring to instructions given at chapter 2 and summarized hereafter:
Install the AW Server 3.2hardware server or AW Server 3.2Virtual server
1. Configure the Network parameters
2. Configure Date & Time parameters
3. Load the Applications from media (Virtual AW Server case)
4. Restore the old AWS2.0 hardware configuration to the new AWS3.2 hardware except for:
• GIB - Uncheck box in Restore Config menu
• Device Data - Uncheck box in Restore Config menu
• Other non-applicable parameters such as licenses are automatically not restored.
(See next section for details)
5. Configure the rest of the new AW Server 3.2parameters
• Licenses
• GIB
• Device Data
• Remote access (inSite)
• Registration Key
6. Upgrade the AWS Client
7. Proceed to final settings and system handover to customer.

310 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.10 Job Card UPG003 - Hardware Upgrade

3.10.5 System Configuration restoration

You may now want to restore some items of the old AW Server System configuration such as remote
hosts to the new AW Server.
However not all of the configuration can be restored.
Make sure to un-check at least the Nuevo, Licensing and InSite check boxes that are specific to the
old server, before restoring the old to new AW Server configuration.
3
Refer to 3.8.7 Restore the Server configuration and licenses on page 292 for details on the restore
process.

Upgrade
3.10.6 Patient data transfer
The currently stored image data can be transferred from the old hardware to the virtual AW Server, if
that is requested by the customer. Warn the customer that this process may take a long time
depending on the number of images to be transferred.

NOTICE
When image transfer is requested by the user, in order to save time (I.e: High Tier
server image filesystem size is 4TB to 6TB), and limit the impact on the new AW Server
(I.e: Virtual AW Server max disk size is 6TB), a choice should be made in advance by the
customer on what image data must be kept and what image data can be erased.
• Make sure with the customer or IT Admin about what image data can be erased.
• Proceed with all possible image data deletion, prior to transfer image data from old hardware
server to new AW server. The currently supported maximum disk size for AW Server (physical or
virtual) image filesystem is 6TB.

NOTICE
The following should NOT be considered as a standard procedure, as the time
necessary to transfer the images may greatly affect the installation / upgrade
time.Make sure this extra time has been planned in the overall installation time.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 311

3.10 Job Card UPG003 - Hardware Upgrade

3.10.6.1 Check with customer what images can be deleted and proceed to
deletion
If it is possible to delete some of the patient data contained into the AW Server database, because
this data is already saved in the PACS, or still contained into the Image source database, it will save
transfer time and then re-installation time.
To delete images at the old AW server, proceed as follows:
• Login to the old AW Server Service Tools interface and select Administrative / Utilities /
Image Database
• Select patient exams candidate for deletion
• Click on Delete selected button, and acknowledge the confirmation message:

3.10.6.2 De-activation of Auto-delete on the old AW Server

• From the Service Tools Initial Configuration / Auto-delete, de-activate Auto Delete (if
applicable).
• Click on Apply to save.

When done with image deletion and de-activation of Auto-delete, proceed with IP address change
so that the old server and new server can be placed on the same network.

3.10.6.3 Change the IP address of the older AW server

1. You will use the old server IP address for the new AW server

312 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.10 Job Card UPG003 - Hardware Upgrade

2. You will give a temporary IP address (in the same sub-network) to the old server .

NOTICE
If the new AW server is not in the same sub-network as the old server, you cannot
give the old server IP address to the new server. Keep the IP addresses as they are,
then you will declare the IP address of the new server to the DICOM hosts on your
network, to ensure the DICOM transfers.
1. Login to the Service Tools interface and select Maintenance / Maintenance 3
2. Enter the Maintenance mode (if not done yet) referring to 3.8.3 Backup the configuration on

Upgrade
page 274.
3. Click on Maintenance / Network

4. Click on IP address, Default gateway tab

5. Change the IP address to the temporary address.

6. Click on Apply and accept the reboot of the server.

7. When the old server has rebooted, make sure it is visible (can be ping’ed) on the network with
its new temporary address.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 313

3.10 Job Card UPG003 - Hardware Upgrade

3.10.6.4 Prepare the old AW Server for image transfer

The following shall be done at the OLD AW Server.
• Open a Terminal tool on the old AW Server from the Service Tools interface
• Log as root.
• De-activate the Firewall on the old AW Server. In the Terminal, type:
service pnf off <Enter>
• Enable ssh - In the Terminal, type:
ssh_enabler <Enter>

3.10.6.5 Image transfer from old to new AW Server

The following shall be done at the NEW AW Server.
• Open the KVM or open a Terminal tool from the Service Tools interface.
• Log as root.
• Switch user to "sdc"
su - sdc <Enter>
• Launch the image transfer script
/usr/share/ServiceTools_AWS/scripts/db_transfer/pull_images <IP_address_old_server>
<Enter>
I.e: /usr/share/ServiceTools_AWS/scripts/db_transfer/pull_images 3.249.12.68 <Enter>
Lots of output will display such as:
Could not open a connection to your authentication agent.
#########################################
Check dirs and files having been defined in a setVriables file on the local host
SCRIPTONREMOTE=/usr/share/ServiceTools_AWS/scripts/db_transfer/runOnRemoteSite.sh
...................................................
Check the system AWS or AW AWS
#########################################
Remote RUN script originality check
.............................................
Remote host ping test
Host is OK
#########################################
Remote host port (22) check
Connection to 3.249.12.68 22 port [tcp/ssh] succeeded!
Port (22) is OK (open)
#########################################
Prepare the automatic log in
Check the .ssh dir
#########################################

314 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.10 Job Card UPG003 - Hardware Upgrade

..........................................................................
#########################################
Log in to Remote host
Could not open a connection to your authentication agent.

WARNING

Permanently added '3.249.12.68' (RSA) to the list of known hosts. 3

Upgrade
[email protected]'s password:
• Enter the OLD SERVER root password and press <Enter>
More output will display such as:
#########################################
Check the remote directory (/export/home1/sdc_image_pool/images/)
#########################################
Calculating required and available spaces ...
#########################################
Run rsync
[==============================================================================
]
100%#########################################
NOTE
Time necessary to complete the transfer images (100%) will depend on the number of
images to be transferred and the speed of Network at your site.
Set back.sh files on remote host
#########################################
Set back the .ssh files on local host
#########################################
Then images are declared (installed) on the new AW Server
Declare images on the host
/export/home/sdc/nuevo/bin/dbExpressInstall
Using log name = default, logging to /export/home/sdc/nuevo/logfiles/terra.log
Using log name = /export/home/sdc/logfiles/db_transfer.log, logging to /export/home/sdc/logfiles/
db_transfer.log
Amount of disk space to be reserved: 311715956
The configuration file is ::/export/home/sdc/terra/resources/terra.cfg
ER_EVENT_TIMEDOUT is :: 0
NOTE
If some errors occur while declaring the images (most of the time when the image is
already stored on the new server - demo images for example), you will get the following
kind of message:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 315

3.10 Job Card UPG003 - Hardware Upgrade

Installing ... One or more file could not be declared !!! Please check the logfile: /export/home/sdc/
logfiles/db_transfer.log. Declaration has been done with ERROR
• Check what exams were not properly transferred and warn the IT admin of the site, so that they
can check the reason in case some exams were not properly copied, and make sure they could
solve the issue before you erase the exam(s) from the old server.
You can also check the/export/home/sdc/logfiles/db_transfer.log logfile for errors, then check
the corresponding exam(s) integrity as shown in next section.
• After having analyzed the db_transfer.log logfile, delete it in order to save disk space:
rm /export/home/sdc/logfiles/db_transfer.log <Enter>

3.10.6.6 Check installation of images on the new AW Server

• Login to the new AW Server Service Tools interface and select Administrative / Utilities / Image
Database
• Check that all exams have been properly re-installed in the new AW Server.
• Select / highlight each Patient name and check that the number of series is consistent
• Select highlight each Series and check that the number of Images is consistent.

3.10.6.7 Final steps on the new AW Server

NOTICE
When transferring image data from the old to new AW Server, "locked" exams may
have been reset to "unlocked".Warn the customer / IT Admin that they will have to
reset the "lock" on those exams, through the AW Server Client UI.

316 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.10 Job Card UPG003 - Hardware Upgrade

3.10.6.8 Final steps on the old AW Server - Delete Patient data

NOTICE
NEVER SEND BACK an old system containing Patient data.Systematically proceed
to complete patient data deletion on the old AW Server, and "wipe out" hard disks
before returning hardware to the recycling center.
Before proceeding with file deletion of your old hardware, make sure that you have saved all 3
necessary files to install the new hardware. Also make sure that the customers have saved their own

Upgrade
files.

NOTICE
The procedure can take a long time, depending on the number of images stored on the
image disks.
NOTE
The below procedures are the responsibility of GEHC for the physical AW servers.For
virtual AW Server, it is the Customer’s responsibility to perform the wiping of their
hypervisor Storage media.
To be compliant, you must use one of the following tools to perform a complete secure wiping of
Customer System Storage media:
• Blancco Drive Eraser
This is the recommended tool as it does not rely on tool shipment/availability and does not
require disassembly and removal of hard drives from equipment.
This is a 3rd party disk erasure software that may be downloaded from a secure GE shared
storage location at any time by authorized personnel. Technicians will be able to create local
boot images for secure wipes of the imaging equipment as needed.
After inserting in the workstation the bootable media (DVD/USB) containing the software, the
workstation will boot on it and the Blancco software will allow you to erase all the disks.
• Disk management Tool
You must order it from the Service Tools Pool, then remove the disks from the workstation and
connect them to the Disk Management Tool to erase them.
Follow instructions given in the 5500610-1EN - Disk Management Tool Service Manual delivered
within the kit.
• Refer to Service Note SNAW3037 - Secure Wipes of Customer System Storage Media
(DOC1615300) for the detailed procedure to erase patient data.
OR
• If any of the above tool are available, use the procedure described hereafter:
1. Insert the new AW Server 3.2 OS DVD into the old server’s DVD drive.
2. Reboot the old AW server
3. When the DVD's boot menu displays, arrow down to select the option: Rescue installed
system.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 317

3.10 Job Card UPG003 - Hardware Upgrade

Boot messages display, then a few screens will pop up:

4. Page through the rescue options to launch a command shell:
• Choose Language: >>> select English
• Keyboard type: >>> select US
• Setup Networking: >>> select No at the question "Do you want to start the Network
interfaces ..."
• Rescue: >>>>> tab to select Skip at the messages "The rescue environment will now ....."
• Shell: Start shell >>> tab to select OK
You will now get access to the system via the Command prompt
5. SUN or HP server: Type the following commands:
ls /dev/sd* <Enter>
Normally, if all disks are present and still functional, you will see the partitions /dev/sda,
and /dev/sdb which correspond to the system partition and the images partition. Note that you
will also see the sub-partitions of sda and sdb such as sda1, sda2, sda3, sdb1, sdb2.
parted /dev/sda print <Enter>
parted /dev/sdb print <Enter>
• Then type in:
dd if=dev/zero of=/dev/sda & <Enter>
dd if=dev/zero of=/dev/sdb & <Enter>
• Wait for at least 20 minutes, then ensure that the partitions are no more readable
parted /dev/sda print <Enter> shall indicate that the disk label is not recognized
parted /dev/sdb print <Enter> shall indicate that the disk label is not recognized
6. Eject the OS DVD
7. Halt the server
halt <Enter>

318 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 3.10 Job Card UPG003 - Hardware Upgrade

8. Power off the server

When the System is "halted", power off the server.

3.10.7 Old hardware return procedure

Old hardware equipment shall be returned to the GEHC Recycling Centers.
Ask your Support Center for the appropriate procedure for your region.
Use the shipping boxes of your new hardware to pack the parts you are returning. 3
Refer to Chapter 5, A.11 Hardware Return Procedure on page 430 for instructions

Upgrade

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 319

Page intentionally left blank
 4
Chapter 4 Service Tasks

4.1 Overview
This chapter contains the following Service procedures:
4.2 Job Card SV001 - Preventive Maintenance (PM) on page 321
4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list on page 327
4.4 Job Card SV003 - Service Procedures on page 333
4.5 Job Card SV004 - Renewal of Digital Certificate on page 357

4.2 Job Card SV001 - Preventive Maintenance (PM)

The server hardware does not have a PM requirement from the Vendor.
However, the server hardware has several fail-over components that are configured to allow the
server to keep functioning if one of them should fail.
Both the server and direct attached storage have redundant power supplies, and disk drive RAID
configurations that allow operation should one of the drives fail. The server also has multiple fans
and temperature sensors that can alert service to a failure before it becomes critical.
The software on the server has several ways in which it detects these components and sensors.
GEHC is not currently able to systemically monitor the sensors to provide pro-active alerts.
In order to take advantage of the fail-over capabilities of the product, and potentially resolve failure
issues before they cause the server to be down – it is advisable to periodically check the software
sensors on the product. If any faults are observed, requests for service should be through the GEHC
service request process.
Preventive Maintenance is necessary to pro-actively detect software related issues, such as
expiration of digital certificate, limited free disk space...
Preventive maintenance applies to both physical and virtual AW Servers.

4.2.1 Recommended PM Schedule

Recommended PM is as follows:
• High Tier servers hardware is under Vendor responsibility for maintenance
• If the system is remotely accessible: 1 remote PM per year - HealthPage and sensors
checks - unless specific monitoring is in place (See Note)
• If the system is not remotely accessible: 1 local PM per year.
• However, when making a site visit, check for disk errors and check the Healthpage.
• Low Tier servers hardware is under GEHC responsibility
• If the system is remotely accessible: 1 local PM + 1 remote PM per year - HealthPage and
sensors checks
• If the system is not remotely accessible: 1 local PM per year - Dust cleaning (does not
apply to the "rack-mount" servers) and cables checks

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 321

4.2 Job Card SV001 - Preventive Maintenance (PM)

• Virtual server:
• If the system is remotely accessible: 1 remote PM per year. As there is no Hardware, this
PM will consist in software PM tasks only.
• If the system is not remotely accessible: 1 local PM per year. As there is no Hardware, this
PM will consist in software PM tasks only.
NOTE
EDS does not require PM for systems monitored via SNMP Trap Receiver / OnWatch.
NOTE
The frequency of PMs could be changed later if too frequent or not frequent enough.

4.2.2 PM Access
• Remotely via the InSite connection (or EDS equivalent remote access).
• Locally via the server keyboard – display – mouse.
• Locally for dust cleaning of the air vents (as often as possible - once a year during the Preventive
maintenance of the Image source (CT, MR, etc...) mainly for the HP Low Tier server.

4.2.3 PM Time
• The PM should be scheduled for no more than 1 hour (1/2 hour typical).

4.2.4 PM Tasks
The main purpose of Preventive Maintenance is to check the software sensors - primarily for any
hardware faults, but also for software errors.
NOTE
Some of the elements in the HealthPage Server Configuration Table are STATUS
indicators – like the DICOM Queue Status – and while they might merit attention, they
are not hardware or system failures requiring separate service dispatch creation.
Investigate them as PM analysis actions, and only create service follow-up dispatches if
the investigation leads to discovery of a system fault condition.

4.2.4.1 PM Software Tasks

Login to the AW Server Service Tools to perform software preventive maintenance tasks.
The PM Software tasks shall be done for all AW Servers, both physical and virtual.
All Software tasks can be done remotely as well as on site.

4.2.4.1.1 Check Version Management

If the Service Tools notified you that new software packages are available, go to "Maintenance" >
"Version Management" menu and install or refuse available updates.

4.2.4.1.2 Check the Healthpage

These tests are NON- INVASIVE, and can be performed at anytime. However, corrective action may
require a RESTART, REBOOT, or entering Maintenance Mode – which will be invasive to clinical
use.

322 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.2 Job Card SV001 - Preventive Maintenance (PM)

NOTICE
Before performing a shutdown or reboot, refer to Chapter 5, A.4 Maintenance Mode on
page 369 for details of important precautions to take.
Remotely connect to the AW Server and examine the Healthpage. Check the following items in the
HealthPage:
• Hardware status OR Virtual Machine status displays no error.
• System configuration displays no error.
• Disk space does not display in RED.
• Image Partition Mount Count (and Date) should not display in Yellow. In the other case, you shall
4
warn the IT Admin of the site that Filesystem check shall be launched in the coming week.

Service Tasks
• Certificate expiration date show no error. In the other case, it is needed to renew the certificate.
• Software Subsystem displays no error.
• Software Subsystems essential for Service Tools displays no error.
• If any faults are observed – a separate service dispatch should be created.
• If the issue is hardware related (High Tier servers case), this will include engaging the Vendor
Hardware Break / Fix process through GEHC.
• If there is a software fault, examine the corresponding error log(s) to discover the root cause, or
next step in the analysis.
• Pay attention to the Server Configuration portion of the HealthPage for any inconsistencies with
product norms - e.g. Memory (DIMM RAM) and Total Disk Space.
• Also check the "Mount Count status", as well as the "Next filesystem check after" date, and warn
the IT Admin if any of these figures are close to the launching of the Filesystem check routine, so
that the site can schedule the manual launching of the filesystem check.
Refer to Appendix A.15 of the Advanced Service Manual for details.
Note: Mount Count and filesystem check can be ignored in case of seamless integration.
• In Software Subsystem section, check that Firewall (pnf) service has the status "OK". If not, you
must turn it On and make sure that the connectivity to the AW Server is maintained (Insite,
remote connected hosts).

4.2.4.1.3 Check ClamAV AntiVirus status

If the ClamAV package is configured, check that no infected file has been detected in the scan logs,
located in /export/home/sdc/logfiles.
Refer to Section A.5.2.2 Checking ClamAV Scan Results on page 377.

4.2.4.1.4 Password change

Ensure that the default password have been changed to customized passwords.
Otherwise, follow instructions to change the passwords. Inform all stakeholders of password
changes.
Refer to 2.14 Job Card IST006 - Changing the Passwords on page 93 for more details.

4.2.4.1.5 Configuration backup

Create a backup of the system configuration on the AW Server, and on your PC, by following
instructions in Chapter 2, 2.25 Job Card IST016 - System Handover to Customer on page 246.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 323

4.2 Job Card SV001 - Preventive Maintenance (PM)

4.2.4.1.6 Configuration Registration

Register the latest configuration to AWCCT Website and ensure that a Registration key is installed.
See Chapter 2, 2.21 Job Card IST013 - Service Tools Configuration on page 200 for details.

4.2.4.1.7 Check the Scalability page (for cluster only)

If the AW Server is part of a cluster, check the status of the cluster as follows:
• Remotely connect to the AW Server Service Tools.
• Go to Initial Configuration > Scalability page.
• Check that the page displays no error for AW Server nodes in the cluster as well as for HAPS
nodes.
If you find an error, refer to Chapter 2 2.20 Job Card IST012 - Virtual Servers Cluster Configuration on
page 196 for more details.

4.2.4.2 PM Hardware Tasks

In case of preventive maintenance on a physical server, perform the Hardware Tasks below.
If you are doing the preventive maintenance of a virtual AW Server, do not perform PM Hardware
Tasks and only perform 4.2.5 PM Completion on page 326.

4.2.4.2.1 Server and DAS Hard disk status check (all HPE hardware)
For on site PM:
• Check the hard disks LED on front and rear of the AW Server.
• Check the hard disks LED on front and rear of the DAS (for HP High Tier only).
For remote PM, connect to a terminal as root, then check the Server hard disks:
• For the HPE ProLiant DL360 Gen10 Server, check the RAID configuration using the Smart
Storage Administrator utility as described in the AW Server 3.2 Hardware Installation Manual
5719442-1EN, section Configuring BIOS Parameters - Configuration checks.
• For the HPE ProLiant DL360 Gen9 Server, check the internal image hard disks, in a terminal
window:
/usr/sbin/hpssacli controller slot=0 physicaldrive all show <Enter>
• For the HPE ProLiant DL560 Gen8 Server, check DAS hard disks (for HP High Tier only, not
applicable in seamless integration), in a terminal window:
/usr/sbin/hpssacli controller slot=2 physicaldrive all show <Enter>
• For the HPE ProLiant DL580 G7 Server, check DAS hard disks (for HP High Tier only, not
applicable in seamless integration), in a terminal window:
/usr/sbin/hpssacli controller slot=7 physicaldrive all show <Enter>
• For the HP ProLiant ML350 G6 Server or the HPE ProLiant ML350p Gen8 Server, the command
below will display the status of all Server hard disks: the 2 system disks and the 4 image disks.
/usr/sbin/hpssacli controller slot=0 physicaldrive all show <Enter>
• NOTE
If the hpssacli command doesn't work, refer to the workaround Hard drives check
command not working on HPE ProLiant DL360 Gen9 Server in the AW Server 3.2
Advanced Service Manual 5771771-1EN.

324 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.2 Job Card SV001 - Preventive Maintenance (PM)

4.2.4.2.2 Dust cleaning (HP Low Tier servers only)

NOTICE
Dust cleaning is only applicable for the "tower" model of the physical servers. Dust
cleaning does not apply to the "rack-mount" servers (Internal cleaning is under the
Vendor responsibility) nor to virtual servers.
This step is applicable for on site PM only (not applicable for remote PM).
The PM hardware tasks for the AW server consist on cleaning the dust accumulated over months, in
the air vents and inside the computer box. 4
Use an appropriate DATA VACUUM CLEANER such as 46–194427P392.

Service Tasks
• Clean the air vents of the computer box.
• As much as possible, you may also carefully clean inside of the computer box.
• Open the computer box side cover
• Pay special note to the Electrostatic Discharge precautions when working inside the CPU box.
• Carefully vacuum out the system, carefully attending to heavy accumulation spots such as the
Processor area.
NOTE
The use of compressed air is not recommended. Blowing dust out with a stream of air
is not Recommended, because of the ESD (Electro–Static Discharge) hazards to
components, and the dust hazard to the personnel in the area near the cleaning
activity.

4.2.4.2.3 Cabling checks (HP Low Tier servers only)

Cabling checks are only applicable for the HP ProLiant ML350 G6 Server and HPE ProLiant ML350p
Gen8 Server tower. Cabling checks does not apply to the HP High Tier servers (Internal cleaning is
under the Vendor responsibility) nor to virtual servers. Some site may not authorize to check the
cabling.
This step is applicable for on site PM only (not applicable for remote PM).
• Visually inspect all cables connected to the Low Tier Server and check that no cable is damaged,
torn, or disconnected.

4.2.4.2.4 iLO System Information check (all HP hardwares)

This step is applicable for on site PM only (not applicable for remote PM).
Connect to the Service processor web interface to analyze the server hardware sensors.
• Select the "System Information" tab, and examine the "Summary" and other sensors tabs for
any faults or errors.
NOTE
It is normal to see the actual current reading or status of the sensors. If the sensor is
in a fault or error condition it will be displayed as such.
• If faults or errors are present in the Sensor Readings the EVENT LOGS TAB may contain more
detailed information.
• If there are any hardware errors or failures, a separate service dispatch should be created to
resolve the issue - which may include engaging the Vendor Hardware Break / Fix Process
through GEHC. The following actions might be perform in this separate service dispatch:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 325

4.2 Job Card SV001 - Preventive Maintenance (PM)

Referring to the appropriate HP server Service guide:

• replace faulty hard disk(s).
• replace faulty DVD drive.
• replace faulty power supply.
• If there are no faults or errors present in the Sensor Readings AND there are no faults on the
Service Tools HealthPage, select the Event Logs Tab and CLEAR the log by using the Clear Log
button.
NOTE
Clearing the log will only clear the log, not the fault condition. Any current faults will
continue to populate the Event Log. Also, note that failed login attempts and BIOS
messages may be marked as critical errors in the Event Log, however these do not
constitute hardware failures.

4.2.4.2.5 System coin battery replacement (HP Low Tier servers only)
This step is applicable for on site PM only (not applicable for remote PM).
• The System battery that provides power to the real-time clock shall be replaced every 3 to 4
years.The battery is a FRU. See Job Card SV002 for part number.
Also refer to the appropriate HP server Service guide for replacement details.
NOTE
Real Time Clock battery replacement for the HP rack-mount systems (HPE ProLiant
DL360 Gen10 Server, HPE ProLiant DL360 Gen9 Server, HPE ProLiant DL560 Gen8
Server, HPE ProLiant DL580 G7 Server) is under the Vendor responsibility.

4.2.5 PM Completion
If tests were successful, enter the following data into your service record:
• System ID
• System Site Name
• Date and Time
• Your Name
• Comments: “AW Server PM tasks completed successfully - the server status is confirmed for
continued normal operation.”
If faults or critical errors, enter the following data into your service record:
• System ID
• System Site Name
• Date and Time
• Your Name
• Comments: “AW Server PM failed the following task(s):
• Details….
• Enter the separate dispatch number created to address the discovered failure(s).”

4.2.6 Preventive Maintenance tasks summary

Below is a summary of tasks to be performed during Preventive Maintenance.

326 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list

NOTE
This summary of tasks is for information only. DO NOT USE THIS SUMMARY AS A
CHECKLIST FOR YOUR PREVENTIVE MAINTENANCE.
Instead, use the electronic Preventive Maintenance form to record the results of your Preventive
Maintenance.
These checklists are interactive forms to be filled in during each Preventive Maintenance.
All servers (High tier / Low tier)
• Server Hard disk status check - check the LED or use the hpssacli command line.
• DAS (or image RAID) Hard disk status check - check the LED or use the hpssacli command 4
line.

Service Tasks
• iLO - Information page checked.
• HealthPage - HW and VM status checked.
• HealthPage System configuration status - Disk space does not display in RED.
• HealthPage System configuration status - Image Partition Mount Count (and Date) do not
display in Yellow. In the other case, you have warned the IT Admin of the site that Filesystem
check shall be launched in the coming week.
• HealthPage System configuration status - Certificate expiration date shows no error. Otherwise,
it is needed to renew the certificate.
• HealthPage - Software Subsystem status checked.
• Healthpage - Software Subsystems essential for Service Tools section shows no red statuses.
• System password changed.
• Stakeholders informed of password changes.
• Configuration backup saved to server and FE or client PC.
• Configuration Registration - latest configuration has been registered on AWCCT Website and a
Registration key is installed on the AW Server.
• For cluster only Scalability page has been checked and no error are displayed.
Low Tier servers
• Hardware- HPE ProLiant ML350p Gen8 Server/HP ProLiant ML350 G6 Server Dust cleaning and
cabling checks.
• Hardware- HPE ProLiant ML350p Gen8 Server/HP ProLiant ML350 G6 Server System coin
battery replaced.
• Hardware- HPE ProLiant DL360 Gen10 Server/HPE ProLiant DL360 Gen9 Server/HPE ProLiant
ML350p Gen8 Server/HP ProLiant ML350 G6 Server Hard disk drive(s) replaced.
• Hardware- HPE ProLiant DL360 Gen10 Server/HPE ProLiant DL360 Gen9 Server/HPE ProLiant
ML350p Gen8 Server/HP ProLiant ML350 G6 Server drive replaced.
• Hardware- HPE ProLiant DL360 Gen10 Server/HPE ProLiant DL360 Gen9 Server/HPE ProLiant
ML350p Gen8 Server/HP ProLiant ML350 G6 Server Power supply replaced.

4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list

The following information is true at the writing of this document, and for general release of the AW
Server. Subsequent updates of this data may occur without this document getting updated at the
same time, or at all. Updated part numbers will be setup to automatically replace their equivalent
out-of-date counterparts.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 327

4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list

The AW Server program is establishing requirements for off-the-shelf OS and hardware. These will
be delivered as part of the AW Server turnkey package for customer convenience.
• OS and hardware are not part of the AW Server medical device claims
• OS and hardware are ordered out of catalog from respective vendors. No modifications are
required for these items to support the AW Server application.
• HP High Tier Hardware is installed by GEHC and serviced by HP.
• HP Low Tier Hardware is installed by GEHC and serviced by GEHC or HP.
NOTE
Sun Hardware is no longer supported in AW Server 3.2

Hardware Type Server Name Installation Service Responsibility

responsibility
High Tier HPE ProLiant DL360 Gen10 Server GEHC HP Vendor
HPE ProLiant DL360 Gen9 Server GEHC HP Vendor
HPE ProLiant DL560 Gen8 Server GEHC HP Vendor
HPE ProLiant DL580 G7 Server GEHC HP Vendor
Low Tier HPE ProLiant DL360 Gen10 Server GEHC HP Vendor
HPE ProLiant DL360 Gen9 Server GEHC GEHC
HPE ProLiant ML350p Gen8 Server GEHC GEHC
HP ProLiant ML350 G6 Server GEHC GEHC

NOTICE
When ordering a Software FRU, always check that the software version of the FRU is
the same as the software version that was previously installed on the system. If the
FRU contains a newer software version, DO NOT upgrade with that FRU. DO NOT USE
THE SOFTWARE FRU MEDIA TO PERFORM UPGRADE OF PLATFORM OR APPLICATIONS.
Using FRU to perform software upgrade is not allowed as there is no traceability for
the FRU. The correct process to upgrade the software is to order a FRU kit which has
the appropriate traceability, or to upgrade through the FMI process when applicable.
Note that all IB software releases are now available through a FRU kit.
NOTE
Refer to AW Server 3.2 Advanced Service Manual 5771771-1EN for hardware FRU
replacement detailed instructions.

4.3.1 AW Server 3.2 Software FRU’s

Part description Part Number

(this list is updated for the AW Server 3.2 Ext. 3.4 release)
AW Server 3.2 Ext. 3.4 SW FRU kit (includes all items below + traceability) 5720614-16
AW Server 3.2 Ext. 3.4 SW and Docs 5720631-10
Operating System AWS3.2_OS Rev 5.1 for AW Server 3.2 5720621-7
AW Server 3.2 User Docs 5720636-9
AW Server 3.2 Ext. 3.4 SW and Docs for Virtual Machine 5720634-10
Open Source SW for AW Server 3.2 * 5720637-7
Operating System Template AWS3.2_OS Rev 5.1 for Virtual AW Server 3.2 5720625-8

328 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list

Part description Part Number

(this list is updated for the AW Server 3.2 Ext. 3.4 release)
Operating System AWS3.2_OS Rev 5.1 for Virtual AW Server 3.2 5720635-7
AW Server 3.2 Ext. 3.4 SW and Docs for Virtual Machine 5818084-3

* The Open Source media is part of the software delivery and shall be left on site. This media
is not used to load or reload software on the AW Server. Part of the Open source software is
included in the AWS software.

Part description Part Number

(prior to the AW Server 3.2 Ext.2.0 release)
4
HP UPS Driver 1.03 5720629

Service Tasks
4.3.2 Volume Viewer Applications Software FRU’s

Part description Part Number

(this list is updated for the AW Server 3.2 Ext.2.0 release)
Volume Viewer Apps 14.0 Ext.2 SW and Docs for AW Server (or higher) 5779879 (or higher)
CardIQ Xpress Process 2.3 Ext.6 SW and Docs CD for AW Server (or higher) 5480372-7 (or higher)
Quantib Brain 1.2 SW and Docs CD for AW Server (or higher) 5737000-2 (or higher)

Part description Part Number

(this list is updated for the AW Server 3.2 Ext.2.0 release)
Volume Viewer Apps 14.0 Ext.2 SW and Docs for Virtual AW Server (or higher) 5779881 (or higher)
CardIQ Xpress Process 2.3 Ext.6 SW and Docs CD for virtual AW Server (or higher) 5483146-7 (or higher)
Quantib Brain 1.2 SW and Docs CD for virtual AW Server (or higher) 5737004-2 (or higher)

NOTE
The Application software FRUs are common to all types of servers (physical, virtual, Low
Tier and High Tier).

4.3.3 Other Application Software FRU’s

Part description Part Number

(this list is updated for the AW Server 3.2 Ext.2.0 release)
CortexID Suite 2.1 Ext.6 SW and Docs for AW Server (or higher) 5479286-6 (or higher)
Advantage 4D 2.3 Ext. 5 SW and Docs for AW Server (or higher) 5400063-6 (or higher)
AdvantageSim MD 9.0 Ext. 4 SW and Docs for AW Server (or higher) 5441046-9 (or higher)
GSI Viewer 2.2 Ext. 5 SW and Docs for AW Server (or higher) 5404922-8 (or higher)
cvi42 v5.3 Ext.. 4 SW & Docs for AW Server (or higher) 5778797 (or higher)

Part description Part Number

(this list is updated for the AW Server 3.2 Ext.2.0 release)
CortexID Suite 2.1 Ext.6 SW and Docs for virtual AW Server (or higher) 5480329-6 (or higher)
Advantage 4D 2.3 Ext. 5 SW and Docs for Virtual AW Server (or higher) 5573917-4 (or higher)

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 329

4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list

Part description Part Number

(this list is updated for the AW Server 3.2 Ext.2.0 release)
AdvantageSim MD 9.0 Ext. 4 SW and Docs for Virtual AW Server (or higher) 5582138-7 (or higher)
GSI Viewer 2.2 Ext. 5 SW and Docs for Virtual AW Server (or higher) 5589804-4 (or higher)
SmartScore 4.0 Ext. 200 SW & Docs for Virtual AW Server (or higher) 5599570-4 (or higher)
cvi42 v5.3 Ext.. 4 SW & Docs for Virtual AW Server (or higher) 5782165 (or higher)

NOTE
The Application software FRUs are common to all types of servers (physical, virtual, Low
Tier and High Tier).

4.3.4 HPE ProLiant DL360 Gen10 Server High Tier – Hardware FRU's

NOTICE
The HPE ProLiant DL360 Gen10 Server High Tier hardware is serviced and supported
by the vendor. However, the following hardware replaceable parts are available at
GEHC.

Part description Part Number

DL360 G9 300GB OS SFF DS HDD 5777279-11
1.8TB IMG SFF DS HDD 5777279-12
DL360 G10 800W Power supply 5841478-14
HPE Racked KVM Kit 5777280-17

4.3.5 HPE ProLiant DL360 Gen9 Server High Tier – Hardware FRU’s
NOTICE
The HPE ProLiant DL360 Gen9 Server High Tier hardware (incl. KVM, PDU, Network
Switch and UPS) is serviced and supported by the vendor, NO hardware replaceable
parts are available at GEHC.

4.3.6 HPE ProLiant DL560 Gen8 Server High Tier – Hardware FRU’s
NOTICE
As the High Tier server hardware (incl. KVM, PDU, Network Switch and UPS) is serviced
and supported by the vendor, NO hardware replaceable parts are available at
GEHC except for the external optical USB DVD drive.

Part description Part Number

External optical USB DVD Drive 5474017-21

330 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list

4.3.7 HPE ProLiant DL580 G7 Server High Tier – Hardware FRU’s

NOTICE
As the High Tier server hardware incl. KVM, PDU, Network Switch and UPS) is serviced
and supported by the vendor, NO hardware replaceable parts are available at
GEHC.

4.3.8 HPE ProLiant DL360 Gen10 Server Low Tier – Hardware FRU’s
4
NOTICE

Service Tasks
The HPE ProLiant DL360 Gen10 Server Low Tier hardware is serviced and supported
by the vendor. However, the following hardware replaceable parts are available at
GEHC.

Part description Part Number

300GB SAS HDD (OS) 5777279-11
600GB SAS HDD (IMG) 5777280-12
800W Power supply 5841478-14
HPE Racked KVM Kit 5777280-17

4.3.9 HPE ProLiant DL360 Gen9 Server Low Tier – Hardware FRU’s
The HPE ProLiant DL360 Gen9 Server Low Tier hardware is serviced and supported by GEHC Service.
The following hardware replaceable parts are available at GEHC.

Part description Part Number

DL360 Gen 9 Low Tier Server FRU without disks 5777280-10
300GB SAS HDD (OS) 5777279-11
600GB SAS HDD (IMG) 5777280-12
16GB RDDR3 ECC DIMM 5777280-13
500W Power supply 5777280-14
Optical DVD drive assembly 5777280-15
Fan assembly 5777280-16
HP KVM assembly (incl. power supply and cables) 5777280-17
FRU Labeling Kit 5802299-2

NOTE
CR 2032 lithium battery coin for Real time Clock is available as FRU: Part Number
5129534-3. However it is not managed by AW modality.

4.3.10 HPE ProLiant ML350p Gen8 Server Low Tier – Hardware FRU’s
The HPE ProLiant ML350p Gen8 Server hardware is serviced by GEHC.
The following hardware replaceable parts are available at GEHC.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 331

4.3 Job Card SV002 - GEHC Replaceable Parts - FRU list

Part description Part Number

ML350p Gen 8 LT Server FRU without hard disks (24 GB memory) 5474018-20
ML350p Gen 8 LT Server FRU without hard disks (64 GB memory) 5474018-30
VGA cable for monitor 5392462-10
Cable RJ45-RJ45 FTP CAT 5e or CAT 6 2237476-2
Chinese KB 5392002
US English USB KB 5183547-4
USB Optical wheel Mouse 5314326-4
20 inches or higher LED Backlit Monitor 5474018-16
FBWC capacitor module for ML350p gen8 5474018-18
Single fan for ML350P gen8 5474018-19
HP 750W CS HE Power Supply 5474018-21
SATA DVD Drive 5474018-22
500GB SATA HDD 7.2K rpm 5474018-23
1TB SATA HDD 7.2K rpm (ML350pG8 - starting Q1 2017) 5474018-41
4 GB DDR3 Registered ECC DIMM 5474018-24
(used for 6x4GB = 24GB memory configuration)
8 GB RDDR3 ECC DIMM for ML350p 5474018-31
(used for 8x8GB = 64GB memory configuration)
2GB FBWC Cache module LT server ML350p gen8 5474018-25
Air flow baffle - central part- LT server ML350p 5474018-26
Air flow baffle - high and low parts for ML350p gen8 5474018-27
Front door for ML350p Gen8 5474018-29
FRU Labeling Kit 5802299-2

NOTE
CR 2032 lithium battery coin for Real time Clock is available as FRU: Part Number
5129534-3. However it is not managed by AW modality.

4.3.11 HP ProLiant ML350 G6 Server Low Tier – Hardware FRU’s

The HP ProLiant ML350 G6 Server hardware is serviced by GEHC, so the following FRUs are available
at GEHC warehouses.

Part description Part Number

HP ML350 G6 computer box with two power supplies (with NO hard disks) 5364293-30
HP ML350 G6 750W Power supply 5364293-21
HP ML350 G6 SATA DVD drive 5364293-22
HP ML350 G6 500GB SATA hard disk drive 5364293-23
HP ML350 G6 4 GB DDR3 Registered ECC DIMM 5474018-24
(used for 6x4GB = 24GB memory configuration)
HP ML350 G6 8GB RDDR3 ECC DIMM FRU for ML350 G6 5364293-31
(used for 8x8GB = 64GB memory configuration)
HP ML350 G6 Fan assembly 5364293-29

332 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

Part description Part Number

HP ML350 G6 Flashed backed Write Cache (FBWC) module for RAID 5364293-25
HP ML350 G6 FBWC capacitor pack module 5364293-19
HP ML350 G6 front door 5364293-28
HP ML350 G6 Air flow Baffle 5364293-26
HP ML350 G6 Air flow Baffle for DIMM 5364293-27
HP USB 3 buttons mouse 5314326-4
HP USB International keyboard 5183547-4
HP USB Chinese keyboard 5392002 4
HP 17¨LCD monitor 5392462

Service Tasks
HP VGA cable 5392462-10
Cable RJ45-RJ45 FTP CAT 5e or CAT 6 2237476-2
Cable 3 M RJ45 RJ45 FTP CAT 5e or CAT 6 5393841
FRU Labeling Kit 5802299-2

NOTE
CR 2032 lithium battery coin for Real time Clock is available as FRU: Part Number
5129534-3. However it is not managed by AW modality.

NOTICE
The 2GB memory FRU is available but should not be ordered for systems running AW
Server 3.2 or higher. Using 2GB memory modules is not a valid memory configuration
for these software releases

Part description Part Number

HP ML350 G6 2GB DDR3 ECC DIMM memory stick => Do not order for AW Server 3.2 5364293-24
=> Do not order for AW
Server 3.2

4.4 Job Card SV003 - Service Procedures

The following information is true at the writing of this document, and for general release of the AW
Server. Subsequent updates of this data may occur without this document getting updated at the
same time, or at all. Updated part numbers will be setup to automatically replace their equivalent
out-of-date counterparts.
The AW Server program is establishing requirements for off-the-shelf OS and hardware. These will
be delivered as part of the AW Server turnkey package for customer convenience.
• OS and hardware are not part of the AW Server medical device claims
• OS and hardware are ordered out of catalog from respective vendors.
No modifications are required for these items to support the AW Server application
• Sun Hardware is not supported anymore in AW Server 3.2
• HP Low Tier Hardware is installed by GEHC HP Low Tier Hardware is fully serviced by GEHC
• HP High Tier Hardware and OS and UPS drivers are installed by a GEHC FE.
HP High Tier Hardware is serviced by and sourced by and through the hardware vendor.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 333

4.4 Job Card SV003 - Service Procedures

NOTICE
DO NOT USE THE SOFTWARE FRU MEDIA TO PERFORM UPGRADE OF
PLATFORM OR APPLICATIONS. Using FRU to perform software upgrade is not
allowed as there is no traceability for the FRU. The correct process to upgrade the
software is to order an FMI kit through the FMI process. All IB software releases
are now available through an FMI kit.

NOTICE
When ordering a Software FRU, always check that the software version of the FRU
is the same as the software version that was previously installed on the system. If
the FRU contains a newer software version, DO NOT upgrade with the FRU and
contact your FMI admin to upgrade through FMI.

4.4.1 Break-Fix Processes

4.4.1.1 Roles
• The HPE ProLiant DL360 Gen10 Server High Tier hardware break-fix process is under the full
responsibility of the Vendor.
• The HPE ProLiant DL360 Gen9 Server High Tier hardware break-fix process is under the full
responsibility of the Vendor.
• The HPE ProLiant DL560 Gen8 Server High Tier hardware break-fix process is under the full
responsibility of the Vendor.
• The HPE ProLiant DL580 G7 Server High Tier hardware break-fix process is under the full
responsibility of the Vendor.
• The HPE ProLiant DL360 Gen10 Server Low Tier hardware break-fix process is under the full
responsibility of the Vendor.
• The HPE ProLiant DL360 Gen9 Server Low Tier hardware break-fix process is under the full
responsibility of the GEHC FE.
• The HPE ProLiant ML350p Gen8 Server Low Tier hardware break-fix process is under the full
responsibility of the GEHC FE.
• The HP ProLiant ML350 G6 Server Low Tier hardware break-fix process is under the full
responsibility of the GEHC FE.
These processes are listed in the following sections.

4.4.1.2 Hardware Vendor Service Support Model

NOTE
Vendor Service support Model in not applicable in virtualized mode.
For the Low Tier servers, the following support model is used:
• Break/Fix in warranty & out of warranty: GEHC HCS (or EDS) will manage Break/Fix: in
warranty and out of warranty: To ensure this model, GEHC has identified a set of FRUs that are
stored in GPRS Service data warehouse. In case, the whole server is out of order, a high FRU
server is available to replace the whole unit
For the High Tier servers, the following Vendor support model is used:
• Break/Fix in warranty: Warranty uplift will be purchased (included in ICV (server, DAS Disk
Array Storage, UPS Uninterruptible Power Supply, Peripherals) to include 4 hours, 24/7 parts and

334 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

on-site service. Warranty duration is 3 years. Service business is responsible for uplift renewals
post year 3 for contract customers.
• Break/Fix out of warranty: You must contact GE Service support to renew HPE warranty
contract.

4.4.1.3 Service Support Procedures

Reactive service procedures shall be performed as described below:
• All service calls initially placed to GEHC HCS (or EDS) FE / OLC or Field Service Engineer (FE).
• GEHC HCS (or EDS) FE / OLC perform remote preliminary triage, and if possible, resolution.
4
• If necessary, GEHC HCS (or EDS) OLC to split RFS (Request For Service) to the Field. For AW
Server High Tier, OLC initiates vendor dispatch in case of Hardware failure.

Service Tasks
• There is an escalation path from the EDS ROC to the AW Engineering team or HCS advanced
support team, for issues the EDS support team can't handle.
• Further guidance on escalation policies and routes is available at the appropriate regional
Services sites.

4.4.1.4 HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8 Server
Hardware - Break-Fix Process
The hardware break — fix model uses a blended vendor/GEHC model. However, when it is
determined that there is a HARDWARE failure in the SERVER or any of the server’s accessories, the
hardware vendor is contracted through GEHC to diagnose and resolve the hardware issue.
When a problem is reported from a field site, a root cause analysis is applied and results in triage of
the problem towards the appropriate resolution path.

NOTE
For IT, RFS is replaced by ROC.
When you have identified or suspect a hardware issue, please follow use generic procedure below
in order to properly involve the HP Service team (some regional differences may apply):

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 335

4.4 Job Card SV003 - Service Procedures

• Identify the Serial Numbers of the Server, R/T3000 UPS, Ethernet switch (as applicable).
• Note the time and date when the problem was encountered.
• Get a problem description from the end user/customer.
• Open the Terminal tool and run the sosreport command. This command is included in the
Linux OS and will build a tar file with the system information that is used by Linux support
engineers, in order to diagnose problems. The output log file is created in /var/log directory.
• Following the hardware issue detected (disk, fan, power supply, controller), run the appropriate
command.
• Call the HP Support Center and plan a visit to the customer site, with the FP Support Center.

4.4.1.5 HP ProLiant ML350 G6 Server / HPE ProLiant ML350p Gen8 Server

Hardware - Break-Fix Process
The hardware break—fix model is the full responsibility of GEHC for the HPE server. When it is
determined that there is a HARDWARE failure in the SERVER or any of the server’s accessories, the
hardware FRUs can be ordered from the GEHC warehouse to resolve the hardware issue.
Both “low level” FRUs (Hard disks, memory modules, etc.) and “high level” FRU (HP ProLiant ML350
G6 Server / HPE ProLiant ML350p Gen8 Server CPU box) are available.

NOTICE
The “high level” FRU (CPU box) is delivered without hard disks. You must use the hard
disks of the defective box or order the hard disks separately.

Figure 4-1 HARDWARE BREAK/FIX FLOW OVERVIEW, HPE HARDWARE

336 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

4.4.2 HPE ProLiant DL360 Gen10 Server and HPE ProLiant DL360
Gen9 Server Hardware Disassembly/Reassembly Procedures
• Servicing the HPE ProLiant DL360 Gen10 Server High Tier Hardware is under the full
responsibility of the vendor.
• Servicing the HPE ProLiant DL360 Gen10 Server Low Tier Hardware is under the full
responsibility of the vendor.
• Servicing the HPE ProLiant DL360 Gen9 Server High Tier Hardware is under the full
responsibility of the vendor. This section is provided for reference. 4
• Servicing the HPE ProLiant DL360 Gen9 Server Low Tier Hardware is under the full responsibility

Service Tasks
of GEHC service.
Refer to 4.4.5 HP Escalation and Communication Flow on page 348 for contact details.

NOTICE
When calling the HP support center for replacement of a defective UPS or KVM,
prepare the Serial number of the HP DL360 server, as the serial number of these
components are not tracked by HP, and specify that you request on-site assistance
for the replacement. Otherwise, the defective part may be sent to the site without HP
Engineers on-site support.
NOTE
The Network Switch has a standard warranty.

4.4.2.1 Electrical Precautions for HPE ProLiant DL360 Gen10 Server and HPE
ProLiant DL360 Gen9 Server
CAUTION
No LOTO procedure as such is applicable to the HPE ProLiant DL360 Gen10 Server and
the HPE ProLiant DL360 Gen9 Server as the internal voltages of the server correspond
to those of a standard "plug and cord" workstation with no residual energy. Service
procedures are thus deemed to carry negligible risk. However, FEs must begin any
service intervention that requires opening the DL360 case with the following
procedure.
1. Perform a server shutdown procedure, preferably from within the AW software, OR by
depressing the On/Off switch on the front panel.
2. Disconnect the two power cords from the electrical outlet and then from the server.
3. Remove the two power cords and any spare power cords from the vicinity of the server,
storing them in a safe place.

NOTICE
Before performing a shutdown or reboot, refer to A.4 Maintenance Mode on page
369 for details of other important precautions to take.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 337

4.4 Job Card SV003 - Service Procedures

4.4.2.2 De-racking the HPE ProLiant DL360 Gen10 Server and the HPE
ProLiant DL360 Gen9 Server
CAUTION
The HPE ProLiant DL360 Gen10 Server and HPE ProLiant DL360 Gen9 Server CPU box
weighs approximately 15 kg (30 pounds). Comply with the HP safety recommendations
provided in the section "Remove the server from the rack" or equivalent in the HPE
ProLiant DL360 Gen10 Server Maintenance and Service Guide 869839-404 or the HPE
ProLiant DL360 Gen9 Server Maintenance and Service Guide 767928-008.

4.4.2.3 Replacing HPE ProLiant DL360 Gen9 Server Low Tier Components
Refer to "Removal and replacement procedures" in the HPE ProLiant DL360 Gen9 Server
Maintenance and Service Guide 767928-008 to replace the following items:
HPE ProLiant DL360 Gen9 Server Low Tier high FRU swap
• Also refer to AW Server 3.2 Hardware Installation Manual 5719442-1EN Section 2.12 Job Card
IST005.
300GB SAS HDD / 600GB SAS HDD
• HDDs are hot-swappable units. They shall be replaced with the system up and running.
Power Supply
• Power supplies are hot-swappable units. They can be replaced one at a time with the system up
and running. Disconnect the power cable from the power supply and extract the unit.
16GB DDR4 2400 MHz DIMM
• Refer to HPE ProLiant DL360 Gen9 Server Maintenance and Service Guide 767928-008
Internal DVD-RW drive
• Refer to HPE ProLiant DL360 Gen9 Server Maintenance and Service Guide 767928-008
Fan module
• Fan modules are hot-plug devices. Refer to HPE ProLiant DL360 Gen9 Server Maintenance and
Service Guide 767928-008
System battery
• Refer to HPE ProLiant DL360 Gen9 Server Maintenance and Service Guide 767928-008

4.4.2.4 Re-configuring the network after a network card replacement

In case of network card replacement by the Vendor, proceed to the following steps to re-configure
the hospital network:
1. Open a Terminal, login as root.
2. Remove the 70-persistent-net.rules file with the the following command:
/bin/rm -f /etc/udev/rules.d/70-persistent-net.rules <Enter>
3. Remove the ifcfg-eth0 file, and if they exist, ifcfg-eth1, ifcfg-eth2 and ifcfg-eth3
with the following commands:
cd /etc/sysconfig/network-scripts/ <Enter>
ls <Enter> to list all files in the folder.
/bin/rm -f ifcfg-eth0 <Enter>

338 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

/bin/rm -f ifcfg-eth1 <Enter> (if applicable)

And so on for ifcfg-eth2 and ifcfg-eth3 (if applicable).
4. Reboot the server.
reboot <Enter>

NOTICE
Before performing a shutdown or reboot, refer to Maintenance Mode for details of
important precautions to take.
5. Configure the iLO service processor: 4
a. Press <F8> when prompted during the boot sequence and follow instructions given in your

Service Tasks
Installation manual at 2.7 Job Card IST001B - Virtual Machine creation on page 44.
b. Disable Hyperthreading settings in the BIOS.
c. Press <F9> during boot-up to enter BIOS menu. In System Options > Processor Options,
select Hyperthreading, then select DisableHyperthreading.
6. Re-configure the Hospital network and Time zone. Follow instructions given in the AW Server
3.2 Installation and Service Manual 5719443-1EN, at chapter 2, Job Card IST005.

4.4.3 HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8

Server Hardware Disassembly/Reassembly Procedures
Servicing the HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8 Server Hardware is under
the full responsibility of the vendor. This section is provided for reference.
Refer to 4.4.5 HP Escalation and Communication Flow on page 348 for contact details.

NOTICE
When calling the HPE support center for replacement of a defective HPE R/T3000
UPS or KVM, prepare the serial number of the HPE ProLiant DL580 G7 Server / HPE
ProLiant DL560 Gen8 Server, as the serial number of these components are not
tracked by HPE, and specify that you request on-site assistance for the
replacement. Otherwise, the defective part may be sent to the site without HPE
Engineers on-site support.
NOTE
The Network Switch has a standard warranty.

4.4.3.1 Electrical Precautions of the HPE ProLiant DL580 G7 Server / HPE

ProLiant DL560 Gen8 Server
CAUTION
No LOTO procedure as such is applicable to the HPE ProLiant DL580 G7 Server / HPE
ProLiant DL560 Gen8 Server as the internal voltages of the server correspond to those
of a standard "plug and cord" workstation with no residual energy. Service procedures
are thus deemed to carry negligible risk. However, FEs must begin any service
intervention that requires opening the HPE ProLiant DL580 G7 Server / HPE ProLiant
DL560 Gen8 Server case with the following procedure.
1. Perform a server shutdown procedure, preferably from within the AW software, OR by
depressing the On/Off switch on the front panel.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 339

4.4 Job Card SV003 - Service Procedures

2. Disconnect the two power cords (HPE ProLiant DL560 Gen8 Server) or the four power cords
(HPE ProLiant DL580 G7 Server) from the electrical outlet and then from the server.
3. Remove the two power cords (HPE ProLiant DL560 Gen8 Server) or the four power cords (HPE
ProLiant DL580 G7 Server) and any spare power cords from the vicinity of the server, storing
them in a safe place.

NOTICE
Before performing a shutdown or reboot, refer to A.4 Maintenance Mode on page
369 for details of other important precautions to take.

4.4.3.2 De-racking the HPE ProLiant DL580 G7 Server / HPE ProLiant DL560
Gen8 Server
CAUTION
The HPE ProLiant DL580 G7 Server CPU box weighs approximately 40kg (89 pounds).
The HPE ProLiant DL560 Gen8 Server CPU box weighs approximately 28kg (61
pounds). Comply with the HPE safety recommendations provided in the section
"Remove the server from the rack" or equivalent in the HP ProLiant DL580 G7 Server
Maintenance and Service Guide 595655-005 or the HP ProLiant DL560 Gen8 Server
Maintenance and Service Guide 696743-005.

4.4.3.3 Replacing HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8
Server components
Comply with the component-specific procedure provided in the chapter "Removal and replacement
procedures" or equivalent in the HP ProLiant DL580 G7 Server Maintenance and Service Guide
595655-005 or the HP ProLiant DL560 Gen8 Server Maintenance and Service Guide 696743-005.

4.4.3.4 Re-configuring the network after a network card replacement

In case of network card replacement by the Vendor, proceed to the following steps to re-configure
the hospital network:
1. Open a Terminal, login as root.
2. Remove the 70-persistent-net.rules file with the the following command:
/bin/rm -f /etc/udev/rules.d/70-persistent-net.rules <Enter>
3. Remove the ifcfg-eth0 file, and if they exist, ifcfg-eth1, ifcfg-eth2 and ifcfg-eth3
with the following commands:
cd /etc/sysconfig/network-scripts/ <Enter>
ls <Enter> to list all files in the folder.
/bin/rm -f ifcfg-eth0 <Enter>
/bin/rm -f ifcfg-eth1 <Enter> (if applicable)
And so on for ifcfg-eth2 and ifcfg-eth3 (if applicable).
4. Reboot the server.
reboot <Enter>

340 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

NOTICE
Before performing a shutdown or reboot, refer to Maintenance Mode for details of
important precautions to take.
5. Configure the iLO service processor:
a. Press <F8> when prompted during the boot sequence and follow instructions given in your
Installation manual at 2.7 Job Card IST001B - Virtual Machine creation on page 44.
b. Disable Hyperthreading settings in the BIOS.
c. Press <F9> during boot-up to enter BIOS menu. In System Options > Processor Options,
select Hyperthreading, then select DisableHyperthreading. 4
6. Re-configure the Hospital network and Time zone. Follow instructions given in the AW Server

Service Tasks
3.2 Installation and Service Manual 5719443-1EN, at chapter 2, Job Card IST005.

4.4.4 HP ProLiant ML350 G6 Server / HPE ProLiant ML350p Gen8

Server Disassembly/Reassembly Procedures
The following section gives directions to disassemble and reassemble the HP ProLiant ML350 G6
Server and HPE ProLiant ML350p Gen8 Server hardware FRUs (Field Replaceable Units):
For the HP ProLiant ML350 G6 Server, refer to HP ProLiant ML350 G6 Server Maintenance and
Service Guide 513502-009 and follow instructions of section "Removal and Replacement
procedures".
For the HPE ProLiant ML350p Gen8 Server, refer to HPE ProLiant ML350p Gen8 Server Maintenance
and Service Guide 661081-009 and follow instructions of section "Removal and Replacement
procedures".

4.4.4.1 LOTO Procedure for HP ProLiant ML350 G6 Server / HPE ProLiant

ML350p Gen8 Server
WARNING
Field Engineers must always adhere to the Lock Out Tag Out (LOTO) procedure when
installing or servicing an HP ProLiant ML350 G6 Server / HPE ProLiant ML350p Gen8
Server. (Normally GEHC FEs are only responsible for servicing the HP ProLiant ML350
G6 Server / HPE ProLiant ML350p Gen8 Server; other server models are the
responsibility of engineers from the respective hardware vendor).

MODE: Imaging
EQUIPMENT: HP ProLiant ML350 G6 Server and
HPE ProLiant ML350p Gen8 Server
Premises: Customer owned locations or facilities
SUBSYSTEM: None
ACTIVITY: Installation, Preventive Maintenance, Corrective Maintenance
Equipment Specific LOTO Procedures
Steps are to be completed in the order listed below
Label /Tag Energy Magnitude Location Procedure for Lockout Zero Energy Tryout, Verification,
Description Source & Energy Release & Testing
Electrical Electrical 110 / 230 Various Carry out server Verify/ Test Equipment to
Wall Outlet VAC shutdown procedure, assure power source has been
preferably from within removed by depressing On/Off

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 341

4.4 Job Card SV003 - Service Procedures

depending the AW software, OR Switch on the server front

on region by depressing the panel.
On/Off switch on the
front panel.
Disconnect the2 power
cords from the
electrical outlet and
then from the server.
Remove the 2 power
cords and any spare
power cords from the
vicinity of the server.
Apply any protective
devices mandated by
local EHS legislation
(LOTO power socket
locks, tags, adaptors).
Equipment Electrical 110V / / 230 Within Wait 5 minutes after Check Power Supplies outputs
Power VAC System Power down to allow using multi-meter for Zero
Supply depending Power for discharge of any Power status.
on region Supplies capacitors in the
Powers Supplies

GEHC Field Service General LOTO Instructions

Shut Down Steps & Return to Service Summary
The following section provides a Business Level Summary of the Key Steps for conducting a LOTO (Lockout Tagout).
Step 1: PREPARE FOR SHUTDOWN:
- Acquire LOTO training and any related training mandated by local EHS legislation.
- Understand the applicable procedures. Determine associated equipment.
- Acquire any protective materials (i.e. socket locks, tags, lock adapters).
- Access consequences of shutdown. Notify all affected persons.
Step 2: NOTIFICATION OF PERSONNEL:
- Personnel who may be affected shall be notified prior to the application and after
the removal of power cords, lockout devices or tagout devices.
- Personnel may include workstation operators, clinical users, technicians, engineers
or area managers.
Step 3: SHUTDOWN:
- Carry out server shutdown procedure, preferably from within the AW software, OR
by depressing the On/Off switch on the server front panel.
Step 4: ENERGY ISOLATION:
- Disconnect the power cord from the electrical outlet and then from the server.
- Disconnect peripheral device cables from the server.
- Remove the power cords and any spare power cords from the vicinity of the server.
Step 5: LOCKOUT TAGOUT (If mandated by local EHS legislation):
- Attach LOTO Red Lock & filled out Red Tag (or local equivalent devices) on each point
of disconnect, shut off, blank & vent as appropriate. Verify that all above is complete.
Step 6: CONTROL STORED ENERGY:
- Assure that all stored potentially hazardous energy has been relieved, dissipated,
restrained, drained or otherwise controlled (i.e. electrical capacitors) by waiting at
least five minutes between power-down and opening the server case.
Step 7: VERIFY ISOLATION:
- Extremely important! Do not assume the posted shutdown procedure is accurate –
Report any inaccuracies immediately to your EHS Rep.

342 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

- Verify that the equipment is fully LOTO-compliant and that all energy is zero.
- Zero energy tests shall include:
1) Attempt to operate the equipment, by the On/Off switch;
2) Check Power Supplies outputs using a multi-meter for Zero Power status..
NOTE
NEVER leave the server unattended with the case open. If you
must leave the server during servicing, resecure the case.
When you return to the server, check that the power cords
have not been reconnected, before opening the case. If
necessary, recommence this procedure from Step 3.
4
Step 8: RETURN TO SERVICE:

Service Tasks
- Assure that maintenance schedule has been successfully completed and any faulty
FRUs replaced.
- Assure that the server case and vicinity are clear of tools
- Assure that all internal parts, covers and side panels have been securely reattached/
reconnected.
- Reconnect peripheral device cables to the workstation.
- Reconnect the power cords to the workstation and then electrical outlet.
- Notify affected persons that energy is to be restored.
- Removes any tags and lockout devices from power sockets.
- Reboot the server and assure that the equipment is functioning safely & properly.

NOTICE
All defective parts must be returned with no delay.Parts which are not returned will
be charged to the region.
The first two Field Replaceable Units (Power supplies and Hard disk drives) are "hot-plug devices". It
means that it is not necessary to power down the server to replace them.

4.4.4.2 Replacing the "hot-plug" power supplies

• Disconnect the power cable from the power outlet, then from the defective HP ProLiant ML350
G6 Server / HPE ProLiant ML350p Gen8 Server power supply. You do not need to shutdown the
server.
• Extract the HP ProLiant ML350 G6 Server / HPE ProLiant ML350p Gen8 Server power supply
(refer to section "Hot-plug power supply" in the HP ProLiant ML350 G6 Server Maintenance and
Service Guide 513502-009 or section "Power supply module" in the HPE ProLiant ML350p Gen8
Server Maintenance and Service Guide 661081-009).
• Insert the new power supply and reconnect the power cable.

4.4.4.3 Replacing the "hot-plug" hard disk(s)

• Extract the defective hard disk drive from its slot (refer to section "SAS/SATA hard drive" in the
HP ProLiant ML350 G6 Server Maintenance and Service Guide 513502-009 or section "Drive" in
the HPE ProLiant ML350p Gen8 Server Maintenance and Service Guide 661081-009).
You do not need to shutdown the server.
• Insert the new Hard disk drive.
• Make sure it is properly detected (front LEDs are flashing while the disk is reconstructed).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 343

4.4 Job Card SV003 - Service Procedures

4.4.4.4 Powering down the server

To replace any of the Field Replaceable Units, you must power down the server and disconnect it
from the mains power. Refer to section "Power down the server" in the HP ProLiant ML350 G6 Server
Maintenance and Service Guide 513502-009 or section "Power down the server" in the HPE ProLiant
ML350p Gen8 Server Maintenance and Service Guide 661081-009.

4.4.4.5 Opening the side cover

NOTICE
The boards and disk drives contain electronic components that are extremely sensitive
to static electricity. Do not touch the components themselves or any metal parts.
Carefully observe electrostatic discharge precautions when servicing inside the unit.
Use a grounding wrist wrap and/or antistatic carpet when handling the drive
assemblies, boards or cards.

CAUTION

To reduce the risk of personal injury from hot surfaces, allow the drives and the
internal system components to cool before touching them.

• Open the front bezel and remove it. Refer to section "Front bezel" in the HP ProLiant ML350 G6
Server Maintenance and Service Guide 513502-009 or section "Remove the security bezel" in
the HPE ProLiant ML350p Gen8 Server Maintenance and Service Guide 661081-009.
• Open the side cover. Refer to section "Rack bezel" in the HP ProLiant ML350 G6 Server
Maintenance and Service Guide 513502-009 or section "Remove the rack bezel" in the HPE
ProLiant ML350p Gen8 Server Maintenance and Service Guide 661081-009.

4.4.4.6 Replacing the DVD drive

Refer to section "Customer self repair" in the HP ProLiant ML350 G6 Server Maintenance and Service
Guide 513502-009 or section "Customer self repair" in the HPE ProLiant ML350p Gen8 Server
Maintenance and Service Guide 661081-009.

4.4.4.7 Replacing the air flow baffles

Refer to sections "Large redundant fan air baffle" and "DIMM baffle" in the HP ProLiant ML350 G6
Server Maintenance and Service Guide 513502-009 or sections "Air baffle" and "PCI air baffles" in the
HPE ProLiant ML350p Gen8 Server Maintenance and Service Guide 661081-009.

4.4.4.8 Replacing a cooling fan

Refer to section "Fan" in the HP ProLiant ML350 G6 Server Maintenance and Service Guide
513502-009 or section "Fan" in the HPE ProLiant ML350p Gen8 Server Maintenance and Service
Guide 661081-009.

4.4.4.9 Replacing the DIMM memory modules

• Refer to section "DIMM" in the HP ProLiant ML350 G6 Server Maintenance and Service Guide
513502-009 or section "DIMMs" in the HPE ProLiant ML350p Gen8 Server Maintenance and
Service Guide 661081-009.
• Question: One of my memory modules is broken, which FRU should I order?
• Answer: Follow the steps below:

344 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

• Determine the hardware model of your Low-Tier server: HP ProLiant ML350 G6 Server or
HPE ProLiant ML350p Gen8 Server. This can be checked in Healthpage Machine type field.
• On the memory module, read the label indicating its capacity: 2GB, 4GB, 8GB.
• Refer to FRUs (Field Replaceable Units) and identify the corresponding FRU Part Number.
• Question: I am swapping my Low-Tier HP ProLiant ML350 G6 Server with the High-Level FRU of
HP ProLiant ML350 G6 Server, which memory modules should I keep, which memory modules
should I return?
• Answer: You should keep the 4GB or 8GB memory modules. You should return the 2GB memory
modules. Always ensure that the ML350 G6 has 24GB (6×4GB) or 64GB (8×8GB) memory
configuration at the end of the FRU swap procedure. 12GB (6×2GB) is not a valid memory 4
configuration for HP ProLiant ML350 G6 Server on AW Server 3.2 or higher.

Service Tasks
4.4.4.10 Replacing the RAID Flash Backed Write Cache module(s)
Refer to section "Flash-backed write cache module" in the HP ProLiant ML350 G6 Server
Maintenance and Service Guide 513502-009 or section "Cache module" in the HPE ProLiant ML350p
Gen8 Server Maintenance and Service Guide 661081-009.

4.4.4.11 Replacing the Real time clock lithium coin battery

System Real Time Clock (RTC) battery, CR2032 - 3V Lithium:
HP original Part number: 319603-001
GEHC FRU Part Number: 5129534-3
NOTE
The FRU 5129534-3 is not managed by AW modality.Alternatively, this battery can be
purchased from your local HP dealer, or any PC or Photo shop.
To replace the battery coin, refer to section "Battery" in the HP ProLiant ML350 G6 Server
Maintenance and Service Guide 513502-009 or section "System battery" in the HPE ProLiant
ML350p Gen8 Server Maintenance and Service Guide 661081-009.

4.4.4.11.1 RTC battery removal

• Power down the server and remove the power cord from the electrical outlet.
• Remove the access panel (see 4.4.4.5 Opening the side cover on page 344)
• Remove any PCI card blocking access to the battery if applicable).
• Press the retaining clip with a flat-bladed tool to release the battery.
• Lift the battery out of the socket.

4.4.4.11.2 RTC battery replacement

• Press the new battery into the socket.
• Replace the PCI card (if applicable).
• Replace the access panel.
• Reconnect the power cord and turn on the server

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 345

4.4 Job Card SV003 - Service Procedures

4.4.4.12 Swapping the HP ProLiant ML350 G6 Server CPU box

NOTICE
The FRU HP ProLiant ML350 G6 Server CPU box is delivered without hard disks and
with two power supplies. Use the 6 hard disks from your defective Unit. If you are not
confident that only the CPU box is defective, make sure to order as well new hard
disks.

4.4.4.12.1 Field supplied tools

• One (foldable) hand cart to move the server safely, for one FE alone.

CAUTION
The weight of the complete ML350 CPU box is above the limit fixed by EHS
specifications. Therefore, if handled by one FE alone, it must be moved and put
into place by means of a transport hand cart.

4.4.4.12.2 Swap procedure

To replace the ML350 server CPU box by the FRU ML350 CPU box, proceed as follows:
1. Carefully remove the 6 HDDs from your defective ML350 CPU box, making sure you store them
in the right order, so that you do not lose the RAID configuration and OS load. We recommend
that you label the disks with a number when removing them.
NOTE
If you use the original HDDs from the old CPU box, with your new FRU CPU box, you
will not need to reload the software. However, you will have to configure the iLO
service processor and re-configure the hospital network and Time zone. See 2.13 Job
Card IST005 - Network and Time Configuration on page 88.
NOTE
If you are NOT going to use the original 500GB HDDs from the old CPU box, you must
also order new 500GB HDDs, and you will need to reload the software.
In both cases, you will have to calculate the new license keys corresponding to the license ID of
the FRU CPU box. See Step 13.
2. Open carefully the FRU ML350 CPU box packaging. You will need to re-use this packaging for
sending back the defective unit.
3. Swap the defective ML350 CPU box with the FRU ML350 CPU box.
4. For the HP Low-Tier ML350 G6, determine which memory module to keep:
Keep the 4GB/8GB memory DIMMs from the previous CPU box and insert them in the FRU CPU
box, as described in Section Replacing the DIMM memory modules. The reason is that the
ML350 G6 CPU box FRU contains only a total of 12GB memory, however 24 GB or more are
required for AW Server 3.2. Refer to the AW Server 3.2 Hardware Installation Manual
5719442-1EN, Appendix A.8 for more details.

346 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

Return the 6 x 2GB memory modules by inserting them in the faulty CPU box that you will return
to GE.
Do not attempt to install both the new memory DIMM modules and the older 2GB memory
DIMM modules: this configuration has not been validated and might lead to performance issues.
5. Carefully insert the 6 x 500GB HDDs, making sure to put them in the right order. Refer to AW
Server 3.2 Hardware Installation Manual 5719442-1EN if needed.
6. If you have chosen to keep the existing hard disks, reconfigure the ethernet ports, following next
steps. In the other case, jump to Step 13.
7. Open a Terminal, login as root.
4
8. Remove the 70-persistent-net.rules file with the the following command:

Service Tasks
/bin/rm -f /etc/udev/rules.d/70-persistent-net.rules <Enter>
9. Remove the ifcfg-eth0 file, and if they exist, ifcfg-eth1, ifcfg-eth2 and ifcfg-eth3
with the following commands:
cd /etc/sysconfig/network-scripts/ <Enter>
ls <Enter> to list all files in the folder.
/bin/rm -f ifcfg-eth0 <Enter>
/bin/rm -f ifcfg-eth1 <Enter> (if applicable)
And so on for ifcfg-eth2 and ifcfg-eth3 (if applicable).
10. Reboot the server.
reboot <Enter>

NOTICE
Before performing a shutdown or reboot, refer to Maintenance Mode for details of
important precautions to take.
11. Configure the iLO service processor:
a. Press <F8> when prompted during the boot sequence and follow instructions given in the
AW Server 3.2 Installation and Service Manual 5719443-1EN at 2.7 Job Card IST001B -
Virtual Machine creation on page 44.
b. Disable Hyperthreading settings in the BIOS.
c. Press <F9> during boot-up to enter BIOS menu. In System Options > Processor Options,
select Hyperthreading, then select DisableHyperthreading.
12. Re-configure the Hospital network and Time zone. Follow instructions given at 2.13 Job Card
IST005 - Network and Time Configuration on page 88.
13. Calculate new license keys. Use eLicense to calculate the new license keys, or contact your
support center with the new CPU box license ID. See A.3 eLicensing on page 362.
14. Default password for the iLO: Refer to the AW Server 3.2 Hardware Installation Manual
5719442-1EN to check or create the default password for the iLO service processor.
15. Load AW Server. As the FRU Low Tier server is not preloaded, refer to Sections 3.8.5 Software
upgrade on page 282 to 3.8.13 Final tests and system handover to customer on page 298 to
load the system with AW Server OS, platform, applications and to configure the AW Server.
16. Labelling: when the new ML350 CPU box is fully loaded, place the labels delivered within the
FRU package on the new CPU box, referring to the included document, and/or refer to the AW
Server 3.2 Hardware Installation Manual 5719442-1EN, Job Card IST007 - Installation of GEHC
Product Labels.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 347

4.4 Job Card SV003 - Service Procedures

DO NOT FORGET to place an EHS safety label as well.

17. e-IFU labelling: If delivered with the FRU unit, and for European sites only, stick the e-IFU label as
well.
18. Ship back the defective CPU box: Use the FRU packaging to ship back the defective ML350 CPU
box (refer to HP ML350 server handling procedure).

NOTICE
Use caution for safely handling the ML350 CPU box, according to EHS
regulations.
19. Returning instructions:
The defective unit must be sent back (without hard disks and with its TWO power supplies)
through the ”SWAP (Supplier Warranty Program) process”. Fill the red label identifying the
defective unit with the following information:
• GEHC part number
• Job number
• Failure description. I.e : Result of Insight diagnostics tool summary if appropriate (see Chap
4, TSG005)
• Workstation Serial number (even for disk drives returned separately)
• FE contact name and ID number
• SWAP/FOI/FOA : Cross Swap Box

NOTICE
DO NOT retain any part from the old unit. Missing parts will be charged to your
region.

4.4.5 HP Escalation and Communication Flow

NOTICE
This section is only applicable for the HP High Tier server.

4.4.5.1 HP Support Center Web site

When a hardware issue has been identified or is suspected on your HP High Tier server, you need to
call the HP service in order to have the hardware part being replaced on-site.
See 4.4.5.2 HP supported countries telephone list on page 350 for the list of HP support phone
numbers.

NOTICE
When calling the HP support center for replacement of a defective UPS or KVM,
prepare the Serial number of the server, as the serial number of these components are
not tracked by HP, and specify that you request on-site assistance for the
replacement. In the other case, the defective part may be sent to the site without HP
Engineers on-site support.
NOTE
The Network Switch has a standard warranty.

348 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

It is also possible to open service calls from the HP Web site, after being registered. Follow the
procedure described below to register and/or request assistance.
• Connect to HP Web site
• Open the Navigator on HP Support Center: www.hp.com/go/hpsc
• Login or Register (if not done yet) on HP Web site
• Using the tab ‘My HP Support Center’, register for a new account or login
• Create a case on HP Web site
• Using the tab “Support option” and the sub-menu “Get help from HP“, click on “Submit or
manage support cases” 4
• Enter the serial number of the server or the serial number of the failed KVM or UPS component

Service Tasks
(may need to enter the serial number of the server) and click on ‘Submit case’.
• Fill-in the issue information
• Write down the case number for future use.
NOTE
There will be no confirmation mail from HP web site.
• To follow the case
• Using the tab “Support option” and the sub-menu “Get help from HP“, click on “Submit or
manage support cases”
• Enter the case number and follow the status.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 349

4.4 Job Card SV003 - Service Procedures

4.4.5.2 HP supported countries telephone list

350 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

Service Tasks

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 351

4.4 Job Card SV003 - Service Procedures

352 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

Service Tasks

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 353

4.4 Job Card SV003 - Service Procedures

354 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.4 Job Card SV003 - Service Procedures

Service Tasks

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 355

4.4 Job Card SV003 - Service Procedures

4.4.6 Hardware Vendor Information Links

4.4.6.1 HP Hardware Vendor Information Links

Description Link
Hewlett Packard Enterprise Home Page https://www.hpe.com/
Hewlett Packard Enterprise Support Center https://support.hpe.com/hpesc/public/home
HPE ProLiant DL360 Gen10 Server - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=a00018808en_us
HPE ProLiant DL360 Gen9 Server - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=c05031449
HPE ProLiant DL560 Gen8 Server - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=c05062110
HPE ProLiant DL580 G7 Server - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=c05282198
HPE ProLiant ML350p Gen8 Server - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=c03908833
HP ProLiant ML350 G6 Server - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=a00021284en_us
Intelligent Provisioning User Guide for HPE ProLiant https://support.hpe.com/hpesc/public/docDisplay?
Gen10, ProLiant Gen10 Plus Servers, and HPE Synergy docLocale=en_US&docId=a00017037en_us
Intelligent Provisioning User Guide for HPE ProLiant https://support.hpe.com/hpesc/public/docDisplay?
Gen9 Servers and HPE Synergy docLocale=en_US&docId=c04419967
HPE Integrated Lights Out (iLO 5) for HPE Gen10 Servers https://support.hpe.com/hpesc/public/docDisplay?
- Document List docLocale=en_US&docId=emr_na-a00019271en_us
HP Integrated Lights-Out 4 (iLO 4) - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=emr_na-a00043732en_us
HP Integrated Lights-Out 3 (iLO 3) - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=emr_na-a00044678en_us
HPE Integrated Lights-Out 2 (iLO 2) - Document List https://support.hpe.com/hpesc/public/docDisplay?
docLocale=en_US&docId=emr_na-a00045684en_us

4.4.6.2 Note about the HP Serial number

NOTE
The serial number is 10 characters CCSYWWXXXX encoded using:

356 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.5 Job Card SV004 - Renewal of Digital Certificate

• CC: Country Code (ex: GB -> Great Britain, CZ -> Czech Republic…)
• S: Site Code Designator (ex: 8)
• Y: Year (ex: 9 -> 2009, 0 -> 2010, 1 -> 2011…)
• WW: Week or the year in ISO format (ex: 01, 02, 30, 52)
• XXXX: Code to create a Unique Identifier

4.5 Job Card SV004 - Renewal of Digital Certificate

This procedure concerns AW Server systems that are using the self-signed certificate provided by 4
AW Server software. This procedure does not apply to AW Server systems using a certificate

Service Tasks
purchased by the customer.

4.5.1 Purpose of this procedure

This procedure introduces information concerning the digital certificate used by AW Server to
authenticate itself at the time of AW Server client connection. By default, the validity of this
certificate is set to 5 years after the installation of AW Server. Once this period of time is over, the
certificate is considered as invalid. This procedure provides instructions to renew the digital
certificate.
NOTE
This procedure may also refer to the "digital certificate" as "authentication certificate" or
"public-key certificate": these namings are all equivalent.

4.5.1.1 How to determine if an AW Server needs certificate renewal

To check if an AW server needs to have its certificate renewed, check the following:
1. Check that the digital certificate is not valid anymore. This typically happens when the AW
Server was installed more than 5 years ago and has not been upgraded or reinstalled since 5
years.
To check the digital certificate validity, follow instructions below:
a. Check the Healthpage Certificate expiration date field. If the field is not green, then it is
needed to renew the certificate, go to the next section for detailed steps on certificate
renewal.
b. To check manually the validity date of the certificate, open a Terminal:
• By using the Service Tools > Tools > Terminal > New modal Terminal. Click on
Connect.
• OR by using PuTTY.
c. Login as root.
d. Enter the following command to display the validity of the certificate:
cd /etc/pki/tls/certs/ <Enter>
openssl x509 -in server.crt -noout -text | grep -A2 Valid <Enter>
(do not forget the upper case for V in Valid)
e. Enter the following command to display the date of the system:
date <Enter>4
The results of previous commands should appear.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 357

4.5 Job Card SV004 - Renewal of Digital Certificate

If the date of the system is later than the date indicated in the Not After field, the
certificate is not valid anymore. Apply the procedure below to renew the digital certificate.
2. Check that the AWS Client displays a warning message at login.
When logging to the AWS Client an Invalid Certificate message appears in a pop-up. If
the user selects Yes, the AWS Client is able to launch normally. However, the message appears
again at each login.

4.5.1.2 Instructions to renew AW Server digital certificate

1. Enter the Maintenance Mode. THIS WILL DISCONNECT ALL USERS USING THE AW SERVER.
a. In the Service Tools, go to Maintenance > Maintenance.
b. Select the Start maintenance tab.
c. Enter a disconnect message, then click on the Start Maintenance button.
d. When asked for confirmation, select OK.
A message confirms that the AW Server is now in Maintenance Mode.
For more details on Maintenance Mode, refer to A.4 Maintenance Mode on page 369.
2. Launch a Terminal in Service Tools, or connect through ssh with PuTTY and login as root.
Refer to the previous section for detailed steps.
3. Type the following command:
/usr/sbin/gensslcertAWE -y 1825 <Enter>
Messages should appear as shown below. This command creates a new self-signed certificate
valid for 1825 days (5 years).
4. The installation process requires a re-start of the httpd web services and will disrupt any
connected clients. Enter the following command:
/etc/init.d/httpd reload <Enter>
5. Check that the Validity date of the certificate has been updated.
Either check the Healthpage, or use the same commands as in Section 4.5.1.1 How to determine
if an AW Server needs certificate renewal on page 357:
a. Enter the following command to display the validity of the certificate:
cd /etc/pki/tls/certs/ <Enter>
openssl x509 -in server.crt -noout -text | grep -A2 Valid <Enter>
(do not forget the upper case for V in Valid)
b. Enter the following command to display the date of the system:
date <Enter>
The results of previous commands should appear.
6. Check that the Certificate is valid for the next 5 years, starting on the current date.
7. Finish the Maintenance Mode:
a. In the Service Tools, go to Maintenance > Maintenance.
b. Select the Finish maintenance tab.
c. Click on the Finish Maintenance button.
A message confirms that the AW Server is in Maintenance Mode.
d. Select OK.

358 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 4.5 Job Card SV004 - Renewal of Digital Certificate

For more details on Maintenance Mode, refer to A.4 Maintenance Mode on page 369.
8. Test the AW Server client:
a. On a client PC, launch AW Server and connect to the AW Server. A pop-up displays at the
first connection to accept the Certificate.
b. Accept the certificate by clicking on Yes.
c. Logout of the AWS client.
d. Connect one more time to the AWS Client. This time, no pop-up should display for
certificate. This confirms that certificate has been successfully renewed.
4

Service Tasks

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 359

Page intentionally left blank
 A
Appendix A Appendices

A.1 Overview
This chapter contains the following appendices:
A.2 Specific field - Characters rules and limitations on page 361
A.3 eLicensing on page 362
A.4 Maintenance Mode on page 369
2.24.2 Anti-Virus setup on page 242
A.6 VMware Support on page 378
A.7 Software Loading Through iLO on page 410
A.9 Useful Commands and Tools on page 419
A.10 Filesystem Check on page 426
A.11 Hardware Return Procedure on page 430
A.12 AW Server Integration in CT/MR Console Environment on page 433
A.13 Physical Servers - Installed Base on page 461

A.2 Specific field - Characters rules and limitations

This section describes the characters rules and limitations that shall be followed to fill in the
Hostname, AE Title, IP Address, Port, System ID, Label/Name and Smoothing factor fields.
1. Hostname
a. The hostname is restricted to 16 characters maximum.
b. Only the following characters are supported:
• [a-z]
• [A-Z]
• [0-9]
• Dash (-)
• Underscore ( _ )
NOTE
Backslash (\) is not allowed
c. The hostname shall NOT contain numbers only or start with a number (I.e: hostname =
123456).
d. The hostname shall NOT contain space(s)
e. The hostname shall NOT contain dot(s)
NOTE
The first dot is considered and used for adding the domain name (if applicable for
the site).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 361

A.3 eLicensing

<hostname>.<domain_name> I.e: aws-06.euro.health.ge.com

2. AE Title
a. Length = 16 characters max
b. Same characters limitation as for the Hostname
c. AW workstation and AW server use Hostname = AE Title
3. IP Address
a. 4 numbers/parts (octets)
b. Numbers [0-255]
c. Numbers separated by one dot each (i.e : 192.9.100.25)
4. Port
a. Only numbers [0-9] between 0 and 65535
b. AW workstation and AW Server use Port # 4006
5. System ID
a. Only the alphanumeric characters are supported:
• [a-z]
• [A-Z]
• [0-9]
6. Label/Name
a. Only the following characters are supported:
• [a-z]
• [A-Z]
• [0-9]
• _-.
7. Smoothing factor
a. Only the following characters are supported:
• [A-Z]
• [0-9]
• Underscore (_) and space

A.3 eLicensing
eLicense Order Fulfillment and License Generation

A.3.1 Foreword
Currently, the AW Server 3.2 Hardware or Virtual server configuration is delivered with:
• 1 Cola License key for the internal License server
• 1 Platform key (8K, 16K, 40K, 80K or 160K slices)
• 1 Pre-processing key (optional)
The following option can be delivered for AW Server 3.2 Hardware or Virtual server configuration:

362 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.3 eLicensing

• 1 Cola License server software package for Windows 7 to load the license server on an external
PC (hardware or virtual) + 1 Cola License key for use with external License server.
OR
• 1 Cola License key upgrade for use with an existing Windows XP external License server
The Advanced Applications software packages are delivered with all configurations orders, and
license keys will be made available in eLicense depending on the Applications purchased by the site.

A.3.2 eLicense operation

The following is an EXAMPLE of an AW Server initial installation license generation flow from an
EXAMPLE stock order. The exact process and flow may vary depending on existing licenses, eLicense
website availability / changes, and order details. A
Also refer to 5537368-1EN - Floating License 3.3.x Installation Manual, for more details.

Appendices
1. Access the eLicense site
http://elicense.gehealthcare.com/elicense/ OR http://elicense.gehealthcare.com/
this second URL is available via the Internet, and via the GEHC VPN connectivity model.
NOTE
NOTE THAT THE PROPER ORDER NUMBER WILL BE REQUIRED:
• Global Order Number (GON): ____________________________
• No GON available:
• For end-customers, please contact your GE Service Personnel.
• GE Service Personnel , please contact your local Support Center or IT ROC
The FE must create an instance corresponding to the model type and then enter the licenseId to
be able to generate licenses.
Use the following Model Type for AW Server 3.2:
• AWS_Primary: To be used for AW Server 3.2 release
• Stand Alone AWS Hardware (Hi-tier, or Low-tier) Including Upgrades of existing
systems.
• VM - AWS Stand Alone (No nodes)
• VM - AWS Primary (first node)
• AWS_ Node :Virtual only - All other AWS Nodes on a system.

NOTICE
AWS_Primary is the only model-type that will produce a CoLA Server
License and individual floating application licenses. It will also produce seat
licenses, AutoLaunch, and Integration Licenses. AWS_Node only generates,
seat licenses, AutoLaunch, and Integration Licenses.
DO NOT Use the following Model Type for AW Server 3.2:
• AWS - reserved for AWS2.0 and earlier
2. In the HOME page (not shown here), enter the order number (GON) under the “Order
Management” section in the “Order Number” field – then click on the “Go” button.
3. For the “initial” AW Server installation - the “Order Information” screen should display similar as
shown below - if there are no licenses created from this order yet.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 363

A.3 eLicensing

• If there are license(s) created from this order, there will be “KEY” icons in the table –
indicating the license key existence.
• In the below example, the AW Server node-lock slice license is the upgrade catalog license,
which is in reality the 40,000 slice license.
• The single AW Server Catalog entry will create TWO NODE-LOCK licenses: The 8K or 16K or
40K or 80K or 160K Platform Enabler & the CoLA License Server Enabler.

4. Click on the “Add a System” button. The following screen should display.

• Here is where you need to enter the licenseID of the AW Server that you intend to license –
this is the Ethernet MAC generated value which is automatically calculated in the Service
Tools > Initial configuration > Licensing tool under Platform Configuration > License ID.
• After entering the licenseID in the above “Enter System Information” field, and making sure
that the “HostID” and “AW” pull-downs are selected – the following screen should display.

364 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.3 eLicensing

Appendices
5. Enter ALL the information requested here.
• The Serial Number of the server should be available on the chassis or in the documentation
provided by the vendor.
• The MAC ID was accessed back in the installation section of this document - using the
command-line ip utility.
• The SYSTEM ID is assigned by the local service team.
NOTE
ALL of this information is essential. Please make sure to enter it!
6. Click on the Continue button, and the following screen should display.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 365

A.3 eLicensing

• In this “Order Assignment” screen, select the licenses that you want to create for the
system that you just previously ADDED, and is now shown in the left part of the table.
Check the boxes, or select Check All if all the catalog entries on this screen are for the AW
Server system entered.
7. Click on the Generate License button. The following screen should display.

• The Select Quantity - you will select the number of Floating License instances you will
license applications for. The only licenses that will show a quantity select pull-down are
floating licenses. Node-locked licenses will (by definition) only show a qty of 1 - no pull-
down to change that.
8. Use the “Quantity” column pull-downs to select the number the order has defined for this
particular system. In the example, the initial Order Information screen showed a quantity of 5

366 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.3 eLicensing

each, so select the 5 in the pull-down menu, then click on the ”Continue” button. The following
screen should display.

Appendices
• The “Order Information” screen now shows all the catalog licenses that have been created
for the system, and their quantities. Notice the “Floatable” column – the server ‘node lock’
slices license is NOT floatable – it is NODE-LOCKED to this node/system.
• If the data in this table is all correct, click the “Confirm Selection(s)” button, and the
following screen should display.

9. The “Order Assignment” screen will now show “KEY” icons in the left part of the table. This
means that “license keys” have been created for the catalog items listed in the row where the
KEY icon displays.
• To examine the actual licenses, and access the options to save or print them – click on the
“Details” button in the top of the left part of the table where the system details are shown.
The following example screen should display.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 367

A.3 eLicensing

• An “example” CoLA License key is DT9D9T73E4OUY2G7 5

The number "5" is not part of the license. It is the number of users licenses available.
10. The “System Information” screen now shows the list of licenses that have been created for the
specified system.
• The above example screen is only a low-resolution example to show the general structure
of the information. Your eLicense session will be much easier to read.
• Notice the buttons at the top of the table.
• Generate New Licenses – This to “manually” generate new licenses without an order
number. This is only available for eLicense ADMIN users. Do not use this in the FIELD.
• Email Licenses – This will allow you to e-mail the license file.
• Save Licenses – This will allow you to download and save the license file to your local
file-system.
• Print Licenses – This will allow you to print a hard copy of the licenses file.
• Update List – This tool is available to manually update the applications list in eLicense
with licenses that may exist on the system, but do not exist on the eLicense page for
whatever reason. There should be no reason to use this option for this product – DO
NOT USE.
• Reconfigure - This is only available for eLicense ADMIN users. Do not use this in the
FIELD if it appears.

368 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.4 Maintenance Mode

NOTE
The above list of eLicense options is an “Administrative” Role list. Some of
these options will not even appear on the eLicense interface for “standard”
field users.

A.4 Maintenance Mode

The following information describe the steps to enter and exit the Maintenance Mode. The
maintenance mode allows the AW Server to be "isolated" from the Clients in order to perform
maintenance operations such as adding/removing Applications, or restoring configuration
parameters.
• The AW Server automatically enters the Maintenance mode after software load (Load From A
Cold). This is also the case for Manufacturing preloaded systems.

Appendices
• The Maintenance mode is not reset by a reboot.
• The system automatically enters the Maintenance mode at reboot if the Registration status
becomes invalid (I.e: expired temporary key)

A.4.1 Entering the Maintenance mode

1. Connect to the server and launch the Service Tools (login as service).
The Version Management tool which allows installing or upgrading Applications must be used
in Maintenance mode.
2. Enter the Maintenance mode under the Maintenance menu.

The Server maintenance tasks panel displays.

3. Click on the Start Maintenance tab.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 369

A.4 Maintenance Mode

4. Check if users are connected.

The example below shows two users connected.

5. If any user is connected, send a broadcast message:

a. Click on the Broadcast message tab.
b. Write a message or modify the default message to adapt it to your needs.
c. Click on Set message to broadcast it.

370 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.4 Maintenance Mode

Appendices
NOTICE
Allow a grace delay (a few minutes) for the users to save their work before
disconnecting them by entering the Maintenance mode.
6. Click on the Start maintenance tab and on Start maintenance.
A pop-up confirmation message appears.

7. Click on Yes.
Another pop-up states that you are in maintenance mode.

A.4.2 Exiting the Maintenance mode

1. In the Service maintenance tasks panel, click on the Finish maintenance tab.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 371

A.4 Maintenance Mode

2. Carefully read the mandatory conditions to be able to exit from the Maintenance mode.
3. NOTE
The Device data and Platform Configuration setup must be complete before exiting
Maintenance.
Check if the Device Data and Platform Configuration setup are complete.
If it is complete, Valid is displayed with a green background. If it is not complete, Invalid is
displayed with a red background.
4. If the Device Data and/or Platform Configuration setup are not complete, click on Device Data
and/or Platform Configuration to complete them.
See 2.16.3 Device Data on page 112 and Platform Configuration for details.
5. If there are still some background processes running (I.e: database recovery), the number and
name of active processes (maintenance tasks) are displayed on top of the Service Tools. In that
case, you will have to acknowledge the message asking you to confirm that you want to force
exiting the Maintenance mode.
6. NOTE
The AW Server must be properly registered and get its registration key before exiting
the Maintenance mode.
If the configuration has not been properly registered, the error message Registration
status is not valid. displays.

372 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.5 Using the ClamAV Anti-Virus Tool

Appendices
a. To enter the Register Configuration menu, click on the link as shown above, or on the
Register Configuration menu link.
Refer to 2.21 Job Card IST013 - Service Tools Configuration on page 200 for detailed steps
of Register Configuration tool.
b. To exit and return to the Maintenance mode main menu, click on OK.
7. Click on the Finish Maintenance button.
The message Successfully switched back server to normal mode! displays.

8. Click on OK to acknowledge.
NOTE
There may be cases where the Maintenance mode mentions (and lists) that there are
still some tasks running, and that terminating the Maintenance mode may stop them.
However, you can decide to force the end maintenance process.

A.5 Using the ClamAV Anti-Virus Tool

A.5.1 Overview
An antivirus package called ClamAV is bundled with the AW Server operating system.
By default the anti-virus is not activated, but in some circumstances, customers may request
that it is activated. However, the need for anti-virus on Linux-based systems such as the AW Server
is debatable for the following reasons:
• Linux built-in permissions apply to every file on the system, and cover read, write and execute.
Typically, software that can impact the system as a whole requires root privileges to run.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 373

A.5 Using the ClamAV Anti-Virus Tool

• Linux does not rely on file extensions to determine file properties; this avoids accidental launch
of malware.
• Unlike Windows™, Linux does not allow outsiders to execute software on the system (although
IIP is an exception to this).
• The AW Server is installed with a PFC firewall which restricts the number of open ports. IIP
services are bound only to GE IP addresses, accessed through the GE Service VPN.
• AW Server does not host email or IM clients.
• Prior to commercial release, AW Server has passed several security scans against known
vulnerabilities.
There is no recommendation to install the ClamAV Anti-Virus by default.
Nevertheless, some customers may have a site security policy that requires antivirus. In this case,
follow the Activation Procedure below to activate ClamAV on each AW Server on the site.
Once activated on a system using the parameters described below, ClamAV provides the following
protection:
• Nightly (or manual) scans of vulnerable directories. Real-time scanning is not available as this
has serious negative impact on clinical performance.
• Only directories in which malicious file can be inadvertently installed will be scanned (if using
the parameters in the instructions below). DICOM files are not scanned, as typically these are
not susceptible to attack. The scanned directories are:
• /home/
• /export/home/
• After set-up, scan logs will be located in /export/home/sdc/logfiles

A.5.2 ClamAV tool activation procedure

NOTICE
To be able to deploy ClamAV on the server, the network must have:
• Possibility to connect to internet
• HTTP Proxy defined (to obtain details, contact the local Network Administrator)

A.5.2.1 Activation Procedure

To set-up ClamAV, perform the following steps:

A.5.2.1.1 Start a Terminal tool and login as root

At the AW Server’s KVM
• Login as root
• Start the Graphical environment:
startx <Enter>
• Open the Terminal
OR
At the Client PC or FE laptop
• Open a Terminal (from the Service Tools / Tools menu)

374 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.5 Using the ClamAV Anti-Virus Tool

• Login as root
OR
At the Client PC or FE laptop
• Start "Putty".
• Putty can be downloaded from the Service Tools menu "Tools>Terminal".
• Enter the IP address of the AW Server and select <Open>
• Login as root

A.5.2.1.2 Configure crontab

• Once you are logged as root, you will use the crontab command to edit the /var/spool/cron/ A
root file.

Appendices
• crontab -e <Enter>
NOTE
By default, the text editor used is vi.
If you want to use gedit, type the following command before typing the crontab
command:
export EDITOR=gedit <Enter>
The editor window opens.
• Remove the # at the beginning of the following line:
# 0 3 * * * /usr/bin/freshclam > /export/home/sdc/logfiles/clam_scan.log; nice /usr/bin/clamscan -r -l /
export/home/sdc/logfiles/clam_scan.log /home /export/home
• Save the file and quit the editor.
The newly activated line in the crontab will set the package to scan the listed directories nightly at
03:00. A new logfile is created nightly ( /export/home/sdc/logfiles/clam_scan.log).
Previous logfiles are archived.

A.5.2.1.3 Change "clamav" directory owner

Type the following command:
• chown clam /var/lib/clamav <Enter>

A.5.2.1.4 Update virus signatures

You must now update the ClamAV virus signature database.
This requires a connection to the Internet.
1. Add the Proxy server information into the freshclam.conf file
• cd /etc <Enter>
• gedit freshclam.conf <Enter> (only available at the KVM)
OR
• vi freshclam.conf <Enter> (available both from the Client PC or FE laptop, and at the
KVM)
• Locate the HTTP proxy parameters above, uncomment (remove the # character) and modify
them so that you can read:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 375

A.5 Using the ClamAV Anti-Virus Tool

HTTPProxyServer n.nnn.nnn.nn
HTTPProxyPort xx
(where n.nnn.nnn.nn is the IP of the site proxy to use, and where xx is the corresponding port).
I.e: HTTPProxyServer 3.249.104.45
HTTPProxyPort 88
2. Execute the command-line
• freshclam <Enter>
This will download and update the latest virus definitions.
NOTE
For further details, refer to on-line documentation: http://www.clamav.net/doc/
cvd.html or the freshclam.conf man page (man freshclam.conf)
Below is an "example" message output of a successful freshclam update. Warnings can be
ignored:
ClamAV update process started at Wed Sep 8 12:16:34 2010

WARNING

Can't query current.cvd.clamav.net

WARNING

Invalid DNS reply. Falling back to HTTP mode.

Connecting via 3.249.104.45

Reading CVD header (main.cvd): OK (IMS)
main.cvd is up to date (version: 52, sigs: 704727, f-level: 44, builder: sven)
Connecting via 3.249.104.45
Reading CVD header (daily.cvd): OK
Downloading daily-11842.cdiff [100%]
Downloading daily-11843.cdiff [100%]
Downloading daily-11844.cdiff [100%]
daily.cld updated (version: 11844, sigs: 121016, f-level: 53, builder: arnaud)

WARNING

Your ClamAV installation is OUTDATED!

WARNING

Current functionality level = 51, recommended = 53

DON'T PANIC! Read http://www.clamav.net/support/faq

Connecting via 3.249.104.45

376 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.5 Using the ClamAV Anti-Virus Tool

Reading CVD header (bytecode.cvd): OK (IMS)

bytecode.cvd is up to date (version: 40, sigs: 9, f-level: 53, builder: edwin)
Database updated (825752 signatures) from database.clamav.net

WARNING

Clamd was NOT notified: Can't connect to clamd through /var/lib/clamav/

clamd-socket connect(): No such file or directory

A.5.2.1.5 Test ClamAV

A
To test that ClamAV is working, execute the command

Appendices
• clamscan -r /export/home/sdc/logfiles <Enter>
This will perform a test scan on the logfiles directory, directing output messages to the command
window.

A.5.2.1.6 Run ClamAV Manually

You may need to run ClamAV manually, either locally on the AW Server, or via a remote login (telnet
session). You can do this with a command similar to the line you added to the crontab. Example,
directing output to a logfile:
/usr/bin/freshclam > /export/home/sdc/logfiles/clam_manual_scan.log; nice clamscan -r -l /export/
home/sdc/logfiles/clam_scan.log /home /export/home
Adapt the directories scanned and the output according to specific needs. Check the scan output /
logfile and take any necessary action as explained in the previous section.

A.5.2.2 Checking ClamAV Scan Results

A.5.2.2.1 Checking infected files in ClamAV logs

You should regularly ensure that ClamAV has not detected infected files and that logfiles are
regularly checked for potential security issues.
NOTE
If infected files are detected, the "Clam AV Antivirus Software status" in the
HealthPage will display in red.
ClamAV logfiles are located in /export/home/sdc/logfiles/clam_scan.log.
At a minimum, the logfiles should be examined according to the Preventive Maintenance schedule.

NOTICE
If a virus is identified during a manual scan or in a logfile:
• Refer the issue in the first instance to the OLC. Never attempt remedial action without first
seeking advice. There is a risk that the system could become unstable, and/or client data could
be lost.
• Recommend to the customer that, although the risk from a virus on a Linux-based system is
very low, they should backup images stored on affected system(s). (It may be advisable to check
other systems on site first, to have a full picture of the problem.)

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 377

A.6 VMware Support

• Backup the AW Server’s configuration data. See 2.20 Job Card IST012 - Virtual Servers Cluster
Configuration on page 196 for details.
Normal scan output consists of messages concerning the latest ClamAV engine, followed by a list of
files scanned, followed by a summary.
NOTE
The message "This version of the ClamAV engine is outdated" may be displayed, but
this is normally not very serious. The AW Server OS includes "a" version of the ClamAV
engine.New versions of this engine may be released between OS releases, and thus the
installed version of ClamAV may not be the latest available. If it becomes necessary to
update to the most current ClamAV engine, it is the user’s responsibility to access the
website listed in the document http://www.clamav.net/doc/cvd.html and to follow the
update process.
You should pay particular attention to the "Infected files" line in the summary. Example:
----------- SCAN SUMMARY -----------
Known viruses: 824560
Engine version: 0.96
Scanned directories: 1
Scanned files: 55
Infected files: 0
Data scanned: 1.96 MB

A.5.2.2.2 Management of infected files

Identify if infected files are present in the ClamAV logfiles ( /export/home/sdc/logfiles/clam_
scan.log.).
If infected files are present, they shall be removed or quarantined:
• Contact the GEHC OLCsupport team to clean the system.
• Once the issues have been solved, remove the ClamAV logfiles.

NOTICE
If the ClamAV tool has to be deactivated, perform the above procedure prior to
deactivation.

A.5.2.3 Further Information

Refer to the ClamAV documentation online:
http://www.clamav.net/doc/cvd.html

A.6 VMware Support

This section describes:
• VMware hypervisor (ESXi) installation steps.
• VMware vSphere Client installation and startup.
• All the procedures of this manual that are performed with VMware vSphere Web Client, are
described in this section with VMware vSphere Client.

378 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

NOTE
These procedures can be performed only if the previous points are completed.
NOTE
The following procedures are given for information only, as they are dependent of the
hardware of the Hypervisor software version, and are subject to change without notice.

NOTICE
For all steps done in VMware and vSphere client, the VMware documentation should
be followed. The ESXi Hypervisor software is not supplied by GEHC.

A.6.1 VMware Hypervisor Installation

A
This section applies to the installation of the VMware ESXi 5.1 Hypervisor on a server hardware

Appendices
owned by the customer. It is similar for ESXi versions supported.
It does not cover installation of the physical server that is owned by the customer.
The following steps are under the IT Administrator responsibility.
1. Make sure the physical server is turned on and that the Hypervisor is installed and running. In
the other case, go to Step 2. If the hypervisor is already installed and running, jump to
A.6.2 vSphere Client installation on page 384.
2. Turn on the physical server and insert the VMware ESXi software media into the DVD drive.
3. The following depends on the server hardware type and the screenshots are given for example.
4. Enter the physical server BIOS setup and select Security / OS Security.
5. Enable Intel Virtualization Technology.
6. Save the setting and exit the BIOS setup.
The server reboots.
7. Select to boot from the ESXi standard Installer when prompted (default choice).

Various installation messages and screens display while the ESXi installer is loading.
The Welcome to VMware installation screen appears.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 379

A.6 VMware Support

8. Press <Enter> to continue.

The End User License agreement screen appears.

9. Press the <F11> key to accept and continue.

The message Scanning for available devices appears for a few moments.
Then, the Select a Disk to Install or Upgrade screen appears.

10. Select the disk where the Hypervisor shall be installed (see above - the physical server in our
example has 3 hard disks) and press <Enter> to continue.
The message Scanning appears for a few moments.
If a previous version of ESXi was installed, you get an additional screen to ask you if you want to
upgrade, upgrade and preserve, or overwrite.
Then, the Please Select a keyboard layout screen appears.

380 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

11. Select the keyboard layout for your server and press <Enter> to continue.
The Please enter a root password screen appears.
A

Appendices
12. Enter a root password and confirm by entering the same password, then press <Enter> to
continue.
The message Scanning system appears for a few moments.
Then the Confirm Install screen appears.

13. Press the <F11> key to confirm installation.

The message Installing ESXi appears and a task bar indicates the installation progress.

Then the Installation Complete screen appears.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 381

A.6 VMware Support

14. Eject the ESXi media from the DVD drive and press <Enter> to reboot.
The server reboots.
15. When the reboot sequence has completed, the server is ready for Network configuration. Press
the <F2> key to enter System Customization.
The login screen appears.
16. Make sure the login name (root) is selected, then arrow down to enter the root password.
17. Enter the root password and press <Enter>.
The System Customization menu appears.

18. Arrow down to Configure Management Network and press <Enter>.

19. Make sure Network Adapters is highlighted and press <Enter>.
The available Network Adapters appears.

382 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

20. Select the first network adapter and press <Space> then <Enter>. A
NOTE

Appendices
If adapters (Network ports) are not connected to the Network, Disconnected
appears as in our example. However, you can set them up and connect them later on
to the Network.
21. Arrow down to IP configuration and press <Enter>
The IP Configuration menu appears.
22. If you intend to use a static IP address:

a. Arrow down to select it then press <Space>.

b. Arrow down to IP Address field and enter the static IP address.
c. Arrow down to Subnet Mask field and enter the Netmask.
d. Arrow down to Default Gateway field and enter the default gateway IP address.
e. Press <Enter>.
23. If you intend to use a dynamic IP address:
a. Arrow down to DNS configuration and press <Enter>, then setup the desired DNS
configuration by entering the DNS server(s) information.
b. Enter a Hostname for your server.
24. Arrow down to select the 2nd Network adapter and press <Space>. Proceed as for the first
Network adapter to setup the parameters (IP address, Netmask, etc..).
25. Arrow down to select the 3rd Network adapter and press <Space>. Proceed as for the first
Network adapter to setup the parameters (IP address, Netmask, etc..).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 383

A.6 VMware Support

26. When done with Network configuration, save the Network settings and quit the Network
Management menu.
27. Press <Esc> to exit Network management menu and press the <Y> key to apply the changes.

28. To test the Network configuration, arrow down to Test Management Network and press
<Enter>.
The menu allows you to ping the default gateway.
29. Press <Enter> to start the test.

The message Pinging address #1 appears, then the result should display OK.
NOTE
If you have chosen to give your server a Static IP address, the Resolving hostname
test fails.
30. Press <Enter>.
The VMware ESXi installation on the physical server is successful.
Press <Esc> to logout.

A.6.2 vSphere Client installation

The following steps are under the IT Administrator responsibility and shall be done on the IT Admin
PC.
1. Launch an Internet navigator and connect to the physical server’s IP address.
http://<IP address of server>
I.e: http://3.249.12.230.
The VMware ESXi Welcome page appears.

384 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

Appendices
2. Make sure that the ESXi version is 5.0, 5.1, 5.5 and 6.0.
3. Click on Download vSphere Client link.
The File download security warning prompts you to choose either to run or save the VMware
application.
4. Click on Run.
The vSphere Client starts downloading. Then the vSphere installation wizard prompts you to
choose the language for installation.
5. Choose the language corresponding to your site then click on OK.
The vSphere Client Wizard starts installing.

The VMware vSphere Client Wizard welcome screen appears.

6. Click on Next to continue.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 385

A.6 VMware Support

The End-User Patent agreement screen appears.

7. Click on Next to continue.
The License agreement screen appears.
8. Read the End-user agreement.
9. Click to select the radio button I agree to the terms in the license agreement.
10. Click on Next to continue.
The Customer information screen appears.
11. Enter the User name, or keep the default Authorized User.
12. Enter the Organization, or keep the default Authorized User.
13. Click on Next to continue.
The Destination Folder screen appears.
14. If you want to choose another destination folder than the default folder, click on the Change
button.
15. Click on Next to continue.
The Ready to Install the Program screen appears.
16. Click on Install to continue.
The Installing VMware vSphere Client status and installation progress display on a status bar. It
takes several minutes to complete, then the Installation Completed screen appears.

17. Click on Finish to exit the installation wizard.

18. Make sure that a VMware vSphere Client icon has been created on your desktop.

A.6.3 vSphere Client startup - Enter the VMware license

The following steps are under the IT Administrator responsibility and shall be done on the IT Admin
PC.
1. Double-click on the VMware vSphere Client icon.
The vSphere Client login menu appears.

386 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

The IP address of the physical server is selected by default.

2. Enter the login name (root) and the login password (root password) that you have set up when A
installing the Hypervisor (see A.6.1 VMware Hypervisor Installation on page 379).

Appendices
The Certificate Warnings screen appears. You may want to select View Certificate or simply
click on the Ignore button to continue.
3. Click on Ignore to continue.
4. NOTE
If you get the following error message, you may have waited too long time before
entering the login credential.

Click on OK in the message window, then click on the Login button of the vSphere Client login
menu.
The VMware License warning appears.

5. Click on OK.
The vSphere Client administration screen appears.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 387

A.6 VMware Support

6. Click on the Configuration tab, then click on Licensed Features under the Software sub-
menu.
The vSphere Client Configuration screen appears.

7. Click on Edit on the right side of the screen.

The Assign License screen appears.

388 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

Appendices
8. Click on the Assign a new license key to this host radio button.
9. Click on the Enter Key button.
10. Enter the license key, as in the example above and click on OK in the Add License Key window.
11. Click on OK in the Assign License window.
This completes the ESXi 5.x or 6.x installation steps.

A.6.4 vSphere Client Case

The sections/steps described in this manual with VMware vSphere Web Client are described in
this section using VMware vSphere Client.
NOTE
These procedures can be performed only if the previous sections are completed.
1. To login to the vSphere Client, double-click on the VMware vSphere Client icon.
The VMware vSphere Client login screen appears.

2. Enter the IP address of the physical server.

3. Login as service.
The Certificate Warnings screen appears.
4. Select View Certificate or click on the Ignore button to continue.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 389

A.6 VMware Support

A.6.4.1 Ethernet ports Allocation

1. Start the VMware VSphere Client. Log as root and enter the root password.
The vSphere Client window displays.
2. • Select the Hypervisor and click on Configuration tab.
• Then click on Network adapters to see the available Ethernet ports and their status.
The "Network Adapters" panel displays.

You can read information about the different adapters such as their speed and the virtual switch
they are linked to.
Check how many network cards are available and which one you plan to attribute to the Virtual
machines that are going to be created.
3. • Now click on Networking
The "Standard switch" panel displays.

This view displays the current configurations of the virtual switches for this Hypervisor.
Virtual switches are entities used by vSphere to link virtual network card of a Virtual Machine to
physical network card of the server hardware. There is also a virtual switch that contains the
"Management network". This virtual switch is used to indicate what physical network card is
used for communication between the Hypervisor and the vSphere clients.
4. It is recommended to keep a dedicated virtual switch for Management Network.
Optional: if the "VM Network" displays as linked to the "Management Network", as in our
example, we need to remove it.
This can be done by doing the following:
• Click on Properties for the virtual switch.

390 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

• In the vSwitch0 properties menu, select the VM Network.

• Click on Remove and click on Yes to acknowledge the confirmation message that pops
up.
• Click on Close when done.
5. • Click on Add Networking
The "Add Network wizard" menu displays
• Select the Virtual machine radio button
• Click on Next when done.
The "Virtual Machines - Network Access" panel displays.
A

Appendices
6. Create a virtual switch for the virtual AW Server by doing the following:
• Select the next available Ethernet port (vmnic1 in our example) and click on Next
NOTE
In case of private network (see step 8 below) select a network adapter that is not
connected to the hospital network.
• Another menu displays showing the "Port Group properties" and preview of the physical
Network adapter vmnic1
• Type in the "Network label" (AWS3 VM01 Hsp Network, for example) and click on Next
• The "Ready to Complete" panel displays. Click on Finish
7. Follow the same procedure to setup other Network adapters if needed (here vmnic2 and
vmnic3) and create the vSphere standard switches that will be attributed to the Virtual
machines (AW Servers) once they have been created.
8. If the AW Server is part of a cluster of virtual AW Servers, an additional network (AW Server
Private Network) needs to be configured to ensure communication between the nodes of the
cluster.
Follow the same procedure to setup the Network adapter for the AW Server Private Network.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 391

A.6 VMware Support

NOTE
Two or more virtual AW Servers hosted on the same physical server can share the
same physical Network adapter for the AW Server Private Network.
9. When complete, the configuration should display as follows:

NOTE
In our example above, the virtual network switch "vmnic3" is not connected (red
cross) to the Hospital network as it will be used for the AW Server Private network (in
case of cluster mode), and therefore separated from the Hospital network (Broadcast
is used on the AW Server Private network).
10. This completes the Network ports allocation.

A.6.4.2 OS Template (OVF) Installation

1. • Insert the OS Template DVD into the DVD drive of the PC
• Make sure you are logged on the vSphere Client as root.
• Click on File and select Deploy OVF Template...

The "Deploy OVF Template" screen displays.

• Click on the Browse button to locate the .OVA file from the OVF Template media, then click
on Open to select.

392 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

Appendices
NOTE
The identification of the release that you are going to install may be different from
that shown in the illustration snapshots, that are given for example.
2. A confirmation screen displays.
• Click on Next.
The "OVF Template Details" screen displays.

• Click on Next.
3. The "Name and Location" screen displays.
• Enter a name for the Virtual Machine: I.e: AWS3_VM01 (for first VM) ; AWS3_VM02 (for
next) , etc.
• Click on Next.
NOTE
If you are using vCenter Server, the menu "Host/Cluster" will also be displayed after
"Name and Location" and before "Storage".Select a host or a cluster then click Next

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 393

A.6 VMware Support

4. The "Storage" screen displays.

• Choose a Datastore that will host the VM (see example below):

• Click on Next.
5. The "Disk Format "details screen displays.
• AW Server / HAPS server VM creation:
Accept the default settings (Thick Provision Lazy Zeroed).
• When done, click on Next.

NOTE
For information about Disk Format, see: https://pubs.vmware.com/vsphere-50/
index.jsp?topic=
%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-4C0F4D73-82F2-4B81-8AA7-1D
D752A8A5AC.html
6. The "Network Mapping" screen displays, to select the networks to be mapped.

394 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

Appendices
• Click on Hospital Network line and select the Destination network from the scroll down
menu. The name of the destination network corresponds to the port group you have
created or identified in 2.6.2 Ethernet ports Allocation on page 35 Section of this Job Card.
As a reminder, this port group has to be associated with at least one physical network card
dedicated to AW Server VM
• Click on Private AWS Network line and select the Destination network from the scroll
down menu.
• For a single virtual AW Server, select the same destination network as for Hospital
Network. This network will not be used by the VM
NOTE
Do not mind the message stating that "Multiple source networks are
mapped to the host network", when displaying.
• Alternatively, you can also associate this second virtual network card to a port group
with no physical network card.
• For a virtual AW Server part of a cluster, select the destination network that
corresponds to the virtual switch you created for private network.
• When done, click on Next.
NOTE
You can change these parameters at a later time by editing the VM settings if needed.
7. The "Ready to Complete" screen displays, to let you know the Virtual Machine details.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 395

A.6 VMware Support

• Click on Finish to accept and start the VM creation

8. The "Deploying <OVF Template Name>" message window displays, and a status bar lets you
know about the installation progress.
It will take several minutes to complete then the following message window will pop-up.

• Click on Close button when done.

9. Once done, eject the DVD from the drive and store it in a safe place.
10. Check that the Virtual Machine has been associated to the right physical network card by:
• Selecting the Hypervisor
• Going to the tab Configuration then selecting Networking.
The configuration should be similar to the following:

396 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

A.6.4.3 Steps to upgrade the Low Tier VM to the High Tier VM

1. • Select the (Low Tier) Virtual Machine you have created under the Hypervisor, and that you
want to upgrade to High Tier VM.
2. • Right click on the Virtual machine and select Edit settings
3. • In Hardware tab select the Memory from the list and set the memory size to 64GB.

Appendices
4. • In Hardware tab select the CPUs from the list and set the CPU number to 24.

NOTE
To achieve the proper CPU number necessary to set core numbers to 24, select 3
virtual sockets and 8 core per sockets.
5. • In Hardware tab select Network adapter 2 from the list and uncheck the Connect at
power on check-box.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 397

A.6 VMware Support

NOTICE
DO NOT disconnect Adapter 1
6. • Click on OK when done.

A.6.4.4 Image data disk creation for Standalone (Non-Integrated)

virtual AW Server
1. • Make sure the Virtual Machine is still selected.
2. • Right click on the Virtual machine and select Edit settings
3. • In Hardware tab, press the Add button.
• Select Hard Disk and press Next

4. • Select Create a new virtual disk and press Next.

398 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

Appendices
• Set the Disk size to:
• 1TB (minimum recommended size)
• 6TB (recommended and maximum supported size)
• Set Disk Provisioning
Thick Provision Eager Zeroed may be proposed by default.
• Click on the corresponding radio button to change to Thick Provision Lazy Zeroed

NOTE
To help for proper choice see: https://pubs.vmware.com/vsphere-50/index.jsp?
topic=
%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-4C0F4D73-82F2-4B81-8AA7
-1DD752A8A5AC.html
• Set Location of disk image
• Select Store with the virtual machine (default setting) and press Next OR
• Select to Specify a datastore or datastore cluster and press Next
5. • When selecting a different datastore, you will get the following screens:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 399

A.6 VMware Support

• Click on Browse, then select the appropriate datastore and press OK:
6. • Set Virtual Device Node to SCSI (1:0). The image data disk will have separate SCSI
controller.
• Set Mode to Independent and Persistent and press Next.

7. • Verify the setting and press Finish

In Hardware tab now you can see in bold a new SCSI Controller and a new Hard Disk.
8. • Click on OK to confirm and exit the installation when done.
• This completes the installation of the Virtual machine.

A.6.4.5 Create a GEHC service user account

1. Create a GE Service role with appropriate permissions:
As a first step, a new "GE Service" role shall be created with the necessary permissions to
administrate a Virtual machine.
• Click on the Home icon, then click on the Roles icon.

400 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

• Click on the Add Role icon A

2. The Add New Role menu displays.

Appendices
• Name the new role "GE Service"

• Give the following permissions (click on + to expand the sub-menus):

• Virtual machine : select to give all permissions
• When done, click on OK

The new "GE Service" role displays in the list of existing Roles.
3. • Click on the Home icon, then click on the Inventory icon.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 401

A.6 VMware Support

4. Create a Service user with GE Service role permissions:

• Make sure the Hypervisor is selected (and not the VM previously created)/
• Click on Local Users & Groups tab.

• In the Local Users & Groups menu field, right click and select Add
5. The Add New User screen displays.

• Create a local user "service" having the "GE service " role permissions
• Type service in the Login field
• Type the password twice in the User password/Password and Confirm fields
• Leave the other fields blank

402 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

• Click on OK when done

• A new user "service " displays in the list of Users
6. Assign the GE Service role permissions to the VM:
• Now click on the + sign in front of the physical server’s IP address (3.249.12.230 in our
example) to expand and display the VMs.
• Click on the Virtual machine name ("AWS31_VM01" in our example) to select.
• Click on the Permissions tab to open the menu.

Appendices
• In the Permissions Tabs menu field, right click and select Add Permission
7. The Add Permissions menu displays.

• On the Assign Role pull-down menu, select the newly created GE Service role.
The list of permissions granted to the GE Service role displays in the window.
• Click on the Add button
8. The Select Users and Groups menu displays.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 403

A.6 VMware Support

• Select the user "service" and click on the Add button

The "service" user name appears in the Users field (just below the Add button).
• Click on OK when done
9. The Assign Permissions menu displays.

The user "service" gets linked to the "GE service" role with the appropriate permissions.
• Click on OK when done
10. The User/Group versus Role screen displays a list of users, including the new user "service".

404 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

11. Finally logout from vSphere Client and login again with the "service" user credentials in order to
check that the account is operational and addresses the virtual machine created to host the
virtual AW Server: A
User: service

Appendices
Password: the password you specified in step 5.
12. This completes the installation of the GE Service account.

A.6.4.6 Setup a NTP server for the ESXi server

1. Make sure you are logged on the vSphere Client as root.
2. • Select the Hypervisor and click on the Configuration tab.

3. • Click on Time configuration under Software category.

• Click on Properties on the right side of the screen.

4. The Time Configuration screen displays.
• Click on Options.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 405

A.6 VMware Support

5. The NTP Daemon Options screen displays.

• Click to select NTP Settings.

• Click on the Add button and enter the site’s NTP server name (I.e: ntp.pool.org) or NTP
server’s IP address in the "Add NTP Server" popup window, then click on OK when done.
6. • Click back to select General and set the startup Policy to Start automatically.

• Start the NTP service by clicking on the Start button

7. Verify that the NTP service has been started and is running.

406 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

8. The GEHC FE shall be provided with the IP address of the NTP server that was used, so that he
will be able to set it in the Virtual AW Server once installed.
This completes the installation of a NTP server for the ESXi server.

A.6.4.7 Virtual machine verification

Login to the vSphere Client and display the virtual machine's characteristics: A
1. Login to the vSphere Client

Appendices
• In the vSphere Client login screen enter the IP address of the physical server.
• Login as service.
The Certificate Warnings screen displays.
You may want to select "View Certificate" or simply click on the Ignore button to continue.
2. Display virtual machine’s characteristics
• Click the Inventory icon (if not already selected).
• Click on the + sign in front of the ESXi’s IP address to expand and view the virtual machines
created.
• Click on the virtual machine name:

The IT admin may have changed the default VM name to any name at their convenience,
especially if there are several virtual AWS on the same server hardware.
If needed, right click on the virtual machine name and select Rename to change the VM
name.
• Click on the Summary tab. The virtual machine’s characteristics display.
3. • Check that the virtual machine’s characteristics are as shown in the example below:
• Red Hat 6..64-bit OS

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 407

A.6 VMware Support

• Virtual CPU: 8 vCPU (low tier VM) or 24vCPU (high tier VM) or 1vCPU (HAPS VM)
• Memory: 24GB (low tier VM) or 64GB (high tier VM) or 4GB (HAPS VM)
• Use edit settings and check that there are 1 or 2 virtual hard disks
• At least 70GB storage (for system)
• Maximum 6TB storage (for image filesystem - Standalone (Non-Integrated) virtual AW
Server only)
Memory overhead and Storage parameters values change from one configuration to another.

A.6.4.8 Map an ISO file

Map an ISO file from a DVD (or an USB media) to the virtual CD/DVD drive:
1. Select your Virtual Machine:
a. Click the Inventory icon (if not already selected) at the top of the window.
b. Click on the + button in front of the ESXi’s IP address to expand and view the virtual
machines created.
c. Click on your Virtual Machine name.
2. Map the ISO file to the virtual CD/DVD drive from the Virtual Machine Console:
a. Click on the CD/DVD icon.
b. Select CD/DVD drive 1 (or the corresponding name for your VM).
c. Select Connect to ISO image on local disk….

d. Browse to the DVD drive or the USB device of the Client PC. Select the ISO file, then click on
Open.

A.6.4.9 Disconnect an ISO file

Disconnect an iso file from the CD/DVD virtual drive:
• Select the CD icon.
• Select CD/DVD drive 1 (or the corresponding name for your VM)
• Select Disconnect from… (e. g. Disconnect from D:\AWS3.iso")
• (optional) If you get a message asking for confirmation, answer Yes.
• A confirmation message similar to the one below displays:
The remote device on <name> connected to D:\aws3.iso is disconnected.

A.6.4.10 Upgrade guest OS

Changed the Guest Operating System information:
• Launch Vsphere Client (if not done yet) and login with the GE Service account created by the IT
Admin (login: service).
• Right click on the VM in the Inventory.
• Select Edit Settings. The screen below opens.

408 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.6 VMware Support

• Select the Options tab. Select General Options line.

• In Guest Operating System, click on the drop-down list.

Appendices
• Select the Guest Operating System you want to changed to.
• Select Save to apply the new setting.

A.6.4.11 Display the Virtual Machine Console and start the virtual
machine
• Click on the Virtual Machine Console icon.
The Virtual Machine Console displays.

• Click on Power On (green arrow) of the Virtual Machine Console (if not already started).
The virtual AW Server OS starts booting up (if not already started).
NOTE
To work with the Virtual Machine Console, simply click into the console field.
To work with any other program on the PC, press <Ctrl> <Alt> simultaneously.
To get back to the Virtual Machine Console, click back into the console field.

A.6.4.12 Ensure VMware Tools are installed and running

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 409

A.7 Software Loading Through iLO

Do not skip this step, otherwise the VMware tools will not be considered as installed and you won't
be able to use the guest shutdown shortcut.
• Select the Virtual Machine and check that in the summary panel the VMware Tools are indicated
as "Running".
NOTE
If it is not the case, install the VMware Tools prior to continue with the next steps.

• Click on the Shut Down Guest button.

The following message should display:
Shut down the guest operating system of the virtual machine 'AWS3_VM01'?
Click on No unless you want to shutdown your Virtual Machine.

A.7 Software Loading Through iLO

A.7.1 Foreword
Some sites do not authorize to access the servers room once the system has been installed, unless
there is a hardware failure. These sites request that the GEHC FE proceeds with any maintenance
action such as Software loading, remotely from the Client PC, or from the FE laptop.
Though AWS service tools are remotely accessible from any client PC properly connected to the site
network, software loading shall normally be done locally at the AW server hardware, using the
server’s DVD drive.
Alternatively, OS and AWS platform software can be loaded remotely using the iLO service
processor, by "mapping" and using the Client PC media drive.
Applications loading can also be done through iLO, from their media via the Version Management
feature of the Service Tools.
See 2.17 Job Card IST009 - External Application(s) Installation on page 132 for details.

A.7.1.1 Pre-conditions
NOTICE
Remote software loading is dependent of the Network traffic. This might be an issue
on certain sites and/or at certain time of the day, when the network traffic is heavy.
• The Client PC or FE laptop should be reserved for this task, that is to say you should avoid
running other tasks or programs such as mail, to save all necessary CPU resources for the
purpose of remote software loading through the Client PC media drive.
• Preferably turn off automatic features like screen saver or automatic backup. The whole of CPU
resources of the Client PC should be dedicated to loading software from the media drive.

A.7.1.2 Before you start

• Make sure your customer has saved all patient data. Patient data is normally preserved during
software load from cold, but it is safe to have all patient data present on the AW server stored
on another system, preferably the archiving system of the site.
• Proceed with the AW Server system backup. See 3.8 Job Card UPG001 - Software Upgrade on
page 269.

410 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.7 Software Loading Through iLO

• Write down all necessary data for reinstalling the network and UPS parameters:
• hostname(s)
• IP address
• Netmask/Network prefix
• Default Gateway
• Internet routers (if applicable)
• UPS configuration

A.7.2 Starting the software load

All the following steps to be done at the Client PC or FE laptop. A

Appendices
A.7.2.1 Software load preparation with iLO 5
1. In a first navigator window, login into the Service Tools as service.
2. Go to the Maintenance mode and make sure no users are currently connected.
If users are connected, make the necessary arrangement to have them properly disconnected,
allowing a grace delay before shutdown. Refer to 3.8 Job Card UPG001 - Software Upgrade on
page 269 for details.
3. Insert the software media into the Client PC (or FE laptop).
4. In a second navigator window, login into the iLO Service processor (http://<iLO_IP_address>) as
root through the Client PC (or FE laptop).
5. Select Security > Access Settings.
The Security - Access Settings page appears.

6. Scroll down to iLO and click on the Edit icon.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 411

A.7 Software Loading Through iLO

7. In order not to be disconnected from the Service Processor during the software load process,
change the Idle connection timeout value from the default value (30mn) to Infinite and click
on OK at the bottom of the page to save the change.

8. Click on Remote Console & Media.

The Remote Console & Media - iLO Integrated Remote Console page appears.

412 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.7 Software Loading Through iLO

Appendices
9. Click on the .NET Console button.
NOTE
You may have to accept the download and installation of the Microsoft.NET piece of
software as described in the Remote Console & Media - iLO Integrated Remote
Console page.
A license key is necessary to use the iLO Integrated Remote Console. This license is factory
installed for GEHC products at HP manufacturing.
In case the iLO Integrated Remote Console would not start, refer to AW Server 3.2 Advanced
Service Manual 5771771-1EN at chapter 2, section 2.7. Check if the license is present, and
install it if not.
The iLO Integrated Remote Console opens and displays the current status of the AW Server.

NOTE
If the steps that are described here are failing and you cannot successfully use the
iLO Integrated Remote Console, use instead the Java Integrated Remote Console.
NOTE
When using the iLO Console Redirection, according to your local PC keyboard
mapping, in order to use typing the commands, it may be necessary to setup the
Client PC (or FE laptop) locales variable for keyboard.
(I.e: type : loadkeys fr <Enter> for French kbd mapping).
Variables will reset to us at the next reboot.
10. Map the Client PC media drive by clicking on Virtual Drives and select drive D: (or E: if any).

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 413

A.7 Software Loading Through iLO

You are now ready for remote software loading.

Refer to chapter 3 for more details on the software Load From cold steps.

A.7.2.2 Software load preparation with iLO 4, iLO 3 or iLO 2

NOTE
The following procedure details the steps for the iLO 4 (it is similar for iLO 3 and iLO 2).
1. In a first navigator window, login into the Service Tools as service.
2. Go to the Maintenance mode and make sure no users are currently connected.
If users are connected, make the necessary arrangement to have them properly disconnected,
allowing a grace delay before shutdown. Refer to 3.8 Job Card UPG001 - Software Upgrade on
page 269 for details.
3. Insert the software media into the Client PC (or FE laptop).
4. In a second navigator window, login into the iLO Service processor (http://<iLO_IP_address>) as
root through the Client PC (or FE laptop).
The iLO Overview page appears.

5. Expand the Administration menu and select Access Settings.

The Access Settings page appears.

414 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.7 Software Loading Through iLO

Appendices
6. In order not to be disconnected from the Service Processor during the software load process,
change the Idle connection timeout value from the default value (30mn) to Infinite and click
on Apply to save the change.
7. Expand the Remote Console menu and select Remote Console.
The Remote Console - iLO Integrated Remote Console page appears.

8. Click on the Launch button.

NOTE
For the iLO 3 or the iLO 4 service processor, you may have to accept the download
and installation of the Microsoft.NET piece of software as described in the Remote
Console - iLO Integrated Remote Console page.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 415

A.7 Software Loading Through iLO

A license key is necessary to use the iLO Integrated Remote Console. This license is factory
installed for GEHC products at HP manufacturing.
In case the iLO Integrated Remote Console would not start, refer to AW Server 3.2 Advanced
Service Manual 5771771-1EN at chapter 2, section 2.7. Check if the license is present, and
install it if not.
The iLO Integrated Remote Console opens and displays the current status of the AW Server.

NOTE
If the steps that are described here are failing and you cannot successfully use the
iLO Integrated Remote Console, use instead the Java Integrated Remote Console.
NOTE
When using the iLO Console Redirection, according to your local PC keyboard
mapping, in order to use typing the commands, it may be necessary to setup the
Client PC (or FE laptop) locales variable for keyboard.
(I.e: type : loadkeys fr <Enter> for French kbd mapping).
Variables will reset to us at the next reboot.
9. Map the Client PC media drive:
iLO 4 case: Click on Virtual Drives tab and select drive D: (or E: if any).

iLO 2 case: Click on the Virtual Media icon and select the Client PC media drive (E: in our
example). By clicking on the drive E: Mount button, the status of the media drive changes from
Mount to Umount.

416 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.7 Software Loading Through iLO

You are now ready for remote software loading.

Refer to chapter 3 for more details on the software Load From cold steps. A
A.7.2.3 Server reboot

Appendices
This procedure details the steps for iLO 5 (it is similar for iLO 4, iLO 3 and iLO 2).
1. Click on Power & Thermal, then select Server Power.

2. To shutdown the AW server, click on the Momentary Press button.

3. Click on OK to acknowledge the confirmation message.
After a few seconds, the System Power turns to OFF.

4. To restart the AW server, click on the Momentary Press button.

5. Click on OK to acknowledge the confirmation message.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 417

A.8 SNMP setup in the iLO service processor

After a few seconds, the System Power turns to ON.

6. Be prepared at the Console to select the boot from AW Server 3.2 media (Install AW Server
3.2 (VS7)). In the other case, the system would boot from the hard disk. If this is the case,
type reboot at the console and make sure you are ready to select Boot from media.
Stay around during the whole load process time in order to make sure the process will not be
interrupted for too long time and to avoid losing connection with the iLO, Console redirection
and the virtual drive.

A.7.2.4 Load From cold steps

• Proceed with the Load From Cold steps (OS + AWS software). Refer to 3.8 Job Card UPG001 -
Software Upgrade on page 269 for detailed instructions.
• When done, proceed with network and time zone setup, then restore the UPS configuration (if
applicable), and install the Applications.

A.7.2.5 Applications loading steps

There are several ways to load the Applications from media:
• locally: media inserted in the server’s DVD drive
• remotely: media inserted in the Client PC media drive
• depending on the type of media: media for hardware server or media for virtual server.
Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132 for details.
NOTE
When using remote loading via the iLO, as the HPE ProLiant DL560 Gen8 Server does not
have an internal DVD drive, you have to select /dev/sr0 instead of selecting /dev/sr1 ,
that may report a mounting error.

A.7.2.6 Final step

• When you have completed the software Load steps you may want to change the Idle
connection timeout value back to the 30 mn default value.

A.8 SNMP setup in the iLO service processor

1. At the Client PC or FE laptop, open a browser (Firefox or Internet Explorer) and type in the AW
Server’s iLO Service processor IP address.
I.e: http://3.249.15.25
2. When the login page loads appears, login as root.
3. When the iLO page appears, select Administration tab, then click on Management tab (see
examples below).
Example: iLO 4 (it is similar for iLO 2 and iLO 3)

418 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.9 Useful Commands and Tools

Appendices
4. Enable / check all Alert trap types are enabled.
HP Insight Manager may not be enabled as HP Insight option is not part of the product offering
for GEHC.
5. Make sure that Level of data returned is set to: Enabled (iLO + Server Association Data).
6. Enter the SNMP Alert Destination:
• No GE PACS case : Enter the AW Server IP address OR
• GE PACS case: Enter the SNMP Trap Receiver server IP address OR
• Site’s SNMP server case: Enter the Site’s SNMP server IP address
7. Click on Apply to save.
NOTE
If the site has an SNMP server, and would like to use it to receive traps, enter its
address in the SNMP Alert Destination field. Consult the site administrator to get
the IP address of this server.
8. To send a test alert to the setup destination logfiles, click on Send Test Alert.
9. Launch the Terminal from the Service Tools > Tools and check the /var/log/snmptraps.lo
g file.
10. Logout from the iLO Service processor by clicking on the Logout button.

A.9 Useful Commands and Tools

A.9.1 Accessing the Terminal and login as root

• Login at the Server’s KVM (Keyboard, Video-monitor, Mouse) as root

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 419

A.9 Useful Commands and Tools

>>> OR
• From the Tools menu, open the New Modal Terminal, that allows keeping the login active
when moving forward to other Service tools, and back to Terminal:

• Click on the Connect button

• Login as root
You may also download the PuTTY Terminal (to be used locally only) from the Download PuTTY link
provided in the Service Tools interface.

A.9.2 Shutting down or rebooting the server

NOTICE
Always use the shutdown command with precaution. If your system is close to the
maximum mount count or passed the 6 month delay, shutting down the server may
trigger the Filesystem check at next reboot and introduce several hours delay before
the server becomes available again. Refer to A.10 Filesystem Check on page 426 for
details.

NOTICE
Always consider checking if there are users connected, and send a warning message
allowing a grace delay of a few minutes prior to shutdown. Refer to A.4 Maintenance
Mode on page 369 - Maintenance mode.

A.9.2.1 Through the Service Tools menu

• From the Tools menu, click on the Reboot sub-menu:

420 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.9 Useful Commands and Tools

• Select the appropriate reboot or shutdown tool and acknowledge the confirmation message
that pops up.The available tools are available via the following buttons:
• Reboot AW Server
• Reboot AW Server with Filesystem check. You can force the filesystem check to launch
it at the most appropriate moment for the site.
• Shutdown AW Server

A.9.2.2 Through command lines

TO BE USED CAUTIOUSLY - NEXT REBOOT TIME MAY LAST SEVERAL HOURS
• To reboot the server, type in:
reboot <Enter>
A
• To shutdown the server, type in:

Appendices
shutdown -h 0 <Enter>
• To shutdown the server, and send a message to the connected clients:, type in:
shutAWSdown <Enter>
• To shutdown the server, and force Filesystem check at reboot, type in:
touch /forcefsck <Enter>
reboot <Enter>

A.9.3 Checking the routing table

• To check the routing table, type in:
ip route <Enter>

A.9.4 Checking the Network settings

• To check the network settings, type in:
ip addr <Enter>

A.9.5 Checking the AWS configuration

• To check the AWS configuration, type in:
/usr/local/bin/conf <Enter>
/usr/local/bin/conf -long <Enter> (gives additional configuration information)
• To check the AWS release, type in:
cat /etc/aweconfig <Enter>

A.9.6 Checking the OS release

• To check the OS release, type in:
cat /etc/aweos <Enter>

A.9.7 Launching the Internet Navigator from the Server’s KVM

The AW server is up and running.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 421

A.9 Useful Commands and Tools

1. At the Server’s KVM (Keyboard, Monitor and Mouse), login as root.

2. Preliminary mandatory setup update for HP LCD8500 KVM.
This setup update is optional for the older HP TFT7600G2 KVM.
This setup update is already done from the AW Server 3.2 Ext.1.0 release (and up), so this
step can be bypassed.
a. Change to /etc/X11 directory:
cd /etc/X11 <Enter>
b. Backup the original xorg.conf file:
cp xorg.conf xorg.conf.ori <Enter>
c. Overwrite with the new file:
cp -f xorg.conf.kvm xorg.conf <Enter>
3. Launch the Xserver to start the graphical mode.
startx <Enter>
The message Current resolution is not supported. Reverting to best display
setting. may appear. This message can be acknowledged by pressing any button on the KVM
screen.
4. When the graphical mode starts, acknowledge the warning message by ticking the Do not
show me this again checkbox and clicking on the Close button. Then, click on the Firefox icon
located at the upper left of the screen.

The Mozilla Firefox navigator page opens.

422 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.9 Useful Commands and Tools

Appendices
5. Connect to the Server by typing its IP address or its iLO/iLOM service processor address:
http://<IP_address_server> I.e: http://3.249.12.114
NOTE
Instead of entering the IP address, it is possible to enter http://localhost/ since
Mozilla Firefox is running directly on the server. It is interesting because Service Tools
can be accessed even when IP address is not configured or not working.
If you start Mozilla Firefox in secure mode (https), the following page appears:

6. Click on I Understand the Risks then on Add Exception....

The following window appears:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 423

A.9 Useful Commands and Tools

7. Check that the IP address of the AW Server is correct.

8. Make sure that the Permanently store this exception checkbox is ticked.
9. Click on the Confirm Security Exception button.
If you typed the AW Server IP address or localhost, the AW Server login interface appears:

If you typed the iLO IP address, the iLO (iLO 4 in our example) login page appears:

424 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.9 Useful Commands and Tools

Appendices
A.9.8 DNS server(s) setup - Alternate method
In case the site’s DNS server(s) have not been set up during the early installation steps (see 2.13 Job
Card IST005 - Network and Time Configuration on page 88), for example if the information was not
available at that time, you can configure it (them) through the Service Tools at a later moment.
DNS server(s) is (are) mandatory if your AW Server shall be integrated with the PACS and/or if your
site has EA3 Users authentication system.

A.9.8.1 Enter the Maintenance mode

To setup the DNS server(s), it is necessary to place the AW Server in the Maintenance mode.
1. Click on Maintenance menu then select Maintenance.
2. Proceed with the preliminary steps prior to place the system in Maintenance mode.
Refer to A.4 Maintenance Mode on page 369 for details.

A.9.8.2 Setup the DNS server(s)

1. Click on Network.
The Perform network configuration panel appears.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 425

A.10 Filesystem Check

2. Click on DNS settings.

3. Enter the DNS server(s) IP address(es) and the Domain name(s).

4. Click on Check IP to verify that the DNS server Host(s) is (are) alive.
5. Click on Apply.

A.10 Filesystem Check

A.10.1 Filesystem Check feature description

NOTE
The filesystem check impact is less significant for full or Seamless integration, as no
external disk array (D2600 DAS) is supported. The image partition used to temporarily
store the images processed on AW Server before sending them to the PACS, is part of the
DL580 / DL560 internal disks, that is to say much smaller than with the D2600 DAS,
therefore the filesystem check time is reduced to a few minutes.
The AW server is programmed to regularly run a Filesystem check upon reboot, in the following
conditions:
• After a certain numbers of boot-up: around 30 - Note that this value can be set differently
• After a certain elapsed time: typically every 6 months
These figures are available in the System Configuration section of the HealthPage:

426 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.10 Filesystem Check

When the mouse is pointed over the Mount count and fsck values, it provides a short description
about the meaning of the fields, and also mentions the rules for their coloring (i.e: yellow means less
than 5 restarts allowed before filesystem check will be started).

A
NOTICE

Appendices
The filesystem Check (fsck) is necessary to preserve the AW Server’s performances. Do
not attempt to avoid it by cycling power off to the AW Server once the process has
started. The process will start again from the beginning when turning on the server
and booting up.

NOTICE
Once the filesystem check is started there is no option to skip it.If the system is
rebooted during filesystem check, the filesystem can be damaged.
Filesystem check is launched for each partition of the AW Server, that is to say: System, Backup and
Images. However, as the System and Backup partitions are much smaller than the Image partition
(GB versus TB), fsck time will be hardly noticeable on those partitions.
Note that there may also be a shift between the mount count for System, and the mount count for
Backup and Images partition, as during the OS load process, the system is rebooted several times,
but the Image and backup partitions are not yet mounted, therefore the mount count is not effective
for them.

A.10.2 Filesystem check Side-effect "issue" description

The side-effect issue that can affect both the users or Service FE (during maintenance tasks such as
upgrade, etc.) is that when rebooting the AW Server, the filesystem check may start unexpectedly,
adding up to several hours to the boot up sequence time (depending on the number of images
stored on the hard disks).

A.10.3 Solutions to minimize the impact

1. Check when the next Filesystem check is programmed.
Refer to the System configuration section of the HealthPage as shown in section 7-1
NOTE
Alternate method to check when the next Filesystem check is programmed:
• Open the terminal under Service Tools/Tools, login as root
• Identify the proper block device corresponding to the images directory.
df –k <Enter>
I;e: /dev/xxx.................
/dev/sdb2 xxx xxx xxx xx% /export/home1

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 427

A.10 Filesystem Check

Depending on server type (DL560, DL580, ML350), image filesystem can be on sda2 or sdb2.
• Query the file system properties
tune2fs -l /dev/sdb2 <Enter> (or /dev/sda2 )
I.e: .........................
Mount count: 26
Maximum mount count: 28
Last checked: Mon May 30 15:29:08 2014
Check interval: 15552000 (6 months)
Next check after: Sat Nov 29 14:29:08 2014
In our example, we can see that the Filesystem check is scheduled to start either in 2 boot-up
(mount count is 26, and maximum count is 28) or at first boot-up after November 29th.
So in that case, warn the IT Admin that the Filesystem Check is going to occur soon, so that they
can force a check in advance over the next weekend for instance.
2. Minimize the impact for the users - Warn the IT admin asap
In order to minimize the impact for the users, the GEHC FE should warn asap the IT admin about
this feature and its side effect, and let them know the procedure for forcing the "fsck" launch at
the best possible moment - i.e: before a weekend.
3. Minimize the impact for GEHC FE
In the preceding example, we can see that the Filesystem check is scheduled to start either in 2
boot-up (mount count is 26, and maximum count is 28) or at first boot-up after November 29th.
This can be an issue for the GEHC FE if an on-site maintenance requiring to shutdown and
reboot the server several times is programmed in the coming weeks.
To minimize the impact, proceed as follows:
Case 1: The Filesystem check can be launched in advance, prior to GEHC FE on-site visit.
The mount count or the due date is getting close to filesystem check:
Contact the IT admin, and if they agree to launch in advance the Filesystem check ( i.e: during the
weekend for minimal impact for the users), remote log in to the system through ISD, open the
Terminal under Service Tools/Utilities and launch the Filesystem check manually before the weekend
prior to the GEHC FE on-site visit.
This will avoid unexpected additional time to the boot up sequence and therefore to FE on-site time.
• Reboot the server forcing the filesystem check
touch /forcefsck <Enter>
reboot <Enter> OR
• Click on the button "Reboot AW Server with filesystem check" utility in the Service Tools,
under Tools / Reboot menu.
Filesystem check can take several hours depending on the number of images stored on the system.
You can monitor the progress on the terminal (KVM) in the server room or with the console
redirection of the iLO. When Welcome to Helios screen displays, press the <Esc> key to view the
progress message.

428 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.10 Filesystem Check

After the filesystem check has completed and the AW server has rebooted, the result of the
"tune2fs" command should indicate a "Mount count" of 1 and a "Last checked" date = current date.
Case 2: The Filesystem check cannot be launched in advance to GEHC FE on-site visit. A
The mount count or the due date is getting close and the IT admin is NOT able to launch in advance

Appendices
the Filesystem check, with the minimal impact on the users, prior to GEHC FE on-site intervention
for maintenance. However it is not recommended to suppress the Filesystem check (mandatory to
maintain system files health), it is possible to postpone the check to a later date if needed.

NOTICE
These commands shall be run by the GEHC FE, locally at the KVM of the AW Server,
prior to proceed with the preventive or corrective maintenance tasks, as the "init 2"
command will stop all service tools.
• Open a root shell (Terminal: login as root)
• Stop the services used by /export/home1 and /export/backup (at least Nuevo)
init 2 <Enter>
/etc/init.d/awsservicermi stop <Enter>
/etc/init.d/servicermi stop <Enter> (only from AWS gen2 release)
• Umount /export/home1:
umount /export/home1 <Enter>
NOTE
The /export/backup filesystem is only 3GB size, so you can leave it mounted.
The filesystem check when launching will not take long to complete on a 3GB
partition.
NOTE
If an error reports that some processes are using the mount point, you can query the
process(es) ID then attempt to stop them:
lsof | grep export.home1 <Enter>
I.e: A terminal is open and connected to /export/home1/sdc_image_pool/import
directory:
bash 21386 root cwd DIR 8,18 4096 189039103 /export/home1/sdc_image_pool/
import
In this case close the terminal connected to the “import” directory or kill the process
as below:
I.e: kill -9 21386 <Enter>
Then run the “umount” command again.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 429

A.11 Hardware Return Procedure

• Then modify the Filesystem properties to postpone the Filesystem check:

Reminder: The condition for the automatic file system check routine to start at reboot is:
• mount count >= max mount count
>>> OR
• current date - last checked >= check interval
You can adjust the following (suggestion is to set at least +10 for mount counter and give at least an
extra week for the next automatic change)
• I.e: change check time interval to 200 days
tune2fs -i 200d /dev/sdb2 <Enter> (if image filesystem is on /dev/sdb2)
• I.e: change the max mount count to 40
tune2fs -c 40 /dev/sdb2 <Enter>
• Invoke the sync command to write out disk cache
sync <Enter>
• Remount the file system manually
mount /export/home1 <Enter>
The command should not report any problem, but a warning message is possible (the file
system was not umounted clearly, suggest fsck) !
• Query the file system properties to make sure the modification has been done properly
tune2fs -l /dev/sdb2 <Enter>
• Perform reboot
reboot <Enter>
Or click on the "Reboot AW Server" button in the Service Tools, under Tools / Reboot menu.

A.11 Hardware Return Procedure

A.11.1 Old hardware removal

• De-install the old hardware referring to the Vendor’s service guide instructions (High Tier server)
and /or to the old AW Server Installation manual (Low Tier server).
• Refer to AW Server 3.2 Hardware Installation Manual 5719442-1EN Chapter 1, Section 1.2 for
general safety information for rack-mountable products and weight lifting posture safety
instructions.
• Use the new server hardware packaging to send back the old system.
NOTE
When removing a Low Tier server, refer to Low Tier server handling procedure
described in the AW Server service manual.

A.11.2 Old hardware return process

Old hardware equipment shall be returned to the GEHC Recycling Centers.
Use the shipping boxes of your new hardware to pack the parts you are returning.
Hardware parts to return are:

430 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.11 Hardware Return Procedure

• Server box + power cords.

• UPS if applicable
• Monitor + video cable + power cord
• Keyboard + cable and Mouse.
• Network cables
NOTE
The addresses below are correct at the time of creation of this manual. Refer to the
latest SNAW3044 Service Note to get up-to-date addresses.

NOTICE
THE RETURNED EQUIPMENT IS DESTINED FOR RECYCLING! DO NOT RETAIN ANY A
PARTOF IT! MISSING PARTS WILL BE CHARGED!

Appendices
A.11.2.1 Return Procedure for Americas
• Use the shipping boxes of new equipment to return old material.

NOTICE
Prior to returning the equipment, contact the GE Healthcare Recycling Center to
notify them of your equipment shipment. Be sure to write the SO number on the
outside of the equipment box so that the Recycling Center can track the returns.
• Return old material and old system Configuration Form located at the beginning of this manual
to:
GEHC-RR
Attn: Part Harvest Dept.
7624 South 10 Street
Oak Creek, WI 53154-1912

A.11.2.2 Return Procedure for ASIA

• Use the shipping boxes of new equipment to return old material.
NOTE
Please contact the local Support Engineer of your region, in order to make sure of the
right address to return old material.
The following is given for information only, and is subject to change.
Make sure it is still appropriate by contacting your local support.

A.11.2.3 Return address for Korea

Samsung GE Medical Systems
Mr Jae Young Cho (K0125)
65–1 Sangdaewong–dong, Chungwong–ku
Sungnam–si, Kyunggi–do
KOREA 462–120

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 431

A.11 Hardware Return Procedure

A.11.2.4 Return address for Australia / New Zealand

GE Medical Systems,
Attn: Max Cardew
Unit 6, 13 Lord Street,
Bontany, NSW 2019
Sydney, AUSTRALIA

A.11.2.5 Return address for GEMS

NOTE
Please contact your Regional Service Head Quarters, to get instructions for returning the
old Systems hardware.

A.11.2.6 Return address for East Asia countries

GE Pacific PTE Ltd
Attn: Bryan Heaney
298 Tiong Bahru Road, 15–01/06
Central Plaza, SINGAPORE 168730

A.11.2.7 Return procedure for other GEHC–Asia countries.

NOTE
Please contact your Regional Service Head Quarters, to get instructions for returning the
old Systems hardware.

A.11.2.8 Return Procedure for Europe

• Use the shipping boxes of new equipment to return old material.
• Return old material and old system Configuration Form located at the beginning of this manual
to:
Geodis Logistics - Harvest
Bat EVL2 Quai 48 - ZI la pièce de la remise
Route de Corbeil - CD26 - 91090 Lisses - France
• If you are sending from the Region France, ship by the usual Spare Parts return process: (Sernam
– Megastore Evry)
• If you are sending from other Regions, use the shuttles to return the Spare Parts. Regional
Distribution point or Local depots:
Antwerpen – Frankfurt – London – Madrid – Milano
Athina – Kobenhavn – Istanbul – Kriens – Lisboa – Mockba – Napoli – Stockholm – Wien
Transport costs will be charged by the ”Recycling Center”. Send the invoice to:
BUC, Compta fournisseur, Ref: Recyclage

432 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

A.12 AW Server Integration in CT/MR Console

Environment
The AW Server can be integrated within the CT/MR Console Environment:
• Within the CT/MR Smart Subscription on Edison HealthLink.
In these environments, the installation procedure is common for CT and MR.
• For CT, the AW Server Client is installed on the CT Console.
• For MR, the AW Server Clients are installed on the customer desktops/laptops.
• Within CT Nano-Cloud Console. A
In this environment the installation procedure is specific. The AW Server Client is installed in the

Appendices
CT Console.
In these environments the OS, the AW Server software and the applications are common for CT and
MR (for sure the specific modality applications are installed only on the corresponding environment),
and are installed in a virtual environment.
In these environments the OS and AW Server software are packaged in a pre-installed image
delivered on USB device and used to install and configure the AW Server.
In these environments the AW Server is configured in the DICOM Direct Connect mode and retrieves
the patients/images data from the CT/MR Console database.
NOTE
Always refer to the relevant service documentation for details.

A.12.1 AW Server Integration in CT/MR Smart Subscription on

Edison HealthLink
The AW Server can be integrated within the CT/MR Smart Subscription on Edison HealthLink.
The Edison HealthLink is installed on an HP ML350 G10 server and hosts the AW Server Virtual
Machine.
The AW Server Client is integrated within the CT Console Client or in a customer desktop/laptop for
MR. It allows console users to do advanced processing with AW Applications remotely.
Prerequisite:
1. Installation of the Edison platform software has been completed.
2. CT option key [SmartSubscription -Connection] is installed
NOTE
This prerequisite is for the CT Console only.
3. Edison Admin Console is available. Also requires [login/password] preparation for use.
4. USB Media containing the combined OS and the AW Server qcow2 image template is necessary.
5. USB Media with Volume Viewer Application is necessary.
6. One Ethernet cable is required to connect the FE laptop to the Edison private network.
Reference Document:
• Edison HealthLink Site Installation Manual (MyWorkshop document DOC2300779)
• Edison HealthLink Platform Service Guide (MyWorkshop document DOC2300778)

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 433

A.12 AW Server Integration in CT/MR Console Environment

• AW Server Feature Connection

• CT Scanner Service Method
• AW Server 3.2 Installation and Service Manual 5719443-1EN

A.12.1.1 FE Laptop Setup

The FE laptop shall be able to connect to the Edison HealthLink using private network static IP
172.16.0.200. Refer to the [Laptop Setup to static 172.16.0.200] section in [Edison HealthLink
Site Installation Manual] for full procedure description.

A.12.1.2 AW Server Installation

A.12.1.2.1 Virtual Machine creation and AW Server deployment

All steps are performed and completed by the GE FE.
The VM will be created with the AW Server loaded from the USB key containing the combined OS
and the AW Server qcow2 image template, as well as a file containing the AW Server configuration.
Use the media (USB key) AW Server 3.2 Ext. 3.4 SW and Docs for Virtual Machine: 5818084
1. Open a console/terminal on the Edison HealthLink:
• From the FE laptop, open a Web Browser (Firefox or Internet Explorer), type in the iLO IP
address and login to the iLO.
Check with IT team for iLO IP address, username and password.
• Start the Java Web Start Console (console/terminal).
• Login to the console/terminal using the Controller Default credential.
Refer to the [iLO Console and Java Web Start Console] section in [Edison HealthLink Site
Installation Manual] for the full procedure description.
2. Virtual Machine creation and AW Server Deployment
a. Insert the USB key into the Edison HealthLink.
b. Identify the USB device by typing the following command in the console/terminal:
sudo fdisk -l <Enter>
NOTE
The first time you use sudo command you may have to enter the root password.
Type in the Controller Default password.
The last USB device inserted will be displayed as the last item in the output of the
command. (e.g. "/dev/sdaa1).

Record the USB device name (here /dev/sdaa1), as it will be used in below commands.

434 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

c. Mount the USB key in read-only using the following command:

sudo mkdir -p /opt/backups/mnt/app_usb <Enter>
sudo mount /dev/sdaa1 /opt/backups/mnt/app_usb <Enter>
NOTE
Here we assume that the USB partition is /dev/sdaa1. If it is not the case,
replace /dev/sdaa1 by the right USB partition as identified in step b.
sudo mkdir -p /opt/backups/mnt/awserver_package <Enter>
sudo mount -ro loop /opt/backups/mnt/app_usb/
aws-3.2-3.4-1.qcow2.iso /opt/backups/mnt/awserver_package <Enter>
d. Create the Virtual Machine and deploy the AW Server using the following command:
A
edison vm install -p /opt/backups/mnt/awserver_package <Enter>

Appendices
Wait for the message "VM Installation successfully completed......." to
display (roughly 5mn).

Press <Enter> to return to prompt.

e. Unmount the USB partition:
sudo umount /opt/backups/mnt/app_usb <Enter>
f. Remove the USB key from the Edison HealthLink:
Ignore the error message when removing the USB media.
Press <Enter> to return to prompt.
3. This completes the VM creation with the AW Server deployment.

A.12.1.2.2 Display AW Server Console

The below steps described the process to display the AW Server Console from the Edison
HealthLink.
1. Login to Horizon OAM Titanium Cloud using edison-usr credential:
NOTE
Log to Horizon OAM Titanium Cloud from a Web Browser with the URL: https://
<OAM IP Address>
Refer to the [Horizon/OAM/Titanium Cloud Dashboard] section in [Edison HealthLink
Platform Service Guide] for login to OAM.
2. Move to Project / Compute / Instances.
3. Click on aw-server-0 Instance Name.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 435

A.12 AW Server Integration in CT/MR Console Environment

4. Click on Console tab and on Click here to show only console.

Press <Enter> if blank display appears.

5. The AW Server console displays:

A.12.1.2.3 Configuring the HA Proxy for AW Server

In order to be able to access the AW Server through the Edison HealthLink, the HA Proxy shall be
configured to forward the ports needed by the AW Server.
Refer to [For AW Server] in the [Application Software Installation] section in [Edison
HealthLink Site Installation Manual].
1. To configure the HA Proxy for AW Server, in the console/terminal, type the following commands:
cd /home/wrsroot/kindler/site_utils <Enter>
sudo haproxy_update.py awserver <Enter>
NOTE
In some Edison HealthLink version the site_utils folder may not exist and the
command may have another extension. In this case type the following commands
instead:

436 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

cd /home/wrsroot/kindler/shell_scripts <Enter>
sudo sh haproxy_update.sh awserver <Enter>

A.12.1.2.4 Update static routing file on AW Server

NOTE
This section is not applicable for the MR Smart Subscription on Edison HealthLink.
1. Display the AW Server Console:
Refer to the A.12.1.2.2 Display AW Server Console on page 435.
2. In the AW Server console, login as root.
3. Create the file route-eth0 with the following text, as follow: A
echo "172.16.0.0/24 via 192.168.103.254 dev eth0" >> /etc/sysconfig/

Appendices
network-scripts/route-eth0 <Enter>
4. Restart the network service by typing the following command:
service network restart <Enter>
5. Confirm that the 172.16.0.0 has been added to the destination by typing the following
command:
route <Enter>

6. Confirm that ping connectivity is successful by typing the following command:

ping 172.16.0.1 <Enter>

7. Return to login mode by typing the following command:

exit <Enter>

A.12.1.2.5 AW Server Configuration

All steps are performed and completed by the GE FE.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 437

A.12 AW Server Integration in CT/MR Console Environment

This section describes the configuration needed for the AW Server within the Edison HealthLink.

A.12.1.2.5.1 Allocate Floating IP Address for AW Server

Allocate floating public IP address for the AW Server.
1. Get the two Server IP addresses of the Edison HealthLink:
a. Login to Horizon OAM Titanium Cloud using edison-usr credential:
NOTE
Log to Horizon OAM Titanium Cloud from a Web Browser with the URL:
https://<OAM IP Address>
Refer to the [Horizon/OAM/Titanium Cloud Dashboard] section in [Edison HealthLink
Platform Service Guide] for login to OAM.
b. Record the following two IP Addresses:
• Edison proxy floating IP (external-net0): _________________
• Edison private proxy floating IP (external-net1): _________________
Refer to the [Verify Edison IP Address] section in [Edison HealthLink Platform Service
Guide] for login to OAM.
Figure A-1 Example

2. Allocate Floating IP Address (Public) for AW Server:

Refer to the [Allocate and Associate a Floating IP Address to an IP Instance] section in
[Edison HealthLink Platform Service Guide] for Basic procedure.
a. Move to Project / Network / Floating IPs.

438 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

Appendices
b. Click on Allocate IP To Project.

c. The following window displays:

Select externalnet-0 and click on Allocate IP to proceed.

After a few seconds, the new public IP address is added to the Floating IPs list.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 439

A.12 AW Server Integration in CT/MR Console Environment

Record the added New Public IP Address number.

d. Move to Project / Compute / Instances.
e. Click on aw-server-0 Instance Name.

f. Move to Actions and select Associate Floating IP in the pull down menu:

g. Select the previously recorded IP Address in the pull down menu:

h. Move to Project / Compute / Instances.

Check that the Edison Proxy Floating IP is added on the aw-server-0:

440 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

Appendices
i. Move to Project / Network / Floating IPs.
Confirm that the Edison Proxy IP Address is added at the aw-server-0:

A.12.1.2.5.2 Network and Time Configuration

1. Display the AW Server Console. Refer to A.12.1.2.2 Display AW Server Console on page 435.
2. In the AW Server console, login as root.
3. In the console type the following command to see the ethernet interfaces:
ip addr <Enter>
Check that for eth0:
• The MAC Address (link/ether) is assigned (not blank).
• The IP address (inet) is the same as the one which was previously allocated.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 441

A.12 AW Server Integration in CT/MR Console Environment

4. Configure the network as described in 2.13 Job Card IST005 - Network and Time Configuration
on page 88 section 2.13.1 Network Configuration on page 88.
Change the Hostname and check that the IP address is the same as in step 3.
5. Configure the date and time as described in 2.13 Job Card IST005 - Network and Time
Configuration on page 88 section 2.13.2 Date and Time Configuration on page 91
6. Reboot the AW Server as described in 2.13 Job Card IST005 - Network and Time Configuration
on page 88 section 2.13.3 Reboot the AW Server on page 93.

A.12.1.2.5.3 Launching Service Tools

The Service Tools allows to configure the AW Server.
1. At the FE Laptop, open any Web Browser and type in the AW Server’s IP address and port #:
https://<Edison Private proxy floating IP address>:5443 <Enter>
2. Log in to the Service Tools as service.
Refer to 2.15 Job Card IST007 - Service Tools Login on page 102 for full details.

A.12.1.2.5.4 Restore a saved Configuration

1. If the installation is part of an upgrade, restore the saved configuration as described in 3.8 Job
Card UPG001 - Software Upgrade on page 269 at 3.8.7.2 Restoration steps on page 293.
NOTE
During the restoration, if the VM has been deleted, a message will popup mentioning
that the license ID of the system does not match with license ID in the back up file.
Ignore the message and close the popup.

A.12.1.2.5.5 Initial Configuration

1. Proceed with Device Data setting as described in 2.16 Job Card IST008 - Initial Configuration on
page 108 at 2.16.3 Device Data on page 112
2. Proceed with other AW Server initial configuration if needed (except for Auto Delete Settings,
Platform Configuration and Licensing which are described below) as described in 2.16 Job
Card IST008 - Initial Configuration on page 108.

A.12.1.2.5.6 Auto Delete Settings

442 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

1. Configure the Auto Delete to avoid running out of space on the images disk, as described in
2.16 Job Card IST008 - Initial Configuration on page 108 at 2.16.7.1 Auto Delete settings on page
116.
• Set Auto delete status to On
• Set Start when image database reaches to 95%
• Set Stop when image database reaches to 70%
• Set Remove image(s) from system database older than to 2 hours
• Set Start auto delete process every to 2 hours

A.12.1.2.5.7 Platform Configuration

A
1. Configure the platform as described in 2.16 Job Card IST008 - Initial Configuration on page 108

Appendices
at 2.16.9 Platform Configuration on page 118. Also refer to 2.19 Job Card IST011 - Integration on
page 172 at 2.19.4 DICOM Direct Connect integration on page 190 for the integration mode.
a. Platform Configuration:
• Select AW Server 40.000 slices (SdC_Low_Tier_Premium) for Platform Enabler
(DICOM Direct Connect integration case).
• Enter the Platform License key.
b. Scalability:
• Set Cluster settings to Select Single Mode.
c. Integration:
• Select DICOM Direct Connect for Integration enabler.
• Enter the License key.
• Set the Authentication URL:
• For CT Console: http://172.16.0.1:9999/host.
• For MR Console: The public IP address of the MR console.

A.12.1.2.5.8 Licensing Configuration

1. Configure the Cola License Server as described in 2.16 Job Card IST008 - Initial Configuration on
page 108 at 2.16.10.3 CoLA License server on page 124.
• Check Built-in for Local License Server.
• Enter the CoLA license key (NodeLock key) in Server Enabler field.
2. Configure the the Floating License as described in 2.17 Job Card IST009 - External Application(s)
Installation on page 132 at 2.17.3 Application(s) Licensing setup on page 134.
Generate the Application Floating Licenses and install them.

A.12.1.2.5.9 Applications Installation and Activation

1. Insert the USB key into the FE laptop.
2. Load the applications from the media as described in:
Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132 at 2.17.5 Load
the Application(s) from media on page 137
3. Install the applications as described in:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 443

A.12 AW Server Integration in CT/MR Console Environment

Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132 at 2.17.6 Install
the Application(s) on page 143
4. Activate the applications as described in:
Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132 at
2.17.7 Activate the Application(s) on page 146

A.12.1.2.5.10 Administrative Configuration

1. Proceed with the AW Server administrative configuration (except for DICOM Hosts
Configuration and End of Review which are described below) as described in 2.18 Job Card
IST010 - Administrative Configuration on page 148.

A.12.1.2.5.11 DICOM Hosts Configuration

1. Configure the CT/MR Console as a DICOM host as described in 2.18 Job Card IST010 -
Administrative Configuration on page 148 at 2.18.1 DICOM Hosts Configuration on page 149.
a. Enter the mandatory fields.
b. Set the IP Address to the eth0 IP address of CT console.
c. Set the Port number to 4006.
2. Configure others DICOM hosts if needed as described in 2.18 Job Card IST010 - Administrative
Configuration on page 148 at 2.18.1 DICOM Hosts Configuration on page 149.

A.12.1.2.5.12 End of Review

1. Configure the End of Review to automatically sends processed images to a DICOM host when
exiting the applications, as described in 2.18 Job Card IST010 - Administrative Configuration on
page 148 at 2.18.9 End of Review on page 170.
a. Check the CT Console Host name.
b. Set the Type to all.
c. Set the Modality to CT.

A.12.1.2.5.13 System Configuration Registration

1. Proceed with the configuration registration as described in 2.21 Job Card IST013 - Service Tools
Configuration on page 200 at 2.21.1 System Configuration Registration on page 200.

A.12.1.2.5.14 Backup the Configuration

1. Backup the Network and the System configuration as described in 2.25 Job Card IST016 -
System Handover to Customer on page 246 at 2.25.2 Backup Parameters and Settings on page
249.

A.12.1.2.5.15 Exiting Maintenance Mode

1. Exit the maintenance mode as described in A.4.2 Exiting the Maintenance mode on page 371.
This complete the AW Server installation and configuration.
2. Install CT option:

444 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

NOTE
This option is for the CT Console only.
• CT Console: Move to the CT Scanner configuration and install the [SmartSubscription -AW
Server] CT option, to enable the functionality of the AW Server VM and the CT Scanner.
Refer to [Smart Subscription /AW Server Feature Connection] in CT Scanner related
Service method.
3. AW Server Client installation. Refer to A.12.1.4 AW Server Client installation on page 445

A.12.1.3 Software Upgrade

A.12.1.3.1 AW Server upgrade A

All steps are performed and completed by the GE FE.

Appendices
This section describes the upgrade/update of the AW Server integrated within the Edison
HealthLink.
1. FE Laptop Setup
The FE laptop shall be able to connect to the Edison HealthLink using private network static IP
172.16.0.200. Refer to the [Laptop Setup to static 172.16.0.200] section in [Edison
HealthLink Site Installation Manual] for full procedure description.
2. Launch the Service Tools. Refer to A.12.1.2.5.3 Launching Service Tools on page 442
3. Backup the Network and the System configuration
Refer to 2.25 Job Card IST016 - System Handover to Customer on page 246 at 2.25.2 Backup
Parameters and Settings on page 249.
4. Delete the Virtual Machine from the Edison HealthLink
Refer to the [Edison HealthLink Platform Service Guide] for the full procedure description.
5. Proceed to the AW Server installation
Refer to A.12.1.2 AW Server Installation on page 434.
NOTE
In this procedure you will be asked to restore the configuration. So, some
configuration parameters will be set and the configuration of the AW Server will be
lighter. However, the licenses shall be generated again as the VM has been deleted
and the license ID has changed.
6. This completes the AW Server upgrade.

A.12.1.3.2 Applications upgrade

All steps are performed and completed by the GE FE.
This section describes the upgrade/update of the applications running on the AW Server integrated
within the Edison HealthLink.
1. Proceed to the Applications Installation and Activation
Refer to A.12.1.2.5.9 Applications Installation and Activation on page 443

A.12.1.4 AW Server Client installation

All steps are performed and completed by the GE FE.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 445

A.12 AW Server Integration in CT/MR Console Environment

NOTE
For the CT Console, the AW Server Client is already installed with the CT option key
[SmartSubscription -Connection] installation.
NOTE
For the MR Console, the AW Server Clients are installed on the customer desktops/
laptops. Refer to 2.22.1.1 Windows TM Client PC installation Procedure on page 205
The below steps describe the AW Server Client update in the CT Console, in case it needs to be
updated without a full reinstallation of the AW Server.
1. Open a console/terminal on the CT Console:
• From the FE laptop, open a Web Browser (Firefox or Internet Explorer), type in the iLO IP
address and login to the iLO.
Check with IT team for iLO IP address, username and password.
• Start the Java Web Start Console (console/terminal).
• Login to the console/terminal using the Controller Default credential.
Refer to the [iLO Console and Java Web Start Console] section in [Edison HealthLink Site
Installation Manual] for the full procedure description.
2. Uninstall the AW Server Client previously installed
If an AW Server Client is already installed, uninstall it as follow:
• In the console type the following commands:
rpm -qa | grep AWE <Enter>
This command displays the installed AW Server Client package(s).
rpm -ql AWE-[VERSION]-solo-[VERSION]-[BUILDHASH].i386 | head -1
<Enter>
This command displays the location of the AW Server Client package(s) installed.
sudo rpm -e AWE-[VERSION]-solo-[VERSION]-[BUILDHASH].i386 <Enter>
This command uninstall the AW Server Client package(s) installed.
[VERSION] and [BUILDHASH] are the version and the build number of the AW Server
Client displayed in the result of the first command.
3. Install the AW Server Client
• Download the Linux Client Software installer by typing the following command:
wget http://<AW Server IP address>/client/AWE-3.2-solo.i386.rpm
<Enter>
• Check the package integrity by typing the following command:
rpm --checksig AWE-3.2-solo.i386.rpm <Enter>
AWE-3.2-solo.i386.rpm: sha1 md5 OK
• Install the AW Server Client by typing the following command:
sudo rpm -ivh --prefix=/usr/g/ctuser/solo_3.2_3.4 AWE-3.2-
solo.i386.rpm <Enter>
NOTE
By default the package is located in /usr/share/solo3 directory. /usr/g/ctu
ser/solo_3.2_3.4 is the location where we want to relocate the package.
4. Hide the AW Server Client window decoration

446 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

• Log in the console as root:

su - <Enter>
• Set the writing rights of the solo.ini file as follow:
chmod a+w /usr/share/solo3/solo.ini <Enter>
OR
chmod a+w /usr/g/ctuser/solo_3.2_3.4/solo.ini <Enter>
• Edit the solo.ini file and append the following line:
vi /usr/share/solo3/solo.ini <Enter>
OR
vi /usr/g/ctuser/solo_3.2_3.4/solo.ini <Enter>
A

Appendices
Add the following line at the end of the file:
-Dui.hideDecoration=true
Save the file and quit the editor.
• Log out from root by typing:
exit <Enter>
5. Check AW Server Client connectivity
• Start the AW Server Client in standalone mode by typing the following command:
/usr/share/solo3/scripts/start.solo <Enter>
OR
/usr/g/ctuser/solo_3.2_3.4/scripts/start.solo <Enter>
• In the interface that displays, enter the IP address of the AW Server and the username:
standard.
You should be able to start the AW Server Client in standalone mode.
6. This completes the AW Server Client installation/update.

A.12.2 AW Server Integration in CT Nano-Cloud

The AW Server can be integrated within the CT Nano-Cloud environment.
CT Nano-Cloud environment is a CT Console that hosts the AW Server Virtual Machine. It allows
console users to do advanced processing with AW Applications remotely from the CT Console.
The AW Server Client is integrated within the CT Console Client.
Prerequisite:
1. Installation of the CT Nano-Cloud software has been completed.
2. USB Media containing the combined OS and the AW Server qcow2 image template is necessary.
3. USB Media with Volume Viewer Application is necessary.
Reference Document:
• Refer to the CT Nano-Cloud service documentation.
• AW Server 3.2 Installation & Service Manual.

A.12.2.1 AW Server Installation

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 447

A.12 AW Server Integration in CT/MR Console Environment

A.12.2.1.1 Virtual Machine creation and AW Server deployment

All steps are performed and completed by the GE FE.
The VM will be created with the AW Server loaded from the USB key containing the combined OS
and the AW Server qcow2 image template.
Use the media (USB key) AW Server 3.2 Ext. 3.4 SW and Docs for Virtual Machine 58
18084.
1. Open a console/terminal on the CT Console:
• From the FE laptop, open a Web Browser (Firefox or Internet Explorer), type in the iLO IP
address and login to the iLO.
Check with IT team for iLO IP address, username and password.
• Start the Java Web Start Console (console/terminal).
• Login to the console/terminal using the Controller Default credential.
Refer to the [iLO Console and Java Web Start Console] section in [Edison HealthLink Site
Installation Manual] for the full procedure description.
2. Get the CT Console available/usable virtual IP address, private subnet and network
prefix from the IT Admin, to avoid subnet conflict with the created virtual subnet.
NOTE
The CT Console virtual IP address, virtual private subnet and network prefix can be
found after the VM creation and the AW Server deployment with the following
command:
ip addr show virbr1 <Enter>
See below screenshot as an example.

• CT Console virtual IP address (in yellow): 192.168.101.1 for example

• Virtual private subnet (in red): 192.168.101 for example
• Network prefix (in blue): 24 for example
3. Virtual Machine creation and AW Server Deployment
a. Insert the USB key into the CT Console.
b. Identify the USB device by typing the following command in the console/terminal:
sudo fdisk -l <Enter>
NOTE
The first time you use sudo command you may have to enter the root password.
Type in the Controller Default password.
The last USB device inserted will be displayed as the last item in the output of the
command. (e.g. "/dev/sdaa1).

448 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

Record the USB device name (here /dev/sdaa1), as it will be used in below commands.
c. Create the mount point for the USB key:
A
sudo mkdir /mnt/ntfs <Enter>

Appendices
d. Mount the USB partition by typing:
sudo mount -t ntfs-3g /dev/sdaa1 /mnt/ntfs <Enter>
NOTE
Here we assume that the USB partition is /dev/sdaa1. If it is not the case,
replace /dev/sdaa1 by the right USB partition as identified in step b.
e. Copy the qcow2 image file on the CT Console:
mkdir -p /usr/g/AWS_VM <Enter>
sudo cp /mnt/ntfs/*.qcow2* /usr/g/AWS_VM <Enter>
NOTE
It may take 5 to 10 mn to complete.
sudo chown ctuser /usr/g/AWS_VM/*.qcow2* <Enter>
f. Unmount the USB partition:
sudo umount /mnt/ntfs <Enter>
g. Remove the USB key from the CT Console:
Ignore the error message when removing the USB media.
Press <Enter> to return to prompt.
h. Remove the directory created as a mount point:
sudo rm -fr /mnt/ntfs <Enter>
i. Create the Virtual Machine and deploy the AW Server using the following commands:
cd /usr/g/ctuser/VMDeploy/scripts <Enter>
deployVMGUI.sh <Enter>
The following window displays:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 449

A.12 AW Server Integration in CT/MR Console Environment

j. Select the Nano Type: TAI-X 4, NGX 16k, NGX 12k.

NOTE
It will automatically adjust the current Memory and Max Memory values to the
given Nano-Cloud configuration type.
k. Check that the following fields are not empty and contain the correct information:
• Autostart is checked.
• Vcpu number: 8
• Current Memory
• MaxMemory: 24GB for TAI-X, 26GB for NGX or 32GB for NGX Frontier.
• VM graphical console port: 5908
• Destination directory: /usr/g/ctuser/AWSVM
If the values are not correct adjust them.
l. Enter or update the Vm name.
m. Check that Custom virt private subnet contains the correct address:
The private subnet default value is 192.168.w.x/y. The 192.168 part is fixed.
Check the third number w and the network prefix y from the virtual private subnet and the
network prefix noted in Step 2. If they are different, change them:
• Check the Custom virt private subnet check box.
• Update the third number and network prefix values.
n. Select the Image source.
Click on the Browse buttton and select the /usr/g/AWS_VM/*.qcow2 image.
o. In case of software upgrade, if the Virtual Machine has not been deleted, reinstall/replace
the VM image disk:
Check the Just reinstall/replace the VM image disk checkbox.

The tool will check if the Vm name specified exists and it will replace the image disk for a
given VM with the image specified by the Image source.

450 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

NOTE
By this method the VM remain untouched, just the image disk will be replaced.
p. Click on the Deploy button to create the Virtual Machine and deploy the AW Server.
Wait until the command line ask you to enter the password, enter the password and press
<Enter>.
Wait until the VM Deployment window auto-closed.
This completes the VM creation with the AW Server deployment.

A.12.2.1.2 Display AW Server Console

The below steps described the process to display the AW Server Console from the CT Console. A
1. Display the Virtual Machine Manager:

Appendices
Type the following command in the CT Console terminal:
sudo virt-manager <Enter>

2. Display the AW Server console:

Double click on the virtual machine. The AW Server console displays.

A.12.2.1.3 AW Server Configuration

All steps are performed and completed by the GE FE.
This section describes the configuration needed for the AW Server within the CT Nano-Cloud.

A.12.2.1.3.1 Network and Time Configuration

1. Display the AW Server Console. Refer to the A.12.2.1.2 Display AW Server Console on page 451.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 451

A.12 AW Server Integration in CT/MR Console Environment

2. In the AW Server console, login as root.

3. Configure the network as described in 2.13 Job Card IST005 - Network and Time Configuration
on page 88 section 2.13.1 Network Configuration on page 88.
Set the Hostname to aws and set the IP address to <virtual private subnet>.5
(<virtual private subnet> noted in A.12.2.1.1 Virtual Machine creation and AW Server
deployment on page 448, Step 2).
For instance: 192.168.101.5.
4. Configure the date and time as described in 2.13 Job Card IST005 - Network and Time
Configuration on page 88 section 2.13.2 Date and Time Configuration on page 91
5. Reboot the AW Server as described in 2.13 Job Card IST005 - Network and Time Configuration
on page 88 section 2.13.3 Reboot the AW Server on page 93.
6. Update the modgecsi.conf configuration file.
a. Edit the modgecsi.conf file. Type in the AW Server Console:
sudo vi /etc/httpd/conf.d/modgecsi.conf <Enter>
b. In the file that opens, insert the following lines at the right location as described in the
picture below:
Order Allow,Deny
Allow from <CT Console virtual IP address> (noted in section A.12.2.1.1 Virtual
Machine creation and AW Server deployment on page 448, Step 2)
For instance: Allow from 192.168.101.1

c. Save the file and quit the editor.

A.12.2.1.3.2 Launching Service Tools

The Service Tools allows to configure the AW Server.

452 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

1. At the FE Laptop, connect to the CT Console using ISD/FFA.

2. Start the Service Desktop interface using the CSD tool:

Appendices
3. Click on Launch AWS Service Tools to start the Servic Tools.
4. Log in to the Service Tools as service.
NOTE
If you do not have the Insite/RSvP connectivity, you should establish a ssh connection
to the CT Console with X11 tunnel. This can be done with PuTTY (or equivalent tool)
by enabling SSH X11 forwarding option. Then you can login with ssh to the CT
Console and type in the terminal: firefox <virtual private subnet>.5
(noted in section A.12.2.1.1 Virtual Machine creation and AW Server deployment on
page 448, Step 2).
For instance: firefox 192.168.101.5
Refer to 2.15 Job Card IST007 - Service Tools Login on page 102 for full details.

A.12.2.1.3.3 Restore a saved Configuration

1. If the installation is part of an upgrade, restore the saved configuration as described in 3.8 Job
Card UPG001 - Software Upgrade on page 269 at 3.8.7.2 Restoration steps on page 293.
NOTE
During the restoration, if the VM has been deleted, a message will popup mentioning
that the license ID of the system does not match with license ID in the back up file.
Ignore the message and close the popup.

A.12.2.1.3.4 Initial Configuration

1. Proceed with Device Data setting as described in 2.16 Job Card IST008 - Initial Configuration on
page 108 at 2.16.3 Device Data on page 112

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 453

A.12 AW Server Integration in CT/MR Console Environment

2. Proceed with other AW Server initial configuration if needed (except for Auto Delete Settings,
Platform Configuration and Licensing which are described below) as described in 2.16 Job
Card IST008 - Initial Configuration on page 108.

A.12.2.1.3.5 Auto Delete Settings

1. Configure the Auto Delete to avoid running out of space on the images disk, as described in
2.16 Job Card IST008 - Initial Configuration on page 108 at 2.16.7.1 Auto Delete settings on page
116.
• Set Auto delete status to On
• Set Start when image database reaches to 95%
• Set Stop when image database reaches to 70%
• Set Remove image(s) from system database older than to 2 hours
• Set Start auto delete process every to 2 hours

A.12.2.1.3.6 Platform Configuration

1. Configure the platform as described in 2.16 Job Card IST008 - Initial Configuration on page 108
at 2.16.9 Platform Configuration on page 118. Also refer to 2.19 Job Card IST011 - Integration on
page 172 at 2.19.4 DICOM Direct Connect integration on page 190 for the integration mode.
a. Platform Configuration:
• Select AW Server 4.000 slices (SdC_Nano_4k) for Platform Enabler (DICOM Direct
Connect integration case).
• Enter the Platform License key.
b. Scalability:
• Set Cluster settings to Select Single Mode.
c. Integration:
• Select DICOM Direct Connect for Integration enabler.
• Enter the License key.
• Set the Authentication URL: http://<CT Console virtual IP
address>:9998/host
(<CT Console virtual IP address> noted in section A.12.2.1.1 Virtual Machine creation
and AW Server deployment on page 448, Step 2)
For instance: http://192.168.101.1:9998/host

A.12.2.1.3.7 Licensing Configuration

1. Configure the Cola License Server as described in 2.16 Job Card IST008 - Initial Configuration on
page 108 at 2.16.10.3 CoLA License server on page 124.
• Check Built-in for Local License Server.
• Enter the CoLA license key (NodeLock key) in Server Enabler field.
2. Configure the the Floating License as described in 2.17 Job Card IST009 - External Application(s)
Installation on page 132 at 2.17.3 Application(s) Licensing setup on page 134.
Generate the Application Floating Licenses and install them.

454 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

A.12.2.1.3.8 Applications Installation and Activation

1. Insert the USB key into the FE laptop.
2. Load the applications from the media as described in:
Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132 at 2.17.5 Load
the Application(s) from media on page 137
3. Install the applications as described in:
Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132 at 2.17.6 Install
the Application(s) on page 143
4. Activate the applications as described in: A
Refer to 2.17 Job Card IST009 - External Application(s) Installation on page 132 at

Appendices
2.17.7 Activate the Application(s) on page 146

A.12.2.1.3.9 Administrative Configuration

1. Proceed with the AW Server administrative configuration (except for DICOM Hosts
Configuration and End of Review which are described below) as described in 2.18 Job Card
IST010 - Administrative Configuration on page 148.

A.12.2.1.3.10 DICOM Hosts Configuration

1. Configure the CT Console as a DICOM host as described in 2.18 Job Card IST010 - Administrative
Configuration on page 148 at 2.18.1 DICOM Hosts Configuration on page 149.
a. Enter the mandatory fields.
b. Set the IP Address to the CT Console virtual IP address (noted in section A.12.2.1.1 Virtual
Machine creation and AW Server deployment on page 448, Step 2).
For instance: 192.168.101.1
c. Set the Port number to 4006.
d. Set the Authentication URL to http://<CT Console virtual IP address>:9998/
host (noted in section A.12.2.1.1 Virtual Machine creation and AW Server deployment on
page 448, Step 2).
For instance: http://192.168.101.1:9998/host
2. Configure others DICOM hosts if needed as described in 2.18 Job Card IST010 - Administrative
Configuration on page 148 at 2.18.1 DICOM Hosts Configuration on page 149.

A.12.2.1.3.11 End of Review

1. Configure the End of Review to automatically sends processed images to a DICOM host when
exiting the applications, as described in 2.18 Job Card IST010 - Administrative Configuration on
page 148 at 2.18.9 End of Review on page 170.
a. Check the CT Console Host name.
b. Set the Type to all.
c. Set the Modality to CT.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 455

A.12 AW Server Integration in CT/MR Console Environment

A.12.2.1.3.12 System Configuration Registration

1. Proceed with the configuration registration as described in 2.21 Job Card IST013 - Service Tools
Configuration on page 200 at 2.21.1 System Configuration Registration on page 200.

A.12.2.1.3.13 Backup the Configuration

1. Backup the Network and the System configuration as described in 2.25 Job Card IST016 -
System Handover to Customer on page 246 at 2.25.2 Backup Parameters and Settings on page
249.

A.12.2.1.3.14 Exiting Maintenance Mode

1. Exit the maintenance mode as described in A.4.2 Exiting the Maintenance mode on page 371.
This complete the AW Server installation and configuration.
2. AW Server Client installation. Refer to A.12.2.3 AW Server Client installation on page 457.

A.12.2.2 Software Upgrade

A.12.2.2.1 AW Server upgrade

All steps are performed and completed by the GE FE.
This section describes the upgrade/update of the AW Server integrated within the CT Nano-Cloud.
1. Launch the Service Tools. Refer to A.12.2.1.3.2 Launching Service Tools on page 452
2. Backup the Network and the System configuration
Refer to 2.25 Job Card IST016 - System Handover to Customer on page 246 at 2.25.2 Backup
Parameters and Settings on page 249.
3. Open a console/terminal on the CT Console:
• From the FE laptop, open a Web Browser (Firefox or Internet Explorer), type in the iLO IP
address and login to the iLO.
Check with IT team for iLO IP address, username and password.
• Start the Java Web Start Console (console/terminal).
• Login to the console/terminal using the Controller Default credential.
Refer to the [iLO Console and Java Web Start Console] section in [Edison HealthLink Site
Installation Manual] for the full procedure description.
4. Display the Virtual Machine Manager:
Type the following command in the CT Console terminal:
sudo virt-manager <Enter>

456 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

5. Shut Down the Virtual Machine

A
Make sure the Virtual Machine is stopped. If not, right click the Virtual Machine and select Shut

Appendices
Down / Shut Down or Force Off.
NOTE
If you do not want to keep the Virtual Machine, you can delete it by right clicking the
VM and select Delete in the pulldown menu.
In this case the licenses should be generated again as the license ID would have
changed.
6. Proceed to the AW Server installation
Refer to A.12.2.1 AW Server Installation on page 447.
NOTE
In this procedure you will be asked to restore the configuration. So, some
configuration parameters will be set and the configuration of the AW Server will be
lighter. However, if you have decided to delete the Virtual Machine, the licenses
should be generated again as the license ID would have changed.
This completes the AW Server upgrade.

A.12.2.2.2 Applications upgrade

All steps are performed and completed by the GE FE.
This section describes the upgrade/update of the applications running on the AW Server integrated
within the CT Console.
1. Proceed to the Applications Installation and Activation.
Refer to A.12.2.1.3.8 Applications Installation and Activation on page 455.

A.12.2.3 AW Server Client installation

All steps are performed and completed by the GE FE.
The below steps describe the AW Server Client installation and update in the CT Console.
1. Start the Service Desktop interface:
a. At the FE Laptop, connect to the CT Console using ISD/FFA.
b. Start the Service Desktop interface using the CSD tool:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 457

A.12 AW Server Integration in CT/MR Console Environment

NOTE
If you do not have the Insite/RSvP connectivity, you should establish a ssh
connection to the CT Console with X11 tunnel. This can be done with PuTTY (or
equivalent tool) by enabling SSH X11 forwarding option. Then you can login
with ssh to the CT Console and type in the terminal: firefox <virtual
private subnet>.5 (noted in section A.12.2.1.1 Virtual Machine creation and
AW Server deployment on page 448, Step 2).
For instance: firefox 192.168.101.5
2. Uninstall the AW Server Client previously installed
If an AW Server Client is already installed, click on AWS Client Install/Uninstall and select
Uninstall in the popup that displays.

The uninstallation is completed once the popup disappears.

3. Install the AW Server Client
a. In the Service Desktop select AWS Client Install/Uninstall and select Install in the popup
that displays.

458 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.12 AW Server Integration in CT/MR Console Environment

b. Check the information in the window that displays.

Appendices
NOTE
The Host Name should be aws.
Click on Accept and wait until the installation is completed.
4. Configure the AW server Client
a. In the Service Desktop select Configure AWS Applications.

b. In the AWS Favorite Application window select your application then click on Accept.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 459

A.12 AW Server Integration in CT/MR Console Environment

5. Restart the CT Console

6. Check AW Server Client connectivity
• In the CT Console switch to the ImageWorks desktop.

• Select a scan instance and click on an AWS application (for instance Reformat). The
application should start.

460 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

7. This completes the AW Server Client installation/update.

A.13 Physical Servers - Installed Base

This appendix describes the instructions for Installed Based Physical Servers.

A.13.1 AW Server - Product Description

The IB physical servers:
• Low Tier: HP ProLiant ML350 G6 Server
• Low Tier: HPE ProLiant ML350p Gen8 Server A
• High Tier: HPE ProLiant DL560 Gen8 Server with the HP D2600 DAS / HP D3600 DAS (Disks Array

Appendices
System).
• High Tier: HPE ProLiant DL580 G7 Server

A.13.1.1 The low-tier workstation type version

Based on the HPE ProLiant ML350p Gen8 Server (older type) and HPE R/T3000 UPS low tier tower-
type. It supports up to 8,000 or up to 40,000 slices at a time, depending upon which license is
purchased..

A.13.1.2 The high-tier rack-mount version

Based on the HPE ProLiant DL580 G7 Server and the HPE ProLiant DL560 Gen8 Server.
It supports up to 16,000, 40,000, 80,000 or up to 160,000 slices at a time, depending upon which
license is purchased.
Figure A-2 HPE ProLiant DL560 Gen8 Server, Rack-Mount,

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 461

A.13 Physical Servers - Installed Base

Figure A-3 HPE ProLiant DL580 G7 Server, Rack-Mount,

Figure A-4 High-Tier, Rack-Mount main accessories

NOTICE
The high-tier rack-mount version based on a Sun Fire x4450 server is no longer
supported.

A.13.2 Hardware Installation Verification

A.13.2.1 HP Low Tier server hardware deliverables

The following process should take no more than 30 minutes.
Verify that the Server Hardware inventory (provided within server documentation) includes the
items below – part numbers are not listed here as they may change:

462 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

1. Inspect HP ML350 to insure that there is no visible chassis damage.

2. Verify that Mouse, keyboard and monitor are connected to the server.
3. Verify the server has six 500GB SATA drives installed – as in the picture below.

Appendices
4. Verify the correct cable connections – as in the picture below – note 2 network cables: 1 for
Service Processor and 1 for application eth0 only.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 463

A.13 Physical Servers - Installed Base

5. Connect the server’s power supplies to the power outlets.

6. Turn on the server.
The server may turn on automatically when it is connected to the power outlet. If it does not,
press the Power On/Off button located in the front of server on the front panel (shown on the
far right side of the following illustration).

464 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

A
Auto-tests will start, the hard disk LEDs will blink, and the front panel LEDs will turn on (green).

Appendices
After a few seconds, the fans will start at high speed, and will then decrease speed sequentially.
Then the screen unblanks and displays initialization messages, then displays the HP ProLiant
logo. Initialization takes some time to complete. Please be patient.

7. When the message Press any key to view option ROM messages is displayed, press
the <Space> bar so that you can see all messages displaying on the screen, such as memory
size, hard disks, etc.
8. Verify that the iLO IP address does not display as Unknown, but displays the proper IP address at
the bottom of the screen.
9. Verify that the following parameters are setup correctly, referring to the AW Server 3.2
Hardware Installation Manual 5719442-1EN:
a. BIOS parameters (press <F9> to enter BIOS setup).
NOTE
The BIOS parameters can be checked without having to reboot the system and
enter the BIOS menu as follow:
• In a terminal, login as root.
• Type the following command: /sbin/conrep -s <Enter>.
• The BIOS parameters are save locally in the file conrep.dat, and can be
viewed using the command cat conrep.dat <Enter> or the command
more conrep.dat <Enter>.
b. iLO Service Processor parameters (press <F8> to enter iLO setup).
c. RAID controllers / RAID levels parameters (press <F8> to enter RAID setup).
• P410i / P420i controller: you should see 2 logical drives:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 465

A.13 Physical Servers - Installed Base

• RAID 1 of about 500 GB (system disk)

• RAID 1+0 of about 1TB (image disk)
10. Hardware initialization sequence takes several minutes to complete. Please be patient. Then
after a while, the screen unblanks and will display the HP ProLiant logo and boot up messages.
NOTE
When booting the AW Server, the Helios progress bar is displayed for OS boot.
However details of other operations are not provided. To display the details, hit any of
the arrow keys or the <Esc> key. This will display of OS boot messages including
filesystem check progress. Hitting any of the arrow keys or the <Esc> key again
displays the previous OS boot screen progress bar.
Once initialization is complete, the boot sequence will continue if the AW Server has been
preloaded by Manufacturing.
11. When boot sequence has completed, login as root.
12. NOTICE
The next steps are only applicable to Factory preloaded systems.
If home1 is not properly mounted you may get the following messages:

ERROR: Image partitions are not mounted!!

Press <Enter> to abort reconfiguration.
a. In that case, press <Enter>.
The server will shutdown with the following messages:

INFO: Backup copies not removed, boot sequence intact.

Ghost configuration as preload has failed.
Check RAID and disks are operational and correctly configured.
Config service will run again at next platform boot.
Press <ENTER> to shutdown.
b. Check that no HDDs of the RAID are failed, before pressing the <Enter> key and
attempting to boot again.
c. When done, press <Enter> to boot.
13. Verify that the OS sees the correct CPUs are installed with the following command levels, and
corresponding results:

Command Result
cat /proc/cpuinfo | more <Enter> Complete information
cat /proc/cpuinfo | grep -i processor <Enter> Filtered on ordered Processor numbers
cat /proc/cpuinfo | grep -i CPU <Enter> Filtered on CPU info

There are 12 (2 x Six-core) processors.

14. Verify that the OS sees the correct amount of memory with the following command:
cat /proc/meminfo | grep -i memtotal <Enter>
MemTotal: 24565372 kB (ML350p G8 and ML350 G6 with 24GB memory option)
OR
MemTotal: 65932080 kB (ML350p G8 and ML350 G6 with 64GB memory option).
15. Verify the partitioning after the AWS load with the following command: df -k <Enter>.

466 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

NOTE
The Used and Available values may differ from those displayed in the example
below.

16. Check the OS version, with the following command and example results: A
cat /etc/aweconfig <Enter>

Appendices
For AWS3.2 Ext.3.4 release:

OS: AWS3.2_OS_5.1
OS Build ID: yyyymmdd I.e: 20190626
17. Check the AWS Platform version, with the following command and results:
cat /etc/aweconfig <Enter>
For AWS3.2 Ext.3.4 release:

AWE_HOME=/usr/share/awe
AWE_VERSION=aws-3.2-3.4-1728.2
AWE_BUILDID=aws-3.2-3.4-1728.2
AWE_BUILDDATE=20190713
AWE_UDI='(01)00840682102384(10)AWS3D2E002D0'
AWE_REF='5719780'
AWE_LOT='AWS3D2E002D0'
AWE_USER=sdc
AWE_GROUP=sdc
HTDOCS=/var/www/html
APACHE_CONFDIR=/etc/httpd
AWE_JVMARGS="-Xmx1000m -Xss128k -server -Dtap.dm.ImageMemory=200 -
XX:+UseParallelGC -XX:+AggressiveHeap"
NOTE
This is an example result. The actual values on your screen may differ at time of
release of the software.
18. To read the MAC address, type in: ip addr show eth0 <Enter>.
A MAC address shall be of the form XX:XX:XX:XX:XX:XX. For example: 00:01:0c:07:ac:88.
19. Use this information to enter the eLicense web site and calculate the keys associated to your
GON (Global Order Number).
Refer to A.3 eLicensing on page 362 for more information on eLicense, or wait until the AW
Server platform software has been loaded, so that you can get access to the HealthPage and/or
use the command licenseId that will display the license ID.
NOTE
Configuration and network functionality of service processor port. On the GEHC FE
laptop, open a browser, enter the service processor's IP address.
http://iLO_IP_address <Enter>
The iLO service processor's main page appears.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 467

A.13 Physical Servers - Installed Base

A.13.2.2 HP High Tier server hardware deliverables

The following process should take no more than 30 minutes.
1. Verify that the Server hardware inventory (provided within server documentation) includes the
items below:
HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8 Server

Description QTY
HP DL580 / DL560 chassis 1
146GB 10K RPM 2.5" SAS HDD or 300GB 15K RPM 2.5" SAS HDD (DL560 starting Q4 2016) 2
internal DVD+/-RW drive (DL580) 1
external USB DVD+/-RW drive (DL560) 1
internal RAID controller 1
Redundant hot-swappable AC power supply (DL580) 4
Redundant hot-swappable AC power supply (DL560) 2
Tool-less slide rail kit 1
External Raid Host Adapter 1

2. Verify that the DAS (Direct Attached Storage) hardware inventory (provided within server
documentation) includes the items below:
HP D2600 DAS / HP D3600 DAS
Not applicable for Full and/or Seamless integration.

Description QTY
1TB SATA Drives 12
Chassis with 2 Power Supplies, 2 Fan Modules, 2 I/O modules, 1 cable .5 meter 1
Rack Mount kit 1

3. Verify that both the HPE ProLiant DL580 G7 Server / HPE ProLiant DL560 Gen8 Server and HP
D2600 DAS / HP D3600 DAS (if applicable) slide out and in the rack enclosure easily, and do not
bind or cause disconnected cables. This means that the cables, and cable arm harness must be
dressed and strain-relieved properly.
4. Inspect all units to insure that there is no visible chassis damage.
5. Verify that the Server is connected to a PDU (either data center PDU or rack mount) and/or to a
UPS (either data center UPS or rack mount).
6. If applicable, verify that the DAS is connected to a UPS (either data center UPS or rack mount).
Not applicable for Full and/or Seamless integration.
7. Verify that the Server Network 1 and iLO port are connected to the Network (either data center
Network switch or rack mount).
8. If applicable, verify that the KVM (mouse, keyboard and monitor) is connected to the server.
9. If rack mount UPS is installed, verify that UPS is powered on, and that the KVM, Network switch,
server and DAS are connected to UPS and PDU as shown below.

468 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

Appendices
10. SAS drives:
• HPE ProLiant DL580 G7 Server: Verify that the server has two 146GB SAS drives, as shown
in the picture below:

• HPE ProLiant DL560 Gen8 Server: Verify that the server has two 146GB SAS drives, as
shown in the picture below:

NOTE
Together with the DL560 delivery, you have received one external USB DVD drive.
You can connect it to the front panel USB connector at the right side of the

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 469

A.13 Physical Servers - Installed Base

DL560 (or to one of the rear USB connectors) when needed. When not in use,
store it in a safe place for future use.
11. If applicable, verify that the attached DAS has twelve 1TB SATA drives installed, as shown in the
picture below. (Not applicable for Seamless integration).
HP D2600 DAS/ HP D3600 DAS:

12. Cable connection:

• HPE ProLiant DL580 G7 Server: Verify the correct cable connections as shown in the picture
below. Note that there are TWO network cables – one for the iLO service processor and one
for the server itself (eth0).

• HPE ProLiant DL560 Gen8 Server: Verify the correct cable connections as shown in the
picture below. Note that there are TWO network cables – one for the iLO service processor
and one for the server itself (eth0).

470 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

Appendices
13. DAS cable:
• HPE ProLiant DL580 G7 Server: If applicable, make sure the DAS cable is connected
between the server and the I/OA IN board. I/OB interface board shall not be used, but can
be left in place. Not applicable for Full and/or Seamless integration. No DAS present.

• HPE ProLiant DL560 Gen8 Server with HP D2600 DAS: If applicable, make sure the HP
D2600 DAS cable is connected between the server and the I/OA IN board. I/OB interface
board shall not be used, but can be left in place.
Not applicable for Full and/or Seamless integration. No DAS present.

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 471

A.13 Physical Servers - Installed Base

• HPE ProLiant DL560 Gen8 Server with HP D3600 DAS: If applicable, make sure the HP
D3600 DAS cable is connected between the server and the I/O1 board: DP-1 connector. I/O2
interface board shall not be used, but can be left in place.
Not applicable for Full and/or Seamless integration. No DAS present.

14. KVM: Verify that the KVM (or monitor) is connected to the VGA output and that the keyboard
and mouse inputs (PS2 or USB) are connected.
15. Apply power to the system. Apply power to the mains inputs of PDU and UPS (if applicable).
• The UPS utility green LED should blink. The KVM turns on.
• The DL580 / DL560 on/off button LED should be steady yellow.
• The DAS should start, all LEDs blinking green.
NOTE
If DAS is not starting (only available for HP D2600 DAS), press the On/Off switch at
the rear of the DAS during a few seconds so the DAS turns on.

472 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

Appendices
16. Power up the UPS (if applicable) by pressing on the I or On button.
• The Network switch option turns on.
• The UPS Utility LEDs should display steady green as shown.
17. Wait about 1 half minute to allow the DAS to synchronize and attach all of its disk partitions
before switching on the server. Power up the server by pressing on the Power On/Off button.

• The Server Power On/Off button light turns from yellow to green.
• There will be LED activity on the Server and the DAS hard disk drives.
• The Network 1 LED should be ON (if the network is configured)
• The Server and DAS Hard disk drives LEDs shall be green.
• Hardware initialization sequence takes several minutes to complete. Please be patient.
Then after a while, the screen unblanks and will display the HP ProLiant logo and boot up
messages.
NOTE
When booting the AW Server, the Helios progress bar is displayed for OS boot.
However details of other operations are not provided. To display the details, hit
any of the arrow keys or the <Esc> key. This will display of OS boot messages
including filesystem check progress. Hitting any of the arrow keys or the <Esc>
key again displays the previous OS boot screen progress bar.
• Once initialization is complete, the boot sequence will continue if the AW Server has been
preloaded by Manufacturing.
18. Verify that the following parameters are setup correctly, referring to the AW Server 3.2
Hardware Installation Manual 5719442-1EN:

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 473

A.13 Physical Servers - Installed Base

a. BIOS parameters (press <F9> to enter BIOS setup).

NOTE
The BIOS parameters can be checked without having to reboot the system and
enter the BIOS menu as follow:
• In a terminal, login as root.
• Type the following command: /sbin/conrep -s <Enter>.
• The BIOS parameters are save locally in the file conrep.dat, and can be
viewed using the command cat conrep.dat <Enter> or the command
more conrep.dat <Enter>.
b. iLO Service Processor parameters (press <F8> to enter iLO setup).
c. RAID controllers / RAID levels parameters (press <F8> to enter RAID setup).
P410i / P420i controller for 2 x 146GB server’s internal HDDs
You should see a RAID 1+0 (or RAID 1) of about 146 GB
P411 / P421 controller for 12 x 1TB DAS’s internal HDDs
You should see a RAID 1+0 of about 6TB.
19. If home1 is not properly mounted you may get the following messages:

ERROR: Image partitions are not mounted!!

Press <Enter> to abort reconfiguration.
a. In that case, press <Enter>.
The server will shutdown with the following messages:

INFO: Backup copies not removed, boot sequence intact.

Ghost configuration as preload has failed.
Check RAID and disks are operational and correctly configured.
Config service will run again at next platform boot.
Press <ENTER> to shutdown.
b. Check that no HDDs of the RAID are failed, before pressing the <Enter> key and
attempting to boot again.
c. When done, press <Enter> to boot.
20. When boot sequence has completed, login as root.
21. NOTICE
The next steps are only applicable to Factory preloaded systems (or after OS has
been loaded).
Verify that the OS sees the correct CPUs are installed with the following command levels, and
corresponding results:

Command Result
cat /proc/cpuinfo | more <Enter> Complete information
cat /proc/cpuinfo | grep -i processor <Enter> Filtered on ordered Processor numbers
cat /proc/cpuinfo | grep -i CPU <Enter> Filtered on CPU info

• HPE ProLiant DL580 G7 Server: There are 24 (4 x Six-core) processors with a model name of
Intel(R) Xeon(R) CPU.

474 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

 A.13 Physical Servers - Installed Base

• HPE ProLiant DL560 Gen8 Server: There are 32 (4 x Eight-core) processors with a model
name of Intel(R) Xeon(R) CPU.
22. Verify that the OS sees the correct amount of memory with the following command:
cat /proc/meminfo | grep -i memtotal <Enter>
• HPE ProLiant DL580 G7 Server: MemTotal: 65836920 kB (64GB).
• HPE ProLiant DL560 Gen8 Server: MemTotal: 65923312 kB (64GB) or 264485424 kB
(256GB).
23. Verify the partitioning after the AWS load with the following command: df -k <Enter>.
NOTE
Alternatively, you can use the df -h command for a display in GBytes.
A
NOTE

Appendices
For HPE ProLiant DL580 G7 Server: System filesystem defaults to sda, backup and
image filesystems to sdb.
NOTE
For HPE ProLiant DL560 Gen8 Server : System filesystem defaults to sdb, backup and
image filesystems to sda
NOTE
The Used and Available values may differ from those displayed in the examples
below.
The example below is for a HP high tier server with DAS.

The example below is for the Integrated HP High Tier server (without external disk array -DAS)
and is similar for a virtual AW Server.

24. Check the OS version, with the following command and example results:
cat /etc/aweconfig <Enter>
For AWS3.2 Ext.3.4 release:

OS: AWS3.2_OS_5.1
OS Build ID: yyyymmdd I.e: 20190626
25. Check the AWS Platform version, with the following command and results:
cat /etc/aweconfig <Enter>
For AWS3.2 Ext.3.4 release:

AWE_HOME=/usr/share/awe
AWE_VERSION=aws-3.2-3.4-1728.2
AWE_BUILDID=aws-3.2-3.4-1728.2
AWE_BUILDDATE=20190713
AWE_UDI='(01)00840682102384(10)AWS3D2E002D0'

5719443-1EN Revision 8 AW Distributed Applications - Enterprise Server 475

A.13 Physical Servers - Installed Base

AWE_REF='5719780'
AWE_LOT='AWS3D2E002D0'
AWE_USER=sdc
AWE_GROUP=sdc
HTDOCS=/var/www/html
APACHE_CONFDIR=/etc/httpd
AWE_JVMARGS="-Xmx1000m -Xss128k -server -Dtap.dm.ImageMemory=200 -
XX:+UseParallelGC -XX:+AggressiveHeap"
NOTE
This is an example result. The actual values on your screen may differ at time of
release of the software.
26. To read the MAC address, type in: ip addr show eth0 <Enter>.
For example: 00:01:0c:07:ac:88.
A MAC address shall be of the form XX:XX:XX:XX:XX:XX.
27. Use this information to enter the eLicense web site and calculate the keys associated to your
GON (Global Order Number).
Refer to A.3 eLicensing on page 362 for more information on eLicense, or wait until the AW
Server platform software has been loaded, so that you can get access to the HealthPage and/or
use the command licenseId that will display the license ID.
NOTE
Configuration and network functionality of service processor port. On the GEHC FE
laptop, open a browser, enter the service processor's IP address.
http://iLO_IP_address <Enter>
The iLO service processor's main page appears.

476 AW Distributed Applications - Enterprise Server 5719443-1EN Revision 8

Manufacturer
GE MEDICAL SYSTEMS SCS
283 RUE DE LA MINIERE
78530 BUC FRANCE

www.gehealthcare.com