The Incident Archive

I was struggeling to use WSLT to migrate my policy store for our production cluster there where classpath problems and naming problems and I just want to make the process easier for my self. So I wrote a little util to do the migration if nothing else this post will help me remeber the classes needed for the migration exercise. Script and classpath (I can post my linux script if anyone wants it) My jar file that you wont have but I will post the code: common.0.0.1.jar, ./migrator.jar Non adf etc 3rd party jars: ./lib/commons-cli-1.2.jar;./lib/commons-io-2.0.1.jar; SET WEBLOGIC_JAR=[your Middleware location]\wlserver_10.3\server\lib\weblogic.jar SET OLD_CLASSPATH=%CLASSPATH% SET CLASSPATH=%CLASSPATH%;%WEBLOGIC_JAR%;./lib/adf-controller-security.jar;./migrator.jar;./lib/adf-share-mbeans-wlst.jar;./lib/adfscripting.jar;./lib/commons-cli-1.2.jar;./lib/commons-io-2.0.1.jar;./lib/commons-logging-1.1.1.jar;./lib/common.0.0.1.jar;./lib/ldapjclnt11.jar;./lib/adf-share-base.jar;./lib/...

Finally fixed the third incarnation of this problem - when we deployed onto our dev cluster and our application deployed fine but when the login page was accessed the app went into an infinite loop. NOTE: Deploying onto the Admin server worked perfectly. In the access logs you see 302 http codes with _afrLoop parameters (302 - redirect). Really could not figure this one out. I added failover and clustering removed them. Reconfigured the security. Created a test app with one page used weblogics default security provider but still NOTHING. I even setup a cluster on my machine and everything worked (Note: I did not setup our dev cluster) So in desperation I check the system-jazn-data.xml file deployed on weblogic an lo and behold none of my application security configurations where setup in the file. I stopped everything and added what I had on my local cluster to the system-jazn-data.xml and everything just works. I need to find out what in our dev configuration is causing the syst...

I am trying to run my ADF app in a cluster and my login page redirects back on itself endlessly. Note this has been resolved - we restarted the entire weblogic server and the problem dissapeared. (I think something went wrong in the deployment) the one other change I made was to change the inner xml of session-descriptor in weblogic.xml FROM: <sharing-enabled>true</sharing-enabled> TO: <persistent-store-type>REPLICATED_IF_CLUSTERED</persistent-store-type> this should not make a difference but I though I would mention it. Here are my notes to self as I moved through the process. Application   adf-config.xml   <adf-controller-config xmlns="http://xmlns.oracle.com/adf/controller/config">     <adf-scope-ha-support>true</adf-scope-ha-support>   </adf-controller-config>     Web.xml   <context-param>     <param-name>org.apache.myfaces.trinidad.CHECK_FILE_M...