• Tools for Modifying Your Application
  

The tmconfig command enables you to browse and modify your configuration file (TUXCONFIG on the MASTER machine) and its associated entities, and to add new components (such as machines and servers) to your application while it is running. When you modify your configuration file (TUXCONFIG on the MASTER machine), tmconfig enables you to perform the following tasks:

• Update the TUXCONFIG file on all machines that are currently booted in the application.
• Propagate the TUXCONFIG file automatically to new machines as they are booted.
• Propagate the TUXCONFIG file automatically to new machines as they are booted.

  Note:

  The tmconfig command runs as a Oracle Tuxedo system client.

Because tmconfig runs as a Oracle Tuxedo client, it is characterized by the following conditions:

• tmconfig fails if it cannot allocate a TPINIT typed buffer.
• The username associated with the client is the login name of the user. (tmconfig fails if the user’s login name cannot be determined.)
• For a secure application (that is, an application for which the SECURITY parameter has been set in the configuration file), tmconfig prompts for the application password. If the application password is not provided, tmconfig fails.
• If tmconfig cannot register as a client, an error message containing tperrno is displayed and tmconfig exits. If this happens, check the user log to determine the cause. The most likely causes for this type of failure are:
  • The TUXCONFIG environment variable was not set correctly.
  • The system was not booted on the machine on which tmconfig is being run.
• tmconfig ignores all unsolicited messages.
• The client name for the tmconfig process that is displayed in the output from printclient (a tmadmin command) is tpsysadm.

• How tmconfig Works
  
• How Results of a tmconfig Task Are Displayed
  

To run tmconfig properly, you must set the required environmental variables. Also, if you have not run tmconfig, we recommend that you walk through a generic tmconfig session, during which you modify entries in your configuration file.

• How to Set Environment Variables for tmconfig
  
• How to Conduct a tmconfig Walkthrough Session
  
• tmconfig Input Buffer Considerations
  

Many aspects of your configuration can be changed dynamically. This section provides instructions for performing the tasks cited in the following list:

1. Enter tmconfig.
2. To specify the MACHINES section of the configuration file, enter 2 after the prompt following the list of sections. (Refer to lines 2-4 in the following sample listing.)
3. Press the Enter key to accept the default operation to be performed. The default is 1)FIRST, an operation that displays the first record in the designated section. In this case, the first record is for the first machine appearing in the MACHINES section. (Refer to line 6.)
4. Press the Enter key to accept the default choices regarding whether to enter the text editor (no) and whether to have the specified operation performed (yes). As requested, the first record in the MACHINES section is now displayed, which is the record for a machine named SITE1 in the following sample listing. (Refer to lines 10-35 in the following listing.)
5. Select the MACHINES section again, by pressing the Enter key after the menu of sections. (Refer to lines 36-38.)
6. Select the ADD operation by entering 4 after the menu of operations. (Refer to lines 39-40.)
7. Enter the text editor by entering y at the prompt. (Refer to line 41.)
8. Change pathnames as appropriate and specify new values for four key fields:
   • TA_TLOGSIZE (refer to lines 50-51)
   • TA_PMID (refer to lines 52-53)
   • TA_LMID (refer to lines 54-55)
   • TA_TYPE (refer to lines 56-57)
9. Write (that is, save) your input and quit the editor. (Refer to lines 58-60.)
10. Direct tmconfig to perform the operation (add the machine) by entering y at the prompt. (Refer to line 61.)

Listing 3‑2 illustrates a tmconfig session in which a machine is being added.

Listing 3‑2 Adding a Machine

