Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member
  1. Architecture of Distribution Monitor ( Files and Directory structures)

Distribution Monitor itself is not an executable or binary, it is consisting of set of scripts and parameter files; which is internally based on SAP tools – R3load, R3szchk, R3ldctl and R3ta. When you UNCAR “Distribution.SAR” file, it contains some scripts and configurable files with default configuration. I will not cover the configuration part in this blog, I will explain more about file and directory structures – which is the backbone of the Distribution Monitor.

For overview of Distribution Monitor, please check the following SCN blog :

http://scn.sap.com/docs/DOC-34138

I am going to use the same example as I have mentioned in part-I blog, that means I will use four nodes for optimization.

Fig1 : Distribution Monitor with four nodes

I will explain all important files and directory structures in this blog.

Directory

Uses

Common directory

/<path>/commDir

Common directory or common file system is mounted to both source, target and to all nodes so that each of these systems can perform read/write activities to common directory. It can be local to source or target system or NAS file system.

Common Directory contains various sub directories and it is important to understand each of these sub-directories. Following are the important sub-directories :

R3ldctl : It contains *.STR files for all SAP standard packages and *.TPL ( database specific template) files.

R3ta : *.WHR (where files for all split tables– condition for splitting  )

R3szchk : *.EXT files (computes space requirements for tables/indexes) for all standard SAP packages.

ExportCtrl : Control file is created while export is running for a package or table split.

EXT4Split : *.EXT files for split tables.

ImportCtrl : Control file is created while running import for a standard package or table spilt

Info : Contains export / import property files and distribution.txt file – that determine distribution of tables and packages amongst various nodes.

PkgSplit : It contains *.STR files for all split tables and non-split tables those are moving out of standard packages.

SapinstImport : You need to specify as “export directory” in SAPINST. It contains LABEL.ASC file and ‘DB’ and “Data’ directory.

Sapview : *.STR file for views

STR4Split : It contains *.STR files for all split tables

Host1 :  Each host-directory contains a lot of information for export and import run. It has the following sub-directories :

  netExchangeDir – Control file for parallel export/import

  exportInstallDirCopy – Copy of exportInstallation directory

  importInstallDirCopy – Copy of importInstallation directory

   Files : ddl mapping files for export and import.

Host2

………

Host4 ( a sub-directory for each node  by its hostname ).

Sub-directory structure under common file system is generated by Distribution Monitor’s “preparation run”. Export/import process read and generates various info into these sub-directories.

Fig2 : commDir directory structure

Directory

Uses

Local directory structure on each node

File and directory structure on each Distribution Monitor node :

Export Directory : Local export directory for each Distribution Monitor node. Export directory size should be calculated as { 10 GB + ( 1/10 * total size of the data distribution for the node )}.

Export Installation Directory :  Log files for export run.

Import Installation Directory :  Log files for import run.

Work Directory : Distribution Monitor executable directory for each node. Best practice is to create the work directory under - /usr/sap/<SID> file system.

Example of Local directory structure:

|-/export/node1         (export directory)

|-/usr/sap/<SID>|-DMWKDir      ( Work directory)

                            |-InstDirExp     (Export Installation directory )

                            |-InstDirImp    (Import Installation directory )

Content of Work directory ( or executable directory ).

Fig3 : Content of Work Directory

Configuration of Distribution Monitor centers around configuration of work directory’s configuration files .I will cover more about configuration in optimization blog part-III.

5 Comments
Labels in this area