A familiar story:
· Develop a Node application with one or more developers
· Use Oracle Developer Cloud Service to organize the development work, host the source code and coordinate build jobs and the ensuing deployment
· Run the Node application on Oracle Application Container Cloud
I have read multiple tutorials and blog posts that each seemed to provide a piece of puzzle. This article shows the full story – in its simplest form.
We will:
· Start a new project on Developer Cloud Service
· Clone the Git repository for this new project
· Locally work on the Node application and configure it for Application Container Cloud
· Commit and push the sources to the Git repo
· Create a Build job in Developer Cloud service that creates the zip file that is suitable for deployment; the job is triggered by changes on the master branch in the Git repo
· Create a Deployment linking to an existing Oracle Application Container Cloud service instance; associate the deployment with the build task (and vice versa)
· Run the build job – and verify that the application will be deployed to ACCS
· Add the ACCS Deployment descriptor with the definition of environment variables (that are used inside the Node application)
· Make a change in the sources of the application, commit and push and verify that the live application gets updated
Prerequisites: access to a Developer Cloud Instance and an Application Container Cloud service. Locally access to git and ideally Node and npm. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Blog
Twitter
LinkedIn
Forum
Wiki
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress
