PHINMS Quick Tips

Public Health Information Network Messaging System (PHINMS) Quick Steps provide an easy reference for frequently-requested information on PHINMS. The Quick Steps refer to Release 3.1. Suggestions for additional Quick Steps can be sent to the PHINMS Web Site point-of-contact available via the Support link.

PHINMS Software Request

Contact to request a copy of PHINMS 3.1 application installation packages.

1. PHINMS System Requirements

PHINMS 3.1 has been tested on the following operating systems with 32- or 64-bit version of Java installed:

  • Windows 2008 Server (Standard or Enterprise) SP2; and
  • Windows 7.

The system requirements for using PHINMS are as follows:

  1. 4GB hard disk space,
  2. 2GB memory,
  3. Windows 2003, XP, 2008, and up Solaris Sparc 10.3 or up, or Red Hat Linux 5.0 and up operating system,
  4. local administrator privileges, and
  5. system administrator privileges on Solaris or Linux.

Some versions are not backwards compatible. Additional factors will need to be considered such as what version the Sender is using versus the Receiver and vice versa. Contact the PHIN Help Desk  for more information.

 Top of Page

2. PHINMS Software Request

 Top of Page

3. PHINMS New Installs

The Installation Wizard guides the user through the base installation of the PHINMS Sender and/or Receiver. It is the responsibility of the administrator to configure routes and database connections after completing the installation. The following major components are installed with the wizard

  1. Tomcat 8 server
  2. JDK 1.7.0 Update 79 (1.7.0_79-b15)
  3. PHINMS 3.1 Receiver and Sender web applications
  4. PHINMS 3.1 default configuration files and directory structure
  5. Shortcut to PHINMS 3.1 console on user specific desktop
  6. Default databases
    • Windows: HSQLDB engine
    • Solaris and Linux: HSQLDB engine

When “Install as service” is selected on Windows platform, Tomcat  8.5.11 will be installed in the Windows services panel with the display name of “PHINMS Tomcat Instance” and HSQLDB with “PHINMS Database Engine Service”.

 Top of Page

4. Compatible Products

PHINMS 3.1 has been tested on the following operating systems, databases, application servers, Sender proxy servers and Receiver proxy servers:

  1. Operating systems:
    • Windows 2003 Server (Standard and Enterprise) SP2
    • Windows XP Pro SP2
    • Sun Solaris 10 Update 3
    • Red Hat Enterprise Linux ES release 4, Kernel version 2.6.9-42.0.8.ELsmp
  2. Certified Default Database:
    • HSQL DB – used for testing purposes
    • MS Access
  3. Production Qualified Databases:
    • Microsoft SQL Server 2000, SQL Server 2005, SQL Server 2008
    • Oracle 10g release 2, 9i Release 2
    • MySQL 4.1, 5.0
  4. Application Servers:
    • Tomcat 5.11Web logic Server 10.3.6
  5. Sender Side Proxy servers:
    • Netscape Proxy server 3.6 SP1 to SP6
    • Squid 2.6 Stable 4
  6. Receiver Side Proxy Servers:
    • Netscape Proxy server 3.6 SP1 to SP6
    • IIS 7.5.76 with Web logic 10.3.6 plug-in
    • IIS 6.0 with Jakarta Tomcat Connector 1.2.15
    • Novell iChain 2.3.3 reverse proxy server

PHINMS has tested certain JDBC drivers to connect to the supported databases and found no issues based on the tests performed. PHINMS does not guarantee nor support the JDBC driver versions shown in the table below. It is the responsibility of the PHINMS customer to decide which JDBC driver to use. The table is provided for reference purposes only.

DB Server Type DB Version JDBC Driver Name Type Version Date Published
MS SQL 2005 sqljdbc.jar
1.2.2828 8/10/2016
Oracle 10g Rel 2 classes12.jar 1/22/2006
Oracle 9i Rel 2 ojdbc6.jar
MySQL 4.1, 5.0 mysql-connector-java-5.0.4-bin.jar

 Top of Page

5. Obtain a CDC Party ID

