bea tuxedo builder

BEA TUXEDO BuilderSetup and Installation Guide

B E A T U X E D O B u i l d e r 2 . 1D o c u m e n t E d i t i o n 2 . 1

N o v e m b e r 1 9 9 8

ystems against hole or eadable

ms Clause at FAR

the part

S,

er,

.

Copyright

Copyright © 1997, 1998 BEA Systems, Inc. All Rights Reserved.

Restricted Rights Legend

This software and documentation is subject to and made available only pursuant to the terms of the BEA SLicense Agreement and may be used or copied only in accordance with the terms of that agreement. It isthe law to copy the software except as specifically allowed in the agreement. This document may not, in win part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine rform without prior consent, in writing, from BEA Systems, Inc.

Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA SysteLicense Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clauseDFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASAsupplement 16-52.227-86; or their equivalent.

Information in this document is subject to change without notice and does not represent a commitment on of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THERESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESACCURACY, RELIABILITY, OR OTHERWISE.

Trademarks or Service Marks

BEA, ObjectBroker, TOP END, and TUXEDO are registered trademarks of BEA Systems, Inc. BEA BuildBEA Connect, BEA Manager, BEA MessageQ, Jolt and M3 are trademarks of BEA Systems, Inc.

All other company names may be trademarks of the respective companies with which they are associated

BEA TUXEDO Builder Setup and Installation

Document Edition Part Number Date Software Version

1.0 840-001001-001 December 1997 1.0

2.0 840-001001-003 July 1998 2.0

2.1 840-001001-004 November 1998 2.1

.......1

.....2

...2

.....3

......5

......6

.....7

.....9

..10

....11

...12

..13

...13

.....14

..14

16

....18

...20

....23

...23

.26

....28

..29

....30

....31

....34

...35

Contents

System Requirements .....................................................................................

Windows Installation........................................................................................

Step 1. View Installation Initialization........................................................

Step 2. View Welcome Windows .............................................................

Step 3. Read Installation Requirements ...................................................

Step 4. Accept the License Agreement ....................................................

Step 5. Provide User Information..............................................................

Step 6. Select the BEA Builder Products to Install ...................................

Destination Directory ..........................................................................

Disk Space.........................................................................................

Step 7. Provide License Information.........................................................

License Validation ..............................................................................

Expired License..................................................................................

Step 8. Check the Selected Component Requirement.............................

Active Expert ......................................................................................

C++ Expert or Configuration Expert or Contract Repository Editor....

Rose Expert .......................................................................................

Contract Repository Server ................................................................

Programming Samples ......................................................................

Online Help and Documentation........................................................

JAVA Runtime Environment 1.1.5 Installation...................................

Finish the Select Components Task ..................................................

Step 9. Select the BEA TUXEDO Builder Program Folder ......................

Step 10. Start Copying Files.....................................................................

Step 11. Monitor the Copy Process..........................................................

Step 12. Append the Jolt License.............................................................

Step 13. Acknowledge Successful Installation .........................................

BEA TUXEDO Builder Setup and Installation Guide iii

.

.

Active Expert Run-Time Installation..........................................................36

UNIX Installation..............................................................................................36

Pre-installation Notes for UNIX..................................................................37

Before You Begin.......................................................................................38

Installation Directory Structure...................................................................38

UNIX System Installation Instructions.......................................................43

UNIX System Installation Script.................................................................44

Post-Installation Notes for UNIX................................................................48

Configuring the Contract Repository Servers....................................................50

Configuring the Jolt Servers........................................................................50

Security and Encryption.......................................................................51

Configuring the Jolt Server Listener....................................................51

Starting the Jolt Servers........................................................................57

Shutting Down the Jolt Servers............................................................57

Configuring the Repository Server..............................................................57

*GROUPS Section...............................................................................58

*SERVERS Section.............................................................................59

Repository File.....................................................................................59

Starting the BEA TUXEDO Builder Applications.............................................60

Starting the Active Expert Application Builder..........................................60

Starting the C++ Expert...............................................................................62

Starting the Rose Expert..............................................................................64

Starting the Configuration Expert...............................................................65

Starting the Contract Repository Editor......................................................67

iv BEA TUXEDO Builder Setup and Installation Guide

SETUP AND INSTALLATION

BEA

the

:

Installing BEA TUXEDO Builder

The following chapter takes you through the step by step procedures to install the TUXEDO Builder 2.1 products. This chapter consists of the following sections:

� System Requirements

� Windows Installation

� UNIX Installation

After you have properly installed the Builder products, refer to the section StartingBEA TUXEDO Builder Applications, to start your newly installed products.

For information on any of these products, see the BEA TUXEDO Builder Release Notes.

System Requirements

To run the BEA TUXEDO Builder software, your system must have the following

� At least 32 MB of RAM

� At least 50 to 100 MB of free disk space

� A Pentium 90 (or above) processor for Windows NT or Windows 95 systems

BEA TUXEDO Builder Setup and Installation Guide 1

INSTALLING BEA TUXEDO BUILDER

lick

s as

Windows Installation

The BEA TUXEDO Builder product setup/install program for the Windows platform is located in the win32/setup.exe file on the CD-ROM.

To install the Builder products, insert the CD into the CD-ROM drive and double con the win32/setup.exe file to launch the Builder products installation.

When the installation program launches, follow the prompts shown in the windowdescribed in the following steps.

Step 1. View Installation Initialization

When the installation starts, the preparation information is shown.

Figure 1 Preparing Install Window

2 BEA TUXEDO Builder Setup and Installation Guide

WINDOWS INSTALLATION

n is

Step 2. View Welcome Windows

When the install preparation process has completed, the Welcome splash screedisplayed.

Figure 2 Welcome Splash Screen

Click Next to display the Welcome information.



Figure 3 Welcome Information Window

Click Next to proceed.



hich d to

Step 3. Read Installation Requirements

After the welcome, the pre-installation notes file is displayed. This file describes wcomponents need to be installed together and specifies the environment requiresuccessfully install the BEA TUXEDO Builder products.

Figure 4 Pre-installation Notes Window

To proceed with the installation, exit the Notepad.



Click

Step 4. Accept the License Agreement

When you close the Notepad, the license agreement is displayed.

Figure 5 License Agreement Window

In order to proceed with the installation, you must accept the license agreement. Yes to accept (or click No to cancel the installation process.)



d.

on

Step 5. Provide User Information

After you accept the license agreement, the User Information window is displayeProvide the requested information, and click Next to continue.

Figure 6 User Information Window

When the Registration Confirmation window is displayed, verify that the informatishown is correct.



Figure 7 Registration Confirmation Window

If the information shown is correct, click Yes to proceed (or click No to redisplay the previous screen).



the

ry

, refer

