Sync DCs from production to NWDI track

[former_member188073]

Hello Dear team,

I have a three system landscape of WAS java on NW 7.0 SP 14. All this while development had taken place by developers directly from NWDS itself. Now our clients want to move to NWDI.

I have created tracks and prepared runtime systems as well. Now I am facing issues moving new modifications through track.. It shows issues in several other DCs.

How do I sync my production or dev with my track/DTR.

Regards,

BVarun

Edited by: Varun Biswas on Apr 16, 2011 10:08 AM

[shreyas_pandya · Accepted solution]

Hi Varun,

To migrate from a classical way of Local Development Environment to a Centralized NWDI environment for all the projects in your landscape is almost like bringing the revolution for your Java development scenario.

It will require lot of efforts and time.

Please understand the below mentioned important points that will help you for migration.

1) In SLD you have created the products and SCs for your custom developed projects.

2) in SLD you have also defined the build-time dependecies for your SC and is ready to be added into a track.

3) In CMS Web UI, You have updated the CMS.

4) In CMS Web UI, You have created your Track with the SC defined in it and runtime systems are also configured in it.

5) In CMS Web UI, You have also imported the Components into Develpoment and Consolidation buildspaces too.

6) You have imported the developement configuration into Developer Studio and have coppied all your Local Development projects into the Track SC which you have imported.

If you need the more detailed & step-by step version of the above points then feel free to ask.

One more important thing you need to see forward is....

When you migrate all your projects to NWDI Tracks then, it becomes unavoidable to deploy all your projects into your production system again. you cannot escape this part.

Explanation:

This is because, during migration all your DCs will be inside activities that will be checked-In to DTR-Server that means your entire source code will be copied to DTR-Server.

Then as a standard procedure it is followed by operations such as Activation, Release, importing into Consolidation & Finally Assembling Components into a SCA file.

This very SCA will be transported to production system containing your latest source code.

This is kind of a risky in the cases where you are not sure of whether the source code that you are copying inside a track is latest or not, because in many organizations there are projects that may be running for more than 3 years. in such cases one should be extra careful and must be sure that the code being migrate to NWDI-track is the latest working code. As the same source code is going to be deployed into the production system ultimately.

I hope you have a clear picture now, please feel free to revert in case if you have any doubts.

Regards,

Shreyas Pandya.

Regards,

Shreyas Pandya

[former_member188073 · Accepted solution]

Hello Shreyas,

Foreseeing this probability, I had asked the developers to take source codes from DTR only. The DTR is updated and all changes are made in the DTR only. The only they are deployed on the DEV. QA and PRD systems.. Now we are mending all DCs one by one. Lets see if this works. It is indeed taking a lot of time

We are checking in and checking out complete DCs and moving activities. Now we are facing issues with particular DCs and are going about the repair as and when they come.

I was hoping for a more standard way, but I guess is the only method.

One thought I am having of reducing the efforts, is by taking the DCs chronologically, I mean the order in which they were changed and touch. Can this work, because now every thing is failing in assembly due to some other DC

Regards,

Varun Biswas

[former_member188073 · Accepted solution]

Hello Shreyas,

Thanks for the details view point that you had provided. My team and me had long discussions for many sessions. We are keen and ambitious to go with it. The simple reason being that there is so much of customization already pushed to production manually that it has become painstakingly important to bring the process back to NWDI tracks.

This reply hence took sometime to come.

