Migrating from WLS 8.x to 9.x or 10 ?

We're preparing to make the effort to migrate up from WLS 8.x.
Our deployments include some heavy usage of Workshop, as well as JMS and WebServices.
As such, we are faced with some real work, particularly with the workshop apps - as workshop in 9.2 is not backward compatible with 8.x.
My question is: Since 10 is about to be released, would we be better spending our money on going straight from 8.x to 10, rather than repeating the upgrade process in a matter of months, if we were to go to 9.2 at this point?
Is there a migration plan from bea for folks who would like to go from 8.x to 10 (skipping 9.x)?
thanks!

Hi,
You can get rid of JSP version specific problems by using the following weblogic.xml file:-
<weblogic-web-app>
<jsp-descriptor>
<jsp-param>
<param-name>backwardCompatible</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<weblogic-web-app>
It will also confirm if the error you are seeing is due to JSP version differences in 8.1 and 9.x.
Regards.

Similar Messages

Migration from WLS 10.0 MP1 to WLS 10.0 MP2

Hello there,
We need to migrate our applications from WLS 10.0 MP1 to WLS 10.0 MP2. Could you please give us an url to download a workshop version that includes WebLogic Portal and WLS 10.0.2?
I've been looking for an installer on the web, but in the Oracle web sites, haven't found any BEA products older versions.
Thanks & Regards
Franco Utreras G.

Hello,
There are 2 options for legacy Weblogic installer download:
Option1: If you have an Oracle Metalink account, you could login and go to Metalink doc ID - 763603.1 which is the "BEA Release Archive". From here you can download the historical BEA releases.
You get the following releases that can be downloaded from here.
Oracle Weblogic Server - Version: 6.1 to 10.3
Oracle JRockit - Version: 7.0 to R27.6
Option2: Login to: https://Metalink.oracle.com
Go to tab: Patches & Updates
Quick Links to: Latest Patchsets, Mini Packs and Maintenance Packs
Patch Bundles for Individual Products or Components
Select BEA Weblogic Platform
Select the WebLogic Main version and SP version
Then you should see the download screen.
HTH
Regards
RC2
http://crkthoughts.blogspot.com

!!! Jsp compilation error in deploying : in migrating from WLS 8.1 to 9.2

Hi,
We are trying to migrate a .war file from WLS 8.1 to WLS 9.2. After other changes are done, while deploying the .war file in in WLS 9.2 we are getting errors for a jsp file:
1> Syntax error near 'import' ^-------------------^
2> at Line 6 ;The qualifier of this name is a package,which cannot contain methods ^---------------------^
the jsp is simple one & goes like this:: (this jsp file also included in another jsp file .... not sure if this causing the problem ?)
<%@ page import="com.src.config.ConfigurationManager" %> // this class is properly present in /WEb-INF/classes/com/src/config/ .... causing error 1
<%
String sRequestURI = request.getRequestURI();
String sBaseURI = sRequestURI.substring(0, sRequestURI.lastIndexOf("/"));
ConfigurationManager configMan = ConfigurationManager.getInstance(); // Line 6 .. causing error 2
String sOraRoot = configMan.getProperty("OraRoot");
%>
any help please !!
Edited by: user10284044 on Dec 10, 2008 10:54 PM

Hi,
You can get rid of JSP version specific problems by using the following weblogic.xml file:-
<weblogic-web-app>
<jsp-descriptor>
<jsp-param>
<param-name>backwardCompatible</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<weblogic-web-app>
It will also confirm if the error you are seeing is due to JSP version differences in 8.1 and 9.x.
Regards.

Migrating from WLS 8.1 SP5 to Sp6

We have successfully runned WLS 8.1 SP5
When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
l edxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?

Anton Gavazuk wrote:
We have successfully runned WLS 8.1 SP5
When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
l edxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?Hi. This is a known issue with 81sp6. Ask support for the patch
for CR308071. We document that it is forbidden to have multiple
XA datasources pointing to the same pool, and we now enforce that,
but the bug is that we were also preventing mulitple datasources
to non-XA pools as well.
Joe

