Deploying Analyzer 7.0.1 on Weblogic 8.1

After successfully installing the software, I logged in to the Weblogic console and tried to deploy the new application. I set the location to C:\Hyperion\Analyzer\Analyzer70.ear. I get the confirm page stating the application will be deployed to the Analyzer server and then I click Deploy and the deployment fails with the following error: --------------------------------------------------------------------------------------------------------------------Exception:weblogic.management.ApplicationException: prepare failed for /Analyzer7_Server Module: /Analyzer7_Server Error: Could not load /Analyzer7_Server: weblogic.servlet.jsp.JspException: (line 1): Error in using tag library uri='HTMLClient' prefix='hya': cannot find tag class: 'com.hyperion.analyzer.htmlclient.tags.RelatedContentEventTag'--------------------------------------------------------------------------------------------------------------------Does anyone know what could be causing this error? Any advice would be greatly appreciated.Thank you,

I have found out the path in is on patch 7.1.0.8 path in directory repository in file sqlscripts.zip.I have created the repository from this files and repository works again!No more help is needed.

Similar Messages

How to create and deploy a simple jstl applicaton in weblogic 10.3.3

How to create and deploy a simple jstl applicaton in weblogic 10.3.3

1) Since JSTL libraries are provided as Web application libraries, they must be deployed before the Web application that is using JSTL functionality is deployed. The libraries can be deployed using the Administration Console or with the command-line weblogic.Deployer tool.
Here’s an example of deploying a JSTL 1.2 library using the weblogic.Deployer command-line:
java weblogic.Deployer -adminurl t3://localhost:7001
-user weblogic -password weblogic
-deploy -library
d:/beahome/wlserver_10.3/common/deployable-libraries/jstl-1.2.war
This command deploys the JSTL 1.2 library using the default library-name, specification-version and implementation-version defined by the MANIFEST.MF in the library.
After a library is deployed, the extension-name, specification-version and implementation-version of the library can be found in Administration console. This information can also be found in the MANIFEST.MF file of the library WAR file.
For more information on deploying a Web module refer below URL
http://docs.oracle.com/cd/E15051_01/wls/docs103/deployment/deployunits.html
2) To reference a JSF or JSTL library, a standard web application can define a <library-ref> descriptor in the application’s weblogic.xml file. Here is an example:
<library-ref>
<library-name>jsf</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.2.0</implementation-version>
<exact-match>false</exact-match>
</library-ref>
For more information on referencing a Web application library refer below URL
http://docs.oracle.com/cd/E15051_01/wls/docs103/programming/libraries.html
3) Create a sample JSP in your application and JSP should look as shown below
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<html>
<head>
<title>TestJSTL</title>
</head>
<body>
<c:set var="topic" value="JSTL" />
<c:out value="${topic}" />
</body>
</html>
4) Create WAR and deploy and test.
Edited by: Murali Veligeti on Jul 26, 2012 9:00 AM

How to deploy a JSR-168 Portlet in Weblogic?

I am running WLS 8.1 with the advanced JSR-168 support installed (not yet running
SP2). I have a JSR-168 portlet war that I had been testing in the JSR-168 reference
implementation (pluto). Can someone please point me to the instructions on how
to now import my portlet war into Workshop so that I can add it to my Weblogic
portal?
Thanks!
-David

You cannot simply "deploy" a JSR 168 portlet into Weblogic using a WAR file in
my experience. This is what I did to achieve deployment of a JSR 168 portlet in
BEA WLS 8.1SP2:
* File | New | Portlet | Java Portlet
* Just type in the name of your view class name when asked for it.
This creates a "YourAppName.portlet" file, which I believe Bea requires for any
Portlet in order to make it available for use in their portals.
* Add your files (*.jar, *.java *.jsp, etc).
* Modify WEB-INF/portlet.xml to include all required descriptor elements that
you have in your WAR file (keep in mind that there is only one portlet.xml for
all portlets in a single web application)
I was unable to use redirects for some reason, but it worked fine with include.
"David" <[email protected]> wrote:
>
I am running WLS 8.1 with the advanced JSR-168 support installed (not
yet running
SP2). I have a JSR-168 portlet war that I had been testing in the JSR-168
reference
implementation (pluto). Can someone please point me to the instructions
on how
to now import my portlet war into Workshop so that I can add it to my
Weblogic
portal?
Thanks!
-David

