Thursday Jan 17, 2013

Configuration Migration Assistant Part 4 - Migration Plans

The Configuration Migration Assistant is meta data driven. It uses the Oracle Utilities Application Framework meta data to drive the underlying engine to migrate the data. With the delivery of each product a predefined set of configuration objects are provided preconfigured to be used by sites. It is possible to extend these definitions and this next set of articles will introduce these objects and how to build your own configurations for custom objects.

Before we discuss the configuration objects there is one piece of information that you need to understand. For an object to be migrated using Configuration Migration Assistant it must have two attributes:

  • It must not have a system generated random primary key. These types of keys may vary from environment to environment and attempting to migrate data with these types of keys may result in unintentional results and even corruption. Configuration data tends not to use random system generated keys but Master and Transaction data does. Configuration Migration Assistant cannot be used for Master or Transaction Data. Master data is things like Accounts, Meters, Crews, Persons, Assets etc.. Transaction Data is data like Bills, Payments, Meter Reads, Tasks etc...
  • Fundamentally Configuration Migration Assitant uses Maintenance Objects to process data but each object to be migrated must have a Business Object for configuration purposes. The Business Object can be any valid Business Object definition. More guidelines about this are in Configuration Migration Assistant Overview (Doc Id: 1506830.1).

The first object to configure for Configuration Migration Assistant is the Migration Plan.  This object defines a primary Business Object and any directly related subordinate Business Objects that must be migrated as a single entity. The relationship between the business objects and the sequence of migration is configured in this object.

The following information is configured:

  • Instruction Sequence - The sequence number for the migration instruction. This is used to process the data in the correct order.
  • Instruction Type - This sets the migration instruction type. There are two values: Primary or Subordinate. There can only be one Primary Instruction Type per Migration Plan.
  • Parent Instruction Sequence - If the Instruction Type is Subordinate, then this is the Instruction Sequence for the parent object for this object. Subordinates can be related to other Subordinates to document multi-level structures.
  • Description and Business Object - The Business object for this instruction. The description is a free format field to allow you to document the instruction. Usually this is populated with a short description of the object.
  • Traversal Criteria Type and Traversal Criteria - This is a definition of how the subordinate is related to the parent object. Configuration Migration Assistant allows you to specify Constraints in the meta data, SQL Statements or XPATH statements to document the relationship. The latter is useful for relating complex business object relationships that arte buried in XML definitions. The Criteria Type determine which method you want to use to express the relationship and the Criteria is the statement to express the relationship. The online help contains examples and guidelines for the Criteria formats supported.
  • Next Migration Plan - Configuration Migration Assistant allows you to reuse Migration Plans and this field allows you to link Migration Plans for consistency. We will discuss this feature in future posts.
  • Algorithms - One of the features of the Configuration Migration Assistant is the ability to manipulate the data upon import. This is where the specification of the algorithm is performed. This is typically done on the target environment.

To do this use the Admin --> M --> Migration Plan menu option.

For example:

 Example Migration Plan

Note: Remember, the product ships with a predefined set of Migration Plans for you to use. You may not have to configure this unless you want to copy the provided plans to tailor them or add custom business objects.

Each object to migrate using the Configuration Migration Assistant must exist in at least one Migration Plan.

For more information about this aspect of the Configuration Migration Assistant and other aspects refer to the Configuration Migration Assistant Overview (Doc Id: 1506830.1) whitepaper available from My Oracle Support.  

Wednesday Jan 16, 2013

Configuration Migration Assistant Part 3 - Master Configuration

The first configuration step that must be performed for the Configuration Migration Assistant, as part of Oracle Utilities Application Framework V4., is to setup a Master Configuration Record for the Migration Assistant Configuration. This record sets up the locations of files exported and imported for each environment. It also sets the suffix for the files.

This must be performed once per environment and before any export or import activities are performed.

To setup this record the following process can be used:

  • Logon to the product environment you wish to configure using the browser
  • Navigate to the Admin --> M --> Master Configuration menu item.
  • Find the Migration Assistant Configuration item. If none, exists you can create it using the Add Action (+).
  • Edit the Migration Assistant Configuration Master Configuration Record by clicking on the name or Action field. For example:

Master Configuration

  • Specify the following on the edit dialog:
    • Export Directory - Directory to place export files into for exports initiated from this environment
    • Import Directory - Directory to get import files from for imports reqeusted for this environment
    • File Suffix - The file suffix (including the '.') to attach to the file automatically.The suffix is simply used to be able to denote the file. The choice of file suffix does not affect the format of the contents of the file at any stage.

