Show TOC

AdministrationLocate this document in the navigation structure

Use

During routine operation, you can manage the functions for collaboration in the portal and modify them as required to suit the current requirements of your company.

The following management tasks for collaboration are described below:

  • Handling the system

    • Starting and stopping the system

    • Backing up and restoring data

    • Load balancing in a distributed system landscape

  • Modifying the available services for collaboration

  • Modifying the functions for searching and displaying user data

  • Administering room templates and room part templates

  • Administering rooms and room-specific functions

  • Activating and deactivating SCF service types

  • Configuring asynchronous collaboration services

  • Configuring groupware integration

  • Configuring Real-Time Collaboration (RTC)

  • Configuring RTC Application Sharing Server

Handling the System

The table below lists the most important tasks for system handling:

Task

Description

Starting and stopping the component

SAP NetWeaver Collaboration can be started and stopped only together with SAP NetWeaver Portal .

See: Starting and Stopping the Portal

Load balancing in a distributed system landscape

Like the portal, SAP NetWeaver Collaboration can be operated in a distributed system landscape.

For the RTC (Real-Time Collaboration) application sharing server, you must also use the SAP Web Dispatcher for load balancing.

See: Running Application Sharing Server in a Clustered Environment

Backing up and Restoring Data

During backup and restore of collaboration data (that is stored in Content Management), the information about Backing Up and Restoring the Portal in the Technical Operations Manual for the portal applies.

Content and some of the collaboration configuration data are stored in the database.

As well as backing up the database, you have to back up the directory hierarchy of the /etc file system repository. This contains system and configuration data. By default, this repository is located at .../usr/sap/<SAP System ID>/SYS/global/config/cm/etc . Include this directory in the data backup and restore process for Collaboration.

Modifying the Available Services for Collaboration

The table below lists the tasks you can perform to modify the available services for Collaboration:

Task

Description

Modifying the configuration for making services available

You can determine which services are visible in the Collaboration Launch Pad (CLP), in the room member list , in the user details , and for each user throughout the portal.

You have the following options:

Modifying the Functions for Searching and Displaying User Data

The table below lists the tasks you can perform to modify the functions for searching and displaying user data

Task

Description

Modifying the user search function

In user management in the User Management Engine (UME), attributes are assigned to each system user (individual user, user group, or role) for which values can be entered in the corresponding user profile.

Based on the attribute values defined for the user search, users can use the user search function to search for system users.

You can change the configuration of the user search function delivered by SAP - the assignment of attributes to system users and the definition of the attributes relevant for the search - to suit the requirements of your company.

See: Configuration of the User Search Function

Modifying the Who's Who iView

By configuring the Who's Who iView, you can influence the search for users and the display of the results list.

See: Configuration of the Who's Who iView

Modifying the User Details iView

You can modify the User Details iView to suit your company requirements. You have the following options:

Modifying the CLP

If your company is not planning to allow users to set their own availability status, you can hide the corresponding iView component - the Awareness Status Selector (ASS) - in the Collaboration Launch Pad (CLP).

See: Hiding the Availability Status Setting in the CLP

Administering Room Templates and Room Part Templates

The table below lists the most important administration tasks for room templates and room part templates:

Task

Description

Changing existing templates

You cannot change the templates delivered by SAP. However, you can duplicate these templates and maintain the duplicates. The following changes can be made:

  • Changing the workset for the template in the PCD folder Template Worksets or RoomPartTemplateWorksets .

    See: Defining the Structure of Rooms

  • Changing the initial content for the templates in the corresponding CM folder. The CM folder containing initial content is entered in the configuration of the input parameters for the template extension. If necessary, you can assign another folder containing initial content to a template.

    See: Defining Room and Room Part Folders in the CM Room Extension

  • Changing the assignment of room parameters and room part parameters to iView properties. To be able to use additional information in the iViews for rooms and room parts, you link the iView properties to the room parameters and room part parameters.

    See: Configuring the Use of Information in Rooms

