Additional Config Information

Centricity
PACS-IW

Additional Configuration Information

I3
Revision 1

GE Healthcare
Integrated IT Solutions, Dynamic Imaging Solutions

Date Comments Rev Initials
Oct-12-2009 Initial Release 1.0 JA

© 2008 General Electric Company. All rights reserved. Page i

GE Healthcare

Table of Contents

1. DEFAULT DEBUGGER .................................................................................................................................. 1
2. NATED ACCESS TO SERVERS .................................................................................................................... 1
3. FORWARD IMAGES BETWEEN SERVERS .................................................................................................. 2
4. QUERY RETRIEVE CONFIGURATION ........................................................................................................ 2
5. TOMCAT ........................................................................................................................................................ 3
6. SUPPORT FOR LARGE STUDIES ................................................................................................................. 4
7. REDIRECTION OF WEB REQUESTS IN LARGE INSTALLATIONS ........................................................... 5
8. PET/CT ....................................................................................................................................................... 6
9. AUTOMATIC PRE-‐FETCH FROM CENTERA ARCHIVE ............................................................................ 6
10. CLIENT DICTATION INTEGRATION ........................................................................................................... 9
11. SUV CALCULATION .................................................................................................................................. 10
12. NM DEFAULT PRESET............................................................................................................................. 10
13. INTERNET EXPLORER CONFIGURATION............................................................................................... 12
14. DISABLE UAC IN WINDOWS VISTA OS................................................................................................ 13
15. DICOM PRINTER SETUP ........................................................................................................................ 18
16. UPDATING A LICENSE FILE IN CENTRICITY PACS-‐IW ...................................................................... 19
17. HL7 ............................................................................................................................................................ 19
18. LOCALIZATION OF CD-‐FILM FILES ....................................................................................................... 20
19. SSL CREATION .......................................................................................................................................... 22

© 2008 General Electric Company. All rights reserved. Page ii

GE Healthcare

Additional Configuration Parameters

This document explains the most common configuration options and how to set them up
within the PACS-‐IW server.

1. Default Debugger
From the CMD window, type drwtsn32-‐I to set Dr. Watson as the default debugger.

2. NATed Access to Servers

This configuration is essential for the loading of images through a server that uses Network
Address Translation for external connections.

1. Open Site Configuration by clicking Start  Integrad  Site Configuration.
2. Navigate to Site Configuration  Info.
3. Click the System Configuration tab (the computer with red checkbox).
4. Check the Use Network Address Translated Access checkbox.

5. Click the Apply Button.
6. Provide a description of the previous configuration. An entry is required; otherwise
the configuration is not accepted.
7. Restart the Storage Controller and Tomcat Services.

© 2008 General Electric Company. All rights reserved. Page 1

GE Healthcare

3. Forward Images between Servers

When images are forwarded between servers, the resulting calls to DNS may slow down the
system. This is related to DNS reverse lookup. To prevent this behavior, include all IP
addresses of DI notes in the host files. (You can add hostnames and IPs to the host file
located at C:\WINDOWS\system32\drivers\etc\ folder)

4. Query Retrieve Configuration

Query Retrieve configuration is located in the Site Configuration tool.
1. Start the Site Configuration tool by clicking Start → Integrad → Site Configuration.
2. Select the Info Tab.
3. Select the Server.
4. Select the QR tab.
5. The following values should not be changed and are explained here for information
only. Consult with Engineering if it seems necessary to change one of these values.
 Enable Query Retrieve – This parameter is used by the Storage Controller and
activates the processing of Query Retrieve requests. QR Server does not depend on
it.
 Query Retrieve Port – This is the port that will accept client requests; this is used by
QR Server.
 QR Server IP Address – This is the address used by Storage Controller to send
responses to the QR Server.
 Storage Controller Listen Port – This is the port used by QRServer to forward client
requests to the Storage Controller.

GE Healthcare
 Storage Controller Send Port – This is the port used by the Storage Controller to
send the response to the QR Server.
 Storage Controller Timeout – This is the time (in minutes) that the QR Server should
