tracert命令概述
tracert是 trace rounte的缩写，即跟踪路由的意思。该命令是windows下的一个路由跟踪、诊断的实用程序，简单的说就是查看打开一个网站到底经过了几个网络节点。
该命令对于网管而言一般用于测试网络的连通性，确定网络故障的位置；对与广大站长而言就是测试一下到达自己所用主机经过的节点数，作为选择主机的一个参考指标（经过的节点数越少越好）。 More …
简介
Ping是一个验证网络上的两个主机之间连通性的分析工具。它发送网间控制报文协议(ICMP)的回应请求(Echo_Request)报文到一个远程IP地址，然后准备接收返回的ICMP应答报文。Ping程序的最初版本的作者是Mike Muss。自该程序诞生以来，已有许多人修改和重写它，并在不同程度上沿用了Ping这一思想。 More …
ipconfig 概述
ipconfig是调试计算机网络的常用命令，通常大家使用它显示计算机中网络适配器的IP地址、子网掩码及默认网关。其实这只是ipconfig的不带参数用法，而它的带参数用法，在网络应用中也是相当不错的。 More …
一、什么是Windows服务
Windows服务也称为Windows Service，它是Windows操作系统和Windows网络的基础，属于系统核心的一部分，它支持着整个Windows的各种操作。诸如DNS客户端、打印程序、Windows更新服务、计划任务、Windows时间服务、告警器等服务，它们关系到机器能否正确运行。如果不能适当地管理这些服务，就会影响到机器的正常操作。 More …
UBBCONFIG文件的定义
一个tuxedo应用系统的所有资源都在一个文本文件中定义，该文件被称为UBBCONFIG。在配置完成后，UBBCONFIG被编译成一个二进制的文件：TUXCONFIG。在tuxedo系统启动时，会从该文件中读取系统的配置信息。UBBCONFIG文件类似Windows下的*.ini文件。
UBBCONFIG文件的组成
UBBCONFIG包括以下8部分，我们称之为节。
RESOURCE(必须) –> 与整个系统有关的配置信息。
MACHINES（必须） –> 一个tuxedo应用系统可以跨越多台服务器，在该节中配置与每台服务器有关的信息。
GROUPS（必须） –> tuxedo中规定而服务可以被分为多个组，在该节中配置与组有关的信息。
SERVERS（可选） –> 与server有关的信息在该节中配置。
SERVICES（可选） –> 与service有关的信息在该节中配置。
NETWORK（可选） –> 与网络有关的信息在该节中配置。
ROUTING（可选） –> 路由规则在该节中配置。
NETGROUPS（可选） –> 与网络分组有关的信息在该节中配置。
RESOURCES（必须）参数
IPCKEY:
tuxedo使用它标识公告板及其他的IPC资源，它不能与服务器上其他的IPC资源的ID号冲突，其范围为32769–262142。
MASTER:
指定tuxedo应用系统的MASTER服务器，在该服务器上对整个tuxedo系统进行管理配置。
DOMAINID
是该tuxedo应用系统的唯一标识。
UID
可对该tuxedo应用系统进行管理的tuxedo系统管理员的用户ID，在unix下就是unix系统的用户ID，默认为执行tmloadcf的用户的ID。
GID
在unix下为UID所指定的用户所在组的ID。
PERM
指定对tuxedo系统IPC资源的存取权限。默认为0666，即任何人都可以对该IPC资源进行存取。
MAXACCESSERS:
设定在本系统的一个节点（一台服务器）上，可以同时有多少个进程访问该tuxedo系统的公告板，默认值为50。它包括本地客户端进程、server进程、service进程，但不包括管理进程，如：BBL、DBBL等。
MAXSERVERS:
设定在本系统中，总共可以有多少个server存在，包括进行管理的server，如：BBL、TMS等。默认值为50。
MAXSERVICES:
设定在本系统中，总共可以有多少个service存在，默认值为100。
MAXACCESSERS、MAXSERVERS和MAXSERVICES三个参数控制该tuxedo应用系统对IPC资源的使用情况。
示例：
*RESOURCES
IPCKEY 111111
PERM 0660
MASTER SXBOSS
MAXACCESSERS 4000
MAXSERVERS 2000
MAXSERVICES 4000
MAXNETGROUPS 200
MAXGTT 200
MAXCONV 100
SCANUNIT 10
SANITYSCAN 5
BBLQUERY 180
BLOCKTIME 900
MODEL SHM
SYSTEM_ACCESS PROTECTED,NO_OVERRIDE
LDBAL Y
MACHINES（必须）参数
LMID
物理处理器名，可以通过”uname –n”或节点名得到
TUXDIR
TUXEDO系统软件安装位置
APPDIR
应用服务位置全路径
TUXCONFIG
TUXEDO配置文件全路径
ENVFILE
环境文件全路径
TYPE
指定该服务器类型，当两台服务器类型不同时，在它们之间传送数据要进行编码/解码工作
ULOGPFX
指定应用日志文件所在的目录及前缀。
UID、GID、PERM、MAXACCESSERS、MAXCONV在这里可以被重新配置，以这里为准
示例：
*MACHINES
nas3_old LMID=SXBOSS
TYPE=AIX
APPDIR=”/boss18/run/bin”
TUXCONFIG=”/boss18/run/cfg/tuxconfig”
TUXDIR=”/bea/tuxedo8.1″
ULOGPFX=”/boss18/run/log/ULOG”
MAXWSCLIENTS=2000
GROUPS（必须）参数
一台机器至少要定义一个服务组。如果没有定义组，管理命令tmadmin可能依然能运行。每个组只要定义组名，映射组名的组号和逻辑机器名。组为分布式交易系统和数据依赖路由等灵活性措施提供了支持。
常见参数意义
组名
组的唯一标识符，可以是字母数字
GRPNO
组的唯一数字标识符
LMID
逻辑机器名
示例：
*GROUPS
OPENGRP_SXBOSS LMID=SXBOSS GRPNO=50
CHGGRP_SXBOSS LMID=SXBOSS GRPNO=60
PAYGRP_SXBOSS LMID=SXBOSS GRPNO=70
QRYGRP_SXBOSS LMID=SXBOSS GRPNO=80
CONGRP_SXBOSS LMID=SXBOSS GRPNO=90
WTCGRP_SXBOSS LMID=SXBOSS GRPNO=190 OPENINFO=NONE
WTCGRP_SXBOSS1 LMID=SXBOSS GRPNO=196 OPENINFO=NONE
SERVERS（可选）参数
SRVGRP
服务属于一个在*GROUPS节中定义的服务组名
SRVID
该Server所对应的ID。在组中应该唯一
MIN
最少启动的进程数
MAX
最多启动的进程数
RESTART
如果设成Y，则服务可以重启动
GRAC，MAXGEN
在GRACE定义时间之内，服务可以重启动MAXGEN次
RCMD
每次服务重启动要执行的一个可执行文件名
CLOPT
跟随服务启动的其他参数
-A 服务内建交易全发布
–r 指定服务记录时间戳，用于以后计算交易处理时间
-e 定义标准错误重定向文件
-o 定义标准输出重定向文件
— TUXEDO参数和服务特定参数的分隔符
… 传给tpsvrinit()的参数
示例：
DEFAULT:
CLOPT=”-A ” SRVGRP=OPENGRP_SXBOSS
RESTART=Y GRACE=0 MAXGEN=10
SERVICES（可选）参数
BUFTYPE
任何向该交易的请求，数据应该是此处定义类型
SRVGRP
交易所在服务所在的组
LOAD
负载因子，表示处理请求的时间，用于计算负载平衡，默认为50
PRIO
优先级，默认为50
示例：
*SERVICES
DEPOSIT BUFTYPE=”FML”
SRVGRP=BANKB1
LOAD=25 PRIO=70
参考链接：
http://tcaosmail-gmail-com.javaeye.com/blog/362630
tuxedo应用系统
一个tuxedo应用系统包括服务端及客户端。服务端安装在服务器上，客户端一般安装在PC机上。从开发角度讲，一个tuxedo应用系统包括服务端程序、客户端程序和一个配置文件。此外，一个tuxedo应用系统可以部署在一台服务器上，也可以部署在多台服务器上。 More …
tmshutdown命令用于关闭所有或部分应用并释放IPC资源。
本命令所有参数与tmboot类似（如：-A，-g，-i，-s，-S），意义相同。
tmshutdown的特殊参数有：
-c
当有客户端正在连接时，tmshutdown不能关闭管理服务。参数-c则可以超越次规则。该参数仅用于管理员需要立即关机而又无法及时通知客户端时。
-P
在非主控节点上，可以用-P参数仅关闭该机器上的应用。
示例：
tmboot -s s1104Cfm;
s1104Cfm为服务名。
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
以下是BEA的官方参考文档：http://e-docs.bea.com/tuxedo/tux80/atmi/rfcmd35.htm#1335246
tmshutdown(1)
Name
tmshutdown—Shuts down a set of BEA Tuxedo servers.
Synopsis
tmshutdown [options]
Description
tmshutdown stops the execution of a set of servers or removes the advertisements of a set of services listed in a configuration file. Only the administrator of the bulletin board (as indicated by the UID parameter in the configuration file) or root can invoke the tmshutdown command. tmshutdown can be invoked only on the machine identified as MASTER in the RESOURCES section of the configuration file, or the backup acting as the MASTER, that is, with the DBBL already running (via the master command in tmadmin(1)). An exception to this is the -P option which is used on partitioned processors (see below).
With no options, tmshutdown stops all administrative, TMS, and gateway servers, and servers listed in the SERVERS section of the configuration file named by the TUXCONFIG environment variable, and removes the IPC resources associated with them. For each group, all servers in the SERVERS section, if any, are shut down, followed by any associated gateway servers (for foreign groups) and TMS servers. Administrative servers are shut down last.
Application servers without SEQUENCE parameters are shut down first in reverse order of the server entries in the configuration file, followed by servers with SEQUENCE parameters that are shut down from high to low sequence number. If two or more servers in the SERVERS section of the configuration file have the same SEQUENCE parameter, then tmshutdown may shut down these servers in parallel. Each entry in the SERVERS section may have an optional MIN and MAX parameter. tmshutdown shuts down all occurrences of a server (up to MAX occurrences) for each server entry, unless the -i option is specified; using the -i option causes individual occurrences to be shut down.
If it is not possible to shut down a server, or remove a service advertisement, a diagnostic is written on the central event log (see userlog(3c)). The following is a description of all options:
-l lmid
For each group whose associated LMID parameter is lmid, all servers in the SERVERS section associated with the group are shut down, followed by any TMS and gateway servers associated with the group.
-g grpname
All servers in the SERVERS section associated with the specified group (that is, for which the SRVGRP parameter is set to grpname) are shut down, followed by all TMS and gateway servers for the group. TMS servers are shut down based on the TMSNAME and TMSCOUNT parameters for the group entry. For a foreign group, the gateway servers for the associated entry in the HOST section are shut down based on GATENAME and GATECOUNT. Shutting down a gateway implies not only that the process itself is stopped; it also implies that the administrative service for the gateway and all advertised foreign services are unadvertised.
-i srvid
All servers in the SERVERS section for which the SRVID parameter is set to srvid are shut down. Do not enter a value for SRVID greater than 30,000; this indicates system processes (that is, TMSs or gateway servers) that should only be shut down via the -l or -g option.
-s aout
All servers listed in the SERVERS section with the name aout are shut down. This option can also be used to shut down TMS and gateway servers.
-o sequence
All servers in the SERVERS section for which the SEQUENCE parameter is set to sequence are shut down.
-S
All servers listed in the SERVERS section are shut down.
-A
All administrative servers are shut down.
-M
This option shuts down administrative servers on the master machine. The BBL is shut down on the MASTER machine, and the BRIDGE is shut down if the LAN option and a NETWORK entry are specified in the configuration file. If the MODEL is MP, the DBBL administrative server is shut down.
-B lmid
The BBL on the processor with the logical name lmid is shut down.
-T grpname
All TMS servers for the server group for which the SRVGRP parameter is set to grpname are shut down (based on the TMSNAME and TMSCOUNT parameters associated with the server group entry).
-w delay
Tells tmshutdown to suspend all selected servers immediately and waits for shutdown confirmation for only delay seconds before forcing the server to shut down by sending a SIGTERM and then a SIGKILL signal to the server.
Because the SIGKILL signal cannot be trapped, any process that receives it is terminated immediately, regardless of the code being executed by the process at that time. Such behavior may cause structural damage to the bulletin board if the process being stopped was updating the bulletin board when it was terminated.
Note: Servers to which the -w option may be applied should not catch the UNIX signal SIGTERM.
Note: When a server is shut down based on receipt of a SIGKILL signal, entries may remain in the bulletin board. When the bulletin board liaison (BBL) is due to shut down, these entries are detected and the BBL does not shut down. A second tmshutdown command may be required to complete system shutdown.
-k {TERM | KILL}
tmshutdown suspends all selected servers immediately and forces them to shut down in an orderly fashion (TERM) or preemptively (KILL).
Because the SIGKILL signal cannot be trapped, any process that receives it is terminated immediately, regardless of the code being executed by the process at that time. Such behavior may cause structural damage to the bulletin board if the process being stopped was updating the bulletin board when it was terminated.
Note: This option maps to the UNIX signals SIGTERM and SIGKILL on platforms that support them. By default, a SIGTERM initiates an orderly shutdown in a BEA Tuxedo server. If SIGTERM is reset by an application, the BEA Tuxedo system may be unable to shut down the server.
Note: When a server is shut down based on receipt of a SIGKILL signal, entries may remain in the bulletin board. When the bulletin board liaison (BBL) is due to shut down, these entries are detected and the BBL does not shut down. A second tmshutdown command may be required to complete system shutdown.
-y
Assumes a yes answer to a prompt that asks whether all administrative and server processes should be shut down. (The prompt appears only when the command is entered with none of the limiting options.)
When the -y option is specified, all services are unadvertised immediately from the bulletin board and any subsequent service calls fail.
-q
Suppresses the printing of the execution sequence on standard output. It implies -y.
-n
The execution sequence is printed, but not performed.
-R
For migration operations only, shuts down a server on the original processor without deleting its bulletin board entry in preparation for migration to another processor. The -R option must be used with either the -l or -g option (for example, tmshutdown -l lmid -R). The MIGRATE option must be specified in the RESOURCES section of the configuration file.
-c
Shuts down BBLs even if clients are still attached.
-H lmid
On a uniprocessor, all administrative and applications servers on the node associated with the specified lmid are shut down. On a multiprocessor (for example, 3B4000), all PEs are shut down, even if only one PE is specified.
-P lmid
With this option, tmshutdown attaches to the bulletin board on the specified lmid, ensures that this lmid is partitioned from the rest of the application (that is, that it does not have access to the DBBL), and shuts down all administrative and application servers. It must be run on the processor associated with the lmid in the MACHINES section of the configuration file.
The -l, -g, -s, and -T options cause TMS servers to be shut down; the -l, -g, and -s options cause gateway servers to be shut down; the -l, -g, -i, -s, -o, and -S options apply to application servers; the -A, -M, and -B options apply only to administrative processes. When the -l, -g, -i, -o, and -s options are used in combination, only servers that satisfy all the qualifications specified are shut down.
If the distributed transaction processing feature is being used such that global transactions are in progress when servers are shut down, transactions that have not yet reached the point at which a commit is logged after a precommit are aborted; transactions that have reached the commit point are completed when the servers (for example, TMS) are booted again.
Interoperability
tmshutdown must run on the master node. In an interoperating application the master node must be running the highest release available. tmshutdown detects and reports configuration file conditions that would lead to the shutting down of Release 4.2 administrative servers on Release 4.1 sites.
Portability
tmshutdown is supported on any platform on which the BEA Tuxedo server environment is supported.
Diagnostics
If tmshutdown fails to shut down a server or if a fatal error occurs, tmshutdown exits with exit code 1 and the user log should be examined for further details; otherwise it exits with exit code 0.
If tmshutdown is run on an active node that is not the acting master node, a fatal error message is displayed:
tmshutdown cannot run on a non acting-master node in an active application.
If shutting down a process would partition active processes from the DBBL, a fatal error message is displayed:
cannot shutdown, causes partitioning.
If a server has died, the following somewhat ambiguous message is produced.
CMDTUX_CAT:947 Cannot shutdown server GRPID
Examples
To shut down the entire system and remove all BEA Tuxedo IPC resources (force it if confirmation is not received in 30 seconds), run the following command:
tmshutdown -w 30
To shut down only those servers located on the machine for which the value of lmid is CS1, enter the following command:
tmshutdown -l CS1
Because the -l option restricts the action to servers listed in the SERVERS section, the BBL on CS1 is not shut down.
Notices
The tmshutdown command ignores the hangup signal (SIGHUP). If a signal is detected during shutdown, the process continues.
See Also
tmadmin(1), tmboot(1), UBBCONFIG(5)
Administering BEA Tuxedo Applications at Run Time