CMS-Transport Studio: Link Transport Organizer is disabled

Dear Experts!
When I using Change Management Service- Transport Studio, I see that the link Transport Organizer is disabled with information
" Change and Transport System not configured for the selected Track" , I already config CMS and TMS as the document guide.
Please help me resolve this problem.
Thanks all.

Hello Thao
The situation looks more like an configuration issue, very
probably caused by the error concerning the name of the RFC destination
(note 1003674): Please ensure that the destination is named
'sap.com/com.sap.tc.di.CTSserver', with only capital 'CTS', but
completedly small 'server' at the end.
Thanks
Kenny

Similar Messages

A Important problem about CMS Transport Studio Test Tab

Hi experts:
    I am use NWDI and modify ESS source code, when i check in my modified project like esstratre and release it . In CMS transport studio i consolidation , assembly it then test it .but i make a fatal mistake,there is some mistake in project esstratre but i already check in it .So in the Test tab SMD deploy failed.
   Now i want restore the history version before i modify the project . But what can i do? Please help me.Thanks a lot.
                         yours zunxian

HI,
there is some mistake in project ess~tra~tre but i already check in it
1. can you check out your DC and correct those changes? and check in it.....its the best solution.
    and good for you , so you can keep some needed changes, present in that activity.
2. in DTR perspective there you can see versions in the version graph view.
3. or use sync to date option for your DC.
But the 1st option is preferable as a developer.

NWDI check-in of CMS transport studio has no entries

Hi,
I want to use the CMS to import existing packages in a new one. The sld and the Landscape Configurator are configured and the packages are in the inbox of the CMS. But there are no packages shown in the check-in table of the transport studio.
Have anyone had this problem before? Whats the reason?
Kind Regards
Norman

Hi Norman,
did you receive an answer to your question or did you find a solution by yourself?
We are facing the same problem, we don't find the MSS Package in the Transport Studio for check in. We did copy the .SCA file into the import folder of the Transport Studio.
Any help would be appreciated!
Regards, Andreas

How to add aditional TAB in transport studio of CMS !!!

Hi,
Query 1:
If we define runtime system configurations for Dev, Consolidation (QA system), test and production in landscape configurator of CMS, same appears as TABs in transport studio of CMS.
Also sequence will be Dev than consolidation than Test and finally production system TAB.
I want to add one more TAB in transport studio of CMS that correspond to my traing portal server, so that I can import all my changes which has been moved to production into my training server, also I want this additional TRAING SERVER TAB to appear after production TAB in transport studio of CMS.
How i can achieve this ??
Query 2:
If i want to bring test server TAB after production TAB in transport studio of CMS , how I can do this ? generally Test system TAB comes before production server TAb, I want Test system TAB to come after production TAB? How to do this ??

Have a look at this blog.
/people/marion.schlotte/blog/2006/03/30/best-practices-for-nwdi-track-design-for-ongoing-development
Additionally search for 'track connection'.
The idea is to create a new track in to which all your production code from the first track can be transported.
Regards, Marcel.

SC's Dependencies are missing in the check-In tab of the transport Studio

In SLD, the SC is created with the following dependencies:
(1) DI Build Tool 7.0
(2) SAP J2EE Engine 7.0
(3) SAP JAVA TECH SERVICES 7.0
Then, in NWDS, in the Development Configuration Window, the SC which is created is loaded.
Within the created SC, the DC is created. but the DC is created with some errors saying " The dependency files are not linked".
XML of CBS Build Compartment:
Software Component SC : SAP_JTECHS
SC State : ( 3 gray colored circle )
<dependencies>
</dependencies>
<build-variants>
<build-variant name="default" required-for-activation="yes">
<variant-mappings>
</variant-mappings>
</build-variant>
</build-variants>
Please note the dependencies tag are empty.
I also done "update CMS". but still it remains the same. please explain me my mistake.
D:\usr\sap\JTrans\CMS\inbox folder is empty.
I could able to see all the buttons in the Check-In tab of the transport Studio. But the Check-In button is disabled and the table of Check-In tab is empty.
The required Track is selected in the left-hand side of the Transport Studio Window.
Please guide me.

Hi Sathya,
First you need to put SCA files
(1) DI Build Tool 7.0
(2) SAP J2EE Engine 7.0
(3) SAP JAVA TECH SERVICES 7.0
In your D:\usr\sap\JTrans\CMS\inbox in the server.
then you can create TRack and add SC dependancy to track...after that it will appear in the check-in tab.
Hope it helps,
Regards,
arun

Immport Failed in Transport studio

Hi experts,
While importing the SAP-JEE.sca, SAP_BUILDT.sca and SAP_JTECHS.sca files in transport studio in CMS I am getting the following error whn importing SAP-JEE.sca file itself.
Info:no changes on the CBS request queue (ZES_Test_D) after a waiting time of 14430000 ms
Fatal:The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
Fatal:Please look after the operational status of the CBS.
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS.
com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:370)
     at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:120)
     at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
     at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
     at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
     at
