2 cloud operations

<Insert Picture Here>
Cloud Service Operations
Oracle Fusion
Human Capital Management

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Fusion Human Capital Management
Flexible Deployment Options
On
Premise
Public
Cloud
Same Great Fusion Applications Functionality
✔
Applications Unlimited Apps Available
✔
Configurable/customizable through Fusion’s built-in extensibility platform
✔
Highly customizable via JDeveloper and database tools
✔
Perpetual License
✔
Maintained on your behalf
Dedicated staging environment on your behalf
Hardware and software included in a single subscription price
Always kept current on latest release
Automated backups
Shared Identity Management with other Cloud services

Flexible Deployment Options
On
Premise
Public
Cloud
Same Great Fusion Applications Functionality
✔ ✔
Applications Unlimited Apps Available
✔
Configurable/customizable through Fusion’s built-in extensibility platform
✔ ✔
Highly customizable via JDeveloper and database tools
✔
Perpetual License
✔
Maintained on your behalf
✔
Dedicated staging environment on your behalf
✔
Hardware and software included in a single subscription price
✔
Always kept current on latest release
✔
Automated backups
✔
Shared Identity Management with other Cloud services
✔

Public Cloud Vs On-Premise

Content Migration Solutions
The Content Migration Solutions between Fusion HCM Cloud Service
environments are classified in terms of the direction from which content
is migrated.
Test-to-Production (T2P) - Migrations occur for one type of content,
such as business intelligence or functional setup, at a time
Production-to-Test (P2T) - Typically migrates an entire production
environment to test and, in doing so, overlays the entire contents of the
test environment

Production-to-Test Migration
 Migrates database content from Production to Test
 Overwrites Test environment which is unavailable for one day
 Both environments must be at the same patch level
 Service is on request - recommendation: Get on the P2T schedule well in advance
 Production user definitions are migrated
Content Migrated :
 All transaction data and functional setup data in the Fusion Applications schema
 File attachments (for example, agreements, orders) stored in Universal Content Management (UCM)
 Flexfield customizations
 Metadata Services (MDS) customizations (for example, Oracle Composer changes)
 BI Web Catalog and Repository Definition (RPD)
 Oracle Data Integrator (ODI) repository
 WebCenter contents

Test-to-Production Migration
The Fusion HCM Cloud Service supports migration of several of the most common customer configurations from the test
environment to the production environment.
The typical use case for such configurations is performing your configurations in the test environment, validating that you configured
them correctly, and migrating them to the production environment

Setup Migration through FSM
 Migrates setup from one environment to another
Typical use case is migration from Test to Production
 Migrates all setup for a Logical Business Object (LBO)
Scope, an FSM concept, allows row-level migration but is not enabled for many HCM LBOs
 Target to Source migration rules:
Setup from target will be inserted into source if it does not exist in the source
Setup rows from target that exist in the source will be updated with changes from the source
General Rule: Effective Start Dates must be the same to be considered as a match

Setup Migration through FSM
The following table identifies the Logical Business Objects (LBOs) for which FSM migration is supported with Release 7

Environment Management Services and Tools
 P2T Content Migration Utility: Copies Production data to Test
 Setup migration through Functional Setup Manager (FSM)
 Flexfield Metadata Migration through FSM
 Page Composer UI Extensions Migration through Fusion Middleware (FMW) and/or CSM
(Customization Set Migration, new with Release 7)
 BI/Reporting Migration through Oracle Transactional Business Intelligence (OTBI)/ Business
Intelligence Publisher (BIP)
 Refresh of Test environment: Provides the customer with a new Test environment
 Data load Delete Scripts: Removes bad/incomplete data from tables during initial
implementation (through Oracle Support)

Cloud Service Options – Requested through MOS

Cloud Change Management
Regular Maintenance : Oracle Cloud Operations reserves the following regular maintenance windows targeted to occur during the
statistically lightest utilization period for that deployment region.
 Mandatory monthly application patching cycle (Patch Bundles)
Cadence is Test environment (1st Friday) first followed by production two weeks later (3rd Friday)
 Optional weekly as-needed one-off patching
 Optional weekly accumulated one-off patching
 4-6 month application upgrade cycle
 1 year tech stack and infrastructure upgrade cycle
(for example, Exadata, Exalogic, OS, firmware, switches, load balancers, firewalls, hypervisor, database)
 Most maintenance is applied Friday evening through Saturday morning (for each time zone)
