How to Update to Rev-Trac 8 SPS00. Document version: 00 8 SPS00. Copyright Revelation Software Concepts Pty Ltd. All rights reserved.

Transcription

1 Document version: 00 8 SPS00 Copyright Revelation Software Concepts Pty Ltd. All rights reserved.

2 Table of Contents Purpose... 1 What is new in Rev-Trac Rev-Trac rebranding... 2 Actions on Rev-Trac Requests... 2 Go-Live Orchestrator... 2 What was new in Rev-Trac Release Management... 3 Web GUI... 3 Rev-Trac Locking Workbench... 3 Systems grouping & system groups cross landscape locking... 3 Rev-Trac Support Package Stack... 4 Supported SAP Versions... 4 Update prerequisites... 5 Requirements for Rev-Trac ABAP... 5 Requirements for Rev-Trac Web GUI... 7 Requirements for Rev-Trac Web Application (xpack)... 7 Update planning... 8 Update procedure... 9 Step 1: Prepare for update... 9 Step 2: Import transport files... 9 Post update tasks...11 Common problems and solutions...12 Return code > 4 during data dictionary activation...12 Return code > 4 due to other reasons...12 Backout procedure...13 Restore Rev-Trac ABAP...13 Backout Rev-Trac Web Application (xpack)...14 Backout Rev-Trac Web GUI...14 Appendix 1. How to create a Rev-Trac diagnostics file...14 Appendix 2 Rev-Trac Licensing...15 Rev-Trac licensing enforcement...15 Obtain Rev-Trac license key...15 Upload Rev-Trac license key...15 Appendix 3. Import extra transport files...16 Appendix 4. Switch to automatic, on-approval background migration...17 Appendix 5. How to check your Rev-Trac field exits...18 Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page ii

3 Appendix 6. How to update the Rev-Trac Web Application (xpack)...20 Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page iii

4 Purpose This guide describes the steps to update from Rev-Trac 5.0 and higher to Rev-Trac 8 SPS00. It is intended for Rev-Trac system administrators. This guide is organised as follows: The Rev-Trac Support Package Stack section explains what a Rev-Trac SPS contains and the installation concept. The What is new in Rev-Trac 8 section explains new features that come with the new version. The Update prerequisites section contains the requirements before starting the update process. The Update planning section describes how to plan for the update process. The Update procedure section describes what to do before you install the update, the installation steps and how to check if the update is successful. The Post update tasks section describes post installation steps. The Common problems and solutions section contains information on troubleshooting problems that might occur during the installation. The Backout procedure section describes the steps to back out a Rev-Trac Support Package Stack update if it fails. Appendix 1 describes how to create a Rev-Trac diagnostics file. Appendix 2 is relevant if updating from Rev-Trac 5.0 SPS16 or earlier. It explains what Rev- Trac licensing enforcement involves and describes the steps to obtain a license key and upload the key. Appendix 3 is relevant if updating from Rev-Trac version prior to Rev-Trac 6.0. It describes how to import extra transport files, if required. Appendix 4 is relevant if updating from Rev-Trac 6.0 SPS04 or earlier. It describes how to switch from automatic, on-approval foreground migration to background migration, if required. Appendix 5 describes how to check whether you have customised Rev-Trac field exits. Appendix 6 describes how to update xpack. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 1

