Professional Documents
Culture Documents
and Maintenance of
WebSphere Application
Server 8.5
ESIS Consulting LLC
Section 2
Installation, Configuration
and Maintenance
Choosing topology
Questions to ask:
1. Where will you place the DMGR ?
2. How many hosts are in your cell ?
3. Do you need Flexible management ? (i.e) Do
you need to install Job Manager and
Administrative Agents ?
4. Do you need a Web Server ? Where is it
located ? (i.e) DMZ or LAN
Determining topology before the installation is important since the installation process
differs for each topology
Secure Proxy for WAS is a high speed reverse proxy that can be used to load
balance and route requests for Web Applications. Consider this as a Web Server.
Secure Proxy does NOT have a web container and hence NO admin console. Use
wsadmin to manage Secure Proxy runtime
Installation steps:
Install WAS as previous topologies. The Secure proxy installation steps are provided
below
1. On Host 1, use profile management tool to create an Administrative Agent profile
2. On host 1, create a secure proxy configuration only profile
3. Register secure proxy with Admin Agent (using registerNode command)
4. Using AdminTask.exportProxyServer command, export secure proxy configuration
to an EAR file
5. On Host 2 install DMZ Secure Proxy (Using IBM installation Manager)
6. Copy the configuration export from Host1 to Host 2 and run AdminTask.
importProxyServer command to import configuration (you must repeat this step
whenever you make configuration changes to Secure Proxyy)
The exact command to use will depend on the platform. Generally windows platforms
will have .exe added to the commands. Unix platforms will not have this extension.
You can install the IBM installation manager in a)Admin mode b)User mode c)Group
mode
Group mode is NOT available on Windows platforms
Admin mode: Only administrators can install and use the product. There can be only
one Admin instance.
User mode: Only the user who performed the install can use the product. There can
be only one User instance per user
Group mode: Users from a particular group can install use the product. The package
you install must be enabled for group mode
Click 'install'
IBM Installation manager searches the
repositories configured and displays the
available packages to install
Select "IBM WebSphere Application Server
Network Deployment" and appropriate
version
You may be prompted for IBM ID and password if "Search service repositories during
installation and updates" option is selected in IBM Installation Manager preferences.
You may also be prompted to update IBM Installation manager to update to its latest
version. You must do so before proceeding.
Websphere 8.5 default runtime environment is Java 1.6. But it does support Java 1.7
Websphere 8.5 default runtime environment is Java 1.6. But it does support Java 1.7
IBM Installation manager log file is an xml file
You can use chutils command to change permissions (Owner and group) on the
entire installation.
Installation verification
The installver command used in Websphere
7 and prior has been replaced by the
verification capabilities of IBM Installation
Manager
Start the IBM Installation manager, click File
-> view installed packages to verify
successfully installed packages
The file 'installed.xml' should contain a
'location' element. (Example: <WAS
Root>/properties/version/installe
d.xml)
The first profile you create is the 'default' profile which is the target for commands
issued from <WAS ROOT>/bin
A node group is a collection of nodes. Node groups define the boundary of a Cluster.
By default all the nodes belong to default Node Group
When you are starting or stopping a managed node, you are really working on the
Node Agent process of the node which is the administrative agent that represents a
node