1 Introduction to Administering Oracle On Track Communication

Oracle On Track Communication is an Oracle Web Logic Server (WLS) Fusion Middleware application. The application includes an On Track Communication Administration Console, which you can use to configure On Track, manage users and groups, deploy add-ons to the application (Gadgets and Features), set default policies and rules, and enable or disable the application for user access.

Every screen in the Oracle On Track Communication Administration Console includes a link to the Oracle On Track Communication Administration Console Help. Configuration tools provided in the console is described briefly in the help. You should use this administration guide to understand the purpose and context of administration procedures; use the help to find specific detail about console screens, buttons, fields, lists, and tools.

Where appropriate, this guide includes links directly to the relevant section or topic in the help.

See Also:

See the Oracle On Track Communication Administration Console Help for brief descriptions of administration tools provided in the Oracle On Track Administration Console.

Some aspects of On Track system configuration must be performed using WLS administration and configuration tools. This guide focuses on the administration tasks which are performed using the Administration Console. Where necessary, you will be directed to WLS documentation for tasks which must be performed using WLS.

Some configuration must be performed using Java Monitoring and Management Console (JConsole). This tool is available as part of the Java Developer Kit (JDK), installed as a prerequisite of On Track. This tool is typically located at the following path:

$JDK_HOME/bin/jconsole.

Oracle On Track Communication makes use of an Oracle Database for storage of both configuration and user data. Some configuration and maintenance tasks require access to the database. Where necessary, you will be directed to Oracle Database documentation for tasks which must be performed using SQL*Plus and other database tools.

See Also:

See the Oracle On Track Communication Installation Guide for details on how to use WLS for initial deployment and configuration of Oracle On Track Communication.

Oracle On Track Communication includes the ability to customize and deploy add-ons to the On Track Communication client. These add-ons are called Gadgets and Features.

Oracle On Track Communication Deployment Scenarios

Oracle On Track Communication runs as an Oracle Web Logic Server (WLS) Fusion Middleware installation application within the Web Logic Server environment. You can have multiple instances on the same or separate machine. You can create multiple tablespaces in your Oracle Database, each for a separate instance of On Track. Any On Track instance can include an instance of the administration console.

If you have multiple On Track instances, they communicate with each other using SSL. For more information about configuring SSL, see the Oracle On Track Communication Security Guide.

For more information about how to configure Oracle On Track Communication to suit your organization's needs, see the Oracle On Track Communication Installation Guide.

Oracle On Track Communication Administration Console

The Oracle On Track Communication Administration Console is your primary interface for configuring the On Track application, managing users and groups, deploying add-ons to the application (Gadgets and Features), setting default policies and rules, and enabling or disabling the application for user access.

Connecting to Oracle On Track Server Instances with the Administration Console

You can use any instance of the administration console to connect to any On Track instance by entering the connection information on the login page.

You can access the console on any On Track server by navigating to the following URL on that server:

https://<server_name>.<domain>:<port>/ontrackAdmin/

The default server instance is defined in the web.xml file for the On Track Application running on the server you connect to. If the default server instance is the server you want to access, you can leave the Override default connection with the following parameters: section blank.

The following parameters in the web.xml file determine the default server connection used by the administration console login page:

• server.connection.protocol: The default value is https.

• server.connection.host: The default value is https localhost

• server.connection.port: The default value is https 443

See Also:

For step-by-step instructions on connecting to any On Track instance with the administration console, see "Connecting to an On Track Instance" in Oracle On Track Communication Administration Console Help.