Migration of SAP Netweaver

I'm currently installing SAP Netweaver 7.0 in Windows Server 2008 R2. The database is MS SQL 2008 R2.
I'm a bit confuse now because I'm not sure need to start a fresh installation or just doing a system copy will do. This is because I already have existing system with server 2003 and MSSQL 2005. I just need to do a system copy to export and import to the new server or I need to do a fresh installation in the new server where I need to install solution manager in order to get the key to proceed with the installation.

> We would like to migrate a SAP NetWeaver system with ca. 90 interfaces from
> data center 1 to data center 2.
> The current OS is SUN and DB is DB2.
> The destination/future OS is Windows with Oracle.
> The questions:
> 1) Which XI specific points (interfaces, messages, etc.) should be considered during the migration?
You have to be aware that Solaris -> Windows implies an endian change (Solaris SPARC is BE whereas Windows is LE). The receiving systems must "know", that the data coming is of a different endianess - depending on which adapter you use.
> 2) Which estimate (round about) does it take?
Nobody can tell you that, it is influenced by hardware, storage power, preparation, parallel tasks etc. etc. etc.
> 3) Where can I find the appropriate documentation?
http://service.sap.com/osdbmigration
Basically you will be doing a heterogenous system copy, roughly spoken "start sapinst, export ABAP and Java, start sapinst on target and import".
Be aware that you need a SAP certified migration consultant on site to do the migration. If you do it on your own you will loose support in case of problems.
Markus

Similar Messages

Migrating SAP NetWeaver WebDynpro 7.0 Applications to WebDynpro 7.3/7.4

Hi,
We are trying to migrate applications from SAP NetWeaver Portal 7.0 to 7.4. The applications were created using SAP NetWeaver WebDynpro Java 7.0 and we're trying to import the Development Components (DC) using SAP NetWeaver Development Studio CE 7.3. However we're encountering an error after rebuilding and repairing the applications
Error Details:
Generation of component ****Comp is terminated with an exception (com.sap.ide.mmservices.wd.general.NoWebDynproContentException: No Web Dynpro content found for project "***". If this project is a Development Component, check if "SapMetamodelWebdynproContent.zip" is present in the classpath.) [Error: com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse Thread[Worker-29,5,main]]
The project was not built since its built path is incomplete. Cannot find the class for com.sap.mw.jco.JCO$Client.
The type com.sap.mw.jco.JCO$Client cannot be resolved. It is indirectly referenced from required .class files
Any ideas regarding the errors?
thank you.

Hi,
thank you all for your replies.
there are no longer errors anymore before deployment. However, once we deploy we encounter a build error.
here are the details:
!ENTRY org.eclipse.ui 4 4 2014-06-18 11:13:00.188
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorationResult(LightweightDecoratorManager.java:378)
at com.sap.ide.tools.core.viewerfwk.ui.tree.wrapper.ProjectWrapper.getTreeNodeLabelText(ProjectWrapper.java:74)
at com.sap.ide.webdynpro.wdexplorer.tree.WDViewLabelProvider.getText(WDViewLabelProvider.java:98)
at com.sap.ide.tools.core.viewerfwk.ui.tree.CompoundLabelProvider.getText(CompoundLabelProvider.java:81)
at org.eclipse.jface.viewers.ViewerComparator.compare(ViewerComparator.java:135)
at com.sap.ide.tools.core.viewerfwk.ui.tree.CompoundViewerSorter.compare(CompoundViewerSorter.java:77)
at org.eclipse.jface.viewers.ViewerComparator$1.compare(ViewerComparator.java:187)
at java.util.Arrays.mergeSort(Arrays.java:1270)
at java.util.Arrays.mergeSort(Arrays.java:1281)
at java.util.Arrays.sort(Arrays.java:1210)
at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:185)
at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:625)
at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2578)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1863)
at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:716)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1838)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1794)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1780)
at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1457)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1392)
at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:402)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1353)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1455)
at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1414)
at com.sap.ide.dictionary.ddicexplorer.tree.DDICContentProvider$1.run(DDICContentProvider.java:709)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Do you have any ideas?
thank you very much!