The strategy we are following is checking in and out every files in DCs one by one which ever is caught with errors in deployment in the quality. But now finally the truck has stopped with java.lang.OutOfMemoryError. Notes [879377|https://service.sap.com/sap/support/notes/879377] and [0001264514|https://service.sap.com/sap/support/notes/0001264514?nlang=E] asked change in JVM parameter for SDM. Did it, increased same to 512 MB. But still the deployments on quality is going "OutOfMemory".

I am posting the log in the next post as the format is really clumsy. Kindly search for OutOfMemory

[former_member188073 · Accepted solution]

30 19:08:19 - Deploy Service status:

Info:11/04/30 19:08:19 - Application : mycompany.com/DC_ReportDrawingMTO_EAR

Info:11/04/30 19:08:19 -

Info:11/04/30 19:08:19 - DrawingMTO_Bean - EJB

Info:11/04/30 19:08:19 - WEB SERVICE PORTS:

Info: /ReportsDrawingMTOSrvc/ReportsDrawingMTOSrvc

Info: - WEBSERVICES

Info:11/04/30 19:08:19 - ReportsDrawingMTOSrvc/ReportsDrawingMTOSrvc - WEB

Info:11/04/30 19:08:19 - mycompany.com/DC_ReportDrawingMTO_EAR - METAMODELREPOSITORY

Info:11/04/30 19:08:19 - ***********************************************************

Info:Apr 30, 2011 7:08:19 PM Info: End of log messages of the target system.

Info:Apr 30, 2011 7:08:19 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Info:Apr 30, 2011 7:08:19 PM Info: Finished successfully: development component 'DC_ReportDrawingMTO_EAR'/'mycompany.com'/'NWI_MYProduct_C'/'17306'/'9', grouped by

Info:Apr 30, 2011 7:08:19 PM Info: Starting to save the repository

Info:Apr 30, 2011 7:08:20 PM Info: Finished saving the repository

Info:Apr 30, 2011 7:08:20 PM Info: Starting: Update: Selected development component 'DC_ReportFrontAvailability_EAR'/'mycompany.com'/'NWI_MYProduct_C'/'17282'/'9' updates currently deployed development component 'DC_ReportFrontAvailability_EAR'/'mycompany.com'/'NWI_MYProduct_C'/'17282'/'7'.

Info:Apr 30, 2011 7:08:20 PM Info: SDA to be deployed: F:\usr\sap\QAS\JC00\SDM\root\origin\mycompany.com\DC_ReportFrontAvailability_EAR\NWI_MYProduct_C\9\17282\mycompany.com_DC_ReportFrontAvailability_EAR.sda

Info:Apr 30, 2011 7:08:20 PM Info: Software type of SDA: J2EE

Info:Apr 30, 2011 7:08:20 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Info:Apr 30, 2011 7:08:31 PM Info: Begin of log messages of the target system:

Info:11/04/30 19:08:20 - ***********************************************************

Info:11/04/30 19:08:20 - Start updating EAR file...

Info:11/04/30 19:08:20 - start-up mode is lazy

Info:11/04/30 19:08:20 - EAR file updated successfully for 141ms.

Info:11/04/30 19:08:20 - Start updating...

Info:11/04/30 19:08:21 - EAR file uploaded to server for 32ms.

Info:11/04/30 19:08:31 - ERROR: Not updated. Deploy Service returned ERROR:

Info: java.rmi.RemoteException: ERROR : ; nested exception is:

Info: java.lang.OutOfMemoryError

Info: at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:329)

Info: at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)

Info: at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)

Info: at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

Info: at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

Info: at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

Info: at java.security.AccessController.doPrivileged(Native Method)

Info: at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

Info: at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Info: Caused by: java.lang.OutOfMemoryError

Info: For detailed information see the log file of the Deploy Service.

Info:11/04/30 19:08:31 - ***********************************************************

Info:Apr 30, 2011 7:08:31 PM Info: End of log messages of the target system.

Info:Apr 30, 2011 7:08:31 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Info:Apr 30, 2011 7:08:31 PM Error: Aborted: development component 'DC_ReportFrontAvailability_EAR'/'mycompany.com'/'NWI_MYProduct_C'/'17282'/'9', grouped by :

Info:Caught exception during application deployment from SAP J2EE Engine's deploy service:

Info:java.rmi.RemoteException: ERROR : ; nested exception is:

Info: java.lang.OutOfMemoryError

