Implementation Guide for Oracle Self-Service E-Billing > Customizing Oracle Self-Service E-Billing >

About the Command Center Application

The Oracle Self-Service E-Billing Command Center is a separate application and is packaged as a separate EAR file. You deploy the Command Center on a separate application server. A system administrator uses the Command Center to run batch jobs and monitor the production environment. Command Center consists of the following components:

• Command Center User Interface. The Command Center user interface is based on Servlet-JSP technology, not struts and tiles.
• Jobs. A Command Center job is a process which an administrator for Oracle Self-Service E-Billing must schedule and run using the Command Center console (UI). Oracle Self-Service E-Billing comes with a set of predefined jobs, such as OLTP loader, batch generator, Hierarchy importer, and so on. A job consists of one or more tasks, and each task performs a specific piece of the processing. Each task is implemented as an EJB and has its own configuration parameters which the administrator also configures using the Command Center UI. When a job runs, the tasks that make up each job run sequentially. For more information about configuring and running jobs in the Oracle Self-Service E-Billing Command Center, see Administration Guide for Oracle Self-Service E-Billing.
• PWC API. A set of APIs used to manage jobs.

Command Center EAR File

The Command Center EAR file is in the EDX_HOME/J2EEApps/commandcenter/weblogic/command-center-weblogic-6.2.ear directory (or the EDX_HOME\J2EEApps\commandcenter\weblogic\command-center-weblogic-6.2.ear directory on Windows). In the directory, EDX_HOME is the directory where you installed Oracle Self-Service E-Billing:

In general, you are not expected to modify this EAR file during deployment. Deploy the Command Center on a separate application server.