1.5 Launching Oracle Content Server Administration Applications

You can launch Content Server administration applications using these methods:

Running Administration Applications as Applets
Running Administration Applications in Standalone Mode

1.5.1 Running Administration Applications as Applets

You can run several of the Content Server administration applications as applets from any Web browser with access to the content server. Applets are convenient for remote administration.

Note:

The Batch Loader, Component Wizard, System Properties, and Content Server Analyzer utilities cannot be run as applets; for security reasons, they must be run in standalone mode from the computer where the content server is deployed. See "Running Administration Applications in Standalone Mode" for details.

Some functions that are available in the standalone version of an application are not available from the applet version. See the documentation for each application for more information.

To run an administration application as a Java applet within a Java-enabled browser:

Open a browser window.
Log in to the content server as an administrator.
Click the Administration tray link in the portal navigation bar.
Click the Admin Applets link.

1.5.2 Running Administration Applications in Standalone Mode

You can run several Content Server administration Java applications in standalone mode from the computer where a content server is deployed. Some of the applications are the same as the applets accessed using a Web browser, such as Configuration Manager and Repository Manager. Some applications such as System Properties and Batch Loader can only run in standalone mode. The method required to start these programs differs slightly between Windows and UNIX installations.

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.

Important:

Before you can run 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 WebLogic Server database connection. See "Configuring System Database Provider for Standalone Mode" and "Configuring External Database Provider for Standalone Mode".

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.

1.5.2.1 Configuring System Database Provider for Standalone Mode

Content Server administration applications that can only run as standalone applications require specific configuration to run in an Oracle WebLogic Server deployment for Content Server. 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:

Create a local (internal) content server user with Admin rights, using the User Admin applet in the browser interface.
Run ./SystemProperties.
Using VNC (or a similar tool such as putty or Xming), go to the domain/ucm/cs/bin directory. For example, /scratch/user/bea/user_projects/domains/domain/ucm/cs/bin
If you have already selected the Oracle thin client for JDBC connection on the Database tab, you can skip this step. Otherwise, on the Paths tab, in the Java Classpath field, enter a path to a JDBC driver for your system database. An Oracle driver is provided in the Enterprise Content Management install, for example:
```
/scratch/user/bea/ecm/ucm/idc/shared/classes/ojdbc5.jar
```
In the Database tab, enter all the necessary JDBC connection information for your system database (database type, database user name, database user password, and so on).
Click OK.

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

1.5.2.2 Configuring External Database Provider for Standalone Mode

You can create an external database provider in Content Server for standalone applications to connect directly to a database with JDBC without using the SystemDatabase Provider for the Oracle WebLogic Server data source. For standalone applications to use OracleTextSearch, you must configure the external database provider to include the JDBC connection information.

By default, the configuration of an incoming provider does not include values for JDBC Driver and JDBC Connection String. You must add these values, but be careful not to change the provider name because you cannot rename an existing provider. To change the name of a provider, you would need to delete it and then add it again.

For information about making changes to a provider, see "Editing Provider Information" in the chapter "Managing System Settings and Processes" in this guide.

1.5.2.3 Configuring JDBC Database Drivers for Standalone Mode

Oracle provides Fusion Middleware datadirect JDBC drivers for MS SQL Server and DB2 databases to support Content Server standalone applications. To configure Content Server so the standalone applications will work with the drivers:

Obtain the JDBC driver and fmwgenerictoken.jar from either the latest label in the DATADIRECT_MAIN_GENERIC series or from the Oracle UCM label.
Include the drivers in your class path by setting the following code, using your path to the driver jars:
```
JAVA_CLASSPATH_jdbcdrivers=path_to_driver_jars
```

Use the driver setting for the appropriate database. You must provide the server name, port number, and database name.

MS SQL Server:

JdbcDriver=com.oracle.fmwgen.jdbc.sqlserver.SQLServerDriver
JdbcConnectionString=jdbc:fmwgen:sqlserver://server1:port;DatabaseName=database

DB2:

JdbcDriver=com.oracle.fmwgen.jdbc.DB2.DB2DriverJdbcConnectionString=jdbc:fmwgen:db2://server1:port;DatabaseName=database

Restart the Content Server.

1.5.2.4 Running a Standalone Application on Windows Systems

Follow these steps to run a standalone Content Server administration application on a Windows operating system:

Select the application from the Windows Start menu:
- To run an administration application, from the Start menu select Programs, Content Server, Content Server-instance, Applications, and then the application.
- To run an administration utility, from the Start menu select Programs, Content Server, Content Server-instance, Utilities, then the utility.
For all applications except for Component Wizard and System Properties, a login screen is displayed. For Component Wizard and System Properties, the main screen of the application is displayed. It may take several seconds for the login screen or the application screen to appear, or the screen may be hidden by other windows.
Enter the administrator login name and password.
Click OK.

The main screen of the application is displayed.

1.5.2.5 Running a Standalone Application on UNIX Systems

Follow these steps to run a standalone Content Server administration application on a UNIX operating system:

Navigate to the DomainHome/ucm/cs/bin/ directory. Executable applications are listed.
Enter ./application_name, where application_name is the name of an executable file. If an application is not listed, it can be entered as a parameter to the IntradocApp application, as in this example:
```
%DomainHome%/bin/intradocApp workflow
```
Press Enter.

For all applications except for Component Wizard and SystemProperties, a login screen is displayed. For Component Wizard and SystemProperties, the main screen of the application is displayed.
Enter the administrator login name and password.
Click OK.

The main screen of the application is displayed.