With SAP NetWeaver 7.3 a new wiki application in included in the offering of SAP

NetWeaver Portal.

In this presentation you will get a feature overview of the wikis in SAP NetWeaver

Portal 7.3.

1

2

3

4

5

There are many advantages to decide for the wikis in SAP NetWeaver

Portal….

On this slide you see how the wikis are integrated into SAP NetWeaver Portal.

Wikis run in the Portal. There is an entry in the top level navigation for the enduser

and also one for the administrator.

Users can either see the user view or both, user and admin view, depending on their

permissions and roles.

The Portal wiki is not a new development. SAP integrated a product from a third-party vendor .

With this third-party-wiki software as a basis, SAP created a SAP specific wiki which is

integrated into SAP NetWeaver Portal. For customers no extra license is necessary, wikis are

part of the NW licence.

Collaborative Authoring: wikis users can work together on wiki documents.

Email notification: user can subsribe to a wiki page and get informed in case of a

content change.

Blacklists: removes profanity/insulting words/phrases automatially from a wiki

page and replaces them for example by asteriks.

Wikis encourage the participation of many users: the boundary to use wiki is very

low.

Version control: the versions of a page are available (for the enduser) and an older

version be be restored.

Advanced page creation for the power user by the use of macros

The possility to self-published pages by contributors

Open and simple editing

User banning by the administrator

Moderation support: pages are approved before they are published.

Access control by a sophisticated permission concept

A wiki does not only do one thing, there is no typical use case for an Enterprise wiki.

This is also the advantage of a wiki: it can be used in many ways, for many purposes

and many scenarios.

Here you see listed five typical use cases for a wiki. Wikis are very flexible in their

use, they are not restricted to these 5 use cases.

13

-> Choose Content Administration -> Portal Content -> Collaboration Wikis.

Here you see all the objects which are available after the installation is finished. You

have three iViews and two roles.

Wiki iViews and roles are delivered out of the box and can be found in the Portal

Content Studio in a special folder.

All you have to do is to go into the User Administration and to assign the wiki admin

and user role to your users and groups.

Then you can start with the wiki configuration and administration.

Some examples of administration tasks.

Now have a look at the administration console of the wiki.

You see three main entries:

•System

•Spaces

•Reporting

Choose Spaces -> Management -> Summary.

One of the most important admin task is the creation of the wiki space hierarchy.

This hierarchy should reflect your group's functional areas or interests.

There is a main space. It cannot be deleted. All spaces which are created by the

administrator are created below the level of this main space.

When defining spaces and sub-spaces, be sure that the hierarchies are intuitive and

understandable for your wiki users.

18

Permissions are always inherited from higher space levels to lower space levels.

This refers to admin and user permissions. Inheritance can be revoked on the actual

space level.

In this screenshot you can see that the permissions for “anyone” and all registered

users are revoked. So the inheritance coming from above was revoked on this space

level. This is done automatically when you create a private space. You can also

revoke permissions manually of you like.

The user permissions are granted per space. You can decide exactly what a user

can do in a given space: read pages, create pages, edit pages, create comments

and announcements.

In addition we also have the permissions for administrators.

You can have one or several system admins. System admins only exist on the main

or global level, not for spaces below this level System admins have all permissions

for all spaces. And full access to the admin console. You always need at least one

system admin for the wiki application.

You could add some space admins on the lower space levels. A space admin is an

additional or optional admin you can define but you do not need to do so.

A space admin has only certain permissions for a given space (for example create

sub-spaces or delete and move wiki pages).

The permission concept is very flexible. You can have a simple permission concept

with only one or two system admins for all your spaces; or you have different space

admins for your different spaces. It depends on what you like to do.

Choose System -> Settings -> Themes.

Three themes are delivered out-of-the box. The SAP tradeshow theme and the high

contrast theme for handcapped people.

There is also a sample theme which customers can use as a starting point to create

custom themes.

Choose Spaces -> Settings -> Filters and Macros.

The standard configuration for wikis includes a list of filters and macros. You can

enable or disable each filter or macro and change its settings. If necessary, you can

add custom filters or macros.

Macros are only operated on the specific section of the content denoted by the

macro tag. Example: Quote highlighting macro (highlights quotes that appear

between tags)

Unlike macros, filters operate on the entire content. An example filter is the Wiki

syntax filter, which will convert plain text using the wiki markup.

The profanity filter (or blacklist filter) for example removes special words from wiki

pages which are abusive or offending.

Choose Spaces -> Settings -> Interceptors.

To examine comments on wiki pages before they appear in the wiki spaces, you can

define interceptors. An interceptor is a special type of filter that can accept, change,

or reject incoming comments.

We also have some simple reports in the wiki application:

For example the page status report which lists the status of the documents in a

selected space.

Or the page details report which lists all wiki documents of a selected space

enriched by detailed information on the documents: the doc ID, the number of

versions, the title, the number of views/hits, the number of auther discussions or

commments and the document size.

27

The homepage of the wiki provides an overview access to all spaces to which you

have at least read permission, and displays a list of the most recently updated

content within them.

The homepage is divided into six sections: Spaces, Most popular documents, least

popular documents, What„s new, Top Contributors and Your Favorites.

The user actions on a wiki page are also dependent on the user permissions. An

administration user has for example much more functions than the normal user.

The rich text editor is the „every user editor“.

Every user also with no wiki markup knowledge can created wiki pages using this

editor.

You can insert images and links, format text with different headings, add

attachments, use the undo button, use emoticons etc.

The Plain text editor is the editor for the power user who is experienced in using wiki

markup language.

You can use this editor to structure and format the pages with macros. A macro is a

rule that determines how you can structure and modify the content of wiki pages.

When a user creates a wiki page, the creator of the page can define how to

collaborate with other users.

By default any other user can edit the document.

The page creator can define that he/she only wants to collaborate with specific

users: for example the team members, buddies or his/her manager.

Or the page creator defines that only he/she is allowed to edit the page.

Different versions of a wiki page can be compared and the revisions are shown.

It is also possible to restore an older version of a wiki page (see next slide).

A user can subscribe to a wiki page. He/she will be informed via email when the wiki

page is updated or changed.

The authors of a wiki page can have a private discussion which is not visible for

other users who not have the permission to edit the page.

Comments can be added by other users when the comment policy was set to „open“.

The wikis can be integrated into the Portal search mechanism.

There is also a separate wiki search, which searches only in the wiki application.

39

A space administrator has more functions than the “normal” enduser. A space

administrator can for example delete and move wiki pages and manage the

collaboration options for every wiki page.

A space admin had less permissions than a system administrator. He has access to

a limited set of administration features.

An administrator can configure the wikis with or without approval processes or

content control. Without an approval process being configured, every wiki user can

create and publish documents right away.

With an approval process being configured, the admin can specify someone to

approve all documents created in the space before they can be published and made

visible to other people.

With a space approver set, people will still be able to create new documents. Instead

of being able to publish the document right away, however, they'll be able to "Submit

for approval."

The author of a wiki page can also start a review process for his/her wiki page. In

this case the author decides for him/herself that the page needs to be reviewed and

approved by another person, maybe a team colleague or his/her manager.

In this case the wiki page is also not published until it is approved.

The approval status is always displayed on a wiki page. The exclamation mark

indicates that the page still has to be approved.

46

47

48

49

52