Installing and Upgrading Add-Ons

Add-On Installation Tool can process two different types of add-on delivery packages: addon installations and add-on upgrades.

Note
Only import packages when the system load is low, since users must not be logged onto the system and there should be no background jobs running. Otherwise, problems can arise, such as terminated transactions or problems with synchronization. Since the add-on installation procedure is identical to the add-on upgrade procedure, the installation is used as an example here. Prerequisites

You must have distributed maintenance certificates in your system if you want to import SAP add-on packages. For more information, see the SAP Support Portal under http://service.sap.com/maintenancecertificate and SAP Note 1240265. You are logged on in client 000. You have loaded the relevant installation packages into your system. You have called Add-On Installation Tool with transaction SAINT. The add-ons that have already been installed are listed on the initial screen.

You have selected the required installation mode in the Add-On Installation Tool settings.

Procedure Before installing add-ons you first have to make a series of definitions: The Add-On Installation Tool guides you through these. Use the Continue button to move to the next step. Choose Back to return to the previous step. 1. Define the installation queue Since it is often not only one add-on that is installed but several add-ons at the same time you first have to select the add-on packages that are to be installed. From the add-on packages that are selected, the system calculates the installation queue in the right order, that is, all packages that the installation consists of. Depending on whether your system is configured in the Solution Manager or not, you can define the installation queue using a stack configuration (Solution Manager) or manually.

Defining the Installation Queue.

Defining the Installation Queue

Procedure 1. To select the add-on packages, choose Start. The Add-On Installation: Add-On Selection screen appears. The list of add-on packages is filtered. The filtered overview shows all packages that match in your system in question according to the initial tests. To deactivate the filter and display all existing add-on packages, choose Deactivate Filter. When creating an add-on, thematically similar add-on packages can be grouped together. Add-on packages that belong to a group are displayed in a tree. To expand or collapse the tree, double-click on the name of the group. 2. Optional: Load further installation packages into your system. To search for additional installation packages in the current systems EPS directory, choose Load. The system then displays any new packages it finds too. For more information, see: Loading Installation Packages. 3. Depending on whether your system is configured in the Solution Manager or not, proceed as described under Defining the Installation Queue Using Stack Configuration (Solution Manager) or Defining the Installation Queue Manually. 4. Extend the queue with the relevant Support Packages if you want to add more Support Packages to the installation queue or if the system informs you that more Support Packages are required. More information: Optional: Extending Installation Queues with Support Packages. 5. To start the queue calculation, choose Continue.
Defining the Installation Queue Using Stack Configuration

If your current system is integrated into a Solution Manager landscape and is already configured in Solution Manager, Maintenance Optimizer provides a list of add-ons and Support Packages for your system in an XML file. Proceed as follows to define the installation queue using a stack configuration: 1. To accept the configured selection, choose Stack Configuration. A dialog box opens, providing a list of configurations in Maintenance Optimizer that are available for your system. 2. Choose the required configuration and confirm your choice by choosing Continue. After making your selection, the Add-On Installation Tool again checks whether the selected configuration is compatible with your system.

If it is not, an error message appears. If the configuration is suitable, it is taken over automatically, and you cannot change it anymore. However, you can reset the entire step by choosing Back. 3. In the Add On Selection dialog box, the add-on packages for the selected configuration are listed. Check the selection and confirm by pressing Continue. The system calculates the complete installation queue including any Support Packages.
Defining the Installation Queue Manually

Proceed as follows to select the add-ons manually that are to be installed: 1. Select the add-ons to be installed and choose Continue. This can have varying results: o The add-ons cannot be installed in this system, as not all installation conditions have been met. If this happens, the condition that is not fulfilled is named. o Additional packages (Support Packages or CRTs) are needed for the installation. The system specifies which packages are missing. The installation does not start. Load the missing packages.

Note
If errors occur during queue definition, read the Queue Calculation Log. 2. Check if the installation queue corresponds to the Support Packages to be imported in the display.

Note
If all installation conditions are fulfilled and all the necessary Support Packages are available, then the installation queue is displayed.

2. Optional: Extend the installation queue with Support Packages. If you also want to include Support Packages with the add-ons to be installed in the installation queue, you can choose Support Packages that are to be imported with the queue for each software component on the Support Package Selection tab. Extending the Installation Queue with Support Packages.