Migration from development to production environment for SAP Netweaver BI

All,
When I created a SAP Netweaver BI connection using BeX query in BW development environment, the system is defaulted to the BW development environment. Since the system textbox can't be modified to use a variable to point to production environment, can you share how you migrate your SWF file to production environment and ensure that it points to the BeX production query?
Thanks for sharing ....

After some more searching, I found this link: http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f005a4ca-d4fd-2c10-adb8-8ec24383cb97

OS/DB Migration - Course and certification for SAP Netweaver 7.00

Hello everybody,
The OS/DB migration course and certification is still based on SAP Web Application Server 6.40, which is a rather old platform, since SAP Netweaver 7.00 is available since 06.2006 as far as I know
There is a particular reason for this delay? Can anyone know when the education offering from SAP will cover the new Basis release?
I'm interested in this field of technology, but if I know that the new course will be available too far in the future, I will focus on other certifications for now
Regards,
Valerio

I am sorry for getting into someone's topic but I would like to clarify few things.
As I understand the information related to the course description is outdated. Although the course currently provided by sap consists of the actual info. And whether that information is reflected in a course book?
What about the examination?
Does it still consists of old questions and corresponds to description at training.sap.com(<AS 6.40) or it does include updated questions related to the latest SAP versions.
And what about the training materials issued by sap for that course?
Same question here. Whether it holds the actual information and consists of latest techniques and descriptions.
I am planning to take the certification w/o taking a course. I have a training material from one of my colleagues who has kindly shared a book with me. He has taken the course some time ago and his book states:
SAP Web AS 6.40
2005/Q3
so I am worried about the consistency of that book. And I would like to be sure before going to exam that there will be no surprise for me by having non-expected questions.
If someone can comment this that would me much appreciated.
Thanks.

Migrating from WebLogic to Sap netweaver j2ee application

Hi all,
We are migration a weblogic j2ee application in to sapnetweaver. In web logic, we have config.properties file which contains weblogic related roles, permissions and all configuration related to the application. If we want to use that file in sap netweaver how to configure it.
Can anyone please explain.
Thanks in advance
Points will be awarded for good answers
Madhuri
Message was edited by:
jaya madhuri bai gaykwada
Message was edited by:
jaya madhuri bai gaykwada

Hi,
There is no file that contains all this properties you'll need to configure it all with the Visual Administrator.
Regards,
Pavel Sheynkman.

Migrating an SAP 4.7x110 system on W2003 32-bit to a 64-bit host (x86_64)

We want to migrate an SAP 4.7x110 system on Windows Server 2003 32-bit to a 64-bit host (x86_64). Afterwards we want to upgrade the system to ECC 6.0.
According to PAM, 4.7x110 is not supported on Windows 64-bit.
According to note 960769,
"After the migration to the 64-bit hardware, your SAP system may have a status that is not supported by SAP for productive use (see Note 814834). You may need to upgrade to a new SAP release. In this exceptional circumstance, SAP offers support for the duration of the upgrade. Note that SAP does not support a longer, more productive use of such a system for the period after the migration and before the upgrade....
...We generally recommend to use SQL Server 2005 (64-bit) for the productive use on x86_64. However, the 32-bit operation of SQL Server 2000 on Windows x86_64 64-Bit (supported by Microsoft) is also supported by SAP...
...The following table illustrates which OS/DB combination supports each SAP release in the target system.
Source System   Target System (Kernel, DB Software)     Support Comment
3.1I   3.1I 32-bit, MSSQL 2000 32-bit    only for upgrade (a,c)
4.0B   4.0B 32-bit, MSSQL 2000 32-bit    only for upgrade (c)
4.5B    4.5B 32-bit, MSSQL 2000 32-bit    only for upgrade (c)
4.6C   4.6D 32-bit, MSSQL 2005 64-bit     productive (b)
620   640 64-bit, MSSQL 2005 64-bit    productive (b)
640   640 64-bit, MSSQL 2005 64-bit    productive (b)
700   700 64-bit, MSSQL 2005 64-bit    productive (b) "
According to note 814834,
"SAP supports the x86_64 platform on Windows 2003 Server SP1 x64 for kernel 4.6D and kernel 6.40 and higher. ... For product versions based on kernel 6.40 and higher, only 64-bit operation is supported."
According to note 905634, about SQL Server 2005 support (where a mention to R3E 4.7 x110 is missing)
"Supported SAP products based on SAP_BASIS 6.20 and SAP_BASIS 6.40
Product Windows platforms
BW 3.10 x86, IA-64
SCM 4.0 x86, IA-64
EBP/CRM 4.0 x86, IA-64
ECC 5.0 SR1 x86, IA-64, x64
NetWeaver'04 SR1 x86, IA-64, x64
SCM 4.1 x86, IA-64, x64
SRM 4.0 SR1 x86, IA-64, x64
CRM 4.0 SR1 x86, IA-64, x64
R3E 4.7 x200 SR1 x86, IA-64, x64
SolMan 3.2 SR1 x86, IA-64, x64 "
+//////////////////////+//
According to all this information, may I move our 4.7x110 system onto a Windows Server 2003 SP1 64-bit, SQL Server 2005 64-bit, and after that we would upgrade to ECC 6.0?
Thanks !!!
Eva
Edited by: Eva Verdaguer on Jul 25, 2008 12:41 PM