Regardless of the PHINMS version installed, a CDC PartyID is required. A PartyID is required for each instance of PHINMS or each installation of PHINMS. A PartyID uniquely identifies a PHINMS installation, also known as an instance or node, in the Public Health Information Network (PHIN). The PHINMS installation transmits the PartyID along with every message which notifies the recipient of the origin of the message. A PartyID will resemble “2.16.840.1.114222.”.

Send a completed PHINMS Software Request for each PHINMS installation to obtain a PartyID from the PHIN Help Desk Save the PartyID until the initiation of the PHINMS installation. The PartyID will be permanently stored once entered into the PHINMS Installation wizard.

 Top of Page

6. Obtain a User ID and Password

Once Step 2 is complete, the PHIN Help Desk will need to be contacted to obtain the User ID, password, and the FTP site used to download the PHINMS software.

 Top of Page


7. Install PHINMS Software

The installation steps are located in the PHINMS Implementation Guides. Refer to one of the following release specific guides:

 Top of Page


8. Obtain a Digital Certificate

A Digital Certificate issued by Verisign through the CDC’s Secure Data Network is required when sending messages to the CDC. A CDC’s Digital Certificate will only be provided to partners sending data to the CDC. When a messaging partner sends data to organizations other than the CDC, a Digital Certificate will need to be acquired from a third-party vendor.

 Top of Page

9. PHINMS Configuration

The PHINMS Implementation Guides provides basic configuration instructions to successfully use PHINMS.

 Top of Page

10. Restart vs. Refresh PHINMS

When PHINMS configuration files have been changed or a new component has been added, the PHINMS Tomcat service will need to be restarted for the changes to take effect. This can be done in Services located in the Administrative Tools folder. When adding data to the database, using the refresh button on the console will suffice.

 Top of Page

11. PHINMS Installation Verification Test

PHINMS has two components, the Sender and the Receiver. Sending a Ping message from the Sender to the Receiver ensures both the PHINMS Sender and Receiver components are working properly. Complete the installation test by referring to one of the following release specific guides:

 Top of Page

12. CDC Connectivity Test

The CDC Connectivity Test is used to verify messages can be sent directly to the CDC or to use the CDC as an intermediary server (Route-not-Read). This test ensures the PHINMS Sender is able to send an outbound Ping message to a PHINMS Receiver hosted at the CDC and the CDC’s Receiver successfully receives the message. Complete the CDC Connectivity test by referring to one of the following release specific guides:

 Top of Page

13. Create Route Map

A Route Map is used to send messages to specific recipients. The Route Map stores the recipient’s attributes, such as the URL, transport protocol, and authentication type. Create a Route Map by referring to one of the following release specific guides:

 Top of Page


14. Transport Queue Configuration

The Sender uses a Transport Queue (TransportQ) is a relational database table interfacing between the application creating the message and PHINMS which stores the meta-base information and data to be sent. The Sender polls the TransportQ for messages. PHINMS is packaged with a database; however, a different database can be configured for the TransportQ. Use the applicable Implementation Guide pertaining to the version which documents the steps to configure a TransportQ. The Implementation Guide is located on the Installation tab.

 Top of Page


15. Worker Queue Configuration

The Receiver uses a Worker Queue (WorkerQ) to store incoming messages in a database table. The WorkerQ is configured from the Receiver configuration screens located in the console. The 3.1 release comes bundled with HSQL but can be configured using other databases. Use the applicable Implementation Guide pertaining to the version which documents the steps to configure a WorkerQ. The Implementation Guides are located on the Installation tab.

See Page 54

 Top of Page


16. Service Map for the Worker Queue Configuration

Each message has an envelope with addressing information tags referred to as a Service and Action pair. They are character strings logically mapped to a Worker Queue (asynchronous messaging). The service and action pair determines the location of the delivery. The Service Map and the Worker Queue are configured on the Receiver. Refer to Step 14. The Service Map also includes the type of Message Handler which is Servlet, Worker Queue, and Error Queue.

 Top of Page


17. Digital Certificate Configuration

Instructions are in the PHINMS 3.1 Implementation Guidepdf icon for importing and exporting the Digital Certificate.

See Page 13

 Top of Page


18. PHINMS Upgrade

Instructions are located in the PHINMS 3.1 Implementation Guidepdf icon for upgrading PHINMS using the correlating version.

See Page 25

 Top of Page

Page last reviewed: December 2, 2019