J2EE versions supported by Weblogic 11g, 12g

Hello,
Can you please direct me to a link that I can find what versions of J2EE or Java EE are reliably supported in 11g and 12g.
Thanks,
Raj

I'm sorry, I thought by mistake that you were asking about Java SE, so I sent you info about Java SE in my previous post. Here is the information about Java EE:
http://www.oracle.com/technetwork/java/javaee/overview/compatibility-jsp-136984.html
http://www.oracle.com/technetwork/java/javaee/overview/compatibility-javaee5-jsp-141098.html
(Just find "WebLogic" on the page and open the link "Tested configuration" below it).
As you can see WebLogic 12c is Java EE 6 compatible and WebLogic 11g is Java EE 5 compatible.

Similar Messages

Versions supported by Weblogic 8.1

Hi,
I am very new to java and weblogic. I am about to install weblogic 8.1 Service Pack 5. I wants to know which are best version of jdk, servlet/jsp, ejb and tomcat supported by weblogic 8.1.
Please help me ..............
Thanks & Regards
-Sandeep

Hi Sandeep,
WLS 8.1 supports the JSP 1.2 specification from Sun Microsystems. JSP 1.2 includes support for defining custom JSP tag extensions. (See Programming JSP Extensions)
WLS 8.1 also supports the Servlet 2.3 specification from Sun Microsystems.
WLS 8.1 supports the Enterprise Java Beans 1.1 and 2.0 specifications.
Please refer to the following links for additional information
http://e-docs.bea.com/wls/docs81/jsp/intro.html
http://e-docs.bea.com/wls/docs81/upgrade/upgrade51to81.html
Cheers
-raj

Xalan version support in Weblogic 5.1-- Collaborate

"Hi,We are using wls 5.1 and we are evaluating collaborate on that. I have used XPathApi(comes with xalan version 2) classes in enablers. When I run the server, Collaborate hub is looking for older version of the classes, although i have included in newer version of xerces

put the newer xerces.jar at the beginning of the classpath when invoking
weblogic in startWeblogic.cmd
"Kiran" <[email protected]> wrote in message
news:3afd3fba$[email protected]..
"Hi,We are using wls 5.1 and we are evaluating collaborate on that. I haveused XPathApi(comes with xalan version 2) classes in enablers. When I run
the server, Collaborate hub is looking for older version of the classes,
although i have included in newer version of xerces

URGENT: Is Weblogic 10.3.4 not supported for OIM 11g ?

Hi Everyone,
Is Weblogic 10.3.4 not supported for OIM 11g ?
I installe & configured all IAM suite components (OAM,OIM,OAAM,SOA) on WLS 10.3.4. I am able to start all servers including OIM. However it is unable deploy "oim". After doing some research , I found below URL which tells WLS 10.3.4 is NOT SUPPORTED for OIM 11g.
Not able start oim_server1, could not open oim url
If that is true, Is there anyway to downgrade Weblogic to 10.3.3 ?
Please provide your inputs and suggestions.
Thanks
GK

No. 11G has been released with all type of supporting infrastructure components to be residing at the same level (i.e 11G only). So you would not be able to just downgrade weblogic to any lower versions.

Weblogic 12c - J2EE version

Hello,
I am migrating our J2EE 1.4 apps from Websphere to Weblogic as part of an evaluation.
I am trying to deploy a J2EE 1.4 application into Weblogic 12c. I see strange classloader exceptions. Is this because Oracle 12 c does not support J2EE 1.4?
If yes, can you please help me on the following :
1. Where can I find the Weblogic servers vs supported J2EE versions?
2. What are the version of Weblogic app servers are suitable for J2EE 1.4?
3. I noticed Weblogic 12c has a feature called 'SmartUpgrade'. I am exploring if this will help me anyway.
Thanks in advance,
Rajesh

