(For more resources on Oracle, see here.)
Deploying applications in production environments is a challenge. The SOA application developers build new projects, or new versions of existing projects, and throw them “over the wall” to the operations team. Administrators have to deploy multiple application files to multiple targets, in a fixed time window. This process is repeated when moving from test to stage to production. This consumes time and requires expertise on these applications. Controlling the WebLogic projects centrally is the first challenge, where administrators have to track the project versions to comply with change and release management guidelines. Next the deployment itself is a challenge, considering the administrator needs to deploy the projects with specific customizations and honor the scheduled maintenance window. All in all, the administrator has too many manual tasks to deal with, given the constraints of the operational environment.
With Grid Control, administrators can deploy multiple OSB projects to a domain deployment procedure framework. A five-step interview process lets the user pick the source projects, pick the target OSB server and domain, set the credentials, specify configurations and the customization file, and schedule a future deployment using the job system.
This set of step-by-step exercises will walkthrough managing the deployment of OSB projects.
The first step is to view the operational store or the Software Library in Grid Control. This is the starting point for administrators to look at the inventory, add items, or change existing items.
The Software Library contains several objects such as operating system images, Oracle homes for database and application server, and deployment artifacts for BPEL, OSB, and so on. The Library is used to track the maturity of these components as they are used on various monitored targets.
(Move the mouse over the image to enlarge.)
In this particular scenario, the administrator has been handed a copy of the OSB project, and needs to deploy it. Before deployment, the administrator needs to upload the projects to the Grid Control Software Library for tracking, operational version control, and to enable deployment:
Note that you can directly export projects from a live OSB server during the deployment process. This will be the most common usage of the deployment procedure. Here, for this workshop though, the export jar has already been created in advance. This export jar contains several projects extracted from another OSB server.
I remember deciding to pursue my first IT certification, the CompTIA A+. I had signed…
Key takeaways The transformer architecture has proved to be revolutionary in outperforming the classical RNN…
Once we learn how to deploy an Ubuntu server, how to manage users, and how…
Key-takeaways: Clean code isn’t just a nice thing to have or a luxury in software projects; it's a necessity. If we…
While developing a web application, or setting dynamic pages and meta tags we need to deal with…
Software architecture is one of the most discussed topics in the software industry today, and…