RMInstallation Guide

CareEnhance® Review Manager
9.0
Installation Guide
McKesson Health Solutions, LLC

www.mckesson.com
InterQual Support 800.274.8374
cesupport@mckesson.com
General Terms: McKesson Health Solutions LLC ("McKesson") is the Owner/Licensor of the InterQual® Clinical Decision Support
Criteria and Software (Clinical Content/Work). McKesson has prepared this Work for exclusive use of its Licensees of software
applications embodying the Clinical Content. This Work contains confidential and trade secret information of McKesson and is
provided to Licensees who have an existing License Agreement in force only under the time-limited license as provided under
that License Agreement. Licensee and any recipient thereunder shall use the Clinical Content in accordance with the terms and
conditions of the License Agreement.
If You Have Been Provided Access for Evaluation Purposes: McKesson Health Solutions LLC ("McKesson") is the
Owner/Licensor of the InterQual Clinical Decision Support Criteria and Software (Clinical Content/Work). McKesson has prepared
this Work for exclusive use of its Licensees of Software applications embodying the Clinical Content. This Work contains
confidential and trade secret information of McKesson and, if you have been provided access to the Work for evaluation purposes
only, is provided to you only under a nontransferable, nonexclusive license whose term is limited to the time frame set forth in
the e-mail notification sent to you containing your access password. You and any recipient hereunder shall use the Clinical
Content in accordance with the terms and conditions of this license and the e-mail notification. You are granted this license
solely for the purpose of your internal evaluation of the Clinical Content/Work as part of your decision whether to license the
Clinical Content/Work, and for no other purpose. You expressly agree to keep the Clinical Content/Work confidential and not to
release or disclose the Clinical Content/Work to any other third person without McKesson's express written permission. Further
reproduction, including but not limited to the printing of any of the Clinical Content/Work or results obtained as part of the
permitted evaluation, adaptation, incorporation into other media, and release of this Work by you is strictly prohibited except
upon prior written permission of an officer of McKesson. Notwithstanding the foregoing, any copies or reproductions of the
Clinical Content/Work made by you during the limited evaluation term shall be destroyed and shall not be used for any purpose
upon the expiration of the term.
Proprietary Notice: The McKesson InterQual® Criteria statements in this work, including, without limitation, the review rules,
directions, commentary, notes, reference summaries and other elements contained herein, and their selection, expression,
format, ordering and other attributes, constitute proprietary and confidential clinical decision support criteria (“Criteria”) and
software (“Software”) and are protected under United States and international copyright and other intellectual property laws.
McKesson asserts the rights described in 48 C.F.R. §§ 12.211-12. Alternatively, should the Government determine that this
license is inconsistent with Federal law or otherwise fails to satisfy the Government's needs, McKesson then asserts restricted
rights as prescribed by the Restricted Rights Notice (JUN 1987) contained in 48 C.F.R. § 52.227-14(g)(3). Moreover, if for any
reason, 48 C.F.R. § 12.211 is determined to be inapplicable to the technical data delivered under this license, then, at a
minimum, McKesson asserts those rights contained in 48 C.F.R. § 252.227-7015(b)(2). In this regard, the Government shall
not use technical data to manufacture additional quantities of any item (except as provided in 48 C.F.R. § 252.227-7015(b)(1)),
nor shall the Government release, perform, display, disclose, or authorize use of such technical data outside the Government,
without first obtaining McKesson's written permission.
Acknowledgments: The McKesson InterQual Criteria are developed by McKesson’s clinical research staff which includes
physicians, registered nurses, and other healthcare professionals. Many of McKesson's clinical staff hold advanced degrees and
case management certification. The clinical content is reviewed and validated by a national panel of clinicians and medical
experts, including those in community and academic practice settings, as well as within the managed care industry throughout
the United States. The clinical content is a synthesis of evidence-based standards of care, current practices, and consensus from
licensed specialists and/or primary care physicians.
Copyright © 2002-2010 McKesson Corporation and/or one of its subsidiaries. All Rights Reserved.
No portion of this publication may be copied, reproduced, or incorporated into any other media without McKesson's prior written
consent.
Produced in Ireland.
The Clinical Content/Work may incorporate the CPT® terminology developed and copyrighted by the American Medical
Association ("AMA"). The CPT codes and terminology are provided pursuant to a license agreement between McKesson and the
AMA.
CPT® copyright 2001-2009 American Medical Association. All rights reserved. Fee schedules, relative value units, conversion
factors and/or related components are not assigned by the AMA, are not part of CPT, and the AMA is not recommending their
use. The AMA does not directly or indirectly practice medicine or dispense medical services. The AMA assumes no liability for
data contained or not contained herein. CPT is a registered trademark of the American Medical Association. Applicable
FARS/DFARS Restrictions Apply to Government Use.
This product includes CPT which is commercial technical data and/or computer data bases and/or commercial computer software
and/or commercial computer software documentation, as applicable, which was developed exclusively at private expense by the
American Medical Association, 515 North State Street, Chicago, Illinois, 60610. U.S. Government rights to use, modify,
reproduce, release, perform, display, or disclose these technical data and/or computer data bases and/or computer software
and/or computer software documentation are subject to the limited rights restrictions of DFARS 252.227-7015(b)(2) (November
1995) and/or subject to the restrictions of DFARS 227.7202-1(a) (June 1995) and DFARS 227.7202-3(a) (June 1995), as
applicable, for U.S. Department of Defense procurements and the limited rights restrictions of FAR 52.227-14 (June 1987)
and/or subject to the restricted rights provisions of FAR 52.227-14 (June 1987) and FAR 52.227-19 (June 1987), as applicable,
and any applicable agency FAR Supplements, for non-Department of Defense Federal procurements.
THE CLINICAL CONTENT, AND ANY SOFTWARE THAT IS PROVIDED UNDER THIS AGREEMENT AND/OR LGPL IS PROVIDED "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL MCKESSON OR ANY
LGPL LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PORTIONS MODIFIED BY LICENSEE HAVE NOT BEEN
INDEPENDENTLY AUTHENTICATED IN WHOLE OR IN PART BY MCKESSON. MCKESSON IS NOT RESPONSIBLE FOR AND HEREBY
DISCLAIMS ANY LIABILITY RELATED TO ANY SUCH MODIFICATIONS AND THEIR INCLUSION HEREIN DOES NOT IMPLY
ENDORSEMENT BY MCKESSON OF MODIFICATIONS.
Trademarks and Registered Trademarks: InterQual®, Autobook®, CareEnhance®, SmartSheets™, and SIM plus™ are
registered trademarks or trademarks of McKesson Health Solutions LLC.
Thomson Reuters® DRG. Thomson Reuters® LOS. Copyright 2010. All Rights Reserved. Republication or redistribution of
Thomson Reuters content, including by framing or similar means, is prohibited without the prior written consent of Thomson
Reuters. “Thomson Reuters” and the Kinesis logo are trademarks of Thomson Reuters.
Windows® is a registered trademark of Microsoft Corporation, which neither endorses this product nor is affiliated with
McKesson.
Visual Basic and Visual Studio 2005 are either registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
Microsoft, Active Directory, FrontPage, IntelliMirror, Visual J#® .NET, and Visual Studio®2005 .NET 2003 are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Business Objects S.A. in the United States and in several other countries all over the world. Business
Objects is an SAP company. © Copyright 2009 SAP AG. All rights reserved.
Oracle Native, Oracle JDBC Driver Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation
and/or its affiliates. Copyright © 1995-2009, Oracle. All rights reserved.
InstallAnywhere 8.0 is a trademark of Flexera Software Inc. All contents are Copyright © 2008 Flexera Software, Inc. All rights
reserved.
jConnect™ is a trademark of Sybase. Sybase®, Powerbuilder® and Adaptive Server® are registered trademarks of Sybase, Inc.
Copyright © 1999-2004 by Sybase, Inc. All rights reserved.
Copyright © 1995-2008 VeriSign, Inc. All rights reserved.
AutoRun is a product from Tarma® Documentation and software are copyright © 1990-2003 Tarma Software Research Pty Ltd.
All rights reserved.Tarma Software Research is a trademark of Tarma Software Research Pty Ltd. Copyright © 1990-2008.
This product includes Zlib software, specifically the Zlib Compression Library, version 1.2.3. Copyright © 1995-2005 Jean-loup
Gailly and Mark Adler. All rights reserved. A copy of the license is located at http://www.zlib.net/zlib_license.html.
Symphonia™ is a trademark of Orion Systems NZ Limited. Copyright © 2002-2009 Orion Health. All rights reserved.
JAVA™, J2SE™, and JRE™ are trademarks of Sun Microsystems, Inc. Copyright 1994-2009 Sun Microsystems, Inc. All rights
reserved.
This product includes PocketSOAP software licensed under the Mozilla Public License, Version 1.1 (the “License”). Copyright ©
Simon Fell, 2000-2004. All rights reserved. You may not use this file except in compliance with the License. You may obtain a
copy of the License at http://www.mozilla.org/MPL/. Software distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and
limitations under the License. The Original Code is PocketSOAP. The Initial Developer of the Original Code is Simon Fell.
This product includes Nhapi software licensed under the Mozilla Public License, Version 1.1 (the “License”). Copyright © 2001-
2009. All rights reserved. You may not use this file except in compliance with the License. You may obtain a copy of the
License at http://www.mozilla.org/MPL/. Software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations
under the License. The Original Code is hapi. The Initial Developer of the Original Code is James Agnew.
This product includes iText software, specifically iText 2.1.5, licensed under the Mozilla Public License, Version 1.1 (the “MPL”)
and the Lesser General Public License (the “LGPL”). Copyright © 1999-2009 by Bruno Lowagie. All Rights Reserved. You may
not use this file except in compliance with the MPL and the LGPL. You may obtain a copy of the MPL at
http://www.mozilla.org/MPL/ or at http://www.lowagie.com/iText/MPL-1.1.txt, and a copy of the LGPL at
http://www.opensource.org/licenses/lgpl-2.1.php. Software distributed under the MPL is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the MPL for the specific language governing rights and
limitations under the MPL. The Original Code is iText. The Initial Developer of the Original Code is Bruno Lowagie. Software
distributed under the LGPL is distributed WITHOUT ANY WARRANTY; WITHOUT EVEN THE IMPLIED WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the LGPL for more details.
This product includes jTDS software. jTDS is licensed pursuant to the Lesser General Public License. Copyright © 2007 the
jTDS Project. All rights reserved. A copy of the license is located at http://www.opensource.org/licenses/lgpl-2.1.php. THIS
PROGRAM IS DISTRIBUTED WITHOUT ANY WARRANTY; WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
This product includes JasperReports software. JasperReports is licensed pursuant to the Lesser General Public License.
Copyright © 2000 - 2009 Jaspersoft Corporation. All rights reserved. A copy of the license is located at
http://www.opensource.org/licenses/lgpl-2.1.php. THIS PROGRAM IS DISTRIBUTED WITHOUT ANY WARRANTY; WITHOUT
EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General
Public License for more details.
This product includes JGroups software. JGroups is licensed pursuant to the Lesser General Public License. Copyright © 2002 -
2009 Bela Ban. All rights reserved. A copy of the license is located at http://www.opensource.org/licenses/lgpl-2.1.php. THIS
PROGRAM IS DISTRIBUTED WITHOUT ANY WARRANTY; WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
This product includes WSDL4J software (the “Program”) licensed under the Common Public License, Version 1.0 (the “License”).
A copy of the License may be obtained at http://www.opensource.org/licenses/cpl1.0.php. EXCEPT AS EXPRESSLY SET FORTH
IN THE LICENSE, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-
INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. EXCEPT AS EXPRESSLY SET FORTH IN THE
LICENSE, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS),
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE
OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
This application was built using the Tlist™ .Net for Winforms © Bennet-Tec Information Systems, Inc.
Copyright © 1994-2005 Bennet-Tec Information Systems, Inc. All rights reserved.
This product includes Java HTML Tidy (“JTidy”) software (HTML parser and pretty printer). Copyright © 1998-2000 World Wide
Web Consortium (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique,
Keio University). All Rights Reserved. A copy of the license is located at
http://jtidy.sourceforge.net/multiproject/jtidyservlet/license.html.
Bouncy Castle Java Library 1.43 Copyright © 2000-2009 The Legion of the Bouncy Castle (http://www.bouncycastle.org); THE
SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.
TxTextControl 10.1 Copyright © 1991-2009 The Imaging Source Europe GmbH. All Rights Reserved.
All rights are reserved by The Imaging Source Europe GmbH. "TX Text Control" is a registered trademark of The Imaging
Source Europe GmbH in the United States of America, European Union and other foreign jurisdictions.
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/). Copyright © 2000-
2005, The OpenSymphony Group. All rights reserved. (1) Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. (2) Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution. (3) The end-user documentation included with the redistribution, if any, must include the following
acknowledgment: 'This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).'
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally
appear. (4) The names 'OpenSymphony' and 'The OpenSymphony Group' must not be used to endorse or promote products
derived from this software without prior written permission. For written permission, please contact license@opensymphony.com.
(5) Products derived from this software may not be called 'OpenSymphony' or 'WebWork', nor may 'OpenSymphony' or
'WebWork' appear in their name, without prior written permission of the OpenSymphony Group. THIS SOFTWARE IS PROVIDED
'AS IS' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE
FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. A copy of the license may be obtained at
http://www.opensymphony.com/oscache/license.action.
This product includes software developed by the Apache Software Foundation (http://www.apache.org). Copyright © 1999-
2009 The Apache Software Foundation, Licensed under the Apache License, Version 2.0. (the “License”); you may not use this
file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-
2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS
IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific
language governing permissions and limitations under the License.
This product includes software (“Jetty”) developed by Mort Bay Consulting Pty. Ltd. Copyright 1995-2009 Mort Bay Consulting
Pty. Ltd. Jetty is licensed under the Apache License, Version 2.0., a copy of which may be obtained at
http://www.apache.org/licenses/LICENSE-2.0, subject to additional licenses and notice requirements available at
http://svn.codehaus.org/jetty/jetty/branches/jetty-6.1/NOTICE.txt.
This product includes software developed by the Apache Software Foundation (http://www.apache.org). Copyright © 2000 The
Apache Software Foundation. All rights reserved. (1) Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer. (2) Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with
the distribution. (3) The end-user documentation included with the redistribution, if any, must include the following
acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally
appear. (4) The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived
from this software without prior written permission. For written permission, please contact apache@apache.org. (5) Products
derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission
of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ”AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
This software may contain fonts developed by MAGENTA Ltd. Copyright © 2004 by MAGENTA Ltd. All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of the fonts accompanying this license ("Fonts")
and associated documentation files (the "Font Software"), to reproduce and distribute the Font Software, including without
limitation the rights to use, copy, merge, publish, distribute, and/or sell copies of the Font Software, and to permit persons to
whom the Font Software is furnished to do so, subject to the following conditions:
The above copyright and this permission notice shall be included in all copies of one or more of the Font Software typefaces. The
Font Software may be modified, altered, or added to, and in particular the designs of glyphs or characters in the Fonts may be
modified and additional glyphs or characters may be added to the Fonts, only if the fonts are renamed to names not containing
the word "MgOpen," or if the modifications are accepted for inclusion in the Font Software itself by the each appointed
Administrator. This License becomes null and void to the extent applicable to Fonts or Font Software that has been modified and
is distributed under the "MgOpen" name. The Font Software may be sold as part of a larger software package but no copy of one
or more of the Font Software typefaces may be sold by itself. THE FONT SOFTWARE IS PROVIDED "AS IS," WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN
NO EVENT SHALL MAGENTA OR PERSONS OR BODIES IN CHARGE OF ADMINISTRATION AND MAINTENANCE OF THE FONT
SOFTWARE BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.
This product includes software developed by the Thai Open Source Software Center Ltd. and Clark Cooper. Copyright © 1998,
1999, 2000 Thai Open Source Software Center Ltd. and Clark Cooper. Permission is hereby granted, free of charge, to any
person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The
above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE
SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.
Patents: Autobook® is U.S. Pat. No. 6,049,794. QualityFIRST U.S. Pat. Numbers are 5,583,758 and 5,953,704.
Notice
The Clinical Content reflects clinical interpretations and analyses and cannot alone either resolve medical ambiguities of
particular situations or provide the sole basis for definitive decisions. The Clinical Content is intended solely for use as
screening guidelines with respect to the medical appropriateness of healthcare services and not for final clinical or
payment determinations concerning the type or level of medical care provided, or proposed to be provided, to a patient.
THE CLINICAL CONTENT IS PROVIDED “AS IS.” MCKESSON HEALTH SOLUTIONS LLC DISCLAIMS ANY OTHER
WARRANTY, EXPRESS OR IMPLIED, INCLUDING AS TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
OR SERVICE OF THE CLINICAL CONTENT, OR THE COMPATIBILITY OF OUTPUT USING THE CLINICAL CONTENT WITH
ANY LAW, REGULATION, OR ORDER. IN NO EVENT SHALL MCKESSON HEALTH SOLUTIONS LLC BE LIABLE FOR
SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES IN CONNECTION WITH, OR ARISING OUT OF, ANY
USE OF THE CLINICAL CONTENT.
275 Grove Street Tel: 617.273.2800

Suite 1-110 Fax: 617.273.3777
Newton, MA 02466-2273 cesupport@mckesson.com
USA www.mckesson.com
Contents
Welcome to the Installation Guide

Who Should Read this Guide .................................................................................................. 10
Product Support ................................................................................................................... 10
Accessing MHS Customer Hub ........................................................................................... 11
Obtaining Product Support ................................................................................................ 11
Chapter 1 Supported Technical Configurations

Review Manager Production Configurations.......................................................................... 12
Supported Installation Configurations ...................................................................................... 13
Server Software .............................................................................................................. 13
Client Workstation Software .............................................................................................. 13
Additional Required Software ................................................................................................. 14
Recommended Hardware Configurations .................................................................................. 15
Chapter 2 Installation Overview

Upgrading or Adding Products to CareEnhance Review Manager .................................................. 16
Installing CareEnhance Review Manager Enterprise for Windows with Jetty ................................... 16
Installing CareEnhance Review Manager Enterprise for Windows with WebSphere.......................... 16
Installing Review Manager Enterprise for Windows with Jetty and Microsoft® IIS .......................... 17
Installing CareEnhance Review Manager Enterprise for Linux with WebSphere .............................. 17
Installing CareEnhance Review Manager .................................................................................. 17
Chapter 3 Upgrading or Adding Products to Review Manager

Enterprise for Windows with Jetty
Before Upgrading to Review Manager Enterprise 9.0.................................................................. 18
Updating the Database .......................................................................................................... 19
Updating a Microsoft Access Database ................................................................................ 19
Updating a Microsoft SQL Server Database.......................................................................... 19
Updating an Oracle Database ............................................................................................ 21
Starting the Review Manager Enterprise Upgrade ...................................................................... 22
Customizing the Installation ................................................................................................... 24
Completing the Upgrade ........................................................................................................ 25
Importing Thomson Reuters® LOS Description Files .................................................................. 25
Migrating Organizational Policies ............................................................................................. 26
Chapter 4 Upgrading or Adding Products to Review Manager

Enterprise for Windows with WebSphere
Updating the Review Manager Database .................................................................................. 27
Upgrading the Review Manager Enterprise Application Files ........................................................ 28
Default Directory Paths for Windows........................................................................................ 28
Default Server and Node Names ............................................................................................. 28
CareEnhance Review Manager Installation Guide 6

Contents
Copying the Required Files..................................................................................................... 29

Documentation files and War files ...................................................................................... 29
Editing the oscache.properties File ..................................................................................... 30
Editing the ReviewManager.xml File ................................................................................... 31
Upgrading the Outbound HL7 Service and the Inbound HL7 Service ........................................ 31
Chapter 5 Upgrading Review Manager Enterprise for Linux with

WebSphere
Updating the Review Manager Database .................................................................................. 32
Upgrading the Review Manager Enterprise Application Files ........................................................ 33
Default Directory Paths for Linux ............................................................................................ 33
Copying the Required Files..................................................................................................... 34
Upgrading the Outbound HL7 Service and the Inbound HL7 Service ........................................ 37
Chapter 6 Creating a WebSphere Cluster

Default Directory Paths for Windows and Linux ......................................................................... 39
Creating the WebSphere Cluster ............................................................................................. 40
Creating the WebSphere Application Server Nodes ............................................................... 40
Creating a New Cluster ..................................................................................................... 42
Configuring the Application Servers for Linux............................................................................ 47
Starting the Node Agents....................................................................................................... 50
Chapter 7 Installing Review Manager Enterprise

Before You Begin .................................................................................................................. 51
Creating the Database........................................................................................................... 52
Creating a Microsoft SQL Server Database .......................................................................... 52
Creating an Oracle Database ............................................................................................. 53
Starting the Installation Process ............................................................................................. 54
Customizing the Installation ................................................................................................... 56
Customizing the Server Software ............................................................................................ 58
Completing the Installation .................................................................................................... 59
Installing Multiple Instances of Review Manager Enterprise......................................................... 60
Copying Review Manager Enterprise Application Files to Additional WebSphere Nodes .................... 60
Documentation files and War files ...................................................................................... 61
Assigning Review Transfer Communication Handlers to Application Servers in the Cluster .......... 63
Chapter 8 Logging on to CareEnhance Review Manager

Before Logging on to CareEnhance Review Manager for the First Time ......................................... 65
Configuring Internet Explorer ............................................................................................ 65
Configuring PDF Viewing Options ....................................................................................... 66
Starting CareEnhance Review Manager .................................................................................... 66
Logging on to CareEnhance Review Manager ............................................................................ 67

Contents
Chapter 9 Installing Review Manager Enterprise for Linux

Prerequisites for Installation................................................................................................... 68
Creating the Review Manager Enterprise Database .................................................................... 69
Populating the Review Manager Enterprise Database ................................................................. 69
Copying Required Files for Linux with WebSphere ..................................................................... 69
Installing Verdana Font .................................................................................................... 72
Chapter 10 Installing and Configuring Inbound and Outbound HL7 for

Linux-based
WebSphere Installations
Prerequisites ........................................................................................................................ 74
Installing and Configuring the Outbound HL7 Service................................................................. 74
Verifying the Outbound HL7 Installation................................................................................... 75
Assigning an Application Server to Be the Outbound HL7 Handler ................................................ 75
Installing and Configuring the Inbound HL7 Service................................................................... 76
Starting the Inbound HL7 Service ...................................................................................... 77
Stopping the Inbound HL7 Service ..................................................................................... 77
Upgrading the Outbound HL7 Service ...................................................................................... 77
Upgrading the Inbound HL7 Service ........................................................................................ 78
Chapter 11 Configuring Inbound and Outbound HL7 for Windows-

based WebSphere Installations
Prerequisites ........................................................................................................................ 81
Configuring the Outbound HL7 Service .................................................................................... 81
Verifying the Outbound HL7 Installation................................................................................... 82
Assigning an Application Server to Be the Outbound HL7 Handler ................................................ 82
Configuring the Inbound HL7 Service....................................................................................... 83
Starting and Stopping the Inbound HL7 Service ................................................................... 83
Upgrading the Outbound HL7 Service ...................................................................................... 84
Upgrading the Inbound HL7 Service ........................................................................................ 84
Chapter 12 Installing Review Manager Enterprise as a WebSphere

Application
Installing the Review Manager Enterprise Application................................................................. 86
Installing the Review Manager Enterprise Help Application.......................................................... 91
Starting the Cluster .............................................................................................................. 92
Verifying the Virtual Host Configuration ................................................................................... 93
Completing the Installation .................................................................................................... 94
Chapter 13 Configuring Microsoft® IIS for Review Manager Enterprise

Configuring Jetty to Accept Proxied Requests............................................................................ 95
Configuring the Jetty Connector.............................................................................................. 96
Configuring IIS 6.0 ............................................................................................................... 99
Adding the isapi_redirect.dll as a Web Server Extension ....................................................... 101
Configuring IIS 7.0 .............................................................................................................. 103

Contents
Appendix A Upgrading or Adding Products to Review Manager

Before Upgrading to Review Manager 9.0 ............................................................................... 107
Updating the Database ......................................................................................................... 108
Updating a Microsoft Access Database ............................................................................... 108
Updating a Microsoft SQL Database ................................................................................... 108
Starting the Review Manager Upgrade Process........................................................................ 110
Customizing the Upgrade...................................................................................................... 112
Upgrading an Administrator Package ................................................................................. 112
Upgrading a Client Package.............................................................................................. 112
Completing the Upgrade ....................................................................................................... 113
Migrating Organizational Policies ....................................................................................... 113
Appendix B Installing Review Manager

Before You Begin ................................................................................................................. 114
Creating the Database.......................................................................................................... 115
If You Use Microsoft Access .............................................................................................. 115
If You Use Microsoft SQL Server ....................................................................................... 115
Starting the Installation Process ............................................................................................ 116
Customizing the Installation .................................................................................................. 118
Installing the Administrator Package........................................................................... 118
Installing a Client Package ............................................................................................... 119
Completing the Installation ................................................................................................... 120
Appendix C Troubleshooting Tips

Separate Database and Application Servers............................................................................. 121
Internet Explorer Security Settings ........................................................................................ 121
Viewing the Online Help........................................................................................................ 122
Viewing Log Files ................................................................................................................. 122
Debugging Information......................................................................................................... 123
Database Connections .......................................................................................................... 124
Java Virtual Machine Tuning .................................................................................................. 124
CacheSize in CareEnhance Review Manager.xml ...................................................................... 125
Jetty MaxThreads Count ....................................................................................................... 125
HL7 Server Linux Script Change............................................................................................. 126
Appendix D Setting Up SSL Security Using Digital Certificates

Certificate Signature Request (CSR) and Private Keys............................................................... 127
Installing Digital Certificates for Jetty ..................................................................................... 129
Prerequisites .................................................................................................................. 129
VeriSign/Thawte ............................................................................................................. 129
Certificates Notes ................................................................................................................ 133
VeriSign ........................................................................................................................ 133
Thawte.......................................................................................................................... 134

Preface
Welcome to the Installation Guide

This guide explains how to install:
 CareEnhance® CareEnhance Review Manager™ Enterprise
 CareEnhance® Review Manager Enterprise for Red Hat Enterprise Linux
This guide explains the hardware and software requirements and tasks that
you should perform before you begin the installation process.
This preface contains the following topics:

 Who Should Read this Guide
 Product Support
Who Should Read this Guide

This book is intended for the person who installs software at your organization.
If you are installing CareEnhance Review Manager Enterprise for Red Hat
Enterprise Linux, the descriptions and procedures in this guide require that
you be familiar with the following:
 Red Hat Enterprise Linux
 IBM® WebSphere® Application Server and WebSphere server clustering
Product Support
You can contact Product Support in the following ways:
 Phone—1-800-CRITERIA or 1-800-274-8374
 E-mail—cesupport@mckesson.com
 Web—MHSCustomerHub.McKesson.com

Product Support
Accessing MHS Customer Hub

The MHS Customer Hub (http://MHSCustomerHub.McKesson.com) provides
interactive support, answers to commonly asked questions, and links to other
resources. To obtain a user ID and password, from the MHS Customer Hub
Welcome page, click “Need a User ID and Password?” For additional
assistance, contact your MHS Customer Hub site administrator.
Obtaining Product Support

If you experience difficulties using the software that you have licensed, please
do the following before you contact Product Support:
 Consult the documentation that accompanies the software.
 Consult your internal help desk.
If you still cannot resolve your problem, before contacting Product Support,
please do the following to assist the Product Support representative in
expediting the diagnosis and resolution of your problem:
 Record the nature of the problem and what you were doing just before the
problem occurred.
 Determine the release number and the build number of the software that
you are using. To obtain this information, on the menu bar, click Help and
then click the “About” option.
 If possible, contact Product Support from in front of your workstation with
the relevant application open.
The response guidelines for Product Support are as follows:
Priority Level Description Callback How To Contact

Product Support
Urgent An issue adversely affecting your ability to operate Within 30 minutes Phone
your business or causing financial liability due to
operational or information deficiency, provided the
issue renders the supported software inoperable for
the majority of users
High An issue that repeatedly affects your use of the Within 1 business Phone
supported software or data integrity hour
Medium An issue that minimally affects your usage of the Within 4 business Submit the issue
supported software or data integrity hours through the MHS
Customer Hub Web
site, phone, or e-mail
Standard An issue of cosmetic nature; a matter of style, Within 8 business Submit the issue
efficiency, or convenience or a usage clarification hours through the MHS
that does not interfere with the operation of your Customer Hub Web
business site, phone, or e-mail

1
Supported Technical Configurations
Review Manager is a Web browser-based software application that delivers

InterQual® Criteria in an efficient, easy-to-use way.
The following are sample installation configurations for CareEnhance® Review

Manager 9.0. This document does not list all of the possible installation
configurations for Review Manager and does not state or imply any specific
level of performance. The listed configurations apply only to Review Manager
9.0 and are subject to change with each new release of Review Manager.
Before purchasing any additional hardware or software to support your Review
Manager implementation or for more information about performance and
installation configurations, consult your McKesson account representative.
Review Manager Production Configurations
Configuration 1 Configuration 2
End User
Workstation
End User Web Server

Workstation Application Server
CareEnhance Review Manager
Web Server Enterprise
DBMS
Configuration 3
DBMS
Web Server
Application Server
DBMS Application Server
CareEnhance Review Manager End User
Enterprise Workstation
Enterprise

1 Supported Installation Configurations
Supported Installation Configurations

McKesson supports Review Manager when it is installed in these configurations.
The language setting for all Review Manager software is “US English.”
Server Software
Table 1–1
Application App. Server OS Web Server DBMS
Server
Jetty 6.1.20a  Microsoft® Windows® Server 2003 Jetty 6.1.20a or Microsoft Access b,c,d
SP2 IIS 6.0 on 32-bit server
 32-bit server or 64-bit server Any of the following on 32-
Jetty 6.1.20 a

® ®
Microsoft Windows Server 2008 a
Jetty 6.1.20 or bit server or 64-bit server:
 32-bit server or 64-bit server IIS 7.0  Oracle 10g (10.2.0.4)
 Oracle 11g (11.1.0.7 R1)
IBM® WebSphere®  Microsoft Windows Server 2003 SP2 Apache 2.2 HTTP
7.0  Microsoft SQL Server
 32-bit server
2005 SP3e
IBM WebSphere 7.0  Red Hat Enterprise Linux Version IBM HTTP Server
 Microsoft SQL Server
4.0 Updater 6f 7.0g
2008 SP1e
 32-bit server
a. McKesson includes the Jetty Web and application servers with Review Manager.
b. You cannot use an Access database if Review Manager is installed on a Linux server.
c. Review Manager and InterQual® View use the Microsoft JET Database Engine to connect to the Access database.
These applications do not require you to have Microsoft Access installed. For Access installations, Review
Manager automatically installs the JET Database Engine. Microsoft Access is required only to view the data in an
Access database outside of the Review Manager application. Note that Microsoft requires an Access license when
10 or more users access an individual Access database.
d. McKesson recommends that you do not use Review Manager with a Microsoft Access database in production
environments.
e. McKesson will support compatibility mode for the CareEnhance® Care Manager Software.
f. A Microsoft Windows-based computer is required to initially install the Review Manager application files and
populate the Review Manager database.
g. Bundled with WebSphere 7.0.
Client Workstation Software

Table 1–2
Client Application Client Operating System Other Required Software
Review Manager Enterprise 9.0 or Any of the following Microsoft operating Any of the following:
Review Manager (desktop version) 9.0 systems:  Internet Explorer 6.0a,b
 Microsoft Windows XP SP2 on 32-bit SP2
client or 64-bit client  Internet Explorer 7.0b
 Microsoft Windows XP SP3 on 32-bit  Internet Explorer 8.0b
client
 Microsoft Windows Vista Business
Edition SP1 on 32-bit client

1 Additional Required Software
Table 1–2
Client Application Client Operating System Other Required Software
Custom Criteria Utility 4.0 Any of the following Microsoft operating Review Manager 9.0
systems on 32-bit client: Any of the following:
 Microsoft Windows XP SP2  Internet Explorer 6.0a,b
 Microsoft Windows XP SP3 SP2
 Microsoft Windows Vista Business  Internet Explorer 7.0b
Edition SP1  Internet Explorer 8.0b
Review Manager Enterprise Mobile Any of the following Microsoft PDA Microsoft ActiveSync® 4.5
5.2 operating systems: (Windows XP only)
 Windows Mobile 2003 Microsoft Windows Mobile
 Windows Mobile 2003 Second Edition Device Center
(Windows Vista only)
 Windows Mobile 5.0
 Windows Mobile 6.0 Professional
Edition
a. Review Manager 9.0 is the last release for which Internet Explorer 6.0 will be supported.
b. McKesson supports only Internet Explorer (32-bit), even on a 64-bit PC.
Additional Required Software

McKesson supports Review Manager when it is used with the following software platforms
Table 1–3
Software Version Notes
SUN JRE 1.6.0_16 The JRE/JVM is automatically installed with Jetty.
Sun JDK/JVM 6.0 1.6.0_16 Only 32-bit JDK/JVM is supported.
IBM JDK 6.0 Sun JVM 6.0 McKesson supports this configuration with WebSphere-based installations only.
compatible
Microsoft 9.0c and DirectX is required only on the workstation used to run the installation program.
DirectX® later
Crystal Reports 11 and later  Crystal Reports is required only to create custom reports.
 Although version CRxi R3 is available, it is not supported by McKesson.
Adobe Reader 8.x or 9.x Reader is required to display Review Manager PDF files, such as the
documentation and Clinical Evidence Summaries.
Adobe Flash 9.x and later This is a new requirement starting with Review Manager 9.0.
Player

1 Recommended Hardware Configurations
Recommended Hardware Configurations

McKesson recommends using Review Manager on computers with the following
minimum hardware specifications to experience appropriate Review Manager
application performance. These are the minimum specifications recommended.
Table 1–4
Review Manager Process RAM Hard Disk Spacea Other
Component or
Review Manager Enterprise 2 GHz 2 GB  1 GB without the N/A
Server Intel® Review Manager
processor database or
or InterQual® View
equivalent database installed on
the same computer
 40 GB minimum with
the Review Manager
database also
installed on the same
computer
 10 GB minimum with
the InterQual® View
database also
installed on the same
computer
DBMS Server 2 GHz 2 GB 40 GB minimum for the N/A
Intel database with or without
processor Review Manager or
or InterQual® View
equivalent installed on the same
computer
Review Manager Enterprise 1 GHz 512 MB 1 GB 1024 x 768 pixel or
Client Workstation Intel higher monitor
processor resolution
or
equivalent
Review Manager (desktop 1 GHz 512 MB 1 GB without the 1024 x 768 pixel or
version) Workstation Intel database or 40 GB higher monitor
processor minimum with the resolution
or database on the same
equivalent computer
Custom Criteria Utility 1 GHz 512 MB 1 GB 1024 x 768 pixel or
Workstation Intel higher monitor
processor resolution
or
equivalent
a. The hard disk space recommendations are estimated values. Your organization must determine the actual values
based on your pattern of present and future use. McKesson is not responsible for failing to provide adequate hard
disk space estimates.

2
Installation Overview
This guide includes installation and upgrade instructions for each supported
CareEnhance Review Manager platform. The following sections describe the
relevant installation and upgrade chapters for each supported platform.
Upgrading or Adding Products to CareEnhance Review

Manager
Refer to the appropriate chapter for your product:
 Chapter 3, “Upgrading or Adding Products to Review Manager Enterprise for
Windows with Jetty”
 Chapter 4, “Upgrading or Adding Products to Review Manager Enterprise for
Windows with WebSphere”
 Chapter 5, “Upgrading Review Manager Enterprise for Linux with
WebSphere”
 Appendix A, “Upgrading or Adding Products to Review Manager”
Installing CareEnhance Review Manager Enterprise for

Windows with Jetty
 Chapter 7, “Installing Review Manager Enterprise”
 Chapter 8, “Logging on to CareEnhance Review Manager”
Installing CareEnhance Review Manager Enterprise for

Windows with WebSphere
1. Chapter 6, “Creating a WebSphere Cluster”
2. Chapter 7, “Installing Review Manager Enterprise”

2 Installing Review Manager Enterprise for Windows with Jetty and Microsoft® IIS
3. Chapter 11, “Configuring Inbound and Outbound HL7 for Windows-based

WebSphere Installations”
4. Chapter 12, “Installing Review Manager Enterprise as a WebSphere
Application”
5. Chapter 8, “Logging on to CareEnhance Review Manager”
Installing Review Manager Enterprise for Windows with Jetty

and Microsoft® IIS
2. Chapter 13, “Configuring Microsoft® IIS for Review Manager Enterprise”
Installing CareEnhance Review Manager Enterprise for Linux

with WebSphere
1. Chapter 6, “Creating a WebSphere Cluster”
3. Chapter 9, “Installing Review Manager Enterprise for Linux”
4. Chapter 10, “Installing and Configuring Inbound and Outbound HL7 for
Linux-based WebSphere Installations”
5. Chapter 12, “Installing Review Manager Enterprise as a WebSphere
Application”
Installing CareEnhance Review Manager

 Appendix B, “Installing Review Manager”
 Chapter 8, “Logging on to CareEnhance Review Manager”

3
Upgrading or Adding Products to Review
Manager Enterprise for Windows with Jetty
This chapter describes all the tasks that you need to perform to upgrade to
CareEnhance Review Manager Enterprise 9.0 or to add new products to an
existing installation of Review Manager Enterprise 9.0.
For installations using Jetty, Review Manager Enterprise 9.0 requires Jetty
6.1.20. The Review Manager installation program automatically upgrades Jetty
during the installation process to ensure that you are using this version.
Before Upgrading to Review Manager Enterprise 9.0

If you have already upgraded to Review Manager Enterprise 9.0 and are
adding new products only, do not update the database. Continue with the
section “Starting the Review Manager Enterprise Upgrade” on page 22.
Before upgrading to Review Manager Enterprise 9.0, do the following:

 Review the system requirements in Chapter 1, “Supported Technical
Configurations.”
 Review the Review Manager 9.0 Release Notes.
 Before upgrading, you should create a full backup of your CareEnhance
Review Manager database.
During installation, Review Manager creates a backup of your existing

installation directory and indicates the location where it has been backed up
to. See “Customizing the Installation” on page 24.
 Obtain the Customer ID, Product Key, and Organization values for the
upgrade. Your McKesson representative will provide you with this
information.
 Make sure that all users have logged out of Review Manager Enterprise.
 Ensure that the Windows user upgrading Review Manager Enterprise has
administrative rights to the installation workstation.

3 Updating the Database
 You can upgrade to Review Manager Enterprise either from version 7.x or
8.x. If you are upgrading from a version prior to 7.0, then you must first
upgrade to version 7.0 before upgrading to version 9.0.
If you upgrade directly from Review Manager Enterprise 7.0 to version 9.0,
the InterQual 2010 Criteria (which is included with Review Manager
Enterprise 9.0) will be installed, but the InterQual 2009 Criteria (which was
included with Review Manager Enterprise 8.0) will not be installed. If you
also want the InterQual 2009 Criteria, then you must first upgrade to Review
Manager Enterprise 8.0 before upgrading to version 9.0.
McKesson recommends upgrading your Review Manager Enterprise test

environment to version 9.0 before upgrading your production environment.
Updating the Database

If you have already upgraded to Review Manager Enterprise 9.0 and are
adding new products only, do not update the database. Continue with the
section “Starting the Review Manager Enterprise Upgrade” on page 22.
Before upgrading the Review Manager Enterprise software, you must first
update the Review Manager database.
Updating a Microsoft Access Database

To maintain the integrity of the database, McKesson strongly recommends
that you run a Repair and Compact on the database prior to installing new
criteria and then again after the installation is completed. For information
about Repair and Compact, see the CareEnhance Review Manager System
Administrator’s Guide.
The Review Manager upgrade process automatically runs the

access_upgrade.sql database script, which is found on the Review Manager
installation DVD in the Scripts folder. This script makes all the necessary
database changes; no user interaction is required.
Updating a Microsoft SQL Server Database

This section describes how to update your Review Manager SQL database.
Upgrading your Microsoft SQL Server Software

If along with your Review Manager Enterprise upgrade you are also upgrading
your Microsoft SQL Server software (for example, from SQL Server 2005 to
SQL Server 2008), then you must first upgrade to your new version of
Microsoft SQL Server, before you upgrade to the latest version of Review

Manager Enterprise. Make sure to backup your database before and after
upgrading Review Manager Enterprise and before upgrading your
database server.
Updating your Review Manager SQL Database

You must perform the following procedure before upgrading Review Manager
Enterprise. Failure to do so will cause errors when accessing the new features
in Review Manager Enterprise. If you have not upgraded your database, the
Review Manager installer will generate an error message and cancel the
upgrade process.
To update your Review Manager SQL database:

1. Log on to Query Analyzer or SQL Server Management Studio as the user
who ran the mss_create.sql script that was used when the database was
created (that is, the owner of the Review Manager tables).
To find the user ID that was used to run this create the database, open the
CareEnhance Review Manager Connection XML Editor (RmXmlEdit.bat),
which is located in the Jetty folder
(C:\Program Files\McKesson\CERME\Jetty by default). The following image
shows the Connection XML Editor interface.
The password associated with this user ID is encrypted and not listed in the
Connection XML Editor. If you forgot the password for this user, use SQL
Server Management Studio to change the user’s password. Make sure to
test the connection when you are done.
Run the mss_upgradeto90.sql script against the Review Manager database.

This script is on the Review Manager installation DVD in the Scripts folder.

Updating an Oracle Database

This section describes how to update your Review Manager Oracle database.
Upgrading your Oracle Software

If along with your Review Manager Enterprise upgrade you are also upgrading
the version of your Oracle software (for example, from Oracle 10g to Oracle
11g), then you must first upgrade to your new version of Oracle and then
upgrade to the latest version of Review Manager. Make sure to backup your
database before and after upgrading Review Manager Enterprise and
before upgrading your database server.
Updating your Review Manager Oracle Database

You must do the following procedure before upgrading any administrator or
client workstations. Failure to do so will cause errors when accessing the new
features of Review Manager. If you have not upgraded your database, the
upgrade process.
To update your Review Manager Oracle database:

1. Log in to your interactive SQL tool (such as SQL*Plus) as the user that you
specified in the oracle_crt_db.sql script.
2. Run the oracle_upgradeto90.sql script against the Review Manager
database.

3 Starting the Review Manager Enterprise Upgrade
Starting the Review Manager Enterprise Upgrade

To start the upgrade process:
1. McKesson recommends that you close all Windows programs, and close any
anti-virus applications.
2. Stop the CERME service and, if applicable, the CERMEHL7 service, and then
close the Services window. Stopping the CERME service will log out any
users that are connected to Review Manager Enterprise.
3. Do either of the following:
 To install Review Manager from the DVD, place the Review Manager
installation DVD into your DVD drive.
The Review Manager DVD has an autorun feature. If autorun is not
enabled on your PC, use Windows Explorer to navigate to your DVD
drive, and open the main.htm file to begin the installation.
 To install Review Manager from a network location, access that
network location and open the main.htm file.
Before the installation begins, you can view and print the Release Notes,
Installation Guides, and System Administrator’s Guide.
4. Click any of the links to view a document. The document opens in a
separate window. View or print the document as necessary.
5. Once you have reviewed the documents, click Continue to proceed with the
installation.
6. Click Install Review Manager/InterQual View.
7. In the File Download window, click Run. When prompted to run software
from publisher McKesson Health Solutions, click Run again.
The installation program will check for available disk space on your C:\, or
home, drive. If there is not enough space, the installation program will
prompt you to select a different drive.
8. Read the information on the Introduction window, and then click Next.
To abort the installation at any point, click Cancel on any installation window.
If you want to go back to a previous window, click Previous on any
installation window.
The License Agreement window appears. The license agreement displays

legal contract issues.
9. Agree to the licensing terms by selecting “I accept...” and then click Next.
The Licensing Information window appears.
To obtain your Customer ID, Product Key, and Organization information,
contact McKesson Product Support.
10.Enter the values exactly as provided by McKesson (including any hyphens),
and then click Next.
The Product Key is 30 characters including hyphens.
When you call McKesson Product Support, you will also receive a default
username and password, which you must use to initially access the
application.

3 Starting the Review Manager Enterprise Upgrade
The Licensed Products Window appears. The Licensed Product window

shows the product, database, and criteria sets for which your organization
is licensed.
The items listed will vary depending on which products your organization has
licensed.
11.Review the list of available products, and then click Next.

The Select Review Manager Application window appears. If you are licensed
for Review Manager Enterprise, Review Manager, and InterQual View, then
the installer will prompt you to choose which product to upgrade.
12.Select Review Manager Enterprise, and then click Next.
The CareEnhance Review Manager Enterprise Installation Type window
appears.
13.Choose the type of upgrade:
 If you are upgrading to a new version of Review Manager
Enterprise (for example, if you are currently running version 8.0 and
want to install version 9.0), select Upgrade, and then click Next.
Choosing the Upgrade option updates your Review Manager Enterprise
software in addition to installing any new products you choose.
 If you are adding new products only (for example, if you already
upgraded your Review Manager Enterprise software to version 9.0, and
you want to install a new criteria product), select Add new products, and
then click Next.
The Existing CERME Installation Location window appears.
14.Continue with the procedure “Customizing the Installation” on page 24.

3 Customizing the Installation
Customizing the Installation

The Existing CERME Installation Location window specifies the location of your
existing installation of Review Manager Enterprise.
1. Click Browse and navigate to the path where your existing installation of
Review Manager Enterprise was installed, and then click Next. The default
path is C:\Program Files\McKesson\CERME.
Review Manager creates a backup of your existing installation and displays
a message indicating the location where it has been backed up to.
2. Click OK in the message.
 If your previous installation uses the Jetty application server, the
Choose Components window appears.
 If your previous installation uses an application server other
than Jetty, the Existing ReviewManager.xml File window appears.
a. Click Browse, and then navigate to the path where the original
ReviewManager.xml file was installed.
b. Click Next.
The Choose Components window appears. The Choose Components
window displays a list of all licensed products.
3. Select which products to install, and then click Next:
 Select the criteria sets that you want to install. You can install all of the
criteria sets for which you are licensed or you can customize your
installation to include only certain criteria sets.
 To copy the Enterprise Mobile installer to your server, select RME Mobile.
 To copy the Custom Criteria Utility installer to your server, select CCU.
Selecting either RME Mobile or CCU only copies that application’s installer to
your server. Selecting either of these options does not install the application.
To install either of these applications, select the application in the Choose
Components window to copy the installer to your server, and then follow the
applicable instructions in either the CareEnhance Review Manager Enterprise
Mobile Installation Guide or the CareEnhance Review Manager Custom
Criteria Utility Installation Guide.
If you previously installed the HL7 Interface or have not licensed the HL7
Interface, or chose a Microsoft Access installation, the Pre-Installation
Summary window appears. Continue with the procedure “Completing the
Upgrade” on page 25.
If you are licensed for the HL7 Interface and chose either a Microsoft SQL
Server or Oracle installation, the HL7 Application window appears.
If you are upgrading Review Manager in a clustered WebSphere environment

and choose to install the HL7 application, do not choose the option to start
the service automatically.
 If you do not want to install the HL7 application, select No, and
then click Next.
The Pre-Installation Summary window appears. Continue with the
procedure “Completing the Upgrade” on page 25.

3 Completing the Upgrade
 To install the HL7 application, select Yes, and then click Next.
The HL7 Service window appears.
a. Enter the port number used for the interface, such as 5001.
b. Enter the service name or leave the default (CERMEHL7).
c. Choose whether or not to have the HL7 service start automatically,
The Pre-Installation Summary window appears. Continue with the
procedure “Completing the Upgrade” on page 25.
Completing the Upgrade

The Pre-Installation Summary window confirms the installation options you
selected.
1. Check your selections on the Pre-Installation Summary window, and if they

are correct, click Install.
The amount of time for the install depends on how many criteria sets you
chose to install.
By default,Review Manager Enterprise and the Review Manager
Administration Module are installed to: C:\Program Files\McKesson\CERME
By default, the application server software is installed to:
 C:\Program Files\McKesson\CERME\Jetty
 C:\Program Files\McKesson\CERME\jre
2. When the installation is complete, click Done.
3. Click Close Window on the Installation window.
You have successfully upgraded Review Manager Enterprise.
For information about configuring end-user workstations to log on to
Review Manager Enterprise, refer to Chapter 8, “Logging on to
CareEnhance Review Manager.”
Importing Thomson Reuters® LOS Description Files

If you used Thomson Reuters® LOS data, then you must use the Review
Manager Administration Module to import the following Thomson Reuters®
LOS description files after upgrading to Review Manager 9.0:
 ICDCM.dat
 DRGT.dat
For instructions about how to import these LOS description files, refer to the
CareEnhance Review Manager Administrator’s Guide.

3 Migrating Organizational Policies
Migrating Organizational Policies

After upgrading to Review Manager Enterprise 9.0, you must migrate your
organizational policies using the organizational policy migration utility in the
System Administration module.
For information on using the organization policy migration utility, see the
CareEnhance Review Manager System Administrator’s Guide.

4
Manager Enterprise for Windows with
WebSphere
This chapter describes how to upgrade CareEnhance Review Manager

Enterprise for Microsoft Windows with WebSphere. You need to update the
Review Manager Enterprise database and install the updated application files
to each application server node.
Make sure that your system meets the system requirements for this release
of Review Manager Enterprise before installing the upgrade.
This chapter contains the following topics:

 Updating the Review Manager Database
 Upgrading the Review Manager Enterprise Application Files
 Default Directory Paths for Windows
 Default Server and Node Names
 Copying the Required Files
Updating the Review Manager Database

You will update the Review Manager Enterprise database using an interactive
SQL tool (such as SQL*Plus). For instructions about how to upgrade your
DBMS (if applicable), update the database, and migrate your Review Manager
organization policies, refer to Chapter 3, “Upgrading or Adding Products to
Review Manager Enterprise for Windows with Jetty.

4 Upgrading the Review Manager Enterprise Application Files
Upgrading the Review Manager Enterprise Application Files

To upgrade the Review Manager Enterprise application files and load the new
data into the database, follow the upgrade procedure in Chapter 3, “Upgrading
or Adding Products to Review Manager Enterprise for Windows with Jetty. If
you choose to install the HL7 application, do not choose the option to start the
service automatically.
Default Directory Paths for Windows

This book references directory paths during the installation and configuration
procedures. If your environment uses different path locations, refer to the
following list, and substitute your path for the default.
 Application Server Folder:
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
Alternatively, you can use any other location that WebSphere supports.
Use the same directory structure for each application server to simplify
sharing configuration files across the cluster.
 Deployment Manager Folder:

C:\Program Files\IBM\WebSphere\AppServer\profiles\DmgrProfile
 Review Manager Enterprise Installation Folder:
C:\Program Files\McKesson\CERME
This directory contains subfolders containing the Review Manager
Enterprise application and documentation files. You can choose any other
location that WebSphere can access.
Default Server and Node Names

This book references default names during the installation and configuration
procedures to describe the different computers and nodes contained in the
WebSphere cell that you will use for Review Manager Enterprise. If your
environment uses different computer or node names, substitute the default
names from the following lists with the names of your servers and nodes.
Computers:
 computer1—This computer hosts the WebSphere Network Deployment
Manager node, which contains the primary cluster controller and the server
administration software for the cluster. This server also hosts one
application server node.

4 Copying the Required Files
 computer2—This computer hosts another application server node.
You may use more than two computers in your cluster. Additional computers
(for example, computer3, computer4, and so on) should each host only one
WebSphere Application Server node. Should you use additional computers,
repeat any instructions provided in this book for computer2 for each
additional computer.
Nodes:
 node1—This is the node on computer1 that contains both the WebSphere
Network Deployment Manager and the first WebSphere Application Server.
 node2—This is the node on computer2 that contains the second WebSphere
Application Server.
Copying the Required Files

After upgrading Review Manager Enterprise, you must copy the updated
application files to each of the application server nodes in the cluster.
Overwrite the old versions of the files on the application servers with the
newer versions as necessary.
Documentation files and War files

If during the initial installation of Review Manager, you accept the default
installation location of C:\Program Files on computer1, the installer creates the
location path of C:\Program Files\McKesson\CERME and creates folders for the
documentation files and war files. The WebSphere Deployment Manager,
located on computer 1then installs the war files into the cluster. This
installation process will propagate the war files to all nodes in the cluster.
Therefore, you do not need to copy the war files to additional locations.
War files
 b2sw.war
 help.war
 help2005.war
 help2006.war
 help2007.war
 help2008.war
 help2009.war
 rm.war
You can optionally copy the documentation files to additional nodes in the
cluster. The documentation files include: DataDictionary.pdf, HL7.zip,
RMInstallationGuide.pdf, and the SystemAdministratorsGuide.pdf.

To copy the oscache.properties file and the log4j.xml file:

1. On computer 1 where you initially installed Review Manager Enterprise,
copy the oscache.properties file from
C:\Program Files\McKesson\CERME\jarfiles into the
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties
directory.
copy the log4j.xml file from
3. Repeat steps 1 and 2 on each additional computer in the cluster.
Editing the oscache.properties File

The oscache.properties file contains configuration options for caching and
clustering. Edit this file to suit your network environment.
To edit the oscache.properties file:

1. On computer1, from the
directory, open the oscache.properties file in any text editor.
2. Set the cache size by editing the cache.capacity value.
3. Review Manager Enterprise uses JGroups 2.0 for the cache invalidate
messaging system with UDP as the default JGroups communication
protocol. However, you can use a different communication protocol. If you
want to use a different communication protocol, change the
cache.cluster.properties value. For example, you could use the following
value for the TCP/IP communication protocol:
cache.cluster.properties=TCP(start_port=7800):TCPPING(initial_h
osts=intersun[7800];port_range=5;timeout=3000;num_initial_membe
rs=2;up_thread=true;down_thread=true):MERGE2(min_interval=5000;
max_interval=10000):FD_SOCK:VERIFY_SUSPECT(timeout=1500):pbcast
.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800):pb
cast.STABLE(desired_avg_gossip=20000):UNICAST(timeout=5000):FRA
G(frag_size=8096;down_thread=false;up_thread=false):pbcast.GMS(
join_timeout=5000;join_retry_timeout=2000;shun=false;print_loca
l_addr=true)
For more information on JGroups 2.0 configuration parameters, visit
http://www.jgroups.org/javagroupsnew/docs/ug.html.
4. If you are using the UDP protocol and you intend to run more than one
OSCache cluster on the same local area network (LAN), then make sure to
specify a different multicast IP address for each cluster (the value is
contained in the cache.cluster.multicast.ip parameter). Make sure the
parameter is uncommented.
5. Save the modified oscache.properties file.
6. For each additional computer (for example, computer2), copy the
oscache.properties file from the
directory on computer1 to the corresponding directory on each additional
computer.

Editing the ReviewManager.xml File

The ReviewManager.xml file contains database configuration settings. Edit this
file to enable clustering mode and to make changes to your database
connection.
To enable clustering and verify or change your database connection settings:

1. On the Windows-based computer where you initially installed Review
Manager Enterprise, from the C:\Program Files\McKesson\CERME directory,
open the ReviewManager.xml file in any text editor.
2. Add the following child element to the <Config> element:<Mode
Cluster="true"/>
For example:
<Config CacheSize="100" numSQLRetry="5" SQLRetryInterval="5000">
<Mode Cluster="true" MainNode="true"/>
...
</Config>
The mainnode attribute is present only on the main node.
3. Review all of the options in the ReviewManager.xml file, and make any
necessary changes.
4. Save the modified ReviewManager.xml file.
5. Copy ReviewManager.xml from the C:\Program Files\McKesson\CERME
directory to the
directory of each application server node (for example, node1).
6. You can customize the performance of each server by editing certain values
in the ReviewManager.xml file. For example, you may want to modify a
specific application server’s copy of ReviewManager.xml to correspond with
that server’s cluster loading configuration.
Servers that receive a higher load should have a higher database
connection limit. However, make sure not to exceed the database network
connection limit when you add the maximum network connections for all
nodes combined.
If you make any changes to the database connection information in

ReviewManager.xml on one server, make sure you make the same changes to
the copy of the file on each of the other servers. Modifying this information in
only one copy of the file could cause the application servers to reference
different Review Manager Enterprise databases.
Upgrading the Outbound HL7 Service and the Inbound HL7

Service
For directions on how to upgrade the outbound HL7 service and the inbound
HL7 servce, refer to “Upgrading the Outbound HL7 Service” on page 84 and
“Upgrading the Inbound HL7 Service” on page 84.

5
Upgrading Review Manager Enterprise for
Linux with WebSphere
This chapter describes how to upgrade CareEnhance Review Manager

Enterprise for Linux. You need to update the Review Manager Enterprise
database and install the updated application files to each application server
node.
Make sure that your system meets the system requirements for this release
of Review Manager Enterprise before installing the upgrade.

 Updating the Review Manager Database
 Upgrading the Review Manager Enterprise Application Files
 Default Directory Paths for Linux
 Copying the Required Files
Updating the Review Manager Database

You will update the Review Manager Enterprise database using an interactive
SQL tool (such as SQL*Plus). For instructions about how to upgrade your
DBMS (if applicable), update the database, and migrate your Review Manager
organization policies, refer to Chapter 3, “Upgrading or Adding Products to
Review Manager Enterprise for Windows with Jetty.

5 Upgrading the Review Manager Enterprise Application Files
Upgrading the Review Manager Enterprise Application Files

To upgrade the application files and load new data into the database, you must
run the Windows installer for Review Manager Enterprise. You must perform
the procedure described in this section on a Windows-based
computer.
To upgrade Review Manager Enterprise on a Windows-based computer, follow

the upgrade procedure in Chapter 3, “Upgrading or Adding Products to Review
Manager Enterprise for Windows with Jetty. If you choose to install the HL7
application, do not choose the option to start the service automatically.
Default Directory Paths for Linux

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01

/opt/IBM/WebSphere/AppServer/profiles/DmgrProile
/opt/McKesson/CERME


Computers:
Nodes:
Application Server.
Copying the Required Files

After upgrading Review Manager Enterprise on your Windows-based computer,
you must copy the updated application files to each of the Linux application
server nodes in the cluster.
To copy the updated files:
Overwrite the old versions of the files on the application servers with the
newer versions from the Windows-based computer as necessary.
1. On the Windows-based computer where you upgraded Review Manager

Enterprise, copy the following files from
C:\Program Files\McKesson\CERME\Doc to computer1 into the
/opt/McKesson/CERME/Doc directory:
 DataDictionary.pdf
 HL7.zip
 RMInstallationGuide.pdf
 SystemAdministratorsGuide.pdf
Enterprise, copy the oscache.properties file from
C:\Program Files\McKesson\CERME\jarfiles to computer1 into the
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/properties directory.
C:\Program Files\McKesson\CERME\warfiles to computer1 into the
/opt/McKesson/CERME/warfiles directory:

 b2sw.war
 help.war
 help2005.war
 help2006.war
 help2007.war
 help2008.war
 help2009.war
 rm.war
4. Repeat steps 1 through 3 on each additional computer in the cluster (for
example, computer2).


1. On computer1, from the /opt/IBM/WebSphere/AppServer/profiles/
AppSrv01/properties directory, open the oscache.properties file in any text
editor.
l_addr=true)
oscache.properties file from the /opt/IBM/WebSphere/AppServer/profiles/
AppSrv01/properties directory on computer1 to the corresponding directory
on each additional computer.


connection.

2. Add the following child element to the <Config> element:
<Mode Cluster="true"/>
For example:
...
</Config>
necessary changes.
directory on the Windows-based computer to the /opt/IBM/WebSphere/
AppServer/profiles/AppSrv01/properties directory of each application
server node (for example, node1).
nodes combined.

the copy of the file on each of the other server. Modifying this information in

Upgrading the Outbound HL7 Service and the Inbound HL7

Service
For directions on how to upgrade the outbound HL7 service and the inbound
HL7 servce, refer to “Upgrading the Outbound HL7 Service” on page 77 and
“Upgrading the Inbound HL7 Service” on page 78.

6
Creating a WebSphere Cluster
The remainder of this book assumes that you are working in a clustered
WebSphere environment. If you do not create a cluster, in the procedures
that start in Chapter 7, “Installing Review Manager Enterprise,” ignore the
steps that instruct you to repeat tasks on additional application servers.
If you do not want to run CareEnhance Review Manager Enterprise in a
clustered environment, you can skip this chapter and proceed with Chapter 7.
This chapter applies to both Microsoft Windows and Linux installs. It describes
the tasks that you need to perform to set up a clustered WebSphere
environment. Clustering is available only for WebSphere. You can install
Review Manager Enterprise in a clustered environment to improve
performance. A cell is a collection of application servers that work together to
process application tasks. Each application server is in a node that resides on a
separate computer in the cluster. The WebSphere Network Deployment
Manager node is installed on only one computer, which manages each of the
WebSphere Application Server nodes in the cluster.
Sample WebSphere Cell
nodeDM1
Deployment
Manager
nodeAP1 nodeAP2
Application Application
Server Server
computer1 computer2
The procedures in this chapter require you to have the WebSphere Network
Deployment Manager installed only on computer1 and a WebSphere
Application Server installed on each server in your cluster (including
computer1). The procedures in this book assume that you have both the
Deployment Manager node and an application server node installed on
computer1.

 Default Directory Paths for Windows and Linux

6 Default Directory Paths for Windows and Linux
 Creating the WebSphere Cluster

 Configuring the Application Servers for Linux
 Starting the Node Agents
Default Directory Paths for Windows and Linux

 Microsoft Windows:
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
 Linux: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01

 Microsoft Windows:
C:\Program Files\IBM\WebSphere\AppServer\profiles\DmgrProfile
 Linux: /opt/IBM/WebSphere/AppServer/profiles/DmgrProile
 Microsoft Windows:C:\Program Files\McKesson\CERME
 Linux: /opt/McKesson/CERME

Computers:

6 Creating the WebSphere Cluster
Nodes:
Application Server.
Creating the WebSphere Cluster

To create the cluster, you create application server nodes, and then assemble
the cluster using these nodes.
Creating the WebSphere Application Server Nodes

To create application server nodes and federate them into the Deployment
Manger:
1. On computer1, start the Deployment Manager.
A. Depending on your Operating System, do one of the following:
 Microsoft Windows—In a Windows command line window, type the
following, and then press Enter:
C:\Program Files\IBM\WebSphere\AppServer\profiles\DmgrProfile\bin
 Linux—In the Red Hat terminal, type the following, and then press
Enter:
cd /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/bin
B. Depending on your Operating System, do one of the following:
 Microsoft Windows—Type the following, and then press Enter:
startManager.bat
 Linux—Type the following, and then press Enter:
./startManager.sh
2. Add the first WebSphere Application Server node (the one that is also on
computer1) to the Deployment Manager.
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
Enter:
cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin


 Microsoft Windows—Type the following (specifying the server
name and port), and then press Enter: addNode.bat
<deploymentManagerHostName> <port>
where deploymentManagerHostName is the name of the computer
that hosts the Deployment Manager and port is the port number of
this machine (typically 8879).
The node is now federated into the Deployment Manager.
 Linux—Type the following (specifying the server name and port), and
then press Enter: ./addNode.sh <deploymentManagerHostName>
<port>
where deploymentManagerHostName is the name of the computer
that hosts the Deployment Manager and port is the port number of
this machine (typically 8879).
The node is now federated into the Deployment Manager.
3. Repeat Step 2 for each subsequent application server node that you wish to
add to the cluster. You need at least two application server nodes to create
a clustered WebSphere environment. Make sure to change the node name
for each additional node (for example, to node2) when running the
addNode.sh shell script.

Creating a New Cluster

1. Log on to the WebSphere Administrative Console:
A. Open your Web browser, and navigate to the following URL:
http://localhost:9060/admin/
This book uses port 9060 for the administration module. In the URL,
replace this number with your administration module port number.
B. Log on to the Deployment Manager.
2. From the navigation panel, expand Servers, expand Clusters, and then click
WebSphere Application Server Clusters.
The Server Cluster window appears.
3. Create a new cluster by clicking New.

The Create a new cluster window appears displaying the Enter basic cluster
information step.
4. In the Cluster name text box, type the name of the cluster. You can use any
name that conforms to your organization’s naming standards.
5. Select the option to Prefer local.

6. Clear the option to Configure HTTP session memory-to-memory replication,

The Create first cluster member step appears.
7. Add the first cluster member:

A. In the Member name text box, type a name for the first cluster member.
You can use any name that conforms to your organization’s naming
standards.
B. From the Select node drop-down list, select node1.
C. Set the server weight.
D. Clear the option to Generate unique HTTP ports.
E. Select the option to the “Create the member using an existing
application server as a template.” From the drop-down list, select the
first application server (the one hosted on nodeAPI).

F. Click Next.
The Create additional cluster members step appears.
8. Add an additional cluster member(s):

A. In the Member name text box, type a name for the second cluster
member. You can use any name that conforms to your organization’s
naming standards.
B. From the Select node drop-down list, select node2.
C. Set the server weight.
D. Clear the option to Generate unique HTTP ports.
E. Click Add Member.
If you want to add additional cluster members, repeat steps A through E
for each member, making sure to select the appropriate node for each
member.

F. Click Next.
The Summary step appears.

9. Confirm that the summary information is correct, and then click Finish.
The Server Clusters window appears.
10.In the Message box, click Save.

WebSphere creates a new cluster comprised of application servers on node
node1 and node2 and updates the local configuration.

6 Configuring the Application Servers for Linux
Configuring the Application Servers for Linux

You configure the application servers only if you are creating a cluster for
Linux. If you are creating a cluster for Windows, continue with “Starting the
Node Agents” on page 50.
Before deploying the Review Manager applications, you must configure each
application server.
To configure each application server:

1. Log on to the Deployment Manager.
2. From the navigation panel, expand Servers, expand Server Types, and then
click WebSphere Application Servers.
The Application Servers window appears.
3. Remove any application servers that are not part of the cluster by selecting
each application server that is not part of the cluster, and then click Delete.
4. For each server in the cluster, configure the OSCache:

A. Click the name of the first server.

The server management window appears.
B. Under the Server Infrastructure heading, expand Java and Process

Management, and then click Process Definition.
The Process Definition window appears.
C. Under the Additional Properties heading, click Java Virtual Machine.

The Java Virtual Machine window appears.

D. In the Generic JVM arguments text field, type the following:

-Djava.net.preferIPv4Stack=true
E. Click Apply to save the changes.
F. Repeat steps A through E for each additional application server in the
cluster.

6 Starting the Node Agents
Starting the Node Agents

After creating the cluster, you must start the node agent for each application
server node.
To start a node agent:

1. On computer1, start the node agent.
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin
Enter:
cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
 Microsoft Windows—Type the following and then press Enter:
startNode.bat
node1 starts.
 Linux—Type the following, and then press Enter: ./startNode.sh
node1 starts.
2. Repeat step 1 for each additional node (for example, node2).

7
Installing Review Manager Enterprise
This chapter describes all the tasks that you need to perform to install
CareEnhance Review Manager Enterprise. Review Manager Enterprise is a Web
browser-based application that requires Web server software. McKesson
includes the Jetty Web Server (for Windows) with the Review Manager
Enterprise installer. You can install Review Manager Enterprise in a clustered
environment using the IBM® WebSphere Application Server.
As part of the installation procedure, you will set up a database to use with
Review Manager Enterprise. The database does not need to be on the same
server as Review Manager Enterprise.
Before You Begin

Before installing Review Manager Enterprise, do the following:
 Review the hardware and software requirements in Chapter 1, “Supported
Technical Configurations.”
 Ensure that the Windows user installing Review Manager Enterprise has
 Decide whether you want to install the application from the installation DVD
or copy the downloaded application files to the network.
If you decide to install across the network, before beginning the
installation, copy the entire contents of the Review Manager installation
DVD to a network drive. Each workstation where you will install Review
Manager Enterprise must have read access to this drive.
installation. Your McKesson representative will provide you with this
information.
 Obtain a username and password to log on to Review Manager Enterprise.
Your McKesson representative will provide you with a default username and
password.
 Determine where you want to install Review Manager Enterprise.
 For WebSphere installations, make sure that you have installed and
configured the following:

7 Creating the Database
 IBM® WebSphere® 7.0 (used for both the application servers and the
Deployment Manager).
 The IBM WebSphere Network Deployment Manager installed on node1
on computer1.
 An IBM WebSphere Application Server installed on the node on each
computer in the cluster (for example, node1 on computer1, node2 on
computer2, and so on).
 A Java SDK. For WebSphere-based installations, McKesson supports any
WebSphere-supported Java SDK that is compatible with version
1.6.0_16 of the Sun Java SDK.
McKesson recommends installing Review Manager Enterprise 9.0 in a test

environment before installing it in your production environment.
Creating the Database

Before installing the Review Manager Enterprise software, you must first
create and configure the Review Manager database.
Review Manager Enterprise supports only the characters contained in the

WE8MSWIN1252 database character set.
Creating a Microsoft Access Database

If you are installing the Access version of Review Manager Enterprise, then the
Review Manager installer automatically creates the Access database during the
installation process.
Creating a Microsoft SQL Server Database

Review Manager Enterprise does not support connectivity to Microsoft SQL
Server in Windows NT Authentication mode; you must use SQL Server
authentication.
To install the Microsoft SQL Server version of Review Manager Enterprise, you
must use a SQL Server login that has database owner privileges on the Review
Manager database. Day-to-day operations of Review Manager Enterprise
require the specific server login with SELECT, UPDATE, INSERT, and DELETE
rights to the Review Manager tables.
Before installing the Microsoft SQL Server version of Review Manager

Enterprise, your database administrator must create the database by doing
the following:
1. Edit the mss_crt_db.sql script (located on the Review Manager installation
DVD in the Scripts folder) to customize the database file names and sizes.
You may also change the user or name of the database created by the

7 Creating the Database
script. If you change the user or name of the database, record these
modifications because you will need to specify these changes later in the
This username and password is used both to install Review Manager

Enterprise and to upgrade to future versions of Review Manager
Enterprise.
The username and password will be encrypted and placed in an XML file that
is used by the software. McKesson recommends that you do not use a login
with sysadmin privileges.
2. Create the database:

A. Log into Query Analyzer as the system administrator (sa or another
login with sysadmin privileges).
B. Run the edited mss_crt_db.sql script.
During the Review Manager installation process, you will reference the
new database name and the server where the database resides.
3. Create the tables:
A. Log into Query Analyzer as the new user created by the mss_crt_db.sql
script.
B. Run the mss_create.sql script on the newly created database. This script
is located on the Review Manager installation DVD in the Scripts folder.
Creating an Oracle Database

Before installing the Oracle version of Review Manager Enterprise, your
database administrator must perform these tasks:
1. Edit the oracle_crt_db.sql script (located on the Review Manager
installation DVD in the Scripts folder) to reflect your installation. Replace
<PATH> with the full path of the folder where you want to put the Oracle
data files. For example, D:\oracle\oradata\CERME\ . Be sure to include the
final slash in order to construct a valid file name. You may also change the
user created by the script. If you change the user, record this modification
because you will need to specify this change later in the installation
process..
This username and password will be used when you install Review Manager
Enterprise. The username and password will be encrypted and placed in an
XML file that is used by the software.
2. The oracle_crt_db.sql script creates three default tablespaces. Do not

change the names of these tablespaces, or the installation will fail.

7 Starting the Installation Process

A. Log into your interactive SQL tool (such as SQL*Plus) as the system
user, or another user with DBA privileges.
B. Run the oracle_crt_db.sql script. This script creates the tablespaces and
the user who will own the Review Manager tables and grants the
necessary database privileges.
A. Log into your interactive SQL tool (such as SQL*Plus) as the new user
that you specified in the oracle_crt_db.sql script (cerme by default).
B. Run the oracle_create.sql script.
5. In order to run Review Manager successfully, the cerme user must have
execute privileges on the DBMS_LOB package. DBMS_LOB is provided by
Oracle Corporation and, by default, all database users may execute it.
Some database administrators restrict access to DBMS_LOB. If your site
does not grant public access to DBMS_LOB, edit and run the command in
the oracle_grant_lob.sql script to grant execute privileges to the cerme
user only.
Starting the Installation Process

Review Manager Enterprise (using Jetty, which is the included application
server) is configured by default to use port number 80. If port 80 is already
being used at your site (for example, for Internet Information Services (IIS))
you will need to change the port to an unused port number, such as 7007.
Install the Review Manager Enterprise application on your network server

(not on a client workstation).
Review Manager Installation Guide, InterQual View Installation Guide, and
System Administrator’s Guide.
installation.

7 Starting the Installation Process

9. Enter the values exactly as provided by McKesson (including any hyphens),
application.
The Licensed Products Window appears. The Licensed Product window shows
the product(s), database(s), and criteria sets for which your organization is
licensed.
licensed.

The Select Review Manager Application window appears. If you are licensed
for Review Manager Enterprise, Review Manager, and InterQual View, then
the installer will prompt you to choose which product to install.
To install InterQual® View, follow the instructions in the InterQual View

Installation Guide.
11.Click Next.
The Review Manager Enterprise Installation Type window appears.
12.Select New installation, and then click Next.
The Choose Components window appears.


The Choose Components window displays a list of all the licensed products.
1. Select which products to install, and then click Next:
 Select the criteria sets that you want to install. You can install all of the
criteria sets for which you are licensed or you can customize your
installation to include only certain criteria sets.
 To copy the Enterprise Mobile installer to your server, select RME Mobile.
 To copy the Custom Criteria Utility installer to your server, select CCU.
Selecting either RME Mobile or CCU only copies that application’s installer to
your server. Selecting either of these options does not install the application.
To install either of these applications, select the application in the Choose
Components window to copy the installer to your server, and then follow the
applicable instructions in either the CareEnhance Review Manager Enterprise
Mobile Installation Guide or the CareEnhance Review Manager Custom
Criteria Utility Installation Guide.
The Choose Install Folder window appears.

2. Specify the path where you want to install Review Manager or keep the
default location, which is C:\Program Files.
If you are installing Review Manager in a clustered WebSphere environment,

accept the default location of C:\Program Files on computer 1. This will install
Review Manager into the C:\Program Files\Mckesson\CERME directory.
The desktop shortcuts check box enables you to create shortcuts on your
Windows desktop to the Review Manager appplication. Whether or not you
choose to create shortcuts on your desktop, you can access the Review
Manager application from Start > Programs > Review Manager.
3. Choose whether or not to create desktop shortcuts, and then click Next:
 If you want to create shortcuts, leave the check box selected.
 If you do not want to create shortcuts, clear the checkbox.
The Review Manager Enterprise Database Information window appears.
4. From the Database Type drop-down menu, select the type of database that
you will use for the Review Manager database. When you select a database,
the installer prompts you to enter database-specific connection
information:
 For a Microsoft Access database, choose the folder where you want to
install the Access database, and then click Next.
 For a Microsoft SQL Server database, specify the following
information, and then click Next.
 Server Name—the server where the database resides.
 Database Name—the name of the SQL database.
 Port Number—the database listener port address. Default is 1433.
 Instance—the system identifier used for this installation. If you are
not installing to an instance, then leave this field blank.

 Enter the user ID and password of the SQL user who ran the
mss_create.sql script used when the database was created. The user
ID and password are used to connect to the database.
 For an Oracle database, specify the following information, and then
click Next:
 Port Number—the database listener port address, usually 1521.
 Instance (SID)—the system identifier used for this installation.
 Schema name—the database user who owns the Review Manager
tables. This name must be in uppercase.
 Enter the User ID and password for the schema. The user ID and
password are used to connect to the database.
The Review Manager Enterprise Reporting Database window appears.
5. Select whether or not to store report data in a separate database.
Review Manager Enterprise allows you to store report information in either
the Review Manager database or a separate database that is a copy of your
Review Manager database. Choosing to store report data in a separate
database that is on a different server from the Review Manager database
might help to improve system performance.
 If you want to store report data in the Review Manager
database:
Select No, and then click Next.
 If you want to store report data in a separate database:
If you choose to use a separate database for report data, prior to the
following procedure, your database administrator must create this database
from a copy of your production Review Manager database (the one you
created in the section, “Creating the Database” on page 52). To keep this
data current, refresh the data in the reporting database often. Your database
administrator will be responsible for keeping your reporting database up to
date.
a. Select Yes, and then click Next.

The Review Manager Enterprise Reporting Database Information
window appears.
b. From the Database Type drop-down menu, select the type of
database to use.
c. Specify the database connection information as you did in Step 4,
If you are not licensed for the HL7 Interface or chose a Microsoft
Access installation, the Jetty Application Server window appears. Continue
with the procedure “Customizing the Server Software” on page 58.
If you are licensed for the HL7 Interface and chose either a Microsoft
SQL Server or Oracle installation, the HL7 Application window appears.
6. Choose whether to install the HL7 application:
If you are installing Review Manager in a clustered WebSphere environment

and choose to install the HL7 application, do not choose the option to start
the service automatically.

7 Customizing the Server Software
 If you do not want to install the HL7 application, select No, and
then click Next.
The Jetty Application Server window appears. Continue with the
procedure “Customizing the Server Software” on page 58.
 To install the HL7 application, select Yes, and then click Next.
The HL7 Service window appears.
a. Enter the port number used for the interface or leave the default
8077.
b. Enter the service name or leave the default (CERMEHL7).
c. Choose whether or not to have the HL7 service start automatically,
The Jetty Application Server window appears.
d. Continue with “Customizing the Server Software” on page 58.
Customizing the Server Software

If you are installing Review Manager in a clustered WebSphere environment,
do not install Jetty. Do install an alternate application server.
The Jetty Application Server window enables you to configure Review Manager
Enterprise to use Jetty as its application server.
1. Choose whether to install the Jetty Application Server:
If you are not installing Review Manager Enterprise for WebSphere, you must
install Jetty.
 If you want to install Jetty

a. Select Yes, and then click Next.
The Review Manager Enterprise Connection Information window
appears.
b. Continue with the procedure in Step 2 to enter connection
information.
 If you want to install another application server
a. Select No, and then click Next.
The Alternate Application Server Configuration Files window appears.
b. Specify the path where you want to install the resource and property
files, or keep the default location, which is C:\Program Files.
If you are installing Review Manager Enterprise in a clustered WebSphere

environment, accept the default location of C:\Program Files on computer 1.
The installer then creates the location path of C:\Program
Files\McKesson\CERME and creates folders for the doc files and war files.
c. Click Next.

7 Completing the Installation
 If you chose to store reporting data in a separate database (in

Step 5 on page 57), the Get Report Connection Information window
appears. Continue with Step 3.
 If you chose to store reporting data in the Review Manager
database (in Step 5 on page 57), the Pre-Installation Summary window
appears. Continue with the procedure “Completing the Installation” on
page 59.
2. Leave the default values or customize the connection information for
Review Manager Enterprise, and then click Next.
Make sure that you use a valid port number that is not already in use on the
server where you install Review Manager Enterprise. Also, use a valid service
name that is not already in use. You can check the service name by going to
Control Panel >Administrative Tools >Services.
 If you chose to store reporting data in the Review Manager

database (in Step 5 on page 57), the Pre-Installation Summary window
appears. Continue with the procedure “Completing the Installation” on
page 59.
 If you chose to store reporting data in a separate database (in
Step 5 on page 57), the Get Report Connection Information window
appears. Continue with Step 3.
3. In the Get Report Connection Information window, enter the reporting
database connection name, and then click Next. The Pre-Installation
Summary window appears.
4. Continue with the procedure “Completing the Installation” on page 59.
Completing the Installation

selected.
chose to install.
By default, Review Manager Enterprise and the Review Manager
Administration Module are installed to: C:\Program Files\McKesson\CERME
 C:\Program Files\McKesson\CERME\Jetty
 C:\Program Files\McKesson\CERME\Jre
You have successfully installed Review Manager Enterprise.
For information about:
 Configuring end-user workstations to log on to Review Manager
Enterprise, refer to Chapter 8, “Logging on to CareEnhance Review
Manager.”

7 Installing Multiple Instances of Review Manager Enterprise
 Copying the required application files to each of the WebSphere

Application Server nodes in the WebSphere cluster, refer to “Copying
Review Manager Enterprise Application Files to Additional WebSphere
Nodes” on page 60.
Installing Multiple Instances of Review Manager Enterprise

In some cases, you may want to install more than one instance of Review
Manager Enterprise. For example, you may want to install one instance in a
test environment and one in a production environment.
To install multiple instances of Review Manager Enterprise:

1. Create another Review Manager database by following the instructions in
“Creating the Database” on page 52.
2. Run the installation again.
3. When you are presented with the Choose Install Folder window, specify a
location that is different from one you used for a previous installation.
For example, if you installed your first version of Review Manager
Enterprise in C:\Program Files\McKesson, then you can install your second
version in any other directory (such as
C:\Program Files\Review Manager Second Installation).
4. When you are presented with the Get Connection Name and Port Number
window, enter values different from the initial install.
For example, if you are setting up a test environment you could enter:
 Port number: 7077
 Service name: CERMETest
5. To access Review Manager Enterprise, include in the URL the port number
that you specified in Step 4.
For example, http://machinename:portnumber/rm/login.
If you are installing Review Manager Enterprise for Windows with Jetty, refer
to Chapter 8, “Logging on to CareEnhance Review Manager.
Copying Review Manager Enterprise Application Files to

Additional WebSphere Nodes
The instructions in this topic apply only to Review Manager Enterprise for
Windows with WebSphere installs.
After creating and populating the database, you must copy the required
application files to each of the WebSphere Application Server nodes in the
WebSphere cluster.

7 Copying Review Manager Enterprise Application Files to Additional WebSphere Nodes
Documentation files and War files

If during the installation of Review Manager, you accept the default installation
location of C:\Program Files on computer1, the installer creates the location
path of C:\Program Files\McKesson\CERME and creates folders for the
documentation files and war files. The WebSphere Deployment Manager,
located on computer 1 then installs the war files into the cluster. This
installation process will propagate the war files to all nodes in the cluster.
Therefore, you do not need to copy the war files to additional locations.
War files
 b2sw.war
 help.war
 help2005.war
 help2006.war
 help2007.war
 help2008.war
 help2009.war
 rm.war
You can optionally copy the documentation files to additional nodes in the
cluster. The documentation files include: DataDictionary.pdf, HL7.zip,
RMInstallationGuide.pdf, and the SystemAdministratorsGuide.pdf.
To copy the oscache.properties file and the log4j.xml file:

copy the oscache.properties file from
directory.
copy the log4j.xml file from
directory.
3. Repeat steps 1 and 2 on each additional computer in the cluster.


1. On computer1, from the
directory, open the oscache.properties file in any text editor.

l_addr=true)
oscache.properties file from the
directory on computer1 to the corresponding directory on each additional
computer.

