Upgrading WebLogic 7.0.2 to WebLogic 7.0.4

Hi,
I have WebLogic 7.0.2 running on Windows. I want to upgrade it to 7.0.4 (SP4).
I downloaded the service pack 4 (SP4) from support side. However, when i run
the installter, it says "Installer is not compatible with the installed product.
Your product directory contains installed component that are not available in
the current installer. Please check your installer to ensure it matches the product
distribution on your system." I made sure that i downloaded patch for WebLogic
server and that it was in right geographical region(North America)......Not sure
why i am gettting this message. Also, i've set up cluster environment, any suggestions
on how i should proceed with upgrading to SP4 would be really helpful.
Thank you
nita

Remove WebLogic Server sp2
and install WebLogic server sp4
thanks,
Deepak
"Nita" <[email protected]> wrote:
>
Hi,
I have WebLogic 7.0.2 running on Windows. I want to upgrade it to 7.0.4
(SP4).
I downloaded the service pack 4 (SP4) from support side. However, when
i run
the installter, it says "Installer is not compatible with the installed
product.
Your product directory contains installed component that are not available
in
the current installer. Please check your installer to ensure it matches
the product
distribution on your system." I made sure that i downloaded patch for
WebLogic
server and that it was in right geographical region(North America)......Not
sure
why i am gettting this message. Also, i've set up cluster environment,
any suggestions
on how i should proceed with upgrading to SP4 would be really helpful.
Thank you
nita

Similar Messages

Upgrading Weblogic 8.1, SP2 to Weblogic 8.1, SP6

wanna to the code changes that are required in web application while upgrading Weblogic 8.1, SP2 to Weblogic 8.1, SP6.

I am currently conducting the same type of upgrade. We have Platform 8.1 SP2 installed. We would like to upgrade to SP3, but I was not sure if any patches were required before the upgrade. After several dicussions with BEA Technical Support, here is what I learned.
To upgrade 8.1 SP2 to SP3, you must first install the following patch...
http://dev2dev.bea.com/products/wlplatform81/patch/wlplat81sp2_patch.jsp
...then use SmartUpdate to upgrade the SP3.
If you choose to fully install 8.1 SP3, then you do not need to install the patch because 8.1 SP3 includes the pacthes. Installing the patches would make no difference anyway since the SP2 installation would be deleted to make room for the SP3 installation. This option is not an upgrade, it is a full installation.
Hope it helps!
Raffi

Migrate source from weblogic 8.1.5 to weblogic 9.2

Hi,
I have to migrate an application running on weblogic 8.1.5 to weblogic 9.2
I have read multiple documents on how to upgrade the domain with wizard and with the database.
But i dont know how to convert the .jpf pageflows to .java pageflows.
Can anybody point to what wizard/tool i have to use

Open the workshot, create any workspace.
then go to import->Other->Select workshop 8.1 application. This will upgrade your code and import you 8.1 app in to 9.2 app.
Make sure that all page flow JSPs has been upgraded correctly. There should not be any and BEA taglib used for netui tags. They are all changed to Beehieves.
If you still see that JSPs are using bea tag libs, then select the project, right click on it and select upgrade.
I hope this helps.

After moving from weblogic 10.0.0 to Weblogic 10.3.3 - JMSException

After moving from weblogic 10.0.0 to Weblogic 10.3.3, web-application began to raise next exception:
<Dec 4, 2012 3:52:05 PM CET> <Error> <HTTP> <pl-1> <traffic-1> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1354632725104> <BEA-101017> <[ServletContext@518010907[app:XXXX-XXXX module:/XXXXXX-connector-servlet path:/XXXXXX-connector-servlet spec-version:2.5]] Root cause of ServletException.
javax.jms.JMSException: [JMSPool:169801]The JMS method setMessageListener may not be called inside an EJB or servlet
at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22)
at weblogic.deployment.jms.WrappedMessageConsumer.preInvocationHandler(WrappedMessageConsumer.java:116)
at weblogic.deployment.jms.WrappedMessageConsumer_weblogic_jms_client_WLConsumerImpl.setMessageListener(Unknown Source)
at XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.createAndStart(OperatorMessageSession.java:174)
at XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.getWork(XXXXXXXXXServlet.java:265)
at XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.doRequest(XXXXXXXXXServlet.java:168)
at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:100)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3700)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3664)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2276)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2175)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1452)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Could anybody help me with this problem? Maybe there are any standard ways to fix this?