Planned Maintenance : Schedules may be viewed on the Oracle Cloud Customer Portal. Oracle will endeavor to provide customers with
five business-day advance notice if a different maintenance window is required. Maintenance extension alerts will also be posted on the
Customer Cloud Portal.
Emergency Maintenance : Oracle will apply emergency maintenance as required to maintain the operation, security, and performance of
the Oracle Cloud services. Emergency maintenance may include, but is not limited to, the application of patches, configuration changes,
hardware repair, or other required activities.

Patching

Upgrades
 Typically two upgrades are provided each year
 Cloud Fusion Applications release numbers are the same as on-premise.
 A Cloud upgrade may include multiple releases.
 Oracle communicates logistics and what’s new before, during, and after the upgrade in many forms.
 Upgrading HCM Cloud customers occurs over several months. Customers may defer an upgrade, but must eventually accept it
 Upgrades are applied to Test environments first and, after customer validation, to Production environments: - Test environments are
upgraded throughout the week. - Production environments are upgraded during weekends
 Customers must plan for and execute upgrade validation
Customer Benefits
 Provides functional and technical enhancements and fixes
Feature/function improvements
Usability enhancements
Technical updates
 Re-establishes the baseline for future updates
 Eliminates the conventional problem of being stuck with an obsolete software version

Recommended Customer Upgrade Validation Procedures
Develop Upgrade Validation Plan
 Review testing plans and scripts originally prepared for the implementation project to test the same scenarios in the newly upgraded environment.
 Review any communications or training materials and guides for feature/function changes due to the upgrade, to incorporate them into the customer's
validation strategy.
Perform Post-upgrade Validation
 Configuration: Review the setup for primary code values, such as Departments, Locations, Jobs and confirm that all appear to be the same as they were
prior to the upgrade.
 Employee Data: Create and run a few simple reports on employees showing their personnel and assignment information prior to the upgrade. Then run
the same reports again after the upgrade to verify that the information appears the same as prior to the upgrade.
 Reports: Run a few regular reports and confirm they are working correctly.
 Integrations: Run a test of each of the customer's integrations to confirm that they are all working properly.
 Security: Sign on to OIM and verify that you can query all of the customer’s organizations. Create a new user and assign roles.
Special Considerations
 Single sign-on: Verify that you are still able to sign in successfully using Lightweight Directory Access Protocol (LDAP) accounts.
 E-mail notifications: If you previously had email notifications turned off in Test, you can control this as part of the customer’s user account settings. Make
sure that you have selected the Suppress User Account and Email Notifications option in the Manage Enterprise HCM Information task.
 Multiple languages: Verify that each of the language packs is still available and working properly.
Upgrade Problem Reporting
Log a Service Request (SR) through My Oracle Support (MOS), providing as much documentation as possible including pre-upgrade and post-upgrade
behaviors.
Oracle will provide problem reporting guidelines for each upgrade (For example, SR naming conventions, problem categorization types to use).

Backup & Disaster Recovery
Backup Policies
 Online backup of the database, code tree, and archive logs are performed by Oracle for Production environments.
 Backup is for Oracle's sole use in the event of a disaster
 Backup is made to disk daily and copied to tape twice a week.
 Backup is maintained at an offsite storage facility for 5 weeks.
 The offsite tape storage vendor (PCI certified for tape vault mgmt) takes the tapes offsite on a daily basis.
 Data stored in the backup tapes for the service is encrypted using strong cryptography (AES-256 bit) and a True
Random Number Generator (TRNG) for the generation of strong keys.
 Restoration of data from the stored backup tapes is tested twice annually.
Disaster Recovery Objectives
 Oracle provides a service option for customers requiring faster recovery responsiveness than that Oracle already provides to
its Cloud customers through its business continuity plan and service level objective of 99.5% uptime.
 The enhanced service provides contractual confirmation of DR efforts – recovery point of no more than one hour and a faster
recovery time objective (no more than 12 hours).

Know How to Work with Oracle SaaS
 Understand key differences between On-premise, SaaS by other providers, and Oracle SaaS.
 Oracle SaaS offers several services and resources to help you perform successful customer engagements.
 First, understand how to work effectively with Oracle Support. They are the primary team you should be contacting for any
issues or guidance you might need during implementation. There are few best practices to triage and escalate the issues. Be
aware of those and apply whenever situation arises.
 Oracle Operations team is like the IT team performing technical operations on your Cloud services. Be aware of how the
team performs certain routine pro-active tasks such as patching. Also know what specific cloud service-related requests the
Oracle Ops team will be performing on your behalf. Understand how you, as an implementer need to request for these.
 Oracle COE is available to assist and guide you during implementation. Understand its function and leverage Oracle COE
appropriately during or after the implementation.

2 cloud operations

Recommended

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to 2 cloud operations (20)

More from mohamed refaei (15)

Recently uploaded (20)

2 cloud operations