connection.

For example:
...
</Config>

necessary changes.
directory to the
directory of each application server node (for example, node1).
nodes combined.

Assigning Review Transfer Communication Handlers to

Application Servers in the Cluster
To use Review Manager Enterprise in a clustered environment, you must select
application servers in the cluster to be review transfer communication
handlers. Each handler must be hosted on a single server. One server can host
multiple different handlers.
Keep in mind that a server hosting a handler will have additional workload, so
consider performance when making your selection and try to distribute
handlers evenly between servers.
Depending on the Review Manager Enterprise configuration, up to three

handlers can be assigned:
 ReviewAuthHandler
 ReviewExportHandler
 NotificationHandler
Example
The following example describes how to assign the ReviewAuthHandler to an
application server in the cluster.
1. On the computer running the application server that you want to be the
ReviewAuthHandler, from the C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties directory,

2. Add the line ReviewAuthHandler="true" attribute to the <Mode> element.

For example:
<Config CacheSize="100" numSQLRetry="5"
SQLRetryInterval="5000">
<Mode Cluster="true" ReviewAuthHandler ="true"/>
...
</Config>
3. For all other application servers in the cluster, do either of the following:
 Do not add the line ReviewAuthHandler attribute to the <Mode>
element of the ReviewManager.xml file.
 Add the line ReviewAuthHandler attribute to the <Mode> element of the