wait for the Storage Controller to process the request and send a response back to
the QR Server. If the timeout is reached with no response from the Storage
Controller, the client gets an empty result.
 Max Concurrent Associations – This is the maximum number of requests QR Server
can handle at one time.
 Max Requests in QR Queue –Before QR Server forwards requests to the Storage
Controller, it queues them. This is the maximum requests that can be queued.
 Max Number of Studies – This is the maximum number of studies that a response
can contain information about.

5. Tomcat
Tomcat’s memory allocation must be modified by starting the service_edit.bat located under
c:\Program Files\jakarta-tomcat-5.5.7\bin.
This is recommended for every install to ensure optimal performance. Navigate to the Java
Tab and change the Memory size allocations:
Initial Memory Pool – change to 256
Maximum Memory Pool – change to 512


GE Healthcare

6. Support for Large Studies

For a viewer to perform adequately with very large studies, the client machines have to
have a System Swap file size of at least 2GB. To support very large studies in conjunction
with MIP/MPR, the file size should be even bigger.

Note that the standard Windows recommendation for sizing the paging file is at least 1.5
times the physical memory. This means that for a 2 GB system, that file should be 3 GB. For
a 4 GB system, that file should be 6 GB, etc.

To configure/verify the client machine, take the following steps:
1. Open the System Properties page from the Control Panel.
2. Click the Advanced tab.
3. In the Performance section, click the Settings button.
4. Click the Advanced tab.
5. In the Virtual memory section, click the Change button.

6. Allocate the memory according to the customer need.


GE Healthcare
7. Redirection of Web Requests in Large Installations
When Centricity PACS-‐IW is implemented in the Large Installation Model, users typically
connect and log in through one of the “nodes” that are local to them (typically located on the
Local Area Network). “Nodes” in this configuration combine the Web and Application
Servers but omit the Database; the Database is instead located on the special node named
“Controller.”

The connectivity between nodes and Controller should be better than T1, usually on the
level of T3, to minimize impact on the speed of database transactions. However, in certain
installations, the characteristics of a network between nodes and controller may affect such
transactions dramatically. In particular, this may occur on ATM networks, or WAN
networks that are using too much of their bandwidth. The effect can be observed as very
long wait times (i.e., more than 10 seconds and, depending on the network, tens of seconds)
before the first images show up in the viewer – when connected through the node instead of
directly to the Controller.

To enhance performance of opening studies in those situations, the configuration can be
changed to re-‐direct certain Viewer requests from a node to the Controller, thus assuring
that database transactions are run.

By default, redirection is off, and all requests are processed at the node to which they have
been sent. To turn such redirection on, set the following parameter in the
Integrad\Current\conf\Startup.conf file:
viewerGetStudyProxyEnabled=on


GE Healthcare

8. PET/CT
The site must have a PET-‐CT license to use PET-‐CT features.

If the site has been upgraded, a new dongle that supports PET/CT must be installed. If the
new dongle has a different license number than the previous dongle, the license must be
reset. Use the following steps to reset the license:

1. From the server, open Windows Explorer and navigate to C:\Integrad\Current\conf
2. Copy the new license file xxx.lcm (the file that contains the PET-‐CT license) to
C:\Integrad\Current\conf
3. Replace the old dongle with the new dongle.
4. From the server, navigate to C:\integrad\current
5. Edit the setup.ini file and edit the license number in the LICENCE_FILE
6. Save and close the file.
7. Navigate to C:\Integrad\Current\Conf
8. Edit the miw3.LicenseService.conf and edit the license number LcFileName.
9. Save and close the file.
10. From Start  Integrad, open the Integrad database.
11. Select the Tools tab.
12. Click the Set License button. Make sure no error message appears.
13. Close the Integrad database.
14. Open the Integrad Control panel and restart the services.

