Deploy component manually into LiveCycle

Hi Guys
I have to deploy my first "Custom Directory Service Provider" and "Custom Authentication Provider" into LiveCycle hosted on WebSphere 6 (Solaris/SPARC), but I would like to install manually, ie without WorkBench and without the Java API.
Can I put these JAR files in some folder, start/stop the applications onto WebSphere, and finish the deployment using the common process through LiveCycle Administration Console ?
Thanks
Marcelo Maciel

Hi Abhi,
You can directly give host name and message server port no. in J2EE Engine properties and deploy it. If this dies not work follow this procedure.
1.[Start |http://help.sap.com/saphelp_nw70/helpdata/en/43/1f1b46e7dd2bc5e10000000a114cbd/frameset.htm]the SDM GUI.
2. [Deploy |http://help.sap.com/saphelp_nw70/helpdata/en/43/2ae0ec69742182e10000000a114cbd/frameset.htm]the ear file.
3. Still you are not able to deploy it, then [undeploy |http://help.sap.com/saphelp_nw70/helpdata/en/28/2c3c1bf823204c8370bfacbe54133b/frameset.htm]it and deploy again.
Feel free to revert in case of any issues.
Regards,
Siva

Similar Messages

Unable to deploy a module into XI Server

Hi together,
I developed a new module within the J2ee Development Studio. Compiling and building is ok. The ear-File is build... everything is fine... execpt the following.
I connected the Development Studio to our XI Server. The connection is stable and working.
Now, i try to deploy my development into the Server through the J2EE Explorer. I get the following result:
10.04.2008 19:31:52 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : srv06007
SDM port : 57018
URL to deploy : file:/C:/DOKUME1/000282/LOKALE1/Temp/temp41484XI_Adapter_Module_Edifact_Parser.ear
Result
=> deployment aborted : file:/C:/DOKUME1/000282/LOKALE1/Temp/temp41484XI_Adapter_Module_Edifact_Parser.ear
Aborted: development component 'XI_Adapter_Module_Edifact_Parser'/'sap.com'/'localhost'/'2008.04.08.13.05.54'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/XI_Adapter_Module_Edifact_Parser.. Reason: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.Bean EDIFACT_TO_XML: can not find method ejbCreate() in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean EDIFACT_TO_XML: can not find method ejbCreate() in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.Error in the local interface com.sap.aii.af.mp.module.ModuleLocal of bean EDIFACT_TO_XML: No corresponding business method in the bean class was found for method process.Error in the bean class: There is no public constructor with no parameters defined within bean com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl. Bean classes must have a public constructor with no parameters.Bean HmisBeanImpl: Cannot find home or component interfaces.; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.Bean EDIFACT_TO_XML: can not find method ejbCreate() in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean EDIFACT_TO_XML: can not find method ejbCreate() in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.Error in the local interface com.sap.aii.af.mp.module.ModuleLocal of bean EDIFACT_TO_XML: No corresponding business method in the bean class was found for method process.Error in the bean class: There is no public constructor with no parameters defined within bean com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl. Bean classes must have a public constructor with no parameters.Bean HmisBeanImpl: Cannot find home or component interfaces.
 at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
 at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
 at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.Bean EDIFACT_TO_XML: can not find method ejbCreate() in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean EDIFACT_TO_XML: can not find method ejbCreate() in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.Error in the local interface com.sap.aii.af.mp.module.ModuleLocal of bean EDIFACT_TO_XML: No corresponding business method in the bean class was found for method process.Error in the bean class: There is no public constructor with no parameters defined within bean com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl. Bean classes must have a public constructor with no parameters.Bean HmisBeanImpl: Cannot find home or component interfaces.
 at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
 at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
 at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
I already copied the needed jar Files in the lib path of the server... I tried out nearly everything. On my workstation everything is OK - I guess, that a library is missing... What can I do, so that the XI is recocnising the jar files? Is there an other reason for that failure?
Since I'm trying to figure out what is happening for one week now, you are my last chance :-).
Thanks & Regards
 Thomas

Hi,
Like Stefan said..
Reason: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.
Change the bean class EDIFACT_TO_XML in package..de.regioit.xi.adapter.module and change it from
Abstract to public, save rebuild and re-deploy......
Regards
Ravi Raman

Ailed deploying components with adobe livecycle configuration manager

Hi all
I have a problem installing my Adobe Livecycle. When I start the configuration manager, I'm following step by step all options but, after the test server connection, when I deploy the components to application server, i have this error
ALC-LCM-030-200
Failed to deploy component ..\working\deployLC\deploy\adobe-generatepdf-dsc.jar
and after this exception the deployment stops
any idea will be appreciated. Thanks in advance
Dani

Hi everyone, I have this problem too.. We are running 4Gig RAM and the system has 15G free space. The JBoss setting.. -Xms and -Xmx are set properly. I restarted the configuration again and again.. this is the 6th times.. and the 1st time it stopped at 80% and now 92%.. Why ? is there any configuration needed ?? ALC-LCM-030-200 Failed for deployment.. [2009-02-05 13:25:44,307], SEVERE, Thread-39, com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, Failed to deploy component C:\Adobe\LiveCycle8.2\deploy\adobe-rightsmanagement-jboss-dsc.jar. com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Echec du déploiement du composant C:\Adobe\LiveCycle8.2\deploy\adobe-rightsmanagement-jboss-dsc.jar. at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:396) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(DeployDSCs.java:149) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask.deployDSCs(ExpressTurnk eyTask.java:457) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask.access$2900(ExpressTurn keyTask.java:64) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask$ActualTask.performTurnk ey(ExpressTurnkeyTask.java:239) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask$ActualTask.<init>(Expre ssTurnkeyTask.java:132) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask$1.construct(ExpressTurn keyTask.java:110) at com.adobe.livecycle.lcm.core.tasks.SwingWorker$2.run(SwingWorker.java:114) at java.lang.Thread.run(Thread.java:595) Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.net.DSCSocketTimeoutException: Internal error. at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.throwExceptionHandler(So apAxisDispatcher.java:199) at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatche r.java:125) at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57) at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208) at com.adobe.idp.dsc.registry.component.client.ComponentRegistryClient.invoke(ComponentRegis tryClient.java:373) at com.adobe.idp.dsc.registry.component.client.ComponentRegistryClient.install(ComponentRegi stryClient.java:131) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.installComponentUsingDoc(DeployDSCs .java:585) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.installComponent(DeployDSCs.java:56 3) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.installAndStartComponent(DeployDSCs .java:554) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:363) ... 8 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:235) at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatche r.java:123) ... 16 more [2009-02-05 13:25:44,620], SEVERE, Thread-39, com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, Echec du déploiement du composant C:\Adobe\LiveCycle8.2\deploy\adobe-rightsmanagement-jboss-dsc.jar. com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Echec du déploiement du composant C:\Adobe\LiveCycle8.2\deploy\adobe-rightsmanagement-jboss-dsc.jar. at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:396) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(DeployDSCs.java:149) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask.deployDSCs(ExpressTurnk eyTask.java:457) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask.access$2900(ExpressTurn keyTask.java:64) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask$ActualTask.performTurnk ey(ExpressTurnkeyTask.java:239) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask$ActualTask.<init>(Expre ssTurnkeyTask.java:132) at com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressTurnkeyTask$1.construct(ExpressTurn keyTask.java:110) at com.adobe.livecycle.lcm.core.tasks.SwingWorker$2.run(SwingWorker.java:114) at java.lang.Thread.run(Thread.java:595) Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.net.DSCSocketTimeoutException: Internal error. at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.throwExceptionHandler(So apAxisDispatcher.java:199) at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatche r.java:125) at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57) at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208) at com.adobe.idp.dsc.registry.component.client.ComponentRegistryClient.invoke(ComponentRegis tryClient.java:373) at com.adobe.idp.dsc.registry.component.client.ComponentRegistryClient.install(ComponentRegi stryClient.java:131) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.installComponentUsingDoc(DeployDSCs .java:585) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.installComponent(DeployDSCs.java:56 3) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.installAndStartComponent(DeployDSCs .java:554) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:363) ... 8 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:235) at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatche r.java:123) ... 16 more

