Page Comparison

Prerequisites

Download all the relevant transport requests from our Download area.

Language Support

Languages supported: English, German and Japanese.

Installation

This chapter contains any necessary pre-installation steps, installation steps and post-installation steps.

In the last 2 scenarios, as there is a new license model introduced with SmartChange that requires new license keys, please contact your local REALTECH Sales Representative before starting the migration.

To install theGuard! SmartChange, please execute the following steps on every system

1. Download the latest Service Pack and Hotfix. The Service Pack includes all necessary components for a new installation.

2. Decompress all transport files downloaded and copy them into the transport directories of all involved systems.
   
   Please execute step

1. 3) only, if you want to use Synchronization Management and only on systems, which are actively involved into the synchronization process:
   

2. Set tp Parameter VERS_AT_IMP to ALWAYS for all systems (refer to Manual "Synchronization Management").
   

3. Import of theGuard! SmartChange Objects

   1. Import request SR1K900050 - SmartChange (Repository v5.2.0.0) into any of the clients.

   2. Import request SR1K900053 - SmartChange (Update-Assistant v5.2.0.0) into any of the clients.

   3. Import request SR1K900051 - SmartChange (Communication Roles v5.2.0.0) into client '000'.

   4. Import request SR1K900052 - SmartChange (Application Roles v5.2.0.0) into all Work Clients.

   5. Install all hotfix transport requests based in SP2.
      

4. Please execute steps

1. 5 -

1. 10 only, if you want to use Transport Management:
   Call transaction ‘/RTC/TM_INI’ in client '000' of every system. This will create an RFC destination to the TM Server System and the required service user with the specified role (refer to manual "Transport Management").
   

2. Call transaction '/RTC/TM_INI' in all working clients of the TM system. This will create a local RFC destination and the required service user with the specified role (refer to manual "Transport Management").
   

3. Import of BADI-Implementations

   1. Import request SR0K900045 - SmartChange (BADI Activation v5.2.0.0) into any of the clients of the involved development systems.
      

4. Optional: Install the online documentation (refer to manual "Transport Management")
   

5. Assign role '/RTC/TM_ALL' to your user. Log out and log in again.
   

6. Call transaction '/RTC/TM' and proceed with the configuration (refer to manual "Transport Management").
   

7. Please execute steps

1. 11 - 13 only if you want to use Synchronization Management:
   Import request SR1K900054 - SmartChange (Extension Indexes v5.2.0.0) into any of the clients.

11.   Establish the required Trusted Relationships (refer to manual "Synchronization Management").

12.   Assign role /RTC/SA_ADMIN to the user, responsible for the further configuration of Synchronization Management (refer to manual "Synchronization Management").

13.   Call transaction '/RTC/SA' on the central Synchronization Management Console and proceed with the configuration (refer to manual "Synchronization Management")

Update

 In order to upgrade theGuard! TransportManager, theGuard! SyncAssist or SmartChange 2015 to SmartChange 2019, please execute the following steps on every system:

If your current installation of TransportManager is not on Release 5.6, please update to that level before starting the migration. The required service packs can be downloaded in our Download area

If you are using TransportManager or SmartChange Transport Management the following upgrade procedure must be applied (Steps 3-7):

1. Import of SmartChange 2019 objects

   1. Decompress all transport files downloaded previously and copy these files into the transport directoryof your TM Server.

   2. Copy the control file 'tm_upd.txt' to the transport directory 'usr/sap/trans/tmp' of your TransportManager Servers.
      

2. Start the Update Process on the TM-Server using the 'Update Assistant' (refer to manual "Transport Management").

1. 1. Call transaction '/RTC/TM_UPDATE' on the TM Server.

   2. Generate the 'Update Queue'.

   3. Start the Import as you are used to when starting the personal queue.

2. After the imports have been finished, start the Scheduling Monitor and check if all systems are unlocked again (except the ones which were explicitly locked before).
   

3. Optional: Install the online documentation (refer to manual "Transport Management").
   

4. For systems that are managed with TransportManager and Synchronization Management:
   Import request SR1K900052 - SmartChange (Application Roles v5.2.0.0) into all Work Clients.
   

5. For systems only managed by Synchronization Management:
   
   Import of SmartChange 2019 Objects

   1. Decompress all transport files downloaded and copy these files into the transport directoriesof all involved systems.

   2. Import request SR1K900050 - SmartChange (Repository v5.2.0.0) into any client of all involved systems.

   3. Import request SR1K900052 - SmartChange (Application Roles v5.2.0.0) into all Work Clients of the involved systems.

Uninstall

Please execute the following steps:

1. Copy transport files of the ‘Uninstall’ Transport request into the transport directory of all affected systems.
   

2. On each system:

   1. Delete all Batch Jobs with Program Step ‘/RTC/TM*’, ‘/RTC/SA*’ or ‘/RTC/R_LIB_LAT*’, if exists

   2. Delete Loader15 Event (see TM BAdI Configuration value ‘Event ID’), deactivate the BADIs /RTC/TM_BEFORE_EXP1 and /RTC/TM_AFTER_EXP_01 and LAT Event ‘/RTC/LIB_TRIGGER_LAT’, if exists

   3. On client ‘000’: Delete user ZRTC4_TM_ADM and ZRTC_SA_ADM, if exists
      

3. On each TM-System:

   1. On each work client: Delete user ZRTC4_TM_ADM
      

4. To delete the Repository objects import the ‘Uninstall’ Transport request into all systems (on client ‘000’) and additionally in TM-System (on each work client). Use Import Option 'Ignore Non-Permitted Table Class' before performing the import. Hint: If the import ends with return code 8, you can safely ignore that.
   

5. Check on each system that there are no entries in DB Table ‘TADIR’ with OBJ_NAME ‘/RTC/*’ left over. Hint: If you use ABAP Suite on the considered system, you can safely ignore entries starting with OBJ_NAME ‘/RTC/AS*’, ‘/RTC/SV*’ and ‘/RTC/E_AS*’
   

6. Check that the User Roles, starting with ‘/RTC/TM*’ and ‘/RTC/SA*’, are completely deleted on each system (on client ‘000’) and on TM-System (on each work client).
   

7. Delete RFC-Destinations, starting with ZRTC4*, ZRTC_SA* and ZRTC_SC* on each system.