1 / 18

Building an Adapter

Building an Adapter. Session Agenda. Review of CONNECT components Project/source layout Customization of adapter components. Assumptions/Expectations. Familiarity with… Java Service Oriented Architecture (SOA) NetBeans GlassFishESB. Review of CONNECT Components.

Télécharger la présentation

Building an Adapter

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. Building an Adapter

  2. Session Agenda Review of CONNECT components Project/source layout Customization of adapter components

  3. Assumptions/Expectations Familiarity with… Java Service Oriented Architecture (SOA) NetBeans GlassFishESB

  4. Review of CONNECT Components

  5. CONNECT ArchitectureMessages From NHIN

  6. CONNECT ArchitectureMessages to NHIN

  7. Project / Source Layout

  8. Source Code Directory Structure

  9. Project Naming Conventions

  10. Project Creation Guidelines • WIKI page describes the projects • http://developer.connectopensource.org/display/CONNECTWIKI/Project+Creation+Guidelines

  11. Special Projects

  12. Web Service WSDL File Naming Conventions • First part identifies the type of service • Adapter: Services on the adapter • Entity: Services on the gateway which are called by the adapter • Nhinc: Services on the gateway that are internal to the gateway • Nhin: NHIN services hosted or called by the CONNECT gateway • If “component” identified in second part… • NhincComponent: Identifies internal components to the gateway • AdapterComponent: Identifies services on the Adapter Service Bus • Used to customize an adapter service • EntityComponent: Identifies gateway internal services which orchestrate a message • Adapter/Entity interfaces may contain word Secured/Unsecured • Identifies whether the interface represents the secured or unsecured interface • Rest of the name identifies the service • Example • AdapterComponentSecuredMPI.wsdl

  13. XML Schema Layout and Naming Conventions • Directory: Interfaces\src\schemas • First level of hierarchy: identifies organization or type of schemas • schemas\nhinc: CONNECT schemas • schemas\nhinc\common: used in gateway and adapter • schemas\nhinc\gateway: used in gateway • schemas\nhinc\hl7: schemas to combine HL7 messages

  14. Connection Manager • Manages endpoint URLs • NHIN services • Replaceable services • Two points of configuration • UDDI • UDDI Update Manager service • uddiConnectionInfo.xml: CONNECT service information cache • Do not modify this file by hand • Internal • Used to override UDDI settings – settings here take precedence over UDDI • Used for non UDDI supported services • internalConnectionInfo.xml

  15. Example internalConnectionInfo.xml <?xml version="1.0" encoding="UTF-8"?> <InternalConnectionInfos> <internalConnectionInfo> <homeCommunityId>1.1</homeCommunityId> <name>DoD</name> <description>DoD Description</description> <services> <service> <name>subjectdiscovery</name> <description>subjectdiscovery</description> <endpointURL> https://localhost:8181/PIXConsumer_Service/SubjectDiscovery </endpointURL> </service> <service> <name>nhincsubjectdiscovery</name> <description>NHIN-CONNECT Internal Subject Discovery</description> <endpointURL> http://localhost:9080/NhinConnect/NhincSubjectDiscovery </endpointURL> </service> </services> </internalConnectionInfo> </InternalConnectioninfos>

  16. Customization of Adapter Components

  17. Adapter Service Bus Components

  18. Steps for Customizing an Adapter Component Create a Web Service that implements the correct WSDL Deploy the web service Update internalConnectionInfo.xml with the URL for the customized WSDL

More Related