Runtime systems

Hi,
What are the various runtime systems available in NWDI ?
Thanks,
Teja

Teja,
you have 4 runtime systems which you can configure Development,consolidation,Test and Production .
check this link
http://help.sap.com/saphelp_nw70/helpdata/EN/44/355093ba830a67e10000000a422035/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/a0/43884445d6474eb103908f355bd558/content.htm
Thanks
Bala Duvvuri
Edited by: Bala Duvvuri on May 11, 2009 4:37 AM

Similar Messages

Runtime system and weird types

When many of objective-c's unique features and 2.0 additions are discussed, it is often said that they depend on the "runtime system" in order to function. What is it? It almost sounds like a virtual machine, but somehow I doubt that.
Also, what is the difference between both Null, nill, and nil, and Bool and BOOL?
Any help is greatly appreciated.

palms831 wrote:
First of all, what is meant by linking against something, and what does linking in general mean? I know it's part of the compilation process, but my knowledge is pretty fuzzy beyond that.
Actually, it is not part of the compilation process. It is part of the building process, but that is different. Compiling takes a symbolic language and converts it into its equivalent machine language. Linking goes through all of the compiled object code and connects functions with their associated function calls. It will then construct some sort of "runtime object" (such as an application or shared library) that can actually be used.
Also, I know that when I instantiate an object I am sending a message to a class object. What I'd like to know is when that class object is created, and what determines which classes get instantiated and which don't.
Any class that you create will get instantiated. (Though one normally doesn't refer to classes being instantiated. Objective-C just happens to have a powerful runtime language that allows you to treat classes almost as if they were objects). A good linker will take any instantiated classes or functions that are never used and remove them from the executable. GCC and other UNIX linkers usually cannot do this. They can only remove unused object files that contain nothing but unused functions. That is why the Linux kernel contains so many tiny files with only one function. Microsoft, Borland, and Codewarrior Linkers were much better at this.

Questions on Runtime systems

Hi to all
I have two questions:
1)
SAP says do not use the system where the JDI s installed as runtime system, I suppose in order to avoid the CMS deadlock described in note 754143. Right ?
Suppose we have three system D (develop), T (test) and P (Pro). Teh JDI is instaleld in D. We define the track Development with the runtime systems T as "test" and P as "production".
As I understood the deploy on the D system happen automatically as soon the activation is triggered into the Dev Studio IF the system D is used as runtime system.
Please could you clarify how we can keep aligned the D environment with the system T and P from the point of view of he deployment if we cannot use the D system as runtime environment ?
2) Suppose we have three system D (develop), T (test) and P (Pro). Teh JDI is instaleld in D.
We defined the tracks DEVELOP and MAINTENANCE, connected by a 'repair' connection.
If I understood weel the DEVELOP track and the MAINTENANCE track should have the Development and the Test runtime system in exchanged order:
the system indicated as Test for the DEVELOP track has to be indicated as Develop for the Maintenance track.
Then the runtime Production system has to be defined for the DEVELOP track only ?
Regards

Hi, thanks H. for the info.
I understood the MAINTAIN track and the DEVELOP track MUST to have different runtime systems.
We need at least, (minimun), 3 different systems (development1 and test on the DEVELOP track and development2 on the MAINTEN track) in order to maintain an old relese of SC while a new release is in progress, right ?
It's then responsability of the 'connection repair' defined between the tracks to move the software from the DEVELOP track to the MAINTEN track.
Please, in which moment of the DEVELOP track the software will be copied also to the MAINTEN track ?
New question about the Consolidation phase.
At the beginning we configured ONLY the runtime development for the DEVELOP track. So the work o teh developers was deployed automatically on that system as they activate their activities into the Developer studio.
As traiing we released the activities and we saw them into teh Consolidation tab queue ready for transport (NO Consolidation runtime system was in place).
Anyway we selected them and run the import. The CMS said it gone well.
After that the activities of the developers were into the Assebly tab queue.
My dubt is that after the import we saw our application working fine on the envirnment indicated as runtime develop system.
I need to clarify if this is the correct behaviour:
A) In this case using only the development runtime system into a track it does not have sense to relase the activities.
The development activity then end at that point and there is nothing else to do into the CMS.
If you need at that point the SCA of your work, to import them elewhere you can find it under the ../Jtrans directory (on condition that you reeased them)
Right?
B) It's an bug of the CMS to allow to run the import from the Consolidation tab while there is no consolidation runtime registered ?
Or it do not represents a real, physical import of software but only a logical step needed to move ahead the sw ?
we suppose when we run the import from the Consolidation tab queue we overwritten again the application on the development runtime system, but I'm not sure of that.

