After installing the WebSphere® Application Server product, you can
install it again on the same machine.
Before you begin
Supported configurations: This
topic is about configuration migration, such as migrating deployment
managers and federated nodes in a network deployment environment.
The Application Migration Toolkit for WebSphere Application Server
provides support for migrating applications from previous versions
of WebSphere Application Server to the latest product version. For
information about migrating applications, read more about the Application
Migration Toolkit.
sptcfg
Read
Overview of migration, coexistence, and interoperability and
Premigration considerations.
About this task
This is not a typical scenario. One of the main goals of
multiple-profile support is to minimize the need for scenarios like
this. One reason that you might want to install two or more instances
of WebSphere Application Server Version 8.0 on the same machine
might be a need to have different fix levels of the product on a machine
for some reason.
Procedure
- Use the Installation wizard to install another set of the
core product files as described in the "Installing the product and
additional software" article in the information center.
Select
the new installation option from the Installation wizard panel to
install a new instance instead of adding features to the last installation
and to install into a separate profile directory.
- Use the Profile Management tool or the manageprofiles command
to create multiple application-server processes.
During
profile creation using the Profile Management tool, you can specify
your port settings. Read the "Creating profiles using the graphical
user interface" article in the information center for more information.
During
profile creation, the manageprofiles command can
use port values that you specify instead of the default port values.
You can use a port file, specify a starting port, or accept the default
port values. Read the "manageprofiles command" article in the information
center for more information.
- If you have a node that you cannot start because of port
conflicts, change port assignments to nonconflicting ports in configuration
files.
Use one of the following methods: