Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

Please note:
If you are already using theGuard! SmartChange 2015 and you want to change to REALTECH SmartChange 2019, please proceed here   

 

To install REALTECH SmartChange, please execute the following steps on every system.

  1. Decompress all transport files downloaded and copy them into the transport directories of all involved systems.

    Please execute step 2) 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 REALTECH SmartChange Objects

    1. Import request RTCK900139 - SmartChange (ServicePack v5.5.0.0) into any of the clients.

    2. Import request RTCK900140 - SmartChange (Communication Roles v5.5.0.0) into client '000'.

    3. Import request RTCK900141 - SmartChange (Application Roles v5.5.0.0) into all work clients.

    4. Import request RTCK900142 - SmartChange (Update-Assistant v5.5.0.0) into any of the clients.

    5. Install all hotfix transport requests based in SP4 into any of the clients.

  4. Please execute steps 4 - 9 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").

  5. 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").

  6. Import of BADI-Implementations

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

  7. Optional: The installation of REALTECH SmartChange Odata Services is necessary if you use the TM Integration Framework for integration to ITSM systems , as well as you use the SmartChange Apps.

    1. Import request RTCK900145 - SmartChange (OData Hub_Registration v5.5.0.0)
      If you use a SAP Gateway hub, please import request into the SAP Gateway hub. If you do not use a SAP Gateway hub, please import request into the client ‘000’ of the TM Server

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

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

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

  11. Please execute steps 12 - 15 only if you want to use Synchronization Management:

  12. Import request RTCK900143 - SmartChange (Extension Indexes v5.5.0.0) into any of the clients.

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

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

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

Update

Please note:
There is a new license model introduced with SmartChange that requires new license keys if you are upgrading from theGuard! Transport Manager or theGuard! SyncAssist to SmartChange. In this case, please contact your local REALTECH Sales Representative before starting the migration.

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

Please note:
If you are using both products, they will both be upgraded simultaneously to REALTECH SmartChange, there is no possibility to upgrade just one product.

If you are already on theGuard! SmartChange 2015, there are no special requirements.

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

  1. Import of REALTECH SmartChange 2019 objects

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

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

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

    1. Import request RTCK900142 - SmartChange (Update-Assistant v5.5.0.0) into any of the clients.

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

    3. Generate the 'Update Queue'.

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

  3. 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).

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

  5. For systems that are managed with Transport Management and Synchronization Management:
    Import request RTCK900141 - SmartChange (Application Roles v5.5.0.0) into all Work Clients.

  6. For systems only managed by Synchronization Management:

    Import of REALTECH SmartChange Objects

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

    2. Import request RTCK900139 - SmartChange (ServicePack v5.5.0.0) into any client of all involved systems.

    3. Import request RTCK900141 - SmartChange (Application Roles v5.5.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. 

On this page

  • No labels