1 / 5

PoC Dynamic Discovery

PoC Dynamic Discovery. BDXR, 2013-05-13. Agenda. Objectives Better understand four corner requirements and candidate technical solutions Metadata location: BDX metadata service location Metadata formats: Busdox SMP 1.0 CPP 3.0 ebMS 3.0 processing modes

aida
Download Presentation

PoC Dynamic Discovery

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. PoC Dynamic Discovery BDXR, 2013-05-13

  2. Agenda • Objectives • Better understand four corner requirements and candidate technical solutions • Metadata location: • BDX metadata service location • Metadata formats: • Busdox SMP 1.0 • CPP 3.0 • ebMS 3.0 processing modes • Holodeck PMode XML file format

  3. Use Cases / Requirements • Determine if a party is a participant in a community • Determine the business / technical capabilities of an entity • Determine if two entities have matching business / technical capabilities • Determine the gateway and configuration an end entity uses to receive or send messages of some type • Determine if two entities c1/c4 are connected via matching intermediaries c2/c3 • Match a metadata record to a cached processing mode • Dynamically generate a processing mode

  4. PoC Components • Metadata Location Service • Twisted Names • Metadata Publication Service • Twisted Web serving metadata XML documents • Scripts using a Discovery Library • Metadata client class (bdxr.py) • Connect client = metadata+format specific processing (connect.py) • Awareness of locally configured processing modes (holodeck.py) • Busdox specific code (smp.py) • ebXML CPP specific code (cpp.py) • ebMS 3.0 configuration (pmode)

  5. Scripts • test_show_metadata_{smp/cpp}.py • Retrieve and display metadata for a party in SMP or CPP format • test_business_match.py • Given two end entities, determines complementary business capabilities • test_connect_smp.py • Retrieve information for an end entity receiver and match against a locally configured PMode • test_connect_cpp_match.py • Retrieve information for sender and receiver end entities, sender and receiver gateways and match agains a locally configured PMode • test_connect_cpp_nomatch.py • As previous, no matching PMode, partial dynamic match (including messaging and security configuration)

More Related