MDM Configuration Assistant Tool

MDM Configuration Assistant is a standalone tool to help check typos, sub-optimal parameter values, duplicate parameters, missing mandatory parameters, relevance of the parameters within the sections, dependencies within the parameters, inconsistent and incorrect settings.

MDM Configuration Assistant tool provides the following configuration options:

  • Assistance with configuring MDM correctly so that you can connect your Master Data Server (MDS) to a DB server
  • Assistance with validating and managing the configuration settings of the INI files (mds.ini, mdis.ini and mdss.ini) of your MDM server

MDM Configuration Assistant Tool

Prerequisites
To run Configuration Validation to Enable MDS Connection to DBMS option, MDM should be at MDM 7.1 SP03 or higher. Start MDM at least once so that the INI files are initialized.
To run Configuration Validation and Management of MDM Configuration Files option, MDM should be at MDM 7.1 SP06 or higher.
JVM 6.1 or higher

Downloading and Running the Tool
You can download this tool from SAP Note 1543650. Download the attached zip file from the note and extract it on the MDM host server. MDM_ConfigAssistant folder will be created. Move this folder to /usr/sap/<SID> location.

MDM Configuration Assistant Tool

If the host server is Unix/Linux, ensure that run_unix has execute permission. Depending on your operating system, run run_unix or run_win.cmd as <sid>adm user.

Depending on the option you choose the tool will ask you to fill in MDM server or DB parameters. Key in the parameters, Confirm input and Execute the checks.

Configuration Validation to Enable MDS Connection to DBMS

You can also run the tool from command line in a batch mode.

For the Configuration Validation to Enable MDS Connection to DBMS option, run the following
<java6 path>\bin\java –jar com.sap.mdm.tco.configAssistant.jar –cfg Connect2DB –ino <MDM_INSTANCE_NUMBER> –dbName <DBMS_NAME> -dbType <DBMS_Type> -dbUser <DBMS_User_Name> -dbPwd <DBMS_Password> [options]

Example: C:\Java\sapjvm_6\bin\java.exe -jar ./bin/com.sap.mdm.tco.configAssistant.jar -cfg Connect2DB –ino 00 -dbName QAUTF -dbType d -dbUser db2user -dbPwd db2password

and for Configuration Validation and Management of MDM Configuration Files option, run the following
<java6 path>\bin\java –jar com.sap.mdm.tco.configAssistant.jar –cfg ManageINISetting –ino <MDM_INSTANCE_NUMBER> [options]

Example: C:\Java\sapjvm_6\bin\java.exe -jar ./bin/com.sap.mdm.tco.configAssistant.jar -cfg ManageINISetting –ino 00

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more