Deploying MDM adapter content in PI 7.1..

Hello,
I have a requirement to deploy MDM content in PI 7.1 server through ESR. But when I try to login into ESR with j2ee_admin or PISUPER user I get the below pasted error. The j2ee_admin and PISUPER users are also not able to login into RWB which means that the password for the admin user is not matching in config tool. At this point I tried to reset the password for the admin user in config tool but Iam not able to see any tabs for the admin user as we have in PI 7.0 or lower versions.
In the secure store I see only jdbc configuration and not the admin details. I also tried to activate SAP* and change the password for the admin user but even activating SAP* is not happening. Please giude me to solve this issue and deploy the content successfully. Thanks in advance.
Error in ESR:
"Authorization error; unknown user name or incorrect password"
Error in config tool when trying to activate SAP:*
Error: Error occurred: The ConfigEntry '[email protected]' in configuration 'cluster_config/system/instances/ID
86091/cfg/services/com.sap.security.core.ume.service/properties' is final. No modify operations are allowed on inherited final ConfigEntries!
System details:
SAP NetWeaver 7.1 - SAP_BASIS - Level 0007.
Windows NT
16x AMD64
ORACLE
10.2.0.2.0

Hai,
Sorry, I have opened the thread in wrong forum. Iam moving this thread to Nteweaver Administration.
Thanks for the support.
Regards,
Yoganand.V

Similar Messages

Deployment of MDM Adapter For PI 7.1

Hi,
I deployed MDM Adapter (MDMADAPTER01_5-10005240.SCA ) in PI 7.1 Server through JSPM and the deployment has been completed successfully. But when i tried to create a communication channel, i am not able to see the MDM Adapter in the Adapter type selection box, so i am struck in this step and not able to proceed further.
Please let me know, is there any stpes to be performed after deploying the MDM Adapter in PI.
Regards,
Ranjith

Hi,
....And there is MDM Adapter 7.1 available in SMP, when i click on SAP MDM, it is giving "no data available".....
Usually, this is caused by the S-number that you used to login to SMP, does not have authorization to view the data..
By the way, coud you please tell me the path ?
Thanks and regards,

Deploying MDM content in PI 7.1..

Hello,
I have a requirement to deploy MDM content in PI 7.1 server through ESR. But when I try to login into ESR with j2ee_admin or PISUPER user I get the below pasted error. The j2ee_admin and PISUPER users are also not able to login into RWB which means that the password for the admin user is not matching in config tool. At this point I tried to reset the password for the admin user in config tool but Iam not able to see any tabs for the admin user as we have in PI 7.0 or lower versions.
In the secure store I see only jdbc configuration and not the admin details. I also tried to activate SAP* and change the password for the admin user but even activating SAP* is not happening. Please giude me to solve this issue and deploy the content successfully. Thanks in advance.
Error in ESR:
"Authorization error; unknown user name or incorrect password"
Error in config tool when trying to activate SAP:*
Error: Error occurred: The ConfigEntry '[email protected]' in configuration 'cluster_config/system/instances/ID
86091/cfg/services/com.sap.security.core.ume.service/properties' is final. No modify operations are allowed on inherited final ConfigEntries!
System details:
SAP NetWeaver 7.1 - SAP_BASIS - Level 0007.
Windows NT
16x AMD64
ORACLE
10.2.0.2.0

Hi ,
Please use PIRWBUSER to login in RWB then it will work fine.
Thanks..
Mohit

Content conversion using PI MDM adapter in PI 7.1

Hello All,
I am using the PI MDM adapter in PI 7.1.
I have a scenario ECC - PI - MDM . ECC will send an IDoc to PI and we need to send a flat file to MDM.
So is it possible to convert the IDoc XML in PI to flat file using PI MDM adapter , and if yes then how ?
Please help
Regards,
Loveena

Hi Loveena,
Check the "Non-XML Inbound Messaging" section in the following document (Page 15)
https://websmp205.sap-ag.de/~sapidb/011000358700001890482008E
Regards,
Ravi kanth Talagana

Error while deploying the Adapter Module