Step 6. Select the BEA Builder Products to Install

The Select Components dialog displays a list of components to be installed.

Figure 8 Select Components Window

Select the components you want to install by clicking on them. (A check mark inbox next to a product indicates that it is selected to be installed.)

Note: Since the Contract Repository Server is not supported on Windows 95 platforms, Windows 95 installations do not include the Contract RepositoServer in the list of components.

For information on dependencies and requirements for each of these componentsto “Step 3. Read Installation Requirements.”



lick

Destination Directory

The path shown for the Destination Directory on the Select Components window isthe location where the Builder products will be installed. The default Destination Directory is YourDrive :\TUXBldr\ as shown in Figure 9.

If you want to install the Builder components in a directory other than the default, con the Browse button to get the file browser. Use the file browser to locate the directory in which you want to install the Builder products and click OK to specify this new path name as the Destination Directory.

Figure 9 Directory Window

If you do change the Destination Directory to something other than the default, youshould see the new path name reflected on the Select Components window.



isk ilable

drive

the 8

Disk Space

The Select Components window also provides information about the disk spacerequired for the currently selected Builder components. (Note that the required dspace changes based on the components you have selected.) To check the avadisk space on another drive, click on Disk Space to get the disk browser. Use the drop-down menu to show available disk space on other disk drives. To reset the used in the Destination Directory path name, choose a new drive and click OK .

If you do change the disk drive, you should see the new drive name reflected asfirst part of the Destination Directory on the Select Component window. (In Figurethe C: drive is specified.)



ken

Step 7. Provide License Information

If the C++ Expert, Rose Expert or Active Expert is selected, the Install License Towindow is displayed. Provide the requested information and then click Next to continue.

Figure 10 Install License Token Window

The installation program checks for the following items.



License Validation

If the license is not valid, the following error message is displayed.

If you get this message, click OK to acknowledge. The Install License Token windowcontinues to be displayed for you to provide a valid serial number and token.

Expired License

If the license has expired, the following error message is displayed.

If you get this message, click OK to acknowledge. The Install License Token windowcontinues to be displayed for you to provide a valid serial number and token.



and

ion

e

Step 8. Check the Selected Component Requirement

Active Expert

In order to run the Active Expert, you must have TUXEDO /WS version 6.3 or 6.4 the Visual Edge Object Bridge version 1.2 installed.

TUXEDO /WS

If you select the Active Expert, the installation program checks if the system hasTUXEDO /WS version 6.3 or 6.4 and the Object Bridge version 1.2.

If the TUXEDO /WS version found is not the correct version, the following error message is displayed.

Click Yes to continue the Builder installation without installing the Active Expert. Click No to cancel the Builder installation until you have installed a supported versof the TUXEDO /WS.

OBJECT BRIDGE

In order to run the Active Expert, you must have the Object Bridge installed. If thObject Bridge is not installed, the following error message is displayed.



g

s.

Click Yes to run the Object Bridge installation and continue with the Builder installation. Click No if you do not want to install the Object Bridge—if you click No, the following error message is displayed.

Click Yes to continue the Builder installation of other components without installinthe Object Bridge or the Active Expert.

When the Object Bridge installation begins, the following screen displays. The TUXEDO Builder installation proceeds after the Object Bridge installation finishe

Figure 11 Object Bridge Deployment Window



he 1.2,

rt

ory be

the with

t the pert

lect If itor

th of

If Object Bridge is found on your system, the following message is displayed. (Tinstallation program is checking to make sure that you have Object Bridge Versionwhich is required by the BEA TUXEDO Builder software.)

Click Yes to cancel the Builder installation until you uninstall the current Object Bridge. Click No if you want to use the existing Object Bridge for the Active Expeand continue with the Builder installation.

C++ Expert or Configuration Expert or Contract Repository Editor

In order to run the C++ Expert, the Configuration Expert or the Contract RepositEditor, the Java Runtime Environment 1.1.5 (JRE 1.1.5) and Jolt client 1.1 must present.

The installation checks if the system has Jolt client 1.1. If Jolt client 1.1 is found onsystem, the installation does not install the zipped Jolt client 1.1 classes shippedBuilder.

If you do not have an existing Java Runtime Environment 1.1.5, be sure to selecJava Runtime Environment 1.1.5 along with the C++ Expert, the Configuration Exor the Contract Repository Editor.

If you have an existing Java Runtime Environment 1.1.5 that you want to use, seonly the C++ Expert, the Configuration Expert or the Contract Repository Editor.you select the C++ Expert, the Configuration Expert or the Contract Repository Edbut do not select an existing JRE 1.1.5, you are prompted to specify the base payour JRE 1.1.5.



rt,

Use the displayed file browser to locate the existing JRE 1.1.5 and click OK .

At this point, the installation program attempts to find the directory <Your_Directory >\bin . If the directory cannot be found, the following error message is displayed.

Click Yes to continue with the Builder installation without installing the C++ Expethe Configuration Expert or the Contract Repository Editor. Click No if you want to cancel the installation until you have installed JRE 1.1.5.



eady s.

n onal

) and

Rose Expert

In order to run the Rose Expert, you must have Rational Rose installed.

If you select Rose Expert, the installation program checks to see if the system alrhas Rational Rose. If Rational Rose is not installed, the following screen appear

If both Rational Rose 98 and Rational Rose 4.0 are installed on your system, theinstallation program detects this and provides the following screen where you cachoose which Rose Expert you want to install (depending on which version of RatiRose you want to use with the BEA Rose Expert plug-in).