Hi Lawrence,
I believed backward compatiblity will be present. We don't use weblogic APIs, as this is the first time we are moving to Weblogic. The Error in the sever_0.log file is as follows:
When processing WebService module 'XXX-stp-web.war'. Failed to load servlet Class: com.XXXsolutions.stp.manager.web.ABCManagerServlet
Ignoring: unable to load class:java.lang.ClassNotFoundException: com.XXXsolutions.stp.manager.web.ABCManagerServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
When processing WebService module 'XXX-stp-web.war'. Failed to load servlet Class: com.XXXsolutions.stp.manager.web.ABCManagerServlet
Ignoring: unable to load class:java.lang.ClassNotFoundException: com.XXXsolutions.stp.manager.web.ABCManagerServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
<03-Jan-2013 15:40:58 o'clock GMT> <Error> <javax.enterprise.resource.webcontainer.jsf.config> <BEA-000000> <Critical error during deployment:
com.sun.faces.config.ConfigurationException:
Source Document: file:/C:/Projects/wlsdomain/servers/Server-0/tmp/_WL_user/XXX-stp/isz0wh/war/WEB-INF/faces-config.xml
Cause: Unable to find class 'com.sun.facelets.FaceletViewHandler'
     at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:273)
     at com.sun.faces.config.processor.ApplicationConfigProcessor.setViewHandler(ApplicationConfigProcessor.java:541)
     at com.sun.faces.config.processor.ApplicationConfigProcessor.processViewHandlers(ApplicationConfigProcessor.java:861)
     at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:334)
     at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
     Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: com.sun.facelets.FaceletViewHandler
     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 java.lang.ClassLoader.loadClass(ClassLoader.java:423)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
     Truncated. see log file for complete stacktrace
Thanks,
Rajesh

Driver OJDBC support version 8i,9i,10g,11g r2 we have not found ?

we have any database on development and try to using one more drivers and not work .
We needs driver multiple cover following with version 8i,9i,10g,11g r2
now lastest we can download ojdbc14 could connecting 8 ,9 10 only
please suggestion .
Many thanks a lot for advance .^^

I hope you are not running under Java 1.4. If you are using Java 5 or up, you can use OJDBC5 or OJDBC6 (the number indicates for which version of Java it is built). Both these driver series support connecting to the Oracle versions you mention.

Is Weblogic 11g supports for Kerberos AES/RC4 Encryption on Windows 2008 R2

Is Weblogic 11g supports for Kerberos AES/RC4 Encryption on Windows 2008 R2?
Thanks,

DES is disabled by default on 2008, could this DC be a Windows 2003? If so then this would be the expected encyption.
The following is the list of the encryption available for each Windows system
Windows 2000, XP,Windows Server 2003:
DES, RC4
         Vista
, Windows Server 2008:      DES, RC4,AES
         Windows 7 and Windows Server 2008 R2:     DES(disabled by default), RC4,AES
From:
http://blogs.msdn.com/b/openspecification/archive/2010/11/17/encryption-type-selection-in-kerberos-exchanges.aspx
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security, BS CSci
2012, 2008, Vista, 2003, 2000 (Early Achiever), NT4
Twitter @pbbergs http://blogs.dirteam.com/blogs/paulbergson
Please no e-mails, any questions should be posted in the NewsGroup.
This posting is provided AS IS with no warranties, and confers no rights.

WebLogic 11g: Weblogic-Application-Version not taken into account

