Error connecting to MDM over Portal

Question

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

Answer 1

Hi Namrata,
I found the following description of com.sap.tech.mdm.tech.mdm4j:
<i>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"/>
</i>
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