Wednesday, April 13, 2016

[389-users] Re: 389 directory server console and httpd.worker process

On 04/13/2016 02:11 PM, xinhuan zheng wrote:
> I want to understand more about 389 directory server. There is a administrative console, 389-console, appearing to be a complete GUI written in Java. There is another process, httpd.worker. When I launch the 389-console, I need to type in (3) information. The administrative cn, bind passwor, and the URL of that httpd.worker is listening on. How does the GUI console interact with the httpd.worker? Who is submitting the requests to the directory server instance? The 389 GUI console or the httpd.worker? Why it needs two separate processes to interact with directory server? Is there a diagram to describe such interaction so I can visualize?
There are no diagrams, sorry. Basically you have the java console which
is just a client to the DS. Then there is the admin server which is
used to perform system tasks, like creating/deleting instances, stopping
& starting servers, etc. Once you are authenticated to the console
(console -> Admin Server(http) -> Directory Server), then it's the
console that issues all the ldap operations to the Directory Server.
> - xinhuan
> --
> 389 users mailing list
> 389-users@%(host_name)s
389 users mailing list

No comments:

Post a Comment