replay

Replays Oracle Smart View for Office, REST API, or EPM Automate load on an environment to enable performance testing under heavy load to verify that user experience is acceptable when the service is under specified load.

You must create a replay file that identifies the activities that should be executed on the service. See Preparing to Run the Replay Command for details information on how to create the replay file.

Applies to

Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Tax Reporting, Account Reconciliation, Profitability and Cost Management, Enterprise Profitability and Cost Management, Oracle Enterprise Data Management Cloud, Narrative Reporting, Sales Planning, and Strategic Workforce Planning.

Required Roles

Service Administrator, Power User, User, Viewer

Usage

epmautomate replay REPLAY_FILE_NAME.csv [duration=N] [trace=true] [lagTime=t] [encrypt=true|false] where:

• REPLAY_FILE_NAME is a CSV file that stores the activities to be executed on the environment.
• Duration, optionally, indicates the number of minutes for which activities are executed on the environment.

  Activities in the HAR file are run one time if this value is not set. If the activities in the HAR file are completed within the time specified by this parameter, EPM Automate reruns the HAR file until the activities are complete. For example, assume that you set duration=10 to replay a HAR file that takes three minutes to run. In this scenario, the replay command runs the HAR file activities four times (lasting 12 minutes) until the fourth iteration is complete.

• trace=true is an optional setting that instructs EPM Automate to create trace files in XML format.

  If this optional setting is specified, EPM Automate creates one folder for each HAR file included in the replay CSV file and stores all related trace files in it. For each activity in the HAR file, EPM Automate generates one trace file that contains Smart View response. Trace files are named trace-N.xml; for example, trace-1.xml where N is a counter that starts at 1.

  The folders that store the trace files are created in the directory from which EPM Automate is run. EPM Automate uses a combination of current system time of the environment and HAR file name in YYYY_MM_DD_HH_MM_SS_HAR_FILE_NAME format to name the folders. For example, if HAR file name is forecast1.har, the folder name may be 2016_06_08_10_21_42_forecast1.

• [lagTime=t], optionally, specifies the number of seconds that the command should wait between the execution of each HAR file included in the replay file. Default is 5 seconds.

  The command displays an error if you specify a value less than 5 seconds. Negative numbers (for example -1) and fractions (for example, 1/2) are not acceptable as the parameter value. Decimal values are supported.

  After initiating the execution of the first HAR file, the command waits for the number of seconds specified by this parameter to initiate the processing of the next HAR file. Because user activities are not usually initiated simultaneously, setting this parameter helps to create a more realistic simulation of load on an environment.

  For example, assume that you want to simulate the load of 1000 users signing on to an environment during the peak hour to perform activities. You can create HAR files to simulate these sessions and then run this command with a lag time of 6 seconds to replicate the load exerted on the environment.

• encrypt=true|false, optionally, specifies whether to encrypt all passwords included in the replay file. Default is true. A random encryption key is used to encrypt the password.

See A Sample Replay Session for detailed steps involved in executing this command.

Example

epmautomate replay forecast1.CSV duration=60 lagTime=5.6