Wolfegang. You can create a new publisher via jUDDI's "save_publisher" API ... this is not part of the UDDI specification (it's available in the BETA console). To do this you must first call "get_authToken" and pass a PUBLISHER_ID for an existing jUDDI publisher that has administrator priveldges. An Administrator has a value of "true" in the IS_ADMIN column of the PUBLISHER table.
Use the authToken returned in the save_publisher API call.
<save_publisher generic="1.0" xmlns="urn:juddi-org:api_v1">
<authInfo>*****</authInfo>
<publisher
publisherID="*****"
publisherName="*****"
admin="true"
enabled="false"
emailAddress="*****"/>
</save_publisher>
<authInfo>*****</authInfo>
<publisher
publisherID="*****"
publisherName="*****"
admin="true"
enabled="false"
emailAddress="*****"/>
</save_publisher>
Does that make sense?
I'm working on a new users guide that will do a better job of explaining this.
Steve
On 9/17/05, Wolfgang Schreiner <[EMAIL PROTECTED]> wrote:
got it, thanks a lot!
but when i want to save a publisher, i'll have to pass an authInfo token
along with the request and to retrieve an auth token, i'll have to
specify the user id. so, it's only possible to insert a publisher
directly via the database using sql-insert and then use the console to
call get_authToken, right?
and saving a business with the token i received also returns me an
"E_authTokenRequired (10120) An invalid authentication token was passed
to an API call that requires authentication. authToken" error
i'm a bit confused by now ...
Steve Viens wrote:
> To address the SOAP Fault issue first. I can't tell which of the
> publish API calls you were making but whichever it was it required
> that you pass it an authToken. To get an authToken you'll need to
> call the "get_authToken" API call and specify a userID. The userID is
> the value specified in the PUBLISHER_ID column of the PUBLISHER
> table. You'll need to replace the *** for the userID attribute (see
> the get_authToken example below where I've specified "jdoe" as the
> userID).
>
> If you're using the default authenticator then it doesn't matter what
> you specify as the password (this is the cred attribute in the
> get_authToken example below). The default authenticator ignores the
> cred attribute value.
>
> <?xml version="1.0" encoding="utf-8"?>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Body>
> <get_authToken generic="2.0" xmlns="urn:uddi-org:api_v2"
> userID="jdoe"
> cred="***"/>
> </soapenv:Body>
> </soapenv:Envelope>
>
> As for where the log file is created. You can change where you would
> like the log file created by including a path in the LOGFILE appender
> value in the log4j.xml file. You can find this log4j.xml file in the
> WEB-INF/classes directory.
>
> Because a path is not specified, where the log file is created is
> different for each app server. In this case Tomcat will create it in
> the /bin directory which is the the same directory in which Tomcat was
> started from. Does that make sense?
>
> Steve
>
>
>
>
>
>
> On 9/15/05, *Wolfgang Schreiner* <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>> wrote:
>
> steve, thanks for your reply
>
> i've made a stupid mistake:
> juddi.dataSource was set to jdbc/juddiDB instead of
> java:comp/env/jdbc/juddiDB
>
> but now i'll get the following:
>
> <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
> xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <soapenv:Fault>
> <faultcode>soapenv:Client</faultcode>
> <faultstring>E_authTokenRequired (10120) An invalid authentication
> token was passed to an API call that requires authentication.
> authToken:
> dontcare</faultstring>
> <detail>
> <dispositionReport generic="2.0 " operator="jUDDI.org"
> xmlns="urn:uddi-org:api_v2">
> <result errno="10120">
> <errInfo errCode="E_authTokenRequired"
> xsi:type="xsd:string">E_authTokenRequired (10120) An invalid
> authentication token was passed to an API call that requires
> authentication. authToken: dontcare</errInfo>
> </result>
> </dispositionReport>
> </detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
> and one more question: juddi.log resides in /bin directory. is
> that ok?
> why not /logs?
> regards
>
>
> Steve Viens wrote:
>
> > Hi Wolfgang,
> >
> > Is anything being logged on the server? Look for juddi.log. Please
> > provide App Server name and version as well as anything you find in
> > the log.
> >
> > The console assumes that the registry it's calling is accessable at
> > http://localhost:8080/juddi < http://localhost:8080/juddi>. If
> it's not then you will have to change
> > the following three lines in controller.jsp to point to the location
> > of your jUDDI registry.
> >
> > final URL INQUIRY_URL = new URL("
> http://localhost:8080/juddi/inquiry")
> < http://localhost:8080/juddi/inquiry%22%29>;
> > final URL PUBLISH_URL = new URL("
> http://localhost:8080/juddi/publish")
> <http://localhost:8080/juddi/publish%22%29>;
> > final URL ADMIN_URL = new URL("
> http://localhost:8080/juddi/admin")
> <http://localhost:8080/juddi/admin%22%29>;
> >
> > Steve
> >
> > On 9/15/05, *Wolfgang Schreiner* < [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>> wrote:
> >
> > Hi *,
> >
> > I decided to use HSQLDB for jUDDI information storage and
> deployment
> > actually worked fine. HSQL comes with a graphical administration
> > tool,
> > which I used to insert some PUBLISHER information and
> happijuddi.jsp
> > returns the following output:
> >
> > + Got a JNDI Context!
> > + Got a JDBC DataSource (dsname=java:comp/env/jdbc/juddiDB)
> > + Got a JDBC Connection!
> > + SELECT COUNT(*) FROM PUBLISHER = 1
> >
> > which made me confident that everything works properly.
> >
> > Unfortunately, the jUDDI Console returns a fault SOAP message
> > containing:
> >
> > <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
> > xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
> > http://www.w3.org/2001/XMLSchema-instance"
> <http://www.w3.org/2001/XMLSchema-instance%22>>
> > <soapenv:Body>
> > <soapenv:Fault>
> > <faultcode xmlns:ns1=" http://xml.apache.org/axis/"
> >
> < http://xml.apache.org/axis/%22>>ns1:Server.generalException</faultcode>
> > <faultstring></faultstring>
> > <faultactor></faultactor>
> > <detail/>
> > </soapenv:Fault>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> > So, what's wrong here? This happens with every get_*, save_*,
> > find_*, ... method I call via the Console
> >
> > regards,
> > Wolfgang
> >
> >
> >
>
>
