Issue in Migration from JDev 10.1.2 to JDev 10.1.3

A web app developed under JDev 10.1.2. Now try to migrate it to JDev 10.1.3. During the migration process, encountered a message:
Migrating /D:/Oracle/App/webroot/WEB-INF/struts-config.xml from JDev 10.1.2 to JDev 10.1.3
Detected custom lifecycle in the ADF application - struts-config.xml is not migrated. Please refer to documentation section on migration.
Migration failed for /D:/Oracle/App/webroot/WEB-INF/struts-config.xml
What should I do?
Thanks

i got same problem too.
run project,display as follow:
java.lang.RuntimeException: Model binding context not initialized at oracle.adf.controller.lifecycle.LifecycleContext.initialize(LifecycleContext.java:113) at oracle.adf.controller.lifecycle.LifecycleContext.initialize(LifecycleContext.java:77) at oracle.adf.controller.struts.actions.DataActionContext.initialize(DataActionContext.java:51) at oracle.adf.controller.struts.actions.DataAction.execute(DataAction.java:150) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:595)

Similar Messages

JMS issues when migration from weblogic 9.2 to 10.3.5

We are facing some issues when migration from weblogic 9.2 to 10.3.5
In weblogic 9.2 :_
BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>
Company
</ejb-name>
<entity-descriptor>
<pool>
<max-beans-in-free-pool>300</max-beans-in-free-pool>
<initial-beans-in-free-pool>150</initial-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>3500</max-beans-in-cache>
<idle-timeout-seconds>100000</idle-timeout-seconds>
<read-timeout-seconds>0</read-timeout-seconds>
<concurrency-strategy>ReadOnly</concurrency-strategy>
</entity-cache>
Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
migration to Weblogic 10.3.5_
With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
Can some one look into this and provide your inputs to resolve this issue.

I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
Tom

Error in deploy, after migration from jdev 11.1.1.3 to jdev 11.1.2.0

Hi,
I am using Jdev 11.1.2.0.
migration successfully at 11.1.1.3 to jdeveloper 11.1.2.0.
when I deploy the new version Viewcontroller project I got the error like "An unreported error occurred in Appc. No errors were reported, but the tool returned a failure result code: 1." .
Regards,
Ragu.

same discussed here as well.. have you tried the suggestions provided here
Re: Migrate from JDeveloper 11.1.1.3 to 11.1.2

What are the Issues in Migration from oracle 8i to oracle 10g

Hi,
Can you let me know what are the issues that i face when i migrate from oracle 8i to oracle 10g. I will be very thankful if you give me a list of issues that you face while migrating from 8i to 10g

In addition to Max's reply, you must be aware that you have to test your applications agains 10g database before you actually upgrade the database.
If you use CBO, it may produce different execution plans for one query when you run it in 8i and 10g. This may affect your application performances, which you don't like to happen.
Also you have to decide how much downtime you can afford during the migration. Can you afford some downtime and how much? If you can't than this makes the situation more complicated.
How big is your database? You may end up only with simple export/import solution using export import utility.
The bottom line is, whatever you decide, you must test your applications running against 10g database before you actually upgrade your database.

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

2007 MacBook Pro issues after migration from 2011 iMac

I recently bought a used 2007 Macbook Pro. I was not very familiar with migration, and I realize now I should have done a bit of research before migrating from my iMac (mid 2010) running 10.8.5. I saw the message saying I should update software, but I couldn't figure out how without logging in, and getting on my network with the MacBook. Anyway, I did the migration. My first issue was the MacBook would not let me log in. I finally got it by resetting the password using a 10.6.4 install disc that came with my iMac. The issues I have now are lots of things either won't work, or I have to run them in 32 bit mode. I'm thinking it's because the newer versions residing on my iMac won't work on the older MacBook. I am unable to open iPhoto, and Desktop & Screensaver, Energy Saver in system prefs. I had to run Mail, iCal, and Contacts in 32 bit. I do not have a disc for Lion, but I just ordered it from the Apple Store. I'm wondering if I shoud just start fresh when I get the disc, or is there any fix for my ignorance? Is a new migration out of the question since the Lion is the most I can run on the MacBook while I'm running Mountain Lion on the iMac. I would really appreciate any advise!
Thanks,
Jeff