1 $ tmconfig
2 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS
3 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
4 10) NETGROUPS 11) NETMAPS 12) INTERFACES [1]: 2
5 Operation: 1)FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE
6 6) CLEAR BUFFER 7) QUIT [1]:
7 Enter editor to add/modify fields [n]?
8 Perform operation[y]?
9 Return value TAOK
10 Buffer contents:
11 TA_OPERATION 4
12 TA_SECTION 1
13 TA_OCCURS 1
14 TA_PERM 432
15 TA_MAXACCESSERS 40
16 TA_MAXGTT 20
17 TA_MAXCONV 10
18 TA_MAXWSCLIENTS 0
19 TA_TLOGSIZE 100
20 TA_UID 4196
21 TA_GID 601
22 TA_TLOGOFFSET 0
23 TA_TUXOFFSET 0
24 TA_STATUS LIBTUX_CAT:1137: Operation completed successfully
25 TA_PMID mchn1
26 TA_LMID SITE1
27 TA_TUXCONFIG /home/apps/bank/TUXCONFIG
28 TA_TUXDIR /home/tuxroot
29 TA_STATE ACTIVE
30 TA_APPDIR /home/apps/bank
31 TA_TYPE 3B2
32 TA_TLOGDEVICE /home/apps/bank/TLOG
33 TA_TLOGNAME TLOG
34 TA_ULOGPFX /home/apps/bank/ULOG
35 TA_ENVFILE /home/apps/bank/ENVFILE
36 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS
37 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL
38 10) NETGROUPS 11) NETMAPS 12) INTERFACES [2]: 
39 Operation: 1) FIRST 2) NEXT 3)RETRIEVE 4) ADD 5) UPDATE
40 6) CLEAR BUFFER 7) QUIT [1]: 4
41 Enter editor to add/modify fields [n]? y
42 491
43 g/home/s//usr/p
44 TA_TUXCONFIG /usr/apps/bank/TUXCONFIG
45 TA_TUXDIR /usr/tuxroot
46 TA_APPDIR /usr/apps/bank
47 TA_TLOGDEVICE /usr/apps/bank/TLOG
48 TA_ULOGPFX /usr/apps/bank/ULOG
49 TA_ENVFILE /usr/apps/bank/ENVFILE
50 /100/s//150/p
51 TA_TLOGSIZE 150
52 /mchn1/s//mchn2/p
53 TA_PMID mchn2
54 /SITE1/s//SITE3/p
55 TA_LMID SITE3
56 /3B2/s//SPARC/p
57 TA_TYPE SPARC
58 w
59 412
60 q
61 Perform operation [y]?
62 Return value TAUPDATED
63 Buffer contents:
64 TA_OPERATION 2
65 TA_SECTION 1
66 TA_OCCURS 1
67 TA_PERM 432
68 TA_MAXACCESSERS 40
69 TA_MAXGTT 20
70 TA_MAXCONV 10
71 TA_MAXWSCLIENTS 0
72 TA_TLOGSIZE 150
73 TA_UID 4196
74 TA_GID 601
75 TA_TLOGOFFSET 0
76 TA_TUXOFFSET 0
77 TA_STATUS LIBTUX_CAT:1136: Update completed successfully
78 TA_PMID mchn2
79 TA_LMID SITE3
80 TA_TUXCONFIG /usr/apps/bank/TUXCONFIG 
81 TA_TUXDIR /usr/tuxroot 
82 TA_STATE NEW
83 TA_APPDIR /usr/apps/bank
84 TA_TYPE SPARC
85 TA_TLOGDEVICE /usr/apps/bank/TLOG
86 TA_TLOGNAME TLOG 
87 TA_ULOGPFX /usr/apps/bank/ULOG
88 TA_ENVFILE /usr/apps/bank/ENVFILE

1. Enter tmconfig.
2. To specify the SERVERS section of the configuration file, enter 4 after the menu of sections. (Refer to line 3 in the following sample listing.)
3. Request the CLEAR BUFFER operation by entering 6 after the menu of operations. (Refer to line 5 in the following sample listing.)
4. Press the Enter key to accept the default section: SERVERS. (Refer to lines 7-9 in the following sample listing.)
5. Request the ADD operation by entering 4 after the menu of operations. (Refer to lines 10-11 in the listing.)
6. Enter the text editor by entering y at the prompt. (Refer to line 12.)
7. Specify new values for three key fields:
   • TA_SERVERNAME (refer to line 15)
   • TA_SRVGRP (refer to line 16)
   • TA_SRVID (refer to line 17)
