So this suppose to be very thorough tutorial with print screens. Unfortunately, images were lost during migration :(
here you go anyway!
Installing
Apex Listener with Glassfish server
1. Download Oracle APEX Listener 1.1.3
(apex_listener.1.1.3.243.11.40.zip )
2. Login as oracle user
mkdir /home/oracle/apex_listener
cd apex_listener
unzip apex_listener.1.1.3.243.11.40.zip
Archive: apex_listener.1.1.3.243.11.40.zip
creating: docs/
creating: docs/AELIG/
…..
…
3. Copy Oracle Application Express Images
Before you begin, you must copy Oracle Application Express
images.
To copy Oracle Application Express images:
Create folder named ” i ” in:
<glassfish directory>/domains/<domainName>/docroot
In my case it is apparently in:
/usr/local/glassfish3/glassfish/domains/domain1/docroot/
mkdir /usr/local/glassfish3/glassfish/domains/domain1/docroot/i
let’s “copy” directories and files. I prefer rsync
rsync -auvr /home/oracle/apex/images/*
/usr/local/glassfish3/glassfish/domains/domain1/docroot/i
* from Oracle apex Listener documentation:
Launch the Administration Console
At least one GlassFish server domain must be started before you
start the Administration Console.
To
launch the Administration Console:
Launch
the Administration Console by typing the following URL in your Web browser:
Create
Users and Roles
Oracle
Application Express Listener requires users be assigned roles to access Oracle
Application Express Listener Administration. This section describes how to
create users and roles. For more information on security realms, users, group
list, or roles, see your Oracle GlassFish Server documentation.
Topics:
About
Roles
Create
Users
About
Roles
Oracle
Application Express Listener requires you assign users roles to access the
Application Express Listener Administration. There are two types of roles:
Admin –
The user has permission to access the Oracle Application Express Listener
Administration page.
Manager
– The user has permission to access the Oracle Application Express Listener
Status Information Page.
You can
enable a default principal-to-role mapping on the Application Server using the
Admin Console if the group list names is defined the same as the role names
To
enable a default principal-to-role mapping:
On the
navigation tree, select Configuration and then Security.
The
Security page displays.
Select
the check box next to Default Principal to Role Mapping.
Click
Save.
Tip:
Enabling the Default Principal to Role requires the Group List
to be the same as the role name as described in the sect section.
Create Users
You must
create users to access the Oracle Application Express Administration page and
Status page.
To
create users:
In the
navigation tree, expand the Configuration node.
Expand
the Security node.
Expand
the Realms node.
Select
the realm to which to add your user (for example, file).
The Edit
Realm page appears.
On the
Edit Realm page, click the Manage Users button.
The File
Users page appears.
On the
File Users page, click New.
The New
File Realm User page appears.
On the
New File Realm User page, create an Admin user:
User ID
– Enter the name of the Oracle Application Express Listener administrator:
adminlistener
Group
List – Enter the role to which the user belong:
Admin
New
Password – Enter a unique password.
Confirm
New Password – Enter the password again.
Click
OK.
Repeat
the previous steps and create another user for the Oracle Application Express
Listener manager, by specifying the following:
User ID:
managerlistener
Group
List: Manager
Click
OK.
Install
the Deployment
Tip:
To install the deployment:
1. On the
navigation tree, click the Application node.
The Applications page displays.
1. Click
the Deploy button.
1. Select Packaged File to be Uploaded to
the Server and click Browse.
2. Navigate
to the location of the apex.war file,
select the file, and click Open.
The Deploy Applications or Modules page displays.
1. On the Deploy Applications or Modules page, specify the following:
1.
Type: Web
Application
2.
Context Root: apex
3.
Application Name: apex
4.
Status: Enabled
5.
Description: Application
Express Listener
6.
Accept all other default settings and click OK.
Tip:
If a check mark does not appear
in the Enabled column for apex,
then select the check box next to apex and
click Enable.
Access Oracle Application Express Listener Administration
To access Oracle Application Express Listener Administration, in
your Web browser go to:
http://<host>:<port>/apex/listenerConfigure
Where:
·
<host> is
the DNS name or IP address of the Administration Server
·
<port> is
the listen port on which the Administration Server is listening for requests
Access Oracle Application Express Listener Administration
To access Oracle Application Express Listener Administration, in
your Web browser go to:
http://<host>:<port>/apex/listenerConfigure
Where:
·
<host> is
the DNS name or IP address of the Administration Server
·
<port> is
the listen port on which the Administration Server is listening for requests
Additional notes:
after some time digging I was not able to go back to
listenerAdmin page until i found post on OTN:
I was working on a similar issue on a new Glassfish
installation. (latest version at time of writing: Glassfish 3.1.2)
Deployed correctly
Initial config working
Users setup correctly with proper group names
The listenerAdmin page produced a http 403 error.
The solution i found was in teh
server-config – Security – JACC setting.
The DEFAULT setting did not seem to pass user and
group back to the APEX listener – causing the security to fail.
Changing the JACC setting to “simple”
corrected the 403 issue in my case.
after this you can login to listenerAdmin page as adminlistener
user you defined during the install
