Skip to main content

Reflecting On The MuleSoft Dallas API Workshop

MuleSoft’s Dallas API Workshop was an educational and enlightening day dedicated to exploring the value and potential of APIs and harnessing the power of API-led development. Throughout the intervening week, we’ve found ourselves returning again and again to the day’s theme to extract and absorb every last insight. One can hardly overstate what APIs represent for the future of business agility or their centrality to digital transformation.

Often when starting a new project, a developer can have doubt on how to implement the structure, which patterns to follow or which of the many frameworks should you choose to achieve a single goal when there are hundreds out there. Many times this reason is why the kickstart is so hard.

Spring cleanup of archive files!


During a project, we casually gathered waaaay too many archive files.  These were intentionally stored, however, in development and testing environments, they became a nuisance, and took up too much space.  Occasionally the Ops team would send out an email saying that disk space was full, and it was time to do some cleanup.

Eventually, without any involvement, log files will get out of hand.  Oracle published in the Lifecycle Management guide ways to configure the diagnostic logging, however, the ".out" files aren't covered.

Sure, you can just go in and delete them occasionally, but why can't this be done automatically?

It can!

*Of note: this can guide is for servers running Linux!

This shows how to dynamically assign tasks to an individual user, or to an application role, or to an LDAP group depending on the human task's incoming data.

AWS has certainly been a buzzword in software development recently. However, the term is so broadly used that often creates more confusion. Is AWS only a new way to host applications? Will an application be developed locally, as it is traditionally done, then get deployed on Amazon’s infrastructure? If so, then what’s the big fuzz?

This is the third in a series of 5 blogs that shows how to expose a database to an Oracle BPM 12c Process using the Oracle SOA Database Adapter.  In this blog, the Database Adapter's Outbound connection pool created in part 2 of this series is configured to include the data source's JNDI name created in part 1 of this series.

Some companies create database schemas that are either prefixed or suffixed with the environment name. This can cause a problem when using the Oracle Database Adapter to execute a stored procedure. When adding a database adapter to a project, one must specify the schema in which the stored procedure was created. Even if <Default Schema> is selected, the schema JDeveloper is connected to the database with will be specified in JCA file that is created.


If you have struggled getting the demo community users loaded for Oracle SOA Suite and BPM in 12c, you are not alone. Quite a bit has changed with Oracle’s demo community seed application we’ve been using for years.  The purpose of this is to help you get the demo users seeded for your installation.

Oracle ESS (Enterprise Scheduling Service) is a nice feature that's standard in Oracle SOA Suite 12c that alleviates the need to use Quartz or external software to run scheduled jobs (including invocations of services). Continuous Deployment can deliver many benefits but in order to get there, environment changes need to be automated as much as possible. AVIO has developed a Maven plugin that helps close the gap.

Subscribe to Blog Lead Image - Network Pen Writing