Hello,
I'm trying to set up Production Redeployment on my EAR, under WebLogic 10.3.6.
However, I can't figure out how to make Weblogic-Application-Version work in MANIFEST.MF
Here is my EAR structure:
MyApplication
--- APP-INF
--- --- lib
--- --- classes
--- META-INF
--- --- application.xml
--- --- weblogic-application.xml
--- --- MANIFEST.MF <- file I update
--- WebApp1
--- --- META-INF
--- --- --- MANIFEST.MF
--- --- WEB-INF
--- --- --- classes
--- --- --- lib
--- --- --- web.xml
--- --- --- weblogic.xml
--- WebApp2
--- --- same as WebApp1
MANIFEST.MF content is the following:
Manifest-Version: 1.0
Weblogic-Application-Version: VERSION_1
The problem is that it's not taken into account when I deploy the application in the WebLogic console.
When I use staged mode, the line Weblogic-Application-Version: VERSION_1 is removed from the staged MANIFEST.MF file.
The only way to manage to version my application is to add the flag -appversion to weblogic.Deployer, but I don't want to use that on a Production environment (and it's not recommended in the documentation!).
Any idea why Weblogic-Application-Version not taken into account? I tried to add debug mode to node weblogic/debug but with no success.
Thanks by advance,
Julien

I tested it at my end and was able to redeploy it successfully with the application versions.
Are you saying that by deploying through weblogic console,the archive version is not honoring/getting picked up .is that correct?
if yes, what does your weblogic console shows for archive version,when you first try to deploy your application with the VERSION_1.
I mean,when you are on the "Optional Settings" Page.Do you see the Archive Version as VERSION_1?
Deployments >> Click on the Install >> select your application ( MyAPP)>> Install this deployment as an application >> Select deployment targets >> Optional Settngs
Example from the Optional settings Page for My application
What do you want to name this deployment?
Name: MyAPP
Archive Version:
VERSION_1
This can confirm that the application being deployed is versioned one and if it doesn't shows up,then you need to check why its not getting picked up.?
Moreover,You can enable the "deploy" debug flag to see whats going wrong in your case during the deployment process
Server > Debug > Weblogic > Deploy
Do refer the below viewlet on the Production Redeployment
http://download.oracle.com/otn_hosted_doc/wls/redeployment/wls-side-by-side-non-annotation_viewlet_swf.html

Deployment of JSR-109 Web Services on Weblogic 11g (OAS migration)

