Hello Colleagues,

how is the SAP JVM 6's JDK installation procedure for NWDS 7.3 und Windows 7, please?

At Installation Guide for the NWDS I found the note regarding the option SAP JVM instead of the Oracle JVM.

The installation of Oracle JVM is quite simple (setup.exe) but how ist process here for SAP JVM.

I couldn't find any documentation regarding the installation process under windows.

As well no exe file at downloaded sar file.

Only "vcredist_x86.msi"???

Download SAP JVM6 vom Service Market Place

Support Packages and Patches --> A-Z Index -->N > SAP NETWEAVER> SAP EHP1 FOR SAP NETWEAVER 7.3--> Entry by Component --> Application Server Java --> SAP JVM 6.1--> Windows Server on IA32 32bit--> SAPJVM6_42-10006998.SAR

Please, could anyone help me here?

Many thanks in advance!

Regards,

Jochen

HI There,

We are going to implement CTS+ in our portal systems which is containing NWDI. Below are details for the same .

NWDI portal version : NW 7.0 EHP1 SP13

NWDI sits on development system and it self is a run time development system and quality is a consolidate system. Currently we are using CMS services in NWDI

and as per SAP recommendations from NW 7.0 EHP1 we can use CM Services but here my doubt is

• Do not use the AS Java, on which the CM Services are running, as a runtime system. When you import software components that have offline deployment parts, deployment causes a deadlock. In other words, the CM Services server is restarted by the import.  ( SAP note 1361909)
• Solution for maintenance tracks described on SDN http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3390

          is not supported for CM Services.

Could you please confirm me whether we can proceed with CM Services or CMS itself as per above comments.

Thanks.

Pavan.

Hi

When I am trying to Import the track in NWDS 7.3 I am getting the following error.

"some infrastructure servers cannot be contacted"

I am trying to Import from System Landscape Directory

and in Windows --> Preferences --> Development Infrastructure --> System Landscape Directory

When I place the URL and click on Ping

The Ping is successful

When I am trying to import a New Development Configuration by doing Import from System Landscape Directory and I can see all my tracks and everything

I can see Remote Development Configuration

But when I try to logon to Development Infrastructure it gives me the following error

"some infrastructure servers cannot be contacted"

Can some one let me know what I need to do to resolve this error.

Regards

JM

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

Hello Friends,

We have PO 7.3 EHP1 SP04 system. (PO - Process Orchestation Single Stack Java System)

I have installed NWDS 7.3 - EHP1 - SP04 version in my system.

(File : nwds-extsoa-7.3-EHP1-SP04-PAT0005-win32.zip)

I have designed NWBPM in NWDS.

When I try to add my PO System in Window --> Preferences --> SAP As Java, after 1 minutes, it displays a message "The following SAP instance cannot be accessed at present.".

Then I tried to add through MMC. Window --> Show View --> Other --> Management Console. Here also, it displays the same message.

I tried to check Network Connections : Window --> Preferences --> General --> Network Connections. Our PO host is not added. All the Proxy Entries and Proxy By Pass Entries are unchecked.

Then I see the .log file in the .metadata folder, the log is given below.

------------------------------------------------------------------

!SESSION 2013-03-06 17:27:39.796

eclipse.buildId=@qualifier@
java.version=1.6.0_37
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.ui 2 0 2013-03-06 17:28:02.717
!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2013-03-06 17:28:02.717
!MESSAGE Cannot bind to an undefined command: plug-in='com.sap.ide.esr.tools.core.ui', id='com.sap.ide.esr.tools.ui.runchecks'

!ENTRY com.sap.ide.jvm.check 1 0 2013-03-06 17:28:44.982
!MESSAGE JVM Version Check succeeded.

!ENTRY com.tssap.util.ui 1 0 2013-03-06 17:28:55.388
!MESSAGE Sap NetWeaver Developer Studio - Platform Feature Version: UNKNOWN

!ENTRY org.eclipse.osgi 2 1 2013-03-06 17:29:09.184
!MESSAGE NLS missing message: Businessworkflow in: com.sap.glx.ide.i18n.messages

!ENTRY com.sap.ide.tools.services 4 0 2013-03-06 17:29:43.980
!MESSAGE Deployment failed: No default SAP system found in the configuration. Goto Window > Preferences > SAP AS Java to set or register one.
!STACK 0
com.sap.ide.eclipse.deployer.api.NdsApiException: No default SAP system found in the configuration. Goto Window > Preferences > SAP AS Java to set or register one.
at com.sap.ide.eclipse.deployer.DeployerPlugin.getCurrentServerInfo(DeployerPlugin.java:97)
at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:246)
at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:218)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:255)
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)

-----------------------------------------------

I could not understand what is this error message.

I referred this thread. (http://scn.sap.com/thread/3243496). Do I need to install sapjvm6.msi. I don't know this installtion will help to fix this.

Could you please help me friends to fix this ?

Thanking you.

Kind regards,

Jegathees P.

Hello All,

We are in the process of upgrading our NWDI servers from 7.0 to 7.31 SP06. We have more than 20 tracks in the 7.0 version which are used for development. We have different types of developments going on in different tracks like Portal developments in a track, Webdynpro developments, ESS and MSS developments, Biller Direct etc. Our landscape is big where we support parallel project and production support activities in different tracks.

We would like to know what will happen to the old developments when we upgrade our NWDI server from 7.0 to 7.31. The dependent components in the latest 7.31 version is different from the 7.0 version.

1) Should we need to create new tracks and import the old developed SC into the new track?

2) We cannot change the production support track components as we need to support the ongoing production needs. What will happen to these tracks after migration to 7.31? Will it still be usable with older version of sca files? This question is specific to ESS, MSS and Biller Direct. We have made huge development changes to these tracks and need to support them until the newer migration goes live.

Thanks,

Nagarajan.

hi,

I am a java developer. I don't know to what to do with NWDI.Now i want to upgrade a custom application done in java  from crm 5.0 to 7.0 for .I have seen this http://scn.sap.com/community/crm/web-channel/blog/2012/10/22/how-to-upgrade-a-modified-crm-webchannel-or-e-commerce-application-based-on-java link. Where I can't understand any thing.Now I am having an ear file of that custom java code.I don't where to start. Please help me....

Regards,

Aravind.

Hi,

I am having two problems.

1. I am getting the classic

     Error: Build stopped due to an error: No JDK_HOME_PATH defined for key 'JAVA_HOME'

This is the whole log,

Jul 24, 2014 3:12:01 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: ess/sg/fam: Build failed for sap.com/ess/sg/fam(sap.com_SAP_ESS_1) in variant "default": The Build terminated with errors

------------------------------------- Build log ------------------------------------------------------

Development Component Build (2014-07-24 15:11:51)

  Component name: ess/sg/fam

  Component vendor: sap.com

  SC compartment: sap.com_SAP_ESS_1

  Configuration: ND1_EHRESS_D

  Location: ND1_EHRESS_D

  Source code location: http://zq4c1:50100/dtr/ws/EHRESS/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/sg/fam/_comp/

  DC root folder: C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\ess\sg\fam\_comp\

  DC type: Web Dynpro

  Host: zq4c1

DC Model check:

   All used DCs are available locally

   validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"

   validating dependency to  public part "default" of DC "sap.com/tc/col/api"

   validating dependency to  public part "default" of DC "sap.com/tc/cmi"

   validating dependency to  public part "default" of DC "sap.com/tc/ddic/ddicruntime"

   validating dependency to  public part "default" of DC "sap.com/tc/ddic/metamodel/content"

   validating dependency to  public part "default" of DC "sap.com/tc/wd/webdynpro"

   validating dependency to  public part "default" of DC "sap.com/tc/logging"

   validating dependency to  public part "default" of DC "sap.com/tc/wdp/metamodel/content"

   validating dependency to  public part "default" of DC "sap.com/com.sap.aii.proxy.framework"

   validating dependency to  public part "default" of DC "sap.com/com.sap.aii.util.misc"

   validating dependency to  public part "default" of DC "sap.com/com.sap.exception"

   validating dependency to  public part "default" of DC "sap.com/com.sap.mw.jco"

   validating dependency to used DC "sap.com/pcui_gp/xssfpm"

   validating dependency to used DC "sap.com/pcui_gp/xssutils"

   validating dependency to used DC "sap.com/ess/per"

   DC model check OK

Start build plugin:

   using build plugin: sap.com/tc/bi/bp/webDynpro

   starting build plugin from : C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\