ReviewManager.xml file, but set the value to false.
For example:
<Config CacheSize="100" numSQLRetry="5"
SQLRetryInterval="5000">
<Mode Cluster="true" ReviewAuthHandler ="false"/>
...
</Config>
The complete example for a two node cluster:

Server 1:
<Mode Cluster="true" ReviewAuthHandler ="true"/>
Server 2:
<Mode Cluster="true" ReviewExportHandler ="true"
NotificationHandler="true"/>

8
Logging on to CareEnhance Review Manager
This chapter describes how to configure each end-user workstation to connect

to CareEnhance Review Manager Enterprise or CareEnhance Review Manager.
Before Logging on to CareEnhance Review Manager for the

First Time
Before logging on to CareEnhance Review Manager for the first time, make
sure to configure the following on each end-user workstation.
Configuring Internet Explorer

Before logging on to CareEnhance Review Manager for the first time, configure
the following in Internet Explorer.
Enable Active Scripting

To use CareEnhance Review Manager, you must enable Active Scripting in
Internet Explorer.
Delete the Internet Explorer Temporary Internet Files

Make sure to delete all Internet Explorer temporary Internet files to ensure
that CareEnhance Review Manager operates correctly.
Configure the Internet Explorer Pop-up Blocker

Before logging on to CareEnhance Review Manager, you must configure the
Internet Explorer pop-up blocker settings to allow pop-ups from the
CareEnhance Review Manager server. For example:
 If the URL you use to access CareEnhance Review Manager is