Sorry, I forgot posting the SAP answer, which is also "Yes":
30.07.2008 - 16:19:00 CET - Respuesta by SAP
Dear Eva,
Yes, you can move to the 64 bit platform with SQL Server 2005 according
to note 960769.
Information in note 905634 means there is no installation DVD for
release 47x110 for SQL Server 2005. So it is not possible to do a fresh
installation of 47x110 except if you follow the workaround of note
899111 (for x64).
Best Regards,
Manuel García Guardiola
SAP Active Global Support - Netweaver Web Application Server
****************************************************************+
Thanks very much for your message, anyway.
Regards !!
Eva

Data Migration from SAP r/3 to SAP R/3

Hi all,
What is the best method to migrate data from one verison of SAP to another verison of SAP ECC say from SAP 3.1 to SAP ECC 6.0?
This is for all SAP modules including sd, mm, pp, fi, co master and transaction data. I know there are number of technologies to load the data such as LSMW, IDOC, ALE, DI, etc but what is the best way to extract all data feeds to be loaded back into SAP.
Thanks in advace.

Take a look to the following link, may be useful for you
SAP NetWeaver - Data Migration (CA-DMI) [original link is broken]
if helpful reward points are appreciated

SAP NetWeaver 7.01 SR1 ABAP Trial Version Installation Fails