Error encountered while doing Migration from WLS 8.1 to WLS 10.0

Hello All ,
We are trying to do a WLS migrate(8.1 to 10.0) for a java/j2ee based application. We did not face any issues while compling application code (using jdk 1.5 & weblogic.jar of WLS 10.0) but while running the ant build script , we encountered an error while executing below part
Line: -----
1 <java classname="weblogic.appc" fork="true" maxmemory="${appc.java.maxmemory}" failonerror="true">
2 <classpath>
3 <pathelement path="${project.classpath}"/>
4 </classpath>
5
6 <jvmarg line="${appc.java.options} -Djava.io.tmpdir=${appc.tmp.dir}"/>
7
8 <arg line="-compiler ${appc.compiler} -output ${_appc.output}
9 -classpath ${_appc.classpath}
10 ${bmwslc.param.options}
11 ${appc.additional.options}
12 ${_appc.input}" />
13 </java>
Line: -----
Following is the error , which we encountered
Line: -----
# [java] Usage: java weblogic.appc [options] <ear, jar, war or rar file or directory>
# [java] where options include:
# [java] -help Print the standard usage message.
# [java] -version Print version information.
# [java] -output <file> Specifies an alternate output archive or
# [java] directory. If not set, output will be
# [java] placed in the source archive or directory.
# [java] -plan <file> Specifies an optional deployment plan.
# [java] -forceGeneration Force generation of EJB and JSP classes.
# [java] Without this flag the classes may not be
# [java] regenerated if it is determined to be
# [java] unnecessary.
# [java] -quiet Turns off output except for errors
# [java] -lineNumbers Add JSP line numbers to generated class
# [java] files to aid in debugging.
# [java] -library <file> Comma-separated list of libraries. Each
# [java] library may optionally set its name and
# [java] versions, if not already set in its
# [java] manifest, using the following syntax: <file>
# [java] [@name=<string>@libspecver=<version>
# [java] @libimplver=<version|string>]
# [java] -librarydir <dir> Registers all files in specified directory
# [java] as libraries.
# [java] -writeInferredDescriptors Write out the descriptors with inferred
# [java] information including annotations.
# [java] -keepgenerated Keep the generated .java files.
# [java] -verbose Compile with verbose output.
# [java] -classpath <path> Classpath to use.
# [java] -source <source> Source version.
# [java] -target <target> Target version.
# [java] -advanced Print advanced usage options.
# [java] <May 18, 2010 12:36:19 PM CEST> <Error> <J2EE> <BEA-160187> <weblogic.appc failed to compile your application. Recompile with the -verbose option for more details. Please see the error message(s) below.>
# [java] [J2EE:160128]ERROR: Incorrect appc command-line. Too many arguments were given. The command-line only takes a single argument, the source file, in addition to the supported options.
Line: -----
All the arguments looks correct to me while debugging . here is the summary of echo statements
${appc.additional.options} =""
${bmwslc.param.options} ="-forceGeneration"
${_appc.input}="test_ear-generic.ear"
I am dumb struck at this point
Please suggest any other thoughts , which you have in mind .
Thanks in advance !
Regards
Shobit

Probably too late for an answer but I try,
We are not able to build our J2EE 1.4 application with weblo 10, we have to build them with weblo 8 which contains the xdoclet. then we deploy it in WL10. then sometimes we have to fix some build constraints that WL10 doesn't allow anymore.

XMLBEANS classcastexception issues when migrating from WLS 8.1 to WLS 9.2

