Xdr test 11

[H S]

Hello, 

We are running Xdr Test 11 from ... We are noticing that we are not able to convert the data into zip file as content is empty. Because of this, we are unable to convert it into Xdr with Limited Metadata. Can you please let us know whether this is expected behavior?

Attached Screenshot and logs for reference. 

Regards,

Harini Sudhagar

[Sai Valluripalli]

Hi,

This issue is resolved now. Please try again. You should be seeing non-empty zip file.

Thanks

[Vijetha Nayak]

Hi Team,

The zip file issue is resolved but the request that comes in from ETT has the below slot 

<Slot name="repositoryUniqueId">
<ValueList>
<Value>65314142.0519.4144.9062.8873831131</Value>
</ValueList>
</Slot>

Is this mandatory slot  repositoryUniqueId as this value present is not supported and fails with the below err 

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"><S:Header><wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope" s:mustUnderstand="1">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse</wsa:Action><wsa:RelatesTo xmlns:wsa="http://www.w3.org/2005/08/addressing">6bfd882c-990c-40c5-bc24-c9d5cc751d42</wsa:RelatesTo></S:Header><S:Body><rs:RegistryResponse xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure"><rs:RegistryErrorList><rs:RegistryError codeContext="Slot repositoryUniqueId: 65314142.0519.4144.9062.8873831131 is not in OID format" errorCode="XDSRegistryMetadataError" location="OidFormat" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error" /></rs:RegistryErrorList></rs:RegistryResponse></S:Body></S:Envelope>

Could you please confirm if the value present for this slot is correct or can we remove this slot and process the request? 

Regards,

Vijetha

[Sai Valluripalli]

The ETT will only send a direct message with XDM ZIP attached to SUT. You have to convert the XDM to XDR and send it back to the ETT endpoint. The XDR MUST be valid to pass this test.

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/f78f7687-765f-411b-a5d6-161459a2b97cn%40googlegroups.com.

[Cibi Krishnan]

Team, need bit more information, is this value coming from the ETT tool itself? the SUT just forwards it to the endpoint, correct?

<Slot name="repositoryUniqueId">
<ValueList>
<Value>65314142.0519.4144.9062.8873831131</Value>
</ValueList>
</Slot>

[H S]

Please clarify the following: 

Question 1:
Is the repositoryUniqueId transmitted from the ETT tool in the appropriate format?

 
<Slot name="repositoryUniqueId">
<ValueList>
<Value>65314142.0519.4144.9062.8873831131</Value>
</ValueList>
</Slot>

If we send the slot, we are getting the following error: 65314142.0519.4144.9062.8873831131 is not in OID format
 
Question 2:
If the answer is ‘Yes’, what is the format (this does not seem to be valid oid, uuid or guid)? And is it necessary to convert it into an OID?
 
Question 3:
<Value>65314142.0519.4144.9062.8873831131</Value>
 
We transformed the periods (.) into hyphens (-) to form a GUID, and then converted that GUID (65314142-0519-4144-9062-8873831131) into the following OID: 2.25.134507773707605629430307298441093648689. When we send this as value for  repositoryUniqueId, we do not get any error message. Is this the type of conversion we were aiming for?

[Cibi Krishnan]

Team,

Can you please review the previous email and respond.

Thanks,

Cibi Krishnan

[Cibi Krishnan]

Please review the clarifications on priority as we are closing in on the deadline.

Thanks,

Cibi Krishnan

[Cibi Krishnan]

Hello Team,

Please help here,

Thanks,

Cibi Krishnan

Sent from my iPhone

On 22 May 2024, at 9:00 AM, Cibi Krishnan <cibikr...@gmail.com> wrote:

Please review the clarifications on priority as we are closing in on the deadline.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/075528fc-f46b-450a-a228-cd464bb3b4b8n%40googlegroups.com.

[Sai Valluripalli]

Yes, you can convert to a valid OID and send it back. You will pas the test as long as the Direct To Address entered on the tool will match the Direct To in what is being sent back to the tool as SOAP XDR header.