A customer has a procedure that can be called via Embedded Procedure Gateway (EPG and orawsv) like this http://192.168.50.7:8080/scan/scan_menu?p_mi_id=104888 ("scan" is the DAD) and I can call the very same procedure via ORDS http://192.168.50.7:19090/ords/ww2b_scan/scan_menu?p_mi_id=104888
It was coded a long time ago but how was it done ? (DB is 12.1)
How can I publish a non-JSON, non-REST procedure that generates nice webpages (using htp, htf, owa) in ORDS? No schema and no module is ORDS enabled, for the life of me I can't say how it's done.
A customer has a procedure that can be called via Embedded Procedure Gateway (EPG and orawsv) like this http://192.168.50.7:8080/scan/scan_menu?p_mi_id=104888 ("scan" is the DAD) and I can call the very same procedure via ORDS http://192.168.50.7:19090/ords/ww2b_scan/scan_menu?p_mi_id=104888
It was coded a long time ago but how was it done ? (DB is 12.1)
How can I publish a non-JSON, non-REST procedure that generates nice webpages (using htp, htf, owa) in ORDS? No schema and no module is ORDS enabled, for the life of me I can't say how it's done.
What you're looking for is called a "pl/sql gateway". The "old" way of serving pl/sql procedures via a web interface was called "mod_plsql". There is a section in the ORDS documentation on how to migrate from mod_plsql to ORDS.