Secure way of starting and stopping oracle application services

Configure Concurrent Manager for START and STOP without the APPS password

         Oracle applications DBA needed to know the APPS username and password in order to start or stop the Oracle application services on an application tier that was running the Concurrent Manager. Considering the security concerns, because most Operating Systems allow all machine users to read a program’s command line arguments, the password may be intercepted.

Starting with Release 12.1.3 it is possible to create an applications user (FND User) with the responsibility

”Concurrent Manager Operator” and use this user’s username and password to start and stop the Oracle application services.

This can implemented by following below steps

      ·  Creating a new application user, say CONCOPER and assign the ”Concurrent Manager Operator” responsibility to this user

       ·        On the application tier update the following 4 variables in the autoconfig context file

Autoconfig Variable	New Value
s_cp_user	CONCOPER (or the one you created)
s_cp_password_type	AppsUser
s_cp_resp_shortname	FND
s_cp_resp_name	Concurrent Manager Operator

       ·          Run autoconfig on the application tier(s)

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 Application users username and password

rather than the APPS username and password.

For example

[applmgr@app01]$ adstrtal.sh -secureapps

 Enter the Applications username: CONCOPER

 Enter the Applications password:

thanks,

Edwin.K