MDM Server - Portal System Settings

Hi ,
Can anyone send a link to a good document on MDM Server and Portal system settings.
Best Regards
Sid

Hi Kunal,
Portal is just the Front end for the backend system MDM.
So if the performance in MDM is slow the same will be reflected even on the front end system.
To improve your MDM system you need to set the field properties in MDM correctly .
Basically your data modelling in MDM must be correct.
Kindly Follow the belwo links which will guide you in improving your system performance by efficient use of data modelling techniques:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10c4cd5f-6893-2a10-a2b0-f9cb3cd38a6f
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80fc0a2e-6561-2910-839e-8ff3e36dd4d6 (data modelling)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/eb7447b1-0c01-0010-8d90-a2e004cad537 (data modelling)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d8aa53-b11d-2a10-aca2-ff2bd42a8692 (data modelling)
Hope It Helped
Thanks & Regards
Simona Pinto

Similar Messages

MDM server user

Hello experts.
The developer requested me to take a look at the error.
MDM Adapter listener could not start due to: Can not create repository session '<server=turin serverUser=Admin repository=My_Catalog_Master user=pleaseMaintain>' caused by: The specified MDM repository was not found on the server
While i was investigating, i haven't found where the guy have specified that the serverUser was Admin. 'Cause, in fact, the server user had a passowrd that should be set somewhere (we removed the password, but devs want a password).
The error itself is not important, i just got curious about the server user.
anyone got a clue? the Communication channel have the user (the mdm repository user) but this Admin user
thanks
Thiago Delou

Hi,
By default, MDM Server takes System account i.e. windows user currently logged in. You can check this in Windows Services, while in Unix it asks for username at the time of server installation and by default it creates user=mdm. First try omitting serveruser parameter else try passing the login credentials of windows user. If you are at Unix then user=mdm should work for you.
Regards,
Jitesh Talreja

Error starting the MDM server in client system

Hi MDM Experts,
I am new to MDM and we have just installed MDM 5.5 on our system. We are able to 'Mount the Repository' via the MDM Console on the client side but when we try to 'Start MDM Server', we encounter the error below:
"Error starting MDM server: The machine (server name) is not Windows-based. The MDM server cannot be started from this application; please use CLIX on the machine instead."
What must we do to resolve this error? Please help us on this matter.
Thanks in advance!
ASP

Hi ASP,
MDM server operations can Be performed through Console only if your Server is Windows based.
You can perform the some repository options through Console ,but for any Server based operations like Mounting the server,Start/Stop server etc you will have to operate through the CLIX ie Command line interface.
I Guess yours is a Unix based system or something else which is not Windows based.
so it will not allow you,
Either you install your server on a windows based system to operate through Console.
Or if you want to continue with the NON windows based system then you will have to use CLIX for most of your Console opeartions.
Hope It Helped
Thanks & Regards
Simona Pinto

MDM 7.1 Portal Connectivity to MDM server

Hi all
I was running the MDM 7.1 ramp up version so far with full connectivity from the portal to MDM. I had configured both the standard business partner and a custom repository using the Portal Business Content . Now that I have migrated to the just released MDM 7.1 (GA ) , I am encountering the following error at the portal level . I am using the standard "Using Mapping" to connect to the MDM server from the portal and not the newly introduced "Trusted Connection" . Any body has any clue as to whats going wrong ..
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)... [see details]
DETAILED MESSAGE
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)
at com.sap.mdm.admin.utils.MdmConnectionProvider.createBlobObjectCache(MdmConnectionProvider.java:308)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.initContexts(MdmeBaseDynPage.java:364)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.doProcessBeforeOutput(MdmeBaseDynPage.java:154)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:127)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:126)
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:56)
... 38 more
Thanks
Ray

