« How many ABCS connectors for supporting multiple application instances | Main | AIA and SOA artifacts visibility »

Mapping AIA Canonical Objects best practices

Here are some of the best practices that are adopted by Oracle PIP Developers. If you are new to PIP and want to know what to look for when mapping Enterprise Business Message (EBM) in your XSLT transformation, please follow below best practices.

Dos:
 Select EBO based on Business Concept and not based on number of fields that match.
 Use Specification group cautiously, avoid if possible.
 Customize EBO for missing fields/Business Concepts
 Use Predefined corecom: prefixed Elements or DataTypes for customization.
 Refer to XMAN reports for understanding XREF/DVM and functional mapping of existing connectors
 Map Flags to Indicator types.
 Map fields semantically.
 Signup for FP and 2 day EBO training.
 Use appropriate Operations (EBMs).

Don'ts:
 Do not map just based on Data types
 Do not map just based on field name.
 Avoid creating your own data types.
 Don't Customize if Custom stub is not present.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on August 21, 2009 12:06 AM.

The previous post in this blog was How many ABCS connectors for supporting multiple application instances.

The next post in this blog is AIA and SOA artifacts visibility.

Many more can be found on the main index page or by looking through the archives.

Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type and Oracle