CBS temp folders (1 for each server node) contain nearly 4 GB each at /usr/sap/SID/JC00/j2ee/cluster /server0/temp/CBS/123456890 (server node #).

This folder contains numerous 2 digit hexadecimal folder names...a8, a9, ba, bb, bc (CBS temporary build folders ?)

Can the content under the temp folder be safely deleted or is there a way to maintain this data ?

NWDI NW7.3 on AIX 6.1

Hi masters,

can anyone tell me the utility of the active workspace and the inactive workspace in the DTR ? Do we absolutetly need them ?

I read somewhere that when activities are activated, they go from the inactive to the active.

Thx.

Hi

I have created several actvities in my NWDS and checked in and actvated them.

I have created a track connection from this track to the other in CMS.

Now i tried to release all my actvities and my colleagues activities too at once. It give a big name comma seperated for each of the actvities.

I am getting an error as below with the activities moved in to the node Failed.

Internal error: com.sap.cms.util.CMSUnexpectedException

The export of SC_CR sap.com/Comp#TRACK1_D.13 failed, tcs returncode was 12

Please let me know anybody got this kind of error. and solution for this.

or atleast let me know how to revert back from failed node to Default node,

Additinal info :

I have list of names seoperated by coma(,) in the failed node in the transport view,  Atleast anybody can tell me how to rename the list of names to simple one

Thanks in advance

Regards,

Pavan

Hello,

we are developing (mostly WD) with NWDI and would like to have a SC for all utiliy-classes and external libraries.

For the part concerning external libraries we are fine: We created an utilities-SC, an ExternalLibrary-DC (containing all Libraries and providing PublicParts for compilation) and a J2EE-ServerComponentLibrary-DC that uses this DC for build- and runtime, makes it deployable and provides a PublicPart "defLib" for usage by WD-DC's with LibraryReference to the lib's name (check in VA under "libraries" -> library XY).

<a href="/people/valery.silaev/blog/2005/09/14/a-bit-of-impractical-scripting-for-web-dynpro this Blog</a>

But how can we have a DC for Java-Classes (sources that can be extended or other classes being added) that will be compiled and deployed one time to the server and that can be referenced/used by other DC's (eg. Webdynpro)?

We were able to deploy the JavaClasses on the J2EE (principle as above: JavaDC used by J2EEServerComponentLibrary-DC) and have tried several things, but either the using WD-DC redeployed the jar again or it could not find it at runtime (NoClassDefFoundException), but did not like Library- or SharingReference in WD..

Does anybody know how to do this?

Best regards,

Manuel

Hi all,

Iam using NWDI 7.3 . I have created a java EE DC for example DC1test  and created a class in it . created a public part for the dc. built the dc.how to use this class in other DC created for example DC2test .

Through manage entities in Public parts (adding generated class file )and adding the DC1test dependency in DC2test will achieve this requirement . how can i refer the DC1test class in one of the methods of DC2test class.

Please help me in this.

Regards

Deva

Hi all,

When i using DI_Allinone_This wizard run all post installation steps for DI, CBS, CMS and DTR in our EP system. The following errors occured:

Step 100/116 Create SofewareComponent

error: Not a valid URL: Unexpected character found[':' at position 7]

Step: Create SofewareComponent

DI_Allinone_This wizard run all post installation steps for DI, CBS, CMS and DTR. > Create SoftwareComponent

Create SoftwareComponent

Description

No specified detailed description

State

START_ACTION

Support Information

Type of Action

InvokeServiceDebug Events

InvokeService:Create SoftwareComponent

Library: sap.com/tc_lmctc_templateslevel1_4_tcc

SourcePath ./All-in-one Complete Configuration of DTR, CBS and CMS/createSoftwareComponent17

Time 2008/02/25 at 09:11:03

WSDL /content/NetWeaver/DI/service/SLDConfig_createSoftwareComponent_createSoftwareComponent.wsdl

InvokeService- Result: Failed

Exception Message:Not a valid URL: Unexpected character found [':' at position 7]

Exception Class:java.net.MalformedURLException

Stacktrace

com.tssap.dtr.client.lib.protocol.impl.URLScanner.next_token(URLScanner.java:587)

com.tssap.dtr.client.lib.protocol.URL.parse(URL.java:518)

com.tssap.dtr.client.lib.protocol.URL.(URL.java:63)

com.sap.ctc.util.SLDConfig.createSoftwareComponent(SLDConfig.java:267)

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

java.lang.reflect.Method.invoke(Method.java:391)

com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:227)

