Thank you for raising this.

I don't have an old database version currently because I switched machines.
I did remove the reference to the 1.1 http version constant ... and it compiles on Oracle 21c.
Will have a look at it next week.

Best, Dietmar.

Hi,
Great sure please and in documentation such releases not mentioned,

Oracle Database Release: The minimum requirement is the availability of the package UTL_HTTP. Thus the integration will work with all Oracle versions in which Oracle APEX can be installed, even Oracle XE (10g).

Thanks

You are absolutely right ... will have to revisit it. For the most part this is still valid, I don't use any specific higher-version features.

Thank you again!

I will be going in details so will be raising concern if any please don't mind in advance. @user_remove.sql also having issues like not dropping a seuquence and a type object. thanks

I don't mind at all ... keep 'em coming :).

Thank you.

I am able to configure JasperReportsIntegration-2.4.0.0 but now stuck at the end. From Tomcat TEST report is showing but when I install test app in APEX it is giving error. Database is 12C and APEX is 22.2.1
on Verify Setup entered URL details as Protocol https then server and port 1443 and context path is JasperReportsIntegration.

Check 1, 2, 3 are Passed but all others failed and here is the error,

Check 4 to 7 following error,
Error occured: ORA-29273: HTTP-Anforderung nicht erfolgreich ORA-28860: SSL-Abbruchfehler ORA-06512: in "SYS.HTTPURITYPE", Zeile 38
and ACL script was also executed.

Apex app tab Report Tester giving following error,

Contact your application administrator. Details about this incident are available via debug id "150653".
ORA-29273: HTTP-Anforderung nicht erfolgreich ORA-24247: Netzwerkzugriff von Access Control-Liste (ACL) abgelehnt

Unable to understand the way forward if it is SSL issue or ACL. Thanks

Release 2.4 is very old.

Did you run the script: sys_install_acl_12_and_above.sql ?

You need to use the exact same configuration as what you want to call via the url. For example, when you want to access http://localhost:8080 then you should configure the ACLs to allow localhost, not 127.0.0.1.

Is the Tomcat on the same machine as your database? Which url do you try to call? http or https?

Best
Dietmar.

Hi Dietmar,
Here are my responses,

Did you run the script: sys_install_acl_12_and_above.sql ? >> YES

You need to use the exact same configuration as what you want to call via the url. For example, when you want to access http://localhost:8080 then you should configure the ACLs to allow localhost, not 127.0.0.1. >> It is https://xxapex.abc.com:1443/ords so I used accordingly.

Is the Tomcat on the same machine as your database? >> YES
Which url do you try to call? http or https? >> https

Thanks

Hi Dietmar, Any suggestion please. thanks

I will have a look later today. Still busy. First I need to set up an environment so that I can test it ... on an older release. Please bear with me. Thanks. Want to make sure, it works flawlessly this time.

Great thanks.

Hi,

please use the latest release and make the following change in the file xlib_http.pks in line 39:

HTTP_VERSION_1_1 constant VARCHAR2(64) := 'HTTP/1.1'; -- #123

=>

HTTP_VERSION_1_1 VARCHAR2(64) := 'HTTP/1.1'; -- #123

So, basically, when you turn the constant into a variable ... it will all work out even on this older database.

You were talking about:

@user_remove.sql also having issues like not dropping a seuquence and a type object

I am sorry, but I cannot reproduce this. All objects that are installed are cleaned up again.
BTW, I am using the latest release. And yes, I remember that objects weren't cleaned up in a previous release ... please use the latest one.

Best
~Dietmar.

Hi, By removing constant the script having no error now resolving the ACL/SSL issues. Will get back to you with my findings or questions. thanks

Great!

For the ACLs you have a sample script to allow them.
In the documentation you will find instructions for running it with SSL: https://github.com/daust/JasperReportsIntegration#accessing-jasperreportsintegration-through-ssl

Generally speaking, since it is running on the same machine, I would use plain http to communicate between the database and the Tomcat and only allow http connection on localhost.

Good luck,
Dietmar.

Dear Dietmar,
You are right already used localhost since on same node but want to configure SSL for later move to multi nodes. Will share if any challenge as will check once certificates imported in the wallet. Thanks