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 DM (WAS ND DM) 22.214.171.124
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 DM
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 creates deployment manager profile 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
- Run the following commands to deploy this charm:
juju deploy ibm-was-nd-dm --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>
To accept the terms:
juju agree ibm-im/1 ibm-was-nd/1 juju deploy ibm-was-nd-dm
To create deployment manager profile,
manageprofilescommand needs values for username and password. To provide these run the following command:
juju config ibm-was-nd-dm dm_admin_user=<user_name> juju config ibm-was-nd-dm dm_admin_pw=<password>
juju config ibm-was-nd-dm was_admin_user="admin1" juju config ibm-was-nd-dm was_admin_pw="admin123"
Note: If any relation established between WAS ND DM and other charms, Please remove the relation before changing these config options.
If any of these values is not set, then the charm will use default values for username/password. Once WAS ND DM charm is deployed successfully, user can also delete existing profile and create new DM profile by setting new values for these configuration options.
- To Expose the IBM WAS ND DM Service to public, run the following command:
juju expose ibm-was-nd-dm
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-dm ibm_im_fixpack=</path/to/fixpack.zip>
To upgrade WAS ND DM installation:
juju attach ibm-was-nd-dm ibm_was_nd_fp1=</path/to/ibm_was_nd_fp1.zip> juju attach ibm-was-nd-dm 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 want to upgrade WAS ND DM installation after cluster setup, make sure that WAS ND Node also upgraded with same fixpack version).
After installing IBM WebSphere Application Server ND DM, use your web browser to see the WebSphere Application Server ND DM console. The URLs for WAS ND DM console are:
http://was-nd-dm-host:9060/ibm/console OR https://was-nd-dm-host:9043/ibm/console
Here was-nd-dm-host represents the public ip address of your machine, where WAS ND DM is installed.
To login WAS ND DM console use user name and password created in step 2 in
Relating with IBM WAS ND Node charm
IBM WAS ND DM charm is related to
IBM WAS ND Node charm, WAS ND DM charm will create dynamic cluster and WAS ND Node charm will federate the nodes to deployment manager(DM). Once all nodes federated to DM, cluster will be started.
To add a relation, run the following command:
juju add-relation ibm-was-nd-dm ibm-was-nd-node
To remove the relation, run the following command:
juju remove-relation ibm-was-nd-dm ibm-was-nd-node
Relating with IBM HTTP Server charm
Install a web server, such as IBM Http Server in the machine where IBM WebSphere Application Server Base installed. It provides the more configuration options, additional layer of security and load balancing for applications deployed on WAS ND cluster. Installing a web server plug-in enables the web server to communicate with the application server.
Here IBM WAS ND DM charm is related to IBM HTTP Server(IHS) subordinate charm. To add a relation, run the following command:
juju add-relation ibm-was-nd-dm ibm-http
When IBM WAS ND DM charm is related to IBM HTTP Server charm,
IBM Http Server,
Web Server Plug-ins for WebSphere Application Server and
WebSphere Customization Toolbox will be installed and configured. The web server definition is automatically created and configured during the configuration of the plug-in. Once IHS configured and admin server started, server status will be sent to the WAS ND DM charm to automatically propagate the plugin.xml file to IHS server. This plugin.xml file contains the WAS ND cluster details to redirect incoming requests to the cluster members.
After establishing relation between IBM WAS ND DM and IBM Http Server charm, you can verify by accessing the sample servlet available in WAS ND using IHS URL and IHS running port 80:
Here ihs-host-name represents the public ip address of your machine, where WAS Base and IHS deployed(IHS is subordinate charm so WAS Base and IHS charms will be deployed on same machine). 'snoop' is the sample servlet on WAS Base server to test the connection between WAS Base and IHS.
To remove the relation, run the following command:
juju remove-relation ibm-was-nd-dm ibm-http
Relating with other consumer charms
IBM WAS ND DM charm can be related to other consumer charms using the following command.
juju add-relation ibm-was-nd-dm <consumer-charm>
When IBM WAS ND DM charm is related to any consumer charm such as IBM WXS, it provides WAS ND DM installation path, profile name, username and password to start/stop the deployment manager.
User name to login WAS ND deployment manager console
The password used to login WAS ND deployment manager console.
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 126.96.36.199 download available [here] [[WAS-ND-188.8.131.52-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) The password used to log in WAS DM console.
- (string) Admin user name to log in WAS DM console.
- (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".