Glassfish with Apex Listener - ORDS, SODA & JSON in the Database

Something I've noted
My successful URL is:
http://localhost:8080/apex40/
If I type this, without the final slash, I get request is not allowed.
http://localhost:8080/apex40
A note if anyone is confused, I'm not sure if it's a Glassfish setting somewhere.
Scott 

We did see this also a fix in in progress and it appears to be specific to how the glassfish is handling the case.
-kris 

Thanks, Kris

Related

|Apex Listner and Custom Authentication

Hi All,
I have spent a long time looking through the forums and beyond, but cannot seem to get to the bottom of this.
I have recently installed Apex Listener (on glassfish) with Apex 4 and 10g on an XP box, and it all works fine. However, when I import an application that was developed using EPG, I cannot log into it, getting the following message:
Expecting p_company or wwv_flow_company cookie to contain security group id of application owner.
     Error      ERR-7621 Could not determine workspace for application (:) on application accept.
OK      The application uses custom authentication and authorisation, maintaining info in session.
I am suspicious that the environment will not let me store a cookie, but I'm not sure. It is a little frustrating, because I wanted to simply use the recommended default configuration for Apex 4. i.e. using the listener. However, now at customer site and just losing so much time on this.
Can anybody help?
thanks
paul 
I guess no one has the answer to this or even a thought ...
or nothing helpful at all.
Thats really disappointing.
I will have to go back to EPG or APache.
Why bother with the big hollbollo about the listener .... 
Hi PJ,
what is the exact version of APEX? And does your application use a page sentry function for custom authentication?
Does your application work when you call it through EPG/mod_plsql? Does only the APEX listener call fail?
Regards
Patrick
-----------
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf 
Patrick
Thanks for the reply. The problem has been fixed when I upgraded to 4.0.2.00.07.
Paul

class loading issue with wlst deployment

Hi
Does anybody know something about the classloading from apex.war with WLS?
In which order the jars must be loaded with WLST?
regards
user12150923 
Hi "user12150923",
Does anybody know something about the classloading from apex.war with WLS?If you can substantiate "something", ... ;)
In which order the jars must be loaded with WLST?Well, I'm not sure if this will be exactly the same in WLST, but I just traced the APEX Listener (1.1.2) in standalone mode and got the following order:
<ol>
<li>xmlparserv2-11.2.0.jar</li>
<li>apex.jar</li>
<li>commons-fileupload-1.2.1.jar</li>
<li>ojdbc6.jar</li>
<li>je-4.0.103.jar</li>
<li>ucp.jar</li>
<li>ojmisc.jar</li>
<li>xdb-11.2.0.jar</li>
<li>poi-3.6-20091214.jar</li>
</ol>
If this doesn't work on your site, you could see in the stack trace which class is missing and hence has to be loaded before. If you need help in interpreting it, don't hesitate to post it here.
-Udo 
Thanks! This is a very good hint for me to look further. 
I'm glad I could help, even without having experience with WLST.
It would be great if you could post your solution once you have it complete, so others searching for that topic could benefit from your efforts.
Thanks,
Udo 
With Version 2.0.1 is it much more comfortable to deploy with WLST!

The URL from Apex Listener.

Hi everybody!
I set up my Apex Listener in a Standalone Mode
How can I set up my URL with my words such as: http:/localhost:8585/myapplication/f?.......
replace for the default URL: http:/localhost:8585/apex/f?.......
I don't know where my DAD is, and how many steps should I do to complete this changes?
And how about
http://localhost:8585/apex" or "http://localhost:8585/apex/apex_admin?
Thanks for any help. 
Hi,
the APEX Listener has fixed (hard coded) contexts in Standalone Mode, so you can't do that. Either deploy the war file to a regular JEE server where you can choose the context, or put a HTTP (reverse) proxy in front to do the switch for you.
Note that Standalone Mode is not intended to be used for productive deployments, but for testing and development purposes only.
-Udo 
thanks very much Udo! 
I'm glad I could help.
Please mark this thread as answered and any helpful or correct answer accordingly, so other users searching the forum might spot relevant posts easily.
Thanks,
Udo

apex_admin page not found

