6 Deploying the IHE Profiles Application

This chapter provides procedures on how to deploy the IHE Profiles Application to the GlassFish application server and how to run HL7 v2 and HL7 v3 sample data through the IHE Profiles Application.

This chapter includes the following section:

• "Deploying an IHE Profiles Application"

• "Running Data Through the IHE Profiles Application"

Deploying an IHE Profiles Application

Deploying an IHE Profiles Application project to a GlassFish application server through the server's web Admin Console. This starts the IHE service.

To Deploy an EAR File from an Admin Console

1. From left panel of the NetBeans IDE, right-click an IHE Profiles Application project. from the Actions Menu,

   The IHE Project Actions menu appears.

2. Click Clean and Build.

3. Start GlassFish.

   The Admin Console appears.

4. In the left panel, choose Applications, select Enterprise Applications, and then click Deploy under Deployed Enterprise Applications in the right panel.

5. Browse to the EAR file of your project, select it, and click OK.

To Deploy an EAR File from the Command Line

1. From the Project Explorer of the NetBeans IDE, right-click an IHE Profiles Application project,

   The IHE Project Actions menu appears.

2. Click Clean and Build.

3. Open the command prompt.

4. Navigate to the <app_server>/bin directory.

5. Run asadmin deploy <directory_path_to>/IHEMPI.ear.

Running Data Through the IHE Profiles Application

Oracle provides both HL7 v2 and HL7 v3 sample data for you to run through the PIX/PDQ system to help you get started with the applications. To enter the HL7 v2 sample messages, you need an HL7 simulator. There are several available on the internet. The HL7 v3 data is provided in the form of test cases that are run from the soapUI project.

The sample data illustrates several scenarios for data processing. You add new records, update existing records, cause assumed matches in the Master Person Index, perform PIX queries for associated local identifiers, perform demographic queries, and perform merges. The data was designed to be run in a specific order to get the expected results from PIX and PDQ queries.

Before you can run these tests, you need to run a database script to add system information to the midm database, as described below. Without this data, the sample tests will fail.

Note:

You can modify the HL7 v2 sample files and the HL7 v3 test input files to insert additional records into the master person index database. If you modify the HL7 v2 sample files, be sure to use an editor that does not automatically convert \r to \r\n, such as UltraEdit.

Use the steps in the following procedures to add the required systems to the database, and then to run HL7 V2 and V3 data.

To Add Required Systems to the Database

1. Navigate to the location where you installed OHMPI, and then to samples\databasescripts\<database_type>.

2. Log into the mpi database from a SQL prompt or editor as the mpi user.

3. Run the clean_ihe_ohmpi_sample_data.sql file against the database.

4. Run the create_ihe_ohmpi_sample_data.sql file against the database.

To Run HL7 V2 Sample Data

Before you begin, make sure that your application server is running, your OHMPI IHE enterprise application is configured and deployed correctly, your HL7 V2 service lifecycle model is deployed and started correctly, your HL7 v2 client simulator is configured and starts correctly. You can use any HL7 v2 compliant client to send and receive HL7 v2.5 and v2.3.1 sample data. Configuring the HL7 v2 client simulator is specific to the type of the simulator you choose. Generally, you should only need to configure its environment to use HL7 v2 listening URL, which is defined in the oracle.hsgbu.ohmpi.ihe.hl7v2.url property for the OHMPI IHE HL7 V2 lifecycle module (by default hl7://localhost:4447), or in the hl7service.xml configuration file.

Note:

Each group of sample data files has a readme file that you should review to learn how each sample data file should be processed and what expected results should be.

1. Navigate to the OHMPI installation directory and then to samples\hl7v2.

   This folder contains a complete set of HL7 v2 sample data files. It also contains subdirectories that each contains a use case. A use case contains a subset of data files that perform specific functions. It contains database scripts for preparing the database to run HL7 v2 sample data. A readme file in the use case directory explains what the use case is and how to run sample data files and the expected results.

2. To process additional records into the system, first backup your sample data files and modify the message data as needed, then use the HL7 v2 simulator to complete the procedure.

3. After processing sample data files from a use case, you can:

   • View the response message or the acknowledge message.

   • Review records from an OHMPI master person index using the Master Index Data Manager (MIDM).

   • Review audit records and message tracing, content, and extensions.

To Run HL7 V3 Sample Data

Under the samples\hl7v3 directory of your OHMPI installation, there is a soapUI sample project that you can use to test your PIXv3 and PDQv3 web services. A readme file explains the test case scenarios.

Before you begin, make sure the application server is running, your OHMPI IHE Profile Application has been deployed, and soapUI has been installed properly.

Note:

To install soapUI, go to http://soapui.org, click the Download Free Open Source button, download the latest version (currently 3.6.1) for your platform (for example, soapui-3.6.1-windows-bin.zip). Unzip the zip file after downloading it.

For best results, run the tests in the order they are displayed in the project. This will show you a full spectrum of PIX v3/PDQ v3 processing. If the tests are run out of order additional errors will occur because the response from the Master Person Index will be different.

1. Adjust web service URLs in the sample soapUI project if necessary.

   The soapUI sample project provided is based on an IHE Profile Application deployed on GlassFish with default configuration, that is, the PIX Manager v3 and PDQ Supplier v3 web services are assumed to be running at http://localhost:8080/PIXManager_Service/PIXManager and http://localhost:8080/PDQSupplier_Service/PDQSupplier, respectively. If your IHE Profile Application is running on a different host or a different port on GlassFish, or if your application is running on WebLogic, then you need to adjust the above two URLs in the soapUI sample project accordingly. To adjust the URLs, open the samples\hl7v3\pixpdqv3-samples-soapui-project.xml in your favorite editor, replace all instances of the above two URLs based on the following instructions:

   • For Glassfish, the web service URLs should be in the following format:

     • http://<host_name>:<port_number>/PIXManager_Service/PIXManager

     • http://<host_name>:<port_number>/PDQSupplier_Service/PDQSupplier

   • For WebLogic, the web service URLs should be in the following format: (the default port number on WebLogic is 7001) :

     • http://<host_name>:<port_number>/PIXManager_Soap12/PIXManager_Service

     • http://<host_name>:<port_number>/PDQSupplier_Soap12/PDQSupplier_Service

2. To start soapUI, go to the ${SOAPUI_HOME}\bin directory and invoke soapui.bat.

3. To import the PIXV3/PDQV3 soapUI project, click File, select Import Project, and then select pixpdqv3-samples-soapui-project.xml from the samples\hl7v3 directory.

4. Expand the PIX and PDQ v3 Samples node in the project tree.

5. Double click the TestSuite-PIXv3 or TestSuite-PDQv3 node to show the Test Suite Editor.

6. Click the Run button to run all the test cases in the test suite.

7. After running a test suite, you can:

   • Check whether the tests passed or failed within soapUI.

   • Review records using the Master Index Data Manager (MIDM).

   • Review audit records and message tracing.