Chapter 3   The Tuxedo Management Console


The Tuxedo Management Console enables you to load files into the UIF repository and manage backend tasks assigned to the administrator. This chapter contains the following information:

• Overview of Management Console

• Tuxedo User Management

Overview of Management Console

---

The management console has two groups of functions:

• Tasks that are used to process and browse data and functions: data mining and add new data sources.

• User management that establishes relationships between the web and backend users.

The user mapping management tasks performed with the management console are explained in this chapter. See the Tuxedo Enterprise Connector Developer's Guide for a description of the other tasks of the management console.

There are two tabs: Tasks and User Mapping Management.

The Tasks tab contains icons for accessing screens that allow you to do Data Mining and to Create New Data sources. See the Tuxedo Enterprise Connector Developer's Guide for more details.

The User Mapping Management tab allows you to access icons for administrative tasks. These tasks are used by the administrator to view which users are using the system at any given period of time.

To Enter the Management Console

There are two versions of the Management Console, one for NT and one for Unix, as follows:

From NT

Select Start>Programs>iPlanet Application Server 6.0>Tuxedo Connector - Management console.

Select the Tuxedo Management Console icon, and click the Open button in the upper right to display the Tuxedo Management Console.

From Unix

To enter the Tuxedo Management Console from Unix enter the following at the Unix prompt:

<ias directory>/ias/APPS/bin/tuxedoconsole.sh

Upon opening the Tuxedo Management Console, the following screen appears:

In the Tasks tab, the following operations can be enacted:

• Data Mining

• Create a new data source

• Fml 16 Import

• Fml 32 Import

• View 16 Import

• View 32 Import

• X_Common Import

• X_C_Type Import

Data mining is the technique used to discover patterns and relationships amongst the data. This information is then used to locate information in a database.

• Field Manipulation Language (Fml) - is a native Tuxedo interface used for maintaining buffers with field/value pairs. Fml 16 Import is the 16-bit version of this interface.

• Fml 32 Import - is the 32-bit version of this generic, native Tuxedo interface.

• VIEW - is a native Tuxedo typed buffer format where the data is composed of one or more fields similar to a C structure or a COBOL record. View 16 Import is the 16-bit version of this format.

• View 32 Import - is the 32-bit version of this native Tuxedo format.

• X_Common Import

• X_C_Type Import

The IDL File

The IDL file is a specific administrator created file that aids in the transfer and conversion of Tuxedo services into repository. For example, Fml 16 and 32, View 16 and 32, X_Common, and X_C_Type to XML files. There are nine types of input/output buffers for Tuxedo:

• FML 16

• FML32

• VIEW16

• VIEW32

• X_COMMOM

• X_C_TYPE

• *STRING

• *CARRAY

• *X_OCTET

The IDL file has three main components:

• Interface

• Services

• Parameters

Interface

The interface is the initial component and wraps around the other two components. The interface begins with the word "interface" followed by the file name, an open brace, the parameter, a closed brace, and semicolon to signify closure:

Services

A Service contains the word "void", the service name, an open parenthesis, the parameters, and then a closed parenthesis and semicolon to signify closure:

Parameters

Parameters contain the in/out file, the buffer name, and the file name. The following are examples of parameters for View 16, View 32, X_Common, X_C_Typename, and String:

The following example displays the three IDL file components, as defined:

Notice the structure and components in the sample.

The following is an .idl file example:

interface tuxedo

{

   void NOINOUTTEST1(
   );

   void STRINGTEST1(
      [in] STRING INPUTSTRING
      [out] STRING OUTSTRING
   );

   void STRINGTEST2(
      [out] STRING OUTSTRING
   );

   void STRINGTEST3(
      [in] STRING INSTRING
   );

   void CARRAYTEST1(
      [in] CARRAY INPUTDATA
      [out] CARRAY OUTPUTDATA
   );

   void CARRAYTEST2(
      [out] CARRAY OUTPUTDATA
   );

   void CARRAYTEST3(
      [in] CARRAY INPUTDATA
   );

   void CARRAYTEST4(
      [in] CARRAY INPUTDATA
      [out] CARRAY OUTPUTDATA
   );

   void XOCTETTEST1(
      [in] X_OCTET INPUTDATA
      [out] X_OCTET OUTPUTDATA
   );

   void XOCTETTEST2(
      [out] X_OCTET OUTPUTDATA
   );

   void XOCTETTEST3(
      [in] X_OCTET INPUTDATA
   );

   void XOCTETTEST4(
      [in] X_OCTET INPUTDATA
      [out] X_OCTET OUTPUTDATA
   );