Take the following steps to verify that the license has been changed.
1. Open Integrad.
2. Open a PET-‐CT study.
3. Open the Layout Editor and click the More Settings tab.
4. Check the “Advanced PET-‐CT” check box.
5. If MIWS30-‐1495.lcm (with PET-‐CT) has been applied, then the Layout Editor can be
saved with the “Advanced PET-‐CT” flag checked. If MIWS30-‐1496.lcm (without
PET-‐CT) has been applied, then a message states “This operation requires a PET-‐CT
license.”

9. Automatic Pre-Fetch from Centera Archive

You can configure Centricity PACS-‐IW to automatically pre-‐fetch (bring online) prior studies
from the Centera archive if such studies are not present on the online storage areas. This
provides quick and seamless access to older studies, which otherwise would have had to be
brought online manually.

9.1 Functional Description

Centricity PACS-‐IW can automatically pre-‐fetch prior studies from Centera if those studies
are not already present online. The pre-‐fetch process can be triggered by an order from RIS
or by an incoming study.

GE Healthcare

The prior studies to pre-‐fetch are determined by configuration parameters that specify how
many studies to pre-‐fetch and how far back in time to look for priors. Priors are the studies
that have the same Patient MRN as the triggering order or study. If the “Use Anatomic
Regions to select priors” option is active, only studies that have the same Anatomic Region
as the one identified by the order will be considered for pre-‐fetch.

Where
In large Installations, the pre-‐fetch may be directed to the online storage of a particular
node.
 Triggered by order – If the pre-‐fetch is triggered by an order in a large installation,
then the value of the Servicing Facility field in that order determines the target node.
Servicing facilities are mapped to nodes. (See the configuration section below.)
 Triggered by study – If the pre-‐fetch is triggered by a study in a large installation,
then the fetch is directed to the same node as the triggering study.

When
 When triggered by an order, the pre-‐fetch can be configured to occur a certain
number of days before the scheduled date-‐time of the procedure, and to occur only
at a particular time period of the day. If an order is cancelled, the pre-‐fetch that did
not occur will be cancelled as well. The pre-‐fetch that is in progress at the time of
order cancellation will complete. For re-‐scheduling of an order to affect a scheduled
pre-‐fetch, the order must first be cancelled and then re-‐scheduled.
 When triggered by a study, the pre-‐fetch will always be triggered immediately.

9.2 Configuration
Configuration of pre-‐fetch is done through the Site Configuration utility, which now includes
a Centera Pre-‐fetch tab.

Note that you must configure each node in the system, and that each should be
configured identically. There are exceptions; see the Centricity PACS-‐IW Guide to
Installation for discussion of special situations when different parameters may be used for
different nodes.

1. From the Centera Pre-‐fetch tab, click the Main sub-‐tab. Specify values based on the
following explanations:
 Centera Pre-‐fetch by Order – When checked, pre-‐fetching is triggered by
orders.
 Centera Pre-‐fetch by Study – When checked, pre-‐fetching is triggered by
studies.
 Pre-‐fetch Target – Enter the IP address of the node which will receive the
pre-‐fetch studies by default when no other target configuration is specified;
in large installations, enter the IP address of the Controller.
 Pre-‐fetch to the same Node – If Pre-‐Fetch by Study is checked, check this
checkbox to pre-‐fetch priors to the same node as that of the triggering study.

Note that if neither of the “Prefetch By… “ checkboxes are checked, the automatic pre-‐
fetch is disabled. If both are checked, the pre-‐fetch is triggered by orders and studies. This

GE Healthcare
pre-‐fetches mostly by order while also allowing for unscheduled studies to trigger a pre-‐
fetch.

2. From the Centera Pre-‐fetch tab, click the Preferences sub-‐tab. Specify values based
on the following explanations:
 Maximum Prior Studies – Specify how many priors should be pre-‐fetched.
The system will pre-‐fetch as many priors as named in this parameter as long
as they are no older than the Max Backward Time.
 Max Backward Time – Specify the age of priors to consider. The system will
pre-‐fetch as many priors as specified in Maximum Prior Studies as long as
they are not older than this value.
 Pre-‐fetching Time – Enter (in days) how far in advance of the scheduled