Hello,
While doing SAP NetWeaver 7.01 SR1 ABAP Trial Version Installation, I am getting below error message:
~
An error occurred while processing option SAP NetWeaver 7.0 SR1 including Enhancement Package 1 > SAP Application Server ABAP > MaxDB > Central System > Central System( Last error reported by the step :
The subkey 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BlackICE' does not exist on the 'localhost' host.). You can now:
Choose Retry to repeat the current step.
Choose View Log to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/NW701/AS-ABAP/ADA/CENTRAL/.
~
I have checked regedt32 and found the entry 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BlackICE' which is having detail (Default) REG_SZ (Value not set). When I double click on (Default) it says "Can not edit: Error reading the value's content"
~
In Services, "BlackICE" service is "Started" and Statup Type is "Automatic" and Logon As "Local System".
I have Microsoft Windows XP Professional Version 2002 Service Pack 2 and 3 GB RAM. I am using user which is part of "Administrator" group.
Can someone help what could be the issue and how I can resolve it so that can complete the Installation.
Appreciate your great help.

Hi Pedro,
could you fix the error?
I'm installing and I have the same problem.
An error occurred while processing option SAP NetWeaver 7.0 SR1 including Enhancement Package 1 > SAP Application Server ABAP > MaxDB > Central System > Central System( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
Choose Retry to repeat the current step.
Choose View Log to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Archivos de programa/sapinst_instdir/NW701/AS-ABAP/ADA/CENTRAL/.
Thanks.
Anibal

Error when installing SAP NetWeaver AS ABAP 7.02 SP6 32-bit Trial

Hello,
I have tried several times to install "SAP NetWeaver AS ABAP 7.02 SP6 32-bit Trial".
But i always get an error during install.
I get this error:
An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 2 > SAP Application Server ABAP > MaxDB > Central System > Central System
( Last error reported by the step :Program 'Migration Monitor' exits with error code 2. For details see log file(s) import_monitor.java.log, import_monitor.log.
My System specs are:
Windows XP Professional SP3
2GB RAM
JRE 1.5.0_22 or JRE 1.4.2 (i have tried both)
Maybe there is a problem with the correct file size of "Part 2 file" on the [download location|http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/f03b3428-91e5-2d10-5fae-9afaad060b0c]
The file size of "part 2 file" should be:
"SAP NetWeaver AS ABAP 7.02 SP6 32-bit Trial Version Part 2 (1.838.392.707 bytes)".
But my file size is always only "1.837.289.009 bytes".
I have tried to download the file with 3 different browsers on two different computers.
Please help

Hi Anders,
No, there is no space anywhere. this is my log
os.name = Windows XP
os.arch = x86
os.version = 5.1
cpu.count = 4
sun.cpu.endian = little
sun.arch.data.model = 32
sun.cpu.isalist = pentium_prommx pentium_pro pentiummmx pentium i486 i386 i86
file.encoding = Cp1252
file.separator = \
path.separator = ;
line.separator = CR/LF
user.name = mphasis
user.home = d:\Documents and Settings\nspadm.MPHNYLAP41L24
user.dir = C:\Program Files\sapinst_instdir\NW702\AS-ABAP\ADA\CENTRAL
user.language = en
user.country = US
java.version = 1.5.0_22
java.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
java.vm.version = 1.5.0_22-b03
java.vm.vendor = Sun Microsystems Inc.
java.vm.name = Java HotSpot(TM) Client VM
java.vm.info = mixed mode
java.compiler =
java.class.version = 49.0
java.home = C:\Program Files\Java\jre1.5.0_22
java.ext.dirs = C:\Program Files\Java\jre1.5.0_22\lib\ext
java.class.path = migmon.jar
java.library.path = C:\Program Files\Java\jre1.5.0_22\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\usr\sap\NSP\SYS\exe\uc\NTI386;D:\sapdb\clients\NSP\bin;D:\sapdb\clients\NSP\pgm;D:\sapdb\programs\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\OEM\DLLShared\;C:\Program Files\Common Files\Roxio Shared\OEM\DLLShared\;C:\Program Files\Common Files\Roxio Shared\OEM\12.0\DLLShared\;C:\Program Files\Roxio\OEM\AudioCore\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\OEM\DLLShared\;C:\Program Files\Common Files\Roxio Shared\OEM\DLLShared\;C:\Program Files\Common Files\Roxio Shared\OEM\12.0\DLLShared\;C:\Program Files\Roxio\OEM\AudioCore\;C:\WINDOWS\system32\WindowsPowerShell\v1.0
java.io.tmpdir = D:\usr\sap\NSP\tmp\
Required system resources are missing or not available:
Import directory 'C:\SAPNW\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP2' does not have valid structure of subdirectories;
Import directory 'C:\SAPNW\NWASABAPTRIAL70206\SAP_NetWeaver_702e_Export\DATA_UNITS\EXP3' does not have valid structure of subdirectories.
I checked the EXP2 and EXP3 directories and there is a DB directory and some LABEL and PRODLABEL files there.
thanks,

Queries related to ABAP Programs migration to SAP ECC 6.0

We are planning to re-implement SAP using SAP ECC 6.0 We are currently using SAP R3 Version 4.7
Regarding migration of existing ABAP Programs and data, I have some queries which may kindly be answered by any of the experts of this forum.
1. I have heard that SAP ECC 6.0 or SAP Netweaver 7.0 will never support BDC programs. To upload data into SAP, BAPI is the preferred option. Is that true?
2. In ABAP Programming, relational operator < (less than), > (greater than), <= (less than or equal to) etc are not supported by SAP Netweaver 7.0. In stead, operator contants LT, GT, LE etc must be used. Other wise, SAP reports syntax error. Is thar true?
3. Screens (Dynpros) have been fully programmed in ABAP Objects in almost all programs related to functional modules (SD,MM,PP,FI/CO etc) in SAP ECC 6.0. Is that true?
4. Programs written in SAP R/3 Version 4.7 will report syntax errors when that program is compiled as it is in SAP Netweaver. Is that true?
I request you to kindly reply for these four queries at the earliest.
Thanking you,
K. RANGARAJAN
ABAP Programmer

SAP ECC6.0 will be supporting BDC programs too.But ,apart from this there are other options like LSMW ,BAPI, ECATT tool
which serves the same purpose . It doesnot mean that SAP wont support BDC.
Coming to relational operators u can use both of them but preferred is operator contants LT, GT, LE.
If there are any obsolete statements or any Obsolete function modules used in version4.7 U will get syntax errors or unicode errors.
Regards,
Lakshman.

Migration of SAP From Windows to AIX

Gurus
I need information regrading migration of SAP ECC 6.0 on Oracle from Windows to AIX.
Thanks

Hi ,
You will find information in the System Copy Guide .
https://websmp104.sap-ag.de/instguidesNW70
SAP NetWeaver 7.0 (2004s) --> Installation ---> <download the suitable system copy guide>
You would also find lot of SAP Notes , go through them and let us know if you have any specific questions/concern.
Regards,
Neel

Migration from SAP BC To SAP P.I

HI Experts ,
I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!
1) What kind of challenges can be faced during migration from BC to XI?
2) What is the best practise for doing the same?
3) Can you share some scenario from where i can have some idea how to do migration?
4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?
Would appreciate your valuable inputs on the same!
I have read How to guide docs on how to do migration from BC to XI but not convinced with the content
Regards
Saras Jain

