Deployment issue in NWDS while deploying BPM

Hi Experts,
I m getting following deployment error in NWDS (SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP11 PAT0002) while deploying BPM.
can u plz revert back if you have encountered similar issue.
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
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:105)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/A6D/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/1418/DC-I205.sda] failed
at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
... 11 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: TxException
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1280)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
... 12 more
Caused by: java.lang.Exception: com.sap.engine.services.ts.transaction.TxRollbackException: Current transaction is marked for rollback
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:621)
at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1277)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.IllegalStateException: Galaxy commit failed (for a possible cause, refer to the nested exception(s)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:117)
at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.beforeCompletion(SynchronizationWrapper.java:36)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.beforePrepare(TXR_TransactionImpl.java:589)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.commit(TXR_TransactionImpl.java:1120)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.commit(TXR_TransactionManagerImpl.java:333)
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:610)
... 24 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Transaction locked for rollback; Commit refused.
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:701)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_precommit(AbstractTransaction.java:186)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:75)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:115)
... 29 more
Caused by: com.sap.glx.core.dock.api.DockException: Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:693)
at com.sap.glx.core.dock.impl.DockingPortal.configureCallback(DockingPortal.java:495)
at com.sap.glx.core.dock.impl.DockingPortal.runConfigureCallback(DockingPortal.java:998)
at com.sap.glx.deploy.impl.DeployControllerImpl$DeployProcessor.runProcessorWork(DeployControllerImpl.java:801)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.run(DeployControllerImpl.java:624)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.access$1300(DeployControllerImpl.java:585)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:549)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:543)
at com.sap.glx.core.kernel.DefaultRuntimeManager.requestRuntimeMode(DefaultRuntimeManager.java:1110)
at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.executeDeployWork(DeployControllerImpl.java:1177)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.executeDeployActuatorCallbackWork(CoreServiceRRHandler.java:138)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.access$400(CoreServiceRRHandler.java:50)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.callCoreServiceHandlers(CoreServiceRRHandler.java:314)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.addVersion(CoreServiceRRHandler.java:337)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2565)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1535)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:339)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:261)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:251)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1265)
... 22 more
Caused by: com.sap.glx.adapter.api.AdapterException: Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit 7b9afc88c8f151c20d38cef0d370f416 using configuration mode DEPLOYMENT
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:669)
... 41 more
Caused by: java.lang.RuntimeException: Transformer could not get lock within 60 seconds
at com.sap.glx.core.internaladapter.Transformer$Share.acquireWrite(Transformer.java:875)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor$GeneratorLocalProvider$ImplementedGeneratorLocal.acquireWrite(Transformer.java:2317)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor.insertRule(Transformer.java:2775)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationHandler.configure(Transformer.java:2930)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplateHandler.configure(Transformer.java:3472)
at com.sap.glx.core.internaladapter.Transformer.configure(Transformer.java:3675)
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:666)
... 41 more
at com.sap.engine.services.ts.transaction.TxRollbackException.writeReplace(TxRollbackException.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1040)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1116)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:331)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:139)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:488)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:81)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
... 3 more

Hi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their.

Similar Messages

Getting errors on EP7.0CE NWDS while deploying the Application

