Complete the setup by creating the Web server definition.
You can use the WebSphere Application Server administrative console
or run the Plug-in configuration script. You must create an application
server profile or a custom profile and federate the node before you can use
the administrative console of the deployment manager to create a Web server
definition. The same is true for running the configuration script that the
Plug-ins installation wizard created. You must assign the Web server to a
managed node when you create it.
The managed node must exist before
running the Plug-ins installation wizard. Otherwise, the installation is considered
a remote installation.
If you install the plug-in, save the script
to run after you create a managed node. Otherwise an error occurs. Wait until
the script runs successfully and creates the Web server definition on the
managed node and node synchronization occurs before starting the Web server.
Adding the node, starts the node agent process. If the node agent is not running
for some reason, start the node. See
startNode command for more information.
Tip: If you want the
Web server to handle requests for an application for multiple managed nodes,
install the application on each managed node and on the Web server definition.
The script already contains all of the information that you must gather when
using the administrative console option. Select one of the following options:
- Using the administrative console:
- Click Servers > Web servers > New and use the Create new Web
server entry wizard to create the Web server definition.
- Select the appropriate node.
- Enter the Web server properties:
- Type: The Web server vendor type
- Port: The existing Web server port (default: 80)
- Installation path: The Web server installation path. This field is required
for IBM HTTP Server only.)
- Service name (Windows operating systems): The windows operating system
service name of the Web server. The default is IBMHTTPServer6.0.
- Use secure protocol: Use the HTTPS protocol to communicate with the Web
server. The default is HTTP.
- Plug-in installation location: The directory path in which the plug-in
is installed.
- Select a template. Select a system template or a user-defined template
for the Web server you want to create.
- Confirmation of Web server creation.
- Running the configuration script. Refer to tins_webplugins_local.