8. Write (that is, save) your input and quit the editor. (Refer to lines 19-21.)
9. Direct tmconfig to perform the operation (add the server) by entering y at the prompt. (Refer to line 22.)

Listing 3‑3 illustrates a tmconfig session in which a server is being added.

Listing 3‑3 Adding a Server

1 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS
2 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
3 10)NETGROUPS 11) NETMAPS 12) INTERFACES [1]: 4 
4 Operation: 1)FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE 
5 6) CLEAR BUFFER 7) QUIT [4]: 
6 Buffer cleared 
7 Section:1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS 
8 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
9 10) NETGROUPS 11) NETMAPS 12) INTERFACES [4]: 
10 Operation: 1) FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE 
11 6)CLEAR BUFFER 7) QUIT [6]: 4 
12 Enter editor to add/modify fields [n]? y 
13 1 
14 c 
15 TA_SERVERNAME XFER 
16 TA_SRVGRP BANKB1 
17 TA_SRVID 5
18 . 
19 w 
20 28 
21 q 
22 Perform operation [y]? 
23 Return value TAOK 
24 Buffer contents: 
25 TA_OPERATION 3 
26 TA_SECTION 3 
27 TA_OCCURS 1 
28 TA_SRVID 5 
29 TA_SEQUENCE 0 
30 TA_MIN 1 
31 TA_MAX 1
32 TA_RQPERM 432 
33 TA_RPPERM 432 
34 TA_MAXGEN 5
35 TA_GRACE 86400 
36 TA_STATUS LIBTUX_CAT:1137: Operation completed successfully 
37 TA_SYSTEM_ACCESS FASTPATH 
38 TA_ENVFILE 
39 TA_SRVGRP BANKB1 
40 TA_SERVERNAME XFER 
41 TA_CLOPT -A 
42 TA_CONV N 
43 TA_RQADDR 
44 TA_REPLYQ Y 
45 TA_RCMD 
46 TA_RESTART Y

1. Enter tmconfig.
2. To specify the MACHINES section of the configuration file, enter 2 after the menu of sections. (Refer to lines 1-3 in the following sample listing.)
3. In order to select the appropriate record in the MACHINES section, you need to toggle through the list of machine records. To view the first machine record, select the FIRST operation by pressing the Enter key after the menu of operations. (Refer to lines 4-5 in the following sample listing.) If you do not want the first machine record, select the NEXT operation to view the next machine record by entering 2 after the menu of operations.
4. Press the Enter key to accept the default choices regarding whether to enter the text editor (no) and whether to have the specified operation performed (yes). The requested record in the MACHINES section is now displayed, which is the record for a machine named SITE3 in the following sample listing. (Refer to lines 9-34 in the following listing.)
5. Select the MACHINES section again, by pressing the Enter key after the menu of sections. (Refer to lines 35-37.)
6. Select the UPDATE operation by entering 5 after the menu of operations. (Refer to lines 38-39.)
7. Enter the text editor by entering y at the prompt. (Refer to line 40.)
8. Change the value of the TA_STATE field from NEW to ACTIVE. (Refer to lines 42-45.)
9. Write (that is, save) your input and quit the editor. (Refer to lines 46-48.)
10. Direct tmconfig to perform the operation (activate the newly configured machine) by entering y at the prompt. (Refer to line 49.)
11. tmconfig displays the revised record for the specified machine so that you can review your change and, if necessary, edit it.
12. If the revised entry is acceptable, select 7 after the menu of operations to end the tmconfig session.

Listing 3‑4 illustrates a tmconfig session in which a server is being activated.

Listing 3‑4 Activating a New Server

1 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS
2 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
3 10) NETGROUPS 11) NETMAPS 12) INTERFACES [1]: 2 
4 Operation: 1) FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE 
5 6) CLEAR BUFFER 7)QUIT [1]:
6 Enter editor to add/modify fields [n]?
7Perform operation [y]? 
8 Return value TAOK 
9 Buffer contents: 
10 TA_OPERATION 4 
11 TA_SECTION 1 
12 TA_OCCURS 1 
13 TA_PERM 432
14 TA_MAXACCESSERS 40 
15 TA_MAXGTT 20 
16 TA_MAXCONV 10 
17 TA_MAXWSCLIENTS 0
18 TA_TLOGSIZE 150 
19 TA_UID 4196 
20 TA_GID 601
21 TA_TLOGOFFSET 0
22 TA_TUXOFFSET 0 
23 TA_STATUS LIBTUX_CAT:1175: Operation completed successfully 
24 TA_PMID mchn2 
25 TA_LMID SITE3 
26 TA_TUXCONFIG /usr/apps/bank/TUXCONFIG /
27 TA_TUXDIR /usr/tuxroot 
28 TA_STATE NEW 
29 TA_APPDIR /usr/apps/bank 
30 TA_TYPE SPARC 
31 TA_TLOGDEVICE /usr/apps/bank/TLOG 
32 TA_TLOGNAME TLOG 
33 TA_ULOGPFX /usr/apps/bank/ULOG 
34 TA_ENVFILE /usr/apps/bank/ENVFILE 
35 Section: 1) RESOURCES, 2) MACHINES,3) GROUPS 4) SERVERS 
36 5)SERVICES 6) NETWORK 7) ROUTING q)QUIT 9) WSL 
37 10) NETGROUPS 11) NETMAPS 12) INTERFACES [2]: 
38 Operation: 1) FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE
39 6) CLEAR BUFFER 7) QUIT [1]: 5 /
40 Enter editor to add/modify fields [n]? y 
41 491 
42/TA_STATE 
43 TA_STATE NEW 
44 s/NEW/ACTIVE 
45 TA_STATE ACTIVE 
46 w
47 412 
48 q 
49 Perform operation [y]? 
50 Return value TAUPDATED 
51 Buffer contents: 
52 . 
53 . 
54 . 

1. Enter tmconfig.
2. To specify the GROUPS section of the configuration file, enter 3 after the prompt following the list of sections. (Refer to lines 1-3 in the following sample listing.)
3. Request the CLEAR BUFFER operation by entering 6 after the menu of operations. (Refer to line 5 in the following sample listing.)
4. Accept the default section, GROUPS, by pressing the Enter key. (Refer to lines 7-9 in the following sample listing.)
5. Request the ADD operation by entering 4 after the menu of operations. (Refer to lines 10-11 in the listing.)
6. Enter the text editor by entering y at the prompt. (Refer to line 12.)
7. Specify new values for three key fields:
   • TA_LMID (refer to line 15)
   • TA_SRVGRP
   • TA_GRPNO (refer to line 17)

The following listing illustrates a tmconfig session in which a group is being added.

Listing 3‑5 Adding a Group

1 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS
2 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
3 10)NETGROUPS 11) NETMAPS 12) INTERFACES [1]: 3 
4 Operation: 1)FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE 
5 6) CLEAR BUFFER 7) QUIT [4]: 6 
6 Buffer cleared 
7 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS 
8 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL
9 10) NETGROUPS 11) NETMAPS 12) INTERFACES [3]:
10 Operation: 1) FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE 
11 6) CLEAR BUFFER 7) QUIT [6]: 4 
12 Enter editor to add/modify fields [n]? y 
13 1 
14 c 
15 TA_LMID SITE3 
16 TA_SRVGRP GROUP3 
17 TA_GRPNO 3 
18 .
19 w 
20 42 
21 q 
22 Perform operation [y]? 
23 Return value TAUPDATED 
24 Buffer contents: 
25 TA_OPERATION 2 
26 TA_SECTION 2 
27 TA_OCCURS 1 
28 TA_GRPNO 3 
29 TA_TMSCOUNT 0 
30 TA_STATUS LIBTUX_CAT:1136: Update completed successfully 
31 TA_LMID SITE3 
32 TA_SRVGRP GROUP3 
33 TA_TMSNAME 
34 TA_OPENINFO 
35 TA_CLOSEINFO

