1. Accessing current release bulletin information
A more recent version of this release bulletin may be available on the World Wide Web. To check for critical product or document information added after the release of the product CD, use the Sybase Technical Library Product Manuals Web site.
To access release bulletins at the Technical Library Product Manuals Web site
Go to Product Manuals.
Follow the links to the appropriate New Era of Networks product.
Select the “Release Bulletin” collection for the product version you are interested in.
You can either download the PDF version or browse the document online.
2. Product summary
For details on system requirements and platform information, see the Clinical Gateway Installation Guide.
This release bulletin provides the latest information about Clinical Gateway and known software problems or documentation updates and clarifications.
3. Special installation instructions
See “5.1 Installation Guide” for recent additions to the Installation Guide.
3.1 Install Adobe Acrobat Reader 5.0
New Era of Networks Process Server documentation is supplied in pdf files. Use Adobe Acrobat Reader version 5.0 to view the documentation. You can download the reader from the Technical Library CD or from the Adobe web site at http://www.adobe.com.
If you are currently using Reader 4.0, you must upgrade to version 5.0 to read the documentation.
To install documentation on Windows:
To install documentation on AIX, HP-UX, or Solaris
Open the applicable platform folder under the acrobat directory on the Technical Library CD.
Follow the instructions in the INSTGUID.TXT file.
4. Known problems
This section describe known problems and workarounds for New Era of Networks Process Server.
[Bug 301062] The Content Type value of text/jsp on the Clinical Gateway Configuration Administration screen damages the cgweb.conf configuration file when you select the Save Configuration button.
Workaround: Use the text/xml or text/html (the default) setting instead of text/jsp.
Bug 301144] The Content Type value of text/jsp on the Clinical Gateway Configuration Administration screen results in Facility displaying ERROR if an encounter list or details are displayed in the right pane.
Workaround: Use text/xml or text/html (the default) setting.
5. Documentation updates and clarifications
5.1 Installation Guide
This section discusses updates and clarifications for the Installation Guide.
5.1.1 Installing Third Party Java Archive (JAR) Files
The following information should be added to Chapter 4 of the Installation Guide.
Clinical Gateway requires third party Java software available for download (the download location is specified in the section below for your platform). The software required is an open source XSLT processor called “Saxon” and the IBM MQ Series MA88 service pack.
You can install the third party JAR files either on the application server (globally, which makes JAR visible to all web applications) or locally, on the Clinical Gateway web application.
Procedures for adding third party JAR files globally vary for different application servers. Typically, you add JAR files to the application server’s CLASSPATH prior to startup. See your application server’s documentation for information about installing a third party JAR globally. Global additions are required for BEA WebLogic and IBM WebSphere. If you use global additions, make the additions prior to deploying CG.war into the application server.
Alternatively, you may install the JARs local to the Clinical Gateway web application by copying the JAR files into the Clinical Gateway web application lib directory (for example, …\EAServer\Repository\WebApplication\CG\WEB-INF\lib for EA Server).
To install locally, you must first deploy the CG.war file into your application server to create the directory structure for the Clinical Gateway web application.
WebLogic does not create a directory structure, so you cannot install locally. WebSphere creates a directory structure, but the third party JARs are required at deployment, so you cannot install locally.
The following sections describe the process of downloading and installing the JAR files on your application server before and after deploying CG.war to the application server.
Adding the Saxon XSLT Processor from Michael Kay (on EAServer, WebSphere, WebLogic)
Perform these steps for all Clinical Gateway installations unless the Saxon XSLT processor is already installed globally on your application server. This procedure adds an XSLT processor used for server-side XSLT transformations. Only Internet Explorer 6 supports client-side XSLT transformations for Clinical Gateway content delivery; all other browsers require server-side transformations.
Download Full Saxon version 6.2.2 at http://saxon.sourceforge.net/. The latest version is certified for use with Clinical Gateway.
Extract saxon.jar file from the downloaded saxon.zip file.
Install saxon.jar as described in your application server’s documentation.
Adding IBM MQ Series service pack MA88 (on EAServer, WebLogic)
This procedure adds MQ Series java API support, which allows the Clinical Gateway web application to communicate with MQ Series. Perform these steps if MQ Series Java API support is not already installed globally on your application server. Steps specific to MA88 and WebSphere are detailed in the steps below
Download MA88 service pack file, ma88_win.zip, from http://www-3.ibm.com/software/ts/mqseries/txppacs/ma88.html.
MA88 – Install the MA88 service pack on the backend server, then copy com.ibm.mq.jar and jms.jar from from ...\MQSeries\java\lib to a temporary directory on the front-end server.
WebSphere – Extract com.ibm.mq.jar and jms.jar directly from ma88_win.zip and copy to a temporary directory on the front-end server.
Install com.ibm.jar or jms.jar as described in your application server’s documentation.
IBM MQ Series service pack MA88 (on WebSphere only)
This procedure adds MQ Series Java API support, which allows the Clinical Gateway web application to communicate with MQ Series. Perform these steps if MQ Series java API support is not already installed globally on your application server. You must perform these steps before you deploy CG.war to WebSphere.
Download MA88 service pack file, ma88_win.zip, at http://www-3.ibm.com/software/ts/mqseries/txppacs/ma88.html.
Extract the files from ma88_win.zip to a temporary directory.
For the most up-to-date information, review the ma88 README file in …\program files\IBM\MQSeries\Java\doc\en_US\readme.txt.
Some path names may have embedded spaces (for example, program files). To resolve this issue, copy the …\program files\IBM\MQSeries\Java directory to a permanent directory location on the front-end server. The new Java directories, particularly Java\lib, are added to the classpath in subsequent steps.
Save a backup copy of …\WebSphere\AppServer\bin\setupCmdLine.cmd, open the original with a text editor, and add the following above the line starting with SET WAS_CLASSPATH= (The values for the following SET commands all comprise one line; they wrap to a second line in this example due to space constraints):
rem Per configuration instructions in MA88 echo adding MA88 jars to classpath in setupCmdLine.bat SET MQDIR=D:\MQSeries\Java\lib SET MQ1=%MQDIR%\com.ibm.mq.jar SET MQ2=%MQDIR%\com.ibm.mqjms.jar SET MQ3=%MQDIR%\jms.jar SET MQ4=%MQDIR%\jndi.jar SET MQ5=%MQDIR%\connector.jar SET MQ6=%MQDIR%\providerutil.jar SET MQ7=%MQDIR%\ldap.jar SET MQ8=%MQDIR%\com.ibm.mqbind.jar SET MQ9=%MQDIR%\fscontext.jar SET MQ10=%MQDIR%\jta.jar SET ALLMQ= %MQDIR%;%MQ1%;%MQ2%;%MQ3%;%MQ4%;%MQ5%; %MQ6%;%MQ7%;%MQ8%;%MQ9%;%MQ10%;
Absolute path values shown for MQDIR variable should be adjusted appropriately.
Add “;%ALLMQ%;” to the end of the line that begins SET WAS_CLASSPATH=:
SET WAS_CLASSPATH=%WAS_HOME%\properties;%WAS_HOME% \lib\bootstrap.jar;%ALLMQ%;
5.2 System Management Guide
This section discusses updates and clarifications to the System Management Guide.
5.2.1 Wrong Web address specified
The System Management Guide includes an incorrect Web address on page 5 in Chapter 2. The correct address is at http://saxon.sourceforge.net
5.2.2 Wrong version of Saxon
References to Saxon 6.4 on page 5, Chapter 2, should refer to Saxon 6.2.2
5.2.3 Starting Process Server
Start the Process Server with a scheduler priority of “low.” Enter:
start /low EPEEngine.cmd
5.2.4 Periodic cleanup of Process Server runtime Database
The following paragraph should appear at the end of Chapter 3 of the System Management Guide:
Periodically run the EPECleanup utilities to remove the Process Server specific audit and history data from the Process Server runtime Database. Enter the following at the command line to run EPECleanup:
5.2.5 Limiting Facility Names for MRN and Account Number Searches
The following information should appear at the end of Chapter 3 of the System Management Guide:
By default, all facility codes supplied through input messages to Clinical Gateway populate the Facility lists in the MRN Search and Account Search input areas.
Typically, sites use a single facility name. For example, a site may use HIS for all entity and encounter OSN elements in the XMLHL7MSG documents input to the Clinical Gateway CGIN queue.
Log in to Clinical Gateway as an administrative user.
Select the Expand/Contract button under SQL Queries.
Append “ where OSN = 'HIS'” in the Value input area (near the bottom of page).
Append “ where OSN = 'HIS'” in the Value input area (near bottom of page).
6. Technical support
For a listing of local support center numbers, refer to online resources from:
For more information on Support Services, education, and consulting services, refer to the Customer Services Reference Guide.
7. Other sources of information
The Technical Library CD contains product manuals and is included with your software. The DynaText reader (included on the Technical Library CD) allows you to access technical information about your product in an easy-to-use format.
Refer to the Technical Library Installation Guide in your documentation package for instructions on installing and starting the Technical Library.
The Technical Library Product Manuals web site is an HTML version of the Technical Library CD that you can access using a standard web browser. In addition to product manuals, you will find links to EBFs/Updates, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.
To access the Technical Library Product Manuals web site, go to Product Manuals.
7.1 Sybase EBFs and software updates
Finding the latest information on EBFs and software updates
Point your web browser to the Sybase Support Page.
Select EBFs/Updates. Enter user name and password information, if prompted (for existing web accounts) or create a new account (a free service).
Select a product.
Specify a time frame and click Go.
Click the Info icon to display the EBF/Update report, or click the product description to download the software.
Creating a personalized view of the Sybase web site (including support pages)
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase web pages.
Point your web browser to Technical Documents.
Click MySybase and create a MySybase profile.