I must be missing something. Where in the instructions for REST Data Services does it address PDF Printing via the APEX Listener?
So I tried checked another APEX instance's print parameters that was using the APEX Listener as its print server and changed mine accordingly, but it still isn't working. This is what the values of the parameters were for that other instance:
PRINT_BIB_LICENSE is 'APEX_LISTENER'
PRINT_SVR_PROTOCOL is 'http'
The other three were default, or blank.
Still receiving the same error as noted above.
Thank you for working with me. I think what's missing here, however, is the understanding that my instance is running in a runtime-only environment. This means I do not have access to the GUI to enable the change as outlined in the second set of instructions you linked. I can only work with the APEX API interface. Does that make sense?
Is there any way to set the environment to non-runtime only....
No. The staging/testing environment is meant to mimic the production environment which cannot be changed. The app will need to be moved to production at some point along with the ability to print. That's why I need to understand how to do it. I'd like to see it work in the staging/testing environment first.
I have actually gone through the process of installing the developer environment into staging/testing. I have set the Report Printing to Oracle APEX Listener in the Instance Settings via the GUI. The result is the same. Checking parameters at the command line, they are as follows:
PRINT_BIB_LICENSE = APEX_LISTENER
PRINT_SVR_PROTOCOL = http
All other PRINT% parameters are empty. I have a sneaking suspicion that it has to do with the ACL's. Here is what they look like right now:
SELECT na.acl , na.host , na.lower_port , na.upper_port , nap.principal , nap.privilege , nap.is_grant FROM dba_network_acls na , dba_network_acl_privileges nap WHERE na.aclid = nap.aclid;
ACL HOST LOWER_PORT UPPER_PORT PRINCIPAL PRIVILEGE IS_GRANT
-------------------------- ----- ---------- ---------- --------------- --------- --------
/sys/acls/power_users.xml * APEX_040200 connect true
I have next tried to use the Apache FOP printing option, but this returns the same ORA-20001 error. For that setup, the fop.war was deployed to GlassFish Open Source Edition. Here are the specs:
Oracle Application Express 4.2 (4.2.3.00.08)
Oracle APEX Listener 2 (188.8.131.527.04.29)
Oracle GlassFish Server Open Source Edition 4 (build 89)
Oracle Database Express Edition 11g (184.108.40.206)
Oracle Linux 6.3 (Santiago)
If this reply attracts no attention, I'll post another question specific to Apache FOP and this error.
NOTE: I ran into the xmlparserv2.jar problem associated with deploying fop.war to GlassFish. Just google that, and you'll see Matthias Hoys' blog post. In addition to that, however, I need to fix my XE environment (he was working with EE) by downloading the oraclesupportfiles.zip file. XE did not have an xmlparserv2.jar file to use.