Database Reference
In-Depth Information
Usually IT sets up hardware infrastructure. DBAs deploy the databases. Various application teams build, test,
and deploy their applications. A cross-functional team wires them to make all of them work together. Dependency
between application components and deployment constraints (for example, database and middleware) should be
in different network segments, which can make this task even more difficult.
EM12c and Oracle Virtual Assembly Builder (OVAB) address this challenge. Figure 5-7 shows the steps followed
in packaging multi-tier applications into an assembly and making it available for deployment.
Figure 5-7. Steps for packaging multi-tier applications for deployment
Using OVAB, application developers and architects can model the application topology graphically, define
all dependencies and deployment constraints, and package the entire application in the form of what we call an
application assembly . These assemblies can then be uploaded to the centralized Software Library in Enterprise
Manager for self-service deployments. An entire multi-tier application (including various application components,
middleware software, databases, operating systems, and the virtual machines containing all of them) can be packaged
together in an assembly. The assembly is then published into the Enterprise Manager Software Library, as shown in
Figure 5-8 , and made available to the users of the cloud for deployment via the Enterprise Manager Self Service portal.
This can reduce the time needed for application deployments, from months and days to hours and minutes.
The resulting standardization in software stack minimizes compliance risks and operational downtime.
Figure 5-8. Uploading the assembly to the Enterprise Manager Software Library
 
Search WWH ::




Custom Search