Iisforward and iisproxy

Does anyone know how I can forward to two different WLS? I have a website with two virtual directories for two applications. one is /fw and the other /tw but in the .ini file there is only one weblogichost entry and no way to distinguish that /fw needs to go to WLS1 and /tw goes to WLS2Please help.

Scott,
If you are using the iisforward.dll, you can only have 1 instance of that dll
per website (on an IIS server a website is a unique combination of port, ip, and
host header). I had a similar issue and I just created two server instances on
separate ports (though separate hosts names might look neater), each forwarding
to different WL servers. For example. IIS address http://iisserver:7777/ forwarded
to http://wlserver_1:7001 and http://iisserver:7778/ forwarded to http://wlserver_2:7001.
Each IIS website had it's own copy of iisforward.dll, iisproxy.dll and iisproxy.ini.
If you must keep your virtual directories you could have them forward to the other
iis websites on the same server.
Good luck,
Barrett
Scott <[email protected]> wrote:
Does anyone know how I can forward to two different WLS? I have a website
with two virtual directories for two applications. one is /fw and the
other /tw but in the .ini file there is only one weblogichost entry
and no way to distinguish that /fw needs to go to WLS1 and /tw goes
to WLS2Please help.

Similar Messages

IISForward and IISProxy Configuration Internals/Interaction

Can someone give a detailed description of how IISForward and IISProxy interact
with IIS as ISAPI modules? We have the IIS plugins functioning properly, we would
just like a more detailed explanation on how they interact and work together when
proxying multiple virtual hosts. It seems that many people are in the dark on
this process, and that any clarification would alleviate many of the posts we
see here. I would also settle for a link to some documentation (not BEA's, it
is very poor!) on this.
Here is an excerpt from some documentation that we have written up internally
that helped us keep track of what we were doing when setting up the IIS Plugins.
Some of this content draws from BEA's documentation so we here at Servicemaster
make no claims on this content:
START OF EXCERPT:
6. Configuring IISForward
6.1 Installing iisforward.dll
Before creating the Virtual hosts in IIS, we need to create the directories that
are going to contain the DLL’s. There is going to be a one-to-one relationship
between Virtual Hosts and DLL directories. First create a directory where all
of the DLL directories will reside:
D:\WebLogicVHosts
Within this directory create the directory for each Virtual Host that will be
connecting to the WebLogic instance:
D:\WebLogicVHosts\vhost1-svmhome.com
D:\WebLogicVHosts\vhost2-svmwork.com
D:\WebLogicVHosts\vhost3-svmmemphis.com
Now copy the iisforward.dll from the directory WL_HOME/server/bin into each of
the directories you created for each of the Virtual Hosts.
6.2 Creating iisforward.ini
Create a file called iisforward.ini. Place this file in the same directories for
each of the virtual hosts that contain the iisforward.dll. This file should contain
the following entry for each virtual website defined in IIS:
vhostN=websiteName:port
websiteName:port=dll_directory/iisproxy.ini
Where:
N is an integer representing the virtual website. The first virtual website you
define should use the integer 1 and each subsequent website should increment this
number by 1.
websiteName is the name of the virtual website as registered with IIS.
port is the port number where IIS listens for HTTP requests.
dll_directory is the path to the directory you created in step 1.
For example:
vhost1=svmhome.com:7001
svmhome.com:7001=D:\WebLogicVHosts\vhost1-svmhome.com \iisproxy.ini
vhost2=svmwork.com:7002
svmwork.com:7002= D:\WebLogicVHosts\vhost2-svmhome.com \iisproxy.ini
vhost3=svmmemphis.com:7003
svmmemphis.com:7003= D:\WebLogicVHosts\vhost3-svmmemphis.com \iisproxy.ini
7. Configuring IISProxy
7.1 Installing IISProxy
Now copy the iisproxy.dll from the directory WL_HOME/server/bin into each of the
directories you created for each of the Virtual Hosts.
D:\WebLogicVHosts\vhost1-svmhome.com
D:\WebLogicVHosts\vhost2-svmwork.com
D:\WebLogicVHosts\vhost3-svmmemphis.com
7.2 Creating iisproxy.ini
The iisproxy.ini file contains name=value pairs that define configuration parameters
for the plug-in. Changes in the parameters will not go into effect until you
restart the "IIS Admin Service".
We need to create a iisproxy.ini configuration file for each of the virtual hosts.
Here is a sample iisproxy.ini file for use with a single, non-clustered WebLogic
Server. Comment lines are denoted with the "#" character.
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicHost=examplehost16
WebLogicPort=7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Here is a sample iisproxy.ini file with clustered WebLogic Servers. Comment lines
are denoted with the "#" character.
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicCluster=examplehost07:7001,examplehost08:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
8. Configuring IIS Virtual Hosts
8.1 Proxying by file extension
At this point we are now ready to configure the virtual hosts within IIS. First
create a new virtual website as you would normally do within IIS. Second add
the iisforward.dll file as a filter service in IIS (WebSite Properties —> ISAPI
Filters tab —> Add the iisforward dll). For each virtual host the path to the
iisforward.dll should be unique. The paths should match the ones that you created
previously. Again, there should be a unique path for each virtual website.
Example:
D:\WebLogicVHosts\vhost1-svmhome.com\iisforward.dll
D:\WebLogicVHosts\vhost2-svmwork.com\iisforward.dll
D:\WebLogicVHosts\vhost3-svmmemphis.com\iisforward.dll
On the App Mappings tab, click the Add button to add file types and configure
them to be proxied to WebLogic Server. In the dialog box, browse to find the
"iisproxy.dll" file that matches the path to the unique iisproxy.dll file for
the virtual host.
Example:
D:\WebLogicVHosts\vhost1-svmhome.com\iisproxy.dll
D:\WebLogicVHosts\vhost2-svmwork.com\iisproxy.dll
D:\WebLogicVHosts\vhost3-svmmemphis.com\iisproxy.dll
Set the Extension to the type of file that you want to proxy to WebLogic Server.
Register .wlforward as a special file type to be handled by iisproxy.dll. Deselect
the "Check that file exists" check box. Set the Method exclusions as needed
to create a secure installation.
When you finish, click the OK button to save the configuration. You can repeat
this process for each file type you want to proxy to WebLogic. When you finish
configuring file types, click the OK button to close the Properties panel.
In the URL, any path information you add after the server and port is passed directly
to WebLogic Server. For example, if you request a file from IIS with the URL:
Example:
http://svmhome.com/jspfiles/myfile.jsp
it is proxied to WebLogic Server with a URL such as
http://examplehost07:7001/jspfiles/myfile.jsp
8.2 Proxying by path
Now, within the iisproxy.dll file for each virtual host, define the property WlForwardPath
in iisproxy.ini. WlForwardPath defines the path that is proxied to WebLogic
Server.
Example:
WlForwardPath=/apps
Set the PathTrim parameter to trim off the WlForwardPath when necessary.
Example:
WlForwardPath=/apps
PathTrim=/apps
The previous trims a request from IIS to Weblogic Server. Therefore, /apps/exampleapp
is changed to /exampleapp.
If you want requests that do not contain extra path information (in other words,
requests containing only a host name), set the DefaultFileName parameter to the
name of the welcome page of the Web Application to which the request is being
proxied. The value of this parameter is appended to the URL.
If you need to debug your application, set the Debug=ON parameter in iisproxy.ini.
A c:\tmp\iisforward.log is generated containing a log of the plug-in's activity
that you can use for debugging purposes.
For each virtual host that you configure to be proxied to WebLogic, set the value
for the Application Protection option to high (isolated) as opposed to Low or
Medium. This allows separate iisforward and iisproxy DLL’s to be loaded into
each virtual hosts (dllhost.exe) memory address space.
END OF EXCERPT
Can someone at BEA verify this information or possible add to it?
Tony