Extending Installation Queues with Support Packages

You can extend the installation queue with Support Packages in the following cases:

The current maintenance level of your SAP system requires an update of one or more software components. Since the risk of a downgrade and the loss of data exists, you should include the relevant Support Packages into the upgrade queue. A list of affected software components is displayed along with the minimum Support Package level that needs to be included. Some software component versions require a minimum Support Package level. If this is not achieved, you are shown a list of affected software components is displayed along with the minimum Support Package level that needs to be included. The installation queue cannot be imported without this update. You want to update your system. If Support Packages exist for an add-on, you can include them in the installation queue.

Procedure 1. To do this, go to the Support Package Selection tab page and select the highest Support Package that you want to import from the selection list for each component that you require. If you do not want to add any other Support Packages for a component, select the empty field from the selection list. The system automatically enters the Support Package Level of the chosen Support Package in the Level field. 2. Once you have selected the target Support Packages for all the components you require, choose Continue. The system calculates the maximum possible queue using the chosen target Support Packages and the installation queue that has already been calculated. The results of the queue calculation are summarized in the Status/Comment section, whilst the resulting queue is listed in detail on the Installation Queue tab page. At the same time, the Support Package Level attained with the calculated queue is displayed on the Software Components tab page for each component, and linked to the Support Package Level of the chosen target Support Package by way of a comparison symbol. This provides you with a rapid overview of the result of the queue calculation. The queue calculation can have the following results:

The extended queue is consistent and corresponds completely to the target Support Packages that you have chosen. The extended queue is consistent, but does not correspond completely to your chosen target Support Packages. For certain components, the chosen target Support Package levels could not be reached using the calculated queue, or more Support Packages from a component had to be included in the queue than had originally been required, in order to ensure a consistent queue. These variances occur because of the dependencies between Support Packages from different components. These make it impossible to completely match the target Support Package levels that you have chosen. This can happen if you need to include Conflict Resolution Transports (CRTs). The system could not extend the installation queue consistently. An error message is displayed to this effect.

Note
If errors occur during queue definition, read the queue calculation log.

3. Optional: Include modification adjustment transports into the installation queue. If you have already executed a modification adjustment (for example, in the development system) and have created an adjustment transport from it, then you can include it in the follow-on systems in the installation queue. Including Modification Adjustment Transports in the Installation Queue.

Optional: Including Modification Adjustment Transports in Installation Queues

Prerequisites

The system prompts you to decide whether to include the modification adjustment transports in the installation queue.

Note
You can suppress this question in the Add-On Installation Tool settings.

You have already executed the modification adjustment for the same installation queue. For more information, see: Executing Modification Adjustments.

Procedure 1. Confirm that you want to include modification adjustment transports. A dialog box appears, containing a list of existing modification adjustment transports. You have the following options: 1. If no adjustment transports are displayed in the list, you need to notify the system of the transports. To do this, choose Find Adjustment Transports. The system searches for adjustment transports in the Transport Management System import queue and in the transport directory on the application server. The system lists the transport requests that you have selected as modification adjustment transports and released in the export system. For each adjustment transport listed, the Status field shows whether or not it fits the current installation queue and can be included. Adjustment transports that match the queue are already selected in the table. An adjustment transport "matches" the queue if the target Package status of the current queue is the same as the one in the export system at the time when the modification adjustment transport is exported.

2. If required, change the adjustment transport selection. You cannot select adjustment transports that do not match the queue. To hide adjustment transports that do not match the queue, choose Activate Filter. 2. To add the adjustment transports in the installation queue, choose Continue.

Caution
When a modification adjustment transport is imported as part of an installation queue, it is deleted from the normal transport flow for Workbench requests. Requests are not forwarded to follow-on systems automatically. If you are working with the classic three-system landscape comprising a development system (DEV), quality assurance system ( QAS) and production system (PRD), the modification adjustment transport is put into the QAS import queue after being exported from the DEV system. Including the adjustment transport in an installation queue in system QAS means that it is deleted from the QAS import queue. Since no transport forwarding takes place when importing an installation queue, the adjustment transport is not forwarded to the PRD systems import queue. You then need to import the adjustment transport into the PRD system as part of an installation queue, using the same procedure as in the QAS.

