Connecting MDM to Remote System

Hello,
I was brought on-site to an MDM assignment that is connected to an SAP 4.7 system. The client is now upgrading to ECC 6.0 and I am going to be in charge of pointing the MDM system from 4.7 to 6.0.
I am not sure where to start or where to look to figure out how to create a new connection to a remote system. I have looked in the Console Ref. Guide, the MDM Master Guide, and a few other places.
Can anyone help me with what needs to be done and perhaps where there is documentation to walk me through this?
Thanks experts!
Nichole
Edited by: Nichole Smith on Jul 26, 2010 5:52 PM

HI Nichole
the remote system defined in MDM is only the logical system and ports are defined pertaining to the remote system defined. This has in turn no dependencies on related landscape.
So no changes required at MDM side. (If you can continue with the existing system name for ECC).
If not change the remote system name in MDM first with the correct logical name.
In the PI system landscape and also ECC we need to define the logical systems matching/pointing to MDM defined remote systems.
You can refer to below thread for step by step guidnace for establishing interface between MDM and ECC
MDM-ECC Integration
hope this helps-Ravi

Similar Messages

Failed to use HTTPS connecting to a remote machine (SP3 WLS6.1 )

we are currently having problem with one of our environment. When we
try to use SSL to connect to a remote system, it seems that wls
implementation try to do a dns lookup first before even going out
through the proxy. The problem is that from that system wls will not
be able to do the lookup needed. The dns is available at the proxy
level. Thus when we use ssl in our application we always received
UnknownHostException.
However, the problem does not happen in the other environment running
SP2 (NT 4.0 SP6a). For HTTP either SP2/3 works fine also.
Have anyone experience the same problem? or can this confirm to be a
'bug' from SP3?
FYI: Our application (servlet) perform a request using https to a
remote server to query some information needed (i.e. wls acting as a
client instead of a server). To connect to the remote system, it
needs to go through a proxy first.
Thanks.
Iwan.

Chukii,
take care that you are using the same jdk version on server and client (1.3 or 1.3.1).
prop.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
prop.put(Context.PROVIDER_URL, "iiop://servername:1051"); works nice. I tested it - but on Windows machines.
Your questions:
1. yes, that's an interesting question. Next one...
2. localhost is a good choice. I didn't change this setting
3. JNDI is a directory service like DNS. The EJBs are registered there and can be found with the lookup(...). If you try to find something like '/home/usr...' you'll get an error message '... not bound' (or something like that). You can find your EJB with the JNDI name you entered in the Deployment Tool.
4. Add your remote servers with 'File|Add Server...' and you'll get deploy your application on any server of your choice.
5. iiop. ldap is for looking up something in a directory service like NIS, ActiveDirectory, etc. rmi looks quite nice, but the communication is defined as RMI over IIOP.
hope it helps
-chris

Error connecting MDM system from XI through Java proxies-standard component