Weblogic deployment plan will not override variables (Weblogic 10.3.5).

I am having some trouble trying to adjust the deployment settings of our application in weblogic. I feel what I'm trying to do ought to be quite simple, but it's not working as expected.
I am just trying to override the context-root in weblogic.xml and the JNDI name for the data source, so these can both be configured at deployment time.
I have removed the application.xml from the ear file, so that shouldn't be affecting the overrides.
What I have so far:
weblogic.xml:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
<context-root>mosaic</context-root>
<resource-description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<jndi-name>LogicalDS</jndi-name>
</resource-description>
web.xml
<?xml version='1.0' encoding='UTF-8'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<resource-ref>
<description>A logical reference to the datasource - mapped in deployment plan</description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
plan.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:deployment-plan xmlns:wls="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd" global-variables="true">

<wls:application-name>mosaic.ear</wls:application-name>
<wls:variable-definition>
<wls:variable>
<wls:name>datasource_name</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>The name of the datasource to map to the mosaic application</wls:description>
</wls:variable>
<wls:variable>
<wls:name>new_context_root</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>URL to deploy Mosaic at</wls:description>
</wls:variable>
</wls:variable-definition>
<wls:module-override>
<wls:module-name>mosaic.war</wls:module-name>
<wls:module-type>war</wls:module-type>
<wls:module-descriptor>
<wls:root-element>weblogic-web-app</wls:root-element>
<wls:uri>WEB-INF/weblogic.xml</wls:uri>
<wls:variable-assignment>
<wls:name>new_context_root</wls:name>
<wls:xpath>/weblogic-web-app/context-root</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:description>Data source for mosaic application</wls:description>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-env-description/resource-env-ref-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-description/[res-ref-name="jdbc/LogicalDS"]/jndi-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
</wls:module-descriptor>
</wls:module-override>
</wls:deployment-plan>
Nothing happens when I use the deployment plan, and neither of the variables appear under the Deployment Plan configuration screens in the admin console. From what I understand, I should at least be asked for these variables, since I have specified that they are null in the deployment plan.
When I use WLST to browse the tree, I find that the runtime configuration just stays as the values in the deployment descriptors.
I have verified the deployment plan is being used in the general tab of the admin console.
Can anyone help me find out what I am doing wrong here? If I don't create a data source called LogicalDS, I get errors about this, suggesting it is not correctly overriding. I am puzzled to why I do not see any variables to specify though..

The documentation implies that this is not the case - see:
http://docs.oracle.com/cd/E24329_01/web.1211/e24443/export.htm#autoId13
'Assigning Null Variables to Require Administrator Input'.
However, require administrator input where? My thoughts were that this option would appear in the admin console under 'deployment plan'. However, although I have specified resource dependencies in the deployment descriptors, and the plan, nothing appears under 'resource dependencies' for the application.
Is the only way to change the context-root deployment URL by actually manually editing an XML file?
To me that seems primitive and will cause us support issues when distributing our application - is there any other way I can enable the ability to specify the data source name and context-root through the web console prior to/during deployment?
Edited by: user12032953 on 11-Jun-2012 07:20

How to upload and deploy an EAR to a remote weblogic domain

I can use ant to deploy EAR file to local weblogic. How to deploy ear files to a remote weblogic?

can you give me configuration details how you are deploying EAR remotely...

Deploying Java stand alone application in Weblogic server

