wlp
Version information
Start using this module
Add this module to your Puppetfile:
mod 'ibmwas-wlp', '0.1.0'Learn more about managing modules with a PuppetfileDocumentation
#ci.puppet.wlp
Puppet modules for installing and managing WebSphere Application Server Liberty Profile #devops
##Description
The liberty module installs and configures WebSphere Application Server Liberty Profile. It provides manifests and templates for creating, managing and configuring Liberty profile server instances.
##Basic Configuration
The wlp module can install Liberty profile from jar archives or zip files. The installation method is configured via the wlp::mode parameter.
###Jar installation:
Jar installation is used to install Liberty from the jar file installable that is provided on wasdev.net. You must set the parameter wlp::acceptLicense to true before invoking the class wlp::install which will install the WebSphere Liberty Profile. If you do not set this variable the installation will fail. By default the install class is configured to use the jar installation method.
###Zip installation:
Zip installation is used to install Liberty from a zip archive. The zip is assumed to be generated by running ./bin/server package Liberty command with --include=all or --include=minify option. You would need to set the wlp::mode parameter to zip in order to trigger a zip installation.
##Requirements
###Platform:
Centos
Redhat
##Modules:
No modules at this time.
Note: The wlp::java_home variable needs to be set for this module to work correctly at this time.
##Parameters
The following parameters can be used to configure the wlp module
acceptLicense = Whether or not you accept the Liberty License. eg:
$acceptLicense = "true"
serverName = The name of the liberty server that should be created on each node. eg:
$serverName = "server1"
baseDir = The parent directory into which the liberty profile will be installed. Note that this is just the directory name and not the full path. eg:
$baseDir = "liberty"
appNames = Defines the names of the applications that will be installed onto the server. eg:
$appNames = [ 'acmeair-webapp-1.0-SNAPSHOT.war','DefaultApplication.ear',]
install_root = The base installation directory for the Liberty Profile. eg:
$install_root="/opt/IBM/"
serverBinaryName = The name of the WebSphere Liberty Base binary. eg:
$serverBinaryName="wlp-developers-runtime-8.5.5.1.jar"
appsDirName = The name of the directory that contains the application content for installation in the files directory of the puppet wlp module. eg:
$appsDirName = "apps"
extendedBinaryName = The name of the WebSphere Liberty extended binary.eg:
$extendedBinaryName="wlp-developers-extended-8.5.5.1.jar"
extrasBinaryName = The name of the WebSphere Liberty Extras binary. eg:
$extrasBinaryName="wlp-developers-extras-8.5.5.1.jar"
mode = The mode of installation. There are two modes of installation namely 'zip' and 'archive'. eg:
$mode = "archive"
artifact = The artifact to install. can be base, extended, extras. eg:
$artifact = "base"
action = The action that should be performed. Possible values are install and uninstall. eg:
$action = "install"
java_home = The directory where Java is installed. eg:
$java_home = "/usr/lib/jvm/java-1.6.0"
puppetFileRoot = This is the location where all the installables should be present in case of standalone puppet. In the case of master agent puppet, this is the location where the master will copy the installable files. eg:
$puppetFileRoot="${userHome}"
includesDir = This is the directory where all the xml files that need to be included into server.xml are placed. Each application can provide an xml file snippet that will be included in the final server.xml. This snippet can contain all the features and config that is needed for that application. eg:
$includesDir ="${wlp::variables::install_root}/${baseDir}/wlp/usr/servers/${serverName}/includes"
applicationSourceDirectory = The complete path to the directory containing application files. eg:
$applicationSourceDirectory = "${userHome}/${appsDirName}"
path = This is used internally and is the path used for puppet spawned shells. eg:
$path = "${wlp::variables::java_home}/bin:/opt/puppet/bin:${wlp::variables::install_root}/${baseDir}/wlp/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin"
##Standalone Puppet Usage
If you want to install Liberty and deploy an application to it on a machine that has puppet installed you need to create a puppet manifest file and paste the following into it.
class { "wlp":
appNames => ['DefaultApplication.ear',],
puppetFileRoot => "/home/puppetuser",
serverBinaryName => "wlp-developers-runtime-8.5.5.1.jar",
standalone => true,
acceptLicense => true
}
First you will need to specify the applications that need to be installed via the appNames parameter. You can specify multiple application names as an array. Next you need to specify the applicationSourceDirectory parameter or the puppetFileRoot parameter so that the wlp module knows where your application artifacts are present. The directory specified by applicationSourceDirectory should contain the following 2 files for each application
1) Application Archive. eg: DefaultApplication.ear
2) snippet to include in server.xml. eg:DefaultApplication.xml
Note that the names should be the same and the extensions will only be different.
The property puppetFileRoot is used to determine the location where your Liberty installable is present and serverBinaryName to determine the name of the Liberty installable file. Applying this manifest will result in Liberty being installed and the applications specified deployed. Finally the server is started.
##Master Agent Puppet Usage
Another usecase would be to install Liberty across multiple nodes. This can be achieved if the nodes are having puppet agents that are federated to a puppet master. In such a case you would need to modify the site.pp manifest file of the puppet master as shown below. You can define a base node that all your nodes that require Liberty installed should extend from. Shown below is a sample base Node for installing Liberty and an application.
node base {
class { "wlp":
appNames => ['DefaultApplication.ear',],
puppetFileRoot => "/home/puppetuser",
serverBinaryName => "wlp-developers-runtime-8.5.5.1.jar",
standalone => false,
acceptLicense => true
}
class { "wlp::copy_files":}->
class { "wlp::install": } ->
class { "wlp::create_server": } ->
class { "wlp::install_application": } ->
class { "wlp::start_server": }
}
A Node extending the base node.
node 'libertyagent' inherits base {
}
An important thing to note here is the location of the files including the application files and the installable files. The installable files need to be present in the files directory of the puppet module. So the default location would be /etc/puppetlabs/puppet/modules/wlp/files. The application files should be present in the directory referred to by the appsDirName variable. By default the value of this variable is apps. So the location where the application artifacts should be present is /etc/puppetlabs/puppet/modules/wlp/files/apps. The reason that we need to put these files in this location is to enable the file server present in the puppet master to server these files to the nodes where the puppet agent is running which needs access to these files.
Notice
© Copyright IBM Corporation 2013, 2014.
License
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "{}"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright {yyyy} {name of copyright owner}
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.