cancel
Showing results for 
Search instead for 
Did you mean: 

UDDI Server login problem

Former Member
0 Kudos

Hi

I'm facing a problem logging into the "Test Registry" that comes default with the SAP J2EE engine. Though I provide the right credentials, the login gives me an error.

It says 'Registry Error: Connection refused: connect'.

What could be the problem? (I've created this user for this registry using Visual Administration' tool too)

Should I be doing something else?

Thanks,

Rajit

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This was solved in the topic

"Sneak Preview 6.40 UDDI Test Registry?"

by: Dan Boyce

but I'll just tell you the detailed version of the answer.

- In the "SAP J2EE Engine Administrator" (go.bat) expand to J2E -> Server 0... -> Services -> Web Services Container

- Select "Web Services Container" and look in the right pane.

- At the bottom there should be 4 tabs including "UDDI Client" and "UDDI Server".

- Click on "UDDI Client".

- Select "A Test Registry".

- Click "Edit registry".

- Add 50000 to each link as so:

http://localhost:50000/uddi/api/inquiry

http://localhost:50000/uddi/api/publish

- click "Save" - this will fix the "connection refused" error when you go to http://localhost:50000/uddiclient and try to use "A Test Registry". This is assuming you connect to the J2EE server interface using port 50000.

http://localhost:50000

- For anyone else who reads this, you have to setup an user in the "UDDI Server" tab as well, otherwise you can't authenticate to the UDDI registry (at the /uddiclient).

good luck!

modified

Benny
Product and Topic Expert
Product and Topic Expert
0 Kudos

This answer should be rewarded!

Former Member
0 Kudos

Hi Joel,

I appreciate your patience to give me a getailed answer. I wonder how I overlooked it although I was playing with those tabbed panes for a long time.

I guess I might have more q's reg publishing

Thanks a lot,

Rajit

Former Member
0 Kudos

Hi Joel,

I appreciate your patience to give me a getailed answer. I wonder how I overlooked it although I was playing with those tabbed panes for a long time.

I guess I might have more q's reg publishing

Thanks a lot,

Rajit

Former Member
0 Kudos

Hi Joel,

I appreciate your patience to give me a getailed answer. I wonder how I overlooked it although I was playing with those tabbed panes for a long time.

I guess I might have more q's reg publishing

Thanks a lot,

Rajit

Former Member
0 Kudos

Hi Joel!

Unfortunately I'm not able to use the UDDI Server provided by WAS 6.40 as it does only work with SAP DB and we have Oracle! This was not mentioned at all in the documentation on help.sap.com but only in SAP Note 641277!

Thus I have registered at the SAP UDDI Test Server at http://udditest.sap.com and I can logon with my user without any problems.