Hi All,
We have an java stand alone application which our client uses. Suddenly they came up with a requirement of using this application from web logic server.We have following directory structure for our application
myapp
- config -> contains all configuration files
- logs -> contains log files
- ssl -> ssl related files
- samples ->contians stub's
- myapp.jar
How to deploy our standalone application in to weblogic server?.
We tried putting whole myapp folder in WEB-INF folder , and from the servlet we are able to invoke an method in an class file( in myapp.jar say Test.getInstance()) but it couldnt find configuration files (in config folder ) and it is throwing an error. We have a class called Test in myapp.jar and when we call getInstance of the class it loads all config files - config file location is hardcoded as /config/myconfig.xml , and we are facing problem here because it couldnt find myconfig.xml.
We also tried packaging whole myapp folder in to jar , but with that also we faced the same problem
Please let us know are we proceeding in the right way and how to deploy our application in weblogic server.We dont prefer making changes to our code at this point of time.
Any info on this will be very helpful to us.
Regards,
Suresh

Hi René van Wijk,
Thanks for quick reply. Link you mentioned gave a basic idea of application structure , but still i couldnt get deployment process.
Am very much new to weblogic.Can you please let me know how to deploy our standalone application in to weblogic, with out making any changes to the code.
Below is folder structure of my java stand alone application *( not webapplication)*
myapp
- config -> contains all configuration files , for ex:- myconfig.xml
- logs -> contains log files
- ssl -> ssl related files
- samples ->contians stub's
- myapp.jar
We have logic to load configuration file (config/myconfig.xml) , in an class and we are not allowed to make any changes to this code, so we cant use Thread.currentThread().getContextClassLoader().getResource(...) .
Regards,
Suresh

Error deploying WebCenter Collaboration 10.3 on WebLogic Server

when i deploy webcenter collaboration 10.3 on WebLogic Server in a Suse Linux was failed with this error
[HTTP:101216]Servlet: "cnscallback" failed to preload on startup in Web application: "/collab". java.lang.NullPointerException at com.plumtree.core.util.SpringPropertyConfigurator.resolvePlaceholder(SpringPropertyConfigurator.java:66) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.resolvePlaceholder(PropertyPlaceholderConfigurer.java:336) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.parseStringValue(PropertyPlaceholderConfigurer.java:286) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer$PlaceholderResolvingBeanDefinitionVisitor.resolveStringValue(PropertyPlaceholderConfigurer.java:401) at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:150) at org.springframework.b10.3
any idea please
thanks
i follow all the instruccion of the installation pdf

Regarding this error..... "cnscallback" failed to preload on startup in Web application: "/collab".
CNS stands for common notification service.
Was notification installed, is it up and running, and is collab properly pointing to it?
Just a guess, but it could be collab requires this to be able to start properly.

Deploy Hibernate (v 3.6) on Weblogic 11gR1 (patch set 2)

Hello,
Facing issues in deploying hibernate JPA 2.0 project on Weblogic server 10.3.3
The error message being:
Module named 'EJB605EAR' failed to redeploy. See Error Log view for more detail.
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
Exception received from deployment driver.
Entries for persistence.xml and weblogic-application.xml are as below.
I know weblogic doesn't support JPA2.0 out of the box. How to make it work?
Thank you for your help and consideration.
Hiren
<?xml version="1.0" encoding="UTF-8"?>
<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="ejb605" transaction-type="JTA">
 <provider>org.hibernate.ejb.HibernatePersistence</provider>
 <jta-data-source>jdbc/EJB605DS</jta-data-source>
 <properties>
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.format_sql" value="true" />
 <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
</properties>
 </persistence-unit>
</persistence>
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.1/weblogic-application.xsd">

<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:prefer-application-packages>
 <wls:package-name>javax.persistence.*</wls:package-name>
</wls:prefer-application-packages>
</wls:weblogic-application>

Hiren,
Hi, you will be interested in this recent thread that discusses JPA 2.0 providers (Hibernate and EclipseLink) in the context of Oracle WebLogic Server 11gR1 10.3.4 (ps3)
Re: Deploy Hibernate based EAR file on Weblogic 10.3.3?
thank you
/Michael O'Brien
http://www.eclipselink.org

BOXI R2 deployment of webcompadapter.war failed on WebLogic 8.1 SP6