Hi.
I'm being part of an ongoing migration effort from Oracle Application Server 10.1.3.5 to WebLogic 11g (10.3.6). Some of the OAS applications use old JSR-109 Web Services, where each service has the following components:
- A SEI interface that extends java.rmi.Remote and declares the service methods, which throw java.rmi.RemoteException (e.g. ServiceSEI)
- A service implementation POJO that implements the SEI interface (e.g. ServiceImpl)
- A [Service]-config.xml file that declares the service and relates name, namespaces, packages, interface and implementation (e.g. Service-config.xml)
- A declaration of the service implementation POJO as a servlet (with mapping) in web.xml (docs says it doesn't have to be technically a servlet)
- A webservices.xml file that defines the service and references the mapping file.
- A [Service]-mapping.xml file that defines the WS-Java mappings.
All the artifacts look right according the old documentation:
- Programming Web Services for WebLogic Server, Creating a J2EE Web Service Manually: http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html
- Web Services for J2EE 1.0 Final Release Spec: http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
The Web Services work OK in OAS. When I try to deploy any of the application that contain one of that services to WebLogic, I get the following Exception:
<BEA-101216> <Servlet: "WSServlet_Procesos" failed to preload on startup in Web application: "/webapp".
java.lang.IllegalStateException: ClassNotFound co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:601)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:273)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:171)
at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:705)
at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:201)
at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:54)
at weblogic.wsee.deploy.ServletDeployInfo.createWsService(ServletDeployInfo.java:91)
at weblogic.wsee.deploy.DeployInfo.createWsPort(DeployInfo.java:372)
at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:83)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
I obviously though the EAR package given to me was incomplete, lacking the ClassNotFound related class, but the package was OK, and is exactly the same that deploys without problems in OAS.
The ClassNotFound related class is referenced in the <java-xml-type-mapping> element of the [Service]-mapping.xml file, e.g.:
<java-xml-type-mapping>
<java-type>co.com.acme.services.ServiceSEI_serviceOperation_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperationResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>result</java-variable-name>
<xml-element-name>result</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
I searched the OAs installation deployment dirs looking for the missing class and found it was present in a Jar called deployment-cache.jar. According OC4J related documentation, this Jar es auto-generated at deployment time.
Weblogic 11g documentation says that kind of Web Services will continue to run, without any changes, on version 10.3.x of WebLogic Server because the associated Web services run time is still supported in this release, although it is deprecated and will be removed from the product in future releases (http://docs.oracle.com/cd/E21764_01/web.1111/e13760/upgrade.htm). I know the right estrategy is migrate the Web Services, but right now my client needs to deploy and use them as they are. I think WL recognizes my service since internally is calling a "Deploytime109MappingHelper" class.
¿Is there any way I can deploy that kind of services to Weblogic 11g? ¿I'm I missing some required step?
As a workaround, I included the OAS generated deployment-cache.jar into the EAR to deploy in Weblogic 11g and the app deploys without errors, but I see this is not a nice solution.
Any help would be much appreciated.
Thanks,
Esteban
Edited by: salzo on Oct 30, 2012 9:54 AM
Edited by: salzo on Oct 30, 2012 9:56 AM

Hi. The [Service]-mapping.xml file is a standard "JAX-RPC mapping file" according the JSR-109 spec and WebLogic 9.2 doc ([1],[2]). That's the file that references the class. Here's a fragment:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>co.com.acme.services</package-type>
<namespaceURI>urn:Service/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>co.com.acme.services</package-type>
<namespaceURI>urn:Services/wsdl</namespaceURI>
</package-mapping>
<java-xml-type-mapping>
<java-type>co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperation</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>String_1</java-variable-name>
<xml-element-name>String_1</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
I'll take a look at the ant task.
Thank you very much.
[1]http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
[2]http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html

Deploying ADF Webapplication (10.1.3) to Weblogic 11g (10.3.4)

Hello All,
I have a web application built using jsp, struts framework and ADF business component. Currently it's deployed on oracle application server. I have requirement where it needs to be deployed on Weblogic 11g (10.3.4. or higher)
Current version of Jdeveloper/ADF we are using is 10.1.3.
According to support matrix, Oracle JDeveloper 11g Application Server Certification Matrix
its possible to deploy applicaiton developed in 10.1.3 to weblogic 10.3.4. Thats what oracle says as per above link.
Is this correct? Has anyone tried it before?
I followed the steps mentioned at Deploying The SRDemo ADF Sample Application on WebLogic Servers and installed ADF runtime as per Installing ADF Runtime Library on Third-Party Application Servers
However when trying to deploy EAR file, I am getting classnot found exception for ADF/Classes.
<30-jan-2014 0:38:51 uur CET> <Error> <HTTP> <BEA-101165> <Could not load user defined filter in web.xml: ServletContext@29344664[app:ivfwebapp module:/ivfwebapp path:/ivfwebapp spe
java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
        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 java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        Truncated. see log file for complete stacktrace
>
<30-jan-2014 0:38:51 uur CET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1391038730677' for task '0'. Error is: 'weblogic.appl
weblogic.application.ModuleException:
        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
        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 java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        Truncated. see log file for complete stacktrace
>
<30-jan-2014 0:38:51 uur CET> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'ivfwebapp'.>
<30-jan-2014 0:38:51 uur CET> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'ivfwebapp'.>
<30-jan-2014 0:38:51 uur CET> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
        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 java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        Truncated. see log file for complete stacktrace
>
I created ADF directory under WLS home and copied required ADF related jars under lib and jlib folder. Do I have to perform any more steps.
It's also mentioned on Deploying The SRDemo ADF Sample Application on WebLogic Servers
Class not found on oracle/adf classes when deploying the application
Verify that the setupadf.cmd file can be located by the WebLogic starting script.
Verify that you started the right domain with the right startup script.
Where can I find this cmd file and what needs to be in there? I am new to weblogic area. Can you please provide more details on this?
My question to ADF experts - Is it possible to deploy web application with ADF business component (only ADF BC) 10.1.3 to Weblogic 10.3.4?
If yes, could you please guide on how to accomplish it?
Note that application has ADF BC only no adf faces or jsf.
Thanks in advance.
Kind regards
Amol Relkar

Hello Shay,
Thanks you for your quick response.
Yes, my application works fine in embeded OC4J in Jdeveloper 10.1.3.
It also runs well on Oracle applicaition server v9.0.4.3.0 which there on test environment.
Current JDeveloper (10.1.3) doesn''t support weblogic 10.3.4 it seems, so I couldn't use ADF Runtime Installer wizard, when I do so it says - Selected directory is not a web logic home directory. So I followed steps manually mentioned in the same link - Installing ADF Runtime Library on Third-Party Application Servers
Basically I copied all mentioned jar files under <Weblogic_home>\ADF\lib and <Weblogic_home>\ADF\jlib
This is the correct way right?
If not could you please elaborate more on this.
Note: I have just ADF BC in my applicaiton no faces stuff.
Thanks in advance,
Kind Regards
Amol Relkar

Trying to deploy OIM on WebLogic 11g

I'm trying to deploy OIM into a WebLogic 11g server (specifically, Oracle Internet Directory) running on RedHat 64 bit.
The purpose of this is to support a Discoverer deployment.
When trying to install Oracle Internet Directory, I am stuck on the screen where it asks you for the Realm. (NOTE: I am trying to deploy OIM into a new domain on the WebLogic server).
I have tried tying different things in here, like 'myrealm' or 'dc=myrealm' or 'dc=us,dc=Acme,dc=com', and I keep getting errors:
INST-5165: Error in validating Realm.
INST-07037: text field value contains one or more invalid characters or the value is not in proper format.
What should I be typing in here? I'm stuck...

Hey there,
So can you please answer the questions stated below:
1.) Which version of OIM did you use to interact with weblogic application server 10.3.1 ?
2.)
Also can we upgrade from weblogic application server 10.3 to 10.3.1(11gR1) ?
Or
We just have to install the weblogic application server 11gR1 separately itself irrespective of 10.3(10gR3) ?
Thanks,
- oidm.

