Transcript WebFOCUS 8: Best Practices for Migration

WebFOCUS 8: Best Practices for Migration
Lori Pieper
Indianapolis User Group Meeting
July 25, 2012
1
Agenda
 What makes WF8 migration so different?
 Upgrade Path for WebFOCUS Product Components
 Planning the Upgrade
 Migration Strategies and Considerations
 Migration workflow
 Validating the migration – what to expect
 Post Migration Tasks
2
What makes WF8 migration so different?
3
What makes WF8 so different?
 Architecture overhaul
 New security – very granular
 Consolidation of WebFOCUS Client objects
 One place to log in for both users and
administrator
 Report Caster and Library
 WF Client content and security held in relational
database repository
 Business Intelligence Portal
 Allows for more flexibility in both development
and the end user experience
4
WF8 Content - New Look
New Content
Migrated Content
5
Granular Security - Permission Sets
6
Some WF “Default” Permission Sets
7
WF8 Repository
•Report Caster
tables named the
same, but have
added new key
fields.
• MR RDBMS
Authorization
tables replaces
by “UOA” tables.
8
Upgrade Path for WebFOCUS Product Components
9
Planning the Upgrade
Upgrade path for WebFOCUS product components
Product
Component Used
Upgrade Path
Managed
Reporting
•MR data and security rules - migrated and stored
in the WebFOCUS 8 repository.
•WebFOCUS 7 domain tree structure will be
preserved.
•Reports should continue to run as they did in
WebFOCUS 7.
BI Dashboard
•BID content - migrated to BI Dashboards
•stored on the file system in
WebFOCUS80/worp
•BID Favorites/Mobile Favorites -stored in
WF8 repository
•BI dashboards can be used “as is” with some
caveats.
10
Planning the Upgrade
Upgrade path for WebFOCUS product components
Product
Component
Used
Upgrade Path
ReportCaster
•Fully integrated with WF8 architecture and
security.
•ReportCaster/ Report Library – migrated
•stored in the WF8 repository.
Developer Studio
•Can be installed on same machine as
Developer Studio 7.
•Can switch between two releases as before
•Leverages WF8 architecture and security.
11
Planning the Upgrade
Upgrade path for WebFOCUS product components
Product
Component
Used
Upgrade Path
Configuration
•As in prior versions, configurations are not
migrated and will need to be re-applied.
•E.g., security settings, custom settings, etc.
Parameters
•Most WebFOCUS 7 parameters are still
available in WebFOCUS 8.
•Some have been removed
Customizations
•All customizations will need to be evaluated
•may no longer be needed
•may be implemented differently
12
Validating the migration – What To Expect
Managed Reporting – MR content
MR content
WebFOCUS 8
Deferred Reports
•Migrated Deferred reports will continue
to run.
Published reports
•Migrated published reports will continue
to run.
•This feature has been removed from
WF8.
•“Publish” in WF8 has a different meaning.
Templates
•Migrated templates will continue to
work.
•This feature has been removed from
WF8.
14
Validating the migration – What To Expect
Managed Reporting – MR content

WebFOCUS 7 - legacy Publish feature
1
2
Published report was written to
ibi_html/publish/{,htm}
End users called the {.htm} directly
15
Validating the migration – What To Expect
Managed Reporting – MR content
WebFOCUS 8 Publish
capability means
something different.
It is related to the
WebFOCUS security
authorization model .
It is used when one
wants to make a
WebFOCUS resource
available to others.
16
Planning the Upgrade –
Migration Strategies and Considerations
17
Planning the Upgrade
Migration Considerations
Security has changed significantly
 Evaluate current MR users/groups/roles/privileges and decide:
 Do not migrate and start from scratch?
 Leave “as is” after migration?
 Restructure security authorization using WebFOCUS 8 security
authorization model?
 Group users according to their role
 Leverage groups and sub-groups to delegate responsibilities
 Minimize user management and administration
 Leverage WebFOCUS groups to minimize or replace user
profiles on the Reporting Server.
NOTE: For LDAP shops: WebFOCUS8 provides a better way to leverage
groups defined LDAP/AD.
18
Planning the Upgrade
Migration Considerations
 WebFOCUS 8 upgrade may be an opportunity to “clean house”:
 Conduct an inventory of applications/report usage:
 Utilize Resource Analyzer to identify reports that:
 Are never used and can be removed
 Can be consolidated
 Should be updated/improved to leverage WebFOCUS 8
