How to Change an Existing File How to Create a New File

20-10 Developers Guide for Oracle Application Integration Architecture Foundation Pack UtilityArtifacts All the Utility schemas and WSDLs are stored in: AIA_HOMEAIAMetaDataAIAComponentsUtilityArtifacts The folder structure convention followed is: UtilityArtifactsschemas UtilityArtifactswsdls

20.1.3.7 How to Change an Existing File

To change an existing file: 1. From JDeveloper, open the relevant file by browsing to AIAWorkstationAIA_ HOMEAIAMetaDataAIAComponentsPath to file 2. Make modifications. Review the upgrade safe extensibility guidelines provided in AIA artifact-specific chapters of the guide. 3. Save. 4. Upload to SOA-MDS appsAIAMetaDataAIAComponents. Refer to Section 20.1.3.15, Updating MDS .

20.1.3.8 How to Create a New File

To create a new file: 1. In JDeveloper, create a new file following the design and development guidelines provided in AIA artifact-specific chapters of the guide. 2. Copy the file to AIAWorkstationAIA_ HOMEAIAMetaDataAIAComponentsPath to file. 3. Upload to SOA-MDS appsAIAMetaDataAIAComponents. Refer to Section 20.1.3.15, Updating MDS . Accessing the Files in the AIA Components Folder Use the following protocol to access the AIA Components content from all the AIA service artifacts at design time and run time: oramds:appsAIAMetaDataAIAComponentsResource Path Name Example: oramds:appsAIAMetaDataAIAComponentsApplicationObjectLibrarySampleSE BLschemasCmuAccsyncAccountIo.xsd The WSDLs in the Enterprise Business Service Library use relative paths to refer to schemas in the Enterprise Object Library. Note: Place the file in this folder. Note: All of the files in the AIA Components folder use relative paths to refer to other files in the AIA Components folder, if needed. Building AIA Integration Flows 20-11 20.1.3.9 How to Work with AIAConfigurationProperties.xml in AIA_HOMEaia_ instancesINSTANCE_NAMEAIAMetaDataconfig AIA provides external configuration properties to influence the run-time behavior of system, infrastructure components, and services. These properties are provided as name-value pairs at the system, module, and service levels in AIAConfigurationProperties.xml. The AIAConfigurationProperties.xml supports two types of configurations: ■ System level, including module level Contains system-level configuration name-value pairs and module-level configuration name-value pairs within the system level. ■ Service level Contains service-specific configuration name-value pairs. The following XPath functions are provided to access the configuration name-value pairs in the AIAConfigurationProperties.xml: ■ aiacfg:getSystemProperty propertyName as string, needAnException as boolean returns propertyValue as string ■ aiacfg:getSystemModuleProperty moduleName as string, propertyName as string, needAnException as boolean returns propertyValue as string ■ aiacfg:getServiceProperty EBOName as string, serviceName as string, propertyName as string, needAnException as boolean returns propertyValue as string getSystemModuleProperty and getServiceProperty functions first look for the appropriate module and service property and if it is not found, they then look for a system property with the same property name. In all three functions, if a matching property is not found, the result depends upon the value of the needAnException argument. If need AnException is true, then a PropertyNotFound Exception is thrown; otherwise, an empty string is returned.

20.1.3.10 How to Add a New Property to AIAConfigurationProperties.xml