procedure the pre-‐fetch should begin. This value is meaningful only when
Pre-‐fetch by Order is enabled.
 Time Of Day -‐ Specify the start and end time of the day when pre-‐fetches
should occur. Typically this is an off-‐hours period, and this value is
meaningful only when Pre-‐fetch by Order is enabled.

Mapping Servicing Facilities to Nodes
The IntegradAdminClient utility allows administrators to map servicing facilities to nodes
for pre-‐fetch purposes. This mapping is only effective when Pre-‐fetch is triggered by order.
1. Click the Add Node button to add one or more nodes to serve as targets for pre-‐
fetched studies.
2. For each node, click the Add Facility button to add one or more facility codes
(exactly as they are sent in the order); this directs pre-‐fetched priors to that node.
Use the Delete button to remove a selected node or facility. If no mapping is defined, or if
the order contains a Servicing Facility that is not mapped, the pre-‐fetch is directed to the
default target specified in Site Configuration.

Limitations and Constraints
Consider the following issues when configuring Pre-‐fetch:
 Make sure that all target nodes have a properly configured Bring Online area with
Auto-‐cleaning enabled and a sufficient watermark setting. If the Bring Online area
gets full, pre-‐fetching will fail.
 Understand that the pre-‐fetching jobs run on their target nodes. This means that
you may specify different parameters (such as time of day to run, days in advance to
run, etc.) differently for each node, and the setting of the target node will take
precedence. In general, it is best to keep all parameters the same unless a particular
node presents special considerations (such as a slower network connection or
different work-‐time hours).
 When setting numeric values for such parameters as Max Backward Time, Max
Backward Time and Pre-‐fetching Time, take care not to set it to zero, or to a negative
or fractional value. If an invalid value is specified, no pre-‐fetch will occur.
 Even though Integrad expects orders to be sent only to the Controller in a large
installation, the Pre-‐Fetch by Order is enabled on all nodes that may be targets of a
pre-‐fetch (i.e., when servicing facility mapping is defined).
 Centera Pre-‐Fetch should not be enabled in an installation with Business Continuity.
 Failures and errors encountered by pre-‐fetch operations are logged in the pre-‐
fetch.log file. Refer to this file to determine what caused a failure when the pre-‐fetch
does not run as expected.

GE Healthcare

10. Client Dictation Integration

As of version 3.7.1, Centricity PACS-‐IW allows for the configuration of Dictation integration
on the Client side. The string that the viewer generates (when the Centricity user clicks the
Dictation button on the Image Viewer toolbar) is configured in the Dictation.ini file that
resides on the client. For example, three files are available on the server under
c:/Integrad/current/downloads. The files are:
dictation_powerscribe.ini
dictation_provox.ini
dictation_insite.ini

This section describes how to set the integration correctly when the dictation.ini file is
created. (It does not describe how to configure the dictation.ini file.)

To launch Dictation Integration from the client side, follow these steps:
1. Copy the appropriate dictation.ini file under C:\Program Files\Integrad.3\MIV.
2. Rename the file to dictation.ini (from dictation_powerscribe.ini to dictation.ini).
3. Edit the file.
4. Set the Enabled key, in the General section, to Y.

5. Configure the correct Port information.


GE Healthcare
11. SUV Calculation
This section describes how to activate SUV calculations.
1. From the server side, start the Integrad Database.
2. Select the Tools tab.
3. Click the Calculate SUV button.

4. Click the Calculate Attenuation Flag Only checkbox if upgrading from 3.7.1; the tool
will only calculate the attenuation flag. If upgrading from 3.6.2, do not click the
Calculate Attenuation Flag only box; the tool will calculate both (the attenuation flag
and the SUV).
5. In the Calculate SUV Factor window, enter the SQL Address and the Server Address.
6. In the Date Time Interval From and To, enter (or select) a date range for studies that
should have SUV calculated.
7. Click the Calculate button and wait until the “Result Calculated” message is
displayed.
8. Restart Integrad services.

12. NM Default Preset

This section explains how to apply default settings for Nuclear Medicine Default Presets.

GE Healthcare

