---

BEA TUXEDO Builder Release Notes

The BEA TUXEDO Builder Release Notes present changes or updates to the standard documentation provided with your BEA TUXEDO Builder 2.0 product release. Information in these Release Notes should be considered authoritative should anything in the Release Notes conflict with information in the online help or the PDF files.

The BEA TUXEDO Builder documentation is presented in HTML and PDF formats on the CD-ROM as well as being available via the BEA Systems Web site, at http://www.beasys.com/.

---

Supported Platforms

This section describes the platforms supported in the BEA TUXEDO Builder 2.0 release. BEA TUXEDO Builder platform support consists of a multifaceted support matrix for various versions of hardware, operating systems, BEA TUXEDO versions, Windows client tools, Java runtime environments, Netscape Navigator, Rational Rose, and Oracle. In an effort to make this issue simpler, we present each product separately and deal with BEA TUXEDO support at a global level wherever possible.

Note: Check the BEA Customer Support Web page for the latest information on certification of Builder products on newer versions of the Java Runtime Environment (JRE) and Java Development Kit (JDK).

Overall Server Platforms

Table 1 Server Platforms

Hardware	Operating System (initial)	TUXEDO Releases
Sun Sparc	2.5.1, 2.61	TUXEDO 6.3, 6.4
HP HP9000	HP-UX 10.102, 10.20, 11.03	TUXEDO 6.3, 6.4
Intel	Intel/Windows NT 4.0	TUXEDO 6.3, 6.4

¹ Support for Sun Solaris 2.6 is available with TUXEDO 6.4 only.

² Support for HP-UX 10.10 is limited. See the following tables for details.

³ Support for HP-UX 11.0 is available with TUXEDO 6.4 only.

Contract Repository Platforms

Table 2 Contract Repository Server Platforms

Operating Systems	Intel/Windows NT 4.0 Sparc Solaris 2.5.1, 2.6 HP-UX 10.10, 10.20, 11.0
Help System Requirements	Netscape Communicator 4.0 or above.

Note: Intel/Windows NT support is with Service Pack 3 installed.

Table 3 Contract Repository Editor Platforms

Operating Systems	Intel/Windows NT 4.0, Windows 95 Sparc Solaris 2.5.1, 2.6 HP-UX 10.20, 11.0
Java Runtime Environment (JRE)	JRE or JDK 1.1.5 (for Windows NT 4.0 and Windows 95) JRE or JDK 1.1.5 (for Solaris 2.5.1, 2.6) JDK 1.1.3 (for HP-UX 10.20, 11.0)
Help System Requirements	Netscape Communicator 4.0 or above.

Active Expert Platforms

Table 4 Active Expert Platforms

Operating Systems	Intel/Windows NT 4.0 and Windows 95
Sample Code Generation	Visual Basic 4.0 and 5.0, PowerBuilder 5.0.03, Microsoft Visual C++ 4.0, 4.1, 4.2, and 5.0
Help System Requirements	Netscape Communicator 4.0 or above.

Rose Expert Platforms

Table 5 Rose Expert Platforms

Operating Systems	Intel/Windows NT 4.0 and Windows 95
Rational Rose	Rational Rose 4.0.5 or later (but not Rational Rose 98)
Rose Expert Generated Code	Windows NT 4.0, Windows 95 (service request classes only) Solaris 2.5.1, 2.6 HP-UX 10.10, 10.20, 11.0
Rose Expert Sample	Microsoft Visual C++ 5.0, Oracle 7.3.3 for database enabled sample, UNIX sample
Java Runtime Environment (JRE)	JRE or JDK 1.1.5
Help System Requirements	Netscape Communicator 4.0 or above.

C++ Expert Platforms

Table 6 C++ Expert Platforms

Operating Systems	Intel/Windows NT 4.0, Windows 95 Sparc Solaris 2.5.1, 2.6 HP-UX 10.10 (support for generated code only), 10.20, 11.0
Java Runtime Environment (JRE)	JRE or JDK 1.1.5 (for Windows NT 4.0 and Windows 95) JRE or JDK 1.1.5 (for Solaris 2.5.1, 2.6) JDK 1.1.3 (for HP-UX 10.20, 11.0)
C++ Expert Generated Code	Windows NT 4.0, Windows 95 (service request classes only) Solaris 2.5.1, 2.6 HP-UX 10.10, 10.20, 11.0
C++ Expert Sample	Same development platforms as described for "C++ Expert Generated Code" along with Oracle 7.3.3 for database enabled sample.
Help System Requirements	Netscape Communicator 4.0 or above.

Configuration Expert Platforms

Table 7 Configuration Expert Platforms

Operating Systems	Intel/Windows NT 4.0, Windows 95 Sparc Solaris 2.5.1, 2.6 HP-UX 10.10 (support for generated configurations only), 10.20, 11.0
Java Runtime Environment (JRE)	JRE or JDK 1.1.5 (for Windows NT 4.0 and Windows 95) JRE or JDK 1.1.5 (for Solaris 2.5.1, 2.6) JDK 1.1.3 (for HP-UX 10.20, 11.0)
Configuration Expert Generated UBBCONFIG	Windows NT 4.0 Sparc Solaris 2.5.1, 2.6 HP-UX 10.0, 10.20, 11.0
Help System Requirements	Netscape Communicator 4.0 or above.

Overall Compiler Support Matrix

The following table shows compilers supported for BEA TUXEDO Builder 2.0.

Table 8 Compiler Support

Hardware	Operating System	Command Name	C++ Compiler Description
Sun-SPARC	Solaris 2.5.x	CC	Sun WorkShop Compiler C++, Version 4.2
HP HP9000	HP-UX 10.10, 10.20	CC	HP Native C++, Version A.10.20
Intel	Intel/Windows NT 4.0 and Windows 95	cl	Microsoft Visual C++, Version 5.0