Hi Saras,
I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.
Scenario
SAP Business Connector enables data exchange between an SAP system and
external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)
replaces SAP Business Connector (SAP BC).
We distinguish between standard scenarios (that do not contain customer-specific
development) and individual scenarios (that do contain services or mappings created
by the customer). The following sections describe how to migrate both types of
scenarios to SAP XI.
Scenario 1 (IDoc HTTP, HTTP IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner by using HTTP.
An external business partner sends an XML document by using HTTP to SAP BC or
to SAP XI. The document is converted to an IDoc and sent to a connected SAP
system in the internal system landscape.
Scenario 2 (IDoc Mail, Mail IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner as an e-mail.
An external business partner sends an e-mail to SAP BC or to SAP XI. The
document is converted to an IDoc and sent to a connected SAP system in the
internal system landscape.
Flow Services
Flow services are services that are written in the proprietary graphical-based flow
language of SAP BC.
Java Services
Java services are services that are written in the Java language.
There are several platforms that support Java, including SAP XI. However, the data
model used in the Java services in SAP BC is proprietary.
Stylesheet Transformations
Stylesheet transformations are often used for mapping purposes. They take an XML
document as input, convert it according to rules defined in the stylesheet, which is
also an XML document, and produce an XML document as output.
The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World
Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.
SAP NetWeaver is the open integration and application platform from SAP. With
NetWeaver 04, there is a significant overlap between the functions of SAP
NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI
as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,
mapping, routing, and adapters to connect to a large number of third-party back-end
systems. SAP BC is therefore no longer needed. New or updated SAP solutions are
based on SAP NetWeaver. Customers looking for a strategic integration solution for
the complete application landscape should therefore now favor SAP NetWeaver.
The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP
BC has not been developed further since this release. SAP BC is not released for
any further platforms (such as Windows 2003) and does not support any further JDK
versions, including the current version (Version 1.4).
For information about the supported SAP BC versions, JDKs, and operating systems,
see SAP Note 309834. For information about the support and maintenance strategy
for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be
aware of the following:
A solution based on SAP BC cannot be a strategic, long-term solution.
A solution based on SAP BC is based on technology that was implemented in
2003 and that is no longer further developed.
SAP BC is supported on limited platforms and for limited JDKs only. Vendor
support for some of these platforms and JDK versions will soon be
discontinued.
SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based
on webMethods proprietary Integration Server, whereas SAP NetWeaver is based
on open standards, such as BPEL4WS (business process execution language for
web services). Therefore, only parts of an SAP BC implementation, such as XSLT
mappings, can be migrated to a solution based on SAP NetWeaver. Any custom
programming based on SAP BC, such as SAP BC flow language, is unlikely to be
reusable in the SAP NetWeaver context.
Purpose of this Migration Guide
The purpose of this migration guide is to provide scenario-based descriptions of the
migration from a companys system landscape that uses SAP BC to exchange
documents with business partners, to a system landscape that uses SAP XI instead.
This migration guide outlines, for certain scenarios, the individual steps a company
has to take to replace an existing SAP BC implementation with SAP XI.
The basic steps in the back-end systems are:
Defining the logical systems
Maintaining the ALE distribution model
Maintaining partner profiles and EDI ports
Maintaining RFC destinations
The basic steps in the SAP XI system are:
Maintaining the System Landscape Directory
Configuring the IDoc adapter
Maintaining the receiver determinations, interface determinations, and
interface agreements
Maintaining the communication channels
The type of scenario to migrate typically has an impact on the communication channels only.
Scenario 1 IDoc/HTTP
IDoc HTTP Using SAP BC
Within the system landscape of a company, an SAP system sends an IDoc
asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML
document. The fields of the IDoc are not modified, that is, the conversion does not
involve any mapping of source fields to target fields. After conversion, SAP BC uses
HTTP to send the XML document synchronously to an external URL of a business
partner.
System Landscape
An SAP system and SAP BC are installed within the same system landscape
of a company.
The following information is defined in the SAP system to allow data
exchange between the SAP system and SAP BC:
o An RFC destination and a logical system for SAP BC
o The distribution model is maintained, if necessary
The following information is defined in SAP BC:
o An SAP server with an alias is defined. For this SAP server, the
information that the SAP BC requires to connect to the SAP system is
specified.
o A listener is configured to listen to requests from the SAP system.
o A routing rule with the transport type XML is configured for the
specific sender, receiver, and message type. The routing rule
determines how a message is to be routed and where it is to be routed
to. The scenario described does not use an ACL, (Access Control List
to restrict execution permissions for this routing rule) or pre-processing
or post-processing SAP BC services.
4.2 IDoc HTTP Using SAP XI
Check the prerequisites described above under Prerequisites for Standard
Scenarios.
The IDoc adapter is used to receive an IDoc from an SAP back-end system and
convert it to XML.
The adapter used to post this XML to an external destination is the plain HTTP
adapter.
To set up the communication channel, perform the following steps:
1. Locate the routing rule in SAP
Business Connector.
In the Administration View, choose
Adapters Routing to navigate to
Routing Rules.
2. Select the details of the relevant routing rule.
To display the details, choose the green triangle (Edit).
Transport is typically set to XML and a URL is specified. You can use this
URL in your SAP XI settings.In some cases, Transport is set to
B2B Service and the parameters Server Alias, Folder and Service
exist. This is the same as when Transport is set to XML and has the
URL http://<serverhost>:<port>/invoke/<folder>/<service>.
You can find <serverhost> and<port> in the definition of the
remote server under Settings >Remote Server in the Administration
View.
3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.
Use the following settings:
Adapter Type: HTTP Receiver
Transport Protocol: HTTP 1.0
Message Protocol: XI Payload in HTTP Body
Adapter Engine: Integration Server
Addressing Type: URL Address
Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy
Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.
regards
Aashish Sinha
P : Reward points if helpful

Which patch to begin with SAP netweaver 2004s - BI 7.0

Hi every body,
I have some questions on this new BW release.
1)Which patch could correct the most problems on BI 7.0?
2)Do the configuration of instal an 7.O with using the 3.5 functionalities, means that we have not the 7.0 bugs on the new objects (DTP, datastore, ...)because we do not use them ?
3)In an upgrade configuration, do it exist a tool or anything which permit to upgrade, for example ODS into Datastore or update rule into DTP and so on ?
Thanks a lot for your answers
best regards
Ulrich LARCHER