BPM standalone and J2EE versions

What is the diffrence between BPM standalone and J2EE versions
and
What are the advantages of Using J2EE Version over standlone?
In configuration document it is mentioned that we need to deploy wlj2eedeployer.ear on weblogic server.
Why this deployment?
Thanks

Depending on your needs, the Engine can be deployed using two different implementation styles.
Standalone Oracle BPM Enterprise Engine
Oracle BPM can be deployed in a standalone environment running on a JVM. This is the original version of the Engine and has been around for 10 years.
The benefits of deploying processes to Enterprise Standalone are:
<li> It does not require an application server J2EE container to run. This means a lower cost of entry if you do not already own WebLogic or WebSphere J2EE application servers.
<li> It is simple to install and administer.
Enterprise Standalone uses a simple active/standby failover mechanism. When the active engine starts, it immediately registers in the Oracle BPM Directory that it is the primary engine. When the standby engine starts on another machine, it sees that another engine has already registered as the active server in the Oracle BPM Directory. Since the active engine is already up, the standby knows that it needs to ping the primary engine periodically to ensure it is still up. If the standby engine fails to get a response from the active engine, the standby notifies the Directory that it is now the active engine. When what was previously the active primary engine restarts, it notifies the Directory that it has restarted, sees that another server is now the primary and then starts as the secondary.
J2EE Application Server Oracle BPM Enterprise Engine
Oracle BPM Enterprise engines can also run on a J2EE application server within WebLogic and WebSphere containers.
Oracle BPM Engines running on a J2EE Application Server support active clustering. This means that as loads increase over time, new nodes can be added making the environment more scalable over time.
With the J2EE Application Server environment automatic failover is automatically provided across nodes.
Finally, in answer to your last question - the deployed wlj2eedeployer.ear is useful because this lets you stop and start the Engine and deploy projects from the simple (ok - somewhat simple) Oracle BPM Process Administrator tool.
Hope this helps,
Dan

