614. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 4/5/2017 4:25:32 PM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

614.1 Files compared

#	Location	File	Last Modified
1	C:\working_scrub\Unredacted\VAP Code Base\VAP_Bld2_Source_Code_CIF_2017-02-14\nvap-ext-svc-proxy\src\main\resources\wsdl	AuditManager.wsdl	Wed Feb 1 18:37:28 2017 UTC
2	eHX-CIF.zip\eHX-CIF\VAP Code Base\VAP_Bld2_Source_Code_CIF_2017-02-14\nvap-ext-svc-proxy\src\main\resources\wsdl	AuditManager.wsdl	Wed Apr 5 12:28:40 2017 UTC

614.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	2	124
Changed	1	2
Inserted	0	0
Removed	0	0

614.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

614.4 Active regular expressions

No regular expressions were active.

614.5 Comparison detail

	1	<?xml vers ion="1.0" encoding=" UTF-8"?>
	2	<!-- Publi shed by JA X-WS RI at http://ja x-ws.dev.j ava.net. R I's versio n is Oracl e JAX-WS 2 .1.5. -->
	3	<definitio ns xmlns=" http://sch emas.xmlso ap.org/wsd l/" xmlns: wsdl="http ://schemas .xmlsoap.o rg/wsdl/" xmlns:xsd= "http://ww w.w3.org/2 001/XMLSch ema" xmlns :tns="urn: gov:va:med :nhin:adap ter:audit" xmlns:ns= "urn:gov:v a:med:nhin :adapter:a udit" xmln s:plnk="ht tp://docs. oasis-open .org/wsbpe l/2.0/plnk type" xmln s:soap="ht tp://schem as.xmlsoap .org/wsdl/ soap/" nam e="AuditMa nager" tar getNamespa ce="urn:go v:va:med:n hin:adapte r:audit">
	4	<t ypes>
	5	<xsd :schema ta rgetNamesp ace="urn:g ov:va:med: nhin:adapt er:audit">
	6	<xsd:i nclude sch emaLocatio n="../sche mas/AuditM anager.xsd "/>
	7	</xs d:schema>
	8	</ types>
	9	<m essage nam e="getAudi tsRequest" >
	10	<par t name="bo dy" elemen t="ns:GetA udits"/>
	11	</ message>
	12	<m essage nam e="getAudi tsResponse ">
	13	<par t name="bo dy" elemen t="ns:GetA uditsRespo nse"/>
	14	</ message>
	15	<m essage nam e="getAudi tsSummaryR equest">
	16	<par t name="bo dy" elemen t="ns:GetA uditsSumma ry"/>
	17	</ message>
	18	<m essage nam e="getAudi tsSummaryR esponse">
	19	<par t name="bo dy" elemen t="ns:GetA uditsSumma ryResponse "/>
	20	</ message>
	21	<p ortType na me="AuditM anagerPort Type">
	22	<ope ration nam e="getAudi ts">
	23	<input name="inp ut1" messa ge="tns:ge tAuditsReq uest"/>
	24	<outpu t name="ou tput1" mes sage="tns: getAuditsR esponse"/>
	25	</op eration>
	26	<ope ration nam e="getAudi tsSummary" >
	27	<input name="inp ut2" messa ge="tns:ge tAuditsSum maryReques t"/>
	28	<outpu t name="ou tput2" mes sage="tns: getAuditsS ummaryResp onse"/>
	29	</op eration>
	30	</ portType>
	31	<b inding nam e="AuditMa nagerBindi ng" type=" tns:AuditM anagerPort Type">
	32	<soa p:binding style="doc ument" tra nsport="ht tp://schem as.xmlsoap .org/soap/ http"/>
	33	<ope ration nam e="getAudi ts">
	34	<soap: operation soapAction ="urn:getA udits"/>
	35	<input name="inp ut1">
	36	<soap:bo dy use="li teral"/>
	37	</inpu t>
	38	<outpu t name="ou tput1">
	39	<soap:bo dy use="li teral"/>
	40	</outp ut>
	41	</op eration>
	42	<ope ration nam e="getAudi tsSummary" >
	43	<soap: operation soapAction ="urn:getA uditsSumma ry"/>
	44	<input name="inp ut2">
	45	<soap:bo dy use="li teral"/>
	46	</inpu t>
	47	<outpu t name="ou tput2">
	48	<soap:bo dy use="li teral"/>
	49	</outp ut>
	50	</op eration>
	51	</ binding>
	52	<s ervice nam e="AuditMa nagerServi ce">
	53	<por t name="Au ditManager Port" bind ing="tns:A uditManage rBinding">
	54	<soap:addr ess locati on="http:/ / ser v er: p o rt /NHINAdapt erAuditMan ager/Audit ManagerSer vice"/>
	55	</po rt>
	56	</ service>
	57	<p lnk:partne rLinkType name="Audi tManager">
	58	<!-- A partner link type is automa tically ge nerated wh en a new p ort type i s added. P artner lin k types ar e used by BPEL proce sses.
	59	In a BPEL process, a partner l ink repres ents the i nteraction between t he BPEL pr ocess and a partner service. E ach partne r link is associated with a pa rtner link type.
	60	A partner link type characteri zes the co nversation al relatio nship betw een two se rvices. Th e partner link type can have o ne or two roles.-->
	61	<pln k:role nam e="AuditMa nagerPortT ypeRole" p ortType="t ns:AuditMa nagerPortT ype"/>
	62	</ plnk:partn erLinkType >
	63	</definiti ons>