Weblogic problem while upgrading from 6.1 to 8.1 urgent pls

Hi All,

There is this app here which I need to migrate from WL 6.1 to 8.1 sp 3..

I am very new to weblogic and to this application. so pls bear with me..

My company is getting out of business, and they sold this product..

so all guys working on this app are gone..

but now this thing came up. and we can accompllish this and somehow make client happy, my company will hire the guys back and will be good for everybody.. so hope you can pls help


This app uses weblogic 6.1 and I know there were some changes made to weblogic.policy file .. new weblogic.policy file looks as below

//                     WEBLOGIC POLICY FILE
// // // // // // // // // // // // // // // // // // // // // // // //
// This file, which conforms to the java.security.Policy file
// definition, configures WebLogic Server for Java 2 security.
// WebLogic Server cannot run without the policies specified here.
//
// Before you can use these policies, edit the URL paths that point to
// your WebLogic installation. The paths you must change are in the
// first two lines following this comment block.
//
// A second grant entry provides an example of setting the permissions
// for your own Java classes.  Modify the URL paths in the first two
// lines of that grant entry to point to the location of your classes or
// any third party Java classes you want to use with WebLogic Server.
// You can copy this entry to protect additional class locations you
// may create.
//
// See http://e-docs.bea.com/wls/docs61/adminguide/cnfgsec.html for
// more information about using this policy file.
//
grant codeBase "file:${wls.home}/-" {
//  permission java.io.FilePermission "/-" , "read,write,execute";
  permission java.io.FilePermission "${wls.home}" , "read,write,execute";
  permission java.io.FilePermission "${wls.home}/-" , "read,write,execute";
  permission java.net.SocketPermission "localhost:1-65000", "connect,accept,listen,resolve";
  permission java.awt.AWTPermission "accessClipboard";
  permission java.awt.AWTPermission "accessEventQueue";
  permission java.awt.AWTPermission "showWindowWithoutWarningBanner";
  permission java.io.SerializablePermission "enableSubclassImplementation";
  permission java.io.SerializablePermission "enableSubstitution";
  permission java.lang.RuntimePermission "accessClassInPackage.*";
  permission java.lang.RuntimePermission "accessDeclaredMembers";
  permission java.lang.RuntimePermission "createClassLoader";
  permission java.lang.RuntimePermission "createSecurityManager";
  permission java.lang.RuntimePermission "defineClassInPackage.*";
  permission java.lang.RuntimePermission "exitVM";
  permission java.lang.RuntimePermission "getClassLoader";
  permission java.lang.RuntimePermission "getProtectionDomain";
  permission java.lang.RuntimePermission "loadLibrary.*";
  permission java.lang.RuntimePermission "modifyThread";
  permission java.lang.RuntimePermission "modifyThreadGroup";
  permission java.lang.RuntimePermission "readFileDescriptor";
  permission java.lang.RuntimePermission "setContextClassLoader";
  permission java.lang.RuntimePermission "setFactory";
  permission java.lang.RuntimePermission "setIO";
  permission java.lang.RuntimePermission "setProtectionDomain";
  permission java.lang.RuntimePermission "setSecurityManager";
  permission java.lang.RuntimePermission "writeFileDescriptor";
  permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
  permission java.net.NetPermission "requestPasswordAuthentication";
  permission java.net.NetPermission "setDefaultAuthenticator";
  permission java.security.SecurityPermission "getPolicy";
  permission java.security.SecurityPermission "setPolicy";
  permission java.util.PropertyPermission "*", "read,write";
  permission javax.xml.parsers.SAXParserFactory "write";
  permission java.lang.RuntimePermission "*";

};

