Attachment 160068 Details for Bug 249739 – use cases

use cases

(hide)

Description:

Filename:

MIME Type:

Creator: Noriko Hosoi

Created: 2007-07-26 19:54:04 UTC

Size: 13.64 KB

patch

obsolete

>1. Register one unregistered DS
>Steps:
>$ sbin/setup-ds.pl
>$ sbin/register-ds-admin.pl
>Beginning registration of the Directory Server
>==============================================================================
>Do you want to use this server as Configuration Directory Server?
>
>Directory server identifier [<serverID>]:
>
>==============================================================================
>The server must run as a specific user in a specific group.
>It is strongly recommended that this user should have no privileges
>on the computer (i.e. a non-root user).  The setup procedure
>will give this user/group some permissions in specific paths/files
>to perform server-specific operations.
>
>If you have not yet created a user and group for the server,
>create this user and group using your native operating
>system utilities.
>
>System User [nhosoi]:
>System Group [nhosoi]:
>
>==============================================================================
>Please specify the information about your configuration directory
>server.  The following information is required:
>- host (fully qualified), port (non-secure or secure), suffix,
>  protocol (ldap or ldaps) - this information should be provided in the
>  form of an LDAP url e.g. for non-secure
>ldap://host.example.com:389/o=NetscapeRoot
>  or for secure
>ldaps://host.example.com:636/o=NetscapeRoot
>- admin ID and password
>- admin domain
>- a CA certificate file may be required if you choose to use ldaps and
>  security has not yet been configured - the file must be in PEM/ASCII
>  format - specify the absolute path and filename
>
>Configuration directory server URL
>[ldap://<fqdn>:<port>/o=NetscapeRoot]:
>Configuration directory server admin ID [admin]:
>Configuration directory server admin password:
>Configuration directory server admin password (again):
>Configuration directory server admin domain [<domain>]:
>
>==============================================================================
>The information stored in the configuration directory server can be
>separated into different Administration Domains.  If you are managing
>multiple software releases at the same time, or managing information
>about multiple domains, you may use the Administration Domain to keep
>them separate.
>
>If you are not using administrative domains, press Enter to select the
>default.  Otherwise, enter some descriptive, unique name for the
>administration domain, such as the name of the organization
>responsible for managing the domain.
>
>Administration Domain [<domain>]:
>
>==============================================================================
>The Administration Server is separate from any of your web or application
>servers since it listens to a different port and access to it is
>restricted.
>
>Pick a port number between 1024 and 65535 to run your Administration
>Server on. You should NOT use a port number which you plan to
>run a web or application server on, rather, select a number which you
>will remember and which will not be used for anything else.
>
>The default in brackets was randomly selected from the available
>ports on your system.
>
>Administration port [9830]: <admport>
>
>==============================================================================
>Registering new Config DS: <serverID>
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID>:
>Beginning Admin Server creation . . .
>Creating Admin Server files and directories . . .
>Updating adm.conf . . .
>Updating admpw . . .
>Registering admin server with the configuration directory server . . .
>Updating adm.conf with information from configuration directory server . . .
>Updating the configuration for the httpd engine . . .
>Starting admin server . . .
>The admin server was successfully started.
>Admin server was successfully created, configured, and started.
>Finished registration of the Directory ServerExiting . . .
>Log file is '/tmp/setupvnRg6q.log'
>
>2. Register multiple unregistered DSes
>Steps:
>$ sbin/setup-ds.pl (repeat as needed; 3 servers in this sample)
>$ sbin/register-ds-admin.pl
>Beginning registration of the Directory Server
>==============================================================================
>Do you want to use this server as Configuration Directory Server?
>
>Directory server identifier [<serverID2>]:
>
>==============================================================================
>The server must run as a specific user in a specific group.
>It is strongly recommended that this user should have no privileges
>on the computer (i.e. a non-root user).  The setup procedure
>will give this user/group some permissions in specific paths/files
>to perform server-specific operations.
>
>If you have not yet created a user and group for the server,
>create this user and group using your native operating
>system utilities.
>
>System User [nhosoi]:
>System Group [nhosoi]:
>
>==============================================================================
>Please specify the information about your configuration directory
>server.  The following information is required:
>- host (fully qualified), port (non-secure or secure), suffix,
>  protocol (ldap or ldaps) - this information should be provided in the
>  form of an LDAP url e.g. for non-secure
>ldap://host.example.com:389/o=NetscapeRoot
>  or for secure
>ldaps://host.example.com:636/o=NetscapeRoot
>- admin ID and password
>- admin domain
>- a CA certificate file may be required if you choose to use ldaps and
>  security has not yet been configured - the file must be in PEM/ASCII
>  format - specify the absolute path and filename
>
>Configuration directory server URL
>[ldap://<fqdn>:<port2>/o=NetscapeRoot]:
>Configuration directory server admin ID [admin]:
>Configuration directory server admin password:
>Configuration directory server admin password (again):
>Configuration directory server admin domain [<domain>]:
>
>==============================================================================
>The information stored in the configuration directory server can be
>separated into different Administration Domains.  If you are managing
>multiple software releases at the same time, or managing information
>about multiple domains, you may use the Administration Domain to keep
>them separate.
>
>If you are not using administrative domains, press Enter to select the
>default.  Otherwise, enter some descriptive, unique name for the
>administration domain, such as the name of the organization
>responsible for managing the domain.
>
>Administration Domain [<domain>]:
>
>==============================================================================
>The Administration Server is separate from any of your web or application
>servers since it listens to a different port and access to it is
>restricted.
>
>Pick a port number between 1024 and 65535 to run your Administration
>Server on. You should NOT use a port number which you plan to
>run a web or application server on, rather, select a number which you
>will remember and which will not be used for anything else.
>
>The default in brackets was randomly selected from the available
>ports on your system.
>
>Administration port [9830]: <admport>
>
>==============================================================================
>Registering new Config DS: <serverID2>
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID2>:
>
>==============================================================================
>Registering Sub DSes:
>==============================================================================
>Please input the Directory Manager password on the server <serverID>:
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID3>:
>Beginning Admin Server creation . . .
>Creating Admin Server files and directories . . .
>Updating adm.conf . . .
>Updating admpw . . .
>Registering admin server with the configuration directory server . . .
>Updating adm.conf with information from configuration directory server . . .
>Updating the configuration for the httpd engine . . .
>Starting admin server . . .
>The admin server was successfully started.
>Admin server was successfully created, configured, and started.
>Finished registration of the Directory ServerExiting . . .
>Log file is '/tmp/setupAupV1E.log'
>
>Notes: You can choose any of the servers as a Configuration Directory
>Server.  Need to restart Sub Directory Servers to make the Pass Through
>Auth activated.
>
>3. Register one unregistered DS to the existing Configuration DS
>Steps:
>$ sbin/setup-ds-admin.pl
>$ sbin/setup-ds.pl
>$ sbin/register-ds-admin.pl
>Beginning registration of the Directory Server
>==============================================================================
>Do you want to use this server as Configuration Directory Server?
>
>Directory server identifier [<serverID>]:
>
>==============================================================================
>Registering new Config DS: <serverID>
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID>:
>
>==============================================================================
>Please input the password for the Administrator User uid=admin,
>ou=Administrators, ou=TopologyManagement, o=NetscapeRoot:
>
>==============================================================================
>Registering Sub DSes:
>==============================================================================
>Please input the Directory Manager password on the server <serverID2>:
>Beginning Admin Server reconfiguration . . .
>Creating Admin Server files and directories . . .
>Updating adm.conf . . .
>Updating admpw . . .
>Registering admin server with the configuration directory server . . .
>Updating adm.conf with information from configuration directory server . . .
>Updating the configuration for the httpd engine . . .
>Restarting admin server . . .
>The admin server was successfully started.
>Admin server was successfully reconfigured and started.
>Finished registration of the Directory ServerExiting . . .
>Log file is '/tmp/setupOUR8pL.log'
>
>4. Register multiple unregistered DS to the existing Configuration DS
>Steps:
>$ sbin/setup-ds-admin.pl
>$ sbin/setup-ds.pl (repeat as needed; 2 servers in this sample)
>$ sbin/register-ds-admin.pl
>Beginning registration of the Directory Server
>==============================================================================
>Do you want to use this server as Configuration Directory Server?
>
>Directory server identifier [<serverID>]:
>
>==============================================================================
>Registering new Config DS: <serverID>
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID>:
>
>==============================================================================
>Please input the password for the Administrator User uid=admin,
>ou=Administrators, ou=TopologyManagement, o=NetscapeRoot:
>
>==============================================================================
>Registering Sub DSes:
>==============================================================================
>Please input the Directory Manager password on the server <serverID2>:
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID3>:
>Beginning Admin Server reconfiguration . . .
>Creating Admin Server files and directories . . .
>Updating adm.conf . . .
>Updating admpw . . .
>Registering admin server with the configuration directory server . . .
>Updating adm.conf with information from configuration directory server . . .
>Updating the configuration for the httpd engine . . .
>Restarting admin server . . .
>The admin server was successfully started.
>Admin server was successfully reconfigured and started.
>Finished registration of the Directory ServerExiting . . .
>Log file is '/tmp/setupSVv1ga.log'
>
>5. Switch the Configuration Server from <serverID> to <serverID2>
>$ sbin/register-ds-admin.pl
>Beginning registration of the Directory Server
>==============================================================================
>Do you want to use this server as Configuration Directory Server?
>
>Directory server identifier [<serverID>]: <serverID2>
>
>==============================================================================
>Cleaning up old Config DS: <serverID>
>
>==============================================================================
>Please input the password for the Administrator User uid=admin,
>ou=Administrators, ou=TopologyManagement, o=NetscapeRoot:
>
>==============================================================================
>Registering new Config DS: <serverID2>
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID2>:
>
>==============================================================================
>Registering Sub DSes:
>==============================================================================
>Please input the Directory Manager password on the server <serverID3>:
>
>==============================================================================
>Please input the Directory Manager password on the server <serverID>:
>Beginning Admin Server reconfiguration . . .
>Creating Admin Server files and directories . . .
>Updating adm.conf . . .
>Updating admpw . . .
>Registering admin server with the configuration directory server . . .
>Updating adm.conf with information from configuration directory server . . .
>Updating the configuration for the httpd engine . . .
>Restarting admin server . . .
>The admin server was successfully started.
>Admin server was successfully reconfigured and started.
>Finished registration of the Directory ServerExiting . . .
>Log file is '/tmp/setupIYavPq.log'
>

Actions: View

Attachments on bug 249739: 160062 | 160063 | 160064 | 160066 | 160067 | 160068 | 160088