To change the Data-Dependent Routing for an application, complete the following steps:

1. Enter tmconfig
2. To specify the ROUTING section of the configuration file, enter 7 after the prompt following the list of sections.
3. Toggle through the list of entries for the ROUTING section by selecting the FIRST and NEXT operations, which display the first and subsequent entries, respectively. Select the entry for which you want to change the DDR
4. Select 5)UPDATE from the menu of operations.
5. Enter the text editor by entering y at the prompt.

   Do you want to edit(n)? y

6. Change the values of relevant fields to the values shown in the “Sample Value” column of the following table:

To change the factory-based routing for a CORBA interface, complete the following steps:

1. Start a tmconfig session.
2. Select the ROUTING section of the configuration file (choice #7 on the menu of configuration file sections).
3. Using the FIRST and NEXT operations, select the entry for which you want to change the FBR.
4. Select the UPDATEoperation.
5. Enter y (for yes) when prompted to say whether you want to start editing.

   Do you want to edit(n)? y

6. Change the relevant fields to values such as those shown in the middle column in Table 3‑3:

The value of the TA_RANGES field is the routing criterion. For example, assume that our modest student enrollment before the update allowed for a routing criterion of student IDs between 100001–100005 to ORA_GRP1, and 100006–100010 to ORA_GRP2. In the change shown in the preceding table, if the value of student_id is between 100001–100050 (inclusive), requests are sent to the servers in ORA_GRP1. Other requests are sent to ORA_GRP2.

For example:

1. Start a tmconfig session.
2. Select the INTERFACES section of the configuration file (choice #12 on the menu of configuration file sections).
3. Using the FIRST and NEXT operations, select the interface entry for which you want to change the FBR. For example, if you defined a new factory-based routing criterion named CAMPUS in the ROUTING section, you could reassign a Registrar interface to this criterion.
4. Select the UPDATE operation.

       Do you want to edit(n)? y  

Some run-time parameters are relevant to all the components (machines, servers, and so on) of your configuration. These parameters are listed in the RESOURCES section of the configuration file.

An easy way to familiarize yourself with the parameters in the RESOURCES section is to display the first entry in that section. To do so, complete the following procedure.

1. Enter tmconfig
2. Select the RESOURCES section, which is the default, by pressing the Enter key after the list of sections. (Refer to lines 1-3 in the following sample listing.)
3. Request the FIRST operation, which is the default, by pressing the Enter key after the menu of operations. (Refer to lines 4-5.)
4. When asked whether you want to edit, accept the default () by pressing the Enter key.

   Do you want to edit(n)?

5. When asked whether you want the specified operation (FIRST) to be performed, accept the default (y) by pressing the Enter key.

   Perform operation [y]?

Listing 3‑6 shows a tmconfig session in which the first entry in the RESOURCES section is displayed.

Listing 3‑6 Displaying the First Entry in the RESOURCES Section

1 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS 
2 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
3 10) NETGROUPS 11) NETMAPS 12) INTERFACES [1]: 
4 Operation: 1)FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE 
5 6) CLEAR BUFFER 7) QUIT [1]: 
6 Enter editor to add/modify fields [n]? 
7 Perform operation [y]? 
8 Return value TAOK 
9 Buffer contents:
10 TA_OPERATION 1 
11 TA_SECTION 0 
12 TA_STATUS Operation completed successfully 
13 TA_OCCURS 1 
14 TA_PERM 432 
15 TA_BBLQUERY 30 
16 TA_BLOCKTIME 6
17 TA_DBBLWAIT 2 
18 TA_GID 10 
19 TA_IPCKEY 80997 
20 TA_LICMAXUSERS 1000000 
21 TA_MAXACCESSERS 100 
22 TA_MAXBUFSTYPE 32 
23 TA_MAXBUFTYPE 16 
24 TA_MAXCONV 10 
25 TA_MAXDRT 0 
26 TA_MAXGROUPS 100 
27 TA_MAXGTT 25 
28 TA_MAXMACHINES 256 
29 TA_MAXQUEUES 36 
30 TA_MAXRFT 0 
31 TA_MAXRTDATA 8 
32 TA_MAXSERVERS 36 
33 TA_MAXSERVICES 100 
34 TA_MIBMASK 0 
35 TA_SANITYSCAN 12 
36 TA_SCANUNIT 10 
37 TA_UID 5469 
38 TA_MAXACLGROUPS 16384 
39 TA_MAXNETGROUPS 8 
40 TA_MAXINTERFACES 150 
41 TA_MAXOBJECTS 1000 
42 TA_SIGNATURE_AHEAD 3600 
43 TA_SIGNATURE_BEHIND 604800 
44 TA_MAXTRANTIME 0 
45 TA_STATE ACTIVE 
46 TA_AUTHSVC 
47 TA_CMTRET COMPLETE
48 TA_DOMAINID 
49 TA_LDBAL Y 
50 TA_LICEXPIRE 2003-09-15 
51 TA_LICSERIAL 1234567890 
52 TA_MASTER SITE1 
53 TA_MODEL SHM 
54 TA_NOTIFY DIPIN 
55 TA_OPTIONS 
56 TA_SECURITY NONE 
57 TA_SYSTEM_ACCESS FASTPATH 
58 TA_USIGNAL SIGUSR2 
59 TA_PREFERENCES 
60 TA_COMPONENTS TRANSACTIONS,QUEUE,TDOMAINS,
61 EVENTS,WEBGUI,WSCOMPRESSION,TDOMCOMPRESSION 
62 TA_SIGNATURE_REQUIRED 
63 TA_ENCRYPTION_REQUIRED 
64 TA_SEC_PRINCIPAL_NAME 
65 TA_SEC_PRINCIPAL_LOCATION 
66 TA_SEC_PRINCIPAL_PASSVAR 

1. Enter tmconfig.
2. Select the RESOURCES section, which is the default, by pressing the Enter key following the list of sections. (Refer to lines 2-4 in the following sample listing.)
3. Request the CLEAR BUFFER operation by entering 6 after the menu of operations. (Refer to line 6.)
4. Select the RESOURCES section again, by pressing the Enter key after the menu of sections. (Refer to lines 8-10.)
5. Select the UPDATE operation by entering 5 after the menu of operations. (Refer to lines 11-12.)
6. Enter the text editor by entering y at the prompt. (Refer to line 13.)
7. Enter (in the buffer):

   TA_PASSWORD new_password

   TA_PASSWORD new_password
8. Write (that is, save) your input and quit the editor. (Refer to lines 18-20.)

Listing 3‑7 shows a tmconfig session in which an application password is changed to neptune.

Listing 3‑7 Changing an Application Password

1 $ tmconfig 
2 Section: 1) RESOURCES, 2) MACHINES, 3)GROUPS 4) SERVERS 
3 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
4 10) NETGROUPS 11) NETMAPS 12) INTERFACES [1]: 
5 Operation: 1) FIRST 2) NEXT 3) RETRIEVE 4) ADD 5) UPDATE 
6 6)CLEAR BUFFER 7) QUIT [4]: 6 
7 Buffer cleared 
8 Section: 1) RESOURCES, 2) MACHINES, 3) GROUPS 4) SERVERS 
9 5)SERVICES 6) NETWORK 7) ROUTING q) QUIT 9) WSL 
10 10) NETGROUPS 11) NETMAPS 12) INTERFACES [1]: 
11 Operation: 1) FIRST 2) NEXT 3)RETRIEVE 4) ADD 5) UPDATE 
12 6) CLEAR BUFFER 7) QUIT [6]: 5 
13 Enter editor to add/modify fields [n]? y 
14 1 
15 c 
16 TA_PASSWORD neptune 
17 . 
18 w 
19 49 
20 q 
21 Perform operation [y]? 
22 Return value TAUPDATED 
23 Buffer contents: 
24 TA_OPERATION 1
25 TA_SECTION 0 
26 TA_STATUS Operation completed successfully 
27 TA_OCCURS 1 
28 TA_PERM 432 
29 TA_BBLQUERY 30 
30 TA_BLOCKTIME 6 
31 TA_DBBLWAIT 2 
32 TA_GID 10 
33 TA_IPCKEY 80997 
34 TA_LICMAXUSERS 1000000 
35 TA_MAXACCESSERS 100 
36 TA_MAXBUFSTYPE 32 
37 TA_MAXBUFTYPE 16 
38 TA_MAXCONV 10 
39 TA_MAXDRT 0 
40 TA_MAXGROUPS 100 
41 TA_MAXGTT 25 
42 TA_MAXMACHINES 256 
43 TA_MAXQUEUES 36 
44 TA_MAXRFT 0 
45 TA_MAXRTDATA 8 
46 TA_MAXSERVERS 36 
47 TA_MAXSERVICES 100 
48 TA_MIBMASK 0 
49 TA_SANITYSCAN 12 
50 TA_SCANUNIT 10 
51 TA_UID 5469 
52 TA_MAXACLGROUPS 16384 
53 TA_MAXNETGROUPS 8 
54 TA_MAXINTERFACES 150 
55 TA_MAXOBJECTS 1000 
56 TA_PASSWORD neptune 
57 TA_STATE ACTIVE 
58 TA_AUTHSVC 
59 TA_CMTRET COMPLETE 
60 TA_DOMAINID 
61 TA_LDBAL Y 
62 TA_LICEXPIRE 1998-09-15 
63 TA_LICSERIAL 1234567890 
64 TA_MASTER SITE1 
65 TA_MODEL SHM />66 TA_NOTIFY DIPIN 
67 TA_OPTIONS 
68 TA_SECURITY NONE />69 TA_SYSTEM_ACCESS FASTPATH 
70 TA_USIGNAL SIGUSR2 
71 TA_PREFERENCES 
72 TA_COMPONENTS TRANSACTIONS,QUEUE,TDOMAINS,EVENTS,WEBGUI, 
73 WSCOMPRESSION,TDOMCOMPRESSION

