OGh Theme session: 10 Things you should know for a successful WebCenter implementation

(1)

OGh Theme session:

10 Things you should know

for a successful WebCenter

(2)

Agenda

1. Introduction

2. WebCenter History

3. WebCenter Suite Present 4. Functional

5. Technical

6. Organizational 7. What’s next

(3)

Introduction

14 Years Oracle Consulting Netherlands (1997 – 2010) Vopak / Arval / Trainings

(4)

Agenda

1. Introduction

5. Technical

(5)

WebCenter History

First: What we need of WebCenter to get the big picture

WebCenter consists of four application groups:

Sites: Web Experience Management

Engage (anonymous) users

Portal: Agile enterprise portal

Deliver intuitive portals, composite applications or mashups

applications or mashups

Content: Content lifecycle integrated

(6)

WebCenter History

WebCenter Sites

• 2011

Oracle acquired FatWire Software • 1996

FatWire established by Mark Fasciano, Ari Kahn and John Murcott • 2003

Acquired Open market’s Enterprise web content management assests, including Content Server

including Content Server • 2004

Launched Content Server 6.0 Web Content Management (WCM) • 2007

FatWire Acquired Infostoria and launched strategy for Web Experience Management (WCM)

• 2010

(7)

WebCenter History

WebCenter Sites

WebCenter Sites consists of: • Content Server

Core functionality for Content Management

• Satellite Server

Improve performance by an additional layer for caching

• Mobility Server

Extend web presence to deliver multi-channel experience

• Analytics • Analytics

Analyse site visites / usage

• Engage

Add Social Sign In functionality

• Community Server

(8)

WebCenter History

WebCenter Content

• 2006

Oracle acquired Stellent • 1989

Stellent founded by Robert Olson • 1999

Intradoc 4 released as Java application making content management services available via HTTP

services available via HTTP • 2004

(9)

WebCenter History

WebCenter Content

WebCenter Content consists of: • Content Server

Provides everything you need to create a vast range of content management applications.

• Records (f.k.a Oracle Universal Records Management)

Enables the centralized administration and application of records and lifecycle policy.

• Rights (f.k.a Oracle Information Rights Management)

Secures and tracks sensitive digital information everywhere it is stored and used.

• Document Capture • Document Capture

Streamlines the capture process of paper and electronic documents.

• Imaging (f.k.a Oracle Imaging and Process Management)

Provides imaging and business process management capabilities for enterprise and business applications.

(10)

WebCenter History

WebCenter Social

• 2011

Oracle announced Oracle Social Network an Oracle OpenWorld • 2012

(11)

WebCenter History

WebCenter Social

Oracle Social Network consists of: • Conversations

Real-time, Multimedia, Sharing

• Business updates

Application Integration, Informational Feeds, Gadgets

• Content

Annotation, Social Tools, Search

• Activity Streams

(12)

WebCenter History

WebCenter Portal

• < 2000

Oracle Web DB, Web front-end based on PL/SQL • 2000

Oracle Portal, first release of Portal solution, spin-off from Web DB • 2007

WebCenter 10g • 2008

Oracle acquired BEA Systems and suddenly had two other portals: Oracle acquired BEA Systems and suddenly had two other portals: Aqualogic User Interaction

WebLogic Portal • 2009

WebCenter 11g Release 1 (11gR1)released • 2010

Oracle acquired Sun Microsystems, added Sun Java System Portal to the list • 2013

(13)

WebCenter History

WebCenter Portal

WebCenter Portal consists of: • WebCenter Portal

Provides everything you need to create a vast range of content management applications.

• WebCenter Services

Web 2.0 services like Discussions, Forum, Blog, Wiki, Presence

• WebCenter Analytics (f.k.a. AquaLogic Analytics)

Analyse site visites / usage

• Pagelet producer (f.k.a. AquaLogic Ensemble)

Expose (parts of) a web application

• WebCenter Portal: Spaces

Out of the box application built with WebCenter Portal integrating WebCenter Services to a ‘community’ application

(14)

Agenda

1. Introduction

3. WebCenter Suite Present

4. Functional 5. Technical

(15)

WebCenter Suite

Present and future

Current status and development includes

• Fusion Middleware 1gR1, Patch Set 6 (PS6, version 11.1.1.7.0) released April 1st ₂₀₁₃

• Focus primarily on bug fixes and further stability improvement

• Tighter integration between the various WebCenter products and Oracle • Tighter integration between the various WebCenter products and Oracle

applications

• Modernize the user interface

• Administration -> Application Development Framework, ADF) • End user -> Multiple platform support (desktop, tablet, phone)

(16)

Agenda

1. Introduction

3. WebCenter Suite Present

4. Functional

5. Technical

(17)

Functional

Use tools for what they are meant for

Use tools for what they are used for, do not invent

your own wheels

Although the WebCenter products have some overlaps in functionality, select the product that best fits the required functionality and do not try to ‘build’ functionality in other products

functionality in other products Examples:

• When incorporating work procedures, use Wiki documents instead of PDF documents

(18)

Functional

(19)

Functional

Think Big Start Small

Think

BIG

start

small

and act fast

Key factor in this is to have an ultimate

vision of an application, even though you are implementing something noticeably different in the beginning.