5 What is new in Rev-Trac 8 Rev-Trac rebranding Rev-Trac was rebranded in June-2018 hence the increment to version 8. The look of this document with new logos & layout is an example of one of the changes. From a technical perspective updating (standard ABAP) Rev-Trac to Rev-Trac 8, like Rev-Trac 7, retains the look and feel of Rev-Trac 6 so you can be confident that your existing use of Rev-Trac will not be disrupted by significant changes from a user perspective. On the other hand, the non-abap software (i.e. Web GUI and Salt) has undergone some significant changes. Whereas previously users were presented with the option of logging into Salt or Rev-Trac, the latest version has a single point of sign on to the Web GUI and what was formerly 'Salt' is now presented as 'Rev-Trac Insights'. Customers who have updated to the latest version of Salt will already be experiencing this. Note that this software is backwards compatible with previous versions of Rev-Trac however new features may not be available until standard Rev-Trac has been updated. Some terminology changes have been made. From a Rev-Trac administrator's point of view here are the key points. The application formerly known as 'Salt' has been renamed 'Rev-Trac Insights'. This application (a suite of tools for developers) is provided free of charge for all Rev-Trac 8 customers. What was formerly known as the 'Salt VM' or 'RSC Core VM' or 'Installation of Salt in your own Linux environment' is now known as the 'Rev-Trac Web Core'. Essentially the Rev-Trac Web Core is what you have after installing Salt (now known as Rev-Trac Insights) either by implementing as a VMWare appliance (i.e. virtual machine) or installed in your own Linux environment. Note that the Rev-Trac Web Core includes the Rev-Trac Web GUI and optionally can also include the legacy product 'RSC Web Application'. Actions on Rev-Trac Requests 'Actions' functionality is an improvement and replacement of Rev-Trac 'Pause' functionality, the purpose being to enable the planned interruption of transport importation to allow some manual procedure to take place. Actions can be added to a Rev-Trac requests in much the same way as transports. For more information refer to the Rev-Trac release notes (RFC Note 13964). Go-Live Orchestrator This provides a means for estimating the time it should take to import a Release. For more information refer to the Rev-Trac release notes (RFC Note 13968). Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 2

6 What was new in Rev-Trac 7 Release Management Release Management is a new feature that provides configuration capability and a workbench to assist users with the implementation of release management strategies. The release management configuration and workbench can be accessed via Rev-Trac console or transaction codes, /RSC/RI01 and /RSC/RI02 respectively. The configuration function allows users create release projects and their associated release and release change types. The Release Management Workbench offers drag-and-drop capability, release-change relationship automation and drill-down to requests details in Rev-Trac Workbench. Now, users can use the Release Management tool to manage releases and their associated changes, all under one roof. Prior to Rev-Trac 7, release management was handled via a manual process, requiring manually linking change requests and copying change transports to a release request. Web GUI Rev-Trac 7 Web GUI is a sophisticated web based approval front end that can be implemented as an option on desktops, laptops as well as mobile devices. With this option, end users are able to use their existing SAP login and approve migration statuses without having to log into SAP. Rev-Trac Locking Workbench A new Rev-Trac 'Locking' workbench has been introduced to centralise lock related administrative and configuration items. As of Rev-Trac 7 SPS02 the features listed below have been introduced into this workbench. 1. Display a queue where each entry is a request for Parallel development for a Rev-Trac Request/ABAP Object. These entries must be either Approved or Rejected by the Lock Administrator. Approving the Parallel development will result in the submission of the Parallel Development utility for that Rev-Trac Request/ABAP object. Note that the developer can submit a request for Parallel Development from the "Row Level Lock" tree report. 2. A report which displays all active Parallel developments. 3. A report which displays all active locks for a supplied Workbench Object. This workbench will be extended in future releases. Systems grouping & system groups cross landscape locking The functionality provides easier management of Rev-Trac locking behavior in N+1 development landscapes. For further details refer to release notes and Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 3