Nice write-up.
Though, I may have found an easier way to use VirtualHost and/or Virtual
Directories with IIS without the need to use the iisforward.dll.
A lot of customers are asking about using multiple WlForwardPath to proxy to
different WebLogic instances. It is possible to use Virtual Directories to
do this.
All that you need to do is set the Application Protection to HIGH for each
Virtual Directory
and then each directory can use it's own iisproxy.dll/iisproxy.ini. Fairly
straight forward and it seems to
work.
As well, you can do Virtual Websites with each one having the application
protection set to HIGH as well. And of course they will each use their own
iisproxy.dll/iisproxy.ini. These virtual Websites can also all listen on
the
same IP/Port and if you want to proxy based on Host header, you can click on
the advanced tab and set the Host header for which this virtual website will
use.
So, all that really needs to be done is when you create the virtual
directory, make sure the
application protection is set to HIGH and change the App Mapping to point to
the new iisproxy.dll/iisproxy.ini.
If you want to proxy everything under that path, then Add another App
Mapping
that has an extension of *.
I do believe this will allow us to completely bypass the need of the
iisforward.
I have tested this with IIS5. With IIS4 it is not possible to register an
App Mapping of *(not sure why).
I hope this helps many of you.
Best regards,
Eric
"Tony Mendoza" <[email protected]> wrote in message
news:[email protected]...
>
Can someone give a detailed description of how IISForward and IISProxyinteract
with IIS as ISAPI modules? We have the IIS plugins functioning properly,we would
just like a more detailed explanation on how they interact and worktogether when
proxying multiple virtual hosts. It seems that many people are in thedark on
this process, and that any clarification would alleviate many of the postswe
see here. I would also settle for a link to some documentation (notBEA's, it
is very poor!) on this.
Here is an excerpt from some documentation that we have written upinternally
that helped us keep track of what we were doing when setting up the IISPlugins.
Some of this content draws from BEA's documentation so we here atServicemaster
make no claims on this content:
START OF EXCERPT:
6. Configuring IISForward
6.1 Installing iisforward.dll
Before creating the Virtual hosts in IIS, we need to create thedirectories that
are going to contain the DLL's. There is going to be a one-to-onerelationship
between Virtual Hosts and DLL directories. First create a directory whereall
of the DLL directories will reside:
D:\WebLogicVHosts
Within this directory create the directory for each Virtual Host that willbe
connecting to the WebLogic instance:
D:\WebLogicVHosts\vhost1-svmhome.com
D:\WebLogicVHosts\vhost2-svmwork.com
D:\WebLogicVHosts\vhost3-svmmemphis.com
Now copy the iisforward.dll from the directory WL_HOME/server/bin intoeach of
the directories you created for each of the Virtual Hosts.
6.2 Creating iisforward.ini
Create a file called iisforward.ini. Place this file in the samedirectories for
each of the virtual hosts that contain the iisforward.dll. This fileshould contain
the following entry for each virtual website defined in IIS:
vhostN=websiteName:port
websiteName:port=dll_directory/iisproxy.ini
Where:
N is an integer representing the virtual website. The first virtualwebsite you
define should use the integer 1 and each subsequent website shouldincrement this
number by 1.
websiteName is the name of the virtual website as registered with IIS.
port is the port number where IIS listens for HTTP requests.
dll_directory is the path to the directory you created in step 1.
For example:
vhost1=svmhome.com:7001
svmhome.com:7001=D:\WebLogicVHosts\vhost1-svmhome.com \iisproxy.ini
vhost2=svmwork.com:7002
svmwork.com:7002= D:\WebLogicVHosts\vhost2-svmhome.com \iisproxy.ini
vhost3=svmmemphis.com:7003
svmmemphis.com:7003= D:\WebLogicVHosts\vhost3-svmmemphis.com \iisproxy.ini
7. Configuring IISProxy
7.1 Installing IISProxy
Now copy the iisproxy.dll from the directory WL_HOME/server/bin into eachof the
directories you created for each of the Virtual Hosts.
D:\WebLogicVHosts\vhost1-svmhome.com
D:\WebLogicVHosts\vhost2-svmwork.com
D:\WebLogicVHosts\vhost3-svmmemphis.com
7.2 Creating iisproxy.ini
The iisproxy.ini file contains name=value pairs that define configurationparameters
for the plug-in. Changes in the parameters will not go into effect untilyou
restart the "IIS Admin Service".
We need to create a iisproxy.ini configuration file for each of thevirtual hosts.
Here is a sample iisproxy.ini file for use with a single, non-clusteredWebLogic
Server. Comment lines are denoted with the "#" character.
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicHost=examplehost16
WebLogicPort=7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Here is a sample iisproxy.ini file with clustered WebLogic Servers.Comment lines
are denoted with the "#" character.
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicCluster=examplehost07:7001,examplehost08:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
8. Configuring IIS Virtual Hosts
8.1 Proxying by file extension
At this point we are now ready to configure the virtual hosts within IIS.First
create a new virtual website as you would normally do within IIS. Secondadd
the iisforward.dll file as a filter service in IIS (WebSite Properties ->ISAPI
Filters tab -> Add the iisforward dll). For each virtual host the pathto the
iisforward.dll should be unique. The paths should match the ones that youcreated
previously. Again, there should be a unique path for each virtualwebsite.
>
Example:
D:\WebLogicVHosts\vhost1-svmhome.com\iisforward.dll
D:\WebLogicVHosts\vhost2-svmwork.com\iisforward.dll
D:\WebLogicVHosts\vhost3-svmmemphis.com\iisforward.dll
On the App Mappings tab, click the Add button to add file types andconfigure
them to be proxied to WebLogic Server. In the dialog box, browse to findthe
"iisproxy.dll" file that matches the path to the unique iisproxy.dll filefor
the virtual host.
Example:
D:\WebLogicVHosts\vhost1-svmhome.com\iisproxy.dll
D:\WebLogicVHosts\vhost2-svmwork.com\iisproxy.dll
D:\WebLogicVHosts\vhost3-svmmemphis.com\iisproxy.dll
Set the Extension to the type of file that you want to proxy to WebLogicServer.
Register .wlforward as a special file type to be handled byiisproxy.dll. Deselect
the "Check that file exists" check box. Set the Method exclusions asneeded
to create a secure installation.
When you finish, click the OK button to save the configuration. You canrepeat
this process for each file type you want to proxy to WebLogic. When youfinish
configuring file types, click the OK button to close the Properties panel.
In the URL, any path information you add after the server and port ispassed directly
to WebLogic Server. For example, if you request a file from IIS with theURL:
>
Example:
http://svmhome.com/jspfiles/myfile.jsp
it is proxied to WebLogic Server with a URL such as
http://examplehost07:7001/jspfiles/myfile.jsp
8.2 Proxying by path
Now, within the iisproxy.dll file for each virtual host, define theproperty WlForwardPath
in iisproxy.ini. WlForwardPath defines the path that is proxied toWebLogic
Server.
Example:
WlForwardPath=/apps
Set the PathTrim parameter to trim off the WlForwardPath when necessary.
Example:
WlForwardPath=/apps
PathTrim=/apps
The previous trims a request from IIS to Weblogic Server. Therefore,/apps/exampleapp
is changed to /exampleapp.
If you want requests that do not contain extra path information (in otherwords,
requests containing only a host name), set the DefaultFileName parameterto the
name of the welcome page of the Web Application to which the request isbeing
proxied. The value of this parameter is appended to the URL.
If you need to debug your application, set the Debug=ON parameter iniisproxy.ini.
A c:\tmp\iisforward.log is generated containing a log of the plug-in'sactivity
that you can use for debugging purposes.
For each virtual host that you configure to be proxied to WebLogic, setthe value
for the Application Protection option to high (isolated) as opposed to Lowor
Medium. This allows separate iisforward and iisproxy DLL's to be loadedinto
each virtual hosts (dllhost.exe) memory address space.
END OF EXCERPT
Can someone at BEA verify this information or possible add to it?
Tony