Error While Creating Runtime Systems on an Existing Track in NWDI

Hi,
There is already a track in NWDI with No runtime Systems.
I have to create the RunTime Systems to do development on this track.
When I try to select the Development checkbox in Runtime systems,
select configure without wizard, Gave   Deploy Host name: **********.com
            Deploy Port :50018 (SDM port)
           Deploy PSWD: SDM Pswd
It gives me a warning..
Synchronization of Runtime System triggered for system dev. Log can be found at
http://*****************************LogViewer?LogName=%2Fsapmnt%2FEPQ%2Fglobal%2FTCS%2FLOG%2FEPQ_WHRBD_D2010081322030045.log&Bsname=EPQ_WHRBD_D
When i go to the log file
I see this Error Message
20100813180502 Info   :cannot create a connection for the buildspace: EPQ_WHRBD_D //connect to deploy tool failed:Server <Host Name> did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to <Host name> at port 50018: Connection timed out:could be due to invalid address
Can you please tell me what could be the Reason.
Basis has already opened the Ports : http port and SDM Port.
I am able to ping the server from cmd prompt.
Points will be allocated for the answer.
Thanks.
Venkat

Hi,
There's no need to update CMS or to check whether the buildspace is open, do not click on JSPM flag (unless you need nwdi control at upgrade)...
The error message means only that from the host where you configure the RTS the SDM cannot be reached or logon request cannot be accepted.
This can be either , because the
- SDM password is wrong (you checked it already)
- the port is wrong (you also checked it. If this is really a 700 RTS, i.e. it has SDM, and the instance number is 00, then the port is really 50018, so this should be fine as well. Only mention, because as of 71X we use the P4 port 5<xx>04 for the deploy controller, as there's no more SDM). Still you can use "netstat -a" to see the status of the ports.
- The host is wrong. I agree with Dao, check not only FQDN, but also IP address.
Using this guide you can always check whether the entered data is correct:
http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CMS%29Q0002
Best regards,
Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

ERROR while saving the runtime systems(read time out exception)

Hi e xperts
I am configuring NWDI and assigned asll the permissions and roles to the CMS user.I created Domain,in landscape configurater
created track and saved.
while saving the rumtime systems the error thrown is
com.sap.cms.util.exception.conf.CMSCCBSCommunicationException: CBS (URL http://dtlepdev:54400/tc.CBS.Appl/archiveapi2/) communication exception: Read timed out (Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.removeBuildspace(CBSConfCommunicator.java:382)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.deleteCreateBuildspace(CBSConfCommunicator.java:338)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.editBuildspace(CBSConfCommunicator.java:277)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.createBuildspace(CBSConfCommunicator.java:168)
at com.sap.cms.pcs.conf.core.services.SystemManagerObject.saveSystem(SystemManagerObject.java:261)
at com.sap.cms.pcs.conf.core.plugin.DefaultTrack.newTrack(DefaultTrack.java:292)
at com.sap.cms.pcs.conf.core.TrackManager.editTrack(TrackManager.java:208)
at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:1002)
at com.sap.cms.pcs.conf.manager.proxy.CmsConfProxyBean.editTrackConfiguration(CmsConfProxyBean.java:489)
at com.sap.cms.pcs.conf.manager.proxy.LocalCmsConfProxyLocalObjectImpl0_0.editTrackConfigurationand also ..
Unable to instantiate a Build Space administrator!
Build Space "DTL_ETRACK_C" [bsID: 27, version: 0] [in-queue: on (privileged), out-queue: "on", processing: off]
<null>
[EXCEPTION]
Buildspace DTL_ETRACK_C does not own the workspace ws/ETRACK/dtl.com_DEFAULTIME/cons/inactive/ . It is currently not owned by any other buildspace
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.checkWorkspace(_BuildSpaceValidator.java:120)
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.validateWSs(_BuildSpaceValidator.java:74)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.validate(BSAdmin.java:192)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.updateState(BSAdmin.java:260)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.determineChanges(BSAdminOrc.java:439)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.validateBuildSpaceData(BSAdminOrc.java:219)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.act(BSAdminOrc.java:341)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:534
In cbs i checked the parametrs they are open and on..
please suggest me on this ASAP..since 2 days i have been struggling and searched in forums..no perfect solution
help me out
perfect soln is immediately awarded...
I
THanks
Mayu

Hi Mayu,
here apparently the CMS cannot communicate to CBS properly and then when CMS tries to talk to CBS using a webservice, it times out due to various reasons, see below.
Strange, I always had this error when the CMS was on a different release like CBS and this caused the communication problem.
Don't you have an entry in your cms log like this?
com.sap.cms.util.exception.CMSUnexpectedException
at com.sap.cms.pcs.conf.manager.CmsConfManager.newTrackConfiguration(CmsConfManager.java:666)
Caused by: java.lang.IncompatibleClassChangeError
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.openConnection(CBSConfCommunicator.java:84)
Please provide me the version of the DI_CMS, DI_CBS (and DI_DTR for the sake of completeness).
You can find this info on the ComponentInfo page.
On 640/700 this is http://<host>:<port>/sap/monitoring/ComponentInfo
as of 710 you find this on the "Components" tab of http://<host>:<port>/nwa/sysinfo
I also think that this is not due to the runtime systems. I guess you have the same problem if you try to create the track without runtime systems, right?
(The "Unable to instantiate a Build Space administrator!" is not necessarily an error, see the note:
#1175019 - Unable to instantiate a Build Space administrator!)
Thank you!
Best Regards,
Ervin

NWDI does not reach runtime systems ... sometimes

Hi all,
we have a strange problem with our new NWDI (7.40 SP5). Globally the NWDI works fine. Until now we have migrated 60 of our 180 tracks to the new environment and beside some smaller errors everything works fine.
Now the first track users try to deploy their developments to the runtime systems. Until now there are about 30 runtime systems connected, from 7.00 up to 7.40 systems. 7.00 systems work fine, all above it is a question of luck whether a deployment/import works or not.
The error message (severity = fatal) is always the same:
Exc=com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'DeployerNWDI' could not be connected to the specified host 'xxx' and port '5xxx4'
At the same time there are these four error messages at the logfiles:
1. Import failed
2. User cannot connect (the one above)
3. User cannot connect with stacktrace
4. Connection lost (the one below)
I have written a small WebDynpro-application at the NWDI-server which tries to open a connection to the runtime systems at a specific port and it is always OK (no firewall problem). I have tried to connect to the runtime systems with the connection user and it is OK too.
What we have figured out so far is that the application server has a problem in its default configuration when the OS has several network adapters and thus several IP addresses. This problem is solved already (there is a SAP note for that). Also we have increased the maximum number of connection the server is able to keep open at the same time.
The strangest part is that it works sometimes if you hit import just a second time after a failed import ...
Does anyone knows the problem or even better a solution? Thanks in advance!
Here is the full stacktrace:
Could not establish connection to AS Java on [P4://xxx:5xxx4]. Connection lost. Check if the host and port specified are correct and AS Java is up and running.
[EXCEPTION]
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.<init>(SessionImpl.java:150)
at com.sap.engine.services.dc.api.session.impl.SessionFactoryImpl.newSession(SessionFactoryImpl.java:36)
at com.sap.engine.services.dc.api.impl.ClientFactoryImpl.createClient(ClientFactoryImpl.java:127)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.getDeployControllerClient(P4APIClientSessionImpl.java:166)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.initClient(P4APIClientSessionImpl.java:137)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.<init>(P4APIClientSessionImpl.java:60)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.newInstance(P4APIClientSessionImpl.java:47)
at com.sap.sdm.apiimpl.remote.client.APIClientSessionFactoryImpl.createAPIClientSession(APIClientSessionFactoryImpl.java:53)
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.sdm.api.remote.ClientSessionFactory.createRemoteClientSession(ClientSessionFactory.java:299)
at com.sap.sdm.api.remote.ClientSessionFactory.createRemoteClientSession(ClientSessionFactory.java:249)
at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:148)
at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:188)
at sun.reflect.GeneratedMethodAccessor1040.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy407.performDirectDeployment(Unknown Source)
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.engine.services.rmi_p4.reflect.LocalInvocationHandler.invokeInternal(LocalInvocationHandler.java:101)
at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)
at com.sun.proxy.$Proxy412.performDirectDeployment(Unknown Source)
at sun.reflect.GeneratedMethodAccessor1039.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)
at com.sun.proxy.$Proxy413.performDirectDeployment(Unknown Source)
at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:292)
at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:356)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:448)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:175)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:499)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:112)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:638)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:610)
at sun.reflect.GeneratedMethodAccessor690.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy514.startImport(Unknown Source)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1760)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2809)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1158)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2856)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:367)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:490)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
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.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.security.login.RemoteLoginContextFactoryImpl.getRemoteLoginContext(RemoteLoginContextFactoryImpl.java:95)
at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:114)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:312)
... 163 more
Caused by: java.io.IOException: Reading reply for initial call failed. Check remote side state
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.resolveInitialReference(P4ObjectBrokerServerImpl.java:1486)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 166 more
Caused by: com.sap.engine.services.rmi_p4.exception.P4BaseConnectionException: Connection lost
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:1320)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:1309)
at com.sap.engine.services.rmi_p4.P4Call.fail(P4Call.java:143)
at com.sap.engine.services.cross.fca.ConnectionImpl.notifyCalls(ConnectionImpl.java:150)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.notifyConnectionClosed(FCAConnectorImpl.java:253)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.clientConnectionClosed(FCAConnectorImpl.java:238)
at com.sap.engine.services.cross.fca.SystemMessageProcessor.parseMessage(SystemMessageProcessor.java:94)
at com.sap.engine.services.cross.fca.SystemMessage.process(SystemMessage.java:22)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
... 3 more