Jeff,
what you’ve bought is the ability to download Lion from the Mac App Store, not a DVD. To be able to access the Mac App Store, you will need to have Mac OS X 10.6.6 or newer installed. The person who sold the MacBook Pro to you should not have included Lion with it, because any version of OS X downloaded from the Mac App Store is non-transferable; he should have included its original two grey installation DVDs, because those are transferable with the MacBook Pro.
Since you’ve now purchased Lion, you will be able to install your purchased version onto your MacBook Pro; however, to associate your MacBook Pro with your Apple ID (and thereby end the association of your MacBook Pro with its former owner), you will need to do a clean reïnstallaton of OS X onto it. To do a clean reïnstallation of OS X, you will need either the original model-specific pair of grey installation DVDs, or the white retail Snow Leopard DVD. It would be best to have both the grey DVDs and the Snow Leopard DVD, since the Snow Leopard DVD does not come with either the iLife applications or the Apple Hardware Test for your MacBook Pro, and your model’s grey DVDs will not let you get to Mac OS X 10.6.6 to have access to the Mac App Store.

Web service issues in migrating from ColdFusion 9 to 10

I'm troubleshooting a problem a client is having with their migration from CF9 to CF10. A webservice call that previously worked, no longer is working. When I call it from my CF10 server, I get this error:
C:...\cfusion\stubs\WS-853189522_2...\service.java:10: class, interface, or enum expected package ...;
The ellipses are to replace proprietary files paths and names.
When I add the cfinvoke attributes wsversion and refreshwsdl, I get a "Unable to read WSDL from URL: .../service.asmx?WSDL" error instead of the above error. I also changed the default ws version from 2 to 1 in the CF Administrator, with no change. Are there any other known issues with CF10 that would interfere with a webservice call that worked in an earlier version?

I found the answer, and it turned out to be quite simple. After making the change to the default webservice version in CF Admin, I needed to restart the server. It now works, although I am curious as to why adding the wsversion attribute to the cfinvoke tag calling the webservice didn't work. My concern now is that if they add an Axis 2 webservice call in the future that they may run into this problem again.

Issue during migrating from Sybase to Oracle using Oracle SQL Developer

I am using SQL Developer v 3.2.20.09 to migrate from Sybase to Oracle Pl/SQL 12c
While migrating the stored procedure the following block did not convert. I got NULL instead of object_id:
Sybase Block:
IF OBJECT_ID(‘dbo.CheckEst’) IS NOT NULL
BEGIN
DROP PROCEDURE dbo.CheckEst
IF OBJECT_ID(‘dbo.CheckEst’) IS NOT NULL
PRINT ‘<<>>’
ELSE
PRINT ‘<<>>’
END
Oracle Block after conversion:
BEGIN
IF NULL/*TODO:OBJECT_ID(‘dbo.CheckEst’)*/ IS NOT NULL THEN
BEGIN
DROP PROCEDURE CheckEst;
IF NULL/*TODO:OBJECT_ID(‘dbo.CheckEst’)*/ IS NOT NULL THEN
DBMS_OUTPUT.PUT_LINE(‘<<>>’);
ELSE
DBMS_OUTPUT.PUT_LINE(‘<<>>’);
END IF;
END;
END IF;
END;
Lines 1 & 4 got converted to NULL. I have many places where such code is written.
Is there any quick way to overcome such an issue? or what needs to be done in such case?

Hi,
You are using an older version of SQL*Developer. Could you download the latest 4.0.2 version available from here -
Oracle SQL Developer
and check if you still have the problem ?
Regards,
Mike

Issues in migrating from jaxb1.0 to jaxb 2.0

Hi,
I am facing following issue while trying to migrate from Jaxb 1.0 to 2.0.
I am not able to generate a java class from the <xsd:element> in jaxb 2.0. This used to work perfectly in jaxb1.0.
the schema as follows:
A. top level schema
<xs:schema
   xmlns:xs ="http://www.w3.org/2001/XMLSchema"
   xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
   xmlns:xjc ="http://java.sun.com/xml/ns/jaxb/xjc"
   jaxb:extensionBindingPrefixes="xjc"
   jaxb:version="2.0">

