Use this article to review a description of a WebSphere Extended
Deployment installation with WebSphere Portal for Multiplatforms that supports
a basic configuration.
Procedure
- Install WebSphere Application Server Network Deployment.
You can also include the following interim fix images:
See Preparing WebSphere Application Server Network Deployment to install
the product
for
more information.
- Install WebSphere Extended Deployment. You can also
include the interim fix image PK30163.
See Installing and configuring the product
for more information.
- Install and federate the ODR node to the deployment manager.
See Adding nodes to the deployment manager
for
more information.
- Optional: Install the DB2 database server node.
See IBM Software Library page for more information.
- Install the primary node for WebSphere Portal for Mulitplatforms.
- Select the location in which you installed WebSphere Application
Server Network Deployment. Type the location or browse for it by
clicking the available button if the location is not listed.
- Select an installation path for WebSphere Portal.
- Optional: Provide the appropriate user ID and password
containing OS privileges to run WebSphere Portal as a service.
- Provide your administrative user ID and password.
- Migrate the default Cloudscape database to a database that allows
remote connections.
- Stop the server by running stopServerWebSphere_Portal in
the command prompt.
- Migrate to WebSphere Portal for Mulitplatforms 5.1.0.3.
- Stop all of the servers that are located on the WebSphere Portal
node. Run the serverStatus_all command in the
command prompt to verify which servers are running.
- Run WebSphere Extended Deployment and run the addNode_includeapps command
to federate the node to the deployment manager.
See the WebSphere Portal for Multiplatforms Information Center for
more information.
- Optional: Install additional nodes for WebSphere Portal
for Multiplatforms.
- Complete the previous steps described to install WebSphere Portal
on each additional node.
- Connect the secondary node to the existing database. Run WPSconfig
connect_database from the WPS_HOME/config directory.
- Modify the WPS_HOME/config/wpconfig.properties file.
Change the value of the PrimaryNode variable from true to false.
- Federate each additional node to the deployment manager, but
do not use the includeapps option.
What to do next
You can now install and configure the nodes to a dynamic cluster
in your WebSphere Extended Deployment environment.