Hi Ray,
This is a trusted connection problem. For this you need to create allow.ip and deny.ip files in your server. In allow.ip you need to give those ip address through which you would be connecting to MDM server executable file(mds.exe) like in your case your portals ip address. And in deny.ip you need to specify those ip which you feel shouldnt connect to MDM server. After assigning this ip remember to restart your mds.
Also the users through which you are trying to connect to an MDM repository, their usernames must exist on the MDM repositoryu2019s Users table.
For more details please see page 299 from MDM 7.1 Console refernece guide
I hope I am able to solve your problem
Thans & Regards
Dilmit Chadha

Is it possible to install a consumer app for mass usage that would alter the ios device proxy settings? Over the air not supervised. Can an app company use an MDM server to do this if the customer consents?

Is it possible to install a consumer app for mass usage that would alter the ios device proxy settings? Over the air not supervised. Can an app company use an MDM server to do this if the customer consents?

HI Chris,
Thanks for taking the time to reply.
Could you expand on your answer, which bit is very doubtful?
Also in your knowledge would Apple work with a company and license it if the software they were developing was desired by consumer demand?
Thanks
Gary

MDM 5.5 SP03 - Error while connecting EP to MDM server

Hello colleagues,
I've deployed the following content of MDM 55 SP03 delivery to portal:
a. com.sap.mdm.tech.mdm4j.sda
b. com.sap.mdm.tech.connector.sda
c. BPMDMTECHN00_0.sca
d. BPMDMAPPLI00_0.sca
Then I created MDM system in Portal, arranged mapping but I couldn't
connect to MDM server using Connection test.
The MDM server is ip and running, port number in Portal is correct,
versions of deployed JAVA API and MDM connector fit to MDM server, user
mapping is correct too.
I actually have no idea what is the problem.
Are there any authorization requirements while connecting from EP to MDM Server?
Thanks and regards,
Konstantin.

Hi Nir,
Sorry for replying so late. I am following the steps given in the Business Package document.
1.I have created a system with system alias SAP_MDM_Repository_Customer(I want to connect to only customer repository) in a folder "Customer Repository".
2. I have created three groups MDM 5.5 SP3 Business Expert, MDM 5.5 SP3 MDM Admin, MDM 5.5 SP3 MD Expert
3. Then from the "Content provided by SAP" -> Specialist i am copying all the roles viz. Business Expert, Master Data Administrator, Master Data Expert. And then in the folder "Customer Repository" paste them as delta links.
4. Then in the user administration tab in the roles tab I am searching by group and adding the roles to these groups as below:
       Group                               Role
MDM 5.5 SP3 Business Expert      Business Expert
MDM 5.5 SP3 MDM Admin            Master Data Administrator
MDM 5.5 SP3 MD Expert            Master Data Expert
(Initially i have not adde eu_role but later i have added that also)
5. Then in the user mapping tab. I do the user mapping for the groups with the mdm repository users as below:
PortalUser           Group                 Repository
user
mdmuser    MDM 5.5 SP3 Business Expert     User/pwd
mdmadmin    MDM 5.5 SP3 MDM Admin           Admin/pwd
mdmexpert MDM 5.5 SP3 MD Expert           Expert/pwd
6. Then when i test the connection i get connection failed error.
7. When i add each roles in the "Everyone" group the connection test is successful but no data is displayed when i login with the portal user mdmuser no data is displayed.
Thats all. AFAIK i have covered every detail. Waiting for your reply.
Regards,
Jaydeep
Message was edited by: Jaydeep Kalmankar

Error connecting to MDM over Portal

Hi!
I have some difficulities with connecting to MDM repository over Portal. I have a working Java project, which connects to the repositroy and executes a search without error.
I developed a WD type DC where I want to use the previous Java program. So I put the java files into a package inside the WD project. The MDM jars have been deployed and added as "Used DC" to my WD DC. On the Portal there is an MDM system created. But when I test my first component, which should execute the search I got the following error message:
"java.lang.IllegalStateException: Login method has not been successfully called.
 at a2i.common.CatalogData.Preprocess(Unknown Source)
 at a2i.common.CatalogData.GetResultSet(Unknown Source)
 at com.sap.excercise.util.jani.MDM_data.Get(MDM_data.java:50)
 at com.sap.excercise.util.jani.Start.Check(Start.java:47)
 at com.sap.excercise.gp.wd.reqbupa.CReqBuPa.search(CReqBuPa.java:284)"