---

Pre-installation Notes for Windows

These pre-installation notes are also included in the file req.txt displayed by the setup program during the Windows installation.

1. Before installing the Active Expert, you must install the BEA TUXEDO 6.3 or 6.4 client (/WS) software. The Active Expert also requires the installation of Object Bridge version 1.2 which will be done automatically when you select the Active Expert component to install. If you have previously installed the Object Bridge software, you must uninstall it before installing the Active Expert. Also, you should be sure that OBRIDGE.DLL is removed from your machine after the uninstall.

2. The C++ Expert, Configuration Expert, Rose Expert, and Contract Repository Editor require access to the Java Runtime Environment 1.1.5 in order to run. You must either have an existing Java Runtime Environment 1.1.5 on your workstation or install the Java Runtime Environment 1.1.5 component from the Builder 2.0 product CD.

3. Before installing the Contract Repository Server on Windows NT 4.0, you must install the BEA TUXEDO 6.3 or 6.4 server (/T) software.

4. When installing the BEA TUXEDO 6.3 or 6.4 server (/T) and client (/WS) components on the same machine (Windows NT 4.0), we suggest that you install the client first, then install the server. When installing the Contract Repository Server on Windows NT 4.0, the installation program looks in the Windows registry for the path (TUXDIR) to the BEA TUXEDO /T Server installation. If the BEA TUXEDO client components are being installed last and you tell the setup program to install in a different directory than the server components, the installation overwrites the TUXDIR settings, thus the server components cannot be found.

5. The Builder 2.0 product comes with a special version of Jolt 1.1, which should only be used with Builder. If you already have the standard version of Jolt 1.1 installed, this special version will not be installed. The installation program will check if the user has Jolt 1.1 on his system through checking the Windows registry. Jolt 1.1 must be present so that the C++ Expert, Contract Repository Editor and Rose Expert can communicate with the Contract Repository server. This special version of Jolt 1.1 uses the Contract Repository instead of the Jolt Repository as its source of interface information. Jolt will officially support the Contract Repository in a future release.

6. Before installing the Active Expert on a system where you want to use Visual Basic, make sure that Visual Basic is already installed. If Visual Basic is not installed first, the Active Expert Add-in will not appear on the Visual Basic Add-in menu. The Active Expert Add-in lets you access a secure BEA TUXEDO system during development time.

7. Before installing the Rose Expert, you must install Rational Rose version 4.0.5 or later (but not Rational Rose 98).

---

Post-installation Notes for Windows

These post-installation notes are also included in the file readme.txt displayed by the setup program during the Windows installation.

1. If you are upgrading from Builder 1.0 you will need to run the bldr_upgrade program to translate your Builder 1.0 Repository to Builder 2.0 format. An example of the command line for this would be:

   bldr_upgrade -r 
   old_data_file -u 
   irepository

   where:

   • old_data_file is your repository data file name

   • irepository refers to the new repository data file included in the 2.0 release

2. After installing the Active Expert, you should set the WSENVFILE environment variable of BEA TUXEDO /WS to point to the correct configuration file. In the configuration file, make sure that the value of the WSNADDR parameter matches the Workstation Listener (WSL) address of the BEA TUXEDO system which is running the Repository server. A sample of this configuration file can be found in the Active Expert installation directory as tuxedo.ini. Also, make sure that the /WS BIN directory is in the PATH.

3. After installing the Contract Repository server, you must set up a BEA TUXEDO server configuration to run the Contract Repository server (IREPSVR), Jolt (JSL), and /WS (WSL). Also, if you want to run the Active Expert sample application, you must have the BANKAPP servers in this configuration. On Windows NT systems, the sample files to help you set up this configuration can be found in the RepServer directory. (UBBSample.txt contains a complete sample UBB configuration. EnvfileSample.txt contains a sample environment file for the sample UBB configuration.) Note that AUTOTRAN must be set to Y (AUTOTRAN=Y) in the UBB for the BANKAPP services to function correctly. For information on the configuration of Jolt 1.1 and the Contract Repository server (IREPSVR), refer to the BEA TUXEDO Builder Setup and Installation Guide.

4. Note that if you would like to do both BEA TUXEDO Builder client development (with C++ Expert, Rose Expert, Active Expert, or Contract Repository Editor) and Jolt client development for the same BEA TUXEDO application, you must configure your BEA TUXEDO development server to run separate BEA TUXEDO domains for each client development environment. The reason you must do this is because the instance of Jolt 1.1 used for C++ Expert or Active Expert development must use the Contract Repository server (IREPSVR) instead of the standard Jolt Repository server (JREPSVR).

5. Before running any of the sample applications, you must read the ReadMe.txt file that is provided in the directory of each sample. It describes additional installation steps that must be performed and information necessary to successfully run that particular sample. For example, the C++ Expert and Rose Expert samples require that BEA TUXEDO server software be installed.

6. If the C++ Expert was previously installed and a reinstallation or a fresh installation is done, the settings.ce file present in the home directory of the logged-in user should be removed before starting the C++ Expert. This ensures that any old installation settings are reset to the new ones. The C++ Expert will automatically create the settings.ce file containing the current installation's settings in the logged-in user's home directory during startup.

7. On Windows 95 systems, the Contract Repository Editor, C++ Expert, Configuration Expert, and the collect data program for Configuration Expert are brought up by BAT files. After closing these Java applications, the DOS windows which are brought up by the BAT files are not closed automatically. You need to close the DOS windows manually. Or if you want the DOS window to close automatically when you exit the application, you can bring up the Properties dialog on the BAT file, click on the Program tab, and set "close on exit".

---

Pre-installation Notes for UNIX

