How do I use simulateConcurrentUsage in Oracle EPM?

Use the EPM Automate command: epmautomate simulateConcurrentUsage INPUT_FILE.zip. The input ZIP must contain a requirement.csv file defining test cases and supporting input files. Upload the ZIP to inbox first using the uploadFile command.

What is simulateConcurrentUsage in Oracle EPM Cloud?

simulateConcurrentUsage is an EPM Automate command that simulates multiple users performing operations simultaneously such as opening forms, saving data, and running business rules. It measures response times under load for performance validation.

Why does simulateConcurrentUsage fail with status failed?

A common cause is the user.csv file format. Remove the header row from the CSV. Also ensure the ZIP file contains the individual files (requirement.csv, input files) directly, not inside a subfolder.

Form Performance and Security Testing with simulateConcurrentUsage

The simulateConcurrentUsage EPM Automate command is one of the most powerful yet underutilized tools available to Oracle EPM administrators. It allows you to simulate multiple users performing operations simultaneously — opening forms, running business rules, saving data — and measure the response times under load.

What You Can Test

The command supports simulating concurrent form opens, form saves (including forms with associated business rules), ad hoc grid operations, and data rule executions. You can specify the number of simulated users, iteration count, and lag time between user actions.

Security Testing Angle

Beyond performance, simulateConcurrentUsage is valuable for security validation. By simulating different users with different security roles, you can verify that your security model holds under concurrent access — ensuring users only see the data they should see, even under load.

Practical Tips

From real-world testing: the user.csv file does not need a header row — removing it resolves a common "failed" status issue. The command can now be run with Service Administrator credentials (previously required Identity Domain Administrator). Always test in your Dev environment first.