FWPIP 12.2 Custom XSL Applied When Composite Redeployed, Not Pushed To MDS
(Doc ID 2433452.1)
Last updated on MARCH 10, 2019
Applies to:Oracle Process Integration Pack for Oracle Utilities Field Work - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
XSL - eXtensible Stylesheet Language
PIP/PIP-FW - Oracle Process Integration Pack for Oracle Utilities Field Work
MDS - Oracle Metadata Service
SOA - Service Oriented Architecture
Atempting to add custom logic to the file Xform_GetWorkOrderLineApptEBM_To_GetWorkOrderAppointmentABM_Custom.xsl at location /<PATH>/Middleware/user_projects/domains/FWPIPDEV_Domain/fwpip/soainfra/apps/services/industry/Utilities/OUMWM/ProviderABCS/GetWOLineApptWinAvailOUMWMUtilitiesProvABCSImplV2/Transformations in order to meet requirements.
However, when pushing the updated file to the MDS, using the command ant -f $SOA_HOME/aiafp/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=$DOMAIN_LOCATION/soa/aia/MDSUtils/UpdateMetaDataDP.xml -DPropertiesFile=$DOMAIN_LOCATION/soa/aia/bin/AIAInstallProperties.xml, it pushes the file under $AIA_HOME/AIAMetadata.
It appears the file is always getting updated under AIAMetaData, irrespective of the path used in the DP file.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!