I've rebuilt my web-application using MDB. For now I got new exception:
####<07.12.2012 16:03:06 FET> <Info> <EJB> <pc-XXXXXX> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-00340877198035A73969> <> <1354885386932> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@14df37f threw exception: javax.ejb.EJBTransactionRolledbackException: EJB Exception: : java.lang.ClassCastException: com.XXX.XXXX.XXXXXX.persistence.OperatorBean cannot be cast to com.XXX.XXXX.XXXXXX.persistence.SwitchboardBean
     at com.XXX.XXXX.XXXXXX.SwitchboardDataImpl.initialize(SwitchboardDataImpl.java:147) // itsSwitchboardBean = itsEntityManager.find(SwitchboardBean.class, switchboardNumber);
     at com.XXX.XXXX.XXXXXX.SwitchboardDataImpl.create(SwitchboardDataImpl.java:86)
     at com.XXX.XXXX.XXXXXX.SwitchboardDataEJB.create(SwitchboardDataEJB.java:64)
persistence.xml:
...     <persistence-unit name="xxxSwitchboard_PU" transaction-type="JTA">
          <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<jta-data-source>jdbc/xxSwitchboard</jta-data-source>
<non-jta-data-source>jdbc/xxSwitchboard</non-jta-data-source>
          <class>com.XXX.XXXX.XXXXXX.switchboard.persistence.OwnerBean</class>
          <class>com.XXX.XXXX.XXXXXX.switchboard.persistence.OperatorBean</class>
          <class>com.XXX.XXXX.XXXXXX.switchboard.persistence.SwitchboardBean</class>
          <class>com.XXX.XXXX.XXXXXX.switchboard.persistence.CallBean</class>
          <exclude-unlisted-classes>false</exclude-unlisted-classes>
     </persistence-unit>...
@Entity
public class OperatorBean extends OwnerBean
@ManyToOne(optional = true, fetch = FetchType.EAGER)
private SwitchboardBean switchboard;
@Entity
public class SwitchboardBean extends OwnerBean
@OneToMany(mappedBy = "switchboard", cascade = CascadeType.PERSIST, fetch = FetchType.LAZY)
private List<OperatorBean> itsOperators = new ArrayList<OperatorBean>();
Seems that it also happened due to updating weblogic version. Could you please advice me how to fix this issue?

WebLogic 9.2 MP1 - NoClassDefFoundError: weblogic/xml/domimpl/Saver

Hello,
I'm currently experiencing the following error in our production WebLogic environment. Curiously, the same WAR file deploys and works fine on our QA and STAGE servers. I must admit that my debugging knowledge of WebLogic is limited, but I have checked the obvious things (same version of WebLogic on all servers, same JAR files present on all, etc).
The error occurs when trying to generate a WSDL for a web service. The error is as follows:
####<Oct 16, 2008 6:46:59 PM BST> <Error> <HTTP> <lxxxxxxxxx.xxxxx.com> <xxxxxx_16621_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1224179219556> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@5ebaa3 - appName: 'AJPServices', name: 'AJPServices.war', context-path: '/AJP/AJPServices'] Root cause of ServletException.
java.lang.NoClassDefFoundError: weblogic/xml/domimpl/Saver
at weblogic.wsee.wsdl.WsdlDefinitions.write(WsdlDefinitions.java:581)
at weblogic.wsee.wsdl.WsdlDefinitions.write(WsdlDefinitions.java:569)
at weblogic.wsee.server.servlet.WsdlRequestProcessor.writeWsdl(WsdlRequestProcessor.java:146)
at weblogic.wsee.server.servlet.WsdlRequestProcessor.process(WsdlRequestProcessor.java:81)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:173)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:176)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Any suggestions would be most appreciated.
Thanks,
Sam
Edited by: user3634124 on 17-Oct-2008 04:41 (Fixed typos)