   void TPURCODETEST1(
      [in] STRING INPUTSTRING
      [out] STRING OUTSTRING
   );

   void TPURCODETEST2(
      [in] STRING INPUTSTRING
      [out] STRING OUTSTRING
   );

   void TPURCODETEST3(
      [in] STRING INPUTSTRING
      [out] STRING OUTSTRING
    );

   void TPFAILTEST1(
      [in] STRING INPUTSTRING
      [out] STRING OUTSTRING
   );

   void TPEXITTEST2(
      [in] STRING INPUTSTRING
      [out] STRING OUTSTRING
   );

   void VIEW16TEST1(
      [in,VIEW16 v16test1] VIEW16 inputBlock
      [out,VIEW16 v16test1] VIEW16 outputBlock
   );

   void VIEW16TEST2(
      [in, VIEW16 v16test1] VIEW16 inputBlock
      [out,VIEW16 v16test2] VIEW16 outputBlock
   );

   void VIEW16TEST3(
      [in,VIEW16 v16test4] VIEW16 inputBlock
   );

   void VIEW16TEST4(
      [out,VIEW16 v16test4] VIEW16 outputBlock
   );

   void VIEW32TEST1(
      [in,VIEW32 v32test1] VIEW32 inputBlock
      [out,VIEW32 v32test1] VIEW32 outputBlock
   );

   void VIEW32TEST2(
      [in, VIEW32 v32test1] VIEW32 inputBlock
      [out, VIEW32 v32test2] VIEW32 outputBlock
   );

   void VIEW32TEST3(
      [in, VIEW32 v32test4] VIEW32 inputBlock
   );

   void VIEW32TEST4(
      [out, VIEW32 v32test4] VIEW32 outputBlock
   );

   void XCTYPETEST1(
      [in, X_C_TYPE xctest1] X_C_TYPE inputBlock
      [out, X_C_TYPE xctest2] X_C_TYPE outputBlock
   );

   void XCOMMONTEST1(
      [in, X_COMMON xcomtest1] X_COMMON inputBlock
      [out, X_COMMON xcomtest2] X_COMMON outputBlock
   );

   void FML16TEST1(
      [in, FML] String string16,
      [out,FML] String string16[]
   );

   void FML16TEST2(
      [out,FML] long long16[]
   );

   void FML16TEST3(
      [in, FML] String string16,
      [in, FML] short short16,
      [in, FML] double double16,
      [in, FML] float float16,
      [in, FML] long long16
   );

   void FML32TEST1(
      [in, FML32] String string32,
      [out,FML32] String string32[]
   );

   void FML32TEST2(
      [out,FML32] long long32[]
   );

   void FML32TEST3(
      [in, FML32] String string32,
      [in, FML32] short short32,
      [in, FML32] double double32,
      [in, FML32] float float32,
      [in, FML32] long long32
   );

   void MIXEDDOTEST1(
      [in] STRING INPUTSTRING,
      [out,FML] String string16[]
   );

   void MIXEDDOTEST2(
      [in,FML] String string16,
      [out] STRING OUTSTRING
   );

   void MIXEDDOTEST3(
      [in,VIEW16 v16test1] VIEW16 inputBlock,
      [out,FML] String string16,
      [out,FML] short short16,
      [out,FML] double double16,
      [out,FML] float float16,
      [out,FML] long long16
   );

   void MIXEDDOTEST4(
      [in,FML] String string16,
      [in,FML] short short16,
      [in,FML] double double16,
      [in,FML] float float16,
      [in,FML] long long16,
      [out,VIEW16 v16test1] VIEW16 outputBlock
   );

   void TRTIMEOUTTEST1(
   );

   void EMP_INSERT(
      [in,FML] long EMP_EMPNO,
      [in,FML] String EMP_NAME,
      [in,FML] String EMP_SSN,
      [in,FML] String EMP_PHONE,
      [in,FML] long EMP_DEPT,
      [in,FML] float EMP_SALARY
   );

   void EMP_UPDATE(
      [in,FML] long EMP_EMPNO,
      [in,FML] String EMP_NAME,
      [in,FML] String EMP_SSN,
      [in,FML] String EMP_PHONE,
      [in,FML] long EMP_DEPT,
      [in,FML] float EMP_SALARY
   );

   void EMP_DELETE(
      [in] String EMP_NO
   );

   void EMP_GET(
      [in] String EMPNO,
      [out,FML] long EMP_EMPNO,
      [out,FML] String EMP_NAME,
      [out,FML] String EMP_SSN,
      [out,FML] String EMP_PHONE,
      [out,FML] long EMP_DEPT,
      [out,FML] float EMP_SALARY
   );

}