Expets,
i am getting below error in communication channel:
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name localejbs/WriteExcelFile, cannot resolve object reference. [Root exception is javax.naming.NamingException: Error occurs while the EJB Object Factory trying to resolve JNDI reference Reference Class Name: Type: clientAppName Content: sap.com/WriteExcelEAR Type: interfaceType Content: local Type: ejb-link Content: WriteExcelFile Type: jndi-name Content: WriteExcelFile Type: local-home Content: com.sap.aii.af.lib.mp.module.ModuleLocalHome Type: local Content: com.sap.aii.af.lib.mp.module.ModuleLocal com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/WriteExcelEAR; nested exception is: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/WriteExcelEAR] cannot be started. Reason: it has hard reference to resource [com.sap.xi.repository] with type [library], which is not active on the server. Hint: 1) Is referred resource deployed? 2) Is referred resource able to start? at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)
I am also getting the same warning when i am deploying the adapter.
Reference list in application-j2ee-engine.xml is as follows:
engine.security.facade
engine.j2ee14.facade
com.sap.aii.af.svc.facade
com.sap.aii.af.ifc.facade
com.sap.aii.af.lib.facade
com.sap.base.technology.facade
com.sap.xi.repository
Kindly help.
Edited by: Priyanka Sharma on Jun 18, 2010 4:29 PM

com.sap.xi.repository reference is not required,, how are you deploying your module on PI server,
You must be using some external library for excel conversion, if external library is present in your deployed file, you don't need to add com.sap.xi.repository reference.
Check:
Is EAR to SDA conversion needed for EJB EAR module
if you opt to use CECLT tool provided with NWDS 7.1, make sure you import SAP EAR File(it will have External library) on your local system.

Error during deploying MDM 7.1 Sp02 bussiness packages in CE7.1 using JSPM

Hello,
I am facing error when i am trying to deploy following MDM sca file in CE7.1 using JSPM
1. BPMDMAPP02_115.sca
2. BPMDMTECH02_115.sca
I have already deployed following SCA file into CE7.1 successfully.
3 .MDMJAVAAPI02_59.sca (deployed success)
is it mandatory that all sca files should be at same path level?currently API is at 59 and App and tech are at 115 .
I am using CE7.1 trail version , i could not find out SDM to deploy sca files,so i am using JSPM to deploy sca files.
Thanks & Regards,
Veeru.

Hi,
Yes, all three should be compatible to MDM server and should be at same patch level.
But i think reason for your deployment error is different.
I found this in SAP note no 1281637
"MDM standard Portal content (iViews) are supported on SAP NetWeaver 2004 and SAP NetWeaver 7.0 (2004s). At this time, there are no plans to migrate the content to be compatible to SAP NetWeaver CE 7.1.
Please Check Note 1281637 - Deployment errors on NW 7.1 CE for MDM portal content
Regards,
Shiv

MDM adapter Non-XML Inbound Messaging

Hi all,
I have a scenario where I transport a csv file via PI (NW711_05_REL) to MDM using the File adapter (sender) and MDM adapter 7.1 7.1 (receiver).
The message is sent through to the MDM port fine, and it seems to choose xml as default file type and PI MSG ID as file name.
This results in an xml file with csv content.
As I want to put the file on the port with its original file type (csv) and name, I need to tweak the MDM adapter a bit. For this I have tried to find MDM specific modules, but have been unable to do so.
I have found a u201Cwork aroundu201D by using u201CSet Adapter Specific Message Attributeu201D on the sender file adapter u2013 described on help.sap.com
Configuring the sender file adapter as described in http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/content.htm i am able to set the "FileName" attribute in dynamic configuration.
This enables me to get some of the desired effect, as the file on the MDM port is now a csv file u2013 half way there!! However the file name remains PI MSG ID...
Am I missing something here or is the adapter not working as intended? I donu2019t understand why it should only use the file type when the entire filename and type is there. I would assume that the entire filename and extension would be used in the MDM port.
I have tried achieving the desired result by using the "AF_Modules/DynamicConfigurationBean" on a JMS adapter, but the result is the same.
I would like to avoid developing my own custom module to handle this, as it seems like it should be possible to handle in a more standard way.
I hope someone out there can help me out, and hope to see a lot of good replies.
Best Regards,
Jesper