Hi Richard,
could you please check whether this note helps?
1492974 - Deployment to a AS Java does not work
Regards,
Ervin

Error creating runtime systems in the track

Hi "NWDI gurus",
we are facing a typical problem. We have cretaed a track, assigned development runtime system initially and had carried on out development successfully. Now we wanted to add test system to our environment(track) and start transporting stuff to test system. When we enetered the SDM host name port and password and said "View/Edit Deployment Substitution Variables" we are getting the following error in our landscape.
"Server nnnnn did not accept login request as "admin" on port 50118. Details"
We use administrator user id to log on to SDM, we have admin user but that refers to network administrator in our LDAP system.
My concern is we were not using "the admin" user in dev and we were successful in our development and deployment and when we came to QA it is giving this error.
Any ideas how to solve this error.
Does admin here refer to the admin user in specific or is it a generic term to even mean the "administrator" user configured in the runtime syste,
Please advise
regards
sam
Message was edited by:
sameer chilama
Message was edited by:
sameer chilama

Hi Sameer,
Could you please tell me the solution of the issue as i am facing the same issue.
Thanks,
Anumit

Cannot Create Runtime Systems in Landscape Configurator

Hi All,
I'm not able to save runtime system information. When i do 'Save' or 'Save and Restore' I get the following error or trace.
communication error: Error during servlet communication / configuartion failed: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE TCSMessage SYSTEM "http://blrkec84192d:50100/TCS/TCSDeployServlet.dtd"> <TCSMessage> <message> <exception> Unexpected error: I/O operation failed : java.lang.ClassNotFoundException: com.sap.engine.lib.xml.parser.helpers.CharArray Found in negative cache -
Loader Info -
ClassLoader name: [sap.com/tcSLCMSTCSEar] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization library:com.sap.tc.Logging library:tc_SL_SDM_Client library:tc.CBS.API library:tcdtr.clientvfs-adl library:tcCBSComponentLibrary library:tc.httpclient library:tc_SL_SDM_Util library:tcSLCMSUtil library:tcSLUTIL library:com.sap.util.monitor.jarm library:com.sap.util.monitor.grmg library:tcjmx service:tcsecsecurestorageservice library:com.sap.aii.util.misc library:com.sap.aii.util.rb library:com.sap.aii.ibtransportclient library:com.sap.aii.util.xml Resources: E:\usr\sap\IN1\JC01\j2ee\cluster\server0\apps\sap.com\tcSLCMSTCSEar\sap.comtcSLCMSTCSimpl.jar E:\usr\sap\IN1\JC01\j2ee\cluster\server0\apps\sap.com\tcSLCMSTCSEar\EJBContainer\clientjars\clientsap.comtcSLCMStcsbeans.jar E:\usr\sap\IN1\JC01\j2ee\cluster\server0\apps\sap.com\tcSLCMSTCSEar\servlet_jsp\TCS\root\WEB-INF\classes E:\usr\sap\IN1\JC01\j2ee\cluster\server0\apps\sap.com\tcSLCMSTCSEar\servlet_jsp\TCS\work E:\usr\sap\IN1\JC01\j2ee\cluster\server0\apps\sap.com\tcSLCMSTCSEar\EJBContainer\applicationjars\sap.comtcSLCMStcsbeans.jar Loading model: {parent,references,local} -
Any pointers in resolving this issue.
Thanks
Srikant

