BPEL EJB Transaction Timeout

See more information in Oracle document 880313.1.

These instructions can also be found here: Can I configure EJB Transaction Timeout through MyST

Step 1:

NOTE: This property is applied via the MyST 'update' action only when soa-infra is shutdown.

Modeling > Platform Blueprint

Click Products > Oracle SOA Suite

Add a parameter

Shutdown the SOA managed servers in order to apply these changes

Run the MyST 'update' action to apply changes to soa-infra application

SOA MBEANs

Below is a working example for configuring some of the commonly tuned SOA Mbean properties.

NOTE: These properties are applied via the MyST 'configure-soa' action and when soa-infra is running.

Step 1: Edit the Platform Blueprint

Navigate to the Platform Blueprint which you want to change in MyST Studio ("Modeling" > "Platform Blueprints")

Click "Edit Configuration"

Go to "Global Variables".

Click "Edit" then "Edit Bulk".

Add the following properties.

oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_CACHE_AGE=2592000000
oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_WAIT_TIME=1800000
oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_USE_CACHED_RESULTS=true LargeRepository=true

Click "Done" then "Save".

Go to "Products" > "Oracle SOA Suite".

Click "Edit" then under "Name-Value Parameters" click "Edit Bulk".

Add the following properties. (Note: audit-level should already exist so only needs to be edited - not created)audit-level=Production

bpel-AuditLevel=production
bpel-BpelcClasspath=/u03/app/oracle/admin/domains/tbpm5_domain/mserver/tbpm5_domain/lib/gen_credentials_client-1/0.jar:/u03/app/oracle/product/12.1.3/tbpm5_domain/soa/soa/modules/oracle.bpm.composer.webapp_11.1.1/commons-codec-1.2.jar
bpel-RecoveryConfig.RecurringScheduleConfig.maxMessageRaiseSize=50
bpel-RecoveryConfig.RecurringScheduleConfig.startWindowTime=00:00
bpel-RecoveryConfig.RecurringScheduleConfig.stopWindowTime=23:59
bpel-RecoveryConfig.RecurringScheduleConfig.subsequentTriggerDelay=900
bpel-RecoveryConfig.StartupScheduleConfig.maxMessageRaiseSize=0
bpel-RecoveryConfig.StartupScheduleConfig.startupRecoveryDuration=0
bpel-RecoveryConfig.StartupScheduleConfig.subsequentTriggerDelay=900
bpel-SyncMaxWaitTime=200
bpmn-RecoveryConfig.RecurringScheduleConfig.maxMessageRaiseSize=0
bpmn-RecoveryConfig.RecurringScheduleConfig.startWindowTime=00:00
bpmn-RecoveryConfig.RecurringScheduleConfig.stopWindowTime=00:00
bpmn-RecoveryConfig.RecurringScheduleConfig.subsequentTriggerDelay=900
bpmn-RecoveryConfig.StartupScheduleConfig.maxMessageRaiseSize=0
bpmn-RecoveryConfig.StartupScheduleConfig.startupRecoveryDuration=0
bpmn-RecoveryConfig.StartupScheduleConfig.subsequentTriggerDelay=900
soa-infra-EMDurationWindowUnits=minutes
soa-infra-EMDurationWindowVal=1
workflow-AcknowlegdeFyiUponRead=false
workflow-HWFFailureRetryCount=1
workflow-MaxNumberOfEmailAttachments=-1
workflow-MaxSizeOfEmailAttachmentsInKB=1

Click "Done" then "Save".

Go to "WebLogic Domains" and expand the domain.

Then, go to "WebLogic Clusters" and click on the SOA cluster.

Set the "Frontend Host" to `acme.soacorp` and "Frontend Http Port" to 80.

Click "Save".

Click "Apply Changes"

Step 2: Update Platform Model based on the Blueprint changes

Go "Modeling" > "Platform Models"

Select the Platform Model corresponding to the previously edited Platform Blueprint

Go to "Actions" and select "Update"In the dialog box select "Update to latest draft" (assuming the Platform Blueprint was edited in the same version that the model is currently on).

Click "Update".

Step 3: Run Configure SOA Action

Now that the Platform Model has been updated to incorporate the recent Platform Blueprint changes, we can run the Configure SOA action.  

From the Platform Model go to to "Actions" and select "Control"  

Select the "Custom" action and enter the "Command" as configure-soa.

Click "Execute"

Once the action has completed click "View" under "Execute Log" to see the changes made.

Configure SOA advanced properties as part of Provisioning

The above SOA configuration step can be configured to automatically run at the end of platform provisioning by adding action.configure.post=configure-soa in the Global  Variables of the Platform Blueprint

Summary of Advanced SOA Properties

This is a non-exhaustive list of available SOA/BPEL/EM/Mediator/BPMN Mbeans attributes that can be configured in MyST Studio.

