57 lines
3.6 KiB
HTML
57 lines
3.6 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Regenerate the Web server plugin configuration with the console and wsadmin</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h4><a name="plgncfgregen"></a>Regenerate the Web server plugin configuration with the console and wsadmin</h4>
|
||
|
|
|
||
|
|
<p>When you make changes to an application server, you must regenerate the Web server plugin configuration file to ensure that the correct set of requests are forwarded to the WebSphere Application Server - Express runtime. To regenerate the plugin configuration, follow these steps:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><a href="#acregen">Use the administrative console to regenerate the Web server plugin configuration</a></li>
|
||
|
|
<li><a href="#wsaregen">Use wsadmin to regenerate the Web server plugin configuration</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p><strong><a name="acregen">Use the administrative console to regenerate the Web server plugin configuration</a></strong></p>
|
||
|
|
<ol>
|
||
|
|
<li><a href="acstart.htm">Start the WebSphere administrative console</a>.</li>
|
||
|
|
<li>In the topology tree, expand <strong>Environment</strong> and click <strong>Update Web Server Plugin</strong>.</li>
|
||
|
|
<li>On the <strong>Update web server plugin configuration</strong> page, click <strong>OK</strong>.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> If you make manual updates to the plugin configuration file, those updates may be overwritten when you regenerate the file. To avoid overwriting your manual updates, make a backup copy of the plugin configuration file before your regenerate the file, then use its contents to manually update the configuration file after you regenerate it.</p>
|
||
|
|
<!-- font color="red">Kent's comment from first review: I'd like to check on this once our final concurrent PTFs are approved - I thought that there was work in progress to eliminate this speedbump so that user added lines would be preserved...</font -->
|
||
|
|
|
||
|
|
<p><strong><a name="wsaregen">Use wsadmin to regenerate the Web server plugin configuration file</a></strong></p>
|
||
|
|
<ol>
|
||
|
|
<li><p>On the CL command line, run the STRQSH (Start Qshell) command.</p></li>
|
||
|
|
|
||
|
|
<li><p>Run the cd command to change to the directory that contains the wsadmin tool:</p>
|
||
|
|
<pre>cd /QIBM/ProdData/WebASE51/ASE/bin</pre></li>
|
||
|
|
|
||
|
|
<li><p><a href="wsarun.htm#start">Start wsadmin</a>.</p></li>
|
||
|
|
|
||
|
|
<li><p>At the wsadmin prompt, run this command to identify the web server plugin configuraiton file generator MBean and assign it to the pluginGen variable:</p>
|
||
|
|
<pre>set pluginGen [$AdminControl completeObjectName type=PluginCfgGenerator,*]</pre></li>
|
||
|
|
|
||
|
|
<li><p>Run this command to generate the updated plugin configuration file:</p>
|
||
|
|
<pre>$AdminControl invoke $pluginGen generate "/QIBM/UserData/WebASE51/ASE/<em>instance</em>/
|
||
|
|
/QIBM/UserData/WebASE51/ASE/<em>instance</em>/config <em>myCell</em> null null null"</pre>
|
||
|
|
<p>where <em>instance</em> is the name of your application server instance and <em>myCell</em> is the name of the cell that contains your application server.</p>
|
||
|
|
<p><strong>Note:</strong> This command has been wrapped for display purposes.</p>
|
||
|
|
<p>This example command invokes the generate operation on the MBean passing the instance directory, the configuration root directory, and the cell name.</p></li>
|
||
|
|
|
||
|
|
<li><p>Run this command to save your changes:</p>
|
||
|
|
<pre>$AdminConfig save</pre></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|