Hi Frndz..
Jus now i installed EP7.0 CE SP3 n NWDS7.0CE , for deploying the app from NWDS i did the same thing like
windows--> preferences -->SAP AS JAVA n their i given the host name n Instance number...
but when am trying to deploy applicatio itz giving the following error
com.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
Reason: Exception while trying to get InitialContext.
[#1]: SessionImpl::getContext():[get ctx. NamingException],cause=Exception while trying to get InitialContext.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
*sap-001:50006 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 10.6.3.112*
Am xpecting a needfull information,thanx in adavance
Regards
Rajesh

Hi,
normally it should not be required to deploy JSF 1.2 with the application as WLS has JSF 1.2 installed. So only make sure you deploy 11.1.1.7 to the WLS server it is supported with
Frank

Deployment issue with SOA - OSB 11g environment

Hi,
We have Dev Environment configured with SOA 11g (11.1.1.4) and OSB 11g (11.1.1.4) on a single weblogic domain. Developed SOA composite app and deployed to the SOA Server. We are exposing our SOA Composite thru OSB ( created osb proxy and business services and accessed soa composite from the client. It s working fine ) layer for the client to access it. The issue here is while deploying it to the production environment (configured OSB and SOA in two separate WL domain) located offshore.
What i saw from the soa doc is that we need to deploy SOA composite to the SOA Server and OSB Configuration to the OSB Server.
but the offshore person is asking us to deploy both SOA composite & osb to the same OSB Server as an .ear file.
Is it possible to deploy both SOA composite & osb to the same osb server ? is there any document on project that involve both soa and osb.
please guide me how to do the deployment
I appreciate all your help.
thanks
sumesh.j

I am wondering if could able to solve the problem of deploying both SOA composite & osb to the same osb server. Even I am facing the same problem....
If you could able to solve the problem then please let us know the steps that you have followed to solve the same.

Configuration error while deploying beans

Hi ,
I am trying to deploy entity beans. While deploying I am getting the
following error. I checked weblogic_classpath. It has got .\classes. Any
help is highly appreciated. Find the attached start script.
EXCEPTION DESCRIPTION: Configuration error. Class weblogic.jdbc.jts.Driver
not found.
at
TOPLink.Public.Exceptions.DatabaseException.configurationErrorClassNotFound(
DatabaseException.java:54)
at
TOPLink.Public.Sessions.DefaultConnector.loadDriver(DefaultConnector.java:11
6)
at
TOPLink.Public.Sessions.DefaultConnector.connect(DefaultConnector.java:54)
at
TOPLink.Public.PublicInterface.JDBCLogin.connect(JDBCLogin.java:180)
at
TOPLink.Private.DatabaseAccess.DatabaseAccessor.p(DatabaseAccessor.java)
at
TOPLink.Private.DatabaseAccess.DatabaseAccessor.connect(DatabaseAccessor.jav
a)
at
TOPLink.Public.ThreeTier.ConnectionPool.buildConnection(ConnectionPool.java:
86)
at
TOPLink.Public.ThreeTier.ExternalConnectionPool.startUp(ExternalConnectionPo
ol.java:91)
at
TOPLink.Public.ThreeTier.ServerSession.connect(ServerSession.java, Compiled
Code)
at
TOPLink.Public.PublicInterface.DatabaseSession.login(DatabaseSession.java:36
3)
at
TOPLink.Private.EJB.WebLogic.DeploymentManager.sessionLogin(DeploymentManage
r.java)
at
TOPLink.Private.EJB.WebLogic.DeploymentManager.setup(DeploymentManager.java)
[startWebLogic.cmd]

Post Author: ejthunder
CA Forum: Deployment
It looks like you're trying to deploy with the CR.NET merge modules for VS2003. You'll need to deploy the CR.NET merge modules for VS2005 instead.
You can find the merge modules for the various versions at this link on the BOBJ site:http://support.businessobjects.com/downloads/merge_modules.asp
Choose the correct version. If you're using the bundled edition of CR.NET that ships with VS2005 - CR.NET 2005, then click on the link for VS2005. If you're using CR XI Developer, or CR XI R2 Developer then click on the link for the version you're using.
The CR.NET 2005 merge modules have deployment instructions in the download.
I hope this helps!
EJ

Bpm 11g error while deploying composite. BPM_CUBE_PROCESS_INDX1

Hello,
Got the following error while deploying the very first composite to a newly installed bpm 11.1.1.5.0 server on windows 2003 server with Oracle 10g Express Data base:
Deploying on partition "default" from "/Farm_BPM_11g_Domain/BPM_11g_Domain/soa_server1"...
Deployment failed on "/Farm_BPM_11g_Domain/BPM_11g_Domain/soa_server1".
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
; nested exception is:
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
; nested exception is:
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_SOAINFRA.BPM_CUBE_PROCESS_INDX1) violated
Query: InsertObjectQuery(CubeProcess(domain:default composite:ComunicacionesOficiales revision:1.01 name:CorrespondenciaExternaEnviada hasNametab:false)).
BPM_CUBE_PROCESS_INDX1 is an index from the SOAINFRA schema... should I change it to be not unique?
Thanks in advance,
Josue

I'm getting the same issue deploying my first application on to a fresh 11.1.1.4 install.
Also win2003 server, also XE.
install is going into partition "default"
On further review, this table is empty before the deploy. Does the deployment try to create the Process twice? Or perhaps I have two different Processes with the same name (but in different Folders?) don't think that jdev will allow this....)
Edited by: wylderbeast on Jun 21, 2011 12:55 PM

Facing issue while deployment on 11.1.1.6 soa server

