[[{“value”:”
SAP MDM Migration-Heterogeneous Steps by Steps
What is MDM?
SAP MDM (Master Data Management) is a tool used to store, manage, and maintain important business data in one central place.
Example
SAP ERP
CRM
SRM
MDM Component Used during the Installation.
MDM Import Server (MDIS) Package
MDM Server (MDS) Package
MDM Shared Server Content Package
MDM Console
Our Landscape
This slide presents the Source and Target Landscape, with a high-level summary of each process step. Distributed Environment. SAP MDM Application is on Different Hardware and HANA DB is on Different Hardware in Target.
This slide present Post Steps in Target SAP MDM Application Server with HANA DB.
Windows Server 2016
Ram 16 GB
Database SQL Server 2012
MDM Version 7.1
Target System Details
Linux Enterprise Server 15 SP6 with 8 GB Ram
Database HANA SPS08 with 16 GB Ram
MDM Version 7.1
We need to install HANA DB on different Hardware.
MDM Application File System Details.
/sapmnt/SID
/usr/sap
/usr/sap/SID
MDM Installation in Target System
Step 1
Target Server File System Details.
You need to install MDM Server in Target.
You need to install HANA DB in Target.
Step 2
Execute SWPM.
Step 3
Select Custom.
Step 4
Give SID of Server.
Step 5
Give Master Password.
Step 6
Next with default screen.
Step 7
Give MDS Instance No.
Step 8
Step 9
HANA Client need to install first and give HANA client path here.
Step 10
MDIS Instance No
Step 11
This Default MDIS Port
Step 12
This is main Screen you should handy below MDM package.
Step 13
Click next and Installation will start.
Step 14
SAP MDM Installation has been finished.
Step 15
As you already installed HANA DB in your Environment.
Now you need to create one User in HANA DB level from Studio with any name.
I have created here MDMUSER.
Now disable password lifetime of MDMUSER.
ALTER USER MDMUSER DISABLE PASSWORD LIFETIME;
Step 16
Now preform Post step from MDM application side.
You can see /usr/sap/SID below MDIS62 and MDS 61 Instances created
Step 17
You can see mds.ini in screenshot. We need to modify this file to connect the HANA DB but before we need to take backup of mds.ini file and then we will modify.
Step 18
After backup of mds.ini file open this in vi mode and paste below entry and saved the file.
HANA Repository Type=COLUMN
HANA DSN Connect=True
HANA Library Path=/usr/sap/hdbclient
Step 19
Now create odbc.ini file in home/sidadm from vi ~/.odbc.ini command.
Now perform the steps below
vi ~/.odbc.ini
export ODBCINI=$HOME/.odbc.ini
echo $ODBCINI
/home/sidadm/.odbc.ini
echo ‘export ODBCINI=$HOME/.odbc.ini’ >> ~/.profile
source ~/.profile
odbcinst -q -s
Step 20
Now run this command to check connection Status
Same MDMUSER and Password will use here which is you in created Step 15.
isql -v MDMHANA MDMUSER password
Connected.
Till here our MDM installation HANA DB installation and Connection Connectivity has been completed.
Step 21
Now we are going to Export repository from Source System.
For repository Export take the backup of your source system, log in to the source system and open the MDM Console.
Ensure that the sidadm password is available before starting the activity.
Step 22
Open MDM Console and first Mount the Server.
Step 23
It will ask you MDM server name. Provide Server name and press Ok.
MDM Server Mounted on Left Side.
Step 24
Now Right Click ok SRM_MDM_CATALOG and Connect to Repository.
It will ask you user name password.
After putting password. Below screen will come.
Then you need Start Repository
Right Click on SRM_MDM_Catalog Start Repository and Update Indices.
Step 25
Now Right Click on Catalog and Archive Repository.
It will ask you Verify Repository Click Yes.
Click Ok You can see Repositary.
It will show you Repositary Export Result. Click on Yes.
Step 26
You can check at Server level Repository path.
/usr/sap/SID/MDSxx/mdm/archives
Source System Activity has been completed here. Now will Start on Target Server
Step 27
Now transfer this Repository to Target server in same location for import.
Login in Target Server
/usr/sap/SID/MDS/mdmxx/acchives
Repository copied in Target Linux Server in same location.
Step 28
Now go to Target MDM Application Server and take backup of mds.ini file.
Again open MDM Console and Mount Target MDM Server there.
Right Click and Mount Mount MDM server
You need to provide MDM hostname.
Step 29
Now Start MDM Server.
Give sidadm password.
Again Right Click on MDM Server Unachives Repository (It means we are importing Source repository to Target Server)
Add
Step 30
Click on right 3 dots for making connections.
DBMS Server Add
Select DBMS Server MDMHANA. Selct DBMS Type HANA
Step 31
Provide mdmuser and password here which we created in HANA Studio.
Give any Repository Name and Finish
Step 32
Unarchive Repository Process has been started. Once it is finished.
Then connect to Repository.
Provide Source Repository User and Password here.
Now Start Repository with Update Indices.
Step 33
Repository has been restored in Target Server.
We can verify Source MDM Repository User and Roles showing in Target Server after Unarchive Repository.
We can verify Repository after Unarchive in Target.
Right Click on Server Verift Repository and check.
Step 34
Now we can check MDM application connected to HANA Server.
Run select * from M_CONNECTIONS query in HANA Studio.
You can see Client IP is MDM application IP.
Step 35
Once Repository imported in Target Server. Go to below path
/usr/sap/SID/MDSxx/config
Open the MDS.INI file in read-only mode to review the repository configuration details. The repository user ID and password can be found in the file.
MDMUSER is the same user which is created in Step15.
If you create any new repository in MDM Console that information will save in mds.ini file.
OS/DB Migration means moving the SAP MDM system from one Operating System and/or Database platform to another while keeping the same MDM repository data and business functionality. All MDM repositories, configurations, users, workflows, and interfaces from the source environment to the target operating system and database platform.
After migration:
All MDM Repositories Were Successfully Migrated.
Repository structure remained unchanged.
No data loss occurred during migration.
System Performance Improved:
Faster database processing in HANA DB.
Better hardware and operating system utilization.
“}]]
Read More Technology Blog Posts by Members articles
#abap