grant {
  permission java.io.FilePermission "/-", "read";
  permission java.io.FilePermission "/tmp/-", "read,write,delete,execute";
  permission java.io.FilePermission "${wls.home}", "read,write,delete,execute";
  permission java.io.FilePermission "${wls.home}/-", "read,write,delete,execute";
  permission java.io.FilePermission "${appl.dir}/isoft", "read,write,delete,execute";
  permission java.io.FilePermission "${appl.dir}/isoft/-", "read,write,delete,execute";
  permission java.io.FilePermission "${wls.config.dir}/", "read,write,delete,execute";
  permission java.io.FilePermission "${wls.config.dir}/*", "read,write,delete,execute";
  permission java.io.FilePermission "${wls.config.dir}/config", "read,execute,write,delete";
  permission java.io.FilePermission "${wls.config.dir}/config/*", "read,write,execute,delete";
  permission java.io.FilePermission "${wls.config.dir}/config/isoftDomain", "read,write,delete,execute";
  permission java.io.FilePermission "${wls.config.dir}/config/isoftDomain/-", "read,write,delete,execute";
  // Permission "enableSubstitution" needed to run the WebLogic console
  permission java.io.SerializablePermission "enableSubstitution";
  // Permission "modifyThreadGroup" required to run the WebLogic Server
  permission java.lang.RuntimePermission "modifyThreadGroup";
  permission java.lang.RuntimePermission "setContextClassLoader";
  // Permission "setIO" needed to start a server from the WebLogic console
  permission java.lang.RuntimePermission "setIO";
  // Permission "getClassLoader" needed for many EJB clients
  permission java.lang.RuntimePermission "getClassLoader";

  permission java.lang.RuntimePermission "stopThread";
  permission java.net.SocketPermission "*:80-", "listen,connect,resolve,accept";
  permission java.net.SocketPermission "localhost:1024-", "listen";
  permission java.util.PropertyPermission "java.version", "read";
  permission java.util.PropertyPermission "java.vendor", "read";
  permission java.util.PropertyPermission "java.vendor.url", "read";
  permission java.util.PropertyPermission "java.class.version", "read";
  permission java.util.PropertyPermission "os.name", "read";
  permission java.util.PropertyPermission "os.version", "read";
  permission java.util.PropertyPermission "os.arch", "read";
  permission java.util.PropertyPermission "file.separator", "read";
  permission java.util.PropertyPermission "path.separator", "read";
  permission java.util.PropertyPermission "line.separator", "read";
  permission java.util.PropertyPermission "java.specification.version", "read";
  permission java.util.PropertyPermission "java.specification.vendor", "read";
  permission java.util.PropertyPermission "java.specification.name", "read";
  permission java.util.PropertyPermission "java.vm.specification.version", "read";
  permission java.util.PropertyPermission "java.vm.specification.vendor", "read";
  permission java.util.PropertyPermission "java.vm.specification.name", "read";
  permission java.util.PropertyPermission "java.vm.version", "read";
  permission java.util.PropertyPermission "java.vm.vendor", "read";
  permission java.util.PropertyPermission "java.vm.name", "read";
  permission java.util.PropertyPermission "java.home", "read";
  permission java.util.PropertyPermission "wls.config.dir", "read";
  permission java.security.SecurityPermission "getPolicy";
  permission java.security.SecurityPermission "setPolicy";
  permission java.lang.RuntimePermission "createClassLoader";
  permission java.lang.RuntimePermission  "accessClassInPackage.sun.io";

  permission java.io.FilePermission "<<ALL FILES>>", "execute";
  permission java.io.FilePermission "${java.installed.home}/-", "read";
  permission java.io.FilePermission "/usr/lib/-", "read";
  permission java.lang.RuntimePermission "accessDeclaredMembers";
  permission java.lang.RuntimePermission "createSecurityManager";

  permission java.security.AllPermission;
 
  permission java.util.PropertyPermission "*", "read,write";
};



And moving to 8.1 (without changing weblogic.policy file), IN SOME PARTS OF App, I am getting error as below

java.lang.NoSuchMethodError: com.actuate.schemas.Login.setEncryptedPwd(Ljava/lang/String;)V


I am not sure what to change in weblogic.policy file, what problem is this../

any ideas how to fix this.. anything to do with weblogic.policy?

regards