Enter name for a new Unix Machine OR [Exit][Previous][Next]> next
§2.3.11 指定域名
<-------------------- Oracle WebLogic Configuration Wizard ------------------->
Select the target domain directory for this domain: ---------------------------------------------------
\\
Enter new Target Location OR [Exit][Previous][Next]> next
<-------------------- Oracle WebLogic Configuration Wizard ------------------->
Edit Domain Information: ------------------------
| Name | Value |
_|________|_____________| 1| *Name: | base_domain |
Enter value for \
<-------------------- Oracle WebLogic Configuration Wizard ------------------->
Edit Domain Information: ------------------------
| Name | Value | _|________|__________| 1| *Name: | weblogic |
Use above value or select another option: 1 - Modify \2 - Discard Changes
Enter option number to select OR [Exit][Previous][Next]> next
§2.3.12 创建域
<-------------------- Oracle WebLogic Configuration Wizard ------------------->
Creating Domain...
0% 25% 50% 75% 100%
[------------|------------|------------|------------]
[***************************************************]
**** Domain Created Successfully! ****
§2.4 创建受管服务器的域
参考《WebLogic 10.3 for Win32》－《创建受管服务器的Domain和Server》。 §2.5 配置和启动节点管理器 §2.5.1 直接运行
$ cd /bea/wlserver_10.3/server/bin $ ./startNodeManager.sh
§2.5.2 配置节点管理器作为Daemon
在/etc/rc.d/rc3.d添加一个启动节点管理器的文件。该文件核心内容是启动节点管理器，即： su - weblogic -c \这样，Linux启动后时自动启动节点管理器。 Runlevel
The term runlevel refers to a mode of operation in one of the computer operating systems that implement Unix System V-style initialization. Conventionally, seven runlevels exist, numbered from zero to six; though up to ten, from zero to nine, may be used. S is sometimes used as a synonym for one of the levels.
In standard practice, when a computer enters runlevel zero, it halts, and when it enters runlevel six, it reboots. The intermediate runlevels (1-5) differ in terms of which drives are mounted, and which network services are started. Lower run levels are useful for maintenance or emergency repairs, since they usually don't offer any network services at all. The particular details of runlevel configuration differ widely among operating systems, and slightly among system administrators.
The runlevel system replaced the traditional /etc/rc script used in Version 7 Unix.
Standard runlevels? Standard runlevels ID Name Description 0 Halt Shuts down the system.
S Single-User Mode Does not configure network interfaces or start daemons.[1]
6 Reboot Reboots the system.
1 = Almost all systems use runlevel 1 for this purpose. This mode is intended to provide a safe environment to perform system maintenance. Originally this runlevel provided a single terminal (console) interface running a root login shell. The increasing trend towards physical access to the computer during the boot process has led to changes in this area. Linux?
The Linux operating system can make use of runlevels through the programs of the sysvinit project. After the Linux kernel has booted, the init program reads the /etc/inittab file to determine the behavior for each runlevel. Unless the user specifies another value as a kernel boot parameter, the system will attempt to enter (start) the default runlevel. Typical Linux runlevels
Most Linux distributions, in addition to the standard runlevels, define the following additional runlevels: Typical Linux runlevels ID Name Description
1 Single-User Mode Does not: configure network interfaces, start daemons, or allow non-root logins.[2]
2 Multi-User Mode Does not: configure network interfaces or start daemons.[3]
3 Multi-User Mode with Networking Starts the system normally.[4]
4 Unused/User defined for special purposes 5 X11 As runlevel 3 + display manager.
^ = The additional behavior of this runlevel varies greatly. All distributions provide at least one virtual terminal. Some distributions start a login shell as the superuser; some require correctly entering the superuser's password first; others provide a login prompt, allowing any user access.
^ = In some cases, runlevels 2 and 3 function identically; offering a Multi-User Mode with Networking.
? Debian Linux
Debian, as well as most of the distributions based on it, like early Ubuntu, does not make any distinction between runlevels 2 to 5. Debian Linux runlevels ID Description 0 Halt
1 Single user mode
2-5 Full multi-user with console logins and display manager if installed 6 Reboot sidux?
sidux, a Debian Sid based distribution (current 20081110). This is the list for sidux operating system runlevels, please note that it does differ from debian stable runlevels. sidux Linux runlevels
ID Description
0 init 0 powers off the PC, halt 1 init 1 single user mode
2 init 2 Multi-User mode without network, and/or to stop or not enter X,
3 init 3 Multi-User mode with network not running the X Window System, and/or to stop or not enter X 4 init 4 to stop or not enter X
5 init 5 Multi-User mode with network running the X Window System, and/or to start X 6 init 6 Reboot
Ubuntu?
Ubuntu 6.10 (Edgy Eft) and later contain Upstart as a replacement for the traditional init-process, but they still use the traditional init scripts and Upstart's SysV-rc compatibility tools to start most services and emulate runlevels.
Red Hat Linux and Fedora?
Red Hat as well as most of its derivatives (such as CentOS) uses runlevels like this: Red Hat Linux/Fedora runlevels ID Description 0 Halt 1 Single user
2 Full multi-user with network enabled but most network services disabled 3 Full multi-user, console logins only 4 Not used/User definable
5 Full multi-user, with display manager as well as console logins 6 Reboot
Which services are started in which runlevels can be managed with the chkconfig tool, which keeps its configuration settings under /etc/rc.d/. /sbin/chkconfig --list lists all the services controlled by chkconfig and whether they are on/off for each runlevel. Setting a service A controlled by chkconfig, for levels X, Y and Z is as simple as /sbin/chkconfig --level XYZ A
SUSE Linux?
SUSE uses a similar setup to Red Hat: SUSE Linux runlevels ID Description 0 Halt 1 Single-user
2 Full multi-user with no networking 3 Full multi-user without display manager 4 Not used/User definable
5 Full multi-user with display manager 6 Reboot
The services that run under a specific runlevel can be modified with YaST | System Services (runlevel) or with chkconfig command like the Red Hat based distributions.
Slackware Linux?
Slackware Linux uses runlevel 1 for maintenance, as on other Linux distributions; runlevels 2, 3 and 5 identically configured for a console (with all services active); and runlevel 4 adds the X Window System. Slackware Linux runlevels ID Description 0 Halt 1 Single-user
2 Full multi-user NO display manager 3 Full multi-user NO display manager 4 Full multi-user with display manager 5 Not used/User definable 6 Reboot
Gentoo? Linux Gentoo Linux runlevels
ID Description 0 Halt 1 Single-user
2 Multi-user, no network
3 Full multi-user with display manager
4 Aliased for runlevel 3 (Full multi-user with display manager) 6 Reboot
System V Releases 3 and 4? System V runlevels
ID Description
0 Shut down system, power-off if hardware supports it (only available from the console)
1 Single-user mode, all filesystems unmounted but root, all processes except console processes killed 2 Multi-user mode
3 Multi-user mode with RFS (and NFS in release 4) filesystems exported
4 Multi-user, user-defined
5 Halt the operating system, go to firmware 6 Halt the system, reboot to default runlevel
s, S Identical to 1 (Single-user mode, all filesystems unmounted but root, all processes except console processes killed) except current terminal acts as the system console ? Solaris Solaris runlevels
ID Description
0 Operating system halted; (SPARC only) drop to OpenBoot prompt
