Documente Academic
Documente Profesional
Documente Cultură
NetWeaver
2004s SR2
n When you perform a system copy, all software units or usage types in the
source system are copied
to the target system. This means that none of the usage types in the target
system can be excluded
from the system copy, nor can you select usage types.
n Dos and Don'ts for system copy:
l Do:
uSave configuration data and runtime data in the J2EE database only. If you
absolutely need
to save this data to the file system level, you must use the Software
Deployment Manager
(SDM) to save the data.
uFollow the Open SQL standard.
uMake sure that all communication runs through the database pool.
l Don't:
uSave any system and infrastructure-specific data in business objects. Use a
pointer to the
central storage of such information, for example:
t SAP SystemID and SID (SAPSID =SID=system name)
t Host name
t IP addresses
t Services and Ports
t Logical destinations and logical system names
t Other technical infrastructure names
uUse file system persistency.
uSet up dependencies between Java and ABAP.
uTry to copy the Java part of an ABAP+Java system to a Java standalone
system or vice versa.
2 Planning
This section describes how to plan your system copy.
Recommendation
We recommend that you make a system copy in order to set up a test, demo,
training, or standby
system.
Only valid for: Oracle
You cannot create standby systems with a system copy. You should perform
upgrades in a test system
first. This way you can identify customer-specific problems that might result
from modifications.
End of: Oracle
The SAP system release of the source and target systems must be the same.
Note
l Unload the source database and load the data into the target database
n The database-independent procedure [page 56] using SAP tools
Use this method if database-specific methods are either not available or not
suitable.
Note
and Windows
UNIX or Windows Use one of the following:
n
Only valid for: UNIX
n
Only valid for: Windows
n
Only valid for: Windows