APEX webservice visibility vs ORDS

Hi Scott,

please start the ords.war file on the command line:

java -jar ords.war

You might even want to turn on debugging in the defaults.xml file:

<entry key="debug.debugger">true</entry>

On the command line it will check the validity of all connection pools and also directly show you the error messages, it is just a lot easier to spot.

Cheers,

~Dietmar.

Hi Scott,

I could reproduce the issue on my system (almost). Typically this error comes up when the connection pools for APEX_REST_PUBLIC_USER and APEX_LISTENER are not working properly.

This is my working config directory. As you can see, I have four connection pools configured (apex.xml for apex_public_user, apex_rt.xml for APEX_REST_PUBLIC_USER, apex_pu.xml for ORDS_PUBLIC_USER and apex_al.xml for APEX_LISTENER).

They all need to be working properly.

Once I delete apex_rt.xml and apex_al.xml (and restart ords) I get the same error as you, the image won't show up in my application. Thus, the original rest users (apex_rest_public_user and apex_listener) are still required in APEX for displaying the APP_IMAGES and WORKSPACE_IMAGES.

The only thing I cannot get my head around is that the images show up in a newly created workspace (as you noted), this is indeed strange.

So:

1) make sure you use the latest version 3.0.1

2) make sure that the connection pools for apex_rest_public_user and apex_listener are working correctly.

3) turn on debugging in defaults.xml:

<entry key="debug.debugger">false</entry>
<entry key="debug.printDebugToScreen">false</entry>

Perhaps you might even have to reinstall everything. Make sure to use a fresh config directory and download/extract into a clean directory, ords will "remember" the values you have entered in the file params/ords_params.properties.

If all that doesn't help, perhaps your problem is related to a different "feature" of APEX 5. They have tightened up the reference syntax in 5.0, you cannot reference #APP_IMAGES# via the #WORKSPACE_IMAGES# tag and vice versa (if you are running in APEX 5.0 compatibility mode, it still works in 4.2 compatibility mode I guess). So make sure, you reference the images correctly.

Hope that helps,

~Dietmar.

Hi swesley_perth,

swesley_perth wrote:

We've upgrade to APEX 5.0.1 and ORDS 3.0 (not sure if 3.0.1), and we have working webservices using ORDS, but they are not shown in SQL Workshop, nor do APP_IMAGES get rendered.
I'm a little sketchy on the details as I did not set this up and my colleague is not at hand, but I'll do best to provide some facts that I'm sure will highlight some simple setting that needs adjusting.
My colleague had web service issues with our existing workspace so he tried creating another, and in the second new workspace it's all working correctly.
ie - I can see services listed in the workshop and images from the repository are rendered correctly using #APP_IMAGES#my_image.png.
For instance, in the new workspace the path resolves as
<img src="125117155154685/r/103/files/static/v2/button_colours.png">
in the workspace that doesn't work it is
<img src="our_workspace_name/r/101/files/static/v2Y/button_colours.png">
and the browser complains it couldn't GET the file.
Selecting from apex_050000.WWV_FLOW_RT$MODULES returns three older records we tested with a while ago, that I see listed in the workshop only in the new workspace.
ORDS_METADATA.ORDS_MODULES shows three different modules, created by my colleage, not seen in either workspace in SQL workshop. But these are active modules managed by my colleague in SQL Developer (I think).
Users APEX_LISTENER and APEX_REST_PUBLIC_USER exist and are unlocked.
I've been using Dietmar's kscope session to try get my head around it, and it seems slide 13 relates to our problem.
daust.blogspot.com.au/2015/09/presentation-slides-for-my-ords-talk-at.html
Any suggestions on things to check/tweak?

     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 Standalone ORDS / 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)

     Does this problem occur for only one file or all the static workspace/application files?

     Enable the Network tab of the Browser Development Tools and inspect what is happening if you load a page with static workspace/application files.

     If you are getting 404 for the workspace/application static files then it is the issue of bad RESTful Services Configuration.

     The RESTful Services configuration is mandatory in APEX 5 and it is not just limited to configuration using apex_rest_config.sql.

     The second step involves configuration of users required for RESTful Services while installing ORDS?

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

     Refer the following threads with same issue :

• How to configure *application and workspace* static files after upgrade from 4.2 to 5.0?
• Static Application and Workspace Files in APEX 5
• APEX 5.0 - Static files not found even if i configured ORDS.

     Also check whether the RESTful users(APEX_LISTENER and APEX_REST_PUBLIC_USER) are unlocked as that may be also causing the problem.

     Refer : 503-service unavailable error after deploying apex listener on glassfish

Regards,

Kiran