A server restart should help!
Thanks,
Rajit S

Which runtime systems do i need to configure in CMS

Hi,
We have development,Test,Production systems in the system landscape.
So What runtime systems do i need to configure in CMS
I am assuming it should be
Development-Development
Consolidation-Test
Test-?
Production-Production
Which runtime system do i need to configure for test system in my landscape(is it consolidation or test).what exactly is the role of consolidation runtime system.is it mandatory to configure that runtime system
Points will be rewarded for the helpful answer

HI Bala,
configure system as
Development-Development
Consolidation- if you dont have server then dont configure it.
Test-Test
Production-Production
NWDI upto consolidation is driven by activities. and assembly to production is driven by SCA. i.e complete software packaging
as Test server means where you can test your complete application.That means you need to deploy whole application as a sca file.
and in NWDI sca file is generated after assembly.
consolidation is only for verifying you changes before packaging you application. it can't be a test server.

Broken DCs after changing the runtime systems in track

Hello,
I am making some WebDynpro changes to ESS using NWDI and NWDS. All was working fine until I changed the runtime systems in the track. Eversince I added the test runtime system in the track, I am getting broken DC errors in sap.com_SAP_ESS_1 compartment. When I looked at the details in CBS, it says that Used Component "tc/bi/bp/pcd" not found. I looked at the compartment sap.com_SAP_BUILDT_1 and this DC is not available in that. When I did sync used DCs in NWDS, I am getting the error "ERROR: Check for used DCs failed: Used component not found: sap.com/tc/bi/bp/pcd. DC not found in DC syncdb." . I performed restore system state and reimported all the required .sca files in to the track. I am still having this problem even after reimport.
Any help is appreciated.
Thanks,
Srihari

Hi Krishna and Snehal,
Thanks for your responses. I have done some more research and found out that the missing DC is available in EP_BUILDT SCA file. I have downloaded sca file for EP_BUILDT from market place and placed it in CMS inbox. I also deployed the .sca file in NWDI system. In CMS, I can not see this .sca file of EP_BUILDT in the check-In tab. I tried to add it as dependency to SAP_ESS SC in Landscape Navigator. But, EP_BUILDT is not available in the list of SWCV when I click on "Define Dependencies". I checked SLD and found out that it is not in the list of SWCV, but is there in "Installed Products" tab of NWDI technical system. Any idea on how to get it as SWCV in SLD or how to get the .sca file in to my "Check-In" tab of track? Please share your thoughts.
Thanks,
Srihari

Track Connections to support Multiple QA & Production Runtime Systems

Hi,
I've read the SAP Help and various other threads in this forum that describe how to configure track connections that will support deployment into multiple production runtime systems. Can the track design therefore support the following scenario :-
Dev --> Consolidation ---> Multiple Pre-Production Runtime Systems --> Multiple Production Runtime Systems.
If this scenario can be implemented in the NWDI Landscape Configurator what would be the best approach to define this ?.
The reason I'm asking is our customer is planning multiple Portals in Production & Pre-Production due to the number of LDAP's currently being used to roll-out to the full user community.
Regards,
Brian.

