Other Custom Object Types

While the focus of this guide is custom tables and custom Java code, there are potentially other customization object types that need to be remediated before moving to the cloud. The table below outlines supported and non-supported extension types that need to be addressed as part of a migration:

Object Type	Description	Remediation Advice
Database Sequences	Sequences stored on the database used for identifier or other processing	Migrate code to use F1- DocumenSequenceAddUpd business service for sequence maintenance
JSP	These are code-complete screens written exclusively in JSP format	These need to be migrated to use UI Maps with simplified JSP code
JSP User Extensions	These are code snippets for legacy JSP based screens to override behavior on those screens	Not supported at the present time
FILE-PATH	Specifications of raw directories on the machine for batch processing. For example, directories to read or write files	Migrate to use aliases using the Cloud Object Storage Adapter
Environment Settings	Settings in various files in the architecture	Not supported as service provides the environment preconfigured.
Custom Threadpool definitions	Settings and architecture of batch execution threadpools	Migrate to use DEFAULT
Configuration Data (Admin Menu)	Administration menu data	Migratable using Content Migration Assistant
PL/SQL Code	Custom pl/sql functions	Not supported for security reasons
Triggers	Custom code on database	Not supported for security reasons
Other database objects	Other database objects that are not listed in the Custom Table support	Not supported
Linux/Unix Scripts	Custom scripts to manage the service	Not supported as service takes on that responsibility
Custom WS-Policies	Custom policies for inbound and outbound integration	Not supported as service provides prebuilt security