Hi
We are migrating our applications from Weblogic 8.1 / xbean (?) to Weblogic 9.2 / apache xbean 2.2.9-r540734 .
We compiled our schema successfully with new version after making changes recommended by bea (replaced all com.bea.xml occurrences to org.apache.xmlbeans ) along with ant task def etc.
XBEAN Compilation produces classes in following package structure: com.tuftshealth.container.providerListService.* and com.tuftshealth.container.providerListService.impl.*
Our XSD looks like below:
===============================
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:this="http://www.tuftshealth.com/Container/ProviderListService" xmlns:messageheader="http://www.tuftshealth.com/Base/MessageHeader" xmlns:name="http://www.tuftshealth.com/Base/Name" xmlns:status="http://www.tuftshealth.com/Base/Status" xmlns:network="http://www.tuftshealth.com/Base/Network" xmlns:date="http://www.tuftshealth.com/Base/DateRange" xmlns:contact="http://www.tuftshealth.com/Base/Contact" xmlns:address="http://www.tuftshealth.com/Base/Address" xmlns:reference="http://www.tuftshealth.com/Base/Reference" xmlns:member="http://www.tuftshealth.com/Base/Member" xmlns:benefit="http://www.tuftshealth.com/Base/Benefit" xmlns:covlimit="http://www.tuftshealth.com/Base/CoverageLimitations" xmlns:groupriders="http://www.tuftshealth.com/Base/GroupRiders" xmlns:buslninfo="http://www.tuftshealth.com/Base/BusinessLineInfo" xmlns:phone="http://www.tuftshealth.com/Base/Phone" targetNamespace="http://www.tuftshealth.com/Container/ProviderListService" elementFormDefault="qualified">
     <import namespace="http://www.tuftshealth.com/Base/MessageHeader" schemaLocation="../Base/MessageHeader.xsd"/>
     <element name="ProviderListRequest" type="this:PrivderListServiceRequestType"/>
     <complexType name="PrivderListServiceRequestType">
          <sequence>
               <element name="MessageHeader" type="messageheader:MessageHeaderType"/>
               <element name="providerRequestInfo" type="this:ProviderListRequestParamsType"/>
=================================
This results in exceptions at run time when we call a Tibco using a generic broker class.
The broker uses following method to return class to us:
obj = XmlObjectBase.Factory.parse(XMLString);
XMLString contains following payload:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ProviderListResponse xmlns:ns0="http://www.tuftshealth.com/Container/ProviderListService">
Debug Info:
PACKAGE NAME: **** com.tuftshealth.www.container.providerlistservice.impl
CLASS NAME: ****** com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl
java.lang.ClassCastException: com.tuftshealth.www.container.providerlistservice.impl.ProviderListResponseDocumentImpl
XmlObjectBase is returning the class with www in package name. This causes ClassCastException.
We tried to use XmlObject and XmlOptions is various combinations to see if "www" in package name goes away but it stays the same.
Can someone please help us here ? It seems that behavior of XmlObject or XmlObjectBase has changed between two versions. Our apps can't work without the broker to return correct class type.
Thanks for your help,
Shikhar

Hi,
You can get rid of JSP version specific problems by using the following weblogic.xml file:-
<weblogic-web-app>
<jsp-descriptor>
<jsp-param>
<param-name>backwardCompatible</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<weblogic-web-app>
It will also confirm if the error you are seeing is due to JSP version differences in 8.1 and 9.x.
Regards.

Migrating apps from WLS 10.3.0 to SOA Suite 11g-- WLS 10.3.3

Hi,
We want to migrate our apps from WLS 10.3.0 to SOA Suite 11g-->WLS 10.3.3. While deploying the apps on WLS 10.3.3 (SOA Suite Domain 11g), it is throwing exception as below. This exception is common for almost all apps. Kindly help.
Caused by: weblogic.utils.compiler.ToolFailureException: Unable to load your custom module provider's module-factory-class com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory
at weblogic.application.compiler.FlowDriver.handleStateChangeException(FlowDriver.java:53)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:37)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169)
... 67 more
Caused by: weblogic.management.DeploymentException: Unable to load your custom module provider's module-factory-class com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory
at weblogic.application.internal.flow.CustomModuleHelper.loadModuleFactory(CustomModuleHelper.java:82)
at weblogic.application.internal.flow.CustomModuleHelper.initFactories(CustomModuleHelper.java:52)
at weblogic.application.utils.CustomModuleManager.createScopedCustomModules(CustomModuleManager.java:119)
at weblogic.application.utils.CustomModuleManager.<init>(CustomModuleManager.java:39)
at weblogic.application.compiler.WARModule.merge(WARModule.java:466)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:41)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
... 72 more