Migration Configuration

  • Save the Record.

For the Export and Import Directories you can use any valid directory but the directory must be read writeable by the user you will use for the export and readable for the user you will use for the import. Security will be discussed in a later post.

From an implementation point of view these directories can be setup as follows:

  • You can use the same directories for import and export.
  • You can use different directories for import and export.
  • You can use a common directories or seperate directories for each environment. For example, you can specify a global set of directories to share files easily. If you use seperate directories you will have to manually transfer export files across these directories.

For more information about this aspect of the Configuration Migration Assistant and other aspects refer to the Configuration Migration Assistant Overview (Doc Id: 1506830.1) whitepaper available from My Oracle Support. 

Friday Jan 11, 2013

Configuration Migration Assistant Part 2 - Flows

To use the Configuration Migration Assistant facility in Oracle Utilities Application Framework V4. the are two main sets of step that must be performed:

  • Configuration - The Configuration Migration Assistant must be configured at an environment level to determine the locations of data exports and imports as well as definitions of the migration specifications.
  • Execution - Registering the intent to export and import data as well as physically exporting and importing the data. Once the data has been imported performing approval of specific changes and then applying the import data set.

These topics will be individually covered in subsequent entries in this blog to target specific settings. The flow diagrams illustrate a summary of the processes used in the Configuration Migration Assistant.

Configuration Flow

To configure the Configuration Migration Assistant the following must be performed:

Configuration Flow

  • Migration Master Configuration - Define the default location for import and export files generated by the Configuration Migration Assistant. Define the default file suffix for the export/import files. This task only has to be done once per environment and must be performed BEFORE the first export or import task is performed.
  • Define Migration Plans - Define the Business Object definitions and their relationships to migrate the group of Business Objects as a single unit. The sequence and relationship is defined for the associated child objects. The relationship, known as Traversal Criteria, is expressed as Constraint, SQL expression or XPath statement describing the related data.
  • Define Migration Requests - Define the groups of migration plans to migrate as a set including the selection criteria expressed as SQL expression, XPath statement or algorithm.

Execution Flow

Once configuration is complete on the source environment then the execution component of the feature can be used to perform migrations. The following flow summarizes these processes:

Execution Flow

  • Define Migration Export - Register the intent to export the data with the Migration Request to use for the export and the file name to use for the export. The Migration Master Configuration record for the environment is used to set the location and suffix. This process wont actually export the data, hence the word intent, it simply registers the fact that you want to export the data.
  • Export Data - Execute the Migration Monitor batch process to physically export all the active Migration Export requests using the specification on the Migration Export.
  • Define Migration Import - Register the intent to import the data file from the import directory. The migration import directory and file prefix are taken from the Migration Master Configuration record for the environment.
  • Import Data - Execute the Migration Monitor batch process to physically export all the active Migration Import requests using the specification on the Migration Import. At the is time the use of the Approval/Rejection process can be defaulted by change type. At this time a Migration Data Set is created to hold the changes.
  • Approval Process - If there are any manual changes that require approval can be manually approved. Regardless of whether approvals are required, the Migration Data Set must be marked Ready to Apply.
  • Apply Changes - Execute the Migration Monitor batch process to physically apply the changes. The Migration Data Set will display the status of each change at application time. Data is re-validated at the time of application to maximize data integrity.

Each of these processes will be expanded on in future blog entries with guidelines. For more information on this facility refer to Configuration Migration Assistant Overview (Doc Id: 1506830.1).

Tuesday Nov 20, 2012

Interfaces Reference Model available

With the implementation of an Oracle Utilities Application Framework based products, you can implement other Oracle technologies to augment your solution. There is a whitepaper available now to outline all the technology integrations possible with various versions of the Oracle Utilities Application Framework.

The whitepaper outlines the possible integrations and implementations of other Oracle technologies to address customer requirements in association with Oracle Utilities Application Framework based products.

The whitepaper covers a vast range of products including:

  • Oracle Fusion Middleware
  • Oracle SOA Suite
  • Oracle Identity Management Suite
  • Oracle ExaData and Oracle ExaLogic
  • Oracle VM
  • Data Options including Real Application Clustering, Real Application Testing, Data Guard/Active Data Guard, Compression, Partitioning, Database Vault, Audit Vault etc..