Iisforward and encoded URLs

I cannot seem to get the iisproxy/iisforward combination to properly handle
encoded URL session strings.
I have been performing my tests with WebLogic Sever 5.1.0sp5, IIS 5 and
Windows 2000 (both IE and Netscape). I use the
examples.servlets.SessionServlet included with WebLogic server. It has a
link that tests encoded URL session management. With sp4 and before, the
iisproxy handled this well, so long as I included the arbitrary extension.
The forwarding works to hit the servlet the first time, but subsequent
times present me with a 404, as if the proxy decided it shouldn't forward
the request and IIS is searching its files. IIS logs confirm this.
Anyone been able to get encodeURL() calls to work through the proxy?
Jesse

Either no one uses encodedURLs or no one bothered trying this. However, I
found this behavior in both IIS 4 and IIS 5 and filed a bug report. A
change request has been made and can be tracked via ID 189897.
Jesse

ISA and iisproxy

How can I properly configure ISA to proxy requests to our WLS 6.1 install?
It seems I should be able to do this simply with destination sets, etc.
Any clues?

Hi,
The problem is because of the keepalive timeout differences between IIS and the J2EE server (HTTP provider)
read this notes :
1.820028
2.713568 symptom 18
3 also read this /thread/56476 [original link is broken]

SSL and IISProxy