Below link might be helpful.
http://kr.forums.oracle.com/forums/thread.jspa?threadID=1049509&tstart=0
Regards,
Anandraj
http://weblogic-wonders.com/

Migrating JMS Persistence from WLS 4.5.2 to WLS 6.1

Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
Thanks

Hi.
I'm not sure that there is an automatic process to accomplish this, but you might get a
better answer by posting this on the JMS newsgroup.
Regards,
Michael
Manuel Villalta wrote:
Hi,
we are migrating several applications from WLS 4.5.2 to WLS 6.1. A application use
JMS with persistence in DB (JMS persistence WLS 4.5.2 is in DB) with WLS 6.1 we want
to change persistence mode to FIles. Therefore during migration process we have to
move the messages stored in the database to a file. The messages stored in the file
will be recovered for WLS 6.1.
My doubt is, Is there a automatic process for migrate messages in the DB to a persistence
file?
Thanks--
Michael Young
Developer Relations Engineer
BEA Support

Creation of domain issues - migration from weblogic 10.3.0 to 10.3.5 versio

Hello,
i would like to kindly ask for a help with following issue:
Basically we are migrating from the 10.3.0 to the 10.3.5 version. We are building the domain using the template in "silent mode". And when i try to create the domain with new weblogic 10.3.5 im getting some errors.
The command to run the creation of the domain is following:
${WL_HOME}/common/bin/config.sh -mode=silent -silent_script=${SILENT_SCRIPT} -log=${WLLOGFILE} >> ${LOGFILE} 2>&1
returnCode=$?
SILENT_SCRIPT contains following commands:
read template from "/local/wg372/BM/appl/config/NEW_DOMAIN_CONFIGURED.jar";
write domain to "/local/wg372/BM/appl/BmDomain";
set OverwriteDomain "true";
close template;
When i setup new env(solaris) with weblogic 10.3.5 im getting following error when the silent_script command (*write domain to "/local/wg372/BM/appl/BmDomain";*) is executed:
2011-07-18 16:53:00,427 INFO [runScript] com.oracle.cie.domain.script.ScriptExecutor - succeed: read template from "/local/wg372/BM/appl/config/NEW_DOMAIN_CONFIGURED.jar"
2011-07-18 16:53:00,427 INFO [runScript] com.oracle.cie.domain.script.ScriptExecutor - write Domain to "/local/wg372/BM/appl/BmDomain"
2011-07-18 16:53:00,505 ERROR [runScript] com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask - There was an error executing the script: /local/wg372/BM/appl/installer/silent_script
java.lang.NullPointerException
     at com.oracle.cie.domain.security.SecurityGenerateLDIFT.buildSecurityInfo(SecurityGenerateLDIFT.java:460)
     at com.oracle.cie.domain.security.SecurityGenerateLDIFT.<init>(SecurityGenerateLDIFT.java:119)
     at com.oracle.cie.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:718)
     at com.oracle.cie.domain.script.ScriptParserClassic$StateMachine.processWrite(ScriptParserClassic.java:573)
     at com.oracle.cie.domain.script.ScriptParserClassic$StateMachine.execute(ScriptParserClassic.java:429)
     at com.oracle.cie.domain.script.ScriptParserClassic.parseAndRun(ScriptParserClassic.java:148)
     at com.oracle.cie.domain.script.ScriptParserClassic.doExecute(ScriptParserClassic.java:110)
     at com.oracle.cie.domain.script.ScriptParser.execute(ScriptParser.java:72)
     at com.oracle.cie.domain.script.ScriptParser.execute(ScriptParser.java:35)
     at com.oracle.cie.wizard.domain.helpers.Executor.runSilentScript(Executor.java:68)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask.runScriptWithExecutor(RunScriptTask.java:551)
     at com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask.execute(RunScriptTask.java:335)
     at com.oracle.cie.wizard.silent.tasks.AbstractSilentTask.run(AbstractSilentTask.java:28)
     at java.lang.Thread.run(Thread.java:662)
