X

Announcements and Technical Advice for the Oracle
Utilities product community from the Product Management team

  • October 13, 2019

Using Metadata to Identify Code to Remediate for the Cloud

Anthony Shorten
Senior Principal Product Manager

The Oracle Utilities Application Framework is meta data based. Some extension types are defined, in meta data, to define them to the Oracle Utilities Application Framework to augment base functionality to satisfy specific requirements. It is possible using a number of SQL statements against that meta data to identify the code. The following configuration objects can be identified in this manner.

Extension Type Key Object Remediation Advice
Custom Java/COBOL Based Batch Programs Batch Control Convert to Plug In Batch
Custom Java/COBOL Based Algorithms Algorithm Type Convert to Scripting and/or Groovy
Custom Java/COBOL Based Foreign Key References (Legacy) Foreign Key Convert to Scripting and/or Groovy
Custom Java Based Audit Programs Audit Convert to Scripting and/or Groovy
Custom COBOL Program Components Program Components Transition to Algorithms
Custom FILE-PATHs on Batch Programs Batch Control Convert to File Adapter definitions
Custom Tables Table Convert to base objects
Custom External System XSL External System Convert XSL to Managed Content
Custom Inbound Web Service XSL Inbound Web Services Convert XSL to Managed Content
Custom Database Objects Data Dictionary Remove Custom Database objects and replace code using objects

The SQL can be used to identify the objects to remediate and then the appropriate action taken to remediate the object.

Additionally the following objects are not available in the Oracle Utilities SaaS Cloud:

  • Custom XAI Classes - Not necessary in Oracle Utilities SaaS Cloud implementations.
  • Custom Route Types - MPL/XAI is not supported in the Oracle Utilities SaaS Cloud.
  • Custom XAI Inbound Web Services (Business Adapter) - XAI should be migrated prior to moving to the Oracle Utilities SaaS Cloud.
  • Custom XAI Rules - MPL/XAI is not supported in the Oracle Utilities SaaS Cloud.
  • Custom JMS Senders - Direct JMS integration not possible. Consider using Oracle Messaging Service with Oracle Integration Cloud.
  • Custom JMS Receivers - Direct JMS integration not possible. Consider using Oracle Messaging Service with Oracle Integration Cloud.
  • Custom JDBC - MPL/XAI is not supported in the Oracle Utilities SaaS Cloud.
  • Custom JNDI - JNDI Resources have replaced with equivalents.

For details of the SQL statements and remediation advice to use, refer to the Planning for the Cloud whitepaper in the Software Configuration Management Series (Doc Id: 560401.1) available from My Oracle Support.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.