Hi Kiran,
May be this thread will come in handy. I explained clearly the procedure to deploy to multiple systems
transport to mulitple systems
thanks

Configuring Runtime systems for a Track

Hello Experts,
I am new to the NWDI administration,here am having some quries for configuring Track related data.
We are using NWDI 7.0 SP18 having local SLD with both roles as landscape and Name server.
We have a requirement to build a new .SCA for MDM-EP perspective.So,we have created a new SC in SLD and created the domain and track for the newly created SC in CMS.
When we are initially creating a track for newly created SC,we selected runtime systems as DEV,Test and production.
Here we have one consolidated tab,where it will integrate all the changes in WS-CONS when we imported the requests.But here what kind of system details we need to provide for consolidation,Because we have already identified 3 sepate systems for DEV,QAS(TEST) and PROD.is it necessary to identify a separate system for consolidation?or is it a simply root path for DEV-to-QAS.
2.For developing with Track,we need to provide the Component Build Service (CBS) with the environment for building the components by importing required .SCA's(SAP-JEE,SAP_BUILDT,SAP_JTECHS).We have imported these SCA's in to DEV before using the track by DEV team.After that these components are added to consolidate tab as well.So,do we need to import all the standard .SCA's in to all the runtime systems for this track?(Pls.Note that all Runtime systems are at same NW 7.0 SP18 level).
Please provide your valuable suggestions to make myself understand this Java transport concepts clearly.
Thanks in Advance..
Regards,
Sanam.

Hi,
Thanks for your clarification.Now we are facing an issue related to broken DC's once we imported the relased requests in to Consolidation phase.
Our developer activated and released 2 change requests.Once it got released it will automatically comes to the consolidation after successful build and autoimport in DEV system.we have tried to import the change requests in to the consolidation(No physical run time system is assigned to the consolidation)---In this phase if you import the chage requests in to consolidation phase:
Repisitory-Import is finished successfully
CBS-Make:identified the broken DC's after CBS Build process
SDM-Deployment Notication:No deployment,because no runtime system is defined.got finished successfully.
So,the DC's got broken during CBS Build phase.After some analysis,we identified the dependency SCA's got missed out in Consolidation.So,we imported the required SCA Components again in to the consolidation for build purpose.Here we again tried by adding those relased change requests to the consolidation queue and imported again.But still,the CBS Build identifying the Broken DC's.Our development SCA has the dependency software components as (SAP_EU,SAP_BUILDT,SAP_JEE,SAP_JTECHS).Thse components are successfully imported in to DEV and can able to see it from NWDS.The same components are imported successfully in to the consolidation as well,but from out 4 components we can able to see only 3 components except SAP_EU in NWDS.
1.So,is that causing any Build problem for my relased change requestes?If yes,why it was missing in consolidation(re-imported twice for SAP_EU).
2.we tried importing the released CR's without checking dependecies are available for consolidation.Is that causing my DC's broken for build phase?
Please suggest your ideas,how can i make my CBS-Build process OK for relased requests.