I'm trying to deploy BOXI r2 SP1 over WebLogic 8.1 SP6.
other .war files get deployed very easily. but webcompadapter.war deployment gives an error.
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0 Module: webcompadapter Error: [HTTP:101179][HTTP] Error occurred while parsing descriptor in Web application "C:\bea\user_projects\domains\bobj\myserver\upload\webcompadapter.war" [Path="C:\bea\user_projects\domains\bobj\myserver\upload", URI="webcompadapter.war" org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.apache.xerces.parsers.DOMParser.parse(DOMParser.java:271) at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:201) at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:700) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) --------------- nested within: ------------------ Received SAXParseException from Sun Parser at line 69, column 48: org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:705) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) Received SAXParseException from Sun Parser at line 69, column 48: org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.apache.xerces.parsers.DOMParser.parse(DOMParser.java:271) at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:201) at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:700) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) --------------- nested within: ------------------ Received SAXParseException from Sun Parser at line 69, column 48: org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:705) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
[Deployer:149033]preparing application webcompadapter on myserver
[Deployer:149033]failed application webcompadapter on myserver
[Deployer:149034]An exception occurred for task [Deployer:149026]
Does anybody has the solution for this?
Thanks in advance.

dkarr, Thanks for your reply. 
here is the constructor I got for the class 'com.corizon.ps.oneview.servlet.OneViewWritebackResultServlet'
 
 public OneViewWritebackResultServlet() 
{ 
senderThread = null; 
jmsConnectionHandler = null; 
closureManager = null; 
mRequestSenderThread = null; 
connected = false; 
} 
 
Is this ok ?
 
Thanks, 
-Ninad

Exception when deploying a JSR 286 portlet into WebLogic+WebCenter

I get the following exception when deploying a JSR 286 portlet into WebLogic:
"<19-ene-2010 13H32' CET> <Error> <oracle.portlet.server.containerimpl.PortletApplicationImpl> <BEA-000000> <Error al procesar el archivo "/WEB-INF/portlet.xml" en la lÝnea 6 columna 68.
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'portlet-app'"
The error message is in spanish. It means:
"Error processing the file "/WEB-INF/portlet.xml at line 6 column 68"
The portlet.xml of my portlet seems to be correct and I've deployed it in other portal servers. So I don't understand the error message.
This is the portlet.xml of my portlet (eclipse XML validator said it was a valid XML)
{code}
<?xml version="1.0" encoding="UTF-8"?>
<portlet-app version="2.0"
xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
xmlns:dnd="http://www.denodo.com/widget/portlet/portletjsr286">
<portlet>
<description>Test Inter Portlet Communication (JSR286)</description>
<portlet-name>Test IPC</portlet-name>
<display-name>Test IPC</display-name>
<portlet-class>com.denodo.ipc.TestIPCPortlet</portlet-class>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>VIEW</portlet-mode>
</supports>
<supported-locale>en</supported-locale>
<resource-bundle>PortletMessages</resource-bundle>
<portlet-info>
<title>Test IPC</title>
<short-title>Test IPC</short-title>
<keywords>Test IPC,Denodo</keywords>
</portlet-info>
</portlet>
</portlet-app>
{code}
*How do I deploy my portlet*
<li> I convert my portlet into to a WSRP portlet by executing
+java -jar wsrp-predeploy.jar source EAR target EAR+
as explained in http://download.oracle.com/docs/cd/E12839_01/webcenter.1111/e12405/wcadm_portlet_prod.htm#CHDECJHI)
</li>
<li>I try to deploy it into WebLogic with the WebLogic Console and I get this exception.
</li>
*My Environment*
WebCenter Suite (11.1.1.2.0) + WebLogic Server (10.3.2) downloaded from the oracle.com. Default configuration
S.O: Windows XP SP3
*Thanks in advance for your time.*

Hi,
Are you including the Toplink jars in your EAR?
-Patrick

No Exchange Pre Deployment Analyzer?

Hi
I am looking to deploy Exchange 2013 and I cannot see any evidence of an exPDA package. Is there not one for 2013?
This was really useful for Exchange 2003 to 2010 and highlighted three issues which were resolved pre-install.
Kind Regards
Steven

