Skip to main content
Jump to: navigation, search

COSMOS UG Web Console

COSMOS Wiki > COSMOS Document Plan > COSMOS Manual Guide

COSMOS User's Guide Web Console section

Category: User's Guide

Owner Sheldon Lee-Loy
Bug # 218841
Due dates Schedule

Getting Started

The COSMOS User interface is a web application that is composed of a set of COSMOS web components that allows users to manage, query and locate data managers. A user can launch the COSMOS UI by pointing a browser to http://localhost:8080/COSMOSUI. This assumes that the COSMOS UI web application is deployed on the localhost at port 8080.

The initial page of the COSMOS Web User Interface displays three main panes. The left pane shows a list of data managers that are registered with the broker. The top right pane shows a detail view that is initially blank, while the bottom right pane shows a properties view that is also initially blank.

Demoi10 gettingstarted.jpg

Additional capabilities may be added to the COSMOS User Interface by providing new web components that can be integrated and configured for the COSMOS User Interface. The COSMOS Uset Interface is built on a framework that provides a list of predefined re-usable components, like query dialog boxes, CMDBf repsponse viewers, etc. The list of web components is outline under the COSMOS Web Component Library section.


Trouble Shooting

Configuration Options

There are several configuration options that are available in The COSMOS UI. These options are defined in the <tomcat-dir>/webapps/COSMOSUI/config/ file.

The following shows the available configuration options.

# DOJO toolkit javascript Location
# DOJO toolkit Base Path
# BASE URL of COSMOS UI Services
# List of resource bundles that contains jprop macro values
# A file that contains the BIRT report template deployment file 
# The COSMOS Report Viewer URL
# The EPR of the Broker
# The default page template

Let us look at some common use cases where one would change the above configuration options.

Use Case 1: The dojo toolkit is installed and deployed on another server or a new dojo toolkit version is available.

Configuration Action: We will need to set the DOJO_PATH and DOJO_BASE_URL properties to the new location of the dojo javascript file. Lets say that we want to use the dojo toolkit hosted on the AOL Content Delivery Network. The location of the dojo 1.0.2 toolkit is hosted at "". As a result we would modify the following properties.

# DOJO toolkit javascript Location
# DOJO toolkit Base Path

This change will configure the COSMOS UI to download the DOJO toolkit from the AOL Content Delivery Network.

Use Case 2: The end point reference of the COSMOS broker is deployed on a different host and port.

Configuration Action: We will need to set the BROKER_EPR to point to the new end point reference. Lets say that our broker EPR is at As a result we would modify the following properties.

# The EPR of the Broker

The other configuration options should be set to their default values and should only be modified if one wants to extend the functionality of the COSMOS UI. These configuration options are discussed in the developer's guide.

Related concepts

| CMDBf Specification Document

Back to the top