Interact | simulator|scenarioDataSource
These configurations are required to run Simulator Coverage Analysis scenario
jndiName
- Description
- Use this jndiName property to identify the Java Naming and Directory Interface (JNDI) data source that is defined in the application server (Websphere or WebLogic) for the Interact Design Time tables.
- Default Value
-
No default value defined.
Schema
- Description
-
The name of the schema containing the tables for the Interact design time data source module. Interact inserts the value of this property before all table names, for example, UACI_IntChannel becomes schema.UACI_IntChannel.
You have to define a schema. If you do not define a schema, Interact assumes that the owner of the tables is the same as the schema. It is required to specify schema name to run coverage scenario successfully.
- Default Value
-
No Default value defined.
type
- Description
- The database type for the data source used by the Interact Design time tables accessed by the Interact Simulator.
- Default Value
- sqlserver
- Valid Value
sqlserver | Db2 | Oracle| MariaDB
connectionRetryPeriod
- Description
- The ConnectionRetryPeriod property specifies the amount of time in seconds Interact automatically retries the database connection request on failure for the learning tables. Interact automatically tries to reconnect to the database for this length of time before reporting a database error or failure. If the value is set to 0, Interact will retry indefinitely; if the value is set to -1, no retry will be attempted.
- Default Value
- -1
connectionRetryDelay
- Description
- The ConnectionRetryDelay property specifies the amount of time in seconds Interact waits before it tries to reconnect to the database after a failure for the learning tables. If the value is set to -1, no retry will be attempted.
- Default Value
- -1
Error Handling for Simulator
This section lists the status codes the application writes into the table UACI_SimulationHistory which is present in the Interact Design time database.
In case of an error the application will show the scenario failed message on the Simulator run page. The detailed status code can be found in the database table UACI_SimulationHistory.
The following are the list of possible status codes that a scenario run history could have: // status code 0-99 are for information
| Status | Code | Severity level | Http Status | Possible UI message |
| SUCCESS | 0 | INFO | OK | Running simulation succeeded |
| RUNNING | 1 | INFO | OK | Running |
| CANCELING | 2 | INFO | OK | Cancelling |
| CANCELED | 3 | INFO | OK | Cancelled |
| EXPORTING_TO_CSV | 4 | INFO | OK | Exporting to CSV |
| EXPORTED_TO_CSV | 5 | INFO | OK | Exported to CSV |
// status code 101-999 are for errors
| Status | Code | Severity level | Http Status | Possible UI message |
| NOT_ENABLED | 101 | WARN | SERVICE_UNAVAILABLE | Simulation is not enabled on this run time server |
| ERROR_RETRIEVE_SCENARIO | 102 | ERROR | INTERNAL_SERVER_ERROR | Error retrieving the scenario information for simulation |
| INVALID_SCENARIO | 103 | ERROR | BAD_REQUEST | Invalid scenario information of simulation |
| ERROR_CREATE_RESULT_TABLE | 104 | ERROR | INTERNAL_SERVER_ERROR | Error creating the table for storing results for simulation |
| ERROR_RETRIEVE_AUDIENCE | 105 | ERROR | INTERNAL_SERVER_ERROR | Error retrieving audience IDs for simulation |
| ERROR_CONNECT_DATABASE | 106 | ERROR | INTERNAL_SERVER_ERROR | Error connecting to {0} database for simulation |
| ERROR_PERSIST_RESULT | 107 | ERROR | INTERNAL_SERVER_ERROR | Error persisting results to database for simulation |
| SCENARIO_NOT_FOUND | 108 | ERROR | NOT_FOUND | Cannot find a scenario ready to run |
| GENERIC_ERROR | 109 | ERROR | INTERNAL_SERVER_ERROR | Server error running simulation |
| ERROR_UPDATE_RESULT | 110 | ERROR | INTERNAL_SERVER_ERROR | Error updating result for simulation |
| ERROR_INVALID_IC | 111 | ERROR | BAD_REQUEST | Interactive channel is not deployed |
// // status code 1001 and above are for UI only, will not be stored in database
| Status | Code | Severity level | Http Status | Possible UI message |
| SIMULATION_ALREADY_RUNNING | 1001 | WARN | PRECONDITION_FAILED | A simulation is already running for this scenario |
| SIMULATION_NOT_FOUND | 1002 | WARN | NO_CONTENT | No ongoing simulation found for this scenario |
| SIMULATION_RUNNING | 1003 | INFO | OK | Running |
| SIMULATION_NOT_RUNNING | 1004 | INFO | OK | Simulation not running |