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
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
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.
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
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.
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:
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.
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
7.1 Sybase EBFs and software updates
Finding the latest information on EBFs and software updates
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.