on 01-19-2010 1:48 PM
Dear Friends,
I have to do system copy for dual stack ABAP+JAVA.I know how to do the ABAP system copy but dont know about java sys copy.
So kindly provide notes or documentation to proceed for java system copy.
thanks in advance.
Regards
Jiggi
There is a kind of shortcut which I am using for test systems, and it is working fine, though it is NOT SUPPORTED (it is not by-the-book): if you retain the same db schema, you can refresh the database and import previously prepared license keys of the copied system (either by re-installing them, or by importing them into the SAPLIKEY table), making necessary post-installation steps (SE06, BDLS, TMS, RZ10 profiles, application server and load balancing groups re-configuration, etc) and making changes in Java stack using Config Tool (instance properties, message server, java parameters if necessary) by hand and in file system (Config Tool first, in order to make it work):
...\j2ee\configtool\config.properties
...\j2ee\cluster\instance.properties
...\j2ee\cluster\bootstrap\bootstrap.properties
...\j2ee\JSPM\data\variables\Jspm.J2EE.DataModel.xml
...\j2ee\templateconfigurator.properties
...\j2ee\ctc\config.properties
...\j2ee\deploying\rdb.properties
...\j2ee\SDM\program\localsdmgui.properties
...\j2ee\admin\cfg\adminCFG.properties
where in Configuration Editor you have to make correct settings under cluster_data (instance properties, bootstrap, dispatcher and server (secure store settings under ID<NR> / kernel / ConfigurationManager properties)), but also in other items if necessary (e.g. CTC, rfcengine_global). I've even tried a more simple and probably the fastest way (and more unsupported): making system copy using storage mirroring (without changing SID and system number, just changing host name and IP address), and it also works fine (with former post-installation procedure about Java). This is certainly not recommended for production systems or landscapes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Download the System copy guide from service market place.
https://websmp108.sap-ag.de/instguides
Look for Java System copy guide under installations under NW 7.0( of whichever appllies)
Gerard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> I am not using export/import method for system copy but going to use copy with database refresh method so in that case which folders are necessary for java system copy from source system.
Java must be copied with sapinst, you can't just copy files.
you can, however, recover the database but you must use sapinst to create an export and sapinst on the target system for the import.
Java stores SID, hostname and other things in many different files on the filesystem and in the database. It's not supported to change those manually, sapinst does the magic for you.
Markus
Hello,
A production migration consist in at least 2 iteration (one test migration and one final migration).
After first iteration sapinst already installed SAP software. The question is now what can be the process for the final migration:
the existing SAP system from the target host is completely removed and installed again during the final migration?
Or how can be avoid reinstalling of software and coping only the database?
Thank you,
Laurentiu
> the existing SAP system from the target host is completely removed and installed again during the final migration?
Yes.
> Or how can be avoid reinstalling of software and coping only the database?
As I wrote before, Java is different than ABAP, Java stores many settings on the filesystem. If you don't use sapinst your can't make sure the database content and the filesystem contentn is in sync.
Markus
Just to clearify:
you can use Backup/Restore the same way you are used to for the database.
But you need a JAVA Export (which is not related to
the DB but to Filesystem-Java-Repository-and-executables stuff) in addition.
This part corresponds to the JAVA CD in the installation (not the db-export).
You do this with sapinst on the SOURCE.
You need to de-install the target before you can do the re-install,
but you can keep the installed ORACLE_HOME.
In the Installation of the target, select DB-specific method, which will stop at a place,
where you do the restore an bring the DB to work the same way you are used to.
After the installation, your profiles will be install-resetted (so backup them before) and
your kernel might be a fresh copy from the CDs, so better replace the archives on
the Kernel CD with current archives from SAPNET or the ones, that correspond to your
intended patchlevel.
Volker
Hi,
For dual stack system, you have to export the java part from the source system first. Then when you will do the target part installation then sapinst will ask for export then give path to this export directory. Rest will be same.
You can check system copy guide for dual stack system in http://service.sap.com/instguides.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.