|
Home > Archive > WebSphere Application Server > December 2005 > Websphere Application Server, IBM HTTP Server, Plugin setup
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Websphere Application Server, IBM HTTP Server, Plugin setup
|
|
| vannguyen0 2005-12-29, 8:53 pm |
| Hi,
I currently have WAS v6, IBM HTTP v6, and the WAS plugin installed on one machine. I'm trying to set up virtual hosts and have a couple of questions. I've setup my httpd.conf to look like this:
...
<VirtualHost 10.10.10.48:80>
ServerName jwatest.ur.com
<Directory "c:/Program Files/IBM HTTP Server/htdocs/en_US">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs/en_US"
DirectoryIndex index2.html
</VirtualHost>
...
I then configure a new virtual host in WAS v6 listening on port:
jwatest.ur.com -> 80
jwatest.ur.com -> 9080
When I install an application, I map the module to only the application server. I can access it via the 9080 port only. When I go back and map the module to both the application server (server1) and webserver (webserver1), I am able to access the applic
ation via port 80. Am I doing this right? When I deploy, do I need to map the module to both the application server and the webserver?
| |
|
| Hi
I would suggest u can re-generate plugin through websphere admin console. You can also generate plug-in after deploying web application.
Also please look into plugin-cfg.xml file and see all respective transport, URI, virtual host entries are available. In our case
<VirtualHostGroup Name="default_host">
<VirtualHost Name="*:9080"/>
<VirtualHost Name="*:80"/>
<VirtualHost Name="*:10014"/>
<VirtualHost Name="*:443"/>
</VirtualHostGroup>
<ServerCluster CloneSeparatorChange="false" LoadBalance="Round Robin" Name="appsername_hostname_appsername_Cluster" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server ConnectTimeout="0" ExtendedHandshake="false" MaxConnections="-1" Name="hostname_appsername_appsername" ServerIOTimeout="0" WaitForContinue="true">
<Transport Hostname="hostname.domain.COM" Port="9080" Protocol="http"/>
<Transport Hostname="hostname.domain.COM" Port="10014" Protocol="https">
<Property Name="keyring" Value="/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/Appsername/etc/plugin-key.kdb"/>
<Property Name="stashfile" Value="/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/Appsername/etc/plugin-key.sth"/>
</Transport>
</Server>
</ServerCluster>
<UriGroup Name=" default_host_Appsername_hostname_Appsern
ame_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/paymentchart/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/onlinepaymentchart/*"/>
I am running paymentchart and onlinepaymentchart applications and used same as context root.
In our case we are using 10014 port for SSL.
Can you please look into Transport, Virtualhost and Uri AffinityCokkie settings and see you application is mapped with associated port and url.
I hope this will help you.
vaze
|
|
|
|
|