Keep in mind the following restrictions when modifying your application dynamically using tmconfig. Be careful about setting parameters that cannot be changed easily.

• Associated with each section is a set of key fields that are used to identify the record upon which operations are performed. (For details, see tmconfig, wtmconfig(1) in the Oracle Tuxedo Command Reference.) Key field values cannot be changed while an application is running. Normally, it is sufficient to add a new entry, with a new key field, and use it instead of the old entry. When this is done, only the new entry is used; the old entry in the configuration is not booted by the administrator.
• Generally speaking, you cannot update a parameter while the configuration component with which it is associated is booted. For example, you cannot change an entry in the MACHINES section while the machine associated with that entry is booted. Specifically:
  • If any server in a group is booted, you cannot change the entry for that group.
  • If a server is booted, you cannot change its name, type (conversational or not), or parameters related to its message queue. (You can change other server parameters at any time but your changes do not take effect until the next time the server is booted.).
  • You can change a SERVICES entry at any time, but your changes do not take effect until the next time the service is advertised.
  • Updates to the RESOURCES section are restricted by the following conditions: the UID, GID, PERM, MAXACCESSERS, MAXGTT, and MAXCONV parameters cannot be updated in the RESOURCES section but can be updated on a per-machine basis; and the IPCKEY, MASTER, MODEL, OPTIONS, USIGNAL, MAXSERVERS, MAXSERVICES, MAXBUFTYPE, and MAXBUFSTYPE parameters cannot be changed dynamically.
  • Carefully track the section of the configuration file in which you are working; tmconfig does not warn against performing an operation in the incorrect section. For example, if you try to update the ENVFILE parameter (in the MACHINES section) while you are working in the RESOURCES section, the operation appears to succeed (that is, tmconfig returns TAOK), but the change does not appear in your unloaded UBBCONFIG file. You can be sure an update is done only when the TAUPDATED status message is displayed.

