Performing Silent Configurations
Silent configurations automate the configuration process so that you can configure Oracle Enterprise Performance Management System products on multiple computers without manually specifying configuration settings on each machine.
To enable silent configurations, record your configuration settings in a response file. You can then run a silent configuration from the command line, using the configuration options that were saved in the response file.
Note:
If you are performing a silent configuration using Remote Desktop, run it using an admin console session. (Launch Remote Desktop using mstsc /admin
).
To record configuration settings and run a silent configuration:
You can also record configuration settings from within EPM System Configurator. To record configuration settings, during configuration, on the Configuration Confirmation page, click or select Save, browse to a location, specify a file name, and click or select Save. The file is saved in the same format as for silent configurations.
Silent response files are not compatible between earlier releases and Release 11.2. If you created silent response files for use with any earlier release of EPM System, you must re-create them for use with EPM System Release 11.2.
You can modify the response file later to change configuration options.
You can use the same silent response file in different environments even when each environment has a different set of passwords for the database, WebLogic, and the Oracle Hyperion Shared Services Admin user. For security reasons, in the generated silent file, password values are stored in encrypted format but EPM System Configurator also supports unencrypted format. Oracle recommends that you change the password properties for Database, WebLogic, and Shared Services in the silent file to the following format:
Database Password
<property name="password" encrypt="true">clearTextPasword</property>
Weblogic Admin Password in applicationServerDeployment section
<property name="adminUser">epm_admin</property>
<property name="adminPassword" encrypt="true">clearTextPasword</property>
Shared Services Admin Password in bean name="customConfiguration" for Foundation
<property name="adminUserName">admin</property>
<property name="adminPassword" encrypt="true">clearTextPasword</property>
Copy a version of the file for each environment and replace clearTextPassword with the appropriate password for that environment. After executing the silent file for each environment, for security reasons, if the file is writable by EPM System Configurator, the password is stored in the file in an encrypted format.