Hi Ulrich,
ad 1.)
We (SAP) recommend to start with SPS7, which greatly improves stability especially in the frontend area. For the backend feature, you could easily go with SPS6.
ad 2.)
pretty much, yet there might be some hiccups. In general, most customers with a technical upgrade (upgrade to SAP NetWeaver 2004s, yet using mainly BW 3.5 features) do not report too many issues.
ad 3.)
for your examples given, there are kind of migration tools. A former ODS Object will automatically be an DataStore Object; a DTP can be created with an update rule as template starting from SPS7 (please be aware that the conversion of a routine can only happen on a best guess base - you will have to check the results in case of extensive / complex ABAP routines). In general, you will also find an extensive description about the migration support tools for SAP NetWeaver in the SPS7 version of the documentation. We have included a dedicated chapter in the technical operation manual (TOM) for most of the features that are affected by migration.
Cheers
SAP NetWeaver 2004s Ramp-Up BI Back Office

SAP Netweaver 7.01 trail on a dual boot MacBook Pro

Hello, I would like to know if SAP Netweaver will work on a MacBook Pro. I am planning to dual boot Windows 7 basic using a software called Bootcamp which is native to Mac OS X 10.5
System Spec :
Model Name:     MacBook Pro
Model Identifier:     MacBookPro5,1
Processor Name:     Intel Core 2 Duo
Processor Speed:     2.4 GHz
Number Of Processors:     1
Total Number Of Cores:     2
L2 Cache:     3 MB
Memory:     2 GB
Bus Speed:     1.07 GHz
*I have two Questions :*
1) Will SAP Netweaver 7.01 trail work with Windows 7 32 bit basic edition ?
2) Are the system spec above sufficient to run SAP ?
Thank's for your time.

