請教各位關於WAS Plugins的安裝問題,急等

fastzch 2007-07-13 09:05:17

我的安裝步驟如下:
1,安裝WAS
2,安裝IHS
3,安裝WAS Plugin
4,啟動WAS
5,將plugin下bin目錄中的configurewebserver.bat copy到WAS_HOME\AppServer\bin目錄下,運行.

運行時産生的結果如下:
C:\Program Files\IBM\WebSphere\AppServer\bin>wsadmin.bat -f configureWebserverDe
finition.jacl webserver IHS "C:\\Program Files\\IBM\\HTTPServer" "C:\\Program Fi
les\\IBM\\HTTPServer\\conf\\httpd.conf" 80 MAP_ALL "C:\\Program Files\\IBM\\WebS
phere\\Plugin" unmanaged ing-4 ing-4 windows
WASX7209I: Connected to process "server1" on node ing-4Node01 using SOAP connect
or; The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are
available as arguments that are stored in the argv variable: "[webserver, IHS,
C:\\Program Files\\IBM\\HTTPServer, C:\\Program Files\\IBM\\HTTPServer\\conf\\ht
tpd.conf, 80, MAP_ALL, C:\\Program Files\\IBM\\WebSphere\\Plugin, unmanaged, ing
-4, ing-4, windows]"

Input parameters:

Web server name - webserver
Web server type - IHS
Web server install location - C:\Program Files\IBM\HTTPServer
Web server config location - C:\Program Files\IBM\HTTPServer\conf\httpd.conf

Web server port - 80
Map Applications - MAP_ALL
Plugin install location - C:\Program Files\IBM\WebSphere\Plugin
Web server node type - unmanaged
Web server node name - ing-4
Web server host name - ing-4
Web server operating system - windows
IHS Admin port - 8008
IHS Admin user ID - ""
IHS Admin password - ""
IHS service name - ""

Web server node definition ing-4Node01 already exists.

Web server definition for webserver already exists.

Start computing the plugin properties ID.
Plugin properties ID is computed.

Start updating the plugin install location.
Plugin install location is updated.

Start updating the plugin log file location.
Plugin log file location is updated.

Start updating the RemoteConfigFilename location.
Plugin remote config file location is updated.

Start updating the RemoteKeyRingFileName location.
Plugin remote keyring file location is updated.

Start saving the configuration.

Configuration save is complete.

Computed the list of installed applications.

Processing the application DefaultApplication.
Get the current target mapping for the application DefaultApplication.
Computed the current target mapping for the application DefaultApplication.
Start updating the target mappings for the application DefaultApplication.
Target mapping is not updated for the application DefaultApplication, exception
= com.ibm.ws.scripting.ScriptingException: com.ibm.websphere.management.exceptio
n.AdminException
javax.management.MBeanException
com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid targe
t is specified in ObjectName WebSphere:cell=ing-4Node01Cell,node=ing-4Node01,ser
ver=webserver1 for module DefaultWebApplication.war+WEB-INF/web.xml.

Processing the application WebSphereTPHost.
Get the current target mapping for the application WebSphereTPHost.
Computed the current target mapping for the application WebSphereTPHost.
Start updating the target mappings for the application WebSphereTPHost.
Target mapping is updated for the application WebSphereTPHost.

Processing the application ivtApp.
Get the current target mapping for the application ivtApp.
Computed the current target mapping for the application ivtApp.
Start updating the target mappings for the application ivtApp.
Target mapping is not updated for the application ivtApp, exception = com.ibm.ws
.scripting.ScriptingException: com.ibm.websphere.management.exception.AdminExcep
tion
javax.management.MBeanException
com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid targe
t is specified in ObjectName WebSphere:cell=ing-4Node01Cell,node=ing-4Node01,ser
ver=webserver1 for module ivtEJB.jar+META-INF/ejb-jar.xml.

Processing the application query.
Get the current target mapping for the application query.
Computed the current target mapping for the application query.
Start updating the target mappings for the application query.
Target mapping is not updated for the application query, exception = com.ibm.ws.
scripting.ScriptingException: com.ibm.websphere.management.exception.AdminExcept
ion
javax.management.MBeanException
com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid targe
t is specified in ObjectName WebSphere:cell=ing-4Node01Cell,node=ing-4Node01,ser
ver=webserver1 for module querybean.jar+META-INF/ejb-jar.xml.

Start saving the configuration.

Configuration save is complete.

看起來應該沒有任何錯誤.
6,重新啟動WAS,然後産生外挂程式和傳送外挂程式,正常.plugin-cfg.xml的內容如下:
<?xml version="1.0" encoding="ISO-8859-1"?>

<Config ASDisableNagle="false" AcceptAllContent="false" AppServerPortPreference="HostHeader" ChunkedResponse="false" FIPSEnable="false" IISDisableNagle="false" IISPluginPriority="High" IgnoreDNSFailures="false" RefreshInterval="60" ResponseChunkSize="64" VHostMatchingCompat="false">
<Log LogLevel="Error" Name="C:\Program Files\IBM\WebSphere\Plugin/logs/webserver/http_plugin.log"/>
<Property Name="ESIEnable" Value="true"/>
<Property Name="ESIMaxCacheSize" Value="1024"/>
<Property Name="ESIInvalidationMonitor" Value="false"/>
<VirtualHostGroup Name="default_host">
<VirtualHost Name="*:9080"/>
<VirtualHost Name="*:80"/>
<VirtualHost Name="*:9443"/>
<VirtualHost Name="*:5060"/>
<VirtualHost Name="*:5061"/>
<VirtualHost Name="*:443"/>
</VirtualHostGroup>
<ServerCluster CloneSeparatorChange="false" IgnoreAffinityRequests="true" LoadBalance="Round Robin" Name="server1_ing-4Node01_Cluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="ing-4Node01_server1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="ing-4" Port="9080" Protocol="http"/>
<Transport Hostname="ing-4" Port="9443" Protocol="https">
<Property Name="keyring" Value="C:\Program Files\IBM\WebSphere\Plugin/config/webserver/plugin-key.kdb"/>
<Property Name="stashfile" Value="C:\Program Files\IBM\WebSphere\Plugin/config/webserver/plugin-key.sth"/>
</Transport>
</Server>
</ServerCluster>
<UriGroup Name="default_host_server1_ing-4Node01_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/WebSphereTPHosts/*"/>
</UriGroup>
<Route ServerCluster="server1_ing-4Node01_Cluster" UriGroup="default_host_server1_ing-4Node01_Cluster_URIs" VirtualHostGroup="default_host"/>
<RequestMetrics armEnabled="false" loggingEnabled="false" rmEnabled="false" traceLevel="HOPS">
<filters enable="false" type="URI">
<filterValues enable="false" value="/snoop"/>
<filterValues enable="false" value="/hitcount"/>
</filters>
<filters enable="false" type="SOURCE_IP">
<filterValues enable="false" value="255.255.255.255"/>
<filterValues enable="false" value="254.254.254.254"/>
</filters>
<filters enable="false" type="JMS">
<filterValues enable="false" value="destination=aaa"/>
</filters>
<filters enable="false" type="WEB_SERVICES">
<filterValues enable="false" value="wsdlPort=aaa:op=bbb:nameSpace=ccc"/>
</filters>
</RequestMetrics>
</Config>

7,訪問http://localhost/hitcount報404錯誤,訪問http://localhost:9080/hitcount畫面正常出現.
8,訪問http://localhost/正常出現畫面

請問各位,錯誤出在哪裏?
我以前好像也是這樣裝過,成功了,但今天為何不成功?
是不是我忘了哪一步?

...全文