Hi Experts i am getting the error " java.net.ConnectException: Connection refused: connect ", while working on nwds 7.0.1 with mdm java api 7.1 sp02, netweaver server 7.1, jdk 1.6. is there any version problem between:- 1) nwds and netweaver server 2)nwds and mdm java api 3)nwds and jdk 4) or there is any other problem Thanks in advance Nitish Sharma
Hi Jun
Thanx for information
can you please tell the exact versions for combination.(nwds+nw AS+jdk+mdm java api) ??
Actualy i am trying to connect mdm with nwds, i tried with simple java project(mdm java api sample framework) its showing above error. Than i tried with j2ee project, i made ear file, but it is not getting deployed on j2ee engine that is present on pi.
can u tell me what could be the solutions for above problems.
Regards
Nitish Sharma
Hii jun
what combination will you suggest ,wchich require less configuration, also in which bpm can be implemented easily.
Also can you please give me solutions for above two problems.
Regards
Nitish Sharma
nw7.3+nwds7.3+mdm7.1+jdk1.6
i am using nwce7.2 sp6 +nwds7.2 sp6+ mdm7.1 sp8+jdk1.6
Hii jun
Did you face these errors
1) connection refused
2) ear file not getting deployed on j2ee engine
Regards
Nitish Sharma
Hi Jun
previously i was working with jdk 1.6+nwds 7.0+mdm 7.1
but now i installed jdk 1.4 according to your suggesion. But still its showing "connection refused error". and a pop-up with "fatal exception".
i made changes in nwds :-
1) window->prefrences->javadoc->C:\j2sdk1.4.2\bin\javadoc.exe
2)window->prefrences->installed libraries->(jre name: j2sdk1.4.2 and jre home directory: C:\j2sdk1.4.2)
are these changes correct, previously these path was for jdk 1.6?
and any other modification required. ??
Thanx in advance
Regards
Nitish Sharma
check the mdm java api you are using, which should match the version of your mdm server.
Hi jun
Now i am trying this scenario with eclipse 3.7 and jdk 1.6.
I am following this link:-
after running mdm java api framework, its showing same error: connection refused.
Please will you try this link, it hardly take 10 min to paste it.
Regards
Nitish Sharma
as i said, please use the right version of mdm java api, don't you see it?
additionally you can check the os admin, to see if there is any firewall which stop your connection
Hi jun
1) I got mdm java api form my friend, but dont how to check its version, can u tell me how to check..
2) and where to check that firewall problem.
Did u tried the link i sent u?
Regards
Nitish Sharma
why should i try......
Hi jun
firewall is off and mdm java api and mdm having same version.
I asked you to try that link because there is pre-bulit program to use mdm functinality, but thanks for your time.
Regards
Nitish sharma
is the sp version also same?
please post your code
Hi jun
Above link contains the mdm java api framework(programs) under prerequisite,you can download, than i followed the steps.
Regards
Nitish Sharma
Nitish,
I went through, all your replies. I want to know, which versions, currently, you are using for the following components. I faced the same problem and find out solution for the same problem, but first provide the following information for better understanding of your problem:
Thx/ -Tarun
Hi Tarun
i have said a thousand time, your java api version should match your mdm server version.
why you just not listen to it......
Nitish,
Your Java API Version (7.1 SP08) and MDM Server version (7.1 SP02) is mismatching. SAP recommends, to connect MDM Java API with MDM Server, the version of MDM Java API and MDM Server must be same.
Ask your Basis team to download MDM Java API 7.1 SP02, from SAP Service Marketplace. If you will replace your 7.1 SP08 api with 7.1 SP02 api, your problem will be resolved.
Please update us after performing suggested changes.
Thx/ -Tarun
Hi Nitish,
Your java API service pack and MDM service pack should be same.
Try with Service pack 02. Your problem should be removed.
Regards
Prateek Agarwal
Nitish,
If your query is resolved then please update this thread as answered/assumened answered.
Thx/ -Tarun
Hi Tarun
server is on some maintainance work, so problem is not solved yet...