EM AttributeComponent in MyST StudioName-Value Parameter in MyST StudioAvailable SinceSoaInfraConfig > AuditLevelBlueprint > Products >audit-level2.0.0+SoaInfraConfig > EMDurationWindowValBlueprint > Products > Oracle SOA Suitesoa-infra-EMDurationWindowUnits                                         4.0.0+SoaInfraConfig > EMDurationWindowValBlueprint > Products > Oracle SOA Suitesoa-infra-EMDurationWindowVal                                           4.0.0+SoaInfraConfig > ServerURLBlueprint > WebLogic Domains > (domain name) > WebLogic Clusters > (soa cluster)Automatically calculated from "Frontend Host" and "Frontend Http Port"2.0.0+SoaInfraConfig > CallbackServerURLAs aboveAs above2.0.0+MediatorConfig > AuditLevelBlueprint > Products > Oracle SOA Suiteaudit-level1.0.0+BPELConfig > AuditLevelBlueprint > Products > Oracle SOA Suiteaudit-level1.0.0+BPELConfig > SyncMaxWaitTimeBlueprint > Products > Oracle SOA Suitebpel-SyncMaxWaitTime4.0.0+BPELConfig > BpelcClasspathBlueprint > Products > Oracle SOA Suitebpel-BpelcClasspath4.0.0+BPELConfig > RecoveryConfig > RecurringScheduleConfig > maxMessageRaiseSizeBlueprint > Products > Oracle SOA Suitebpel-RecoveryConfig.RecurringScheduleConfig.maxMessageRaiseSize4.0.0+BPELConfig > RecoveryConfig > RecurringScheduleConfig > startWindowTimeBlueprint > Products > Oracle SOA Suitebpel-RecoveryConfig.RecurringScheduleConfig.startWindowTime4.0.0+BPELConfig > RecoveryConfig > RecurringScheduleConfig > stopWindowTimeBlueprint > Products > Oracle SOA Suitebpel-RecoveryConfig.RecurringScheduleConfig.stopWindowTime4.0.0+BPELConfig > RecoveryConfig > RecurringScheduleConfig > subsequentTriggerDelayBlueprint > Products > Oracle SOA Suitebpel-RecoveryConfig.RecurringScheduleConfig.subsequentTriggerDelay4.0.0+BPELConfig > RecoveryConfig > StartupScheduleConfig > maxMessageRaiseSizeBlueprint > Products > Oracle SOA Suitebpel-RecoveryConfig.StartupScheduleConfig.maxMessageRaiseSize4.0.0+BPELConfig > RecoveryConfig > StartupScheduleConfig > startupRecoveryDurationBlueprint > Products > Oracle SOA Suitebpel-RecoveryConfig.StartupScheduleConfig.startupRecoveryDuration4.0.0+BPELConfig > RecoveryConfig > StartupScheduleConfig > subsequentTriggerDelayBlueprint > Products > Oracle SOA Suitebpel-RecoveryConfig.StartupScheduleConfig.subsequentTriggerDelay4.0.0+BPMNConfig > RecoveryConfig > RecurringScheduleConfig > maxMessageRaiseSizeBlueprint > Products > Oracle SOA Suitebpmn-RecoveryConfig.RecurringScheduleConfig.maxMessageRaiseSize4.0.0+BPMNConfig > RecoveryConfig > RecurringScheduleConfig > startWindowTimeBlueprint > Products > Oracle SOA Suitebpmn-RecoveryConfig.RecurringScheduleConfig.startWindowTime4.0.0+BPMNConfig > RecoveryConfig > RecurringScheduleConfig > stopWindowTimeBlueprint > Products > Oracle SOA Suitebpmn-RecoveryConfig.RecurringScheduleConfig.stopWindowTime4.0.0+BPMNConfig > RecoveryConfig > RecurringScheduleConfig > subsequentTriggerDelayBlueprint > Products > Oracle SOA Suitebpmn-RecoveryConfig.RecurringScheduleConfig.subsequentTriggerDelay4.0.0+BPMNConfig > RecoveryConfig > StartupScheduleConfig > maxMessageRaiseSizeBlueprint > Products > Oracle SOA Suitebpmn-RecoveryConfig.StartupScheduleConfig.maxMessageRaiseSize4.0.0+BPMNConfig > RecoveryConfig > StartupScheduleConfig > startupRecoveryDurationBlueprint > Products > Oracle SOA Suitebpmn-RecoveryConfig.StartupScheduleConfig.startupRecoveryDuration4.0.0+BPMNConfig > RecoveryConfig > StartupScheduleConfig > subsequentTriggerDelayBlueprint > Products > Oracle SOA Suitebpmn-RecoveryConfig.StartupScheduleConfig.subsequentTriggerDelay4.0.0+em.log.handlersGlobal Variablesem.log.handlers=odl-soa1
em.log.handler.odl-soa1.name=odl-handler
em.log.handler.odl-soa1.maxFileSize=11M
em.log.handler.odl-soa1.retentionPeriod=week
em.log.handler.odl-soa1.rotationFrequency=day
em.log.handler.odl-soa1.target=soa_server12.2.0+em.props > oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_USE_CACHED_RESULTSGlobal Variablesoracle.sysman.emas.discovery.wls.FMW_DISCOVERY_USE_CACHED_RESULTS2.5.1+em.props > oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_CACHE_AGEGlobal Variablesoracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_CACHE_AGE2.5.1+em.props > oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_WAIT_TIMEGlobal Variablesoracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_WAIT_TIME2.5.1+em.props > LargeRepositoryGlobal VariablesLargeRepository4.0.0+HumanWorkflowConfig > AcknowlegdeFyiUponReadBlueprint > Products > Oracle SOA Suiteworkflow-AcknowlegdeFyiUponRead6.5.2+HumanWorkflowConfig > HWFFailureRetryCountBlueprint > Products > Oracle SOA Suiteworkflow-HWFFailureRetryCount6.5.2+HumanWorkflowConfig > MaxNumberOfEmailAttachmentsBlueprint > Products > Oracle SOA Suiteworkflow-MaxNumberOfEmailAttachments6.5.2+HumanWorkflowConfig > MaxSizeOfEmailAttachmentsInKBBlueprint > Products > Oracle SOA Suiteworkflow-MaxSizeOfEmailAttachmentsInKB6.5.2+