6
System landscape:- Sender System - Production? Central/Control system – we can use Solution Manager however we should deploy a TDMS server built on SAP Netweaver? Receiver system – Non-production system, we can start with Sandbox during initial testing stages and then rest of the systems? The receiver system is on the same release as that of the sender system The repository objects are identical to those in the sender system. You also need a working network connection between central and source system operating system access with administrator/root permissions on source and target system The tools to be updated are R3load (R3load export tool - check version with R3load -v) R3ldctl (Control tool, creates control files - check version with R3ldctl - v) R3szchk (Sizecheck tool, determines tables sizes - check version with R3szchk -v)

TDMS Query and execution

  • Upload
    anandna

  • View
    94

  • Download
    2

Embed Size (px)

DESCRIPTION

TDMS Query and execution

Citation preview

Page 1: TDMS Query and execution

System landscape:-

Sender System - Production?Central/Control system – we can use Solution Manager however we should deploy a TDMS server built on SAP Netweaver?Receiver system – Non-production system, we can start with Sandbox during initial testing stages and then rest of the systems?

The receiver system is on the same release as that of the sender system

The repository objects are identical to those in the sender system.

You also need a working network connection between central and source system

operating system access with administrator/root permissions on source and target system

The tools to be updated are R3load (R3load export tool - check version with R3load -v)

R3ldctl (Control tool, creates control files - check version with R3ldctl -v)

R3szchk (Sizecheck tool, determines tables sizes - check version with R3szchk -v)

db<database>slib.dll (or db<database>slib.(s)o on Unix platforms) - check version with transaction SM51 and note Note 400818 - Information about the R/3 database library. Note: updating that library requires a stopped system.

However we would recommend that you load the shell creation package (process type TDSHL for R3, TDSHB for BW and TDSHC for CRM) in your TDMS system and then follow the documentation availalbe behind each activity.

Control System: All TDMS-specific settings and Customizing are stored in the control system. The control system triggers the TDMS activities in the process tree.

Central System: The backend processing for data migration takes place in the central system.

Page 2: TDMS Query and execution

We recommend that you implement the control system on a server separate from the sender system or the receiver system. The separation ensures enhanced performance and data security.

If you want to set up a non-production system, which is not on the transport path, as the receiver system, use one of the following methods to prepare your receiver system: Perform an SAP TDMS shell creation using the production system as the source system.

Perform an SAP system copy using the production system as the source system.

For All Systems in the SAP TDMS System Landscape You have installed the following Add-Ons along with the latest support packs to run SAP TDMS: DMIS 2011 DMIS_CNT 2011

SAP TDMS 4.0 is available for the SAP system releases listed in this section. For the Control System You have installed SAP Basis Release 700 or above

Activation of SAP TDMS-Related WebDynpro Services: Use t-code SICF and activate following services - BTP_PCLPACKAGE_OIF /sap/bc/webdynpro/sap/btp_pclpackage_oif - BTP_LANDSCAPE_OIF /sap/bc/webdynpro/sap/btp_landscape_oif - BTP_PROJECT_OIF /sap/bc/webdynpro/sap/btp_project_oif - BTP_BLUEPRINT_OIF /sap/bc/webdynpro/sap/btp_blueprint_oif - BTP_DOCUOBJECT /sap/bc/webdynpro/sap/btp_docuobject - BTP_PCLACTIVITY_OIF /sap/bc/webdynpro/sap/btp_pclactivity_oif - BTP_PEMBLOCK_OIF /sap/bc/webdynpro/sap/btp_pemblock_oif - BTP_BLUEPRINTS_POWL_TDMS /sap/bc/webdynpro/sap/btp_blueprints_powl_tdms - BTP_CONTMGMT_TDMS /sap/bc/webdynpro/sap/btp_contmgmt_tdms - BTP_LANDSCAPE_POWL_TDMS /sap/bc/webdynpro/sap/btp_landscape_powl_tdms - BTP_PORTFOLIO_TDMS /sap/bc/webdynpro/sap/btp_portfolio_tdms - BTP_PROJECT_POWL_TDMS /sap/bc/webdynpro/sap/btp_project_powl_tdms - CNVTDMS*

- all CNV*TDMS* services /sap/bc/webdynpro/sap/cnv*tdms*

SAP TDMS uses the SAP NetWeaver Business Client (NWBC) as the frontend technology. SAP TDMS is now available for NWBC Release 3.5 and NWBC Release 4.0.

Assign role(s) and respective authorizations to users: For more information, see the Security Guide at https://websmp101.sap-ag.de/securityguide. Choose SAP Components -> SAP Test Data Migration Server -> SAP TDMS 4.0 Security Guide.