different in the beginning. Example:

• The organization does not yet have a Content Management team in place but is planning for it.

(20)

Functional

Think Big Start Small

We want a portal for customers and employees, functioning

as a single point of information and collaboration.

1. Create an information environment (traditional intranet) where information can be added by a few people without workflow

2. Add ‘group spaces’ in which teams can collaborate / share information for a common goal (e.g. projects)

3. Add back office integrations to give employees insight into: 1. Evaluations

2. Employee Benefits (base contract, company car, health insurance, …) 3. Hour registration

4. Add customer portal functionality

1. Grant customers privileges in relevant employee evaluations during selection 2. Let customers participate in project collaboration

3. Let customers approve hours registered by employee

(21)

Functional

Migration / Upgrade considerations

When migrating from an old portal to WebCenter Portal

Many concepts and architectural structures are different. Consider re-creating content /functionality for:

Oracle Portal WebCenter Portal

Oracle Portal WebCenter Portal

Web Content directly on page Content item in WebCenter Content Departmental pages WebCenter Portal Spaces

(22)

Agenda

1. Introduction

5. Technical

(23)

Technical

Get the right resources

Get the right resources, specialists in their fields

Although WebCenter Portal is based on ADF, not all ADF specialists

(architects, designers, developers) have the required skills for a WebCenter project.

Almost always, a WebCenter project consists of the usage of at least two products from the WebCenter Suite.

(24)

Technical

Get the right resources

Where can we get the right resources?

(25)

Technical

(26)

Technical

Standard functionality

Stay close to standard functionality

When you utilize standard functionality of the product, they will evolve automatically over time to embrace:

• New technology (HTML 5, Tablets etc) • New features (enhancements)

• New features (enhancements) • Bug fixes

Also, you can contact Oracle Support for issues like: • Defects

(27)

Technical

Customize, don’t custom build

Customize components, do not built custom ones

Within WebCenter Portal you have the ability to customize components to match your requirements. Try customization first.

When customization cannot meet your requirements, think of building custom functionality

custom functionality Examples:

• Members task flow

(28)

Technical

Use skinning in ADF

A WebCenter Portal site is not a static application

Involve a design agency that grasps the concept of a dynamic site Not a good idea:

• Adding images as background of navigation items • Adding images as background of navigation items • Adding images as background of portlets / taskflows Remember that:

(29)

Technical

Use skinning in ADF

Do not let the Design Agency dictate the exact HTML that needs to be sent to the browser to achieve a certain look and feel.

(30)

Technical

Use skinning in ADF

Example to identify and change the look and feel

1. To see the skinning class names change the web.xml file of the WebCenter Portal applications to not compress the class names. 2. Then view the page source of the Portal page to identify the classes

used used

3. Finally, create a skin and change the look and feel of the required skin classes

(31)

Technical

(32)

Technical

Use skinning in ADF

Additional tip:

To differentiate between resources for multiple spaces, add a text file in the folder containing the resource to describe the use.

(33)

Technical

Perform adequate tests

Adequate test includes Functional and Performance

When performance testing, take into account: • Customizations end users can apply

• Custom code

• When integrating back office applications, do not forget to test them • When integrating back office applications, do not forget to test them

either. They might get heavier load

When not all functional requirements are met, consider thinking BIG and starting small.

(34)

Agenda

1. Introduction

5. Technical

6. Organizational

(35)

Organizational

Involve the end users

Involve the end users, but not too many

• Make sure a representation is involved in the design of the application • Make sure all departments are represented

• Do not involve too many end user. The more end users, the more opinions you get

opinions you get

• Make sure the group is fixed to avoid changes during the project • Empower this representation to make decisions

(36)

Organizational

Stimulate usage

Stimulate the entire organization to use the new

application

To maximize acceptance of new technologies (Web 2.0 capabilities Wiki, blog and other modern ways of communication) make sure all layers of the

organization embrace and use it. organization embrace and use it. Examples:

• CEO embraces social media by being available on chat, keeping

employees up to date on what he’s doing and communicate less with email and more with personal video

• Employees get targets on participation and activity on social intranet. These result might influence evaluation / compensation.

(37)

Organizational

Administer the application

Make sure you have expertise to keep it up & running

The application landscape is often relative new and internal knowledge lacks. Therefore, make sure the necessary technical expertise is transferred from the developers to administrators.

Examples:

• Administrators can get trainings for all the used applications, but interaction and dependencies are often not taught or specific for the solution

(38)

Agenda

1. Introduction

5. Technical

6. Organizational

(39)

What’s next?

Get up to speed

There are several trainings available

Both Oracle University and Vijfhart have multiple sets of trainings available. For Oracle Partners, the Oracle Partner Network (OPN) has Bootcamps. On OPN you can also follow Guided Learning Paths to get the best

information for certification information for certification

As a partner, get Specialized to get the most out of your expertise

(40)

What’s next?

Learn from the community

Join the OGh WebCenter Special Interest Group (SIG)

Audience: • Customers • Partners Purpose: Purpose: • Share knowledge • Share experience

• Interact with Oracle subject matter experts

More information:

• http://www.ogh.nl/page.aspx?event=197

• [email protected] or [email protected]

(41)