- style
runScript
- Kari Draheim (Unlicensed)
- Jack Reynebeau
- Dan Reynebeau
Executes a SQL script. This operation takes the SQL script and processes each statement in the database using JDBC.
Please note that the statements in the SQL files must be delimited by a semi-colon. Also this operation does not support the execution of Oracle PL/SQL statements (See runPLSQLScript operation).
Environment/Instance Properties
Property Name | Required | Description |
|---|---|---|
| Yes | The JDBC URL of the database. |
| No | The username that will be used to connect. |
| No | The password for |
| Yes | Classpath for locating the JDBC Driver (e.g. for Weblogic - {ORACLE_HOME}/oracle_common/modules/ oracle.jdbc_11.2.0/ojdbc6.jar). |
Project Properties
Property Name | Required | Description |
|---|---|---|
|
|
|
Inputs
Input Name | Required | Description |
|---|---|---|
| No | The username that will be used to connect with. This input takes precedence over the environment instance scoped |
| No | The password for |
| Yes | The name of the script to execute. |
| No | This option allows destructive statements to be ran. See the note below. |
Outputs
Output Name | Required | Description |
|---|---|---|
|
|
|
Artifacts
This operation consumes one or more SQL files, and an optional sequence file, from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
Endpoint Execution
This operation will randomly execute on one of the endpoint identified during selection.
Special Considerations
The statements in the SQL files must be delimited by a semi-colon. Also note that this operation does not support the execution of Oracle PL/SQL statements (See runPLSQLScript operation).
The FDJDBC_RUN_DESTRUCTIVE input allows a mechanism for disallowing certain destructive SQL commands. If the input is set to true: DROP, DELETE, and TRUNCATE will be allowed within the script. If the input is set to false: the plugin operation will abort with a validation error prior to running any of the commands in the script. This check cannot stop malicious actors, but instead helps to provide some security against accidental running of destructive commands. It is up to the customer to decide whether they want to allow such commands.
Sequence File for multi-file processing:
If you want to execute multiple SQL scripts, instead of specifying an SQL file within the FDJDBC_INP_FILE_NAME input, a file containing an ordered list of SQL files to execute may be used. The plugin will detect whether a SQL file or a sequence file has been specified based on the format of the file. The format of a sequence file is as follows:
!SEQ / CreateHR.sql / GrantHR.sql / ADFStateMgt.sql
The !SEQ line (must be the first line) at the top of the file indicates a sequence file. After the sequence line, an ordered list of files to run follows.
Replacement Properties
See Appendix.
- style