Unable to see deployed component in webdynpro content administrator

Hi,
I created a DC under sap.com domain in one of the tracks and was able to checkin and activate that deploy that successfully,
When i looked at the deployment log and activation log it says component is successfully deployed.
I looked in the DTR and CBS and I could see the deployed component
But when i look at the deployed components in Webdynpro content administrator under sap.com it is not showing the DC which i created and deployed.
What is the wrong with the deployment
Please let me know what is the solution
Points will be awarded for sure
Bala

Hi,
1. Did you try searching through content administrator->web dynpro->'Search' tab for the relevant object?
2. It seems that the runtime system you are looking at is configured with the "Disable automatic deployment" option in the CMS. Pls check the status.
3. If it so, you can start manual deployment as follows:
a. Start the deployment servlet using http://<CBS_host>:<port>/TCS/Deployer
b. In the "Buildrequests in queue" list, select the "buildspace name" for which you want to start the deployment and enter this name in the Buildspace field.
c. Select "Submit".
This will perform the deployment action.
Regards
Srinivasan T

Deploy OBIEE 11g into WebCenter

Can someone give me step by step instruction of how to deploy OBIEE Portlets into WebCenter? I don't need the high level explainations. For example, if I will need to create a .war file please tell me which files need to be included in that war file. Thanks.

