Install the Deployment Manager

In this scenario we install the WebSphere deployment manager and configure it for portal and assume that the DMGR is configured on a remote node. The steps that are completed are:

  • Installation of the binaries
  • Configuration of the DMGR profile
  • Copies and extracts the
  • Augment the DMGR profile
  • Start the DMGR ready for the next steps

Augmenting the DMGR profile will automatically make the following changes:

  • Increases the HTTP connection timeouts for the DMGR server
  • Increases the SOAP connector timeout for JMX in the DMGR server
  • Increases the JVM Maximum Heap size for the DMGR server
  • Enables Application Security
  • Creates a 'wpsadmins' group in the default file repository
  • Adds your administrative user to the 'wpsadmins' group.
  • Increases the soap timeout in the soap.client.props file.

To achieve this; the installation and configuration are associated in just one RapidDeploy project. This installation will be completed using the WebSphere Portal installation media and will install from a network location.

NOTE: You will need to be familiar with IIM response files in order to create you first template; the plugin provides a sample response xml file for reference.

To create a new project, go to the project page and select the Project Creation Wizard and on the product tab select the WebSphere Portal 8 plugin from the available products. Next on the Environment tab select the WebSphere Portal 8 Configure Dmgr Template, complete all the required parameters.

Tasks related to this template:

  • WebSpherePortal8InstallBinary
  • WebSpherePortalConfigureDMRGTask

It is advised that you read up on each task that is associated with each task in the templates before running or modifying them, this will save you time and help you to complete the required fields correctly.

TO DO - Insert link to taskmetadata.xml

When installing the binaries you can have a pre-installed DMGR profile which will be used or it will be created by the WebSpherePortalConfigureDMRGTask if it does not exist.

Review and create the project, this will create a new project the required basic tasks needed to create a deployment manager.

In the project files you will find the normal RapidDeploy project file with 2 extra files:

  • install_WAS_BASE.xml

You can use these files or replace them with your own versions either in the package or on a different shared location on the file system. file is created when a primary node is first created and should match the version of portal you are installing, the default file added to the project is for WebSphere Portal 8.0.

The install_WAS_BASE.xml file is a sample response file which can also be replaced in the package or a new path to a shared file can be used.

Reviewing and modifying the project.

On the project page select the newly created project and select the Orchestration tab:

The task will be prepopulated default values and with the data dictionary items that were completed during the project creation wizard. To us a different response file just modify the path in the WebSpherePortal8InstallBinary Task, supported variables can also be used if using IBMIM 1.72 or newer.

In the WebSpherePortalConfigureDMGR Task review and modify the parameters as needed. file is created when a primary node is first created and should match the version of portal you are installing, the default file added to the project is for WebSphere Portal 8.0.

Once you are have modified and reviewed the package it is now ready for deployment, please referee to the RapidDeploy documentation on creating and deploying a new package.

Once the deployment has completed launch the DMGR admin console on: (9060 is the default port)