2
05.12.2010 Page 1 of 2 SAP Note 943334 - TMS setup in high availability systems Note Language: English Version: 7 Validity: Valid Since 30.05.2007 Summary Symptom TMS cannot communicate with servers that correspond to the SAP HA solution. Other terms High availability systems, Enqueue servers without dialog processes Reason and Prerequisites TMS requires an excellent dialog-supporting server as a communication partner for each system. This is usually the central instance. Unfortunately, with HA systems, this is only a server without dialog processes. Solution If possible, implement the attached correction instructions into all systems of the TMS landscape. You must at least implement the corrections in the TMS domain controller and in the HA systems. In this case, you must manually create the 'TMS_MGR_LOADBALANCING' report. This report allows you to activate or deactivate load balancing for communication with TMS targets. The default user group 'SPACE' is used as a target group. If you have a TMS new configuration, you must first perform the normal TMS domain setup. In doing so, ensure that the dialog instance that you are using is available at the time of the setup. Execute the TMS_MGR_LOADBALANCING report on the TMS domain controller, give it the SID of the HA system and select the Loadblon field in the selection screen. Then execute the report. You are automatically brought to the TMS system overview. Double-click to go to the detailed information for the HA system. The current host names of the dialog instance are in the 'Communication' tab. Enter the message server names here. Save and distribute the configuration. As of this point in time, all of the systems of the transport domain use the load balancing technique for the TMS communication for the selected system. For the processing ability of the transport system, you must ensure that at the time when you import into the system or export from the system, the transport directory exists in the active dialog and background process instances and has the correct authorizations and can be accessed by the system. Header Data Release Status: Released for Customer Released on: 30.05.2007 11:20:39 Master Language: German Priority: Correction with medium priority Category: Program error Primary Component: BC-CTS-TMS Transport Management System Secondary Components: BC-CST Client/Server Technology

sapnote_0000943334

Embed Size (px)

Citation preview

Page 1: sapnote_0000943334

05.12.2010 Page 1 of 2

SAP Note 943334 - TMS setup in high availability systems

Note Language: English Version: 7 Validity: Valid Since 30.05.2007

Summary

SymptomTMS cannot communicate with servers that correspond to the SAP HA solution.

Other termsHigh availability systems,Enqueue servers without dialog processes

Reason and PrerequisitesTMS requires an excellent dialog-supporting server as a communicationpartner for each system. This is usually the central instance.Unfortunately, with HA systems, this is only a server without dialogprocesses.

SolutionIf possible, implement the attached correction instructions into allsystems of the TMS landscape. You must at least implement the correctionsin the TMS domain controller and in the HA systems. In this case, you mustmanually create the 'TMS_MGR_LOADBALANCING' report.This report allows you to activate or deactivate load balancing forcommunication with TMS targets. The default user group 'SPACE' is used as atarget group.

If you have a TMS new configuration, you must first perform the normal TMSdomain setup. In doing so, ensure that the dialog instance that you areusing is available at the time of the setup.Execute the TMS_MGR_LOADBALANCING report on the TMS domain controller, giveit the SID of the HA system and select the Loadblon field in the selectionscreen. Then execute the report. You are automatically brought to the TMSsystem overview. Double-click to go to the detailed information for the HAsystem. The current host names of the dialog instance are in the'Communication' tab. Enter the message server names here. Save anddistribute the configuration.

As of this point in time, all of the systems of the transport domain usethe load balancing technique for the TMS communication for the selectedsystem. For the processing ability of the transport system, you must ensurethat at the time when you import into the system or export from the system,the transport directory exists in the active dialog and background processinstances and has the correct authorizations and can be accessed by thesystem.

Header Data

Release Status: Released for CustomerReleased on: 30.05.2007 11:20:39Master Language: GermanPriority: Correction with medium priorityCategory: Program errorPrimary Component: BC-CTS-TMS Transport Management System

Secondary Components:BC-CST Client/Server Technology

Page 2: sapnote_0000943334

05.12.2010 Page 2 of 2

SAP Note 943334 - TMS setup in high availability systems

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_BASIS 60 610 640

SAP_BASIS 70 700 702

SAP_BASIS 71 710 720

Support Packages

Support Packages Release Package Name

SAP_BASIS 610 SAPKB61047

SAP_BASIS 620 SAPKB62059

SAP_BASIS 620 SAPKB62060

SAP_BASIS 640 SAPKB64018

SAP_BASIS 700 SAPKB70008

SAP_BASIS 700 SAPKB70009

Correction Instructions

CorrectionInstructions

Validfrom

Validto

SoftwareComponent

Type*)

ReferenceCorrection

LastChanged

470235 610 610 SAP_BASIS C Y6AK051590 26.04.200617:51:55

470236 640 640 SAP_BASIS C Y6DK051632 26.04.200617:52:43

470237 700 700 SAP_BASIS C Y7AK030371 26.04.200617:53:04

470239 620 620 SAP_BASIS C Y6BK075918 26.04.200617:54:44

475290 640 640 SAP_BASIS C Y6DK052309 09.05.200617:14:23

475291 620 620 SAP_BASIS C Y6BK076690 27.09.200612:36:57

475292 610 610 SAP_BASIS C Y6AK051796 09.05.200617:17:13

475473 700 700 SAP_BASIS C Y7AK031529 09.05.200617:17:49

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work