features
19
Planning the Upgrade
Migration Strategies
 Two options for Migration:
 Full Migration – everything in WF7 is migrated at one time to
WF8
 WF migration tool should be used
 Staggered Migration – you migrate by application or instance of
WF
 WF migration tool may be used with separate WF
installations.
NOTE: The WF MR migration tool migrates everything:
Users, groups, roles, domains, content
…except BID
20
Planning the Upgrade
Migration Strategies
For either Migration option:
 If WebFOCUS 7 development is active during the upgrade, you will
need to do one of the following:
 Manage ongoing WebFOCUS 7 development during upgrade:
 intermediate WebFOCUS 8 environment – move as
developed
 manual tracking, logging and promotion of changes
 Lockdown all new WebFOCUS development until everything is
migrated.
 This option ensures nothing gets lost.
Remember “development” includes users creating “My Reports”
21
Managing ongoing development during upgrade
….or an option for “cleaning house”
 Full migration from WebFOCUS 7 to an intermediate version of
WebFOCUS 8
 Use WebFOCUS 8 Change Management from the intermediate
version of WebFOCUS 8 to the targeted WebFOCUS 8 environment
(Sandbox, Dev).
This workflow is illustrated below
• Existing
WebFOCUS 7
Production
Full migration
with WF 8
migration
tools
WebFOCUS 8
Change
Management
• Intermediate
version of
WebFOCUS 8
• WebFOCUS 8
Sandbox/Dev
Use WebFOCUS
8 Change
Management to
promote to
QA/Prod
22
Migration workflow
23
Migration workflow
 Migration Utilities
 WebFOCUS 8 is packaged with a number of migration utilities
which migrate content from:
 WebFOCUS Reporting Server – has not changed
 Managed Reporting
 Business Intelligence Dashboard
 Business Intelligence Dashboard Favorites/Mobile Favorites
 ReportCaster
24
Migrating earlier releases to WebFOCUS 8
 WebFOCUS 8 migration supports:
 Managed Reporting migration from Release 7.6.x and 7.7.x to
Release 8
 Business Intelligence Dashboard (BID) migration from Release
7.6.x and 7.7.x to Release 8
 ReportCaster migration from Release 7.6.x to Release 8
 For WebFOCUS versions 4.x, 5.x or 7.1.x, it is best to migrate to the
latest 7.6.x or 7.7.x release to minimize migration steps.
 Special consideration for Unicode
 Unicode BI Dashboard Migration
 Needs to be performed at the
WebFOCUS 7.7.x level
prior to WebFOCUS 8 migration.
25
Migration workflow
 WebFOCUS 8 migration process consists of three steps:
 Export
 This step will extract WebFOCUS 7 data using WebFOCUS 8
migration using export utilities.
 Export migration logs are created and is useful for
capturing errors if they occur.
 Import
 This step will import WebFOCUS 7 data into WebFOCUS 8
using import utilities.
 Import migration logs are created and and is useful for
capturing errors if they occur.
 Validate
 This step is to validate the migrated data
 ..what should we expect after migration?
26
Migration workflow
1
2
Copy WebFOCUS 8
migration utilities
to the WebFOCUS
7 environment
Stop WebFOCUS 7
Environment
Run the
WebFOCUS 8
MR/BID/RC export
utilities
Copy extracted
WebFOCUS 7
content to
WebFOCUS 8
Run the
WebFOCUS 8
import utilities
Validate migrated
content
27
Validating the migration – what to expect
28
Managed Reporting
29
Validating the migration – what to expect
Managed Reporting – MR security objects
 Managed Reporting security objects
 Users
Users
 Groups
Groups
 Roles and Privileges
User Default Roles (UDR)
 MR security authorization rules are maintained with
UDR
 The concept of the role being attached to a user is
mimicked in WF8 using User Default Role (UDR).
 Designed to simplify the migration process and
provide customers with an optional starting point
in WebFOCUS 8.
30
Validating the migration – What To Expect
Managed Reporting – MR security objects
 Here is a glimpse into the WebFOCUS 8 UDR and how it is designed