1. Under some circumstances, a HP-UX system will append a "." to file names when the file is stored on a CD-ROM. The install.sh install script depends on a file called readme being in the platform directory. The readme file sometimes appears as "readme." on HP-UX systems and the installation will fail if it cannot find this file. There are two possible workarounds:

   • Copy the files to disk (via cp -r) and rename "readme." to "readme"

   • Start the PFS daemons for mounting the CD-ROMs:

     nohup pfs_mountd &
     nohup pfsd &

     Mount the CD-ROM with the pfs_mount command:

     pfs_mount -o xlat=unix /dev/dsk/dev_file /mount_point

   Once one of the previous has been completed, you can run the install.sh program and complete the installation.

2. When mounting the installation CD on a UNIX system, you should use the -o cdcase option. Following is an example of using this option:

   mount -F cdfs -o cdcase /dev/dsk/c0t2d0 /cdrom

   For more information, refer to the mount_cdfs reference page.

3. Before installing the Contract Repository Server, you must install the BEA TUXEDO 6.3 or 6.4 server (/T) software on your server.

4. The C++ Expert, Configuration Expert, and Contract Repository Editor require access to the Java Runtime Environment (JRE) in order to run. (Refer to "Supported Platforms" of these Release Notes for information on which versions of the JRE are supported for each product.)

---

Post-installation Notes for UNIX

1. If you are upgrading from Builder 1.0 you will need to run the bldr_upgrade program to translate your Builder 1.0 Repository to Builder 2.0 format. An example of the command line for this is:

   bldr_upgrade -r 
   old_data_file -u 
   irepository

   where:

   • old_data_file is your repository data file name

   • irepository refers to the new repository data file included in the 2.0 release

2. After installing the Contract Repository server, you must set up a BEA TUXEDO server configuration to run the Contract Repository server (IREPSVR), Jolt (JSL), and /WS (WSL). Also, if you want sample applications, you must have the BANKAPP servers in this configuration. On UNIX, the sample files to help you set up this configuration can be found in the udataobj directory under the TUXDIR directory. (ubbirep contains a complete sample UBB configuration. irep.env contains a sample environment file for the sample UBB configuration.) Note that AUTOTRAN must be set to Y (AUTOTRAN=Y) in the UBB for the BANKAPP services to function correctly. For information on the configuration of Jolt 1.1 and the Contract Repository server (IREPSVR), refer to the BEA TUXEDO Builder Setup and Installation Guide.

3. Note that if you would like to do both C++ Expert and Jolt client development for the same BEA TUXEDO application, you must configure your BEA TUXEDO development server environment to run separate BEA TUXEDO domains for each client development. The reason you must do this is because the instance of Jolt 1.1 used for C++ Expert development must use the Contract Repository server (IREPSVR) instead of the standard Jolt Repository server (JREPSVR).

4. Before running any of the sample applications, you must read the ReadMe.txt file that is provided in the directory of each sample. It describes additional installation steps that must be performed and information necessary to successfully run that particular sample. For example, the C++ sample requires that BEA TUXEDO server software be installed.

5. If the C++ Expert was previously installed and a reinstallation or a fresh installation is done, the settings.ce file present in the home directory of the logged-in user should be removed before starting the C++ Expert. This ensures that any old installation settings are reset to the new ones. The C++ Expert will automatically create the settings.ce file containing the current installation's settings in the logged-in user's home directory during startup.

---

Known Limitations

The following tables identify known limitations or bugs associated with the BEA TUXEDO Builder 2.0 release and includes possible workarounds, where applicable. Each bug has an associated change request (CR) identification number. Please refer to this number when contacting Customer Support for problem resolution or updates on these issues. (See "Contacting Customer Support.")

All Products

Table 9 All Products Change Requests

CR013515	Using keyboard shortcuts in a hesitant way causes text fields in dialogs to refuse input
	Problem	If users enter keyboard shortcuts and pause on a key so that the Ctrl or Shift key(s) are depressed for an extended period of time rather than for an instant, then the appropriate dialog is displayed but the text fields will not accept input. The problem is registered as Bug # 4035364 at JavaSoft. For more information, see: http://developer.java.sun.com/developer/ bugParade/index.html
	Platform	Windows NT and Windows 95 (for all Builder products except the Active Expert, which does not have this problem)
	Workaround	When using keyboard shortcuts (especially Shift and Ctrl keys), type the key sequence quickly and let go of the keys immediately.

Contract Repository Editor

Table 10 Contract Repository Editor Change Requests

CR013222	When bringing up client components on UNIX systems, scrollbar warning is displayed
	Problem	On Solaris and HP-UX platforms, the following warning is generated during startup: The scrollbar page increment is less than 1 This warning does not affect the functioning of the Contract Repository Editor in any way. (This warning is being redirected to the stderr file.)
	Platform	Solaris and HP-UX platforms
	Workaround	This warning does not affect the functioning of the Contract Repository Editor and should be ignored.
CR013278	Modifying an element to have the same element name, length and type as an existing one crashes the IREPSVR
	Problem	Duplicate elements are not allowed in the Contract Repository. The Contract Repository Editor prevents you from adding a duplicate element and displays an alert message, but it does not catch an attempt to modify an existing element to create a duplicate. If you modify an existing element to have the exact same name, length, and data type of another element, this causes the IREPSVR to crash.
	Platform	All platforms.
	Workaround	Do not create duplicate elements.
CR013448	Starting the Bulk Loader for the Contract Repository on Windows platforms does not work as documented
	Problem	In the Contract Repository Editor online help, under 4. Bulk Loading TUXEDO Services; Getting Started Using the Bulk Loader; "Using Windows NT or Windows 95 Platforms," the instructions on how to activate the bulk loader are incomplete.
	Platform	Applies to instructions for Windows NT and Windows 95 only
	Workaround	To start the bulk loader on a Windows NT or Windows 95 platform, type the following: C:\> set CLASSPATH=C:<pathname> C:\> jre|java bea.repositoryadm.ibld -classpath %classpath% [-n] [-u usrname] [-r usrrole] <// host: port> < filename> Then type your user password and application password (if required) and press Enter. Note: You can use either the jre or java. If you are using only the Java Runtime Environment (JRE) you can use jre. If you are using the Java Development Kit (JDK), you can use either java or jre.
