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
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 126.96.36.199 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.
If you are installing WebLogic Server on a 64-bit platform using a .jar installation program use the downloaded wlsversionnumber_generic.jar . Start the installation using the following command. Include the -d64 flag in the installation command when using a 32/64-bit hybrid JDK.
$ java -d64 -jar wls1035_generic.jar
Welcome screen – Click Next
Choose Middleware Home Directory – Create a new Middleware Home and enter the directory of your choice
Register for Security Updates
Choose Install Type – Choose Custom to be able to select the JDK of choice
Choose Products and Components – No changes needed
JDK Selection – Pick the JRockit JDK previously installed
Choose Product Installation Directories – No changes needed
Confirm Product Installation Directories
Installer is running
An overview of the WebLogic Server installation screen can be viewed in the gallery:
While I had to document these steps for a customer that is new to WebLogic Server, I thought why not share these relatively easy steps in a blog post as well. So here they are. The screen shots that come with it are at the bottom.
Create Data Source
Use a browser to go to the WLS Console, for example http://somehost:7001/console/login/LoginForm.jsp
On the home page, click the Data Sources link. You can find it in the Domain Configurations, Services section;
On the Summary of JDBC Data Sources page click the New button (to change current configuration click the link of the Data Sources you want to change);
Choose the Name, JNDI Name, and select the Database Type (Oracle). Click Next to confirm and continue;
Choose the Database Driver. This is depending on the selected Database Type. We used Thin XA for Instance connections for the Data Sources created in the project. Click Next;
Click Next after you read the Transaction Options;
Enter the Connection Properties and after that Next to confirm and continue:
Database User Name
Click the Test Connection button, and if the test succeeded click next;
On the Select Targets page check for example the AdminServer. Click finish.
If you’re not using elastic IP you have to configure WebLogic / SOA Suite running on EC2 to listen to external calls. A good example of such an external call would be: you trying to deploy a composite from the JDeveloper installation on your local PC. If you don’t configure this you’ll run into:
Error sending deployment request to server
java.net.ConnectException: Connection timed out: connect
To configure the External Listen Address log into the WebLogic Console.
Select Environment – Server
Click the server (AdminServer)
Click Advanced to show the advanced settings
Enter the External Listen Address
It can be helpful to also edit your host file to save you from retyping the quite long EC2 host name over and over again.
It is possible you noticed that after the installation of Oracle AIA 11g R1 starting the Managed Server of WLS takes more time than before the installation. This is not only due to the new Composites. There are also some settings you could change to reduce the time the Managed server to which you deployed AIA needs to start up.
Change JDBC settings
To alter some of the JDBC settings that are configured during the AIA 11g installation go to the WLS Adminnistartion console – http://yourserver:port/console. In the Domain Structure choose: > Services > JDBC > Data Sources.
Change the settings of the following JDBC Data Sources that were created during the install of AIA of the AIA Demo:
Data Source Settings
In the Settings for "Data Source Name" select the Configuration and the Connection Pool tab. Expand the the Connection Pool tab by clicking the Advanced link. The alter the Login Delay from 30 to 0 seconds.
This will reduce the time that is needed to start the Managed Server by several minutes.
In this blogpost I’ll share some steps you can take to get your AIA 11g R1 installation back on track. If you do not perform the Pre-Installation Configurations as described in the Foundation Pack 11g Release 1 (188.8.131.52.0) Installation Guide (available as partnumber E17949-01 via eDelivery), it is possible that your AIA installation fails. After checking the pre-installation configuration it is possible to start the installation again if you follow these steps:
Navigate to /user_projects/domains/ and delete the edit.lok file.
Delete any file located in /user_projects/domains//pending
Log into the weblogic console and activate all the changes.
Restart SOA Suite and Weblogic domain.
Press retry button on the installation screen
If the installation screens are no longer available because you closed them, use the log files to figure out what targets haven’t been performed yet and run these targets (in the sample case below it were Deployments and PostInstallScript):
Move to the /aia30/aia_instances/aia30poc/bin and source ./aiaenv.sh.
ant -f /aia30/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=/aia30/config/FPInstallDP.xml -DPropertiesFile=/aia30/config/AIAInstallProperties.xml Deployments
ant -f /aia30/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=/aia30/config/FPInstallDP.xml -DPropertiesFile=/aia30/config/AIAInstallProperties.xml PostInstallScript
Oracle Application Integration Architecture, or AIA in short, recently became available for SOA Suite 11g R1. We did an installation of this AIA 11g R1 release. To prepare for this we used Foundation Pack 11g Release 1 (184.108.40.206.0) Installation Guide. Which is available as part number E17949-01 via edelivery. In the software requirements in the document it is stated that:
Download the AIA-Foundation Pack 220.127.116.11.0 patch 9717829 and follow the instructions in the document “Installing a fresh instance of AIA FP 11gR1 PS2 on Oracle SOA Suite 11g PS2” before you install AIA Foundation Pack 11g Release 1 (18.104.22.168.0). Apply AIA-Foundation Pack 22.214.171.124.0 patch 9717829 after you install AIA Foundation Pack 11g Release 1 (126.96.36.199.0).
Please be careful: patch 9717829 is only required if you are using SOA Suite 11g R1 PS2 (188.8.131.52). This can become clear when reading the document “Installing a fresh instance of AIA FP 11gR1 PS2 on Oracle SOA Suite 11g PS2” and the readme.txt that comes with the patch.
If you’re installing AIA-Foundation Pack 184.108.40.206.0 on SOA Suite 11g R1 PS1 (220.127.116.11) this patch is not needed.
AIA Foundation Pack 11g Certification Matrix
The certification matrix for AIA FP 11g R1 can be found here. It states:
AIA Foundation Pack 11gR1 (18.104.22.168) is certified against Oracle SOA Suite 11gR1 (22.214.171.124) or Oracle SOA Suite 11gR1 (126.96.36.199) through patch 9717829.
Besides the reference in the documentation library to the Install Guide and the Quick Install Guide, there are several blogs describing the installation of 188.8.131.52. Which is actually a patch on 184.108.40.206:
The one on Oracle blogs by James Taylor includes OSB 220.127.116.11
SOA Suite on Amazon EC2
This week it was announced that BPM 11g R1 is available as an Amazon Machine Image (AMI). This AMI includes SOA Suite 11gR1 Patchset 2 and JDeveloper with the SOA and BPM extension. In AWS filter on 64-bit and put soa-bpm in the search box. This should enable you to find oracle-soa-bpm-11gr1-ps2-4.1-pub. Some of the tips I posted on x SOA Suite in the cloud could be useful here as well.