<xs:annotation><xs:appinfo>
    <jaxb:globalBindings generateElementProperty="false" generateValueClass="false">
      
      <xjc:typeSubstitution type="complex"/>
    </jaxb:globalBindings>
</xs:appinfo></xs:annotation>
</xs:schema>B. main schema file
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace      = "C"
           xmlns:xs             = "http://www.w3.org/2001/XMLSchema"
           xmlns                = "C"
           attributeFormDefault = "unqualified"
           elementFormDefault   = "unqualified">
<xs:element name="AAAA" type="BBBB">
    <xs:annotation>
      <xs:documentation>q2w2iug78gt8h</xs:documentation>
    </xs:annotation>
</xs:element>
<xs:complexType name="BBBB">
    <xs:sequence>
      <xs:element name="www" type="xs:normalizedString"/>
      <xs:element name="yyy" type="OCICommand" minOccurs="1" maxOccurs="15"/>
    </xs:sequence>
</xs:complexType>
</xs:schema>On compiling both these schema files I get only BBBB.java. previously we used to get AAAA.java as well.
Any help will be appreciated.
Thanks

I have found the answer to my query. I missed out the '@generateElementClass' attibute of the <jaxb:globalBindings> in my global xsd file (vendor cusotmization). by making generateElementClass="true". will generate java classes for <xs:element> also.
:)

Issue on migration from OTM 8 to 9

Hello,
I'm trying to migrate from Oracle Test Manager 8 to 9. I would like to use an old schema built on OTM 8. I've created a new Database Connection using OATS - Database Configuration in order to use my old schema. Anytime I try to log in OATS Administration Login using Administrator account, the application alert me that I'm trying to open a connection to an old version that must be updated. When I choose yes I get this error: "The Oracle Test Manager for Applications database could not be updated. Please make sure that the user has Administrator rights for the database and that the password entered is correct."
So I checked "User" table on db using this query:
SELECT * FROM "Users" where isactive = 0 and deleted = 0;
"Administator" account appears in the result list.
I've followed this guide: http://kr.forums.oracle.com/forums/thread.jspa?threadID=995410&tstart=146, so I've tried to change isactive flag of default user to 1 from 0 but nothing changed.
Can someone give me some tips?
Thank you.

Version 8 I guess was pre OATS user...
There's a 'Oracle Application Testing Data Migration Tool' under in your ATS programs menu listing. I should be used for migrations, if I recall the default DB in 8 was MSAccess but the migration tool offers migrations from different DBs also previous Oracle DBs.
I haven't used it but it might help. You still need to know the owner of your OTM schema though... Use a DB management tool to find out.
/J

Issue while migrating from File to DB based repository for SAP adapter