http://rmserver/rm/login, then allow Internet Explorer to display pop-ups
from rmserver.

8 Starting CareEnhance Review Manager
 If the URL you use to access CareEnhance Review Manager is

http://18.28.94.12/rm/login, then allow Internet Explorer to display pop-
ups from 18.28.94.12.
Hide the Internet Explorer Status Bar

Connecting to CareEnhance Review Manager via an IP address (such as
http://10.96.86.115:6006/rm/login) using Internet Explorer causes the
Internet Explorer status bar to appear at the bottom of each CareEnhance
Review Manager window. To prevent the status bar from appearing, do either
of the following:
 Connect to CareEnhance Review Manager via a host name (such as
http://servername:6006/rm/login).
 Add the IP address of your CareEnhance Review Manager server to your
Internet Explorer Trusted Sites list.
For example, if the URL you use to access CareEnhance Review Manager is
http://18.28.94.12/rm/login, then add 18.28.94.12 to your Trusted Sites
list.
Configuring PDF Viewing Options

CareEnhance Review Manager displays PDFs, such as a Clinical Evidence
Summary (CES), using Adobe Reader. To properly configure your system to
correctly display PDFs in CareEnhance Review Manager:
1. In Internet Explorer, click Tools > Internet Options > Advanced tab.
2. In the section labeled Browsing, clear the option to “Reuse windows for
launching shortcuts,” and then click OK.
3. In Adobe Reader, click Edit > Preferences > Internet.
4. Select the option to “Display PDF in browser,” and then click OK.
Starting CareEnhance Review Manager

To ensure that CareEnhance Review Manager starts correctly, do the following:
 If you are using the Microsoft SQL Server version or the Oracle version of
CareEnhance Review Manager Enterprise, you must start the database
before you start CareEnhance Review Manager Enterprise
 If you are using CareEnhance Review Manager with Microsoft SQL server or
Oracle as your DBMS, you must start the database before you start

8 Logging on to CareEnhance Review Manager
Logging on to CareEnhance Review Manager

To log on to CareEnhance Review Manager:
1. From the Windows Start Menu, click Programs > CareEnhance Review
Manager/Enterprise > CareEnhance Review Manager (or CareEnhance
Review Manager Admin for the Administration Module).
Alternatively, you can open Internet Explorer and type the URL in the
address bar:
 For CareEnhance Review Manager Enterprise or CareEnhance Review
Manager:
 If your application server uses port 80 (the default), type
http://machinename/rm/login
(where machinename is the name or IP address of your server).
 If your application server uses a port other than 80, type
http://machinename:portnumber/rm/login
(where machinename is the name or IP address of your server and
portnumber is the port number).
 For the System Administration Module:
 If your application server uses port 80 (the default), type
http://machinename/rm/admin
(where machinename is the name or IP address of your server).
 If your application server uses a port other than 80, type
http://machinename:portnumber/rm/admin
(where machinename is the name or IP address of your server and
portnumber is the port number).
The Login window appears.
2. Read the McKesson proprietary text.
3. Type the default username and password you were given by McKesson, and
then click Login.
The first time you log on to CareEnhance Review Manager Enterprise, you
must accept the security warning to enable printing. A Microsoft ActiveX®
printer plug-in will be added to Internet Explorer.

9
Installing Review Manager Enterprise for
Linux
CareEnhance Review Manager Enterprise is a Web browser-based application

that requires Web server software. You can install Review Manager Enterprise
in a clustered environment using the IBM® WebSphere Application Server.
As part of the installation procedure, you will Install Review Manager

Enterprise first on a Microsoft Windows-based computer to initially populate
the Review Manager database.
After you create your WebSphere cluster, you need to create and populate the
Review Manager Enterprise database and install the application files to each

 Prerequisites for Installation
 Creating the Review Manager Enterprise Database
 Populating the Review Manager Enterprise Database
 Copying Required Files for Linux with WebSphere
 "Installing Verdana Font
Prerequisites for Installation

Before installing Review Manager Enterprise for Linux, make sure that you
have installed and configured the following:
 Red Hat Enterprise Linux Version 4.0 Updater 6.
 IBM® WebSphere® 7.0 (used for both the application servers and the
Deployment Manager).
 The IBM WebSphere Network Deployment Manager installed on node1 on
computer1.
 An IBM WebSphere Application Server installed on the node on each
computer in the cluster (for example, node1 on computer1, node2 on
computer2, and so on).

9 Creating the Review Manager Enterprise Database
 A Java SDK. For WebSphere-based installations, McKesson supports any

WebSphere-supported Java SDK that is compatible with version 1.6.0_16 of
the Sun Java SDK.
 Your DBMS.
For information about database compatibility, see Chapter 1, “Supported
Technical Configurations.
Creating the Review Manager Enterprise Database

You will create the Review Manager Enterprise database using an interactive
SQL tool (such as SQL*Plus). For instructions on how to create the database,
refer to Chapter 7, “Installing Review Manager Enterprise”.
Populating the Review Manager Enterprise Database

To populate the database, you must run the Microsoft Windows installer for
Review Manager Enterprise. You must perform the procedure described
in this section on a Windows-based computer.
To install Review Manager Enterprise, follow the procedures in Chapter 7,

“Installing Review Manager Enterprise, and do the following:
 When prompted for the installation location, accept the default value
(C:\Program Files). This value will install Review Manager Enterprise into
the C:\Program Files\McKesson\CERME directory.
 If you choose to install the HL7 application, do not choose the option to
start the service automatically.
 Do not install Jetty.
 Do install an alternate application server. When prompted to provide the
directory containing your application server’s resource and property files,
type the following: C:\Program Files\McKesson\CERME
Copying Required Files for Linux with WebSphere

After creating and populating the database, you must copy the required
application files to each of the WebSphere Application Server nodes in the
WebSphere cluster.
To copy the required files:

1. On computer1, create the Review Manager Enterprise installation directory
and subdirectories. To create these directories, in the Red Hat terminal,
type the following lines, pressing Enter after each line:
mkdir -p /opt/McKesson/CERME
cd /opt/McKesson/CERME
mkdir doc

9 Copying Required Files for Linux with WebSphere
mkdir warfiles
Manager Enterprise, copy the following files from
C:\Program Files\McKesson\CERME\Doc to computer1 into the
/opt/McKesson/CERME/doc directory:
 DataDictionary.pdf
 HL7.zip
 RMInstallationGuide.pdf
 SystemAdministratorsGuide.pdf
Manager Enterprise, copy the oscache.properties file from
Manager Enterprise, copy the log4j.xml file from
C:\Program Files\McKesson\CERME\warfiles to computer1 into the
/opt/McKesson/CERME/warfiles directory:
 b2sw.war
 help.war
 help2005.war
 help2006.war
 help2007.war
 help2008.war
 help2009.war
 rm.war
6. Repeat steps 1 through 5 on each additional computer in the cluster (for
example, computer2).


1. On computer1, from the /opt/IBM/WebSphere/AppServer/profiles/
AppSrv01/properties directory, open the oscache.properties file in any text
editor.

l_addr=true)
oscache.properties file from the /opt/IBM/WebSphere/AppServer/profiles/
AppSrv01/properties directory on computer1 to the corresponding directory
on each additional computer.

connection.

For example:
...
</Config>
necessary changes.


directory on the Windows-based computer to the /opt/IBM/WebSphere/
AppServer/profiles/AppSrv01/properties directory of each application
server node (for example, node1).
nodes combined.

Installing Verdana Font

McKesson recommends that you install Verdana font for optimal Smartsheets
and InterQual View PDF generation.
To install Verdana font:

1. Download VERDANA.TTF font file from
http://sourceforge.net/projects/corefonts/files/
2. Copy VERDANA.TTF font to a folder on a Linux machine (for example /opt/
fonts).
3. Edit ReviewManager.xml to add the folloing line:
<Fonts path="/opt/fonts" name="VERDANA.TTF"/>
where path specifies the folder path where verdana font file was placed,
and name specifies the name of the verdana font file.

10
Installing and Configuring Inbound and
Outbound HL7 for Linux-based
WebSphere Installations
This chapter describes how to install and configure the HL7 Interface in your
Red Hat Enterprise Linux environment to use inbound and outbound
messaging.
Inbound HL7 is not a WebSphere application. You will install inbound HL7 as a
background service. In a clustered environment, you will install the inbound
HL7 service on only one server.
Outbound HL7 is a part of the CareEnhance Review Manager Enterprise

application that is hosted by WebSphere. In a clustered environment, you
must select one of the application servers to be the primary outbound HL7
handler. McKesson recommends that you choose a different server from the
one hosting the HL7 server.

 Prerequisites
 Installing and Configuring the Outbound HL7 Service
 Verifying the Outbound HL7 Installation
 Assigning an Application Server to Be the Outbound HL7 Handler
 Installing and Configuring the Inbound HL7 Service
 Upgrading the Outbound HL7 Service
 Upgrading the Inbound HL7 Service

10 Prerequisites
Prerequisites
Before installing and configuring the HL7 services, make sure that you have
done the following:
 Installed and configured Review Manager Enterprise in your Linux
Environment
 Have not modified or removed your original Windows-based installation of
Review Manager Enterprise (which you used to populate the initial
database)
 You have superuser access to the Red Hat Enterprise Linux computer on
which you will install the HL7 service
Installing and Configuring the Outbound HL7 Service

To enable the HL7 Interface for outbound messaging:
Manager Enterprise, copy the Symphonia-3.8.7.jar file from
C:\Program Files\McKesson\CERME\jarfiles to the
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/
<ServerName>Cell01/rm_war.ear/rm.war/WEB-INF/lib directory of each
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/properties directory of
each application server node.
 jakarta-regexp-1.5.jar
 mklic.sh
 Symphonia3-Runtime.lic
 Symphonia-3.8.7.jar
3. Convert the mklic.sh shell script to the Unix text file format using the
dos2unix program:
On computer1, in the Red Hat terminal, type the following lines, pressing
Enter after each line:
dos2unix /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/mklic.sh
4. Update the HL7 license information:
A. In the Red Hat terminal, type the following, and then press Enter:
cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/properties
B. Type the following, and then press Enter: ./mklic.sh
The Symphonia3.properties file is created in the same directory. This file
contains the HL7 license string.

10 Verifying the Outbound HL7 Installation
Verifying the Outbound HL7 Installation

To verify that the Review Manager HL7 Interface is configured correctly, on
each application server, log on to the Review Manager System Administration
Module. If the Navigation Pane contains an HL7 item, then the HL7 Interface is
configured correctly. If the System Administration Module on any of the
application servers does not display the HL7 Navigation Pane item, then repeat
the procedure in “Installing and Configuring the Outbound HL7 Service” on
page 74.
Assigning an Application Server to Be the Outbound HL7

Handler
If you are using Review Manager Enterprise in a clustered environment, you
must select one application server in the cluster to be the outbound HL7 queue
handler. Keep in mind that this application server will have to handle additional
workload, so consider performance when making your selection. McKesson
recommends that you choose a different server from the one hosting the HL7
server.
To assign an application server to be the outbound HL7 handler:

outbound HL7 handler, from the /opt/IBM/WebSphere/AppServer/profiles/
AppSrv01/properties directory, open the ReviewManager.xml file in any text
editor.
2. Add the line OutboundHL7QueueHandler="true" attribute to the <Mode>
element. For example:
<Mode Cluster="true" OutboundHL7QueueHandler="true"/>
...
</Config>
 Do not add the line OutboundHL7QueueHandler attribute to the <Mode>
 Add the line OutboundHL7QueueHandler attribute to the <Mode>
element of the ReviewManager.xml file, but set the value to false. For
example:
<Mode Cluster="true" OutboundHL7QueueHandler="false"/>
...
</Config>

10 Installing and Configuring the Inbound HL7 Service
Installing and Configuring the Inbound HL7 Service

To install and configure the Inbound HL7 service:
1. On computer1, create an HL7 installation directory. To create this directory,
in the Red Hat terminal, type the following, and then press Enter:
mkdir -p /opt/HL7Server
C:\Program Files\McKesson\CERME\jarfiles to your HL7 Server into the
/opt/HL7Server directory:
 cermehl7.xml
 cermehl7apps.jar
 CERMEHL7FileLoader.sh
 CreateCERMEHL7Service.sh
 mklic.sh
 rm.jar
 RmHL7XmlEdit.sh
3. Convert the shell scripts to the Unix text file format using the dos2unix
program:
dos2unix /opt/HL7Server/CERMEHL7FileLoader.sh
dos2unix /opt/HL7Server/CreateCERMEHL7Service.sh
dos2unix /opt/HL7Server/RmHL7XmlEdit.sh
dos2unix /opt/HL7Server/mklic.sh
4. Using any text editor, open the CERMEHL7FileLoader.sh and
CreateCERMEHL7Service.sh files and edit the
CERME_REVIEW_MANAGER_XML variable to point to the location on
computer1 where you copied the ReviewManager.xml file. If you followed
this guide, this file should be in the /opt/IBM/WebSphere/AppServer/
profiles/AppSrv01/properties directory.
The shell script files (CERMEHL7FileLoader.sh, CreateCERMEHL7Service.sh,

and RmHL7XmlEdit.sh) are configured to reference the /opt/HL7Server
directory. If you copied the HL7 files to another directory, then you must also
edit the HL7_INSTALL_PATH variable in each of these scripts.
The HL7 startup script (CreateCERMEHL7Service.sh) has a variable
(JAVA_HOME), which is set to the default location of Java as delivered with
WebSphere (/opt/IBM/WebSphere/AppServer/java/jre/bin). If this is not the
correct location for WebSphere, you must modify the script accordingly.
5. If necessary, change the port number (the default is 7779). Using any text
editor, open the cermehl7.xml file, and edit the port number specified by
the following element:
<Setting Name="Port" Value="7779"/>

10 Upgrading the Outbound HL7 Service

cd /opt/HL7Server
Starting the Inbound HL7 Service

To start the inbound HL7 service:
1. In the Red Hat terminal, type the following, and then press Enter:
cd /opt/HL7Server
2. Type the following, and then press Enter:
./CreateCERMEHL7Service.sh
The HL7 server starts on the port number specified in cermehl7.xml.
Stopping the Inbound HL7 Service

The following change has been made to the CreateCERMEHL7Service.sh script
for Review Manager Enterprise 8.0.
The HL7 process is now started in the background. A stop script

(StopCERMEHL7.sh) is generated based on the process ID (PID) of the
background HL7 process that was started.
To stop the inbound HL7 service:

 Type the following, and then press Enter:
./StopCERMEHL7.sh
If the start script is run while the previous HL7 process is still running, the stop
script will be executed before the HL7 start script starts another HL7 process.
The stop script can be run independently of the start script.
The stop script can only be run once (it removes itself from the file system)
since it is referencing a specific PID.
Upgrading the Outbound HL7 Service

The outbound HL7 service is a part of the Review Manager Enterprise
application that is hosted by WebSphere. Therefore, the outbound HL7 service
is automatically upgraded when you upgrade the rm.war application (for
instructions about upgrading the Review Manager Enterprise application, refer
to Chapter 5, “Upgrading Review Manager Enterprise for Linux with
WebSphere”).
After upgrading the rm.war application, do the following to complete the

outbound HL7 service upgrade process:

10 Upgrading the Inbound HL7 Service

Manager Enterprise, copy the Symphonia-3.8.7.jar file from C:\Program
Files\McKesson\CERME\jarfiles to the /opt/IBM/WebSphere/AppServer/
profiles/AppSrv01/installedApps/<ServerName>Cell01/rm_war.ear/rm.war/
WEB-INF/lib directory of each application server node.
A. On computer1, in the Red Hat terminal, type the following, and then
press Enter:
cd /opt/IBM/Websphere/AppServer/profiles/AppSrv01/properties
Upgrading the Inbound HL7 Service

To upgrade the inbound HL7 service:
1. On the server running the HL7 service, stop the service by selecting the
terminal window in which the HL7 service is running and pressing CTRL+C.
C:\Program Files\McKesson\CERME\jarfiles to your HL7 Server into the HL7
installation directory (for example, /opt/HL7Server). Overwrite the old
versions of these file if necessary.
 cermehl7.xml
 CERMEHL7FileLoader.sh
 CreateCERMEHL7Service.sh
 mklic.sh
 rm.jar
 RmHL7XmlEdit.sh
3. Convert the shell scripts to the Unix text file format using the dos2unix
program:
dos2unix /opt/HL7Server/CERMEHL7FileLoader.sh
dos2unix /opt/HL7Server/CreateCERMEHL7Service.sh
dos2unix /opt/HL7Server/RmHL7XmlEdit.sh
dos2unix /opt/HL7Server/mklic.sh
4. Using any text editor, open the CERMEHL7FileLoader.sh and
CreateCERMEHL7Service.sh shell scripts and edit the
CERME_REVIEW_MANAGER_XML variable to point to the location on

computer1 where you copied the ReviewManager.xml file. If you followed

this guide, this file should be in the /opt/WebSphere/AppServer/properties
directory.
The shell script files (CERMEHL7FileLoader.sh, CreateCERMEHL7Service.sh,

and RmHL7XmlEdit.sh) are configured to reference the /opt/HL7Server
directory. If you copied the HL7 files to another directory, then you must also
edit the HL7_INSTALL_PATH variable in each of these scripts.
The HL7 startup script (CreateCERMEHL7Service.sh) has a variable
(JAVA_HOME), which is set to the default location of Java as delivered with
WebSphere (/opt/IBM/WebSphere/AppServer/java/jre/bin). If this is not the
correct location for WebSphere, you must modify the script accordingly.
cd /opt/HL7Server
7. Start the HL7 service:
cd /opt/HL7Server
B. Type the following, and then press Enter:
./CreateCERMEHL7Service.sh

11
Configuring Inbound and Outbound HL7 for
Windows-based WebSphere Installations
This chapter describes how to configure the HL7 Interface in your Windows
with WebSphere environment to use inbound and outbound messaging.
Inbound HL7 is not a WebSphere application.
If you install CareEnhance Review Manager in the default location of

C:\Program Files on computer 1, the installer will create the inbound HL7
server as a background service on computer 1 for you. In a clustered
environment, you install the inbound HL7 service on only one server.
Outbound HL7 is a part of the CareEnhance Review Manager Enterprise

application that is hosted by WebSphere. In clustered environment, you must
select one of the application servers to be the primary outbound HL7 handler.
McKesson recommends that you choose a different server from the one
hosting the HL7 server.

 Prerequisites
 Configuring the Outbound HL7 Service
 Verifying the Outbound HL7 Installation
 Assigning an Application Server to Be the Outbound HL7 Handler
 Configuring the Inbound HL7 Service
 Upgrading the Outbound HL7 Service
 Upgrading the Inbound HL7 Service

11 Prerequisites
Prerequisites
Before configuring the HL7 services, make sure that you have done the
following:
 Have not modified or removed your original installation of CareEnhance
Review Manager Enterprise on computer 1(which you used to populate the
initial database)
 You have superuser access to the computer on which you will configure the
HL7 service
Configuring the Outbound HL7 Service

To enable the HL7 Interface for outbound messaging:
1. On computer 1 where you initially installed CareEnhance Review Manager
Enterprise, copy the Symphonia-3.8.7.jar file from
C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\AppSrv01\
installedApps\<ServerName>Cell01\rm_war.ear\rm.war\WEB-INF\
lib directory of each application server node.
directory of each application server node.
 jakarta-regexp-1.5.jar
 RmHL7mkLicense.bat
By default, HL7 inbound will be running on computer 1. Choose a different

cluster node (for example, computer 2) to run outboundHL7.
3. On computer 2, edit the path dependencies of RmHL7mkLicense.bat

accordingly.
In a DOS shell on computer2, change directories to
Type RmHL7mkLicense.bat and press Enter.

11 Verifying the Outbound HL7 Installation
Verifying the Outbound HL7 Installation

To verify that the CareEnhance Review Manager HL7 Interface is configured
correctly, on each application server, log on to the CareEnhance Review
Manager System Administration Module. If the Navigation Pane contains an
HL7 item, then the HL7 Interface is configured correctly. If the System
Administration Module on any of the application servers does not display the
HL7 Navigation Pane item, then repeat the procedure in “Configuring the
Outbound HL7 Service” on page 81.
Assigning an Application Server to Be the Outbound HL7

Handler
If you are using CareEnhance Review Manager Enterprise in a clustered
environment, you must select one application server in the cluster to be the
outbound HL7 queue handler. Keep in mind that this application server will
have to handle additional workload, so consider performance when making
your selection. McKesson recommends that you choose a different server from
the one hosting the HL7 server.
To assign an application server to be the outbound HL7 handler:

outbound HL7 handler, from the C:\Program Files\IBM\WebSphere\
AppServer\profiles\AppSrv01\properties directory, open the
ReviewManager.xml file in any text editor.
2. Add the line OutboundHL7QueueHandler="true" attribute to the <Mode>
element. For example:
<Mode Cluster="true" OutboundHL7QueueHandler="true"/>
...
</Config>
 Do not add the line OutboundHL7QueueHandler attribute to the <Mode>
 Add the line OutboundHL7QueueHandler attribute to the <Mode>
element of the ReviewManager.xml file, but set the value to false. For
example:
<Mode Cluster="true" OutboundHL7QueueHandler="false"/>
...
</Config>

11 Configuring the Inbound HL7 Service
Configuring the Inbound HL7 Service

When CareEnhance Review Manager Enterprise is installed in the default
location of C:\Program Files on computer 1, the inbound HL7 service will
automatically be created on computer1. Therefore, you do not need to create
the HL7Server folder.
The service will be run out of C:\Program Files\McKesson\CERME\jarfiles on

computer1.The Symphonia3.properties file will be created by the installer.
Also, an instance of the ReviewManager.xml file will reside in the CERME folder.
The bat files (CERMEHL7FileLoader.bat, CreateCERMEHL7Service.bat, and

RmHL7XmlEdit.bat) are configured to reference the C:\Program
Files\McKesson\CERME directory. If you intend to run inbound HL7
somewhere other then in the default location, you must edit the path
dependencies in these files.
To configure the port number and license information:

A. In the Windows DOS shell on computer1, type the following, and then press
Enter:
C:\Program Files\McKesson\CERME\jarfiles
B. Type the following, and then press Enter: RmHL7mkLicense.bat
Starting and Stopping the Inbound HL7 Service

Start and Stop the CERMHL7 service using the Windows Computer
Management - Services Console on computer1.

11 Upgrading the Outbound HL7 Service
Upgrading the Outbound HL7 Service

The outbound HL7 service is a part of the CareEnhance Review Manager
Enterprise application that is hosted by WebSphere. Therefore, the outbound
HL7 service is automatically upgraded when you upgrade the rm.war
application. For instructions about upgrading the CareEnhance Review
Manager Enterprise application, refer to Chapter 4, “Upgrading or Adding
Products to Review Manager Enterprise for Windows with WebSphere”.
After upgrading the rm.war application, do the following to complete the

outbound HL7 service upgrade process:
Enterprise, copy the Symphonia-3.8.7.jar file from
C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\AppSrv01\
installedApps\<ServerName>Cell01\rm_war.ear\
rm.war\WEB-INF\lib directory of each application server node.
By default, HL7 inbound will be running on computer1. Choose a different
cluster node (such as computer 2) to run outboundHL7.On computer2, edit
the path dependencies of RmHL7mkLicense.bat accordingly.
2. In a DOS shell, on computer2, change directories to C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties. Type
RmHL7mkLicense.bat and press Enter.
Upgrading the Inbound HL7 Service

To upgrade the inbound HL7 service:
1. Stop the CERMHL7 inbound service using the Windows Computer
Management - Services console on computer1.
When CareEnhance Review Manager Enterprise is installed in the default
location of C:\Program Files on computer 1, the inbound HL7 service will
automatically be created on computer1.The service will be run out of
C:\Program Files\McKesson\CERME\jarfiles on computer1. An instance of
the ReviewManager.xml file will reside in the CERME folder.
During the upgrade, the following files will be updated:
 cermehl7.xml
 CERMEHL7FileLoader.bat
 CreateCERMEHL7Service.bat
 RmHL7mkLicense.bat
 rm.jar
 RmHL7XmlEdit.bat

The bat files (CERMEHL7FileLoader.bat, CreateCERMEHL7Service.bat, and

RmHL7XmlEdit.bat) are configured to reference the C:\Program
Files\McKesson\CERME directory. If you intend to run inbound HL7
somewhere other then in the default location, you must edit the path
dependencies in these files.
To configure the port number and license information:

A. In the Windows DOS shell on computer1, type the following, and then
press Enter:
C:\Program Files\McKesson\CERME\jarfiles
B. Type the following, and then press Enter: RmHL7mkLicense.bat
4. Start the CERMHL7 inbound service using the Windows Computer
Management - Services console on computer1.

12
Installing Review Manager Enterprise as a
WebSphere Application
This chapter describes how to set up a WebSphere cluster to run CareEnhance

Review Manager Enterprise. You must install Review Manager Enterprise and
its associated applications as WebSphere applications.

 Installing the Review Manager Enterprise Application
 Installing the Review Manager Enterprise Help Application
 Starting the Cluster
 Verifying the Virtual Host Configuration
 Completing the Installation
Installing the Review Manager Enterprise Application

This section describes how to install Review Manager Enterprise as a
WebSphere application.
To install the Review Manager Enterprise application files:

1. Log on to the WebSphere Administrative Console.
2. From the navigation panel, expand Applications, expand Application Types,
click WebSphere Enterprise Applications, and then click Install.

12 Installing the Review Manager Enterprise Application
The Preparing for the application installation window appears.
3. Depending on your Operating System, do one of the following:

 Linux—Select Remote file system, and type the following path:
/opt/McKesson/CERME/warfiles/rm.war
 Windows—Select Remote file system, and type the following path:
C:\Program Files\McKesson\CERME\warfiles\rm.war
4. In the Context Root text box, type the following:
/rm
5. Select the option to “Prompt me only when additional information is
required.”

6. Click Next.
WebSphere unpacks the .WAR file, and then displays the installation
options.

7. Either accept the default installation options or customize the settings for
your environment, and then click Next.
The Map modules to servers step appears.
8. Map the modules to the servers:

A. In the Clusters and Servers box, select all of the listed clusters and
servers.
B. Select module, and then click Apply.

C. Click Next.
9. To deploy the application, confirm that the summary information is correct,

and then click Finish.
The Installing window appears (only the final section is shown below).
10.Click Save.
WebSphere saves the changes to the master configuration.

12 Installing the Review Manager Enterprise Help Application
Installing the Review Manager Enterprise Help Application

This section describes how to install Review Manager Enterprise Help as a
WebSphere application.
Historical help content is available with Review Manager Enterprise 8.0. For
both Linux and Windows, the context root format is /help<year>. For
example, /help2005,/help2006, and so on. The context root for the current
year is /help. The help war naming format is help<year>.war. For example,
help2005.war.
To install the Review Manager Enterprise Help application files:

2. From the navigation panel, expand Applications, and then click Install New
Application.
The Preparing for the application installation window appears.
3. Depending on your Operating System, do one of the following:
 Windows—Select Server Path, and type the following path:
C:\Program Files\McKesson\CERME\warfiles
 Linux—Select Server Path, and type the following path:
/opt/McKesson/CERME/warfiles/help.war
4. In the Context Root text box, type the following:
/help
5. Select the option to “Prompt me only when additional information is
required.”
6. Click Next.
WebSphere unpacks the .WAR file, and then displays the installation
options.
7. Either accept the default installation options or customize the settings for
your environment, and then click Next.
The Map modules to servers step appears.
8. Map the modules to the servers:
A. In the Clusters and Servers box, select all of the listed clusters and
servers.
B. Select module, and then click Apply.
C. Click Next.
9. To deploy the application, confirm that the summary information is correct,
and then click Finish.
The Installing window appears.
10.Click Save.
WebSphere saves the changes to the master configuration.

12 Starting the Cluster
Starting the Cluster

Starting the cluster also starts the application servers and the applications that
you just installed.
To start the cluster:

1. If it is not open, open and log on to the Deployment Manager on
computer1.
2. From the navigation panel, expand Servers, expand Clusters, and then click
WebSphere Application Server Clusters.
The Server Cluster window appears.
3. Select the cluster, and then click Start.

12 Verifying the Virtual Host Configuration
Verifying the Virtual Host Configuration

You only need to perform the following procedure if you installed Review
Manager Enterprise in a clustered environment.
After starting the applications, verify that WebSphere is configured to use the
correct connectivity options.
2. From the navigation panel, expand Environment, and then click Virtual
Hosts.
The Virtual Hosts window appears.
3. Review the virtual host configurations. If incorrect virtual hosts are

displayed:
A. Select the incorrect virtual host, and then click Delete.
B. Click New.
The New window appears.
C. In the Name text box, type the virtual host name, and then click OK.
D. Repeat steps A through C for each incorrect virtual host.
4. If you made any changes to the virtual hosts, restart the cluster.

12 Completing the Installation

To complete the installation, do the following:
 Configure the Web Server Plug-in:
Configure the Web server plug-in to point to the correct locations of the
Deployment Manager plug-in and keys. To configure the Web server plug-
in, consult your Web server’s documentation.
 Configure each client workstation:
For information about configuring each client workstation, refer to
Chapter 8, “Logging on to CareEnhance Review Manager”.
 Log on to Review Manager Enterprise:
For information about logging on to Review Manager Enterprise, refer to
Chapter 8, “Logging on to CareEnhance Review Manager”.

13
Configuring Microsoft® IIS for Review
Manager Enterprise
This chapter describes how to configure Microsoft Internet Information

Services (IIS) to host Review Manager Enterprise. Instructions are provided
for both IIS 6.0 and IIS 7.0. Reference links to the ISAPI filters are provided in
this chapter.
Configuring Jetty to Accept Proxied Requests

1. Enable AJP/1.3 Connector in Jetty 6.1.x as follows:
A. To allow Jetty to accept requests for CERMe from IIS, edit the
/mckesson/jetty/etc/jetty.xml file and ensure that the AJP/1.3
Connector is enabled (that is, not commented out).
B. To enable the AJP/1.3 Connector in CERMe, remove the comment
symbols () around the following section in the etc/jetty.xml
file:



<Call name="addConnector">
<Arg>
<New class="org.mortbay.http.ajp.AJP13SocketConnector">
<Set name="Port">8009</Set>
<Set name="MaxIdleTime">0</Set>
<Set name="confidentialPort">443</Set>
</New>
</Arg>
</Call>

13 Configuring the Jetty Connector
Configuring the Jetty Connector

1. Depending on whether you are configuring IIS 6.0 or IIS 7.0, do one of the
following:
 For IIS 6.0, download the version 1.2.26 of isapi_redirect-x.x.x.dll
from the URL below to a temp directory:
 Windows 32 machine:
http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/
binaries/win32/
http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/
binaries/win64/
 For IIS 7.0, download the latest version of isapi_redirect-x.x.x.dll from
the URL below to a temp directory:
http://apache.wildit.net.au/tomcat/tomcat-connectors/jk/binaries/
win32/
http://apache.wildit.net.au/tomcat/tomcat-connectors/jk/binaries/
win64/
2. Create a folder to house the isapi dll. (for example, C:\Isapi).
3. Copy the dll to the <ISAPI> folder.
4. Rename the downloaded version of the file in step 3 to isapi_redirect.dll.
5. In the <ISAPI> directory, create a folder called conf.
6. In the <ISAPI> directory, create a folder called logs.
7. Create an empty isapi_redirect.properties file in the <ISAPI> directory.
8. Create an empty workers.properties.minimal and uriworkermap.properties
file and place in the conf folder
9. In the <ISAPI> directory, edit the isapi_redirect.properties file and
paste the contents in Figure 1 below.
Change the 3 installation paths to match your environment and save the
file. For now, leave the log_level to debug for troubleshooting until we
have a working set, then change the debug to error.
Restart IIS after making changes to the properties files.
Figure 1
# Configuration file for the Jakarta ISAPI Redirector
# The path to the ISAPI Redirector Extension, relative to the

website
# This must be in a virtual directory with execute privileges
extension_uri=/rm/isapi_redirect.dll
# Full path to the log file for the ISAPI Redirector

log_file=C:\Isapi\logs\isapi_redirect.log

# Log level (debug, info, warn, error or trace)

log_level=debug
# Full path to the workers.properties file

worker_file=C:\Isapi\conf\workers.properties.minimal
# Full path to the uriworkermap.properties file

worker_mount_file=C:\Isapi\conf\uriworkermap.properties
10.In the <ISAPI>/conf folder, edit the workers.properties.minimal file and
paste the following contents in Figure 2. Change the 2 installation paths to
match your environment and save the file.
Figure 2
workers.tomcat_home=C:\Program Files\McKesson\CERME\Jetty\
# This file provides minimal jk configuration properties needed
to # connect to Jetty.
workers.java_home=C:\Program Files\McKesson\CERME\Jre\
#
# The workers that jk should create and work with.
#
worker.list=worker1
#
# Defining a worker named worker1 and of type ajp13.
# Note that the name and the type do not have to match.
#
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
# Example socket channel, override port and host.

[channel.socket:localhost:8009]
port=8009
host=127.0.0.1
# define the worker

[ajp13:localhost:8009]
channel=channel.socket:localhost:8009
# Uri mapping. This says that any incoming connection to any

file
# under "/jetty/" should be handled the worker defined above

[uri:/jetty/*]
worker=ajp13:localhost:8009
# CERMe app context - /rm

[uri:/rm/*]
# CERMe help context - /help*

[uri:/help*/*]
11.In the <ISAPI>/conf folder, edit the uriworkermap.properties file and
paste the following contents.
# uriworkermap.properties - IIS
#
# This file provides mappings for the workers
# defined in workermap.properties.minimal.
# The general syntax for this file is:
# [URL]=[Worker name]
#CERMe app worker mapping

/rm/*=worker1
# CERMe help worker mapping

/help*/*=worker1

13 Configuring IIS 6.0
Configuring IIS 6.0

The person completing the following IIS Adminstration tasks, must have
Administrator rights.
1. Using the IIS management console (Internet Information Services in

Administrative Tools), add a new Virtual Directory to your IIS web site.
The name of the virtual directory must be rm, as it must correspond with
the first part of the extension_uri setting specified in the
isapi_redirect.properties file. Its Physical path should be the directory
where you placed isapi_redirect.dll.
2. When you create the new virtual directory, give it execute access.

3. Find the newly created rm virtual directory under Default Web Site.
4. Right-click on the rm virtual directory, and then click Properties.

The rm Properties window appears.
5. Click the Remove button next to the application name, and then click Apply.
6. Click OK.
7. Add isapi_redirect.dll as a filter to your IIS web site as follows:
A. Right-click on the Web Sites icon on the left pane of the Internet
Services Manager (or IIS management console), and select Properties.
B. Select the ISAPI Filters tab.

The name of the filter should reflect its task; for example, confluence,
and its executable must be the full path to the ajp isapi redirector DLL.
8. Restart IIS (stop and start the IIS service - not just the web server - do this
by right-clicking on Local Computer in the IIS Manager and choosing All
Tasks, Restart IIS...).
9. Verify that the confluence filter is marked with a green up arrow confirming
that it is loaded and initialized correctly. If the ajp redirector did not
initialize properly, check the log file for errors messages
(C:\<ISAPI>\logs\isapi_redirect.log).
Adding the isapi_redirect.dll as a Web Server Extension

To add the isapi_redirect.dll as a web server extension:
1. Click on the Web Service Extensions icon in the left pane of the Internet
Services Manager (or IIS management console).
The web service extensions UI will display in the right pane.
2. Click the Add a new Web service extension… link.
The New Web Service Extension window appears.

3. Enter a name for the extension (for example, rm_isapi extension).
4. Click the Add button for Required files.

The Add file window appears.
5. Click the Browse... button and locate the isapi_redirect.dll.
In the example below for IIS 6.0, the <ISAPI> directory that houses the
isapi_redirect.dll is named Mck_IIS.
6. When you locate the dll, click Open, and then click OK.

The New Web Service Extension window appears.
7. Select the Set status extension to Allowed check box, and then click OK.
In the example above, disregard the 2 that displays in the isapi_redirect2.dll

file name.
The ISAPI dll should now be registered with IIS 6.

8. Restart IIS 6.0.
You have now completed configuring Microsoft Internet Information
Services (IIS) 6.0 to host Review Manager Enterprise.
Review Manager, refer to Chapter 8, “Logging on to CareEnhance Review
Manager.”
Configuring IIS 7.0

1. Using the IIS management console (Internet Information Services in
Administrative Tools), add a new Virtual Directory to your IIS web site.
The name of the virtual directory must be rm, as it must correspond with
the first part of the extension_uri setting specified in the
isapi_redirect.properties file.
2. In the Add Virtual Directory window, enter rm in the Alias field.

3. Verify that the Physical path is the directory where you placed
isapi_redirect.dll, and then click OK. In this example, it is C:\Isapi.
4. Under Default Web Site in the left pane, right-click on rm, and then select
Edit Permissions.
The Isapi Properties window appears.
5. Make sure that users have the following permissions, and then click OK.
 Read & execute
 Read
 List folder contents
6. Click Default Web Site in the left pane, and then double-click the ISAPI
Filters icon in the right pane.

ISAPI Filters information appears in the right pane.
7. Right-click on the ISAPI Filters pane, and then click Add on the menu that
appears.
The Add ISAPI Filter window appears.
8. Add isapi_redirect.dll as a filter to your IIS web site as follows:

A. In the Filter name field, enter rm.
B. In the Excutable field, enter the full path to the isapi_redirector.dll,
which is C:\Isapi\isapi_redirect.dll.
C. Click OK.
9. To confgure handler mappings, click rm in the left pane, and then double-
click on the Handler Mappings icon in the right pane.
The Handler Mappings information displays.
10.In the Name column, double-click ISAPI-dll.

The Edit Module Mapping window appears.
11.In the Executable (optional) field, enter the path as

C:\Isapi\isapi_redirect.dll, and then click OK.
An Edit Script Map prompt appears.
12.Click Yes at the prompt.
13.Under Handler Mappings, verify that ISAPI-dll appears as Enabled.
14.Restart IIS 7.0.

You have now completed configuring Microsoft Internet Information
Services (IIS) 7.0 to host Review Manager Enterprise.
Manager.”

A
Manager
This chapter describes all the tasks that you need to perform to upgrade to
CareEnhance Review Manager 9.0 or to add new products to an existing
installation of Review Manager 9.0.
For installations using Jetty, Review Manager 9.0 requires Jetty 6.1.20. The
Review Manager installation program automatically re-installs Jetty during the
installation process to ensure that you are using this version.
Before Upgrading to Review Manager 9.0

If you have already upgraded to Review Manager 9.0 and are adding new
products only, do not update the database. Continue with the section
“Starting the Review Manager Upgrade Process” on page 110.
Before upgrading to Review Manager 9.0, do the following:

 Review the system requirements in Chapter 1, “Supported Technical
Configurations.”
upgrade. Your McKesson representative will provide you with this
information.
 Before upgrading, you should create a full backup of your Review
Manager database.
During installation, Review Manager creates a backup of your existing

installation directory and indicates the location where it has been backed up
to. See “Customizing the Upgrade” on page 112.
 Make sure that all users have logged out of Review Manager.
 Ensure that the Windows user upgrading Review Manager has

A Updating the Database
 You can upgrade to Review Manager either from version 7.x or 8.x. If you
are upgrading from a version prior to 7.0, then you must first upgrade to
version 7.0 before upgrading to version 9.0.
If you upgrade directly from Review Manager 7.0 to version 9.0, the
InterQual 2010 Criteria (which is included with Review Manager 9.0) will be
installed, but the InterQual 2009 Criteria (which was included with Review
Manager 8.0) will not be installed. If you also want the InterQual 2009
Criteria, then you must first upgrade to Review Manager 8.0 before
upgrading to version 9.0.
McKesson recommends upgrading your Review Managertest environment to

version 9.0 before upgrading your production environment.
Updating the Database

If you have already upgraded to Review Manager 9.0 and are adding new
products only, do not update the database. Continue with the section
“Starting the Review Manager Upgrade Process” on page 110.
Before upgrading the Review Manager software, you must first update the
Review Manager database.
Updating a Microsoft Access Database

To maintain the integrity of the database, McKesson strongly recommends
that you run a Repair and Compact on the database prior to installing new
criteria and then again after the installation is completed. For information
about Repair and Compact, see the CareEnhance Review Manager System
Administrator’s Guide.
The Review Manager upgrade process automatically runs the

access_upgrade.sql database script, which is found on the Review Manager
installation DVD in the Scripts folder. This script makes all the necessary
database changes; no user interaction is required.
Updating a Microsoft SQL Database

This section describes how to update your Review Manager SQL database.
Upgrading your Microsoft SQL Server Software

If along with your Review Manager upgrade you are also upgrading your
Microsoft SQL Server software (for example, from SQL Server 2005 to SQL
Server 2008), then you must first upgrade to your new version of Microsoft
SQL Server, before you upgrade to the latest version of Review Manager. Make
sure to backup your database before and after upgrading Review
Manager and before upgrading your database server.

A Updating the Database
Upgrading your Review Manager SQL Database

You must do the following procedure before upgrading any administrator or
client workstations. Failure to do so will cause errors when accessing the new
features in Review Manager. If you have not upgraded your databases, the
upgrade process.
To update your Review Manager SQL database:

1. Log on to Query Analyzer or SQL Server Management Studio as the user
who ran the mss_create.sql script that was used when the database was
created (that is, the owner of the Review Manager tables).
To find the user ID that was used to run this create the database, open the
CareEnhance Review Manager Connection XML Editor (RmXmlEdit.bat),
which is located in the Jetty folder
(C:\Program Files\McKesson\CERME\Jetty by default). The following image
shows the Connection XML Editor interface.
The password associated with this user ID is encrypted and not listed in the
Connection XML Editor. If you forgot the password for this user, use SQL
Server Management Studio to change the user’s password. Make sure to
test the connection when you are done.
2. Run the mss_upgradeto90.sql script against the Review Manager
database. This script is on the Review Manager installation DVD in the
Scripts folder.

A Starting the Review Manager Upgrade Process
Starting the Review Manager Upgrade Process

To start the upgrade process:
Installation Guides, and System Administrator’s Guide.
installation.

application.

A Starting the Review Manager Upgrade Process
The Licensed Products Window appears.The Licensed Product window

is licensed.
licensed.

The Select Review Manager Application window appears. If you are
licensed for Review Manager Enterprise, Review Manager, and InterQual
View, then the installer will prompt you to choose which product to
upgrade.
11.Select Review Manager, and then click Next.
The Review Manager Installation Type window appears.
12.Choose the type of upgrade:
 If you are upgrading to a new version of Review Manager (for
example, if you are currently running version 8.0 and want to install
version 9.0), select Upgrade, and then click Next.
Choosing the Upgrade option updates your Review Manager software in
addition to installing any new products you choose.
 If you are adding new products only (for example, if you already
upgraded your Review Manager software to version 9.0, and you want
to install a new criteria product), select Add new products, and then
click Next.
The Existing CERM Installation Location window appears.
13.Continue with the procedure “Customizing the Upgrade” on page 112.

A Customizing the Upgrade
Customizing the Upgrade

The Existing CERM Installation Location window specifies the location of your
existing installation of Review Manager.
1. Click Browse and navigate to the path where your existing installation of
Review Manager was installed, and then click Next. The default path is
C:\Program Files\McKesson\CERM.
Review Manager creates a backup of your existing installation and displays
a message indicating the location where it has been backed up to.
2. Click OK in the message.
The Type of Installation window appears.
The Client installation includes the Review Manager application and the Web
server. You should choose this installation for most users. The Administrator
installation includes the Review Manager application, the Web server, and the
System Administration Module. After creating the database and installing the
criteria, use the System Administration Module to configure and maintain
Review Manager. Typically, there is only one administrator installation.
For Microsoft Access installations, installing the Administrator package also

updates the Review Manager Microsoft Access database, so you must install
the Administrator package at least once.
A Client package installation prompts you for the location of the Access
database, so you must upgrade the Administrator package prior to any
client packages.
Upgrading an Administrator Package

To upgrade an Administrator package:
1. Click the Administrator icon, and then click Next.
The Choose Components window appears.The Choose Components window
displays a list of all the licensed products.
2. Select which products to install, and then click Next.
You can install all of the criteria sets for which you are licensed or you can
customize your installation to include only certain criteria sets.
Select Review Manager Application to install Review Manager in addition to
the Administration Module.
The Pre-Installation Summary window appears.
3. Continue with the procedure “Completing the Upgrade” on page 113.
Upgrading a Client Package

To upgrade a Client package:
1. Click the Client icon, and then click Next.
2. Continue with the procedure “Completing the Upgrade” on page 113.

A Completing the Upgrade
Completing the Upgrade

selected.
chose to install.
By default, Review Manager and the Review Manager Administration
Module are installed to: C:\Program Files\McKesson\CERM
 C:\Program Files\McKesson\CERM\Jetty
 C:\Program Files\McKesson\CERM\jre
You have successfully upgraded Review Manager.
Manager.”
Migrating Organizational Policies

After upgrading to Review Manager 9.0, you must migrate your organizational
policies using the organizational policy migration utility in the System
Administration module.
For information on using the organization policy migration utility, see the
CareEnhance Review Manager System Administrator’s Guide.

B
Installing Review Manager
This chapter describes all the tasks that you need to perform to install
CareEnhance Review Manager. Review Manager is a Web browser-based
application that requires Web server software. McKesson includes the Jetty
Web Server (for Windows) with the Review Manager installer.
The Review Manager Installer installs the application on your client computer
and loads the criteria sets into your database. While the application is installed
on your client computer, the database may reside either on your client
computer or a network server.
Before You Begin

Before installingReview Manager, do the following:
 Review the hardware and software requirements in Chapter 1, “Supported
Technical Configurations.”
 Ensure that the Windows user installing Review Manager has administrative
rights to the installation workstation.
 Decide whether you want to install the application from a DVD or copy the
downloaded application files to the network.
If you decide to install across the network, before beginning the
installation, copy the entire contents of the Review Manager installation
DVD to a network drive. Each workstation where you will install Review
Manager must have read access to this drive.
installation. Your McKesson representative will provide you with this
information.
 Obtain a username and password to log on toReview Manager. Your
McKesson representative will provide you with a default username and
password.
 Determine where you want to installReview Manager.

B Creating the Database
 Decide whether you want to install the Administrator or Client Review

Manager software.
McKesson recommends installingReview Manager 9.0 in a test environment

before installing it in your production environment.
Creating the Database

Pre-installation planning should be performed by the person responsible for
installations at your site.
Review Manager supports only the characters contained in the

WE8MSWIN1252 database character set.
If You Use Microsoft Access

If you are installing the Access version of Review Manager, then the Review
Manager installer automatically creates the Access database during the
If You Use Microsoft SQL Server

Review Manager does not support connectivity to Microsoft SQL Server in
Windows NT Authentication mode; you must use SQL Server authentication.
To install the Microsoft SQL Server version of Review Manager, you must use a
SQL Server login that has database owner privileges on the Review Manager
database. Day-to-day operations of Review Manager require the specific server
login with SELECT, UPDATE, INSERT, and DELETE rights to the Review Manager
tables.

B Starting the Installation Process
Before installing Review Manager using Microsoft SQL Server, your database
administrator must perform the following tasks:
1. Edit the mss_crt_db.sql script (located on the Review Manager installation
DVD in the Scripts folder) to customize the database file names and sizes.
You may also change the user or name of the database created by the
script. If you change the user or name of the database, record these
modifications because you will need to specify these changes later in the
This username and password is used both to install Review Manager and to
upgrade to future versions of Review Manager.
The username and password will be encrypted and placed in an XML file that
is used by the software. McKesson recommends that you do not use a login
with sysadmin privileges.

A. Log into Query Analyzer as the system administrator (sa or another
login with sysadmin privileges).
B. Run the edited mss_crt_db.sql script.
During the Review Manager installation process, you will reference the
new database name and the server where the database resides.
A. Log into Query Analyzer as the new user created by the mss_crt_db.sql
script.
B. Run the mss_create.sql script on the newly created database. This script
is located on the Review Manager installation DVD in the Scripts folder.
Starting the Installation Process

Review Manager (using Jetty, which is the included application server) is
configured by default to use port number 7776. If port 7776 is already being
used at your site (for example, for Internet Information Services (IIS)) you
will need to change the port to an unused port number, such as 7007.
Install the Review Manager application on a client workstation (not on your

network server).

B Starting the Installation Process

Review Manager Installation Guide, InterQual View Installation Guide, and
System Administrator’s Guide.
installation.

application.
The Licensed Products Window appears. The Licensed Product window

is licensed.
licensed.

The SelectReview Manager Application window appears. If you are licensed
forReview Manager Enterprise, Review Manager, and InterQual View, then
the installer will prompt you to choose which product to install.
To install InterQual® View, follow the instructions in the InterQual View

Installation Guide.

B Customizing the Installation
11.Select Review Manager, and then click Next.

The Review Manager Installation Type window appears.
12.Select New installation, and then click Next.
The Type of Installation window appears.

The Type of Installation window enables you to select whether to install the
client or administrator version of Review Manager.
The Client installation includes the Review Manager application and the Web
server. You should choose this installation for most users. The Administrator
installation includes the Review Manager application, the Web server, and the
System Administration Module. After creating the database and installing the
criteria, use the System Administration Module to configure and maintain
Review Manager. Typically, there is only one administrator installation.
For Microsoft Access installations, installing the Administrator package also

creates the Review Manager Access database, so you must install the
Administrator package at least once.
Client package installations prompt you for the location of the Access
database, so you must install the Administrator package before
installing any Client packages.
Installing the Administrator Package

To install the Administrator package:
1. Click the Administrator icon, and then click Next.
The Choose Components window appears and displays a list of all the
licensed products.
2. Select which products to install.
You can install all of the criteria sets for which you are licensed or you can
customize your installation to include only certain criteria sets.
Select Review Manager Application to install Review Manager in addition to
the Administration Module.
default location, which is C:\Program Files.
The desktop shortcuts check box enables you to create shortcuts on your
Windows desktop to the Review Manager appplication. Whether or not you
choose to create shortcuts on your desktop, you can access the Review
Manager application from Start > Programs > Review Manager.
4. Choose whether or not to create desktop shortcuts, and then click Next:
 If you want to create shortcuts, leave the check box selected.

B Customizing the Installation
 If you do not want to create shortcuts, clear the checkbox.

The Review Manager Database Information window appears.
information:
 For a Microsoft Access database:
a. Choose the folder where you want to install the Access database, and
then click Next.
The Review Manager Database ID window appears.
b. Enter a Database ID. If you are creating multiple installations, for
example, on laptop computers, the Database ID must be unique on
each laptop. The Database ID is used to create unique numbers for
such items as reviews. The Database ID can be any name of your
choosing.
c. Click Next.
The Database ID is not the database name.
 For a Microsoft SQL Server database:

a. Specify the following information:
 Port Number—the database listener port address. Default is 1433.
b. Click Next.
Installing a Client Package

To install a Client package:
1. Click the Client icon, and then click Next.
default location, which is C:\Program Files, and then click Next.
The Review Manager Database Information window appears.
information:

B Completing the Installation
 For a Microsoft Access database, choose the folder where the

Microsoft Access database is located (the database was created during
the Administrator package installation), and then click Next.
 For a Microsoft SQL Server database, specify the following
information, and then click Next.
 Port Number—the database listener port address, Default is 1433.
The install program will verify that it can connect to the Review Manager
database. If it cannot, then you will be given the opportunity to correct
the connection information.

TheReview Manager Connection Information window appears.
1. Leave the default values or customize the connection information for
Review Manager, and then click Next
chose to install.
By default, Review Manager and the Review Manager Administration
Module are installed to: C:\Program Files\McKesson\CERM
 C:\Program Files\McKesson\CERM\Jetty
 C:\Program Files\McKesson\CERME\Jre
You have successfully installed Review Manager.
Manager.”

C
Troubleshooting Tips
This appendix provides information for troubleshooting CareEnhance Review

Manager Enterprise and CareEnhance Review Manager.
Separate Database and Application Servers

For optimal performance, McKesson recommends that:
 The CareEnhance Review Manager application reside on a separate server
than the database
 You periodically restart the server
Internet Explorer Security Settings

If you are experiencing problems performing certain tasks within CareEnhance
Review Manager, your Internet Explorer security settings may be set at a level
that is too high. If you adjust the settings for Internet and Local intranet to the
default level, and add the CareEnhance Review Manager URL to the Trusted
sites at the default level, CareEnhance Review Manager should work
effectively.
To adjust the security settings:

1. Open Internet Explorer.
2. From the Tools menu, select Internet Options.
3. Click the Security tab.
4. Change the security settings as necessary, and then click OK.

C Viewing the Online Help
Viewing the Online Help

If the CareEnhance Review Manager Help does not appear properly, try the
following:
 Clear your temporary Internet files, making sure to select the option to
delete all offline content.
 Configure your pop-up blocker. For instructions, refer to “Configure the
Internet Explorer Pop-up Blocker” on page 65.
Viewing Log Files

CareEnhance Review Manager consists of several executable Java run-time
and CareEnhance Review Manager application WAR files. It is possible that
after an extended period of successful operations one of the components
might experience problems. There are several log files that you can use to
troubleshoot problems. You can print these log files or attach them to e-mails
that you send to McKesson Product Support for analysis.
On Microsoft Windows, all log files (for Jetty-based installations) are located in
the C:\Program Files\McKesson\CERME\Jetty\logs directory unless otherwise
specified.
CERMEConsole.log File
CareEnhance Review Manager creates the CERMEConsole.log file, which
contains informational messages. For Jetty installations, restarting the
CareEnhance Review Manager Enterprise service truncates the log file. If you
access CareEnhance Review Manager using a port number other than 80, then
the port number appears in the log file name (for example,
CERME8001Console.log).
CERMEError.log File
CareEnhance Review Manager creates the CERMEError.log file, which records
errors from either Java run-time or Jetty. For Jetty installations, restarting the
CareEnhance Review Manager Enterprise service truncates the log file. If you
access CareEnhance Review Manager using a port number other than 80, then
the port number appears in the log file name (for example,
CERME8001Error.log).
When reporting an issue with CareEnhance Review Manager, send a copy of

this file to McKesson. Make sure the copy is of the file from the workstation
that is experiencing the issue.
rm.log File
This file logs all criteria loaded into the database during installation. This file is
located in the C:\Program Files\McKesson\CERM folder.

C Debugging Information
ReviewManager.xml File
Use this file to define database connections and miscellaneous items used by
the Web/application server. The parameters used are defined within the XML
file.
Jetty.xml
Use this file to determine the listening port number and information about
about the Jetty service. This file is located in
C:\Program Files\McKesson\CERM\Jetty\etc.
Additional Log Files

In addition to the previously described log files, the following files may be used
to identify any problem:
 CareEnhance_Review_Manager_Product_Installlog.log (located in
c:\Program Files).
 CERM_Installer_Debug.txt
 CERM_Installer_Actions_Debug.txt
 audit_log2.txt (The location of this file is specified in the Global Settings in
the Administration Module. For details on setting the location, refer to the
System Administrator’s Guide.)
 iq_system_access.txt (The location of this file is specified in the Global
Settings in the Administration Module. For details on setting the location,
refer to the System Administrator’s Guide.)
 iq_activity_audit.txt (The location of this file is specified in the Global
Settings in the Administration Module. For details on setting the location,
refer to the System Administrator’s Guide.)
 c:\Program Files\McKesson\CERME\logs
 If you are licensed for HL7, then you can access these logs as well:
 CERMEHL7Console.log
 CERMEHL7Error.log
 OutboundHL7Activity.log
Debugging Information
You can log debugging information to the CERMEConsole.log and
CERMEError.log files.
To enable debug logging, in the ReviewManager.xml file, change the

debugSQLx attributes from “N” to “Y.” For example:
<ReviewManager appType=”CERM” xml:space=”preserve”>
<Config CacheSize=”100” debugSQL1=”Y” debugSQL2=”Y” debugSQL3=”Y”
debugSQL4=”Y” debugLevel1=”Y” debugLevel2=”Y” debugLevel3=”Y”
debugLevel4=”Y” >
...

C Database Connections
For Jetty installations, restarting the CERMe service truncates the debugging
log files.
Database Connections
The Microsoft Windows installation and the ReviewManager.xml file each need
a connection to the database(s). Currently, CareEnhance Review Manager
Databases connect using a DSN-less type connection to connect to a particular
database for new and upgrade installations. Beginning with CareEnhance
Review Manager 9.0, ODBC data sources are no longer used. Connections to
the CareEnhance Review Manager MS SQL database are handled by a JDBC
driver.
For CERMe 9.0, connection to the CareEnhance Review Manager Microsoft

Access database is handled in the ReviewManager.xml. It utilizes the default
install folder path if the database is located on the same machine where
CareEnhance Review Manager is installed (C:\Program Files\McKesson\). If the
Access database is located on a separate machine, then its location must be
entered in UNC path format (\\mypc\drive\folder name).
CareEnhance Review Manager relies on the database to secure the data which
is accomplished by a username/password mechanism defined by the database.
Both a password and the corresponding username are stored in two places:the
database and the ReviewManager.xml file. The CareEnhance Review Manager
application connects to a database using a database-provided username and
the corresponding password. These parameters are stored in the
ReviewManager.xml file in encrypted form. If you change either a username or
a password in a database, you will need to repeat the change in the
ReviewManager.xml file. For more information on changing your password,
refer to the CareEnhance Review Manager System Administrator’s Guide.
Database connections are pooled. The size and behavior of a pool is set at the
time of a CareEnhance Review Manager installation. The pool parameters
are:initial number of connections, maximum number of connections in a pool,
and the session timeout parameter. Default settings for a pool might be
insufficient for a multi-user installation and may be changed using the
RmXmlEdit.bat file.
Java Virtual Machine Tuning

If you did not modify the default configurations set in CareEnhance Review
Manager 8.0, then the recommended configurations will be set by default in
CareEnhance Review Manager 9.0.
If your site experiences poor performance with CareEnhance Review Manager,

McKesson recommends that you adjust the heap size of the Java virtual
machine to allocate more memory space. The recommended allocation is "-
1024M", meaning to use up to 1024MB of physical memory for Java programs.
This is based on the assumption that you are running CareEnhance Review
Manager Enterprise on a machine with 2GB of RAM.

C CacheSize in CareEnhance Review Manager.xml
 Previous Setting:-Xmx256M
 Recommended setting:-Xmx1024
To make this change, you modify the CreateCERMEService.bat file located in

the C:\Program Files\McKesson\CERMe\Jetty folder:
1. Stop the CERMe service.
2. Locate the CreateCERMEService.bat file and make a copy of this file.
3. Open the CreateCERMEService.bat file using an editor such as notepad.
4. Replace "-Xmx256M" with "-Xmx1024M" and save the file.
5. Restart the CERMe service.
CacheSize in CareEnhance Review Manager.xml

The CacheSize in ReviewManager.xml file is used by CareEnhance Review

Manager Enterprise to cache frequently used data.
To improve performance, you can edit the “Config” element in the

ReviewManager.xml file:
2. Locate the ReviewManager.xml file and make a copy of this file.
3. Open the ReviewManager.xml file using an editor such as Notepad.
4. Change the CacheSize value to 1000 and save the file.
5. Restart the CERMe service
Jetty MaxThreads Count

Jetty maxThreads is the limit to the number of threads that can be allocated to
connections for that HTTP listener. This will effectively limit the number of
simultaneous users of the server as well as the maximum memory usage.
Please see this URL for further details:
http://docs.codehaus.org/display/JETTY/Walkthrough+jetty.xml
Edit the jetty.xml file to change the ThreadPool setting. Set the value of
maxThreads to 1024 by doing the following:

C HL7 Server Linux Script Change

2. In the C:/Program Files/McKesson/CERME/Jetty/etc folder, locate the
jetty.xml file and make a copy of this file.
3. Open the jetty.xml file using an editor such as notepad.
4. Change the maxThreads count to 1024 and save the file.
5. Restart the CERMe service.
HL7 Server Linux Script Change

The following change has been made to the CreateCERMEHL7Service.sh script
for CareEnhance Review Manager Enterprise 8.0.
The HL7 process is now started in the background. A stop script

(StopCERMEHL7.sh) is generated based on the process ID (PID) of the
background HL7 process that was started.
To stop the inbound HL7 service:

 Type the following, and then press Enter:
./StopCERMEHL7.sh
If the start script is run while the previous HL7 process is still running, the stop
script will be executed before the HL7 start script starts another HL7 process.
The stop script can be run independently of the start script.
The stop script can only be run once (it removes itself from the file system)
since it is referencing a specific PID.

D
Setting Up SSL Security Using Digital
Certificates
A digital certificate is a virtual identity that contains a digital signature and

other identifying information that has been issued and sealed by a certification
authority (CA). A CA is a trusted organization that issues and manages digital
certificates. Digital certificates are used to verify and authenticate the identity
and privileges of a person or organization on the Web. Digital certificates
enable secure e-business by providing assurances of identity for both
customers and vendors.
Your company might have its own documentation for creating certificates. If
available, McKesson recommends that you refer to this documentation before
following the process described in this appendix. In addition, application
servers come with their own documentation for setting up SSL certificates. The
instructions in this appendix outline a general process for creating a certificate
for setting up SSL for your Web Application Server, using Jetty as an example.
Certificate Signature Request (CSR) and Private Keys

To acquire a digital certificate from a certificate authority, you must submit a
request to that CA in a format called a Certificate Signature Request (CSR).
The CSR contains information that is used to identify the entity that is
requesting the certificate. This information is referred to as an X.500
distinguished name and is required for X.509 certificates.

D Certificate Signature Request (CSR) and Private Keys
The following table describes the X.509 certificate field names.
Field X.500 Description

Code
Full host name CN The fully-qualified name of the application server on which the digital certificate will be
installed. This name is used for DNS lookups of the application server. For example,
node.mydomain.com. Web browsers compare the host name in the URL to the
name in the digital certificate. The name specified here must exactly match the
name used in your URL. If you change the host name later, you must request a new
digital certificate.
Note: If the server is being accessed via an intranet then the appropriate name may
simply be the server name and the port number (e.g. myserver:8080).
For example:
 If your URL is http://www.<server>.com
then use www.<server>.com
 If your URL is http://<server>
then use <server>
 If your URL is http://<server>:8080
then use <server>:8080
Organizational unit name OU The name of your division, department, or other operational unit of your organization.
Organization name O The name of your organization. The certificate authority might require any host names
entered in this field to belong to a domain registered to this organization.
Locality name (city) L The name of your city or town. If you operate with a license granted by a city, this field
is required; you must enter the name of the city that granted your license.
State name S The name of the State or Province in which your organization operates if your
organization is in the United States or Canada, respectively. Do not abbreviate.
Country code C The two-letter ISO code for your country. The code for the United States is US.
Private Key Password N/A The password used to encrypt the private key.
Enter a password in this field if you want to use a protected key with the application
server. If you choose to use a protected key, you are prompted for this password
whenever the key is used. If you specify a password, you get a PKCS-8 encrypted
private key. If you do not want to use a protected key, leave this field blank.
Random String N/A A string of characters to be used by the encryption algorithm. You do not have to
remember this string in the future. It adds an external factor to the encryption
algorithm, making it more difficult for anyone to break the encryption. For this reason,
enter a string that is not likely to be guessed.
If you use this feature, it is recommended that you use a long string with a good
mixture of uppercase and lowercase letters, digits, spaces, and punctuation
characters; these long, mixed strings contribute to more secure encryption.
Strength N/A The length (in bits) of the keys to be generated. The longer the key, the more difficult it
is for someone to break the encryption. For some application servers, you might need
a special license in order to use certain encryption strength keys. Speak to the server
vendor for details.

D Installing Digital Certificates for Jetty
Installing Digital Certificates for Jetty

Jetty utilizes Java’s JSSE keytool/keystore for managing keys and certificates.
For more information, see
http://java.sun.com/javase/6/docs/technotes/tools/windows/keytool.html
Prerequisites
Depending upon the version of Java that you are using, you might have to
perform additional steps in order to complete the setup. This document
assumes that you are using JRE 1.6.0_16 for keystore management.
JRE 1.5 incorporates JSSE. Earlier versions of Java require a separate

download/install of JSSE.
VeriSign/Thawte
It is important that you specify an alias and that the alias is the same for
each of the following steps.
1. Generate private-key / public-key pair. The public key is wrapped in a self-

signed certificate. To generate the key, type the following a
keytool -genkey -v –keyalg RSA –alias <alias> -keystore
<keystore-name> -storepass <keystore-password>
-keypass <key-password>
keytool -genkey -v –keyalg RSA –alias mck -keystore keystore.ks
-storepass secret -keypass reallysecret
For the preceding example, you are prompted to enter the values of your
distinguished name (this is the recommended approach). A keystore called
keystore.ks is created in the directory from which keystore is run. The
private and public keys are added under an alias of ‘mck’. The key is
encoded using the RSA algorithm.
Alternatively, if you are familiar with the structure of X.500 distinguished
names, you could specify the distinguished name on the command line
instead of being prompted for it. If you use spaces or “:” in the fields, the
field must be surrounded by escaped-quotes (e.g. \”).
For example:
keytool -genkey -v –keyalg RSA –alias mck –dname
"CN=www.mysite.com, OU=Development, O=\”McKesson Corporation\”,
L=\”San Francisco\”, ST=California, C=US" -keystore keystore.ks
-storepass secret -keypass reallysecret
2. Backup your keystore.

3. Generate a certificate request (CSR)

keytool -certreq –alias <alias> -keystore <keystore-name> -
storepass <keystore-password> -file <csr filename>
keytool -certreq –alias mck -keystore keystore.ks
-storepass secret –file mycert.csr
In the preceding example, a CSR is generated from your X.500
distinguished name that you specified when you created the keystore via
–genkey. The CSR is saved to the file ‘mycert.csr’. You might want to
generate the CSR to your console to facilitate cutting and pasting the
following into the CA’s Web site:
keytool -certreq –alias mck -keystore keystore.ks
-storepass secret
4. Backup your CSR.
5. Submit CSR to a certificate authority to obtain a CA certificate
Use the table below to determine the type of certificate to obtain.
Table D–1 Types of Digital Certificates
Vendor URL Certificate Type
VeriSign http://www.verisign.com/ssl/index.html  Secure Site (40-bit)1 – Secure Server Id
Server Type: JavaSoft
 Secure Site (128-bit)1 – Global Server Id
Server Type: Apache
Thawte http://www.thawte.com SSL Chained CA Cert
Submitting the CSR to a CA usually requires you to provide information

about your organization. The CA uses this information to validate your
company’s credentials. In addition, you must provide the CA with the text
of the CSR that you generated above. The CSR contains an encrypted
version of your distinguished name. It can take several days to receive a
response from the CA.
Example CSR (the CSR includes both the begin and end strings):
-----BEGIN NEW CERTIFICATE REQUEST-----
MIIBxDCCAS0CAQAwgYMxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybml
hMRYwFAYDVQQHEw1TYW4gRnJhbmNpc2NvMSIwIAYDVQQKExlNY0tlc3NvbiBDb3
Jwb3JhdGlvbiwgSW5jMRQwEgYDVQQLEwtEZXZlbG9wbWVudDENMAsGA1UEAxMEa
W1hYzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAmpvHBJo8KfDIjaa2oRpq
UdaCJp7ZH8Fo4oSK7+5enAYRdejwWsFljLIG/bxX6E3PSPXAX/+FlfswVud6mHl
QLbex1nCQluHdm7swaNuVWJOV7ZPlgrh3t2dqyhId9x0e+tm2LvNV5sSOsnQ0mR
gV+uerqmSutIOcQiLDvufcVZECAwEAAaAAMA0GCSqGSIb3DQEBBAUAA4GBAAvA5
nJrXpiVzpnYmdosxlnlZPcoTkoF5aA+AaCcH/Bua+FdknPpbYorgkbCmhbXT25+
ktTREEJHtrRzHwRIWzRSkqh9M0pk+ABolT78ZoCScG11v/yhnEX/XGElNda83wT
6fML6mXZRZDPP5j0wA0pn96QuUvm63zuajrpr92/+
-----END NEW CERTIFICATE REQUEST-----
6. If applicable: Obtain the CA Intermediate Certificate (or Server Certificate
Chain). For VeriSign, the intermediate certificate can be found on the
VeriSign Web site at:
http://www.verisign.com/support/ssl-certificates-support/install-ssl-
certificate.html
In the right column of the table shown, there is a blue box with a URL,
clicking on the URL will produce a box with the certificate. It is
recommended that you copy the intermediate certificate into a file called
verisign-intermediate.cer.

7. If applicable: Import the CA Intermediate Certificate (or Server Certificate

Chain) into the keystore using an alias name different from the alias used
to create your private key.
keytool -import -v -alias <new-alias> -trustcacerts
-keystore <keystore-name> -storepass <keystore-pass>
-keypass <key-passord> -file
<CA-intermediate-certificate-file>
keytool -import -v -alias verisignintermediate
-trustcacerts -keystore keystore.ks -storepass secret -keypass
verysecret -file verisign-intermediate.cer
For VeriSign: If you skip this step, you will receive chaining errors when you
try to import your CA response certificate into your keystore.
8. Import the CA response certificate into the keystore.

keytool -import -v -alias <alias> -trustcacerts
-keystore <keystore-name> -storepass <keystore-pass>
-keypass <key-passord> -file <CA-certificate-file>
keytool -import -v -alias mck -trustcacerts -keystore
keystore.ks -storepass secret -keypass verysecret
-file verisign.cer
The certificate response is typically delivered to you via email in an ascii
text format called PEM. You should paste the certificate response from the
CA into a file called <mycertificate>.cer.
The certificate will be bounded by, and must include, the begin and end
strings, for example:
-----BEGIN CERTIFICATE-----
MIIDdjCCAuOgAwIBAgIQHvQQsxE05mvAakh7UoRGGjANBgkqhkiG9w0BAQQFADB
fMQswCQYDVQQGEwJVUzEgMB4GA1UEChMXUlNBIERhdGEgU2VjdXJpdHksIEluYy
4xLjAsBgNVBAsTJVNlY3VyZSBTZXJ2ZXIgQ2VydGlmaWNhdGlvbiBBdXRob3Jpd
HkwHhcNMDIwMzI3MDAwMDAwWhcNMDMwMzI3MjM1OTU5WjCBgzELMAkGA1UEBhMC
VVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcUDVNhbiBGcmFuY2lzY28
xIjAgBgNVBAoUGU1jS2Vzc29uIENvcnBvcmF0aW9uLCBJbmMxFDASBgNVBAsUC0
RldmVsb3BtZW50MQ0wCwYDVQQDFARpbWFjMIGfMA0GCSqGSIb3DQEBAQUAA4GNA
DCBiQKBgQCam8cEmjwp8MiNprahGmpR1oImntkfwWjihIrv7l6cBhF16PBawWWM
sgb9vFfoTc9I9cBf/4WV+zBW53qYeVAtt7HWcJCW4d2buzBo25VYk5Xtk+WCuHe
3Z2rKEh33HR762bYu81XmxI6ydDSZGBX656uqZK60g5xCIsO+59xVkQIDAQABo4
IBEDCCAQwwCQYDVR0TBAIwADALBgNVHQ8EBAMCBaAwPAYDVR0fBDUwMzAxoC+gL
YYraHR0cDovL2NybC52ZXJpc2lnbi5jb20vUlNBU2VjdXJlU2VydmVyLmNybDBE
BgNVHSAEPTA7MDkGC2CGSAGG+EUBBxcDMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8
vd3d3LnZlcmlzaWduLmNvbS9ycGEwHQYDVR0lBBYwFAYIKwYBBQUHAwEGCCsGAQ
UFBwMCMBkGCmCGSAGG+EUBBg8ECxYJMTc3NjY3MjI3MDQGCCsGAQUFBwEBBCgwJ
jAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AudmVyaXNpZ24uY29tMA0GCSqGSIb3
DQEBBAUAA34Adgcl/vkqi4SgiNVKAJgcps28pqJDt+vtrCAb+YupTNTKaAp/mCg
HGmCTrLMac8yKOlsKz0U8O22JIp6Kj7ekx5yBy0JDU3CAPdV247xghX+QHnvu0J
mb7KNVweK+gR7VzL8D68CVmRpzazzItNCYjs1PV3Q89qr6fwXTDp0=
-----END CERTIFICATE-----
9. Modify <Jetty-home>\etc\jetty.xml.
The CareEnhance Review Manager Enterprise Installer will do this for you.

Uncomment the SSL socket connector and set the appropriate values. The
SSL connector can be found by searching for ‘SslSocketConnector’.
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.security.SslSocketConnector">
<Set name="Port">8443</Set>
<Set name="maxIdleTime">30000</Set>
<Set name="handshakeTimeout">2000</Set>
<Set name="keystore"><SystemProperty name="jetty.home" default="." />/etc/
keystore</Set>
<Set name="password">OBF:1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4</Set>
<Set name="keyPassword">OBF:1u2u1wml1z7s1z7a1wnl1u2g</Set>
<Set name="truststore"><SystemProperty name="jetty.home" default="." />/etc/
keystore</Set>
<Set name="trustPassword">OBF:1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4</Set>
<Set name="handshakeTimeout">2000</Set>
</New>
</Arg>
</Call>
You can conceal your passwords in this file by obfuscating them. For
information about obfuscating your passwords, refer to your Jetty
documentation.
Once obfuscated, you need to add the obfuscation string to your XML in place
of your clear text password. In addition, the string will need to be prefaced
by the string: “OBF:”.
10.Remember that the default port for https is 443 not 80, so change 8443 to
443 if you want to use URLs without explicit port numbers. Production sites
usually have a HttpListener on port 80 and a SunJsseListener on port 443.
Note that these ports are privileged, so you might want to use a redirection
mechanism to map the ports. For example, map port 80 to 8080 and port
443 to 8443.
11.Make sure that your system wide cacerts file contains the root CA
certificate for your certificate vendor.
The Java JRE ships with root CA certificates for both VeriSign and Thawte. If
you are using another vendor, you will need to acquire the root CA
certificate for that vendor and import it into the cacerts file. The cacerts file
is typically found at <java-home>\lib\security, where <java-home> is the
runtime environment's directory (the JRE directory in the SDK or the top-
level directory of the Java 2 Runtime Environment).