Data Mining

Upon selecting the data mining option, the Choose Data Source window appears as follows:

A list of available data sources appears, select a data source, and click the OK button. The Choose Tuxedo Function window appears:

Use this window to choose the IDL files to be converted to XML and imported to the UIF repository. You may select one or more IDL files to load at a time. Select a function from the list of available funtions presented and click the OK button. The selected IDL file(s) are converted to XML and loaded into the UIF repository. Use the Add Function button to add a Tuxedo function. The following is a sample of a .idl file for Tuxedo-online Bank sample application:

The following shows the IDL file converted to XML, and loaded into the UIF repository browser:

Notice the similar structures in both the IDL file and the UIF browser repository such as inquiry, deposit, and withdraw. You must restart your browser and management console to view the loaded function(s). Click the Cancel button to return to the previous window.

Create New Data Source

This feature is used to create new data sources.

Upon selecting this option, the Create New Data Source window appears:

Enter in the following information:

DataSource Name	This is the name you assign to the new data source.
WSNADDR	The work station address of the computer and port number that Tuxedo is running under.
WSDEVICE	The work station device as it appears in the Tuxedo system.
TUXDIR	The directory path where Tuxedo is installed.
PASSWORD	The password used to log on to the Tuxedo system. This password is issued by the application administer. This password is specified in the initialization information.
SECURITY	You can choose from the available security options. TPNOAUTH means Tuxedo Protocol Normal Authority. TPSYSAUTH means Tuxedo Protocol System Authority only, limiting the user to system related areas. TPAPPAUTH is Tuxedo Protocol Application Authorization, limiting the user to applications only.

Click on OK to continue to create the new data source, or Cancel to return to the previous window. Restart the management console and the browser to view the new data source.

Edit the Data Source

The Details button invokes the Data Source Details window.

To edit a data source, click on the edit button to edit the datasource.

The window lists the following information for the existing data source:

WSNADDR	The workstation address of the computer and port number that Tuxedo is running under.
WSDEVICE	The workstation device as it appears in the Tuxedo system.
TUXDIR	The directory path where Tuxedo is installed.
PASSWORD	The password used to log on to the Tuxedo system. This password is issued by the application administer. This password is specified in the initialization information.
SECURITY	You can choose from the available security options. TPNOAUTH means Tuxedo Protocol Normal Authority. TPSYSAUTH means Tuxedo Protocol System Authority only, limiting the user to system related areas. TPAPPAUTH is Tuxedo Protocol Application Authorization, limiting the user to applications only.

Type in the required information and click OK. The data source has been edited Restart the management console and the browser to view the new function.

Fml 16 Import

Fml 16 Import is the 16-bit version of this native Tuxedo interface used to maintain buffers with field/value pairs.

Upon selecting the Fml 16 option, the Choose Data Source window displays:

Select a data source from the sources listed, and click on OK. The selected data source is selected for import. Click on Cancel to return to the previous screen. Click on Details to view the DataSource Details window, as follows:

To import the Fml 16 Import interface, do the following:

1. Click on Add Function.

   The File Section window appears.

2. Select the desired Tuxedo Fml 16 definition text file.

3. Select the file and click the OK button.

Fml 32 Import

Fml 32 Import is the 32-bit version of this native Tuxedo interface used to maintain buffers with field/value pairs.

Upon selecting the Fml 32 Import option, the Choose Data Source window displays:

Select a data source from the sources listed, and click on OK. The selected data source is selected for import. Click on Cancel to return to the previous screen. Click on Details to view the DataSource Details window, as follows:

To import the Fml 32 Import interface, do the following:

1. Click on Add Function.

   The File Section window appears.

2. Select the desired Tuxedo Fml 32 definition text file.

3. Select the file and click the OK button.

View 16 Import

View 16 Import is the 16-bit version of a native Tuxedo buffer format where the data is composed of one or more fields similar to a C structure or a COBOL record.

Upon selecting the View 16 Import option, the Choose Data Source window displays:

Select a data source from the sources listed, and click on OK. The selected data source is selected for import. Click on Cancel to return to the previous screen. Click on Details to view the DataSource Details window, as follows:

To import the View 16 Import interface, do the following:

1. Click on Add Function.

   The File Section window appears.

2. Select the desired text file.

   The imported file should be .vv for NT and .V for Solaris.

3. Select the file and click the OK button.

View 32 Import

View 32 Import is the 32-bit version of a native Tuxedo buffer format where the data is composed of one or more fields similar to a C structure or a COBOL record.

