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.
Software & terms:
Charm for IBM WebSphere Application Server ND Node (WAS ND Node) 18.104.22.168
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 ND Node
This charm is using IBM WAS ND charm as a basic layer to install IBM WAS ND Software. After WAS ND installation, this charm will create custom profiles (cluster members) to configure dynamic cluster setup.
**Please note that the WAS ND charms (WAS ND, WAS ND DM and WAS ND Node) will create IBM WAS ND dynamic cluster.
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 AMD64 (x86_64):
IBM Installation Manager 1.8 (
IBM WAS ND 8.5.5 part1 (WASND_v8.5.5_1of3.zip)
IBM WAS ND 8.5.5 part2 (WASND_v8.5.5_2of3.zip)
IBM WAS ND 8.5.5 part3 (WASND_v8.5.5_3of3.zip)
Packages for Ubuntu on Power (ppc64le):
IBM Installation Manager 1.8 (
IBM WAS ND 8.5.5 part1 (WAS_ND_V8.5.5_FOR_POWERLE_ML.zip)
IBM WAS ND 8.5.5 part2 (WASND_V8.5.5_2OF_2_FOR_POWERLE_ML.zip)
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
This charm will deploy
WAS ND Nodes to configure WAS ND dynamic cluster. WAS ND node will act as a cluster member. When you add relation between WAS ND DM and WAS ND Node charms, WAS ND DM charm creates the dynamic cluster and Node will be added as a cluster member.
Deploy the WAS ND DM charm:
juju deploy ibm-was-nd-dm --resource ibm_im_installer= --resource ibm_was_nd_installer1= --resource ibm_was_nd_installer2= --resource ibm_was_nd_installer3=
Deploy the WAS ND Node charm:
juju deploy ibm-was-nd-node --resource ibm_im_installer=</path/to/ibm_im_installer.zip> --resource ibm_was_nd_installer1=</path/to/ibm_was_nd_installer1.zip> --resource ibm_was_nd_installer2=</path/to/ibm_was_nd_installer2.zip> --resource ibm_was_nd_installer3=</path/to/ibm_was_nd_installer3.zip> OR juju deploy -n <num> ibm-was-nd-node --resource ibm_im_installer=</path/to/ibm_im_installer.zip> --resource ibm_was_nd_installer1=</path/to/ibm_was_nd_installer1.zip> --resource ibm_was_nd_installer2=</path/to/ibm_was_nd_installer2.zip> --resource ibm_was_nd_installer3=</path/to/ibm_was_nd_installer3.zip>
- Add a relation between WAS ND DM and WAS ND Node
juju add-relation ibm-was-nd-dm ibm-was-nd-node
This will create WAS ND Node host which is ready to add more hosts to the WAS ND cluster. To add more units of WAS ND Node, you can use
add-unit to add more hosts to your WAS ND cluster (each added unit will be designated as new cluster member).
juju add-unit ibm-was-nd-node
This command will add a WAS ND Node to your existing WAS ND cluster.
To accept the terms:
juju agree ibm-im/1 ibm-was-nd/1 juju deploy ibm-was-nd-node
- To Expose the IBM WAS ND Node Service to public, run the following command:
juju expose ibm-was-nd-node
Once deployed, user can upgrade the existing installation by installing fixpacks:
If user wants to upgrade existing installation of Installtion Manger, run the following command:
juju attach ibm-was-nd-node ibm_im_fixpack=</path/to/fixpack.zip>
To upgrade WAS ND Node installation:
juju attach ibm-was-nd-node ibm_was_nd_fp1=</path/to/ibm_was_nd_fp1.zip> juju attach ibm-was-nd-node ibm_was_nd_fp2=</path/to/ibm_was_nd_fp2.zip>
Note: WAS ND DM and WAS ND Node installation should be in same level(If you wan to upgrade WAS ND Node installation make sure that WAS ND DM also upgraded with same fixpack version).
Verification Of WAS ND Cluster
Once the IBM WAS ND Node is deployed successfully and relation is established between WAS ND DM and WAS ND Node, you can verify your WAS ND cluster by using below URLs.
Login to DM console:
http://was-nd-dm-host:9060/ibm/console OR https://was-nd-dm-host:9043/ibm/console
In the DM console click Servers > Clusters > Dynamic clusters >
. On right side, click dynamic cluster members and verify the status of the cluster members. All cluster members should be started.
Here was-nd-dm-host represents the public ip address of your machine, where WAS ND DM is installed.
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 ND 22.214.171.124 download available [here] [WAS-ND-126.96.36.199-download
Information about installation of WAS ND on 'ppc64le' based machine available here
More information about IBM IM Downloadable file and WAS ND downloadable files available here
For issues with this charm, please contact IBM Juju Support team email@example.com
- (string) The options passed to the 'curl' command when fetching files from curl_url. For example: '-u <user:password>'
- (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>'
- (string) Space separated list of extra deb packages to install.
- (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.
- (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.
- (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.
- (string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".