D Certificates Notes
System administrators can configure and manage the cacerts repository

using keytool, specifying JKS as the keystore type. The initial password of
the cacerts keystore is changeit, or no password.
IMPORTANT: Verify your cacerts file. Because you trust the CA’s file, verify
this in your cacerts file as entities for signing and issuing certificates to other
entities. Manage the cacerts file carefully. The cacerts file should contain only
certificates of the CA’s you trust. It is your responsibility to verify the trusted
root CA certificates bundled in the cacerts file and make your own trust
decisions. To remove an untrusted CA certificate from the cacerts file, use
the delete option of the keytool command.
12.Restart Jetty.
Certificates Notes
The following sections describe general information about digital certificates.
VeriSign
 What is the difference between a VeriSign 40-bit SSL Secure Server ID and
a 128-bit SSL Global Server ID?
The primary difference between the two types of VeriSign Server IDs is the
strength of the SSL session that each enable. Secure Sockets Layer (SSL)
technology is the industry-standard method for protecting Web
communications developed by Netscape® Communications Corporation.
The SSL security protocol provides data encryption, server authentication,
message integrity, and optional client authentication for a TCP/IP
connection. Because SSL is built into all major browsers and Web servers,
simply installing a digital certificate turns on their SSL capabilities.
SSL comes in two strengths, 40-bit and 128-bit, which refer to the length of
the "session key" generated by every encrypted transaction. Longer keys
provide stronger encryption that it is more difficult to decrypt. Most
browsers support 40-bit SSL sessions and the latest browsers enable users
to encrypt transactions in 128-bit sessions—trillions of times stronger than
40-bit sessions.
Secure Site Pro and Commerce Site Pro Services include 128-bit SSL
Global Server IDs, which enable 128-bit SSL encryption—the world's
strongest—with both domestic and export versions of Microsoft and
Netscape browsers. (Most people in the U.S. use export-version browsers).
Secure Site and Commerce Site Services include 40-bit SSL Secure
Server IDs, which enable 40-bit SSL when communicating with export-
version Netscape and Microsoft Internet Explorer browsers, and 128-bit
SSL encryption when communicating with domestic-version Microsoft and
Netscape browsers.For more information, see
http://www.verisign.com/ssl/ssl-information-center/faq/index.html.
 At present, only the Secure Server ID supports Java. Java is not supported
