Microsoft Internet Information Services (IIS)
The Web Server Plug-ins Configuration Tool can determine the correct files to edit.
Note
The best practice is to use 32-bit plug-ins on IIS 7.
Sun Java System Web Server (formerly Sun ONE Web Server and iPlanet Web Server) Version 6.0 and later
obj.conf and magnus.conf
9. Specify a unique name for the web server definition, and click Next.
10. Select the configuration scenario.
. Choose the local scenario.
a. Perform one of the following actions:
Enter the installation location of WebSphere Application Server (app_server_root).
Click Browse, find the installation location of WebSphere Application Server (app_server_root), and click OK.
b. Click Next.
11. Select the profile to configure with the current web server plug-in, and click Next.
12. Review the summary information, and click Configure to begin configuring the web server, web server plug-in, and application server profile.
13. Verify the success of the installation on the summary panel, and click Finish.
If a problem occurs and the installation is unsuccessful, examine the logs in the plugins_root/logs directory. Correct any problems and re-configure.
14. Copy the configureweb_server_name script to paste on Machine A.
15. Create the web server definition on Machine A.
You can use the administrative console of the deployment manager to create the web server definition on a federated node; or you can run the configuration script that the Web Server Plug-ins Configuration Tool created.
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.
Running the configuration script
. Paste the configureweb_server_name script from Machine B to the app_server_root/bin directory on Machine A.
a. Issue the appropriate command from a command window:
./plugins_root/bin/configureweb_server_name.sh
plugins_root\bin\configureweb_server_name.bat
./plugins_root/bin/configureweb_server_name
If you have enabled security or changed the default JMX connector type, edit the script and include the appropriate parameters on the wsadmincommand.
16. From the administrative console of the deployment manager, click System administration > Save Changes to Master Repository > Synchronize changes with Nodes > Save.
17. Domino web server only: Set the WAS_PLUGIN_CONFIG_FILE environment variable.
On platforms such as AIX or Linux, sourcing a script to the parent shell allows child processes to inherit the exported variables. On Windows systems, run the script as you would run any other command. Sourcing is automatic on Windows systems.
18. Start the Snoop servlet.
See the Snoop procedure for the standalone application server for the full procedure.
Results
The installation of the Web Server Plug-ins results in the creation of the Plugins directory and several subdirectories. The following directories are among those created on a Linux system, for example:
plugins_root/bin contains the binary plug-ins for all supported web servers
plugins_root/logs contains log files
plugins_root/properties contains version information
The Web Server Plug-ins Configuration Tool creates a web server definition within the application server profile unless one already exists.
The Web Server Plug-ins Configuration Tool configures the web server to use the profile_root/plugin-cfg.xml file.
The application server 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. The standalone application server regenerates the file in the following location:
profile_root
/config/cells/cell_name/nodes/
web_server_name_node/servers/
web_server_name/plugin-cfg.xml
On a federated node, the creation or removal of clusters and cluster members also causes file regeneration. The deployment manager regenerates the file for a federated application server in the following location:
profile_root
/config/cells/cell_name/nodes/
node_name_of_AppServer/servers/
web_server_name/plugin-cfg.xml
What to do next
You can start a standalone application server and the web server immediately after configuring the plug-in for the local web server. Open the administrative console of the application server after you start the server and save the changed configuration.
After configuring the plug-in for the local web server, you can start a federated application server and the web server after running the script that completes the configuration. Open the administrative console of the deployment manager. Wait for node synchronization to occur. Save the changed configuration that includes the new web server definition.
See Selecting a web server topology diagram and roadmap for an overview of the installation procedure.
See 
Plug-ins configuration for information about the location of the plug-in configuration file.
See Web server configuration for information about the files involved in configuring a web server.
See Editing web server configuration files for information about how the Web Server Plug-ins Configuration Tool configures supported web servers.
See Installing and configuring web server plug-ins for information about other installation scenarios for installing web server plug-ins.
以下文章点击率最高
Loading…