Oracle BI EE 10.1.3.3/2 – Deploying JSR 168 Portlets – Displaying Reports in Web Center Suite using JDeveloper
Please refer this:
As you would probably know, BI EE by default comes pre-bundled with JSR-168 portlets that can be deployed in any standard Portal that complies with WSRP and JSR-168 standards. So basically one can access the BI EE reports from any standard compliant portal. Today we shall see how to go about using these compliant portlets to retrieve a sample report into Web Center Suite using JDeveloper. The entire process can be divided into 3 main phases. They are
1. Deploying WSRP Java Containers in an Oracle Application Server - Phase 1
2. Deploying BI EE JSR 168 portlets into the above WSRP Java container - Phase 2
3. Calling BI EE reports from Web Center suite using the above deployed Portlet - Phase 3
In my case, i have the following list of components.
1. BI EE running on a standalone OC4J in a laptop (say Machine A)
2. A standard Oracle Application Server (10.1.2 or above) running on a seperate Machine (say Machine B. This is where we will deploy the Portlets). This Application Server has Portal and Wireless installed.
3. JDeveloper (10.1.3.2 or above since they get bundled with a Web Center Suite OC4J) on Machine A.
Phase 1:
For Phase 1 ie to install the WSRP container, the documentation is very clear and you can get the list of the step by step instructions here
Phase 2:
1. Once the WSRP container has been created (in my case i have created a container called wsrp), go to {OracleBI}\web\sdk. There you would find a file called sawjsr168portlets.war. Copy this file to a local folder like D:\Portlets.
2. Open a command prompt and navigate to D:\Portlets folder( the folder to which we copied the jsr168portlets.war file). Now type in the following command
jar -xf sawjsr168portlets.war
What this would do is it would open up the war file and will expose the contents in the same directory. So, you basically can see new directories like WEB-INF that would get created.
3. Now go to D:\Portlets\WEB-INF and open the Portlets.xml file in a text editor. Search for oracle.bi.presentation.sawserver.URL and in the “value” tag enter the URL of the BI EE presentation services.
For example
<preference>
<name>oracle.bi.presentation.sawserver.URL</name>
<value>http://10.176.246.99:9704/analytics/saw.dll</value>
<read-only>false</read-only>
</preference>
Search for oracle.bi.presentation.portlets.jsr168.reportui.AdminUserName and enter Administrator in the value tag. For example
<preference>
<name>oracle.bi.presentation.portlets.jsr168.reportui.AdminUserName</name>
<value>Administrator</value>
<read-only>false</read-only>
</preference>
Search for oracle.bi.presentation.portlets.jsr168.reportui.AdminPwd and enter the password for the Administrator user. For example
<preference>
<name>oracle.bi.presentation.portlets.jsr168.reportui.AdminPwd</name>
<value>welcome1</value>
<read-only>false</read-only>
</preference>
Search for oracle.bi.presentation.report.Path and enter a report URL. For example
<preference>
<name>oracle.bi.presentation.report.Path</name>
<value>/shared/paint demo/demo report</value>
<read-only>false</read-only>
</preference>
4. Now open up web.xml in a text editor. Search for com.siebel.analytics.web.SAWServer.Host and enter the machine name/ip where BI EE is hosted. For example,
<init-param>
<param-name>com.siebel.analytics.web.SAWServer.Host</param-name>
<param-value>10.176.246.99</param-value>
</init-param>
5. Now go back to D:\portlets via command prompt and enter the following commands.
jar -uf sawjsr168portlets.war WEB-INF\portlet.xml
jar -uf sawjsr168portlets.war WEB-INF\web.xml
This would update the war file with the changes that we made above.
6. Now go to the Application Server enterprise manager and Deploy this war file inside the WSRP container that was created above. i have used biee and /biee for the application name and its URL. Ensure that you are able to access the WSDL using the URL http://MIDTIERHOST:PORT/biee/portlets?WSDL
Now our Phase 2 is complete.
Phase 3:
1. Open JDeveloper 10.1.3.2 and create a sample application using Webcenter Application as the template.
2. Now lets register the portlet that we deployed above. Give it some name and enter the WSDL url while doing the registration. After that click on finish (keep everything else default).
3. Once registered create a simple JSF-JSP page and include this portlet that we registered from the Component Pallette. Ensure that you are exposing the UI components with some sample class names.
4. Now execute this JSP. You should see the sample report output.
You can also pass the report path dynamically from within web center suite. You need to bind the parameter to the URL.

