Cisco Cisco Collaboration Server (CS) User Guide
form security rules for your application, both about who can manipulate the resource
and how they manipulate it, and about the resource's limits to the server's
and how they manipulate it, and about the resource's limits to the server's
computational resources such as disk space and memory usage.
Begin by opening a browser and going to the <server
name>/Cisco_CS/html/capi/capiconfig.jhtml page. Here you will see a section
labeled "Existing Resources" and a field to enter a new Resource Type. Type a name
labeled "Existing Resources" and a field to enter a new Resource Type. Type a name
for your Resource and click the add button. You have just created your Resource
Type, and now you may configure it.
Type, and now you may configure it.
Choose your object model from the list provided under the `Resource' sub-heading.
Enter the HTML page to push in the browser when someone joins your session under
the `Resource' sub-heading. This page will most likely contain your collaborative
the `Resource' sub-heading. This page will most likely contain your collaborative
applet.
If you want to use the session's history, check the `Enable History' box under the
`History' sub-heading and put a value for the maximum history size in the area
below it. The server will only maintain a history list of the size indicated in that box.
below it. The server will only maintain a history list of the size indicated in that box.
If you have memory limitations, are dealing with a large amount of data in each
session, or expect a large number of simultaneous sessions on one server, you may
session, or expect a large number of simultaneous sessions on one server, you may
want to decrease the maximum event buffer size under the `Events' sub-heading. If
a participant's connection to the server is temporarily interrupted, the server will
store that participant's events for a period of time until either the participant
a participant's connection to the server is temporarily interrupted, the server will
store that participant's events for a period of time until either the participant
reconnects to the server or the server times that participant out. This value specifies
a maximum number of events to maintain per participant, and if this value is
a maximum number of events to maintain per participant, and if this value is
exceeded, a reconnecting caller will receive an error and must handle the reconnect
differently.
differently.
Decide what sets of events you would like recorded to the database, and check the
appropriate check boxes under the `Database' sub-heading.
appropriate check boxes under the `Database' sub-heading.
Under the `Load/Save' sub-heading, decide if you would like the server to support
load and save operations. The session's history may also be loaded and saved. Check
the appropriate checkboxes.
load and save operations. The session's history may also be loaded and saved. Check
the appropriate checkboxes.
Under the `Leadership' sub-heading, decide if you would like leadership to be
dependent on the Cisco Collaboration session. If this is a stand-alone session, this
dependent on the Cisco Collaboration session. If this is a stand-alone session, this
value is ignored.In some circumstances, you may want a participant's events to
affect the object model even if that participant is not the leader. Normally, no
affect the object model even if that participant is not the leader. Normally, no
participant but a leader if it exists may modify the objects in the object model. If this
is the case, enter those event types' values in the list under the `Leadership' sub-
is the case, enter those event types' values in the list under the `Leadership' sub-
heading.
Finally, choose what information about the session and each participant your
application will have access to. If, for example, you uncheck the `Phone Number'
application will have access to. If, for example, you uncheck the `Phone Number'
box, then an application will not be allowed to get the phone number for a
33