7 If you need more information about any of these features please contact Rev-Trac support at Rev-Trac Support Package Stack A Rev-Trac Support Package Stack (SPS) comprises of mandatory ABAP and optional non-abap components. Standard Rev-Trac: the ABAP package. The ABAP package is also known as Standard Rev-Trac. It contains instructions and transport files suitable for all SAP systems running SAP Basis 620 or higher, unicode or non-unicode. Lower SAP releases are not supported for this version. The latest Rev-Trac support stack can be imported into systems running Rev-Trac 5 or higher. It is not necessary to import any intermediate versions of the software. Note that all systems running under a Rev-Trac Master system must run the same version of the software. Running mixed software versions is not supported. Optional Rev-Trac: the non-abap components. The non-abap Rev-Trac software is an optional extra customers can install to obtain additional functionality. Over the years this software has evolved and there have been some name changes so here is an overview to more clearly explain what is involved in updating it. The first non-abap Rev-Trac software was the Rev-Trac 'Web Application' which provided the following applications: xpack (browser access), xreports (graphical reporting), xconnect (3rd party integration), xdeploy (non-sap changes) and OOPS+ (OOPS for non-abap transports). As of Rev-Trac 7 SPS03, the Rev-Trac 'Web Application' is only supported if it is running on the Rev- Trac Web Core (refer below for details). Note that SAP WAS, Apache Tomcat, ServletExec/IIS and other J2EE Web Servers will not be provided with updates from Rev-Trac 7 SPS03 onwards. The Rev-Trac Web Core is the latest version of Rev-Trac non-abap software and is implemented either as a VMWare Appliance provided by Rev-Trac or as a result of installing Salt (Rev-Trac Insights) on a customer's own Linux environment. The Rev-Trac Web Core was formerly known as the 'Salt VM', the RSC Core VM or 'Installing Salt in your own Linux environment'. The Rev-Trac Web Core implicitly includes Rev-Trac Insights (formerly known as Salt) and the Rev- Trac Web GUI. The Web GUI is a browser based user interface which enables users to perform web based approvals including migration approvals thus superseding xpack. The Web GUI is also the focal point for the more sophisticated functionality customers are increasingly requiring of Rev-Trac. For this reason customers are encouraged to implement the Rev-Trac Web Core. Over time the Rev-Trac Web Core will shift from being optional to essential. Finally, the Rev-Trac Web Core is the platform which can run the Rev-Trac Web Application for customers who still require it - typically for 3rd party integration. Customers stranded on old implementations of the Web Application should contact Rev-Trac support for assistance in converting their existing Web Application over to the new Rev-Trac Web Core platform. Supported SAP Versions As of Rev-Trac 7 SPS03, SAP Basis versions 610 or lower (such as 46C) are no longer supported. The minimum SAP Basis level supported by Rev-Trac 7 SPS03 is SAP Basis 620 (Unicode and Non- Unicode). Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 4

8 Update prerequisites Requirements for Rev-Trac ABAP WARNING: This software does not support SAP Basis 610 and earlier. 1. For each system where Rev-Trac is installed, copy into the transport file system the transport cofile and data file of each of the transports shown below. For SAP Basis 620 or higher Rev-Trac 8 SPS00 main transport Rev-Trac 8 SPS00 security profiles transport Rev-Trac 8 SPS00 supplement transport Transport A47K A47K A47K For each DEVELOPMENT system where Rev-Trac is installed execute transaction SE01 and look for the Rev-Trac Field Exits transport A47K If this transport is present in the system there is no need to reimport it. If transport A47K is not present in the system refer to Appendix 5. How to check your Rev-Trac field exits before proceeding further. For any development system which will require this transport, copy into the transport file system, the transport cofile and data file of the Field Exits transport. This transport contains RFC For more detail refer to Release Note For SAP Basis 620 or higher Create Rev-Trac Field Exits transport Transport A47K For each DEVELOPMENT system where Rev-Trac is installed execute transaction SE01 and look for the Rev-Trac BADI transport A47K If this transport is present in the system there is no need to reimport it. For any development system which will require this transport, copy into the transport file system the transport cofile and data file of the BADI transport. This transport contains RFC For more detail refer to Release Note For SAP Basis 620 or higher Create Rev-Trac BADI transport Transport A47K Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 5

9 4. Check if there are any supplements available in addition to the one included with RT 8 SPS00. Copy into the transport file system the corresponding transport cofiles and data files. Note: From time to time after an SPS release, Rev-Trac supplementary transport files are made available for download from the Rev-Trac support portal at Supplements usually include recommended changes for the SPS such as bug fixes or changes to ensure compatibility with the latest SAP software. 5. Confirm you have to administrator access to Rev-Trac by accessing user configuration from the Rev-Trac master console menu: Configuration -> Process -> Organisations -> Users. Your user ID should have 3 set for AdminAuth. 6. Confirm authorisation to use transaction STMS in all systems or TP command at the operating system level. 7. From Rev-Trac Console, go to menu path Administration > Rev-Trac version Print out the RSC Rev-Trac component version and dependencies report or the Rev-Trac 7 SPS Version Matrix report for identifying the SAP Basis version (in the 'Rel' column) of each system to confirm all candidate systems for the intended update are running on SAP Basis version 620 or higher. 8. If you are running Rev-Trac 5.0 SPS16 or earlier, you need to obtain a Rev-Trac license key before updating Rev-Trac. Please complete steps in the Obtain Rev-Trac license key section in Appendix 2. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 6

