BLAZON push.aspx and notificationurl call after OCR/Conversion complete..

We submitted the OCR request using push.apsx and gave notificationurl like below. We would like to know, where to capture the results from notificationurl like documented in BLAZON Enterprise SDK? (notificationurl=http://someotherserver:9999&
threadid=f2dcccda-b773-4a89-a579-d0837ef707395&
type=drw&
jobid=1283039571341035583&
starttime=7/31/2017 3:48:33 PM&
filename=AIRPLANE.DWG&
tempdir=C:…\JobProcessor\tempdir\670fa231&
ext=DWG&
targetfile= C:…\JobProcessor\tempdir\670fa231\AIRPLANE.pdf&
endtime=7/31/2017 3:48:33 PM&
totaltime=00:00:00.9260270&
mainfile=AIRPLANE.pdf&
publishername=JPName)

http://w003ffn0c.ams.bnymellon.net:8090/QueueServer/push.aspx?source=\\w003ffn0c\test\RajInput\4064035.tif&

target=\\w003ffn0c\test\RajOutput\OCRd&

outputformat=pdf&DoOCR=True&notificationurl=http://localhost:9999

Find more posts tagged with

Comments

Thankaraj Udhayasuriyan

Any Input on this?

Dominic_Fulginiti

Thankaraj,

I am not entirely sure I understand your question. The goal of any integration using push.aspx is to send a job for conversion. This will take some time and in order to be asynchronous, we provide a parameter for notification URL so that the integrator may capture the job completion and know the job is done and to grab the files.

For example, if you are integrating into a document repository that stores things internally as objects, typically the integration code will call push.aspx, say to make a PDF rendition of a Word doc, and specify a unique URL for call back, such that when the job is done your integration code will catch that call back at it's own HTTP endpoint and given unique job information in the URL can then do the further processing to finish the job (e.g. grab the resulting PDF and place into the document repository as a new object or version of an object).

It is up to the integrator to determine how to handle these notification URL requests as best fit in their application model. Note as well that in any given deployment, any network communication considerations (e.g. firewall policies, etc.) must be handled correctly to allow the bi-directional communication between the servers.

Regards,

Dominic

Thankaraj Udhayasuriyan

Hi Dominic

Yes, we have specified our endpoint in the notificationurl, but once the job is processed, it is not calling back the endpoint. That is the issue...

Rajender