Page 3: TDMS Query and execution

Provide at least eight batch processes and eight dialog processes for each system participating in a migration process.

However, if the sender system and the central system are on the same SAP system, you are required to double the minimum number of available processes.

Disable the DB archive logs and the SAP system parameter REC/CLIENT in the receiver system to improve the data transfer performance

890797.

The standard way of setting up the TDMS server is to install the TDMS software in an empty SAP system. Alternatively, an existing system, such as the SAP Solution Manager System, may be used. For more information about the installation of SAP TDMS, see SAP Notes 1577441 and 1577442.

List of SAP Notes The following table lists all SAP Notes mentioned in this Master Guide. SAP Note Number

Title Description

1577441 Installation of TDMS Software

Installation of TDMS Software

1577442 Installation of TDMS Software

Installation of TDMS Software

1249737 SAP TDMS and Code Pages

SAP TDMS and Code Pages

890797 System Settings for SAP TDMS

Required and Recommended System Settings

CNV_MBT_TDMS

SAP Note 877860 describes the installation procedure and provides additional information with regard to the installation of TDMS

To setup TDMS install add-ons DMIS 2011, DMIS_CNT 2011 and DMIS_EXT (optional) on all the systems.

We have to install the TDMS (DMIS, DMIS_CNT, DMIS_EXT with latest patch levels) software on the sender, receiver and central system. After Successful Installation of DMIS and DMIS_ addon with SPs. Generate profiles for TDMS projects

Generate profiles which starts with these names : SAP_TDMS* , SAP_DMIS* , SAP_CMIS* , SAP_SLOP*. Read see SAP Note 897100.

Create a CPIC user in the sender and receiver systems and give them SAP_TDMS_User role.

In the central system run CNV_MBT_TDMS transaction. If you click on the information button (or F7) you can see some help files.

Execute TXN CNV_MBT_TDMS Create a project, sub project and a package. Then read the documentation for each step in the package.

Page 4: TDMS Query and execution

Create New Package based on your scenario like Shell creation. After successful creation of New Package we will get PROCESS TREE / MONITOR

PACKAGE Screen. We will get following kind of screen once the TDMS Package got created, based on the UI you work with. Use TXN CNVMBTUISWITCH to switch to UI.

Work processes

The following processes should be available, depending on the CPU number (for each server).

Dialog processes : 3 * CPU number (at least 6)

Background processes: Number of dialog processes on DB server (at least 6 + 2 class A processes)

Other processes : in accordance with the instance role

System change option

Client setting (table T000/Transaction SCC4)

Client-specific changes:

'Automatic recording of changes'

Changes for all clients:

'Changes to Repository and cross-client Customizing allowed'

Profile parameter

rdisp/max_wprun_time : 900 (s)

rec/client : OFF

rdisp/btctime : 60

Other settings

OS collector must be activated (Transaction ST06 --> Operating System Collector --> Start)

a) Database settings Logging should be minimized (see the detail settings for the relevant DB system)

Required components and component Support PackagesThe following table provides an overview of the required software component releases and Support Packages.

Add-on releaseRequired component release

Support Package

DMIS 2011_1_620 SAP_BASIS 620 SAPKB62051DMIS 2011_1_640 SAP_BASIS 640 SAPKB64004DMIS 2011_1_700 SAP_BASIS 700 SAPKB70014DMIS 2011_1_700 SAP_BASIS 701 ---DMIS 2011_1_700 SAP_BASIS 702 ---DMIS 2011_1_710 SAP_BASIS 710 SAPKB71004DMIS 2011_1_710 SAP_BASIS 711 ---DMIS 2011_1_730 SAP_BASIS 730 ---DMIS 2011_1_731 SAP_BASIS 731 ---

Page 5: TDMS Query and execution

Additional information about the installation:

CD material number of add-on installation 51041567 or 51041566

Release of DMIS 2011_1 with Enhancement Packages For information about compatibility with SAP Enhancement Packages, refer to release strategy notes

1231203 and 1487845.

The following table provides an overview of the required software component releases and Support Packages.

Add-on releaseRequired component release

Support Package

DMIS_CNT 2011_1_620 DMIS 2011_1_620 ---DMIS_CNT 2011_1_640 DMIS 2011_1_640 ---DMIS_CNT 2011_1_700 DMIS 2011_1_700 ---DMIS_CNT 2011_1_710 DMIS 2011_1_710 ---DMIS_CNT 2011_1_730 DMIS 2011_1_730 ---DMIS_CNT 2011_1_731 DMIS 2011_1_731 ---

Additional information about the installation:

CD material number of add-on installation51041567