路虽弥,不行不至;事虽少,不做不成。
分类: Oracle
2012-02-02 13:06:06
You can query System profile: ICX: Forms Launcher value to find the CGI url
APP-FND-01542 when logging directly into forms via the f60cgi in 11.5.10 [ID 293609.1] | ||
| ||
|
Modified 21-APR-2008 Type BULLETIN Status PUBLISHED |
|
Checked for relevance on 21-APR-2008
PURPOSE
-------
How to enable the ability to login directly via the f60cgi.
SCOPE & APPLICATION
-------------------
The distribution of this note is set to 'Limited.' These steps are
intended for to enable DBAs to login to forms directly only for
troubleshooting purposes with guidance from Oracle Support.
Accessing f60cgi is disabled in 11.5.10
----------------------------------------
With increased security in Oracle EBusiness Suite 11.5.10, the ability to
connect directly to forms via f60cgi has been disabled. By default, a user will
see the following error after entering their username and password:
APP-FND-01542: This Applications Server is not authorized to access this database.
This is expected functionality.
Enabling f60cgi direct login
------------------------------
It is possible to login however this method should only be used when
debugging problems.
1. Backup and open $APPL_TOP/admin/
2. Update the context variable:
s_appserverid_authentication
By default in 11.5.10, this is set to SECURE.
In previous 11i versions, this was set to OFF.
For debug purposes, you can use ON or OFF.
Modes:
- ON : Partial
- SECURE : activates full server security (SECURE mode)
- OFF : deactivates server security
3. Run Autoconfig to instantiate the change.
You should now be able to access forms directly again using the f60cgi call.
4. After you have finished your Forms debugging, please reset
s_appserverid_authentication to SECURE and re-run Autoconfig.
Alternative option
---------------------
Running Autoconfig is the preferred method of updating
s_appserverid_authentication.
If you are unable to run Autoconfig during troubleshooting, you can run the
the following commands instead from $FND_TOP/secure directory:
Disable:
java oracle.apps.fnd.security.AdminAppServer apps/apps \
AUTHENTICATION OFF DBC=host_visdemo1.dbc
Enable:
To activate basic server security, from the command line, enter:
jre oracle.apps.fnd.security.AdminAppServer apps/apps \
AUTHENTICATION ON DBC=
To activate full server security (SECURE mode), from the command
line, enter:
jre oracle.apps.fnd.security.AdminAppServer apps/apps \
AUTHENTICATION SECURE DBC=
Check the status:
java oracle.apps.fnd.security.AdminAppServer apps/apps \
STATUS DBC=host_visdemo1.dbc
How To Access Forms Directly In Oracle Applications R12 [ID 552301.1] | ||
| ||
|
Modified 10-MAR-2009 Type HOWTO Status PUBLISHED |
|
In this Document
Applies to:
Oracle Applications Technology Stack - Version: 12.0 to 12.1
Information in this document applies to any platform.
Goal
By default in Oracle Applications R12, users are not able to access Forms directly via the following url:
The following error would pop out:
APP-FND-01542: This Applications Server is not authorized to access this database.
The goal of this document is to allow users access to the Oracle Applications R12 directly via Forms especially in cases where access to the following url is not available:
NOTE: Accessing Forms directly is not supported and should only be used for diagnostic and troubleshooting purposes.
Solution
1. Edit $CONTEXT_FILE which is located in $INST_TOP/appl/admin
2. Change
to
Application Server Security Authentication can take one of the following values {ON, OFF, SECURE}.
OFF - Server security is not checked. Any application server machine can access the database.
ON - Some level of trust is required to access the database. Either the Application Server is registered with the database or the module and version ID are known to be trusted.
SECURE - Full trust is required for access to the database. Only registered Application Server machines and trusted code modules may connect.
3. Run $INST_TOP/admin/scripts/adautocfg.sh to instantiate the changes
4. Users are now able to access Forms directly.
NOTE:
Remember to set the Application Server Security Authentication back to SECURE by settting the value of s_appserverid_authentication to SECURE and running autoconfig.