Hi,
Currently, there is no official documents about the Exchange Pre-Deployment Analyzer for Exchange 2013.
The tools that we can use when we decide to install Exchange 2013 have been suggested above.
Microsoft Exchange Server Jetstress 2013 Tool
Microsoft Exchange Server Deployment Assistant
Office 365 Best Practices Analyzer
Besides, here is a blog about Office 365 Best Practices Analyzer for Exchange 2013.
http://blogs.technet.com/b/exchange/archive/2013/10/01/beta-of-microsoft-office-365-best-practices-analyzer-for-exchange-server-2013-now-available.aspx
Thanks for understanding.
Best regards,
Belinda Ma
TechNet Community Support

Error while deploying a war file in Oracle Weblogic 10gr3 server

Hi
I am trying to deploy a web application which uses Hibernate 3 in Oracle weblogic 10gr3.But I am getting following exception.The same application gets deployed in tomcat without any problem.
urce [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'autoMeteringInterceptor' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'validator' while setting bean property 'validator'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'tenant.tenantService' while setting bean property 'tenantService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenant.tenantService' defined in ServletContext resource [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:256)
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
 at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
 at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
 at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:273)
 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
 at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
 at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
 at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
 at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
 at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'tenant.tenantService' while setting bean property 'tenantService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenant.tenantService' defined in ServletContext resource [WEB-INF/servicesContext.xml]: Cannot resolve reference to bean 'genericDao' while setting bean property 'genericDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'genericDao' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'saasHibernateSessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'saasHibernateSessionFactory' defined in ServletContext resource [WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: Tenant.byUserName, slaUsageOfTenant.bySlaCriterion, ServiceUsage.byCriterion, SLA.getSlaList, ServiceUsage.byTenantId
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:256)
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
 at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
 at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:248)
 at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:128)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:950)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:740)
 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:417)
 at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
 at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
 at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:273)
 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
 at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
 at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
 at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
 at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
 at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Initially this application was giving me absolute path related errors.But when I made changes to applicationContext.xml as follows,giviing absolute path for Hibernate mapping files
<property name="mappingDirectoryLocations">
 <list>
 *<value>file:D:\saas-mappings</value>*
 </list>
</property>
I have extrached all the *.hbm.xml file to above location that is D:\saas-mappings.But now the application is giving me above mentioned error.The error says that it is related to Named queries.I am pasting the contents of a sample *.hbm.xml file having named query as a sample
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping package="com.psl.saas.domain">
 <class name="TenantSlaUsage" table="tenantslausage_v2">
 <id name="tenantId" column="tenantId">
 </id>
 <property name="maxValue">
 <column name="maxValue"></column>
 </property>
 <property name="thresholdValue">
 <column name="thresholdValue"></column>
 </property>
 <property name="slaType" column="slaType" type="com.psl.saas.dataservice.SaasEnumSlaType"/>
 <many-to-one name="slaCriterion" class="SLACriterion" column="slaCriterionName" lazy="false" unique="true" />
 <property name="usageCount">
 <column name="usageCount"></column>
 </property>
 </class>
 *<query name="slaUsageOfTenant.bySlaCriterion">
 <![CDATA[from com.psl.saas.domain.TenantSlaUsage where tenantId=:tenantId and slaCriterionName=:slaCriterionName]]>
 </query>*
</hibernate-mapping>
Any help on this will be greatly appreciated
Thanks in Advance
-Sameer Gijare

Hi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org

Error while deploying ADF application to a standalone weblogic server

