Requested URL is not allowed - ORDS, SODA & JSON in the Database

Working on:
CentOS 5.5
Glassfish 3.0.1 (the new Oracle branded one :D)
JDK 1.6.20
Did work previously with apex listener build: apex_listener. (configured manually...could never get the roles and users straight before the guide)
Redeployed latest because I saw some problems and the first thing to do is deploy latest.
Edit Added:
Glassfish runs on 8080 with ssl on 8181. Iptables redirects from 80 to 8080 and 443 to 8181.
And, even though in the configuration below I have specified nothing for the inclusionlist, I have done both and currently have it with the inclusionlist as: "apex, wwv_flow*, p, f, z, n, apex*"
It just so happens when I took that snapshot of the config it wasn't in there at the time.
Errors (full log, status, and config to follow):
Edited by: rwendel on Jul 9, 2010 1:58 PM 

Never mind - I checked every log but the right one. OBJECT_TYPE error on XE. I looked straight at it the other day but didn't need it on the older point release. Needed it now. Seems to get me in. Hopefully my other problem is gone.
Edited by: rwendel on Jul 9, 2010 1:59 PM


Comms Express problem after installing patch

I had the mail and address book components of comms express working but was hitting the bug with the calendar not being able to show dates after 2006. So I installed patch 122793-12 which is supposed to fix this issue.
After installing the patch I got the following error on restarting the application server (which is the web container):
a.session.ManagerBase|_ThreadID=10;|IOException while loading persisted sessions
: writing aborted;
on: com.sun.uwc.common.util.UWCPreferences writing aborted;
: com.sun.uwc.common.util.UWCPreferences
This occurs when the app svr tries to load the comms express web app.
I went through the and carefully, comparing the old version and the version modified by the patch. The only change of note is that the patch added the following to
I found that if I commented out these lines the application server started up correctly. However, on logging into comms express I found the Mail tab had dissapeared and clicking the Calendar tab produced "The selected calendar(s) was either deleted or does not exist or you do not have permissions to view it. Select another calendar(s).".
So any ideas as to (a) what these new webmail.proxy settings are all about and/or (b) any other ideas as to why this patch has messed up Comms Express?
The version of our Messenging Server is v6.2 Rev. 3.04 Build 2005.196.0138 and we are using Identity SSO.
you need to uncomment those lines, and put the correct entries in. . . . 
So any ideas as to (a) what these new webmail.proxy settings are all about and/or (b) any other ideas as to why this patch has messed up Comms Express?Please note that by installing patch 122793-12, you have actually upgraded to a new release of the product which introduced a number of underlying structural changes (one of these being that comms-express now communicates differently for webmail access).
Prior to doing this upgrade there are a large number of pre-requisite and also post-install steps that need to be carried out as per the upgrade guide:
Other 6.3 (comm-suite-5) upgrade patches are available at:
Shane, thanks for alerting me to the fact that I had inadvertantly upgraded from 6.2 to 6.3. I decided to backout this patch and to install one of the obsoleted patches that fixes the calendar server date problem without upgrading to 6.3.
So I backed out the patch using backout-newconfig and restarted the application server.
The problem is that now when I try and login to communications express I get the following errors in the log:
SEVERE: Could not load the file: <uwcbasedir>/WEB-INF/domain/<Our.Domain.Name>/ (No such file or directory)
Jun 27, 2007 3:22:02 PM com.sun.uwc.common.util.UWCDomainCache loadUWCDomainProp
WARNING: Unable to load domain configuration file for domain<Our.Domain.Name> has also just existed in the root of <uwcbasedir>/WEB-INF/domain and this directory has never had our domain name as a subdirectory. So why would installing/uninstalling this patch suddently cause Comm Express to start looking for things in different directories?
I have tried manually creating this directory and putting a copy of there but that caused "Invalid Session ID" errors.
I have checked and and they are back to being exactly as they were before the patch was installed.
"backout_newconfig" doesn't uninstall the patch, just the config changes. You also need to use the pkgrm command to remove the patch. 
Well, I used patchrm to remove the patch but I still get the same problem. 
are there error messages? Has anything changed since before you backed the patch out? "it still doesn't work" isn't really a very precise description of the problem. 
After uninstalling the patch it seems that Comms Express was expecting a domain specific configuration. I'm not sure why, but anyway, I created a directory for the domain under <uwcdeploydir>/WEB-INF/domain and copied the and locale directories into it.
Then when I restart the application server there are no errors in either the app server log or uwc log. But when I browse to the Comms Express login page I get the following errors in the log:
FINE: IdentitySSOAuthFilter: Resolved domain? <My.Domain.Name>
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.IdentitySSOAuthFilter doFilter
FINE: 1. session is not present.. get token manager..
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.IdentitySSOAuthFilter doFilter
WARNING: SSOException..Invalid session ID.
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.LDAPAuthFilter doFilter
FINE: Check If Identity is enabled
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.auth.LDAPAuthFilter doFilter
FINE: Identity is enabled....return
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.util.UWCDomainCache loadUWCTheme
WARNING: Theme for localeenand<My.Domain.Name> is not configured
Jun 28, 2007 11:35:27 AM com.sun.uwc.common.util.UWCDomainCache loadUWCTheme
Nothing has changed other than the fact that I installed and uninstalled the patch. I have checked the and and they are identical to the original versions (prior to installing the patch).
I have tried creating a locale and domain specific theme but that didn't help and I think the errors about the theme just result from the original "Invalid Session ID" error.

