Tuxedo动态配置
Tuxedo的动态配置可以通过tmadmin和tmconfig两个命令行工具实现不同级别的配置修改。tmadmin的作用主要是监控
Tuxedo的运行,可以修改服务的参数;而tmconfig功能更强大,可以在线修改当前
Tuxedo的系统UBB配置,即通过MIB修改用UBBCONFIG生成的二进制TUXCONFIG在内存的拷贝。
1 用tmadmin修改配置
进入tmadmin后用命令help可以列出所有命令。
2用tmconfig更改TUXCONFIG(UBBCONFIG)
tmconfig工具实际上遍历TUXCONFIG的内容并通过MIB API修改其配置。要正确运行tmconfig,建议设置以下环境变量:
TUXDIR=/usr/
Tuxedo
TUXCONFIG=/usr/app/tuxconfig
EDITOR=vi
主要的界面如下:
tmconfig
Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS
5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL
10) NETGROUPS 11) NETMAPS 12) INTERFACES [1]:
Operation: 1) FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE
6) CLEAR BUFFER 7) QUIT [1]: 4
Enter editor to add/modify fields [n]?
Perform operation [y]?
1. 用tmconfig增加新主机
1.进入tmconfig后,选择2)MACHINES项
2.然后可以先选择3)RETRIEVE看看当前的配置,缺省是第一个MACHINE的配置
3.通过选择2)NEXT可以一直向后搜索MACHINE配置,直到空记录为止。
4.选择4)ADD
Enter editor to add/modify fields [n]? y
5.进入vi编辑状态,可以按照一定格式增加配置。格式为:
MIB域名[tab]值
6.增加MACHINE必须加入以下的域:
oTA_TUXCONFIG
oTA_TUXDIR
oTA_APPDIR
oTA_TLOGDEVICE
oTA_TLOGSIZE
oTA_PMID
oTA_LMID
oTA_TYPE
例:
TA_TUXCONFIG /usr/apps/bank/tuxconfig
TA_TUXDIR /usr/tuxroot
TA_APPDIR /usr/apps/bank
TA_TLOGDEVICE /usr/apps/bank/TLOG
TA_ULOGPFX /usr/apps/bank/ULOG
TA_ENVFILE /usr/apps/bank/ENVFILE
TA_TLOGSIZE 150
TA_PMID SERVER109
TA_LMID SITE1
TA_TYPE Sun
7.存盘退出vi,执行操作即可。
8.激活新增的MACHINE: 重新选择2)MACHINES –> 5)UPDATE
9.进入vi后查找TA_STATE,将其值从NEW改为ACTIVE
10.存盘退出vi并执行操作。
2. 用tmconfig增加新Server进程
1.进入tmconfig后,选择2)SERVER项
2.可以先选择3)RETRIEVE看看当前的配置,缺省是第一个SERVER的配置
3.通过选择2)NEXT可以一直向后搜索SERVER配置,直到空记录为止。
4.选择4)ADD
Enter editor to add/modify fields [n]? y
5.进入vi编辑状态,可以按照一定格式增加配置。格式为:MIB域名[tab]值
6.增加MACHINE必须加入以下的域:
oTA_SERVERNAME
oTA_SRVGRP
oTA_SRVID
例:
TA_SERVERNAME /usr/apps/bank/teller_server
TA_SRVGRP GROUP1
TA_SRVID 15
7.存盘退出vi,执行操作即可。
3、系统核心参数参考
Message Queues Parameters
·MSGMNI: Total Number of Queues (Use this formula: Add MAXACCESSERS + (No. Servers with Reply Queues) - (No. Servers in MSSQ Set) + (No. MSSQ Sets) + 7) to determine the appropriate value
·MSGMAP: Number of entries in control map used to manage message segments (Not defined in NT). Set to 2 * MSGMNI
·MSGMAX: Maximum message size in bytes. Set to the largest message size or 75% of the queue size (whichever is bigger)
·MSGMNB: This is the queue size itself (64K, 128K, etc.)
·MSGSSZ: Size of a segment in bytes (Not defined in NT). The value of MSGSSZ should be such that a multiple of MSGSSZ is equal to the size (including the BEA
Tuxedo System header) of the most commonly sent message. Usually set to 16, 32, or 64.
·MSGTQL: Total Number of In-Flight messages in the system at once
·MSGSEG: Number of message segments in the system (Not defined in NT). You need to find out the queue space of your machine and then the following formula applies: MSGSEG * MSGSSZ = Machine Queue Space Size (note it will swap)
Semaphores Parameters
·SEMMNS: Maximum number of semaphores in the system. The minimum requirement for SEMMNS is MAXACCESSERS - MAXWSCLIENTS + 13 (local clients and all servers)
·SEMMNI: Maximum number of active semaphore sets. For small apps,(100 to 500 servers),10 sets are usually sufficient. For large apps, (>500 servers) 32-64 sets are usually sufficient (do a tmloadcf -c to see which is the best)
·SEMMSL: Maximum number of semaphores per semaphore sets (Not defined in NT). Use the formula: SEMMNS = SEMMNI * SEMMSL
·SEMMAP: Size of the control map used to control semaphore sets (Not defined in NT). Set to SEMMNI
·SEMMNU: Number of undo structures in the system. Set to SEMMNS
·SEMUME: Maximum number of undo entries per undo structure (Not defined in NT). Set to SEMMNS
Shared Memory Parameters
·SHMMAX: Maximum shared memory segment size in bytes. Bulletin Board Size (must be greater than 1,400,000). Largest BB today is approx. 5 MB (this parameter is normally set much higher for the database, so use their rules)
·SHMSEG: Maximum number of segments one process can attach to (for a busy application you need to set this from 32-64)
·SHMMNI: Maximum number of shared memory identifiers in the system. Normally the default of 100 is acceptable (unless more than 100 entities plan on allocating shared memory)
·SHMMIN: Minimum shared memory segment size in bytes. MUST be set to 1.
Other Tunables
·ULIMIT: Maximum file size. ULIMIT needs to be large enough so that you can install BEA
Tuxedo and build servers. 4 megabytes recommended.
·MAXUP: Maximum number of processes per non-super user. The BEA
Tuxedo system processes--servers and administrative processes—run with the UID specified in the application's UBBCONFIG file. MAXUP needs to be large enough to allow all of these processes to run.
·NOFILES: Maximum number of open files per process. A BEA
Tuxedo server requires a minimum of four file descriptors.
·NPROC: Maximum number of processes (systemwide).
·NREGION: Number of region table entries to allocate. Most processes have three regions: text, data, and stack. Additional regions are needed for each shared memory segment and shared library (text and data) attached. However, the region table entry for the text of a ``shared text'' program is shared by all processes executing that program. Each shared memory segment attached to one or more processes uses another region table entry.
·NUMTIM: Maximum number of STREAMS modules that can be pushed by the Transport Layer Interface (TLI). A typical default value is 16; you should have it set to at least 256.
·NUMTRW: The number of TLI read/write structures to allocate in kernel data space. A typical default value is 16; you should have it set to at least 256.
Tuxedo系统平台的调试参数及步骤
1.配置MAXSERVERS、MAXSERVICES两个参数,看是否满足ubbfile文件的配置的服务数和服务参数的个数。Tmadmin——bbs,看里面的参数个数。
2.数据库的可以连接数的大小是否满足ubbfile文件里面同一个数据库连接得servers的数目。参照xa_NULL*.trc文件的错误提示。
3.用命令tmloadcf –c ubbfile看 Tuxedo的进程所需要的共享内存配置。然后修改系统的共享内存的配置。除了AIX平台外,系统的共享内存参数——set shmsys:shminfo_shmmin要设置为1。
4.Tmunloadcf看现在运行的 Tuxedo环境。
5.Tmadmin——crdl-b-z创建日志文件。
6. Tuxedo环境的设置顺序。Tuxconfig——tmadmin——TLOG;
该贴被liulin_2编辑于2012-12-13 15:41:59