In order to run the Rose Expert, the Java Runtime Environment 1.1.5 (JRE 1.1.5Jolt client 1.1 must be present.



the with

t the

lect 1.1.5,

rt.

The installation checks if the system has Jolt client 1.1. If Jolt client 1.1 is found onsystem, the installation does not install the zipped Jolt client 1.1 classes shippedBuilder.

If you do not have an existing Java Runtime Environment 1.1.5, be sure to selecJava Runtime Environment 1.1.5 along with the Rose Expert.

If you have an existing Java Runtime Environment 1.1.5 that you want to use, seonly the Rose Expert. When you select the Rose Expert but do not select the JREyou are prompted to specify the base path of your JRE 1.1.5.

Use the displayed file browser to locate the existing JRE 1.1.5 and click OK . (Make sure that the directory you specify includes a \bin directory.)

At this point, the installation program attempts to find the directory <Your_Directory >\bin . If the directory cannot be found, the following error message is displayed.

Click Yes to continue with the Builder installation without installing the Rose ExpeClick No if you want to cancel the installation until you have installed JRE 1.1.5.



ake are in

e is

am,

erver r.

Contract Repository Server

The Contract Repository Server option is displayed only on Windows NT 4.0 platforms because the Windows 95 workstation cannot act as a server.

If you select the Contract Repository Server, the installation program checks to msure TUXEDO version 6.3 or 6.4 is present and the required server components place.

If the TUXEDO server components cannot be found, the following error messagdisplayed.

Click Yes to continue the Builder installation without installing the Contract Repository servers. Click No if you want to cancel the installation until you have installed the TUXEDO system.

If the installation finds TUXEDO 6.3 or 6.4, the Contract Repository server progrand the associated files, are installed underneath the TUXEDO directory.

The installation also checks if the Jolt server 1.1 is present on the system. If Jolt s1.1 is found, the installation will not install the Jolt 1.1 server shipped with Builde

The installation program also collects the following information in generating thesample TUXEDO UBBCONFIG file (ubbsample.txt ) for the Contract Repository Server.

Note: You can get the ubbsample.txt file from the location YourDrive :\TUXBldr\RepServer .



and

he

Figure 12 Edit Data Window

Provide the machine name, JSL and WSL Port number in the Edit Data window click Next to proceed.

The Confirm Information window displays the information you have provided for tmachine name, JSL and WSL Port numbers.



Figure 13 Confirm Information Window

If the machine name, JSL and WSL Port numbers are correct, click Next to proceed. Otherwise, click Back to display previous windows where you can re-enter the information.



e of e it

ents e

g

ive r and

n dify

Programming Samples

If you choose to install the Programming Samples, you need to install at least onthe following components: Active Expert, C+ Expert, Rose Expert (or already havon your system).

If you select to install the Programming Samples but none of the Builder componare already present on your system or have not been selected to be installed, thfollowing window is displayed.

Click Yes to continue with the Builder installation without installing the ProgramminSamples. Click No to cancel the installation and begin again by installing Active Expert, C+ Expert, Rose Expert along with the Programming Samples.

Online Help and Documentation

We recommend that you install the Online Help and Documentation with the ActExpert, C+ Expert, Rose Expert, Configuration Expert, Contract Repository Editoapplications. If you select any of these applications but do not select Online HelpDocumentation, the following message is displayed.

If you get this message, click OK to acknowledge. (Then if needed, you can click oBack on the Install License Token window to redisplay the previous screen and moyour choices on the Select Components window shown in Figure 8.)



ut

rt, t the

ns of the

ot way,

etup the

You also have the option of installing the Online Help and Documentation without any Builder GUI products. For information on how to access the documentation withousing context-sensitive GUI help, refer to the Release Notes (item 1. under “Miscellaneous Notes” for Online Help and Documentation).

If you choose to install the Online Help and Documentation with the Active ExpeC++ Expert, Rose Expert, and/or the Contract Repository Editor, keep in mind thacontext-sensitive online help system associated with the product graphical user interfaces (GUIs) requires Netscape Navigator 4.0 or above.

Note: The Online Help system was tested with Netscape Navigator 4.05.

The installation checks to ensure that your system has one of the required versioNetscape Navigator installed. If an appropriate Netscape Navigator is not found,following message is displayed.

Click Yes to begin the installation of Netscape Navigator 4.05 or click No to proceed with the Builder installation without installing the Netscape Navigator. (If you do nhave the appropriate browser, but install the Online Help and Documentation anyyou will at least have access to the PDF versions of the documentation when theinstallation process is complete.)

At the start of the Netscape Navigator installation, the Netscape Navigator 4.05 Swindow is displayed. To install the Netscape Navigator, follow the instructions onNetscape Navigator 4.05 Setup window.



plete.
The Builder installation proceeds after the Netscape Navigator 4.05 Setup is com
Figure 14 Netscape Navigator Setup Window



e

.

JAVA Runtime Environment 1.1.5 Installation

If you select the Java Runtime Environment 1.1.5 from the installation options, thfollowing screen is displayed.

Figure 15 Java Runtime Environment Installation Window

In order to proceed with the installation, you must accept the license agreement

The following licensing agreement window appears.



files n the

Figure 16 Java Runtime Environment Licensing Agreement

Click Yes to accept. (Otherwise, click No to cancel the installation.)

Select the components you want to install, and the directory where you want theto be located. If you want to set the destination directory to somewhere other thadefault destination directory, select the new directory now.



duct

nd must

Figure 17 Java Runtime Environment Components Window

Select the component you want to install. (A check mark in the box next to a proindicates that it is selected to be installed.) The default component selected is Program Files.

Click Next to select the chosen components (Otherwise, click Cancel to cancel the installation.). The installation program will begin copying files to the specified directory.

Finish the Select Components Task

After you have selected the BEA TUXEDO Builder products you want to install averified that you have the components required for a successful installation, you select your TUXEDO Builder program folder.



y er

Step 9. Select the BEA TUXEDO Builder Program Folder

The BEA TUXEDO Builder program folder window gives you the option to specifthe name and location of the folder that will contain the newly installed BEA Buildproducts. (The default program folder is BEA TUXEDO Builder 2.1.)

Figure 18 Select Program Folder Window

When the appropriate folder is selected, click Next to proceed.



es and

g

Step 10. Start Copying Files

Just before the selected components are actually installed, the Start Copying Filwindow is displayed. This window shows a summary of the components selectedinstallation options chosen.

Figure 19 Start Copying Files Window

If the displayed summary is correct, click Next to proceed with the installation.

Before the setup program starts copying mfc42.dll to the WINSYS directory, the installation checks to see if this file is already present on the system. If an existinmfc42.dll is found on the system, the date is compared with that of the mfc42.dll on the CD-ROM.



is file

tarts nt

O

.0

Note: The figure shows the message displayed if the file found on your systemolder than the one to be installed. A different message is displayed if the found is newer than the one to be installed.

Click Yes to create a backup copy of the existing file and install the mfc42.dll from the CD-ROM. Click No to use the mfc42.dll that is already on your system.

If you choose to install the Contract Repository Server before the setup program scopying irepostitory file, the installation checks to see if this file is already preseunder misc in your TUXEDO directory. If an existing irepository file is found, the following message is displayed.

Click Yes to create a backup copy of the existing file and install the irepository file from the CD-ROM. Click No to use the file that is already on your system.

Note: We recommend that you make a backup copy when installing the TUXEDBuilder 2.1 product over TUXEDO Builder 1.0. This is in case you want toconvert your TUXEDO Builder 1.0 Contract Repository to the TUXEDO 2release.

Step 11. Monitor the Copy Process

While the files are being copied to the target system, a Setup status window is displayed to keep you informed of the progress of the installation.

While the copy is in progress, you do have an option to cancel the installation.



em. ion

Figure 20 The Setup Status Window

If you selected to install the Configuration Expert, the installation script asks youwhether you want to collect data for the Configuration Expert. This default Configuration Data file is called the ConfigExpert.dat . For each machine added, aset of default template resource managers is added.

The following screen appears.

Figure 21 The Configuration Expert Setup Window

Click Yes to collect information about the machines that are located on your systClick No if you want to set up this information at another time using the ConfiguratData Editor. If you click on Yes, an information dialog appears. Click OK to bring up the Configuration Data Editor as shown in Figure 22.



d the ain

ht

tion

n.

Figure 22 Configuration Data Editor Main Window

The machines available in the Configuration Data file appear in the left panel, anattributes that you want to modify appear in the fields in the right portion of the mwindow screen.

If there are no machine listed in the left panel, you must fill in the fields on the rigpanel, and select Add.

On Windows 95, a DOS command prompt window appears behind the ConfiguraData Editor main window. After clicking on the OK or Cancel button, you need to close the DOS command prompt window to proceed with your Builder installatio



LT

Step 12. Append the Jolt License

If you select the Contract Repository Server to install, and you do not have a JOlicense, you must append the contents of the lic-builder.txt file to lic.txt . The following window appears.

Figure 23 Jolt Append Window

Click OK to acknowledge you have a JOLT license.



etup


Step 13. Acknowledge Successful Installation

After the files have been successfully copied to the destination directories, the SComplete window is displayed.

Figure 24 Setup Complete Window

Before you can begin work with Builder products, you need to perform the post-installation tasks in the ReadMe file.

To view the ReadMe file at this time, select the check box Yes I want to view the ReadMe file now, and click Finish.

If this is unchecked, you can view the ReadMe file in the Builder install directory at a later time.


me

lled.

sed

X

Active Expert Run-Time Installation

When deploying a client application written using the Active Expert, certain run-ticomponents must be installed on the client. A separate Active Expert run-time installation program called axsetup.exe is provided for this purpose. You can find the file axsetup.exe in the ActiveExpert directory. (You can also get this file fromthe Builder CD.)

Run the axsetup.exe file in the same way as any setup program. Note that axsetup.exe does not need to be run every time a new client application is insta

UNIX Installation

This section includes the following topics:

� Pre-installation Notes for UNIX

� Before You Begin

� Installation Directory Structure

� UNIX System Installation Instructions

� UNIX System Installation Script

� Post-Installation Notes for UNIX

Your CD-ROM contains all of the necessary files for installing and running the TUXEDO Builder Contract Repository (including the Jolt 1.1 component). The CD-ROM contains an installation script for UNIX systems and a separate GUI-bainstaller for Windows NT users. To install the Contract Repository (including the Jolt 1.1 component), follow the instructions for your respective platform.

Note: For installation of these products you need CD-ROM access and approximately 16 Megabytes (MB) of disk storage if you select “all” for UNIinstallation.


UNIX INSTALLATION

s

u

Pre-installation Notes for UNIX

These pre-installation notes are also included in the BEA TUXEDO Builder Release Notes.

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 appearsas “readme. ” on HP-UX systems and the installation will fail if it cannot find thifile. 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 reference page on mount_cdfs .

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 requireaccess to the Java Runtime Environment (JRE) in order to run. (Refer to the section “Supported Platforms” in the BEA TUXEDO Builder Release Notes for information on which versions of the JRE are supported for each product.) Yomust have an existing Java Runtime Environment on your workstation.



te

Before You Begin

Note: These requirements are for the “server” and “all” options only. If you choose a different option other than “server” and “all”, you can install the Builder products anywhere.

Before installing:

� You need to either own the directory where TUXEDO is installed, or have wripermission to that directory.

� You need to know the location of the TUXEDO directory where the Jolt 1.1 component is going to be installed. The installation script will prompt you for this location.

Installation Directory Structure

The following listing shows the directory structure for UNIX.

Listing 1 TUXEDO Builder UNIX Installation Directory Structure

.:

alpha hp install.sh sgi win32

alphant ibm sco sun5x

./alpha:

dux40

./alpha/dux40:

6.3 6.4

./alpha/dux40/6.3:

bldr readme

./alpha/dux40/6.3/bldr:

bldrsvr.Z copyright pkginfo space suminfo


UNIX INSTALLATION

./alpha/dux40/6.4:

bldr readme

./alpha/dux40/6.4/bldr:


./alphant:

SETUP.INS _INST32A.EX_ commdsk1.z setup.dbg setup.pkg

Uninst.Exe _setup.dll resvrdsk163.z setup.exe

Versions.txt _setup.lib resvrdsk164.z setup.ini

./hp:

hp1010 hp1020 hp11

./hp/hp1010:

6.3 6.4

./hp/hp1010/6.3:

bldr readme

./hp/hp1010/6.3/bldr:


./hp/hp1010/6.4:

bldr readme

./hp/hp1010/6.4/bldr:


./hp/hp1020:

6.3 6.4

./hp/hp1020/6.3:

bldr readme

./hp/hp1020/6.3/bldr:



bldrall.Z bldrcpp.Z bldredi.Z copyright space

bldrcon.Z bldrdoc.Z bldrsvr.Z pkginfo suminfo

./hp/hp1020/6.4:

bldr readme

./hp/hp1020/6.4/bldr:



./hp/hp11:

6.4

./hp/hp11/6.4:

bldr readme

./hp/hp11/6.4/bldr:



./ibm:

aix421

./ibm/aix421:

6.3 6.4

./ibm/aix421/6.3:

bldr readme

./ibm/aix421/6.3/bldr:


./ibm/aix421/6.4:

bldr readme

./ibm/aix421/6.4/bldr:


UNIX INSTALLATION


./sco:

insco32

./sco/insco32:

6.3 6.4

./sco/insco32/6.3:

bldr readme

./sco/insco32/6.3/bldr:


./sco/insco32/6.4:

bldr readme

./sco/insco32/6.4/bldr:


./sgi:

mpirx62

./sgi/mpirx62:

6.3 6.4

./sgi/mpirx62/6.3:

bldr readme

./sgi/mpirx62/6.3/bldr:


./sgi/mpirx62/6.4:

bldr readme

./sgi/mpirx62/6.4/bldr:




./sun5x:

sol251 sol26

./sun5x/sol251:

6.3 6.4

./sun5x/sol251/6.3:

bldr readme

./sun5x/sol251/6.3/bldr:



./sun5x/sol251/6.4:

bldr readme




./sun5x/sol26:

6.4

./sun5x/sol26/6.4:

bldr readme





UNIX INSTALLATION

ary

lled.

he

ibed

UNIX System Installation Instructions

The BEA TUXEDO Builder installation shell script allows you to install all components necessary for the Contract Repository system (including the necessJolt 1.1 components).

When installing, ensure that all necessary hardware and software has been instaSee the “Supported Platforms” section in the BEA TUXEDO Builder Release Notes for information about the hardware and software requirements.

1. Log in as a user who has write permission in the TUXEDO directory.

(Only applicable if you are installing using the server or all option.)

2. Insert the CD-ROM in the CD-ROM drive. If you are running on Solaris and tdaemon /usr/sbin/vold is running, the CD-ROM should be automatically mounted in the /cdrom directory. Type:

cd /cdrom

If you are not running on Solaris or vold is not running, consult your UNIX administration documentation to mount the CD-ROM.

3. Type ls

The directory contents should look similar to the sample below. If not, verify that you are installing the correct CD-ROM.

hp install.sh sun5x win32

Type

sh ./install.sh

4. Press Enter.

This invokes the installation script. The step-by-step install screens are descrin the following section.



help ing the g

re

UNIX System Installation Script

The UNIX system installation script provides a set of step-by-step instructions to you quickly install your product. This script lets you specify your platform, operatsystem, and other installation details. The installation script prompts you throughentire installation process. You can cancel the installation at any time by pressinCTRL-C simultaneously.

1. Type the number that corresponds to the name of the operating system you ausing (for example, if using Sparc Solaris 2.5.1, type 15). Press Enter.

01) alpha/dux40/6.3 02) alpha/dux40/6.4 03) hp/hp1010/6.3