Dear Friends
We are trying to connect to the MDM system from XI through Java proxies(i.e standard components),in relation to that we have done the following:
1)registered the interfaces
a)http://XIserver:port/ProxyServer/register?ns=http://sap.com/xi/GDSConsole&interface=GDS_Data_Import_In&bean=localejbs/sap.com/GDS/DataImport&method=gDSDataImportIn
b)http://XIserver:port/ProxyServer/register?ns=http://sap
.com/xi/GDSConsole&interface=GDS_DP_In&bean=localejbs/sap.com/GDS/Dat
aPoolIn&method=gDSDPIn
2)Deployed the ears within Build10.zip, i.e
a)GDS_1.0.6.1_Build10.ear and
b)GDS_ExternalValidations_1.0.6.1_build10.ear
3)set the sap.application.global.properties file inside the GDS_1.0.6.1_Build10.ear
as follows:
SAP application properties
#!Path to GDS folder containing the configuration files
ConfigurationFilesLocation=/usr/sap/P70/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/GDS
#!External validation modules (EJB names) delimited by semicolon character.
ExternalValidationModules=ExternalValidations_EJBs
#!IP or server name of MDM server
MDM.server=172.18.139.200
#!MDM repository port as appears in MDM console
MDM.port=2000
#!MDM repository name as appears in MDM console
MDM.repositoryName=GDS_1
#!version of MDM server and connector
MDM.version=5.5.42.103
#? secure=true
#! MDM Admin user password
MDM.AdminPassword=
#!Data pool name - should match a remote system defined in MDM console
DestinationDataPoolName=
#!Data pool 13 digits GLN
DestinationDataPoolGln=
#!Provider 13 digits GLN
ProviderGln=
#!Provider time zone e.g. EST
ProviderTimeZone=
#!Data pool schema URL
SchemaLocation=
#!Message Timeout
MessageTimeout=10
#!Backend import client system - should match a remote system defined in MDM console.
ImportData.ClientSystem.Name=R3
!# The format that dates will appear in the UI
#Available date formats:      MM/dd/yyyy
#                     dd/MM/yyyy
#                     MM-dd-yyyy
#                     dd-MM-yyyy
#                     dd-MMM-yyyy
#                     dd/MMM/yyyy
#                     MMM dd, yyyy
Where MM=1-12, MMM=Jan,Feb,Mar,etc.
Note: Extreme caution should be taken when choosing to use month names,
#          since different regional settings on the client and server machines
#          will cause dates to be uninterpretable.
#          It is strongly advised to use numeric month format, eg. MM-dd-yyyy, etc.
DateFormat=dd/MM/yyyy
DEBUG.SaveIncomingMessagesToFile=false
#!defines if incoming message will be saved in arc folder
DEBUG.ImportData.SaveArchive=false
#!defines if outgoing message will be saved
DEBUG.SaveOutgoingMessagesToFile=false
But still we are getting errors as:
a)com.sap.aii.af.ra.ms.api.MessagingException: com.sap.mdm.gds.proxy.dataimport.GDSConsole_Message_Exception: : com.sap.aii.proxy.xiruntime.core.ApplicationFaultException: com.sap.mdm.gds.proxy.dataimport.GDSConsole_Message_Exception
inside SXMB_MONI
when we trigger an Idoc and try to send the data inside the MDM GDS system.
and
b)Failed to send message,reason:Exception on method gDSDPOut
when we try to register something,even after the data is validated by the system.
Can anybody help??
It is of urgent requirement.
Edited by: Arjun Ghose on Jul 15, 2008 4:36 PM

Hi ,
   I found a document which says that MDM4J is the legacy API and is considered deprecated .The MDM Java API is the new one .I have both of them in the java build path . I am not sure if this is that cause of the problem .
Now I had a look at the javadoc for the new API but I am not able to locate the class to obtain a connection to the MDM server from a custom application being built in Netweaver Developer Studio . Can someone help me out with the same ?What would be the code to obtain the connection to the MDM server with the new JAVA API ?
Regards
DeepaK Singh

Unable to Edit/Remove Remote Systems using MDM 7.1

Unable to find an answer to this in either the forums or the Wiki...
Using MDM 7.1 through the SAP MDM Console 7.1.03.54
I can add a new Remote System, it comes up with the default values for the Remote System fields:
Name: New Remote System, Code: NewRemoteSystem, Type: Inbound, Key Generation: None
But I cannot modify the field values nor can I delete the Remote System.
The right-click context menu always has 'Delete Remote System' greyed out.
Nor do I see any mechanism to modify the fields' values. Moving to the Remote System Detail pane, none of the fields are edittable; I have tried left-clicking, right-clicking, double clicking, using the Edit tool bar menu - nothing lets me edit these fields.
My user account has the Admin role. Looking to the Admin role, it has Execute for all functions, and Read-Write to the Remote Systems in the Tables and Fields tab.
Any help would be appreciated.

Hi Andrew,
Your repository should be in unloaded state to make changes in any table whether main table, subtable, Ports, Special tables or Remote Systems table etc. As you want to make changes in your repository Remote Systems, please unload your repository->Go to Admin>Remote systems>Make necessary changes (Add/Delete/update)--> Then load repository.
Note: You can only add User and Roles during Repository loaded state.
Regards,
Mandeep Saini

I want to buy an Apple TV device but I need to be sure of its benefits. I have contracted a Satellite TV. Is it true that if I connect Apple TV to system, I can watch TV through IPad wherever by using wireless and App Remote

