Run .SystemProperties. The System Properties window is displayed. On the Paths tab, the Specify Database Driver Classpath checkbox is selected by On the Database tab, enter all the necessary JDBC connection information in the Click OK.

Managing System Processes 3-9 Running the standalone version of an application offers greater security than browser applets, and enables you to send passwords without having them captured or copied from the web or a network. ■ Section 3.4.2.1, Configuring a SystemDatabase Provider for Standalone Mode ■ Section 3.4.2.2, Configuring a JDBC Database Driver for Standalone Mode ■ Section 3.4.2.3, Configuring an External Database Provider for Standalone Mode ■ Section 3.4.2.4, Running a Standalone Application on a UNIX System ■ Section 3.4.2.5, Running a Standalone Application on a Windows System

3.4.2.1 Configuring a SystemDatabase Provider for Standalone Mode

Oracle Content Server administration applications and utilities that can only run in standalone mode require specific configuration to run in an Oracle WebLogic Serverdomain with Oracle UCM and an Oracle Content Server instance. The configuration changes for a standard non-customized Oracle WebLogic Server connection are necessary to have the applications authenticate Oracle WebLogic Server users and to set up a JDBC connection to the Oracle WebLogic Server system database. To configure Oracle WebLogic Server system database connections: 1. As system administrator, use VNC or a similar tool such as putty or Xming to navigate to the DOMAIN_HOMEucmcsbin directory. For example: MW_HOME user_projectsdomainsucm_domainucmcsbin

2. Run .SystemProperties. The System Properties window is displayed.

3. On the Paths tab, the Specify Database Driver Classpath checkbox is selected by

default, so you must enter a path to a JDBC driver for your system database in the Database Driver Classpath field. The Oracle driver ojdbc6dms.jar is provided with the Enterprise Content Management install in the following directory. MW_HOME oracle_commonmodulesoracle.jdbc_11.1.1ojdbc6dms.jar Important: Before you can run Oracle Content Server administration applications in standalone mode, additional configuration is required to authenticate the applications on Oracle WebLogic Server and to have a JDBC connection to the system database and access to the Oracle WebLogic Server database connection. See Configuring a SystemDatabase Provider for Standalone Mode on page 3-9 and Configuring an External Database Provider for Standalone Mode on page 3-11. If a standalone application is required to connect to an SSL-enabled database where digital certificates are used for authentication, then the database root CA certificate must be imported into the standard Java key store that the application uses to check trusted sources. For configuration details, see Importing a Database Root CA Certificate into the Key Store for a Standalone Application in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. 3-10 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

4. On the Database tab, enter all the necessary JDBC connection information in the

fields for your system database database type, database user name, database user password, and so on.

5. Click OK.

You should now be able to run a standalone application. For example, as the Administrator user you created on the Oracle Content Server instance, run .BatchLoader.

3.4.2.2 Configuring a JDBC Database Driver for Standalone Mode