| Oracle® Retail Functional Artifacts Guide Release 14.1 E57325-01 |
|
 Previous |
 Next |
The purpose of this document is to provide detailed information about the following:
How artifacts are designed and packaged for release, as well as the standards used for their creation.
Version strategy and implementation of that strategy, as well as the standards used for base Business Objects.
Customization strategy and implementation of that strategy, including extension of base Business Objects.
The Oracle Retail Business Object (BO) is the name given to the logical representation of an Oracle Retail Business Entity. The definition of that object is in the form of an XML Schema (XSD). The schema represents the common object definition for business concepts, such as account, supplier, purchase order, and item.
Within Oracle Retail, the messages that flow between the retail applications are defined statically through these XML schemas (XSDs). These Business Objects are the message payloads, or the basis of message payloads for the Oracle Retail integration products, such as the Oracle Retail Integration Bus (RIB) and RIB Integration Gateway Services (IGS) and Web Service Providers created by the Retail SOA Enabler tool.
The Oracle Retail integration infrastructure products work with multiple technologies (for example, Java EE and PL/SQL). So they have different ways of representing the same functional XML message structure in the various technologies. The Business Object XSD is the common source used to generate the various manifestations of the BO (payloads) used within the infrastructure products and to ultimately communicate the Business Objects appropriately to the Oracle Retail API technology.
The XSDs are strict, and they are used by Oracle Retail standard tools to produce the design time physical objects used by the application's API technology (PL/SQL or Java), as well as the runtime validations used by the various integration components.
Retail Functional Artifacts is the collective name given to the package containing the base Business Object XSDs and the various representations of the same structure/definition in these different technologies. These representations include the following:
For Java EE, the artifacts are JAXB Java Beans. JAXB is a standard Java XML binding technology. It provides the mechanism to convert XML instances to Java objects (and vice versa) in a standard way. The JavaEE Web service infrastructure internally uses JAXB to marshall and unmarshall the SOAP messages. For every Business Object XSD, there is a corresponding JAXB bean.
For PL/SQL retail applications, the artifacts are Oracle Objects. These objects are user defined database objects that define the XML message structure inside the database. For every Business Object XSD, there is a corresponding Oracle Object SQL defined.
