Last updated on FEBRUARY 22, 2017
Applies to:Oracle Applications DBA - Version 12.2 and later
Information in this document applies to any platform.
Oracle E-Business Suite Maintenance Guide Release 12.2 is saying that we can use -secureapps options for adstrtal.sh.
Oracle E-Business Suite Setup Guide
Part Number E22953-13
Starting and Stopping the Concurrent Manager with the Concurrent Manager Operator User
Traditionally the operator starting and stopping the application services needed to know the APPS username and password
in order to start the application services on an application tier that was running the Concurrent Manager.
Starting with Release 12.1.3, it is possible to create an Oracle E-Business Suite user (FND User) with the responsibility
”Concurrent Manager Operator” and use this user's username and password start and stop the application services.
The procedure is the following:
1. Createa new user, for example, "CONCOPER", and assigning the ”Concurrent Manager Operator” responsibility to this user.
2. On the application tier, update the following four variables in the AutoConfig context file, as listed in the following table:
AutoConfig Variable New Value
s_cp_user CONCOPER (or the one you created)
s_cp_resp_name Concurrent Manager Operator
Following this change, the application tier services can be started and stopped by calling adstrtal.sh and adstpall.sh with
the -secureapps option and the script will prompt for the Oracle E-Business Suite user's username and password rather
than the APPS username and password.
[applmgr@app01]$ adstrtal.sh -secureapps
Enter the Applications username: CONCOPER
Enter the Applications password:
However, one can't start EBS by "adstrtal.sh -secureapps" even if they set their EBS as the manual says.An error occurs in adadminsrvctl.sh as follows.
There is no change.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms