Administration Console Online Help
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
The BEA Tuxedo Administration Console simplifies the task of managing your BEA Tuxedo application resources. The BEA Tuxedo Administration Console enables you to quickly and easily perform the administrative tasks associated with managing mission-critical applications. With the BEA Tuxedo Administration Console, you can create domains and administrative class objects (such as machines and services), as well as manage Tuxedo CORBA interfaces, factories, and interface queues. The BEA Tuxedo Administration Console provides a browser-based solution for remote system administration.
This topic describes the administration tasks you can perform using the BEA Tuxedo Administration Console.
This topic includes the following sections:
The BEA Tuxedo Administration Console allows you to customize your administrative environment and set default parameters. Setting up and customizing the BEA Tuxedo Administration Console includes the following tasks:
To set general default parameters for your administrative session:
Table 3-1 explains the options available on the Settings window.
Indicates the criterion (name or state) by which administrative objects will be sorted. Here are two examples: |
|
Indicates the default work mode (view-only or edit) for the current session as follows:
Note: You can override this default setting for individual tree objects. For more information, see the section Switching Edit and View Modes. |
You can set the BEA Tuxedo Administration Console to the following default work modes:
By default, your BEA Tuxedo Administration Console is set to Edit mode so that you can create or modify parameters by editing the appropriate fields in the configuration tab pages. (To change the default mode for the session, select Settings—>Defaults from the menu bar and follow the steps in Setting General Default Parameters.)
You can momentarily override the default setting for individual tree items. Most likely you will use this feature to override a default View mode to edit an attribute on an object. If you return to the same object later in the session, it reverts to the default mode (in this case, View only) unless you override the default again.
To change the mode for a specific object in the Tree View:
You can customize the configuration Tree View so that only the administrative classes (tree objects) you want to see are displayed. To control what class folders are displayed in the tree, follow these steps:
As shown in Figure 3-2, the Select Folders window is displayed.
Figure 3-2 Select Folders Dialog Box
Note: The items listed in the Folders window will vary, depending on which type of tree object you select. Figure 3-2 shows the Select Folders window displayed for the domain class object.
To create new domains and individual administrative class objects, you use the Create New Object window to define identifying attributes for the object such as name, location, and so on. The BEA Tuxedo Administration Console provides a class-specific Create New Object window for each class to which you can add an object. The fields on the Create New Object window vary, depending on the administrative class.
You cannot create new objects for all of the classes displayed in the Tree View. (For example, you cannot create new Client class objects.) For a complete list of the administrative resources you can create, see Table 3-1.
This section provides general instructions on how to create a new object via the BEA Tuxedo Administration Console, using domains as an example. For detailed information on how to fill in attribute fields for a specific type of object, refer to the help topics listed in Table 3-1.
To create any new administrative object, use the following general procedure:
Figure 3-3 Quick Menu on a Device
Figure 3-4 Quick Menu on a CORBA Interfaces Class Object
The Create New Object window is displayed as shown in Figure 3-5, prompting you for the identifying attributes needed to establish a new device object, or as shown in Figure 3-6, prompting you to establish a CORBA interface class object.
Figure 3-5 Create New Object Window for a Device
Figure 3-6 Create New Object Window for the CORBA Interfaces Class Object
The new object appears in the tree contained under the folder you selected originally. (Or, at the same level as whatever non-folder object you selected originally.) The new object automatically includes empty folders of the appropriate subclasses in which you can create new member objects if needed.
Table 3-1 lists topics that give detailed information on how to fill in the fields on the Create New Object window for a specific type of object.
To configure a domain and its administrative objects shown in the Tree View, you use the Configuration Tool tab pages displayed on the right side of the main window. The tab pages (also called tab folders) show the current attribute settings for the administrative object selected in the tree.
Depending on the type of administrative object you select, anywhere from one to eight tab pages is displayed—each page containing a set of attributes related to a particular administrative area for that object such as Networking, Security, Transactions, and so on. Many of the attribute fields on the tab pages are editable, so you can specify or change attributes as needed.
To configure an administrative object:
The Configuration Tool tab pages for that administrative object are displayed on the right side of the main window, as shown in Figure 3-7.
Figure 3-7 Selecting an Administrative Object
Note: For more information about setting your default configuration mode or switching from one mode to another, see the section Switching Edit and View Modes.
Note: Defaults are only available for some fields. The defaults are listed in the help topic for the specific field. If you use the default, you need to click the Refresh button to display the default value.
Not all the fields on the tabbed folders can be edited; some information that cannot be changed, such as statistics for the current operation of the domain.
Table 3-2 lists topics that give detailed information on how to fill in attribute fields on the Configuration Tool tab pages for a specific type of object.
Configuring Application Queue Transactions (T_APPQTRANS Class) |
|
There are a number of operations that you can perform only when you are connected to a domain. These include:
You have two options for connecting to an existing domain.
To connect to a domain listed on the menu bar Domain list, select Domain—>Domain Name.
To open a domain not on the list:
The Connect window is displayed as shown in Figure 3-8.
The BEA Tuxedo Administration Console automatically disconnects you from a domain whenever necessary (for example, when you select another domain name from the pull-down menu of Domains).
To disconnect from the domain to which you are currently connected, exit the GUI by selecting Domain—>Exit Application from the menu bar.
As the system administrator, you are the only user who is authorized to activate the BEA Tuxedo domain and domain resources. You must perform the initial activation process on the Master machine on which the application configuration file is located.
You can activate all or part of a BEA Tuxedo domain. Specifically, you can activate:
The BEA Tuxedo Administration Console displays the Activate Objects window. Click the Domain tab to display the Domain information as shown in Figure 3-9.
Figure 3-9 Activate Domain Tab Page
The Domain tab page contains a single option that indicates whether you want to activate only administrative servers for the domain, or the entire domain.
The BEA Tuxedo Administration Console displays the Progress of Activate window. For more information about this window, see How to Monitor the Progress of Activate.
To activate domain and class objects:
The BEA Tuxedo Administration Console displays the Activate Objects window containing a set of class-specific tab pages (see Figure 3-10). Click a tab to display the page for the type of object you want to activate.
The Activate Objects window contains six tab pages as shown in the following table.
The entire domain. (Refer to How to Activate a Domain.) |
|
As shown in Figure 3-10, all Activate class objects tab pages include the following list boxes:
All objects shown indicate their current state next to the object name.
Figure 3-10 Activate Objects Window
Move the object(s) you want to activate into the ACTIVATE THESE list and all other objects into the DO NOT ACTIVATE THESE list. (To move an object from one list (or column) to another, highlight the object name and click one of the arrow buttons between the two columns as shown in Table 3-4.)
The Machines tab page also contains an option to Only Activate Administrative Servers. For more information about this option, see Activating Only Administrative Servers.
Note: When you click Activate, you are activating only the selected objects on the current tab, not on all tabs. To activate several types of objects (such as machines, groups, servers, and so on) you need to step through this procedure for each type of object—opening the Activate window, clicking on a particular tab, making your selections, and clicking Activate.
The BEA Tuxedo Administration Console displays the Progress of Activate window. For more information about this window, see How to Monitor the Progress of Activate.
The Bulletin Board Liaison Processes (BBLs) and the Distinguished Bulletin Board Liaison Process (DBBL) are BEA Tuxedo administrative servers. Generally, these servers are activated first. If a BBL fails to activate, the other servers on that machine will not be activated. If the DBBL fails to activate, the entire application's activation process fails.
You can choose whether to limit your activation to BBLs and the DBBL for the entire domain or for selected machines as follows:
As objects are activated, the Progress of Activate window is displayed (as shown in Figure 3-11). The Progress of Activate window tracks the status of the activation process as it occurs. You can:
If you do not want to view the Progress of Activate window during the activation process, click Dismiss to close the window. The activation process continues in the background.
Figure 3-11 Progress of Activate Window
Note: Alternatively, if you decide you do not want to activate the chosen objects, you can click Terminate to end the activation process at any time. However, because terminating the operation in mid-process could yield unexpected results, it is recommended that you allow the process to conclude and then deactivate the undesired objects.
The BEA Tuxedo Administration Console enables you to deactivate all or parts of a BEA Tuxedo domain. Specifically, you can deactivate:
Note: You can also deactivate bridges. For more information about deactivating bridges, see Creating Bridges Between Machines.
The BEA Tuxedo Administration Console displays the Deactivate Objects window. Click the Domain tab to display the Domain information as shown in Figure 3-12.
Figure 3-12 Deactivate Domain Tab Page
To select either of these options, click the check boxes. (A check mark indicates the associated action will be performed as a part of the deactivation).
The BEA Tuxedo Administration Console displays the Progress of Deactivate window. For more information about this window, see How to Monitor the Progress of Deactivate.
The BEA Tuxedo Administration Console displays the Deactivate Objects window containing a set of class-specific tab pages (see Figure 3-13). Click a tab to display the page for the type of object you want to deactivate.
The Deactivate Objects window contains six tab pages as shown in the following table.
The entire domain. (Refer to How to Deactivate a Domain.) |
|
As shown in Figure 3-13, all Deactivate class objects tab pages include the following list boxes:
All objects shown indicate their current state next to the object name.
Figure 3-13 Deactivate Objects Window
Move the object(s) you want to deactivate into the DEACTIVATE THESE list and all other objects into the DO NOT DEACTIVATE THESE list. (To move an object from one list (or column) to another, highlight the object name and click one of the arrow buttons between the two columns as shown in Table 3-4.)
Note: When you click Deactivate, you are deactivating only the selected objects on the current tab, not on all tabs. To deactivate several types of objects (such as machines, groups, servers, and so on) you need to step through this procedure for each type of object—opening the Deactivate window, clicking on a particular tab, making your selections, and clicking Deactivate.
The BEA Tuxedo Administration Console displays the Progress of Deactivate window. For more information about this window, see How to Monitor the Progress of Deactivate.
Application servers are user-defined or BEA Tuxedo defined servers configured by the user in the UBBCONFIG file. You can deactivate only application servers for the entire domain or for selected machines as follows:
See also Forcing Deactivation.
If you attempt to deactivate application servers for a domain or machine while there are clients still connected to the machine, the deactivation fails.
However, you can force deactivation even if clients remain connected as follows:
As objects are deactivated, the Progress of Deactivate window is displayed (as shown in Figure 3-14). The Progress of Deactivate window tracks the status of the deactivation process as it occurs. You can:
If you do not want to view the Progress of Deactivate window during the deactivation process, click Dismiss to close the window. The deactivation process continues in the background.
Figure 3-14 Progress of Deactivate Window
Note: Alternatively, if you decide you do not want to deactivate the chosen objects, you can click Terminate to end the deactivation process at any time. However, because terminating the operation in mid-process could yield unexpected results, it is recommended that you allow the process to conclude and then activate the objects again.
Using the BEA Tuxedo Administration Console, you can migrate server groups and machines to alternate processors. This allows you to schedule maintenance for the original machine. You can also move groups of services from one machine to an alternate machine. By doing so you can schedule maintenance for the original machine.
Note: A server group is the smallest unit that can be migrated to an alternate location.
Before you can migrate server groups and machines, MIGRATE must be an option for the domain (see the Options field on the System Parameters folder for the domain) and a backup machine must be specified (see the Master, Backup Machine field on the General folder for the domain).
When you migrate a server group, the environment on the destination machine must duplicate the environment on the source machine, including all packages such as database software and any other application software necessary to run the application.
You use the Migrate Objects window to select the object(s) you want to migrate. To display the Migrate Objects window, select Tools —>Migrate from the menu bar. (Alternatively, you can click the Migrate toolbar button or right-click a Groups object in the tree and select Quick Menu—>Migrate.)
The BEA Tuxedo Administration Console displays the Migrate Objects window containing a set of class-specific tab pages. Click a tab to display the page for the type of object you want to migrate.
To migrate a server group from one machine to another:
Your next steps depend entirely on the applications you are running. To ensure an orderly migration, you might need to drain queues, shut down groups, migrate databases using tools provided by the database vendor, and so on.
To migrate all servers from one machine to another:
Your next steps depend entirely on the applications you have running. You may need to drain queues, shut down groups, migrate databases using tools provided by the database vendor, and so on, to ensure an orderly migration.
As objects are migrated, the Progress of Migrate window is displayed. The Progress of Migrate window tracks the status of the migration process as it occurs. You can:
If you do not want to view the Progress of Migrate window during the migration process, click Dismiss to close the window. The migration process continues in the background.
Note: Alternatively, if you decide you do not want to migrate the chosen objects, you can click Terminate to end the migration process at any time. However, because terminating the operation in mid-process could yield unexpected results, consider allowing the process to conclude and then migrating the undesired objects back to the original machine.
If you have identified one machine as a Master and a second machine as a Backup, you can choose to run the BEA Tuxedo application from either machine. For example, you can swap the application from the Master to the Backup so that you can perform down-time maintenance on the Master machine. Or, if the Master processor loses the virtual circuit to other processors while the application is running, you can log in to the Backup machine. You can then bring up the DBBL on the backup node, and allow the application to continue running (although possibly in a degraded state).
To have the option to swap machines, you must have set the names of the machines that serve as the Master and Backup nodes of your system. You can set the Master and Backup machines, by either:
For more information about the Master, Backup Machine field, see the section Master Machine (TA_MASTER) in the section Configuring Domain Resources (T_DOMAIN Class) and Machine Role (TA_ROLE) in the section Configuring Machines (T_MACHINE Class).
To swap a BEA Tuxedo domain from one machine to another:
You can clean machines by removing dead, partitioned machines from the booted machine list or by checking for dead clients and servers if the machine is not partitioned.
Select Clean to clean the bulletin board on the specified machine to restart or clean up any servers that may require it. If the machine in question is partitioned, entries for processes and services identified as running on that machine are removed from all non-partitioned bulletin boards.
Occasionally, you may find it necessary to clean your machine (e.g., when the network has gone down or when clients or servers have been killed). The clean operation has the following effects:
If the machine is partitioned, entries for processes and services identified as running on the machine are removed from all non-partitioned bulletin boards. If the machine is not partitioned, any processes or services that cannot be restarted or cleaned up are removed.
If you clean a partitioned machine but the machine is still running, you have to kill the BEA Tuxedo system application and processes and remove all of the BEA Tuxedo system application shared memory, semaphores, and message queues by hand. A reboot is often faster.
You can perform the following service-related operations.
To advertise a service (either from an existing service or from a service default object), complete the following steps:
The Advertise Service window is displayed as shown in Figure 3-15.
Figure 3-15 Advertise Service Window
buildserver(1)
). If you leave this field blank, the entry in the Service Name field is used as the Function Name.To make a currently advertised service unavailable:
To reactivate a suspended service:
You can perform the following client-related tasks using the client Quick Menu.
If you want to isolate your client temporarily, you can suspend it.
When you suspend a client, the client is prevented from performing the following tasks:
tpcall
(3) or tpacall
(3)tpconnect
(3)tpbegin
(3)tpenqueue
(3)Clients within a transaction can make these calls until they abort or commit the current transaction, at which time they are suspended.
To reactivate a suspended client:
A client can be killed, or abortively deactivated, to remove it from the BEA Tuxedo application. The recommended method to kill a client is:
If the abortive deactivation is successful, a Result of Requested Change window is displayed, and the client icon is displayed as dead (icon with an X). To remove any dead items from the tree view, you need to use the Quick Menu Clean option.
If the client cannot be killed, an error message is displayed specifying the reason. Although the BEA Tuxedo Administration Console process will refuse to kill itself; one BEA Tuxedo Administration Console process can be used to kill another.
The application may not be able to kill the client due to platform or signaling restrictions. In this case, a native client is abortively terminated at its next access to Application-to-Transaction Manager Interface (ATMI), and a Workstation client connection to a workstation handler (WSH) will be preemptively torn down. The connections to all clients attached to that WSH are terminated.
You can perform the following workstation handler-related tasks using the Client Quick Menu.
If you want to isolate the clients connected to a particular workstation handler temporarily, you can suspend it. When you suspend a workstation handler, the clients connected to it are prevented from performing any of the following tasks:
tpcall
(3) or tpacall
(3)tpconnect
(3)tpbegin
(3)tpenqueue
(3)In addition, the suspended workstation handler will not accept any new client connections.
Note: A workstation handler involved in a transaction when you suspend it is not actually suspended until the transaction is aborted or committed.
To suspend a workstation handler:
To reactivate a suspended workstation handler:
A workstation handler can be killed, or abortively deactivated, to remove it from the BEA Tuxedo application. The recommended method to kill a workstation handler is as follows:
If the abortive deactivation is successful, a Result of Requested Change dialog box is displayed and the object is displayed as dead (icon with an X) until you clean it out with the Quick Menu Clean option. The connections to all clients attached to that workstation handler are terminated.
If you cannot kill the workstation handler, an error message is displayed, specifying the reason. The application may not be able to kill the workstation handler due to platform or signaling restrictions. In this case, a Workstation client connection to a workstation handler will be preemptively torn down.
You can use the BEA Tuxedo Administration Console to allocate and initialize shared memory and to remove shared memory and other IPC resources (for example, message queues and semaphores). The options that perform these functions are Open and Close.
To open an application queue space:
To close an application queue space:
You can delete an application queue message from its queue space if you do not need to keep it any longer.
To delete the application queue message:
If you must stop a transaction before it is complete, you can abort the transaction. Any data that changed as a result of that transaction is rolled back to its value at the start of the transaction. The transaction must be in either the ACTIVE, ABORTONLY, or COMCALLED state.
Caution: There is a very slight risk that the data roll back may not be successful. You can minimize the risk by aborting a transaction early in the process.
If you cannot abort the transaction, an error message is displayed specifying the reason.
A bridge is a connection or link between two machines in a multi-processor domain. From the BEA Tuxedo Administration Console, you can perform the following tasks:
To create a bridge between two machines, complete the following steps:
You can manage application security with the BEA Tuxedo Administration Console ACL objects. The BEA Tuxedo Administration Console allows you to create new ACL groups, set configuration parameters for ACLs, and ACL Principals. Domain ACLs also allow you to control access to an entire domain.
To create new ACL Groups, display the Create New Object form and enter values for the fields:
BEA Tuxedo system resources include CORBA interfaces, CORBA interface queues, and CORBA factories that are used in BEA Tuxedo client and server applications. You can use the BEA Tuxedo Administration Console to manage BEA Tuxedo resources during run time as follows:
During run time, you can perform the following actions on a CORBA interface:
If you want to isolate your interface temporarily, you can suspend it.
If the suspend is successful, the BEA Tuxedo Administration Console displays a Result of Requested Change dialog box and the tree represents the interface as suspended.
Note: If the interface cannot be suspended, the BEA Tuxedo Administration Console displays an error message.
To reactivate a suspended interface:
During run time, you can perform the following actions on a CORBA interface queue:
Prevent clients from accessing an interface queue on the application |
|
Allow clients to access an interface queue on the application |
If you want to isolate your interface queue temporarily, you can suspend it.
To suspend a CORBA interface queue:
To reactivate a suspended CORBA interface queue:
The BEA Tuxedo Administration Console displays the Result of Requested Change dialog box, indicating whether the reactivation is successful.
The BEA Tuxedo Administration Console only allows you to view BEA Tuxedo CORBA factory information. You cannot make configuration changes to a factory and you cannot create new factories. You can use the Configuration Tool pane to view the interface name for a Factory, the Factory ID, and the object state.
You can use the BEA Tuxedo Administration Console to monitor and track system events. The following sections describe how to use the BEA Tuxedo Administration Console for:
You can use the BEA Tuxedo Administration Console to view current statistics for administrative class objects using the Statistics Tool window.
The Statistics Tool window provides statistics for domains, machines, servers, services, and clients. To display the Statistics Tool window, select Tools —>Stats from the menu bar or click the Stats toolbar button. The BEA Tuxedo Administration Console displays the Statistics Tool window as shown in Figure 3-16.
The Statistics Tool displays the domain tab pages by default. You can click a tab to view the statistics for any of the other listed administrative class objects. The domain tab displays statistics for the following administrative classes in a domain:
The following table lists the parts of the Statistics Tool window.
The BEA Tuxedo Administration Console updates statistics at a regular interval. You can specify this interval in the Refresh field at the top of the Statistics Tool window. The interval value represents the number of seconds between Refresh operations. The default interval for refreshing the statistics is 60 seconds.
To suspend updating statistics, enter a zero in the Refresh field. To resume updating statistics, enter a number greater than zero. When you enter a zero in the Refresh field, the Hold button is re-labeled Resume; when you enter a value greater than zero, the Resume button toggles back to Hold.
You can display the statistics on any of the tab pages as either a two-dimensional or three-dimensional bar graph. To switch between these two types of graphs:
The BEA Tuxedo Administration Console can display statistics for all of the available objects in a class. At the bottom of the Statistics Tool window, the status line displays the number of class objects for which statistics are currently being displayed and the total number of objects of this type for which statistics are available. Figure 3-16 lists [Domain] Displaying: 5 Total: 5
. This line indicates statistics are displayed for all five of five possible objects.
You can select other available administrative objects and display their statistics using the Select Objects dialog box. To display this dialog box, click Select in the Statistics Tool window (upper left). As shown the following example, the Select Objects dialog box lists the available administrative objects for which you can display statistics.
To select one or more items from the list, highlight the item. Click OK to show statistics for your selection and close the Select Objects dialog box. Click Apply to show statistics for your selection and keep the Select Objects dialog box open for further selections.
If the system event broker server (TMSYSEVT) is configured, you can use the BEA Tuxedo Administration Console to monitor system-generated events.
To view system events via the Event Tool:
The menu bar across the top of this window offers four options as shown in the following table.
Create a record of the data currently held by the Event Tool. |
|
Display the Format Options dialog box to select parameters for the information being collected by the Event Tool. See Figure 3-18. |
|
Figure 3-18 Event Tool Format Options Window
Using the BEA Tuxedo Administration Console, you can view the ULOG
file from a selected machine in the active domain. You use the Logfile Tool window to display a ULOG
file.
To display the Logfile Tool window, select Tools —>Logfile from the menu bar or click the Logfile toolbar button. The Logfile button displays the ULOG
file from a particular machine in the active domain.
The Logfile Tool window is shown in Figure 3-19. The Logfile Tool initially displays a blank viewing area, a drop-down list box and several buttons. The following table describes the Logfile Tool window components.
To view a ULOG
file for a specific object, select a machine from the drop-down menu in the top left corner of the window. (To display the menu, press and hold the left mouse button on the down arrow. To select a menu item, drag the cursor to highlight a menu item and release the the mouse button.) As shown in Figure 3-19, the Logfile Tool displays the ULOG
file for the selected machine.
Figure 3-19 Sample ULOG File in Logfile Tool Window
To save a record of the displayed ULOG
file, click Snapshot on the Logfile Tool window.
To modify the format of the ULOG
display:
The Logfile Format window is displayed, as shown in Figure 3-20.
Figure 3-20 Logfile Format OptionsWindow
As shown in Figure 3-21, the Logfile Tool provides additional options. When you first invoke the Logfile Tool only a single row of buttons appears in the upper left corner of the Logfile Tool window. To display the additional Logfile Tool options, click the + sign button. The six fields that are then displayed allow you to select a ULOG
file and specify which parts of it you want to see.
Figure 3-21 Logfile Tool with All Options Displayed
![]() ![]() |
![]() |
![]() |