When setting up a continuous integration solution for Oracle SOA Suite code, it is best to work with mavenized projects, and thus rely on Oracle-provided maven plugins to do the tough job of compiling and deploying artifacts.
This way of working has been introduced by Oracle in the 12c range of products. There are no Maven plugins available for 11g Oracle products.
This post describes how to set up the plugin in a Binary Repository for Maven to be able to fetch it when the time has come to compile a SOA Composite.
The Oracle SOA Maven Plugin needs to be published to a Maven repository, this can be a local repository or a remote repository. Here, we’ll discuss a remote repository, as publishing to your local repository is similar and even easier!
Make sure your binary repository is set up, and you have a user and password with sufficient rights to add binaries to the repository.
Edit your Maven Settings file, it is located at ~/.m2/settings.xml.
Make sure that you set up a profile, and that the profile/id matches activeProfiles/activeProfile. Also make sure that repository/id matches server/id for the credentials to be used when communicating to the server.
Combined, the settings.xml file would look something like this: Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.