Deployment error in .ear in portal project
After starting admin server in workshop for weblogic, I am trying to publish the .ear portal project.
But its giving the following error,
weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)Unable to deploy EJB: ProxyPagePersistenceManager from netuix.jar:
Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
Exception Stack Trace:
java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1557)
at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:469)
at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1329)
at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:787)
at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:607)
at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:503)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
Unable to deploy EJB: ProxyPagePersistenceManager from netuix.jar:
Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.ejb20.interfaces.PrincipalNotFoundException: Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
at weblogic.ejb.container.internal.SecurityHelperWLS.deployPolicy(SecurityHelperWLS.java:357)
at weblogic.ejb.container.internal.SecurityHelper.deployPolicy(SecurityHelper.java:306)
at weblogic.ejb.container.internal.SecurityHelper.deployPolicy(SecurityHelper.java:294)
at weblogic.ejb.container.internal.SecurityHelper.deployAllPolicies(SecurityHelper.java:249)
at weblogic.ejb.container.internal.SecurityHelper.deployAllPolicies(SecurityHelper.java:228)
at weblogic.ejb.container.internal.RuntimeHelper.deployAllPolicies(RuntimeHelper.java:249)
at weblogic.ejb.container.deployer.EJBDeployer.deployAllPolicies(EJBDeployer.java:770)
at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:934)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1188)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425)
FYI, I am using Oracle Weblogic server v10.3 and pointbase DB.
I was unable to resolve it....!!
Just found a workaround...I didnt' used a EAR after that....
But still this SAP note could help u out.....!!
Deployement error in EAR DC
Required note is :
SAP Note Number: 1270242
"None of the available containers recognized the components"
Similar Messages
-
Hot Deploy Error - Build your first Portal
The following is the error I got when I tried to hot deploy a portal in EBCC for
welogic 7.0:
"Not found" error occurred when connecting to server. Please go to Connection
Settings and check service names.
Any help on that will be greatly appreciated?
Thanks,
RitaRita,
Is you server running? This means that an HTTP 404 was returned when trying
to access the DataSyncServlet. Check your server name, port, application
name etc. under the Connection Settings.
If you want to verify the URL you can just hit it with a web browser. It
should look something like:
http://locahost:7501/p13nAppDataSync/DataSyncServlet (for an application
called 'p13n')
Sincerely,
Daniel Selman
"Rita" <[email protected]> wrote in message
news:3d3ef190$[email protected]..
>
The following is the error I got when I tried to hot deploy a portal inEBCC for
welogic 7.0:
"Not found" error occurred when connecting to server. Please go toConnection
Settings and check service names.
Any help on that will be greatly appreciated?
Thanks,
Rita -
Getting Deploy Error when using the WebDynpro Compiler
Hi,
I have a VC application which uses the RFC from R/3.
When i am using the Compiler as WEBDYNPRO, it is giving me Deploy Error as:
WebDynpro Compiler:
Portal request failed
(Model properties Namespace and Vendor are not specified for source archieve generator)
Also,
I checked the Iview property in the Portal but i am unable to find this properties.
Guide me when and where this Complier type is uesd..?
Thanks & Regards,
Dhruv ShahHi,
I am unable to find this properties.
In the Model View i searched a lot.
I have another question also.
Do you know how to refresh the table from the RFC.
Thanks& regards,
Dhruv Shah -
Error when I deployed the java EAR application in NWDS 7.1
HI All,
I got the error when I deployed the java EAR application in NWDS 7.1 version..help me out...........................................
com.sap.ide.eclipse.deployer.api.APIException: DeployException,cause=[ERROR CODE DPL.DCAPI.1023] AuthorizationException.
Reason: , An error occurred during the deployer retrieval. Cause =[ERROR CODE DPL.DC.3151] The user LJ4PJW could not be authorized, because doesn't own the (com.sap.engine.interfaces.security.ServiceAccessPermission dc) permission for deploy controller. at com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
Thanks
CostaThe user LJ4PJW could not be authorized, *because doesn't own the* (com.sap.engine.interfaces.security.ServiceAccessPermission dc) *permission for deploy controller. a*t com.sap.ide.eclipse.deployer.dc.ComponentManagerImpl.getDeployProcessor(ComponentManagerImpl.java:62)
The user is not have proper authorizations. Use some other administrators user id which has all admin roles and authorizations assigned and try to deploy.
Regards,
Ravi -
Error deploying 2 processes in the same project BPM 11gR3 Project
Hi I have a problem to deploy a project in OBPM 11gR3.
I have 2 processes on the same project, and tried separately on different projects and working properly. But when I put in the same project I get the following error.
[02:09:38 PM] Sending internal deployment descriptor
[02:09:38 PM] Sending archive - sca_BPM_CGEO_PROJECT_rev1.0.jar
[02:09:47 PM] Received HTTP response from the server, response code=500
*[02:09:47 PM] Error deploying archive sca_BPM_CGEO_PROJECT_rev1.0.jar to partition "default" on server soa_server1 [auohscgeo20.oracleoutsourcing.com:40513]*
[02:09:47 PM] HTTP error code returned [500]
[02:09:47 PM] Error message from server:
Error during deployment: Deployment Failed: Error occurred during deployment of component: BPMCGEOPROCESOGENERACIONCONTRATOVENTA to service engine: implementation.bpmn, for composite: BPM_CGEO_PROJECT: java.lang.NullPointerException.
[02:09:47 PM] Check server log for more details.
[02:09:47 PM] Error deploying archive sca_BPM_CGEO_PROJECT_rev1.0.jar to partition "default" on server soa_server1 [auohscgeo20.oracleoutsourcing.com:40513]
[02:09:47 PM] #### Deployment incomplete. ####
[02:09:47 PM] Error deploying archive file:/D:/Archivos/Casas GEO/SRC/GEO/BPM/BPM_CGEO_APPLICACION/BPM_CGEO_PROJECT/deploy/sca_BPM_CGEO_PROJECT_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Edited by: Eduardo.Reyes on 28-mar-2011 18:01Hi Eduardo
This may not help but I am getting a similar problem and I have a possible workaround.
I'm not a BPM expert though so...
I have got a Null Pointer Exception, three times successively attempting to redeploy a BPMN Process SAR to WLS via JDeveloper only after I've added a new process to the project and attempted to redeploy.
[05:45:17 PM] HTTP error code returned [500]
[05:45:17 PM] Error message from server:
Error during deployment: Error occurred during deployment of component: Responder313Process to service engine: implementation.bpmn, for composite: nicolson-soasuite-bpmn-ipc: java.lang.NullPointerException.
[05:45:17 PM] Check server log for more details.
The only way I can stop this Exception is to Undeploy the existing Process via Enterprise Manager, Stop and Restart WLS. (Which is very tedious...).
To explain, I'm working though the various uses of Send/Receive tasks as described in Modeling and Implementation Guide for Oracle Business Process Management 11g Release 1 (11.1.1.4.0) - 6.4 Communicating With Other Processes and Services.
So I have about five scenarios, each with a simple Caller/Responding process and each with some very simple combination of Send/Receive tasks. When the deployment works, the process communications test fine via EM.
Personally, this looks like a bug. I'm using version below on Win XP SP3.
About
Oracle JDeveloper 11g Release 1 11.1.1.3.0
Studio Edition Version 11.1.1.3.0
Build JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660
Copyright © 1997, 2010 Oracle and/or its affiliates. All rights reserved.
IDE Version: 11.1.1.3.37.56.60
Product ID: oracle.jdeveloper
Product Version: 11.1.1.3.37.56.60
Version
Component Version
========= =======
ADF Business Components 11.1.1.56.60
BPMN Editor 11.1.1.3.0.6.84
Java(TM) Platform 1.6.0_18
Oracle IDE 11.1.1.3.37.56.60
SOA Composite Editor 11.1.1.3.0.25.57
Versioning Support 11.1.1.3.37.56.60
Regards
Jim Nicolson -
Not able to deploy portal projects
Hi all,
I am trying to deploy .net iviews on the portal but I am not able to deploy it. Its giving time out error. Neither I am able to view any .net iviews that were already deployed on the portal. Can anyone help me on this issue.
rgdsMessages in lig file...
#1.5#0002B3D56632003D0000001D000013480003F58C333224DF#1114407432890#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#316##iGateSAP_J2E_9772450#Administrator#0234d570b54811d9a80a0002b3d56632#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/System/Server#Java###Exception ID:01:37_25/04/05_0007_9772450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : PortalApplication4.PortalComponent1
Component class : com.sap.portal.dotnet.framework.iViewProcessorComponent
User : Administrator
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.lang.RuntimeException: .NET server is not running
at com.sap.portal.dotnet.framework.iViewProcessorService.ProcessRequest(iViewProcessorService.java:219)
at com.sap.portal.dotnet.framework.iViewProcessorComponent.doContent(iViewProcessorComponent.java:16)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
#1.5#0002B3D56632004D0000001B000013480003F58C34912FC4#1114407455875#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#316##iGateSAP_J2E_9772450#Administrator#0234d570b54811d9a80a0002b3d56632#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/System/Server#Java###Exception ID:01:37_25/04/05_0008_9772450
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : PortalApplication5.PortalComponent1
Component class : com.sap.portal.dotnet.framework.iViewProcessorComponent
User : Administrator
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.lang.RuntimeException: .NET server is not running
at com.sap.portal.dotnet.framework.iViewProcessorService.ProcessRequest(iViewProcessorService.java:219)
at com.sap.portal.dotnet.framework.iViewProcessorComponent.doContent(iViewProcessorComponent.java:16)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : PortalApplication1.PortalComponent1
Component class : com.sap.portal.dotnet.framework.iViewProcessorComponent
User : Administrator
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.lang.RuntimeException: .NET server is not running
at com.sap.portal.dotnet.framework.iViewProcessorService.ProcessRequest(iViewProcessorService.java:219)
at com.sap.portal.dotnet.framework.iViewProcessorComponent.doContent(iViewProcessorComponent.java:16)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
Someone pls help. -
Global error page for portal project
Hi
This is regarding weblogic 8.1.
We have a portal project which contains several portlets. For handling exceptions
in a page flow we have a global error page at the project root level and each
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed in the portlet
context. How can we make this error page to take up the whole screen and display
it outside of the portlet context so that all other links within the portal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
SameerSameer,
Please post this question to the weblogic.developer.interest.portal
newsgroup.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Sameer Dalal" <[email protected]> wrote in message
news:3f4bd37f$[email protected]..
>
Hi
This is regarding weblogic 8.1.
We have a portal project which contains several portlets. For handlingexceptions
in a page flow we have a global error page at the project root level andeach
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed inthe portlet
context. How can we make this error page to take up the whole screen anddisplay
it outside of the portlet context so that all other links within theportal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer -
Displaying error message on XRPM Portal on changing the status of Project
Hi All,
I want to display an error message on the Portal when user tries to change the status of the Project from 'CREATED' to 'RELEASE' and clicks on SAVE.
I have checked the following BADI's but i am not able to retrieve the newly selected status.
DPR_ATTRIBUTES -> Methods 1) CHECK 2) CHANGE_CHECK
RPM_PROJ_CUST_FIELDS
Any help will be highly appreciated!
Thanks.
Runal.Hi Runal,
I think, the reason is that the status is not attribute of the project, rather a linked object. That is why the Badi method is not get called.
Please check with the Badi DRP_EVENTS, this Badi is typically called, if the status of object is changed.
Kind regards,
Zhenbo -
Error Deploying and Publishing a New BPM Project
I'm trying to Deploying and Publishing a New BPM Project (based on http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html), but the following error:
The size of the attachment exceeds the limit of 10000000 bytes
Thanks and Best Regards,Hi,
There are two options (radio buttons) when you publish and deploy. Right now you are probably picking the second option (to publish and deploy the exported project from Studio).
Try it again using the first option. I haven't had to do it in a while, but using this you should be able to point the Process Admin tool to your project's directory directly and not your export file.
See if that helps,
Dan -
Error deploying J2EE Application (EAR) to standalone OC4J
Hi
I'm invoking the admin_client.jar utility to deploy a webservice on a standalone OC4J, here is the command:
java -jar %OC4J_HOME%\j2EE\home\admin_client.jar deployer:oc4j:localhost:23791 oc4jadmin test -deploy -file C:\10GIDS\BIN\johnTestWS.ear -deploymentname johnsws -bindAllWebApps default-web-site -contextRoot johnsws
I get the following error:
Deploy error: Deploy error: Operation failed with error:Error compiling :C:\JDeveloper_10g\j2ee\home\applications\johnsws\johnTestWS-web: Syntax error in source or compilation failed in: C:\JDeveloper_10g\j2ee\home\application-deployments\johnsws\johnTestWS-web\oracle\generated\runtime\XmlreturnBase__SOAPSerializer.java java.lang.NoClassDefFoundError: com/sun/tools/javac/MainException in thread "main"
The java.lang.NoClassDefFoundError: com/sun/tools/javac/MainException in thread "main" error string (from my limited understanding) would mean there is a jar file missing from the CLASSPATH or something, yet, because the '-jar' option is selected when running the java command I don't have the option to include any classpath in the command string. What am I doing wrong?
I've been trying to assemble and deploy this web service for ages now and I think I'm very close to the end, can someone please show me that I'm doing something very simple wrong....?smydo,
I see you answered yourself in the other forum where you posted the same question:
Problems deploying Web Service to standalone OC4J from Windows command line
Good Luck,
Avi. -
Error while loading SAP Portal
Can anybody help me to resolve the issue of installation of SAP Portal. This is a fresh installation and I got the following error while installing the portal.
I will appreciate any body who helps me to resolve the issue.
Info: Begin of log messages of the target system:
10/10/21 19:52:31 - ***********************************************************
10/10/21 19:52:32 - Start updating EAR file...
10/10/21 19:52:32 - start-up mode is lazy
10/10/21 19:52:32 - EAR file updated successfully for 109ms.
10/10/21 19:52:32 - Start deploying ...
10/10/21 19:52:32 - EAR file uploaded to server for 79ms.
10/10/21 19:52:32 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.dqe.beans..
Reason: Exception during generation of components of application sap.com/com.sapportals.dqe.beans in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.dqe.beans in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:477)
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:291)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.dqe.beans in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:609)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:462)
... 10 more
Caused by: java.lang.NoClassDefFoundError: com/metamatrix/platform/service/api/exception/ServiceException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructors(Class.java:865)
at com.sap.engine.services.ejb.deploy.verifier.BeanClassCheck.check(BeanClassCheck.java:33)
at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:51)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:258)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2057)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
... 16 more
For detailed information see the log file of the Deploy Service.
10/10/21 19:52:32 - ***********************************************************
Info: End of log messages of the target system.
Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Error: Aborted: development component 'com.sapportals.dqe.beans'/'sap.com'/'SAP AG'/'609.20041012204607.0000':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.dqe.beans..
Reason: Exception during generation of components of application sap.com/com.sapportals.dqe.beans in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/com.sapportals.dqe.beans in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not restore state of J2EE Engine now.
Error: -
At least one of the Deployments failed -
Info: Summarizing the deployment results:
Error: Aborted: G:\SoftWare\netweaver\Identified\SAPNETWEAVER041DVD_ADDON\EP-KMC\DQE\SDA\J2EE\com.sapportals.dqe.beans.ear
Processing error. Return code: 4
Error: Processing error. Return code: 4
ERROR 2010-10-21 19:52:33
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\NW04SR1\EP\EP\callSdmViaSapinst.log.Hi,
I believe VISTA is not a recomended OS for SAP Portal, I tried for a week to install and finally gave up
check this
Adventures with NetWeaver Portal 7 - Vista Installation
jo
Edited by: Ravi Joseph on Dec 12, 2008 11:51 AM -
Helps for WLP9.2 in a cluster: deploy errors, propagation errors
I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1 WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1. Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2. Bea private patch: RSGT, fixed cluster deployments.
3. Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4. IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2 Common problems and their fixes
2.1 Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove file: <domain>/config/config.lok
b. Edit file: <domain>/config/config.xml
c. Remove all elements of: <app-deployment> ? </app-deployment>
d. Start the Admin server
e. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2 The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1. Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Perform these clean up steps on one or both managed instances:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3. The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3 Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove directory: <domain>/servers/AdminServer/data/ldap
b. Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c. Start the Admin server
d. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/servers/<managed_name>
b. rm ?rf data
This forces the re-down load of the LDAP directory.
c. Start each managed server.
d. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4 The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1. Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2. Set the correct DB access password encryption in the jdbc/*.xml files.
a. cd <domain>/bin
b. . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c. java weblogic.security.Encrypt <the_db_password>
d. Edit the returned string into every <domain>/config/jdbc/*.xml
e. Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3. Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4. Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5. Start the managed instances.
2.5 Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1 WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1. Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2. Bea private patch: RSGT, fixed cluster deployments.
3. Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4. IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2 Common problems and their fixes
2.1 Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove file: <domain>/config/config.lok
b. Edit file: <domain>/config/config.xml
c. Remove all elements of: <app-deployment> ? </app-deployment>
d. Start the Admin server
e. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2 The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1. Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Perform these clean up steps on one or both managed instances:
a. cd <domain>/config
b. rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c. cd <domain>/servers/<managed_name>
d. rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e. Start each managed server.
f. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3. The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3 Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1. Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a. Find the PID to kill: lsof ?C | grep <listen port number>
b. kill <pid>
c. Run kill again and if the pid is still running then do: kill -9 <pid>
2. Admin server:
a. Remove directory: <domain>/servers/AdminServer/data/ldap
b. Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c. Start the Admin server
d. Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3. Both Managed servers:
a. cd <domain>/servers/<managed_name>
b. rm ?rf data
This forces the re-down load of the LDAP directory.
c. Start each managed server.
d. Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4 The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1. Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2. Set the correct DB access password encryption in the jdbc/*.xml files.
a. cd <domain>/bin
b. . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c. java weblogic.security.Encrypt <the_db_password>
d. Edit the returned string into every <domain>/config/jdbc/*.xml
e. Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3. Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4. Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5. Start the managed instances.
2.5 Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts. -
Deployment error in OC4J_Portal instance during install of o9iASW
Hi,
After the installation of the 9.0.2 infrastructure I've installed wireless. During the deployment of the webtool, customization, wirelessSDK in the OC4J_Portal instance I got the following error:
Deploying application 'webtool' to OC4J instance 'OC4J_Portal'...
ERROR: Deploy failed.
Error message returned is: Instance: orawireless.portal.ucc.nl Message: See base exception for details.
Base Exception:
java.lang.NullPointerException:nullSee base exception for details.
Deploying application 'customization' to OC4J instance 'OC4J_Portal'...
ERROR: Caught exception during deploy.
Deploying application 'wirelessSDK' to OC4J instance 'OC4J_Portal'...oracle.ias.sysmgmt.exception.TaskException: The
configuration files for this Oracle9iAS instance are inconsistent with the
configuration stored in the repository. In order to protect the repository,
no further configuration or deployment operations are allowed until the problem with the configuration on the filesystem
is resolved. This condition arises when a prior operation was unsuccessful. Please check the logs located at
ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating
the configuration files on disk. Some possible causes are:
* permissions on files
* file contention issues on Windows NT
* EMD and dcmctl running concurrently
* internal Oracle error
After resolving the problem that prevented DCM from updating the configuration
files, you may use the dcmctl resyncInstance command to resolve the problem.
Alternatively, you can stop and then restart the active dcmctl or EMD
process and resyncInstance will automatically be performed.
at oracle.ias.sysmgmt.task.TaskMaster.evaluate(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.ApplicationDeployment.deployCommon(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.ApplicationDeployment.deploy(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.EarDeployerImpl.deploy(Unknown Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.deploy(Unknown Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.main(Unknown Source)
ERROR: Caught exception during deploy.
Deploying application 'studio' to OC4J instance 'OC4J_Portal'...oracle.ias.sysmgmt.exception.TaskException: The
configuration files for this Oracle9iAS instance are inconsistent with the
configuration stored in the repository. In order to protect the repository,
no further configuration or deployment operations are allowed until the problem with the configuration on the filesystem
is resolved. This condition arises when a prior operation was unsuccessful. Please check the logs located at
ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating
the configuration files on disk. Some possible causes are:
* permissions on files
* file contention issues on Windows NT
* EMD and dcmctl running concurrently
* internal Oracle error
After resolving the problem that prevented DCM from updating the configuration
files, you may use the dcmctl resyncInstance command to resolve the problem.
Alternatively, you can stop and then restart the active dcmctl or EMD
process and resyncInstance will automatically be performed.
at oracle.ias.sysmgmt.task.TaskMaster.evaluate(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.ApplicationDeployment.deployCommon(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.ApplicationDeployment.deploy(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.EarDeployerImpl.deploy(Unknown Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.deploy(Unknown Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.main(Unknown Source)
ERROR: Caught exception during deploy.
Stopping OC4J instance 'OC4J_Portal'...oracle.ias.sysmgmt.exception.TaskException: The configuration files for this
Oracle9iAS instance are inconsistent with the
configuration stored in the repository. In order to protect the repository,
no further configuration or deployment operations are allowed until the problem with the configuration on the filesystem
is resolved. This condition arises when a prior operation was unsuccessful. Please check the logs located at
ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating
the configuration files on disk. Some possible causes are:
* permissions on files
* file contention issues on Windows NT
* EMD and dcmctl running concurrently
* internal Oracle error
After resolving the problem that prevented DCM from updating the configuration
files, you may use the dcmctl resyncInstance command to resolve the problem.
Alternatively, you can stop and then restart the active dcmctl or EMD
process and resyncInstance will automatically be performed.
at oracle.ias.sysmgmt.task.TaskMaster.evaluate(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.ApplicationDeployment.deployCommon(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.ApplicationDeployment.deploy(Unknown Source)
at oracle.ias.sysmgmt.deployment.j2ee.console.EarDeployerImpl.deploy(Unknown Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.deploy(Unknown Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.main(Unknown Source)
done.
DCM Terminated.
The error in the file "log.xml" at ORACLE_HOME/dcm/logs shows the following error:
[CDATA[oracle.ias.repository.schema.SchemaException: Unable to retrieve the requested
attributes:javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient Access Rights]; remaining name
'orclReferenceName=iasdb.hostname ,cn=IAS Infrastructure Databases, cn=IAS, cn=Products, cn=OracleContext'
On metalink I've found out that more people have had this problem. I've read about bug 2507365 and a patch in 9.0.3 but I couldn't find a real solution for the problem.
Does this error has something to do with a confuguration of a previous installation of another user?
Is there an easy way to work around this problem? Can I change something in the access rights and deploy the wireless administration tools in the OC4J_Portal instance manually? Would safe me a lot of time.
Thanks in advance for your help.
Regards,
ThomasI've found a topic on Metalink named "Manually deploy oc4j_portal?" but I couldn't get access to it.
(http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&p_id=265286.996)
I have two application server instances on one machine with the Windows2000 Server OS (sp2)
The infrastucture instance:
ora9ias_home
The wireless instance:
ora9iasw_home
* The following services are up and running in ora9ias_home:
-HTTP Server
-Internet Directory
-OC4J_DAS
-Single Sign-On:orasso:7777
The Internet Directory instance:
-Repository <hostname>:1521:iasdb :UP
-Directory Integration :UP
-Directory Replication :DOWN
-LDAP Metrics (Configure) : DOWN
I'm able to log on the OID via SSO with the orcladmin user
* The following services are up and running in ora9iasW_home:
-HTTP Server
-OC4J_Portal (the instance is UP but the studio/customization/webtool instances need to be deployed)
-OC4J_Wireless
-Web Cache
-Wireless
The following schema is configured:
WIRELESS Oracle iAS Wireless <hostname>:1521:iasdb
So the instances in the OC4J_Portal were not deployed during installation. After trying to manually deploy
the webtool.ear and associate the usermanager with JAZN LDAP User Manager (ldap://<hostname>:4032). I get the
following error:
"An error occurred while redeploying the application. The configuration files for this Oracle9iAS instance
are inconsistent with the configuration stored in the repository. In order to protect the repository, no
further configuration or deployment operations are allowed until the problem with the configuration on the
filesystem is resolved. This condition arises when a prior operation was unsuccessful. Please check the
logs located at ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating the configuration
files on disk. Some possible causes are: * permissions on files * file contention issues on Windows NT *
EMD and dcmctl running concurrently * internal Oracle error After resolving the problem that prevented DCM
from updating the configuration files, you may use the dcmctl resyncInstance command to resolve the
problem. Alternatively, you can stop and then restart the active dcmctl or EMD process and resyncInstance
will automatically be performed".
Associating the instance with the JAZN XML User Manager gives the same error.
In the emctl batch file I've created I can see the following error during the deployment:
OBJECT CACHE: HttpSession=c7d93daf948143ffa173bd73ae6b0a60; getObject() name=Ins
tanceAdminObject_oc4j_orawireless.<hostname>OC4JPortal, return value=oracle
.sysman.eml.ias.oc4j.InstanceAdminObject@49153e
EMSDK DEBUG: Global Tabs
EMSDK DEBUG: Link[name=targets,text=Targets,destination=/emd/console/targets,image=null]
Link name : ias/oc4j/deployWiz/roles
Invalid Bread Crumbs, linkname = ias/oc4j/deployWiz/roles
EMSDK DEBUG: Global Tabs
EMSDK DEBUG: Link[name=targets,text=Targets,destination=/emd/console/targets,image=null]
EMSDK DEBUG: Global Tabs
EMSDK DEBUG: Link[name=targets,text=Targets,destination=/emd/console/targets,image=null]
Link name : ias/oc4j/deployWiz/publishServices
Invalid Bread Crumbs, linkname = ias/oc4j/deployWiz/publishServices
EMSDK DEBUG: Global Tabs
EMSDK DEBUG: Link[name=targets,text=Targets,destination=/emd/console/targets,image=null]
EMSDK DEBUG: Global Tabs
EMSDK DEBUG: Link[name=targets,text=Targets,destination=/emd/console/targets,image=null]
Link name : ias/oc4j/deployWiz/summary
Invalid Bread Crumbs, linkname = ias/oc4j/deployWiz/summary
EMSDK DEBUG: Global Tabs
EMSDK DEBUG: Link[name=targets,text=Targets,destination=/emd/console/targets,ima
ge=null]
oracle.ias.sysmgmt.exception.TaskException: The configuration files for this Oracle9iAS instance are inconsistent with the configuration stored in the repository. In order to protect the repository,
no further configuration or deployment operations are allowed until the problem
with the configuration on the filesystem is resolved. This condition arises when
a prior operation was unsuccessful. Please check the logs located at
ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating
the configuration files on disk.......
Do you have any suggestions of things I could try? Do I have to check out the settings of the OC4J_portal instance? I've also checked the Access Rights for cn=IAS Infrastructure Databases, cn=IAS, cn=Products, cn=OracleContext user the Oracle Directory Manager.
Instance Properties
Server Properties
Website Properties
JSP Container Properties
Replication Properties
Advanced Properties
Application Defaults
Data Sources
Security
Global Web Module
UDDI Registry
Thanks!
Regards,
Thomas. -
JDeveloper 11g deployment error to local Web Logic server
I'm trying to run an existing ADF project for the first time from a JDeveloper 11g.
But get the error below, can anyone help me?
Deploying Application...
<09-03-2009 11:07:23 CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application VEU Portal Consumer is not versioned.>
<09-03-2009 11:07:23 CET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1236593243599' for task '0'. Error is: 'weblogic.management.DeploymentException: '
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
Truncated. see log file for complete stacktrace
>
<09-03-2009 11:07:23 CET> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'VEU Portal Consumer'.>
<09-03-2009 11:07:23 CET> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
Truncated. see log file for complete stacktrace
>
[Deployer:149034]An exception occurred for task [Deployer:149026]deploy application VEU Portal Consumer on DefaultServer.: .
weblogic.management.DeploymentException:
#### Deployment incomplete. #### Mar 9, 2009 11:07:23 AM
oracle.jdeveloper.deploy.DeployException
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:247)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:157)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
at oracle.jdevimpl.runner.adrs.AdrsStarter$4$1.run(AdrsStarter.java:1316)
Caused by: oracle.jdeveloper.deploy.DeployException
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:413)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:238)
... 11 more
Caused by: oracle.jdeveloper.deploy.DeployException: Deployment Failed
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:395)
... 12 more
#### Cannot run application VEU Portal Consumer due to error deploying to DefaultServer.
[Application VEU Portal Consumer stopped and undeployed from Server Instance DefaultServer]
Thanks
ClausDid you use the embedded WLS?
In this case I would try a fresh install, because you should not see this error. If you are using a stand alone WLS you need to install the ADF runtime onto the server.
the error java.lang.ClassNotFoundException: oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener means that there is something wrong with the ADF installation on the WLS server.
Timo -
Web service deployment error - CE 7.2(CAF)
I am getting deployment error for CE 7.2 CAF application.
it was working fine. Suddenly with out any changes in the code or the web service, I am not able deploy the application.
if I remove the modeled service , it is successfully deployed. But modeled service is required to expose the service for other applications.
any one have suggestions? does this is a problem from J2EE engine? any authentication problems??
its a nested error:
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [<projectname>~ear].
; nested exception is:
com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [<projectname>~ear]
sdu file path: [/usr/sap/CED/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/582/<projectname>ear.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:178)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:92)
at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:236)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)Resolved myself : delete the project in webAS using deployment perspective and delete the project in NWDS and recreate the same project and deploy with WSDL.
Maybe you are looking for
-
How do I get a voice memo to my computer?
I need to get the recorded into my MacBook Pro. Lion, 10.7.5. Can't send email, too long. Need this in my computer today. Thanks
-
Now that I have the latest 6.0 version of iTunes my computer will no longer recognize or acknowledge that my iPod is plugged in. I have a 30Gb click wheel. does anyone have any suggestions?
-
How to hide ABAP report source codes like program SAPMSYST
hello guys , I only want to know how SAP hide ABAP codes, any one could told me? BRs. Justin
-
Hi For performance and security reasons it is usually better to use SQL-Parameters (like :1) in SQL-Queries instead of building the SQL-String directly. I'd like to adopt this best practice but stumbled over a problem: BC4J adds Parameters when apply
-
I need the function module name
i got the requirement to post data to FBS1 FB01 FBV1 transaction before posting the data to transaction i need to check the data in the iternal table for validity . this can be hadled by function modules or bapi if any now the name please reply