In Windows env im getting following error:
create.domain:
[exec] -mode="silent" -silent_script=J:/_dev/build/installer/silent_script
[exec] << read template from "J:/_dev/build/config/NEW_DOMAIN_CONFIGURED.jar"
[exec] >> succeed: read template from "J:/_dev/build/config/NEW_DOMAIN_CONFIGURED.jar"
[exec] << write Domain to "J:/_dev/build/BmDomain"
[exec] CFGFWK-60550: Script execution aborted. The script may contain an error.
[exec] null
CFGFWK-60550: - doc says
CFGFWK-60550: Script execution aborted. The script may contain an error.
Cause:
Action:
Level: 1
Type: ERROR
Impact: Configuration
I tried to google for this issue, look into the weblogic documentation but with no luck.
So i would like to kindly ask, if anyone of you perhaps could give me a hint/advise with this problem.
Thanks in advance.

Hi,
thanks for the reply but im not sure if we are talking about the same thing. What i need is to upgrade the weblogic "DOMAIN" not the weblogic installation itself.
Anyway,
after some googling and testing im again stucked with another issue:
1. First i have created the old doman (10.3.0)
2. Then i have tested the domain with the new weblogic version 10.3.5 - as it should be (and is) compatible within those 2 versions
---> worked fine
3. Then via offline WLST(of weblogic 10.3.5) i have managed to create new template with command writeTemplate(nameOfTemplate.jar)
4. But when i try to create the new domain with the new template via WLST(of weblogic 10.3.5) im again stucked (im able to read the template in wlst but not able to writeDomain ) - error:
wls:/offline> readTemplate('/home/wg372/tmp/new_template.jar')
wls:/offline/BmDomain>writeDomain('/home/wg372/tmp/new_domain')
Error: writeDomain() failed. Do dumpStack() to see details.
wls:/offline/BmDomain>dumpStack()
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.ScriptException: The application location must have write permission.
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1538)
at com.oracle.cie.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:803)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyInstance.invoke(Unknown Source)
at org.python.pycode._pyx3.writeDomain$15(/var/tmp/WLSTOfflineIni6651397525640719781.py:71)
at org.python.pycode._pyx3.call_function(/var/tmp/WLSTOfflineIni6651397525640719781.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx24.f$0(<console>:1)
at org.python.pycode._pyx24.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
Caused by: com.oracle.cie.domain.script.ScriptException: The application location must have write permission.
at com.oracle.cie.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:757)
at com.oracle.cie.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:795)
... 29 more
I tried to have a look around for the "The application location must have write permission." problem but again with no luck.
Furthemore when i try to do the same with old domain template, with old version of WLST (of weblogic 10.3.0), i have no problems with creating of the domain.
Any ideas?
Ill keep you updated :-)

Problem with servlet after migrating from OC4J to WebLogic 10.3

I come across a problem when I was migrating from jDev 11g TP4 to production version in that step also server got changed from OC4J to webLogic.
I am running java http servlet along other jspx pages. When everything was on OC4J there was no problem whit security on this servlet ( servlet was under same authorization automatically, and I was able to create new application module on this servlet by createRootApplicationModule
) but when I changed to WebLogic 10.3 I come across a numerous problems. First one is solved i managed to put the servlet under same authorization as jspx pages by
*<servlet>*
*<servlet-name>report</servlet-name>*
*<servlet-class>path.to.class</servlet-class>*
*<security-role-ref>*
*<role-name>name</role-name>*
*<role-link>valid-users</role-link>*
*</security-role-ref>*
*</servlet>*
but when I trying to create new application module I get JBO-30003 error which is Caused by:
oracle.adf.share.security.ADFSecurityAuthenticationException: JAAS login error.
Invalid null input: name
Has anybody any idea what I am doing wrong?
Thank you for your help, Rok Kogov&scaron;ek

for example:
web.xml
<security-role>
<role-name>yourrole</role-name>
</security-role>
weblogic.xml
<security-role-assignment>
<role-name>yourrole</role-name>
<principal-name>wlsuser</principal-name > 
</security-role-assignment>