In a multiple-machine configuration, always perform the following tasks:

• Specify a backup for the MASTER machine, along with the MIGRATE option (even if a need for application server migration is not anticipated).
• For MAXSERVERS, MAXSERVICES, and other parameters that define maximum limits, assign settings that are high enough to allow for sufficient growth. If your application is initially deployed on only one machine, but is expected to grow to a multiple-machine configuration, use the MP model, specifying the LAN option and a network entry for the initial machine.
• Set the parameters in the MACHINES section carefully because updating them requires shutting down the machine (and switching the MASTER to the backup in the case of the MASTER machine)

• Tasks That Cannot Be Performed on a Running System
  

When you use the tmconfig command to update the TUXCONFIG file and any bulletin board entries associated with it, the changes you make are permanent; they persist after the system is shut down and rebooted.

In some situations, however you may want to make temporary changes to a running application. For example, you may want to:

• Suspend Tuxedo ATMI services or servers
• Resume Tuxedo ATMI services or servers
• Advertise services or servers
• Unadvertise services or servers
• Change ATMI service parameters
• Change CORBA interface parameters
• Change the timeout value
• Suspend CORBA interfaces

You can perform these tasks with the tmadmin command, as specified in the procedures provided in this section.

• How to Set Environment Variables for tmadmin
  

To suspend a Tuxedo ATMI server or a service, enter the tmadmin and susp (short for suspend) commands, as follows:

The suspend command marks one of the following as inactive:

• One service
• All services of a particular queue
• All services of a particular group ID or server ID combination

After you suspend a service or a server, any requests for it that remain on the queue are handled, but no new service requests are routed to the suspended server. If a group ID or server ID combination is specified and it is part of an MSSQ set, all servers in that MSSQ set become inactive for the services specified.

To have a Tuxedo ATMI server or a service resume, enter thetmadmin and resume (or res) commands, as follows:

The resume command undoes the effect of the suspend command; it marks as active for the queue one of the following:

• One service
• All services of a particular queue
• All services of a particular group ID/server ID combination

If, in this state, the group ID or the server ID is part of an MSSQ set, all servers in that MSSQ set become active for the services specified.

To advertise a service or server, enter the following commands:

$ tmadmin > adv [{[-q queue_name] | [-g grpid] [-i srvid]}] service

Although a service must be suspended before it may be unadvertised, you do not need to unsuspend a service before readvertising it. If you simply advertise a service that was unadvertised earlier, and is currently suspended, the service is unsuspended.

To unadvertise a service or server, you must suspend it by entering the following commands:

Unadvertising a service has more drastic results than suspending it. When you unadvertise a service, the service table entry for it is deallocated and the cleared space in the service table becomes available to other services.

The tmadmin command allows you to change, dynamically, the values of service parameters for a specific group ID/server ID combination or for a specific queue.

The following table lists the tmadmin commands available for changing service parameters defined in this way.

The -s option must be specified, either on the tmadmin default command line or on the tmadmin chl, chp, or chtt command line. Because it is possible to set the -s option on the default command line, the -s option is considered optional on the chl, chp, and chtt command lines.

The tmadmin command allows you to change, dynamically, the values of interface parameters for a specific group ID/server ID combination or for a specific queue.

Table3‑5 lists the tmadmin commands available for changing interface parameters defined in this way.

The -I option must be specified, either on the tmadmin default command line or on the tmadmin chl, chp, or chtt command line. Because it is possible to set the -I option on the default command line, the -I option is considered optional on the chl, chp, and chtt command lines.

To change the transaction timeout (TRANTIME) for an interface or service with the AUTOTRAN flag set, run the changetrantime (chtt) command, as follows:

[-s service] | -g groupname -i srvid -s service |

-I interface [-g groupname]} newtlim

You cannot change transaction timeouts begun by application clients using tpbegin() or tx_set_transaction_timeout().

For example:

If a suspended interface is resumed, clients will be able to invoke methods on that interface.