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.

Similar Messages

How to configure/implement stateful r3 connection in Arfc2 model?

Hi,
After migration to Arfc2 model rfc function executed in different r/3 session.
How to configure/implement stateful behavior as arfc1 for using abap enqueue, transaction, shared between fm global variables from function group?
Wbr, Ivan

Hi,
thanks for your reply, but I'm afraid your post does not answer my question.
I don't have an issue concerning the state of the Web Dynpro Application - my problem is, that if I use ARFC2 (and not its predecessor ARFC1) to call an ABAP backend, every call to a function in this backend results in an independent session and this way doesn't share the same space in memory.
Indeed, you need less RFC connections this way, and this is an important advantage, but in some cases you have to redesign and rewrite substantial parts of an application if it was designed under aspects of ARFC1.
And I'm now looking for a way to have ARFC1-like behaviour with ARFC2.
Greets
Bernd

How to migrate CAF project from 7.0 to 7.2 ?

Hi, All.
     I have developed some caf projects with NW7.0. Now I have to migrate those projects to NW7.2.
     NWDS 7.2 seems be able to convert the caf project from NW7.0 to NW7.2, but not all of the project.
     After conversion I lost my application services and only reserved entity services.
     Dose there anyone know how to migrate the caf project completely?
Thanks a lot.

I have already tried many ways to migrate my caf projects.
Only bo part of caf project can be migrated, but I still need to recode the as.
It means nothing, because most codes were written in as part.
I decide to recode it. >.<

Dirty DCs in NW7.11

Hi,
I have migrated my application to NW7.11.
The CBS build fails because of Dirty DCs. Here is the result in the log file:
20090512174657 Info   :Starting Step CBS-make at 2009-05-12 17:46:57.0199 +2:00
20090512174658 Info   :wait until CBS queue of buildspace MAIN_ST511SP_C is completely processed, before starting the import
20090512174658 Info   :CBS queue of buildspace MAIN_ST511SP_C is completely processed. Starting the import now.
20090512174658 Info   :=================================================================
20090512174658 Info   :buildspace = MAIN_ST511SP_C   build request id = 1602746
20090512174658 Info   :wait until CBS queue of buildspace MAIN_ST511SP_C is completely processed, before asking for build results
20090512174658 Info   :waiting for CBS queue activity
20090512174729 Info   :build process already running: waiting for another period of 30000 ms
20090512174729 Info   :waiting for CBS queue activity
20090512174759 Info   :build process already running: waiting for another period of 30000 ms
20090512174829 Info   :build process already running: waiting for another period of 30000 ms
20090512174829 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512174859 Info   :waiting for CBS queue activity
20090512174929 Info   :build process already running: waiting for another period of 30000 ms
20090512174929 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512174959 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175029 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175059 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175129 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175159 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175229 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175259 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175329 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175359 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175429 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175459 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175529 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175559 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175629 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175659 Info   :waiting for CBS queue activity
20090512175729 Info   :build process already running: waiting for another period of 30000 ms
20090512175729 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175759 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175829 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175859 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175929 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512175959 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180029 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180059 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180130 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180200 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180230 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180300 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180330 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180400 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180430 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180500 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180530 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180600 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180630 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180700 Info   :There are still dirty DCs in buildspace, waiting for 30 seconds.
20090512180730 Info   :CBS queue of buildspace MAIN_ST511SP_C is completely processed. Asking for build results now.
20090512180730 Fatal :the compartment sap.com_STORE_UI_1 contains dirty DCs after the CBS build process:
20090512180730 Info   :dirty DC in compartment sap.com_STORE_UI_1 (dcname=scm/sui dcvendor=sap.com)
20090512180730 Fatal :Dirty DCs in buildspace sap.com_STORE_UI_1 after the CBS build process
20090512180730 Info   :Step CBS-make ended with result 'fatal error' ,stopping execution at 2009-05-12 18:07:30.0418 +2:00
The current used DCs are:
ENGFACADE
FRAMEWORK
SAP_BUILDT
WD-RUNTIME
Can you please assist?
Thank you and best regards,
Hassane.

Hi Ayyapparaj,
Actually I don't have J2EE installed on my local PC. However I just tried to build the project and I get the following errors:
[javac] ERROR: C:\Documents and Settings\i801193\workspace.jdi\2\t\97D641A4D3B4BBA42480A8F5FF379837\gen_wdp\packages\com\sap\fre\sui\StoreUserInterfaceComp.java:24: package org.apache.xalan.transformer does not exist
[javac] ERROR: C:\Documents and Settings\i801193\workspace.jdi\2\t\97D641A4D3B4BBA42480A8F5FF379837\gen_wdp\packages\com\sap\fre\sui\StoreUserInterfaceComp.java:77: package com.sun.corba.se.internal does not exist
I am wondering if there are missing dependencies in the track.
What doo you think?
Hassane.

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

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.

ARFC2 Migration

Hello experts
I am trying to migrate my ARFC models (origin 6.40) to ARFC2 models (7.20) but I get the message:
Unable to reimport new model. Reimport failed.
Migration to Adaptive RFC 2 model for ...Model failed
Any ideas?
Thanks
Hans

Hello together
I think I know the problem now, when I create a new ARFC2 model I get an error message in the workspace log:
java.lang.IllegalArgumentException: Name may only contain A..Z, a..z, 0..9 or '_' but is /DORMAPP1/BAMODNO
After searching a bit I found an SAP note 1438679 explaining that '/' is an invalid character and has to be replaced.
I would say the '/' is fairly common in ABAP as it is used for customer/partner namespaces.
Does anybody know how to cope with this problem (apart from using the deprecated ARFC model)?
Regards
Hans

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 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

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

Problems with language in ARFC2

Hi,
after migrating JCO Connections to ARFC2 I have a problem with the messages and textes from the RFC Functions.
Before ARFC2 the messages where in the correct language of the logged in user.
But now in ARFC2 there are only the german messages.
Are there any settings, that the language of the user should be used?
Best regards,
Peter

Hello Peter,
I'm facing the same problem with arfc2 models - the language of the logged in user is ignored completely. Did you find a solution for the problem?
Kind regards,
Helmut

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

Migration to ARFC2 in NW7.30

Similar Messages

Maybe you are looking for