However, if I want to logon using the WAS 6.40 UDDI Client Tool (http://host:50000/uddiclient) I also get "Registry Error: Connection refused: connect".

I have setup the SAP UDDI Test Registry in the J2EE Admin Tool but I cannot access

https://udditest.sap.com:443/UDDI/api/inquiry/

https://udditest.sap.com:443/UDDI/api/publish/

or

http://udditest.sap.com/UDDI/api/inquiry/

http://udditest.sap.com/UDDI/api/publish/

using the WAS 6.40 UDDI Client Tool. What do I have to configure in the J2EE Admin Tool to make it work?

Regards, Tanja

Former Member
0 Kudos

When you say "I can logon", where are you logging on? SAP's web site, some UDDI Client, or something else?

If you login to uddi.sap.com, then you'll probably find the UDDI client there. I noticed there are "inquiry" and "publish" links at the top and some java utilities after I login. I think that's where your uddi client is.

As a catch-all, I'll just say this. I'm not 100% sure so someone catch me if I'm wrong but,

If you are running the J2EE Server on your computer, then you type

http://localhost:50000, then click on "UDDI Client" to access the uddiclient.

If you are running the J2EE Server on "HOST", then you login using

http://HOST:50000, then click on "UDDI Client" to access the uddiclient.

If you cannot connect to either of the links above, I'm assuming one of the following - neither you nor HOST are running the J2EE server, the HOST server is setup on a different port for security, HOST has blocked access to port 50000 using a firewall, or there is an authentication problem with your domain(?).

You'll have to ask the person running HOST how you can access their J2EE server. To access those four links you'll need to get that UDDI client running first, since they use SOAP protocol, and only want to talk to the uddi client.

Hope I've helped.

Joel

Former Member
0 Kudos

Hi!

> When you say "I can logon", where are you logging on?

I can logon to the SAP Test UDDI using SAP's web site http://udditest.sap.com.

> If you are running the J2EE Server on "HOST", then

> you login using

> http://HOST:50000, then click on "UDDI Client" to

> access the uddiclient.

I can access http://host:50000/uddiclient without any problems but when chose the SAP Test Registry then I cannot logon because of "Registry Error: Connection refused: connect".

I can logon to the UDDI Server running on my J2EE Engine using http://host:50000/uddiclient. However, the UDDI Server on my J2EE Engine is of no use as it is not possible to import the tModels when using Oracle instead of SAP DB. So I need to use some other UDDI Server.

I'd like to get this working with the SAP Test Registry to be able to deploy Web Services to a UDDI directly from the SAP Netweaver Developer Studio. The SAP Netweaver Developer Studio is also making use of http://host:50000/uddiclient.

Regards, Tanja

Former Member
0 Kudos

I have a suspicion that the problems being reported with the SAP UDDI Test Registry might be a result of it having been upgraded to a UDDI v3. The SAP UDDI server that is part of the UBR and the one that comes with 6.40 are UDDI v2. I have no idea if v3 is supposed to be backwards compatible with v2 clients. The SAP UDDI Test Registry is in beta stage right now though.

I'll try to find out some more about this and post back here.

Former Member
0 Kudos

Hi,

About UDDI v3 beta version,

If you are planning to publish to the UDDI registry, you should use the 'test' registries. These currently support UDDI V3 Beta, and are <b>backwards compatible with the UDDI V2 API.</b>

Above info is provide at http://www.soaprpc.com/archives/000005.html

Meanwhile we too are facing exactly similar problem at our end. Through VA we can publish the service in local registeries but it fails while connecting to udditest with similar error message i.e.

Registry Error. Connection timed out.

I've maintined proxy setting properly in Web Service Container --> UDDI client tab.

But is it somewhere else as well that we need to specify the proxy ? or related to something else ?

Former Member
0 Kudos

Hi,

Observed one thing. May be related to this.

UDDI page in help mentions a running

sap.com/com.sap.engine.services.webservices.tool

sap.com/tc~uddiapplication

as one of the prerequisites for UDDI publication.

When checked in VA at Application Tracking node, I could locate application

sap.com/com.sap.engine.services.webservices.tool

as running. But another one i.e.

sap.com/tc~uddiapplication

is missing from VA. Its not there in the list.

Rajit, or others who are facing this problem can you check this in VA ?

Regards,

Youvraj

Former Member
0 Kudos

Please ignore above comment about tc~uddiapplication. Thats not the problem.

Answers (1)

Answers (1)

Former Member
0 Kudos

Dears,

We know that is possible create aliases into the DNS server pointing to the real hostnames, We’ve done this already and it’s working!. The point key here is:

How to configure virtual hosts into “Sap Web Servicer”, in order to translate the real hostname machine “brjgs916” to the alias just created “uddi”, this will make the webserver respond to http://uddi:50100/uddiclient instead of http://brjgs916:50100/uddiclient?

How can we configure the sap webserver to respond by port 80 and port 50100 simultaneously; once we get knowing this, we should be able to configure the webserver to respond by the address http://uddi/uddiclient instead of http://uddi:50100/uddiclient?

Thanks a lot!

Luciana