CR013677	If the Contract Repository server (IREPSVR) is not running, you cannot successfully log on to the Contract Repository Editor and no alert is given to indicate what the problem is
	Problem	If the IREPSVR is not running, the Contract Repository Editor will not be able to connect to the Contract Repository. No error message is displayed to indicate what the problem is. For the Contract Repository Editor, a clue that the IREPSVR is not running is that upon logon the repository view in the Editor appears empty. It is not possible, in this case, to expand any of the root nodes in the Repository tree view-no contents or data will be displayed. (See also CR013677 in Table 11 and Table 13.)
	Platform	All platforms
	Workaround	Make sure the Contract Repository server (IREPSVR) is running.

Active Expert

Table 11 Active Expert Change Requests

CR010369	Live updates not working
	Problem	The Active Expert does not show live updates to the Contract Repository.
	Platform	All platforms
	Workaround	To view updates to the Contract Repository created while the Active Expert Application Builder is running, you must exit and restart the Active Expert Application Builder. Exiting and restarting will give you a consistent and up-to-date Repository and Workstation window display.
CR010370	Interface name limitation
	Problem	ActiveX controls with names of more than 40 characters will not work. This is a Visual Basic limitation. In Visual Basic, the ActiveX control name is partially determined by the module and interface names. For example, if there is a module foo, and an interface bar, the Visual Basic name will be: fooLibCtl.foobarOCX
	Platform	All platforms
	Workaround	The Active Expert Application Builder does not allow users to create ActiveX controls for which the module and interface names would produce an ActiveX control name that would be greater than 40 characters.
CR010481	Cannot pick up online help/doc if it is not installed with Active Expert at the same time
	Problem	If the Online Help and Documentation is installed before or after the Active Expert is installed, the Online Help and Documentation is not accessible from the Active Expert Application Builder.
	Platform	All platforms
	Workaround	Uninstall the Active Expert and reinstall it along with the Online Help and Online Documentation. Otherwise, contact Technical Support for a solution that involves editing the Windows registry.
CR010516	ActiveX controls are not supported in Visual C++
	Problem	ActiveX controls are not supported for Visual C++.
	Platform	All platforms
CR010518	Sample code for multi-dimensional carrays as structure members is not supported
	Problem	Sample code for multi-dimensional carrays as structure members is not supported.
	Platform	All platforms
CR010521	To use PowerBuilder (PB) with Active Expert you must set the PB install to use long names
	Problem	Active Expert runtime does not work if you choose the short names option during the PowerBuilder installation.
	Platform	All platforms
	Workaround	To use PowerBuilder with the Active Expert, you must set the PowerBuilder installation to use 32-bit long names. On the Choose Operating System dialog of the PowerBuilder setup program, pick the 32-bit-long names option. This installs 32-bit applications using long directory names, which the Active Expert run time requires.
CR010522	To use VIEW buffers in Active Expert, you must create a struct and element in the Contract Repository
	Problem	Use of VIEW buffers in the Active Expert requires that the appropriate structures and elements are available in the Contract Repository.
	Platform	All platforms
	Workaround	To use VIEW buffers in BEA TUXEDO Builder products, you need to create a structure (struct) in the Contract Repository that represents the VIEW. Then an element must be created with that structure as its type. The Active Expert requires that the name of this type of structure element has to be the same as the VIEW file name. For example: struct name: view5 element name: view5_elm (this is of type view5) VIEW .V file: VIEW view5_elm
CR010523	Active Expert does not distinguish between out and in/out parameters returned only on exception
	Problem	The Contract Repository displays different icons for output and input/output parameters returned only on exception. The Active Expert does not make this distinction; all parameters returned only on exception are displayed as output parameters. The input/output only on exception icon is not used.
	Platform	All platforms
CR010547	BEA recommends using the Active Expert with PowerBuilder 5.0.03
	Problem	Numerous problems exist using the Active Expert with versions of PowerBuilder earlier than version 5.0.03.
	Platform	All platforms
	Workaround	BEA recommends using the Active Expert with PowerBuilder 5.0.03 or above.
CR010562	Cannot delete module in some cases
	Problem	The Active Expert Application Builder is unable to delete a module whose type library has been deleted outside of the Application Builder-this results in an error, and the module will not be deleted.
	Platform	All platforms
	Workaround	Using the Active Expert Application Builder, regenerate the type library, and then delete the module

Rose Expert

Table 12 Rose Expert Change Requests

CR013252	Input acceptance problems for Project Root and Template directory fields in Generate Settings dialog. (No error checking for invalid input.)
	Problem	In the Generate Settings dialog: The Project Root Directory and Template Directory fields accept relative path names (using . or .. ) but the code is generated under the Rational Rose directory rather than under the Rose Expert directories as intended. If you want to use the root directory, the Project Root Directory and Template Directory fields will not accept path names in the format MyDrive: (without the backslash after the colon).
	Platform	All platforms
	Workaround	For the Project Root Directory and Template Directory fields in the Generate Settings dialog: Enter only absolute path names. (Do not use . or .. syntax.) Enter MyDrive:\ if you want to use the root directory.

C++ Expert

Table 13 C++ Expert Change Requests

CR013222	When bringing up client components on UNIX systems, a scrollbar warning is displayed
	Problem	On Solaris and HP-UX platforms, the following warning is generated during startup: The scrollbar page increment is less than 1 This warning does not affect the functioning of the C++ Expert in any way. (On UNIX platforms, this warning is being redirected to the stderr file.)
	Platform	Solaris and HP-UX platforms
	Workaround	This warning does not affect the functioning of the C++ Expert and should be ignored.