by the Global Server ID. This is due to the fact that their intermediate CA is
incompatible with JSSE (according to VeriSign). An alternative to this is to
obtain a 128-bit Global Server ID for Apache.

D Certificates Notes
 When using the 40-bit certificate, you will only achieve 128-bit encryption if
supported by your browser. For IE, you need the “domestic” version. If you
specify Help > About Internet Explorer, cipher strength should be indicated
under the browser version. It should indicate 128. If not, you need to
update the browser. If you purchase the 128-bit certificate, it will “enforce”
128-bit encryption, regardless of the browser cipher strength (domestic or
export). In addition, if the browser happens to only support a lesser cipher
strength, such as 56-bit, the certificate will also enforce 128-bit encryption.
 Trial certificates available for free download are equivalent to the 40-bit
Secure Server certificates. If you want to try to use a trial certificate for
testing, you will need to obtain a test CA root and install it into your
browser. For more information, see
http://www.verisign.com/ssl/buy-ssl-certificates/free-ssl-certificate-trial/
test-root-ca/index.html.
 Trial certificates are not good for testing and can take 1hr to several days to
obtain.
 Verisign “certificate roots” (needed by the browser) are provided by default
with most browsers and with the Java JRE distribution.
 You have 30 days to modify your CSR or certificate once purchased. After