Give me your suggestions
Regards
Harshavardhan

Hello Harshavardhan
Please check the following;
-the engine is running and that CBS is running.
-idlestart is set to false.
-Can you please log on to the CBS Web UI (Component Build service link
on top of the CMS UI page) and do a search for requests (requests tab
in the CBS UI) in the buildspace. Do check and
let us know whether there are any requests that are queued or failed.
As you see in the error log the TCS cannot import the request
because queue is not empty and can be caused for any problem in
previous request.
Thanks
Kenny

Import SCA files in Development Tab of the Transport Studio take more time

Hi,
After Check-In files in the Transport Studio, the import of SCA files starts in the development Tab of the Transport Studio.
The import takes more time. Why this happens?
Am I missing any configuration? Please specify in detail.
Thanks in Advance,
Sathya

SC: sap.com_SAP-JEE:
SDM-deploy
Returncode : Not executed.
How to check the username, password and url for SDM?
Log file of Repository-import:
Info:Starting Step Repository-import at 2009-10-13 22:15:49.0484 +5:00
Info:Component:sap.com/SAP_JTECHS
Info:Version :SAP AG.20060119105400
Info:3. PR is of type TCSSoftwareComponent
Info:Component:sap.com/SAP_BUILDT
Info:Version :SAP AG.20060411165600
Info:2. PR is of type TCSSoftwareComponent
Info:Component:sap.com/SAP-JEE
Info:Version :SAP AG.20060119105300
Info:1. PR is of type TCSSoftwareComponent
Info:Step Repository-import ended with result 'not needed' at 2009-10-13 22:15:49.0500 +5:00
Log File of CBS-make :
Import got failed.
Info:build process already running: waiting for another period of 30000 ms
Info:no changes on the CBS request queue (DM0_DEMObp1_D) after a waiting time of 14430000 ms
Fatal:The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
Fatal:There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
     at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:369)
     at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:120)
     at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
     at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
     at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1736)
     at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
     at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2009-10-14 02:16:28.0296 +5:00

[Urgent]importing error on Consilidation stage on transport studio

Hi all
object from IR in using CMS was transfered to Production successfully, but when i export configuration object from ID, it was sent to CMS successfully, and i can see it on consolidation tab on transport studio as waiting for import.
when i tried to import it. i got "import failed"
anybody help me?
error log is below;
Software Component sap.com/SAP-INTDIR
Version CMS_ID.KKXI_D.8
Label Export list-Myscenario2
System ID.KKXI-Consolidation
Step Repository-import
Log D:\usr\sap\JTrans/CMS/log/ID.KKXI_C@CMS/[email protected]
Info:Starting Step Repository-import at 2006-01-19 17:31:52.0328 +9:00
Info:Component:sap.com/SAP-INTDIR
Info:Version :CMS_ID.KKXI_D.8
Info:1. PR is of type TCSChangeRequest
Info:export and import XI are different: http://xid.kk.net:50000/dir -> http://xip.kk.net:50000/dir
Info:reading of XI06f7b49088c611dac604001018006446.cl for xichangelist 06f7b49088c611dac604001018006446
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: XiTransportException received:
ClientServerException exception:Internal error: Unable to transfer changes for object Service | XIP to change list "XI 3.0 Import"
Message was edited by: David

ClientServerException exception:Internal error: Unable to transfer changes for object Service | WSD to change list "XI 3.0 Import" (db8254c0-6ab8-11db-a90b-0017084cb84a) since object still in change list "XI 3.0 Import" (e9f6b680-67d0-11db-9a1c-0017084cb84a)
I think it's same error.
I didn't find open object in change list.
Dose anyone know a solution of that.
Please help me.
sskim
Message was edited by: SangSu Kim

CMS to use Portal Transports??

Hello All,
I was wondering if i could use the CMS for the Portal Transports. Is this Possible?? If yes, then someone could help me configuring this.
Regards
Vaib

If you are talking about transports in the Portal, then no CMS is not used. I think you may mean TMS or CTS.
There is a transport process that uses export / import feature which allows you to move content from Development to Test and Production like R/3 concept.
You Export Content using the Package Export Editor.
System Administration > Transport > Export
Create a transport package or create one
Select content from the navigation screen, right click and choose Add <Object> to Transport Package to add the object to the transport package
Use the Export button to preview the content that will be exported, including any dependent objects. From this you can exclude any objects, in the SAP namspace (com.sap.portal or com.sap.km) will be excluded.
Select a name for the export with Start Export.
The Download Export File link can be used to download the export file, if required.
Import content:
Ensure the *.pkg or .epa file is available
Start the transport import utility by choosing Administration > Transport > Import
Select the client or server as the Source for Package Files, select the file and use the Upload to preview the contents.
Select the appropriate option for overwriting the existing content.
Use the Import to start the import process

SC State in Transport Studio!