CR013677	If the Contract Repository server (IREPSVR) is not running, you cannot successfully log on to the C++ Expert and no alert is given to indicate what the problem is
	Problem	If the IREPSVR is not running, the C++ Expert will not be able to connect to the Contract Repository. No error message is displayed to indicate what the problem is. For the C++ Expert, a clue that the IREPSVR is not running is that the Logon button persists after you click it rather than changing to a Logoff button as it ordinarily would after successful logon. (See also CR013677 in Table 10 and Table 11.)
	Platform	All platforms
	Workaround	Make sure the Contract Repository server (IREPSVR) is running.
CR013723	Incorrect code is generated for operation parameters of type CARRAY
	Problem	CARRAY type is not handled correctly
	Platforms	All platforms
	Workaround	The workaround is to edit the generated code in several files. For details, refer to "Workaround for CR013723 - Modifying Generated Code."

Workaround for CR013723 - Modifying Generated Code

In the C++ Expert, incorrect code is generated for operation parameters of type CARRAY. If you must use CARRAY for binary data, you can modify the generated code by editing a few files.

For a workaround, we assume that a Module named Module1 has an interface named Interface1 in the Contract Repository. Interface1 has an operation named op1() with a parameter param1 of type carray of length of 16 (for our example).

The generated code for the operation op1() is incorrect wherever param1 occurs.

Edit the following files to get the generated code to work.

1. Module1_Interface1.h file

   • Change all occurrences of char param1 to char param1[16]

   • Change all occurrences of char _param1 to char _param1[16]

   • Also, if param1 is a parameter of mode out or inout, then change char Getparam1(); to char* Getparam1();

2. Module1_Interface.cpp file

   • In the op1Reply class default constructor, delete references to _param1 or initialize _param1 using memcpy() or by any other means.

   • In the other constructor for op1Reply, make changes to the signature the same way as described for the Module1_Interface1.h file. Add code to copy the contents of argument param1 to private data member _param1, using memcpy() or by any other means. Also, add code in op1Reply::ExtReply() to extract the value from the FML buffer using SeFget().

   • Change the return type op1Reply::Getparam1() from char to char*

3. Interface1.h file

   Change all occurrences of char param1 to char param1[16]