that time, you need to pay $100 to get a reissue of the certification.
Intermediate CA certificates can be obtained at
http://www.verisign.com/support/ssl-certificates-support/install-ssl-
certificate.html.
Thawte
 Thawte is now owned by Verisign
 Thawte has several different types of certificates available for purchase. For
Jetty, you must obtain the SSL Chained CA Cert. If you purchase the X.509
v3 or equivalent, it will not work as it does not establish the trust chain
properly
 Trial Chained CA certificates available for free download are not fully trusted
and will display a trust error if the certificate is viewed in the browser. This
is corrected by actually “buying” the certificate. The purchased certificate is
fully trusted.
 Trial certificates are good for testing and can be downloaded instantly from
the Web site.
 Thawte “certificate roots” (needed by the browser) are provided by default
with the Java JRE distribution.

RMInstallation Guide

Uploaded by

Document Information

Original Description:

Original Title

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

RMInstallation Guide

Uploaded by

Copyright:

Available Formats

CareEnhance® Review Manager

McKesson Health Solutions, LLC

275 Grove Street Tel: 617.273.2800

Welcome to the Installation Guide

Chapter 1 Supported Technical Configurations

Chapter 2 Installation Overview

Chapter 3 Upgrading or Adding Products to Review Manager

Chapter 4 Upgrading or Adding Products to Review Manager

