Using CookieName in the iisproxy.ini file

Question

Hello All,
          According to the Weblogic 451 docs, In the IISProxy.ini file, you should
          set the "CookieName= "
          property to whatever value you have specified for the
          "weblogic.httpd.session.cookie.name="
          property in your weblogic.properties file. (If it is anything other than the
          default name which is "WeblogicSession").
          We have an IIS proxy fronting 2 Weblogic App Servers which run in a
          clustered mode. Also the
          cookie name is specified in the properties file to something different than
          the default WeblogicSession
          (lets say it is "mySession").
          When we do this we see the strange behavior of the application routing us
          back to our Login page in the middle
          of a session. We assume this is happening because when our request is
          switched to a different App Server it
          cannot be associated with any session. And so we are asked to login and
          create a new session.
          This started happening only when we switched to using IIS Proxy and have the
          CookieName
          set to "mySession". This problem goes away if we change the cookieName to be
          the default and remove
          the entry from the IISProxy.ini file.
          Our App Servers are running Weblogic 4.5.1 with sp8.
          Any ideas ??
          Thanks
          Ketan.
          

Answer 1

The cookie name in your ISAPI plugin and weblogic.properties should be the
          same in all your plugins and weblogic servers. This is required. Plugin and
          WLAS share the same cookie. However, plugin and WLAS are in different
          processes. In order for plugin and WLAS to locate the same cookie, same
          cookie name in the configuration is required.
          Cheers - Wei
          Ketan Bhukhanwala <[email protected]> wrote in message
          news:[email protected]...
          > Hello All,
          >
          > According to the Weblogic 451 docs, In the IISProxy.ini file, you should
          > set the "CookieName= "
          > property to whatever value you have specified for the
          > "weblogic.httpd.session.cookie.name="
          > property in your weblogic.properties file. (If it is anything other than
          the
          > default name which is "WeblogicSession").
          >
          > We have an IIS proxy fronting 2 Weblogic App Servers which run in a
          > clustered mode. Also the
          > cookie name is specified in the properties file to something different
          than
          > the default WeblogicSession
          > (lets say it is "mySession").
          >
          > When we do this we see the strange behavior of the application routing us
          > back to our Login page in the middle
          > of a session. We assume this is happening because when our request is
          > switched to a different App Server it
          > cannot be associated with any session. And so we are asked to login and
          > create a new session.
          >
          > This started happening only when we switched to using IIS Proxy and have
          the
          > CookieName
          > set to "mySession". This problem goes away if we change the cookieName to
          be
          > the default and remove
          > the entry from the IISProxy.ini file.
          >
          > Our App Servers are running Weblogic 4.5.1 with sp8.
          >
          > Any ideas ??
          >
          > Thanks
          > Ketan.
          >
          >