#!/bin/bash
# sample shell script
#
# create the deployment manager node
# and the deployment manager server
manageprofiles.sh -create
-profileName CellManager
-profilePath /opt/profiles/cellManager
-templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/dmgr
# create a profile for a node that will be managed
# by the deployment manager we just created
# There are no servers in this node -- just a node agent
manageprofiles.sh -create
-profileName FirstNode
-profilePath /opt/profiles/firstNode
-templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/managed
# Federate the new node into the cell
# that the deployment manager controls
addNode.sh DmgrHostName -profileName FirstNode
# Create an application server in the node
wsadmin.sh -lang jython
-c "AdminTask.createApplicationServer( FirstNode,
['-name', 'muggle', '-template', 'default'] )"
|
Installing WebSphere Application Server v6.1 will typically involve the following activities more or less in the order listed
-
Install the WebSphere Application Server binaries on
each computer that will have a managed web server, an
application server, a node agent, or a deployment
manager.
-
Use the manageprofiles shell script to create a
deployment manager profile
-
Use the manageprofiles shell script to create a
managed node. (Earlier versions of WAS called this a
custom node) This node will not have any application
servers or node agents at this time.
-
Use the addNode shell script to federate the new node.
This creates a node agent and tells the node agent where
to find the deployment manager for this cell
-
Add one or more application servers and web servers to
the new node
|
