Monday, April 20, 2009
A whole new world
What will it look like when Oracle MySQL and Berkeley DB come together?
Which one is better Oracle Internet Directory(OID) or Sun Directory Server?
JAVA maybe is the only one that is needed by everyone
What will the fate of Solaris be, another Linux or FreeBSD?
Network is still computer, but Sun is no longer that Sun was.
Friday, April 3, 2009
Shell Programming Tips
$n:$1the first parameter,$2 the second one ...
$#:number of parameters
$0:name of current running program
$?:return value of command or function just have been called
$*:save all the parameters as "parameter 1, parameter 2, ..."
$@:save all the parameters as "parameter 1", "parameter 2", ...
$$:PID of this program
$!:PID of last program called by this program
read load value of variables from file
#cat VERSION
3.2.11
IFS=.
read MAJOR MINOR PATCH <> VERSION
Using &&
express1 && express2
the express right of "&&" will be executed when the left one return true.
Using ||
express1 || express2
the express right of "&&" will be executed when the left one fail to execute.
trap
trap " " 1 2 3 to ignore the SIGHUP SIGINT SIGQUIT signals
trap : 1 2 3 to receive the SIGHUP SIGINT SIGQUIT signals
Wednesday, February 27, 2008
Lustre File System at a glance
Lustre can be built from either a pre-packaged release or freely-available source code. Installing Lustre from a pre-existing package is quite straight-forward. Integrating Lustre into an existing kernel and building the associated Lustre software can be somewhat involved.
Lustre has been extensively tested with a selected set of distributions on i386, ia64, and x86_64 architectures, and also tested on PowerPC/PowerPC64 machines.
Lustre installation/configuration requires the following:
* Linux kernel patched with Lustre-specific patches
* Lustre modules compiled for the above kernel
* Lustre utilities required for configuration
Lustre Networking (LNET) software provides a network abstraction layer that simplifies using Lustre across multiple network types of. LNET and Lustre's administrative utilities require the following packages:
- readline: Install the -devel version of this package, which includes the header files.
Lustre releases prior to version 1.6 also require:
- libxml2: Install the -devel version of this package.
- Python: http://www.python.org
- PyXML: http://pyxml.sourceforge.net/
Several advanced Lustre functions, such as server failover, require packages and configuration outside of the scope of this document.
The RPMs/tarballs available on download site for every Lustre release:
- kernel-smp-
.rpm - Lustre-patched Linux kernel RPM; use with matching Lustre Utilities and Lustre Modules package below. - lustre-modules-
.rpm - The Lustre kernel modules for the above kernel. - lustre-
.rpm - Lustre Utilities - userspace utilities for configuring and running Lustre; please use only with matching kernel RPM, above. - kernel-source-
.rpm - Lustre-patched Linux kernel source RPM - companion to the kernel package; not required to build or use Lustre - lustre-source-
.rpm - Contains the Lustre source code (which includes the kernel patches), not required to build or use Lustre.
Lustre requires a number of patches to the core Linux kernel, mostly to export new functions, add features to ext3, and add a new locking path to the VFS. You can either patch your kernel with patches from the Lustre source tarball or download pre-patch kernel RPM along with matching lustre-lite-utils RPM.
There are two methods to install the Lustre software:
- Install using RPMs (easy, but you must use a CFS kernel)
- Install from source code (if you need your own kernel)
- Install the kernel RPM kernel-smp
.rpm - Install the Lustre modules lustre-modules-
.rpm - Install the utilities RPM lustre-
.i386.rpm - Update lilo.conf or grub.conf to boot your new kernel
- Reboot
The source code tarball for Lustre is located at: download site. As described above, Lustre requires a Linux kernel patched with some Lustre patches. A Lustre-patched kernel can be obtained in two ways:
- Patching a core kernel with the relevant kernel patches from this source code tarball following instructions at: kernel patch management wiki.
- Installing the pre-patched kernel RPM located at: download site
In general, CFS recommends that you obtain the pre-patched Lustre kernel RPM from download site. If you want to patch your own kernel:
1. Install quilt utility for patch management.
2. Copy the .config file in your kernel source, as it will be deleted in this process!
3. Refer to the lustre/kernel_patches/which_patch file to determine which patch series best fits your kernel.The example below shows a sample which_patch file:
SERIES MEMNONIC COMMENT
vanilla-2.4.24 linux-2.4.24 patch includes UML
rhel-2.4.21 linux-rhel-2.4.21-15 RHEL3 2.4.21
2.6-suse linux-2.6.5 SLES9 2.6.5
4. Unsupported kernels may have patches at the Lustre Users Group.
5. Follow the instructions in KernelPatchManagement to patch the kernel Once the kernel is patched, rebuild the kernel as follows:
a. make distclean (this step is important!) (make sure to include jbd and ext3 support in the kernel or in a module)
b. cp save-dot-config .config
c. make oldconfig dep bzImage modules (make sure that preemption is disabled (in 2.6), and modules are enabled)
d. update lilo.conf or grub/menu.lst
e. Reboot with the new kernel.
CFS suggests that you download the tarball for Lustre source code and extract the contents as in the following example (this example assumes that you are using Lustre v1.0):
src$ tar zxvf lustre-
The following are sample build instructions for Lustre:
Note: If you are using a CVS checkout, you will need to run the following to create the configure script (automake version 1.5 or greater is necessary):
lustre$ sh autogen.sh
If you are building Lustre against a pre-patched kernel-source RPM for an already-built kernel RPM, there are a few steps to do first. Otherwise, if you have already built the kernel you can skip these steps.
[linux]$ cp /boot/config-`uname -r` .config
[linux]$ make oldconfig || make menuconfig
# For 2.6 kernels
[linux]$ make include/asm
[linux]$ make include/linux/version.h
[linux]$ make SUBDIRS=scripts
# For 2.4 kernels
[linux]$ make dep
Now to build the Lustre RPMs:
$ cd /your/source/for/lustre
[lustre]$ ./configure --with-linux=/your/patched/kernel/sources
[lustre]$ make rpms
[edit]
Patchless client
The Lustre client (only!) can be built against an unpatched 2.6.15-16 kernel. This results in some small performance losses, but may be worthwhile to some users for maintenance reasons. The Lustre configure script will automatically detect the unpatched kernel and disable building the servers.
[lustre]$ ./configure --with-linux=/unpatched/kernel/source
Lustre system consists of 3 types of subsystems - Clients, a Metadata Server (MDS), and Object Storage Targets (OST's). All of these can co-exist on a single system or can be running on different systems. A Lustre client system can also optionally contain a Logical (Object) Volume manager (LOV) that can transparently manage several OST's; this component is required for achieving file striping.
It is possible to set up the Lustre system in many different configurations using the administrative utilities provided with Lustre. Lustre includes some sample scripts in the /usr/src/lustre-1.4.7/lustre/tests directory on a system where Lustre has been installed (or the lustre/tests subdirectory of a source code installation) that enable quick setup of some simple, standard configurations.
Note - if your distribution does not contain these examples, skip down do the "Using Supplied Configuration Tools" section. Verify your mounted system as below.
This section provides an overview of using these scripts to set up a simple Lustre installation.
1. Single System Test using the llmount.sh script:
The simplest Lustre installation is a configuration where all three subsystems execute on a single node. You can execute the script llmount.sh, located in the /usr/src/lustre-1.4.7/lustre/tests/ directory, to set up, initialize, and start the Lustre file system for a single node system. This script first executes a configuration script identified by a 'NAME' variable. This configuration script uses the lmc utility to generate a XML configuration file, which is then used by the lconf utility to do the actual system configuration. The llmount.sh script then loads all of the modules required by the specified configuration.
Next, the script creates small loopback filesystems in /tmp for the server nodes. You can change the size and location of these files by modifying the configuration script.
Finally, the script mounts the Lustre file system at the mount-point specified in the initial configuration script, the default used is /mnt/lustre. The following are all of the steps needed to configure and test Lustre for a single system: The llmount.sh script is mostly useful for initial testing with Lustre to hide many of the background steps needed to configure Lustre, it is not indended to be used as a configuration tool for production installations.
a. Starting the System: Two initial configuration scripts are provided for a single system test. Any changes to the loopback filesystem locations or sizes, or Lustre filesystem mountpoint have to be made in these scripts. i. local.sh: This script contains lmc commands that generate an XML (local.xml) configuration file for a system with a single MDS, OST, and Client. ii. lov.sh: This script contains lmc commands that generate a configuration file with an MDS, LOV, two OST's and a Client.
b. Execute the llmount.sh script as shown below, specifying setup based on either local.sh or lov.sh:
NAME={local|lov} sh llmount.sh
Sample output from executing this command on a random system looks like the following:
# NAME=local sh llmount.sh
config.portals ../utils/../portals
loading module: portals srcdir ../utils/../portals devdir libcfs
loading module: ksocknal srcdir ../utils/../portals devdir knals/socknal
loading module: obdclass srcdir ../utils/.. devdir obdclass
loading module: ptlrpc srcdir ../utils/.. devdir ptlrpc
loading module: ldlm srcdir ../utils/.. devdir ldlm
loading module: ost srcdir ../utils/.. devdir ost
loading module: fsfilt_ext3 srcdir ../utils/.. devdir obdclass
loading module: obdfilter srcdir ../utils/.. devdir obdfilter
loading module: mds srcdir ../utils/.. devdir mds
loading module: osc srcdir ../utils/.. devdir osc
loading module: mdc srcdir ../utils/.. devdir mdc
loading module: llite srcdir ../utils/.. devdir llite
The GDB module script is in /r/tmp/ogdb-localhost.localdomain
NETWORK: NET_localhost_tcp NET_localhost_tcp_UUID tcp localhost 988
LDLM: ldlm ldlm_UUID
OSD: ost1 ost1_UUID obdfilter /tmp/ost1 200000 ext3 no 0
MDSDEV: mds1 mds1_UUID /tmp/mds1 ext3 no
OSC: OSC_localhost.localdomain_ost1_MNT_localhost 2dd80_OSC_localhost.local_6c1af22326 ost1_UUID
MDC: MDC_localhost.localdomain_mds1_MNT_localhost 4d135_MDC_localhost.local_771336bde1 mds1_UUID
MTPT: MNT_localhost MNT_localhost_UUID /mnt/lustre mds1_UUID ost1_UUID
#
You can the verify that the file system has been mounted from the output of df:
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/ubd/0 1011928 362012 598512 38% /
/dev/ubd/1 6048320 3953304 1787776 69% /r
none 193712 16592 167120 10% /mnt/lustre
#
Note: The output of the df command following the output of the script shows that a Lustre filesystem as been mounted on the mount-point /mnt/lustre. The actual output of the script included with your Lustre installation may have changed due to enhancements or additional messages, but should resemble the example.
You can also verify that the Lustre stack has been set up correctly by observing the output of find /proc/fs/lustre:
# find /proc/fs/lustre
/proc/fs/lustre
/proc/fs/lustre/llite
....
/proc/fs/lustre/ldlm/ldlm/ldlm_canceld/service_stats
/proc/fs/lustre/ldlm/ldlm/ldlm_cbd
/proc/fs/lustre/ldlm/ldlm/ldlm_cbd/service_stats
#
Note: The actual output may depend on what modules are being inserted and what OBD devices are being instantiated. Also note that the filesystem statistics presented from /proc/fs/lustre are expected to be the same as those obtained from df.
c. Bringing down a cluster and cleanup using script llmountcleanup.sh:
Cleanup and unmounting of the filesystem can be done as shown below:
NAME=
d. Remounting the Filesystem using script llrmount.sh:
Remounting can be done with the llrmount.sh script as shown below. Using llmount.sh again will reformat the devices so llrmount.sh should be used if you want to keep the data in the filesystem:
NAME=
As described in earlier sections, Lustre uses clients, a metadata server, and object storage targets. It is possible to set up Lustre on either a single system or on multiple systems. The Lustre distribution comes with utilities that can be used to create configuration files easily and set up Lustre for various configurations. Lustre uses three administrative utilities - lmc, lconf, and lctl - to configure nodes for any of these topologies. The lmc utility can be used to create configuration files in the form of XML files that describe a configuration. The lconf utility uses the information in this configuration file to invoke low-level configuration utility lctl to actually configure systems. Further details on these utilities can be found in the man pages. The complete configuration for the whole cluster should be kept in a single file. The same file will be used on all the cluster nodes to configure the individual nodes.
The next few sections describe the process of setting up a variety of configurations.
Note: you can use "lconf -v" to show more verbose messages when running other lconf commands.
Important: You must use fstype = ext3 for Linux 2.4 kernels, and fstype = ldiskfs for 2.6 kernels. (In 2.4, Lustre patches the ext3 driver, and in 2.6 provides its own.)
1. Client, MDS, and two OSTs on a single node:
This is a simple configuration script where the client, MDS, and the OSTs are running on a single system. The lmc utility can be used to generate a configuration file for this as shown below. All the devices in the script below are shown to be loopback devices, but you can specify any device here. The size option is required only for the loopback devices; for others the utility will extract the size from the device parameters. (See Using Real Disks below).
#!/bin/sh
# local.sh
# Create node
rm -f local.xml
lmc -m local.xml --add node --node localhost
lmc -m local.xml --add net --node localhost --nid localhost --nettype tcp
# Configure MDS
lmc -m local.xml --format --add mds --node localhost --mds mds-test --fstype ext3 --dev /tmp/mds-test --size 50000
# Configure OSTs
lmc -m local.xml --add lov --lov lov-test --mds mds-test --stripe_sz 1048576 --stripe_cnt 0 --stripe_pattern 0
lmc -m local.xml --add ost --node localhost --lov lov-test --ost ost1-test --fstype ext3 --dev /tmp/ost1-test --size 100000
lmc -m local.xml --add ost --node localhost --lov lov-test --ost ost2-test --fstype ext3 --dev /tmp/ost2-test --size 100000
# Configure client
lmc -m local.xml --add mtpt --node localhost --path /mnt/lustre --mds mds-test --lov lov-test
When this script is run these commands create a local.xml file describing the specified configuration. The actual configuration could then be executed using the following command:
# Configuration using lconf
$ sh local.sh
$ lconf --reformat local.xml
This command would load all the required Lustre and Portals modules, and would also do all the low level configuration of every device using lctl. The reformat option here is essential at least the first time to initialize the filesystems on OST's and MDS's. If it is used on any subsequent attempts to bring up the Lustre system, it will re-initialize the filessystems.
2.Multiple Nodes
Lustre can also be set up on multiple systems, with the client on one or more systems, the MDS on another system, and the OSTs on yet other nodes. The following is an example of the configuration script that could be used to create such a setup. In the below examples, replace node-* with the hostnames of real systems. The servers, clients, and the node running the configuration script all need to be able to resolve those hostnames into IP addresses via DNS or /etc/hosts. One common problem with some Linux setups is that the hostname is mapped in /etc/hosts to 127.0.0.1, which causes the clients to be unable to communicate to the servers.
#!/bin/sh
# config.sh
# Create nodes
rm -f config.xml
lmc -m config.xml --add net --node node-mds --nid node-mds --nettype tcp
lmc -m config.xml --add net --node node-ost1 --nid node-ost1 --nettype tcp
lmc -m config.xml --add net --node node-ost2 --nid node-ost2 --nettype tcp
lmc -m config.xml --add net --node node-ost3 --nid node-ost3 --nettype tcp
lmc -m config.xml --add net --node client --nid '*' --nettype tcp
# Cofigure MDS
lmc -m config.xml --add mds --node node-mds --mds mds-test --fstype ext3 --dev /tmp/mds-test --size 50000
# Configures OSTs
lmc -m config.xml --add lov --lov lov-test --mds mds-test --stripe_sz 1048576 --stripe_cnt 0 --stripe_pattern 0
lmc -m config.xml --add ost --node node-ost1 --lov lov-test --ost ost1-test --fstype ext3 --dev /tmp/ost1-test --size 100000
lmc -m config.xml --add ost --node node-ost2 --lov lov-test --ost ost2-test --fstype ext3 --dev /tmp/ost2-test --size 100000
lmc -m config.xml --add ost --node node-ost3 --lov lov-test --ost ost3-test --fstype ext3 --dev /tmp/ost3-test --size 100000
# Configure client (this is a 'generic' client used for all client mounts)
lmc -m config.xml --add mtpt --node client --path /mnt/lustre --mds mds-test --lov lov-test
# Generate the config.xml (once). Put the file in a place where all nodes can get to it.
$ sh config.sh
# Start up OST's first
$ lconf --reformat --node node-ost1 config.xml
$ lconf --reformat --node node-ost2 config.xml
$ lconf --reformat --node node-ost3 config.xml
# Then MDS's (which try to connect to the OST's)
$ lconf --reformat --node node-mds config.xml
# And finally clients (which try to connect to OST's and MDS's).
$ lconf --node client config.xml
# Or use 0-config "mount" command for clients (see below)
$ mount -t lustre node-mds:/mds-test/client /mnt/lustre
Startup of clients and servers using lconf can actually occur in any order, but startup may block until all the servers that the node needs are up and communicating.
Lustre can use any physical device that can be formatted as an EXT3 filesystem. An entire scsi drive could be specified as --dev /dev/sdb, or a single partition could be specified as /dev/sdb2. The --reformat option to lconf will completely erase and reformat the drive or partition for use with Lustre - use with caution.
Lustre provides support for mounting the Lustre file system using a simple NFS-like mount command. The client configuration information is recorded on the MDS when the MDS is reformatted. Subsequently, when a mount command is invoked on the client, the configuration log on the MDS is read and the required devices setup and configured on the client. The filesystem mount-point is specified in the mount command. The XML file is not needed for 0-config clients. In order to support 0-config, you will have to modify your modprobe-configuration so that modprobe know how to load the modules for Lustre. The mount command will be similar to:
mount -t lustre [-o nettype=
A network type of tcp is the default. The client-profile is the client node name (passed as --node argument to lmc). Please note that for 0-config to work, the node must have a mount-point entry specified with lmc's --add mtpt command. The lustre/conf/modules.conf file illustrates the changes that need to be made to your modules.conf file for 0-config on linux-2.4:
# sample modules.conf for autoloading lustre modules on zeroconf clients
add below kptlrouter portals
add below ptlrpc ksocknal
add below llite lov osc
alias lustre llite
Modutils for linux-2.6 uses a different configuration-file. The entries should be added to modprobe.conf.local or to a new file in the /etc/modprobe.d/ directory:
# sample modprobe.conf.local for autoloading lustre modules on zeroconf clients
install kptlrouter /sbin/modprobe portals; /sbin/modprobe --ignore-install kptlrouter
install ptlrpc /sbin/modprobe ksocknal; /sbin/modprobe --ignore-install ptlrpc
install llite /sbin/modprobe lov; /sbin/modprobe osc; /sbin/modprobe --ignore-install llite
alias lustre llite
# sample modprobe.conf.local for autoloading lustre modules on zeroconf clients with elan
install kptlrouter /sbin/modprobe portals; /sbin/modprobe --ignore-install kptlrouter
install kqswnal /sbin/modprobe kptlrouter; /sbin/modprobe --ignore-install kqswnal
install ksocknal /sbin/modprobe kqswnal; /sbin/modprobe --ignore-install ksocknal
install ptlrpc /sbin/modprobe ksocknal; /sbin/modprobe --ignore-install ptlrpc
install llite /sbin/modprobe lov osc; /sbin/modprobe --ignore-install llite
alias lustre llite
Note that if you are working from RPM's then you must install the lustre-lite-utils RPM as well as the kernel RPM otherwise this will fail with the error:
LustreError: 6946:(llite_lib.c:540:lustre_fill_super()) Unable to process log:
LustreError: 6946:(llite_lib.c:603:lustre_fill_super()) Unable to process log: -clean
Once your Lustre filesystem has been mounted on a client, you are able to create files and directories subject to normal Linux file/directory permissions: touch /mnt/lustre/foo
Once your Lustre filesystem has been mounted on a client, you are able to create files and directories subject to normal Linux file/directory permissions: touch /mnt/lustre/fooTo get a sense of the performance of the file system, run the "vmstat" utility on the OSS's while creating files on the lustre file system. Using "iozone" will give a more accurate performance measure than "dd" in our example:
oss1> vmstat 1
oss2> vmstat 1
client> dd of=/mnt/lustre/bigfile if=/dev/zero bs=1048576
or
client> cd /mnt/lustre; iozone -a
The "bo" column from vmstat will show blocks (1024 bytes) out every second, so this gives a throughput rate in KB/sec.
A user-space library version of the Lustre file system is now available for some versions of Lustre, it gives a user application linked with the library access to Lustre file systems. The key goals for the library are to provide a portable mechanism to access Lustre from different POSIX compliant operating systems, to provide access from microkernel based systems and from the Windows operating system.
More information is available at LibLustreHowTo.
Monday, December 3, 2007
Google's BigTable
官方的 Google Reader blog 中有对BigTable 的解释。这是Google 内部开发的一个用来处理大数据量的系统。这种系统适合处理半结构化的数据比如 RSS 数据源。 以下发言是 Andrew Hitchcock 在 2005 年10月18号基于: Google 的工程师 Jeff Dean 在华盛顿大学的一次谈话 (Creative Commons License).
首先,BigTable 从 2004 年初就开始研发了,到现在为止已经用了将近8个月。(2005年2月)目前大概有100个左右的服务使用BigTable,比如: Print,Search History,Maps和 Orkut。根据Google的一贯做法,内部开发的BigTable是为跑在廉价的PC机上设计的。BigTable 让Google在提供新服务时的运行成本降低,最大限度地利用了计算能力。BigTable 是建立在 GFS ,Scheduler ,Lock Service 和 MapReduce 之上的。
每个Table都是一个多维的稀疏图 sparse map。Table 由行和列组成,并且每个存储单元 cell 都有一个时间戳。在不同的时间对同一个存储单元cell有多份拷贝,这样就可以记录数据的变动情况。在他的例子中,行是URLs ,列可以定义一个名字,比如:contents。Contents 字段就可以存储文件的数据。或者列名是:”language”,可以存储一个“EN”的语言代码字符串。
为了管理巨大的Table,把Table根据行分割,这些分割后的数据统称为:Tablets。每个Tablets大概有 100-200 MB,每个机器存储100个左右的 Tablets。底层的架构是:GFS。由于GFS是一种分布式的文件系统,采用Tablets的机制后,可以获得很好的负载均衡。比如:可以把经常响应 的表移动到其他空闲机器上,然后快速重建。
Tablets在系统中的存储方式是不可修改的 immutable 的SSTables,一台机器一个日志文件。当系统的内存满后,系统会压缩一些Tablets。由于Jeff在论述这点的时候说的很快,所以我没有时间把听到的都记录下来,因此下面是一个大概的说明:
压缩分为:主要和次要的两部分。次要的压缩仅仅包括几个Tablets,而主要的压缩时关于整个系统的压缩。主压缩有回收硬盘空间的功能。Tablets的位置实际上是存储在几个特殊的BigTable的存储单元cell中。看起来这是一个三层的系统。
客户端有一个指向METAO的Tablets的指针。如果METAO的Tablets被频繁使用,那个这台机器就会放弃其他的tablets专门支 持METAO这个Tablets。METAO tablets 保持着所有的META1的tablets的记录。这些tablets中包含着查找tablets的实际位置。(老实说翻译到这里,我也不太明白。)在这个 系统中不存在大的瓶颈,因为被频繁调用的数据已经被提前获得并进行了缓存。
现在我们返回到对 列的说明:列是类似下面的形式: family:optional_qualifier。在他的例子中,行:www.search-analysis.com 也许有列:”contents:其中包含html页面的代码。 “ anchor:cnn.com/news” 中包含着 相对应的url,”anchor:www.search-analysis.com/” 包含着链接的文字部分。列中包含着类型信息。
注意这里说的是列信息,而不是列类型。列的信息是如下信息,一般是:属性/规则。 比如:保存n份数据的拷贝 或者 保存数据n天长等等。当 tablets 重新建立的时候,就运用上面的规则,剔出不符合条件的记录。由于设计上的原因,列本身的创建是很容易的,但是跟列相关的功能确实非常复杂的,比如上文提到 的 类型和规则信息等。为了优化读取速度,列的功能被分割然后以组的方式存储在所建索引的机器上。这些被分割后的组作用于 列 ,然后被分割成不同的 SSTables。这种方式可以提高系统的性能,因为小的,频繁读取的列可以被单独存储,和那些大的不经常访问的列隔离开来。
在一台机器上的所有的 tablets 共享一个log,在一个包含1亿的tablets的集群中,这将会导致非常多的文件被打开和写操作。新的log块经常被创建,一般是64M大小,这个 GFS的块大小相等。当一个机器down掉后,控制机器就会重新发布他的log块到其他机器上继续进行处理。这台机器重建tablets然后询问控制机器 处理结构的存储位置,然后直接对重建后的数据进行处理。
这个系统中有很多冗余数据,因此在系统中大量使用了压缩技术。
Dean 对压缩的部分说的很快,我没有完全记下来,所以我还是说个大概吧:压缩前先寻找相似的 行,列,和时间 数据。
他们使用不同版本的: BMDiff 和 Zippy 技术。
BMDiff 提供给他们非常快的写速度: 100MB/s – 1000MB/s 。Zippy 是和 LZW 类似的。Zippy 并不像 LZW 或者 gzip 那样压缩比高,但是他处理速度非常快。
Dean 还给了一个关于压缩 web 蜘蛛数据的例子。这个例子的蜘蛛 包含 2.1B 的页面,行按照以下的方式命名:“com.cnn.www/index.html:http”.在未压缩前的web page 页面大小是:45.1 TB ,压缩后的大小是:4.2 TB , 只是原来的 9.2%。Links 数据压缩到原来的 13.9% , 链接文本数据压缩到原来的 12.7%。
Google 还有很多没有添加但是已经考虑的功能。
1. 数据操作表达式,这样可以把脚本发送到客户端来提供修改数据的功能。
2. 多行数据的事物支持。
3. 提高大数据存储单元的效率。
4. BigTable 作为服务运行。
好像:每个服务比如: maps 和 search history 历史搜索记录都有他们自己的集群运行 BigTable。
他们还考虑运行一个全局的 BigTable 系统,但这需要比较公平的分割资源和计算时间.
Tuesday, October 30, 2007
Solaris 10 and Net-SNMP
To disable Sun's SNMP
#svcadm disable svc:/application/management/snmpdx:default
the Net-SNMP daemon program locates at /usr/sfw/sbin/snmpd, and configure file of snmpd saved with the name snmpd.conf at /etc/sma/snmp. Use svcadm to start of stop snmpd:
#svcadm enable svc:/application/management/sma:default
#svcadm disable svc:/application/management/sma:default
Log File
if there's any error or warning messages, see the file /var/svc/log/application-management-sma\:default.log. The default log file of snmpd is /var/log/snmpd.log.
Configuration file
We may use /etc/sma/snmp/snmpd.conf.save as the working configure file to test wheather our snmpd daemon is ok.
#cp /etc/sma/snmp/snmpd.conf.save /etc/sma/snmp/snmpd.conf
#svcadm restart sma
P.S. There's another file also named as snmpd.conf stored in /var/sma_snmp directory, and which is called persistent storage file. The persistent storage file, /var/sma_snmp/snmpd.conf, contains USM security information and any MIB components that are set for persistent storage. This file also contains the engineID and the engineID boots. This persistent storage file is automatically updated when the System Management Agent starts. When the System Management Agent stops, the snmpusm and snmpvacm utilities write user security information to this storage file.
Using the AgentX Protocol
The AgentX protocol is supported in the System Management Agent. By default, the System Management Agent ships with a secure profile, that is, read–only access. AgentX allows interaction with third party subagents, provided that these subagents support AgentX over Unix Domain Sockets. For security reasons, AgentX is not supported over TCP/UDP. For more information on the AgentX protocol, see http://www.ietf.org/rfc/rfc2741.txt Edit the main /etc/sma/snmp/snmpd.conf configuration file to configure the System Management Agent to use the AgentX protocol. By default, the AgentX protocol is disabled. The following procedure describes how to enable the AgentX protocol. To enable the AgentX protocol add the following to /etc/sma/snmp/snmpd.conf file:
master agentx
restart the sma (system management agent).
# svcadm restart svc:/application/management/sma:default
Using the SMA
To view the status of the agent
# svcs svc:/application/management/sma:default
To See Which MIBs Are Initialized
# /usr/sfw/sbin/snmpd -Dregister_mib -Dmib_init -L
To Check the Disk Space and Network on a Local or Remote Machine
# /usr/sfw/bin/snmpwalk -v1 -c public localhost HOST-RESOURCES-MIB::hrStorageIndex
# /usr/sfw/bin/snmpget -v1 -c public localhost HOST-RESOURCES-MIB::hrStorageSize.1
# /usr/sfw/bin/snmpwalk -v1 -c public localhost HOST-RESOURCES-MIB::hrStorageUsed
# /usr/sfw/bin/snmpnetstat -v 2c -c public -a localhost
if all these works, congratulations, the sma is configured and brought on properly.
Tuesday, June 12, 2007
Common Array Manager
When all components above installed succsessfully, remember to modify your firewall settings and registry, or you'll get "Authentication failed" message when logining to the Java web console.
using regedit on your XP system and set
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest
to 0.
Wednesday, May 30, 2007
Sun Java Communications Suite 5 on Multi-Hosts
This deployment example contains the following sections:
- Summary of Changes
- About This Deployment Example
- Installing the Example
- Configuring Components
- Starting and Stopping Communications Services
- Accessing Sun Resources Online
Summary of Changes
The following describes the changes that have occurred from the Sun Java System Communications Services 6 2005Q4 single host installation example (as described in Deployment Example: Sun Java Communications Services 2005Q4 on a Single Host):
- Portal Server is no longer installed.
- Solaris™ Operating System (OS) 10 is used.
- Hosted domains are now configured.
- All Communications Express UI rendering elements are now deployed in the same web container to support Single Sign-On. As a result, Access Manager is no longer required for Communications Express and there are fewer configuration settings that you have to enter
About This Deployment Example
This section provides an overview of this deployment scenario, the hardware and software used, and the procedures you follow to install, configure, and use this deployment.
This section contains the following topics:
Installation Overview
This scenario results in a functioning deployment suited for the evaluation and testing of Sun Java Communications Suite 5. These instructions are merely intended to guide the evaluator through an initial installation.
What Components Are Installed?
This example guides you through installing the following Communications Suite and Java Enterprise System components:
- Sun Java System Messaging Server 6.3
- Sun Java System Calendar Server 6.3
- Sun Java System Communications Express 6.3
- Sun Java System Directory Preparation Tool 6.4
- Communications Services Delegated Administrator 6.4
- Sun Java System Web Server 7.0
- Sun Java System Message Queue 3.7 UR1
- Sun Java System Access Manager 7.1
- Sun Java System Directory Server Enterprise Edition 6.0
- All Shared Components
The example installation in this document uses the following data that you change according to your installation and test machine:
Recommended Ports
For convenience, this example uses a set of recommended ports. If you use different ports, be sure to make the changes consistently throughout the installation. For example, this document uses port 8800 for the Web Server admin port. If you decide to use port 3333 instead, be sure to change it everywhere 8800 occurs in the deployment example.
Note
Unless otherwise indicated, all of the examples and instructions in this document assume that you are logged in as root.
Implementation Specifications for This Example
This section describes implementation specifications for this example.
Table 3 Client Software Requirements
Component
Platform Requirement
Browser
Netscape™ Communication 7.1, Internet Explorer 6.0 sp4+, or Mozilla™ 1.7.12, Firefox 2.0.3
Summary of Installation and Configuration
Installing and configuring this example involves the following high-level steps:
- Preparing the system for Sun Java Communications Suite
- Running the Java ES installer and selecting the necessary components
- Installing Messaging Server, Calendar Server, Communications Express, Delegated Administrator, Instant Messaging, Web Server, Directory Server, and Access Manager software
- Configuring Delegated Administrator
- Configuring Messaging Server
- Configuring Calendar Server
- Configuring Communications Express
- Configuring users
Installing the Example
This section describes how to install and configure components on multiple systems for evaluation purposes. Some components are configured after installation, using component configuration tools.
This section contains the following topics:
Checking Installation Requirements
Before you install components, use the steps in this section to make sure the computer on which you are installing is ready.
To Check System Requirements
The computer should meet the following requirements:
To Check DNS
Verify that DNS is running and configured properly:
- Make sure that the /etc/resolv.conf file has name server entries with the IP addresses of valid name servers. For example:
- Make sure that the /etc/hosts file has an entry for the fully qualified host name of the server. This fully qualified host name should be listed before the non fully qualified host name. For example:
- Make sure that the /etc/nsswitch.conf file is configured to use files first to resolve host names. The hosts line in the nsswitch.conf file should list files first in its entry:
To Unzip the Sun Java Communications Services Zip Files
Installing the Components
You install Communications Suite components by running the Java Enterprise System installer.
To Start the Installer
- Log in as root to the machine on which you are installing Communications Suite software.
- Change to the JCS5 directory where you stored and unzipped the Communications Suite zip files.
- Change to the sun_java_commsuite5 directory
- Change to the Solaris_x8 platform directory.
- Start the Java Enterprise System installer in graphical mode.
./installer
- Click Next at the Welcome page.
- Accept the license.
- Select the Upgrade existing software radio button then click Next to continue.
- Select the following products then click Next:
- Click Next to upgrade shared components.
- The installer verifies system requirements. When the installer finishes, click Next.
The installer displays the Ready to Upgrade window.
- Click Next.
- Deselect the registration checkbox then click Install.
The upgrade begins. When the upgrade finishes, the Installation Complete page appears.
- Click Close to exit the installer.
- Restart the Java Enterprise System installer in graphical mode.
./installer &
- Click Next at the Welcome page.
- Accept the license.
The Choose to Upgrade window appears.
- Select the Install new software radio button then click Next to continue.
- Select the following products then click Next to Continue
- on mail.abc.beta.com select the following components:
- Sun Java System Messaging Server 6.3
- Sun Java System Calendar Server 6.3
- Sun Java System Message Queue 3.7 UR1
- on am.abc.beta.com select the following components:
- Sun Java System Communications Express 6.3
- Communications Services Delegated Administrator
- Sun Java System Web Server 7.0
- Sun Java System Access Manager 7.1 (only the required software; no Client SDK)
- on ds.abc.beta.com select the following components:
- Sun Java System Directory Server Enterprise Edition 6.0 (Core, Control Center, Command-Line Utility)
- Sun Java System Directory Preparation Tool 6.4
- on all systems select:
- All Shared Components
- Some versions of Solaris require that the Java SE SDK be upgraded prior to installation. If you are prompted to upgrade the Java SE SDK, choose the default selection to automatically upgrade the SDK to the version included with the installer. Then click Next to continue.
- Click Next to upgrade shared components.
- Specify the installation directories.
Locations:
- Directory Preparation Tool: /opt/SUNWcomds
- Directory Server: /opt/SUNWdsee
- Access Manager: /opt (will create /opt/SUNWam)
- Web Server: /opt (will create /opt/SUNWwbsvr7)
- Web Server Instance: /var/opt/SUNWwbsvr7
- Messaging Server: /opt/SUNWmsgsr
- Calendar Server: /opt (will create /opt/SUNWics5)
- Delegated Administrator: /opt/SUNWcomm
- Communications Express: /opt/SUNWuwc
- Accept the target directories for each product and click Next.
- The installer verifies system requirements, such as memory, disk space, and operating system patches. When done click Next.
- Choose Configure Now then click Next.
- The installer lists the components that must be configured after installation. This document informs you of the order in which to do so.
- Click Next to configure the remaining components. You configure these components as part of the installation process.
Continue with the following procedures to input the appropriate information for each of these products when prompted by the installer.
To Select Common and Web Server Settings
This installation assumes the use of Sun Java System Web Server. You can choose an alternate web container but that is beyond the scope of this document.
- In the Account Preferences Panel, you are asked whether or not you want to use your UserID and Password information for all administrator accounts, or if you want to provide administrator account information for each component.
Choose the All Administrator Accounts option and type admin for the Administrator User ID and adminpass for the Administrator Password then click Next.
- The installation script prompts for a series of options. The following table shows how to respond to the Common and Web Server configuration options.
To Select Directory Server Settings
- The following table shows how to respond to the Directory Server configuration options.
To Select Access Manager Settings
- The following table shows how to respond to the Access Manager configuration options.
To Install the Software
To Verify the Installation
Once the installation has completed, start LDAP and verify that it works.
- Verify that you can log in to the Access Manager console as amadmin. The URL for the Access Manager console is:
http://fully-qualified-hostname:web-server-port/amconsole
In this example, type:
http://am.abc.beta.com/amconsole
Use amadmin and adminpass as the user ID and password.
- After verifying that you can log in to the Access Manager console, log out.
- Proceed to Configuring Components for instructions on how to configure Communications Suite components.
Uninstalling the Components
After you complete your evaluation, you can use the Java Enterprise System uninstaller to remove the components that you installed. See the Sun Java Enterprise System 5 Installation Guide for UNIX:
Configuring Components
This section describes how to configure and start the components that you use in this example deployment.
This section contains the following topics:
Before You Begin
Before you configure the Messaging Server software, you need to create the mailsrv user and disable the sendmail process. The mailsrv user is used in Configuring Messaging Server.
To Create the mailsrv User
- Messaging Server requires a mail server user, which must exist before you can finish the installation. You can skip this step, because the group and user are created during the configuration time. However, you might want to create the mailsrv user yourself as shown below. For this installation, use the useradd command to create a user with username mailsrv and group mail. You use this ID in Step d (under Step 2).
Type the following commands to create the user mailsrv with a user ID of 7633, a group ID of mail, and a user home directory of /export/home/mailsrv on mail.abc.beta.com host. (This assumes the /export/home directory already exists.)
To Disable sendmail
Preparing the Directory and Configuring Messaging Server
This section explains how to prepare the Directory Server LDAP schema and configure Messaging Server.
To Apply Schema 2 to Your Directory Tree
- Run the comm_dssetup.pl script on ds.abc.beta.com:
cd /opt/SUNWcomds/sbin
/usr/bin/perl comm_dssetup.pl
- Type y to continue.
The perl script prompts for a series of options. The following table shows how to respond to the prompts.
- Confirm your choices and type y to continue. The comm_dssetup script proceeds.
- When prompted, type y to continue with script.
Continue with the next section after the comm_dssetup script finishes and displays its “Successful Completion” message.
Configuring Delegated Administrator and Communications CLI
This section describes configuring Delegated Administrator console and utility, which provide user management.
To Configure Delegated Administrator
- Run the configurator script on am.abc.beta.com:
cd /opt/SUNWcomm/sbin
./config-commda
- Click Next in the Welcome window.
- Accept the default for the Directory to store User Mgmt data files: [/var/opt/SUNWcomm]
If the directory does not exist, click Create Directory to create the directory.
- Install Delegated Administrator Utility, Console, and Server.
The installation script prompts for a series of options. Use the following table to respond to the configuration options:
- Select Configure Now.
The script begins to run.
- When the panel displays “All Tasks Passed,” click Next to continue.
Two warnings appear: one is remind you to restart Web Server; the other is to remind you to enable the mail and calendar services in the domain. The next steps correct these problems.
- Click Close to complete the configuration.
- Restart Web Server:
cd /var/opt/SUNWwbsvr7/https-am.abc.beta.com/bin
./stopserv
./startserv
- Modify the mail and calendar domains, and create users by using the commadmin utility:
Create as many users as you need. Steps later in this document show how to add Presence and Instant Messaging services to those users.
Configuring Messaging Server
This section describes configuring Messaging Server, including configuring the Webmail port.
To Configure Messaging Server
- Run the Messaging Server configure script on mail.abc.beta.com:
cd /opt/SUNWmsgsr/sbin
./configure
The Configuration Wizard appears. Read the introductory information and proceed by clicking Next.
- Verify the following:
- Fully qualified host name of Messaging Server, FQHN: [mail.abc.beta.com]
- Directory to store config/data files: [/var/opt/SUNWmsgsr]
When prompted, choose to create the new directory.
- Install MTA, Message Store, and Webmail Server. There is no need to install the Multiplexor for this deployment.
- Name of the mail server Unix user: Unix username [mailsrv]
- Unix group: [mail]
- The installation script prompts for a series of options. Use the following table to respond to the configuration options:
Table 9 Values for Messaging Server configure Script
Option
[Default Value]
Enter:
User/Group Server LDAP
[ldap://ds.abc.beta.com:389]
accept default
Bind As
[cn=Directory Manager]
accept default
Password
--
adminpass
Postmaster email address
--
alvin@abc.beta.com
Password for Messaging Server accounts
--
adminpass
Default email Domain
[abc.beta.com]
accept default
Organization DN
[o=abc.beta.com,o=beta.com]
accept default
- Click Next, then click Configure Now.
You will receive an error about the Webmail port being in use. Click OK to acknowledge this message. The configuration begins. The following step corrects the Webmail port problem.
- When the configuration is finished, click Next to continue, then click Close to exit.
Note
You might observe a failure such that not all the messaging configuration tasks have passed. If this is the case, rerun the Messaging Server configuration script by repeating all the steps above. When prompted for the directory to store configuration or data files, use the same directory as before. A popup window will state that this directory already exists. Click Accept Anyway to verify that the same directory will be used.
- (Option)Configure the Webmail port:
/opt/SUNWmsgsr/sbin/configutil -o service.http.port -v 8080
- Start Messaging Server:
/opt/SUNWmsgsr/sbin/stop-msg
/opt/SUNWmsgsr/sbin/start-msg
- Continue with the next section to configure Calendar Server.
Configuring Calendar Server
This section shows you how to run the Calendar Server configuration script and how to verify the Calendar Server configuration.
To Configure Calendar Server
- Run the Calendar Server configurator script on mail.abc.beta.com:
cd /opt/SUNWics5/cal/sbin
./csconfigurator.sh
- Click Next at the Welcome page.
- The installation script prompts for a series of options. Use the following table to respond to the configuration options:
Table 10 Values for Calendar Server csconfigure Script
Option
[Default Value]
Enter:
LDAP Server Host Name
[ds.abc.beta.com}
accept default
LDAP Server Port
[389]
accept default
Directory Manager DN
[cn=Directory Manager]
accept default
Directory Manager Password
--
adminpass
Enable Virtual Domains support
[Checked]
accept default
Virtual Domains setting: Default domain
[abc.beta.com]
accept default
Calendar Administrator Username
[calmaster]
accept default
Calendar Administrator Password
--
adminpass
Calendar Administrator Email address
[calmaster@abc.beta.com]
accept default
Site administrator
[Yes]
accept default
Set up a Front End/Back End deployment
[Unchecked]
accept default
Email Alarms
[Enabled]
accept default
Administrator Email Address
[calmaster@abc.beta.com]
accept default
SMTP Host Name
[mail.abc.beta.com]
accept default
Service Port
[80]
3080
Maximum Sessions
[5000]
accept default
Maximum Threads
[20]
accept default
Number of server processes
[1]
accept default
Runtime User ID
[icsuser]
accept default
Runtime Group ID
[icsgroup]
accept default
Start Calendar Server after Successful Configuration
[Unchecked]
accept default
Start Calendar Serve on System Startup
[Checked]
Unchecked
Configuration Directory
[/etc/opt/SUNWics5/config]
accept default
Database Directory
[/var/opt/SUNWics5/csdb]
accept default
Attachment Store Directory
[/var/opt/SUNWics5/astore]
accept default
Logs Directory
[/var/opt/SUNWics5/logs]
accept default
Temporary Files Directory
[/var/opt/SUNWics5/tmp]
accept default
Enable Archive
[Checked]
accept default
Archive Directory
[/var/opt/SUNWics5/csdb/archive]
accept default
Enable Hot Backup
[Checked]
accept default
Hot Backup Directory
[/var/opt/SUNWics5/csdb/hotbackup]
accept default
Keep archives for (in days)
[Minimum: 3, Maximum: 6]
accept default
Keep hot backups for (in days)
[Minimum: 3, Maximum: 6]
accept default
Same as archive checkbox
[Checked]
accept default
- Click the Configure Now button to configure Calendar Server.
The Configuration begins and takes less than two minutes.
- Click Next when the configuration is complete.
- Click the Details button to verify that all packages configured correctly. Click the Close button to exit the configurator.
- Start the Calendar Server daemons:
cd /opt/SUNWics5/cal/sbin
./stop-cal
./start-cal
- Continue with the next section to configure Communications Express.
Configuring Communications Express
This section shows you how to run the Communications Express configuration script.
To Configure Communications Express
- Run the Communications Express configurator script on am.abc.beta.com:
cd /opt/SUNWuwc/sbin
./config-uwc
- Click Next at the Welcome page.
- Accept the default for Directory to store configuration and data files: [/var/opt/SUNWuwc]
Choose to create the directory when prompted.
- Install the Mail and Calendar Components.
The installation script prompts for a series of options. Use the following table to respond to the configuration options:
Table 11 Values for config-uwc Script
Option
[Default Value]
Enter:
Hostname
[am]
accept default
DNS Domain
[abc.beta.com]
accept default
Web Container
[Web Server]
accept default
Web Server Root Directory
[/opt/SUNWwbsvr7]
accept default
Web Server Config Root Directory
[/var/opt/SUNWwbsvr7]
accept default
Web Server Instance Identifier
[am.abc.beta.com]
accept default
Virtual Server Identifier
[am.abc.beta.com]
accept default
HTTP Port
[80]
accept default
Administration Server Port
[8800]
accept default
Administrator User ID
[admin]
accept default
Administrator Password
--
adminpass
Secure Administration Server Instance
[Unchecked]
accept default
Web Container User ID
[webservd]
accept default
Web Container Group IP
[webservd]
accept default
URI Path
[/uwc]
Enable Hosted Domain Support
[Unchecked]
Checked (Yes)
URL of Directory Server
[ldap://wireless.comms.beta.com:389/]
ldap://ds.abc.beta.com:389/
Bind DN
[cn=Directory Manager]
accept default
Password
--
adminpass
DC Tree suffix
[o=beta.com]
accept default
Default Domain
[abc.beta.com]
accept default
Enable Access Manager for Single Sign-On
[Unchecked]
accept default (not enabled)
Webmail Server Host Name
[wireless.comms.beta.com]
mail.abc.beta.com
Webmail Server Port Number
--
80
Enable login in secure mode
[Unchecked]
accept default (not secure)
Webmail Server SSL Port Number
--
Leave blank
Webmail Admin User ID
--
admin
Admin Password
--
adminpass
Calendar Server Hostname
[wireless.comms.beta.com]
mail.abc.beta.com
Calendar Server Port
[9004]
3080
Calendar Admin User ID
[calmaster]
accept default
Calendar Administrator User Password
--
adminpass
URL of PAB Directory Server
[ldap://ds.abc.beta.com:389]
accept default
Bind As
[cn=Directory Manager]
accept default
Password
--
adminpass
- Click the Configure Now button to configure Communications Express.
- After the configuration is finished, click Next to continue.
The system displays a message to restart the Web Server instance.
- Click OK.
- Click Next to continue.
- Click Close to quit the Communications Express configurator script.
- Restart Web Server:
cd /var/opt/SUNWwbsvr7/https-am.abc.beta.com/bin
./stopserv
./startserv
Verifying the Configuration
This section describes how to verify the configuration for Communications Express client, Delegated Administrator, and Instant Messenger. You simply verify that you can log in to the various services. After you are satisfied that you can log in, log out.
- In your web browser, open the following URL for the Communications Express client:
http://am.abc.beta.com/mail
- Log in as one of the users created earlier.
If you created a user according to the previous steps, type alvin for the user name, and demo for the password.
- In your web browser, open the following URL for Delegated Administrator:
http://am.abc.beta.com/da/DA/Login
Log in as user admin. The password is adminpass.
- Continue with the next section to configure Access Manager.
Creating Additional User Accounts and Groups
This section describes how to create additional users accounts and groups. Users and groups created in this fashion work with both Communications Services products and Portal Server (if you add Portal Server to this deployment at a later date).
To Create End User Accounts and Groups
- The following example shows how to create users using the Delegated Administrator command-line utility and also how to create a group consisting of the users created.
/opt/SUNWcomm/bin/commadmin user create -D admin -F Demo -l demo1 -L One -n abc.beta.com -p 80 -w adminpass -W demo -X am.abc.beta.com -S mail,cal -E demo1@abc.beta.com -H mail.abc.beta.com
/opt/SUNWcomm/bin/commadmin user create -D admin -F Demo -l demo2 -L Two -n abc.beta.com -p 80 -w adminpass -W demo -X am.abc.beta.com -S mail,cal -E demo2@abc.beta.com -H am.abc.beta.com
/opt/SUNWcomm/bin/commadmin group create -D admin -G Demostaff -n abc.beta.com -p 80 -w adminpass -X am.abc.beta.com -S mail -E Demostaff@abc.beta.com -H mail.abc.beta.com -o calmaster -m demo1 -m demo2
To Create User Accounts by Using Delegated Administrator Console
An alternative to using the Delegated Administrator command-line utility to create users is to use the Delegated Administrator console. The high-level steps to create users with Delegated Administrator console are the following:
Prior to using Delegated Administrator, check the resource.properties file to make sure users will be created using options consistent with your usage. Because this example uses a hosted domain scenario, you do not need to edit this file to make changes. If you do want to make changes, perform the following steps.
- Change directories to /var/opt/SUNWcomm/WEB-INF/classes/sun/comm/cli/server/servlet and edit the resource.properties file on am.abc.beta.com.
The default settings for servicepackage refresh rates are as follows:
servicepackage-ttlhours=5
servicepackage-ttlminutes=0
These settings establish the time between refreshes of service packages. In a demo scenario, service packages do not change very often so there is no need to refresh them every five minutes. Instead, they are refreshed every five hours. This improves Delegated Administrator performance. If you later decide to change the refresh rate, for example, to 20 hours, then make this change:
servicepackage-ttlhours=20
The default setting for calendar ID type is set using the switch-caltype variable as follows:
switch-caltype=hosted
The caltype can either be hosted or legacy. When you set caltype to hosted, users are created as uid@domain rather than uid, when you use Delegated Administrator to create them.
- The first time you use Delegated Administrator console, you must add service packs to the organization that contains your users. In a web browser, open the URL for the Delegated Administrator console and log in as amadmin (password is adminpass):
http://am.abc.beta.com/da/DA/Login
- Click the check box next to the comms.beta.com organization, then click the Allocate Service Package button.
The Allocate Service Package window appears. Service packages are organized within a set of three pages.
- Click the Single Page button (to the right of the Compare button) to map the three pages into a single page view.
- Select the desired service packages.
Choose from among earth, mars, mercury, and venus, because they have mail and calendar services enabled. Each service package has a different mail quota.
- Click Next to continue.
- Accept the Mail Service defaults, then click Next.
- If you chose a service package that contains Calendar, type the Calendar Host wireless.comms.beta.com and Anonymous Login Yes. Then click Next.
- Select the quantity of each service pack desired then click Next.
A quantity of 100 is adequate for demo purposes.
- Review your choices and click Finish.
The service packages are created.
- Once the service packs have been allocated for the domain, you can now add users to the domain. Click the domain link, comms.beta.com.
- Click the New button to create a new user account within this domain.
- Type a First Name (such as Demo), Last Name (such as Five), Display Name (such as Demo Five), then click Next.
- There is no need to type postal information, so click Next.
- Select a service pack for this user, for example, earth, then click Next.
- Type the email address, for example, demo5@comms.beta.com. Mail Delivery Option should be Local Inbox. Leave the other fields blank.
- Click Next.
- Choose your calendar preferences and pick your preferred timezone. Then click Next.
- Type Login ID and Password. In this example, Login ID is demo5 and password is demo.
- Click Next to continue.
- Verify the user information then click Finish to create the user account.
- Log in to Access Manager as amadmin and verify that the IM and Presence services have been added to the newly created user. If not, assign services to those users as described previously in To Add Services to the Lower Level Organization.
Starting and Stopping Communications Services
This section describes the commands needed to start and stop all the Communications Services.
To Start and Stop Services
You should stop services before attempting to start them.
- To stop all services:
Table 12 Commands to Stop Communications Services
Service
Command
Instant Messaging
/opt/SUNWiim/sbin/imadmin stop
Access Manager
/etc/init.d/amserver stop
Web Server
/var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin/stopserv
Web Server Administrator
/var/opt/SUNWwbsvr7/admin-server/stopserv
Calendar Server
/opt/SUNWics5/cal/sbin/stop-cal
Messaging Server
/opt/SUNWmsgsr/sbin/stop-msg
Directory Server
/opt/SUNWdsee/ds6/bin/dsadm stop /var/opt/SUNWdsee/dsins1
- To start all services:
Table 13 Commands to Start Communications Services
Service
Command
Directory Server
/opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dsins1
Messaging Server
/opt/SUNWmsgsr/sbin/start-msg
Calendar Server
/opt/SUNWics5/cal/sbin/start-cal
Web Server Administrator
/var/opt/SUNWwbsvr7/admin-server/startserv
Web Server
/var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin/startserv
Access Manager
/etc/init.d/amserver start
Instant Messaging
/opt/SUNWiim/sbin/imadmin start
Accessing Sun Resources Online
The docs.sun.comSM web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities.
To access the following Sun resources, go to http://www.sun.com:
