DVMs DVMs and Cross References

29-12 Developers Guide for Oracle Application Integration Architecture Foundation Pack

29.8 DVMs and Cross References

This section includes the naming standards for: ■ Section 29.8.1, DVMs ■ Section 29.8.2, Cross References

29.8.1 DVMs

When creating DVMs, the following naming standards should be followed:

29.8.1.1 Map Name

Map names: ■ Must start with the object name. This allows you to identify maps that belong to a certain object. The object name should be equivalent to the EBO name. ■ Should be followed by the element name that needs domain value mapping. ■ Must be uppercase. Pattern: {Object Name}_{Element Name} Examples: CUSTOMERPARTY_ACCOUNTTYPECODE, INVOICE_REJECT_REASON, SALESORDER_CARRIER_TYPECODE DVM File Name Examples: CUSTOMERPARTY95ACCOUNTTYPECODE, INVOICE95REJECT95REASON, SALESORDER95CARRIER95TYPECODE

29.8.1.2 Map Column Names

Map column names: Table 29–11 Naming Standards for Participating Application Services Artifact Name Name Registered in Mediator with the same name as exposed by the application. For example, BRMCUSTService, Account_BS Namespace Follows the namespace used by the application. Namespace Prefix Follow the namespace prefix standard. WSDL Follows the WSDL name as exposed by the application. WSDL Message Follows the message names exposed in the application WSDL. WSDL Port Type Follows the port types exposed in the application WSDL. WSDL Port Type Operations Follows the operation names exposed in the application WSDL WSDL Binding Follows the WSDL WSDL Service Follows the service name exposed in the application WSDL Oracle AIA Naming Standards for AIA Development 29-13 ■ Must be set to the participating application instance name abbreviation that the column value represents. This name can be the application name and its version, or an instance name in case two similar applications of the same version are integrated. The name must be a unique identifier for the application instance across the integration platform in the form: {Application Abbreviated Name}_ {Sequence Number}. The sequence number uniquely identifies multiple instances of the same application. ■ Must be uppercase. ■ A column named COMMON must be always added. This column contains the values used in the EBOs within the platform. Examples: COMMON, EBIZ_01, PSFT_01, SEBL_02, SEBL_03, PORTAL_01, IFLEX_01

29.8.2 Cross References