have you gone thur these settings?
Non-XML Inbound Messaging
When the backend system uses the PI File Adapter sender as the communication channel to deliver messages to the PI server, and the receiving MDM channel corresponds to an inbound MDM port of type other than XML (for example, Flat text file), then you must enable the File Adapter Specific Message Attribute named File Name as follows:
       1.      Edit the corresponding File Adapter sender communication channel.
       2.      In the Advanced tab, choose Set Adapter Specific Message Attribute.
       3.      Choose the File Name.
       4.      Save and activate the changes.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/frameset.htm

Issue with Receiver MDM Adapter - Integrated Configuration

Hi Experts,
My scenario is I need to pick a file from PI Directory and push it into MDM Ready folder.
The source file structure is ~ delimiter text file and at the receiving end , I need to push the same file as it is.
At the receiving side I have used MDM Adapter.
The issue at receiving side is:
I am receiving file with .xml extension with the same content as of source file but my requirement is .txt file.
Please advise on this.
I am using SAP PI 7.31.
P.S.- I have not used FTP at the receiver side due to some other concerns.
Thanks,
Vivek Jain

Hi Amit,
Thanks for the reply.
Yes we had tested successfully via SOAP UI as well (forgot to mention that). We are getting back the expected response in SOAP UI without using any credentials. We got the same response when we tested it through OS commands from PI server.
The WS is hosted by the target system and they haven't maintained any credentials at their end. So when PI is trying to access, we don't need to provide any credentials. My question is, whether the target system should keep any credentials to send the synchronous response back to PI (java stack). We have tried that as well but since there aren't any logs, we are unable to verify whether the credentials are coming correctly.
The service interfaces are correct and PI configuration are OK. I will try the XPI inspector for logs as you have suggested.
Thanks
Justin

Where to download MDM Business Content for PI 7.0/7.1?

Hi Everyone!
I kindly ask for your help on my problem: I am not able to find the MDM Business Content for PI 7.0/7.1 anywhere. I searched in the Service Marketplace for a long time, but without any results... https://websmp109.sap-ag.de/installMDM seemed to be a good place for it, as well as in "Software Distribution Center" -> "Support Packages and Patches" -> "SAP Content" -> "ESR Content (XI Content)", but neither supply the adequate file
Can anyone help me? Thank you very much!
Best regards
Benedikt

Christian, thank you very much!
Call me blind, but I still can't find it.
After Navigating to Support Packages and Patches --> SAP NetWeaver as suggested, I just have the following options:
SAP NETWEAVER
ADAPTIVE COMPUTING CONTROLLER
SAP NW IDENTITY MANAGEMENT
ACCEL. AD FOR SAP NETWEAVER
Technology components releases prior to SAP NetWeaver
When I follow to the first option (SAP NETWEAVER) I just have the options for various releases of SAP NetWeaver, but no MDM in one of them
Do you have another hint?

MDM Adapter: MDM Adapter listener could not start (MdmSecureSocketFactory)

Hi there,
We are running the following versions of the PI MDM adapter:
MDM_ADAPTER 710.700 SP7 (1000.710.700.7.0.20110411174317)
MDM_JAVA_API 710 SP5 (1000.710.0.5.111.20101227095400)
com.sap.mdm.tech.apireset 710 (710.20101227094734.0000)
com.sap.mdm.tech.connector 710 (710.20101227094734.0000)
com.sap.mdm.tech.mdm4j 710 (710.20101227094734.0000)
tc/mdm/adapter/svc 710.700 (8917411)
And the following versions on the MDM Server itself:
SHARED_COMP 7.1.05.104
MDS 7.1.05.104
MDIS 7.1.05.104
MDSS 7.1.05.106
MDLS 7.1.05.99
All the MDM adapters have the same error now:
MDM Adapter listener could not start due to:
com/sap/mdm/net/MdmSecureSocketFactory
Does anyone know what this error means?
Any help would be greatly appreciated
Lynton

Was just a version issue, the MDM java API and MDM adapter had different versions.....un-deploying and re-deploying solved the issue.
Lynton

MDM Adapter doubt