Oracle Retail J2EE version

Hi All,
Can any one advise me Java version used in RIB 13.1 & RPM 13.1. (Java version and J2EE version). Is Annotations been used in the same?
Regards,
SK

check e.g. document 1081376.1 on oracle support:
RIB 13.1.1 - Oracle Application Server 10g 10.1.3.4
RPM 13.1.2 - Oracle Application Server 10g 10.1.3.4
The Oracle Application Server (this is not BEA Weblogic) provides the containers to run the J2EE applications in.
Please see relevant OAS version's documentation for the applicable J2EE version.
Best regards, Erik Ykema

WebLogic 11g EAR EJB Classpath and class loaders

All,
I have been having issues migrating Spring based EJB applications from OC4J to WebLogic 11g (10.3.1). I have been in communication with Oracle who has suggested a work around however I am keen to see if anyone else can suggest a solution.
The application is dependant on stateless session EJB beans that communicate with a Spring managed service tier to perform the business logic and database access. PitchFork is used to inject the Spring managers into the EJB’s using the spring-ejb-jar.xml configuration file. Note originally I was using the SpringBeanAutowiringInterceptor however I could not get this to work. See WebLogic 11g and Spring beens injected into EJB for details.
When the application is deployed packaging all the dependant jars within the APP-INF\lib folder I get a verity of errors from the following InvalidClassException, NoSuchMethodError, AbstractMethodError and IllegalArgumentException. I am using Spring 2.5.3 to match the supported WebLogic version. Note within the EAR application.xml the library-directory is set to APP-INF/lib. The issue appears to be Spring, PitchFork, commons-logging and aspectj libraries are being loaded form WebLogic and do not have visibility on jars within the application or have been modified when bundled for WebLogic. An example of this is the PitchFork jar within WebLogic has been changed excluding the spi package resulting in java.lang.ClassNotFoundException: org.springframework.jee.spi.PitchforkUtilsImpl errors.
Moving the jars to the domain library path does not resolve any of the issues. I have been unable to successfully deploy the application picking up the application jars using the prefer-application-packages configuration.
Oracle has advised me to deploy the libraries into the WebLogic system classpath by modifying the startWebLogic command to load the libraries into the classpath. I am concerned that modifying the system classpath will result in an unstable WebLogic server as I will be replacing modified jar files packages with WebLogic (such as PitchFork). This will also limit the applications that can be deployed within the server as each application must use the same libraries and versions (as the application ibraries are leing ignored).
Has anyone else hit this issue and corrected it? Can anyone think of an alternative solution?
Regards
Neil

