If you are upgrading to Oracle Database 12c for an Oracle Utilities Application Framework based product then you can use Oracle Enterprise Manager to manage your Information Lifecycle Management based data management solution.
To use it you simply install Oracle Enterprise Manager and then register the 12c database instance (PDB and non-PDB are supported) and then when selecting the database target use the Information Lifecycle Management menu option from the Administration --> Storage menus. For example:
This means that you can use Oracle Enterprise Manager as a viable alternative to ILM Assistant for Oracle Database 12c targets.
Last week I conducted three sessions on a number of topics. The presentations used in those sessions are now available from the Sessions --> Content Catalog on the Oracle OpenWorld site.Just search for my name (Anthony Shorten) to download the presentations in PDF format.
The sessions available are:
- Cost-Effective Data Management for Oracle Utilities Applications
- Streamline Utility IT Operations with Oracle Enterprise Manager
- Addressing Cybersecurity in Oracle Utilities Applications
I know a few customers and partners came to me after each session to get a copy of the presentation. They are now available as I pointed out.
A few times I have encountered issues and problems at customers that can defy explanation. After investigation I usually find out the cause and in some cases it is the way the implementation has created the data in the first place. In the majority of these types of issues, I find that interfaces or even people are using direct INSERT statements against the product database to create data. This is inherently dangerous for a number of reasons and therefore strongly discouraged:
- Direct INSERT statements frequently miss important data in the object.
- Direct INSERT statements ignore any product business logic which means the data is potentially inconsistent from the definition of the object. This can cause the product processing to misinterpret the data and may even cause data corruption in extreme cases.
- Direct INSERT statements ignore product managed referential integrity. We do not use the referential integrity of the data within the database as we allow extensions to augment the behavior of the object and determine the optimal point of checking data integrity. The object has inbuilt referential integrity rules.
To avoid this situation we highly recommend that you only insert data through the object and NOT use direct INSERT statements. The interface to the object can be direct within the product or via Web Services (either directly or through your favorite middleware) to create data from an external source. Running through the object interface ensures not only that the data is complete but takes into account product referential integrity and conforms to the business rules that you configure for your data.
Take care and create data through the objects.
The ConfigTools facility allows customers to implement customizations to Oracle Utilities products. A Best Practices whitepaper has been released to provide implementers additional advice and techniques for this facility to use it effectively.
The whitepaper covers such topics as:
- Overview of each ConfigTools objects such as Business Objects, Business Services, Query Zones, UI Maps, Data Areas etc including additional advice and techniques for efficient use.
- Using Fields, Managed Content, Standard components, Lookups and Extended Lookups for building flexible solutions
- Developing Multi-lingual solutions
I will be presenting three sessions at Oracle Openworld this year. Feel free to come to the sessions if you are attending and have a chat with me on your implementations and general feedback.
The three sessions I am conducting are:
- Cost-Effective Data Management for Oracle Utilities Applications [CON7815]
- Addressing Cybersecurity in Oracle Utilities Applications [CON7822]
- Streamline Utility IT Operations with Oracle Enterprise Manager [CON7961]
I will also be around the Oracle Utilities area for general discussions with customers and also be appearing at demo grounds.
See you there.
The Oracle Utilities family of products use Oracle standard technology such as the Oracle Database and Oracle Fusion Middleware (a.k.a. Oracle WebLogic). As we use those technologies the features and techniques for those products in Oracle's Maximum Availability Architecture can be applied to Oracle Utilities products.
Oracle Maximum Availability Architecture is a set of processes and guidelines for implementing high availability solutions. For Oracle Utilities products the following MAA solutions are applicable:
Other MAA documents are also applicable for Oracle Exadata, Oracle ExaLogic and Oracle VM. The guidelines and processes can be used to design and configure specific MAA solutions for Oracle Utilities products at your site.