Hi
I recently migrated from file based repository to DB based repository.
SAP Adapter: DB repository for JCA configuration
After that I created the new targets and the jca log file showed me correct entry saying that it read from DB repository.
Thread[Thread-6,6,main] [info ] Repository URL 'jdbc:oracle:thin:@db_host:1521/fmwdbqa' resolved to repositoty type: oracle
But when I restarted the weblogic server I observed that it is again reading from the file repository.
Thread[[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [info ] Repository URL 'file:///opt/apps/Oracle/Middleware/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/config/XYZ/repository.xml' resolved to repositoty type: file
Any reason why this is happening? Any other setting required to avoid this?
Regards
Subhankar

Hi Manoj
I checked the web.xml under MW_HOME/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/iwafjca.war/WEB-INF folder. The iway.jndi is set to below :
<param-name>iway.jndi</param-name>
<param-value>eis/OracleJCAAdapter/DefaultConnection</param-value>
I checked the outbound connection settings from Admin console under below path
Home >Summary of Deployments >iwafjca > configuration
I can see that the properties IWayRepoURL, IWayRepoUser and IWayRepoPassword are set to blank here. Where exactly are these property values picked from ? Or do I need to manually edit it here in admin console itself?
Regards
Subhankar

Issue migrating from Jdev eloper 11.1.1.0.2 to 11.1.1.2.0

Hi,
I ha migrated my application and I did the following:
1. Open app in 11.1.1.2.0, I accepted all wizard default options
2. Build->clean all
3. Right clic rebuild model and view contoller projects
4. I got errors as "class not found" in my view controller, but the class are in the path. I think that is because the dependences not were correctly mapped.
5. I solved compiling each class that is not referenced and I make rebuild and 0 errores, but if I make clean again and rebuild, the errors appears again about references to class.
thanks for yours suggestions.

I have already checked the path of both projects in my applictaion, and is fine. However, checking dependencies, i found that in the Model project, was a call to a class in the ViewController project, which get some parameter needed for the EO to work. I removed that call to the ViewController class from the EO, and removed the associated import. After that, my entire application compiled.
Now I need to know hot to get a session variable from an EO class, to supply that parameter that was getting from my ViewController class before.
Thanks

Error while migrating from JDev 11.1.1.3 environment to 11.1.1.6

Hi,
I have developed a BPEL process including Human task and Business rules on JDeveloper 11.1.1.3. The human task worklist page and its project were autogenerated and then I was deploying both the projects from Jdeveloper to weblogic 10.3.3 server and it was working fine.
We needed to migrate the same project to JDev version 11.1.1.6 and for this I have imported the two projects into the new workspace and JDeveloper itself migrated the project to thie higher version.
However, while using the same deployment process and deploying on compatible weblogic server, I am facing issue while deploying worklist application and following appears on the domain log:-
There was a failure when processing annotations for application /u01/oracle/SOA/SOA_INST/user_projects/domains/base_domain/servers/AdminServer/upload/ApprovalPage/app/WorklistADFPage.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet
Failure occurred in the execution of deployment request with ID '1352977219006' for task '29'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'WorklistADFPage.war'' weblogic.application.ModuleException: Failed to load webapp: 'WorklistADFPage.war' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused By: java.lang.ClassNotFoundException: oracle.adf.library.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:108) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1370) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:452) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:497) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
In JDeveloper it says:-
Weblogic Server exception: weblogic.application.ModuleException: Failed to load webapp: "WorklistADFPage.war"
Caused by: java.lang.ClassNotFoundException: oracle.adf.library.webapp.ResourceServlet
Also when I see the libraries and classpath of my project I see ALE components jar marked in red.
My Composite gets deployed, and the issue comes only with worklist project.
Please suggest how to approach to resolve this issue.
Thanks in advance.

Hi,
actually there is no backward migration path if you used Facelets for building your pages. For page fragments you will need to manually change ui:composite to jsp:root tags. To ensure web.xml is setup correctly you should create a new project in 11.1.1.6 and copy the web.xml over (ensuring the web.xml is configured for ADF use). Probably copying the content of the JDeveloper 11g R2 project into the 11g R1 project and then fixing problems is the way to go. As said, there is no automated backward migration path
Frank

Issues after migrating from 3.0.6.6.5 to 3.0.9.8.3A

G'day All,
Over the last week or so I have performed some test migrations using copies
of our production Portal environment and here are some of the issues that I have encountered.
ISSUE 1 - Performance
Using a stopwatch (primitive, I know) I visited a few parts of our Portal and recorded timings
Performance did not improve dramatically. In fact, after the 3.0.9.8.3A patch, some things slowed right down.
I tested using a Sun Ultra 80 (2 x 450MHz CPUs) our Development host.
(I also tested using a spare Ultra 10 (1 x 333MHz) This was MUCH slower than the numbers seen below)
In all the timings below, I did the following:
1.Logged on as PORTAL30 this takes me to the Portal Home page showing the Build tab
2. Clicked on the Navigator icon
3. From the Navigator Pages section, I clicked on our company homepage
4. From the Main tab on the company homepage, I clicked on our Customer Service tab (one of many that we have)
5. Click on the Ops & Security tab (another one of ours)
6. Click on Logout
Timings are in SECONDS. I ran thru the process at least 3 times and recorded
the final 2 timings to allow for the first time thru populating caches etc.
Pre migration - Portal 3.0.6.6.5 iAS 1.0.2.0.1
Log in          4     3
Navigator     3     3
Homepage     3     3
First tab     4     3
Second tab     3     3
Logout          1     1
Post iAS migration - Portal 3.0.6.6.5 iAS 1.0.2.2.0
Log in          4     3
Navigator     3     3
Homepage     3     3
First tab     4     4
Second tab     3     4
Logout          1     1
** No significant difference
Post Portal migration - Portal 3.0.9.8.2 iAS 1.0.2.2.0
Log in          3     3
Navigator     3     3
Homepage     3     4
First tab     4     4
Second tab     3     3
Logout          1     1
** No significant difference
Post iAS Patch 1866039 Required by Portal 3.0.9.8.3A
Log in          3     3
Navigator     3     3
Homepage     4     4
First tab     4     4
Second tab     3     3
Logout          1     1
** No significant difference
Post Portal migration - Portal 3.0.9.8.3A iAS 1.0.2.2.0
Log in          3     3
Navigator     19     19 !!!!!!!!
Homepage     20     21 !!!!!!!!
First tab     3     3
Second tab     3     3
Logout          1     1
** Bringing up Navigator and the first page from Navigator now takes ages.
Analysing PORTAL30 objects using wwsbr_stats.gather_stats made no difference
to the above timings.
Anyone have any ideas about this???
Bear in mind that this slow down probably only affects me as the
developer since end users pretty much stick to the tabs on the homepage
and never need to use Navigator.
And end user login and presentation of the company homepages takes about 4 seconds.
ISSUE 2 - Fonts
During the migration, many of our developed forms/reports now contain headings/labels that
are so small as to be unreadable (eg 1 point in size)
This seems to be due to the fact that originally the fonts were sized as (-3, -2, -1, 0, +1, +2, +3)
relative sizing. This has been screwed up during migration and has ended up as fonts
being sized 1, 2, 3 points in size.
I will have to visit each form and report and set sizes accordingly.
The PEOPLE_APP application supplied by Oracle also suffers from this problem and is a little harder
to fix. (Check Metalink)
ISSUE 3 - Menu permissions
I have a couple of menus that are only viewable by certain groups.
This permission disappeared along the way leaving the menu NOT visible to anyone.
I will have to visited each menu and set permissions once again.
I hope this list may help others embarking on the same migration path.
I would highly recommend copying your production environment and practising on the copy first.
Regards,
Tony Cook
eSign Australia
[email protected]

Further to the performance problem above, I found the following bug on Metalink:
Bug Number: 2391402
PERFOMANCE DEGRADATION WITH 3.0.9.8.3 ON IE
Funnily enough, this bug was meant to be addressed by the 3.0.9.8.3A patch that I had already applied.
After reading the bug report I added the following line to httpd.conf
BrowserMatch "MSIE" nokeepalive downgrade-1.0 force-response-1.0
I am now seeing the following timings
Log in          3     3
Navigator     3     3 !!!!!!!!
Homepage     3     3 !!!!!!!!
First tab     3     3
Second tab     3     3
Logout          1     1
There is a 15 second timeout that was adding to the response times I was seeing prior
to making the change to the httpd.conf file eg. 19 seconds down to 3ish
Regards,
Tony Cook
eSign Australia
[email protected]

JCA Issue with migration from EP 6.0 SP2 to SAP NW2004s (EP 7.00 SP7)

We are currently using JCA on EP 6.0 SP2 platform to connect to SAP R/3 backend system for custom java iviews as shown below ...
Context ctx = null;
IConnectionFactory connectionFactory = null;
IConnection client = null;
IConnection aConnection = null;
try
     //Obtain the initial JNDI context
     ctx = new InitialContext();
     //Perform JNDI lookup to obtain connection factory
     connectionFactory = (IConnectionFactory) ctx.lookup("EISConnections/SAPFactory");
     connectionFactory.setConnectionTimeOut( 900 );
     IConnectionSpec spec = connectionFactory.getConnectionSpec();
     // FOR MiniP
     ((Map) spec).put("client", "100");
     ((Map) spec).put("UserName", "USER_ID");
     ((Map) spec).put("Password", "password");
     ((Map) spec).put("logonmethod", "UIDPW");
     ((Map) spec).put("Language", "EN");
     ((Map) spec).put("ashost", "10.14.17.44");
     ((Map) spec).put("sysnr", "02");
     aConnection = connectionFactory.getConnectionEx(spec);
catch (Throwable th)
     StringWriter sw = new StringWriter();
     th.printStackTrace( new PrintWriter( sw ) );
     log("Caught an exception (Throwable) : \n" + sw.toString() );
When we migrated the code, the connection to SAP R/3 system is failing. Searching servicemarketplace for some solution, we found a note 820857 and made the necessary code change for JNDI lookup from "EISConnections/SAPFactory" to "deployedAdapters/SAPFactory/shareable/SAPFactory" but we are still getting the following connection failure errors ...
(R3/BW) Failed to get connection. Please contact your admin.
com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: Nested Exception. Failed to get connection. Please contact your admin.
     at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedException(SAPConnectorException.java:107)
Also, the help link is not updated for any changes ...
http://help.sap.com/saphelp_nw04s/helpdata/en/89/8a185c148e4f6582560a8d809210b4/content.htm
I really appreciate any help being provided for solving the issue.

Hello! Bhabesh,
Could you please check your stack against mine, i am pasting that stack here.
Please let me know if you are getting the same error or something else.
FYI, i am pasting my code too. Please check if you are using the same way.
Stack
#1.5#00306EE9EE3A001A0000064F00003A28000422D070FB68FD#1164178553286#com.sap.portal.iView#sap.com/irj#com.sap.portal.iView#z10002722#42##asap86.symbol.com_NPQ_6376950#Guest#d2b1aed079f511db93d200306ee9ee3a#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/System/Server#Java###Connection Failed: Nested Exception. Failed to get connection. Please contact your admin.
[EXCEPTION]
#1#com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: Nested Exception. Failed to get connection. Please contact your admin.
     at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedException(SAPConnectorException.java:137)
     at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:184)
     at com.symbol.intr.cs.authcheck.beans.AuthorizationChecker.getConnection(AuthorizationChecker.java:182)
     at com.symbol.intr.cs.authcheck.beans.AuthorizationChecker.connectionOK(AuthorizationChecker.java:79)
     at com.symbol.intr.cs.authcheck.beans.AuthorizationChecker.isAuthorizedRunCheck(AuthorizationChecker.java:294)
     at com.symbol.intr.cs.authcheck.beans.AuthorizationChecker.isAuthorized(AuthorizationChecker.java:289)
     at com.symbol.intr.cs.authcheck.main.Controller$MyController.onCheckAuthorizations(Controller.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:324)
     at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
     at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Code
     protected IConnection getConnection(StringBuffer sb)
          throws Exception {
          Hashtable env = null;
          Context initctx = new com.sapportals.portal.prt.jndisupport.InitialContext(env);
          IConnectionSpec spec = connectionFactory.getConnectionSpec();
          spec.setPropertyValue("client", "095");
          spec.setPropertyValue("user", "Z10002722");//CPICR3Q095 - Chandu's ID: Z10002434
          spec.setPropertyValue("passwd", "initpass");
          spec.setPropertyValue("lang", "EN");
          spec.setPropertyValue("ashost", "157.235.1.24");//157.235.1.24 asap84.symbol.com
          spec.setPropertyValue("sysnr", "02");
          IConnection connection = null;
          try {
               connection = connectionFactory.getConnectionEx(spec);
          } catch (Exception e1) {
               StringBuffer exceptionMessage = new StringBuffer();
               exceptionMessage.append("<font color='red'>");
               exceptionMessage.append(
                    "<br>A connection to SAP could not be achieved.  ");
               exceptionMessage.append(
                    "The possible cause is a bad definition of the connection ");
               exceptionMessage.append(
                    "as loaded from the connection_specs.properties file.  ");
               exceptionMessage.append("Please check this file.  ");
               exceptionMessage.append("Check the user ID shown above and the password.  ");
               exceptionMessage.append("Also, check the host and system number as shown above.");
               exceptionMessage.append("</font>");
               ILogger logger =
                    PortalRuntime.getLogger(IPortalConstants.IVIEW_LOGGER);
               logger.log(e1, e1.getMessage(), Level.SEVERE);
//               throw new ConnectionFailedException(exceptionMessage.toString());
               throw new Exception(exceptionMessage.toString());
          return connection;
Thanks!
Regards,
Kishore

Issue in Migration from JDev 10.1.2 to JDev 10.1.3

Similar Messages

Maybe you are looking for