com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceExecuter.executeService(JavaServiceExecuter.java:94)

com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:55)

com.sap.tc.lm.ctc.cul.serviceimpl.executor.CULServiceExecutor.executeService(CULServiceExecutor.java:52)

com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault.execute(InvokeServiceControllerDefault.java:145)

com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:206)

com.sap.tc.lm.ctc.metamodel.process.controller.ProcessExecuter.run(ProcessExecuter.java:141)

java.lang.Thread.run(Thread.java:761)

Messages at cancel time

Messages at exception time

<createSoftwareComponentInput> <PRODUCTNAME>NWDIDEMO</PRODUCTNAME> <COMPONENTNAME>NWDIDEMO</COMPONENTNAME> <VERSION>1.0</VERSION> <VENDOR>nwdi</VENDOR> <HOST/> <PORT/> <SLDUSER>NWDI_CMSADM</SLDUSER> <SLDPASSWORD>% secure content %</SLDPASSWORD> </createSoftwareComponentInput>  

global

<root> <HOST>sapepdev</HOST> <SYSTEM_ID>EPD</SYSTEM_ID> <INSTANCE_ID>68506</INSTANCE_ID> </root>  

WebDynpro

<WebDynpro> <loggedInUser>Administrator</loggedInUser> <initial>true</initial> </WebDynpro>  

ErrorMsg

<ErrorCodes/>  

EMPTY_MESSAGE_FOR_XPATH

<EMPTY_MESSAGE_FOR_XPATH/>  

UMEDestination

<Destination type="j2eeengine" subtype="default"/>  

CTCImportParameters

<CTCImportParameters/>  

local

<root> <COMPONENTNAME>NWDIDEMO</COMPONENTNAME> <CONFIGURATION>cluster_data/server/cfg/services/tc.CBS.Service</CONFIGURATION> <DOMAINID/> <CMSHOST/> <NWDI_CMS_ADMIN>NWDI_CMSADM</NWDI_CMS_ADMIN> <TRANSPORT_DIRECTORY>/trans/EPS/in/CMS</TRANSPORT_DIRECTORY> <PORT/> <SLD_ADMIN>NWDI_CMSADM</SLD_ADMIN> <VENDOR>nwdi</VENDOR> <NWDI_PASSWORD>% secure content %</NWDI_PASSWORD> <ACTION>sap.com_com.sap.lcr.LcrInstanceWriterNR</ACTION> <SLDUSER>NWDI_CMSADM</SLDUSER> <NWDI_CMS_PASSWORD>% secure content %</NWDI_CMS_PASSWORD> <NWDI_ADMIN>NWDI_ADM</NWDI_ADMIN> <VALUE>false</VALUE> <GROUPNAME>NWDI.Developers</GROUPNAME> <J2EE_PASSWORD>% secure content %</J2EE_PASSWORD> <NWDI_ADM_USER>NWDI_ADM</NWDI_ADM_USER> <SLDPORT>init</SLDPORT> <SLDPASSWORD>% secure content %</SLDPASSWORD> <NWDI_CMS_USER>NWDI_CMSADM</NWDI_CMS_USER> <TRACK_NAME>DEMO</TRACK_NAME> <SLDHOST>init</SLDHOST> <USERNAME>NWDI_DEV</USERNAME> <CMSPORT/> <ACTIONS>CMS.Export</ACTIONS> <KEY>idleStart</KEY> <NWDI_DEV_USER>NWDI_DEV</NWDI_DEV_USER> <GROUP>NWDI.Developers</GROUP> <COMPONENT>sap.com/com.sap.lcr*sld</COMPONENT> <P4PORT/> <VERSION>1.0</VERSION> <PRODUCTNAME>NWDIDEMO</PRODUCTNAME> <DESCRIPTION>DEMO</DESCRIPTION> <J2EE_ADMIN/> <HOST/> <CMSID/> <ROLE>LcrInstanceWriterNR</ROLE> </root>  

usageProperties

<root> <DW>true</DW> <NWA>true</NWA> </root>  

com.sap.tc.lm.ctc.SystemType

<SystemType> <MegaTenancyFlag>false</MegaTenancyFlag> <MegaTenancyType>CTC_NULL</MegaTenancyType> <SystemRole>CTC_NULL</SystemRole> <SystemLocation>CUSTOMERSITE</SystemLocation> <BCDesignTimeFlag>false</BCDesignTimeFlag> <AppRuntimeFlag>true</AppRuntimeFlag> </SystemType>  

