SharePoint Integration
1C05
IT-Symposium 2007
April 17th, 2007 CongressCenter Nürnberg, GermanySharePoint Integration
Jan-Jürgen Eden
Solution Architect
16
thApril 2007
Agenda
Introduction
Internal HP Systems
Solutions for the People Ready Business
Manufacturing
Financial Services
Questions & Answers
Introduction
HP
Largest implementation of SPS 2003 outside of Microsoft
Member of MOSS 2007 TAP programme
Heterogeneous Environment
How we use SPS 2003
Secure Extranet partner collaboration
Intranet Presence
Professions (Business departments) Team sites (internal collaboration)
Internal collaboration
Team site on demand to all employees IT Control
260,000 users 80,000 concurrent
1200 web sites created a month 900 deleted/removed a month 80 TB of data
Strategic replacement for other solutions
Challenges and Benefits
Benefits
Reduced e-mail
Reduced time for projects
Faster response
Knowledge Management
On-demand
Challenges
Deleted data?
Site design
English only (except
Japan – Japanese only)
IT Control
HP Team spaces roadmap
SharePoint V2
FY05
FY06
FY07
SharePoint 2001 LiveLink eRoom Groove (limited) Groove SharePoint 2007 SharePoint (non-KIM) eRoom (external) Domino
SharePoint
Current deployments
NA2 (Houston, USA)
• Largest deployment • Company wide portals • Local workspaces NA (Houston, USA) • part of NA2 • Local workspaces JPN (Tokyo) •Deployed in Japanese •Localized Workspaces •Bus. Specific Portals
(in progress)
SNO (Australia)
•Local Workspaces
•Bus. Specific Portals (in progress)
EMEA 1 UK
•Local Workspaces •Bus. Specific Portals
Owned by HP In partnership 2 Custom solutions Bangalore, STSD India, GDIC India EMEA2 France Custom solutions (w orldw ide IPG, migration ongoing)
- Singapore, - Israel - Barcelona, SP - Vancouver, CAN
SharePoint Future deployments
NA2 (Houston, USA, KIM)
• Largest deployment (6 TB) • Local workspaces • Global enterprise wide portals • Local bus. specific Portal
SGP (Singapore, KIM)
Localized Workspaces Bus. Specif ic Portals
• local Workspaces • Bus. Specific Portals • with WSS Japanese language pack
EMEA (Sw indon, UK, KIM)
•Local Workspaces •Bus. Specific Portals
Owned by HP
Migration target for
• Houston NA farm • eroom • LiveLink (KMS) • IPG farm in Canada • etc
Migration target for
• LiveLink (KMS)
• IPG farm in Israel and Barcelona • etc
Migration target for
• KIM Japan • KIM Sydney • LiveLink (KMS) • LiveLink (Konnect) • Eroom
• IPG farm in Singapore • etc
DC Austin DC Austin
Lotus Notes, Domino, Public Folder)
Details:
Austin f arm (lef t):
• local Workspaces • Bus. Specific Portals • HA and BC • 4 front ends • multiple search and index • dedicated crawl box • 16TB initial storage
Details:
Austin f arm (right):
• internal mission critical Workspaces and Portals • External Customer and partner Workspaces
• HA, BC and DRP • 2 front end each • 2x8 TB initial storage
Upgrade
to new SharePoint version
Move
from legacy to central data centers
Improve
the service
Improve manage-ability by segmenting the service
Improve reliability by reducing customizations
Eliminate junk sites
Re-factor some portals and large sites
Move to SharePoint 2007 (MOSS 2007)
The product team has four main goals
Upgrade over time – not forced to do an all-at-once
Don’t require the complete shutdown of SharePoint
Ability to write-your-own upgrade code
Consistent set of experiences
There are three main upgrade approaches
in-place (Small farms)
gradual (Medium Large)
content DB (To build a new farm)
Upgrade approaches
In-place upgrade
Updates existing databases and servers
Easiest approach, environment offline while it runs
Gradual upgrade – upgrade site collections
Granular control: one to many site collections at a time
Run old and new versions side-by-side; rollback to SPS supported
More complex and resource intensive
Content DB migration – upgrade into separate farm
Attach SPS content database to MOSS farm and upgrade runs
SPS stays available and untouched by upgrade
Summary of tradeoffs
Upgrade
Approach
In-Place
Gradual
DB Migration
PROs
• Simple• Upgrade smaller sets of data at a time
• SPS & MOSS stay live
• Can revert to original
• Uses existing HW
• Upgrade & move to new farm
• SPS is a separate farm, not affected
CONs
• Entire farm offline during upgrade
• No revert ability
• Hardware intensive: memory & SQL storage
• Redirects for SPS URLs during upgrade
• Many complex manual steps required, higher risk of error
• Requires new farm, double the SQL storage
HP Hosting Service
HP hosting service – Launch April 2007
Takes advantage of MOSS 2007 features
HP & Microsoft Solutions for the
People-Ready Business
Collaboration & Content Management Messaging & Unified
Communications Business Intelligence Business Process Integration Core Infrastructure The Enterprise HP Services M ic ro s o ft T e c h n o lo g y H P T e c h n o lo g y
The full strength of HP
Physical to digital reference information
Manage
& Retain
Document
Capture
HP AutoStore
HP Output Server
Document
Delivery
Archive HP StorageWorks ArrayDistributed Scanning
Financial FrontOffice – New Account
BizProc Frmk - Functional Modules Detailed
SharePoint 2007
Document Management – 1million docs/year
Records Management – 10 year retention
Collaboration
Workspace
K2.Net 2003
Business Processes Layer
HP.BizProc
frmkTypical Initial set-up (August 2006)
Manufacturing - The Final Config?
Partner Extranet
Perimeter Network Corporate Network