Install ORDs

Hi Muazzam,

Muazzam wrote:

 

I would like to print reports in PDF format using apex 4.2.2 or v5. But I have read that ORD 3 is required to work even after enabling PDF in instance setting under apex admin.

Now I am having issue installing ORDS as well as it stops in process and localhost:8080/ords shows 404 page.

     Refer the following thread : Re: Re: ORDS installation after APEX 5

     In the above thread I have discussed the issues faced during installing ORDS with APEX 5 and some tips before installing ORDS in order to avoid the later errors.

Regards,

Kiran

Can you please share the full error stack trace?

Thanks,

Ganesh

Hi Muazzam,

Muazzam wrote:

 

I would like to print reports in PDF format using apex 4.2.2 or v5. But I have read that ORD 3 is required to work even after enabling PDF in instance setting under apex admin.

    ORDS 3 contains bundled Apache FOP which can be used for PDF Printing in Oracle APEX. But before using Apache FOP a java based application for PDF printing it must be deployed to a Java EE Application Server. Hence, installation of ORDS and deploying it to Supported Java EE Server should be done first. Then, configuring ORDS as Print Server for Oracle APEX Instance Settings and if your are using Oracle Database 11g or later, then configuring ACLs for using the Printing Services should be done. This is explained in your previous thread.

    Refer : Re: Failed to load PDF Document

    NOTE : Please do not abandon your threads. You should close them by marking the appropriate replies helpful/correct.

Now I am having issue installing ORDS as well as it stops in process and localhost:8080/ords shows 404 page.

    Refer the recent thread with similar issue : Re: new created apex gets 404 after upgrading ords3.0.1

    Also the following threads in the APEX OTN Forum, the same thing is being discussed:

• In a report the link "Print" is not being showed
• ORDS installation after APEX 5

Ganesh Pitchai-Oracle wrote:

 

Can you please share the full error stack trace?

Muazzam wrote:

 

how?

     For debugging 404 issue you are facing on ORDS:

• Locate the ORDS configuration folder.
• Enable the Debug Tracing in defaults.xml (If entry is not there add the entry)
• Enable the Detail Request Error messages in defaults.xml (If entry is not there add the entry)
• Start(re-start) the ORDS Standalone / Supported Java EE Application Server
• Navigate to the APEX URL
• Copy/paste the debug log into the forum reply.(Usually the error is at the end of the log, paste/attach the whole log from where the first exception occurs)

    NOTE : Deploying ORDS to Supported Java EE Application Server is mandatory, if you want to use it as Print Server with Oracle APEX. The reason is discussed in the above mentioned thread. Refer : Re: Re: ORDS installation after APEX 5

Regards,

Kiran

Hi Muazzam,

Muazzam wrote:

 

    Again you are showing the command prompt log of the ORDS.

    If you have followed this steps mentioned above, then your the error stack will be directly printed to the browser screen:

     For debugging 404 issue you are facing on ORDS:

• Locate the ORDS configuration folder.
• Enable the Debug Tracing in defaults.xml (If entry is not there add the entry)
• Enable the Detail Request Error messages in defaults.xml (If entry is not there add the entry)
• Start(re-start) the ORDS Standalone / Supported Java EE Application Server
• Navigate to the APEX URL
• Copy/paste the debug log into the forum reply.(Usually the error is at the end of the log, paste/attach the whole log from where the first exception occurs)

    Have you seen my reply to the similar thread regarding 404 error : Re: new created apex gets 404 after upgrading ords3.0.1

Regards,

Kiran

Hi Muazzam,

Muazzam wrote:

 

Stack Trace

 NotFoundException [statusCode=404, reasons=[]] at oracle.dbtools.http.entrypoint.Dispatcher.choose(Dispatcher.java:82) at oracle.dbtools.http.entrypoint.Dispatcher.dispatch(Dispatcher.java:92) at oracle.dbtools.http.entrypoint.EntryPoint$FilteredServlet.service(EntryPoint.java:123) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:73) at oracle.dbtools.http.forwarding.QueryFilteringRewrite.doFilter(QueryFilteringRewrite.java:82) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.forwarding.ForwardingFilter.doFilter(ForwardingFilter.java:59) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.cors.CORSPreflightFilter.doFilter(CORSPreflightFilter.java:67) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.cookies.auth.CookieSessionCSRFFilter.doFilter(CookieSessionCSRFFilter.java:61) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.auth.AuthenticationFilter.authenticate(AuthenticationFilter.java:89) at oracle.dbtools.http.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:62) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.url.mapping.db.PLSQLMapper.doFilter(PLSQLMapper.java:37) at oracle.dbtools.url.mapping.URLMapping.doFilter(URLMapping.java:78) at oracle.dbtools.url.mapping.filter.URLMappingFilter.doFilter(URLMappingFilter.java:63) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.locale.LocaleFilter.doFilter(LocaleFilter.java:60) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.cors.CORSResponseFilter.doFilter(CORSResponseFilter.java:71) at oracle.dbtools.http.filters.HttpResponseFilter.doFilter(HttpResponseFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.errors.ErrorPageFilter.doFilter(ErrorPageFilter.java:75) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.ecid.ECIDFilter.doFilter(ECIDFilter.java:35) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.auth.ForceAuthFilter.doFilter(ForceAuthFilter.java:44) at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45) at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64) at oracle.dbtools.http.filters.Filters.filter(Filters.java:47) at oracle.dbtools.http.entrypoint.EntryPoint.service(EntryPoint.java:80) at oracle.dbtools.http.entrypoint.EntryPointServlet.service(EntryPointServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at oracle.dbtools.rt.web.HttpEndpointBase.dispatchableServices(HttpEndpointBase.java:166) at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:88) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:751) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:566) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:219) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1111) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:498) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1045) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:98) at org.eclipse.jetty.server.Server.handle(Server.java:461) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:284) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:534) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536) at java.lang.Thread.run(Unknown Source)

     While configuring ORDS 3.0 have you skipped "PL/SQL Gateway" configuration ( as this step refers to configuring Oracle APEX with ORDS (configuring APEX_PUBLIC_USER) which is required for functioning of Oracle APEX with ORDS) ?

    Else you will run in following error :

