- This topic has 7 replies, 5 voices, and was last updated 7 years, 7 months ago by
.
-
Topic
-
-
Replies
-
-
-
Something appears to be lost in the decode process from base-64 to pdf, can someone determine if I am doing this correctly?
Win 2003 Server SP2
CL 5.7 R2
See attachment for inbound message in .msg file.
See attachments for what pdf should look like and what it does look like?
proc code:
package require base64
foreach segment $segments {
if {[cequal [crange $segment 0 2] “OBX”]} {
set obx_fields [split $segment $field_delim]
set list_size [llength $obx_fields]
while { $list_size < 6 } {
lappend obx_fields “”
set list_size [llength $obx_fields]
}
set obx_5_fields [split [lindex $obx_fields 5] $comp_delim]
set list_size [llength $obx_5_fields]
while { $list_size < 5 } {
lappend obx_5_fields “”
set list_size [llength $obx_5_fields]
}
set pdf_data [base64::decode [lindex $obx_5_fields 4]]
break
}
}
set PDFFileName [cconcat $HciProcessesDir “/” $myprocessName “/que_pdf_data/CentralLogic_Test.pdf”]
if { [catch {set outfile [open $PDFFileName w]} cerr] } {
puts [cconcat “–> WARNING: Error Creating ” $PDFFileName ” File – ” $cerr “r”]
} else {
puts $outfile $pdf_data
close $outfile
}
-
James,
First are you positive the inbound message has that fiel base-64 encoded?
If this is done following the HL/7 standard OBX-2 should have the proper data type (I think that is ED) and then OBX-5 should have the proper structure which includes a component that tells you the encoding technique deployed.
But even if the standard is not literally followed (not surprising), you need to make sure the data is actually base-64 encoded. Otherwise it most certainly could contain one or moer of the characters specified in MSH-1 and MSH-2 causing your parsing to fail and possibly not giving you all of the data you want.
The Base64 package will attempt to decode whatever you give it even if it is not Base64 encoded.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
-
I have a hard time with the code but if you are writing it to a file and it is indeed a PDF document you have to change translation type to binary
set PDFFileName [cconcat $HciProcessesDir “/” $myprocessName “/que_pdf_data/CentralLogic_Test.pdf”]
Better stated as [file join $HciProcessesDir
que_pdf_data CentralLogic_Test.pdf]
# w+ will reate file if it does not exist
if { [catch {open $PDFFileName w+} outfile]} {
echo –> WARNING: Error Creating $PDFFileNamenFile – $outfilen
—- May need an error return here
} else {
fconfigure $outfile -translation binary
puts $outfile $pdf_data
close $outfile
}
The looping to get segment data is not very ergonomic. Take a look at the lsearch command
-
Right on! I added the “w+” and “fconfigure” and now receive readable output. Also, thank you for the code tidbits.
Being my first time doing this, on the PDF view, I see there is an “X” in the top box, supposedly our logo. Is that not supposed to be embedded or do we need a seperate file? Probably need to discuss with vendor?
See attached new output…
-
-
- The forum ‘General’ is closed to new topics and replies.
