IISProxy Idempotent question

We are using the WL IIS 5.1 Plugin and have set Idempotent=off HungServerRecoverSecs=60,
ConnectTimeoutSecs=8 and ConnectRetrrySecs=2 in the IISProxy.ini file.
My understanding is that if a servlet response is not recieved within 60 secs
as in our case, the request will timeout and not failover to the other server
in the cluster. However, does the IIS plugin keep trying to execute the same request
on the same server based on the ConnectionRetrySecs property or is the request
aborted after the 60 sec timeout?
Thanks in advance,
Adnan

Similar Messages

Iisproxy header question

We're looking at the HTTP traces of connections through the IISProxy and direct and finding a duplicate date header on proxied requests.
Has anyone else noticed this? The problem we are trying to solve is intermittent failures at a client company that uses a transparent proxy/filter device. The only difference in the traces is this extra header field.
Here's an example:
HTTP/1.1 200 OK
Date: Tue, 20 Sep 2005 18:30:55 GMT
Date: Tue, 20 Sep 2005 18:30:56 GMT <----------------
X-Powered-By: ASP.NET
Content-Length: 4839
Content-Type: text/html
Expires: Mon, 01 Jan 1990 05:00:00 GMT
Cache-control: private

No, there's not. Emails are 'sent' by the SMTP server, not by the mail client. So, the header originates with the server. The iPhone only sends plain text emails, whereas Outlook usually uses RTF or HTML for newly-composed mails - so, that's a clue. But, it's certainly not definitive.

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

Question about Load balancing with IISPROXY

          Hi,
          We are running WLS 5.1.0 SP5 on NT 4.0 SP6. We are not using clustering.
          We are able to round robin between multiple instances of the WLS successfully.
          Question: If one of the instances of WLS goes down, is there any way to configure
          the plugin to take it out of the loop automatically (without using clustering)?
          Thanks,
          Anil.


This is not the syntax. Syntax is just this:
          MaxSkips=something.
          eg: MaxSkips=25
          The doc says:
          5:10:1000 for min:default:max
          By which we mean that default value is 10, max is 1000 and min is 5. I guess the
          docs are confusing about the syntax here. We will correct them.
          --Vinod.
          Anil Kommareddi wrote:
          > Vinod,
          > I could not find any documentation on the MaxSkips parameter except in the Service Pack
          > docs. The syntax is MaxSkips=min:default:max.
          >
          > how do the min and max parameters work?
          >
          > Vinod Mehra wrote:
          >
          > > Even if the servers in the WebLogicCluster list are non clustered you WILL be
          > > able to do load balancing. But the problem is if the servers go down the plugin
          > > will not remove them. But it not that bad. If an connection attempt fails the
          > > server is marked as bad and will be skipped for the next MaxSkips (default=10)
          > > cycles of load balancing. MaxSkips parameter is configurable for IISProxy
          > > (SP4 onwards, I think).
          > >
          > > -Vinod.
          > >
          > > Prasad Peddada wrote:
          > >
          > > > I believe there won't be any load balancing unless you use servers in a cluster. As
          > > > an alternative you can use hardware load balancers directly in a situation like this.
          > > >
          > > > Anil Kommareddi wrote:
          > > >
          > > > > Hi,
          > > > >
          > > > > We are running WLS 5.1.0 SP5 on NT 4.0 SP6. We are not using clustering.
          > > > > We are able to round robin between multiple instances of the WLS successfully.
          > > > >
          > > > > Question: If one of the instances of WLS goes down, is there any way to configure
          > > > > the plugin to take it out of the loop automatically (without using clustering)?
          > > > >
          > > > > Thanks,
          > > > > Anil.
          > > >
          > > > --
          > > > Cheers
          > > >
          > > > - Prasad

Setting up a cluster for the first time: newbie questions