04) hp/hp1010/6.4 05) hp/hp1020/6.3 06) hp/hp1020/6.4

07) hp/hp11/6.4 08) ibm/aix421/6.3 09) ibm/aix421/6.4

10) sco/insco32/6.3 11) sco/insco32/6.4 12) sgi/mpirx62/6.3

13) sgi/mpirx62/6.4 14) sun5x/sol251/6.3 15) sun5x/sol251/6.4

16) sun5x/sol26/6.4

Install which platform's files? [01-16, q to quit, l for list]: 15

Note: In this example, we chose 15) sun5x/sol251/6.4

2. You are prompted to confirm your choice. If correct, type y for “yes,” or n for “no” or q to “quit.” Press Enter.

** You have chosen to install from sun5x/sol251/6.4 **

BEA Builder Release 2.1

This directory contains the BEA Builder System for

Solaris 2.5.1 on SPARC

Is this correct? [y,n,q]: y


UNIX INSTALLATION

L

e

3. Type y for “yes”, to install the package. Press Enter.

To terminate the installation at any time

press the interrupt key,

typically <del>, <break>, or <ctrl+c>.

The following packages are available:

1 bldr BEA Builder Repository Server

Select the package(s) you wish to install (or 'all' to install

all packages) (default: all) [?,??,q]: 1