Hi
what are all the advantages of using MDM adpater in PI 7.1
1.Will MDM adapter accesses directly the repository (in console or data manager or syndicator)?
2.How MDM adapter can be compared with import manager or syndicator .
3. MDM adpater enables to load the data directly to any repository ?
4. how the integration of PI7.1 with MDM 7.1 takes place ?
am bit confused, can you pls explain ?
thanks
manian

Hi Manian,
Please go through this link; it will give you a good idea about the new features of MDM 7.1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d0b0e7-f144-2b10-17a2-982103c96ac0
Some key points on MDM-PI Adapter; this will definitely answer all your questions:
1. MDM 7.1 will offer new functionality to directly push/pull data into/from MDM using the MDM JAVA API.
2. The MDM PI Adapter will support SAP Netweaver PI 7.0 and 7.1
3. The MDM PI adapter is shipped as a separate file to be deployed on the PI adapter engine.
4. Message flow between PI and MDM can be monitored end to end (e.g. show if messages have been recieved and properly imported into MDM)
5. Error handling is improved because the Communication Channel in PI is pointing to one specific Repository Port.
6. Restarting of messages if a service is unavailable is possible.
7. Configuration/System landscape setup/Integration
       (a) MDM Adapter can be used instead of the File Adapter.
       (b) Configuration of FTP is no longer needed.
       (c) MDM Adapter is easy to implement and straight forward to monitor.
       (d) Higher reliability of data transfer.
8. Message Flow PI to MDM
       (a) Data sent from any connected system to PI is stored within PI's internal database.
       (b) XML message is forwarded to the defined communication channel (MDM PI Adapter).
       (c) MDM JCA Adapter itself invokes the MDM JAVA API sends the message to MDM using MDIS Port Functions.
       (d) Store the message in XMl format in XML format into the corresponding MDIS port folder so that MDIS can import the files independently.
       (e) "Finished import event" is thrown by MDIS and caught by the MDM JCA Adapter.
        (f) The import status is used to update the PI monitoring accordingly.
9. Message flow from MDM to PI
       (a) The Syndication event is triggered by MDSS as soon as the syndication is finished.
       (b) The data is available as XML file in the corresponding port folder.
       (c) The MDM JCA Adapter catches the syndication event and uses the MDSS Port functions to retrieve the data.
       (d) PI XMl message is created and sent to the PI AF for reciever determination and further message processing.
       (e) It is important to understand that only MDSS is able to throw the syndication event.
       (f) A manual syndication using the syndicator does not throw this event, meaning that the MDM 7.1 PI adapter is unable to pick the XMl message coming from manual syndication.
All these points should give you a very clear picture of all the abilities of MDM-PI Adapter.
Hope this will answer most of your questions.
Regards,
Varun

Receiver MDM adapter not working !!! Please suggest !!!

Hi Experts ,
mine is a idoc to MDM adapter scenerio. The idoc message is successfully passing the PI integration engine , but failing in the adapter engine ( MDM communication channel ) giving the following message.
Configuration error: Can not create repository session - server=xxxxxx.XX.XXXXXX.net serverUser=Admin repository=xxxxxxxx user=Admin]' caused by: The specified MDM repository was not found on the server (xxxxxx) Configured MDM access parameters for inbound port: [ MDM Server: xxxxx.xx.xxxxxx.net , Repository: xxxxxxxxxx , Port Code: CREMMDM0XIncrementalData , Remote System Code: ECC , DBMS Server: xxxxxx.xx.xxxxxx.net , DBMS Type: ORCL
I have tried connecting to the same MDM server using a receiver file adapter and it is working absolutely fine. But dont know why the mdm adapter is giving the following error. I have cross checked the adapter parameters with the MDM guy. They are OK.
I was wondering this was a version / service error, how can I chack the service pack of MDM Comm channel .
Please suggest . Urgent
Regards,
Arnab.
Edited by: Arnab Mondal on Jan 19, 2012 12:04 PM
Anything guys??
Any feed guys??
Edited by: Arnab Mondal on Jan 20, 2012 5:37 AM

Try a reset, which is similar to a computer restart and is done by pressing and holding the home button and the sleep/wake or on/off button simultaneously until you see the Apple logo and then release.

Reg: MDM adapter in PI 7.1