Any help appreciated with this situation:
          I'm trying to set up a cluster for the first time and running into
          issues (no big surprise). I'll outline my situation and pose questions
          as they arise. If/when I get things to work I'll post a step-by-step
          summary of what it took to get a simple cluster going.
          Here's what I have:
          machines:
          1 Windows 2000 machines with WL 6.1
          2 RedHat Linux machines with WL 6.1
          All machines are on the same Home LAN, can see each other, etc.
          IP addresses are:
          Windows box: 192.168.1.100
          Linux box 1: 192.168.1.102
          Linux box 2: 192.168.1.103
          servers:
          I've set up the Windows machine as my admin server, and set up
          a managed server on each Linux machine. I created a cluster that consists
          of the 2 Linux machines and deployed the web app and EJB to the cluster.
          The Windows machine is acting as a Proxy using ClusterServlet.
          The web application has been set as the Default Web Application on the
          two Linux machines. All 3 machines are listening on ports 80/443. I also
          set up session memory replication through the console.
          Application:
          I have an application that I package as an EAR file. I'm using it as a
          "reference" application designed to mimic a real world app as much as possible.
          The EAR file contains a web application that uses Struts. It also consists
          of a single Stateless Session Bean. The WAR file and EJB Jar are all
          packaged up into the EAR file. I've been able to run this application just
          fine on a single managed server on all 3 machines.
          The web application works fine, and it can invoke the EJB. I can also
          invoke the EJB from Java stand-alone clients. Struts works great. All is
          well with the world. Now I'm trying to "cluster-ize" this app using
          the environment described above and encountering issues.
          I've read the docs and followed the instructions according to the
          "Weblogic Bible" book. I can bring up all 3 servers and the Linux
          managed servers connect to the cluster just fine. I can also
          see the Struts messages in their logs which normally happens and tells me
          the webapp is initialized properly. The console tells me that the managed
          servers are running. I get no error messages starting up any of the serves.
          Here are the problems I am encountering.
          When I try to access the Web Application (through a browser on the
          Windows machine using http://localhost) I get the following error message:
          <Nov 19, 2002 6:44:33 AM EST> <Error> <HTTP> <HttpServer(1754841,null default ct
          x,admin) found no context for "/". This request does not match the context path
          for any installed web applications and there is no default web application confi
          gured.>
          Also, when I try to invoke the EJB through a stand-alone Java client,
          I get a JNDI lookup error on the EJB's home interface.
          Questions:
          Question1: I noticed when setting up the machines that console lets you
          define a "Machine" or a "Unix Machine". What's the difference? Should I
          define the Linux machines as Unix machines or machines, and what are the
          consequences of either choice?
          Question2:
          I'm not totally clear on how my web.xml should look to set up Struts,
          the ClusterServlet, and a servlet filter I'm using to test Servlet filters.
          Here is what I had before I tried to cluster and which works fine:
          <filter>
          <filter-name>MainFilter</filter-name>
          <filter-class>com.refapp.servlets.MainFilter</filter-class>
          <init-param>
          <param-name>myAttribute</param-name>
          <param-value>Foo</param-value>
          </init-param>
          </filter>
          <filter-mapping>
          <filter-name>MainFilter</filter-name>
          <url-pattern>/*</url-pattern>
          </filter-mapping
          
          <servlet>
          <servlet-name>action</servlet-name>
          <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
          <init-param>
          <param-name>application</param-name>
          <param-value>refappstruts</param-value>
          </init-param>
          <init-param>
          <param-name>config</param-name>
          <param-value>/WEB-INF/struts-config.xml</param-value>
          </init-param>
          <init-param>
          <param-name>debug</param-name>
          <param-value>2</param-value>
          </init-param>
          <init-param>
          <param-name>mapping</param-name>
          <param-value>org.apache.struts.action.RequestActionMapping</param-value>
          </init-param>
          <load-on-startup>2</load-on-startup>
          </servlet>
          <servlet-mapping>
          <servlet-name>action</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          <welcome-file-list>
          <welcome-file>index.do</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>index.html</welcome-file>
          </welcome-file-list>
          (I have set up a "dummy" 0-length file called index.do that triggers
          Struts to go into its ActionServlet when first accessing the web site).
          Here is how I added ClusterServlet to web.xml:
          servlet>
          <servlet-name>ClusterServlet</servlet-name>
          <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
          <load-on-startup>0</load-on-startup>
          <init-param>
          <param-name>defaultServers</param-name>
          <param-value>192.168.1.102:80:443|192.168.1.103:80:443</param-value>
          </init-param>
          <init-param>
          <param-name>DebugConfigInfo</param-name>
          <param-value>ON</param-value>
          </init-param>
          </servlet>
          <servlet-mapping>
          <servlet-name>InitServlet</servlet-name>
          <url-pattern>/servlet/InitServlet</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>action</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>/</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>*.html</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>*.jsp</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          Clearly there is a problem with the Default Web application not being
          seen/mapped properly. Any chances my URL mappings for the filter servlet,
          Struts, and ClusterServlet are stepping on each other?
          With respect to the EJB, here is what my weblogic-ejb-jar looks like:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>Hello</ejb-name>
          <stateless-session-descriptor>
          <pool>
               <max-beans-in-free-pool>100</max-beans-in-free-pool>
          </pool>
          <stateless-clustering>
          <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          <stateless-bean-load-algorithm>
          round-robin
          </stateless-bean-load-algorithm>
          <stateless-bean-methods-are-idempotent>
          true
          </stateless-bean-methods-are-idempotent>
          </stateless-clustering>
          </stateless-session-descriptor>
          <jndi-name>Hello.Home</jndi-name>
          </weblogic-enterprise-bean>
          I run this through ejbc and package everything up into the EAR file.
          However, I get a JNDI lookup failure when I try to access the Bean from
          a standalone Java client running on the Windows machine.
          Here is the jndi.properties file that I am using:
          java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
          java.naming.provider.url=t3://localhost:80
          Any ideas what I'm doing wrong here? I can post config.xml also if needed.
          Thanks in advance!


Let me try to answer :)....
          A1> No need to name diff machines by default weblogic
          considers the servers are physically located in diff boxes.
          The names are used to differtiate the mang servers which are in
          multihomed
          Some things to chk
          1> Did u targeted the ear file Target as cluster.
          2> Can u see on the Admin console that both the man servers
          are participated in the cluster( u can see by clicking the monitoring
          tab on the Cluster node).
          3>Is the URL:PORT for the default web app correct?
          the reason: is I dont see the port# on the link u mentioned
          4> probably ur ejb might not been deployed on the target thats the
          reason u cant access thru java client. If u correct the targets that
          will probably fix it.
          Hope this helps
          Please post the result
          Thanks
          Sudhir
          [email protected] (Chris) wrote in message news:<[email protected]>...
          > Any help appreciated with this situation:
          > I'm trying to set up a cluster for the first time and running into
          > issues (no big surprise). I'll outline my situation and pose questions
          > as they arise. If/when I get things to work I'll post a step-by-step
          > summary of what it took to get a simple cluster going.
          > Here's what I have:
          >
          > machines:
          > 1 Windows 2000 machines with WL 6.1
          > 2 RedHat Linux machines with WL 6.1
          > All machines are on the same Home LAN, can see each other, etc.
          > IP addresses are:
          > Windows box: 192.168.1.100
          > Linux box 1: 192.168.1.102
          > Linux box 2: 192.168.1.103
          >
          > servers:
          > I've set up the Windows machine as my admin server, and set up
          > a managed server on each Linux machine. I created a cluster that consists
          > of the 2 Linux machines and deployed the web app and EJB to the cluster.
          > The Windows machine is acting as a Proxy using ClusterServlet.
          > The web application has been set as the Default Web Application on the
          > two Linux machines. All 3 machines are listening on ports 80/443. I also
          > set up session memory replication through the console.
          >
          > Application:
          > I have an application that I package as an EAR file. I'm using it as a
          > "reference" application designed to mimic a real world app as much as possible.
          > The EAR file contains a web application that uses Struts. It also consists
          > of a single Stateless Session Bean. The WAR file and EJB Jar are all
          > packaged up into the EAR file. I've been able to run this application just
          > fine on a single managed server on all 3 machines.
          > The web application works fine, and it can invoke the EJB. I can also
          > invoke the EJB from Java stand-alone clients. Struts works great. All is
          > well with the world. Now I'm trying to "cluster-ize" this app using
          > the environment described above and encountering issues.
          >
          > I've read the docs and followed the instructions according to the
          > "Weblogic Bible" book. I can bring up all 3 servers and the Linux
          > managed servers connect to the cluster just fine. I can also
          > see the Struts messages in their logs which normally happens and tells me
          > the webapp is initialized properly. The console tells me that the managed
          > servers are running. I get no error messages starting up any of the serves.
          >
          > Here are the problems I am encountering.
          >
          > When I try to access the Web Application (through a browser on the
          > Windows machine using http://localhost) I get the following error message:
          >
          > <Nov 19, 2002 6:44:33 AM EST> <Error> <HTTP> <HttpServer(1754841,null default ct
          > x,admin) found no context for "/". This request does not match the context path
          > for any installed web applications and there is no default web application confi
          > gured.>
          >
          > Also, when I try to invoke the EJB through a stand-alone Java client,
          > I get a JNDI lookup error on the EJB's home interface.
          >
          > Questions:
          > Question1: I noticed when setting up the machines that console lets you
          > define a "Machine" or a "Unix Machine". What's the difference? Should I
          > define the Linux machines as Unix machines or machines, and what are the
          > consequences of either choice?
          >
          > Question2:
          > I'm not totally clear on how my web.xml should look to set up Struts,
          > the ClusterServlet, and a servlet filter I'm using to test Servlet filters.
          > Here is what I had before I tried to cluster and which works fine:
          >
          > <filter>
          > <filter-name>MainFilter</filter-name>
          > <filter-class>com.refapp.servlets.MainFilter</filter-class>
          > <init-param>
          > <param-name>myAttribute</param-name>
          > <param-value>Foo</param-value>
          > </init-param>
          > </filter>
          >
          > <filter-mapping>
          > <filter-name>MainFilter</filter-name>
          > <url-pattern>/*</url-pattern>
          > </filter-mapping
          >
          >
          > 
          > <servlet>
          > <servlet-name>action</servlet-name>
          > <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
          >
          > <init-param>
          > <param-name>application</param-name>
          > <param-value>refappstruts</param-value>
          > </init-param>
          >
          > <init-param>
          > <param-name>config</param-name>
          > <param-value>/WEB-INF/struts-config.xml</param-value>
          > </init-param>
          >
          > <init-param>
          > <param-name>debug</param-name>
          > <param-value>2</param-value>
          > </init-param>
          >
          > <init-param>
          > <param-name>mapping</param-name>
          > <param-value>org.apache.struts.action.RequestActionMapping</param-value>
          > </init-param>
          > <load-on-startup>2</load-on-startup>
          > </servlet>
          >
          > <servlet-mapping>
          > <servlet-name>action</servlet-name>
          > <url-pattern>*.do</url-pattern>
          > </servlet-mapping>
          >
          > <welcome-file-list>
          > <welcome-file>index.do</welcome-file>
          > <welcome-file>index.jsp</welcome-file>
          > <welcome-file>index.html</welcome-file>
          > </welcome-file-list>
          >
          > (I have set up a "dummy" 0-length file called index.do that triggers
          > Struts to go into its ActionServlet when first accessing the web site).
          >
          > Here is how I added ClusterServlet to web.xml:
          >
          > servlet>
          > <servlet-name>ClusterServlet</servlet-name>
          > <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
          > <load-on-startup>0</load-on-startup>
          > <init-param>
          > <param-name>defaultServers</param-name>
          > <param-value>192.168.1.102:80:443|192.168.1.103:80:443</param-value>
          > </init-param>
          > <init-param>
          > <param-name>DebugConfigInfo</param-name>
          > <param-value>ON</param-value>
          > </init-param>
          > </servlet>
          >
          > <servlet-mapping>
          > <servlet-name>InitServlet</servlet-name>
          > <url-pattern>/servlet/InitServlet</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>action</servlet-name>
          > <url-pattern>*.do</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>/</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>*.html</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>*.jsp</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>*.do</url-pattern>
          > </servlet-mapping>
          >
          >
          > Clearly there is a problem with the Default Web application not being
          > seen/mapped properly. Any chances my URL mappings for the filter servlet,
          > Struts, and ClusterServlet are stepping on each other?
          >
          > With respect to the EJB, here is what my weblogic-ejb-jar looks like:
          >
          > <weblogic-ejb-jar>
          > <weblogic-enterprise-bean>
          > <ejb-name>Hello</ejb-name>
          > <stateless-session-descriptor>
          > <pool>
          >      <max-beans-in-free-pool>100</max-beans-in-free-pool>
          > </pool>
          > <stateless-clustering>
          > <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          > <stateless-bean-load-algorithm>
          > round-robin
          > </stateless-bean-load-algorithm>
          > <stateless-bean-methods-are-idempotent>
          > true
          > </stateless-bean-methods-are-idempotent>
          > </stateless-clustering>
          > </stateless-session-descriptor>
          > <jndi-name>Hello.Home</jndi-name>
          > </weblogic-enterprise-bean>
          >
          > I run this through ejbc and package everything up into the EAR file.
          > However, I get a JNDI lookup failure when I try to access the Bean from
          > a standalone Java client running on the Windows machine.
          > Here is the jndi.properties file that I am using:
          >
          > java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
          > java.naming.provider.url=t3://localhost:80
          >
          > Any ideas what I'm doing wrong here? I can post config.xml also if needed.
          >
          > Thanks in advance!

Iisforward iisproxy error

Hi,
I have installed and configured the iisforward/iisproxy plugin with IIS 6.0 + WLS 8.1 SP5.
iisproxy.ini [CONTENT]:
WebLogicHost=10.20.140.34
WebLogicPort=8010
Debug=ON
DebugConfigInfo=ON
WlForwardPath=/portal
I tried to load the page but nothing happens..just an error page from IE.
wlproxy.log [CONTENT]:
Mon May 28 15:22:49 2007 loadFile(): Properties loaded from \\?\C:\bea\weblogic81\server\bin\iisproxy.ini
Mon May 28 15:22:49 2007 init: created a new server node: id='10.20.140.34:8010'
Mon May 28 15:22:49 2007
================New Request: [portal/console.wlforward] =================
Mon May 28 15:22:49 2007 SSL is not being used
Mon May 28 15:22:49 2007 resolveRequest: wlforward: /portal/console
Mon May 28 15:22:49 2007 Mon May 28 15:22:49 2007 timer thread starting
URI is /portal/console, len=15
Mon May 28 15:22:49 2007 Request URI = [portal/console]
Mon May 28 15:22:49 2007 attempt #0 out of a max of 5
Mon May 28 15:22:49 2007 Trying a pooled connection for '10.20.140.34/8010/8010'
Mon May 28 15:22:49 2007 getPooledConn: No more connections in the pool for Host[10.20.140.34] Port[8010] SecurePort[8010]
Mon May 28 15:22:49 2007 general list: trying connect to '10.20.140.34'/8010/8010 at line 1265 for '/portal/console'
Mon May 28 15:22:49 2007 INFO: New NON-SSL URL
Mon May 28 15:22:49 2007 Connect returns -1, and error no set to 10035, msg 'Unknown error'
Mon May 28 15:22:49 2007 EINPROGRESS in connect() - selecting
Mon May 28 15:22:49 2007 Local Port of the socket is 1283
Mon May 28 15:22:49 2007 Remote Host 10.20.140.34 Remote Port 8010
Mon May 28 15:22:49 2007 general list: created a new connection to '10.20.140.34'/8010 for '/portal/console', Local port: 1283
Mon May 28 15:22:49 2007 WLS info in sendRequest: 10.20.140.34:8010 recycled? 0
Mon May 28 15:22:49 2007 URL::parseHeaders: StatusLine set to [200 OK]
Mon May 28 15:22:49 2007 parsed all headers OK
Mon May 28 15:22:49 2007 sendResponse() : uref->getStatus() = '200'
Mon May 28 15:22:49 2007 for 10.20.140.34/8010/8010, updating JVMID: 336430126
Mon May 28 15:22:49 2007 Going to send headers to the client. Status :200 OK
Mon May 28 15:22:49 2007 *******Exception type [WRITE_ERROR_TO_CLIENT] raised at line 1545 of .\iisproxy.cpp
Mon May 28 15:22:49 2007 NOT failing over after sendResponse() exception: idempotent=1 pastFailover=1
Mon May 28 15:22:49 2007 request [portal/console] did NOT process successfully ..................
Anyone can help me?
[]'s
Emerson Santos

In your source, you have set the prefix to /irj/. If you change it to /irj it will work.
Note - IISProxy is no longer supported, SPNegro should be used instead.
Paul

IIsProxy version for windows authentication

We are in the process of installing windows authentication to our EP 6.0 portal. We are running on SP 11 J2EE with portal SP 11 patch 3.
The first question I have in document Using Header variables or Integrated Windows Authentication section Installing the IIsProxy module says for security reasons we need to install version 1.7.0.0. Was this version released, we cannot find it on the service market place?
My second question, when we use version IISPROXY16_2-10001433.SAR the authentication mechanism works fine to the portal but I cannot navigate within the portal, it looks like the screen get stuck on the first Iview no matter what role you choose. When we use version IISPROXY15_0-10001969.SAR things work fine. I increased the trace while using IISProxy 16.2 but there were no errors in the logs. We would like to be on the latest version. Any idea what might be the problem?
Thanks for your help,
Mike Fasheh

Hi folks !
I have made this configuration a couple of times without problems (other iisproxy version), but for some reason this time is not working and Im totally desesperated =(
Scenario:
- 1st server, win 2003, iis 6.0: Iisproxy 1.6.2 installed, it forwards the requests correctly
- 2st. server, ibm with aix, sap ep 6.0 sp12. Configurations made for NT authentication.
The problem:
For some reason the virtual directories defined in IisProxy.xml file are not taking the IIS Security Settings (Integrated Windows Authenticated). The iisproxy is just forwarding the request, but the IIS is not making the NT authentication.
If I change the name of the virtual directory in the IisProxy.xml file (put any name). In this case, IIS applies the security settings correctly.
Any clue about this ?
Thanks a lot for your help !!!!!!
Regards from Mexico,
Diego

ISAPI plugin setup for Idempotent --- URL level

The document http://www.weblogic.com/docs51/admindocs/isapi.html#ini says
          Idempotent=ON/OFF is a URL level flag, does this mean I can indicate which
          servlet is idempotent and which is not ? but it fails to tell me how to set
          it for different URL, what's the setup look like?
          iisproxy.ini
          weblogichost=myserver
          weblogicport=7001
          Idempotent=ON --- this would make everything idempontent, how about if I
          want /idem/*.jsp all idempotent and /noidem/*.jsp not idempotent ?
          thanks


No you cannot set it per servlet, it is an application level flag.
          I think the doc is confusing so we will correct it.
          Current doc says:
          "This is a URL level flag. By default it will be "ON". This means that if the
          servers do not respond within HungServerRecoverSecs, the plug-ins will failover.
          If set to "OFF" the plug-ins will not failover. It can be
          set differently for different URL's or Mime types."
          The correct statement for ISAPI should be:
          "This is a application level flag. But it can be set differently for different
          iisproxy.ini files. By default it will be
          "ON". This means that if the servers do not respond within
          HungServerRecoverSecs, the plug-ins will
          failover. If set to "OFF" the plug-ins will not failover."
          By "It can be set differently for different iisproxy.ini files", I mean the
          following. You can point to different
          iisproxy.dll's for different Virtual directories in IIS. So in each of those
          IISproxy.ini files
          you can have a different value for the Idempotent parameter.
          NSAPI and Apache plugins support multiple objects so the above statement is true
          upto some extent for them.
          But then again you cannot set it for each servlet differently there too, unless
          you have a didicated object for
          each servlet in NSAPI,. which is theoretically correct but would be a ridiculous
          design :)
          Thanks for pointing out. We will correct the docs. Sorry for the confusion.
          --Vinod.
          Tony Lu wrote:
          > The document http://www.weblogic.com/docs51/admindocs/isapi.html#ini says
          > Idempotent=ON/OFF is a URL level flag, does this mean I can indicate which
          > servlet is idempotent and which is not ? but it fails to tell me how to set
          > it for different URL, what's the setup look like?
          >
          > iisproxy.ini
          >
          > weblogichost=myserver
          > weblogicport=7001
          > Idempotent=ON --- this would make everything idempontent, how about if I
          > want /idem/*.jsp all idempotent and /noidem/*.jsp not idempotent ?
          >
          > thanks

Need for idempotent stateless session beans

I'm trying to find a solution for failovering method calls on a stateless
          session bean, even for method calls that already have started.
          I understand that failover services for failures that occur while the method
          is in progress, are supported only for idempotent method.
          My question is why ???
          Assuming that I start a transaction each time I call a method on a bean, I
          believe that committing the work will be done only after the method returned
          successfully. Why can't the stub decide that if it something went wrong in
          the transaction then it wasn't committed and it can be run again ?
          We need the method call failover services real bad, while making the methods
          idempotent can be very awkward sometime.
          TIA
          Eran.


Eran Erlich wrote:
          > I'm trying to find a solution for failovering method calls on a stateless
          > session bean, even for method calls that already have started.
          > I understand that failover services for failures that occur while the method
          > is in progress, are supported only for idempotent method.
          > My question is why ???
          > Assuming that I start a transaction each time I call a method on a bean, I
          > believe that committing the work will be done only after the method returned
          > successfully. Why can't the stub decide that if it something went wrong in
          > the transaction then it wasn't committed and it can be run again ?
          Its hard to decide whether the stub has to retry or not since the failure
          could have happened anytime. So, the stub will retry only if it knows for sure
          that it is safe to retry.
          - Prasad
          >
          > We need the method call failover services real bad, while making the methods
          > idempotent can be very awkward sometime.
          >
          > TIA
          > Eran.

Clustering with wl 6.1 - Questions

Hi,
          Sorry for the duplicity, but I realized I need to start a new thread.
          Regards,
          Manav.
          ==================
          Hi,
          My setup is:
          Admin: 192.168.1.135:7001 (XP). Cluster address:192.168.1.239, 192.168.1.71
          managed server 1: 192.168.1.239:7001 (SunOS)
          managed server 1: 192.168.1.71:7001 ('98)
          I have a sample SLSB deployed on the server. The deployment desriptors are
          configured as:
          <stateless-session-descriptor>
          <stateless-clustering>
          <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          <stateless-bean-load-algorithm>random</stateless-bean-load-algorithm>
          <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
          potent>
          </stateless-clustering>
          </stateless-session-descriptor>
          A test client acess the cluster by specifying the JNDI URL
          "t3://192.168.1.71, 192.168.1.239:7001" and works properly.
          1. If I kill one of the managed servers, the requests are load balanced to
          the other server. But the behaviour is erratic - after one server dies, it
          actually executes faster!?! And no, its independed of whichever managed
          server I kill.
          2. How do I monitor how many instances were created on each managed server?
          Does it the WL console show this somewhere?
          3. I have not done anything special to setup the JNDI tree? I'm a li'l hazy
          on this (am reading documents on the same). Any pointers? I'm still trying
          to grasp the need (I understand the bit about synchronizing the JNDI tree in
          the cluster to keep all servers aware of the EJBs deployed on them, and on
          others on the cluster, but i'm sure there's more to it that I don't know
          about).
          4. I find when the managed servers join the cluster, any errors/info
          messages are not stored in their respective logs. Is this the right
          behaviour? Are these logs stored on the admin server instead? (Is this what
          the log file wl-domain.log used for?)
          5. How do i monitor the deployed ejbs through the console? Does it tell me
          the number of creations/destructions, method calls, etc? How to determine if
          the pool is adequate or requires to be increased?
          6. What is a realm? How is it helpful?
          7. What is a replication group? How does it help me in clustering?
          The more I read, the more I keep getting confused. I don't expect the gurus
          to answers all questions, but any help will be appreciated.
          With Warm Regards,
          Manav.


Hi,
          Sorry for the duplicity, but I realized I need to start a new thread.
          Regards,
          Manav.
          ==================
          Hi,
          My setup is:
          Admin: 192.168.1.135:7001 (XP). Cluster address:192.168.1.239, 192.168.1.71
          managed server 1: 192.168.1.239:7001 (SunOS)
          managed server 1: 192.168.1.71:7001 ('98)
          I have a sample SLSB deployed on the server. The deployment desriptors are
          configured as:
          <stateless-session-descriptor>
          <stateless-clustering>
          <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          <stateless-bean-load-algorithm>random</stateless-bean-load-algorithm>
          <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
          potent>
          </stateless-clustering>
          </stateless-session-descriptor>
          A test client acess the cluster by specifying the JNDI URL
          "t3://192.168.1.71, 192.168.1.239:7001" and works properly.
          1. If I kill one of the managed servers, the requests are load balanced to
          the other server. But the behaviour is erratic - after one server dies, it
          actually executes faster!?! And no, its independed of whichever managed
          server I kill.
          2. How do I monitor how many instances were created on each managed server?
          Does it the WL console show this somewhere?
          3. I have not done anything special to setup the JNDI tree? I'm a li'l hazy
          on this (am reading documents on the same). Any pointers? I'm still trying
          to grasp the need (I understand the bit about synchronizing the JNDI tree in
          the cluster to keep all servers aware of the EJBs deployed on them, and on
          others on the cluster, but i'm sure there's more to it that I don't know
          about).
          4. I find when the managed servers join the cluster, any errors/info
          messages are not stored in their respective logs. Is this the right
          behaviour? Are these logs stored on the admin server instead? (Is this what
          the log file wl-domain.log used for?)
          5. How do i monitor the deployed ejbs through the console? Does it tell me
          the number of creations/destructions, method calls, etc? How to determine if
          the pool is adequate or requires to be increased?
          6. What is a realm? How is it helpful?
          7. What is a replication group? How does it help me in clustering?
          The more I read, the more I keep getting confused. I don't expect the gurus
          to answers all questions, but any help will be appreciated.
          With Warm Regards,
          Manav.

Iisproxy.dll problem

Hello all,
our group is having a problem with Weblogic's IIS plugin from the SP8 for WL5.1.
The plugin resubmits
long requests(queries) after about 5 minutes if the results don't come back from
the database in this
period of time, even though the ConnectionTimeoutSecs and ConnectionRetrySecs have
been set
to the same value, so it (the plugin) would never resubmit the request and would
time out after the
specified amount of seconds(according to the documentation).
But it does not work. Is there a bug in iisproxy.dll?
Any help would be appreciated.
Dmitriy.

ConnectionTimeoutSecs and ConnectionRetrySecs are more for the connection
between the client and the web server. They are used to calculate number of
connection retries with weblogic. HungServerRecoverSecs is the parameter you
need to play with. default=300 and max=600. It defines the timeout for reads
and writes
from/to weblogic. Note that plugin retries at least twice. Also you may
want to
set the parameter Idempotent to false in case you don't want failover at
all.
--Vinod.
"Dmitriy Kopylenko" <[email protected]> wrote in message
news:3a79a237$[email protected]..
>
Hello all,
our group is having a problem with Weblogic's IIS plugin from the SP8 forWL5.1.
The plugin resubmits
long requests(queries) after about 5 minutes if the results don't comeback from
the database in this
period of time, even though the ConnectionTimeoutSecs andConnectionRetrySecs have
been set
to the same value, so it (the plugin) would never resubmit the request andwould
time out after the
specified amount of seconds(according to the documentation).
But it does not work. Is there a bug in iisproxy.dll?
Any help would be appreciated.
Dmitriy.

General concurrency question

Hello,
          We are in the process of writing an EJB-based application
          running on top of WLS in a clustered environment and wonder
          about the following:
          1. We have transactional control in a session bean to make sure
          that proper synchronization is used when concurent clients (JSPs)
          invoke services on instances of the same session bean.
          Would this work fine in the clustered environment? i.e. is any
          additional code/care needed so that the same
          transaction/synchronization control work equally well in the
          clustered environment?
          2. Some entity EJBs will certainly be replicated. Does the
          clustering automatically take care of data validity? i.e. in
          cluster 1 the database info the entity bean gets updated while
          in cluster 2 a client (say a session bean) accesses the entity bean,
          do we have guarantee that cluster 2's client gets the data as
          was updated by cluster 1's client?
          Any information would be greatly appreciated. Many thanks
          in advance!
          Please Cc your replies to [email protected], if
          not a burden.
          -Mourad


The dbIsShared property of the deployment descriptor will also address the
          concerns in your second question.
          --Joe Sherwin
          Senthil Kumar S wrote:
          > Mourad Zerroug wrote:
          >
          > > Hello,
          > >
          > > We are in the process of writing an EJB-based application
          > > running on top of WLS in a clustered environment and wonder
          > > about the following:
          > >
          > > 1. We have transactional control in a session bean to make sure
          > > that proper synchronization is used when concurent clients (JSPs)
          > > invoke services on instances of the same session bean.
          > >
          > > Would this work fine in the clustered environment? i.e. is any
          > > additional code/care needed so that the same
          > > transaction/synchronization control work equally well in the
          > > clustered environment?
          >
          > Statefull session bean`s Home can be clusterable not the remote objects.
          > So if the client connects to a session bean then it will be pinned
          >
          > Stateless session beans:
          > In this case u have ot make sure the services are idempotent. The
          > implementation should take care of those duplicate calls
          >
          > >
          > > 2. Some entity EJBs will certainly be replicated. Does the
          > > clustering automatically take care of data validity? i.e. in
          > > cluster 1 the database info the entity bean gets updated while
          > > in cluster 2 a client (say a session bean) accesses the entity bean,
          > > do we have guarantee that cluster 2's client gets the data as
          > > was updated by cluster 1's client?
          >
          > It depends on the isolation level u set.
          > weblogic.com/docs51/classdocs/API_ejb/EJB_reference.html#1056190
          >
          > >
          > >
          > > Any information would be greatly appreciated. Many thanks
          > > in advance!
          > >
          > > Please Cc your replies to [email protected], if
          > > not a burden.
          > >
          > > -Mourad

Got a question? Just AskBEA!!

BEA Customer Support is excited to announce our new and enhanced online support service
called AskBEA. AskBEA provides the easiest way for you to ask customer support questions
online, anytime, and receive immediate response. Simply select the product grouping and
the area you want to search, ask a question in plain English, and AskBEA will provide you with
relevant answers from various online resources.
The power of AskBEA lies in it's ability to use a single interface to search disparate online
knowledge sources through out bea.com, including product documentation, white papers on
developer center, support knowledge base and product newsgroups. This service will allow
newsgroup protocol NNTP information to be more intuitively navigable, accessed and utilized
by BEA customers. AskBEA is powered by answerFriend's questionEngineTM that uses XML and
WebLogic's JSP and EJB technologies. Unlike other keyword search engines, answerFriend's
questionEngineTM, the advanced natural language processing engine technology provided by
answerFriend, has the ability to interpret your question and bring you precise, relevant, accurate
answers.
With AskBEA your question is parsed into concepts. These concepts are matched against the BEA
concept knowledge base, and answers returned by the engine are scored and ranked based on the
concept matching. Therefore, the more detailed the question, the more accurate the result.
For example, queries such as 'How to create a jar file?', 'How do I setup iisproxy.ini?', or 'Database
mapping to ejb' have enough concepts for the engine to bring the most accurate results. However,
queries such as 'jsp problem', 'not enough space' or 'download document' are likely to result in too
many results and will dilute the response set.
As a member of the e-generation who uses BEA products to build state-of-the-art e-commerce
applications, we realize your time is valuable. AskBEA is the first step to address your needs for an
online service that empowers you with the tools to access relevant information quickly, on your own,
and at your convenience.
Visit AskBEA now! http://www.bea.com/support/.
Thank you.
BEA Customer Support Organization
[new_ask.jpg]

I think it would be cool if BEA could also answer questions here...

SETTING OF IISPROXY.INI FILE

Well we are trying that whenever we shutdown the weblogic server at ourpoduction site,(our login page is with jsp extention) it shouldautomaticallygive the user a message "site under......".I checked in the documentationthatfor such a thing we can set a property in iisproxy.ini file as ErrorPage=url(in case iis is not able to get a response from weblogic it will go to thecustomized error page we define).MY first question is can we set thispropertyin the weblogic 4.5.1 version in the ini file.If yes i tried it but doesn'twork what are the steps to be followed?else can you suggest some solution.


The error page URL needs to be an HTML file located on the web server. It
          cannot be a JSP. Since the IISPROXY.INI file is shared regardless of how
          many virtual servers you may have, I would refer a fully qualified URL
          instead of relative.
          "AMIT SOOD" <[email protected]> wrote in message
          news:3b009b6e$[email protected]..
          > Well we are trying that whenever we shutdown the weblogic server at
          ourpoduction site,(our login page is with jsp extention) it
          shouldautomaticallygive the user a message "site under......".I checked in
          the documentationthatfor such a thing we can set a property in iisproxy.ini
          file as ErrorPage=url(in case iis is not able to get a response from
          weblogic it will go to thecustomized error page we define).MY first question
          is can we set thispropertyin the weblogic 4.5.1 version in the ini file.If
          yes i tried it but doesn'twork what are the steps to be followed?else can
          you suggest some solution.

Conn. IISPROXY on Win2K and AIX WebLogic server...

Greetings,
Does anybody know if it is possible to connect IIS 5.0 servers to an
AIX WebLogic app server? The IIS 5.0 servers are using IISPROXY.DLL.
I can get a login screen to pass through the dll, proving connectivity
from the IIS box to the app server (and the DB), but as soon as I hit
the login button, I get an error.
Thanks in advance for any insight that you may be able to share with
me!

Hi.
I need more information. What version/service pack level of WLS are you
running? Are you using the IIS plugin from the same service pack level?
Does your application work fine if you hit the WLS server directly?
What is the specific error you are seeing? Is there a corresponding error
in the WLS log file, or the IIS log file (set Debug to ON in
iisproxy.ini).
You might also try to post this question on the plugin newsgroup -
weblogic.developer.interest.plugin.
Thanks,
Michael
David wrote:
Greetings,
Does anybody know if it is possible to connect IIS 5.0 servers to an
AIX WebLogic app server? The IIS 5.0 servers are using IISPROXY.DLL.
I can get a login screen to pass through the dll, proving connectivity
from the IIS box to the app server (and the DB), but as soon as I hit
the login button, I get an error.
Thanks in advance for any insight that you may be able to share with
me!--
Michael Young
Developer Relations Engineer
BEA Support

IISProxy Idempotent question

Similar Messages

Maybe you are looking for