We are using IIS in a DMZ and proxy servlet requests to WLS inside a
firewall. The clients will connect using a SSL session to IIS, passing a
client certificate. How do we get access to the certificate in order to
parse it and identify the client on WLS? Should WLS be set up with SSL as
well? Is the certificate proxied as well?
What is the best way to configure this scenario?
Thanks,
Ernst.

e> How do we get access to the certificate in order to parse it and
e> identify the client on WLS?
Our servlet documentation should explain how to do this.
<b

IISProxy can't handle concurrent requests

Hi
Im working with a cluster of 2 WLS5.1/SP8
One IIS5 Running on Windows2000.
I configured successfully iisforward and iisproxy and everything works fine
as long as few users work with the system.
however when trying to send a concurrent request from 20 users some of them
up to 10 gets a 403 as response.
I can see it in the IIS access log file as well.
I turned debug=ON in the iisproxy.ini and i see that only the number of
users that do get a 200 response are realy being sent to one of the WLS
pair, those that return 403 seems not to even try to connect to a WLS.
It seems like a weblogic bug.
Help will be appreciated
Dror.

It seems that the problem is IIS on Win2000 Workstation has a 10 connection
hardcoded limit
"Dror Last" <[email protected]> wrote in message
news:[email protected]..
Hi
Im working with a cluster of 2 WLS5.1/SP8
One IIS5 Running on Windows2000.
I configured successfully iisforward and iisproxy and everything worksfine
as long as few users work with the system.
however when trying to send a concurrent request from 20 users some ofthem
up to 10 gets a 403 as response.
I can see it in the IIS access log file as well.
I turned debug=ON in the iisproxy.ini and i see that only the number of
users that do get a 200 response are realy being sent to one of the WLS
pair, those that return 403 seems not to even try to connect to a WLS.
It seems like a weblogic bug.
Help will be appreciated
Dror.

Weblogic 10.3 and IIS7

I'm having trouble locating documentation on how to have IIS7 proxy and funnel all traffic to the weblogic instance (iisforward and iisproxy). Can someone point me to the documentation or give appropriate steps related to IIS7?
Thanks,
Jon

Hi, it helps some but it's still written for IIS6. For example, step 3 suggests i add a mime type and enter all extensions i want to proxy. Do they mean Mime Types within IIS7 or Handler mappings (and which kind of handler? managed, script, wildcard, module).

Changing server directories

Our installation (converting from Jrun) is on top of IIS4 (NT).
The default WL directory for serving JSP's is C:\bea\wlserver6.1\config\mydomain\applications\DefaultWebApp
We want to change it to point to a different directory (which is also an IIS virtual directory) such as G:\sch\eer\www
All of this is on the same machine, for development purposes.
What is the best way to accomplish this?
I've been trying to use iisforward and iisproxy without success.
Thanks
Stan

Hi.
I don't think this is possible - WLS 6.x has rather rigid file directory requirements. I believe this is being improved
upon in the next release of WLS, FWIW.
Regards,
Michael
Stan wrote:
Our installation (converting from Jrun) is on top of IIS4 (NT).
The default WL directory for serving JSP's is C:\bea\wlserver6.1\config\mydomain\applications\DefaultWebApp
We want to change it to point to a different directory (which is also an IIS virtual directory) such as G:\sch\eer\www
All of this is on the same machine, for development purposes.
What is the best way to accomplish this?
I've been trying to use iisforward and iisproxy without success.
Thanks
Stan--
Developer Relations Engineer
BEA Support

Weblogic 8.0 and IIS 5.0 plug in issue