Problem Summary
Facing issue while deployment on 11.1.1.6 soa server
Problem Description
We are facing issue while deploying a bpm project over a newly built bps-soa server 11.1.1.6.
While we are deploying a bpm project, first it is taking around 40mins to create .jar file and then while deploying, it is getting failed with transaction timed out error.
"composite: Onboarding: javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 301 second".
we have tried with changing all transaction parameters also like JTA,XA( as similar to our exiting running QA/PROD environment which is on 11.1.1.5) but even then facing the same issue.
The code were originally build over 11.1.1.5 version, for the first time opening with jdev, code gets migrated and over the upgraded code we did some business specific changes and now trying to deploy over the new server.
Code is getting successfully compiled and also .jar file is creating properly but while deployment facing error(As shared earlier).
Also tried to deploy the same .jar file using em consle(to soa-infra) but facing similar issue.
Error Codes
Problem Category/Subcategory
BPM 11g installation issues
Uploaded Files
Template Question Responses
1) ### Product Versions Including Build Numbers ###
BPM SOA suite 11.1.1.6
2) ### Is the Issue Reproducible ###
Yes, mentioned in issue detailes.
3) ### OS Version ###
SunOS xxxxx 5.10 Generic_144488-06 sun4v sparc SUNW,T5440
More logs:
Name
=== ODM Data Collection ===
[2013-02-27T01:10:59.436-05:00] [soa_server1] [WARNING] [] [oracle.soa.bpel.engine.deployment] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] Unable to obtain the audit metadta java.lang.IllegalStateException: The transaction associated with this transaction-scoped persistence context has been rolled back and as a result, the EntityManager has been closed. No further operations are allowed in this transaction context. Please see the server log for the cause of the rollback.
[2013-02-27T01:11:17.402-05:00] [soa_server1] [WARNING] [] [oracle.soa.bpel.engine.deployment] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] Unable to obtain the audit metadta java.lang.IllegalStateException: The transaction associated with this transaction-scoped persistence context has been rolled back and as a result, the EntityManager has been closed. No further operations are allowed in this transaction context. Please see the server log for the cause of the rollback.
[2013-02-27T01:11:18.147-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.deployment] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] BPEL Component "default/Onboarding!2.0*soa_8130f118-f9b5-462a-8e75-5ec0f34b45bd/Remediation" successfully loaded.
[2013-02-27T01:11:18.166-05:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine] [tid: [STUCK].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 486af90ee4d37577:-6eb9b41c:13d15783e85:-8000-000000000000142f,1:18454:2] [APP: soa-infra] Unable to activate process Remediation[[
javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwEJBException(EJBRuntimeUtils.java:156)
at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:595)
at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetry(BaseLocalObject.java:455)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:52)
at oracle.bpm.bpmn.engine.ejb.impl.BPMNServerManagerBean_6gbx7k_IBPMNCubeServerManagerLocalBeanImpl.deployComponent(Unknown Source)
at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:842)
at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.load(BPMNServiceEngine.java:636)
at oracle.bpm.bpmn.engine.service.BPMNServiceEngine.load(BPMNServiceEngine.java:151)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployComponents(CompositeDeploymentConnection.java:243)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
BEA1-172EC48037986ACD0C13
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
... 2 more
FileName
soa_server1-diagnostic-2.log

2 things must be noticed:
First: ODI 11g is not supported by JDK 7, I always use the JDK1.6.0_27 and works fine. When you try to open the ODI Studio, this message appears, telling that ODI is supported only with JDK 6 versions, so don't try to use JDK 7.
Second: I always install the JDK in a path without spaces, like "C:\JDK1.6.0_27\" and the excatly same thing to odi install files. So I call via Command Prompt:
C:\ODI_INSTALL\Disk1\setup.exe -jreLoc C:\JDK1.6.0_27\
I did over 20 windows installations using these settings, it'll work perfectly.
Regards.
Luiz Araujo

Error while deploying a PAR file from NWDS into an ECC.

Hi all,
I am getting this error while deploying a PAR file from NWDS into an ECC.
Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
more detail.
My server is running properly
1 - Where is sap-plugin.log file? I don´t find it.
2 - Could there be another file with another name with information about the error?
3 - Is there another way to deploy the file directly from the ECC?
Regards,

Hi,
Just make sure you have maintained correct server setting to check the same open the NWDS and follow this path
Windows/ Prefereces / SAP Enterprise Portal
Check the following enteries
Alias
Host
Port
Login etc.
Regards,

Error While Deploying A Web Dynpro Appln thru NWDS