Problem with installed Opensso

I’ve installed Sun OpenSSO Enterprise on Solaris 10 with Sun Directory Server, had it configured and had been using for about a month. Then, yesterday, I’ve rebooted the server. Now, when I go to the URL where OpenSSO was installed, I get the Configuration Option page. Does anyone have any idea how I can resolve this without having to reinstall everything from scratch and losing all the configurations?
I've resolved this issue. It was because Opensso domain was started before directory server.
Edited by: angelmoon on Apr 21, 2009 2:43 PM 
In 7.1 this was usually due to the fact of the bootstrap file being gone.
Recreating the bootstrap file and pointing to to your config would fix it.

Data validation failed for the attribute, Server List.

I have access manager 7.1 installed from JES 5u1, application server 9.1 on solaris 10 x86 machines.
Two front end servers are there running http and https
Now configuring load balancer. I am able to access front end servers through LB.
let say LB as
and front end servers are
and my platform list have two entries right now|01|02
i was trying to add site list in there
so I prepared something like below|01|02|01|01|02|01|03|02|04|02i also tried only with the entries of http but it gave the same error
Data validation failed for the attribute, Server List.Am I missing any configuration?
Edited by: mr.chhunchha on Sep 6, 2008 2:20 AM
Edited by: mr.chhunchha on Sep 6, 2008 2:22 AM 
10 days response????

Can not configure Apex listener

