This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:oracle:databases [2011/03/31 16:27] doc |
integration:rdbms:oracle:databases [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| **[[integration:rdbms:oracle:databases|Databases]]** | | **[[integration:rdbms:oracle:databases|Databases]]** | | ||
| [[integration:rdbms:oracle:tables|Tables]] | | [[integration:rdbms:oracle:tables|Tables]] | | ||
| + | [[integration:rdbms:oracle:constraints|Constraints]] | | ||
| + | [[integration:rdbms:oracle:datatypes|Datatypes]] | | ||
| [[integration:rdbms:oracle:queries|Queries]] | | [[integration:rdbms:oracle:queries|Queries]] | | ||
| [[integration:rdbms:oracle:updates|Updates]] | | [[integration:rdbms:oracle:updates|Updates]] | | ||
| - | [[integration:rdbms:oracle:storedproc|Stored Procedures]] | | ||
| [[integration:rdbms:oracle:example|Example]] | [[integration:rdbms:oracle:example|Example]] | ||
| Line 25: | Line 26: | ||
| <code> | <code> | ||
| - | create database "STAR" | + | create database "SIMPLE" |
| type oracle | type oracle | ||
| version "11" | version "11" | ||
| - | user "myuser" | + | user "simple" |
| - | password "mypassword" | + | password "simple" |
| index_directory "idx" | index_directory "idx" | ||
| - | in "star.xml"; | + | in "simple.xml"; |
| </code> | </code> | ||
| Line 39: | Line 40: | ||
| <code> | <code> | ||
| - | create database "STAR" | + | create database "SIMPLE" |
| type oracle | type oracle | ||
| version "11" | version "11" | ||
| - | user "myuser" | + | user "simple" |
| - | password "mypassword" | + | password "simple" |
| - | service "star" | + | service "simple" |
| index_directory "idx" | index_directory "idx" | ||
| - | in "star.xml"; | + | in "simple.xml"; |
| </code> | </code> | ||
| === Oracle Security === | === Oracle Security === | ||
| - | Omnidex uses a single user and password to access an Oracle database. Oracle database administrators should provide an appropriate user and password that gives access to all of the database objects referenced in the Omnidex Environment Files. | + | Omnidex provides two methods of supporting Oracle security. |
| - | When connecting to an Omnidex Environment File, it is generally not possible to pass different user and passwords dynamically; however, there is an exception to this rule. The user and password can reference [[appendix:reference:envvar:home|environment variables or shell commands]]. This can provide a rudimentary mechanism for providing dynamic user and passwords. Care should be taken when using this approach, though. All users passed should have access to all database objects declared in the Omnidex Environment File, and should also have access to all rows in the tables. | + | * Administrators can register a user and password in the Omnidex Environment File. This user and password will always be used to access the Oracle database, and no users and passwords will be needed from the application. |
| + | * The application can pass a user and password in the [[dev:connections:home|Omnidex Connection String]]. This user and password is then passed directly to Oracle to access the database. | ||
| + | One of these approaches must be used to allow connections to the Oracle database. Administrators should insure that the user and password provides access to all of the database objects referenced in the Omnidex Environment Files. | ||
| ===== ===== | ===== ===== | ||