Build Plugin 'WebdynproPlugin', Version 7.00 SP 15 (645_VAL_REL, built on 2008-02-16 00:51:04 CET, CL79160)

   development component:  ess/sg/fam (sap.com)

      software component:  SAP_ESS (sap.com)

                location:  ND1_EHRESS_D

                    type:  Web Dynpro

           build variant:  default

         output location:  C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\ess\sg\fam\_comp\gen\default

       generation folder:  C:\Documents and Settings\nd1adm\.dtc\1\t\9BEBB9B83BED543CBB6BD26A34D713CE

       plugin start time:  2014-07-24 15:12:00 GMT+08:00 (SGT)

                 Java VM:  Java HotSpot(TM) Client VM, 11.0-b15 (Sun Microsystems Inc.)

General options:

  convert *.xlf to *.properties: yes

  include sources for debugging: yes

Warning: Source folder "META-INF" does not exist and will be ignored.

Checking path lengths for sources

Path length checks finished in 0.265 seconds

Preparing data context..

No public part descriptor found for component "tc/col/api" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "tc/cmi" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "tc/ddic/ddicruntime" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "tc/ddic/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "tc/wd/webdynpro" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "tc/logging" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "tc/wdp/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "com.sap.aii.proxy.framework" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "com.sap.aii.util.misc" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "com.sap.exception" (vendor "sap.com"), public part "default", using legacy mode.

No public part descriptor found for component "com.sap.mw.jco" (vendor "sap.com"), public part "default", using legacy mode.

Error: com.sap.tc.buildplugin.util.BuildPluginException: No JDK_HOME_PATH defined for key 'JAVA_HOME'

  at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaCompiler(JavaMacroContextProvider.java:235)

  at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaEnvironment(JavaMacroContextProvider.java:180)

  at com.sap.tc.buildplugin.JavaMacroContextProvider.execute(JavaMacroContextProvider.java:35)

  at com.sap.tc.buildplugin.PrepareContextBuildStep.prepareTechnologySpecificData(PrepareContextBuildStep.java:187)

  at com.sap.tc.buildplugin.PrepareContextBuildStep.setupBuildFileCreatorContext(PrepareContextBuildStep.java:95)

  at com.sap.tc.buildplugin.PrepareContextBuildStep.execute(PrepareContextBuildStep.java:56)

  at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)

  at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)

  at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)

  at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)

  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 com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)

  at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)

  at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)

  at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)

  at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5633)

  at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction.buildDCs(DcCreateProjectAction.java:1027)

  at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.execute(DcCreateProjectAction.java:299)

  at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)

  at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)

  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)

Error: Build stopped due to an error: No JDK_HOME_PATH defined for key 'JAVA_HOME'

Build plugin finished at 2014-07-24 15:12:01 GMT+08:00 (SGT)

Total build plugin runtime: 1 second

So what am I doing?

I am trying to do? I am trying to sync the sources. (attachment snc2.png)

I already changed/added the java home at 3 locations,

Visual administrator (attachment snc3.png)

vmparam file (attachment snc4.png)

I downloaded all the java versions are 32 bit.

But even after doing all these I am still facing the issue.

My NWDI version and details.

are ver. 7SP15

and NWDS is 7.0.12

And the NWDS when I clicked on configuration details I noticed this log and the first few lines are really fishy..

** Date: 7/24/14 4:36 PM

*** System properties:

JDK1.3.1_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10

JDK1.4.2_HOME=C:\j2sdk1.4.2_17

JDK1.4_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10

allUserDir=C:\Documents and Settings\All Users\Application Data

awt.toolkit=sun.awt.windows.WToolkit

Notice that JDK1.3.1_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10, it is pointing to jdk1.6.0, but where to change to that? is this the issue?

Tried all possible things and solutions that I could find online but no use.

2

I have problem with the server (DTR) keep disconnecting once in a while, it says

DTR server http://<hostname>:50000 unreachable.

Socketclosed...

temporarily what i am doing is that to restart my instance from mmc and that works for a while, I believe it is the FQDN name that I have to change for the dtr, but where can I change that? and also what is the reason that it is able to connect the first few times when i restart the server but not later?

Thanks for your time.

Hi

When I am trying to Import the track in NWDS 7.3 I am getting the following error.

"some infrastructure servers cannot be contacted"

I am trying to Import from System Landscape Directory

