ibm was nd #4

Description

IBM WebSphere Application Server Network Deployment provides an advanced, flexible runtime environment for large-scale application deployments. It offers near-continuous availability with advanced performance and management capabilities for mission-critical applications.


Charm for IBM WebSphere Application Server Network Deployment (WAS ND) 9.0.0.0

Overview

IBM WebSphere Application Server Network Deployment provides an advanced, flexible runtime environment for large-scale application deployments. It offers near-continuous availability with advanced performance and management capabilities for mission-critical applications. For details on IBM Websphere Application Server Network Deployment, as well as information on purchasing, please visit Product Page and at the Passport Advantage Site. More information available at the IBM Knowledge Center.

IBM WebSphere Application Server Network Deployment

This charm is used as a common layer for IBM WAS ND DM and IBM WAS ND Node charms to install IBM WAS ND Software. This charm is internally using ibm-im charm as a base layer to install Installation Manager tool for IBM WAS ND Software installation.

**Please note that the WAS ND charms (WAS ND, WAS ND DM and WAS ND Node) will create IBM WAS ND dynamic cluster.

IBM SDK, Java Technology Edition

WebSphere Application Server now uses a separately packaged, IBM Java SDK. It requires Java SDK version 8.

Prerequisites

This charm makes use of resources, a feature only available in Juju 2.0. During deploy or upgrade, you will need to specify the installable package(s) required by this charm. Download your licensed IBM WebSphere Application Server ND packages from the Product Page.

Packages for Ubuntu on Z (s390x):

IBM Installation Manager 1.8 (agent.installer.linux.gtk.s390x_1.8.5000.20160506_1125.zip)

IBM WAS ND 9.0.0(WAS_ND_V9.0_MP_ML.zip)

IBM JAVA SDK 8 (sdk.repo.8030.java8.linux.zip)

Usage

To use this charm, you must agree to the Terms of Use. You can view the full license for IBM Installation Manager and IBM WebSphere Application Server Network Deployment products by visiting the im-license-info and was-nd-license-info page.

Search for "IBM WebSphere Application Server Network Deployment" and choose the license that applies to the version you are using.

Memory and Disk Requirements

Minimum 2.0 GB of disk space for installed image and Minimum 1 GB of physical memory recommended.

WebSphere Application Server ND Charm requires 15 GB of root disk to download packages and install the IBM WebSphere Application Server ND Software. By default available root disk space is 8GB.

To request a larger root disk, run the following command:

    juju set-constraints root-disk=15G

Deploy

Run the following commands to deploy this charm:

juju deploy ibm-was-nd --resource ibm_im_installer=</path/to/ibm_im_installer.zip> --resource ibm_was_nd_installer=</path/to/ibm_was_nd_installer.zip> --resource ibm_java_sdk_installer=</path/to/ibm_java_sdk_installer.zip> --resource ibm_was_nd_fp=</path/to/ibm_java_sdk_installer.zip> --series xenial

Note: This charm requires acceptance of Terms of Use. When deploying from the Charm Store, these terms will be presented to you for your consideration.

To accept the terms:

juju agree ibmcharmers/ibm-was-nd/1

** This charm can be deployed and tested. But it is useful when you use it as a layer with IBM WAS ND DM and IBM WAS ND Node charms.

This layer is intended to be extended by IBM WAS ND DM and IBM WAS ND Node charms that would install WAS ND software.
IBM WAS ND DM and IBM WAS ND Node layered charms could include this layer so it could install IBM WAS ND to configure deployment manager(DM) and Nodes to setup dynamic cluster.

To use this layer, include the following in layer.yaml:

includes: ['layer:ibm-was-nd']

Reactive States

This layer charm will set the folowing state.

`ibm-was-nd.installed` : This state will be set once WAS ND software is installed successfully.

IBM WebSphere Application Server Network Deployment Information

(1) General Information

Details about IBM WAS ND software available at IBM Knowledge Center.

Information on procuring WAS ND product is available at the Passport Advantage site

(2) Download Information

Details about WAS 9.0.0.0 download available [here] [[WAS-ND-9.0.0.0-download]

Information about installation of WAS ND on 's390x' based machine available here

More information about IBM IM Downloadable file and WAS ND downloadable files available here

Contact Information

For issues with this charm, please contact IBM Juju Support team jujusupp@us.ibm.com

Configuration

license_accepted
(boolean) Some IBM charms require acceptance of a license before installation can proceed. If required, setting this option to True indicates that you have read and accepted the IBM terms and conditions found in the license file referenced by the charm.
curl_url
(string) Location of the IBM product installation file(s). This should be a URL that curl can use to download files. Multiple URLs should be separated by a space. NOTE: cryptographic verification is required and must be specified as part of the URL query string with the key a valid hash algorithms md5, sha256, or sha512, and the the checksum value itself (http://<url>?[md5|sha256|sha512]=<checksum>). For example: 'http://example.com/file.tgz?sha256=<sum>' 'sftp://example.com/file1.tgz?md5=<sum> ftp://example.com/file2.tgz?md5=<sum>'
package_status
(string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".
install
extra_packages
(string) Space separated list of extra deb packages to install.
curl_opts
(string) The options passed to the 'curl' command when fetching files from curl_url. For example: '-u <user:password>'
install_keys
(string) List of signing keys for install_sources package sources, per charmhelpers standard format (a yaml list of strings encoded as a string). The keys should be the full ASCII armoured GPG public keys. While GPG key ids are also supported and looked up on a keyserver, operators should be aware that this mechanism is insecure. null can be used if a standard package signing key is used that will already be installed on the machine, and for PPA sources where the package signing key is securely retrieved from Launchpad.
install_sources
(string) List of extra apt sources, per charm-helpers standard format (a yaml list of strings encoded as a string). Each source may be either a line that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.