Hello.
I have a problem with apex_admin page.
We updated apex to 4.1 version and updated listener to 1.1.3.
All listener pages (status, admin, configure) are working.
We can run apex on http://hostname:port/apex
But when we try to go to apex admin page on http://hostname:port/apex/apex_admin, we get:
not found
What could be the problem?
Thanks,
Regards 
What do the installation docs say the URL for the admin page is? 
Hi Dejan,
are you able to login to workspace "internal"?
And did you try to use the URL with a trailing slash, e.g. http://hostname:port/apex/apex_admin/ ?
If the answers to the previous questions are negative, could you please provide some additional information on your system? Db, previous APEX and APEX Listener version, upgrade workflow you executed... And did you receive any errors during the upgrade? Perhaps you still have the installation logs at hand for a review.
In general, this doesn't sound like an issue caused by something in APEX Listener, as I know it is capable to display the admin application.
-Udo 
Hello.
Thanks for your reply.
Trailing slash doesn't help.
The problem we have is, that we updated APEX to 4.1 - but updated to Runtime Environment by mistake.
So we executed apxdvins.sql script as described in installation documentation (3.8.1 Converting a Runtime Environment to a Full Development Environment).
Now we can develope application and everything works except admin page.
Regards,
Dejan
Edited by: DejanH on Jan 25, 2012 2:55 PM 
Hello Dejan,
runtime would have been my first thought if you hadn't claimed /apex would work...
Anyway, it would still be interesting to know whether you're able to login to workspace 'internal'. And can you determine if it's actually the alias /apex/apex_admin that fails or perhaps some of the redirects that come afterwards, i.e. which is the concrete URL you get the 404 for? Or do you even get a different status code?
-Udo

listenerAdmin not working in WebLogic

I seem to be having the same issue that folks are having within the Glassfish server. I've configured the APEX listener on WebLogic 11g (10.3.5). Followed the instructions to create the adminlistener and managerlistener and their respective groups: Admin and Manager and assigned the users apppropriately (followed the installation instructions). I've used listenerConfig to configure the listener but when trying to access listenerAdmin URL I get the dreaded 403 error. Any help would be appreciated.
Thanks,
Jack 
Hi Jack,
could you post some additional information of what exactly you did and which version of APEX Listener you use?
And did you try to reset your browsers authentication cache? As I've learned when investigating similar problems (also discussed here) both listenerStatus and listenerAdmin use the same realm for basic authentication ("APEX"). If your browser stores your authentication information for one of these realms (which it usually does) and you try to enter the other part, it resends these information, which can lead to a 403 (as discussed in Link http://localhost:8080/apex/listenerConfigure not working).
Possibly this caching is even instance-independent (as the realm doesn't include any host/instance/... information), so if you've entered different credentials for another instance, this could be an explanation as well. Could you try to erase any entry concerning APEX Listener from your browser cache? Or try a different browser you ususally don't use, perhaps even a portable version of Firefox or something like that, where you can be sure you have a fresh start and can safely abandon everything once you've done?
The latter case would only be relevant if you aren't even asked before you get the 403. So the question is: Can you enter the credentials at all, or do you get the 403 right away?
Another possibility: Did you try with a simple password (without any special character)? And did you restart your WLS after adding those users? Possibly these changes aren't effective immediately.
-Udo 
Thanks for the quick reply Udo. From the looks of it, you must live in this forum.
I resolved my problem. The documentation says to create roles called Admin and Manager but when I looked into the web.xml file to verify that I was typing things in correctly, it says that the two roles are ApexAdmin and ApexManager. :(
I made the adjustment in the console and voila, it worked. By the way, I'm using Apex Listener version 1.1.3.243.11.40 
Hello,
From the looks of it, you must live in this forum. Well, it's more like there's not very much other users are watching it...
I resolved my problem. The documentation says to create roles called Admin and Manager but when I looked into the web.xml file to verify that I was typing things in correctly, it says that the two roles are ApexAdmin and ApexManager. :(That's strange. Where did you get the file from? It's definetly not the original web.xml. The one you get from OTN download actually fits to the documentation. I just did a download and re-checked that everything's still as it should be...
I made the adjustment in the console and voila, it worked.Great to hear that, anyway! ;)
Have fun using APEX Listener!
-Udo
P.S.: Please mark this thread as answered and any helpful or correct answer accordingly, so other users searching the forum for a similar problem can spot relevant posts easily. Thanks!

Categories

Resources