Migration to NW7.11

Hi,
Maybe you can help me.
I am migration RWBS application based on WD for Java to NW7.11 and I am facing some copiling errors:
For example:
Code in NW7.0:
import com.sap.tc.webdynpro.services.sal.datatransport.core.IInputMassDatasource;
import com.sap.tc.webdynpro.services.sal.datatransport.core.InternalMassDataTransport;
Cannot longer be resolved and therefore the statement:
     IInputMassDatasource source = InternalMassDataTransport.addInputMassDatasource(htmlSrc, WDWebResourceType.HTML);
Cannot be compiled.
I guess this has to be replaced by import com.sap.tc.webdynpro.services.sal.datatransport.api.IWDInputMassDatasource;
However IWDInputMassDatasource is an interface and I don't know how to get an instance implemeting this interface and how to replace the statement above.
I also didn't find any documentation is the portal except JAVADOC which is not helpful.
Thank you and best regards,

Hi Armin,
Thank you so much for your quick answer.
I would like to confirm with you if the changes below are correct as I don't yet have J2EE installed for testing.
OLD CODE:
import com.sap.tc.webdynpro.services.sal.datatransport.core.IInputMassDatasource;
import com.sap.tc.webdynpro.services.sal.datatransport.core.InternalMassDataTransport;
public void print( java.lang.String pContent, java.lang.String pTitle )  {
  ByteArrayInputStream htmlSrc = new ByteArrayInputStream(pContent.getBytes());
  IInputMassDatasource source = InternalMassDataTransport.addInputMassDatasource(htmlSrc, WDWebResourceType.HTML);
String url = source.getUrl();
IWDWindow win = wdComponentAPI.getWindowManager().createNonModalExternalWindow(url,pTitle);
win.show();
NEW CODE:
public void print( java.lang.String pContent, java.lang.String pTitle )  {
  ByteArrayInputStream htmlSrc = new ByteArrayInputStream(pContent.getBytes());
  IWDResource source = WDResourceFactory.createMassDataResource(htmlSrc,   WDWebResourceType.HTML);
String url = source.getUrl(WDFileDownloadBehaviour.AUTO.ordinal());
IWDWindow win = wdComponentAPI.getWindowManager().createNonModalExternalWindow(url,pTitle);
win.show();
Best regards,
Hassane.

Similar Messages

  • NWDI & SLD migration to NW7.3

    Dear all,
    We are running NWDI 7.01 SP10 and are planning to upgrade to NW CE7.3 with usage development infrastructure.
    Can NW CE7.3 be installed first and then can the tracks be exported from the old nwdi and imported to new NWDI CE?
    In this scenario, we are also planning to install or upgrade the SLD's (version 7.0) to NW7.3. What should the sequence be, first SLD and then NWDI or does it matter? In the case of the SLDs, can the SLD repositories also be exported and imported to new environment?
    Is there any relevant documentation on this kind of migration?
    Thanks!
    Neeta

    Hi,
    I can suggest the NWDI system copy guide:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70ee5ab2-8d7a-2c10-d88b-dbe2fdf666e7?QuickLink=index&overridelayout=true
    Best Regards,
    Ervin

  • Migration to NW7.11 dependencies

    Hi,
    According to the step by step migration document the relevant required DCs should contain tc/bl/exception/lib and tc/bl/jrfc/api. After migragtion these two DCs are shown as deprecated.
    I selected tc/bl/exception/lib and I pressed CLRL + 1 but there is no alternative proposed.
    Can you help please?
    Best regards,
    Hassane.

    Hi,
    I've the same problem.
    I want to replace tc/bl/exception/lib, but I didn't get any suggestions...
    Has anybody an idea?
    Regards,
    Jens

  • Portal Logon page repeating/ redirecting to itself on first attempt

    All,
    Apologies in advance if this is not the appropriate forum.  We are in the process of migrating a NW7.0SPS13/EP7.0SPS13 installation from a remote site to a local site with a database only UME and SSO to an ECC6.0 backend.  The new target installation has picked up a rather odd behavior.  When loggin onto the portal, the logon page repeats/refreshes/redirects to itself with valid ID and password with no error message.  The only apparent action is the clearing of the password field.
    My only clue so far is the absence of this script in the http trace on the initial logon attempt which shows up on the second attempt:
    http://<host>:51100/irj/portalapps/com.sap.portal.httpconnectivity.httpauthentication/scripts/CAManagerScript.js
    I did find this related thread and attempted the suggestions with no luck:
    Re: portal logon page coming again
    I felt this might be the best place to post question since this may be an authentication/connectivity issue.
    Thanks in advance,
    Lee

    You are correct, we are not implementing SPNego but at this point I will take any suggestions that might be conceptually related...
    We are attempting to migrate/clone the entire server (OS,J2EE,MSSQL05...) from a remote hosted environment to a local network environment.
    I checked the Everyone, Authenticated, and Anonymous groups for the correct roles/Java permissions and all seems to be in-line with the correctly functioning remote system with correct user assignment.
    With some further log filtering I was able to where find this error:
    The default keystore view [TicketKeystore] does not exist. Authentication stack: [ticket]. The possible reasons for that problem are: keystore does not exist or the user has no permission to read from the keystore view. You can delete the TicketKeystore and restart the engine so that the engine automatically re-creates it.
    I suspect the SAPLogonTicketKeystore was recreated incorrectly...  I will have the migration team recreate it again.  FWIW, I am unfamiliar with the process of assigning user access to this object as the error suggests.
    Thanks for the suggestions...

  • Which one is the best way in migration from sap bpc ms 5.1 to nw7.5

    Hi,
    I am doing Migration project from SAP BPC MS to NW.
    In this which one is the best way migrating By manually or By using SAP Migration tool.
    What are the merits and demarits migrating by manually.
    The data is moving from MS to NW as it is by using sap migration tool.
    Could you please answer my questions as early as possible.

    Hi,
    You would need manual effort anyways. Some of the objects are not either migrated or you need to update manually after the migration. Example, reports have to be modifed and as they may not work due to some of the options.
    Also your packages, script logic etc have to recreated. So its upto you as the migration toosl takes across your appset, applications, dimensions and the master data etc. The manual involvement is inevitable. You need to probably take what the tool allows you to do and make manual corrections for the objects that are not supported.
    Thanks,
    Sreeni

  • Migration to ARFC2 in NW7.30

    Hi colleagues,
    I excecuted the steps to migrate a JAVA WD application from ARFC1 to ARFC2.. Aftre building and deploying the application. I get the following exception:
    com.sap.tc.webdynpro.progmodel.model.api.WDModelException: The type of model represented by class 'com.sap.fre.sui.bapi.model.BapiModel' is not compatible for creation by WDModelFactory!
        at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getNewModelInstance(ModelFactory.java:340)
        at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getOrCreateModelInstanceFromScopeMaintainer(ModelFactory.java:263)
        at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getModelInstance(ModelFactory.java:70)
        at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:94)
        at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:35)
        ... 56 more
    2eca19123b5211dfb8860000303c8bee. The causing exception is nested. RID=2eca19103b5211dfcad40000303c8bee
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:661)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:347)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
      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:453)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:439)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:428)
      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:272)
      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:462)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:270)
      at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:116)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:97)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.tc.webdynpro.services.exceptions.ApplicationFaultException: wdDoInit: exception thrown in this user coding area
      at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:164)
      at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
      at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
      at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:586)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1452)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:658)
      ... 46 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to create or init instance of model 'com.sap.fre.sui.bapi.model.BapiModel' in scope APPLICATION_SCOPE with instanceId 'null'
      at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getOrCreateModelInstanceFromScopeMaintainer(ModelFactory.java:284)
      at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getModelInstance(ModelFactory.java:70)
      at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:94)
      at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:35)
      at *com.sap.fre.sui.StoreUserInterfaceComp.shareRfcConnections(StoreUserInterfaceComp.java:1023)*
      at com.sap.fre.sui.StoreUserInterfaceComp.wdDoInit(StoreUserInterfaceComp.java:176)
      at com.sap.fre.sui.wdp.InternalStoreUserInterfaceComp.wdDoInit(InternalStoreUserInterfaceComp.java:666)
      at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
      ... 52 more
    Caused by: com.sap.tc.webdynpro.progmodel.model.api.WDModelException: The type of model represented by class 'com.sap.fre.sui.bapi.model.BapiModel' is not compatible for creation by WDModelFactory!
      at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getNewModelInstance(ModelFactory.java:340)
      at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getOrCreateModelInstanceFromScopeMaintainer(ModelFactory.java:263)
      ... 59 more
    I suspect the statement at line 1023 of the the class StoreUserInterfaceComp.java
    IWDDynamicRFCModel bapiRfcModel      = (IWDDynamicRFCModel)WDModelFactory.getModelInstance(BapiModel.class);
    But I don't know how to fix it.
    Thank you and best regards,
    Hassane.

    Hi Armin,
    Thank you so much for your quick answer.
    I would like to confirm with you if the changes below are correct as I don't yet have J2EE installed for testing.
    OLD CODE:
    import com.sap.tc.webdynpro.services.sal.datatransport.core.IInputMassDatasource;
    import com.sap.tc.webdynpro.services.sal.datatransport.core.InternalMassDataTransport;
    public void print( java.lang.String pContent, java.lang.String pTitle )  {
      ByteArrayInputStream htmlSrc = new ByteArrayInputStream(pContent.getBytes());
      IInputMassDatasource source = InternalMassDataTransport.addInputMassDatasource(htmlSrc, WDWebResourceType.HTML);
    String url = source.getUrl();
    IWDWindow win = wdComponentAPI.getWindowManager().createNonModalExternalWindow(url,pTitle);
    win.show();
    NEW CODE:
    public void print( java.lang.String pContent, java.lang.String pTitle )  {
      ByteArrayInputStream htmlSrc = new ByteArrayInputStream(pContent.getBytes());
      IWDResource source = WDResourceFactory.createMassDataResource(htmlSrc,   WDWebResourceType.HTML);
    String url = source.getUrl(WDFileDownloadBehaviour.AUTO.ordinal());
    IWDWindow win = wdComponentAPI.getWindowManager().createNonModalExternalWindow(url,pTitle);
    win.show();
    Best regards,
    Hassane.

  • Export data from database table before database migration

    Hello,
    We are planning to migrate our SAP ERP 6 Ehp4/NW7.01 from Oracle 11.2 to IBM DB2 v. 9.7 database. During test migrations I have established that we spend a lot of time for one particular table (COEP). Because we donu2019t have possibility to archive this table before migration I have an idea to export data from previous years from this table to the file system (using an ABAP report), delete those data from table before migration and then after migration, import back to the database from the file system.
    Does anybody have any concerns or suggestions about this idea?
    Thank you for your answers
    Andrej

    Hello Andrej,
    I strongly do not recommend to do so.
    I am not sure whether technically this could work at all..
    Even it if would work .. In order to really save time, the export and the import would have to be a dirty one (meaning the system is operational and in production). With this there is a high risk to produce inconsistencies on this table.  And you most likely will receive no support if something unforeseen happens and you end with problems.
    Also  your approach (if it should work at all) , would have to be tested thoroughly by you , also protecting the table from any changes.
    I do not believe that this can save any effort compared to implementing advanced migration techniques like table splitting.
    On top, you would go high risk to end with an unsupported system, with not using official migration procedures
    Hans-Juergen

  • Failed to create deployable object '********' since it is not a Web Dynpro object - Migration from 7.0 to 7.4

    I have installed NWDS 7.30 EHP1 SP 14 PAT000   with JVM 6 SAP AG
    to   migrate wedynpro development components from 7.0 to
    NW7.4 WAS SAP AG 1.6.0_85 on Windows Server 2008 R2 6.1  SP09 PAT000
    In track imported below SCAs of version  7.31 SP14 .
    Could able to migrate and build in NWDS, getting deployment errors.
    Followed   
    http://scn.sap.com/docs/DOC-55584 
    and   
    http://scn.sap.com/community/nwdi/blog/2014/03/26/nwdi-vs-nwdi-content 
    COMP_BUILDT
    ECM-CORE
    ENGFACADE
    ENGINEAPI
    ESCONF_BUILDT
    FRAMEWORK
    MOIN_BUILDT
    SAP_BUILDT
    WD-RUNTIME
    Deployment Errors:-
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
        at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
        at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
        at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
        at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
        at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
        at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
        at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
        at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
        at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
        at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
        at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
        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.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] Operation [update] of [sdu id: [XXXXXXX.com_home~chgemail]
    sdu file path: [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ] failed
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:100)
        at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)
        at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
        at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
        ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [update] of [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear] failed
        at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:489)
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)
        ... 11 more
    Caused by: com.sap.engine.services.servlets_jsp.webcontainer_api.exceptions.WebContainerExtensionDeploymentException: Error during deployment of application {0}
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:52)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeployInternal(ExtensionHandler.java:169)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeploy(ExtensionHandler.java:129)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerProvider.deploy(WebContainerProvider.java:334)
        at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:360)
        at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:327)
        at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:446)
        at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:409)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:478)
        at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:234)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:582)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:487)
        ... 12 more
    Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.DeploymentException: Failed to deploy application 'XXXXXXX.com/home~chgemail'.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:324)
        at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.notifyOnDeploy(DeployableObjectInternal.java:122)
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:49)
        ... 27 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:79)
        at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObjectFactory$1.getDeployableObject(AbstractDeployableObjectFactory.java:87)
        at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObject(WDDeployableObject.java:43)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.calculateVMOsOfDeployableObject(RepositoryContainerHook.java:264)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:181)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:297)
        ... 29 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.
        at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:228)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:77)
        ... 34 more
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]

    C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear
    can you find this ear in your local drive?

  • RE:Migration of KM content

    Hi Experts
    I want to migrate KM content from development to production server (EP7).Will the metadata propeties get migrated if i use  ICE protocol.I also need to migrate the properties related to search.  Will i be able to achieve this through ICE protocol or should i use CTS transport to migrate configuration  properties.
    Please suggest me to proceed further.
    Regards
    Chandana

    Hi chandana,
    no matter which way you use for the transport, you need to first migrate the[ KM properties configuration|http://help.sap.com/saphelp_nw70/helpdata/en/e1/029c414c79b25fe10000000a1550b0/frameset.htm] and afterwards the KM content. You can make use of a Change and Transport System (CTS) if you have one, but that's not required.
    After you have successfully transported the configuration, you can use WebDAV or ICE to transport content, if you only care about your custom properties relevant for search, but the new tool provided with NW7.0 SPS14 is the more advanced. It allows you to filter documents and also to transport the GUID. The link to the documentation is provided by Steve above, and just to make sure, it works also for folders and not only for single documents.
    Hope this helps,
    Robert

  • Migrate EJB from NW 7.0 to NW 7.4

    Hi,
    Understood that NW 7.4 is using EJB 3.0 and JDK 1.6 while NW 7.0 is EJB 2.1 with JDK 1.4.2. I have an application developed in NW 7.0 and now need to migrate to NW 7.4. Realized the method for EJB 2.1 and EJB 3.0 is quite different. Any method to do it or I have to recode and rebuild it at NW 7.4.
    Meanwhile the EJB project actually also tied with WebDynpro Java, for the UI parts, would like to know way to migrate both at once.
    Thanks.

    Hi Adrian,
    As already mentioned by Rolf, so don't have much to write but also go through the below links which are describing about EJB2.1 with NW7.4 and migration as well.
    Creating EJB 2.1 Components - Developing Java EE 5 Applications - SAP Library
    SAP NetWeaver Portal 7.3 – Top 10 lessons learned from ramp-up you should know before getting started!
    Thanks,
    Hamendra

  • Migration from NW 7.0 to NW 7.3

    Hello,
    In NWDS 7.3, When I tried to Import a DC created in NW7.0 environment, It got created in WDJ Explorer with few errors.
    The methods like invalidate(), bind() etc were in error.
    These methods seem to have been deprecated in NW 7.3
    The import Wizard suggests to right click on the project abd say Repair->Internal Web Dynpro API Usage. But this does no remove those errors.
    Please suggest how to remove these errors.
    Regards
    seventyros
    Edited by: seventyros on Sep 20, 2011 6:13 AM

    Hi,
    When you migrate from NW 7.0 to Composition environment you need to migrate the imported DC.IF you will right click on the component you will get an option of migrating.
    There is a help provided in the form of cheat sheet which guides you about the steps in migration.You can refer the following document though it is for CE 7.1
    TechEd '07: CE206 - Migrating Web Dynpro Java Applications From SAP NetWeaver 7.0 to CE 7.1
    Regards
    Radhika

  • NWDI migration issue - all DCs are not migrated

    I am trying to migrate a track from one NWDI (7.0)to another NWDI (7.3)for NW7.0 based code.
    in the old NWDI , the track consists of 30 DCs and there are no broken DCs , I have exported the SCA file from Assembly and basis copied it to new NWDI's CMS inbox.
    We have imported the SCA file and created the track with proper dependencies in the new NWDI.
    But the track in new NWDI shows only 20DCs and 10of the DCs are missing.
    When I checked in DTR, I see the toplevelDcs are missing in the inactive section of the workspace.
    what will be the issue and how can I resolve such issue?

    Please refer note  1259604 - CMS check-in tab: Not all files from inbox are displayed
    https://service.sap.com/sap/support/notes/1259604

  • Migration of WDJ Connecting MDM5.5 to MDM 7.1

    Hello Experts,
    Currenlty we are migrating WDJ and a EJB created for webservice connecting to MDM from 7.0 to 7.3. Out MDM was 5.5 the new MDM is 7.1.
    I could migrate WDJ code successfully and deployed as well. We have installed MDM_JAVA_API and also imported as SC in NWDI track.
    WDJ application is to perform test connection of the given MDM server details. But we are facing a issue called "Error while trying to invoke the method com.sap.mdm.session.NetWeaverMdmDestinationProperties.getServerName() of an object loaded from local variable 'destination'"
    Since this is a migrated code we have not used any MDM destination in the code. But just for testing i created a MDM destination and its test is success.
    Also i creating portal system with MDM server details and when we test the system connection test it throws the same error ""Error while trying to invoke the method com.sap.mdm.session.NetWeaverMdmDestinationProperties.getServerName() of an object loaded from local variable 'destination'".
    Our portal vesion is NW7.3 with SP7.
    Regards,
    Karthi Velayuthan

    Please look at, Hope this is helpful for you...
    http://scn.sap.com/thread/1627412
    Regards
    Vijay

  • Can i reuse my WD Java applications developed in NW7.0 in CE 7.1

    Dear SDNs,
    I have developed a MDM related Workflow applications using WebDynpro Java in NetWeaver 7.0 version and now we are switching to NetWeaver CE 7.1 version. in that case how can i reuse my WD applications in NW7.0. will the direct redeployement work in CE 7.1 server?
    Please confirm me.
    Your inputs will be appricated.
    Thanks in advance,
    Sireesha.

    Refer to below link for WD migration:
    https://cw.sdn.sap.com/cw/docs/DOC-136995
    https://cw.sdn.sap.com/cw/docs/DOC-136998/diff?secondVersionNumber=3
    Hope it helps
    Regards
    Deepak

  • I need lookup syntax to run the logic in BPC NW7.5

    Hi,
    I am doing Migration project from BPC MS7.0 to BPC NW7.5. In this I faced one problem.
    I write one Script logic using Lookup syntax. Here one error message displayed when I validate the logic "Invalid Lookup strecture: Invalid application name".I am giving the right name of the application.
    Please find attached logic,Let me know is there any error syntatically. But it is working in the MS version.
    Please correct the code and let me know any prerequisites to run the Lookup syntax.
    *Lookup Staff_Additions
    *DIM Salary="Salary_redis"     
    *DIM Category="Budget"     
    *DIM Client_Group="1010"     
    *DIM DataSrc="Input"     
    *DIM Intco="Non_Interco"     
    *DIM RptCurrency="LC"     
    *DIM Time="2011.MAR"
    *DIM Account="41000"
    *ENDLOOKUP
    *When Category.ID
    *Is = "Budget"
    *WHEN INTCO.ID
    *Is = "NON_INTERCO"
    *When JOB_TITLE.ID
    *Is = "NO_JOBTITLE"
    *When SALARY.ID
    *Is = "SALARY_REDIS"
    *When RptCurrency
    *Is = "LC"
    *When DATASRC
    *Is = "INPUT"
    REC(Expression=ROUND(.07692 Lookup(STAFF_ADDITIONS),0),Time="2010.APR",SALARY="SALARY_MO")
    *ENDWHEN
    *ENDWHEN
    *ENDWHEN
    *ENDWHEN
    *ENDWHEN
    *ENDWHEN
    *COMMIT

    Hi,
    I think your question got answered when you asked it the first time:
    Re: There is an error in the process of validating the lookup function in NW
    Try to apply these ...
    Kind regards
    Matthias

Maybe you are looking for

  • Smart-Form name for Printing of Payment-Receipt in Tcode FBCJ

    Dear Sir, We use Tcode FBCJ for the making of Cash Payment . To Print the Cash Payment Receipt , we first select the Payment Line Item then Click on Edit --> Print Receipt . This call a Smart-Form and Payment Receipt get printed . We need to know the

  • HT4623 ipad stuck when using apple tv

    After connecting my Ipad to Apple tv I now find the Ipad appears to be still connected to Itunes,and locked,I am now having to completley reset the Ipad which will take about three hours,I now have no confidence in usimg my Ipad with apple TV in the

  • How to set Password History in ACS? Sarbanes-Ox...

    I am using acs 4.0 for tacacs auth to network devices. I need to be able to force the password history to prevent users from using any of the previous 5 passwords. I see that there is an option to prevent from using the "last" one, but not 5. Can I o

  • Standby VPN in the ASA 5505

    Hello, I'm triying find out if there is a way to put a second vpn site-to-site as standby and if the primary come down  this standby come to up. for exemplo, I have a ASA 5505 in my branch office I wish add two VPN site-to-site to my head office. one

  • Lock and Unlock Time Stamp

    Hi, Is there a way to get the time stamp when we lock and unlock the entities. And also the User name who performed the lock and unlock task? Rgds Abhi