10 Requirements for Rev-Trac Web GUI 1. Check if you have the RSC Web Core installed Use transaction /n/rsc/cf10 or from Rev-Trac Console, go to menu path Configuration > Global > Global Parameters An entry in the Web GUI URL field indicates Rev-Trac Web Core is installed. 2. If there is an entry here, you should update Salt (Rev-Trac Insights) to the latest version. This will automatically include the latest version of the Rev-Trac Web GUI. This can be done preferably any time before the Rev-Trac update, or as soon as possible afterwards. For more information about how to do this refer to the "Salt Installation and Administration Guide" which can be downloaded from the support area of our web site. Note that in future this guide is likely to be renamed in accordance with Salt being renamed to 'Rev-Trac Insight'. 3. If there is no entry in the Web GUI URL field or, the field does not exist, download the document 'Rev-Trac Web GUI Administrator Guide' for information about how to implement the Rev-Trac Web GUI. At this point the Web GUI is strongly recommended but nevertheless optional. Requirements for Rev-Trac Web Application (xpack) 1. Check if you have the Rev-Trac Web Application (xpack) installed Use transaction /n/rsc/cf10 or from Rev-Trac Console, go to menu path Configuration > Global > Global Parameters An entry in the Web app URL field indicates The Rev-Trac Web Application (xpack) is installed. 2. If there is no entry in the Web app URL field, it means the Web Application has not been installed; therefore, no update is required. Otherwise, please refer to Appendix 6. How to update The Rev-Trac Web Application (xpack). Note: If you need to update xpack, you should do so as soon as possible after you have successfully updated Rev-Trac master and all systems under its control to version 8 SPS00. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 7

11 Update planning 1. Read through the release notes and this guide. 2. Obtain change management approvals required by your organisation. 3. Schedule a Rev-Trac outage to run the update. Choose a time that: Allows you to install the ABAP package in all systems as well as the Web Application (if required) during the same outage, AND 3.2. No Rev-Trac batch migration jobs or deployment jobs are scheduled to run. Note: Non-migration Rev-Trac jobs (for example, the OOPS refresh job) will fail in a safe manner if they continue to run during the update. 4. As Rev-Trac systems age they hold more information and retaining good performance requires that systems under Rev-Trac control are, if not well tuned, then at least not badly tuned. To this end it is recommended to execute transaction ST02 in each system and review the on screen report. Any indications of buffer swapping will be highlighted in red and should be brought to the attention of you Basis team to carry out the tuning adjustments required to eliminate the swapping. Note that this will improve performance for all processing on the affected systems - not just Rev-Trac performance. 5. Send s and use SM02 to send system messages to Rev-Trac users to notify them the date and time the system will be unavailable due to the installation. 6. If you are using Rev-Trac 6.0 SPS04 or earlier, complete steps in Appendix 4. Switch to automatic, on-approval background migration BEFORE updating Rev-Trac. 7. Read the Backout procedure section and gather any requirements (i.e. transports of earlier Rev-Trac versions) to perform a backout. 8. Raise a support case via the Rev-Trac support portal at providing the date of the planned update and include a fresh Rev-Trac diagnostics file. (See Appendix 1. How to create a Rev-Trac diagnostics file). 9. The Rev-Trac Web Application can only be updated to the latest support pack version if it is running on the Rev-Trac Web Core. The last update for legacy implementations of this product was Rev-Trac 7 SPS02. WARNING: Rev-Trac may not function correctly if systems within an installation are running different support package stack levels. A system dump may occur if someone is using Rev-Trac during the installation due to ABAP code changes. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 8