Creating templates

In template administration, you can create new templates. It is advisable to copy (duplicate) an existing template and to modify the copy.

See: Providing Templates for Rooms .

Administering rooms and room-specific functions

The table below lists the most important administration tasks for rooms and room-specific functions

Task

Description

Administering rooms

As a content administrator, you can use special functions to manage all available rooms. For example, this includes locking and deleting rooms.

See: Controlling the Use of Rooms

Providing information if no access to room

If a user calls up a room (through a link), but the room is not accessible, the system can display an information page. Otherwise, the system would display a blank page. Displaying the information page is used to provide information, but can also prevent unauthorized access to an object.

In appropriate cases, for example, if a room is locked or the link is invalid, you can create a page in the Portal Content Directory (PCD) containing pertinent information.

See Providing Information in the Event of Problems Accessing Rooms

Activating and Deactivating of SCF Service Types (RTC, WebEx)

The table below contains information about activating and deactivating SCF service types:

Tasks

Description

Activating service types

During the installation of Collaboration, the system does not automatically activate services for synchronous collaboration, such as WebEx.

See: Activating Synchronous Collaboration Service Types

Deactivating application sharing

If you do not intend to use or no longer require Real-Time Collaboration (RTC) application sharing functionality, you must deactivate the RTC application sharing server.

See: Enabling / Disabling the Application Sharing Server (RTC) .

Configuring Asynchronous Collaboration Services

The table below lists the most important configuration tasks for the asynchronous collaboration services:

Tasks

Description

Configuring discussions

SAP provides a predefined room part for handling discussion groups in rooms.

You can control the type of entry for posts by assigning the appropriate commands or by changing the corresponding command parameters.

See: Configuring Discussion Groups .

Making discussion groups available

If you want to integrate discussion groups in portal pages outside of rooms, you can create the iViews required on the basis of iView templates.

See: Configurating Discussion Groups .

Configuring the Universal Worklist

In the portal and in rooms, tasks are handled in the Universal Worklist (UWL). You can change the layout and behavior of the UWL.

For more information, see Configuring the Universal Worklist .

Configuring Groupware Integration

The table below provides information about the configuration of the Groupware integration:

Task

Description

Configuring the groupware

You can use configuration interfaces to change settings in the groupware integration.

See: Groupware

Configuring Real-Time Collaboration (RTC)

The table below provides information about the configuration of RTC for instant messaging and application sharing sessions.

Task

Detailed Information

Choose the polling policy that best suits your environment and scenario in order to control the load generated on the portal server.

See Configuring the Polling Type

Define the maximum number of instant messaging and application sharing sessions that can run concurrently, and the maximum number of users per session.

See Configuring Maximum Numbers of Sessions and Users Allowed

Configuring RTC Application Sharing Server

This section provides information about the configuration of Real-Time Collaboration (RTC) functionality.

Task (On Demand)

Detailed Information

If you have installed RTC Application Sharing Server as standalone engine on a dedicated machine, define the connection on the portal server to the new standalone RTC Application Sharing Server.

See Setting Application Sharing Server Parameters (RTC) .

Define general parameters for the Application Sharing Server.*

See Setting Application Sharing Server Parameters (RTC) .

Define specific parameters for running Application Sharing Server in a clustered environment (optional).*

See Running Application Sharing Server in a Clustered Environment .

Configure Application Server Java system and application thread settings.*

See Configuring Thread Settings for Application Sharing Server (RTC) .

Configure browser settings on client machines to accept the RTC ActiveX control.

See Configuring Client Browsers to Accept the RTC ActiveX Control .

*As part of your long-term maintenance operations, you should periodically check the settings and adjust them, if necessary.

Task (Periodic)

Detailed Information

Monitor the Application Sharing Server to verify the Application Sharing Server configuration at setup, and to subsequently troubleshoot any problems that may occur during application sharing.

See Monitoring the Application Sharing Server (RTC) .