WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

What is next?
You can start the Web server and WebSphere Application Server without any
manual steps and access the snoop servlet through the Web server to verify
that everything is working.
► LOCAL_DISTRIBUTED
A LOCAL_DISTRIBUTED plug-in configuration has the following
characteristics:
– A stand-alone profile federated into a deployment manager cell.
– A managed node that is either federated or unfederated in a cell.
– A managed profile found after a default deployment manager cell
detected. See (A) in Figure 6-1 on page 189.
The Plug-ins installation wizard performs the following tasks in this case:
– Does not create a Web server definition for the default distributed profile.
– Configures the Web server to use the plugin-cfg.xml file in the Web server
definition directory that the user needs to create manually. You cannot
start the Web server until the manual steps are completed.
What is next?
– If the managed node is still not federated, federate the node first. This will
avoid the Web server definition being lost after the federation has
occurred.
– Run the manual Web server definition creation script.
– Start the Web server and WebSphere Application Server and run the
snoop servlet to verify that everything is working.
► REMOTE
A REMOTE plug-in configuration has the following characteristics:
– A remote install type selected by user at install time.
– A default deployment manager profile.
– No default profiles detected in the WebSphere Application Server directory
given by user.
– A default, unfederated, stand-alone profile with an existing Web server
definition.
The plug-ins installation wizard performs the following tasks in this case:
– Does not create a Web server definition for the default distributed profile.
– Configures the Web server to use the plugin-cfg.xml file in
/config//plugin-cfg.xml.
190 WebSphere Application Server V7.0: Concepts, Planning, and Design