• Re: Re: ORDS 3 404 Error
• Re: problem with ords 3.0

    Also, with ORDS 3.0.2.294.08.40 installables the "readme.html" file is provided with the section "404 Errors when configuring Oracle REST Data Services" is provided which says :

404 Errors when configuring Oracle REST Data Services

There are two main causes of 404 - Not Found errors:

• Using /ords instead of /ords/(ORDS 3.0.0 only, fixed in 3.0.1 and later).

  Oracle REST Data Services is deployed at a context-root of /ords/, in previous versions there was logic to handle the case where a user accessed /ords instead of /ords/. In ORDS 3.0.0 this functionality was regressed, but it has been fixed in this release. If you access /ords your browser will be redirected to /ords/.

• Not configuring the PL/SQL Gateway If you want to to use Oracle Application Express or you wish to access PL/SQL Stored Procedures, then you must enable the PL/SQL Gateway during the installation process.

  A quick way to check if you have completed this step is to check in the configuration folder if the file named: conf/apex.xml exists. If it does not exist then it implies that the PL/SQL Gateway was not configured.

  If you do not use Application Express then there will be no stored procedure available to serve the /ords/ resource. This means that accessing this URL will produce a 404 - Not Found status, this is expected.

  Use the misc.defaultPage configuration setting to specify the name of a PL/SQL procedure to serve the /ords/ resource. This must be a PL/SQL procedure that takes zero arguments, and uses Oracle Web Agent (OWA) APIs to produce a HTML response. This setting can be configured in SQL Developer under:

  View > REST Data Services > Administration

  and then when editing a configuration, under:

  REST Data Services > Environment > PL/SQL Gateway > Default Web Page

  If you don't wish to use Oracle Application Express or PL/SQL procedures then you do not need to configure the PL/SQL Gateway, however as explained above accessing /ords/ will always produce a 404 - Not Found status, since there is nothing to serve this resource, this is expected.

Regards,

Kiran

Hi Muazzam,

Muazzam wrote:

 

Thats not the issue as I have apex.xml file in conf directory

     Again include the error stack without formatting and include the whole error stack from the first exception. The whole error stack on one line is hard to examine.

Regards,

Kiran

Hi Muazzam,

Muazzam wrote:

 

Thats not the issue as I have apex.xml file in conf directory

     As a second thought, discard the existing configuration (delete the configuration folder) and re-configure ORDS 3.0.2 using SQL Developer.

     Refer : https://www.youtube.com/watch?v=vigcbPTekIs

     BEFORE INSTALLING ORDS 3.0 check whether your system fulfils the system requirements.

     Refer : http://docs.oracle.com/cd/E56351_01/doc.30/e56293/install.htm#AELIG7019

     NOTE the following points while installing ORDS 3.0:

• Remember to configure PL/SQL Gateway while installing ORDS 3.0
• Keep the passwords for APEX_PUBLIC_USER, APEX_REST_PUBLIC_USER and APEX_LISTENER users ready.

     If you have not configured RESTful Web Services in Oracle APEX 5, then configure it using apex_rest_config.sql (this script creates the users APEX_LISTENER and APEX_REST_PUBLIC_USER)

     Refer : https://docs.oracle.com/cd/E59726_01/install.50/e39144/listener.htm#HTMIG29159

     NOTE : This step is IMPORTANT and should be performed BEFORE installing ORDS.

• BEFORE going for ORDS installation remember the above three DB users are UNLOCKED with a proper password and note down the passwords.
• DO NOT configure ORDS in Standalone Mode.
• Deploy ORDS to a Supported Java EE Application Server, preferably Apache Tomcat.

     Refer : http://docs.oracle.com/cd/E56351_01/doc.30/e56293/install.htm#AELIG7222

Regards,

Kiran

Hi Muazzam,

Muazzam wrote:

 

I have followed all of the above stepts but PDF printing is still creating damaged file "Failed to load PDF document".

    Please provide the following info regarding your environment details:

• Detail Oracle APEX Version
• Detail Oracle Database Version
• Detail ORDS Version
• Detail Supported Java EE Application Server Version (if using one)
• Detail JDK Version

    NOTE : Here "Detail" means the major+minor version. For e.g. Application Express 4.2.4.00.08

    So, you have performed all the above installation steps for ORDS.

     Have you configured ORDS as "Print Server" in APEX Instance settings and granted appropriate ACLs? Refer the following reply in your previous thread :

    You have to configure ORDS as "Print Server" in Oracle APEX Instance Settings:

    Refer : https://docs.oracle.com/cd/E59726_01/doc.50/e39151/adm_wrkspc002.htm#BABIECEE

    Also, if you are using Oracle Database 11g or later, you have to configure appropriate ACL in order to connect to the "Print Server" configured.

    Refer : https://docs.oracle.com/cd/E59726_01/install.50/e39144/listener.htm#HTMIG29160

     Refer : Re: saving output in pdf

Regards,

Kiran