I am using Jdeveloper 11.1.1.6.0, and I am trying to deploy my application to a standalone server running on a Unix box and I get the following error message:
[04:12:44 PM] ---- Deployment started. ----
[04:12:44 PM] Target platform is (Weblogic 10.3).
[04:13:00 PM] Retrieving existing application information
[04:13:01 PM] Running dependency analysis...
[04:13:01 PM] Building...
[04:13:05 PM] Deploying profile...
[04:13:09 PM] Wrote Web Application Module to C:\JDeveloper\PortingAppln\ViewController\deploy\ADF1.war
[04:13:13 PM] Deploying Application...
[04:20:19 PM] [Deployer:149191]Operation 'deploy' on application 'ADF1' is initializing on 'ADF1'
[04:20:45 PM] Weblogic Server Exception: weblogic.application.WrappedDeploymentException: oracle/jrf/PortabilityLayerException
[04:20:45 PM] See server logs or server console for more details.
[04:20:45 PM] weblogic.application.WrappedDeploymentException: oracle/jrf/PortabilityLayerException
[04:20:46 PM] #### Deployment incomplete. ####
[04:20:46 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Can someone help me with this problem.
Thanks,
Srini.

Well, how did you do?
I am having a similar problem.
1) Installed WLS 10.3.5 on a Linux machine
2) Installed ADF runtime libraries (ofm_appdev_generic_11.1.1.5.0_disk1_1of1.zip)
3) I can see at deployments
- adf.oracle.businesseditor(1.0,11.1.1.2.0)
- adf.oracle.domain(1.0,11.1.1.2.0)
- adf.oracle.domain.webapp(1.0,11.1.1.2.0)
- DMS Application (11.1.1.1.0)
- em
- emai
- emas
- emcore
- FMW Welcome Page Application (11.1.0.0.0)
- jsf(1.2,1.2.9.0)
I created from scratch a new Fusion Web app. It just has 1 ADF read-only table based on the HR.COUNTRIES table. It runs perfectly on the integrated WL.
I cannot deploy it to my standalone WLS. The error:
[02:01:37 PM] Unable to determine the target platform from the Profile. Using default
[02:01:37 PM] ---- Deployment started. ----
[02:01:37 PM] Target platform is (Weblogic 10.3).
[02:01:37 PM] Retrieving existing application information
[02:01:37 PM] Running dependency analysis...
[02:01:37 PM] Building...
[02:01:37 PM] Deploying 2 profiles...
[02:01:37 PM] Wrote Web Application Module to C:\JDeveloper\mywork\TesteAPP\ViewController\deploy\TesteAPP_ViewController_webapp.war
[02:01:37 PM] Wrote Enterprise Application Module to C:\JDeveloper\mywork\TesteAPP\deploy\TesteAPP_Project1_TesteAPP.ear
[02:01:37 PM] Deploying Application...
[02:01:39 PM] [Deployer:149191]Operation 'deploy' on application 'TesteAPP_Project1_TesteAPP' is initializing on 'ADFServer'
[02:01:39 PM] [Deployer:149193]Operation 'deploy' on application 'TesteAPP_Project1_TesteAPP' has failed on 'ADFServer'
[02:01:39 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application TesteAPP_Project1_TesteAPP on ADFServer.: Failed to load webapp: 'testeADF'.
[02:01:39 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'testeADF'
[02:01:39 PM] Caused by: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@1021039597[app:TesteAPP_Project1_TesteAPP module:testeADF path:/testeADF spec-version:2.5]", defined in weblogic.xml [Extension-Name: jsf, Specification-Version: 2, exact-match: false]
[02:01:39 PM] See server logs or server console for more details.
[02:01:39 PM] weblogic.application.ModuleException: Failed to load webapp: 'testeADF'
[02:01:39 PM] Deployment cancelled.
[02:01:39 PM] ---- Deployment incomplete ----.
[02:01:39 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I am using JDeveloper 11.1.2.1.0
What am I missing here? It must be something obvious, but I am stuck.
Thanks in advance.

Error while deploying ADF application to a standalone weblogic

jdeveloper version: 11.1.2.2
Issue: I have built a standalone weblogic server (10.3.5.0) and am trying to deploy my ADF application to it. The deployment fails with the following message. The stand alone server I have built is on the same machine where jdeveloper is installed and I am using same weblogic that came with jdeveloper install. The aplication runs fine on integrated server. I have researched this issue and have got more or less same answer of installing ADF run time libraries. Can someone please help me with exactly what I need to install and how?
Thanks,
Saurabh.
[09:49:44 AM] Unable to determine the target platform from the Profile. Using default
[09:49:44 AM] ---- Deployment started. ----
[09:49:44 AM] Target platform is (Weblogic 10.3).
[09:49:55 AM] Retrieving existing application information
[09:49:55 AM] Running dependency analysis...
[09:49:55 AM] Building...
[09:50:18 AM] Deploying profile...
[09:50:20 AM] Wrote Web Application Module to C:\JDeveloper\mywork\EmployeeTrack\ViewController\deploy\EmployeeTrack_ViewController_webapp.war
[09:50:20 AM] Deploying Application...
[09:50:24 AM] [Deployer:149191]Operation 'deploy' on application 'EmployeeTrack_ViewController_webapp' is initializing on 'ADFServer'
[09:50:26 AM] [Deployer:149193]Operation 'deploy' on application 'EmployeeTrack_ViewController_webapp' has failed on 'ADFServer'
[09:50:26 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application EmployeeTrack_ViewController_webapp on ADFServer.: Failed to load webapp: 'EmployeeTrack_ViewController_webapp.war'.
[09:50:26 AM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'EmployeeTrack_ViewController_webapp.war'
[09:50:26 AM] Caused by: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@29261813[app:EmployeeTrack_ViewController_webapp module:EmployeeTrack_ViewController_webapp.war path:/alonedemo spec-version:2.5]", defined in weblogic.xml [Extension-Name: adf.oracle.domain.webapp, exact-match: false], [Extension-Name: jstl, Specification-Version: 1.2, exact-match: false], [Extension-Name: jsf, Specification-Version: 2, exact-match: false]
[09:50:26 AM] See server logs or server console for more details.
[09:50:26 AM] weblogic.application.ModuleException: Failed to load webapp: 'EmployeeTrack_ViewController_webapp.war'
[09:50:26 AM] Deployment cancelled.
[09:50:26 AM] ---- Deployment incomplete ----.
[09:50:26 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)

Thanks Timo.. You were right.. Those setting helped me fix the initial issue.. Now I have another issue and was wondering if you have seen this as well?
[11:35:13 AM] Unable to determine the target platform from the Profile. Using default
[11:35:13 AM] ---- Deployment started. ----
[11:35:13 AM] Target platform is (Weblogic 10.3).
[11:35:13 AM] Retrieving existing application information
[11:35:13 AM] Running dependency analysis...
[11:35:13 AM] Building...
[11:35:20 AM] Deploying profile...
[11:35:21 AM] Wrote Web Application Module to C:\JDeveloper\mywork\EmployeeTrack\ViewController\deploy\EmployeeTrack_ViewController_webapp.war
[11:35:21 AM] Deploying Application...
[11:35:23 AM] [Deployer:149191]Operation 'deploy' on application 'EmployeeTrack_ViewController_webapp' is initializing on 'ADFServer'
[11:35:25 AM] [Deployer:149193]Operation 'deploy' on application 'EmployeeTrack_ViewController_webapp' has failed on 'ADFServer'
[11:35:25 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application EmployeeTrack_ViewController_webapp on ADFServer.: Failed to load webapp: 'EmployeeTrack_ViewController_webapp.war'.
[11:35:25 AM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'EmployeeTrack_ViewController_webapp.war'
[11:35:25 AM] Caused by: java.lang.ClassNotFoundException: oracle.adf.library.webapp.ResourceServlet
[11:35:25 AM] See server logs or server console for more details.
[11:35:25 AM] weblogic.application.ModuleException: Failed to load webapp: 'EmployeeTrack_ViewController_webapp.war'
[11:35:25 AM] Deployment cancelled.
[11:35:25 AM] ---- Deployment incomplete ----.
[11:35:25 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)

Deploy sip servlet to Occas5.0(weblogic) occurs exception: com.bea.wcp.sip.engine.server.setup.SipAnnotationParsingException

hi,
I install Occas on OS win7 64bit, jdk 1.6.0.45.
I got the following error message while I start Occas server:
because error occurs when parsing sip related annotations of "testservicecomplexobject-application"
WLST-WLS-1396579151484: com.bea.wcp.sip.engine.server.setup.SipAnnotationParsingException
at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.<init><SipAnnotationData.java:155>
Also, when I deploy a sip servlet package(sar) to the Occas server, after deploy finish, at the deployment manager page,
health term is none.
and also I found many error info in AdminServer/logs/domain.log as below blue font:
####<Apr 4, 2014 11:09:21 AM CST> <Error> <WLSS.Setup> <E76C3BE51B4188> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1396580961513> <BEA-331210> <Skip SIP related logic, because error occurs when parsing sip related annotations of "b2bua-sip-servlet-1.0.0-SNAPSHOT"
com.bea.wcp.sip.engine.server.setup.SipAnnotationParsingException:
 at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.<init>(SipAnnotationData.java:155)
 at com.bea.wcp.sip.util.DeploymentUtil.getOrCreateAnnotationData(DeploymentUtil.java:74)
 at com.bea.wcp.sip.util.DeploymentUtil.getAnnotationData(DeploymentUtil.java:89)
 at com.bea.wcp.sip.engine.server.SipServerTailModule$1.visit(SipServerTailModule.java:129)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.visitAllContexts(SipServerTailModule.java:112)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.initialize(SipServerTailModule.java:137)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.prepare(SipServerTailModule.java:69)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
 at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
 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:207)
 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:747)
 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:159)
 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:46)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.LinkageError: loader constraint violation: when resolving overridden method "antlr.debug.LLkDebuggingParser.removeMessageListener(Lantlr/debug/MessageListener;)V" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, antlr/debug/LLkDebuggingParser, and its superclass loader (instance of sun/misc/Launcher$AppClassLoader), have different Class objects for the type antlr/debug/MessageListener used in the signature
 at java.lang.Class.getDeclaredMethods0(Native Method)
 at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
 at java.lang.Class.privateGetPublicMethods(Class.java:2556)
 at java.lang.Class.getMethods(Class.java:1412)
 at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.classAnnotationParsing(SipAnnotationData.java:344)
 at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.jarAnnotationParsing(SipAnnotationData.java:288)
 at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.annotationParsing(SipAnnotationData.java:223)
 at com.bea.wcp.sip.engine.server.setup.SipAnnotationData.<init>(SipAnnotationData.java:144)
 at com.bea.wcp.sip.util.DeploymentUtil.getOrCreateAnnotationData(DeploymentUtil.java:74)
 at com.bea.wcp.sip.util.DeploymentUtil.getAnnotationData(DeploymentUtil.java:89)
 at com.bea.wcp.sip.engine.server.SipServerTailModule$1.visit(SipServerTailModule.java:129)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.visitAllContexts(SipServerTailModule.java:112)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.initialize(SipServerTailModule.java:137)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.prepare(SipServerTailModule.java:69)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
 at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
 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:207)
 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:747)
 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:159)
 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:46)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Apr 4, 2014 11:09:21 AM CST> <Error> <WLSS.Engine> <E76C3BE51B4188> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1396580961523> <BEA-330004> <Failed to deploy SIP application "b2bua-sip-servlet-1.0.0-SNAPSHOT"