HI,
I am getting an error while deploying a Web Dynpro Application through NWDS.Following is the Exception
Aborted: development component '<ComponentName>'/'local'/'LOKAL'/'0.2006.07.26.15.06.05':Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [sapsbx28] with user name: [J2EE_ADMIN] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.] (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
When i give a request for deployment it asks for the SDM password. I enter a valid SDM pwd. If i enter a invalid SDM pwd i get some other exception. So the pwd SDM entered by me is correct.
can any one help me in solving this
regards
Nilesh Taunk

Hi Nilesh,
Try opening Visual Admin if your not able to login with username(administrator) and password. Problem with NWD2004s do the following steps.
C:\usr\sap\J2E\JC01\j2ee\configtool->configtool.bat->open it
1. Click on Secure store
2. Right you will find :
admin/password/J2E->retype your admin passowrd which you gave during installation=>SAVE properly
Restart the server and try login visual admin
Deploy now...Other wise see this thread same error solved:
Re: An Deploy Problem about Credentials.
Regards
Suresh

Problem while deploying PAR from NWDS

Hi,
I am getting this error while deploying a PAR file from NWDS.
Operation Failed: Please make sure the server is running or check the log (sap-plugin.log) for
more detail.
regards,
Arun

Hi
You also have the option of uploading the par by logging into the portal ...
System Administration->Support->Portal Runtime->Administration Console
just browse and upload the par file...
Create an IView from par and can see the output
Avinash

Deploy Exception Error while Deploying DCs in NWDS 7.3

Hi
I have this following error while deploying the DCs into the AS Java.
"Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [demo.sap.com_dc] failed] "
The DC which i created is a Dictionary DC Which contains Tables created from the entities in EJB DC.
Thanks
Teja

Hi Ervin,
Thanks for your help. The error I was getting is resolved. It was due to Higher version of NWDS (version including SP and PAT needs to be considered).
On checking the stack throughly I came up with the error:
"The given process model was built with a NWDS or development track of a higher version than the target runtime. Revision number of built process model: 4.4. Revision number of process runtime: 4.3. Please refer to SAP note 1600131 for details......"
One thing learnt:- First thing you need to check is the exact version of SAP PO including the Service Pack and Patch Level.
You can check this from:
1. Directly through the URL:: http://<host>:<port>/sap/monitoring/SystemInfo
2. From http://<server>:<port>/ -> System Information -> Component Information
The NWDS should be either less than or equal to the version of SAP PO. You need to check all the details including Service Pack and Patch level.
Ex- If the version of your PO is 7.30 SP 08 PAT 0000
You cannot deploy SAP PO server with 7.30 SP 09 PAT 0000 nor 7.30 SP 08 PAT 0013.
You can consider 7.30 SP 08 PAT 0000 or less than that.
*** In our case, although the SAP PO and NWDS are of same version i.e 7.31. But the higher SP and PAT of the NWDS was giving the error.
Regards,
Atreyee

Error while deploying NWDS application

While deploying the NWDS projects, I am recieving an error message:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts
The same problem is occuring with various projects, which earlier used to deploy. Plz help.

Thanks Benny
I did so but am constantly getting errors while deploying
the error message is com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon).
I unlocked the password and reset it but am constantly getting the same error message and after some deployment trials, the user gets locked.
Plz help.

Getting Duplicate Object existing issue while deploying the BIAR file

Hi All,
We are trying to deploy BIAR File with XI R2 Command tool InstallEntSdkWrapper. But we are getting Duplicate Object exixting issue while deploying the BIAR file.
Error Message:
[report] [InstallEntSdkWrapper.main] Connecting to CMS plmdevapp31:6400 as administrator
   [report] [InstallEntSdkWrapper.CmsImportFile] Exception: An error occurred at the server :
   [report] Failed to commit objects to server : Duplicate object name in the same folder.
   [report]
   [report] [InstallEntSdkWrapper.main] BIAR File could not be imported
If we are doing any promition with Import Wizard we have an option to "Overwrite object contents" option to overwite exixting objects. It will very helpful if any one suggest how we can achieve this through InstallEntSdkWrapper.
Unfortunately there is no documentation availabe on InstallEntSdkWrapper.
Cheers!

That's a limitation with the XI Release 2 InstallEntSdkWrapper.jar tool.
Sincerely,
Ted Ueda

Issue while Deploying Project through JDeceloper to server