Change runtime systems in a track

Hello,
We had a track in which we had configured CONS as our QA system....and we moved all changes to PROD(which were definitely Assembled)....now they were some new changes which were done after this which were imported into CONS and deployed to QA and were tested(which were not Assembled)......then we made TEST to point to our QA system.....now the changes which are not Assembled are not working in QA.....and all the previous changes which were Assembled and moved to PROD are working in QA.....
So do we need to Assemble the latter changes although they were already deployed to QA when it was pointing to CONS Runtime System...
Regards,
Shikhil

The question is that 'do we need to Assemble and Import the changes which were made after changing the runtime system' although they were already deployed to QA when CONS was pointing to it...
Regards,
Shikhil

Upgrade Runtime Systems create new Tracks?

Hi all,
we are in the situation, that our Runtime Systems will upgrade from NW04 to NW04s. Cause we have ongoing development, we can not upgrade existing tracks itself, while the release change will last several weeks (D,Q and P). The idea was, to create new Tracks for new release and reimport SCs from assembly step of old release.
So we defined Products and Software Components in SLD with new Version Number, with the dependencies for the new versions.
Created new Tracks in CMS, Imported all SCA and made required changes. So far so good.
Unfortunatly in Assembly Step of new Track i`m not able anymore to Change Patch Level and Support Package Stack, only the "keep current" option is available.
Thanks for any help
Regards Oliver

Hello NWDI Users,
i followed thee guide here: https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5834. [original link is broken] [original link is broken] [original link is broken]
The Problem still exists. In Track of new release (NW7.0) i`m not able to increase the
Support Package Number nor Patch Level.
So software versioning is diabled in 7.0??
Regards Oliver

Un able create runtime systems in CMS - landscape configrator

Hi All,
when i am trying to create track in that runtime system i am receving following error
CBS (URL http://<host>:58000/tc.CBS.Appl/archiveapi2/) authorization exception: User not authorized to log into build server. ( Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://<host>:58000/CBSWebService/CBSHttpSOAP?style=rpc" )
i have added ll the rolls to this user still i am receving above authorisation error
please suggest if i need to add any addtion roles to create run time systems
Samrat

we have applied note 896427
issue got resolved

Is it possible to define a Runtime System after the SC has been approved?

Hello,
I have created a Track for a certain SC called TestSC.
When I did that, I defined only our development server as a Runtime System and imported the relevant SCs (SAP_BUILDT, SAP_JTECHS, SAP-JEE) only to this server.
Now, the TestSC has been developed, assembled and approved.
Is it possible, at this stage, to define the production server and import the TestSC to it?
The reason I am asking this is because at SAP tutorials you need to define these Runtime Systems in advance and import the relevant SCs (SAP_BUILDT, SAP_JTECHS, SAP-JEE) to each one of them before the actual development starts. If I will define the production server now, will I still need to import these SCs to the production server or only the TestSC I have created?
Thank you in advance,
Roy

Hi Roy,
for the systems DEV and CONS, you always have to import them, as without you won't be able to do development.
For TEST and PROD, there are at the moment no technical reasons for the import of these SCAs. But the CMS doesn't make a difference between SCAs that do not have to be deployed and the ones that have to be deployed (e.g. when you are working with external libraries that come in separate SCAs). The CMS transports all SCA that are checked-in and decides while the import what it has to do with the certain SCA (what can be three steps in DEV/CONS: import, build, deploy, while in TEST/PROD it's only deploy). This can also lead to the situation that no action is performed in a certain stage.
Perhaps there will be a version check implemented in later SPs, so that you will receive a message when trying to import SCAs from another SP level than your runtime system. Then it is mandatory to check this also in TEST and PROD.
Best regards,
Timo

Runtime systems

Similar Messages

Maybe you are looking for