Hey Sam,
Are you using the same kinda startup means ?
(NodeManager / Regular Scripts)
If you created your application the same way on all environments, you could try to use the script from QA to production (means you'll have to do it by night :) ) or in the other way : try your production startup script in the QA env.
Else, the good old-fashioned way : compare both config.xml with WinCompare or BeyondCompare or anything that does the job.
Make also sure you don't have any XML Registry declared and that your domain/lib directories look alike.
Hope this helps.

Has anyone gotten OAM/WebLogic SSPI to work w/WebLogic Portal Server 9.2?

Hi,
I was wondering if anyone here has been able to get the WebLogic SSPI (10.1.4.0.1) working with WebLogic 9.2 (on Solaris 10)?
I've gotten it installed, but when I switch from the default "myrealm" WebLogic realm to the "NetPointRealm", WebLogic will no longer start.
After enabling security debugging in WebLogic, it appears that the user that I'm using with the startup is authenticating properly with OAM, but then that user is not getting the WebLogic "admin" role, which then causes the WebLogic boot to fail.
I have the "admin" role in WebLogic mapped to the "Administrators" group OR the "BEA_Administrators" group, and in OAM, the user is a member of both groups, and in the WebLogic security debug, I can see that the groups are being returned, but the group names are somewhat strange (extra characters), and that may be why the role mapper may be failing (it returns "Anonymous" role).
Jim

Hello
I am also facing problems with OAM 10.X to work with weblogic 9.2 on Solaris 10.
Presently after instalation & initial configuation, when i enable Netpoint realm, server is not starting. But i can see weblogic boot user getting authenticated successfully in access server audit logs. After switching to debug mode - server startup throws error :
<Throwing LoginException(NRE005 : Invalid member weblogic)>
Can you please let me know how did you resolve your problem. It might give me a direction to debug.
Thanks
Sumit

Migration weblogic portal 4.0 to weblogic portal 8.1

I am trying to migrate weblogic portal 4.0 to weblogic portal 8.1. I need help
how to do this ?
thanks

I am trying to migrate weblogic portal 4.0 to weblogic portal 8.1. I need help
how to do this ?
thanks

Cannot communicate from weblogic 10.3.5 to weblogic 8.1.4 (OIM 11gR1)

Hi all,
when i run java class adapter in oim 11gR1, which contain ejb class from other weblogic(8.1.4), i facing problem that request which i run cannot finish or process is looping forever.
my code :
public String create(){
SecurityMngr = (SecurityManager) connMthdDsms.connectionForDsms().get("a");
success = SecurityMngr.addUser(uvo);
if (success)
result = "C";
does error is about connection between weblogic 10.3.5 with weblogic 8.1.4. or other?
i use OIM 11gR1 bp7, Weblogic 10.3.5,
regards

Hi all,
when i run java class adapter in oim 11gR1, which contain ejb class from other weblogic(8.1.4), i facing problem that request which i run cannot finish or process is looping forever.
my code :
public String create(){
SecurityMngr = (SecurityManager) connMthdDsms.connectionForDsms().get("a");
success = SecurityMngr.addUser(uvo);
if (success)
result = "C";
does error is about connection between weblogic 10.3.5 with weblogic 8.1.4. or other?
i use OIM 11gR1 bp7, Weblogic 10.3.5,
regards

Difference between WebLogic 6.1 Domain and WebLogic 7.0 Domain

What is most reliable way of differentiating WebLogic 6.1 Domain with WebLogic
7.0 domain? WebLogic 6.1 Domain meaning interrelated set of WebLogic 6.1 servers.
A server in a domain listed within config.xml when started with WebLogic 6.1 binaries
become WebLogic 6.1 server and when started with WebLogic 7.0 binaries become
WebLogic 7.0 server.
Is there any thing in config.xml file that differentiate the domain affront?

I think in ur classpath /weblogic classpath ,u have the jar file of weblogic5.1. make sure to remove all classpath setting of weblogic5.1

Programming Weblogic with jmx without using weblogic api?

Hi,
I want to know if it is possible to program weblogic management service without
using weblogic api but just rely on standard JMX interface and methods.
Currently, I am relying on weblogic api weblogic.jndi.Environment and weblogic.management.MBeanHome
interface to get the context and access the MBean Server subsystem. Can I find
the equivalent using jmx?
My code is as follows:
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(username);
env.setSecurityCredentials(password);
Context ctx = env.getInitialContext();
MBeanHome home = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
String domain = home.getDomainName();
homeServer = home.getMBeanServer();
Thank you.

Hi Ryan,
I have looked through the documentation.
It told me that I need to use weblogic.management.MBeanHome interface to get MBeanHome
and from there then I can only use jmx interface.
I presume it is not possible not to use weblogic.jar if I want to establish the
initial connection with Weblogic server?
Thanks.
ryan upton <[email protected]> wrote:
YongLeong wrote:
Hi,
I want to know if it is possible to program weblogic management servicewithout
using weblogic api but just rely on standard JMX interface and methods.
Currently, I am relying on weblogic api weblogic.jndi.Environment andweblogic.management.MBeanHome
interface to get the context and access the MBean Server subsystem.Can I find
the equivalent using jmx?
My code is as follows:
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(username);
env.setSecurityCredentials(password);
Context ctx = env.getInitialContext();
MBeanHome home = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
String domain = home.getDomainName();
homeServer = home.getMBeanServer();
Thank you.I think you'll find your answer here:
http://edocs.bea.com/wls/docs81/jmx/index.html
HTH
~Ryan

Can weblogic workshop be installed without weblogic server

I was trying a custom installation to install weblogic workshop 8.1 without weblogic server. But, when I only choose weblogic workshop, it still picks the weblogic server to install.
I want to understand can we just have weblogic workshop installed on various machines, so that we can build on various machines and finally deploy them all to a single server??
Any help for me to understand this will be much appreciated.
Note: I've installed a evaluation version of the software, not sure if that makes any difference..

Has anyone else solved this problem? We too are experiencing the same problem.
We are trying to build a .JWS file from within an ANT build script. The build script compiles the site into a single EAR file that should contain a deployable and usable JWS component, however it obviously does not.
If anyone has a solution, please let us know. We're facing a code freeze on this project by this Friday and really need some help.

Upgrade weblogic 12.1.1 to weblogic 12.1.3 in a different hosts

Hello.
I need your help with this case, when I try to migrate a domain (Weblogic 12.1.1) in a new server (with weblogic 12.1.3), I have this error:
sc-saswebD0-3>(ora09378):/orasoft/product/middleware/wlserver_12.1/wlserver/common/bin>./unpack.sh -template=/orasoft/dbprocs/template/pck_sastest.jar -omain=/orasoft/product/middleware/user_projects/domains/SASWebtest
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
<< read template from "/orasoft/dbprocs/template/pck_sastest.jar"
>> fail: read template from "/orasoft/dbprocs/template/pck_sastest.jar"
Required component home not found for component 'WebLogic Server' version '12.1.1.0' in the MW_HOME: /orasoft/product/middleware/wlserver_12.1
Can you helpme with that?
Regards,
Milton

Thank you Helios.
But when I searched in metalink, i found the following information for upgrading 12.1.2 to 12.1.3
Please correct me if i am wrong.
1.Follow Path E in database preparation guidelines doc id:761570.
2.Apply R12.AD.B.delta.3 patch 9239809.
3.Apply Oracle Applications Technology 12.1.3 Product Family Release Update patch 8919491.
4.Apply Oracle Workflow and Oracle Application Object Library Patches. (Required)
1.
Apply the following mandatory patch:
9869602:R12.OWF.B, Patch 9869602
9888158:R12.FND.B, Patch 9888158
5.Apply Oracle E-Business Suite Applications Technology Online Help Patch 9400185
Thanks,
Kavitha

How to upgrade to jpa 2.0 in weblogic 10.3.0.0

We are using weblogic server 10.3.0.0.For fixing a bug,we need to upgrade to JPA 2.0/Eclipse link 2.x.Right now we are using JPA 1.0/Eclipse link 1.0.1
Please advise what are the ways to upgrade.
I came to know that one of the ways is applying patch on server.Is the 9J3A patch should be applied.Will change in version to 2.0 in persistence also be required to upgrade.

We are using weblogic server 10.3.0.0.For fixing a bug,we need to upgrade to JPA 2.0/Eclipse link 2.x.Right now we are using JPA 1.0/Eclipse link 1.0.1
Please advise what are the ways to upgrade.
I came to know that one of the ways is applying patch on server.Is the 9J3A patch should be applied.Will change in version to 2.0 in persistence also be required to upgrade.

JDEV upgrade no compatible with previuos version WebLogic

I've just tried to upgrade JDev since I am experiencing some errors and I got this message from the installer
** The product maintenance level of the current installer (WebLogic Server:10.3.2.0) is not compatible with the maintenance level of the product installed on
** your system (WebLogic Server:10.3.1.0) . Please obtain a compatible installer or perform maintenance on your current system to achieve the desired level.
I'm not going to upgrade all system for JDEV, any suggestion for a work around?

Set up your phone as new & do the software update. Once the update is complete, go to Settings>General>Reset and choose Erase all content and settings.
The next time around, you can restore from your backup.
~Lyssa

Help needed on upgrading portal application from sp3 to weblogic portal 10

Hi Guys
I have an application which is currently running on BEA Weblogic Portal 8.1 sp3. We need to upgrade our application from 8.1 sp3 to BEA Weblogic 10 version.
(1) Is there any way for upgradation from 8.1 sp3 to portal 10 directly or do I need to upgrade it from sp3 to sp4 and then from sp4 to portal 10? Pls clarify?
(2) How reliable are the BEAs automated scripts for retaining the personalization/customization of my application on sp3 to upgraded version i.e portal 10?
(3) I believe, we do not need to do any coding/design changes/architectural changes into my application for this upgrade.
Any help on this will be highly appreciated
Thanks
Jameel

1) I believe only sp4 and later to weblogic 10 is supported (http://www.bea.com/content/news_events/white_papers/BEA_WL_Portal10_ds.pdf)
so yes i think you need to upgrade from sp3 to a later version of the service pack
2) You tell us :)
3) Depends on your application and the features you have used. E.g. I believe Content management has changed between sp3 and what 10 supports.
regards
deepak

Upgrading WebLogic 7.0.2 to WebLogic 7.0.4

Similar Messages

Maybe you are looking for