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.

Similar Messages

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

  • Two Tracks for the same Runtime System?

    Hello,
    can you please tell me if it is allowed to connect two tracks to the same runtime systems?
    We have already a track connected to our systems. Now we have created a new track to deliver different content to those systems. We wanted to connect the new track to the same runtime systems. Our basis team told me that a where-used message came up that told them "The following runtime systems are already used elsewhere in the CMS domain".
    Can you tell us if we will get problems because of this?
    Thanks in advance,
    Br,
      Michael

    Hello again,
    ok now, thats something completely different CRM modification is always special.
    To be honest i cannot tell for sure what will happen. As far as i know the default deploy strategy of NWDI is "deploy any version" which means NWDI will order SDM to just deploy not regarding any SDM Version (you are on a 7.0x System right?)
    So it should be possible if everything else, excelt those 2 DCs is the same things should work. But if not the last deplyoed version of the shared DCS will be active. Which might lead to problems then.
    As far as you described, the setup is as the CRM modification guides mentioned.
    My first thought is that you are not forced to use CUSTCRMPRJ as SC name for the projects as far as I know. OS maybe the leanest thing would be to just use CUSTCRMPRJ_light (.o)) for the second track.
    Hmmm not sure if this is a good idea or thought to the end. I don't have the CRM modifications guide at hand at the moment. But I guess there was a part where something was mentioned similar to this.
    After all I have to say:Sorry. I can't give you solid, reliable tip/advice for this case. Maybe my thought will help you.
    Or maybe someone else knows better.
    Have a good time
    Jan

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

  • 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

  • Error in configuring Runtime systems

    When we try to create a development runtime system using Landscape Configurator we are getting an error.After providing SDM Host,Port number and password when we click 'Save' it is throwing this error
    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} -
    : </exception> </message> </TCSMessage>
    Any idea what might have gone wrong?
    Regards,
    Shabeer

    Hi Shobhan
    I'm too facing similar problem as when i try saving the runtime systems similar error comes.
    For your insight to my problem:
    1. Is this first time you are creating a track ? --> Yeah track is getting created for first time.
    2. Have you created Product and SC with all 3 required dependencies ? --> Only in SC that dependencies have been created and not product. will that matter here.
    3. Have host file entries for all runtime systems is made in NWDI server ? ---> where do i look for this?
    Thanks
    Srikant

  • It will not open Mozilla at all, it comes up with a problem box, which states on the first line: Access denied to system because of URL Filter Configuration.

    Problem Report -
    Access denied to system because of URL Filter Configuration.
    Message ID -
    FILTER_DENIED
    Problem Description -
    Your system was configured to deny access to the requested URL.
    Possible Problem Cause -
    Request denied, as specified in the local filter list configuration.
    Possible Solution -
    Contact your network support team if this problem persists.
    It comes up with thie above in a box with two colums. i can only usse internet explorer now.

    Does any body know how to fix it?
    I just got off the phone to my new isp and they said they could not help me at all.

  • 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

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

  • 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

  • Adding Runtime systems later

    ALL,
    We plan to do some modification of Xss components using NWDI based on NW04s SR1 . We have already installed NWDI , created the tracks etc .We also have a three tier landscape consisting of Dev, QA and Prod .I am giving below my concerns
    We have now installed and configured development landscape only .QA and Prod  is in the progress .So in the runtime system of track , I have only added the parameters of DEV landscape .
    Can I start the development now in NWDI and later add the QA and PROD as runtime systems ? Is this a bad practice or what is the impact of adding runtime systems later ?
    Aneez

    This is no problem at all.
    The only impact this has is that new Development Configurations will be created once you add the new runtime systems and the developers need to reimport the configurations in NWDS. It is wise to make sure that there are no open activities when you're adding the new runtime systems, just to make sure that nothing gets lost/stuck.

  • 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

  • NWDS - autodeploy into runtime systems

    Hello,
    we have an NWDI on NW04s SP13 with a track. Several developers have their own NWDS with each thier own J2EE. The developers are created on the NWDI. I have configured for the DEV_RUNTIME system automatic deployment.
    The developers told me, that they need the sdm password for the DEV_RUNTIME system. Could you please explain me, if this is true? I thougth a user and pw from the NWDI would be all what they need.
    Regards,
    Alexander

    The developers should only need the SDM password for their local J2EE Engines. Deployment to the Dev runtime system of the track is done by NWDI using the SDM password provided in the runtime system definition.
    In order to deploy changes to the Dev runtime system, developers must Check-In and Activate their activities. An activation triggers a central build by CBS and if this build is successful, it triggers deployment to the Dev runtime system.

  • NWDI Track - Runtime Systems options

    Hello All,
    We are implementing Manager Self Service (MSS) in our company. (Webdynpro Java XSS 600)
    We have Development (DEV) , Test (TST) and Production (PRD) systems in our landscape. (EP 7.0 SP 13)
    We have installed and configured NWDI and created a track for the development on MSS.
    In my track, I have the option of selecting upto 4 runtime systems.
    I have a few questions about selecting the runtime system options in my track in our scenario:
    1. Can I skip consolidation system in my track (no entry for runtime system consolidation in the Runtime Systems tab of the
    Track Data page under Landscape Configurator). (OR) is it mandatory to have consolidation system defined?
    2. In my track, If I use Development - DEV, Consolidation - TST, and Production - PRD are there any disadvantages with this
    configuration. In this case, after the assembly of all the components in the track, the assembled components are
    deployed directly on the Production Server (which I think might be a risk). Please suggest if we would have any other
    problems with this configuration.
    3. Can I define both Development and Consolidation systems in my track to be "DEV"- and then Test would be "TST"
    and Production would be "PRD". Would there be any complications with this scenario ?
    Please suggest the best practise of defining the runtime systems in a track - in our scenario.
    Thanks,
    Jaya

    Hi
    I would recommend that you use your test/QA system as the runtime for "test" runtime - this way you get a chance to test out the assembled applications prior to putting them into your production system.
    In our landscape we have no runtime for dev, use our development portal as our Consolidation runtime.  The developers have local java engines that they can test their development on and therefore not impact on the true development system (therefore avoiding disruption to testing)
    We have only recently started using MSS & ESS as such we will be installing local Portals for the developers to use and keep our development model the same.
    regards
    marina

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

Maybe you are looking for