2. CON7911: Building the Roadmap to a Successful Oracle Commerce Upgrade
Oracle Open World
Brian Benjamin
Consulting Practice Manager
Oracle Commerce Consulting

4. Program Agenda 1
Roadmap Approach Scoping Your Upgrade Planning Technical Steps to be Considered 2 3 4

5. Approach Scope Defined Planning Design Development GO Live
Testing & Prepare
Load & Performance Testing
Env Readiness (STAG/PROD), Cut-Over Activities
GO Live

6. Set your Objective
Scope your upgrade project to focus on your primary objective
Determine timing of upgrade
Review 3rd party supported platforms matrix
Identify all components of hardware and software stack that will be required to upgraded as a part of the Commerce software upgrade

7. What to Include New version features – which ones and how many?
Option 1 - Limit scope to upgrading the software platform and release new features after the platform upgrade
Option 2 – Implement several new features along with the software platform upgrade
Cut-over approach
Option 1 - In-place upgrade
Option 2 - Parallel production environments

8. Planning The more you plan, the smoother the upgrade
Start with review sessions to understand the current state of your platform.
Conduct review sessions for application architecture, hardware / software stack, database layout and definition, 3rd party integrations, individual components like BCC, CSC, Store Front, Oracle Commerce Guided Search
Identify only the components that need to be modified as a part of the upgrade
Validate upgrade approach and the migration path to be used
Determine the Search migration path

9. Planning Upgrade or Migration?
Legacy ATG Search and Oracle Commerce Guided Search
Upgrade or Migration?
Oracle Commerce Guided Search (Endeca) is the Search Engine for v11.0 forward
Legacy ATG Search is phased out for Commerce Service Center (CSC) as of v11.0
It is important to note that data is not automatically migrated for profile and order searches. The removal of ATG Search means that all profile and order data needs to be re-indexed via a baseline index.

10. Planning The Dynamo-based assembler APIs are recommended
Legacy ATG Search to Oracle Commerce Guided Search
The Dynamo-based assembler APIs are recommended
Do you intend to mange the user experience with Oracle Commerce Experience Manager?
Reconsider the deployment sizing from an Oracle Commerce Guided Search/Experience Manager point of view

11. Preparing Schemas for Oracle Commerce v11.1
Run the 9.x to 10.0.x Migration Kit
Run the to 10.1 Migration Kit
Run the to 10.2 Migration Kit
Run 10.2 to 11.0 Migration Kit
Run the 11.0 to 11.1 Migration Kit
Upgrade From 9.x
Run the 10.0.x to 10.1 Migration Kit
Upgrade From 10.0.x
Upgrade From 10.1.x
Upgrade From 10.2.x
Upgrade From 11.0

12. Preparing Web / Application Layer
Re-configure web servers / firewall
Upgrade webserver layer, if mandated by the 3rd party support matrix
Web Layer
Re-configure application server layer
Upgrade application server versions, if mandated by the 3rd party support matrix
Application servers
Install Oracle Commerce 11.0 on a build server
Update build scripts
Create / modify build tasks on the build server
Build process

13. Design Considerations
Oracle Commerce
Analysis and design of the individual components – Store Front, BCC, CSC, Oracle Commerce Guided Search, etc.
Generate design for how the components are going to change as a part of the upgrade
Identify areas of improvement (to be in tune with best practice recommendations) post upgrade

14. Design Considerations
Upgrading Oracle Commerce Guided Search
Recommend using the Assembler API, this API will get everything necessary for your page from Oracle Commerce Guided Search, and other systems, in a single request
Take advantage of the Oracle Commerce Guided Search integration to quickly index your Product Catalog data with OOTB components
If you use the OOTB integration components you’ll need to use the Deployment Template for Product Catalog Integration

15. Design Considerations
Legacy ATG Search to Oracle Commerce Guided Search
You should use the Assembler API, if you are a Guided Search customer (no Experience Manager) since packaged Assembler queries are available to use
Index your data via the OOTB components as long as you have Oracle Commerce or later
Design your records to be as lightweight as possible, less records is better
Only add to the Thesaurus entries and stop words that make logical sense. We have guidelines available. Endeca is more capable from a linguistic point of view.

16. Development Upgrade the individual components
Coding and Testing
Upgrade the individual components
Validate the upgraded platform in your DEV environment
Build testing plan – be thorough and conservative in your estimates
Plan for cut-over activities and build an executable play book, and rehearse

17. Upgrade at a Glance: Technical Tasks
Pre-Upgrade Tasks
Installation
Database Migration
Application Upgrade
Pre-Go Live Tasks
Backup Database
Backup Publishing Data
Complete all CA Projects
Shutdown all Application Servers
Allocate new Endeca servers
Install Oracle Commerce Platform
Copy Oracle Commerce Store Front module: Configure Build & Deploy to new Environment
Install Oracle Endeca Commerce (MDEX, Platform Services, Tools and Frameworks & CA)
Review DB Migration Scripts
Execute Scripts
Review Migration Notes
API/Library updates
Iterative resolution of code/referential errors
Perform Endeca Migration steps as per documents
Re-index Endeca Data
Launch full deployment to all workflow targets
Clear browser caches
Clear application server cache
Regenerate Web Services
Test upgraded platform & application
Typical sequence of upgrade is:
Database schema migration
Data migration
Build and release process validation
Code refactoring
Configuration changes – CA and CSC configurations
Validate deployed code after upgrade