I want to buy an Apple TV device but I need to be sure of its benefits. I have contracted a Satellite TV. Is it true that if I connect Apple TV to system, I can watch TV in my IPad wherever by using wireless and App Remote??

If you have an iPad 2 you can wirelessly mirror it to your TV via the ATV device. If you have an iPad 1 then you can use airplay but not all apps are enabled to push video, as the developer needs to do this.
You can also view all local content from iTunes or your iPad, pushed via airplay/home-sharing.
The other services available are iTunes movie rentals, TV shows (past purchases viewable from the cloud), Photo Stream, Netflix, Vimeo, Podcasts, Youtube, Sports etc.
More info
http://www.apple.com/appletv/

Assign records to different remote systems in MDM

Hello Experts,
I am using qualified range to generate internal number range for vendor. The remote key & remote system details for the records are generated during syndication. My scenario is that I have couple of records in MDM for different remote systems. I want to syndicate it to the respective systems. Is there a way to identify the respective records per system with out inserting the details in "edit key mapping".
If we try specifying Remote system details in edit key mappings with a blank or specific Key value , then the qulaified number generated for vendors is overwritten with this key value mentioned in key mapping.
I need to retain both the qualified range functionality as well as tag the records to different remote systems.
Kindly advice.
Thanks and Regards,
Elizabeth.

Hi Shiv
So, i am not sure, but this all makes me feel that syndication tasks can not be executed parallel.
Your understanding here is correct since we are using here the same table for syndication process so it will be executed in steps. I mean syndication 2 has to wait until the syndication 1 ends. But the thing is that even after syndication 1 completes syndication 2 is not going to place that's the issue here.
Please find solution which tells same thing in MDM import manager context.
Can I run two Import Managers at the same time?
Yes, several instances of the Import Manager can be open concurrently. The only existing limitation though is when actual importing process starts the tables involved in the importing process are locked for write access. So if two instances of the Import Manager import to different tables then no synchronization issue occurs. If they use the same table, then the instance getting access second has to wait until the first ends.
For more details, Please refer this below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7dc6ba86-0501-0010-0b82-849437929f0d?quicklink=index&overridelayout=true
@ Elizabeth: After Syndication 1, Have you checked after sometime whether syndication2 & so-on takes place or not. I feel that Syndication for syndication 2 , syndication 3 & syndication 4 should also occur after some time as they executed one by one not parallel so will take some time. Just check and revert with result whether your workflow gets completed after some time or not.
Note: Make sure that for all these Syndications outbound ports Processing Type = Manual in Console else syndication will not occur.
Regards,
Mandeep Saini

Query a List of Open WMI connections on a server from a remote system

We are monitoring a specific windows service on a server using Sitescope remote monitoring. The sitescope system uses a WMI method to Check if the service on a specific server is up or not. Initially it works like a charm but over time the WMI connections from
sitescope time out and we have been told that Sitescope is not closing the WMI connection it opens gracefully and the open connections pile up.
I am looking for a way to list open WMI connections to a specific service and/or server from a remote system and a way to kill those connections via a scheduled PowerShell (or batch/perl) script. I was able to list specific classes by -list parameter
of the Get-WmiObject cmdlet
but am unable to determine which class will give me the information that I require and the method to kill those connections.

Sitescope is not closing the WMI connection it opens gracefully and the open connections pile up.
1. It's not clear what "not closing the WMI connection it opens gracefully" means. WMI is a management technology that uses DCOM to connect to remote computers. (Is it really a question about DCOM?)
2. It's not clear what specifically "open connections pile up" means and what problem(s) it causes.
3. This is really a support question for that software's developer, not a question about WMI.
-- Bill Stewart [Bill_Stewart]

Runtime repository connects on remote system fails in connection

Hi,
I've created runtime repository and access users and target schema on linux server through owb server install. Sqlplus onnections from my window2k PC work OK for all 3 users.
I created a second runtime repository connection from my owb designer on windows2k system. When I bring up deployment manager and try to connect to the remote target through this connection, it fails with RTC-5260:failed to connect to runtime platform...,and ORA_01017:invalid username/password. Also, I notices a java thread on the remote linux server was created each time I tried the connection .
I have the connection alias under both OWB and OracleDB tnsnames. What's the problem?
~Tracy