4. Define the start options or check those selected. Defining Start Options.

Defining the Start Options

You can define start options for the individual modules according to your system requirements. If you confirm the dialog field without changing any settings, the import tool assumes the default start options, according to the selected import mode. If you change any settings, you can save them as a template for future import activities. Prerequisites You have started importing the queue. If you want the import to run in the background, you need to ensure that your system has at least two free background processes available, and that no other background processes are running. Procedure 1. In the Start Options for the Queue dialog, you can select the options you require for each module from the relevant tab page: o Immediate Start/Continue in Dialog Immediately Choose this option if you want the module to be processed immediately in the dialog. If you select this option for multiple modules, they are processed consecutively without interruption. The mode is blocked for the duration of the import.
o

Immediate Start/Continue in Background Immediately Choose this option if you want the module to be processed immediately in the background. If you select this option for multiple modules, they are processed consecutively without interruption.

Later Start/Continue in Background Later Choose this option if you want to start the module in the background later. Select the required start date and time using input help. If you choose No Start After, the module is processed only in the period between Planned Start and No Start After. If no background processes are available during this time, the module is not processed.

Manual Start/Continue Manually Choose this option if you want to process the module manually. The import tool interrupts the process after processing the previous module.

2. If you change the start option for a module, start options for other modules can be affected too. Choose Enter to refresh the summary of selected start options displayed in the upper part of the dialog. 3. If you want to save your selection as a template for future import activities, choose Save As Template. The template is then used by default whenever the import process is started again in the same import mode.

Note
You can only save the selected options as a template when starting a new queue import and defining the options for the entire import process. When restarting the import process after a module has been processed or after an error has occurred, it is no longer possible to save the changed options as a template. If you have saved a date and time as a template, the time is automatically used for the next import process, and the date changed accordingly. 4. Confirm your selection by choosing Continue. Result The import tool starts importing the queue using your start options. If the import tool interrupts the processing procedure after processing a module, you can check the start options before the next module starts and change them if required. If you have scheduled modules to be processed in the background, you can only make changes using Job Administration. To do this, choose Environment Background Processing in the import tool . Example Standard Settings for Unchanged Use of the Conventional Import Procedure If you have chosen the conventional import (import mode Downtime-minimized not activated), the following settings are made by default: Module Preparation Import 1 Import 2 Clean up Option Immediate Start in Dialog Continue in Dialog Immediately Continue in Dialog Immediately Continue in Dialog Immediately

Standard Settings for Unchanged Use of the Import Mode Downtime-Minimized If you have selected import mode Downtime-minimized, the following settings are made by default:

Module Preparation Import 1 Import 2 Clean up More Information

Option Immediate Start in Dialog Continue in Dialog Immediately Continue Manually Continue Manually

Checking the Status of Background Processing

Checking the Status of Background Processing

If you have scheduled OCS Packages to be imported in the background, you can check the status of the scheduled background job in Job Administration. This may be necessary, for example, if the system is shut down while a background job is running, causing the background processing to change to an inconsistent state. Support Package Manager and Add-On Installation Tool do not allow you to change the parameters of a background job after it has been scheduled. If you want to modify a background job later (to change the start time of the import, for example) or if you want to delete the job entirely, you can do this in Job Administration. Prerequisites In the start options, you have specified that you want at least one module to be processed in the background. To make changes to a background job that has been scheduled by another user, you need the relevant authorization. Procedure The job scheduled for background processing is called OCS_QUEUE_IMPORT. 1. Call Job Administration by choosing the Environment menu in the import tool, or by calling transaction SM37 2. Select job OCS_QUEUE_IMPORT. 3. You have the following options: o Check the status of the job o Check the job log o Make changes to the job o Delete the job Alternatively you get to the menu using System Own Jobs in the display of your own jobs. Here you can see an overview of jobs you have scheduled in the past, together with their status. Choose Job Selection to go to Job Administration. Result The import tool copies the changes from Job Administration. If you have deleted a background job, the status of the package queue changes accordingly. In the import tool, you can restart or reschedule the import of the OCS queue either in the dialog or in the background. You can find more information on background processing in Job Administration, under Help Application Help .

