Migration to PPCS Cloud
This chapter of the document consists of information related to migration process of PPS Desktop to Cloud based solution.
Contracting Process/Tenant Creation / Setup in OIC Portal / Contracting Process
Work with Oracle’s Contracting staff to get the Tenant created in the OIC Portal along with the agreed licensing terms on seat count, expiry dates, etc.
Library Migration
The Tenant administrator will be responsible for updating the existing library for cloud deployment. The Tenant may have a separate contract with Oracle to assist with these activities however the main goals are to:
- Migrate resource maintenance activities to Studio and make sure Library is in RDBMS format.
- Review Men.Res and available actions. Compare to sample in Appendix to see if there’s anything unique that must be added. Items such as Send and Receive WIP, Pack WIP DB, etc may no longer be applicable.
- Review WIP – all WIP must be either deleted or completed before moving to the cloud. We will not support Cloud migration of WIP transactions.
- Review Archive – Determine if existing archive content should be migrated to the Cloud environment and develop an approach to do so, evaluating archive index and content.
- Review configuration files – split options into those that are controlled by the Tenant within each environment and those that are set on the server by the AMS team ; items such as directory locations and FTP controls.
Undo Existing setup
Uninstall the existing PPS setup from local machine.
Basic Environment Setup
Review the Environment setup needed for allowing the Library Migration activity
- Download PPCS client from OIC Portal, and install it.
- JDBC-ODBC connectivity / setup
- MRL Preparation/Changes
- INI changes
- DAP.INI changes
These activities will occur for each library, there will be additional effort for each tier within the cloud (test, staging, and production).
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal notices.