CareEnhance Review Manager Installation Guide 6

Copying the Required Files..................................................................................................... 29

Chapter 5 Upgrading Review Manager Enterprise for Linux with

Chapter 6 Creating a WebSphere Cluster

Chapter 7 Installing Review Manager Enterprise

Chapter 8 Logging on to CareEnhance Review Manager

CareEnhance Review Manager Installation Guide 7

Chapter 9 Installing Review Manager Enterprise for Linux

Chapter 10 Installing and Configuring Inbound and Outbound HL7 for

Chapter 11 Configuring Inbound and Outbound HL7 for Windows-

Chapter 12 Installing Review Manager Enterprise as a WebSphere

Chapter 13 Configuring Microsoft® IIS for Review Manager Enterprise

CareEnhance Review Manager Installation Guide 8

Appendix A Upgrading or Adding Products to Review Manager

Appendix B Installing Review Manager

Appendix C Troubleshooting Tips

Appendix D Setting Up SSL Security Using Digital Certificates

CareEnhance Review Manager Installation Guide 9

Welcome to the Installation Guide

This preface contains the following topics:

Who Should Read this Guide

CareEnhance Review Manager Installation Guide 10

Accessing MHS Customer Hub

Obtaining Product Support

The response guidelines for Product Support are as follows:

Priority Level Description Callback How To Contact

CareEnhance Review Manager Installation Guide 11

Review Manager is a Web browser-based software application that delivers

The following are sample installation configurations for CareEnhance® Review

Review Manager Production Configurations

End User Web Server

CareEnhance Review Manager Installation Guide 12

Supported Installation Configurations

Client Workstation Software

CareEnhance Review Manager Installation Guide 13

Additional Required Software

CareEnhance Review Manager Installation Guide 14

Recommended Hardware Configurations

CareEnhance Review Manager Installation Guide 15

Upgrading or Adding Products to CareEnhance Review

Installing CareEnhance Review Manager Enterprise for

Installing CareEnhance Review Manager Enterprise for

CareEnhance Review Manager Installation Guide 16

3. Chapter 11, “Configuring Inbound and Outbound HL7 for Windows-based

Installing Review Manager Enterprise for Windows with Jetty

Installing CareEnhance Review Manager Enterprise for Linux

Installing CareEnhance Review Manager

CareEnhance Review Manager Installation Guide 17

Before Upgrading to Review Manager Enterprise 9.0

Before upgrading to Review Manager Enterprise 9.0, do the following:

During installation, Review Manager creates a backup of your existing

CareEnhance Review Manager Installation Guide 18

McKesson recommends upgrading your Review Manager Enterprise test

Updating the Database