Error while deploying the application into 11.1.1.2

Hi,
I am trying to deploy the application into Jdev 11.1.1.2 i am getting the following error.
04:11:39 PM] Wrote Enterprise Application Module to C:\Documents and Settings\rkanigolla.admin\Application Data\JDeveloper\system11.1.1.2.36.55.36\o.j2ee\drs\ESPSApp
[04:11:39 PM] Deploying Application...
<Nov 25, 2009 4:11:55 PM MST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1259190702422' for task '0'. Error is: 'java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory'
java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace>
<Nov 25, 2009 4:11:55 PM MST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'ESPSApp [Version=V2.0]'.>
<Nov 25, 2009 4:11:55 PM MST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace>
#### Cannot run application ESPSApp due to error deploying to IntegratedWebLogicServer.
[04:11:55 PM] #### Deployment incomplete. ####
[04:11:55 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
[Application ESPSApp stopped and undeployed from Server Instance IntegratedWebLogicServer]
Please help me how can i resolve this.

Hi,
Thanks for you reply.
We are trying to Run/deploy the application in jdev 11.1.1.1.2.0 that was developed in jdev 11.1.1.1.0. We are getting the following exception,
<Nov 25, 2009 6:38:22 PM MST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1259199473394' for task '0'. Error is: 'java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory'
java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
Truncated. see log file for complete stacktrace
But the same application with some other system is working fine.

Deploying Enterprise Archive into weblogic 10.3.4.0 application server

Hi All,
I am trying to deploy enterprise archive into web-logic application server. This ear contains two modules. web service module and web application module.
This application was previously running on Apache tomcat server and now i am migrating to web-logic application server.
I am getting following error when deploying to the web-logic application server. Below exception.
For web service and web application, I am using Hibernate and Spring frameworks. Following are the dependencies of web service
[INFO] ------------------------------------------------------------------------
[INFO] Building WebServiceModule Maven Webapp 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ MavenWebAppModule ---
[INFO] com.packt.maven:MavenWebAppModule:war:1.0-SNAPSHOT
[INFO] +- com.packt.maven:BusinessLogicModule:jar:1.0-SNAPSHOT:compile
[INFO] | +- com.packet.maven:DataPersistanceModule:jar:1.0-SNAPSHOT:compile
[INFO] | \- com.packt.maven:DataModelModule:jar:1.0-SNAPSHOT:compile
[INFO] +- com.packt.maven:WebServiceClientModule:jar:1.0-SNAPSHOT:compile
[INFO] +- org.apache.struts:struts2-core:jar:2.1.8:compile
[INFO] | +- com.opensymphony:xwork-core:jar:2.1.6:compile
[INFO] | | \- org.springframework:spring-test:jar:2.5.6:compile
[INFO] | +- org.freemarker:freemarker:jar:2.3.15:compile
[INFO] | +- ognl:ognl:jar:2.7.3:compile
[INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
[INFO] | \- commons-io:commons-io:jar:1.3.2:compile
[INFO] +- org.apache.struts:struts2-spring-plugin:jar:2.1.8:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-core:jar:2.5.6:compile
[INFO] | \- org.springframework:spring-context:jar:2.5.6:compile
[INFO] | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] +- xml-apis:xml-apis:jar:1.0.b2:provided (scope not updated to compile)
[INFO] +- javassist:javassist:jar:3.12.1.GA:compile
[INFO] +- com.oracle:ojdbc6:jar:11.2.0:compile
[INFO] +- org.springframework:spring:jar:2.5.6:compile
[INFO] +- org.springframework:spring-web:jar:2.5.6:compile
[INFO] +- org.hibernate:hibernate:jar:3.2.7.ga:compile
[INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] | +- javax.transaction:jta:jar:1.0.1B:compile
[INFO] | \- asm:asm-attrs:jar:1.5.3:compile
[INFO] +- dom4j:dom4j:jar:1.6.1:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] +- cglib:cglib:jar:2.2:compile
[INFO] +- antlr:antlr:jar:2.7.7:compile
[INFO] +- asm:asm:jar:3.3:compile
[INFO] +- javax.xml.soap:saaj-api:jar:1.3.3:compile
[INFO] | \- javax.activation:activation:jar:1.1:compile
[INFO] +- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.4:compile
[INFO] | \- org.jvnet:mimepull:jar:1.4:compile
[INFO] \- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO]
Following are the dependencies of maven web app module
[INFO] ------------------------------------------------------------------------
[INFO] Building MavenWebAppModule Maven Webapp 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ WebServiceModule ---
[INFO] com.packt.maven:WebServiceModule:war:1.0-SNAPSHOT
[INFO] +- org.springframework:spring:jar:2.5.6:compile
[INFO] +- org.springframework:spring-web:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-context:jar:2.5.6:compile
[INFO] | | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] | \- org.springframework:spring-core:jar:2.5.6:compile
[INFO] +- xml-apis:xml-apis:jar:1.0.b2:provided (scope not updated to compile)
[INFO] +- javax:javaee-api:jar:6.0:provided
[INFO] +- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO] +- com.oracle:ojdbc6:jar:11.2.0:compile
[INFO] +- org.hibernate:hibernate:jar:3.2.7.ga:compile
[INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] | +- javax.transaction:jta:jar:1.0.1B:compile
[INFO] | \- asm:asm-attrs:jar:1.5.3:compile
[INFO] +- dom4j:dom4j:jar:1.6.1:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] +- cglib:cglib:jar:2.2:compile
[INFO] +- antlr:antlr:jar:2.7.7:compile
[INFO] +- com.sun.xml.ws:jaxws-rt:jar:2.2.3:compile
[INFO] | +- javax.xml.ws:jaxws-api:jar:2.2.3:compile
[INFO] | | +- javax.xml.bind:jaxb-api:jar:2.2.2:compile
[INFO] | | \- org.glassfish:javax.annotation:jar:3.1-b35:compile
[INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile
[INFO] | +- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.8:compile
[INFO] | +- com.sun.xml.stream.buffer:streambuffer:jar:1.2:compile
[INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.1:compile
[INFO] | | \- stax:stax-api:jar:1.0.1:compile
[INFO] | +- org.jvnet.staxex:stax-ex:jar:1.4:compile
[INFO] | | \- javax.xml.stream:stax-api:jar:1.0-2:compile
[INFO] | +- com.sun.org.apache.xml.internal:resolver:jar:20050927:compile
[INFO] | +- org.jvnet:mimepull:jar:1.5:compile
[INFO] | +- com.sun.xml.ws:policy:jar:2.2.2:compile
[INFO] | | +- com.sun.xml.txw2:txw2:jar:20090102:compile
[INFO] | | \- com.sun.istack:istack-commons-runtime:jar:2.2.1:compile
[INFO] | +- org.glassfish.gmbal:gmbal-api-only:jar:3.1.0-b001:compile
[INFO] | | \- org.glassfish.external:management-api:jar:3.0.0-b012:compile
[INFO] | \- org.glassfish.ha:ha-api:jar:3.1.8:compile
[INFO] +- asm:asm:jar:3.3:compile
[INFO] \- org.jvnet.jax-ws-commons.spring:jaxws-spring:jar:1.8:compile
[INFO] +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] +- org.apache.xbean:xbean-spring:jar:2.7:compile
[INFO] +- javax.jws:jsr181-api:jar:1.0-MR1:compile
[INFO] +- javax.xml.soap:saaj-api:jar:1.3:compile
[INFO] +- com.sun.xml.stream:sjsxp:jar:1.0:compile
[INFO] +- javax.annotation:jsr250-api:jar:1.0:compile
[INFO] \- javax.activation:activation:jar:1.1:compile
[INFO]
In my weblogic application configuration i have provided following configuration to load java from my applications first. Could anybody help me on this issue. Thanks in advance for anyhelp
<?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://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.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>antlr.*</wls:package-name>
 </wls:prefer-application-packages>
</wls:weblogic-application>
Exception.......
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.sun.xml.ws.transport.http.servlet.SpringBinding#0' defined in ServletContext resourcepring/config/SpringBeans.xml]: Cannot create inner bean '(inner bean)' of type [org.jvnet.jax_ws_commons.spring.SpringService] while setting bean property 'service'; nested exceramework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exception is java.lang.Linkageaint violation: when resolving field "DATETIME" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the referring class, javax/xml/datatype/Datahe class loader (instance of <bootloader>) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:230)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1245)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1010)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exceptiogeError: loader constraint violation: when resolving field "DATETIME" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the referring class, jtatypeConstants, and the class loader (instance of <bootloader>) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type
Edited by: user8643895 on Apr 14, 2013 3:42 AM

This forum is about iAS. For weblogic go to: WebLogic Server - General

Deploying a Portlet into Weblogic

Hi Folks,
I have a basic question about deploying a portlet into weblogic.
I created a simple JSF/ADF application and used the Portlet Bridge to "Portletize" it.
When I run the application using JDev11 everything works fine, but If I try to deploy it into a standalone weblogic I got errors
related with missing libraries.
The question is, Do I need to have Oracle Webcenter installed in this standalone weblogic server, in order to support my application deploy?
TIA,
Luis

Hi Luis,
For a portletized ADF application to be deployed on webcenter, it requires even the OC4J containers to be pre-configured.
Basically, any webcenter application or the Portletized ADF applications require oracle.wsrp library to be present in the container's library.
Please check in your Weblogic container if it is present. If not, check how to Pre-Configure the weblogic container, ideally, oracle should provide an executable or some command to make it pre-configured.
I am aware of these steps to perform on Application Server 10g's Container. Oracle should have its containers pre-configured in 11g, but if they are not, you need to follow the same steps.
As far as JDeveloper iis concerned, both the Embedded OC4J as well as the in built server which is Preconfigured Server are as the name suggests pre-configured. Hence, everything works fine when you run from JDev. But same is not the case with Contianers in server. So, we need to explicitly make them pre-confgired to start running these Portletized ADF Applications.
Hope this answer helps you.
Regards,
Kunal Chheda.

How to deploy repository manually in OBIEE 11g

Hi,
I understand that the RPD to be deployed in EM(enterprise Manager) in OBIEE 11g. But unfortunatley we are unable to open core-application in EM for RPD Deployment. The EM is very slow.
Can any one help me in deploying RPD MANUALLY or by using some command prompts other than in EM..
Thanks.

You have to disable the central configuration:
http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10541/disable_em.htm#BEIIAEGD
Change your repository in the file nqsconfig.ini
and
change the password if needed in the credential store ...
http://gerardnico.com/wiki/_detail/dat/obiee/obiee11g_credential_store.jpg?id=dat%3Aobiee%3Acredential
But if you can't open EM, it will be very difficult and may be you must have to add resource (memory, ...) to your server.
Success
Nico

IFD Import into LiveCycle Error

I am able to open an .ifd file in Output Designer 5.5 but I receive an error when trying to import it into LiveCycle Designer. I receive the following message, "XML parsing error: no element found (error code 3), line 1, column 1, of file ..." Anyone have a clue about what the problem might be?

XML is a file type not /usually/ imported, but you should be
able to
create a text member and set it's filename to the XML file.
Try
something like (executed from your message window):
tMember = _movie.newMember(#text)
tMember.name = "XML document"
tMember.filename = "pathToXML"
tMember.linked = 0

How to check who has deployed a PAR into the portal

Hi there,
is there any log from which can be checked who has deployed a PAR into the portal (probably using NWDS directly)?!
Thanks in advance
Praveen

Hello Praveen,
You can find the user info from the trace files which are located in usr/sap/SID/DVEBMGS<SysNo.>/j2ee/cluster/server0/log/ subfolders.
Try to extract the info from the Tracefiles.
Again if you have the Logviewer configured then you might be able to find the same info there too.
Regards,
Premkishan

Got this error after deploying ear file into OC4J server.

Hello Frnsz,
Can any one help to resolve the following error :)
Got this error after deploying ear file into OC4J server.
2008-06-04 14:57:58.551 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/pager-taglib.tld
2008-06-04 14:57:58.566 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.566 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-bean.tld
2008-06-04 14:57:58.598 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.598 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-html.tld
2008-06-04 14:57:58.629 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.629 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-logic.tld
2008-06-04 14:57:58.660 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.660 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-nested.tld
2008-06-04 14:57:58.691 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:57:58.691 WARNING J2EE JSP-0027 Errors parsing file:/C:/Program Files/Java/oc4j/j2ee/home/applications/MyEarProject/MyEarProjectWeb/WEB-INF/tld/struts-tiles.tld
2008-06-04 14:57:58.723 NOTIFICATION Binding web application(s) to site default-web-site ends...
2008-06-04 14:57:58.723 NOTIFICATION Application Deployer for MyEarProject COMPLETES. Operation time: 3422 msecs
2008-06-04 14:58:04.895 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.910 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.926 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.942 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.957 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 JSP Tld Cache Logging:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.973 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:04.989 WARNING J2EE JSP-0003 loading Tld's into cachedConfigTable:
2008-06-04 14:58:05.020 NOTIFICATION J2EE JSP-0008 Unable to dispatch JSP Page : Exception:oracle.jsp.parse.JspParseException: /WEB-INF/jsp/login.jsp: Line # 2, <%@ taglib uri="/WEB-INF/tld/struts-html.tld" prefix="html"%>
Error: java.lang.ClassNotFoundException: org.apache.struts.taglib.html.MessagesTei
Cheers,
Cap

Cross posted in correct forum
[http://forum.java.sun.com/thread.jspa?threadID=5302192]

Importing large margined PDF documents into LiveCycle

I have a PDF document with very large margins (height approx A4 x1; width approx A4 x5). When I go to import this PDF into LiveCycle to start making an eForm, only part of the PDF is displayed in the Design View tab. The remainder of the document is available for viewing in the Preview PDF tab. Can you tell me how I can set the margins in the Design View tab so I can continue completing the form?
Here are some screenshots of what I mean...
Design View tab -
Preview PDF tab -
Can someone tell me how I can increase the viewable magins in the Design View so I can continue creating this eForm?
Thanks,
Andy

Please double click on Design View and check if this works.
Thanks,
Wasil

How to deploy the project into my weblogic Application Server?

How do I deploy the project into my weblogic Application Server? Should it be fine if I copy the project folder to the AS root?
Also, How should i invoke the Context sensitive help from Javascript assuming project deployed to Weblogic AS.
I am using Robohelp 10.
Thanks in advance.

Hi,
You generate the help and then you copy the generated output to the server.
For context sensitivity, which output are you using? Try the following
pages for more info:
http://www.grainge.org/pages/authoring/calling_webhelp/calling_webhelp.htm
http://www.wvanweelden.eu/article-category/context-sensitivity
Greet,
Willam

*HOW TO INSERT DATA MANUALLY INTO A BW TABLE*

Dear experts,
I'm working in BW 3.5 version.
Since I need to test some tables which are going to be load manually, please could anyone explain me which are the steps to insert data manually into a BW table.
Thank you very much in advance,
Jorge

Hi Jorge,
You can maintain the TMG(Table maintenance generator) and then enter the data manually. TMG creation Tcode is se55. and to view and maintain TMG it is sm30 .
Or if you have the data in excel. You can write a simple excel uploading ABAP program which will load your excel data to the table .
Hope the above reply was helpful.
Thanks & Regards,
Ashutosh Singh
Edited by: Ashutosh Singh on Apr 30, 2011 6:45 AM

Deploy component manually into LiveCycle

Similar Messages

Maybe you are looking for