The whitepaper contains a summary of the integration solution possibilities, links to further information including product specific interfaces.

The whitepaper is available from My Oracle Support at KB Id: 1506855.1

Wednesday Aug 29, 2012

Implementing Oracle Exadata for Oracle Utilities Customer Care And Billing

In association with our performance team, a new whitepaper has been released for Oracle Utilities Customer Care And Billing that outlines the best practices for using Oracle Exadata with that product.

The advice in the whitepaper is based upon certification and performance testing performed by our internal performance teams to assit in sites implementing the database component of Oracle Utilities Customer Care And Billing on an Oracle Exadata platform.

It is recommended that the contents of this whitepaper be used alongside existing best practices for the Oracle Exadata platform.

The whitepaper is available from My Oracle Support under Implementing Oracle Exadata with Oracle Utilities Customer Care and Billing (Dod Id: 1486886.1)

Saturday Aug 18, 2012

Updated Technical Whitepapers

A number of whitepapers have had a few updates lately and have been republished on My Oracle Support. The whitepapers that have been updated are:

Implementing Oracle ExaLogic and/or Oracle WebLogic Clustering  (Doc Id: 1334558.1)

  • Updated sections for AIX installation

Production Environment Configuration Guidelines (Doc Id: 1068958.1)

  • Add new advice from our Black Belt team based upon customer feedback and experiences.
  • Added new advice from our Performance Testing team to optimize the settings for a product.

The full set of the available whitepapers will be updated over the next few months. Watch this blog and My Oracle Support for further announcements.

Tuesday Jul 31, 2012

Updated ExaLogic Guidelines whitepaper

The Implementing Oracle ExaLogic and/or Oracle WebLogic Clustering (Doc Id: 1334558.1) available from My Oracle Support has been updated with additional advice for products using the Oracle Utilities Application Framework.

The following changes have been made to the document:

  • Correction to the document to explicity outline that the SPLEBASE environment variable must be set prior to starting any node in the cluster for the product to use files not included in EAR/WAR files.
  • Added Best Practices section outlining addition performnce configuration suggestions and some advice for optimizing ExaLogic with Exadata.
  • Added advice for configuring JMS in a cluster. This is particularly useful for customers using JMS for product to product integration or using the Message Driven Bean functionality in Oracle Utilities Application Framework V4.x.
  • Added advice for Oracle Service Bus (OSB) integration in a clustered environment for customers using OSB in association with the Oracle Utilities Application Framework based product.

Wednesday Jul 25, 2012

Oracle ExaLogic advice for Oracle Utilities Application Framework products

The Oracle WebLogic Clustering for Oracle Utilities Application Framework whitepaper (Doc Id: 1334558.1), available from My Oracle Support, has been updated to now include advice for Oracle ExaLogic. To reflect the new information the document is now renamed "Implementing Oracle ExaLogic and/or Oracle WebLogic Clustering".

The Oracle ExaLogic additional advice includes the following:

  • Implementation of the SDP protocol for use with the online component of the product. This improves communication between the tiers.
  • Configuration of Oracle WebLogic settings for optimization with Oracle ExaLogic.
  • Configuration of ExaLogic GridLink Data Sources for online transactions.

The document can be used by customers and partners who are implementing Oracle WebLogic clustering with or without Oracle ExaLogic.

Wednesday Jul 18, 2012

OUAF Released (i.e. Service Pack 1)

In the past the Oracle Utilities Application Framework V4.1 supplied Group Fixes (GF1 - GF4 have been released). In line with other Oracle products, Oracle Utilities Application Framework now releases cumulative Service Packs on a regular basis instead of Group Fixes.

Service Packs now include all the fixes since the original release since the product was initially released. For new customers, you can install the original released product from the Oracle Delivery Cloud and then the latest service pack via My Oracle Support to keep up to date with fixes, enhancements and new platforms.

Along with the Service Pack is a new version numbering scheme. If you are familiar with other Oracle products and Oracle technology you will recognize the new numbering scheme. The new version number format is as follows:

X.Y.Z.A.B where

X.Y.Z is the version number of the product (as we originally quoted it). For example Oracle Utilities Application Framework V4.1 would be 4.1.0.
A is the Service Pack
B is reserved for special circumstances. Usually it is 0.

This means the new Service Pack brings Oracle Utilities Application Framework V4.1 up to officially. This is extremely important as when you register a bug or enhancement you need to quote the official release number so that our engineers can target the problem or enhancement to the right version of the product.