Upon selecting the View 32 Import option, the Choose Data Source window displays:

Select a data source from the sources listed, and click on OK. The selected data source is selected for import. Click on Cancel to return to the previous screen. Click on Details to view the DataSource Details window, as follows:

To import the View 32 Import interface, do the following:

1. Click on Add Function.

   The File Section window appears.

2. Select the desired text file.

   The imported file should be .vv for NT and .V for Solaris.

3. Select the file and click the OK button.

X_Common Import

Upon selecting the X_Common Import option, the Choose Data Source window displays:

Select a data source from the sources listed, and click on OK. The selected data source is selected for import. Click on Cancel to return to the previous screen. Click on Details to view the DataSource Details window, as follows:

To import the X_Common Import interface, do the following:

1. Click on Add Function.

   The File Section window appears.

2. Select the desired text file.

   The imported file should be .vv for NT and .V for Solaris.

3. Select the file and click the OK button.

X_C_Type Import

Upon selecting the X_C_Type Import option, the Choose Data Source window displays:

Select a data source from the sources listed, and click on OK. The selected data source is selected for import. Click on Cancel to return to the previous screen. Click on Details to view the DataSource Details window, as follows:

To import the X_C_Type Import interface, do the following:

1. Click on Add Function.

   The File Section window appears.

2. Select the desired text file.

   The imported file should be .vv for NT and .V for Solaris.

3. Select the file and click the OK button.

Tuxedo User Management

---

The Tuxedo User Management tab allows you to access icons for administrative tasks. These administrator tasks are used to view which users are using the system at any given time, and to assign connection pools.

In the Tuxedo User Management tab, the following options are available:

• Tuxedo User Mapping

• Tuxedo Connection Pools

Tuxedo User Mapping

From the Tuxedo Management Console window, click the Tuxedo User Mapping tab. The Tuxedo User Management tree file appears on the left, and the Data Source Name appears on the right. In the Tuxedo User Mapping option, you can add, edit and delete web user information and entity formation.

The Data Source Name window displays the following selected data:

Web User Information	The web user information, such as the user's ID, the transaction name, and the entity name, is listed here: .
Entity Information	The entity information such as the backend user name, and entity name, is listed here.

Web User Information

The Web User Information is used to map a web user identity to a backend user identity. The administrator assigns an entity name for the web users. This web ID is used by the server to enable users to move freely across multiple systems. You can add, change users, and delete users and entities from this window. The aministrator assigns entity information before the web user information, as one is based upon the parameters defined in the entity information. Because certain web user's parameters are based upon entity information parameters, the administrator must first establish entity information. The Web User Information area lists the following:

Web ID	This is an ID assigned to users on the system.
Entity Name	This is the name of the assigned backend user. The naming process is dependent upon the database type used.

Editing a Web User

You can add a new web user, change a web user, and delete a web user by pressing the corresponding button.

To add a new web user, click on the New User button. The Web User Information window appears:

Figure 3-1    The Web User Information window

Type in the web ID, and select an entity name from the available names. Click on OK when finished to return to the main window.

To change a user, click on the Change User button and edit the desired field. Click on OK when finished to return to this window.

To delete a web user, select the desired web user and click on the Delete button. The web user will be deleted and you will return to the main window.

Entity Information

The Entity Information area is used to list the following data about the backend entities assigned to the web users:

Backend User Name	The name of the backend user. This name also indicates which system the user is currently using.
Backend Password	The password of the backend user. This is assigned by the user.
Entity Name	The name of the backend entity. This is assigned by the system administrator. Certain responsibilities and restrictions can be associated with this parameter.

Editing an Entity

You can add a new entity, change an entity, and delete an entity by clicking on the corresponding button.

To add a new backend entity, click on the New Entity button. The Entity Information window appears:

Figure 3-2    The Entity Information window

Type in the appropriate data iand click on the OK button. The new entity information will appear in the Entity Information area of the window.

To change a entity information, click on the Change entity button and edit the desired field(s). Click on the OK button. The edited entity will appear in the Entity Information area of the window.

To delete a backend entity, select the desired entity and click on the Delete button.

When you have completed all actions in this window, click on the Save button. All your additions and changes will be saved to the system.

---

Note	When you delete backend users, also delete web users. Web users pointing to deleted backend users will not function.

---

Tuxedo Connection Pools

Pools are used to conserve connections to the Tuxedo database.

The Tuxedo Connection Pools lists pool information such as debug level, maximum pool size, maximum wait, monitor interval, steady pool size, unused maximum life, and entity.

To change a pool, select the desired field, enter in the desired value within the allowed parameters, and click the Save button.