This content has been marked as final. Show 15 replies
Did you attached the document to the Endpoint ?
Yes, I did.
This is the document I followed to create this scenario.
Edited by: 988688 on Feb 19, 2013 12:26 AM
Edited by: 988688 on Feb 19, 2013 12:27 AM
when I try to send the ADTA03_2.3.1_1.txt using the b2bsimulatorMake sure that file is UTF-8 encoded and there are no additional characters in the starting of the file (use any text editor which can show the non-ASCII characters). Most probably problem is with your input payload. You may also check the payload in wire message report.
PID|1||A000010^^^HosA^MR^HosA||Kessel^Abigail||19460101123045|M|||7 South 3rd Circle^^Downham Market^England -Norfolk^30828^UK||||||||A2008090801529\r
PV1|1|I||I|||FUL^Fulde^Gordian^^^^^^^^^^MAIN|||EMR|||||||||V2008090801529^^^^VISIT|||||||||||||||||DISH DISP|disch loc|||||||2008090801529|20080910112956\r
The above is the HL7 V 2.3.1 ADT A03 message I am trying to send. It is the same message that Wire message payload has.
I have also used a sample test message generated from B2B doc editor.
And even tried with other versions of the HL7 message (e.g HL7 V 2.3.1 ADT A01 and ADT A04).
However I try, I am getting the same error. (HC-50083: Document protocol identification error.)
I appreciate the effort you all are trying to help me out on this issue.
Also I am getting the same error even for good/bad payload. "HC-50083 - DOCUMENT PROTOCOL IDENTIFICATION ERROR"
Is it anything to do with this Bug ? (From Oracle Support)
Bug 13833441 : B2B-50083 - DOCUMENT PROTOCOL IDENTIFICATION ERROR
No, it must not be related to that bug. Can you export your repository and send it to me with the test payload? (id in my profile). Will quickly verify it.
Thank you Anuj.
I sent you the email with sub: HC-50083: Document protocol identification error
Tested your configuration with your payload and it works perfectly fine. I tested with both file endpoint and MLLP endpoint(same which is configured in your configuration). I also tested with Michael's HL7 Sender tool and message went through successfully. So for sure it is an environment specific issue.
Can you provide "opatch lsinventory" output from your SOA home? Make sure that you are testing this on 18.104.22.168.0 and you have patch#13357551 applied in your SOA home. Also make sure that you followed post installation instructions of patch#13357551 correctly.
I tested it on Linux X86-64 machine. Which OS are you working with?
Hi Anuj, Thanks for the effort.
I have sent you the opath inventory in the mail 'RE: HC-50083: Oaptch_inventory.txt'.
path#13357551 is applied on SOA home. All the post-installation steps are done. And the testing is on 22.214.171.124.0.
The machine is Windows server 2008 R2, 64bit.
What do you suggest to make it work on my machine ?
Thank you very much
Hello,1 person found this helpful
Your inventory looks good as per the opatch output but it does not prove that post installation steps went successfully. I will suggest to raise a SR with support as without reviewing your system, it may not be possible to figure out the problem point. You seems to be using a certified platform (Windows server 2008 R2, 64bit) so support should accept your request without any issue. You may also refer this thread in your SR.
Thank you Anuj. Looks like I made a mistake running the wrong post-installation step.
Can I re-run the post installation steps with out de-installing or re-applying the patch#13357551 ?
Because, I should run the step 5.1 instead step 5.
5.1 in Readme.txt
ant -f ant-soahc-postinstall.xml updateWin64Library (Win64 Only)
ant -f ant-soahc-postinstall.xml copyauditfiles
Please start the Admin Server and Managed Server(s).
Run the following commands.
ant -f ant-soahc-postinstall.xml deployui
ant -f ant-soahc-postinstall.xml updateparam -Dparam=b2b.InBoundDispatcher -Dvalue=1
ant -f ant-soahc-postinstall.xml updateparam -Dparam=b2b.OutBoundDispatcher -Dvalue=1
Edited by: 988688 on Feb 22, 2013 3:31 AM
Yes, you can. It won't cause any issue.1 person found this helpful
sorry, updated my previous post. I will run those steps and let you know.
Yes, as the readme states -
For AIX64,Win64, Win32 platforms please follow step 5.1 instead of step 5.Regards,