Red Hat CERTIFICATE SYSTEM 6.0 - MIGRATION GUIDE Manuel d'utilisateur Page 32

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 36
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 31
Migrating SAP ERP 6.0 and IBM DB2 LUW version 9.1 from Solaris
10 Enterprise on Sun Fire T2000 to Red Hat Enterprise Linux
Advanced Platform for SAP applications on IBM System x3650 M2
with Intel Xeon processor
32
Appendix C. Moving the central instance from Solaris 10 on the Sun
Fire T2000 to Red Hat Enterprise Linux Advanced Platform for SAP
applications on the IBM System x3650 M2
This procedure assumes that you have a correctly configured and
working distributed system based on ABAP, using SAP ERP 6.0 and
the 7.01 version of the NetWeaver kernel, and that you have
followed the preparations detailed above. Therefore, we assume
that matters such as configuring the firewall to allow the global and
profile directories have already been attended to. In particular, we
assume that you have Solution Manager installed and the system
landscape configured.
In the description below, we provide names and part numbers of
the specific DVDs and CDs we used for this process. For
convenience, we copied the ISO images to a file server and
mounted them on the target server. However, that does not
change the procedures below.
During the course of this migration, you will need the SAP
Cryptographic Library. If you do not already have it, you can
download it from https://service.sap.com/swdc (Login required).
Select Download, and select SAP Cryptographic Software. When we
downloaded the version for Linux, its file name was 90000115.SAR.
1. Log into the current central instance server, the Sun Fire
T2000, using the <SAPSID>adm account, and perform the
following steps:
a) Use the command cat /etc/group to get the group
id for the sapsys group. You will use this later.
b) Use the command cat /etc/passwd to get the user
ID the <SAPSID>adm account. You will use this
later.
c) Type stopsap all to shutdown the SAP system. At
this point, the T2000 is no longer part of this
process.
2. Log into the database instance server, the IBM x3850 M2,
using the <SAPSID>adm account:
a) Type stopdb to shutdown the database.
b) Optionally, make a safe copy of the existing
/sapmnt/<SAPSID>/profile directory.
c) Delete <SAPSID>_DVEBMGS00_<HOSTNAME> and
START_DVEBMGS00_<T2000 HOSTNAME> files.
Vue de la page 31
1 2 ... 27 28 29 30 31 32 33 34 35 36

Commentaires sur ces manuels

Pas de commentaire