Dear All,
My scenario is IDOC PI(7.1) MDM(7.1) .
In moni it is showing successful and when checked in Runtime workbench for MDM adapter (receiver communication channel) it is showing error as,
"Message processing failed. Cause: java.lang.Exception: JNDI name of the ra connectionFactory is not configured. Go to the directory and create a value with name 'JNDIName' and value 'deployedAdapters/<ra name>/shareable/<ra name>' as module configuration data of the module 'ModuleProcessorExitBean' "
Can anyone suggest me on this.
Regards,
Lavanya.B

Hi Rajesh,
Thanks for the reply.In the Receiver MDM Adapter, we have two things,
Processing sequence
Module Name type Module key
localejbs/ModuleProcessorExitBean Local Enterprise Bean 1 (default)
Module Configuration
Module key Parameter Name Parameter Value
Could you please explain me in detail what need to filled as this is the first time I am configuring the MDM Adapter.
Regards,
Lavanya

MDM Adapter supporting PI 7.0 released with MDM 7.1

Hi,
I have imported the MDM adapter which supports PI 7.0 and is released with MDM7.1 to facilitate Syndication/Import of data from/to MDM and configured the sender channel in PI for the same to fetch the file from the outbound port of MDM server.
I observe that when file is syndicated to outbound port and is ready for PI processing, the adapter do not instantly fetch the file from outbound port even for hours but when i make a dummy change in Communication channel and again activate the same then it fetches the file and processes it in PI but after that if any other file is syndicated in the outbound port i have to again manually make a dummy change and activate it in PI and so on.
I found one Sap Note 1452509 which is relevant to this but want to know if the settings mentioned in SAP note are to be made on MDM server or PI and if there is any other setting which i have to make in channel or in MDM so that file is processed instantly/near real time manner.
I am on PI7.0
Thanks,
Amit

Hey Amit,
If you are talking about "Restart the MDM ADAPTER java component" then it will be done on PI server. MDM system does not have any java component.
This is a common error which we also faced, it happens often right after the restart of MDM server.
I have seen cases where when MDM server was restarted, we had to come to PI and restart the MDM Adapter services to make Sender MDM Adapter pick files from Ready folder.
>>if there is any other setting which i have to make in channel or in MDM
No other settings are required
Thanks
Aamir
Edited by: Aamir Suhail on Feb 7, 2011 5:44 PM

PI MDM Adapter Error - MDM port not found

We are working on an R/3 - PI - MDM scenario using the PI MDM Adapter. We are currently encountering the following errors.
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-08 15:31:22 Error Message could not be forwarded permantely to the JCA adapter. Reason: System error: MDM port not found
2009-09-08 15:31:22 Error Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found
2009-09-08 15:31:22 Error Adapter Framework caught exception: System error: MDM port not found
2009-09-08 15:31:22 Error Delivering the message to the application using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found.
Is there an issue with our receiver communication channel and the MDM Access Parameters? We are using the Port code and Remote System code provided by the MDM team.
Anyone experience this same issue?

We are no longer seeing the MDM Port Not found error, but we are still seeing the UnknownServer error. Looking at RWB Message Monitoring it appears that the message is successfully sent to the MDM server, but nothing is coming into the Ready folder. Any ideas on where the message is going, and why it is not showing up in the Ready folder?
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-11 14:04:15 Information The message was successfully received by the messaging system. Protocol: XI URL: http: //XXXXXXXX/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-09-11 14:04:15 Information Using connection MDM_http ://sap.com/xi/MDMAdapter. Trying to put the message into the receive queue.
2009-09-11 14:04:15 Information Message successfully put into the queue.
2009-09-11 14:04:15 Information The message was successfully retrieved from the receive queue.
2009-09-11 14:04:15 Information The message status was set to DLNG.
2009-09-11 14:04:15 Information Delivering to channel: MDS_TEST_CC
2009-09-11 14:04:15 Information The message was successfully delivered to the application using connection MDM_http ://sap.com/xi/MDMAdapter.
2009-09-11 14:04:15 Information The message status was set to DLVD.
I thought the implementation of the MDM Adapter was suppose to be straightforward and simple
Edited by: Chris Williar on Sep 11, 2009 9:56 PM

Deploying MDM adapter content in PI 7.1..

Similar Messages

Maybe you are looking for