HI,
Error finding SOA configured servers to deploy. Deployment cannot continue.
Javax.naming.communicationException [Root exception is java.net.ConnectionException: t3://blr-ro-narik.in.xxx.com:7001:Destination unreachable; nested exception is: java.net.protocolException: unrecognized response from proxy:’HTTP/1.1.502 Proxy Error (The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not c onfigured to allow SSL requests from this port. Most Web browsers use port 443 for SSL requests. ); No available router to destination].
Note:- The above error, i am getting while deploying a project through "Application Server" to Admin Server.
If any1 knows regarding this issue,please Let me know detailed.
Regards
Narik

Hi,
Check
Runtime errors with ADF Dynamic region
java.lang.IllegalStateException: The expression "#{bindings.dynamicRegion1.
Problem with bounded task flow: binding lost?

Bpm xsd/ReviewObject.xsd not found in composite while deploying

Hi,
I am a newbie to BPM.
Installed 11.1.1.5.0 soa/bpm suite.
Tried http://st-curriculum.oracle.com/obe/fmw/obpm/11g/r1/firstProcess/firstprocess_obpm11g.htm
Getting error while deployment of the above saying
The XML-Schema file for the fact com.oracle.xmlns.bpm.bpmobject.hellomodule.reviewobject.ObjectFactory could not be found in the composite.
The XML-Schema file xsd/ReviewObject.xsd could not be found in the composite. The XML fact com.oracle.xmlns.bpm.bpmobject.hellomodule.reviewobject.ObjectFactory of target namespace assumes the existence of the schema file in the composite.
Check the composite for the schema xsd/ReviewObject.xsd and make sure it has target namespace. The schema is expected in the project xsd or businesscatalog folder. If the error persists, contact Oracle Support Services.
Exception:
at oracle.bpel.services.rules.fabric.xml.RuleDictionarySchemaUsage.addToResultSet(RuleDictionarySchemaUsage.java:222
at oracle.bpel.services.rules.fabric.xml.RuleDictionarySchemaUsage.addToResultSet(RuleDictionarySchemaUsage.java:167
at oracle.bpel.services.rules.fabric.xml.RuleDictionarySchemaUsage.getComponentSchemaQNames(RuleDictionarySchemaUsage.java:126
Installed as per the quick start guide mentioned in the documentaion page, ie. with oracle-xe, wls 10.3.5, rcu 11.1.1.5.0, soa 11.1.1.5.0
configured the domain for bpm suite for developers, soa suite for developers
Developed and deployed from jdeveloper as per the above bpm example link.
If tried without the business rule component, there are no errors, works fine and able to check from /bpm/workspace properly.
Please let me know what needs to be done to correct the above error.
Thx

Hi,
i believe that is a bug in the composite editor. You MUST NOT copy ReviewObject.xsd from the businessCatalog folder to the xsd folder.
Instead, try creating the Business Rule from the BPMN process. This can be done from the "Implementation" dialog of the Business Rule activity.
In that dialog, you can specify the input and output of the Business Rule by dragging&dropping from the Process Data Objects into that dialog.
There is no need to even look at the XSD, it is all hidden under the covers.
Not sure why the tutorial wants you to create the rules component from the composite editor, i will check and get that fixed.
Let me know if that works for you.
Best Regards,
Ralf

Deployment issue using BPM TaskForms-ViewController to the SOA Server

Hi Guyzz,
I am facing an issue in deploying View Controller project created using BPM activity -- Human Task. I am depolying to the standalone weblogic -- Soa Server.
but i am getting the below error
Error log:
Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11133]Unable to bind Business Interface to the JNDI name: ProjectsManager, throw exception javax.naming.NameAlreadyBoundException: [EJB:011224]Unable to bind the interface com.atc.projects.facade.ProjectsManager to ProjectsManager. Another EJB has already bound an interface to that name."; remaining name ''.
NestedException Message is :[EJB:011224]Unable to bind the interface com.atc.projects.facade.ProjectsManager to ProjectsManager. Another EJB has already bound an interface to that name."
using Jdev 11.1.1.5
Regards
Peter
Edited by: Peter on May 23, 2013 3:02 AM

repost...
I found like two of the projects weblogic-EJB.jar is having the same entry i.e in Project Model and OASIS Model.
I removed one entry in OASIS Model and the deployment is complete but the task is not initiating in the BPM workspace.
The duplicate entry
<weblogic-enterprise-bean>
    <ejb-name>ProjectsManager</ejb-name>
    <stateless-session-descriptor>
      <business-interface-jndi-name-map>
        <business-remote>com.atc.projects.facade.ProjectsManager</business-remote>
        <jndi-name>ProjectsManager</jndi-name>
      </business-interface-jndi-name-map>
    </stateless-session-descriptor>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>ProjectsManager</jndi-name>
    <local-jndi-name>ejb/local/ProjectsManager</local-jndi-name>
</weblogic-enterprise-bean>This entry is in two projects...can anyone suggest me a solution
Any help will be very useful for me.
Thanks in Advance
Peter
Edited by: Peter on May 30, 2013 3:32 AM

Deployment issue in NWDS while deploying BPM

Similar Messages

Maybe you are looking for