Hi people/collegues,
I am trying to use NWDI.
step1. A track is configured. -> OK
step2. Create a SC and adding dependencies (Production State: developed or planned). -> OK
step3. Adding an SC to the track -> OK
Going to the Transport Studio and after check-in the dependencies,my SC is directly in Assembly and not in Development . Why?
Any advice? It is important.
Thanks in advance for your replies.

Thanks for your replies.
My track definition contains the SCs for the development and the development system is checked in the runtime systems of the track.
Is not possible that my SC is in "assembly" because it is considerates as an unit assembly at the beginning?
Then only the DCs could be change the own status from dev to consolidation?
Best regards,
Mirco.

In NWDI transport studio propagation request is of type TCSSoftwareComponen

Hi all,
I am now currently installaing NWDI for my lansdscape.
I created a software component added dependencies, domain and track after that in transport studio i was trying to import the these files as per the document(SAPBUILDT13_0-10003479,SAPJEE13_0-10003469.SCA,SAPJTECHS13_0-10003467.SCA) while doing it showing import running for a long tome then i checked the log files its diplaying an error its not imported like that.
For your reference i posted the log also.
20080417095931 Info   :Starting Step Repository-import at 2008-04-17 09:59:31.0571 +5:00
20080417095931 Info   :Component:sap.com/SAP_JTECHS
20080417095931 Info   :Version :SAP AG.20070812015951
20080417095931 Info   :3. propagation request is of type TCSSoftwareComponent
20080417095931 Info   :Sources will not be imported for this SC
20080417095931 Info   :Component:sap.com/SAP_BUILDT
20080417095931 Info   :Version :SAP AG.20070811184000
20080417095931 Info   :2. propagation request is of type TCSSoftwareComponent
20080417095931 Info   :Sources will not be imported for this SC
20080417095931 Info   :Component:sap.com/SAP-JEE
20080417095931 Info   :Version :SAP AG.20070812015311
Regards
Vijay kumar G
20080417095931 Info   :1. propagation request is of type TCSSoftwareComponent
20080417095931 Info   :Sources will not be imported for this SC
20080417095931 Info   :Step Repository-import ended with result 'not needed' at 2008-04-17 09:59:31.0617 +5:00

Hi all
solved on own.
Regards
Vijay

Transport Studio

Hi Experts,
I try use NWDI, but, I created a Product and Software Component in SLD, and define my dependencies. After, I created a new track with a SC. This SC has the DC necessaries (JEE, Build and JTechs).
Now, when I go to Transport Studio, the Check in tab is empty? Whats happened?
Because this error, I have errors in NWDS with my DCs
Regards,
Davi

Hi,
what errors do you get in the Netweaver developer studio?
Cehckin tab in Transport studio is just used to upload some Software components in the track. In my opinion emptiness of checkin tab should not create any problem in the NWDS.
If you can post the error details, we can check what is the problem.
Akshatha

Do not see created SC in check in tab of transport studio

Hi,
We have created a SC in SLD and created a track and added that SC in Track.
But when coming to the transport studio . Do not see the created sc , but can see the three dependent SCs as they are present in inbox.
we are in Netweaver2004s . OS : windows
any solutaion ?

Hi Kousik,
If I am not wrong then you have created SC in SLD and you wanted to start development under this SC, right?
You have not added this SC as dependant SC. It will show only dependant SCs in the check-in list. You have to import those SCs into Development to start working with this.
Try to import configuration from Developer studio. You will see your SC.
If my assumption is wrong please reply.
Regards,
Bhavik

Transport internal links

Hello,
Is it possible to transport internal links in km? I tried it with ICE transport and via Portal Drive. It didn't work.
Thanks,
Kirsten

Hello,
You can transport internal links in KM with ICE. However, there are some issues with this...sometimes some links are not transported. I was told through SAP OSS that the issues should be fixed in SPS 21. However, we are not able to upgrade to SPS 21 yet to confirm this.
Hope this help,
The Hung Nguyen

Automatic deployment of Interactive Forms through CBS and Transport Studio?

Good evening!
I just finished my last changes on my first Web Dynpro project and a local build and deployment worked without problems.
Now, when I check in the changes into DTR, activate and release the files, then my changes on different web pages are displayed but now the Interactive Form that worked before is no longer generated and no error message can be found.
We are currently using Netweaver 2004 on our development systems with Web AS 6.40 PatchLevel 108290.313 on AIX 5.3 as our development portal.
So, could you tell me where I can find errors of the Adobe Document Service ? I think that the problem is somehow connected to the ADS, but I am absolutely unsure.
Thank you for your answers and for your help.
Regards,
Sascha

We actually didn't have a problem with the transport studio and CBS, it all had to do with the usage of different browsers on the development system (with IE) and our development portal (which I tested from my local computer with Firefox) ... the problem was once again sitting between keyboard and chair.

CMS-Transport Studio: Link Transport Organizer is disabled

Similar Messages

Maybe you are looking for