5. Install the queue. The selected start options define when the queue is installed. For example, if you have selected the option Immediate Start for the preparation module, then the installation starts straight after you have confirmed the start options. Depending on the selected import mode, the Add-On Installation Tool executes the installation. For more information, see Installing the Queue.

Installing the Queue

The installation takes place in a defined import process that is described in detail under General Description of the Import Process. Procedure
Conventional Import Mode

1. If you have accepted the standard options without making any changes then the installation starts after you have confimed the start options. The Add-On Installation Tools executes the entire process in dialog. Since the whole import process is run through in this case without stopping, your system must already be non-productive at this time.

Note
To bring the system to a non-productive status in an orderly way, reschedule all scheduled background jobs using the BTCTRNS1 report and let any background jobs that are running complete, or terminate them manually. Prompt all users to close any transactions they are working in and to log off from the SAP system. If you have selected a start time or Continue Manually for module Import 2, your system can stay in production operation until module Import 2 starts. 2. After starting installation, Add-On Installation Tool runs through a set series of phases. If errors occur in any of these phases, the installation process terminates, and a description of the error is provided. Once the problem has been corrected, choose Continue to restart the installation process. Firstly, the Add-On Installation Tool performs all the preparation and test steps (module Preparation). If any errors in this module cannot be resolved, you can reset the installation with Back.

Note

For more information on the check steps in the Preparation module, see Checks with Importing a Queue. Then it executes the import steps of the Import 1 and Import 2 modules.

Caution
Since the database is already changed in these phases, you cannot reset the installation once the Import 1 module has started. You have to continue it after correcting any possible errors. 3. If you have modified SAP objects but have not included any adjustment transports, or if the included adjustment transports do not cover all objects that need adjusting, AddOn Installation Tool prompts you to perform a modification adjustment during one of the subsequent phases. To do this, proceed as described under Adjusting Modifications. 4. To complete the installation process, choose Continue. 5. After you have installed the queue successfully, check the Logs. 6. If you have already canceled background jobs, you can reschedule them using the BTCTRNS2 report.
Import Mode Downtime-Minimized

1. If you have selected the import mode downtime-minimized, some of the objects that are to be imported are imported inactively. You can continue using your system productively during this phase. 2. After starting installation, Add-On Installation Tool runs through a set series of phases. If errors occur in any of these phases, the installation process terminates, and a description of the error is provided. Once the problem has been corrected, choose Continue to restart the installation process. Firstly, the Add-On Installation Tool performs all the preparation and test steps (module Preparation). If any errors in this module cannot be resolved, you can reset the installation with Back.

Note
For more information on the check steps in the Preparation module, see Checks with Importing a Queue. It then runs through the import steps that can be performed during production operation (module Import 1).

Caution
Since the database is already changed in these phases, you cannot reset the installation once the Import 1 module has started. You have to continue it after correcting any possible errors.

The development environment is blocked when module Import 1 starts, thus ensuring that modifications do not endanger the consistency of the system. Add-On Installation Tool then displays a dialog box informing you that you need to stop production operation for the next import module (Import 2). 3. To stop the installation process and change the state of the system, choose Cancel. For this, cancel any background jobs using the BTCTRNS1 report and, if necessary, allow any running background to complete, or terminate them manually. Prompt all users to close any transactions they are working in and to log off from the SAP system. 4. To continue the installation process, choose Continue. The next phase activates the inactively imported objects and imports the remaining objects from the Installation Packages in the queue. Once these phases have been completed, Add-On Installation Tool informs you that you can restart production operation in your system.

Note
This applies only if you have made either no or very few modifications to SAP objects. 5. If you have modified SAP objects but have not included any adjustment transports, or if the included adjustment transports do not cover all objects that need adjusting, AddOn Installation Tool prompts you to perform a modification adjustment during one of the subsequent phases. To do this, proceed as described under Adjusting Modifications. 6. To complete the installation process, choose Continue. In the subsequent installation phases, program code and program texts that have been made obsolete by the imported objects are physically deleted from the database. The installation process is complete.

Note
You can restore productive status in parallel to this import module, or you can start with the preparation activities for restoring productive status (for example, execute ABAP Mass Generation with the SAP Load Generator). You can schedule the previously canceled background jobs using the BTCTRNS2 report. 7. After you have installed the queue successfully, check the Logs.