1. From the server side, open Windows Explorer and navigate to
c:\Integrad\current\downloads\<current viewer version>
2. Double click LayoutSelectionLib.exe.
3. Enter the username and password.

4. Enter the server IP Address for the server.
5. Click the Login button.
6. In the Resource type drop-‐down list, select GLW.
7. Click the Load Button.
8. Click Find Bad.

GE Healthcare

9. On the right, select NM-‐default.
10. Click the Fix Bad button.
11. Close the Window and restart Services.

13. Internet Explorer Configuration

When saving new tabs, the Centricity user may be prompted to allow a scripted window. To
prevent the generation of this message, use the following steps to modify the Internet
settings.
1. From the Tools menu of IE, click Internet Options.
2. Click the Security tab.
3. Select the Trusted Sites icon.


GE Healthcare

4. Click the Sites button.
5. Add the site, in the format https://<Server name> to the first field.

6. Click the Add button to add; then click the Close button.

14. Disable UAC in Windows Vista OS
14.1 Method 1 - Using MSCONFIG

1. Launch MSCONFIG from the Run menu.
2. Click the Tools tab. Scroll to the "Disable UAC" item and click that row.


GE Healthcare

3. Click the Launch button.
4. A CMD window opens. Close the window when the command finishes executing.
5. Close MSCONFIG and reboot the computer to apply the changes.
UAC can be re-‐enabled: select the "Enable UAC" line and then click the Launch button.
14.2 Method 2 - Using Regedit

1. Open Registry Editor.
2. In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE'Software'Microsoft'Windows'CurrentVersion'P
olicies'System
3. Locate the following value (DWORD): EnableLUA and enter a value of 0. To re-‐enable
UAC, change the value to 1.

Note that a valid backup should be in place before making changes to the registry. If
you need to delete or modify keys or values from the registry, you can first export
that key or value to a .REG file before making the changes.

4. Close the Registry Editor. You must reboot the computer to apply changes.

14.3 Method 3 - Using Group Policy

This method can be done via Local Group Policy or Active Directory-‐based GPO, which is
suitable for disabling UAC for many computers at once on a large network.

GE Healthcare

If using Local Group Policy, open the Group Policy Editor (Start  Run  gpedit.msc) from
a Vista computer.

If using an AD-‐based GPO, open the Group Policy Management Console (Start  Run 
gpmc.msc) from a Vista computer that is a member of the domain. In the GPMC window,
browse to the required GPO that is linked to the OU or domain where the Vista computers
are located, then edit it.
1. In the Group Policy Editor window, browse to Computer Configuration  Windows
Settings  Security Settings  Local Policies  Security Options.

2. In the right pane, scroll to find the User Access Control policies (near the bottom).
Configure the following policies:


GE Healthcare

3. Reboot the computers.
14.4 Method 4 - Using Control Panel

1. Open Control Panel.
2. Under User Account and Family settings, click the "Add or remove user account."

3. Click one of the user accounts, such as Guest.

GE Healthcare
4. Under the user account, click the "Go to the main User Account page" link.

5. Under "Make changes to your user account," click the "Change security settings" link.

6. In the "Turn on User Account Control (UAC) to make your computer more secure,"
click to unselect the "Use User Account Control (UAC) to help protect your
computer." Click the OK button.


GE Healthcare

15. DICOM Printer Setup

This section explains how to setup and test a DICOM Printer.

1. Open the DicomPrinters.conf file located in the C:\Integrad\Current\conf
folder.

2. Edit the [Printer1] settings for the needed DICOM printer. Leave the number
of formats => 2. If the number of formats is less than 2 the system will error
when trying to print.
3. Test the setup by printing a study from PACS-‐IW.


GE Healthcare

16. Updating a license file in Centricity PACS-IW