Info: (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Info:Apr 30, 2011 7:08:31 PM Info: Starting to save the repository

Info:Apr 30, 2011 7:08:32 PM Info: Finished saving the repository

Info:Apr 30, 2011 7:08:32 PM Info: Starting: Update: Selected software component 'MYProduct_JAVA'/'mycompany.com'/'NWI_MYProduct_C'/'1000.1.0.4.0.20110414050440''/'7' updates currently deployed software component 'MYProduct_JAVA'/'mycompany.com'/'NWI_MYProduct_C'/'1000.1.0.4.0.20101202134806''/'0'.

Info:Apr 30, 2011 7:08:32 PM Error: Aborted: software component 'MYProduct_JAVA'/'mycompany.com'/'NWI_MYProduct_C'/'1000.1.0.4.0.20110414050440''/'7':

Info:Failed deployment of SDAs:

Info:development component 'DC_ReportFrontAvailability_EAR'/'mycompany.com'/'NWI_MYProduct_C'/'17282'/'9' : aborted

Info:Please, look at error logs above for more information!

Info:Apr 30, 2011 7:08:32 PM Info: Starting to save the repository

Info:Apr 30, 2011 7:08:33 PM Info: Finished saving the repository

Info:Apr 30, 2011 7:08:33 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Info:Apr 30, 2011 7:08:33 PM Error: -

---

At least one of the Deployments failed -

---

Info:end of log received from SDM

Info:RC of deployment: 12

Info:Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2011-04-30 19:15:41.0484 +5:00

[former_member249412]

hello experts,

i am also facing the same issue of outofmemory exception

i was moving my regular activities vai track the assembly phase was completed successfully when i started the import into the quality it failed giving me the error of out of memory exception

the next post gives the CMS log file file where the error cn b seen at the bottom

Edited by: Amar Ghuge on Nov 22, 2011 6:19 AM

[former_member249412]

***********************************************************

Info:11/11/17 13:30:43 - Start updating EAR file...

Info:11/11/17 13:30:43 - start-up mode is lazy

Info:11/11/17 13:30:43 - EAR file updated successfully for 156ms.

Info:11/11/17 13:30:43 - Start updating...

Info:11/11/17 13:30:43 - EAR file uploaded to server for 32ms.

*Info:11/11/17 13:30:55 - ERROR: Not updated. Deploy Service returned ERROR: *

Info: java.rmi.RemoteException: ERROR : nested exception is:

nfo: java.lang.OutOfMemoryError

Info: at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:329)

Info: at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)

Info: at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)*

Info: at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)*

Info: at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

Info: at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

Info: at java.security.AccessController.doPrivileged(Native Method)

Info: at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

Info: at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Info: Caused by: java.lang.OutOfMemoryError

Info: For detailed information see the log file of the Deploy Service.

Info:11/11/17 13:30:55 - ***********************************************************

Info:Nov 17, 2011 1:30:55 PM Info: End of log messages of the target system.

Info:Nov 17, 2011 1:30:55 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Info:Nov 17, 2011 1:30:55 PM Error: Aborted: development component 'DC_PW_SplToolReportEar'/'lntinfotech.com'/'NDI_EALPS_C'/'17392'/'95', grouped by :

Info:Caught exception during application deployment from SAP J2EE Engine's deploy service:

Info:java.rmi.RemoteException: ERROR : ; nested exception is:

Info: java.lang.OutOfMemoryError

Info: (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Info:Nov 17, 2011 1:30:55 PM Info: Starting to save the repository

Info:Nov 17, 2011 1:30:56 PM Info: Finished saving the repository

Info:Nov 17, 2011 1:30:56 PM Info: Starting: Update: Selected software component 'EALPS_JAVA'/'lntinfotech.com'/'NDI_EALPS_C'/'1000.1.0.4.0.20111117051816''/'1' updates currently deployed software component 'EALPS_JAVA'/'lntinfotech.com'/'NDI_EALPS_C'/'1000.1.0.4.0.20111020120854''/'0'.

Info:Nov 17, 2011 1:30:56 PM Error: Aborted: software component 'EALPS_JAVA'/'lntinfotech.com'/'NDI_EALPS_C'/'1000.1.0.4.0.20111117051816''/'1':

Info:Failed deployment of SDAs:

Info:development component 'DC_PW_SplToolReportEar'/'lntinfotech.com'/'NDI_EALPS_C'/'17392'/'95' : aborted

Info:Please, look at error logs above for more information!

Info:Nov 17, 2011 1:30:56 PM Info: Starting to save the repository

Info:Nov 17, 2011 1:30:57 PM Info: Finished saving the repository

Info:Nov 17, 2011 1:30:57 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Info:Nov 17, 2011 1:30:57 PM Error: -

---

At least one of the Deployments failed -

---

Info:end of log received from SDM

Info:RC of deployment: 12

Info:Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2011-11-17 13:36:41.0515 +5:00

[former_member249412]

urgently need solution for the posts kindly help.....

[former_member188073]

Shreyas' suggestions helped. Developments have now prevailed from track

We are now checking out and in all DCs that we doubt. Things are moving pretty fine now.

Required lot of patience

Thanks