18. Pre-Upgrade Tasks Backup Database Backup Publishing Data
Prepare
Backup Database
Set restore point
Replicate new DB for upgrade
Backup Publishing Data
Complete Content Administration Projects
Project workflow should be empty
It is important to backup your data prior to upgrade. Application platform upgrade is a critical change to a live system. The most important data stores in Oracle Commerce Platform reside mostly in the Database and some in the file system.
Versioned system needs to be in synchronized state, with no pending transaction before the migration. This not only ensures data integrity but also minimize possibility of data corruption during the process of upgrade. If possible, it is recommended that the versioning system be re-initialized after the upgrade, if possible.
Shutdown ATG servers: Because you cannot change the engine of a running car. However, we have performed migration with zero downtime (which is not recommended) for clients with specific needs. The best practice is to have an adequate downtime to streamline the migration process.

19. Installation Install Oracle Commerce Platform
Install and Configure
Install Oracle Commerce Platform
Copy Oracle Commerce StoreFront module
Configure build & deploy to point to new destination
Install Oracle Commerce Guided Search/Experience Manager (MDEX, Platform Services, Tools & Frameworks and CAS)
It is important to backup your data prior to upgrade. Application platform upgrade is a critical change to a live system. The most important data stores in Oracle Commerce Platform reside mostly in the Database and some in the file system.
Versioned system needs to be in synchronized state, with no pending transaction before the migration. This not only ensures data integrity but also minimize possibility of data corruption during the process of upgrade. If possible, it is recommended that the versioning system be re-initialized after the upgrade, if possible.
Shutdown ATG servers: Because you cannot change the engine of a running car. However, we have performed migration with zero downtime (which is not recommended) for clients with specific needs. The best practice is to have an adequate downtime to streamline the migration process.

20. Database Migration Review DB Migration Scripts Execute Scripts
Schema and Data Migration
Review DB Migration Scripts
Check if DB conforms to OOTB Oracle Commerce
Check that tables and indices exist in DB schema
Execute Scripts
Execute with appropriate DB user
Execute using “nohup”
Monitor logs
Oracle Commerce Platform contains a highly configurable proprietary Object Data Model (Repository – Data Anywhere Architecture), which maps relational data in Database to the Object model in the application. From a database administration standpoint, it is important to understand this ORM strategy in place within the application especially when designing or extending a commerce solution, it is critical that this is accounted. DB migration scripts respect this ORM strategy and expects that any customization being done by the customer have undergone architecture and design which conforms to the OOTB data granularity and division into database schemas. The complexity in DB migration is proportional to the amount of deviation in relational data architecture from the Product default.

21. Application Migration
Review Migration Notes
For applications that have their own migration-related requirements, beyond the database schema
Any applications not listed the Migration Notes can be assumed to have no additional migration steps
API/Library updates
Some classes & components might have been deprecated
There might be new OOTB functionalities that can be leveraged
Iterative resolution of code/referential errors
Identify and resolve application errors (e.g. ClassNotFoundException, etc.)
There are two fundamental pieces in application (or codebase and configuration) upgrade:
Remove ‘dead code’ – code which is no longer valid since the underlying dependencies (classes and components) have either been deprecated or removed form the Platform
Assessment of custom functionalities developed in the old Platform and attempt to replace with OOTB features and leverage Oracle Support (reduce custom code sustenance cost)
It may take more than one iteration to address all code errors and bring the custom codebase up to the migrated/destination platform version.

22. The CIM Migration Tool
With the Oracle Commerce 11.0 release, much of the migration process is performed by a new utility: The Configuration and Installation Manager (CIM) Migration Tool
This tool automates schema and data migration based on your current installation and your installed migration kits

23. Test and Prepare System Integration Testing User Acceptance Testing
Get Ready
System Integration Testing
User Acceptance Testing
Load / Performance Testing
Prepare for launch
Cut-over and Launch

24. Pre-Go Live Tasks Launch full deployment to all workflow targets
Before Launch
Launch full deployment to all workflow targets
Clear Browser caches
Clear application server caches
Regenerate Web Services
Run catalog exports to MDEX
Test upgraded platform & application

25. Go Live Restart all web / application servers
Launch
Restart all web / application servers
Check traffic is flowing to new web / application layer
Check application working internally and externally
Check monitoring systems – monitor logs
Check analytics to ensure conversion, order volume, average order value all as expected
Keep a close eye on until you have enough traffic to raise your confidence levels

26. Post Go-Live Continue to monitor traffic patterns and metrics
After Launch
Continue to monitor traffic patterns and metrics
Continue to monitor resource utilization on web, app and database layers
Continue to check analytics to ensure conversion, order volume, average order value all as expected and are sustainable
Start prioritizing the list of ‘nice to have’ features that were identified as a part of the scoping exercise

27. Questions?

30. Appendix

31. Application Migration: Web Commerce
A major feature of Oracle Commerce 10.1 was the merge of Commerce B2B and B2C features:
If you are using the B2BCommerce module, then dependencies need to be updated (applies only if your current version is older than 10.1)
All commerce pipeline changes must be accounted for in migration

32. Application Migration: Business Control Center
Merchandizing
If you are using view mappings, then all custom view mappings must be considered for migration
Migrate the versioned file assets
Update custom workflows
Update deployment topology

33. Application Migration: Commerce Service Center
CSC
Legacy ATG Search within CSC was removed in version 11.0
Upgrade the JSPs
Upgrade any form-handlers as applicable

34. Application Migration: Other Miscellaneous Applications
Other Applications and Integrations
Update internal (DPI) user roles in database
With each version, new internal roles and users have been added for new functions as well as more granularity in access control
This applies to BCC and CSC
REST WebServices Migration
Regenerate WebServices to update new API references

35. Application Migration: Oracle Endeca Commerce
Perform Endeca Migration steps as documented
Update Configuration to point to new CAS instance
Re-Index data
Test updated Experience Manager / Oracle Endeca Commerce environment