1. Open the following directory: C:\Integrad\Current\conf
2. Locate the file named MIWS30-‐XXXX.lcm, where XXXX is the Plug ID you are
working with.
3. Change that file to MIWS30-‐XXXX.lcm.old and place the new MIWS30-‐XXXX.lcm file
in that folder. If the new License and Plug Number are different then the already
installed License and Plug Number, open miw3.LicenseService.conf located in
C:\Integrad\current\conf folder and change the MIWS30-‐XXXX.lcm to the new Plug
Number and save.
4. Open the Integrad database application by clicking on the Start button and selecting
Integrad  Integrad Database.
5. In the Integrad Database Application, select the Tools tab and click the Set License
Button. The window displays the results.
6. Restart the Tomcat Service from the Control Panel.
The control panel updates to show that the process is complete.

17. HL7
The necessary components for HL7 are Iguana and Chameleon. Iguana is a complete
package that contains Chameleon as an HL7 parser. Chameleon is installed with every
install of the Integrad Environment. This latest version of Chameleon is 4.5.

Chameleon
Chameleon run-‐time licenses should be applied in accordance with the type of installation.
To order the license, the machine ID and customer name are required.
1. Double-‐click the Chameleon icon and view the machine ID. Based on the ID, a
key will be issued on the interfaceware website.
2. The Field Service Engineer or Project Manager of the site should email the
Chameleon machine ID to Arlene Daly and Emilia Buddle to generate a PO with
Interfaceware.
3. Once a license is issued on the Interfaceware website, one of the Interface
specialists can fetch and apply the license on the server.
For single server environment — one license on the main server
For cluster environment — one license for each cluster node
For large installation environment —one license for the controller, one for each
cluster node (if present) and one for any remote nodes that may have HL7
outgoing messages in RIS integrations (e.g., IDX, Meditech, etc)

Note that Chameleon is always on a server that has PACS installed.


GE Healthcare
Iguana
Iguana run-‐time licenses should be applied in accordance with the type of message
distribution, filtering and number of channels required for a particular customer.

By default, an Iguana run-‐time license allows setup for five channels. Additional channels
may be purchased from Interfaceware via Arlene Daly and Emilia Buddle.
Obtain the machine ID, as outlined above for Chameleon. This should be submitted along
with the customer name in the same way as Chameleon licenses. Based on the ID, a key will
be issued on the Interfaceware website. Iguana keys are considerably longer than
Chameleon keys.

Image notification
Customers who have purchased an image notification interface need a chameleon run-‐time
license as well, according to the following descriptions:
For single server environment — one license on the main server
For cluster environment — one license for each cluster node
For large installation environment —one license for the controller, one for each
cluster node (if present) and one for each remote node

18. Localization of CD-Film Files

During installation of the Viewer Software 3 files, INDEX.HTM, MANIFEST.HTM, and
README.TXT are placed in the C:\Integrad\Current\downloads\IHE folder. These files are
built in English and need to be translated and\or customized for localization.

1. Navigate to C:\Integrad\Current\downloads\IHE

2. Right Click on INDEX.HTM and Select Edit …


GE Healthcare

3. Make any necessary translations and/or customizations and Save File.

4. Open README.TXT


GE Healthcare

5. Make any necessary translations and/or customizations and Save File.
19. SSL Creation

The quick procedure
Everything is done in command line. After every step you should run "keytool -‐list -‐v -‐
keystore .keystore -‐storepass changeit" to verify the contents of the keystore. Also, make a
back up copy of the keystore because the changes are irreversible:
1) Create a new folder and copy the default keystore to it.
a) mkdir <nameofyourdirectory>
b) copy "C:\Program Files\jakarta-‐tomcat-‐5.5.7\.keystore" .
2) Delete the tomcat alias.
a) keytool -‐delete -‐alias tomcat -‐keystore .keystore -‐storepass changeit
3) Create a new tomcat alias
a) keytool -‐genkey -‐keyalg RSA -‐sigalg MD5withRSA -‐alias tomcat -‐keystore .keystore -‐
validity 9999 -‐storepass changeit