I'm trying to install Apex listener in standalone mode on Aix 6.1. I'm pasting the output. When trying to go to http://livaixoradev01:8080/apex/listenerConfigure I'm not getting any response - it's just hanging.
$ /usr/java6/bin/java -Dapex.home=/ccrrd1_orabin/apex_listener -Dapex.images=/ccrrd1_orabin/apex/images -Dapex.port=8080 -jar /ccrrd1_orabin/apex_listener/apex.war
INFO: Starting: /ccrrd1_orabin/apex_listener/apex.war
See: 'java -jar apex.war --help' for full range of configuration options
INFO: Extracting to: /ccrrd1_orabin/apex_listener
INFO: Using classpath: file:/ccrrd1_orabin/apex_listener/apex/____embedded/start.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/apex.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/commons-fileupload-1.2.1.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/je-4.0.103.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/ojdbc6.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/ojmisc.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/poi-3.6-20091214.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/ucp.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/xdb-11.2.0.jar:file:/ccrrd1_orabin/apex_listener/apex/WEB-INF/lib/xmlparserv2-11.2.0.jar:
INFO: Starting Embedded Web Container in: /ccrrd1_orabin/apex_listener
Enter a username for the APEX Listener Administrator [adminlistener]:
Enter a password for adminlistener:
Confirm password for adminlistener:
Enter a username for the APEX Listener Manager [managerlistener]:
Enter a password for managerlistener:
Confirm password for managerlistener:
Mar 22, 2012 4:37:44 PM ____bootstrap.Deployer deploy
INFO: Will deploy application path=/ccrrd1_orabin/apex_listener/apex/WEB-INF/web.xml
Mar 22, 2012 4:37:44 PM ____bootstrap.Deployer deploy
INFO: Not a valid WebApp, will be ignored : path=/ccrrd1_orabin/apex_listener/apex/WEB-INF/web.xml
Mar 22, 2012 4:37:45 PM ____bootstrap.Deployer deploy
INFO: deployed application path=/ccrrd1_orabin/apex_listener/apex/WEB-INF/web.xml
Mar 22, 2012 4:37:45 PM com.sun.grizzly.Controller logVersion
INFO: Starting Grizzly Framework 1.9.18-o - Thu Mar 22 16:37:45 EDT 2012
INFO: Please complete configuration at: http://localhost:8080/apex/listenerConfigure
thanks for any ideas/help,
Hi Sue,
from what you describe it sounds like there's a firewall blocking the access to your APEX Listener port.
Note that there have been several reports on problems with APEX Listener on AIX. Colm posted instructions on how to patch the apex.war on AIX here: {thread:id=2318817}
I don't think you've reached the state where the issue(s) addressed by that patch would be relevant, as you should at least see a stack trace now, but perhaps you can prepare your apex.war while searching for the network issue.
Hi Udo,
Thanks for your answer. I looked again at the output I pasted below and I noticed the line"Not a valid WebApp". I did a search in Metalink for this string and found Note 1369154.1 :Standalone APEX Listener on AIX Deploy Message:Info: Not a Valid Webapp, Will be Ignored. The conclusion is :
Currently there is no fix for this issue.
The workaround is to not use the standalone environment on AIX, instead use a proper web server, such as Weblogic or Glassfish.
Do you have access to Metalink or should I paste the note here ? Can you tell me if this is relevant to my issue ?
Hi Sue,
you're right, I missed that line because it's logged as "INFO", which is definetly an inappropriate severity for that kind of failure.
As far as I remember that issue, the reason actually is in the Oracle XML libraries that conflict with the IBM JDK on AIX. Did you try out the patch described by Colm? There are a few people who solved their problems that way.
Anyway it's recommended to use a proper JEE container for production environments. I guess this workaround could have removed focus from that issue, and perhaps the internal processes didn't allow Colm's solution to be published officially, because it hadn't been tested on the acutal (non-Oracle) platform.
After applying Colm workaround I was able to bring up Apex listener on IBM. However when trying to import an application it's hanging on "Installing Application" - anybody encountered this issue after applying the workaround ?
Edited by: Sue on May 21, 2012 8:52 AM 
Hi Sue,
great to hear you've advanced one step.
Do you see any error either in your browser or in APEX Listener's log?
One of the possible causes for problems with installing applications could be your APEX tablespaces have run full. In that case, it could take a lot of time until you receive the database message about "unable to allocate..." (more space).
Hi Udo,
Thanks for your answer. You are 100% percent right. The issue was that the tablespace ran out of space.
I was surprised that there was no error reported in the alert file and I was also trying to look for some log fie pertaining to the import but could not find one so I have two questions :
1. What do you mean by "it could take a lot of time until you receive the database message about "unable to allocate..." - is there a point when this message should have appeared in the alert file and if yes when ?
2. Is there an import log file in APEX and if yes how do I find it ?
As always thanks,
Hi Sue,
I'm glad to hear you finally got your APEX Instance with APEX Listener up and running as expected now.
1. What do you mean by "it could take a lot of time until you receive the database message about "unable to allocate..." - is there a point when this message should have appeared in the alert file and if yes when ?There should be some ORA-message when you hit the fixed size or extend limit of a tablespace, e.g. ORA-01653. But in many databases, this doesn't happen immediately as the so called "Resumable Space Allocation" feature is in place. See the [url]Database Administrator's Guide for details.
If the timeout is set high enough it might happen that your client connection (in APEX Listener) will get a timeout before the error occurs and hence you won't see it. I'd expect it to appear in the alert.log as well, but possibly delayed as well. It could even happen that the transaction is rolled back when the connection is aborted by APEX Listeners connection pool (e.g. because AbandonedConnectionTimeout has hit). In that case, the error wouldn't appear at all - a nightmare for troubleshooting...
Perhaps it should be considered to disable the resumable-feature in APEX Listener's sessions in a future release.
2. Is there an import log file in APEX and if yes how do I find it ?You could import using the command line instead of the application builder and see (and spool) the output of the application script. The application builder itself doesn't provide a log file.
P.S.: Please mark this thread as answered if you think your issue is resolved, and also mark any helpful or correct answer accordingly so other users searching for similar issues can spot relevant posts easily.

How to configure GlassFish SSO with Sun ONE LDAP

O/S: Linux OEL 5
GlassFish: 3.0.1
Does anyone have any experience (or direction they can point me) with using GlassFish SSO with APEX? To be more precise, this will be APEX -> GlassFish SSO?
Edited by: user601798 on Jun 19, 2012 9:58 AM 
I have the same question.
Our users sign on their workstations using their Active Directory ID. For our SSO solution we've always used the old 10gR2 32-bit Oracle HTTP Server (Apache 1.3) with NTLM to get the Active Directory user name and feed that name into a sentry page function which looks the name up in a security database.
We're wanting to move to 11gR2 64-bit on Windows2008 with GlassFish Server 3.1.2 and Apex Listener 1.1.3. But I can't find a practical open source SSO solution for this new environment that would match what we're able to do with our old set up described above.
What is the most practical open source SSO solution for our new environment?
Any help or nudge in the right direction is appreciated. Thanks!
Edited by: JP Kreps on Jul 20, 2012 2:31 PM