hi,
I have a computer with Windows 2000 server and IIS 5.0 installed.
I am trying to open a connection with a Weblogic Server 8 SP3 on another machine.
My iisproxy.dll and iisproxy.ini
are on the folder: C:\WINNT\system32\inetsrv
iisproxy.ini :
WlForwardPath=/IhmActivation
Debug=ALL
WebLogicHost=toto
WebLogicPort=49162
WLLogFile=C:\iisproxy3.log
I have configured iisproxy.dll in IIS 5.0
Based on what I entered in my configuration file iisproxy.ini, if I type the URL:
http://localhost/IhmActivation/here.do
it should point to
http://toto:49162/IhmActivation/here.do
I get a 401 message:
Going to send headers to the client. Status :401 Unauthorized xxx
The login and password are ok.
So I do not know where the problem comes from.
Does anyone have an idea please ?
Thanks for your help.

Since you are attempting to proxy by path you need to configure the iisforward.dll as stated in step #3 here:
http://e-docs.bea.com/wls/docs81/plugins/isapi.html#100382

Another IISPROXY question (multiple SAP systems)

Hi!
We've got a challenge. We have SAP EP (6.0 SP12), visible from outside
(via MS ISA server publishing). Also we have several SAP systems (BW,
ERP2004, Solution Manager), that we want to make available from web.
We installed IIS proxy module on portal server machine. It's working.
I even maneged to publish some test reports and WebGUI of BW server.
But when I try to publish in a simmilar way other system, I fall into
problem.
When you call '/sap/bw/' for example, SAP system after authentication
converts it to something like '/sap(lsdkSDF435ssdgf)/bw'. As far as I
understand between "(" and ")" there is some hash of password or something.
The problem is, that it's true and the same for all SAP systems.
So if I put in iisproxy.xml following strings:
<mapping name="bw">
<source>
 <protocol>http</protocol>
 <prefix>/sap/bw/</prefix>
</source>
<source>
 <protocol>http</protocol>
 <prefix>/sap/bw</prefix>
</source>
<source>
 <protocol>http</protocol>
 <prefix>/sap/public/bc/its/mimes/</prefix>
