Show TOC Entering content frame

Process documentation Language Import During the Upgrade Locate the document in its SAP Library structure

Process Flow

As of SAP Web Application Server Release 6.10 there is a new upgrade procedure, the System Switch Upgrade.
The new procedure installs an instance of the target release (shadow system) in parallel with the running source release system on the same database. This parallel system contains all the software of the target release and is used to integrate any Support Packages included in the upgrade, add-ons, and customer modifications into the target release.
The language data is imported into the shadow system. This data is merged with customer object data, and only then is it made available to the new runtime environment. This also applies to the corresponding language-specific tables.
As a result, the language import is a part of the upgrade procedure. At the start of the upgrade, the system asks you whether you want to import all installed languages during the upgrade.

Note

The languages English and German are always imported in the upgrade. Any languages that you choose not to import in the upgrade must be imported afterwards with transaction SMLT.

A language import during the upgrade consists of the following phases:

·        Phase LANG_SELECT

This phase analyzes the available language CDs and unpacks the language packages that can be used in the upgrade into the upgrade directory. You are asked which languages you want to update with the language packages during the upgrade.

The analysis of the language CD is logged. The file PEVALLAN.<SID>is created in the log directory of the upgrade. This file contains additional information about the packages and can help you to find out the source of any problems.

·        Phase JOB_RSTLANUPG

This phase sets the SMLT control information for the language packages imported during the upgrade.

The languages are imported into the system using the same procedure as for Support Packages. For example, this is how translations are loaded into the shadow system in the phase SHADOW_IMPORT_ALL.
The fact that the language data is always imported before any Support Packages in the upgrade means that there are no sequence problems.

Note

After the upgrade you must use transaction SMLT to supplement the imported languages.

 

 

Leaving content frame