java.lang.NullPointerException
 at com.bea.wcp.sip.engine.server.setup.SipDeploymentDescriptor.<init>(SipDeploymentDescriptor.java:285)
 at com.bea.wcp.sip.engine.server.setup.SipDeploymentDescriptor.parse(SipDeploymentDescriptor.java:148)
 at com.bea.wcp.sip.engine.server.CanaryContext.initContext(CanaryContext.java:396)
 at com.bea.wcp.sip.engine.server.CanaryContext.<init>(CanaryContext.java:334)
 at com.bea.wcp.sip.engine.server.CanaryServer.installContext(CanaryServer.java:1001)
 at com.bea.wcp.sip.engine.server.SipService.setupSipServletContext(SipService.java:126)
 at com.bea.wcp.sip.engine.server.SipServerTailModule$1.visit(SipServerTailModule.java:130)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.visitAllContexts(SipServerTailModule.java:112)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.initialize(SipServerTailModule.java:137)
 at com.bea.wcp.sip.engine.server.SipServerTailModule.prepare(SipServerTailModule.java:69)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
 at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
 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:207)
 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:747)
 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:159)
 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:46)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Can anyone give some suggession?
Thanks in advance!
BR//Margin

Hi,
I changed my jvm from sun jdk to latest jrockit and the issue was solved :)

Deploying Analyzer 7.0.1 on Weblogic 8.1

Similar Messages

Maybe you are looking for