</source>
<source>
 <protocol>http</protocol>
 <prefix>/sap(</prefix>
</source>
<target>
 <protocol>http</protocol>
 <host>bw-server.ourdomain.local</host>
 <port>8000</port>
</target>
<compress-types>text/html, text/plain</compress-types>
</mapping>
it's working for BW server. We able to see reports and webGUI.
If I try to add following strings for ERP2004 server:
<mapping name="erp">
 <source>
 <protocol>http</protocol>
 <prefix>/erp/sap/bc/gui/sap/</prefix>
 <new-prefix>/sap/bc/gui/sap/</new-prefix>
 </source>
 <source>
 <protocol>http</protocol>
 <prefix>/erp/sap/bc/gui/sap</prefix>
 <new-prefix>/sap/bc/gui/sap</new-prefix>
 </source>
 <source>
 <protocol>http</protocol>
 <prefix>/erp/sap/bw/BEx</prefix>
 <new-prefix>/sap/bw/BEx</new-prefix>
 </source>
 <source>
 <protocol>http</protocol>
 <prefix>/erp/sap/bw/BEx/</prefix>
 <new-prefix>/sap/bw/BEx/</new-prefix>
 </source>
 <source>
 <protocol>http</protocol>
 <prefix>/erp/sap/public/bc/its/mimes/</prefix>
 <new-prefix>/sap/public/bc/its/mimes/</new-prefix>
 </source>
 <source>
 <protocol>http</protocol>
 <prefix>/erp/sap/public/bc/ur/Design2002/</prefix>
 <new-prefix>/sap/public/bc/ur/Design2002/</new-prefix>
 </source>
 <source>
 <protocol>http</protocol>
 <prefix>/erp/sap/bc/public/systemlogin/</prefix>
 <new-prefix>/sap/bc/public/systemlogin/</new-prefix>
 </source>
 <source>
 <protocol>http</protocol>
 <prefix>/sap(</prefix>
 </source>
 <target>
 <protocol>http</protocol>
 <host>erp2004-server.ourdomain.local</host>
 <port>8000</port>
 </target>
<compress-types>text/html, text/plain</compress-types>
</mapping>
and try to open webGUI, it redirects to BW server.
A think that's because double '/sap(' prefixes.
How can we avoid that?
Same situation for SolMan.
In portal's 'System Landscape' setup is:
BW system
ITS
 ITS description: CLIxxxSID
 ITS host name: portal-server.ourdomain.ru (this name in accessible from internet, it's a host where portal and IISPROXY are installed)
 ITS path: /sap/bc/gui/sap/its/webgui
ERP2004 system
ITS
 ITS description: CLIxxxSID
 ITS host name: portal-server.ourdomain.ru
 ITS path: /erp/sap/bc/gui/sap/its/ (I added /erp/ trying to distinguish request to ERP2004 server), without it it's also not working)
In intranet (if we do not use IISPROXY) everything is working. Of course with other system definitions in System Landscape.
Do I need to provide more details? Or my question is clear?
Thanks in advance for help and support!
Regards,
DK
P.S. Actually I opened an OSS message on this topic (with "high" priority), but no SAP activities since September, 6th :o(

Hi Jayesh!
Seems it's not working :o( And worst thing, that I do not know why :o(
What i've done.
1) Created an alias '/erp/sap/', that points to '/default_host/sap/bc/gui/sap/its/webgui'.
2) In System Landscape edited system definition (of an ERP2004 system), so that ITS path is now '/erp/sap/' and ITS host 'ourportal.ourdomain.ru'.
3) Created an 'SAP transaction iView' that should launch SU01 transaction in ERP2004 system.
Now when I try to open it from page, portal tries to connect me to our BW server.
Seems that alias are working in some other way :o(
Here's what I can see in IISPROXY log:
11:57:29 Filter J2EE --> GET /erp/sap/
11:57:29 7616 Proxy GET http://erp2004.ourdomain.ru:8000/erp/sap/
11:57:29 7616 Proxy HTTP/1.1 200 OK | queued for 0.000 sec, processed in 0.078 sec.
11:57:29 7616 Proxy | GET http://erp2004.ourdomain.ru:8000/erp/sap/ | HTTP/1.1 200 OK | 0.000 | 0.078
11:59:41 Filter J2EE --> GET /sap(dslkknvDSAFSADVFDSVaslkdv)/bc/gui/sap/its/webgui?okcode=/nSU01&DisconnectOnClose=0&sap-client=200&sap-language=en&sap-accessibility=
11:59:41 6952 Proxy GET http://bw.ourdomain.local:8000/sap(dslkknvDSAFSADVFDSVaslkdv)/bc/gui/sap/its/webgui
So it's still tries to open '/sap(dslkknvDSAFSADVFDSVaslkdv)/bc/gui/sap/its/webgui' instead of /erp/sap(
dslkknvDSAFSADVFDSVaslkdv)/
Thanks for help and support!
Regards,
DK

Basic Authentication with IISProxy?

hi,
is the IISProxy the appropriate tool for tunneling http-requests to http-servers behind a firewall (reverse proxy)?
i made it work with ep60. but accessing other http-servers with own mappings (for example /tomcat/ directs to a tomcat server) fails.
problems I'm facing:
1. basic authentication is not transmitted to the http-server (e.g. tomcat). the logon-box pops up, but the data doesn't seem to be transmitted through IIsProxy.
2. URLs created from other servers don't know that the IISProxy requires a special filter-string (again /tomcat/) when they create absolute links.
are there other / better reverse proxys (apache?) that can handle these things?
kr, achim
ps: what about the filter-element attributes authentication="normal" remote-address="skip"?
i haven't found any documentation about them, but they look like to be configured...
Message was edited by: Achim Hauck

After checking some more I was wrong (I got it confused with a Sap logon ticket plugin)
But in note 480520 it is described how to setup reverse proxy with apache. There is an attached document to the note which explains it.
Text of the note:
Symptom
How to integrate SAP J2EE Engine 6.20 with Apache Webserver
Reason and Prerequisites
SAP J2EE Engine 6.20 can be integrated with Apache Web Server,no plugin is needed. The same is valid for SAPJ2EE 610 or In-Q-My 427.
Solution
General Information on how to use the Apache Webserver in combination with the SAP J2EE Web Application Server :
1. You are permitted to use the Apache Webserver together with the SAP J2EE Web Application Server. In this way SAP guarantees continued support for the SAP Application.
2. Due to the high number of possible configurations and versions available, SAP can only provide some examples of possible configurations. These normally suffice to use the SAP Application.
3. You might need to contact consultants specialized in this area for error analysis and further configurations.
This consultation is not provided by SAP Support.SAP J2EE Engine (and its predecessor In-Q-My Application Server) can be integrated with Apache web server, no plugin is needed.
Please review the attached Configuration Guide in order to get some configuration examples using Reverse Proxy and/or URL Rewriting.
Btw, the major benefit of using IIS and IISproxy is that Integrated windows authentication is possible (SSO from OS)
Great idea to make a blog out of this.

Iisproxy does not load

Hello,
I am using ITS 6 with iisproxy 16_2 . I have done configuration but iisproxy is not loading under the default web site isapi filter tab. iiproxy.dll and iisproxy.xml are in inetpub/scripts and mscvr71.dll has been copied into windows/system32. A log file is not being written.
Can anyone help.
Thanks
Mr.T

Hello Tahir,
have you done the Steps I've described in my Weblog <a href="https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/920">Integrated Windows Authentication with SAP EP 6.0 SP 3 and higher Part 1 of 2</a>?
Regards
Gregor

Urgent: intalling Iisproxy module

Dear all
i downloded copied the file into c:\inetpub\scripts(like Iisproxy.dll, Iisproxy.pdb and IisProxy.xml)
in the ISAPI Filters tab..i added name "Iisproxy" and assigned the path i.e, c:\inetpub\scripts
Created a virtual directory called "scripts" assigned the path like c:\inetpub\scripts. assign the permissions Read and run scripts...etc
opend the Properties of "Scripts" -> virtual directory tab...
already application has come by default called "scripts" and choosed the "configaration"
i clicked on ADD button...it shows me all checkboxes and text areas like Executable..
extension
verbs
script engine..
but the "OK" is disabled...can anybody please tell me y it is disabled...
I'm using IIS 5.1 ....IisProxy module 6.1
pl help me
regards
PRadeep

Hi Ignacio
Still i was unable to solve this problem.
I'm explainig u what are the steps i have done.
Steps:
Downloded IisProxy 1.6.1 from SAP. unziped using sapcar...there i got 6 files.
namely IisProxy.dll,IisProxy.pdb,IisProxy.xml...
1. copied into c:\Inetpub\Scripts
2.Under "Default Website" properties..ISAPI filter tab..i added IisProxy.dll.
Note: it says unknown.
3.In the Properties of the Default website scripts...i created Virtual directory called "Scripts".. Application name = scripts and choosed Configuration..and i pointed to the IisProxy.dll which is Executable file.
extension = *
Verbs = all
Script engine = yes
4.I modifyed IisProxy.xml file in C:\inetpub\Scripts\IisProxy.xml
Note: Mapping name=" This is unique" or should i change
<ISAPI-config version="1.6">
<filter name="IisProxy filter" authentication="forward" />
<extension name="IisProxy extension" />
<mapping name="IisProxy samples" log-level="0">
<source>
<protocol>http</protocol>
<prefix>/irj/</prefix>
</source>
<source>
<protocol>http</protocol>
<prefix>/irj</prefix>
<new-prefix>/irj/</new-prefix>
</source>
<source>
<protocol>http</protocol>
<prefix>/abc15.uk.us1508.Company.com/</prefix>
<new-prefix>/irj/</new-prefix>
</source>
<source>
<protocol>http</protocol>
<prefix>/logon/</prefix>
</source>
<target>
<protocol>http</protocol>
<host>localhost</host>
<port>50000</port>
</target>
<compress-types>text/html, text/plain</compress-types>
</mapping>
<config>
<source>
<protocol>http</protocol>
<host>localhost</host>
<prefix>/IisProxy</prefix>
</source>
<source>
<protocol>https</protocol>
<host>localhost</host>
<prefix>/IisProxy</prefix>
</source>
</config>
</ISAPI-config>
5. Copied the MSCVCR71.dll into C:\Windows\System32
6. Restarted IIS
Testing IisProxy module:
7. Created Virtual directoy called "irj" in default website..and i pointed to C:\Inetpub\Scripts (Please note this..this is wrong or right)
SAP documentation says select the location in the file system that contains ur content..C:\Inetpub\Website(example)..or do i need to create a folder in inetpub called website.
Testing..
http://localhost:80/irj
nothing is displaying...
when i see in logfile.. it says unable to load XML file.
Im using..IIS 5.0 ..IisProxy module 1.6.1 windows XP professional
Pl help me in this..
regards
Pradeep
Message was edited by: Pradeep Reddy

Need help to setup iis with iisproxy.dll

I have create an iisproxy.xml and i have this error in the iisproxy.dll when a try to access to the virtual directory of the portal :
18:39:44 Global E-Init IisProxy Extension 1.6.2.0 initializing.
18:39:48 Global Init E LoadFromFile(
?\D:\Inetpub\Scripts\IisProxy.xml ): XML Error 0x80070035 at line 0, char 0:
in "(null)"
The network path was not found.
18:39:48 Global E-Init E Failed to load config file '
?\D:\Inetpub\Scripts\IisProxy.xml'.
I have 2 directory in d:\inetpub :
-Scripts with iisproxy.dll iisproxy.xml and iisproxy.pdb
-IisProxy which is the virual folder for accessing to the portal.
On Script i have check this :
Read
Execution permission : Execute
Application pool : DefaultAppPool
On IisProxy i have the same configuration except that
the wildcard application map point to iisproxy.dll
The iisproxy.xml look like this :
<?xml version="1.0" encoding="utf-8" ?>
<ISAPI-config version="1.6">
<filter name="IisProxy filter" log-level="3" log-flags="0" debug-flags="0" priority="high" extension-url="/Scripts/IisProxy.dll" authentication="normal" remote-address="skip" />
<extension name="IisProxy extension" log-level="3" log-flags="0" debug-flags="0" access="filter" />
<mapping name="IisProxy samples" log-level="3" log-flags="0" debug-flags="0" keep-alive="true" use-continue="true" close-socket="true" close-socket-delay="1000" thread-count="100" max-socket-age="37">
<mapping name="ep60sp2">
<source>
<protocol>http</protocol>
<prefix>/irj</prefix>
</source>
<source>
<protocol>http</protocol>
<prefix>/logon</prefix>
</source>
<target>
<protocol>http</protocol>
<host>localhost</host>
<port>50000</port>
</target>
</mapping>
<compress-types min-size="1024">text/html, text/plain</compress-types>
</mapping>
<config>
<source access="filter">
<protocol>http</protocol>
<host>localhost</host>
<prefix>/IisProxy</prefix>
</source>
</config>
</ISAPI-config>
Using :
Windows 2003
MSXML 3 SP4
IIS 6
EP6SP11
Regards, L.Mouillart

I implemented SSO succesfully with EP 6 SP9 using Windows integrated authentication. Used IISProcy 1.5.0.
It is two step prcoes.
1) Configure ISAPI filter for IRJ
2) Configure WebAS for Logon Module Stack. Create new module called HeaderVariableLoginModule.
Complete following steps.
1) Make sure you have IIS installed. Take a backup before the changes
2) Installl ISAPI filter called IRJ.
3) COpy IISPrxy files into the directory under Inetpub.
4) Map ISAPI filter IRJ to the IISProcy ditrectory.
5) Restart website to test ISAPI filter.
6) Please make sure to add logging for IISProcy filter. This gives very good info.
7) You can check the IisProxy.log file in the directory where you copied the IISProxy files.
8) CHeck and make sure REMOTE_USER is populated in the IisProxy.log file.
Configuration of WebAS server:
1) Create new login module called HeaderVariableLoginModule
2) Add this to the stack called ticket.
3) Change BasicPasswordLoginModule to optional.
Please use following URL for more details.
http://help.sap.com/saphelp_nw04/helpdata/en/d0/a3d940c2653126e10000000a1550b0/frameset.htm
This should fix all your problems. Let me know how it went.
Give me the points.
<?xml version="1.0" encoding="utf-8" ?><!DOCTYPE ISAPI-config[ <!ELEMENT ISAPI-config ( filter, extension, ( mapping | config )* )> <!ATTLIST ISAPI-config version CDATA #REQUIRED > <!ELEMENT filter (log-path?)> <!ATTLIST filter name CDATA #IMPLIED log-level CDATA "3" log-flags CDATA "0" debug-flags CDATA "0" priority ( high | medium | low ) "high" extension-url CDATA "/scripts/IisProxy.dll" authentication ( skip | normal | forward ) "normal" remote-address ( skip | forward ) "skip" > <!ELEMENT extension ( keystore-dir?, log-path?, data-path?, trace-path? )> <!ATTLIST extension name CDATA #IMPLIED log-level CDATA "1" log-flags CDATA "0" debug-flags CDATA "0" access ( filter | direct | both ) "filter" > <!ELEMENT keystore-dir (#PCDATA)> <!ELEMENT log-path (#PCDATA)> <!ELEMENT data-path (#PCDATA)> <!ELEMENT trace-path (#PCDATA)> <!ELEMENT mapping ( source+, target, compress-types*, protocol-header?, certificate-header?, cert-chain-header?, cipher-header?, keysize-header?, keystore-path?, log-path?, data-path? )> <!ATTLIST mapping name CDATA #IMPLIED log-level CDATA "1" log-flags CDATA "0" debug-flags CDATA "0" keep-alive ( true | false ) "true" use-continue ( true | false ) "true" close-socket ( true | false ) "true" close-socket-delay CDATA "1000" thread-count CDATA "100" max-socket-age CDATA "37" > <!ELEMENT source (protocol, host?, port?, prefix, new-prefix?)> <!ATTLIST source access ( filter | direct | both ) "filter" > <!ELEMENT protocol (#PCDATA)> <!ELEMENT host (#PCDATA)> <!ELEMENT port (#PCDATA)> <!ELEMENT prefix (#PCDATA)> <!ELEMENT new-prefix (#PCDATA)> <!ELEMENT target (protocol, host, port)> <!ELEMENT compress-types (#PCDATA)> <!ATTLIST compress-types min-size CDATA "1024" > <!ELEMENT protocol-header (#PCDATA)> <!ELEMENT certificate-header (#PCDATA)> <!ELEMENT cert-chain-header (#PCDATA)> <!ELEMENT cipher-header (#PCDATA)> <!ELEMENT keysize-header (#PCDATA)> <!ELEMENT keystore-path (#PCDATA)> <!ELEMENT config ( source+ )>]><ISAPI-config version="1.6"> <filter name="IisProxy filter" log-level="3" authentication="forward" /> <extension name="IisProxy extension" /> <mapping name="IisProxy" log-level="3" debug-flags="-1"> <source> <protocol>http</protocol> <prefix>/irj/</prefix> </source> <source> <protocol>http</protocol> <prefix>/logon/</prefix> </source> <target> <protocol>http</protocol> <host>slcserver.pacificorp.us</host> <port>50000</port> </target> <compress-types>text/html, text/plain</compress-types> </mapping> <config> <source> <protocol>http</protocol> <host>localhost</host> <prefix>/IisProxy/</prefix> </source> <source> <protocol>https</protocol> <host>localhost</host> <prefix>/IisProxy/</prefix> </source> </config></ISAPI-config>

IISPROXY needs WebLogic locally?

Is it possible to run WebLogic to serve JSPs/servlets on a separate box
behind
the IIS box and still have iisproxy work? I.e. would copying IISPROXY.dll
and
IISPROXY.ini to the IIS box without installing the whole WebLogic on the IIS
box sufficient for the proxy to work?
Thanks,
Ben.

Yes..
Just give it a shot and let us know if you encounter any problems.
--kumar allamraju
Benjamin Lin wrote:
Is it possible to run WebLogic to serve JSPs/servlets on a separate box
behind
the IIS box and still have iisproxy work? I.e. would copying IISPROXY.dll
and
IISPROXY.ini to the IIS box without installing the whole WebLogic on the IIS
box sufficient for the proxy to work?
Thanks,
Ben.

Iisforward and iisproxy

Similar Messages

Maybe you are looking for