7 Replies Latest reply on Sep 7, 2015 6:33 AM by Kiran Pawar

    Help with new APEX install

    JackBox

      I am new to APEX and I am trying to get an initial install working.  I have a frontend server with WebLogic and Restful Services installed and a Backend server with oracle 12c and APEX 5.01.  I have deployed the ords.war and i.war files on the weblogic server and started ords.  I just want to get to the login page.  I have been trying http://127.0.0.1:8080/ords and I get a webpage that shows "ORACLE REST DATA SERVICES" at the top and then it has a 404 error.  In the rest data services windows it shows "WARNING: The pool_config view or table was not found in schema: APEX_LISTENER"  Any ideas what I missed?

        • 1. Re: Help with new APEX install
          JackBox

          I have made some progress and I am thinking my problem may be related to the static images.  On my front end server I copied the "images" folder from the backend server where APEX is installed.  When I created my i.war file I ran the following

          java -jar ords.war static c:\rest\images

           

          I can get to the following and see my version

          http://127.0.0.1:7001/i/apex-version.txt

           

          But when I go to http://127.0.0.1:7001/ords I get a 404 error.

           

          Do I need to run @reset_image_prefix.sql on my backend server?

          • 2. Re: Help with new APEX install
            JackBox

            I have also noticed that my FLOW_FILES account on oracle is disabled and expired.  Looking in the instructions that Oracle Application Express creates this account but I do not see where I ever gave this a password.  Should this account be enabled and should I change the password to something I know?

            • 3. Re: Help with new APEX install
              Kiran Pawar

              Hi JackBox,

               

                   Please provide the following info which will help pointing out the issue:

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

               

                   For debugging this 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 Oracle Weblogic 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)

               

                   Regarding 404 - While configuring ORDS 3.0 have you skipped "PL/SQL Gateway" configuration? ( 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 :

                   Also open your "ords.3.0.1.177.18.02" folder and run the "readme.html" file in a browser and check the section "404 Errors when configuring Oracle REST Data Services" regarding the causes for 404.

               

              Regards,

              Kiran

              • 4. Re: Help with new APEX install
                JackBox

                DB Version 12.1.0.2

                ORDS Version 3.01

                WebLogic 12.1.3.0.0

                JDK 8 Update 51

                 

                Below is the steps I have taken to try and get APEX working

                 

                Setup 2 Windows VM servers APEXBACK and APEXWEB

                 

                On APEXBACK

                1.  Installed Oracle DB Created APEXDB as a single instance no Multitenant

                2.  Installed APEX as follows

                ran undopwd.sql to disable password complexity

                Installed apex with

                @apexins.sql SYSAUX SYSAUX TEMP /i/

                 

                All of the following accounts exist and are enabled and passwords are not expired

                APEX_050000, APEX_PUBLIC_USER, APEX_REST_PUBLIC_USER, APEX_LISTENER, ORDS_PUBLIC_USER, and FlOWS_FILES.  The FLOWS_FILES is created but it is locked and disabled.  I did unlock and reset the password on this seeing if this was the issue.

                 

                ran @apxchpwd.sql to create a APEX_ADMIN account

                 

                On APEXWEB

                3.  Installed JDK

                4.  Installed WebLogic and created a basic "production" Administration Server weblogic domain default port 7001

                5.  Copied the "images" folder from APEXDB server to APEXWEB server c:\rest\images

                6.  Installed ORDS

                    java - jar ords.war

                 

                    I noticed after the install on the APEXDB server I have a few more accounts.  I notice that the ORDS_METADATA account is created but is locked and expired.

                 

                7.  I have tried starting ords in standalone mode

                    java -jar ords.war standalone --apex-images c:\rest\images

                 

                    I do get the following message

                 

                    WARNING: *** jdbc.MaxLimit in configuration apex_al is using a value of 10,

                    WARNING: *** jdbc.InitialLimit in configuration apex_al is using a value of 3

                  

                    and then going to http://127.0.0.1:8080/ords

                 

                The page that displays says Oracle Rest Data Services and gives a 404 error

                 

                I have also tried deploying the ords.war and i.war files via Weblogic but I get the same page displayed with the same 404 error when going to

                    http://127.0.0.1:7001/ords

                 

                I enabled the Data Request Error Message in the defaults.xml and below is the output

                 

                NotFoundException [statusCode=404, reasons=[]]

                  at oracle.dbtools.url.mapping.URLMappingsProvider.map(URLMappingsProvider.java:79)

                  at oracle.dbtools.url.mapping.filter.URLMappingFilter.doFilter(URLMappingFilter.java:55)

                  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:844)

                  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:844)

                  at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)

                  at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)

                  at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)

                  at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:346)

                  at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)

                  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)

                  at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)

                  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)

                  at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)

                  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)

                  at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3436)

                  at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3402)

                  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

                  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)

                  at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)

                  at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2285)

                  at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2201)

                  at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)

                  at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1572)

                  at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)

                  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)

                  at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)

                • 5. Re: Help with new APEX install
                  JackBox

                  You had also asked if I had skipped the PL/SQL Gateway configuration and yes I did skip this.  I thought that since I chose Rest Services as my listener I did not need this.

                  • 6. Re: Help with new APEX install
                    JackBox

                    I reconfigured ORDS and selected PL/SQL and now I am getting a login page and no 404.  I confused why this is even an option seems like it is required.

                    • 7. Re: Re: Help with new APEX install
                      Kiran Pawar

                      Hi JackBox,

                      JackBox wrote:

                       

                      I reconfigured ORDS and selected PL/SQL and now I am getting a login page and no 404.  I confused why this is even an option seems like it is required.

                           The "PL/SQL Gateway" configuration is required in case if you want to configure Oracle APEX with ORDS 3.0.

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

                           It is optional in case of ORDS 3.0 (if you don't want to use Oracle APEX), as in ORDS 3.0 version you can host RESTful Web Services independent of Oracle APEX. Pre ORDS 3.0, it was dependent on Oracle APEX to host RESTful Web Services. Hence pre ORDS 3.0, configuration with Oracle APEX was mandatory.

                       

                           Have you gone through my reply in this thread : Re: problem with ords 3.0

                           Which says:

                      Hi Maahjoor,

                      Maahjoor wrote:

                      NOTE : The term "PL/SQL Gateway" refers to the Oracle APEX configuration with ORDS and has to do nothing with Embedded PL/SQL Gateway (EPG) which is one of the web listener options used for Oracle APEX.

                      really?? i was thinking both of them are the same thats why when i was configuring ORDS and it was asking for PL/SQL Gateway, i skip it. thats why it never create the apex.xml file may be.

                          Yes, the "PL/SQL Gateway" (while configuring ORDS 3.0) refers to configuring Oracle APEX with ORDS (configuring APEX_PUBLIC_USER) which is required for functioning of Oracle APEX with ORDS.

                          The ORDS configuration itself creates the required files(no need to manually copy) and which configuration files contains which information is mentioned here:

                          Refer : http://docs.oracle.com/cd/E56351_01/doc.30/e56293/config_file.htm#AELIG7201

                       

                          The "Embedded PL/SQL Gateway" refers to configuring the Internal mod_plsql viz. Oracle XML DB HTTP Server with Oracle APEX (using ANONYMOUS user).

                          This misunderstanding may be the cause behind recent 404 errors while configuring ORDS 3.0 with Oracle APEX.

                       

                      Regards,

                      Kiran