Hi,
I am in the process of updating the tracking bug# 331569 with copies of the eclipse EAR/WAR projects and the EAR for these scenarios. Here are some details on how I got past the 2nd CCE on the org.eclipse.persistence.jpa.PersistenceProvider class (not the javax one)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=331569
Essentially an SE persistence unit running both JPA 2.0 api and the 2.0 XSD schema work fine. I will next retest the EE case with variations of the 3 types of injection on the SSB or Servlet.
Update: There are 3 (possibly 4) issues here (all of these may become obsolete when the next WLS version ships)Initially I got the same 2.0 schema error and the ClassCastException on org.eclipse.persistence.jpa.PersistenceProvider
It turns out that my import of the 2 eclipse projects from my bug # 296271 for WebLogic 10.3.2.0 lost their facets(specifically the dynamic web facet) because I associated them with a different WebLogic 10.3.3.0. - this caused the CCE I was experiencing like Sri.
Anyways, after creating an EAR/Web project combination from scratch in eclipse associated with the 10.3.3.0 instance - I predeployed/deployed/ran fine - even with the 2.0 schema - in SE bootstrap mode (no EE yet).
Reproduction Procedure:
redoing project from scratch as I noticed that the war was not at the root of the ear - it was a jar in the app-inf/lib dir - my imported eclipse project was not referenced correctly as a web module facet- create empty EAR and WAR project with references
- download and open my EAR and WAR project code from bug # 296271
https://bugs.eclipse.org/bugs/show_bug.cgi?id=296271
- do essentially all the steps in the page below (I paraphrase for re-verification)
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#DI_1.1:_Alternative_3:_Application_Level_Shared_Library_-InUse
- copy applicationService, entity and FrontController servlet code into new projects
- create persistence.xml and MANIFEST.MF manifest in src\META-INF
- update manifest
Class-Path: APP-INF/lib/eclipselink.jar
APP-INF/lib/javax.persistence_2.0.0.v200911041116.jar
- copy both javax.persistence 2.0 and eclipselink 2.x jars to APP-INF/lib
- change ordering of WebLogic library modules classpath reference (javax.persistence 1.0) to ear reference (2.0 version)
- update web.xml with servlet tags
- update weblogic.xml with new context root
- make the persistence unit name the same in persistence.xml and ApplicationManagedService
- update weblogic-application.xml with prefer-application-packages overrides
<wls:prefer-application-packages>
<wls:package-name>javax.persistence.*</wls:package-name>
<wls:package-name>org.eclipse.persistence.*</wls:package-name>
</wls:prefer-application-packages>
- enable server redirect logging

<property name="eclipselink.logging.logger" value="DefaultLogger"/>
- start WebLogic 10.3.3.0
- deploy (run on) server from eclipse or export ear to auto deploy directory
1) JPA 2.0 XSD usage on 10.3.3.0
- I reproduced this issue with a bad EAR
- was able to use the 2.0 schema within the WAR-only application managed EAR
persistence.xml<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">

<persistence-unit name="example2" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>localJTA</jta-data-source>
<class>org.eclipse.persistence.example.business.Cell</class>
<shared-cache-mode>NONE</shared-cache-mode>
<properties>
<property name="eclipselink.target-server" value="WebLogic_10"/>
<property name="eclipselink.logging.level" value="FINEST"/>
<property name="eclipselink.target-database" value="Derby"/>

<property name="eclipselink.logging.logger" value="DefaultLogger"/>



</properties>
</persistence-unit>
</persistence>
2) CCE on JPA provider implementation class
Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit example2: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider
- I reproduced and fixed this one (was Eclipse project facet issue) - EAR was wrong
- was able to run JPA 2.0 code fine on an SE PU (predeploy/deploy together)
- EE injection should not work but I will post an example EAR anyway
log[EL Example]: enterprise: JPA 2.0 Metamodel: MetamodelImpl@56287508 [ 3 Types: , 1 ManagedTypes: , 1 EntityTypes: , 0 MappedSuperclassTypes: , 0 EmbeddableTypes: ]
3) CCE on JPA spec interface class
- I could not reproduce this one
Re: WebLogic 11g EAR EJB Classpath and class loaders
Error processing persistence unit PT of module pt: Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit PT: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider cannot be cast to javax.persistence.spi.PersistenceProvider
4) CCE on fallback Kodo JPA provider (if an invalid say 2.1 JPA XSD schema is referenced)
java.lang.ClassCastException: kodo.persistence.PersistenceProviderImpl
at javax.persistence.Persistence.findAllProviders(Persistence.java:186)
java.lang.NoSuchMethodError: javax/persistence/EntityManager.getMetamodel()Ljavax/persistence/metamodel/Metamodel;
- reproduced by using the 1.0 javax.persistence jar (but named as the 2.0 one in APP-INF/lib)
- fixed by using either the 1.0 or 2.0 JPA XSD schema and using the correct 2.0 spec jar
thank you
/michael

Database connection error in Weblogic 11g