BEA Builder Repository Server

(sparc) Release 2.1

Copyright (c) 1998 BEA Systems, Inc.

Portions * Copyright 1986-1997 RSA Data Security, Inc.

All Rights Reserved.

Distributed under license by BEA Systems, Inc.

TUXEDO is a registered trademark.

BEA Jolt is a trademark of BEA Systems, Inc.

4. Type the number of the installation option you prefer. The Jolt 1.1 JSH and JScomponents are installed in an existing TUXEDO directory. You must install TUXEDO prior to this installation.

Note: The following example is shown choosing the “all” option. If you select another option, you may not be asked some of the questions shown in thexample.

For HP10.10/6.3 and 6.4, you will only be able to install options 1 and 2.

The following installation options are available:

1 all Install the full BEA Builder System

2 server Install server only

3 cpp Install CPPExpert only

4 config Install ConfigExpert only

5 editor Install Editor only

6 doc Install documentation only

Select an option (default: all) [?,??,q]: 1



Note that the server will be installed into an existing

TUXEDO directory. You MUST have previously installed TUXEDO

version 6.3 or 6.4 to attempt this installation.

Base directory of existing TUXEDO installation [?,q]:

/home/kwiseman/tux/6.4

Determining if sufficient space is available ...

30330 blocks are required

1423072 blocks are available to /home/kwiseman/tux/6.4

Using /home/kwiseman/tux/6.4 as the TUXEDO base directory

Please specify the location of the Java Runtime Environment or

the JDK

Enter a pathname (default: /usr/jrehome) [?,q]:

/home/zhang/jdk/jdk1.1.5

Using /home/zhang/jdk/jdk1.1.5 as the location.

Please specify the location of Netscape

NETSCAPEDIR (default: /usr/netscape) [?,q]:

Using /usr/netscape as the location

Please enter your Builder License Serial # and Token:

Serial number [?,q]: 1234567890

License token [?,q]: 1234567890123456

Unloading

/net/build/bldr/b20v8/CDIMAGE/sun5x/sol251/6.4/bldr/bldrall.Z

...

bin/IREPSVR

bin/repimport

bin/jmigrate

bin/bldr_upgrade

bin/JSL


UNIX INSTALLATION

ta

bin/JSH

udataobj/irep.f32

udataobj/jrep.f16

udataobj/jwsladmin.f32

udataobj/lic-builder.txt

udataobj/irepository

udataobj/irep.env

udataobj/ubbirep

udataobj/bldr/client/samples/CPPExpert/NoDB/BANKAPP/AccountFact

ory.cpp

...

61000 blocks

... finished

NOTE: If you don't already have a JOLT license, APPEND the

contents of

'/home/kwiseman/tux/6.4/udataobj/lic-builder.txt'

to:

'/home/kwiseman/tux/6.4/udataobj/lic.txt'.

Config Expert: processsing...

Would you like to run the Config Expert to enter machine

information now? You can always run it after installation by

executing the command

/home/kwiseman/tux/6.4/udataobj/bldr/client/ConfigExpert/bin/Co

nfigEditor

5. For more information on entering machine information, see Configuration DaEditor Main Window, or see BEA TUXEDO Builder Configuration Online Help Version 2.1.

Do you want to run ConfigEditor now? [y,n]: n

Config Expert: done.

CR Editor: processsing...



CR Editor: done.

CPP Expert: processsing...

CPP Expert: done.

6. The script continues with the installation process until the status message, “Installation of BEA Builder Repository Server was successful” displays.

Changing file permissions...

... finished

Installation of BEA Builder was successful

7. The script returns to the installation prompt. Type q to quit.

The following packages are available:

1 bldr BEA Builder

Select the package(s) you wish to install (or 'all' to install

all packages) (default: all) [?,??,q]:

The installation is now complete. The following section provides information on post-installation issues.

Post-Installation Notes for UNIX

These post-installation notes are also included in the BEA TUXEDO Builder Release Notes.

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.1 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.1 release


UNIX INSTALLATION

O

the

t

for e of

).

s

n or

2. After installing the Contract Repository server, you must set up a BEA TUXEDserver configuration to run the Contract Repository server (IREPSVR), Jolt (JSL), and /WS (WSL). Also, if you want sample applications, you must haveBANKAPP servers in this configuration. On Windows NT, the sample files to help you setup 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.) On UNIX, the sample files to help you setup this configurationcan 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 “Configuring the ContracRepository Servers.”

