1Z0-451: Monitoring and managing SOA 11g Deployment

This is part of 1Z0-451: Oracle SOA Foundation Practitioner Exam

<< Previous

* Deploy new composite application for the first time
* Deploy a new revision (e.g. 2.0) along with old revision (e.g. 1.0). Latest revision becomes the new default revision.
* A SOA bundle (ZIP file) containing multiple SOA composite application revisions (e.g. 2.0, 3.0, 4.0)

* Click SOA Infrastructure Menu:

* Right click SOA > soa-infra

* From Deployed Composites > Deploy…

* Right click any deployed composite

* Need to specify partition in hwtaskflow.xml file in adfmsrc directory.

<hwTaskFlows
 xmlns="http://xmlns.oracle.com/bpel/workflow/hwTaskFlowProperties">
   <ApplicationName>worklist</ApplicationName>
   <LookupType>LOCAL</LookupType>
   <TaskFlowDeploy>false</TaskFlowDeploy>
   <PartitionName>partition2</PartitionName>

* Access Redeploy menu the same way as accessing Deploy menu
* Replaces the old version if one exists
* Existing running instances changed to stale state.
– Audit trail details still available
– Flow trace details still available.

* Access Undeploy menu the same way as accessing the Deploy menu
* Existing running instances changed to stale state.
– Audit trail details still available
– Flow trace details not available.

* Deploying SOA Composite Applications

* Access Test page:

* OWSM Security Policies

* HTTP Basic Auth

* Advanced

* None

* Open Deployed Composites tab
* Select the composite (no check box, need to select a row like in spreadsheet)

* Search utility
* List of instances

* Delete, Abort

* Delete With Options

* Instances without any associated composite application
* Orphan instances can only be deleted by purge script, i.e. can not be deleted using Delete All Instance

* Support individual and bulk recoveries of BPEL and Mediator service components
* BPEL needs fault policy configuration of ora-human-intervention action
* Human task service component faults are recovered from Worklist
* Recoveries are performed from Faults and Rejected Messages tab

* Test cases are
– created in JDeveloper
– included in SOA Composite
– deployed and administered from EM
* Tested from Unit Tests tab

* Managed from Policies tab

* See this post for a tutorial

* Original design-time composite
* Post deployment changes
– in the rules dictionary
– domain value maps (DMVs)
– binding component properties
– audit level settings
– payload validation status
– policy attachment

* Partition logically groups composite applications into groups
* Bulk lifecycle management tasks can be performed on a partition to include all composite applications

* All BPEL and BPMN sensors are enabled by default.
* Sensors can only be disabled per component type

* Managing SOA Composite Applications

* Centralized management console: monitor availability and performance of complete SOA environemnt.
* Discovery and service modeling: can discover composite apps, SOA Infra, BPEL, OSB services
* Runtime governance
* Infrastructure management: monitor availability and performance of SOA Infra components
* Configuration management:
* Deployment automation
* Adapter metrics
* Business-IT alignment: BAM/EM
* Service level management
* Application dependency and performance
* Historical analysis and reporting
* Instance tracing

* http://www.oracle.com/technetwork/oem/grid-control/overview/ds-soa-mgmt-pack-1-128301.pdf
* Overview of Oracle SOA Management Pack Enterprise Edition
* Oracle® Fusion Middleware 2 Day Administration Guide 11g Release 1 (11.1.1)