Installation Overview

The Sun GlassFish ESB Healthcare Pack is installed on top of an existing GlassFish ESB v2.2 environment. The installer automates several configuration tasks for the PIX/PDQ solution, such as creating database tables, creating the connection pools and JDBC resources, defining security, and so on.

The Healthcare Pack Installer allows you to customize your installation. You can install the full healthcare solution, just Sun Master Index, just the HL7 Binding Component (BC), or both Sun Master Index and the HL7 BC. In order to use the PIX/PDQ solution in the healthcare pack, both Sun Master Index and the HL7 BC need to be included in the installation.

Installation Process

When you install the complete Healthcare Pack, the installation wizard performs several tasks automatically, including the following:

• Creates the databases and users in your MySQL 5.1 environment.

• Creates the JDBC connection pools and data resources in the GlassFish domain.

• Creates JMS resources for the Master Index JMS topic.

• Creates application variables and configurations.

• Creates user profiles in the GlassFish security file realm for web-based PIX/PDQ applications.

• Builds and deploys the PIX/PDQ projects.

You can configure the installer not to perform these tasks or to only perform a subset of these tasks. If you opt to have the installer build and deploy the PIX/PDQ projects, several JBI components are started when you start the GlassFish server. These components include the BPEL Service Engine, HL7 Binding Component, HTTP Binding Component, and JMS Binding Component.

Important Installation Notes

By default, the Healthcare Pack Installer checks whether any of the artifacts listed above exists, and makes modifications to the MySQL installation or to the runtime environment based on whether they are found. If the artifacts already exist, the installer updates your environment as follows:

• If a database schema named midm or arrdb exists in MySQL, it is dropped and replaced.

• If a database user named mdm or arr exists in MySQL, it is dropped and replaced.

• If a connection pool named cpPatientXA, cpPatientSequenceXA, or MyArrdbPool exists, the installer will not create the new connections pool nor will it update the existing one. The same goes for their corresponding JDBC resources.

• If a JMS destination named PatientTopic, tHL7V3, tHL7V2, tSUNXDS, or tXDSMerge exist, the installer will not create the new destination nor will it update the existing one. The same goes for their corresponding JMS resources.

• If a user named mdm, atna, or pixadmin exist in the GlassFish file realm, the user is updated by the installer.