All,
After following the transport help about the CMS transports, I still do have a question which I cannot find back on how it should be working.
I had set up a DIM track and a OAP track and between that a transport track connection which I had set on 'transport' as written in the SAP docu.
Know they are busy doing there normal transports in de first track, but when they approved the transport in this case in M, I cannot see them.
How does it normally work transporting between tracks?
We search for a solution in NWDI which automtically compress javascript and css files during activation or build process. There is a java library from Yahoo (YUI Compressor) which can be used. But how is it possible to call user functions during the build process in NWDI. With Apache ANT it is possible to define the steps in build.xml. NWDI also works with ANT as Buildtool, but how we can modify the build.xml File?
Hi ,
I am very new to the NWDS . I am not able to delete the DC configurations as it says , some files are changed/edited , look over your open activities. The error pop screen says ,
"there are objects to be checked out , cant remove configurations as the files of follwing dc are checked out :... "
To remove configurations , make sure no files in dc are checkout.
How do i do this ??
Please help!!
Hi,
I have seen many posting about this subject, but i had the feeling most people managed to avoid the Local SC file and fixed it in a different way. Somehow I had the feeling, that nobody managed to use the export feature
Can i use the SC Export feature within the NWDS to import custom SC's to a development track in the NWDI?
I did use it including all sources, but when i try to import the file, then it always ends up with the message :
20130529162808 Info :1. propagation request is of type TCSSoftwareComponent20130529162808 Fatal :check failed, because the sources are not contained in the archive
I checked the file, and all sources are there in the "SOURCEARCHIVES" folder. I also did import the SCA file into another ecliplse workspace as local SC and it work. All sources do show up in the local DCs.
I saw some comments about making sure, that the SLD has the same dependencies maintained and i did. All CMS definitions are in sync with the SLD
Any suggestions?
Thank you for your help
Hello,
We have a E-Commerce landscape connected to NWDI. One of the standard software components was initially modified by the developers through NWDI. Later on, the component was excluded from deployment. Now, when we try to update the component through JSPM, it shows that "local version modified by NWDI" which would prevent JSPM from updating the component. Similarly, as the component has been excluded from deployment in CMS, it cannot be updated through CMS also. We donot need any of the initial changes made to the component.
Is there anyway to reset the status of the component so that we can update it using JSPM?
thanks
Vipin
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
Hello expert,
I have build BRM component locally and deployed to DEV server, but now I am migrating this to NWDI.
Here is the steps I have performed
1) copy Local DC to Imported configuration
2) Created the project
3) added to Source control
4) Check in
When I am trying to check in, it tries to build on Server and activation is failing.
I am getting below error in CBS Request log
"Build
Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID"
Any idea why
thanks,
CK
Hello,
we're migrating some projets from 7.0 to 7.3, we've migrate most of the projects and activate them without problems.
One of our project is a portal mastheadcustomization:
we've migrated the project and we've no problem in building on NWDS but when we chek-in and activate we've the following problem:
Build number assigned: 20523
Change request state from QUEUED to PROCESSING
REQUEST PROCESSING started at 2013-04-16 12:18:19.202 GMT
ACTIVATION request in Build Space "JDI_Portail_D" at Node ID: 109,003,250
[id: 12,562; parentID: 0; type: 4]
[options: FORCE ACTIVATE PREDECESSORS]
Waiting for access: 7 ms
===== Pre-Processing ===== started at 2013-04-16 12:18:19.209 GMT
List of requested for activation activities:
''irsn.org_SPECIFIC_IRSN_1'' compartment
default
[ISN 42][created by MTC_STR at 2013-04-16 14:18:18.0][OID 357b3161a68d11e2a9a30000067f41f2]
There is 1 activity in compartment irsn.org_SPECIFIC_IRSN_1
1 activity will be processed by this request
Analyze dependencies to predecessor activities... started at 2013-04-16 12:18:19.216 GMT
Analyzing predecessors in compartment "irsn.org_SPECIFIC_IRSN_1"
8 not activated predecessors are detected
The following activities are being added to request:
"default" [seq. no 35][created by MTC_STR at 4/16/13 10:35 AM][ID 08e344eba66711e2a99e0000067f41f2]
"fix brokzen dc" [seq. no 34][created by MTC_STR at 4/16/13 10:07 AM][ID 08e34512a66711e2bb470000067f41f2]
"default" [seq. no 37][created by MTC_STR at 4/16/13 11:20 AM][ID 4d420f61a67611e2b9c70000067f41f2]
"default" [seq. no 41][created by MTC_STR at 4/16/13 12:14 PM][ID 7f52a0cea67a11e2ab400000067f41f2]
"default" [seq. no 40][created by MTC_STR at 4/16/13 11:53 AM][ID 7f52a0fba67a11e2be980000067f41f2]
"default" [seq. no 39][created by MTC_STR at 4/16/13 11:46 AM][ID 8469ee54a67911e2c4e30000067f41f2]
"default" [seq. no 38][created by MTC_STR at 4/16/13 11:36 AM][ID dc814858a67611e2c3fc0000067f41f2]
"default" [seq. no 36][created by MTC_STR at 4/16/13 11:16 AM][ID f40bb231a67011e292780000067f41f2]
Analyze dependencies to predecessor activities... finished at 2013-04-16 12:18:19.243 GMT and took 27 ms
Analyze versions... started at 2013-04-16 12:18:19.244 GMT
List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2013-04-16 12:18:19.263 GMT and took 18 ms
Synchronize metadata for [irsn.org/IRSN_Masthead] started at 2013-04-16 12:18:19.281 GMT
Verification of DL [ws/Portail/irsn.org_SPECIFIC_IRSN/dev/active/] finished at 2013-04-16 12:18:19.300 GMT and took 6 ms
Verification of cache (level 2: Comparison of attributes) finished at 2013-04-16 12:18:19.326 GMT and took 26 ms
Synchronize metadata for [irsn.org/IRSN_Masthead] finished at 2013-04-16 12:18:19.327 GMT and took 46 ms
<REDEFINE> ''irsn.org/IRSN_Masthead'' DC
Analyze versions... finished at 2013-04-16 12:18:19.334 GMT and took 90 ms
Analyze activities... started at 2013-04-16 12:18:19.334 GMT
Loading component definitions
1 component to be build in compartment "irsn.org_SPECIFIC_IRSN_1"
Analyze activities... finished at 2013-04-16 12:18:19.355 GMT and took 21 ms
Calculate all combinations of components and variants to be built...
Analyze request DC BV... started at 2013-04-16 12:18:19.360 GMT
''irsn.org/IRSN_Masthead'' variant ''default''
''sap.com/tc/bi/bp/portalapplication'' variant ''default'' cannot be built. ACTIVATION will fail.
NO SUCCESSFUL BUILD for the used variant ''default'' of component ''sap.com/tc/bi/eptech'' is available.
[DC 167 variant ''default''][SC 739 ''sap.com_EP_BUILDT_1''] using [DC 169 variant ''default''][last successful build: 20401]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Build Variant mapping is not defined. Configuration does not allow DC references from Compartment ''sap.com_EP_BUILDT_1'' [id: 739] BV ''default'' [id:739] to Compartment ''sap.com_SAP_BUILDT_1'' [id: 749]
Analyze request DC BV... finished at 2013-04-16 12:18:19.420 GMT and took 60 ms
===== Pre-Processing ===== finished at 2013-04-16 12:18:19.421 GMT and took 212 ms
Change request state from PROCESSING to FAILED
Error! The following problem(s) occurred during request processing:
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
Error! The following error occurred during request processing: Activation failed due to component "sap.com/tc/bi/bp/portalapplication" variant "default". The component is OK.
REQUEST PROCESSING finished at 2013-04-16 12:18:19.423 GMT and took 221 ms
No build logs available for the request.
we can't understand what
''sap.com/tc/bi/bp/portalapplication'' variant ''default'' cannot be built. ACTIVATION will fail.
NO SUCCESSFUL BUILD for the used variant ''default'' of component ''sap.com/tc/bi/eptech'' is available.
could mean. Do you have any clues?
Thank you in advance.
Hello All,
We currently upgraded our NWDI server to 7.31 and have few tracks which need to be supported in 7.0 version too. From our 7.31 NWDS we are able to login and initialize the development infrastructure. But for some reason when we want to import the development configurations in NWDS 7.0 it just hangs in there for 15 mins and then gets the timeout error.
I enabled debugging in NWDS and found the logs that the DTR Server is unreachable. The DTR is up and running. I can login to DTR through browser, CMS and also from my 7.31 NWDS. The lower version of NWDS 7.0 SP13 is causing this issue. I searched the forums and there is only one thread that matches my issues but the solution was not posted in the end :-(
http://scn.sap.com/thread/1881014
I have raised an OSS Message with SAP but just wanted to check if there are people in the community who has faced / has any ideas about this issue.
Thanks,
Nagarajan.
Hi,
Currently, we have 7.2 development landscape that includes CE 7.2
connected to NWDI 7.2.
At the same time we have another system with new NWDI 7.31 configured and
we would like to understand how can we "merge" the current 7.2 system into 7.31 system
so we will have one NWDI in the organization.
Is it possible ? how exactly ? can we "Upgrade" 7.2 SCs to 7.31 during the merge ?
Kind regards,
Dimitry
Hi All,
We are configuring NWDI 7.0 track for NW 7.31 development, we have downloaded required SCA from SMP. And copied all the required SCA to the location mentioned in "Transport Directory" (in below screenshot: that is - /usr/sap/trans/EPS/in/<XXXfolder>)
We have created Software Component for development, added the all the required "BuilTime" dependencies, created track, and updated the CMS and "Build Variant".
Question:
1. The required SCA's are not seen in Check-in Tab in CMS
2.When we imorted track in NWDS, we DO NOT see sub components in dependent components (for example: WSRM component should display 'tc/esi/esp/wsrm/facade' which is not visible)
Please let me know if you have any suggestions.
Regards,
Patana
Experts,
1. I have already existing four different tracks in my NWDI with all the components CMS, CBS, DTR, SLD working fine.
2. A user is assigned with appropriate roles of NWDI developer and NWDI administrator and has correct authorizations for roles and groups.
3. When this user tries to import via the 'Development Configuration Import' and remote option in the NWDS, he is able to see only two tracks in the list instead of four.
4. There are no errors, just the fact that instead of four tracks entries only two are available in the list.
What is the issue here?
Regards,
Kaushik
I am looking for the best/quickest way to get a bunch of Java WARs deployed to NetWeaver. From what I am gathering, it appears that they may need to first be packaged as EARs? Then, I have read that NetWeaver Developer Studio can be used to deploy applications. Is this the preferred/quickest option? Are there alternative ways, such as through NetWeaver's administration console or via a Maven plugin?
I am trying to download NetWeaver Developer Studio, but it is proving difficult to find where to download it from on sap.com. If I go to http://www.sap.com/platform/netweaver/components/index.epx --> SAP NetWeaver Developer Studio this will take me to SAP NetWeaver Visual Composer, which doesn't seem to be right? Or is it? Can you please provide me with the correct location for a SAP NetWeaver Developer Studio (preferably for Linux).
Also, as a follow on question, how or where can I configure NetWeaver to have a JNDI data source?
I am using SAP NetWeaver 7.3 SP09 and PI 7.4 However, when I connect to the ESR of the PI system, I cannot see or import the Operation mappings defined in there. Is it that SP09 does not support Operation mapping to be imported from PI environment? Please suggest. Thanks. Anuradha.
Hi All,
We upgraded our NWDI to NW7.3 SP9.
We are facing issue while Assemble and attach to the CTS+ Transport Request.
There are broken DCs in the Consolidation track.
The error log shows
20130613122237 Info :Starting Step Check-assembly at 2013-06-13 12:22:37.0063 +3:00
20130613122237 Info :Checks for software component *.com,*_SBM_MDM are performed now:
20130613122237 Info :list of broken DCs:
20130613122237 Info :*.com,sbm/mdm/connect
20130613122237 Info :*.com,sbm/mdm/lib
20130613122237 Info :*.com,sbm/mdm/prt
20130613122237 Info :*.com,sbm/mdm/prtclnt
20130613122237 Info :*.com,sbm/mdm/sasrprts
20130613122237 Info :*.com,sbm/mdm/sdwrap
20130613122237 Info :*.com,sbm/mdm/search
20130613122237 Info :*.com,sbm/mdm/suptree
20130613122237 Info :*.com,sbm/mdm/swdwrapper
20130613122237 Info :*.com,sbm/mdm/swforms
20130613122237 Info :*.com,sbm/mdm/vmdforms
20130613122237 Info :*.com,sbm/mdm/wfmonitor
20130613122237 Fatal :Nonempty list of broken DCs, stopping export now
20130613122237 Info :list of problem DCs:
20130613122237 Info :*.com,sbm/mdm/prt
20130613122237 Info :*.com,sbm/mdm/connect
20130613122237 Info :*.com,sbm/mdm/prtclnt
20130613122237 Info :*.com,sbm/mdm/lib
20130613122237 Info :*.com,sbm/mdm/sdwrap
20130613122237 Info :*.com,sbm/mdm/suptree
20130613122237 Info :*.com,sbm/mdm/vmdforms
20130613122237 Info :*.com,sbm/mdm/sasrprts
20130613122237 Info :*.com,sbm/mdm/swforms
20130613122237 Info :*.com,sbm/mdm/swdwrapper
20130613122237 Info :*.com,sbm/mdm/search
20130613122237 Info :*.com,sbm/mdm/wfmonitor
20130613122237 Fatal :Nonempty list of problem DCs, stopping export now
20130613122237 Info :Checks for software component *.com,*_SBM_MDM finished succesfully
20130613122237 Info :Step Check-assembly ended with result 'fatal error' ,stopping execution at 2013-06-13 12:22:37.0279 +3:00
There are 12 DCs are broken in the CBS.
Could you please help to fix this asap?
Regards,
Senthil
Hi experts, how are things?
We upgrade our NWDI from 7.01 to 7.3 SP08 some weeks ago and after this upgrade, show us this error when we try to access the DTR:
<DAV:error><DAV:access-denied/></DAV:error>
Have you any idea what should we do to solve this issue?
Thanks
Marcos
Hi All,
We have done system copy from old NWDI system to new NWDI system.
Done few code changes based on business requirements in the old NWDI system.
So moved changes and Imported into CMS till Assembly successfully and assembled also.
From Assembly tab downloaded latest SCA files and copied into Inbox of new NWDI system. [Same inbox path is configured for Check In tab].
Also copied Stanadard Plugs[SAPJEE , JTECH, BUILDT..etc] in Inbox folder.
Issue is the Code changes SCA file is not displaying Check-In tab of CMS.
Could you please tell /help how to resolve the issue. Is there any other way to copy latest SCA file to new NWDI system.
Note : copied SCA file with full permissions and also Standard SAP Plugin displaying in Check-In tab.
your help will be appreciated.
Best Regards
CW
Hello SDN!
We require to copy our developed SCs with their sources from old track to new for continiuing developing in new track. The problem is that these tracks belongs to different SLDs and there is no way to make connection between these SLDs or tracks. How we can copy it?
Thanks and regards,
Lev
Hi All,
I have a portal & webdynpro application in the form of a single .sca file.
I unzipped the file using winzip and got two files - .ear and .epa.
I want to import this in NWDS to view the code and make some changes in webdynpro.
Can anybody give me the step by step procedure to do this?
Will surely award points for useful answers.
thanks
Juhi Kulshreshtha
Hi All,
We are on NW 7.01 and we will be upgrading to NW7.31 in a short time. In the process, the NWDI too will be upgraded.We have modified the standard ESS , MSS components using NWDI as per the customer requirements.
Now, when we upgrade our system to NWDI 7.31,
Please help.
Regards,
Adren