1 / 27

iEHR SOA Suite for the VA/DoD Federated Healthcare Enterprise

iEHR SOA Suite for the VA/DoD Federated Healthcare Enterprise. Getting on the bus: An introduction to using the Government and Contractor Sandbox Harris Healthcare Solutions August 16, 2012. Agenda. Introduction Lab overview Admissions Access Policies Support

taipa
Download Presentation

iEHR SOA Suite for the VA/DoD Federated Healthcare Enterprise

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. iEHR SOA Suite for the VA/DoD Federated Healthcare Enterprise Getting 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

  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

  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

  10. TightVNC – GUI access to Servers

  11. Access Mirth Connect Admin Screen

  12. Mirth Dashboard

  13. Layer7 SecureSpanGateway Console Login

  14. Layer7 Admin Console

  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

More Related