Install the WebSphere Portal 8 on the primary node.

In this scenario we install the WebSphere Portal 8 on a Primary Node.

The steps that are completed are:

  • Installation of the binaries
  • Migrate the database
  • Create the profile Template
  • Federate the Primary node to an existing DMGR

When creating the profile template it will create a backup of the primary node's wp_profile, enable the Portal profile templates within the WebSphere Application Server Profile Management tool.

This will allow you to create new Portal profiles in the future, Recommended not to skip this section if you are building a multi node environment.

Completing this step is a prerequisite for configuring the secondary nodes should you wish to add more nodes.

WARNING: This task requires write access to the PortalServer root directory. By default, this directory is read/execute only (550). If you are using a non-root user, then this task may halt as a result and ask you to give temporary Write access to the PortalServer root directory for this user.

You can reset permissions after the scripts are completed.

Using the default template WebSphere Portal will be configured to use an external database. If you not require this step this ignore the Database settings on the template page and disable the WebSpherePortalDatabaseMigrationTask in the Orchestration file.

Please check for any additional database steps based on which database you are migrating too. The plugin WebSpherePortalDatabaseMigrationTask will create 6 databases following the instructions in the Product Documentation:

  • Feedback
  • Likeminds
  • Release
  • Community
  • Customization
  • JCR

Configure you Portal to use a Database

NOTE: Before running the WebSpherePortalDatabaseMigrationTask you must configure the appropriate scripts to setup the initial tables/schema’s. In order to create the databases, you must be logged into the system as the database administrator. Ensure the database client is installed and configured on the node.

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 Primary Node Template, complete all the required parameters.

Tasks related to this template:

  • WebSpherePortal8InstallBinary
  • WebSpherePortalProfilesFromTemplatesNodeTask
  • WebSpherePortalDatabaseMigrationTask
  • WebSpherePortalFederatePrimaryNodeTask

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.

TODO - Incert link to taskmetadata.xml

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 files these added extra files:

  • <serverName>.<environmentName>.<applicationName>.db>
  • <serverName>.<environmentName>.<applicationName>.dmgr>

The *.db file contains all the database configuration details and is used by the WebSpherePortalDatabaseMigrationTask when enabled to populate the wkplc property files used by WebSphere Portal.

The *.dmgr file contains the configuration details and is used by the WebSpherePortalFederatePrimaryNodeTask to populate the wkplc property files used by WebSphere Portal.

Ensure that the cluster definition was created correctly by logging into the DMGR Admin Console and browse to Server -> Clusters -> WebSphere Application Server Clusters. An entry for your Portal cluster should be present.

We have one manual step to complete at this stage as this would require a seperate deployment to the DMGR node you automate.

While logged in to the DMGR, navigate to Servers → Server Types → WebSphere application servers → WebSphere_Portal → Session Management → Distributed Environment Settings

  1. Click the blue link for 'Memory-to-memory replication'.
  2. In the Replication Domain drop-down menu, select the one for your cluster (e.g. PortalCluster).
  3. In the Replication Mode drop-down menu, select 'Both client and server'.
  4. Click OK and Save all changes.
  5. Restart the DMGR, NodeAgent, and WebSphere_Portal server.

At this point, you have successfully installed WebSphere Portal v8.0 with WebSphere Application Server - Verify Portal is functional by accessing it in your web