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.

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 logging into runtime user

My coworker recently added a new windows agent that is on a different domain than her Tidal master and is getting the error
*** Error logging into runtime user when she tries to run a job through Tidal.
She verified that the runtime user has the proper rights on the agent server, she logged onto the agent as the runtime user and ran the script from the job manually and it ran successfully.
Is there a known problem with using a runtime user that was created in domainA but trying to run a job on an agent server in domainB?
Thanks

It turns out that the problem was with the userid the agent service was running under. She changed the service to run with the Local System credentials and the problem was solved.

Strange Behaviour into Runtime Workbench

Hi all,
I have a question for us.
Into our system PI 7.1 we have a strange behaviour in Runtime Workbench - Message Monitoring.
When I choose for the fiel "FROM" the value "Database" I obtain the list of software component that I find the value "Integration Server".
But when I choose the value "Database (Overview)" the value "Integration Server" into list of software component doesn't exist.
Why Do the system have this behaviour?
best regards,
Davide Bruno

Hey,
The old way of seeing msg use - the db option... In Pi 71 the db overiew options gives you an aggregated view of ur messages. this is very helpful in tracking repeated failures, anylysing the types of failures etc...The "strange" view is actually a pretty neat tool... We used to do this in excel sheets after dowloading the report from sxmb_moni..
regards,
Arvind R

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

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

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.

Maximum number of runtime systems

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 . My question is how may maximum runtime systems , I can have ( from NWDI there are 4 visible like ) . For eg : If I wanted to include SAndbox and training landscape , totally there will be file landscape . Will NWDI support more that 4 landscape to add as runtime systems in a track ? Is there any mechanism to do this ?
Aneez

you can get some documentation from the sap library, e.g.:
http://help.sap.com/saphelp_nw04/helpdata/de/13/602b27f6fb41b4a9eb4f72eabb9832/frameset.htm
This is the Netweaver 2004 documentation, in case you use NW 2004s just type "track connection" into the search field and you'll find a similar chapter for NW 2004s.
Regards,
Cornelia

How to deploy the application into Test system in NWDI

Hi ,all
i hava some problems about NWDI, Could you help me ?
I hava defined the test system in runtime system of NWDI .
As a general ,it must be deploy the application into test system for test before transport the CR, is it right?
if so , how can i do to deploy the application into test system before assembly?
regards.

Hi Zhijun,
Thank you for your repay.
You are welcome
After assembly , can i deploy the application into test system by CMS? mean that if it can be done not through CR?
Yes, you import the changes on the "Test" tab of the transport studio of the CMS webui. This will deploy the changes to Test (to the system you have specified in the runtime system configuration for this track)
and what is the benefit of Dev system and Con system
See the guide: http://help.sap.com/saphelp_nw70/helpdata/en/b6/e6b9fc9ec00f4ca4a0d3e0645e87b5/frameset.htm
Best Regards,
Ervin

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

Couldn't log into SAP System (message 00264) after SAP_BASIS update

Hello,
we performed SAP_BASIS update to SAPKB70023 and get a problem with logon into a SAP system with message 00264 (Status &2 of the user interface &1 missing).
We have a 64-bit non-Unicode system on Solaris/SPARC/Oracle and Kernel level 333.
We tried to import MENUSYST program from note 1285869, but nothing happened at all. The parameter abap/unicode_check we set to "on" but this didn't help us.
So after selecting system record in SAP Logon now we get the initial logon screen with no "new password" button and error 00264 (Status 0020 of the user interface SAPMSYST missing.) and couldn't log into the system.
We have no idea why correct and existing statuses are not working.
Please suggest us what to do to fix this problem.
Thanks in advance!

Check this,
http://forums.sdn.sap.com/thread.jspa?threadID=835278
it may be useful.
Regards,
Ravi

NWDS - autodeploy into runtime systems

Similar Messages

Maybe you are looking for