I would like to know what is DEV and CONS configuration files in during import of the configuration file.
And i am also not clear that what is the role of central development system in the Track, as every Developer is having his on local WAS on his machine. Developer can test all his developments on local machine.
What is the diffrence between development and consolidation system in the Track? Why to invest on define two diffrent system?
Dev (Dovelopment)is the workspace for all dovelopment for your project,where as Con (Consolidation) is the one you will place the tested code (the final one) to consolidate the code.
We are thinking to implement complete JDI environment.
So i was intrested in knowing why two seprate box are needed. can't we merge the funtionality of the Development system and the Consolidation system.
or we were thing to make the WAS engine on the administrator's workspace the consolidation system.
and from the document i knew that DEV workspace is the workspace where developers work and CONS is the wokspace where the administrator works. (here i think we can say team lead or project manager). when the developer activates the change the change is moved to CONS workspace.
You don't require two separate boxes, rather you need two workspaces.
if you see JDI Architecture
Developer creates projects in dovlopment space(You can have J2ee locally for testing locally) so many dovelopers will there. where as Administrator will create a product where CBD and CMS comes in to picture here all consolidated code from all developers will be integrated tested (combined one).this final code will be moved to CoN workspace and product version will be released.I hope you got cleared.
Please go through ACL's who can do what,naturally evrybody can't do everthing,Naturally all consolidation and production is done by Sys Admin/Project manger. So he will have his own autority,Doveloper will have his workspace intercommunication tales place in bwtween DC's each Dev will have saparate Box,
but i want to know that the two Runtime system ( Development and Consolidation) that we configure in Track (CMS) can that be same.
what is the benefit of keeping two seprate Runtime system for Development and Consolidation. Can't we have something like SAP R/3(development, testing and production) and both developer and administrator can test their workspace on Same Runtime System.
The development and consolidation workspaces will be in the same system physically (you dont need two systems just for storing workspace) but deployment to the development system will happen from development workspace and deployment into the test system will happen from consolidation workspace
I want to know that the two Runtime system ( Development and Consolidation) that we configure in Track (CMS) can those be same.
Can't we have something like in SAP R/3 (development, testing and production) and both developer and administrator can test their workspace on Same Runtime System which in this case in development.
what is the benefit of keeping two seprate Runtime system for Development and Consolidation in JDI landscape.
Yes you can have the runtime test system, same as the consolidation system. The runtime test system is usually used to mirror production sized data , typically used for load testing and most other testing that is done on the consolidation. For complex scenarios such as distributed development its better to have a consolidation system . For simple scenarios it can be eliminated.
You do not have to define runtime systems at all: Each runtime system is optional. This means that you can even have a track without runtime systems. However, in such a case you will have to deploy the software you are building by hand then, using SDM on the target system. You might do this if you want to deploy to multiple non-clustered systems that represent the same stage. (This might be the case in global solutions where you want to put the systems that run the software as close as possible to the endusers for performance reasons).
From my point of view you will hardly ever use the Development runtime system, since developers can deploy to their Development system from the NWDS.
In case you have multiple separated development teams (working on different SC's in the same Development Track) it is advisable though to setup and define a Consolidation runtime system to check that all the code that these teams create works with eachother (integration testing). Each team will probably have their own Development system for testing their own code in an isolated environment. Since they use the same track but different runtime systems for testing their code, you simply cannot define a Development runtime system for the track.
You use the Test system for QA and user acceptance testing.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.