4. Interface1.cpp file

   Change the signature of op1() to match the changes made in Interface1.h file. Add code in op1() to add the param1 to the FML buffer. Make sure you specify the length in the SeFadd() operation (argument #4 in SeFadd()).

5. Interface1Impl.h file

   Change the signature of op1() to match the changes made in Interface1.h file.

6. Interface1Impl.cpp file

   • Change carray* param1 to char param1[16]

   • Change the signature of op1() to match the changes made in Interface1.h file. Add your application specific code. If using the generated test operation logic code, then make changes for param1 to initialize it with some value.

7. Interface1Skel.cpp file

   • In op1(TPSVCINFO* rqst) code, add definitions for param1 as follows:

     If it is of mode in, then add char param1[16];

     If it is of mode out, then add char* _param1;

     If it is of mode inout, then add char param1[16]; and char* _param1; add SeFget() code to extract from FML buffer if param1 is of in or inout mode.

   • Also, add SeFadd() code to add the value of param1 (if out or inout parameter). Make sure to specify the length in the SeFadd() operation (argument #4 in SeFadd()).

8. Module1_tst file

   • If you use the generated test client, then make similar changes as above to the definitions and initializations of param1.

   • Change carray* param1 to char param1[16]

Configuration Expert

Table 14 Configuration Expert Change Requests

CR012551	On Step 4, in Jolt or Repository tab with JREPSVR or IREPSVR selected, the Repository File path name defaults to an incorrect location.
	Problem	Currently, the Repository File path names default to the misc/ RepositoryFile in the installed TUXEDO directory (TUXDIR). The default location given is correct only for the Repository IREPSVR for Windows NT systems. The other defaults are incorrect.
	Platform	All platforms.
	Workaround	For Jolt JREPSVR for Windows NT systems, the Repository File path name should be: TUXDIR\udataobj\jolt\repository\jrepository For Jolt JREPSVR for UNIX systems, the Repository File path name should be: TUXDIR/udataobj/jrepository For Repository IREPSVR for UNIX systems the Repository File path name should be: TUXDIR/udataobj/irepository
CR013473	On properties dialogs, fields where you specify names (for example, application or group name) accept invalid input
	Problem	Special characters which should be surrounded by "" in the TUXEDO configuration file are still accepted in the text field and "" is not used internally when those characters are entered, which causes a tmloadcf error.
	Platform	All platforms.
	Workaround	Do not use special characters in this field. Use only alphabetical, numeric, or underscore characters, but do not start with a number.
CR013474	In Application Properties dialog, the IPC Key upper limit message information is not correct
	Problem	The upper limit of IPCKEY is 262143 (that is, less than 262144). Currently, the IPC Key field accepts 262144. If you enter a number out of the range, the alert message provides incorrect information. It says "Field 'IPC Key' must be in the range [32769-262144]". According to the BEA TUXEDO Reference Manual (ubbconfig(5) and TM_MIB (T_DOMAIN), 262143 is acceptable, but 262143 still gives the following error from tmloadcf: "CMDTUX_CAT:1670: ERROR: IPCKEY parameter must be > 32768 and 262143".
	Platform	All platforms.
	Workaround	For IPC Key, enter numbers within the range of 32769-262143.
CR013503	Open last application does not work for newly created application
	Problem	You can set an option on the Configuration Expert to "open last application on startup." (Choose Settings->General from the menu bar to see this option.) But this option does not work properly for a new configuration with no modifications. If you create a new configuration but close it without making any changes (no save required in this case), then exit the Configuration Expert, the next time you start the Configuration Expert the new configuration you created will not be displayed (as you would expect). Instead, the configuration you were working on previously is displayed.
	Platform	All platforms.
	Workaround	Use File->Open and choose the file you want.
CR013508	Go menu and keyboard shortcuts to Step 5 (Generate & Startup) do not clear previous step title
	Problem	If you use the Go menu or keyboard shortcuts to navigate to Step 5 (Generate and Startup), you get the correct display (with Application Startup and Command Output labels) but the Step title shown does not update to "Step 5. Generate & Startup" as expected.
	Platform	All platforms.
	Workaround	Use the back and next buttons by the Step titles to navigate to Step 5.

Samples

Table 15 Samples Change Requests

CR013376	The Contract Repository server must be installed to run Rose Expert and C++ Expert samples to avoid a Configuration startup error
	Problem	The Contract Repository server must be installed to run Rose Expert and C++ Expert samples-otherwise, the Contract Repository server fails to start. It is not necessary to bring up the Contract Repository server, but the Contract Repository server is specified in sample ubbconfig file.
	Platform	All platforms.
	Workaround	Either install the Contract Repository server or remove the entry for it in the ubbconfig file.
CR013416	C++ Expert and Rose Expert sample applications are not for Windows 95, but still get installed on that platform
	Problem	The C++ Expert and Rose Expert samples require that you bring up a local server, which is not possible on Windows 95. Also, the code generated for client test logic is native client code.
	Platform	Windows 95 platforms
	Workaround	If you are using a Windows 95 platform, you cannot run the sample applications. Please ignore them.
CR013601	C++ Expert and Rose Expert sample applications will hang if spaces are included between strings in text fields (for example, Open Account dialog address field)
	Problem	In the C++ Expert and Rose Expert samples, the Open Account dialog cannot process input entries that include spaces.
	Platform	All platforms
	Workaround	If you need spaces in the address field, then edit the BANKAPPClient.cpp as follows: Change cin >> (ADDRESS); to gets(ADDRESS);
CR013686	For C++ and Rose Expert samples, the TMS-ORA733 process cannot be started on UNIX due to a missing environment variable in the BANKAPPUnix.env file
	Problem	You cannot run the C++ Expert or Rose Expert sample with the Oracle database using the BANKAPPUnix.env file as shipped.
	Platform	Solaris platforms only
	Workaround	Edit the BANKAPPUnix.env file as follows. Add an entry for LD_LIBRARY_PATH to the BANKAPPUnix.env file. The LD_LIBRARY_PATH entry should include the $TUXDIR/lib, $ORACLE_HOME/lib, and system library directories such as the runtime locations of the libsunmath.so.1 shared library. Typically, this library would be in /opt/SUNWspro/lib.
CR013721	For Active Expert sample, post installation tasks in the Visual Basic Readme.txt file contain some misleading information
	Problem	Step 2 in the post-installation tasks for the Visual Basic Active Expert samples incorrectly suggests you can "drag and drop" the BANKAPP module in the Application Builder after deployment. This is not advisable.
	Platform	All platforms
	Workaround	If you want to drag and drop the BANKAPP module in the Application Builder after deployment, unregister the deployment package first (regsvr32 /u < deploymentpkg.dpy>).

Online Help System

Table 16 Online Help Change Requests

CR011426	Netscape 4.x cannot locate homepage after online help is opened
	Problem	Running the NetHelp system on Windows NT concurrently with other instances of the Netscape Communicator 4.0 browser can result in the Communicator 4.0 browser being unable to locate the home page. The cause of this is that an extra netscape.exe process is running.
	Platform	Windows NT
	Workaround	Either enter a URL or file location manually or terminate the extra netscape.exe process.
CR013428	Screen shot in Online help is only based on Windows platform
	Problem	Most of the Builder dialogs look the same on Windows platforms and UNIX platforms. But some standard dialogs (such as Open File and New File dialogs) look different depending on the platform. All the screens shown in the Online Help are based on the Windows platform.
	Platform	All platforms
	Workaround	None.
CR013463	Sometimes the Help system does not show up
	Problem	Sometimes when you try to bring up the Online Help from a Builder application, the Help window does not open. Often, on the second or third try it will display. If not, use the following workaround.
	Platform	All platforms
	Workaround	If the Online Help fails to open, open the Netscape Communicator 4.x Browser, minimize it, and then try opening the Online Help from the application again.
CR013625	Inconsistent behavior in bringing up context sensitive help on Solaris
	Problem	f the user PATH does not include Netscape, an error "Netscape can't start" is displayed.
	Platform	Solaris platforms only
	Workaround	Make sure the path to the Netscape executable is in your user PATH before you start the Configuration Expert.
CR013655	No alert dialog appears when Help is selected on HP from Configuration Expert
	Problem	The context-sensitive online help is not enabled for HP platforms. When you try to access the help menu from a Builder product on HP, an alert dialog should be displayed which gives the name of the HTML file you can open in a Web browser to read the help as online documentation. In the Configuration Expert, the alert dialog is not enabled.
	Platform	HP platforms only
	Workaround	View the help information as online documentation in a Web browser. For Configuration Expert, open the following file in the browser: < Builder_Install_Dir>/client/doc/ cfghelp.htm/default.htm Note: The documentation files will be available only if you chose the option to install the online help and documentation during the installation procedure. (Also, refer to CR013725 in this table.)
CR013656	Wrong help file is mentioned in an alert dialog when Help is selected on HP from Contract Repository Editor
	Problem	The context-sensitive online help is not enabled for HP platforms. When you try to access the help menu from a Builder product on HP, an alert dialog should be displayed which gives the name of the HTML file you can open in a Web browser to read the help as online documentation. In the Contract Repository Editor, the alert dialog specifies the wrong HTML file.
	Platform	HP platforms only
	Workaround	For the Contract Repository Editor, open the following file in the browser: < Builder_Install_Dir>/client/doc/ crephelp.htm/default.htm Note: The documentation files will be available only if you chose the option to install the online help and documentation during the installation procedure. (Also, refer to CR013725 in this table.)
CR013657	The alert dialog that is displayed when Help is selected on HP from Contract Repository Editor needs to be resized
	Problem	The context-sensitive online help is not enabled for HP platforms. When you try to access the help menu from a Builder product on HP, an alert dialog should be displayed which gives the name of the HTML file you can open in a Web browser to read the help as online documentation. The alert dialog does not show the full text upon initial display. You need to resize it.
	Platform	HP platforms only
	Workaround	Refer to CR013656 and CR013725 in this table.
CR013725	Context-sensitive online help is not available on HP platforms
	Problem	The context-sensitive online help is not enabled for HP platforms. In most cases when you try to access the help menu from a Builder product on HP, an alert dialog is displayed which gives the name of the HTML file you can open in a Web browser to read the help as online documentation.
	Platform	HP platforms only
	Workaround	To view the help information as online documentation on HP systems, open one of the following files in a Web browser: For C++ Expert, < Builder_Install_Dir>/client/doc/ c++help.htm/default.htm For Contract Repository Editor, < Builder_Install_Dir>/client/doc/ crephelp.htm/default.htm For Configuration Expert, < Builder_Install_Dir>/client/doc/ cfghelp.htm/default.htm Note: The documentation files will be available only if you chose the option to install the online help and documentation during the installation procedure.

---

Miscellaneous Notes

The following sections list miscellaneous notes on each product. Issues tracked as change requests (CR) are followed by a CR ID number in parentheses.

All Products

The following notes generally apply to all products:

1. Table 17 lists the client names for Builder products. The client names are assigned internally. You must use these internally-assigned client names for the Builder products if you are setting up or maintaining secure BEA TUXEDO applications which require a client name (for example, with commands such as tpusradd or tpadusr).

   Table 17 Builder Client Names (Use for Secure BEA TUXEDO Applications)

   Product	Client Name
   Contract Repository Editor	Contract Repository Editor
   Active Expert	AppBuilder
   Rose Expert	Rose Bulk Loader
   C++ Expert	C++ Expert

2. For all Builder GUIs except the Active Expert, due to a bug in the Java AWT, the state of the Caps Lock key is checked only when a Java application is started. Pressing the Caps Lock key actually "locks" the keyboard input in lowercase or uppercase depending on conditions (refer to CR013515 for additional information). The problem is registered as Bug #4035364 at JavaSoft. For more information, see:

   http://developer.java.sun.com/developer/bugParade/index.html

Contract Repository

1. The migration utility JMIGRATE does not support migration of VIEWs from the Jolt 1.01 and 1.1 Repositories to the Contract Repository.

2. The Contract Repository database is a formatted text file that can be read with any text editor. We suggest that you do not modify this file with a text editor. Only change the Repository database with the Editor or the Bulk Loader utility.

3. Over time, the Repository database will become filled with change records. To remove these change records from the database, stop and restart the Repository server (IREPSVR). During the server shutdown phase a .BAK file is created with a unique file name based on the date and time of server shutdown. As with BEA TUXEDO ULOG files, it is a good idea to delete the extraneous .BAK files occasionally.

4. The Contract Repository services use FML field ids from 2000 to 2500. Customers should not place application FML field ids in this range.

5. You should only start one instance of the IREPSVR with the write attribute (-w) enabled in your Repository Server BEA TUXEDO configuration.

6. When describing VIEW buffers in the BEA TUXEDO environment, you can have a VIEW element with the same name but different data types in two or more VIEWs. It is not possible to describe these types of VIEWs in the Contract Repository.

7. If you set FIELDTBLS32 with your application FML field tables, you must also include the BEA TUXEDO Builder product related field tables. Add the following to FILEDTBLS32: jrep.f16, jwsladmin.f32, irep.f32

8. Use of the Contract Repository Editor on a monitor at 640x480 resolution is not recommended. The display of some non-resizable dialogs is too large for the screen.

9. The export and unexport functions in the Contract Repository Editor are not currently implemented or enforced by the Active Expert or the C++ Expert. They are present in the Contract Repository Editor for future compatibility with the Jolt product.

10. In the Contract Repository Editor Online Help, the instructions for starting the bulk loader on Windows NT and Windows 95 platforms is incomplete. (For the proper instructions and more detail, refer to CR013448 in Table 10 of these Release Notes.)

Rose Expert

1. On the Generate Settings window, if you choose the option to generate Service Test Logic, then you need to delete the < ControlClass>Impl.cpp file if you change your model and want to regenerate the code for it. The service test logic is contained in a protected code section, so the only way to change it is to delete the file or delete all the lines in the file (including blank lines) in the protected code section. (For more information on the use of protected sections in generated files, refer to the section "Generated Service Implementation" under the API topic in the Rose Expert Online Help.)

2. The C++ compiler and the linker need several patches on HPUX 10.10 to work correctly. You can get the patches from your HP support contact or from the HP Web site.

   Ensure that you have the following patch levels on your system:

   • PHSS_11669

   • PHSS_14732

   • PHSS_15043

   • PHSS_15389

C++ Expert

1. On the Generate Settings window, if you choose the option to generate Service Test Logic, then you need to delete the < ControlClass>Impl.cpp file if you change your model and want to regenerate the code for it. The service test logic is contained in a protected code section, so the only way to change it is to delete the file or delete all the lines in the file (including blank lines) in the protected code section. (For more information on the use of protected sections in generated files, refer to the section "Generated Service Implementation" under the API topic in the C++ Expert Online Help.)

2. In the Online Help, under the topic "Accessing the Contract Repository Objects" in the description of the "Contract Repository Tree View," Table 2-1. Tree Objects includes a discussion of a parameter type called input/output returns only on exception (special case of input/output which only returns a value including when an exception is caught). In the table, this parameter type is designated as "Not in C++ Expert"- this is incorrect. This parameter type is available in the C++ Expert.

3. The C++ compiler and the linker need several patches on HPUX 10.10 to work correctly. You can get the patches from your HP support contact or from the HP Web site.

   Ensure that you have the following patch levels on your system:

   • PHSS_11669

   • PHSS_14732

   • PHSS_15043

   • PHSS_15389

Active Expert

1. When using VIEW buffers in the Active Expert, the Active Expert does not require that you have the VIEW binary files on the workstation using the VIEW buffers.

2. On Windows platforms, certain environment variables must be set in order to run the Active Expert.

   • On Windows 95, the suggested method is to add the WSENVFILE environment variable declaration to the autoexec.bat file. For example, the WSENVFILE entry in your autoexec.bat file should look similar to this:

     SET WSENVFILE=<
     YourPath>\tuxedo.ini

     Note that the equal sign (=) must not be delimited by spaces.

   • On Windows NT platforms, the equivalent method is to set the environment variables using the Control Panel.

Configuration Expert

1. If you modify the servers.lst file either by regenerating it with the C++ Expert or Rose Expert or by editing the file directly, you must close the current configuration and then re-open it to see the latest server list displayed under Step 3 (Configure Servers).

2. In the Files Reference section of the Configuration Expert Online Help, the examples of the iservers.lst and gservers.lst files are misleading because spaces are shown between the entries. If there is a space before or after an entry in the iservers.lst or gservers.lst files (that is, between the commas), the Configuration Expert cannot read the list.

   Do not use spaces between entries in these files iservers.lst or gservers.lst files.

   An example of correct syntax for the gservers.lst file is:

   Account,ACCT,TUXEDO/SQL,N,-A
   Balance,BAL,TUXEDO/SQL,N,-A 
   Teller,TLR,TUXEDO/SQL,N,-A -- -T 100
   Transfer,XFER,TUXEDO/SQL,N,-A

3. Use of the iserver.lst and gserver.lst files needs further explanation.

   In the Files Reference section of the Configuration Expert Online Help, under the topic "Example of the iservers.lst," it says "The only difference is that the Module name will always appear exactly the same as the server name."

   But this only happens when the iserver.lst file is created using the Configuration Expert. If you edit the file manually, you can use a different module name and the Configuration Expert still can read it.

4. When the hierarchical tree for the current configuration is collapsed, you can still add objects to the tree. The object will be added based on which item in the tree is currently selected-but since the tree is collapsed, you will not be able to see where it is being added.

5. On the Machine Properties dialog, Limits tab, information for the Maximum Number of Native Clients and Maximum Number of WS Clients fields is required. You must specify values for these fields.

Active Expert BANKAPP Client Samples

1. Be sure that the BEA TUXEDO application that contains the BANKAPP services has been configured with all services set to AUTOTRAN=Y. The default configuration provided by the setup program has this set properly. If this is not set, the sample application will produce unpredictable results at runtime.

2. The default BANKAPP configuration does not enforce any security. Thus, you do not need to enter any data in the logon dialog to successfully logon.

Online Help and Documentation

1. If you have installed the Online Help and Documentation without any Builder GUI products, use the following instructions to access the Builder documentation:

   • To view the Builder documentation with a Web browser, open the following file in the browser:

     YourDrive:TUXBldr\doc\< YourProduct>help.htm\default.htm (Windows NT)

     < Builder_Install_dir>/client/doc/< YourProduct>help.htm/
default.htm (UNIX)

   • To access PDF versions of the documentation in an Adobe Acrobat Reader:

     YourDrive:TUXBldr\doc\acropdf\< YourProduct>help.pdf (Windows NT)

     < Builder_Install_dir>/client/doc/acropdf/< YourProduct>help.pdf (UNIX)

     Note: If you do not have a reader, you can download one from the Adobe Web site at http://www.adobe.com/

2. Further clarification on the Back, Forward history buttons on the Help window may be needed. (For a fully annotated illustration of the Help window, open the Online Help window. Look for About this Online Help, click on the first topic in that section called "How to Use the Online Help" and scroll to the bottom of the page to display Figure 1. BEA TUXEDO Builder Online Help.)

   Figure 1 Back, Forward Buttons

   

   The Back and Forward buttons at the bottom of the Help window are history buttons that allow you to navigate through previously visited links. However, when you first open the Help window, there is no history of visited links recorded. So, if you click on these buttons when you first open the Online Help, nothing happens-the currently displayed file remains in the window. Only after you take some links by clicking on one of the Help Topics or the Next, Previous buttons (at the top of the display) will you have a history of visited links. Once you have this history, you can navigate the visited links using the Back button (first) and then the Forward button. Note, also, that whenever the currently displayed file is the most recently visited file, the Forward button is not active.

   If you click on the Back and Forward buttons when they are inactive (when there is no history present to go back to or when you are at the most recent file and try to go forward), the cursor changes to a "timer" but nothing happens. Simply move the cursor off of the buttons and it reverts to an active cursor.

3. In the Online Help for some of the products, when you click on topic links other than main headings, the title of the link target is hidden just above the display area. If you scroll up slightly (once the new file is in the display) you will see the appropriate heading, code title, figure title, or table title to which you jumped.

---

Contacting Customer Support

If you have any questions about this version of BEA BEA TUXEDO Builder, or if you have problems installing and running BEA BEA TUXEDO Builder, contact BEA Customer Support through BEA WebSupport at www.beasys.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

• Your name, e-mail address, phone number, and fax number

• Your company name and company address

• Your machine type and authorization codes

• The name and version of the product you are using

• A description of the problem and the content of pertinent error messages

---

---