Migration from OAS 10g to Weblogic 10.3

Hello,
I migrate large app from OAS 10g to Weblogic 10.3.
1.
The main part of the job was to prepare descriptors for Weblogic. Unfortunatelly I don't find any tool that could do the job:( There are some problems with descriptors namespaces. This schema and namespaces given in 10.3 docs are not working (not available):
http://edocs.bea.com/wls/docs103/ejb/DD_defs_reference.html
So I use the one from 10 release in weblogic-ejb-jar.xml:
weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
and form 9 release in weblogic-cmp-rdbms-jar.xml:
<weblogic-rdbms-jar xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-rdbms20-persistence.xsd">
There are also some bugs in docs about ejb relations.
After fixing some schema compliance exc this step success.
2. Next the EJBComplianceChecker - its much more restrictive than OAS verification. So updates in ejb interfaces are necessary. It is not a problem with small app but when there ale a lot of code/branches to migrate it's become a problem. I have been looking for some switch that could help with this but with no result/
EJBComplianceChecker - Spec veryfication level
3. Now after EJB compliance checker done its job with success I have an exception that I do not understand:
An error occurred during activation of changes, please see the log for details.
Exception
preparing module: EJBModule(corpo_ejb.jar)
Unable to deploy EJB: corpo_ejb.jar from corpo_ejb.jar:
There are 1 nested errors:
java.io.IOException: JDT compilation error! at
weblogic.ejb.container.ejbc.CompilerForJDT.compile(CompilerForJDT.java:66)
at
weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:357)
at
JDT compilation error!
Could you please give me some point where the problem could be? I don't have any idea where to start looking for..
What are your experiences with migrations from OAS to Weblogic 10?
Thanks in advance!
Edited by: Stoigniew Sztank on Oct 10, 2008 4:00 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 4:01 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 4:02 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 4:04 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 8:05 AM

Hi Stoigniew Sztank,
I am working on migrating Enterpirse application developed using Struts, Ejb2.0, JMS. Its been deployed on OAS 10G and Websphere, but I need to deploy the application on Weblogic 10.3. It seems you have migrated a J2ee application from OAS 10G to Weblogic 10.3. Please can you list me the steps that you followed to migrate the application.
As per my understanding follwing things needsto be taken care of:-
1) Weblogic Descriptor files:
1.1 Weblogic.xml:- we added security roles and ejb-reference-description for the ejbs.
1.2 Weblogic-ejb-jar.xml for all the ejbs used in the application.
1.3 Weblogic-application.xml
1.4 Resource Adapter
2) JMS queue set up
3) JDBC set up
It would be a great help if you can let me know what are the steps to migrate the application.
Thanks and Regards
Deepak Dani

EJB Migration Problem (WLS 9.2 = WLS 10.3.2)

Hi,
we are migrating Stateful, Stateless, and Message Driven Bean from wls 9.2 to wls 10.3.2. There is no compile error. But workshop shows Error: "Failed to retrieve WLS runtime for EJB processing".
Thank you very much for your input.
John

Hi,
we are migrating Stateful, Stateless, and Message Driven Bean from wls 9.2 to wls 10.3.2. There is no compile error. But workshop shows Error: "Failed to retrieve WLS runtime for EJB processing".
Thank you very much for your input.
John

EJB perfomance issue while migrating from weblogic 10.0 to 10.3

