A customer uses this to get a certain report:
l\_report := apex\_util.get\_print\_document
( p\_report\_data => dbms\_xmlgen.convert(l\_report\_data.getclobval(), gc\_entity\_decode) -- clob
, p\_report\_layout => l\_report\_layout -- clob
, p\_report\_layout\_type => lower(l\_tpe\_extensie) -- varchar2 default 'xsl-fo'
, p\_document\_format => lower(l\_ovb\_extensie) -- varchar2 default 'pdf'
, p\_print\_server => bbs\_constanten.gc\_bip\_print\_server -- varchar2 default null
);
bbs_constanten.gc_bip_print_server resolves to an (for years unchanged) url in the format:
http://<dns-name for bi-server>:8080/xmlpserver/convert
After the upgrade to 24.2 this fails with an ACL error => access denied.
We figured out that instead of connecting to server in the provided url, the code uses the apex instance parameters
PRINT_SVR_HOST
PRINT_SVR_PORT
PRINT_SVR_PROTOCOL
PRINT_SVR_SCRIPT
The PRINT_SRV_HOST was pointing to another bi-server, not having an ACL off course…
After adding the ACL for APEX_240200 for http to the server mentioned in PRINT_SVR_HOST the problem was “worked around”.
Changing the parameter PRINT_SVR_HOST to the correct b-server is the solution here.
We can not find any explanation for this obviously changed behaviour….
Anybody who can explain this or point us to documentation/note/… that explains this?