on 06-10-2009 11:01 AM
Hi all,
We´re developing a customized b2b application based on the application in SAP.SHRWEB. We've been following ISA DEvelopment & Extension guide and have been able to deploy our customized application to the developmentserver through NWDI.
We are now trying to transport our application to the testsystem, but get stuck because our assembled CUSTCRMPROJ .sca-file doesn't contain any deploy archives. Therefore the application don't get deployed to our testsystem.
Any ideas what goes wrong here?
Hi Anders,
As usually you assemble the the SCA files(SHRWEB) first. after that assemble CUSTCRMPRJ even status shows Assemble,. then your problem will be resolved.
Regards,
Anil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, consolidation is needed.
The steps goes like
Check in
> Activate
> Release (can be grouped)
> Consolidate(all activities) all released activities or which so ever you want to include in your transport. Make sure there is no component consolidated that has dependency on a component that is not getting transported.
> Assemble(adviced, not to uncheck anything, but if there are components that are broken but doesn't have impact on any other component, the relevant check box can be unchecked. )
> Import in Transport tab > This will deploy the SCA in your test system.
Regards,
Nitin
We're not entirely sure that the configuration is correct and we had help from a consultant to do this job, so we're not sure of exactly how the configuration was done. There are a few suspicious things in the system though.
We don't have a Consoldation runtime configured. I that needed to pass the activities on to test?
Our CUSTCRMPRJ has version 7.0 although SHRWEB and SHRAPP are 6.0. We can't find any CUSTCRMPRJ 6.0 in the SLD, although there are 5.0 and 7.0. I this correct?
I've looked at the Consolidation tab now. The funny thing is that we can't find our CUSTCRMPRJ in the history on the Consolidation tab. There is an activity from the creation of CUSTCRMPRJ with the initial configuration of context root. Shouldn't that be seen on the Consolidation tab?
Now we have run in to another problem. We tested to do a new activity with a small change in CUSTCRMPRJ, checked it in, activated and released it. The new activity shows up in Consolidation tab, but when we try to do an import it times out.
We get the timeout in CBS-Make while doing import of an activity in Consolidation tab.
CBS-Make log
-
20090617144515 Info :Starting Step CBS-make at 2009-06-17 14:45:15.0679 +1:00
20090617144515 Info :wait until CBS queue of buildspace NED_CRM60D01_C is completely processed, before starting the import
20090617144515 Info :CBS queue of buildspace NED_CRM60D01_C is completely processed. Starting the import now.
20090617144516 Info :=================================================================
20090617144516 Info :buildspace = NED_CRM60D01_C build request id = 834
20090617144516 Info :wait until CBS queue of buildspace NED_CRM60D01_C is completely processed, before asking for build results
20090617144516 Info :waiting for CBS queue activity
20090617144546 Info :build process already running: waiting for another period of 30000 ms
20090617144546 Info :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090617144616 Info :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090617144646 Info :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090617144716 Info :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090617144746 Info :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090617144816 Info :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090617144846 Info :waiting for CBS queue activity
20090617144917 Info :build process already running: waiting for another period of 30000 ms
20090617144947 Info :build process already running: waiting for another period of 30000 ms
20090617144947 Info :waiting for CBS queue activity
20090617145018 Info :build process already running: waiting for another period of 30000 ms
20090617145018 Info :waiting for CBS queue activity
20090617145049 Info :build process already running: waiting for another period of 30000 ms
20090617145049 Info :waiting for CBS queue activity
20090617145120 Info :build process already running: waiting for another period of 30000 ms
20090617145120 Info :waiting for CBS queue activity
20090617145151 Info :build process already running: waiting for another period of 30000 ms
20090617145151 Info :waiting for CBS queue activity
continuing like this until timeout...
-
Use the CBS WebUI to check the state of your buildspace (the Consolidation buildspace ends with C): Find out which DCs are dirty and why. Also compare the number of DCs of the base SC's (SAPJTECHS, SAP_BUILDT, etc.) with the development buildspace (_D); if these do not match you may need to reimport them with CMS.
This was resolved a long while ago. It showed to be a really simple thing causing all the trouble. There where some old activities in the system that wasn't released. Since these where made more than two weeks ago, and by another user they were filtered out by the actvites filter in NWDS. This filter is hidden under the smalll arrow up in the left corner of the activites view.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.