Found one solution from metalink for this. Note:257687.1

HTTP Response :500 unable to connect to remote system.

Hi,
I am doing proxy-xi-file scenario, where i am getting this error in sxmb_moni in R/3.
The error reads with red flag:
HTTP Response :500 unable to connect to remote system.
Please tell me what can be the reason.

Snehal,
Error: The error message 503 Service unavailable Application stopped! is displayed.
Description: The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
Refer SAP Note 803145,807000,791655
You can have a look on this blog for the same.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Sarvesh

When connecting to remote system, once again asking user & password details

hi
I created one RFC in R/3 system, with the same logical system name of xi, giving all technical and logon details.
When I click on remote logon to enter into xi system,it is once again asking user logon details. After entering the details it is allowing into the xi system. Directly it is not entering into remote system when I click remote logon button.
I created both sides (in xi and R/3) and checked the same thing. Both sides I am getting the same problem. it is showing client name correctly but user and password name it is displaying the same server information. like if I am connecting from R/3 to XI means it is showing XI client number but R/3 user and password. Once after I change user and password and press enter it is going into remote system.
Could someone please help me on this?
Thanks in advance and best regards,
1234

hi lavanya
Provide the user with the corresponding authorization or avoid using the protected users DDIC and SAP*
check below
Trusting Transaction SMT2
The trusting transaction SMT2 (or SM59 ® RFC ® Trusting Systems) constructs a list of all trusting systems that have been established for this trusted system. Here, a logon and authorization check for the current user and client is performed, using the destination TRUSTING_SYSTEM@S00 that has been automatically created.
This basically corresponds to transaction SM51, if you use Remote Login to perform a logon on a different application server.
If problems occur while setting the destination TRUSTING_SYSTEM@S00 (such as host name or service information), you either have to create a new destination for your needs, and then enter the host name or service information using SAP router strings, or adjust the network settings of the server. To correct the problem in transaction SMT2, you have to adjust the network configuration of the server. As this transaction is only to be used for test purposes, in this case you could also choose to ignore the error.
To perform a logon as a different user or client, you have to create a new RFC destination with a trusted option set.
In this scenario, the following error text in SMT2 can be ignored:
No authorization to log on as a trusted system (Trusted RC=0)
If the host name contains the character '_' (as in "my_host"), then the generation of the related trusting system destination may lead to incorrect settings. This problem can be corrected by implementing Support Package SAPKB46D09 (see below). For earlier releases, the changes required to correct the problem can be made manually.
regards
kummari

MDM 7.1 remote key generation on different Remote Systems

I am checking onthe remote key gerneration.
1. When I import data from a remotesystem lets say A AND the data have e.g.. a vendor number in Vendors from BusinessContent
    the remote keys are generated for this remote system.
2. Whe I want to syndicate these date to another remote system e.g. SAP ERP, the objectid i.e. LIFNR is NOT shown in
   the syndicators Destination Preview.
   independent of the map properties setting "Remote Key Override"
3. When I enter the key by hand inthe data manager the data are shown in the syndicator but only it "Remote key overrifde"is
   set to the target system.
Question:
It looks like that the remote keys for a different remotesystem other than the one I omported from are NOT set.
How to do a automatical assignment to the keys of this different Remote System

I checked:
SAP ERP Remote System range 100000 999999
A range 100000 199999
Key Mappings defined for SAP ERP Remote System (checked in Data Manager)
key Mappings not defined for A (checked in Data Manager)
Everything I do I do in the Syndicator
With mapping property "Remote Key Override" marekd as "Reset" no LIFNR is written to SAP ERP
With this property set to SAP ERP the LIFNR is sent.
When I use System A it doesn't matter which settings I have there is no VendorNumber sent out.
Looks like I miss the settings for a property?

Change remote system in sydnicator map

I have imported a syndication map from a remote system and want to duplicate the same map out to another remote system, how can i change the remote system value in the map properties?
Adam Sellers.

Hi Adam,
When you are opening the MDM syndicator. Go to .. File>Connect to source
Here you can mention the Type and Remote system.The Remote system you select here gets reflected in your Map properties.
Now import The Exported Map.
Hope it helped
Thanks & Regards
Simona Pinto

