Getting started

There are many different ways to build a WebSphere Portal cluster. For this quick start guide we will install the following components using the default templates within the plugin.

  1. Installing the Deployment Manager on a separate server
  2. Configuring the Deployment Manager
  3. Installing the Primary Portal node
  4. Configuring the Primary node for a remote database
  5. Enabling Portal profiles
  6. Federating and Clustering the Primary Node
  7. Installing an additional Portal Node
  8. Federating and Clustering an additional Portal node
  9. Deploying, deleting Portlets and Portal Configuration
  10. Cloning portal content

Templates in RapidDeploy are a quick way to get started for the default task and can be easily modified by adding or deleting tasks in the orchestration file.

NOTE: This guide assumes you are familiar with creating projects in RapidDeploy so will only cover the steps that are required to build a new WebSphere Portal 8 environment.

NOTE: This guide also assumes you have knowledge on WebSphere Portal 8 installation and administration. Please refare to - Portal Wiki

Templates

Templates in RapidDeploy are a quick way to get started for the default task and can be easily modified by adding or deleting tasks in the orchestration file. A number of templates and tasks have been pre-built for the WebSphere Portal plugin to help you achieve the above goals in and easy and quick way, in the guide we will go over each template one by one and how you can alter these to suit you different needs.

The WebSphere Portal Plugin 1.0.0 comes with four built in templates:

  • WebSphere Portal 8 Configure Dmgr Template
  • WebSphere Portal 8 Primary Node Template
  • WebSphere Portal 8 Secondary Node Template
  • WebSphere Portal 8 Application Template

We create the environments using the WebSphere Portal 8 Templates, which extracts all of the variables (settings that change between environments), to a dictionary file of name/value pairs. We then 'clone' (copy) this environment to further downstream ones by changing the values in the dictionary file (where required) for the new environment.

In this way we use a single file to capture, as name value pairs, the differences between environments. The template will also create the base midvision-orchestration.xml file with a number pre-set tasks and resource tokens i.e @@intsallPath@@.

On selection of a template in the Project Creation Wizard – Environment page, a user is presented with a template form asking for certain parameters, some optional.

Once these have been filled in to the user’s requirements the wizard will create a package with pre-defined orchestration task list and other required files depending on the template that was chosen.

Let’s look at one template as an example.

Figure 1.0 WebSphere Portal 8 Configure Dmgr Template

Figure 1.0 WebSphere Portal 8 Configure Dmgr Template

The WebSphere Portal 8 Configure Dmgr Template will create the following files as default.

DMGR_INSTALL

  • - classpath.xml
  • - log4j.properties
  • - midvision-deploy-orchestration.xml

    j2ee

    • -filesForDmgr.zip
    • -install_WAS_BASE.xml

    config

    • -deploymentManager.portalEnv.portalCluster.portal.env
    • -deploymentManager.portalEnv.portalCluster.portal.py
    • -deploymentManager.portalEnv.portalCluster.portal.conf
    • -deploymentManager.portalEnv.portalCluster.portal.dict

Default task are:

Figure 2.0 WebSphere Portal 8 Configure Dmgr Template

Once the default template project has been created the project orchestration task list can be amended if required. Just open the project in edit mode and you can edit the orchestration file by adding, removing or modifying the task list as you would any other RapidDeploy project.