Hello Everyone,
I am new to this forum and Weblogic. I am in the process of migrating a big application from Weblogic 8.1 to Weblogic 11g. I am facing a issue with JDBC Commit. I am getting following exception while trying to commit
####<Feb 18, 2010 1:11:51 PM EST> <Debug> <JTAPropagate> <PPXP2CE951B506> <AdminServer> <ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <3de6adeed2d219bd:-1c9bd9a6:126e245ecb6:-7fff-0000000000000010> <1266516711438> <BEA-000000> <java.lang.Exception: DEBUG: receiveRequest, tx=Xid=BEA1-0000957A69A07E5F133C(16499456),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=300,XAServerResourceInfo[demoPool_cashlinkdomain]=(ServerResourceInfo[demoPool_cashlinkdomain]=(state=ended,assigned=none),xar=demoPool,re-Registered = false),SCInfo[cashlinkdomain+AdminServer]=(state=active),properties=({}),local properties=({weblogic.jdbc.jta.demoPool=[autoCommit=false,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=demoPool,appname=null,moduleName=null,connectTime=187,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=false,lastSuccessfulConnectionUse=1266516711423,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:310)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:344)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:433)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1584)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1357)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:438)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:395)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
at com.mycompany.res.services.util.DatabaseHelper.getConnection(DatabaseHelper.java:109)
at com.mycompany.res.services.util.DatabaseHelper.getConnection(DatabaseHelper.java:46)
at com.mycompany.res.services.security.ejb.LoginManagerEJB.login(LoginManagerEJB.java:64)
at com.mycompany.res.services.security.ejb.LoginManagerEJB_z7om1c_EOImpl.login(LoginManagerEJB_z7om1c_EOImpl.java:573)
at com.mycompany.res.services.security.ejb.LoginManagerEJB_z7om1c_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
,currentThread=Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={},supportIsValid=true]}),CoordinatorURL=AdminServer+10.240.15.248:7001+cashlinkdomain+t3+)
at weblogic.transaction.internal.TxDebug.debugStack(TxDebug.java:60)
at weblogic.transaction.internal.TransactionManagerImpl.receiveRequest(TransactionManagerImpl.java:1366)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:287)
at weblogic.rmi.cluster.ClusterableServerRef.dispatch(ClusterableServerRef.java:242)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1138)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1020)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:240)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:882)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:453)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:322)
at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:298)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
What is going wrong with this?
I get the following error every time Weblogic is trying to do database connection check
####<Feb 18, 2010 1:35:40 PM EST> <Debug> <JTA2PC> <PPXP2CE951B506> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-028CACE03896> <3de6adeed2d219bd:-1c9bd9a6:126e245ecb6:-7fff-00000000000000c6> <1266518140849> <BEA-000000> <BEA1-028CACE03896: JDBC Internal: TX[BEA1-028CACE03896] committing-->committed
java.lang.Exception: DEBUG
     at weblogic.transaction.internal.TransactionImpl.setState(TransactionImpl.java:1711)
     at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:2945)
     at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2737)
     at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2657)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:285)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
     at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:286)
     at weblogic.jdbc.common.internal.ConnectionEnv.testInternal(ConnectionEnv.java:734)
     at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:704)
     at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:487)
     at weblogic.common.resourcepool.ResourcePoolImpl.testResource(ResourcePoolImpl.java:2260)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1601)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1507)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496)
     at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:1942)
     at weblogic.common.resourcepool.ResourcePoolImpl.access$800(ResourcePoolImpl.java:40)
     at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2368)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user12640178 on Feb 18, 2010 10:36 AM
Edited by: user12640178 on Feb 18, 2010 10:38 AM

Priya,
Thank you so much for your response. I did test my database source from console and on the console it reported the test was successful, where in the admin logs has same exception logs. I did try creating a non XA connection and it did not have these errors. But my application did raise same exception while doing transaction.
The application has around 250 EJB's that are written long ago and they all comply to EJB 1.1 spec. I am in the process of investigating the level of support for EJB 1.1 in Weblogic 11g.
- Kasi

J2EE versions supported by Weblogic 11g, 12g

Similar Messages

Maybe you are looking for