These error appear at the connection part of the code. The connection is done by the following code:
import a2i.common.CatalogData;
import a2i.generated.RC;
public class Connect {
 // file with connection specific information
 static private CatalogData catalog = null;
// // variables to be populated from a file
 static private String hostname = "localhost";
 static private int port = 2345;
 static private String username = "Admin";
 static private String password = "Admin";
 static private String language = "English [US]";
 static private int mincon;
 static private int maxcon;
 static private int timeout;
 static private String log;
 static private int logging;
 // used for single instance catalog object
 static private Object singletonLock = new Object();
 public CatalogData instance() {
 // if there is no catalog instance
 if (catalog == null) {
 // get a lock to create the singleton instances
 synchronized (singletonLock) {
 // check again
 if (catalog == null) {
 // get parameters of connection from property file
// loadProperties();
 // create catalogdata instance
 catalog = new CatalogData();
 // try logging in
 int resultLogin =
 catalog.Login(
 hostname,
 port,
 username,
 password,
 language
 if (resultLogin != RC.RC_OK) {
 System.out.println(
 "Error logging into MDM server: "
 + RC.GetTextForError(resultLogin)
 + " ("
 + resultLogin
 + ")");
 return null;
 System.out.println("nLogged into MDM server.");
 // return catalog instance
 return catalog;
 public void logout() {
 try {
 catalog.Logout();
 }catch (a2i.core.StringException e){ e.A2iPrintError(); }
 finally
 System.out.println("Finished.");
Have you any ideas this problem can be caused by?
Regards,
Peter

Hi Namrata,
I found the following description of com.sap.tech.mdm.tech.mdm4j:
Name: com.sap.mdm.tech.mdm4j.sda/
keyname: com.sap.mdm.tech.mdm4j
keyvendor: sap.com
keylocation: SAP AG
keycounter: 5.50.20061217101225.0000
Implementation-Title: com.sap.mdm.tech.mdm4j
Implementation-Vendor-Id: sap.com
Implementation-Version: 5.50.20061217101225.0000
Specification-Title: SAP MDM Java API
Specification-Vendor: SAP AG
Specification-Version: 5.5.4.3
Implementation-Vendor: SAP
componentelement: <componentelement name="com.sap.mdm.tech.mdm4j" vendor="sap.com" comp
onenttype="DC" subsystem="NO_SUBSYS" location="SAP AG" counter="5.50.2
0061217101225.0000" deltaversion="F" updateversion="LB-20061227155700"
componentprovider="SAP AG"/>

Exactly the project I am developing is a Web Dynpro type Development Component, so it is not a simple Web Dynpro Application. Thats why I have created another DC which includes all the MDM jars (Version 5.5.35.16) and added to my WD DC as "Used DC..".
Thanks,
Peter

MDM Server is responding very slow

Hi,
I am working with only 21,695 records and MDM Server is responding very slow.
MDM Server is running on Intel(R)Xeon(TM) 2.40Ghz 2.39Ghz, 3.89 GB of RAM.
System: Microsoft Windows Server 2003 Standard Edition Service Pack 2.
The hard disk partition F: has 43.7 GB Freespace.
It is impossible to do MDM Workflow matching and Merging with this slow speed.
Regards
Kaushik Banerjee

Hi Kaushik,
Please try to stop and restart the database server.
You can check the below:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_mdm/~form/handler7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31303132373435%7d
Re: MDM Server is very slow and locks users out
Hope it helps.
Thank you,
Priti

Error in MDM - EP integration : "Failed to connect to MDM server. ....."

Dear SDN,
I m in middle of configuring the MDM and EP integration.
EP Version Info :
J2EE Engine 6.40 PatchLevel 108290.313
Portal 6.0.20.0.0
BP has been installed.
We are able to view MDM system and MDM search IViews in the Wizards in the portal.
MDM Version Info : MDM 5.5 SP 04
I come across the following error :
Step 4: An error has occurred
Failed to connect to MDM server. Check your system. The server may be down or there may be an error in one or more of your system parameters.
System parameters are Server name and pwd .
This parameters are used to start the server and pwd for accessing the server while mounting the server.
Also at the same time, my MDM server is running and repository is shown loaded and running.
Kindly suggest what should have been missed out from our side or some way we can make sure that error does not occur.
Please help.
Regards,
Chandani Shah.

Hi Chandani,
in Portal clik on Personalization, and in User Mapping you need to map the MDM repository user (may be Admin)..... then try another time.
Please, check the BP version in order to unserstand if it is the rigjt version for your MDM.
Hoper this help you.
Regards,
Vito

What is the best approach to connect MDM server.

Hi Experts,
There are sevaral ways to connect MDM server from EP
1) Using JNDI look up
2) Throgh SystemAlias
Which one is best among performance wise, and can any body explain advantages and disadvantages
of all three.
Regards,
Sandeep.
Edited by: sandeep_ca Reddy on Aug 4, 2008 9:43 AM

Hi Sandeep,
Kindly go through the link below for information on
Accessing MDM Repositoryu2019s Data and Edit It, Create New Records through Portal
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40ac1b5b-d33e-2b10-5892-b29c890eaa01
This article uses the method of System Alias.
The second link gives you info on
Looking Up Enterprise Beans
http://help.sap.com/saphelp_nw04/helpdata/en/38/3e5a4201301453e10000000a155106/frameset.htm
I have done the EP integration with MDMusing System ALias. However I hav'nt done it using JNDI Lookup.
Hence it will be difficult to compare the performance of both the process. However, while working with System Alias, the performance was quite good as easily you can connect to the repository in a MDM server and then perform the User mapping. The fiurther process can be understood in the article mentioned above.
Hope it helps.
*kindly reward points if helpful
Thanks and Regards
Nitin Jain

EP not see MDM server

Hi Gurus
When I create a new MDM system in a Portal Content -> MDM Connection Wizard on step 4 (Select Repository) I cannot select any MDM repository because the drop-down empty. So I cannot finish the wizard and create a new MDM system reference in EP.
My EP (NW 7.00 SP13) and MDM Server (5.5 SP6) are running on the same host. In MDM Console I can connect to my MDM server and see the MDM repository mounted to it.
What is the problem with the MDM Connection Wizard? Maybe I specified the wrong properties on steps 1-3?
Please, help!
Thanks and Regards,
Sergei

>1. Verify that you have deployed the correct SCA files i.e. of compatible version with that of MDM Server
>2. Only running repositories would be visible in the drop down
>3. Try passing Server IP instead of Server Name
1. How can I check this? I deployed the following SCAs: BP_MDM_TECHNOLOGY (5.50.6.0), MDM_JAVA_API (5.50.6.0) & MDM_WEB_UI. My MDM server seems a little bit newer: it's version is 5.5.64.92. Can it cause the problem?
2. Yes, MDM server is running and the remote repository is loaded too.
3. I've tried this. No any changes in behavior.
In general when I come to the step Select Repository I do not see any delays. It seems the EP's wizard does not even try to connect to MDM server host which I specified on step 3. If, for example, I specify any unreachable wrong MDM Server host and go to step Select Repository it'll appear immediately without any connection attempts to the wrong host.
Maybe something need to be configured additionally? What I did was I installed MDM Server + Console, started the MDM server, created and mounted MDM repository located on the remote MS SQL Server, then I deployed the SCAs mentioned before and restarted my J2EE server.
Thanks and Regards,
Sergei

Error in starting MDM Server from MDM Console

Hi,
I have installed SAP MDM 5.5 SP05 on Windows 2003 Server.
When i try to start the MDM Server (i.e. MDM Service) from the MDM console it gives me the following error:
Error Starting apmdmd(MDM Server): The machine 'apmdmd' is not Windows-based. The MDM server cannot be started from this application; please use CLIX on the machine instead. 
But if i start the MDM Service manually and then mount the server, it works fine.
Kindly help.
Regards,
Chintan Sheth

It sounds to me like a problem potentially with either the permissions of the Windows user or perhaps a software firewall. The Console uses a low-level Windows API function to determine if the target machine on which MDS is installed is Windows-based. This function may be blocked by some OS or firewall-level setting. This may be the case even if you are able to use the same client machine to connect to the target machine via the Service Control Manager and start MDS from there.
I would like to help with this problem, but I need to know a few more things:
When the problem occurs, is the Console running on the same Windows machine as MDS?
You mentioned Windows 2003 Server... when you run the Console on this machine, are you logged in as an Administrator of the machine? And do you still get the error when you attempt to start MDS from within the Console?
Once MDS is started, and you mount it within the Console, are you having any other problems, such as logging in to a repository, or viewing logs?
Is there a firewall installed on the machine or machines that the software is installed on? We may have to review the settings of the firewall, or try temporarily disabling it (on both ends, or at least on the machine running MDS), to see if the problem goes away -- then we'll know the problem is with the firewall settings.
CLIX is a fine workaround if you can use it, but clearly this problem needs to be rectified.
-cleo

Problem with Application Server Portal 9.0.2.0.1.

I have a problem with Application Server Portal and Wireless 9.0.2.0.1.
Firstly I've installed the infrastructure on a Pentium 3 866Mhz 512Mb of Ram, with Windows 2000 Server (Italian) service pack 2.
I've maintained all predefined settings and I've chosen the UTF8 character set.
After installation, my infrastructure and OID works fine. The OID has port 4032 (as set by Oracle Universal Installer) instead of predefined 389.
After this I've installed Application Server Portal and Wireless on another host: a Pentium 3 733Mhz 384Mb of Ram, with Windows 2000 Server (Italian) service pack 2.
I've also maintained all predefined settings and automatic configuration of Portal and Wireless. I've pointed to my Infrastructure.
Try to test the Portal demonstration but an error occurred:
"SERVICE TEMPORARILY UNAVAILABLE. The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
On my EM Console I see: component instances 'OC4J_Portal' and 'OC4J_Demos' are UP, instead 'Portal:portal:7777' is down.
On the component lists I've clicked the link of component instance Portal:portal:7777, the 'control services' and 'Accessible Server SSO' are started, while 'Accessible Portal Repository' is down.
What can I do to get my portal started?

hi,
i have exactly the same problem. did you solve yours?
any suggestions or help how to do it?
thanks
erik
please reply to this post or [email protected]

An error occured on the server while reading settings

Hi to everyone,
Today i renewed my server's Profiles Manager Code Signing Certificate following this link http://support.apple.com/kb/HT5358
The certificate was renewed sucessfully for one year.
I switched the Profile Manager Off then next to "Sign configuration profiles" i clicked the Edit button and from the Certificate list, i selected the certificate named "myserver.mydomain.com Code Signing Certificate - myserver.mydomain.com OD Intermediate CA" which was the only listed certificate that i had renewed.
When i turned on the Profile Manager i faced the issue.
An error occured on the server while reading settings so the Profile Manager can't start.
From Logs
Error: The server '127.0.0.1' reported an error while processing a command of type: 'readSettings' in plug-in: 'servermgr_devicemgr'. Error: Error Domain=servermgr_devicemgr Code=1 "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendo r/rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb :941:in `initialize': could not connect to server: Connection refused (PGError)
Is the server running locally and accepting
          connections on Unix domain socket "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"?
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 941:in `connect'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 941:in `connect'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 217:in `initialize'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 37:in `new'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 37:in `postgresql_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:223:in `send'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:223:in `new_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:245:in `checkout_new_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:188:in `checkout'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:184:in `loop'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:184:in `checkout'
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor .rb:242:in `synchronize'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:183:in `checkout'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:98:in `connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:326:in `retrieve_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_sp ecification.rb:123:in `retrieve_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_sp ecification.rb:115:in `connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/base.rb:1299:in `table_exists?'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config /initializers/settings.rb:10
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activesupport/lib/active_support/dependencies.rb:173:in `load_without_new_constant_marking'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activesupport/lib/active_support/dependencies.rb:173:in `load'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:622:in `load_application_initializers'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:621:in `each'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:621:in `load_application_initializers'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:176:in `process'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config /environment.rb:55
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/railties/lib/commands/runner.rb:39
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /runner:3
" UserInfo=0x7ff048a8dc20 {NSLocalizedDescription=/Applications/Server.app/Contents/ServerRoot/usr/share/ devicemgr/backend/vendor/rails/activerecord/lib/active_record/connection_adapter s/postgresql_adapter.rb:941:in `initialize': could not connect to server: Connection refused (PGError)
          Is the server running locally and accepting
          connections on Unix domain socket "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"?
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 941:in `connect'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 941:in `connect'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 217:in `initialize'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 37:in `new'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb: 37:in `postgresql_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:223:in `send'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:223:in `new_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:245:in `checkout_new_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:188:in `checkout'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:184:in `loop'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:184:in `checkout'
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor .rb:242:in `synchronize'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:183:in `checkout'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:98:in `connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_po ol.rb:326:in `retrieve_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_sp ecification.rb:123:in `retrieve_connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/connection_adapters/abstract/connection_sp ecification.rb:115:in `connection'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activerecord/lib/active_record/base.rb:1299:in `table_exists?'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config /initializers/settings.rb:10
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activesupport/lib/active_support/dependencies.rb:173:in `load_without_new_constant_marking'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/activesupport/lib/active_support/dependencies.rb:173:in `load'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:622:in `load_application_initializers'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:621:in `each'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:621:in `load_application_initializers'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:176:in `process'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /../config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config /environment.rb:55
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /rails/railties/lib/commands/runner.rb:39
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'
          from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'
          from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/script /runner:3
Do anyone can help me ? I will appriciate it so much.
I' m looking forward to your reply.
Thanks a lot.
I

You were right!! After macboo reboot the issue was solved the Profile Manager started again without problems!!
Thaks a lot!!

Error while connecting to MDM server from Webdynpro

Hi ,
   I am trying to connect to MDM server (5.5 SP04 no patches) through a webdynpro application . The following is the piece of code that I am using as a test .
CatalogData CatalogData = new CatalogData();
    int resultLogin = 0;
    try {
          resultLogin = CatalogData.Login("USNOC01AQ05",2005,"Admin","Erico1234","English [US]");
    }catch(Exception e){
          wdContext.currentContextElement().setValueattr("Not Connected");
         //System.out.println("Error while establishing connection");
    if (resultLogin != RC.RC_OK){
          wdContext.currentContextElement().setValueattr("Not Connected");
         //System.out.println("Error logging to the SDM server");
         //System.exit(-1);
     wdContext.currentContextElement().setValueattr("Connected");
    //System.out.println("MDM server connected");
The import statements are as follows
import a2i.common.CatalogData;
import a2i.generated.RC;
I have put the following jar files in the java build path
MDM4J
mdm-admin
mdm-common
mdm-core
mdm-data
mdm-protocol
When I deploy my application I get the following error
java.lang.NoClassDefFoundError: a2i/common/CatalogData
It can't be determined from the exception chain, which class loader failed to load the above class. But at least the class loader of the current application does not contain a resource with name 'a2i/common/CatalogData'.
What do you guys think is the problem ?
Regards
DeepaK Singh

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

MDM Server - Portal System Settings

Similar Messages

Maybe you are looking for