Remote System and Remote Key Mapping at a glance

Hi,
I want to discuss the concept of Remote System and Remote Key Mapping.
Remote System is a logical system which is defined in MDM Console for a MDM Repository.
We can define key mapping enabled at each table level.
The key mapping is used to distinguish records at Data Manager after running the Data Import.
Now 1 record can have 1 remote system with two different keys but two different records cannot have same remote system with same remote key. So, Remote key is an unique identifier for record for any remote system for each individual records.
Now whenever we import data from a Remote System, the remote system and remote key are mapped for each individual records. Usually all records have different remote keys.
Now, when syndicating back the record with default remote key is updated in the remote system that is sent by xml file format.
If same record is updated two times from a same remote system, the remote key will be different and the record which is latest contains highest remote key.
Now, I have to look at Data Syndication and Remote key.
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back. But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
Regards
Kaushik Banerjee

You are right Kaushik,
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back.
Yes, but if they are duplicate, they needs to be merged.
But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
This is after merging. So whichever remote key has tick mark in key mapping option(default) , it will be syndicated back.
Pls refer to these links for better understanding.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/80eb6ea5-2a2f-2b10-f68e-bf735a45705f
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9eecc8c%0c
Hope this helps,
+ An

Syndicating based on Addition of a Remote System Key

Hi
We have a distributed system syndication scenario where we need to syndicate a record automatically when a remote system key is added to an existing harmonized record in MDM. By adding the Remote System Key, it essentially means the remote system is 'subscribing' to the new harmonized record.
Is there any way to fire off a syndication event when a new remote system key is added to a record? It seems that MDM currently only flags a record as ready to be syndicated when a value changes in one of the fields of that record - it doesn't seem to identify the addition of a new system key to the record as a change to the record.
Thanks for your assistance in advance.

Hi Ravi
Thanks for the reply. The current view is that we were going to add it manually as a remote system key mapping, as the material record would already exist and would have been harmonized in mdm - so no need to add it through an import map. The scenario is that the master record already exists and another system wishes to also receive this record. Any thoughts on what options do we have if we go this approach?
Also, is their anyway to indicate if a remote system key is added for a new system to an existing mdm material, to indicate when syndicating that the record being sent is a 'Create' record - and hence only to syndicate it to the new remote system added and not to the other systems which also have remote key's against that record?
Thanks
Costa

Search for [Remote Key] and [Remote System] in Data Manager

Hello all
I would like to be able to search on the remote key and the remote system in the MDM Data Manager is that not possible? I thought I remembered seeing that possibility under the Free-Form Search but now I can't find it.
I have, however, found this in the Data Manager reference guide:
REMOTE SYSTEM AND REMOTE KEY FIELDS
MDM uses the remote systems defined in the Remote Systems table
within the MDM Console to store and maintain key mapping information
for each record or text attribute. It does this using a virtual key
mapping field that you never see in the MDM Client.
This virtual key mapping field is very much like a qualified lookup field
into a virtual key mapping qualified lookup table.
Key Mapping information stored in virtual lookup field
The Remote System and Remote Key fields are normally not visible;
however, they do appear in several places in the MDM Client.
Specifically, both fields: (1) appear in the File > Export dialogs in Record
mode for exporting value pairs; (2) are recognized by the File > Import
dialog in Record mode for importing value pairs; and (3) appear in the
Edit Key Mappings dialogs in both Record mode and Taxonomy mode,
for viewing and editing value pairs.
Is there any way to search on the value in the remote key from the Data Manager?

Not sure search i think not possible.
But you can see keys as mentioned:
Enable Key mapping in Console.
MDM Client maens MDM Data Manager.
They do appear in several places in the MDM Client or Data Manager. Three different methods to see in DM are given already below:
Specifically, both fields: (1) appear in the File > Export dialogs in Record mode for exporting value pairs; (2) are recognized by the File > Import dialog in Record mode for importing value pairs; and (3) appear in the Edit Key Mappings dialogs in both Record mode and Taxonomy mode, for viewing and editing value pairs.
BR,
Alok

Connecting MDM to Remote System

Similar Messages

Maybe you are looking for