and in Windows --> Preferences --> Development Infrastructure --> System Landscape Directory

When I place the URL and click on Ping

The Ping is successful

When I am trying to import a New Development Configuration by doing Import from System Landscape Directory and I can see all my tracks and everything

I can see Remote Development Configuration

But when I try to logon to Development Infrastructure it gives me the following error

"some infrastructure servers cannot be contacted"

Can some one let me know what I need to do to resolve this error.

Regards

JM

Hi Experts ,

I have two machines , in which nwds 7.01 in installed , in one of the machine im able to import the configurations and create a new dc etc , and in another machine im able to import the development configurations but im not able to create a new dc , llike the name space prefix is not getting displayed , i removed configuration and reimported again but not able to find a solution have gone throught this link .

http://scn.sap.com/people/kenny.tully/blog/2011/05/30/namespace-prefixes-are-not-available-in-nwds

Please suggest a solution.

Regards

Govardan

hi Experts ,

While configuring the sld in my nwds 7.3 sp 10 im getting the below error please help me to solve the issue

com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: Received response is not a CIM Operation Response! Check "http://**.***.***.***:50000/sld/" is the correct URL for the SLD CIM Object Manager (default is "http://**.***.***.***:50000/sld/cimom") and that user "" has access to the SLD via http and is not required to change his/her password.

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:550)

......................

Regards

Govardan

Hi guys,

I've got a problem updating my freshly installed NWDS 7.11 SP09. The problem is already described here without answer: http://scn.sap.com/message/13414310

I found that it seems to be a problem accessing a https resource. I tried to configure the proxy to be used for http and https (Configuration - General - Network Connection), but no luck. The ping in the configuration of the NWDS Update Policy leads to the same error. I also tried to define "proxy" as hostname for the proxies as suggested in another thread. I still get the "premature end of file" error when starting the update manager. Even if I open the policy.xml file via File- Open File, it can't find the xml! In my web browser it works perfectly though!

I add the screenshots below as evidence

Any ideas?

Thanks in advance,

Philippe

Hi experts!

We have installed a brand new 7.40 SP05 WebAS as a NWDI-server with an Oracle database 11.2.0.3.0. For some time everything was fine but since last week every build process takes about 4 hours and then fails. At the logfile it looks like this:

20140129095032 Info :buildspace = xxx_ABC10D_C build request id = 243 
20140129095032 Info :wait until CBS queue of buildspace xxx_ABC10D_C is completely processed, before asking for build results
20140129095032 Info :waiting for CBS queue activity
20140129095102 Info :build process already running: waiting for another period of 30000 ms
20140129095132 Info :build process already running: waiting for another period of 30000 ms
20140129095202 Info :build process already running: waiting for another period of 30000 ms
20140129095232 Info :build process already running: waiting for another period of 30000 ms
20140129095302 Info :build process already running: waiting for another period of 30000 ms
20140129095332 Info :build process already running: waiting for another period of 30000 ms 
...

What we have found until now is a blocking database sql-statement which blocks the following sql-statement. The database process is also running at 100% our administrator told us. The blocking sql statement is changing but the blocked statement is always the same:

UPDATE "CBS_LOCK" SET "LOCKIT" = "LOCKIT" + 1 WHERE "LOCKGROUP" = :1  AND "LOCKID" = :2

Did anyone had the same problem and found a solution?

Hi Experts,

I have done a system upgrade from NWDI 7.1 to NWDI 7.4.

Now i am having a problem when import SCA in DEV system. This process run forever...

The log is:

20140729101501 Info :Starting Step CBS-make at 2014-07-29 10:15:01.0294 -3:00

20140729101501 Info :wait until CBS queue of buildspace DN1_TRAF2P_D is completely processed, before starting the import

20140729101501 Info :waiting for CBS queue activity

20140729101533 Info :build process already running: waiting for another period of 30000 ms

20140729101603 Info :build process already running: waiting for another period of 30000 ms

20140729101633 Info :build process already running: waiting for another period of 30000 ms

20140729101704 Info :build process already running: waiting for another period of 30000 ms

20140729101734 Info :build process already running: waiting for another period of 30000 ms

20140729101804 Info :build process already running: waiting for another period of 30000 ms

20140729101834 Info :build process already running: waiting for another period of 30000 ms

20140729101904 Info :build process already running: waiting for another period of 30000 ms

