Do we need reimport after changes in Runtime environment Parameter.

[Former Member]

Hi,

We have ECC 5.0 , EP 6.0 , ESS/MSS Webdynpro and NWDI installed on one host with different instance and port no. We have installed NWDS in EP developer system.

Created one track for Development with Runtime system "Dev" as we are in "Blue Print' phase no QA and Production available as of now.

1. Few days back we have changed track data as below ..

While installation of NWDI we have configured Development Runtime SDM Host and Port as "NWDI" SDM Host and Port no, We have changed this setting recently to "ECC" development server SDM host and port no. As we have noticed all the ESS MSS WebDynpro should get deploy over the ECC development server and should used SDM of ECC rather than NWDI. Is this setting right or wrong?

Do we need to restore the system status of Development and reimport the entire component in Development and consolidation? Please advice.

When my EP developer create package in NWDS for modification in existing ESS WebDynpro, which Build space he should use? LJD_ESSTrack_C or LJD_ESSTrack_D.

We currently have one track. Perhaps the SDN blog mentioned about

the maintainance track. Fortunately we would like to modify the SAP provided ESS/MSS WebDynpro, Do we need "Maintainance" track? Do we need "Consolidation" runtime system configured to this track?

I am following about reimport is just because we have h/w restriction and if we start unnecessary import, it will impact our development operation adversely with high I/O.

Thanks in advance.

Sanny.

[Former Member · Accepted solution]

> As we have noticed all the ESS MSS WebDynpro

> should get deploy over the ECC development server and

> should used SDM of ECC rather than NWDI. Is this

> setting right or wrong?

<b>This setting is correct ...</b>

> Do we need to restore the system status of

> Development and reimport the entire component in

> Development and consolidation? Please advice.

<b>If you change your track configuration like add or modify a new runtime system , then you will have to restore system state and import the standard components JTECHS, BUILDT and JEE. The BUILDT plugin will cause entire rebuild of the workspace so this will take time.</b>

>

> When my EP developer create package in NWDS for

> modification in existing ESS WebDynpro, which Build

> space he should use? LJD_ESSTrack_C or

> LJD_ESSTrack_D

<b>

He should use LJD_ESSTrack_D and should be changing the DCs from inactive workspace</b>

> We currently have one track. Perhaps the SDN blog

> mentioned about

> the maintainance track. Fortunately we would like to

> modify the SAP provided ESS/MSS WebDynpro, Do we need

> "Maintainance" track? Do we need "Consolidation"

> runtime system configured to this track?

<b>

You currently need only one track for modification , you usually get to maintenance mode post go live</b>

> I am following about reimport is just because we have

> h/w restriction and if we start unnecessary import,

> it will impact our development operation adversely

> with high I/O.

<b>

If your developers have imported the Development configuration and have created their projects then this remiport shouldnt stop them from developing.

Better to define your Track completely at the start otherwise each time you add a new system you will have to perform restore system state.</b>

> Thanks in advance.

>

>

> Sanny.

[Former Member · Accepted solution]

Hi,

Your information is very precise.

However I am getting one more error while reimport of ESS SC.

Info:Starting Step Repository-import at 2006-03-30 11:58:12.0336 -5:00

Info:Component:sap.com/SAP_ESS

Info:Version :MAIN_xss04VAL_C.20051124134619

Info:1. PR is of type TCSSoftwareComponent

Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailureException received: Internal Server Error:communication error: VcmFailureException received: Internal Server Error

com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailureException received: Internal Server Error

at com.sap.cms.tcs.client.DTRCommunicator.writeChangelistData(DTRCommunicator.java:264)

at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:259)

at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:500)

at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)

at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)

at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)

at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)

at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1252)

at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1170)

at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)

at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)

at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java(Compiled Code))

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java(Compiled Code))

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java(Inlined Compiled Code))

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java(Compiled Code))

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java(Compiled Code))

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java(Compiled Code))

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java(Compiled Code))

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java(Compiled Code))

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java(Compiled Code))

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java(Compiled Code))

at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))

at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))

at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))

at java.security.AccessController.doPrivileged1(Native Method)

at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))

Info:Step Repository-import ended with result 'fatal error' ,stopping execution at 2006-03-30 11:58:53.0931 -5:00

Thanks in advance.

Sanny.

[Former Member · Accepted solution]

Hi Santosh

The CBS process goes nuts after an import , try restarting the CBS service or restarting the instance before starting the next import.

Regards

Pran

[Former Member · Accepted solution]

Thanks a ton.. The problem got solved.

Do we have any alternatives for this issue.

Please advice.

Sanny.

[Former Member · Accepted solution]

How did you get the problem solved, we are continually getting the same exception ?

[Former Member · Accepted solution]

Hi,

Try to investigate and apply following correction.

please start the configtool of the Engine and check that the following

values are set:

Dispatcher-> Services->HTTP Provider

KeepAliveTimeout = 300 (seconds)

MaxRequestContentLength = 1048576 (kB)

Server->Services-> HTTP Provider -> Properties TAB

ServletsLongDataTransferTimeout = 600000 (milli seconds)

Then restart the whole Engine and try the import again.

This solved my problem.

Thanks

Sanny.

[Former Member · Accepted solution]

Hi,

I am facing the same problem. I am also using ECC 5.0, EP 6. ESS components are SP22. I have tried all the above solutions but is of no help. Am still getting the same error. Please help

Thanks

[Former Member]

If you want your ECC system to contain all SC's and custom developments, you should execute a Restore System State and make sure that everything gets re-imported (from SP14 or SP15 this is done automatically).

When developing you should always use the _D Development Configuration (this is connected to the Development stage). The _C configuration is connected to the Consolidation stage and is intended for Release bugfixing (fix bugs you encounter during Acceptance Testing in the Consolidation or Test stage (this of course depends on your track set up)).

You use a maintenance track if you want to be able to fix Production problems with high priority. You do not need to assign runtime systems to any other stage than the Production stage.

Update: Pran was quicker