Install the WebSphere Portal 8 on the secondary node.

In this scenario we install the WebSphere Portal 8 on a secondary node, this step can be run many time depending on the number of nodes you require in your environment.

The steps that are completed are:

  • Installation of the binaries.
  • Create the profile from the the profileTemplates.zip file that was created on the primary node.
  • Federate the secondary node to an existing DMGR.

If you default database is derby then you can leave the default database settings as default as these will be ignored during the deployment.

I need to review this section

NOTE: Select a new database only if you have migrated the primary node to that same database. Ensure the database client is installed and configured on the node.

Edit the wkplc_dbdomain.properties file in the wp_profile root/ConfigEngine/properties directory and ensure that the database password values are all set correctly.

NOTE: This file should be pre-populated with your database information from running the 'enable-profiles' script on the primary node earlier.

Edit the wkplc_dbtype.properties file in the wp_profile root/ConfigEngine/properties directory and ensure that the dbType.DbLibrary value is valid for this system.

NOTE: This file should be pre-populated with your database information from running the 'enable-profiles' script on the primary node earlier.

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

Tasks related to this template:

  • WebSpherePortal8InstallBinary
  • WebSpherePortalProfilesFromTemplatesNodeTask
  • WebSpherePortalFederateSecondaryNodeTask

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:

NOTE: Do Not add any WebSphere Portal profile when building the response file as it will be created automatically by the profileTemplate.zip file from the primary node.

NOTE: It is important to add the newly created profileTemplate.zip to your new package or the correct a path to the shared file system, this same package will be used for all secondary nodes in your new enviroment.

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.

Restart the DMGR, NodeAgent, and WebSphere_Portal server.

At this point, you have successfully installed WebSphere Portal v8.0 with WebSphere Application Server 8.0.0.3 - Verify Portal is functional by accessing it in your web http://mysecondaryportal.com:10039/wps/portal