Hi,
I have an EJB service which I am migrating from 10.0 to 10.3
The service contains an entityManager.find() method which takes less than 2 secs to execute on 10.0 and more than 10 secs on 10.3.
The code snippet and the log trace are as below --
Code:
      logger.debug("Looking up Person for id " + personId);
   Person info = entityMngr.find(Person.class, personId);
    if(info != null) {
        logger.debug("Found Person" + info.getFirstName() + " " + info.getLastName() + " for id " + personId);
log entries:
05/31/2010 *02:35:25,197* DEBUG persistence.bean.PersistenceService [[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)':822] - Looking up Person for id 12014
05/31/2010 *02:35:36,272* DEBUG persistence.bean.PersistenceService [[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)':829] - Found Person Vitasha Harinarine for id 12014
Could somebody please help me debugging this issue? The code has not changed before migrating to 10.3. I have checked that the datasources on both environments are exactly the same.
Any help would be greatly appreciated.
Thanks in advance!
Regards,
Nishtha

Don't do that. The ClassLoader used to manage web components is the child of the classloader used to manage EJB components - the servlet can use EJB classes, the EJB's cannot use web classes.
This is also very poor practice as it couples the business logic layers of you system to the presentation - only the reverse should be done. WLS 6.0 is behaving appropriately.
Chuck

IllegalArgumentException after migrated to WLS 6.1

Hi,
I am using WLS 6.1 and Visibroker 4.5.
I have a problem that got the IllegalArgumentException when calling same
functions after migrate from 6.0 to 6.1. Please advise.
Re: It is working fine in WLS 6.0
Error message
==========
*** Begin of Error Caught in Class:
com.shk.j2ee.security.manager.SecurityManagerEJB, Method: login ***
*** Error Message: java.lang.IllegalArgumentException: port out range:-14373
*** End of Error Caught in Class:
com.shk.j2ee.security.manager.SecurityManagerEJB, Method: login ***
In CreditManagerEJB.setSessionContext()
*** Begin of Error Caught in Class:
com.shk.j2ee.credit.manager.CreditManagerEJB, Method: ejbCreate ***
*** Error Message: java.lang.IllegalArgumentException: port out range:-14373
*** End of Error Caught in Class:
com.shk.j2ee.credit.manager.CreditManagerEJB,
Method: ejbCreate ***
Regards,
Franco NG

"Franco Ng" <[email protected]> writes:
So can you provide a stacktrace?
andy
HI,
Thanks for your reply, I knew the GIOP problem, have followed the document
provided by WLS 6.1 and changed GIOP version to "1". I also tried value
type and no value type version, and sun & NT version of VisiBroker 4.5.
However, the problem is same.
Please advise!!
Regards,
Franco
"Andy Piper" <[email protected]> wrote in message
news:[email protected]..
"Franco" <[email protected]> writes:
I have a problem that got the IllegalArgumentException when calling same
functions after migrate from 6.0 to 6.1. Please advise.
Re: It is working fine in WLS 6.0
Error message
==========
*** Begin of Error Caught in Class:
com.shk.j2ee.security.manager.SecurityManagerEJB, Method: login ***
*** Error Message: java.lang.IllegalArgumentException: port out
range:-14373
*** End of Error Caught in Class:
com.shk.j2ee.security.manager.SecurityManagerEJB, Method: login ***
In CreditManagerEJB.setSessionContext()
*** Begin of Error Caught in Class:
com.shk.j2ee.credit.manager.CreditManagerEJB, Method: ejbCreate ***
*** Error Message: java.lang.IllegalArgumentException: port outrange:-14373
*** End of Error Caught in Class:
com.shk.j2ee.credit.manager.CreditManagerEJB,
Method: ejbCreate ***You need to provide more data. These are not weblogic classes. Can you
get a stacktrace?
Note that in WLS 6.1 we support GIOP 1.2. Visi has bugs in its GIOP
1.2 implementation so you will need to force GIOP 1.1 by putting:
DefaultGIOPMinorVersion="1"
in your server mbean in config.xml
andy

Migration from Workspaces to JNDI

Hello all,
Does anyone know if there is a way to have informations about this subject ?
And I was wondering whether it was a big job or not to migrate from
workspaces (wls 5.1) to wls 6 with JNDI.
Thank you for any help
Laurent Nel

I have solved the problem by changing as:
<jta-data-source>testDS</jta-data-source>And also by adding the following property.
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction.WeblogicTransactionManagerLookup" />/Onur
Edited by: Onur Aktaş on 15.Eyl.2009 17:19

Migrating from WLS 8.x to 9.x or 10 ?

Similar Messages

Maybe you are looking for