| | 1

IEHR SOA SUITE FOR THE VA/DOD FEDERATED

HEALTHCARE ENTERPRISEGETTING ON THE BUS: AN INTRODUCTION TO USING THE GOVERNMENT AND CONTRACTOR SANDBOX

HARRIS HEALTHCARE SOLUTIONS

AUGUST 16, 2012

| | 2

AGENDA

• Introduction• Lab overview

– Admissions– Access Policies– Support

• Local SOA Suite nodes – Mirth Connect• SOA Suite Security – Layer7 Secure Span Gateway• Enterprise SOA Suite – IBM WebSphere Stack

| | 3

INTRODUCTION

• Currently two sandbox systems– Government run at Pacific JITC ITEC– Contractor facility at Harris in Melbourne, FL

• Contains the SOA Suite software including the IBM Stack, Mirth Connect, Layer7 SSG, and CA Introscope

• Can be used to try out the software by developing components or apps and deploying within the sandbox

| | 4

THREE PARALLEL ENVIRONMENTS

| | 5

SANDBOX VCENTER

| | 6

SANDBOX ADMISSIONS

• VA/MHS/Programmatic Contractor completes a Harris provided access request document through a Harris SOA Suite Programmatic sponsor citing access method and associated needs

• Sponsor submits forms through Harris approval systems and approval chains

• Account is build for the requesting user in the Harris Healthcare Solutions Center domain

• Domain credentials (UID/PWD) passed on to the user with instructions on initial access based on method

6

| | 7

Access Methods• Supported access

methods are:– Host based SSL or

IPSEC VPN (client)• IP based direct access to

Sandbox assets or exposed services

– Client based RDP• Access to a Sandbox

desktop containing tools for dev/test

Note: Sandbox request gets a user into the Sandbox space, though other credentialing may occur with the space at the system or services level

7

| | 8

SANDBOX TECHNICAL SUPPORT

• Where experiencing difficulty with access or operation with the sandbox, the user would initiate support with an email to SOAADMIN@harris.com gaining assistance (Tier 1).

– Tier 1 is responsible for access or credentials into the sandbox space – Inbound problems are logged along with the resolution communications assignment chain

• Issues above access or credentials into the sandbox space would be forwarded to SOA Suite Engineering disciplines for resolution (Tier 2).

– Tier 2 is responsible for SOA Suite system, software operations, sandbox credentials and system/service access

– Tier 2 would be responsible for software/hardware vendor engagement as Tier 3 necessary for remediation

| | 9

LOGIN TO YOUR DEVELOPER VM VIA RDP

9

| | 10

TIGHTVNC – GUI ACCESS TO SERVERS

| | 11

ACCESS MIRTH CONNECT ADMIN SCREEN

| | 12

MIRTH DASHBOARD

| | 13

LAYER7 SECURESPANGATEWAY CONSOLE LOGIN

13

| | 14

LAYER7 ADMIN CONSOLE

14

| | 15

IBM TOOLS

• A number of tools are installed to support products such as:

• Message Broker and MQ

• WebSphere Service Registry and Repository (WSRR)

• WebSphere Application Server (WAS)

| | 16

CREATE A WAS PROFILE

| | 17

RATIONAL APPLICATION DEVELOPER

• Eclipse-based tool for developing Java/Java EE, portal, Web 2.0, mobile, OSGi, and SOA applications

• Web and mobile development

• Rapid development and testing: Optimized and integrated support for the latest IBM WebSphere Application server

| | 18

RAD PREFERENCES – ADD A SERVER

| | 19

CREATE A CONNECTOR PROJECT AND DEFINE THE SERVER TO WHICH TO ATTACH THE PROJECT

| | 20

RAD – WAS CONFIGURED

| | 21

RAD – WAS STARTED AND EAR DEPLOYED

| | 22

IBM INTEGRATION DESIGNER (IID)

• Eclipse-based tool for building SOA-based BPM and integration solutions across

– WebSphere Process Server– WebSphere ESB– WebSphere Adapters

• Drag and Drop

| | 23

IBM INTEGRATION DESIGNER – ADD AND CONFIGURE SERVER

| | 24

IBM INTEGRATION DESIGNER – NEW SERVER INSTALLED

| | 25

CREATE A LOCAL MESSAGEBROKER

| | 26

WEBSPHERE MQ EXPLORER

• Eclipse-based tool to remotely configure MQ.

• Start the Prepare WebSphere MQ Wizard and step through it

• Choose defaults

• It will launch MQ Explorer

• Verify the results in MQ Explorer

| | 27

MESSAGE BROKER TOOLKIT