3. Note that if you would like to do both C++ Expert and Jolt client development the same BEA TUXEDO application, you must configure your BEA TUXEDOdevelopment server environment to run separate BEA TUXEDO domains foreach client development. The reason you must do this is because the instancJolt 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 requirethat BEA TUXEDO server software be installed.

5. If the C++ Expert was previously installed on this machine and a reinstallatioa 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. Thisensures 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.



ing

Configuring the Contract Repository Servers

This section explains how to configure the Contract Repository Servers. The followtopics are included:

� Configuring the Jolt Servers

� Configuring the Repository Server

Configuring the Jolt Servers

The Jolt servers are:

� Jolt Server Listener (JSL). The JSL is configured to support clients on an IP/port combination. The JSL works with the Jolt Server Handler (JSH) to provide client connectivity to the backend of the Jolt system. The JSL is administered by the same tools used to manage any resource within a BEA TUXEDO environment.

� Jolt Server Handler (JSH). The JSH is a program that runs on a TUXEDO server machine to provide a network connection point for remote clients. TheJSH works with the JSL to provide client connectivity residing on the backendof the Jolt system.

The system administrator’s responsibilities for the server components include:

� Determining server network addresses.

� Determining the number of clients to be serviced by one JSH (for example, ifthere are 10 clients per JSH and 10 JSHs, 100 clients can be connected).

� Determining the minimum and maximum number of JSHs.


CONFIGURING THE CONTRACT REPOSITORY SERVERS

nd the s are

tes nets ernal

, and t DES a. The the

t

Security and Encryption

Authentication and key exchange data that are transmitted between Jolt clients aJSL/JSH are encrypted using DES (56-bit) encryption. All subsequent exchangeencrypted using RC4 encryption. International packages use 40-bit key.

Programs using the 56/128-bit encryption cannot be used outside the United Stawithout proper approval from the United States government. Customers with intraextending beyond the United States cannot use this mode of encryption if any intclients are outside of the United States.

The 128-bit version generates a 128-bit RC4 session encryption key at logon timethis session key is transmitted over the network in a message protected by 56-biencryption. The temporary session key is then used to encrypt the session's datoverall security level achieved is equivalent to 56-bit DES encryption, even thoughdata encryption is using a 128-bit key.

Configuring the Jolt Server Listener

The Jolt Server Listener (JSL) is a TUXEDO server responsible for distributing connection requests from the system to the JSH. TUXEDO must be running on the hosmachine where the JSL and IREPSVR is located.

To configure the JSL, you must modify the UBBCONFIG file. For information regarding TUXEDO configuration, refer to the TUXEDO Administration Guide. Listing 2 shows relevant portions of the UBBCONFIG file.

Listing 2 UBBCONFIG File

*MACHINES

MACH1 LMID=SITE1

MAXWSCLIENTS=40

*GROUPS

JSLGRP GRPNO=95 LMID=SITE1

*SERVERS

JSL SRVGRP=JSLGRP SRVID=30 CLOPT= “ -- -n // machinename : port# -d

/dev/tcp -m2 -M4 -x10”

Change the following sections of the UBBCONFIG file.



ted for .

or all

,

f 200 l

.

The parameters shown in Table 1 are the only parameters that should be designathe server groups and servers. You do not need to specify any other parameters

Note: Ensure that Resource Managers are not assigned as a DEFAULT value fgroups in the *GROUPS section of your UBBCONFIG file. This will assign a Resource Manager to the JSL and you will receive an error during tmboot . In the *SERVERS section, DEFAULT values for RESTART, MAXGEN, etc.are acceptable defaults for the JSL.

*MACHINES SECTION

The MAXWSCLIENTS parameter is required in the *MACHINES section of the configuration file and applies to specific machines. The Jolt server and /WS use MAXWSCLIENTS in the same way. MAXWSCLIENTS communicates the number of accesser slots to reserve for the Jolt and /WS clients to TUXEDO. For example, islots are configured for MAXWSCLIENTS, this number configures TUXEDO for the totanumber of remote clients used by Jolt and the /WS.

Specify MAXWSCLIENTS in the configuration file. If it is not specified, the default is 0

Listing 3 shows the MACHINES section of a UBBCONFIG file for a machine called SERVERMACHINE.

Listing 3 UBBCONFIG File

" SERVERMACHINE" LMID=SITE1 TUXDIR="/home/tuxedo" APPDIR="/home/tuxedo/apps/bankapp" ENVFILE="/home/tuxedo/apps/bankapp/envfile" TLOGDEVICE="/home/tuxedo/apps/bankapp/TLOG" CLOPT="-e tmusrevt.out -o tmusrevt.out -A -- -f /usr/tuxedo/bankapp/tmusrevt.dat" SEQUENCE=11

Table 1 UBBCONFIG File Sections

Section Parameters to be specified

*MACHINE MAXWSCLIENTS

*GROUPS LMID, GRPNO

*SERVERS SRVGRP, SRVID, CLOPT



e

he

ior

r

Required FML Field Tables. The ENVFILE specifies environment variables for thTUXEDO system. Jolt requires that the following files be referenced in the environment:

� jrep.f16

� jwsladmin.f32

� irep.f32

As shown in Listing 4, the required files are defined in the FIELDTBLS variable. TFLDTBLDIR specifies the directories in which to search for these files. The jrep.f16 , jwsladmin.f32 , and irep.f32 files are found in the udataobj directory.

Listing 4 FIELDTBLS Variable in the envfile File

FIELDTBLS=Usysflds,bank.flds,credit.flds,event.flds,jrep.f16,jwsladmin.f32,irep

.f32

FLDTBLDIR=/home/tuxedo/udataobj:/home/tuxedo/apps/bankapp

VIEWDIR=/home/tuxedo/apps/bankapp

VIEWFILES=aud.V

If ENVFILE="/home/tuxedo/apps/bankapp/envfile" is included in the definition of the UBBCONFIG file (shown in Listing 3), the FIELDTBLS and FLDTBLDIR definitions are taken from the envfile file and not from your environment variable settings.

If you remove the ENVFILE="envfile" definition, the FIELDTBLS and FLDTBLDIR definitions are taken from your environment variable settings. The FIELDTBLS and FLDTBLDIR definitions must be set to the appropriate value prbooting TUXEDO.

*GROUPS SECTION

A *GROUPS entry is required for the group that includes the Jolt Server Listene(JSL). The group name is selected by the application.

1. Specify the same identifiers given as the value of the LMID parameter in the *MACHINES section.

2. Specify the value of the GRPNO between 1 and 30,000 in the *GROUPS section.



