Portal, V6.1
Manage your cluster
After installing and configuring your clustered environment, you will need to manage the different parts of your cluster to ensure a highly available production environment.
Perform the following tasks to manage your cluster:
- Renaming the node
In a clustered environment, it may be necessary to rename a node because the deployment manager does not permit duplicate node names in a cell. You must first change the name in the deployment manager using the IBM WAS command renameNode. IBM WebSphere Portal stores the node name information in the registry so after running the WAS command, you would need to update the information in the registry.- Determining application sharing between clusters
If applications are shared between clusters, there are maintenance implications. An application definition is cell-scoped, meaning that a single application can be used by any server running on any node within the cell. The relationship between an enterprise application and the server where it runs is called a mapping. For a cluster to run an instance of an application, the application must be mapped to that cluster. An application that is shared between multiple clusters will have multiple mappings.- Applying updates to custom applications
For customer-written portlet applications that are pre-deployed as standard EARs and then configured within each cluster using XMLAccess, use the same update procedure as used for portlet applications provided with IBM WebSphere Portal.- Manage portlets in your cluster
Because all WebSphere Portal servers in the cluster share the same database, any node can be used to manage portlets. Cluster nodes do not need to be stopped when managing portlets. When you deploy a portlet, WebSphere Portal stores the portlet configuration data in the WebSphere Portal database and then forwards the portlet application's Web module and associated configuration to the deployment manager. The deployment manager is responsible for pushing the Web module to each node in the cluster. Because all WebSphere Portal servers in the cluster share the same database, any node can be used to manage portlets. Cluster nodes do not need to be stopped when managing portlets.- Manage replication in your cluster
Replication is a service provided by WAS that transfers data, objects, or events among application servers. Data replication can be used to make data for session manager, dynamic cache, and stateful session beans available across many application servers in a cluster.- Manage Portal Scripting Interface in your cluster
The Portal Scripting Interface allows you to create administrative tasks that administrators can run from a command line. You must prepare your cluster to manage Portal Scripting Interface.- Manage Single sign-on settings in your cluster
If you configured the nodes in your cluster to use single sign-on (SSO), you can change the SSO settings for the cluster.- Updating Personalization properties in a cluster
IBM WebSphere Portal provides two property files that modify to customize the Portal Personalization feature. These files are not managed by the deployment manager, so if you make any changes to these files on a node in the cluster, those changes are not transferred to other nodes when you perform a synchronization of the cluster members.- Manage WAS in your cluster
In some situations you might need to install additional WAS features on the nodes in your cluster. For example, this could be necessary if a portlet requires a WAS feature not currently installed on the nodes. When installing additional features in a clustered environment, install the features on every node in the cluster. Also, the WAS ND node cannot have fewer features than the nodes that it manages. Consequently, if you install a new feature on the managed nodes, review the features on the WAS ND node to determine whether also install the feature on the WAS ND node. For example, if you select the full installation option for WebSphere Portal, the WAS will not have the extended messaging feature installed by default. If any of your portlets use the extended messaging feature, you will have to install this new feature on all nodes before you are able to deploy these portlets.
Parent topic
Administering WebSphere Portal
Related concepts
Portal administration tools
Controlling access
Auditing
Browser behavior and scenarios
Manage portal resources with policies
Manage portlets and portlet applications
Creating pages
Use Web clipping to import content
Multiple virtual portals
Language support
Use WSRP services
Related tasks
Change database passwords that are used by WebSphere Portal
Including static content in the portal
Manage pages
Use portlet wires
Manage your site
Related reference
Reference
Related information
Users and groups
Manage portlets on a page
Customizing pages
Portal Search