Service Pack 1 is available for download from My Oracle Support at Patch 13967347.

Monday Jul 16, 2012

Using Oracle Fusion Middleware targets with OUAF Based products in OEM 12c

One of the advantages of Oracle Enterprise Manager 12c is the ability to manage Oracle WebLogic directly from the console with or without the use of the Oracle WebLogic management packs. Obviously customers can manage more with the packs but some basic administration and monitoring capabilities can be used from the basic Oracle Enterprise Manager 12c installation.

With Oracle Utilities Application Framework V2.x and above, the use of Oracle Weblogic is different to the typical base use of Oracle WebLogic. The Oracle Utilities Application Framework uses Oracle WebLogic in what I call "embedded mode". Customers install Oracle WebLogic as per the standard Oracle WebLogic installation process but "point" the installation to the Oracle Utilities Application Framework to execute the product. The advantage of this for non-production is that you can share a single copy of Oracle WebLogic across multiple environments on a single machine easily and each environment is isolated operationally with its own domain and own administration server. The disadvantage is that Oracle Enterprise Manager 12c cannot easily recognize the installation using the Auto-Discovery functionality provided by that product.

All is not lost though, it is possible to use the functionality using the "Add Targets Manually" functionality to expose the Oracle WebLogic instance for each environment as a target to manage.

To use this facility you need the following installed and available:

  • Oracle Enterprise Manager 12c console and OMS somewhere in your architecture
  • The machines that house the environment MUST be registered to the OMS as managed targets of "Host" target type. This ensures the agent is deployed and working to those machines.
  • The instances of Oracle WebLogic to be registered for the environments must be executing. Oracle WebLogic instances that are not active will not be registered using this process.

From the "Setup" menu in Oracle Enterprise Manager 12c select "Add Targets Manually" from the "Add Target" menu. Select the "Add Non-host Targets using Guided Process" and select "Oracle Fusion Middleware" from the Target Type list. For example:

Add Targets Manually example

Use the "Add Using Guideed Discovery ..." button to initiate the process. This will display a dialog to manually add the Oracle WebLogic embedded target type.

To register an envieonment specify the following:

  • Administration Server Host - The host name used for WL_HOST in your environment. This host must be registered to Oracle Enterprise Manager 12c as a target so that the agent is redeployed.
  • Port - The port number assigned to the environment (WL_PORT).
  • Username - An account authorized to the Oracle WebLogic console. The Oracle Utilities Application Framework installer creates an initial user system that can be used if you have not got a site specific value for this user. This userid is used, by default, for all operations to the target. It must be an Administration account not a product account.
  • Password - The password configured for the Username.
  • Unique Domain Identifier - An unique identifier for the domain to denote within Oracle Enterprise Manager 12c. This is important and should be some value that means something for your admninistrator to understand. This also allows multiple targets per host to be defined easily. Make sure you do not use any embedded blanks and special characters for the name.
  • Agent - This is the default host and port for the OEM agent on that machine. Just for references and can be altered if the default port is different for OEM at your site.

For example:

 Example Oracle WebLogic manual target definition

Press "Continue" to complete the process. If the above parameters are correct then new targets should appear in the console as management targets. The Oracle WebLogic domain and each of the deployments will appear seperately in the target list. For example:

Example target discovery

The targets can now be managed and monitored using the facilites of Oracle Enterprise Manager 12c from the console.

For example:

Example Monitor/Management screen

You can repeat this process for each of your environments. This process does not need to be repeated as once a target is registered Oracle Enterprise Manager 12c will maintain the connection.

Thursday Jun 07, 2012

Threading Overview

One of the major features of the batch framework is the ability to support multi-threading. The multi-threading support allows a site to increase throughput on an individual batch job by splitting the total workload across multiple individual threads. This means each thread has fine level control over a segment of the total data volume at any time.

The idea behind the threading is based upon the notion that "many hands make light work". Each thread takes a segment of data in parallel and operates on that smaller set. The object identifier allocation algorithm built into the product randomly assigns keys to help ensure an even distribution of the numbers of records across the threads and to minimize resource and lock contention.

The best way to visualize the concept of threading is to use a "pie" analogy. Imagine the total workset for a batch job is a "pie". If you split that pie into equal sized segments, each segment would represent an individual thread.