to maintain existing MR security relationships.
31
Validating the migration – What To Expect
Managed Reporting – MR content
Old MR content
WebFOCUS 8
Domains
Mapped to Folders
Sub-folders
Mapped to Sub-folders
Standard Reports
Maintains same tree structure
Reporting Objects
Maintains same tree structure
MyReports
Stored In a MyContent folder
Saved Parameter Reports Should continue to run
URL Standard Reports
Should continue to run
Shared Reports
Shared Content – Empty user folders do
not get migrated
32
Validating the migration – What To Expect
Managed Reporting – MR content
WebFOCUS 7
WebFOCUS 8
33
BI Dashboard
34
Validating the migration – what to expect
BI dashboards –vs- BI Portals
BI Dashboard
BI Portal
35
Validating the migration – What To Expect
BI Dashboard
 BI Dashboard content – copied, not converted to WF8 BI Portal

BI dashboards will continue to run in WebFOCUS 8 with some
caveats:
 Some BI dashboard features have been removed, for instance:
 “redirect” on logout is no longer “by view” but is now a
global setting.
 Some BI dashboard features have been implemented
differently:
 “Domain Tree” is now the “Resource Tree”
 “Role tree” would now be handled through the WF8
security layer
36
Validating the migration – what to expect
BI dashboards - Then and Now
WebFOCUS 7
WebFOCUS 8
37
Validating the migration – What To Expect
BI dashboard content
 BID Features that are implemented differently in WebFOCUS 8 and
documented in the WebFOCUS 8 Upgrade Considerations:
 BI dashboard Login Pages
 Different URL for BI dashboard Login page
 Customizations to login pages will need to review for
compatibility
 Managing public user ID
 Enabling WF_Public_Role
 Changing default public user ID
 Disabling public user
 Specifying Reporting Server credentials
 Replacement of scroll buttons by scroll bars for trees and blocks
 Search
38
ReportCaster
39
Validating the migration – What To Expect
ReportCaster – Security objects
 RC security authorization rules maintained after migration
RC security objects
WebFOCUS 8
ReportCaster user IDs
No longer separate. Unified architecture
means we have one user.
•Their assigned permissions determine if
they can access Report Caster.
Execution user IDs
Migrated and mapped to related
schedules.
IBIMR_RC_SVCUSER
Removed. No longer required due to
new architecture and security model.
40
Validating the migration – What To Expect
ReportCaster - Content
 All migrated Report Caster and Report Library content are
available from the “Content Tree”
 Schedules
 Alert Schedules
 Group BlackOutDates
 Distribution Lists
 Access Lists
 Watch Lists
41
Validating the migration – What To Expect
ReportCaster - Content
 Migrated Report Caster schedules will be in Content  Report Caster
 Distribution lists, etc., - in separate folders under Report Caster
 Migrated Library output will be found in the content tree based upon
their output options:
 Content  Library Content  Category – if this was from the
reporting server schedule
 Content  Domains  Category – if this was from the MR
Domain schedule
NOTE: For new schedules and library content, you can put these
anywhere for which you have the proper permissions.
42
Validating the migration – what to expect
ReportCaster – Content
WebFOCUS7
Call ReportCaster
RC
Administration UI
Create RC new content
43
Validating the migration – what to expect
Report Library Content - WebFOCUS 7
Access Report Library
Report Library Content
Report Library Access List
44
Validating the migration – what to expect
ReportCaster Content – Centralized in WebFOCUS 8
WebFOCUS 8
Report Library Content – From MR Report
Report Library Content – From APPS Folder
Report Caster Content
45
Post Migration Tasks
46
Post Migration Tasks
MR Security Authorization - Enable User Default Role
 From WebFOCUS Administration Console
 Navigate to Configuration => Other
 Set IBI_Enable_UDR to a value of TRUE
47
Post Migration Tasks
MR Security Authorization - Configure Public user ID
 WebFOCUS 7
 Manage the public user ID from BI View Builder.
 Change the user ID from public to named user
 Set Reporting Server credentials for Reporting Server.
 WebFOCUS 8
 Manage the public user ID from Administration Console
48
Post Migration Tasks
BI Dashboard –BI View Builder Admin permissions
BI View Builder Administrators
WebFOCUS 7
In BI View Builder, MR and Group
administrators were able to view and add BI
content to all group views.
 They were not required to be members of
groups to perform this function.
• Migrated MR or Group administrators are
•
WebFOCUS 8
•
not migrated into all groups.
In BI View Builder, a user that is assigned
“MR and Group administrator” permissions
cannot by default, view and add BI content
to all group views.
Can only create group views and add BI
content to Group Views for Groups they are
members of.
49
Thank you for attending our session
50