I'm having lots of problems installing SAP NetWeaver 7.01 SR1 on my MacBook with WinXP Pro SP2 running in Parallels. I have allocated 1 GB RAM to WinXP and changed the Paging to 4096 MB which is the maximum. I have over 150 GB allocated to the C: drive.
I also changed the number of processes to 1. I am assuming that the change to the C:\Program Files\sapinst_instdir\NW701\AS-ABAP\ADA\CENTRAL\inifile.xml file will do the trick.
      <fld name="migmonJobNum">
        <properties>
          <property name ="doc-long" value ="
Number of parallel Migration Monitor jobs." />
        </properties>
        <strval><![CDATA[1]]>
        </strval>
      </fld>
I tried to continue the old installation that I had to stop since it had taken more than 12 hours on the Phase 12 of 27 - Create Database Schema step. If this does not work (this is my third hard time trying to do this after having to uninstall), I think I will get VMware and just install this on the Windows 2003 Server if I can't get this working on XP.
Since you were able to get it working on XP, technically, I should be able to even though it's running in Parallels. There must be a way to monitor the MaxDB database activity to see why the Create Database Schema is taking so long.
Thanks for you help in advance,
Jay

SAP NetWeaver 7.30 High-Availability installation without MSCS

Hi all,
Do we have any option to install SAP NetWeaver 7.30 High-Availability System on the third-party cluster solution, except for MS Cluster Service?
I tried to install the first cluster node without MSCS configuration, however, sapinst.exe checks whether we already set up MSCS on this node, then installer aborted.
I'd like to know the way to disable this checks. (Or, way to mimic the installer as if MSCS cluster configuration was done.)
If unavailable, I have to install MSCS first, and SAP NetWeaver, then also have to uninstall MSCS instead of out cluster software;
It seems to me no sense.
Best regards,

Hi Peter,
Thanks for your quick response.
It is disappointed for me that HA Installation is tightly combined with MSCS.
Do we have a way to migrate from other installation scenario to High-Availability?
For example, once we install ASCS instance as distributed system, then migrate
it for High-Availability usage, leveraged by profile updates and so on?
I'm not sure how High-Availability installation is different from other installation
scenario except for installation path and hostname to be used for connection.
Best regards,

Migration of SAP Netweaver

Similar Messages

Maybe you are looking for