The concept of threading has advantages and disadvantages:

  • Smaller elapsed runtimes - Jobs that are multi-threaded finish earlier than jobs that are single threaded. With smaller amounts of work to do, jobs with threading will finish earlier.

Note: The elapsed runtime of the threads is rarely proportional to the number of threads executed. Even though contention is minimized, some contention does exist for resources which can adversely affect runtime.

  • Threads can be managed individually – Each thread can be started individually and can also be restarted individually in case of failure. If you need to rerun thread X then that is the only thread that needs to be resubmitted.
  • Threading can be somewhat dynamic – The number of threads that are run on any instance can be varied as the thread number and thread limit are parameters passed to the job at runtime. They can also be configured using the configuration files outlined in this document and the relevant manuals.

    Note: Threading is not dynamic after the job has been submitted
  • Failure risk due to data issues with threading is reduced – As mentioned earlier individual threads can be restarted in case of failure. This limits the risk to the total job if there is a data issue with a particular thread or a group of threads.
  • Number of threads is not infinite – As with any resource there is a theoretical limit. While the thread limit can be up to 1000 threads, the number of threads you can physically execute will be limited by the CPU and IO resources available to the job at execution time.

Theoretically with the objects identifiers evenly spread across the threads the elapsed runtime for the threads should all be the same. In other words, when executing in multiple threads theoretically all the threads should finish at the same time. Whilst this is possible, it is also possible that individual threads may take longer than other threads for the following reasons:

  • Workloads within the threads are not always the same - Whilst each thread is operating on the roughly the same amounts of objects, the amount of processing for each object is not always the same. For example, an account may have a more complex rate which requires more processing or a meter has a complex amount of configuration to process. If a thread has a higher proportion of objects with complex processing it will take longer than a thread with simple processing. The amount of processing is dependent on the configuration of the individual data for the job.
  • Data may be skewed – Even though the object identifier generation algorithm attempts to spread the object identifiers across threads there are some jobs that use additional factors to select records for processing. If any of those factors exhibit any data skew then certain threads may finish later. For example, if more accounts are allocated to a particular part of a schedule then threads in that schedule may finish later than other threads executed.

Threading is important to the success of individual jobs. For more guidelines and techniques for optimizing threading refer to Multi-Threading Guidelines in the Batch Best Practices for Oracle Utilities Application Framework based products (Doc Id: 836362.1) whitepaper available from My Oracle Support

Tuesday May 01, 2012

Certification Matrix for Oracle Utilities Products

The platform certification matrix for the Oracle Utilities Products has been released and is available for use within My Oracle Support. The document contains information about the support platforms for the following products:

  • Oracle Utilities Customer Care and Billing.
  • Oracle Utilities Mobile Workforce Management.
  • Oracle Real-Time Scheduler.
  • Oracle Utilities Meter Data Management.
  • Oracle Utilities Smart Grid Gateway.
  • Oracle Utilities Framework.
  • Oracle Utilities Business Intelligence.
  • Oracle Utilities Work and Asset Management.
  • Oracle Utilities LODESTAR EIP.

The document is available under Certification Matrix for Oracle Utilities Products [KB ID 1454143.1].

The matrix document contained in the KB article is an up to date platform list for each product. This list should be checked prior to the installation of the documentation for the latest platforms. The platforms in the installation guides are the platforms at the time of publication and may be subject to change over time.

Wednesday Apr 11, 2012

Calling XAI Inbound Services from Oracle BI Publisher

Note: This technique requires Oracle BI Publisher which supports Service Complex Types. Web Services require credentials for authentication.

Note: The deafults for the product installation are used in this article. If your site uses alternative values then substitute those alternatives where applicable.

Note: Examples shown in this article are examples for illustrative purposes only.

When building a report in Oracle BI Publisher it may be necessary to call an XAI Inbound Service to get information via the object rather than directly calling the database tables for various reasons:

  • The CLOB fields used in the Object are accessible for a report.

Note: CLOB fields cannot be used as criteria in the current release.

  • Objects can take advantage of algorithms to format or calculate additional data that is not stored in the database directly. For example, Information format strings can automatically generated by the object which gives consistent information between a report and the online screens.

