Hardware Migration

Prerequisites

· Download required software dump and patches from SAP  market place

· Compare filesystem area with supply source SAP system database

· Set paage memory

Actions on Target server

· Install Oracle RDBMS software

· Apply RDBMS patch to the Source DB patch level

· Install SAP NW2004 with ABAP content

· Install Java add in on ABAP

· Request and apply SAP license for new hardware

· Start J2EE on new server

· Upgrade Kernel to the Source Kernel patch level

· Take full backup of database

· Take java filesystem backup

· Bring down target SAP server alongside with DB

· Stop all the services associated to oracle and SAP

· Delete datafiles from sapdatas , origlogs and mirrlogs in target system

Actions on source server

· Request Downtime for source SAP server

· Suspend jobs the usage of SAP report btctrns1 in source server

· Bring down SAP alongside with DB in source server

· Stop all services associated to Oracle and SAP in source server

· Start zipping of sapdatas, origlogs and mirrorlogs

· Zip J2EE filesystem j2EE,SCS, SYS folders.

· Copy the zipped files manually by way of Wan to target server

Actions on target server

· Unzip the zipped files and copy or overwrite them in accordance to the structure

· Change hostname in ABAP in accordance to SAP Note 8307

· Change hostname in RZ70

· Change hostname in j2ee config tool in accordance to SAP Note 757692

· Start DB,

· Delete source ops$ customers and recreate for Target server and change the password

· Start SAP and J2EE

· Re Install SAP license

· Reconfigure SMLG,RZ10,RZ04,RZ12, DB13 etc.. accordingly

· Check RFC connections and reconfigure if required

· Reconfigure STMS

· Reconfigure SLD and JCO destinations the usage of visual admin tool.

· Restart cluster for adjustments to be affected

· Check SLD and portal

· In SLD exchange hostname in profile and server settings if required

· Reschedule jobs the usage of SAP report btctrns2

· Configure backup strategy

· Take full database backup alongside with J2EE filesystem. 

Procedure for connecting R3 with PI

Below is the method to create RFC connection between ECC and PI system.
This is required throughout PI Installation or after PI system copy.

Actions to be accomplished in PI system

1.Create RFC connection for R3 the usage of T-Code sm59

2.Create a port the use of T-Code IDX1

Use R3 RFC destination

Actions to be finished In R3 server

1.create a logical system for XI system the use of BD54 T-Code

2.Create RFC destination to PI server the use of sm59 T-Code

3.create partner profile for the logical system the use of T-Code WE20

ALL About TSK files

ALL About TSK files

These TSK files are pure text files and contain an entry for every action within the form:

with = T, D, P, I, V (Table structure, Data, Primary key, Index, View)

= C, I, E (Create, Import, Export),

= xeq, ok, err

For the first time, R3load reads a TSK file completely, closes the file, renames it during a TSK.bck (for example, SAPSDIC.TSK.bck) and opens the TSK file for writing. After each execution an entry of the action is written with the corresponding status.

If all actions are processed, or if the unprocessed actions might be written back to the TSK file after an error, the TSK.bck file is deleted. During start-up, if R3load also finds a TSK.bck addition to a TSK file , it terminates immediately with a corresponding error message, as this either means an R3load process is running and is processing this request, or that a significant error has already occurred (possibly with a core dump) which will not be eliminated during the restart, but requires user intervention (for example, a full filing system , corrupt files after disk crash) When the error has been eliminated you want to merge the TSK file and therefore the TSK.bck file before or during the restart of the R3load.

There are several options available to do this:

o Manual: The TSK file contains current entries for all objects that are processed. The bck file contains entries for all objects, however, the status could also be outdated. When you merge both the files, the entries missing within the TSK file must be manually transferred from the bck file. You must then rename the bck file.

o Call R3load with the extra option '-merge_bck' (in this case, all missing entries are set to the status 'err'). This consolidates the TSK file and also the bck file and the R3load for the export or

import is started. If the R3load processes are started by the MigrationMonitor, you'll configure the extra R3load option within the *_monitor_cmd.properties file.

o As of a particular patch level in Release 6.40, the R3load contains the choice '-merge_only'. If you call the R3load with the choice '-merge_only , only the TSK file and therefore the bck file are

merged, but the export or import isn't started. You can use the choice 'R3load -h' to see whether the R3load contains the choice '-merge_only'.

Activating SAP* User in Visual Admin in SAP

Activating SAP* User in Visual Admin in SAP

Use:
In critical situations where you configured user management incorrectly and may not be able to log on to any applications, or all administrator users are locked, you'll activate the emergency user SAP* to permit you to log on to applications, especially the configuration tools, and alter the configuration. The SAP* user has full administrator authorizations. For security reasons, the SAP* user doesn't have a default password, so you want to specify a password once you activate the user.

Procedure

1. Activate the SAP* user:

a. Start the config tool for editing UME

properties as described in Editing UME Properties.

Editing UME Setting:

1. Start the Config Tool by executing

\j2ee\configtool\configtool.bat.

2. within the tree, navigate to Global server configuration services com.sap.security.core.ume.service.

The list of UME properties appears.


¡ To change the value of a property:

i. Select the property in the list.

ii. In Value at rock bottom of the screen, enter the new value that you simply want to assign to the property.

iii. Choose Set.

iv. Choose (Apply changes).


To restore a property to its default value:

i. Select the property in the list.

ii. Choose Restore to default.

iii. Choose (Apply changes).


To restore all properties to their default values:

i. Choose Restore all to default.

3. Restart the nodes in the cluster for the changes to take effect.


b. Set the following properties:

Property Value Comment

ume.superadmin.activated true This activates the SAP* user.

ume.superadmin.password

Enter any password of your choice. This defines the password for the SAP* user.

c. Restart the Java application server.

The SAP* user is now activated. While it's activated, all other users are deactivated. You can only log on

with the SAP* user.


2. Fix your configuration as needed , logging on with the user ID SAP*and the password you specified.

For example, to go online to the Visual Administrator to unlock users or create a replacement administrator user,

proceed as follows:

i. Start the Visual Administrator by executing \j2ee\admin\go.bat.

ii. If you've got not already done so, you've got to make a replacement connection entry during which you specify SAP* because the user name.

For more information, see Creating a replacement Connection Entry.

iii. within the hook up with SAP J2EE Engine dialog, select the connection entry you created and choose Connect.

iv. Enter the password you laid out in the UMEproperties and choose Connect.

v. Do whatever is important to repair your configuration. For example, unlock all administrator users.

Similarly, you'll log on to the UME administration console using the SAP* user.


3. once you have fixed your configuration, deactivate the SAP* user again.

a. Start the config tool inorder to edit UME properties as described in Editing UME Properties section.

b. Set the property ume.superadmin activated to false.

b. Restart the Java application server.