integrating novell teaming within your existing infrastructure

Post on 28-Nov-2014

841 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

So you've decided to implement Novell Teaming, but how do you use it to leverage your existing environment to the fullest extent? Using product demonstrations, this session will how you how to configure authentication against existing LDAP directories; how to integrate with Novell GroupWise, Exchange or other e-mail systems; and how to expose existing document stores so they can be searched and accessed through the Novell Teaming interface.

TRANSCRIPT

Integrating Novell® Teamingwithin Your Existing Infrastructure

Robin RedgraveCollaboration Technical Specialistrredgrave@novell.com

Kai ReichertCollaboration Technical Specialistkreichert@novell.com

© Novell, Inc. All rights reserved.2

Agenda

• Using existing server environment• Authentication sources• Inbound and Outbound messaging • Using WebDAV mapped drives• Using Mirrored Folders to access existing documents• Data synchronization with Novell® Data Synchronizer• Using information feeds• Access from Mobile devices

Server Environment

© Novell, Inc. All rights reserved.4

Platforms

• Teaming will run on the following

– Novell® Open Enterprise Server (OES) 2 Linux

– SUSE® Linux Enterprise Server (SLES) 10 or SLES 11

– Windows Server 2003 or Windows Server 2008

• Plus latest support pack

© Novell, Inc. All rights reserved.5

Databases

• Can use existing Database environment

– MySQL

– MSSQL

– Oracle

• Take advantage of

– Existing High availability

– Existing Backup environment

– Existing product knowledge

© Novell, Inc. All rights reserved.6

File system

• Teaming needs a file system to store files

– Can use existing data environment

• Take advantage of

– Existing High availability

– Existing Backup environment

© Novell, Inc. All rights reserved.7

Front End Access

• Access to Teaming via Browser

– Supports http and https on

> Internet Explorer 7 or newer

> Firefox 3.5 or newer

> Safari

• Teaming uses Tomcat

– Default ports need to be redirected to use port 80 or 443

• Access to can be secured by using Access Manager

• DMZ scenario may require a multi-server setup

Authentication

© Novell, Inc. All rights reserved.9

Authentication

• Can use existing LDAP Authentication sources

– eDirectory™

– Active Directory

– Open LDAP?

• Also has a local directory

– Useful for external users

• Can mix and match directories in your environment

– eDirectory/Active Directory/Local

© Novell, Inc. All rights reserved.10

LDAP Synchronisation

• Can use filters to limit imported users

– Only members of a Teaming group have access

• Users can be removed/disabled if deleted from LDAP

• Can import existing Groups

– No requirement to recreate groups

– Can assign rights dynamically to new users

• Can create Groups based on OU

– Based on filter

Inbound and Outbound E-mail

© Novell, Inc. All rights reserved.12

E-mail (Outbound)

• SMTP relay configured as part of the install

• E-mail address is taken from the server hostname

• Enable relaying on the relay if need be

– Can be enabled just from the teaming server address

• Or authenticate to relay

• TLS is supported for secure communication

© Novell, Inc. All rights reserved.13

E-mail (Inbound)

• Each folder can be configured to receive inbound email– Ensure there is an MX record for the Teaming server– Only users with sufficient rights are allowed to post to a folder– Anonymous contributions can be made using the posting agent

• The old method is still supported (Not recommended)– POP– IMAP

• Ensure nothing else is running on Port 25– May need some port redirection

© Novell, Inc. All rights reserved.14

GroupWise® Integration

• Adds a teaming folder structure in the windows client– Single sign-on– Allows user to view teaming information in Novell® GroupWise®

– Can subscribe to Teaming calendars/RSS feeds– Can Mail to a team

• In GroupWise 8 SP2– Enhanced integration options

• Configured in ConsoleOne®

> Client settings

Using WebDAV

© Novell, Inc. All rights reserved.16

WebDAV

• Allows a Teaming folder to be mounted as a drive

• Treated as a normal file share

– Document versioning

– Teaming rights active

– Activity logged

– File locks will be honoured

• Can be some issues with Vista and Windows 7

Using Information Feeds

© Novell, Inc. All rights reserved.18

RSS

• A separate feed per folder• Need an RSS client to read it

– Novell® GroupWise®

– Outlook– Notes– Others....

• Also support ATOM Feeds• Warning:

– The feed is non-authenticated, do not give to anyone else

© Novell, Inc. All rights reserved.19

Teaming Feed

• Browser-based feed

– New in Teaming 2.1

– Periodically updated

– Displays

> Site wide

> Tracked places

> Team places

Mirrored Folders

© Novell, Inc. All rights reserved.21

Mirrored Folders

• Expose existing document stores in teaming– Can be read/write or read only

– Full indexing

– Workflows

– Can add additional data the the entry form

– Comments

• Drawbacks– No version control

– File locks not honoured

– Does not use existing file rights on the server

Mobile Access

© Novell, Inc. All rights reserved.23

Mobile Access

• Access Teaming from your mobile

– Easy to use

– View optimised for smaller display

– Core functionality available

• Can be used as a cut down interface from desktops

Data Synchronization

© Novell, Inc. All rights reserved.25

Data Synchronizer

• Synchronizes personal calender and task items

– Bi-directional

– To any connected system

> Novell® GroupWise®

> Exchange

> Notes

> Mobile devices

> … And others

Questions?

© Novell, Inc. All rights reserved.27

Summary

• Teaming can easily use your existing environment– Multiple platform support

– Multiple directory support

– SMTP mail inbound and outbound to standard mail systems

– Browser access

– RSS

– Expose legacy document stores

– Easy access for all users from any location

• Non intrusive co-existence with existing systems

Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

top related