| Oracle® Web Conferencing Administrator's Guide Release 2 (2.0.4.3) Part Number B10877-03 |
|
|
View PDF |
| Oracle® Web Conferencing Administrator's Guide Release 2 (2.0.4.3) Part Number B10877-03 |
|
|
View PDF |
Oracle Web Conferencing lets you easily configure a single deployment instance to meet the requirements of various lines of business, by creating individual sites and customizing system, application, and conference level properties for those sites.
Web Conferencing sites are created by the business administrator. (See "Setting User Roles" for details about assing a user the business administrator role.) For every site created, the integrating application or line of business uses a unique authentication token along with the site ID to communicate with the Web Conferencing Application. Creating a site provides the following benefits:
Customized system, application, and conference properties.
Support for custom integrated flows which can bypass the Web Conferencing Application.
Support for custom Web Conferencing Console behavior based on the properties set for the site.
Site-level reports which give the same depth and breakdown of data as the global Web Conferencing site reports.
Custom user interfaces, including a separate Oracle Web Conferencing prelogin application page with full support for listing public conferences only for the specific site.
Custom branding to uniquely identify the integrating site/line of business.
The global site is pre-created and cannot be deleted. By default, all users belong to site "iMeeting," which is a global site. However, a user can belong to more than one site.
The Real-Time Collaboration system uses the concept of site to provide a customized ÒviewÓ of the Oracle Web Conferencing deployment, for each of the integrating applications. In an enterprise, a single deployment of the Real-Time Collaboration system can be used by various integrated applications supporting lines of business, such as a sales department, a support department, etc. To support the integrating applications, you create sites with unique site IDs.
An application in an enterprise can integrate with Oracle Web Conferencing in two ways:
It can programmatically invoke Web Conferencing functions using Oracle Real-Time Collaboration Integration Service calls or,
If the application has a browser-based interface, it can invoke the Oracle Web Conferencing Application pages directly.
In either case, a site ID enables the Real-Time Collaboration system to provide a customized service for each integrating application.
The Oracle Web Conferencing administrator creates a site by providing a unique site name, display name, and description for the site. To create a site, the administrator does the following:
Log in with an administrator account (the account must have been assigned the businessadmin role as described in "Setting User Roles").
Click the Sites tab.
Click the Create Site button.
Create a site, assigning it a Site Name (required) and optional display description.
Click Apply
The Real-Time Collaboration system then registers the site and provides the administrator with a site ID and an authentication token, both of which are system-generated. An application that wants to integrate with the Real-Time Collaboration system can use the new site ID to make the appropriate calls.
For Oracle Real-Time Collaboration Integration Service calls, the site ID is passed as one of HTTP header fields in the HTTP request to invoke the service. For any application Web page that provides a link to the Oracle Web Conferencing Application page, it can provide the site ID as a URL parameter. For example, the following URL can be used to provide a customized view of Oracle Web Conferencing for site 123456.
http://<hostname>:<port-number>/imtapp/app/prelogin.uix?siteID=123456
Entering this URL into a browser returns a page that has the look and feel and contents specified for site 12345 using any Web Conferencing properties, as described in "Customizing Site Properties". Any conferences created from the application pages will have the attributes defined for conferences for that site.
After you have created a site, you can then set up site-specific properties to control the interaction of the integrating site with Oracle Web Conferencing. For all properties that you do not change, the values of the corresponding default Web Conferencing site apply. See Chapter 5, "Configuration" for descriptions of properties that can be set at the site level.
There are two broad classes of properties that affect how users interact with the site:
Application Properties: Change the look and feel of the Oracle Web Conferencing Application pages. Examples of such properties are the co-branding name that appears at the top of each application page, the e-mail address of the Contact Us page, the number of rows displayed for each table in the application page, and so on.
Conference Properties: Change the attributes of any conference, whether it is invoked from the application pages or from the integration service calls. Examples of such properties include the Startup (collaboration) Mode of the conference, the availability of chat during the conference, and so on.
Figure 9-1, "Site Property Inheritance" shows how the various property values in Oracle Web Conferencing are inherited and set. When a site is created, it inherits the default values of all the properties from the system settings. For each site the administrator can set various conference-level and application-level properties to override the default values. Some of the conference-level properties can be changed from inside the Web Conferencing Console when the conference is running. For example, the default setting for the system is to set the start mode of each conference to Cobrowse mode. When a site is created, this default value is inherited for that site. The site administrator can override this default value by changing the StartupMeetingMode property to, for example, Desktop Sharing mode.