12 Update procedure Step 1: Prepare for update 1. Log into Rev-Trac as Rev-Trac administrator. 2. If you want to create versions of changes you have made directly to Rev-Trac (for example, a manual code change), you have to release their SAP change requests now To identify these SAP change requests, use transaction SE16 in each system to look up records in table TLOCK where Lock Key = /RSC/*. 3. Use transaction SM37 to check that no transport import or package deployment batch job is scheduled to run during the installation period. 4. Check that all RFCs used to poll other systems are available From Rev-Trac Console, go to menu path Administration > Health check Select only Perform RFC check and execute All systems listed in the Checking RFCs used to poll other systems section must be available and none is listed with a red traffic light. 5. Lock Rev-Trac to prevent users other than yourself from creating or changing Rev-Trac requests. From Rev-Trac Console, go to menu path Administration > Lock / Unlock. 6. Backup current Rev-Trac configuration settings in case a backout is required From Rev-Trac Console, go to menu path Configuration > Tools > Download/upload configuration Accept all defaults and execute Save the output to a file e.g. RT_Config_YYMMDD.txt. 7. Proceed to Step 2: Import transport files only if you have completed all the steps above. Step 2: Import transport files 1. If your Rev-Trac version is prior to Rev-Trac 6.0, import extra transport files as in the Appendix 3. Import extra transport files before continuing to the next step. 2. If you are using TP command to import the transports, include umodes If you are importing the package using transaction STMS, select the following options: - Import transport request again Overwrite Originals, and Overwrite Objects in Unconfirmed Repairs Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 9

13 4. Import the transports as listed below: For SAP Basis 620 or higher (Unicode and Non-Unicode) Transport Description Where A47K A47K A47K A47K A47K Rev-Trac 8 SPS00 main transport Rev-Trac 8 SPS00 security profiles transport Rev-Trac 8 SPS00 supplement transport Create Rev-Trac Field Exits transport Create Rev-Trac BADI transport Import into every system where Rev-Trac is installed. Typically import into client 000 but any client can be used. Import into every system where Rev-Trac is installed and into the following clients: In all systems, client 000. In the master system, the client where SAPconnect (transaction SCOT) is configured. In the development systems, any client where transports will be created. Import into every system where Rev-Trac is installed. Typically import into client 000 but any client can be used. IMPORTANT: Read Step 2 in the Requirements for Rev-Trac ABAP section on page 3 before you proceed. Only if required, import into each development system where Rev-Trac is installed. Typically import into client 000 but any client can be used. Read Step 3 in the Requirements for Rev-Trac ABAP section on page 3 before you proceed. Only if required, import into each development system where Rev-Trac is installed. Typically import into client 000 but any client can be used. 5. Proceed to the next step only if return code is <= 4. If return code is > 4, please refer to the Common problems and solutions section. 6. Import (typically into every system) any additional supplementary transports following the accompanying instructions. 7. If you were running Rev-Trac 5.0 SPS16 or earlier before the update, complete Upload Rev- Trac license key section of Appendix 2 before proceeding to the next step. 8. From Rev-Trac Console, go to menu path Configuration > Activate changes. Accept all defaults and execute. 9. From Rev-Trac Console, go to menu path Administration > Rev-Trac version The Rev-Trac 8 SPS Version Matrix report is displayed Verify that the SPS column shows the updated version for all systems. 10. If an inconsistency occurs in a system, perform the following steps: Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 10

14 10.1. Make sure you have activated changes as in step 8 above. Note: Failure to activate change is a common cause to reported version problems Perform RFC check as in Step 1: Prepare for update Import the correct transport file into the systems where they are different and make sure the return code is <= From Rev-Trac Console, go to menu path Configuration > Activate changes. Accept all defaults and execute From Rev-Trac Console, go to menu path Administration > Rev-Trac version The Rev-Trac 8 SPS Version Matrix report is displayed Verify that the SPS column shows the updated version for all systems If inconsistency still occurs, raise a support case via the Rev-Trac support portal at After all systems have been updated successfully and if you are using the Rev-Trac Web GUI, check to confirm there are no further available updates for Salt (in later versions, Salt has been renamed to Rev-Trac Insights). For further details refer to the heading "Requirements for Rev-Trac Web GUI" earlier in this document. Import any updates which are available. 12. After all systems have been updated successfully and if you have existing xpack installed, proceed to updating to the latest by following the instructions in Appendix 6. How to update xpack. 13. Proceed to the Post update tasks section only if ABAP update and xpack update (if applicable) have been completed successfully. Post update tasks 1. Unlock Rev-Trac and inform users that Rev-Trac is available again. 2. Attach a fresh Rev-Trac diagnostics file (see Appendix 1. How to create a Rev-Trac diagnostics file) to the relevant support case. 3. For information about installing Rev-Trac Web GUI, please request for assistance by raising a support case via the Rev-Trac support portal at 4. A new template file has been included with the SPS software download since RT7 SPS01. It has some advantages over the older version. Updating to the new version is optional. If you previously updated using the Rev-Trac 7 SPS01 or later template there is no need to update it again. For more details refer to note in the Rev-Trac 7 SPS01 release notes. If you require assistance in updating to the latest template, raise a support case via the Rev-Trac support portal at From Rev-Trac 8 SPS00 onwards the templates have been further updated to include the new Rev-Trac branding and appearance however there is no functional difference. Note: The first /RSC/MIGRATION_MONITOR job may fail with error message Function not found. Subsequent jobs should execute without error. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 11

15 Common problems and solutions Return code > 4 during data dictionary activation Reason TMS import process fails to recognise that a dependency has actually been satisfied within the same transport. This is a common issue in older SAP systems. Solution Import the transport file again using transaction STMS. Select only Import Transport Request Again. Return code > 4 due to other reasons Solution 1. Import transport files again and make sure return code is <= If your Rev-Trac version is prior to Rev-Trac 6.0, import extra transport files as in the Appendix 3. Import extra transport files before continuing to the next step If you are using TP command to import the transports, include umodes If you are importing the package using transaction STMS, select the following options: Import transport request again Overwrite Originals, and Overwrite Objects in Unconfirmed Repairs 1.4. Repeat the import of the transports specified in "Step 2: Import transport files" under the "Update Procedure" heading. 2. Check the STMS alert viewer for error messages. 3. Analyse all relevant TP steplogs from the transport log directory. 4. Check for possible database tablespace issues. 5. Go to transaction ST22 to check for SAP short dumps. 6. Go to transaction SM21 and identify the cause of the problem from the SAP system log. Note: In particular, check for DDIC related errors. On numerous occasions, users have incompletely performed an Oracle upgrade immediately before the Rev-Trac update resulting in DDIC related errors on transport import. 7. If you are unable to resolve the problem, raise a critical support case via the Rev-Trac support portal at and include details of the steps above including screenshots and a fresh Rev-Trac diagnostics file (see Appendix 1. How to create a Rev-Trac diagnostics file). Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 12

16 Backout procedure If you fail to install a Rev-Trac Support Package Stack update, raise a critical support case via the Rev-Trac support portal at WARNING: Backout should be regarded as a last resort and in practice, is unlikely to be recommended by Rev-Trac support. If you do need to back out an update, complete the following steps only in consultation with Rev-Trac support. Restore Rev-Trac ABAP 1. Import the Rev-Trac version that was in use before the update. 2. If multiple transports are involved (as is the case with some earlier Rev-Trac versions), use transaction STMS to import the transports as a group. This will minimize errors that may occur when transports are imported out of sequence. 3. Load the Rev-Trac configuration settings you saved before the update From Rev-Trac Console, go to menu path Configuration > Tools > Download/upload configuration The RSC Download /upload configuration screen is displayed Select Upload Configuration (Presentation server) Select Delete Existing and Add New Configuration Table Entries Execute The All Entries Confirmation dialog is displayed. Click the Yes button A file selection dialog is displayed. Select the backup file you saved in Step 1: Prepare for update of the Update procedure. Note: The SAP GUI may be unable to upload the file if the filename is too long. Ensure the length of the path plus filename is less than 128 characters A list of tables and records uploaded is displayed. 4. Distribute the configuration settings in your master to every other system From Rev-Trac Console, go to menu path Configuration > Activate changes Accept all defaults and execute. 5. From Rev-Trac Console, go to menu path Administration > Rev-Trac version From the RSC Rev-Trac component version and dependencies report or the Rev- Trac 7 SPS Version Matrix report, verify that all systems have the same SPS version before the update. 6. Apply all manual changes or import Rev-Trac supplementary transports you had previously performed. 7. Create a fresh Rev-Trac diagnostics file (see Appendix 1. How to create a Rev-Trac diagnostics file) and attach it to the support case. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 13

17 Backout Rev-Trac Web Application (xpack) If you are using the Web Application and have updated to the latest version there is no need to backout this software. The updated version should continue to operate successfully with the earlier version of Rev-Trac. Backout Rev-Trac Web GUI The Rev-Trac Web GUI is part of Rev-Trac Insights which is backwardly compatible with previous eligible versions of Rev-Trac. Roll back of the Rev-Trac Web GUI is not required. Nevertheless you should raise a support case with Rev-Trac support reporting any concerns about compatibility related to the Web Application or the Web GUI. Appendix 1. How to create a Rev-Trac diagnostics file 1. From Rev-Trac Console in the Rev-Trac master system, go to menu path Administration > Diagnostics. 2. Click Execute. 3. Save the output to the automatic generated filename. Do not change the filename. Note: Attach the diagnostics file to a relevant support case. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 14

18 Appendix 2 Rev-Trac Licensing Rev-Trac licensing enforcement License enforcement was introduced in Rev-Trac 5.0 SPS15. From version 5.0 SPS15, Rev-Trac has included a facility to upload a Rev Trac license key. From this version onwards, Rev-Trac checks that the installation is operating within the terms of the loaded license. If no license is loaded, or if an installation is operating outside the terms of a loaded license, Rev-Trac displays informational messages to this effect to Rev-Trac administrators, but in all other respects continues to function normally. Rev-Trac s functions are not curtailed. However Rev- Trac add-on components such as xpack and xdeploy require a valid license key to be loaded prior to use. Obtain Rev-Trac license key 1. Create a fresh Rev-Trac diagnostics file (see Appendix 1. How to create a Rev-Trac diagnostic file). 2. If your Rev-Trac master cannot generate a diagnostic file, from Rev-Trac Console, go to menu path Administration > Health and execute with all options selected. Save the file in HTML format. 3. Raise a support case via the Rev-Trac support portal at to request for a license key and attach the Rev-Trac diagnostics file. Upload Rev-Trac license key 1. From Rev Trac Console, go to menu path Administration > License key > Load license key. 2. Select the license file obtained from Rev-Trac support and select Open. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 15

19 Appendix 3. Import extra transport files 1. Check the Rev-Trac version and DEV Core version of the Rev-Trac master from the RSC Rev-Trac component version and dependencies report obtained in the Update prerequisites section under Requirements for Rev-Trac ABAP. 2. To view over-ride, from Rev-Trac console, go to menu path Configuration > Global Advanced. 3. To view Web app URL, from Rev-Trac console, go to menu path Configuration > Global > Global parameters. 4. Complete the step below to import the relevant transport only if Condition 1 or Condition 2 below is fulfilled. Condition 1 Condition 2 Rev-Trac 5.0 Dev Core 13 or 14 AND XPACK_SERVER_APP over-ride exists Rev-Trac 5.0 Dev Core 15 to 18 AND; either Web app URL is configured, OR XPACK_SERVER_APP over-ride exists Table 2: Conditions for Rev-Trac 5.0 Dev Core 13 to Import the transport below into client 000 of the Rev-Trac master. SAP Basis 620 or higher: A47K Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 16

20 Appendix 4. Switch to automatic, on-approval background migration From Rev-Trac 6.0 SPS05 and onwards, Rev-Trac no longer supports automatic, on-approval foreground migration (foreground migration). If your Rev-Trac version is prior to Rev-Trac 6.0 SPS05, you need to switch any foreground migrations to automatic, on-approval background migrations (background migration) before updating Rev-Trac to version 6.0 SPS05 or higher. Otherwise, the message Please specify background migration method for project PPP type TTT status SSS will appear when a user approves a foreground migration and the migration will not proceed. Procedure 1. Determine whether you are using foreground migration. From Rev-Trac Console, go to menu path Configuration > Process > Assign process. 2. From the Process assignment : Overview screen, look under Process assignment > Assignments per project / request type > Migration method and target > Mig. 3. You are currently using foreground migration if Mig value is 2 or If you have configured many project/request type combinations, it may be difficult to check all their settings manually. Alternatively, use GlobalView link from the Rev-Trac support portal Create a fresh Rev-Trac diagnostics file (see Appendix 1. How to create a Rev-Trac diagnostics file) Log on to the Rev-Trac support portal at Select the GlobalView link On the GlobalView page, use the Upload diagnostics facility to upload the diagnostics file Wait two or three minutes to allow the file to be analysed, then click on the link beneath the GlobalView dashboard heading to launch the GlobalView dashboard Click on the Refresh button on the dashboard toolbar to refresh the screen From the System list at the top right corner, select the Rev-Trac master system whose diagnostics file was uploaded and click the Health Check thermometer Read the Rev-Trac configuration health check report. Figure 1: Rev-Trac configuration health check report 5. Message ID 034 (see Figure 1) confirms that you currently have foreground migration configured. To identify which project/request type combinations are associated with foreground migration, double-click the Deprecated migration method in use message. 6. To configure background migration, please refer to the Rev-Trac migration queue section of the Rev-Trac Administrator Guide. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 17

21 Appendix 5. How to check your Rev-Trac field exits The latest SAP upgrades include new checks for object catalogue and component information (more details can be found in SAP note ). Some Rev-Trac objects were affected and these have been corrected in Rev-Trac SPS03. One affected area is Rev-Trac field exits. This is the only area of Rev-Trac where Rev-Trac related functionality can potentially overlap with a customer's own developments. Although this scenario is seldom encountered, it is still advisable to check. To do so, proceed with the following instructions. Procedure 1. Log in to each development system in turn. 2. Execute transaction SE Enter Function Module FIELD_EXIT_TRKORR. 4. If the function module does NOT exist then this field exit is not in use (no problem). 5. If the function module does exist and the entry is as shown below, (and no additional entries), there is no problem. 6. Execute transaction SE Enter Function Module FIELD_EXIT_TRORDERTXT. 8. If the function module does NOT exist then this field exit is not in use (no problem). 9. If the function module does exist, and the entry is as shown below, (and no additional entries), there is no problem. 10. Provided there is 'no problem' with either of the function modules, then you can be confident that importing the field exit transport will not affect any of your own customisation. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 18

22 11. If you encounter other field exit related entries, raise a support case via Rev-Trac support portal at and request for assistance in merging the Rev-Trac field exit requirements with your existing modifications. In this scenario, you can still confidently proceed with your Rev-Trac update WITHOUT importing the field exit transport as it does not contain any functional changes - it only contains changes required to eliminate warnings during SAP upgrades. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 19

23 Appendix 6. How to update the Rev-Trac Web Application (xpack) From SPS03 onwards, xpack only runs on the Salt platform (RSC Core VM and Linux). The following platforms for xpack are no longer supported: SAP WAS Apache Tomcat ServletExec/IIS Please refer to the relevant sections to update to the latest xpack. Updating existing xpack on Salt (Rev-Trac Web Core) platforms Procedure 1. Request xpack files from Rev-Trac support Raise a support case to request for xpack files, via the Rev-Trac support portal at Provide your Salt ID in your support case. Tip: Obtain your Salt ID from the License menu on the Salt Administration page. 2. Upon confirmation from Rev-Trac support, proceed to the next step. 3. Log in to Salt as the Salt administrator. 4. On the Salt Administration page, select Software updates from the menu. The Software updates screen is displayed. 5. From the drop-down option, verify that Rev-Trac web application (xpack) is now listed as a component available for download. 6. On the Software updates screen, click the Download button for the Rev-Trac Web Application component. 7. When the download is complete, click the Install or Upload file button. 8. You are asked to accept a license agreement, and confirm that you want to install the Rev- Trac Web Application. Give all confirmations when prompted. 9. An Installing update page is displayed. When the software update is complete, you are prompted to log in again. Updating existing xpack on SAP WAS, Apache Tomcat, ServletExec/IIS and other J2EE Web Servers As migrating your xpack to the Salt platform may be quite an involved process, it is recommended that you request for assistance by raising a support case at the Rev-Trac support portal at The process will involve: 1. Installing Salt on Salt platform. For details, please refer to Salt Installation and Administration Guide available via the Rev-Trac support portal. 2. Installing xpack on Salt platform. For details, please refer to Rev-Trac 7 How to install xpack on Salt Platform available via the Rev-Trac support portal. 3. Migrating xpack data. Rev-Trac 8 SPS00 Date: 31-Jul-2018 Page 20