rough ingle ress

ions ing

the by the at the re a

d 8003.

eric use t

iple

d

ue

*SERVERS SECTION

Clients connect to the Jolt applications through the JSL. Services are accessed ththe Jolt Server Handler (JSH). The JSL supports multiple clients and acts as a spoint of contact for all the clients to connect to the application at the network addthat is specified on the JSL command line. The JSL schedules work for handler processes. A handler process acts as a substitute for clients on remote workstatwithin the administrative domain of the application. The handler uses a multiplexscheme to support the multiple clients concurrently.

The network address specified for the JSL designates a TCP/IP address for bothJSL and any JSH processes associated with that JSL. The port number identified network address specifies the port number on which the JSL accepts new clientconnections. Each JSH associated with the JSL uses consecutive port numberssame TCP/IP address. For example, if the initial port number is 8000 and there amaximum of three JSH processes, the JSH processes use ports 8001, 8002, an

Note: Port numbers used by the JSHs are sequentially incremented by one numdigit after the JSL port number. If JSL is using port number 8000, its JSHs8001, and so on. Misconfiguration of the subsequent JSL results in a pornumber collision.

Each handler uses a multiplexing scheme on its designated port to support multclients concurrently on one port.

TUXEDO parameters including RESTART, RQADDR, and REPLYQ can be usewith the JSL. See the TUXEDO Administration Guide for additional information regarding run-time parameters. Enter the following parameters:

1. To identify the SRVGRP parameter, type the previously defined group name valfrom the *GROUPS section.

2. To indicate the SRVID, type a number between 1 and 30,000 that identifies the server within its group.

3. Verify that the syntax for the CLOPT parameter is as follows:

CLOPT= “-- -n // machinename : port# -d /dev/tcp -m2 -M4 -x10”

Note: The CLOPT parameters may vary. Refer to Table 2 for pertinent command-line information.



r

4. If necessary, type the optional parameters:

� Type the SEQUENCE parameter to determine the order that the servers are booted.

� Specify Y to permit release of the RESTART parameter.

� Type 0 to permit an infinite number of server restarts using the GRACE parameter.

Table 2 Command-Line Options

Command-Line Option Description

[-c connection_mode ] Allowed connection modes from clients:

RETAINED - the network connection is retained for the full duration of a session.

RECONNECT - the client establishes and brings down a connection when an idle timeout is reached, reconnecting fomultiple requests within a session.

ANY - the server allows a client to request either a RETAINED or RECONNECT type of connection for a session. Default is ANY. (Optional)

[-d device_name] The device for platforms using the Transport Layer Interface. There is no default. (Required; optional for sockets)

[-I init-timeout ] The time (in seconds) that a client is allowed to complete initialization through the JSH before it is timed out by the JSL. Default is 60 seconds. (Optional)

[ -m minh ] The minimum number of JSHs that are available in conjunction with the JSL at one time. The range of this parameter is between 0 and 255. Default is 0. (Optional)

[-M maxh] The maximum number of JSHs that are available in conjunction with the JSL at one time. The range of this parameter is between 1 and 4096. If this option is not specified, the parameter defaults to MAXWSCLIENTS divided by the rounded-up -x multiplexing factor. (Optional)



e

s

s

a

-n netaddr Indicate the network address where the clients connect to thJSL. This is a required parameter and is the contact point used by Java workstation clients to access the application.

The port number identified by the network address specifiethe port number on which the JSL accepts new client connections. Each JSH associated with the JSL uses consecutive port numbers at the same TCP/IP address.

The network address is composed of 1) an initial two digitsindicating hexadecimal characters, followed by three groupof numbers indicating 2) protocol, 3) port number, and 4) IPaddress.

For example: // machinename : port#

There is no default. (Required)

[-T Client-timeout ] The time (in minutes) allowed for a client to stay idle. If a client does not make any requests during this time, the JSHdisconnects the client and the session is terminated. If an argument is not supplied, the session does not timeout.

When the -c ANY or -c RECONNECT option is used, always specify -T with an idle timeout value. If -T is not specified and the connection is suspended, JSH does not automatically terminate the session. The session never terminates if a client abnormally ends the session.

If a parameter is not specified, the default is no timeout. (Optional)

[-w JSH] The Jolt Server Handler is indicated by this command-line option. Default is JSH. (Optional)

[-x mpx-factor ] A parameter used to control the degree of multiplexing within each JSH process. This is the number of clients that one JSH can service. Default value is 10. (Optional)

[-Z 40|128] When establishing a network link between a client and theJSH, allow encryption up to the 40|128 level. 40 and 56/128 specify the length (in bits) of the encryption key. Thelength, 128, is synonymous with 56/128-bit encryption. Thedefault value is 0.

Table 2 Command-Line Options

Command-Line Option Description



ee

n

ting

s

e is

nts

w

nt

Starting the Jolt Servers

Using the command tmloadcf , create a binary TUXCONFIG file from the UBB configuration file. Type tmboot -y to start all administrative and server processes. Sthe TUXEDO Administration Guide for information on tmloadcf and tmboot .

Note that TUXEDO monitors the JSL and restarts it in the event of a failure. WheTUXEDO restarts the listener process, the following occurs:

� Clients attempting a listener connection must try to reconnect. Clients attempa handler connection receive a timeout or a time delay.

� Clients currently connected to a handler are disconnected (JSH exits when itcorresponding JSL exits).

Shutting Down the Jolt Servers

All shutdown requests to the servers are initiated by the TUXEDO command, tmshutdown -y . During shutdown:

� No new client connections are accepted.

� All current client connections are terminated. TUXEDO will rollback in-flight transactions. Each client receives an error message indicating that the servicunavailable.

Configuring the Repository Server

The Contract Repository contains TUXEDO service definitions that allow the clieto access TUXEDO services. The Contract Repository files included with the installation contain service definitions used internally by TUXEDO Builder.

To configure the Contract Repository, modify the application UBBCONFIG file. The UBBCONFIG file is an ASCII version of the TUXEDO configuration file. Create a neUBBCONFIG file for each application. See the TUXEDO Reference Manual for information regarding the syntax of the entries for the file. Listing 5 shows relevaportions of the UBBCONFIG file.



The

Listing 5 Sample of UBBCONFIG File

*GROUPS

JREPGRP GRPNO=94 LMID=SITE1

*SERVERS

IREPSVR SRVGRP=JREPGRP SRVID=98

RESTART=Y GRACE=0 CLOPT="-A -- -W -N -P /app/irepository"

Note: For UNIX systems, use the slash (/ ) when setting the path to the irepository file. For NT systems, use the backslash (\ ) and specify the drive name (e.g., c:\app\repository ).

Change the following sections of the UBBCONFIG file.

*GROUPS Section

