cgpax.blogg.se - Sap ecc dimp 5.0 upgrade to EHP7

The Connector then starts the "correct" SAP ECTR. The alternative to the files ectr_env.txt and ectr_setenv.bat is to use the Connector.

The files ectr_env.txt and ectr_setenv.bat are no longer created by SAP ECTR 5.2 to find the most recently started SAP ECTR.

Technical differences between Launcher 5.2 vs. The variable PLM_TEMPROOT is then always made up as follows: PLM_TEMPROOT=%PLM_TEMPBASE%\\ The (option in jvm-config.xml) and the are always appended to PLM_TEMPBASE. The default value for PLM_TEMPBASE is "java.io.tmpdir" (%TEMP%). Via the variable PLM_TEMPBASE, however, it is possible to define the main directory (in the plm_initialize.bat).

It is not possible to change the individual directories below the Tempdir.

The expression after APPDATA (SAP\PLM) can be customized via the option in the jvm-config.xml file (for 5.2: SAP\ECTR, for 4.7: DSCSAG\ECTR). The default value for PLM_DATAROOT is %APPDATA%\SAP\PLM. The directory is only used by SAP ECTR and can no longer be "manipulated".

There is no more setting possibility for PLM_DATAROOT.

Overview of all deeper changes as a result of the new Java start environment for 5.2:

The start environment of SAP ECTR 5.1 has been adopted as far as possible.

The following describes what has been changed / replaced and how the new technology works. The starting procedure of SAP ECTR 5.2 has been fundamentally redesigned. Installing the latest SAP ECTR 5.2 version All libraries used (such as felix) have also been upgraded to the latest released version.All customer-specific classes must be checked, adapted if necessary and recompiled in any case.SAP ECTR 5.2 can no longer be started on computers that only support 32-bit.

Impact of the introduction of Java 11 on the existing installation: Use of Java 11 as Java runtime environment (JRE) Users who hardly need any changes and are satisfied with the "small" (upscaled) icons can store the "5.1er" images-sap.jar file and the "5.1er" images.jar file renamed to \customize\classes\.The mapping of the customer-icons.txt file must be modified according to the structure above.New customer-specific symbols are also required for customer-specific extensions if these are to be displayed "well" with HiDPI.Information for users who demand large icons:.There is a fallback in SAP ECTR 5.2 to upscale small icons.The structure in the symbol config file standard-icons.txt and customer-icons.txt has been changed.It is possible to pack both structures into one JAR file in order for the system to be compatible with the 5.2 and 5.1 frontend.Images are stored in the image folder in the format image.png and (double size).