Enabling ASADMIN User
Before enabling ASADMIN user, make sure that all workflow agent listeners, service components, background engines, and notification mailers are all up and running. You can verify the information in Oracle Workflow Manager. Otherwise, the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT) assignment will not be reflected correctly to the ASADMIN user after it is enabled.
Note: Ensure that the APPLSYS.WF_ERROR queue is enabled in order for the Workflow Deferred Notification Agent Listener to run.
Use the following steps to enable ASADMIN user:
Log in to Oracle E-Business Suite with an administrator role and choose the User Management responsibility in the Navigator.
Click the Users link from the navigation menu to open the User Maintenance window.
Enter information in the search area to locate the ASADMIN user.
Click the Update icon next to the ASADMIN user to open the Update User window.
Remove the Active To date field and click Apply .
Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.
Enter the new password twice and click Submit .
After the ASADMIN user is enabled from Oracle E-Business Suite, you must perform the following tasks:
Verify if the ASADMIN user has the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT) role in wf_user_roles.
If the 'Apps Schema Connect Role' role is not present in the wf_user_roles for the ASADMIN user, then run the 'Workflow Directory Services User/Role Validation' concurrent program to grant the role.
Reset the ASADMIN password in the file system.
Update the file as shown below to reset the password:
<user> <name>ASADMIN</name> <display-name>Default Apps SOA User</display-name> <description>Used by SOAProvider for DB connection</description> <credentials> !<NEW PASSWORD> </credentials> </user>
Note: The password should be preceded by a '!' (Exclamation) so that when OAFM is started, it gets encrypted. For example, if the password is 'welcome', then you have to change it to "!welcome". In addition, the password of ASADMIN should be synchronized between system-jazn-data.xml file and the database through the application user interfaces.
Caution: Do not use the same password given in this example for "ASADMIN" user. Use a different password instead to avoid some potential security risk in your system.
Bounce the middle-tier and retry the generation process.