fabric3
Content
Documentation
Developer Reference
Packaging
Service Delivery
Service Delivery
search
attachments
weblink
advanced
image-effects
image-attributes
Paragraph
Paragraph
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Preformatted
Quote
Bold
Italic
Underline
Colour picker
More colours
Formatting
Strikethrough
Subscript
Superscript
Monospace
Clear formatting
Bullet list
Numbered list
Task list
Outdent
Indent
Align left
Align center
Align right
Page layout
Link
Table
Insert
Insert content
Files and images
Link
Symbol
Emoticon
Markup
Horizontal rule
Insert macro
User mention
Jira Issue/Filter
Info
Status
Gallery
Table of Contents
Jira timeline
Lucidchart Diagrams
Trello Board
Other macros
Page layout
No layout
Two column (simple)
Two column (simple, left sidebar)
Two column (simple, right sidebar)
Three column (simple)
Two column
Two column (left sidebar)
Two column (right sidebar)
Three column
Three column (left and right sidebars)
Find/Replace
Keyboard shortcuts help
You are not logged in. Any changes you make will be marked as
anonymous
. You may want to
Log In
if you already have an account.
<h2>The Fabric3 Service Delivery Model</h2><p>Traditional deployment models for Java EE and Servlet applications involve packaging a single archive and deploying it to a one-size-fits-all server distribution such as an application server. Many production environments will automate this process by creating installation and deployment scripts. Advanced setups may use IT automation software such as <a href="http://docker.io">Docker</a>, <a href="http://www.opscode.com/chef/">Chef</a> or <a href="https://puppetlabs.com/">Puppet</a>. Integrating Java-based server distributions often leads to complex automation scripts since those servers were originally designed to be manually installed. </p><p><span style="line-height: 1.4285715;">This picture has been further <span class="inline-comment-marker" data-ref="eb3f4885-cf65-4799-91ed-5ec80d9e6f7f">complicated</span> by the drive toward greater modularity and designing applications as loosely coupled services. Packaging applications as a single archive, while simple, does not lend itself well to modularity. Fabric3 addresses these requirements by providing Gradle and Maven plugin for assembling a custom runtime image including application modules as part of an automated build. The produced image can then be integrated into a deployment setup managed by IT automation software. The following illustrates a typical (and recommended) Fabric3 delivery model:</span></p><p><span style="line-height: 1.4285715;"><img class="confluence-embedded-image" loading="lazy" src="https://fabric3.atlassian.net/wiki/download/attachments/1212498/Slide22.jpg?version=4&modificationDate=1374854299198&cacheVersion=1&api=v2" data-image-src="https://fabric3.atlassian.net/wiki/download/attachments/1212498/Slide22.jpg?version=4&modificationDate=1374854299198&cacheVersion=1&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="1474593" data-linked-resource-version="4" data-linked-resource-type="attachment" data-linked-resource-default-alias="Slide22.jpg" data-base-url="https://fabric3.atlassian.net/wiki" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="1212498" data-linked-resource-container-version="10" data-media-id="b7c56603-6c3a-491e-9ae6-4bea9c4afd7d" data-media-type="file" title="fabric3 > Service Delivery > Slide22.jpg" data-location="fabric3 > Service Delivery > Slide22.jpg" data-image-height="405" data-image-width="720"> </span></p><p><span style="line-height: 1.4285715;">Instead of packaging an application separately from the server image, the Fabric3 assembly plugins allow you to define a runtime image including a set of contributions that contain application services. The runtime image can be customized to contain only extensions required for the application and custom configuration. After the runtime image is built, it can be released to a repository and further integrated with a deployment system. </span></p><p><span style="line-height: 1.4285715;">The next sections describe how to use the <a class="confluence-link" href="/wiki/spaces/FABRIC/pages/15204591/Fabric3+Gradle+Assembly+Plugin" data-linked-resource-id="15204591" data-linked-resource-version="2" data-linked-resource-type="page" data-linked-resource-default-alias="Fabric3 Gradle Assembly Plugin" data-base-url="https://fabric3.atlassian.net/wiki">Fabric3 Gradle Assembly Plugin</a> and the <a class="confluence-link" href="/wiki/spaces/FABRIC/pages/1540300/Fabric3+Maven+Assembly+Plugin" data-linked-resource-id="1540300" data-linked-resource-version="10" data-linked-resource-type="page" data-linked-resource-default-alias="Fabric3 Maven Assembly Plugin" data-base-url="https://fabric3.atlassian.net/wiki">Fabric3 Maven Assembly Plugin</a>.</span></p><p> </p>
Save
Close
Edit
Preview
View changes
Revert to last published version
{"serverDuration": 456, "requestCorrelationId": "12e9b797c5bb4e4dbc8cd55867062ef0"}