What role APPLSYSPUB user plays in oracle applications?

Intially oracle applications connects to this public schema, APPLSYSPUB This schema has sufficient privileges to perform the authentication of an Applications User (FND user), which includes running PL/SQL packages to verify the username/password combination and the privilege to record the success or failure of a login attempt.

The public ORACLE username and password that grants access to the Oracle E-Business Suite initial sign-on form. The default is APPLSYSPUB/PUB.

Once had changed the APPLSYSPUB password must propagate the change to application tier configuration files. If  the instance is Autoconfig enabled, must edit the CONTEXT file on each tier prior to running Autoconfig.

In the CONTEXT file, locate the autoconfig variable “s_gwyuid_pass” and set it to the new password, then run AutoConfig in each applicatins nodes.

Always change password of APPLSYSPUB with FNDCPASS

$ FNDCPASS APPS/[apps_pwd] 0 Y SYSTEM/[system_pwd] ORACLE APPLSYSPUB [new_pwd]

0 & Y are flags for FNDCPASS
0 is request id  (request ID 0 is assigned to request ID's which are not submitted via Submit Concurrent Request Form)
'Y' indicates that this method is directly invoked from the command-line and not from the Submit Request Form.

If you are not using AutoConfig you must manually edit the following configuration files :

1) FND_TOP/resource/appsweb.cfg
2) OA_HTML/bin/appsweb.cfg
3) FND_TOP/secure/HOSTNAME_DBNAME.dbc

All application tier processes (Apaches) must be restarted following the password change and password propagation.

Related Posts by Categories