20140729101934 Info :build process already running: waiting for another period of 30000 ms

...

...

20140729113122 Info :build process already running: waiting for another period of 30000 ms

20140729113152 Info :build process already running: waiting for another period of 30000 ms

20140729113152 Fatal :build processing for buildspace: DN1_TRAF2P_D is not enabled, cannot continue without NWDI administrator action

20140729113152 Info :Step CBS-make ended with result 'fatal error' ,stopping execution at 2014-07-29 11:31:52.0295 -3:00

I have found a lot of threads here, but no one help me.

The parameter idleStart is configured to false.

I try to keep BUILD_TOOL_JDK_HOME and JDK_HOME_PATHS as default, and try to set to java 6.

The build variant in CMS was configured too.

After the changes i restated the CBS service and try to import again in DEV system. But nothing happens.

If i import just one or all the components, it get a long time and catch the error showed above.

I have restarted the server a lot of time too.

Can someone have any idea how to fiz it?

Best Regards

Marcos Brandão

Hello Experts.

I have got a new project now:

I want to generate a JSP and deploy it on SAP NetWeaver Portal 7.3.

First of all, I installed NetWeaver Developer Studio 7.3 with JDK 1.6.0_21.

We are using a NWDI 7.01 SP 7.

My Problem:

On our SAP NetWeaver Portal 7.3 is a JDK 6 (1.6.0_21) running.....When I create a new Track in our NWDI, it has to be build by the Component Build Service also with JDK 6....

Can you tell me, how I set up the required JDK only for that new Track - but not as default for all Tracks in the NWDI.

P.S. It would be also very nice, if someone could confirm me, that the only required Software Component (SC) I need for deploying on NW Portal 7.3 is called: "SAP BUILD TOOL 7.3".

Dear Friends,

Is there a way we can utilize SAP NWDI application for NON-SAP Code Version Control?

Our goal is to provide version control for some UNIX scripts of which we are going to deploy across the landscape...

Thank you,

Sri

Hi,

I have an unique error.

In our project, we have installed NetWeaver 7.0 EHP1 SP4 as the Portal Devlopment Server.

I have done all the steps for Post Installation Steps of NWDI.

Now, there is an SAP SRS Compnent being deployed in Portal and functional consultant are

also using it.

Component Name : ISRSRS05_0-20002510.SCA

Version: SP05 for IS-R-SRS 602.

Now, this component is already being deployed in our Portal Server SAP NetWeaver 7.0 EHP1 SP4.

I was able to import this component in our NWDI track.

The dependent components of this .SCA are EP-BUILDT 7.0, SAP-JEE 7.0, SAP-BUILDT 7.0 and SAP_JTECHS 7.0

All the mandatory steps in Landscape Configurator and Transport Studio in CMS were done without error.

Then, I imported the NWDI track Configuration in NWDS 7.01 SP4.

I am able to import the inactive dcs of IS-R-SRS but when checking out, I am getting

Checkout failed: Checkout file failed (server response: Communication error [cause: Read timed out]):/TST/sap.com_IS-R-SRS/dev/inactive/DCs/sap.com/is/isr/srs/men/app/_comp/src/packages/com/sap/is/isr/srs/men/app/MainAppComp.wdcomponent /DJ1_TST_D~is~isr~srs~men~app~sap.com/src/packages/com/sap/is/isr/srs/men/app/MainAppComp.wdcomponent

The error in NWDS .metadata log is

!MESSAGE Feb 2, 2010 5:48:46 PM       com.sap.dtr.client.lib.protocol.requests.RequestBase     [Thread[main,5,main]] Error: 
java.net.SocketTimeoutException: Read timed out     at java.net.SocketInputStream.socketRead0(Native Method)     at java.net.SocketInputStream.read(SocketInputStream.java:129)     at java.net.SocketInputStream.read(SocketInputStream.java:182)     at com.sap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:327)

But I can create activities successfully in NWDS (DTR).

I am able to write code in Compnent Controller of my custom SC VIN_PRD.

Now, my question is whether this is java.net.SocketException or incompatibility of software.

My delivery manager told me to get the older version of NWDS ie., NWDS 6.40 but I am sure

that will not work with SAP NetWeaver 7.0 EHP1 SP4.

There is an error in DTR log  server but on earlier date:

com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask#Java#background.outOfDBConnections#com.tssap.dtr.server.deltav.resources.log_messages#Service unavailable, running background task {0} failed. Database connection pool is out of connections. Check connection pool and database settings.#1#com.tssap.dtr.server.deltav.runtimeconfig.impl.ConfigParamsCheckerTas

Regards

Kaushik Banerjee

Hi There,

We are implementing the CTS+ in our external portal landscape which is in NW 7.01 SP13. Currently we are having NWDI in our development system and through NWDI the deployment will happen, As a part of this there is one track which is existing having the development runtime system is DEV and consolidation system is QAS system.

But as a part of CTS+ we have created a new track with copy of the existing track details and imported the SC's and SCAs to new track. but the new track all the DC's are in broken status.

Could you please suggest me how to correct all the broken DC's in new track.

Note: all the DC's in existing track are working  OK.

Appreciate your help.

Thanks.

Pavan.

Hello guys.

I need your help.

I want to cleanup archives directory.

How should I do it? or may I use note 1746879 - How to delete DTR workspace and workspace folder?

Some while back we had modifications to both SAP_ESS and SAP_MSS in our Portal system, and of course we have used NWDI to track and manage those modifications during support pack applications.  However, we have since dropped the modifications to MSS, using the SAP-delivered code instead, although we still are keeping some ESS modifications.  I would like to be able to drop the status of 'modified' for the SAP_MSS component so that I no longer have to wait for length NWDI imports to get updates into our systems and instead can just let JSPM do its work.  In the past I successfully managed to do this for SAPPCUI_GP, but I no longer can seem to figure out how to achieve this end.

Our portal is on 7.01 sps10 (currently moving to sps13), and the ESS component is 603 sp10 (moving to sp12; the backend ERP system is 604 sps10 going to sps13).  The MSS component is 600 sp20 (moving to sp21).  The NWDI system is also on 7.01 sps13.

Starting with our sandbox portal, I redefined the associated NWDI track so that SAP_MSS was no longer marked as developed SC.  I kicked things off in JSPM, using the support package stack option, with the system under NWDI control as a DEV/CONS system.  Everything worked fine, except that both SAP_ESS and SAP_MSS were recognized as modified and therefore not deployed by JSPM.  JSPM is now at 7.01 sp13 pl0 (though internally it reports itself as sp12 pl0, so there must not have been any change from sp12 to sp13).

I thought I would now be clever and restart JSPM using the single support packages option, as in the past this has allowed me to overwrite a modified SC with the SAP-delivered one.  No dice.  JSPM still insists MSS is a modified component and will not allow deployment except via NWDI.

Ok, fine.  It's a sandbox.  I can afford to get rough, though I prefer not to, as the idea here is to figure out what I'm going to do in the DEV, TEST, and PROD systems later.   Anyway, following the instructions in Note 1462405 (Remove NWDI Control of SAP AS Java for JSPM / SUM), I removed the runtime system from the track, and then restarted JSPM.   This didn't work; JSPM still insists that the system is under NWDI control and won't let me deploy the SC.  I restarted the SDM and tried again, with no change (actually, I had to restart the SDM after removing the RTS from the track before JSPM could even logon).

After more searching, I found Note 1147113 (JSPM: This system is not under NWDI control), and followed those instructions.  In the Jspm.JSPM.DataModel.xml file, sure enough I found the 'nwdiRole' setting still at 'DEV(2)' and the 'nwdiSystem' setting at 'true', so I edited the file per the Note, changing the values to 'NOT_NWDI(0)' and 'false' respectively.  I then tried JSPM again, but it still insists the system is under NWDI control.  I restarted the SDM after confirming my edits in the xml file, and tried again.  It doesn't work.

Per Note 1632696 and SDN Thread 1646379, I deleted the three 'DataModel' files so that JSPM would re-initialize the model from scratch, but it still thinks it's an NWDI-controlled system, and the newly recreated DataModel file doesn't even have a reference to NWDI control at all.  Clearly the 7.01 version of JSPM is not getting this information from these xml files, and it is not getting it from NWDI; it's persisting it somewhere else.

Does anyone have any idea where that somewhere else might be?  Or how to get JSPM to 'forget' that it once was an NWDI-controlled system?  Or if not that, to simply allow me to "reset to original" on a Software Component (similar to what we can do in SPAU and SPDD)?

Best regards,

Matt