GE Healthcare
b) What is your first and last name? Enter your domain name or IP like
pacs.yourhospital.com or 172.1.1.10.
c) What is the name of your organizational unit? I usually put PACS-‐IW.
d) What is the name of your organization? Put the name of the customer.
e) What is the name of your City or Locality? City where this pacs is installed.
f) What is the name of your State or Province? Type out the full name of the state. New
York, not NY.
g) What is the two-‐letter country code for this unit? US for United States. Other country
codes.
h) Is <CN=pacs.yourhospital.com, OU=PACS-‐IW, O=Dynamic Imaging, L=Allendale,

ST=New Jersey, C=US> correct? Yes.
i) press ENTER to use the same password.
4) Generate the Certificate Signing Request(CSR).
a) keytool -‐certreq -‐sigalg MD5withRSA -‐alias tomcat -‐keystore .keystore -‐file

certreq.txt -‐storepass changeit
5) Submit CSR to certifying authority. Wait for certificate response.
a) Each authority has it's procedure. For testing purposes, you can try a Free Trial
Verisign Certificate.
6) Import intermediate certificates.
a) If you've named the file inter1.cer,

keytool -‐keystore .keystore -‐storepass changeit -‐keyalg RSA -‐import -‐trustcacerts -‐
alias inter1 -‐file inter1.cer
b) Repeat for each intermediate cert.
7) Import certificate response.
a) If you've named it cert.cer,

keytool -‐keystore .keystore -‐storepass changeit -‐keyalg RSA -‐import -‐trustcacerts -‐
alias tomcat -‐file cert.cer
8) Install the new keystore back into tomcat.
a) copy .keystore "C:\Program Files\jakarta-‐tomcat-‐5.5.7\.keystore"
b) Overwrite? Yes.
c) Restart Tomcat.

GE Healthcare
How certs work
To make the certificate warning go away, the SSL cert must fulfill 3
conditions:
The domain name in the keystore matches what the user types in to reach the site (ie.
192.0.0.3 or pacs.yourhospital.com).
Valid expiration date
It is signed by a trusted certifying authority.

The default certificate installed on PACS-‐IW fails all three of these (CN=TEST,
expires 8/8/2001, and is self signed).The first two are fixed just by creating a new
keystore. The last one requires the submission of the CSR to a certifying authority
and importing the certificate response and whatever intermediate certificates that
are necessary.

Intermediate Certificates: Most certifying authorities don't sign your certificate with
the root certificate found in your browser. Instead they will sign your cert with an
intermediate certificate. That certificate might be signed by yet another
intermediate certificate and so on until finally you reach the root certificate. So, our
job is to keep importing certificates to establish a "chain of trust" from the root
certificate to our keystore.

If you set the extension of the file to ".cer" you'll be able to open the cert in windows
and view "Issued to" and "Issued by". The certificate reply will be Issued to your
domain and Issued by the intermediate certificate. The intermediate certificate
might by Issued by another intermediate certificate and so on until you reach the
root certificate.
PKCS7
Verisign sometimes returns the signed cert and all the intermediates in one file. You
can't import it directly. What you need to do is convert it to be imported using
keytool.

If you open the file with notepad it should have a line somewhere in the beginning
that looks like "-‐-‐-‐-‐-‐-‐BEGIN PCKS7-‐-‐-‐-‐-‐-‐".

Just rename the file with the extension .p7b and double click on it to open the
Windows Encryption tool. It will display the chain of trust in sort of a tree fashion.
Expand out the tree and right-‐click on each cert and export each one as a "DER
encoded X.509 format." Then import each cert into the keystore as described in the
steps above.

Expired Certs

GE Healthcare

After a while, the cert will expire. Is there a way to update a keystore with a new
expiration date? No, there isn't. You need to either start from scratch with a new
keystore or if you backed up the keystore after you created the CSR, you can submit
same CSR and import the certs to a copy of the backed up keystore.


Additional Config Information

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Additional Config Information

Uploaded by

Copyright:

Available Formats

Additional Configuration Information

Oct-­12-­2009 Initial Release 1.0 JA

© 2008 General Electric Company. All rights reserved. Page i

Table of Contents

© 2008 General Electric Company. All rights reserved. Page ii

Additional Configuration Parameters

2. NATed Access to Servers

© 2008 General Electric Company. All rights reserved. Page 1