To use this facility the following process must be performed:

  • Ensure that the product group, cisusers by default, is enabled for the SPLServiceBean in the console. This allows BI Publisher access to call Web Services directly. To ensure this follow the instructions below:
    • Logon to the Oracle WebLogic server console using an appropriate administrator account. By default the user system or weblogic is provided for this purpose.
    • Navigate to the Security Realms section and select your configured realm. This is set to myrealm by default.
    • In the Roles and Policies section, expand the SPLService section of the Deployments option to reveal the SPLServiceBean roles.
    • If there is no role associated with the SPLServiceBean, create a new EJB role and specify the cisusers role, by default. For example:

 cisusers EJB role

  • Add a Role Condition to the role just created, with a Predicate List of Group and specify cisusers as the Group Argument Name. For example:

cisusers Role Condition

  • Save all your changes.
  • The XAI Inbound Services to be used by BI Publisher must be defined prior to using the interface. Refer to the XAI Best Practices (Doc Id: 942074.1) from My Oracle Support or via the online help for more information about this process.
  • Inside BI Publisher create your report, according to the BI Publisher documentation. When specifying the dataset, under the Data Model Report option, specify the following to use an XAI Inbound Service as a data source:

Parameter Comment
Type Web Service
Complex Type true
Username Any valid user name within the product. This user MUST have security access to the objects referenced in the XAI Inbound Service
Password Authentication password for Username
Timeout Timeout, in seconds, set for the Web Service call. For example 60 seconds.
WSDL URL Use the WSDL URL on the XAI Inbound Service definition as your WSDL URL. It will be in the following format by default:
  • <host> - Host Name of Web Application Server
  • <port> - Port allocated to Web Application Server for product access
  • <server> - Server context for server
  • <service> - XAI Inbound Service Name

Note: For customers using secure transmission should substitute https instead of http and use the HTTPS port allocated to the product at installation time.

Web Service Select the name of the service that shows in the drop-down menu. If no service name shows up, it means that Publisher could not establish a connection with the server or WSDL name provided in the above URL in order to get the service name. See BI Publisher server log for more information.
Method Select the name of the Method that shows in the drop-down menu. A method name should show in the Method drop-down menu once the Web Service name is selected.

For example:

  • Additionally, filters can be used from the Web Service that can be generated, required or optional, from the WSDL in the Parameter List. For example:

Example Filters

Wednesday Apr 04, 2012

Batch Best Practices and Technical Best Practices Updated

The Batch Best Practices for Oracle Utilities Application Framework based products (Doc Id: 836362.1) and Technical Best Practices for Oracle Utilities Application Framework Based Products (Doc Id: 560367.1) have been updated with updated and new advice for the various versions of the Oracle Utilities Application Framework based products.

These documents cover the following products:

Whilst there is new advice, some of which has been posted on this blog, a lot of sections have been updated for advice based upon feedback from customers, partners, consultants, our development teams and our hard working Support personnel.

All whitepapers are available from My Oracle Support.

Oracle Utilities Framework Batch Easy Steps

Oracle Support have compiled a list of common Questions and Answers for Batch Processing in Oracle Utilities Application Framework. Customers and partners should take a look at these questions and answers before posting any question to support to save time.

The Knowledge Base article is available from My Oracle Support under FW - Oracle Utilities Framework Batch Easy Steps (Doc ID 1306282.1).

This article answers the questions but also posts links to other documents including the Batch Best Practices for Oracle Utilities Application Framework based products (Doc Id: 836362.1) and Oracle Utilities CCB Batch Operations And Configuration Guide (Doc Id: 753301.1) for more detailed information and explanation.

Customers of Oracle Utilities Meter Data Management V2.0 and above, Oracle Utilities Mobile Workforce Management V2.0 and above, Oracle Enterprise Taxation and Policy Management V2.0 and above, and Oracle Utilities Smart Grid Gateway V2.0 (all editions) and above should refer to the Batch Server Administration Guide shipped with their products on eDelivery instead of using Doc Id: 753301.1.


Anthony Shorten
Hi, I am Anthony Shorten, I am the Principal Product Manager for the Oracle Utilities Application Framework. I have been working for over 20+ years in the IT Business and am the author of many a technical whitepaper, manual and training material. I am one of the product managers working on strategy and designs for the next generation of the technology used for the Utilities and Tax markets. This blog is provided to announce new features, document tips and techniques and also outline features of the Oracle Utilities Application Framework based products. These products include Oracle Utilities Customer Care and Billing, Oracle Utilities Meter Data Management, Oracle Utilities Mobile Workforce Management and Oracle Enterprise Taxation and Policy Management. I am the product manager for the Management Pack for these products.


« April 2014