Configuration and Administration
Data Source Manager: Connection Tab
This page is accessed via Configuration and Administration > System Administration > Data Source Manager.
Note: Cloud users do not have access to this page. OnPrem users must be a DBA to access this page. These screens should only be used by experienced database administrators (DBAs).
A data source in Oracle Transportation Management contains all information needed to establish JDBC connections. For example:
- a JDBC driver and connection
- a TNS name for integration web utilities
- a schema for metadata retrieval
- an encrypted Oracle RDBMS user password
- a default VPD user
- a SQL command to run on initialization of the connection
A data source points to a physical database which represents the physical Oracle RDBMS instance. Multiple data sources can point to the same database, with a single database representing the primary application database. A data source can represent a single connection or a pool of connections.
Creating a Data Source
- Enter a Data Source ID.
- Select a Domain Name.
- Select a Manager from the drop-down list. This is not editable after it is added.
- Enter a TNS Name.
- Enter a Schema.
- Enter an Edition. This is the database edition name used by the system.
- Select the Profile Leaks check box if you want to run a diagnostic tool to determine who is holding connections in the pool.
- Select a Database from the drop-down box. GC3 is the current OTM database. ODS is an offline data store, typically archived OTM data.
- Enter a Database User.
- Enter a password for the user in the Database Password field, and then reenter the password in the Retype Database Password field.
- Enter a startup command in the Startup Command field.
- Enter an Oracle Transportation Management User.
- Select the Multi-User check box, if you want the VPD to be reset.
- Enter a JDBC URL in the JDBC URL field. If you are using an external data source defined in WebLogic, then preface the URL with "jndi:", but without quotes. So it would look like: jndi:<data source name>.
- Enter a JDBC driver.
- Click the Connection Pool Specification button.
Continue defining a database source on the Pool tab.