By default the Oracle BPM engine (Business Process Management) is configured so it won’t publish events to BAM (Business Activity Management). So should you choose to use BAM and use these great dashboards, you have set the DisableActions property to false/empty. Here is how it works to configure BPM to BAM:
Log in to the Fusion Middleware Control – http://bpm-host:7001/em
Navigate through the Farm – WebLogic Domain – select the domain and then select the Server in which BPM is running (soa_server1 in a default install)
Use the WebLogic Server dropdown menu as shown in the first screenshot
Select the System Mbean browser in the menu
Expand the folder ans shown in the second screenshot: Application Defined MBeans - oracle.as.soainfra.config - BMNNConfig - bpmn
Find the DisableActions property and remove it’s value
To have the BPM server push events to BAM – Business Activity Monitoring – we have to configure the BPM suite to use the BAM Adapter. The BAM Adapter is configured (like other SOA Suite and BPM Adapters) in the WebLogic Server Console.
Configure BAM Adapter
In the WLS Console, locate the Domain structure and select Deployments.
In the Deployments table that is shown, search and click the OracleBAMAdapter (you could filter on type Resource Adapter)
As shown in the first screenshot: Select the Configuration tab and within that the Outbound Connection Pools tab
Drill down on the oracle.bam.adapter.adc.soap.SOAPConnectionFactory to eis/bam/soap
In the properties tab: fill in the details of the connection to the BAM Server (depending on how you installed it). Remember to acknowledge the changes of each field using the enter key (leaving a field without using the enter key and changes will be lost)
First time you alter the BAM Adapter you have to create a Deployment Plan. Select the Path to the deployment plan and Save
Since you need to update the Adapetr now, select it and chose Update
Choose the option Update this application in place with the new deployment plan changes and click Finish.
In Oracle SOA Suite 10g, or more specific BPEL 10g, one could group functionality in domains. This feature has been away in the early versions of SOA Suite 11g. They have returned in more recent version and can be used for all SCA composites (instead of BPEL only). Nowadays these 10g domains are called partitions.
Create SOA Suite partition
Login to the Fusion Middleware Enterprise Manager: http://server-name:portnr/em
Use the tree-view on the left and select soa-infra.
Use the SOA Infrastructure dropdown menu and select the Manage Partitions item.
The manage partitions page appears and you should select Create… to create your new SOA Suite partition.
Enter a name for the partition and press the create button.
While deploying SCA appications from JDeveloper or ANT you should add the partition from now on.
Install JDeveloper in a seperate Middleware Home. When starting JDeveloper choose the “Default” role. To enable JDeveloper to perform development for the SOA Suite and develop and deploy SCA composites you have to install an extension called SOA Composite Editor. When you want to develop BPM processess you need to install BPM Studio extension following these steps:
Select Help > Check for Updates
Select Oracle Fusion Middleware Products and Official Oracle Extensions and Updates and click Next
Select Oracle SOA Composite Editor and Oracle BPM Studio 11g and click Next
An Oracle SOA 11G installation presents a few challenges for administrators and one of these is managing the growth of the SOA database. The advice facilitates better dialog between SOA and Database administrators when planning and managing database requirements.
This document covers everything you need to know about the SOA Infrastructure Database for Oracle SOA Suite 11g. Here we bring together content from sources such as OTN, Product Documentation and our Knowledge Base in an effort to provide you with a single comprehensive resource.
Update: WebLogic 12.1.1 VirtualBox Appliance available
With OTN Virtual Developer Day a WebLogic 12c VirtualBox appliance became available. On the appliance there are Labs and other Java development tools like: Hudson, Subversion, Maven, NetBeans IDE, and Eclipse (including OEPE).
Update: Updated/Patched WebLogic 184.108.40.206 distribution available
Just read Markus Eiseles blog on an updated WebLogic Server 12c on OTN. If you obtain the updated product distribution for WebLogic Server 12.1.1 after March 16, 2012, the patches are included. If you obtained a product distribution for WebLogic Server 12.1.1 prior to March 16, 2012, and you do not wish to re-install with the updated WebLogic Server distribution, you can obtain the patches from Oracle Support.
After installing Oracle Enterprise Repository (OER) we experience some memory issues. Besides the messages in the log files, we also couldn’t use the console and em as we did before (when we were just running SOA Suite). It turned out the installation of OER in the same Weblogic domain resulted in some unexpected things.
The WebLogic Server and SOA Suite are started using the startWebLogic script (for windows .cmd and on Linux/Unix .sh). This script uses the setDomainEnv script to set the environment variable for the domain. The setDomainEnv script in turn calls the setSOADomainEnv that actually sets the USER_MEM_ARGS. That in the end are used in the startWebLogic script.
After the installation of OER the setDomainEnv not only calls the setSOADomainEnv. It also calls a script that sets the USER_MEM_ARGS for the oer_server in the domain. Apparently the memory required for OER is less than needed for the SOA Suite. Since the script for OER is executed last, memory setting remain low. As shown in the smippet taken from the setDomainEnv.cmd:
To solve the memory issue when starting the WebLogic Server using the startWebLogic script we alter the sequence so the setOERDomainEnv.cmd goes before the setSOADomainEnv.cmd.
If the installer put a second call to setSOADomainEnv.cmd in the setDomainEnv.cmd. That doesn’t work because the setSOADomainEnv.cmd contains the following check:
REM Skip running this script again if it was run onceif "%XENGINE_DIR%" == "" goto set_env
echo ** SOA specific environment is already set. Skipping ...
REM Skip running this script again if it was run once
if "%XENGINE_DIR%" == "" goto set_env
echo ** SOA specific environment is already set. Skipping ...