Deploying TestStand app on TestStand-less target
I want to deploy a TestStand app on a target that doesn't have TestStand installed on it. I ran into this before on a different target, and the only way I could get around the ActiveX error messages I saw was to install TestStand on the target. Now we're going to send this deployment out, and I remembered my previous troubles. Will I again have to install TestStand at the target. If not, what specific files should I look for in my LabWindows/CVI and TestStand projects that will tell me that I have what I need.
As I understand it, TestStand "apps" require the TestStand engine at a
minimum. You can create a distribution kit from within TestStand
that just distributes the engine. The sequence files have a
separate installer. This is how I've done my test systems in the
past. You will need to provide a serial number and activate the
engine when you deploy it. Otherwise it will run in demo mode
only.
If you want to make it easy for the people installing your app, you
could build a distribution kit in TestStand that distributes the engine
along with your application. I don't think it's easy to do this
in CVI.
I am the founder of CnCSoftwareSolutions. When not cleaning up baby drool, I write about test data or work on Vision, a tool for understanding your test data. Visit me at www.cncsoftwaresolutions.com
Similar Messages
-
Deploy teststand system Labview instrument drivers
I'm trying to deploy a teststand application but I have an error with some Labview VI's.
I'm using some VI's to control an Agilent 34401A, so Labview instruments library that
is in the default package was used. The error says that Labiew Could no open the following VIs...
I don't want to install the Labview development system on the target machine, so I don't know
how to fix this problem.
I tried to copy the library to a different location an removing the VIs that are not wired (VI Tree.vi),
but I have the same error. (On the sequence was changed the path to the new VI location).
Thanks
MarcosMarcos,
You can execute VIs using the LabVIEW Runtime Engine, but all of the source VIs must be processed to collect their required dependencies and insure they are compiled in the current version of LabVIEW. The Deployment Utility process VIs from your sequences automatically. The TestStand Reference Manual has a chapter on deploying TestStand systems that should help you get started.
-Rick Francis -
I am trying to use the Deployment Utility to deploy TestStand to a target. I have modified the TestExec.prj through CVI and have created an installer using CVI to do that. I have also modified the modelsupport2.prj with some additional GUI's. I have also made the necessary changes to all the other files required. I have sone this several times with other versions of TestStand.
For some reason, the deployment utility is not picking up the files located in /All Users/Documents/TestStand 4.1.1/Components/
Therefore it is not getting the modified GUI, the Language files requires, the modelsupport2 files, etc. etc. etc.
I have tried multiple deployments selecting different settings, but nothing seems to work. I finally copied iver the components directory from the development machine to the target and now my modelPanels GUI (which is all modifed in modelsupport2.dll) and it seems to work. However, this is not the correct way, right????
Please advise.Hi Kelly,
All the files that were modifed in the modelsupport2.dll have been modified in the TestStand public directories, so I know that is not the problem. The files in the normal TestStand directories remain unchanged.
I have also tried to select the "Display files in the TestStand Public Directories", but this is where I run into other problems. The deployment utility reports several errors and warnings that will cause my deployment to fail. The errors reported are as follows:
1. You may need to add any sequence files referenced by the following expressions: (Too many to list, but all have to do with reportgen)
2. The following files were not found: (too many to list, but all are .vi's. I don't even have LabView installed!)
3. The following vi's could not be loaded: (Again, too may to list, but see above.... Labview not installed!)
Regarding the vi's, I have tried to deselect any of the items that seem to be LabView related, but It still gives me those errors/warnings. I have also tried to exclude any LabView items by excluding them in the Labview sections, but that does not help either.
Please explain if possible.
Thanks,
Gregg -
Hi,
I have tried many suggestions and configurations but I still cant get my deployed TestStand to run in other PC. I kept getting "Unable to launch the 'LabVIEW .Application' ActiveX automation server. TestStand cannot find a LabVIEW Development System installed in this computer." My test sequence also uses custom process model. Below are the things that I have done:
1. Configured the LabVIEW adapter to use RTE and enable "Always Run VI in LabVIEW RTE" in the LabVIEW Advanced Settings under Module tab.
2. Added configuration .ini files that will be used, including TestExec.ini and TestStandModelModelOptions.ini in workspace.
3. Enable "Install TestStand Engine" and leave Engine Options/ Drivers and Components as default.
Below are my questions:
1. Since I am using custom process model, where should I save this .seq in?Is it in my working directory or TestStand components folder? Reason why I am asking this is because I tried both ways, the latter gave me
"Warning: This problem will cause an error when building a deployable image or an installer. The following file(s) were not found:
rfid_read_write.seq in step 'Reset Test Sequence', sequence 'MainSequence', sequence file 'C:\Program Files (x86)\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\SequentialModel_RFID.seq'"
Obviously rfid_read_write.seq has already been included and present.
2. Should I also include this custom process model .seq file in the workspace/deployment?
3. How to solve the unable to launch LabVIEW.Application issue?
Thanks.Hi, it looks like the app has trouble starting up:
05/01/17 10:21:47 - ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
Did you have any errors on the compile of the code?
You also want to check if the app is deployed (if so you may want to remove it before re-deploying it) -
Hi,
In TestStandIf you want to run a TS script that calls VIs on a Runtime engine only system you have to use the Deploy TestStand utility to do that. Since a Runtime Engine only system does not have vi.lib you must search all the .seq for VI calls and then traverse all the SubVis to find all the calls to VIs in vi.lib. The Deploy TestStand does that for you. It moves all the VIs and SubVIs to a SupportVI directory and mass compiles them. Once all VIs are within the same directory the runtime engine can find them.
Note: This is a very nasty poorly written tool. I had a deploy that would take about 6 hours to complete. I wrote my own that takes about 4 minutes to complete. -
ActiveX Automation server error on deployed TestStand
I'm trying to deploy TestSTand 2.0 + LabVIEW 6.1 on a PC under Win-2K.
I created and deployed TS Engine and Operator Interface for LV.
I try to deploy the "Auto.seq" test from the TS exemples.
Of course, it works on my Development system.
On the deployed system, I got an error : -18351; An error occurred reading an ActiveX Automation server type library.
Step 'Read Database Option - Construct' of sequence 'Get Database Options' in 'SequentialModel.seq'
Step 'Read Database Option - Read Options' of sequence 'Get Database Options' in 'SequentialModel.seq'
After having ignored those 2 errors, the tests goes on normally and the report looks fine.
I also get this error opening the database configuration:
Step 'Read Database Option - Construct' of sequence 'Edit Database Options' in 'Database.seq'
From answers already given for similar subjects, I've checked that TsDBOptions.dll is present and registered (done regsvr32...) on the PC.
Can someone help ?
Note: upgrading to more recent TS + LV versions is not a solution!Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
-Doug -
When I try to run:
Tools>>Deploy TestStand System>>Deployed Files>>LabVIEW Options>>Lock VI Diagrams
I get the following error after I hit the Build key:
Failure : linker.cpp line 2022
LabVIEW version 6.1
I suspect I need version 7.0?? Can anyone confirm this or let me know what I'm doing wrong?Rick,
I've only got one simple vi in my sequence. I can run the build utility with no errors until I select the "Lock VI Diagrams" option. Note that my error code is now 1035 instead of 2022 like it was previously. The 2022 error was caused by not suppling password in the Lock VI Diagram box.
Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller
Attachments:
deployment_trial.zip 14 KB -
When I start the Deploy TestStand system dialog and start a build it gets this far
Saving File:
C:\Documents and Settings\cglidden\My Documents\TestStand Deployment\DCT 3p1\Installer\DCTwPick.tsd
Processing Workspace...
Done processing workspace file
Beginning build process, please wait.
8:18 AM
and then hangs. I am using TestStand 3.1 on a Win 2K machine and am deploying because the sequence uses LabVIEW 7.0 VIs. I had a problem before with the utility hanging later in the process but the same fixes do not work here. There is no hidden dialog box stopping things either.
Any ideas?
Thanks,
ChasHi Chas,
Are you able to create a simple sequence with just a
message box and deploy that?
Thanks,
Terry S.
Staff Software Engineer
National Instruments -
Error deploying ADF App (Fusion Web Application) to JBOSS 7.1.1.Final
When i'm deploying ADF App in JBOSS 7.1.1.Final AppServer it gives me the following in JDeveloper 11g release 2 (11.1.2.2.0):
[02:53:17 PM] Target platform is (JBoss 5.x).
[02:53:17 PM] Running dependency analysis...
[02:53:17 PM] Building...
[02:53:17 PM] Deploying profile...
[02:53:17 PM] ADF shared library is not available, implicitly deploying library ADF Controller Runtime
[02:53:17 PM] ADF shared library is not available, implicitly deploying library ADF Controller Schema
[02:53:17 PM] ADF shared library is not available, implicitly deploying library ADF Page Flow Runtime
[02:53:18 PM] Wrote Web Application Module to C:\JDeveloper\mywork\ola\ViewController\deploy\ola_ViewController_webapp.war
[02:54:48 PM] Copied C:\JDeveloper\mywork\ola\ViewController\deploy\ola_ViewController_webapp.war to //10.10.1.11/jboss-as-7.1.1.Final/standalone/deployments/ola_ViewController_webapp.war
[02:54:48 PM] Elapsed time for deployment: 1 minute, 30 seconds
[02:54:48 PM] ---- Deployment finished. ----
On the JBoss side it gives me the stack error: [http://justpaste.it/zom]
I can´t understand what's missing.
Thanks in advance.Ok finally i've done it...it deployed with no errors.
But now when i look it in my browser it just shows me:
<?xml version='1.0' encoding='windows-1252'?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<af:document id="d1">
<af:form id="f1">
<af:pageTemplate viewId="/oracle/templates/threeColumnTemplate.jspx" id="pt1">
<f:facet name="center"/>
<f:facet name="header"/>
<f:facet name="end"/>
<f:facet name="start"/>
<f:facet name="branding"/>
<f:facet name="copyright"/>
<f:facet name="status"/>
</af:pageTemplate>
</af:form>
</af:document>
</f:view>
Now i'm out of ideas. -
WLST script to deploy an app to a cluster?
Hi,
I'm using WL 9.2.2. Does anyone have a script that deploys an app, "myApp" to a cluster "myCluster"?
Seems like a simple thing, but I'm hitting a wall when trying to search on Google. - DaveDave, try my old blog:
http://blogs.oracle.com/jamesbayer/2007/10/automate_wls_console_tasks_wit.html
Instead of the target being the admin server for the deploy command, it could be "myCluster".
Also, for trying to get the syntax, you could also use server 10.0 or 10.3 and use the "Record" feature in the console. That syntax should be mostly backward compatible with 9.2 for main use cases. -
Not able to deploy ADF app in weblogic
hi all,
I am using 11.1.1.5 . when I am trying to deploy adf app ,I am getting this error.
An error occurred during activation of changes, please see the log for details.[J2EE:160149]Error while processing library references.
Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false ....... so on
I am not sure what went wrong. can anyone suggestClick on Deployements
Click on adf.oracle.domain(1.0,11.1.1.2.0) library
Click on Targets tab and select the server where the application going to be deployed (
Click on “Save”
Follow same steps from 3 to 5 on following library too
- adf.oracle.businesseditor(1.0,11.1.1.2.0)
- adf.oracle.domain.webapp(1.0,11.1.1.2.0)
Try again deploying,it will work now. -
hi people, i know this should be the n+1 time this question is posted here, i have read all post before and follow their instructions to have a Tomcat 6 working with a very simple adf components. the error i get is Tomcat cant deploy that app. this is how tomcat is configured:
inside lib dir:
1116 adf-controller-api.jar
132 adf-controller.jar
500 adf-controller-rt-common.jar
4 adf-controller-security.jar
668 adf-faces-databinding-rt.jar
32 adflibfilter.jar
8 adflogginghandler.jar
7576 adfm.jar
44 adfmweb.jar
16 adf-pageflow-dtrt.jar
216 adf-pageflow-fwk.jar
340 adf-pageflow-impl.jar
44 adf-pageflow-rc.jar
1568 adf-richclient-api-11.jar
7320 adf-richclient-impl-11.jar
316 adf-share-base.jar
648 adf-share-ca.jar
3004 adfsharembean.jar
16 adf-share-security.jar
268 adf-share-support.jar
16 annotations-api.jar
1944 cache.jar
56 catalina-ant.jar
128 catalina-ha.jar
1160 catalina.jar
232 catalina-tribes.jar
112 commons-el.jar
56 db-ca.jar
1544 dms.jar
492 dvt-databindings.jar
128 dvt-facesbindings.jar
3420 dvt-faces.jar
6368 dvt-jclient.jar
1244 dvt-trinidad.jar
1268 dvt-utils.jar
32 el-api.jar
608 fmw_audit.jar
808 glassfish.jsf_1.2.9.0.jar
368 glassfish.jstl_1.2.0.1.jar
344 identitystore.jar
368 inspect4.jar
108 jasper-el.jar
516 jasper.jar
1376 jasper-jdt.jar
2512 javatools-nodeps.jar
64 javax.activation_1.1.0.0_1-1.jar
352 javax.jsf_1.2.0.1.jar
16 javax.management.j2ee_1.0.jar
12 javax.transaction_1.0.0.0_1-1.jar
3004 jewt4.jar
364 jmxframework.jar
612 jmxspi.jar
444 jps-api.jar
648 jps-common.jar
24 jps-ee.jar
1644 jps-internal.jar
112 jps-unsupported-api.jar
72 jrf-api.jar
332 jsf-api.jar
776 jsf-ri.jar
76 jsp-api.jar
24 jstl.jar
5488 mdsrt.jar
2476 ojdbc6dms.jar
1948 ojdbc6.jar
4 oracle-el.jar
216 oraclepki.jar
168 org.apache.commons.beanutils_1.6.jar
144 org.apache.commons.digester_1.8.jar
40 org.apache.commons.logging_1.0.4.jar
168 osdt_cert.jar
256 osdt_core.jar
88 servlet-api.jar
56 share.jar
388 standard.jar
744 tomcat-coyote.jar
228 tomcat-dbcp.jar
72 tomcat-i18n-es.jar
52 tomcat-i18n-fr.jar
56 tomcat-i18n-ja.jar
0 tree.txt
1224 trinidad-api.jar
4220 trinidad-impl.jar
1244 wls-api.jar
4 wls.jsf.di.jar
1196 xercesImpl.jar
752 xmlef.jar
1412 xmlparserv2.jar
i am deploying the app directly from jDeveloper the same way shay does in a video tutorial i have found. it looks like everything goes fine:
[02:47:09 PM] ---- Deployment started. ----
[02:47:09 PM] Target platform is (Tomcat 6.x).
[02:47:09 PM] Running dependency analysis...
[02:47:09 PM] Building...
[02:47:16 PM] Deploying profile...
[02:47:17 PM] Wrote Web Application Module to /home/isanchez/jdeveloper/MyGecu/View/deploy/GeCUweb.war
[02:47:18 PM] Wrote Enterprise Application Module to /home/isanchez/jdeveloper/MyGecu/View/deploy/GeCUweb.ear
[02:47:18 PM] Copied /home/isanchez/jdeveloper/MyGecu/View/deploy/GeCUweb.war to /usr/share/Tomcat6a/webapps
[02:47:18 PM] Elapsed time for deployment: 9 seconds
[02:47:18 PM] ---- Deployment finished. ----
the application is very simple. it only shows a login.jsp page with adf components, and it would be really nice this applications should be working like this. I have finished a full application using ADF with jDeveloper and I only need this final step.
this is how the app is configured by the developer:
WEB-INF/web.xml:
<?xml version = '1.0' encoding = 'UTF-8'?>
<web-app 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/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
<context-param>
<description>If this parameter is true, there will be an automatic check of the modification date of your JSPs, and saved state will be discarded when JSP's change. It will also automatically check if your skinning css files have changed without you having to restart the server. This makes development easier, but adds overhead. For this reason this parameter should be set to false when your application is deployed.</description>
<param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<description>Whether the 'Generated by...' comment at the bottom of ADF Faces HTML pages should contain version number information.</description>
<param-name>oracle.adf.view.rich.versionString.HIDDEN</param-name>
<param-value>false</param-value>
</context-param>
<filter>
<filter-name>JpsFilter</filter-name>
<filter-class>oracle.security.jps.ee.http.JpsFilter</filter-class>
<init-param>
<param-name>enable.anonymous</param-name>
<param-value>true</param-value>
</init-param>
</filter>
<filter>
<filter-name>trinidad</filter-name>
<filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>JpsFilter</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>trinidad</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>resources</servlet-name>
<servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>BIGRAPHSERVLET</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.graph.GraphServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>BIGAUGESERVLET</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.gauge.GaugeServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>MapProxyServlet</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.geoMap.servlet.MapProxyServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>GatewayServlet</servlet-name>
<servlet-class>oracle.adfinternal.view.faces.bi.renderkit.graph.FlashBridgeServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/adf/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/afr/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>BIGRAPHSERVLET</servlet-name>
<url-pattern>/servlet/GraphServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>BIGAUGESERVLET</servlet-name>
<url-pattern>/servlet/GaugeServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>MapProxyServlet</servlet-name>
<url-pattern>/mapproxy/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/bi/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>GatewayServlet</servlet-name>
<url-pattern>/flashbridge/*</url-pattern>
</servlet-mapping>
</web-app>
WEB-INF/trinidad-config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config">
<skin-family>fusion</skin-family>
</trinidad-config>
and WEB-INF/faces-config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
<application>
<default-render-kit-id>oracle.adf.rich</default-render-kit-id>
<locale-config>
<default-locale>es</default-locale>
<supported-locale>es</supported-locale>
</locale-config>
</application>
<managed-bean>
<managed-bean-name>SelectedApp</managed-bean-name>
<managed-bean-class>gecu.view.SelectedApp</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>DatabaseQueryBean</managed-bean-name>
<managed-bean-class>gecu.view.DatabaseQueryBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>ClavesQueryBean</managed-bean-name>
<managed-bean-class>gecu.view.ClavesQueryBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>LoginBean</managed-bean-name>
<managed-bean-class>gecu.view.LoginBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>usuario</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
<managed-property>
<property-name>password</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
</managed-bean>
<navigation-rule>
<from-view-id>/login.jsp</from-view-id>
<navigation-case>
<from-outcome>failure</from-outcome>
<to-view-id>/login.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/core/select.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>logout</from-outcome>
<to-view-id>/logout.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/core/main.jsp</from-view-id>
<navigation-case>
<from-outcome>done</from-outcome>
<to-view-id>/core/main.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>logout</from-outcome>
<to-view-id>/logout.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>select</from-outcome>
<to-view-id>/core/select.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>filter</from-outcome>
<to-view-id>/util/filters.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>export</from-outcome>
<to-view-id>/util/exports.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>calc</from-outcome>
<to-view-id>/util/calcs.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/core/select.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/core/main.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/util/filters.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/core/main.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/util/exports.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/core/main.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/util/calcs.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/core/main.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<navigation-rule>
<from-view-id>/index.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/login.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<managed-bean>
<managed-bean-name>ControlSession</managed-bean-name>
<managed-bean-class>gecu.model.ControlSession</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
<managed-bean>
<managed-bean-name>backing_util_calcs</managed-bean-name>
<managed-bean-class>gecu.view.Calcs</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<!--oracle-jdev-comment:managed-bean-jsp-link:1util/calcs.jsp-->
</managed-bean>
<managed-bean>
<managed-bean-name>backing_util_exports</managed-bean-name>
<managed-bean-class>gecu.view.Exports</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<!--oracle-jdev-comment:managed-bean-jsp-link:1util/exports.jsp-->
</managed-bean>
<managed-bean>
<managed-bean-name>backing_util_filters</managed-bean-name>
<managed-bean-class>gecu.view.Filters</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<!--oracle-jdev-comment:managed-bean-jsp-link:1util/filters.jsp-->
</managed-bean>
</faces-config>
If someone has got really nicely configured the tomcat 6 running ADF components error free, it would be good if you can share it with us, i run out ideas and still got no answers.
Really thanked for all help received.
isyhi John,
you are correct. I would like to ask you something else if I can, becouse programming these days is a matter of time, and you may know how much that cost to a company. Our other option, instead of working with Tomcat, it is an Oracle IAS server we have here, but I do not know if that is supported with ADF components. We need to deploy our recently made application from jDeveloper 11g, and we need to have the production server online next week to start working on.
Something else I would like to comment, just to talk about, java is made for people, and it is really powerfull. Java enterprise web applications also, and it would be good, if you are developing with ADF, to be able to transport those applications to be used under different web servers. Just to make them "academical" and ease to learn. This last quote is just my own opinion as a java developer and learner on web development using powerfull jsf components like adf.
sincerely
Israel -
Hello everybody,
I have been developing my first app that will go in production soon. It works properly and I would like now to put it under user test on our UAT environment.
In order to achieve that, I configured the farm in order to host a company app catalog.
After configuration of the farm I created an app catalog in one of my web applications.
I uploaded the app file to the app catalog library and then added it to the catalog site.
Now I would like to deploy the app to a target site collection and in order to do that I go to the app catalog site, then I click on the ... button of the app and then click on "deployments".
In there I enter the site collection in which I want to add the app but when I click on "Add" an error message appears: "Invalid site collection" (or similar, since I have it in french this is my own translation)
So I am stuck here. I have my app in the farm but cannot deploy it to a site collection in order to use it then.
The site collection to which I am trying to add the app to is in another web application than the app catalog (just in case that maters).
Any thoughts on this?
Thanks in advance for your help
Carlos"App Catalog is scoped to a web application, all apps that you want to make available for a web application have to be in the App Catalog site collection for that web application"
http://technet.microsoft.com/en-us/library/fp161234%28v=office.15%29.aspx
if you want to deploy apps to different web application then you have to create a new app catalog specific that web application and upload the apps to that app catalog so they will be available to all site collection within that web application.
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful -
Getting the BEA-101163 error while deploying the app on the server.
I am getting the deployment error <Could not load user defined listener: java.lang.ClassNotFoundException: > while deploying the app on the weblogic 10.3.3 server.
Please find the stack trace below :
####<Aug 18, 2010 2:56:43 PM UTC> <Error> <HTTP> <ss> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
Kernel>> <> <> <1282143403578> <BEA-101163> <Could not load user defined listener:
java.lang.ClassNotFoundException:
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:123)
at weblogic.servlet.internal.EventsManager.registerPreparePhaseListeners(EventsManager.java:71)
at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1843)
at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1193)
at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:453)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
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)
>
####<Aug 18, 2010 2:56:43 PM UTC> <Error> <Deployer> <ss> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<WLS Kernel>> <> <> <1282143403640> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1282143360031' for task '2'. Error is:
'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:404)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
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.ClassNotFoundException:
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:123)
at weblogic.servlet.internal.EventsManager.registerPreparePhaseListeners(EventsManager.java:71)
at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1843)
at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1193)
at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:453)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
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)
>
####<Aug 18, 2010 2:56:43 PM UTC> <Warning> <Deployer> <ss> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<WLS Kernel>> <> <> <1282143403734> <BEA-149004> <Failures were detected while initiating deploy task for application 'AOS'.>
####<Aug 18, 2010 2:56:43 PM UTC> <Warning> <Deployer> <ss> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<WLS Kernel>> <> <> <1282143403734> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:404)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
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.ClassNotFoundException:
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:123)
at weblogic.servlet.internal.EventsManager.registerPreparePhaseListeners(EventsManager.java:71)
at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1843)
at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1193)
at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:453)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
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)
>
####<Aug 18, 2010 2:56:43 PM UTC> <Error> <Console> <ss> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'>
<weblogic> <> <> <1282143403781> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:404)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
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.ClassNotFoundException:
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:123)
at weblogic.servlet.internal.EventsManager.registerPreparePhaseListeners(EventsManager.java:71)
at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1843)
at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1193)
at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:453)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381)
>Did you fix this issue ? If yes .Can you please share the steps
-
Unable to deploy ADF app from Jdev 10.1.3.3 to OAS 10.1.3.1
Dear colleagues,
I'm deploying my app from JDev 10.1.3.3 to OAS 10.1.3.1. And it is driving me crazy, my application is a J2EE ADF application. When I try to deploy I'm getting the following errors: I've tried everything during days, but still I'm not able to run it :(. The application is working fine in Jdeveloper
This first error, I could solved adding the jhsadfrt-10.1.3.jar in the OracleAS_1\j2ee\home\applib directory. See the error solved:
Operation failed with error:
******************** FIRST ERROR (SOLVED)********************************************
Missing class: oracle.jheadstart.model.adfbc.v2.JhsApplicationModule
Dependent class: amaos.model.common.AmaosModule
Loader: amaos.root:0.0.1
Code-Source: /D:/product/10.1.3.1/OracleAS_1/j2ee/home/applications/amaos/ejb2.jar
Configuration: <ejb> in D:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\amaos
(Failure analysis caught java.lang.IllegalStateException: ClassLoader "amaos.root:0.0.1" (from <application> in /D:/product/10.1.3.1/OracleAS_1/j2ee/home/applications/amaos/): This loader has been closed and should not be in use.)
******************* CURRENT ERROR AFTER SOLVING THE FIRST ****************
The missing class is available from the following locations:
1. Code-Source: /E:/product/10.1.3.1/OracleAS_2/BC4J/lib/bc4jct.jar (from <code-source> in /E:/product/10.1.3.1/OracleAS_2/j2ee/home/config/server.xml)
This code-source is available in loader adf.generic.domain:10.1.3.1.
This code-source is available in loader adf.oracle.domain:10.1.3.1
2. Code-Source: /E:/product/10.1.3.1/OracleAS_2/BC4J/lib/bc4jmt.jar (from <code-source> in /E:/product/10.1.3.1/OracleAS_2/j2ee/home/config/server.xml)
This code-source is available in loader adf.generic.domain:10.1.3.1.
This code-source is available in loader adf.oracle.domain:10.1.3.1
3. Code-Source: /E:/product/10.1.3.1/OracleAS_2/BC4J/lib/adfm.jar (from <code-source> in /E:/product/10.1.3.1/OracleAS_2/j2ee/home/config/server.xml)
This code-source is available in loader adf.generic.domain:10.1.3.1.
This code-source is available in loader adf.oracle.domain:10.1.3.1
Any ideas?
Thanks
Message was edited by:
BenalúaBenalua,
(sorry, I don't know how to type the "u" with the diacritic mark above it in your name)
Did you deploy the ADF 10.1.3.3 libraries to the 10.1.3.1 app server? An alternative might be to apply the 10.1.3.3 patch to the 10.1.3.3 app server.
John
Maybe you are looking for
-
USB-6009 pulse train generation with digital output....
Hello! I've bought a new USB NI-Card (USB-6009) and now I'm trying to adopt an old vi that uses traditional DAQ drivers. I wrote that vi for a PCI NI-Card (PCI-6024E), which has two counters to generate two pulse trains simultaneously. Now I've only
-
Why does Firefox Crash Constantly?
Like others who have reported this issue, Firefox has been crashing constantly on numerous different websites. I have Windows 7 32bit which was recently re-installed, fully updated. All drivers are up to date, all add-ons are updated, all plug-ins ar
-
Copying Files from Case-Sensitive External to Non-Case-Sensitive Internal?
+(Sorry if this is the wrong sub-forum, I didn't know which one this question fit in)+ I just got a new iMac today and I'm trying to transfer some of my old files (specifically iTunes & iPhoto). My old computer was an MBP & only had an 80 GB HD, so t
-
Cannot run 'exec dbms_xdb.setlistenerlocalaccess(false)' in sqlplus for XE
Cannot run 'exec dbms_xdb.setlistenerlocalaccess(false)' from within sqlplus. Apparently it does not exist, because when i do sql> describe dbms_xdb it shows sethttpport... but not the setlistenerlocalaccess.
-
I upgraded my ipad mini its showing an activation error
This device is not registered as part of the iPhone Developer Program.If you are a member of the Program, please register your device in the iPhone Developer Program Portal. this showing when i am connect my ipad mini to my mac book pro what should i