This procedure describes installing a Web server and its plug-in on a machine where the default profile is a custom profile.
Before you begin
This procedure configures the custom profile that is the default profile on the machine. This procedure assumes that you already have installed a deployment manger on Machine A.
The WebSphere Application Server node on Machine B is the custom node that you create in this procedure. This procedure starts the deployment manager and federates the custom node before installing the Web server plug-ins.
Start the deployment manager. The deployment manager must be running to successfully federate and configure the custom node.
Why and when to perform this task
Use the following procedure to install the Web server plug-in, configure the Web server, and create a Web server definition in the default custom profile (custom node).
Steps for this task
Click Servers > Applications servers > New and follow the instructions to create a server. A server is not required for installing the plug-ins but it lets you verify the functionality of the Web server.
The DefaultApplication includes the snoop servlet. The verification step uses the snoop servlet.
Use the stopServer command or the administrative console of the deployment manager to stop the managed node.
The fully qualified path identifies the installation root directory for the Network Deployment product core files.
See Plug-ins configuration for a description of the logic that determines what path is configured by default. The wizard determines the characteristics of the managed application server node to determine the best path for the file:
profile_root /config/cells/cell_name/nodes/ node_name_of_custom_profile/servers/ web_server_name/plugin-cfg.xml
Accept the default value.
You can use the administrative console of the deployment manger to delete an existing Web server or to create new ones. Federated nodes can have more than one Web server definition.
The wizard shows an installation status panel as it installs the plug-ins. The wizard displays the Installation summary panel at the completion of the installation.
See Fast paths for WebSphere Application Server for help in deploying applications.
Identify the same managed node each time. Give each Web server a different nick name.
Result
This procedure results in the installation of the Web server plug-ins for WebSphere Application Server on a Web server machine. The Plug-ins installation wizard creates a Web server definition within the managed node.
The Plug-ins installation wizard configures the Web server to use the plugin-cfg.xml file that is within the managed custom node.
The deployment manager regenerates the Web server plug-in configuration file, plugin-cfg.xml whenever an event occurs that affects the file. Such events include the addition or removal of an application, server, or virtual host.
profile_root /config/cells/cell_name/nodes/ node_name_of_custom_profile/servers/ web_server_name/plugin-cfg.xml
What to do next
After installing the binary plug-in for the local Web server, you can start the managed node and the Web server after running the configuration script that completes the installation.
See Plug-ins configuration for information about the location of the plug-in configuration file.
See Web server configuration for more information about the files involved in configuring a Web server.
See Editing Web server configuration files for information about how the Plug-ins installation wizard configures supported Web servers.
See Installing Web server plug-ins for information about other installation scenarios for installing Web server plug-ins.
Related concepts
Plug-ins configuration
Related tasks
Installing Web server plug-ins