Recent Posts by David Craft

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 16 - Securing Deployment With SSL Out of the box, a SOACS instance encrypts SSL traffic using a self-signed certificate.  You can retrieve this certificate using your browser (usually you click the lock next to the address bar and navigate to the "export" option) and then use keytool to import the...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 15 - Deploying to SOACS One issue in deploying from DevCS is the firewall and proxy. First, the proxy information must be specified on the command line.  DevCS exports HTTP_PROXY_HOST and HTTP_PROXY_PORT on the shell environment and specifies the proxy information in the settings.xml, but the Maven plugin...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 14 - Recap and More This is a quick recap chapter.  The provided video shows how quickly you can go from scratch to a fully built project using DevCS.When you use the SOA Maven Archetype to generate a SOA project, the resulting pom.xmls are independent of each other.  This leads to fragmentation and...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 13 - Building and Deploying Using Hudson Finally, part of the whole reason you are here: building your artifacts on the cloud. To begin, we again need the repository information. In the previous chapter, I put the repository information in settings.xml. This was partly done for simplicity. The introduction...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 12 - Populating Remote Maven Repository If you followed a previous chapter, you should have your local Maven repository populated with the necessary SOA binaries. In order to build on the cloud, the project's remote Maven repository needs to be seeded with the same binaries. We can use the same sync plugin...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 11 - Maven Encryption To get started with Maven encryption, you need to create a master private key using some passphrase you come up with: mvn --encrypt-master-password The output of this command is your private key. In order for Maven to use it, create a file under Maven's .m2directory (usually under your...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 10 - Merge Requests Before you start making changes, you should create a branch using gitflow: git flow start feature start <name of feature> I recommend some naming convention for the branch names, especially if you publish them to the remote Git repository. Something like: "$USER/$FEATURE_NAME"...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 09 - Initial Git Commit One important step to take early on is to create a ".gitignore" file. This will tell Git to not add generated files to source control. The final artifact and all its temporary files such as generated sources, class files, build logs, and such should not be checked in. Not only do...

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service. < Previous Chapter | Next Chapter > Chapter 08 - Deploying to On-Premise Server BIG WARNING: As mentioned in a previous chapter, JDeveloper defaults the revision to "1.0" whereas Maven expects the revision to "1.0-SNAPSHOT". To work seamlessly across both, for each project, you should change the "revision" in composite.xml: <composite...