Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Business Process Designer Administration Guide for Financial Services > Workflow Policies Server Administration > Creating Database Triggers >
Running the SQL Script File
Once Generate Triggers has completed, run the SQL script file if the EXEC parameter is FALSE.
To run the SQL script file
- Connect to the database server as the Siebel tableowner using your RDBMS vendor's SQL tool (for example, ISQL for Microsoft or SQL*Plus for Oracle).
- Run the SQL script file specified by the Trigger File Name parameter. The default file name is TRIGGER.SQL. The default location of this file is the root of the directory that the Siebel Server was installed in. For example, this might be:
C:\siebsrvr\trigger.sql
- Verify that no errors are reported.
For example, the policy administrator, Bill Stevens, has finished creating policies in the test Siebel Client and wants the database triggers set in the Siebel database for the new policies. Using the Generate Triggers component, he sets the file output name.
This creates a file, TRIGGER.SQL, for the database administrator containing all the triggers that need to be modified or created in the test database for these policies.
The database administrator then runs the following command in SQL*Plus to create the triggers in the Oracle database:
SQL>@<
path
>\mytrig.sql
The successful creation of each database trigger in the Oracle database is indicated on the screen. For information on the syntax required for other databases, refer to your database documentation.
NOTE: On an MS SQL server database, execute the script trigger.sql as the database owner (dbo) login for the Siebel database.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Business Process Designer Administration Guide for Financial Services Published: 22 May 2003 |