Wizard

<DI_UserInputWizardPage0> <Container0> <J2EE_ADMIN value="administrator"/> <J2EE_PASSWORD value="% secure content %"/> <NWDI_CMS_USER value="NWDI_CMSADM"/> <NWDI_CMS_PASSWORD value="% secure content %"/> <NWDI_ADM_USER value="NWDI_ADM"/> <NWDI_PASSWORD value="% secure content %"/> <NWDI_DEV_USER value="NWDI_DEV"/> <NWDI_DEV_PASSWORD value="% secure content %"/> </Container0> <Container1> <SLD_HOST value="sapepdev.ansteel.com"/> <SLD_PORT value="50000"/> </Container1> </DI_UserInputWizardPage0>  

SLDAdministrator

<SLDAdministrator> <Host>CTC_NULL</Host> <Port/> <User>CTC_NULL</User> <Password>CTC_NULL</Password> </SLDAdministrator>  

J2EEAdministrator

<J2EEAdministrator> <User>CTC_NULL</User> <Password>CTC_NULL</Password> </J2EEAdministrator> 

Can somebody help me!

Best Regards

Terry

Hi,

This is very critical issue.

User is getting locked while connecting to NWDS.User is hitting SLD and

getting locked in SLD.Apparently i have kept the password of user to

same in NWDI and SLD.Please check at earliest as user are unable to

develop application.I have attached screeprint.Once i reset the password for user

he is able to check in and after some time password is expired in SLD.

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

Hi,

Can somebody tell me asto how to customize OVS in webdynpro java development framework?

I would like to show my own customized view at the time of adding OVS extension instead of adding the listener.

Thanks and Regards,

Arya

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.

Hello Experts,

We are trying to update DTR,CBS and runtime system details in CMS after system is migrated to new hardware,but getting following error.

Even after changing system details in landscape configuration,system is trying to reach old server url and not allowing us to update the track.

Both DTR and CBS looks ok on new system.

Any ideas?

Thanks,

Balaram

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 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

Hello,

I have a weird problem. I was developing in NWDS and when I tried to build the application (in order to deploy it) an error appeard, something like "build not completed ... " something about a ressource file ...

I tried 2-3 times again but the number of errors grow...

After that I closed NWDS and since then I cannot open it again. There appears a pop-up that says: "This workspace was written with a different version of the product and needs to be updated. Press OK to update the workspace and open it." When I press OK another pop-up appears "Problems during startup. Check the ".log" file in the ".metadata" directory of your workspace."

I did not install a new NWDS version ... The entries in the logfile are not helping ...

Can somebody help me with an idea?

Best regards

Kris

Hello All,

I have installed a new NetWeaver Version 7.4 on top of it i have successfully installed Billerdirect 635.

I am able to configure XCM and use Billerdirect.In order to do some custom changes i  have installed DI and created a track using NWA.

In the process of   creating an track template i don't see the netweaver version 7.4 in it, It's showing NW 7.3 and below.

Even after creating Track, When i see in CMS my dependencies in FSCM_BD are 730. I have also verified in SLD for FSCM_BD it is showing up 730 version software dependence.

Can i go-head and  check in the code in to tracks and ask developer to change the code, will that effect my BD   server because my NW it's on 7.4 and the software components are 730.

Attaching the same screenshot of my dependency after creating track for software component FSCM_BD 635.

Please help me in moving forward.

Thanks,

Vardhan

Hi There,

We have implemented the CTS+ functionality in our NWDI portal landscape  and tested the same. It is working fine.

Initially transports are created with SIDXXXXX ( *K900009) after this point, all the transports are creating with alphabets ( SIDK90000A, SIDK90000B, SIDK90000C etc.)

Could you please let me know why it is creating instead of numbers.

Is it standard behavior if not please let me know how to correct this.

Thanks,

Pavan.

Hello Experts,

We are trying to update DTR,CBS and runtime system details in CMS after system is migrated to new hardware,but getting following error.

Even after changing system details in landscape configuration,system is trying to reach old server url and not allowing us to update the track.

Both DTR and CBS looks ok on new system.

Any ideas?

Thanks,

Balaram

Hello, folks.

I have a specific task of finding files in DTR that were changed during specific time period. Can anybody give pointers how to get that information? I tried CBS and executed search on requests that were activated during that time period, but it lists components that were involved, and not specific files. Ideally, I'd like to see a list similar to the log that shows when you check in your files, listing which files were uploaded and which were skipped.

Your help will be greatly appreciated!

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

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.