1) Download these two JAR files from below link
http://www.oracle.com/technetwork/middleware/bpm/downloads/index.html
2) Run this Command in CMD
3) Once Popup opens up, come to 5th window by doing next-next
4) This Screen would come up post installation
Sometimes it is required to create a dropdown which should use base data as a variable rather than a binding.
1) Create a variable inside variables binding
2) Give variable name and create it of string type.
3) Select list binding type
4) Select second option from “Select List Binding Type”
5) Create a data mapping and use List Item configuration for default value of your dropdown.
Map code and for showing default option use Please Select
please write to us if you have any problem in configuring it at support@dnafizz.com
Sometimes its preferable to delete child record as well, on deleting parent table records.
Its quite easier open your association, go to behaviour, tick Composition Association and tick “Implement Cascade Delete”
1. Download and copy the ShareSoaInfraPartition.ear to access MDS Offline
or you can get it from this loction as well
https://code.google.com/p/kavin-sample-apps/downloads/detail?name=ShareSoaInfraPartition.ear
2. Connect to WLST and deploy the above application on the AdminServer. Use the WLST under $MIDDLEWARE_HOME/ oracle_common/common/bin.
3. Run the below command to export the metadata from the AdminServer. Change the values appropriate to your environment.
Command:
wls:/domain/serverConfig>
exportMetadata(application=’ShareSoaInfraPartition’,server=”,toLocation=”,docs=’/deployed-composites/deployed-composites.xml’)
Result:
Executing operation: exportMetadata.
Operation “exportMetadata” completed. Summary of “exportMetadata” operation is:
List of documents successfully transferred:
/deployed-composites/deployed-composites.xml
1 documents successfully transferred.
4. Open the deployed-composites.xml within deployed-composites folder under .
5. Delete the composite series or revision which is causing the problem and save the file.
6. Import the updated file under into MDS.
Command:
wls:/domain/serverConfig> importMetadata(application=’ShareSoaInfraPartition’,server=’AdminServer’,fromLocation=”,docs=’/deployed-composites/deployed-composites.xml’)
Result:
Executing operation: importMetadata.
Operation “importMetadata” completed. Summary of “importMetadata” operation is:
List of documents successfully transferred:
/deployed-composites/deployed-composites.xml
1 documents successfully transferred.
7. Restart your SOA server or soa-infra.
There is not Out of box feature to achieve this.
What I am proposing is a workaround which reduces manual effort of recreating views and Flex fields mapping at each environment.
Precisely we need to take export of these tables from particular environment where shared views and flex field mapping resides and copy it to the environment where we need to do it.
[SOAINFRA].[WFUserTaskView]
[SOAINFRA].[WFUserTaskViewGrant]
[SOAINFRA].[WFAttributeLabelMap]
[SOAINFRA].[WFAttributeLabelUsage]
Every BPEL and BPM project within SOA 11g should have a fault-policies.xml and a fault-bindings.xml.
You can recover from faults that occur in BPEL process and Oracle Mediator service components by
defining a fault policy. You define the fault policy in the fault-policies.xml and fault-bindings.xml during
design time. The fault policy describes how to handle runtime faults. If a fault is defined, it is
automatically handled by the fault policy during runtime. If a defined fault results in a condition in which
human intervention is the prescribed action, you perform recovery actions from Oracle Enterprise
Manager Console. Both individual fault recovery and bulk fault recovery are supported. You can
recover from individual faults in Oracle Enterprise Manager Console by modifying the following:
• Variable values in BPEL process service components
• Payloads in Oracle Mediator service components.
While these files can be highly customized, this document will cover a basic example that can
immediately be copied into each of your existing BPM projects.
fault-policies.xml
4
8
myFaultHandler.log
C:projects
fault-bindings.xml
