How to Audit SOA Composite Applications at the BPEL Activity Level
This section describes how to create and configure the audit policy and audit policy binding files.
To audit SOA composite applications at the BPEL activity level:
- Create and configure an audit policy file (for example, named
audit-policy.xml) that defines the audit level settings for the BPEL activities. The file can have any name and must follow the schema described in the preceding section.<auditPolicies xmlns="http://schemas.oracle.com/bpel/auditpolicy" xmlns:bpel="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" version="1.0"> <auditPolicy name="whilePolicy"> <!-- enabling this will cause all assign activities to not log --> <!-- anything to the audit trail --> <activity type="bpel:assign" auditLevel="production"/> <!-- enabling this will cause all scope activities and all --> <!-- enclosed activities to not log anything to the audit trail --> <activity type="bpel:scope" auditLevel="production"/> <!-- enabling this will cause all while activities to log with --> <!-- minimak level --> <activity type="bpel:while" auditLevel="production"/> <activity type="bpel:reply" auditLevel="production"/> <activity type="bpel:flow" auditLevel="production"/> <activity type="bpel:switch" auditLevel="off"/> <activity type="bpel:terminate" auditLevel="production"/> <activity type="bpel:empty" auditLevel="development"/> <activity type="bpel:wait" auditLevel="production"/> <activity type="bpel:throw" auditLevel="off"/> <activity type="bpel:catchAll" auditLevel="production"/> <activity type="bpel:sequence" auditLevel="off"/> <activity type="bpel:receive" auditLevel="production"/> </auditPolicy> </auditPolicies>Note:
To enable BPEL extensions to be audited, enter
bpelx:execwith an appropriate auditing level (for example,production).<activity type="bpelx:exec" auditLevel="production"/>
- Create and configure an audit policy binding XML file (for example, named
audit-binding.xml) that binds the audit policy to the BPEL process. The file can have any name and must follow the schema described in the previous section. This example uses the wildcard option to enable all BPEL processes that begin withmyProcessto be audited. Several other auditing options have been commented out.<auditPolicyBindings xmlns="http://schemas.oracle.com/bpel/auditpolicyBinding" version="1.0"> <!-- enabling this will cause all processes in the domain to use this --> <!-- policy audit --> <!-- <process auditPolicyName="whilePolicy" name="BPELProcess*"/> --> <!-- enabling this will cause all processes that start with the name --> <!-- myProcess to use the audit policy 'noLoops' --> <process auditPolicyName="noLoops" name="myProcess*"/> <!-- enabling this will cause all processes --> <!-- process auditPolicyName="noAssign" name="*"/> --> </auditPolicyBindings>
- Place the XML file in the same directory as the
composite.xmlfile. - Define the
audit-policy.xmlandaudit-binding.xmlfiles in thecomposite.xmlfile.<property name="oracle.composite.bpelAuditPolicyFile">audit-policy.xml</property> <property name="oracle.composite.bpelAuditBindingFile">audit-binding.xml</property>
- Deploy the SOA composite application.