3. Forward Images between Servers

4. Query Retrieve Configuration

© 2008 General Electric Company. All rights reserved. Page 2

© 2008 General Electric Company. All rights reserved. Page 3

6. Support for Large Studies

© 2008 General Electric Company. All rights reserved. Page 4

© 2008 General Electric Company. All rights reserved. Page 5

9. Automatic Pre-­Fetch from Centera Archive

9.1 Functional Description

© 2008 General Electric Company. All rights reserved. Page 6

© 2008 General Electric Company. All rights reserved. Page 7

© 2008 General Electric Company. All rights reserved. Page 8

10. Client Dictation Integration

© 2008 General Electric Company. All rights reserved. Page 9

12. NM Default Preset

© 2008 General Electric Company. All rights reserved. Page 10

© 2008 General Electric Company. All rights reserved. Page 11

13. Internet Explorer Configuration

© 2008 General Electric Company. All rights reserved. Page 12

14. Disable UAC in Windows Vista OS

14.1 Method 1 -­ Using MSCONFIG

© 2008 General Electric Company. All rights reserved. Page 13

14.2 Method 2 -­ Using Regedit

14.3 Method 3 -­ Using Group Policy

© 2008 General Electric Company. All rights reserved. Page 14

© 2008 General Electric Company. All rights reserved. Page 15

14.4 Method 4 -­ Using Control Panel

3. Click one of the user accounts, such as Guest.

© 2008 General Electric Company. All rights reserved. Page 16

© 2008 General Electric Company. All rights reserved. Page 17

15. DICOM Printer Setup

© 2008 General Electric Company. All rights reserved. Page 18

16. Updating a license file in Centricity PACS-­IW

© 2008 General Electric Company. All rights reserved. Page 19

18. Localization of CD-­Film Files

© 2008 General Electric Company. All rights reserved. Page 20

© 2008 General Electric Company. All rights reserved. Page 21

19. SSL Creation

b) copy "C:\Program Files\jakarta-­‐tomcat-­‐5.5.7\.keystore" .

2) Delete the tomcat alias.

a) keytool -­‐delete -­‐alias tomcat -­‐keystore .keystore -­‐storepass changeit

3) Create a new tomcat alias

© 2008 General Electric Company. All rights reserved. Page 22

h) Is <CN=pacs.yourhospital.com, OU=PACS-­‐IW, O=Dynamic Imaging, L=Allendale,

i) press ENTER to use the same password.

4) Generate the Certificate Signing Request(CSR).

a) keytool -­‐certreq -­‐sigalg MD5withRSA -­‐alias tomcat -­‐keystore .keystore -­‐file

5) Submit CSR to certifying authority. Wait for certificate response.

6) Import intermediate certificates.

a) If you've named the file inter1.cer,

b) Repeat for each intermediate cert.

7) Import certificate response.

a) If you've named it cert.cer,

8) Install the new keystore back into tomcat.

a) copy .keystore "C:\Program Files\jakarta-­‐tomcat-­‐5.5.7\.keystore"

© 2008 General Electric Company. All rights reserved. Page 23

Oct-12-2009 Initial Release 1.0 JA

9. Automatic Pre-Fetch from Centera Archive

14.1 Method 1 - Using MSCONFIG

14.2 Method 2 - Using Regedit

14.3 Method 3 - Using Group Policy

14.4 Method 4 - Using Control Panel

16. Updating a license file in Centricity PACS-IW

18. Localization of CD-Film Files

b) copy "C:\Program Files\jakarta-‐tomcat-‐5.5.7\.keystore" .

a) keytool -‐delete -‐alias tomcat -‐keystore .keystore -‐storepass changeit

h) Is <CN=pacs.yourhospital.com, OU=PACS-‐IW, O=Dynamic Imaging, L=Allendale,

a) keytool -‐certreq -‐sigalg MD5withRSA -‐alias tomcat -‐keystore .keystore -‐file

a) copy .keystore "C:\Program Files\jakarta-‐tomcat-‐5.5.7\.keystore"