CONNECT Installation
and Configuration
Assumptions/Expectations
Familiarity with…
•
Java
•
Service Oriented
Architecture (SOA)
•
NetBeans
•
GlassFishESB
CONNECT 2.0 Installation Options
Windows
Based Install
Windows based install– Preconfigured GlassFish Binary Install – Full Binary Install
– Source Code Install
Solaris Install
Full Binary InstallSite URL: http://www.connectopensource.org/display/NHINR2/Release+2.0+Home This session’s
CONNECT Site:
Items to Download for
Source Code Install
• Source Code Implementation and Administration Guide
– Gives step-by-step instructions for installing, configuring, and building CONNECT 2.0 – NHIN_CONNECT_Release_2_0_A038_A039_A040_System_Implementation_Admin
istration_Source_Code_March_31_2009.pdf
• NHIN CONNECT Source – NHIN CONNECT Source tree
– NHIN_Connect_Source_2.0_04012009.zip
• Third Party Tools
– Software applications needed for CONNECT
– NHIN_Connect_Third_Party_Tools_2.0_04012009.zip
• Third Party Components
– Libraries and components needed by CONNECT
Hardware Requirements
Two Computers
• GatewayEach Computer
• CPU: 2GHz or better • RAM: 4 GB min• Hard Disk Size: Based on deployment configuration
• Hard Disk Speed: Preferred: 10,000 RPM, Minimum:
7,200 RPM
• Network Interface: Preferred: 1 GB, Minimum: 100 MB
Software Requirements
•
Windows XP or higher
•
Java SDK 1.6, Update 11, Build 3
•
GlassFishESB version 2.0, Nightly Build: 20090201
•
Metro version 1.4
•
MySQL version 5.0
Installation of Gateway and Adapter
• Most of the installation steps are the same
• Gateway and Adapter have a
different set of deployed services
• File locations should not be
changed from the install directions
• Environment variables are set where appropriate in the
Basic Installation Steps
•
Download necessary files from CONNECT site
•
Unzip files to C:\
•
Install JDK
•
Install GlassFishESB
•
Update NetBeans ant with additional libraries
•
Install Metro 1.4
•
Set up certificates
•
Update domain.xml configuration file
•
Install third party components
Basic Installation Steps (cont.)
•
Update HTTP binding component application variables
•
Install MySQL
•
Create CONNECT database, schemas, and tables
•
Install SoapUI
•
Compile NHIN CONNECT source
•
Update property/configuration file settings
•
Deploy NHIN CONNECT components
Demonstrations Divided into Steps
Using a set of preconfigured virtual machines
Configured to different stages of the install process
Demonstrations focused on more complex instructions
Demonstration Part 1
Steps Completed Previously
– Download necessary files from CONNECT site (§3)
– Unzip files to C:\ (§4.1)
– Install JDK (§4.2.1)
– Install GlassFishESB (§4.2.2)
– Update NetBeans ant with additional libraries (§4.2.3)
Steps Shown in Demonstration
– Install Metro 1.4 (§4.2.4)
– Set up certificates (§4.2.5)
– Update domain.xml
configuration file (§4.2.6)
– Install third party components (§4.2.7)
– Update HTTP binding component application variables (§4.2.8)
Source Code Directory Structure
Directory Description
C:\projects\NHINC\Current\Product
Contains master ant script that compiles the CONNECT
gateway and adapter
C:\projects\NHINC\Current\Product\Production
This project will contain sub folders that separate the code by its primary location (i.e. Common, Gateway, Adapter) C:\projects\NHINC\Current\Product\Production\Adapter CONNECT adapter source C:\projects\NHINC\Current\Product\Production\Common Source used by both gateway and adapter C:\projects\NHINC\Current\Product\Production\Gateway CONNECT gateway source C:\projects\NHINC\Current\ThirdParty Contains third party libraries needed to compile
Project Naming Conventions
Projects Ending In… Type of Project
EJB or Ejb Enterprise java bean
Lib Java library
CA OpenESB composite application
DAO Data Access
(Note some data access objects are defined as Lib)
BPEL BPEL source code
Special Projects
Project/Directory Purpose
Common\Interfaces Contains all of the WSDL and schemas that are
being used within CONNECT
Common\Properties Contains property files and configuration files
Known Third Party Component Issue
•
On library copy step DO NOT copy the following libraries
to C:\GlassFishESB\glassfish\lib
– xalan-2.7.0.jar
– xercesImpl-2.8.1.jar
– xml-apis-1.3.0.4.jar
– xstream-distribution-1.3-bin.zip
•
Issue/Solution has been posted to forum
•
If these are copied, the following error will occur at
run-time
– “org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.”
Demonstration Part 2
Steps Completed Previously
Demonstration 1 steps
Install MySQL (
§4.2.9)
Steps Shown in Demonstration
Create CONNECT database, schemas, and tables
(
§4.2.10)
Steps Completed Previously
Demonstration Part 1 and Part 2 Steps
Install SoapUI (
§4.2.11)Steps Shown in Demonstration
Compile NHIN CONNECT Source
Show Command – But will not be waiting for command to finish (§4.3)
Demonstration Part 4
Steps completed previously
Demonstration part 1, 2 and 3 steps
Compile has completed on both adapter and gateway
Steps shown in demonstration
Update property/configuration file settings (
§4.4)
Deploy NHIN CONNECT components (
§4.5)
• Partial – will not take the time to deploy each component during session • CONNECT 2.0 must be deployed using NetBeans IDE and not from the
Binary Installation Differences
• Location of the property/configuration files
– Binary install:
• c:\GlassFishESB\glassfish\domains\domain1\config\nhin
• This directory will need to be created during the installation process
– Source install:
• C:\projects\NHINC\Current\Product\Production\Common\Properties
• NHINC_PROPERTIES_DIR environment variable
– Points to the correct location of property/configuration files
• WSDL and schema files (binary install)
– Place a copy of the WSDL and schema files in:
Binary Installation Differences (cont.)
•
NHIN certificates
– Binary install:
• Uses NHIN generated certificates
• Need to make sure certificates are correctly configured in domain.xml – see section 8.1.1 in the Full Binary
Installation Guide
– Source install:
• Uses developer generated certificates
• Works only for internal gateway testing – it does not work across multiple gateway machines
