RADE

Source Code Manager

adl_admin_site

Administrating a site

Quick Reference

Abstract

The adl_admin_site command administrates an existing site.

Synopsis
Usage
Options
Examples
References

Synopsis

adl_admin_site [-h | -help | -?] (1)
adl_admin_site [-db database] -db_user table_creator -db_type database_type -db_size database_size -init_db [-install_dir directory] -target_dir directory (2)
adl_admin_site -init_profile -profile_type profile_type [-install_dir directory] -site_file site_info_file (3)
adl_admin_site -create_service | -remove_service -service_type service_type [-db database] [-start_at_boot] [-port port] [-fs_files directory] [-fs_data directory] (4)

Usage

To see all the existing site's names, run the [1] adl_ls_site command. To create a new site, run the [2] adl_mk_site command. To rename an existing site, run the [3] adl_ren_site command.

This command runs the administrator commands of an existing database and is used for managing a site. There are different usages of this command. You can:

(1) get the usage.
(2) generate sql scripts, into -target_dir directory, for initializing a new database.
(3) generate user or administrator profiles according to the current installation and the given central database.
(4) create or remove a service for the Monitor, the File Contents Server or the Multi-site Transfer Manager (Windows-NT only).

The database must be already created.

The database type is the type of database to initialize. This option is valid only for the case (2)

database_type = cdb, for a central database
database_type = monitor, for a monitor database
database_type = dept, for a departmental datatabase

The database size is the estimated database size regarding the amount of data and users

database_size = small, for a small database
database_size = medium, for a medium database
database_size = large, for a large database

The profile type gives the type of the profile to be generated

profile_type = user, for generating an user profile
profile_type = admin, for generating an administrator profile

The service type specifies for which daemon the service is to be created

service_type = monitor, for the Monitor
service_type = fcs, for the File Contents Server
service_type = transfer, for the Multi-site Transfer Manager

[Top]

Options

adl_admin_site accepts the following options:

`-h\|-help\|-?`	Help of the command
`-db database`	Identifier of an existing database
-db_user table_creator	database account granted for creating tables
-db_type database_type	type of database to initialize (for (2) only)
-db_size database_size	estimated database size regarding the amount of data and users
-init_db	to ask for generating (and possibly executing) sql scripts for the given database
-install_dir directory	path to the installation directory
-target_dir directory	target directory for data to be generated (must exist)
-init_profile	to ask for generating SCM profile
-profile_type profile_type	to specify what kind of profile to generate
-site_file site_info_file	path to a profile defining variables for the current site
-create_service	to ask for creating a new Windows-NT service for the Monitor or the File Contents Server (4)
-remove_service	to ask for removing an existing Windows-NT service (4)
-service_type service_type	to specify for which daemon the service is to be created
-start_at_boot	to specify that the given service must be automatically started at boot time.
-port port	port number for communicating with the Monitor or the File Contents Server (for (4) only)
-fs_file directory	file directory associated with the File Contents Server (for (4) only)
-fs_data directory	data directory associated with the File Contents Server (for (4) only)

[Top]

Examples

Creation of the sql scripts for initializing a new departmental database (Unix sample):

adl_admin_site –db SID –db_user adl –db_type dept –db_size small –init_db  –target_dir /tmp

[Top]

References

[1]	adl_ls_site: Listing all existing sites
[2]	adl_mk_site: Creating a new site
[3]	adl_ren_site: Renaming an existing site
[4]	Installing SCM on the SCM server(s)

[Top]

History

Version: 1 [May 2001]

Document created

[Top]