-----
With that combination (APEX listener 1.1.3 on Glassfish 3.1.1 on Java 7 u3..) :
there is already a problem with authentication when trying to access Glassfish console.
I type the username and password in the right way, yet not able to access unless I type this command on asadmin utility:
enable-secure-admin
-----------

403 means your user has been authenticated successfully but it doesn't have the right role mapped.
You indicate that your user has Admin role, and probably you also defined that role case sensitive. Did you also choose the right realm for that user? It should be the realm file .
Perhaps you have to restart GlassFish to make sure the user and role information are present for APEX Listener.

How can I make the default-config running ??

You can't. See the [url http://docs.oracle.com/cd/E18930_01/html/821-2426/abdjl.html#scrolltoc]corresponding section of the HA-Admin Guide for more details. Though for Oracle GlassFish, these concepts are implemented equally in the OSE.
Why would you think there is a need to switch to that one?
I'm not a GlassFish expert (and this is no GlassFish-Forum... ;) ), but if you want a fresh start, you could do one of the following two things:
1) overwrite your server-config with default values
2) create and assign a new config

In both cases, stop your instance and create a backup of your domain.xml.

For 1) you edit the domain.xml and overwrite the block below

<config name="server-config">

up to the closing tag for config with the values from

<config name="default-config">

and restart your instance. Note that the default-config has different ports and settings than you might expect from your server-config.

For 2) you could either start your instance again and copy the config via admin console (or GUI), or edit the domain.xml manuall by creating a copy of the whole block of the default-config within the configs tag and rename it, e.g. to test-cofnig. Then change your instance to use that config by editing the referenced config, e.g.

I was checking the Forum for a similar problem, and I found a long thread between you and one of Oracle Advocate.... you suggested to make sure that the default server is running ...
However, I think the cause of my problem is that I installed Glassfish first with Java 7 then changed to Java 6 .... The ideal solution was to uninstall Glassfish and reinstall it again ....

Yeah, that meant more or less that I wanted to make sure that no other configuration change (like JVM parameter) had been effective without noticing. "default server" in that sense meant to (re)create the configuration that shipped, not actually the "default-config". Sorry for any confusion I might have caused by that. ;)

However, I think the cause of my problem is that I installed Glassfish first with Java 7 then changed to Java 6.

I think so, too. Probably some issue with different versions of the hash/encryption function or something like that used in Java 7 without downward compatibility. Though I'm not a GlassFish expert, I assume that the authentication in file realm is somehow linked with Java's keytool which had several changes from Java 6 to Java 7.

Anyhow, have fun with your new instance. And thanks for reporting back after you've solved the problem!