A *GROUPS entry is required for the group that includes the Contract Repository.group name parameter is a name selected by the application.

1. Specify the same identifiers given as the value of the LMID parameter in the *MACHINES section.

2. Specify the value of the GRPNO between 1 and 30,000 in the *GROUPS section.

Table 3 UBBCONFIG File

Section Parameters to be specified

*GROUPS LMID, GRPNO

*SERVERS SRVGRP, SRVID



g

ry.

ith

t self,

e

t y

*SERVERS Section

The Contract Repository server, IREPSVR, contains services for accessing and editinthe Repository. Multiple IREPSVR instances share repository information through ashared file. Include IREPSVR in the *SERVERS section of the UBBCONFIG file.

1. Indicate a new server identification (e.g., 98) with the SRVID parameter.

2. Specify the -w flag for one IREPSVR to ensure that you can edit the RepositoThe Repository is read-only without this flag.

Warning: You must start only one writable IREPSVR (i.e., only one IREPSVR wthe -w flag). Multiple writable IREPSVRs are not supported.

3. Use the -N flag to notify the server to advertise the new set of services. If the -N flag is not specified, the environment does not work.

4. Type the -P flag to specify the location of the repository file. An error messagedisplays in the TUXEDO ULOG file if the argument for the -P flag is not entered.

5. Use tmloadcf to create the configuration file and tmboot to boot the system. See the TUXEDO Administration Guide for information on tmloadcf and tmboot .

Repository File

A default Repository file, irepository , is provided during installation. This file includes bankapp services that you can modify, test, and delete using the ContracRepository Editor. It also contains service interfaces for the Contract Repository itbut these are not visible through the Editor.

Start with the irepository file provided with the installation, even if you are not going to test the bankapp application. Delete the bankapp packages or services that are not needed.

The path name of the file must match the argument of the -P option.

Warning: Do not modify the Contract Repository files manually or you will not bable to use the Contract Repository Editor. Although the irepository file can be modified and read with any text editor, the system does nohave integrity checks to ensure that the file is in the proper format. Anmanual changes to the irepository file may not be detected until runtime.



ion

t to ut

Starting the BEA TUXEDO Builder Applications

The following sections describe how to start each of the BEA TUXEDO Builder applications once you have installed the Builder software.

Starting the Active Expert Application Builder

To start the Active Expert Application Builder, choose Start—>Programs—>BEA TUXEDO Builder—>Active Expert from the “Start” menu on the Windows DesktopTaskbar.

If you accepted the default location path at installation, the Active Expert ApplicatBuilder executable is installed in:

YourDrive :\TUXBldr\ActiveExpert\appbldr.exe (for Windows 95 or NT)

If you have set up a shortcut to the Active Expert, simply double-click on the Application Builder icon on your desktop.

Note: To get an Active Expert icon on your desktop, create a Windows shortcuthe Active Expert Application Builder. For instructions on creating a shortcto an application, refer to your Windows documentation.


STARTING THE BEA TUXEDO BUILDER APPLICATIONS

Figure 25 Active Expert Application Builder at Start-up

For information on working with the Active Expert, refer to the online help in the Active Expert application.

Menu BarToolbar

Workspace



o

on

sh

ert. es.

me

Starting the C++ Expert

On Intel/Windows platforms, choose Start—>Programs—>BEA TUXEDO Builder—>C++ Expert from the “Start” menu on the Windows Desktop Taskbar tstart the C++ Expert.

Or if you have set up a shortcut to the C++ Expert, simply double-click on the iconyour desktop.

On UNIX platforms, follow these steps to start the C++ Expert:

1. In a UNIX Bourne shell, change directories (cd ) to the following location:

<Builder_Install_dir >/client/CPPExpert/

2. Enter the following at the command line prompt:

sh ./CPPExpert.sh

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



+

Figure 26 C++ Expert at Start-up

For information on working with the C++ Expert, refer to the online help in the C+Expert application.

Menu BarToolbar

Workspace



n

t have

nu.

ose

Starting the Rose Expert

Unlike the other Builder products, the Rose Expert is a plug in so you cannot start it from within the Builder directories.

To use the Rose Expert, start your Rational Rose Application and choose the optioTools—>BEA TUXEDO Builder from the Rational Rose menu bar. For some options, there are prerequisite tasks. (For example, to Generate Classes you muscreated a component package in the current model.)

Figure 27 shows how to get to the Rose Expert from the Rational Rose Tools me

Figure 27 Getting to the BEA Rose Expert Menu Options

For information on working with the Rose Expert, refer to the online help in the RExpert application. (To get Help on the Rose Expert, choose Help—>BEA TUXEDO Builder from the Rational Rose menus.)



on

Starting the Configuration Expert

On Intel/Windows platforms, choose Start—>Programs—>BEA TUXEDO Builder—>Configuration Expert from the “Start” menu on the Windows DesktopTaskbar to start the Configuration Expert.

Or if you have set up a shortcut to the Configuration Expert, simply double-click the icon on your desktop.

On UNIX platforms, follow these steps to start the Configuration Expert:


<Builder_Install_dir >/client/ConfigExpert/bin/


sh ./ConfigExpert



in

or

Figure 28 Configuration Expert at Start-up

For information on working with the Configuration Expert, refer to the online helpthe Configuration Expert application.

You can also start the Configuration Data Editor from the ConfigExpert directories.

� On Intel/Windows platforms, double-click on the cedit.bat file in YourDrive :\TUXBldr\ConfigExpert\ .

� On UNIX platforms, in a Bourne shell change directories (cd ) to <Builder_Install_dir >/client/ConfigExpert/bin/ and enter the following at the command line prompt: sh ./ConfigEditor

The Configuration Data Editor is an auxiliary maintenance application for addingdeleting machines from the Configuration Data file, which is used by the Configuration Expert.

For information on working with the Configuration Data Editor, refer to the onlinehelp in the Configuration Expert application (Help—>Tasks—>Adding New Machines with the Editor) or to the online help in the Configuration Data Editor itself.

Menu BarToolbar

Workspace



k on

Starting the Contract Repository Editor

On Intel/Windows platforms, choose Start—>Programs—>BEA TUXEDO Builder—>Contract Repository Editor from the “Start” menu on the Windows Desktop Taskbar to start the Contract Repository Editor.

If you have set up a shortcut to the Contract Repository Editor, simply double-clicthe icon on your desktop.

On UNIX platforms, follow these steps to start the Contract Repository Editor:


<Builder_Install_dir >/client/RepEditor/


sh ./CRep.sh



e

Figure 29 Contract Repository at Start-up

For information on working with the Contract Repository Editor, refer to the onlinhelp in the Contract Repository Editor application.

Menu BarToolbar

Workspace


bea tuxedo builder

Documents