BEA Tuxedo. Using the BEA Tuxedo Domains Component

Transcription

1 BEA Tuxedo Usig the BEA Tuxedo Domais Compoet BEA Tuxedo Release 8.0 Documet Editio 8.0 Jue 2001

2 Copyright Copyright 2001 BEA Systems, Ic. All Rights Reserved. Restricted Rights Leged This software ad documetatio is subject to ad made available oly pursuat to the terms of the BEA Systems Licese Agreemet ad may be used or copied oly i accordace with the terms of that agreemet. It is agaist the law to copy the software except as specifically allowed i the agreemet. This documet may ot, i whole or i part, be copied photocopied, reproduced, traslated, or reduced to ay electroic medium or machie readable form without prior coset, i writig, from BEA Systems, Ic. Use, duplicatio or disclosure by the U.S. Govermet is subject to restrictios set forth i the BEA Systems Licese Agreemet ad i subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR ; subparagraph (c)(1)(ii) of the Rights i Techical Data ad Computer Software clause at DFARS , subparagraph (d) of the Commercial Computer Software--Licesig clause at NASA FAR supplemet ; or their equivalet. Iformatio i this documet is subject to chage without otice ad does ot represet a commitmet o the part 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 THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. Trademarks or Service Marks BEA, WebLogic, Tuxedo, ad Jolt are registered trademarks of BEA Systems, Ic. How Busiess Becomes E-Busiess, BEA WebLogic E-Busiess Platform, BEA Builder, BEA Maager, BEA elik, BEA WebLogic Commerce Server, BEA WebLogic Persoalizatio Server, BEA WebLogic Process Itegrator, BEA WebLogic Collaborate, BEA WebLogic Eterprise, ad BEA WebLogic Server are trademarks of BEA Systems, Ic. All other compay ames may be trademarks of the respective compaies with which they are associated. Usig the BEA Tuxedo Domais Compoet Documet Editio Date Software Versio 8.0 Jue 2001 BEA Tuxedo Release 8.0

3 Cotets About This Documet What You Need to Kow... vii e-docs Web Site... viii How to Prit the Documet... viii Related Iformatio... viii Cotact Us!... ix Documetatio Covetios...x 1. About Domais What Is the BEA Tuxedo Domais Compoet? Busiess Operatios Iteroperatig with Each Other Buildig a Multiple-domai Cofiguratio Tools to Set Up ad Maitai a Multiple-domai Applicatio Types of Domai Gateways Fuctioality Supported by Domai Gateways Example of a Applicatio Usig Domai Gateways Messagig Paradigms Supported by Domai Gateways Request/Respose Commuicatio Betwee Local ad Remote Services Coversatioal Commuicatio Betwee Local ad Remote Services Queued Messagig for Data Storage Typed Buffers to Package Data Defiig Trasactio ad Blockig Timeouts i Domais Specifyig How Your Domais Coect Determiig the Availability of Remote Services with the Dyamic Status Feature How Your Coectio Policy Affects Dyamic Status Usig the BEA Tuxedo Domais Compoet iii

4 What Is the Domais Cofiguratio File? Descriptios of Sectios of the DMCONFIG File Domais Termiology Improvemets Covertig the Domais Cofiguratio File Covertig DMCONFIG to a Biary File Covertig the BDMCONFIG File to a Text File Features of BEA Tuxedo System Domais Plaig ad Cofigurig ATMI Domais Plaig to Build Domais from Multiple BEA Tuxedo Applicatios Optio 1: Recofigure the Applicatios Cofiguratio File for Combiig the Sample Applicatios Limitatios of Optio Optio 2: Redefie the Applicatios as Separate BEA Tuxedo Domais Modifyig the Applicatio Cofiguratio Files Addig DMCONFIG Files Sample Domais Applicatio: creditapp The creditapp README File Cofigurig a Domais Eviromet Cofigurig a Sample Domais Applicatio (simpapp) Cofiguratio Tasks How to Set Eviromet Variables for lapp Example How to Defie the Domais Eviromet for lapp (i the ubbcofig File) Server Defiitios Example of a Applicatio Cofiguratio File for lapp How to Defie Domais Parameters for lapp (i the DMCONFIG File) Example of a Domai Gateway Cofiguratio File for lapp How to Compile Applicatio ad Domais Gateway Cofiguratio Files for lapp How to Set Eviromet Variables for rapp Example How to Defie the Domais Eviromet for rapp (i the UBBCONFIG File) Example of a Applicatio Cofiguratio File for rapp iv Usig the BEA Tuxedo Domais Compoet

5 How to Defie Domais Parameters for rapp (i the DMCONFIG File) Example of a Domai Gateway Cofiguratio File for rapp How to Compile Applicatio ad Domai Gateway Cofiguratio Files for rapp How to Compress Data Betwee Domais How to Route Service Requests to Remote Domais Settig Up Security i Domais Impact of BEA Tuxedo Applicatio Security o Domais Security Domais Security Mechaisms How to Create a Domais Access Cotrol List (ACL) Usig Stadard BEA Tuxedo Access Cotrol Lists with Imported Remote Services Settig the ACL Policy for a Remote Domai Settig the Credetial Policy for a Remote Domai How to Set Up Domais Autheticatio T_DM_PASSWORDS MIB Class Defiitios Settig Domais Passwords Examples of Codig Security Betwee Domais Example 1: Settig Security to NONE Example 2: Settig Security to APP_PW Cofigurig the Coectios Betwee Your Domais How to Request Coectios at Boot Time (ON_STARTUP Policy) How to Request Coectios for Cliet Demads (ON_DEMAND Policy) How to Limit Coectios to Icomig Messages Oly (INCOMING_ONLY Policy) How to Cofigure the Coectio Retry Iterval for ON_STARTUP Oly Cotrollig the Coectios Betwee Domais How to Establish Coectios Betwee Domais How to Break Coectios Betwee Domais How to Report o Coectio Status Cofigurig Failover ad Failback i a Domais Eviromet How to Cofigure Domais to Support Lik-level Failover Cofigurig Domais-level Failover ad Failback Usig the BEA Tuxedo Domais Compoet v

6 3. Plaig ad Cofigurig CORBA Domais Overview of Multiple CORBA Domais Iterdomai Commuicatio Fuctios of Multiple-domai Cofiguratio Elemets Cofigurig Multiple CORBA Domais The Cofiguratio File The Domai Cofiguratio (DMCONFIG) File The factory_fider.ii File Local Factories Types of CORBA Domai Cofiguratios Directly Coected Domais Idirectly Coected Domais Examples: Cofigurig Multiple CORBA Domais Sample UBBCONFIG Files Admiisterig Domais Usig Domais Ru-time Admiistrative Commads How to Migrate DMADM ad a Domai Gateway Group Usig the Admiistrative Iterface, dmadmi(1) Usig the Domais Admiistrative Server, DMADM(5) Usig the Gateway Admiistrative Server, GWADM(5) Usig the Gateway Process Maagig Trasactios i a Domais Eviromet Trasactio Maagemet Capabilities Usig the TMS Capability Across Domais How Gateways Coordiate Trasactios Across Domais Usig GTRID Mappig i Trasactios Defiig Tightly-coupled ad Loosely-coupled Relatioships Global Trasactios Across Domais Usig Loggig to Track Trasactios How Loggig Works Recoverig Failed Trasactios vi Usig the BEA Tuxedo Domais Compoet

7 About This Documet This documet explais how to cofigure ad admiister BEA Tuxedo domais, for either a data-depedet BEA Tuxedo ATMI eviromet or a object-orieted BEA Tuxedo CORBA eviromet. This documet covers the followig topics: Chapter 1, About Domais, provides a overview of the BEA Tuxedo Domais compoet. Chapter 2, Plaig ad Cofigurig ATMI Domais, explais how to pla ad cofigure a domai for a BEA Tuxedo ATMI eviromet. Chapter 3, Plaig ad Cofigurig CORBA Domais, explais how to cofigure a domai for a BEA Tuxedo CORBA eviromet. Chapter 4, Admiisterig Domais, explais how to admiister BEA Tuxedo domais. What You Need to Kow This documet is iteded maily for admiistrators who cofigure operatioal parameters that support missio-critical the BEA Tuxedo systems. It assumes a familiarity with the BEA Tuxedo platform. Usig the BEA Tuxedo Domais Compoet vii

8 e-docs Web Site BEA product documetatio is available o the BEA corporate Web site. From the BEA Home page, click o Product Documetatio or go directly to the e-docs Product Documetatio page at How to Prit the Documet You ca prit a copy of this documet from a Web browser, oe file at a time, by usig the File >Prit optio o your Web browser. A PDF versio of this documet is available o the BEA Tuxedo documetatio Home page o the e-docs Web site (ad also o the documetatio CD). You ca ope the PDF i Adobe Acrobat Reader ad prit the etire documet (or a portio of it) i book format. To access the PDFs, ope the BEA Tuxedo documetatio Home page, click the PDF files butto ad select the documet you wat to prit. If you do ot have the Adobe Acrobat Reader, you ca get it for free from the Adobe Web site at Related Iformatio The followig documets provide related iformatio about BEA Tuxedo software. Istallig the BEA Tuxedo System paper copy distributed with the CD BEA Tuxedo Release Notes paper copy distributed with the CD Settig Up a BEA Tuxedo Applicatio available through the BEA Tuxedo Olie Documetatio CD, this guide describes how to set up ad admiister the BEA Tuxedo system. viii Usig the BEA Tuxedo Domais Compoet

9 Admiisterig a BEA Tuxedo Applicatio at Ru Time available through the BEA Tuxedo Olie Documetatio CD, this guide describes how to admiister BEA Tuxedo applicatios at ru time. Scalig, Distributig, ad Tuig CORBA Applicatios available through the BEA Tuxedo Olie Documetatio CD, this guide describes how to tue ad scale CORBA applicatios that ru i the BEA Tuxedo CORBA eviromet. For more iformatio about cofigurig ad admiisterig BEA Tuxedo ATMI ad BEA Tuxedo CORBA eviromets, refer to the CORBA Bibliography at Cotact Us! Your feedback o the BEA Tuxedo documetatio is importat to us. Sed us at docsupport@bea.com if you have questios or commets. Your commets will be reviewed directly by the BEA professioals who create ad update the BEA Tuxedo documetatio. I your message, please idicate that you are usig the documetatio for the BEA Tuxedo 8.0 release. If you have ay questios about this versio of BEA Tuxedo, or if you have problems istallig ad ruig BEA Tuxedo, cotact BEA Customer Support through BEA WebSupport at You ca also cotact Customer Support by usig the cotact iformatio provided o the Customer Support Card, which is icluded i the product package. Whe cotactig Customer Support, be prepared to provide the followig iformatio: Your ame, address, phoe umber, ad fax umber Your compay ame ad compay address Your machie type ad authorizatio codes The ame ad versio of the product you are usig A descriptio of the problem ad the cotet of pertiet error messages Usig the BEA Tuxedo Domais Compoet ix

10 Documetatio Covetios The followig documetatio covetios are used throughout this documet. Covetio boldface text Ctrl+Tab italics moospace text moospace boldface text moospace italic text UPPERCASE TEXT Item Idicates terms defied i the glossary. Idicates that you must press two or more keys simultaeously. Idicates emphasis or book titles. Idicates code samples, commads ad their optios, data structures ad their members, data types, directories, ad fileames ad their extesios. Moospace text also idicates text that you must eter from the keyboard. Examples: iclude <iostream.h> void mai ( ) the poiter psz chmod u+w * \tux\data\ap.doc tux.doc BITMAP float Idetifies sigificat words i code. Example: void commit ( ) Idetifies variables i code. Example: Strig expr Idicates device ames, eviromet variables, ad logical operators. Examples: LPT1 SIGNON OR x Usig the BEA Tuxedo Domais Compoet

11 Covetio Item { } Idicates a set of choices i a sytax lie. The braces themselves should ever be typed. [ ] Idicates optioal items i a sytax lie. The brackets themselves should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list]... Separates mutually exclusive choices i a sytax lie. The symbol itself should ever be typed.... Idicates oe of the followig i a commad lie: That a argumet ca be repeated several times i a commad lie That the statemet omits additioal optioal argumets That you ca eter additioal parameters, values, or other iformatio The ellipsis itself should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list] Idicates the omissio of items from a code example or from a sytax lie. The vertical ellipsis itself should ever be typed. Usig the BEA Tuxedo Domais Compoet xi

12 xii Usig the BEA Tuxedo Domais Compoet

13 CHAPTER 1 About Domais This topic icludes the followig sectios: What Is the BEA Tuxedo Domais Compoet? Buildig a Multiple-domai Cofiguratio Example of a Applicatio Usig Domai Gateways Messagig Paradigms Supported by Domai Gateways Defiig Trasactio ad Blockig Timeouts i Domais Specifyig How Your Domais Coect What Is the Domais Cofiguratio File? Covertig the Domais Cofiguratio File Features of BEA Tuxedo System Domais What Is the BEA Tuxedo Domais Compoet? The BEA Tuxedo applicatio programmig framework simplifies the developmet of ope olie trasactio processig (OLTP) distributed applicatios by hidig the complexity associated with the distributio of applicatio processig. The framework cosists of the followig: Usig the BEA Tuxedo Domais Compoet 1-1

14 1 About Domais A exteded cliet/server model that hides the heterogeeity of differet computers ad applicatio programs, as well as the locatio of applicatio programs. A cetralized admiistratio system that allows applicatio admiistrators to cotrol all cooperatig machies as a sigle applicatio. As a busiess grows, applicatio developers may eed to orgaize differet segmets of the busiess by sets of fuctioality that require admiistrative autoomy but allow sharig of services ad data. It may ot be appropriate to structure a group of applicatios as a sigle distributed applicatio because of the fuctioality, geographical locatio, cofidetiality requiremets, ad potetial growth of each. Also, a eterprise may wat to expad busiess by cooperatig with other orgaizatios that provide OLTP services uder the cotrol of differet trasactio processig moitors, such as BEA s TOP END, Trasarc s Ecia, IBM s CICS, Bull s TDS, Bull s TP8, ICL s TPMS, ad so forth. Each set of fuctioality defies a applicatio that spas oe or more computers, ad is admiistered idepedetly from other applicatios. Such a fuctioally distict applicatio is referred to as a domai; i practice, the orgaizatio ofte uses the domai s fuctioality as part of its ame so you fid applicatios with ames like the accoutig domai or the order etry domai. A BEA Tuxedo domai is a sigle computer or etwork of computers cotrolled by a sigle BEA Tuxedo cofiguratio file. Busiess Operatios Iteroperatig with Each Other The BEA Tuxedo System Domais feature provides a framework for iteroperability amog the domais of a busiess that cotiues the BEA Tuxedo ehaced cliet/server model. Iteroperability meas more tha merely the capability of commuicatig from oe domai to aother. By trasparetly makig access to services of a remote domai available to users of the local domai (or acceptig local service requests from users of a remote domai), Domais, i effect, break dow the walls betwee the busiess applicatios of a orgaizatio. Applicatio programmers ca use the ATMI iterface to access the services provided by remote domais, or to defie services that ca be executed by a remote domai. 1-2 Usig the BEA Tuxedo Domais Compoet

15 Buildig a Multiple-domai Cofiguratio The Domais feature also eables BEA Tuxedo applicatios to cooperate with dozes of applicatios ruig i other admiistrative domais. The BEA Tuxedo system provides a commo framework for cotrollig very large applicatios that may iclude domais ruig other trasactio processig systems. Buildig a Multiple-domai Cofiguratio To build a multiple-domai cofiguratio, you eed to cosider the followig tasks: Itegrate your existig BEA Tuxedo applicatio with other domais Esure iteroperability across domais Preserve or restrict access to services across domais Accept or dey service requests across domais Domais achieve these tasks through a highly asychroous, multitaskig, multithreaded gateway. A domai gateway (DGW) is a BEA Tuxedo-supplied server that hadles requests to remote domais ad from remote domais. Ay request ca be processed withi a trasactio. The followig figure illustrates how oe BEA Tuxedo domai commuicates with aother domai via a domai gateway. Usig the BEA Tuxedo Domais Compoet 1-3

16 1 About Domais Figure 1-1 Two-way Commuicatio Through a Gateway I this illustratio, the gateway processes outgoig credit card authorizatio requests to aother domai. The gateway also hadles icomig authorizatio resposes. Domai gateways maage all the commuicatio betwee domais. The gateway processes iclude a gateway admiistrative server (GWADM) that eables ru-time admiistratio of the domai gateway group ad a Domais admiistrative server (DMADM) that eables ru-time admiistratio of the BEA Tuxedo applicatio-wide Domais cofiguratio iformatio. Tools to Set Up ad Maitai a Multiple-domai Applicatio The followig illustratio shows the tools provided by the BEA Tuxedo system for settig up ad maitaiig a multiple-domai cofiguratio. 1-4 Usig the BEA Tuxedo Domais Compoet

17 Buildig a Multiple-domai Cofiguratio Figure 1-2 Domais Admiistrative Tools Domais Admiistrative Tool dmadmi(1) DMCONFIG(5) BDMCONFIG dmloadcf(1) ad dmuloadcf(1) Descriptio A commad that allows you to cofigure, moitor, ad tue domai gateway groups dyamically. Use this commad to update the BDMCONFIG file while a applicatio is ruig. The commad acts as a frot-ed process that traslates admiistrative commads. These commads sed requests to the DMADMIN service, a geeric admiistrative service advertised by the DMADM server. DMADMIN ivokes fuctios that validate, retrieve, or update iformatio i the BDMCONFIG file. DMCONFIG is the text versio of the cofiguratio file for a multiple-domai cofiguratio; BDMCONFIG is the biary versio. dmloadcf reads the DMCONFIG file, checks the sytax, ad optioally loads a biary BDMCONFIG cofiguratio file. dmuloadcf traslates the BDMCONFIG cofiguratio file from biary to text format. Usig the BEA Tuxedo Domais Compoet 1-5

18 1 About Domais Domais Admiistrative Tool DMADM(5) GWADM(5) GWTDOMAIN(5) Descriptio (Cotiued) A admiistrative server that eables you to maage a Domais cofiguratio at ru time. DMADM provides a registratio service for gateway groups. This service is requested by GWADM servers as part of their iitializatio procedure. The registratio service dowloads the cofiguratio iformatio required by the requestig gateway group. The DMADM server maitais a list of registered gateway groups, ad propagates to these groups ay chages made to the cofiguratio file (BDMCONFIG). A admiistrative server that supports ru-time admiistratio of a specific gateway group. This server registers with the DMADM server to obtai the cofiguratio iformatio used by the correspodig gateway group. GWADM accepts requests from DMADMIN for ru-time statistics or chages i the ru-time optios of the specified gateway group. Periodically, GWADM seds a I-am-alive message to the DMADM server. If o reply is received from DMADM, GWADM registers agai. This process esures the GWADM server always has the curret iformatio about the Domais cofiguratio for its group. A gateway process that receives ad forwards messages from cliets ad servers i all coected domais (for BEA Tuxedo Domais). Types of Domai Gateways The BEA Tuxedo system provides differet types of gateways to accommodate various etwork trasport protocols used to commuicate with remote domais. Access to remote domais that use the same commuicatio ad trasactio commitmet protocol is provided through a group of gateways that implemet the cofiguratio defied for a particular local domai. Followig are the differet types of domai gateways: BEA Tuxedo Domais (TDomais) gateway (that is, the GWTDOMAIN gateway) provides iteroperability betwee two or more BEA Tuxedo applicatios through a specially desiged TP protocol that flows over etwork trasport protocols such as TCP/IP. 1-6 Usig the BEA Tuxedo Domais Compoet

19 Buildig a Multiple-domai Cofiguratio Note: GWTDOMAIN gateways should ot be specified as members of a MSSQ set. They should ot have a reply queue (REPLYQ=N should be specified). GWTDOMAIN gateways are recommeded to be restartable. BEA elik OSI TP gateway provides iteroperability betwee BEA Tuxedo applicatios ad other trasactio processig applicatios that use the OSI TP stadard. OSI TP is a protocol for distributed trasactio processig defied by the Iteratioal Stadards Orgaizatio (ISO). BEA elik Adapter for Maiframe SNA gateway provides iteroperability betwee cliets ad servers i a BEA Tuxedo domai, ad cliets ad servers i a MVS/CICS or MVS/IMS eviromet i a remote SNA domai. It also supports commuicatio with multiple SNA etworks. BEA elik Adapter for Maiframe TCP: l For CICS gateway makes it possible for o-trasactioal tasks withi BEA Tuxedo regios to access services provided by CICS applicatio programs ad vice-versa. It eables a BEA Tuxedo domai to commuicate, via the TCP/IP etwork trasport protocol, with a CICS eviromet. l For IMS gateway provides trasparet commuicatios betwee cliet ad server trasactios i a IMS system ad a BEA Tuxedo domai, a CICS system, or aother IMS system. BEA TOP END Domai Gateway (TEDG) provides iteroperability betwee TOP END systems ad BEA Tuxedo domais. Fuctioality Supported by Domai Gateways Domai gateways support the followig fuctioality: Admiistratio gateways ca be booted or shut dow exactly as ay other BEA Tuxedo server. Ru-time admiistratio is provided through a admiistrative server, DMADM. Usig DMADM, applicatio admiistrators ca make chages to a domais cofiguratio file, ad tue the performace of a gateway group. (The DMADM admiistrative server should be booted before gateway groups.) ATMI gateways ca access the programmig iterface betwee a domai ad the BEA Tuxedo system esurig access to the followig messagig models: Usig the BEA Tuxedo Domais Compoet 1-7

20 1 About Domais l l l Request/Respose Model applicatio programs usig the BEA Tuxedo system ca request services from applicatios ruig i other domais. Also, remote applicatios ca request services from local servers. (No chages are required to the applicatio program to accommodate this iterdomai fuctioality.) Coversatioal Model applicatio programs ca establish coversatios with programs ruig i other domais. Remote domais ca establish coversatios with coversatioal services offered by local servers. (No chages are required to the applicatio program to accommodate this iterdomai fuctioality.) Queuig Model applicatio programs usig the BEA Tuxedo system ca store data o queues. Ay cliet or server ca store messages or service requests i a queue i a remote domai ad all stored requests are set through the trasactio protocol to esure safe storage. (No chages are required to the applicatio program to accommodate this iterdomai fuctioality.) Multidomai Iteractio gateways ca commuicate with multiple domais. Multietwork Support gateways ca commuicate with other domais via a variety of etwork protocols, such as TCP/IP, IPX/SPX, ad others. However, a gateway is limited by the capabilities of the etworkig library to which it is liked. I other words, a gateway typically supports a sigle type of etwork protocol. Trasactio Maagemet applicatio programs ca iteroperate with other domais withi a trasactio. The gateway coordiates the commitmet or rollback of trasactios ruig across domais. Typed Buffer Support gateways ca perform ecodig ad decodig operatios for all the types of buffers defied by the applicatio. See Also What Is a Multiple-domai Cofiguratio? o page 3-47 i Itroducig BEA Tuxedo ATMI Example of a Applicatio Usig Domai Gateways o page 1-9 Messagig Paradigms Supported by Domai Gateways o page Usig the BEA Tuxedo Domais Compoet

21 Example of a Applicatio Usig Domai Gateways Example of a Applicatio Usig Domai Gateways The followig figure shows a BEA Tuxedo applicatio that requires services (i this case, credit card authorizatios) from a remote domai. Figure 1-3 High-level View of Two Commuicatig Domais The applicatio also accepts service requests (for example, balace iquiries) from remote domais. The gateway process provides bidirectioal trasactio cotrol, ad admiistrative tools for cofigurig a local domai to iteroperate with other domais. BDMCONFIG, the cofiguratio file for a multiple-domai applicatio, idetifies exported services, imported services, addressig, ad ay access cotrol lists to be used. The followig figure shows a more detailed view of a sample Domais eviromet. Usig the BEA Tuxedo Domais Compoet 1-9

22 1 About Domais Figure 1-4 Example Domais Eviromet The example shows a credit card authorizatio ceter ruig uder the cotrol of the BEA Tuxedo system. The authorizatio ceter has two gateway groups: bakgw1 (which uses the TCP/IP protocol) ad bakgw2 (which uses the OSI TP protocol). bakgw1 provides access to two remote BEA Tuxedo domais (Bak ABC ad Bak CBA); bakgw2 provides access to oe remote domai (Bak XYZ) usig the OSI TP protocol. I this example, Bak ABC geerates service requests to the credit card authorizatio ceter. These requests are received by a gateway ruig withi group bakgw1. This gateway issues a service request, o behalf of the remote domai, to the credit card authorizatio service provided by a local server. The server processes the request ad seds the reply to the gateway, ad the gateway forwards the reply to Bak ABC. The credit card authorizatio ceter may also issue service requests. For example, the authorizatio ceter may sed balace iquiries to Bak XYZ. Domais makes this possible by providig a gateway that acts like a local server that advertises services available i other domais as if they were local services Usig the BEA Tuxedo Domais Compoet

23 Messagig Paradigms Supported by Domai Gateways Domais provides the otio of a local domai that cotrols icomig requests ad provides a geeric addressig framework for the applicatio. Local domais help to provide partial views of a applicatio, that is, a subset of the local services available to a set of remote domais. Each local domai is always represeted by a sigle gateway server group. Messagig Paradigms Supported by Domai Gateways The fuctios of the BEA Tuxedo cliet/server model are supported by the followig messagig paradigms i domai gateways: Request/Respose Commuicatio Betwee Local ad Remote Services o page 1-11 Coversatioal Commuicatio Betwee Local ad Remote Services o page 1-13 Queued Messagig for Data Storage o page 1-13 Request/Respose Commuicatio Betwee Local ad Remote Services Domai gateways provide support for the request/respose model of commuicatio defied by the ATMI iterface. A BEA Tuxedo applicatio ca request remote services exactly as if they were offered locally. Usig the BEA Tuxedo Domais Compoet 1-11

24 1 About Domais Support for ATMI Fuctios The followig BEA Tuxedo ATMI fuctios are logically limited to use withi a sigle applicatio ad are ot supported across domais: tpiit(3c)/tpterm(3c) BEA Tuxedo applicatios do ot attach to the eviromet of a remote domai; they use Domai gateways to access a remote domai. Therefore, a extra tpiit()/tpterm() sequece is ot eeded for remote applicatios. tpadvertise(3c) ad tpuadvertise(3c) caot be used across domais. Domai gateways do ot support dyamic service advertisemets across domais. tpotify(3c) ad tpbroadcast(3c) Domais does ot support the usolicited commuicatio paradigm provided by these primitives. Evet postig (tppost(3c)) ad otificatio of evets (tpsubscribe(3c)) Domais does ot support these fuctios across domais. Support for tpforward(3c) is provided to preserve applicatio portability. Forwarded requests are iterpreted by domai gateways as simple service requests. This process is show i the followig diagram, which illustrates the simple sceario of a service usig tpforward to sed a request to a remote service. Figure 1-5 Usig tpforward to Sed a Request to a Remote Service 1-12 Usig the BEA Tuxedo Domais Compoet

25 Messagig Paradigms Supported by Domai Gateways Coversatioal Commuicatio Betwee Local ad Remote Services The ATMI is a coectio-orieted iterface that eables cliets to establish ad maitai coversatios with services programmed i the coversatioal paradigm. BEA Tuxedo applicatios use tpcoect(3c) to ope a coversatio with a remote service, tpsed(3c) ad tprecv(3c) to commuicate with this service, ad tpdisco(3c) to ed the coversatio. Domai gateways maitai the coversatio with the remote service, ad support the same sematics for returs (that is, tpretur with TPSUCCESS or TPFAIL) ad discoects that are defied for BEA Tuxedo coversatioal services. Note: The ATMI coectio-orieted fuctios provide half-duplex coversatios; tpforward(3c) is ot allowed withi a coversatioal service. Applicatio admiistrators idicate that a remote service is coversatioal by specifyig CONV=Y i the DM_REMOTE_SERVICES sectio of the DMCONFIG file. Queued Messagig for Data Storage The BEA Tuxedo system eables messages to be queued to persistet storage (disk) or to o-persistet storage (memory) for later processig or retrieval. ATMI provides primitives that allow messages to be added (that is, tpequeue) or read (that is, tpdequeue) from queues. Reply messages ad error messages ca be queued for later retur to cliets. A admiistrative commad iterpreter (that is, qmadmi) is provided for creatig, listig, ad modifyig queues. Servers are provided to accept requests to equeue ad dequeue messages (that is, TMQUEUE server), to forward messages from the queue for processig (that is, TMQFORWARD server), ad to maage the trasactios that ivolve queues (that is, TMS_QM server). Domai gateways exted support for queued messagig services across domais. Usig the BEA Tuxedo Domais Compoet 1-13

26 1 About Domais See Also What Is Request/Reply Commuicatio? o page 2-14 i Itroducig BEA Tuxedo ATMI What Is Coversatioal Commuicatio? o page 2-9 i Itroducig BEA Tuxedo ATMI What Is Queue-based Commuicatio? o page 2-13 i Itroducig BEA Tuxedo ATMI Typed Buffers to Package Data I BEA Tuxedo applicatios, typed buffers are used to sed data betwee cliets ad servers. The typed buffer mechaism allows applicatio programmers to trasfer data without eedig to kow which data represetatio scheme is used by the machies o which the applicatio s cliets ad servers are ruig. A domai gateway ca receive ad process service requests set from workstatios, BEA Tuxedo machies, ad remote domais with differet machie represetatios. A typed buffer switch decodes the data set with the service request. The admiistrator must defie the typed buffer switch appropriate for the applicatio. Data-depedet routig depeds upo matchig specified criteria to fields withi data. If data is ecoded, however, there is o way to determie the cotets of that data i order to route that data accurately. I additio, a domai gateway eeds access to the cotets for the followig reasos: The gateway may have to apply data-depedet routig to select the appropriate remote domai for the service requested. (Data-depedet routig criteria for remote domais are defied i the Domais cofiguratio file.) Differet data formats may be used withi differet domais, depedig o the etworkig protocols implemeted or used i each domai. Therefore a domai gateway always tries to decode ay service request that is received ecoded Usig the BEA Tuxedo Domais Compoet

27 Defiig Trasactio ad Blockig Timeouts i Domais OSI termiology provides a useful distictio betwee abstract sytax (that is, the structure of the data) ad trasfer sytax (that is, the particular ecodig used to trasfer the data). Each typed buffer implicitly defies a particular data structure (that is, its abstract sytax) ad the ecodig rules (or typed buffer operatios) required to map the data structure to a particular trasfer sytax (for example, XDR). The BEA Tuxedo system provides a set of predefied buffer types (STRING, CARRAY, FML, FML32, VIEW, VIEW32, X_C_TYPE, X_OCTET, X_COMMON, ad XML) ad the ecodig rules required to map these types to the XDR trasfer sytax. Note: A programmer ca supply a custom buffer type by addig a istace to the tm_typesw array i TUXDIR/lib/tmtypesw.c (see tuxtypes(5) ad typesw(5)), ad supplyig routies for the ew type (see buffer(3c)). See Also What Are Typed Buffers? o page 2-24 i Itroducig BEA Tuxedo ATMI Customizig a Buffer o page 3-28 i Programmig BEA Tuxedo ATMI Applicatios Usig C tuxtypes(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece typesw(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece Defiig Trasactio ad Blockig Timeouts i Domais The BEA Tuxedo system provides two timeout mechaisms: a trasactio timeout mechaism ad a blockig timeout mechaism. The trasactio timeout is used to defie the duratio of a trasactio, which may ivolve several service requests. The Usig the BEA Tuxedo Domais Compoet 1-15

28 1 About Domais timeout value is defied whe the trasactio is started (with tpbegi(3c)). The blockig timeout is used to defie the duratio of idividual service requests, that is, how log the applicatio is willig to wait for a reply to oe service request. The BEA Tuxedo trasactio timeout mechaism is used uchaged i the Domais framework. Use of the same trasactio timeout mechaism is ecessary because domai gateways implemet the TMS fuctioality ad therefore are required to hadle the TMS_TIMEOUT messages geerated by the Bulleti Board Liaiso (BBL). Domai gateways, however, caot use the BEA Tuxedo blockig timeout mechaism. The blockig timeout mechaism uses iformatio stored i the registry slot assiged to each cliet or server. (Iformatio i the registry slot is used by the local BBL to detect requesters that have bee blocked for a time greater tha BLOCKTIME.) Domai gateways, however, are multitaskig servers that ca process several service requests at a time, which meas they caot use the registry slot mechaism. Whe a blockig timeout coditio arises, the domai gateway seds a error/failure reply message to the requester, ad cleas ay cotext associated with the service request. Specifyig How Your Domais Coect You ca specify the coditios uder which a local domai gateway tries to establish a coectio to a remote domai by selectig oe of the followig coectio policies: Coect at boot time (ON_STARTUP) Coect whe a cliet program requests a remote service (ON_DEMAND) Accept icomig coectios but do ot iitiate a coectio automatically (INCOMING_ONLY) 1-16 Usig the BEA Tuxedo Domais Compoet

29 Specifyig How Your Domais Coect Determiig the Availability of Remote Services with the Dyamic Status Feature The gateway process (GWTDOMAIN) advertises those services that are imported from oe or more remote domais i the bulleti board. These services typically remai advertised regardless of whether the remote service is reachable. The capability of the BEA Tuxedo domai gateways kow as Dyamic Status reports the status (as determied by the BEA Tuxedo system) of remote services. Whe Dyamic Status is i effect, the status of a remote service depeds o the status of the etwork coectio betwee the local ad remote gateways. Remote services are cosidered available wheever a coectio to the domai o which they reside is available. Whe a etwork coectio to a remote domai is ot available, services i that domai are cosidered uavailable. This policy is ivoked whe the coectio policy is ON_STARTUP (that is, whe a local domai gateway tries to establish a coectio to a remote domai at boot time) or INCOMING_ONLY (that is, whe a local domai gateway does ot try to establish a coectio to remote domais upo startig). For each service, the gateway keeps track, ot oly of the remote domais from which the service is imported, but also of which remote domais are available. I this way, the gateway provides itelliget load balacig of requests to remote domais. If all the remote domais from which a service is imported become ureachable, the service is suspeded i the bulleti board. For example, suppose a service called RSVC is imported from two remote domais, as specified by the followig etries i the DM_REMOTE_SERVICES sectio of the cofiguratio file: RSVC RDOM=R1 RSVC RDOM=R2 Whe coectios to both R1 ad R2 are up, the gateway load balaces requests for the RSVC service. If the coectio to R1 goes dow, the gateway seds all requests for RSVC to R2. If both coectios go dow, the gateway suspeds RSVC i the bulleti board. Subsequet requests for RSVC are either routed to a local service or aother gateway, or fail with TPENOENT. Usig the BEA Tuxedo Domais Compoet 1-17

30 1 About Domais Note: Whe the coectio policy is ON_DEMAND, a coectio is attempted oly whe either a cliet requests a remote service or a admiistrative coect commad is ru. How Your Coectio Policy Affects Dyamic Status Dyamic Status is ot available i all Domais cofiguratios; whether it is available depeds o which coectio policy you establish betwee your domais. The followig table describes how each coectio policy affects Dyamic Status. Table 1-1 Availability of Dyamic Status Uder This Policy... ON_STARTUP ON_DEMAND INCOMING_ONLY Dyamic Status Is.. O. Services imported from a remote domai are advertised as log as a coectio to that remote domai is active. A coectio ca be established i ay of the followig ways: Automatically Maual through the dmadmi commad Through a icomig coectio Off. Services imported from remote domais are cotiually advertised. Ways i which a coectio ca be established are: Cliet request Maually through the dmadmi commad Through a icomig coectio O. Remote services are iitially suspeded. A domai gateway is available for icomig coectios from remote domais, ad remote services are advertised whe the local domai gateway receives a icomig coectio or whe a maual coect commad is issued. A coectio ca be established i the followig ways: Maually through the dmadmi commad Through a icomig coectio 1-18 Usig the BEA Tuxedo Domais Compoet

31 What Is the Domais Cofiguratio File? What Is the Domais Cofiguratio File? All domais cofiguratio iformatio is stored i a biary file called BDMCONFIG. You ca create ad edit a text versio of this file, DMCONFIG, with ay text editor. You ca update the compiled BDMCONFIG file while the system is ruig by usig the dmadmi(1) commad whe usig Domais. I a multi-domai applicatio, a separate BDMCONFIG file must be created for each participatig domai. System access to the BDMCONFIG file is provided through the Domais admiistrative server, DMADM(5). Whe a gateway group is booted, the gateway admiistrative server, GWADM(5), requests from the DMADM server, a copy of the cofiguratio file required by that group. The GWADM ad DMADM servers also esure that ru-time chages to the cofiguratio are reflected i the correspodig domai gateway group. Descriptios of Sectios of the DMCONFIG File The followig table provides a descriptio of each sectio i the DMCONFIG file. Table 1-2 DMCONFIG File Sectios Sectio DM_LOCAL_DOMAINS DM_REMOTE_DOMAINS DM_LOCAL_SERVICES Purpose Describes the eviromet for a particular domai gateway group. It assigs a logical applicatio ame, LDOM, to the subset of local services available to remote domais. You ca use multiple etries i this sectio to defie multiple gateway groups withi a sigle BEA Tuxedo applicatio. Each gateway group ca provide access to domais of differet types. Idetifies the remote domais available to cliets ad servers of this Domais applicatio. Describes the local services provided by a local domai (LDOM) i the DM_LOCAL_DOMAINS sectio. Specificatio of services ca also be used to restrict access to local services from remote domais; oly services specified are available to remote domais. Usig the BEA Tuxedo Domais Compoet 1-19

32 1 About Domais Sectio DM_REMOTE_SERVICES DM_ROUTING DM_ACCESS_CONTROL DM_dmtype Purpose (Cotiued) Describes the set of services provided by remote domais. It also ames the local gateway group (through the LDOM parameter) that provides access to the remote service. Specifies criteria for data-depedet routig used by gateways to route service requests to specific remote domais. Specifies a access cotrol list (ACL) that ames (via RDOMs) the remote domais permitted to request local services. The ACL parameter i the DM_LOCAL_SERVICES sectio ca be used by settig ACL=ame_of_list to restrict access to a particular local service to the listed set of remote domais. Defies the parameters required for a particular Domais cofiguratio. Curretly, the value of dmtype ca be OSITP, SNAX, TOPEND, or TDOMAIN. This topic focuses oly o TDOMAIN. Cosult BEA elik for Maiframe documetatio for iformatio about OSITP ad SNAX. Cosult Usig the BEA Tuxedo TOP END Domai Gateway for iformatio about TOPEND. Each domai type must be specified i a separate sectio. I a DM_TDOMAIN sectio, etries associated with a remote domai ca be specified more tha oce, with differet etwork addresses, to implemet the mirrored gateway facility. (See DMCONFIG(5) for a descriptio ad a example of a mirrored gateway.) Domais Termiology Improvemets For BEA Tuxedo release 7.1 or later, the Domais MIB uses improved class ad attribute termiology to describe the iteractio betwee local ad remote domais. The improved termiology applies to the DM_MIB classes, referece page, ad error messages, the DMCONFIG file sytax, ad various DMCONFIG error messages. For backwards compatibility, aliases are provided betwee the DMCONFIG termiology used prior to BEA Tuxedo release 7.1 ad the improved Domais MIB termiology. For BEA Tuxedo release 7.1 or later, DMCONFIG accepts both versios of the termiology. For details, see Domais Termiology Improvemets i the DM_MIB(5) referece page Usig the BEA Tuxedo Domais Compoet

33 Covertig the Domais Cofiguratio File See Also Cofigurig a Domais Eviromet o page 2-18 DMCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece Covertig the Domais Cofiguratio File o page 1-21 Covertig the Domais Cofiguratio File This sectio provides istructios for covertig a text versio of a Domais cofiguratio file (DMCONFIG) to a biary versio (BDMCONFIG), ad vice versa. Covertig DMCONFIG to a Biary File The dmloadcf(1) commad parses DMCONFIG (a text file), ad loads the iformatio about the Domais cofiguratio ito a biary file called BDMCONFIG. The commad uses the eviromet variable BDMCONFIG to poit to the directory i which the cofiguratio should be stored. The BDMCONFIG file ca be stored o the same device as the TUXCONFIG file (or the biary versio of the UBBCONFIG file). Figure 1-6 Relatioships Betwee Cofiguratio Commads ad Files Usig the BEA Tuxedo Domais Compoet 1-21

34 1 About Domais The dmloadcf(1) commad, through the -c optio, also provides a estimate of the IPC resources eeded for each local domai specified i the cofiguratio. As show i the precedig figure, the dmloadcf commad uses the $TUXDIR/udataobj/DMTYPE file. It checks the DMTYPE file to verify that the domai types specified i the cofiguratio file are valid. Each Domais istatiatio has a domai type. The type is used as a tag i the file TUXDIR/udataobj/DMTYPE. Each lie i this file has the followig format: dmtype:access_module_lib:comm_libs:tm_typesw_lib:gw_typesw_lib The file has the followig etry for TDOMAIN: TDOMAIN:-lgwt:-lwi -lws -lwi:: Covertig the BDMCONFIG File to a Text File To uload a biary versio of a Domais cofiguratio file (that is, to covert it from biary to text format), ru the dmuloadcf(1)commad Usig the BEA Tuxedo Domais Compoet

35 Features of BEA Tuxedo System Domais Features of BEA Tuxedo System Domais Aliasig capability allows you to defie map service ames betwee local ad remote applicatios, allowig for easy itegratio of applicatios that use differet amig schemes. Availability allows you to specify alterate destiatios to hadle failure coditios. Scalability ad modular growth programmers ca structure their applicatios for modularity, isolatio of failures, ad idepedet growth. Iteroperatio with other trasactio processig applicatios is achieved easily by addig to the Domais cofiguratio the descriptio of services used by a remote applicatio. Security a access cotrol list (ACL) facility is provided to restrict access to local resources from a particular set of remote domais. Domais also provides ecryptio ad password verificatio. Trasparecy ad idepedece applicatio programmers eed o kowledge of how services are distributed. A service may be available o the same machie as a cliet, o aother machie i the local domai, or o a remote domai. Cliet applicatio programmers do ot eed to kow the implemetatio chages made to a service, the locatio of a service, etwork addresses, ad so o. Trasactio maagemet ad reliability this Domais feature is itegrated with the BEA Tuxedo trasactio maagemet capabilities. Usig the BEA Tuxedo Domais Compoet 1-23

36 1 About Domais 1-24 Usig the BEA Tuxedo Domais Compoet

37 CHAPTER 2 Plaig ad Cofigurig ATMI Domais This chapter describes how to pla ad cofigure domais i a BEA Tuxedo ATMI eviromet. For iformatio about cofigurig domais i a BEA Tuxedo CORBA eviromet, refer to Chapter 3, Cofigurig CORBA Domais. This topic icludes the followig sectios: Plaig to Build Domais from Multiple BEA Tuxedo Applicatios Sample Domais Applicatio: creditapp Cofigurig a Domais Eviromet How to Compress Data Betwee Domais How to Route Service Requests to Remote Domais Settig Up Security i Domais Cofigurig the Coectios Betwee Your Domais Cofigurig Failover ad Failback i a Domais Eviromet Usig the BEA Tuxedo Domais Compoet 2-1

38 2 Plaig ad Cofigurig ATMI Domais Plaig to Build Domais from Multiple BEA Tuxedo Applicatios Suppose a bak has developed the two BEA Tuxedo applicatios show i the followig figure: bakapp ad a credit card authorizatio ceter. Figure 2-1 Two BEA Tuxedo Applicatios The bakapp applicatio coects ATMs at various bak braches to the cetral bak office. The Credit Card Authorizatio Ceter processes applicatios for credit cards. Over time, the bak realizes that their customers would be better served if the bakapp applicatio could commuicate directly with the credit card authorizatio applicatio. I this way, they could offer istat credit cards to ayoe opeig a ew accout. bakapp is distributed as a sample applicatio with the BEA Tuxedo software. The credit card authorizatio applicatio is a hypothetical extesio of bakapp. Take a look at the cofiguratio file (represeted i the followig sample code) to see how to implemet bakapp as a multiple-machie applicatio: TUXDIR/apps/bakapp/ubbmp. 2-2 Usig the BEA Tuxedo Domais Compoet

39 Plaig to Build Domais from Multiple BEA Tuxedo Applicatios You have the followig optios: Optio 1: Recofigure the Applicatios o page 2-4 Optio 2: Redefie the Applicatios as Separate BEA Tuxedo Domais o page 2-9 Usig the BEA Tuxedo Domais Compoet 2-3

40 2 Plaig ad Cofigurig ATMI Domais Optio 1: Recofigure the Applicatios Oe solutio is to combie two BEA Tuxedo applicatios ito oe, as show i the followig figure. Figure 2-2 Combiig Two BEA Tuxedo System Applicatios I the process of combiig the two applicatios ito a sigle cofiguratio, the followig chages are made: OPTION=LAN is specified ad a NETWORK sectio is icluded. Server migratio is eabled by specifyig OPTION=MIGRATE; at the same time a backup master site is defied. The gateway server is redefied as three other servers: TLRA, ACCTA, ad CRDT. Credit Authorizatio services are added. 2-4 Usig the BEA Tuxedo Domais Compoet

41 Optio 1: Recofigure the Applicatios Cofiguratio File for Combiig the Sample Applicatios The followig code shows a possible cofiguratio file for the combied applicatios. Listig 2-1 Sample Cofiguratio File for the Combied Applicatio *RESOURCES IPCKEY UID 0000 GID 000 PERM 0660 MAXACCESSERS 40 MAXSERVERS 35 MAXSERVICES 75 MAXCONV 10 MASTER SITE1,SITE2 SCANUNIT 10 MODEL MP LDBAL Y OPTIONS LAN,MIGRATE MAXGTT 100 MAXBUFTYPE 16 SCANUNIT 10 SANITYSCAN 5 DBBLWAIT 6 BBLQUERY 50 BLOCKTIME 2 *MACHINES mach1 LMID=SITE1 TUXDIR= /home/mylogi/tuxroot APPDIR= /home/mylogi/bakapp ENVFILE= /home/mylogi/bakapp/envfile TLOGDEVICE= /home/mylogi/bakapp/tlog TLOGNAME=TLOG TUXCONFIG= /home/mylogi/bakapp/tuxcofig ULOGPFX= /home/mylogi/bakapp/ulog TYPE= type1 mach2 LMID=SITE2 TUXDIR= /home/mylogi/tuxroot Usig the BEA Tuxedo Domais Compoet 2-5

42 2 Plaig ad Cofigurig ATMI Domais mach3 LMID=SITE3 mach4 LMID=SITE4 *GROUPS DEFAULT: TMSNAME=TMS_SQL APPDIR= /home/mylogi/bakapp ENVFILE= /home/mylogi/bakapp/envfile TLOGDEVICE= /home/mylogi/bakapp/tlog TLOGNAME=TLOG TUXCONFIG= /home/mylogi/bakapp/tuxcofig ULOGPFX= /home/mylogi/bakapp/ulog TYPE= type2 TUXDIR= /home/mylogi/tuxroot APPDIR= /home/mylogi/bakapp ENVFILE= /home/mylogi/bakapp/envfile TLOGDEVICE= /home/mylogi/bakapp/tlog TLOGNAME=TLOG TUXCONFIG= /home/mylogi/bakapp/tuxcofig ULOGPFX= /home/mylogi/bakapp/ulog TYPE= type2 TUXDIR= /home/mylogi/tuxroot APPDIR= /home/mylogi/bakapp ENVFILE= /home/mylogi/bakapp/envfile TLOGDEVICE= /home/mylogi/bakapp/tlog TLOGNAME=TLOG TUXCONFIG= /home/mylogi/bakapp/tuxcofig ULOGPFX= /home/mylogi/bakapp/ulog TYPE= type1 TMSCOUNT=2 BANKB1 LMID=SITE1 GRPNO=1 OPENINFO= TUXEDO/SQL:/home/mylogi/bakapp/bakdl1:bakdb:readwrite BANKB2 LMID=SITE2 GRPNO=2 OPENINFO= TUXEDO/SQL:/home/mylogi/bakapp/bakdl2:bakdb:readwrite BANKB3 LMID=SITE3 GRPNO=3 OPENINFO= TUXEDO/SQL:/home/mylogi/bakapp/bakdl3:bakdb:readwrite BANKB4 LMID=SITE4 GRPNO=4 OPENINFO= TUXEDO/SQL:/home/mylogi/bakapp/bakdl4:bakdb:readwrite *NETWORK SITE1 SITE2 NADDR= <etwork address of SITE1> BRIDGE= <device of provider1> NLSADDR= <etwork listeer address of SITE1> NADDR= <etwork address of SITE2> BRIDGE= <device of provider2> NLSADDR= <etwork listeer address of SITE2> 2-6 Usig the BEA Tuxedo Domais Compoet

43 Optio 1: Recofigure the Applicatios SITE3 SITE4 NADDR= <etwork address of SITE3> BRIDGE= <device of provider3> NLSADDR= <etwork listeer address of SITE3> NADDR= <etwork address of SITE4> BRIDGE= <device of provider4> NLSADDR= <etwork listeer address of SITE4> *SERVERS DEFAULT: RESTART=Y MAXGEN=5 REPLYQ=Y CLOPT= -A Servers for the bakapp part TLR SRVGRP=BANKB1 SRVID=2 TLR SRVGRP=BANKB2 SRVID=3 RQADDR=tlr2 CLOPT= -A -- -T 600 TLR SRVGRP=BANKB3 SRVID=4 XFER SRVGRP=BANKB1 SRVID=10 XFER SRVGRP=BANKB2 SRVID=6 XFER SRVGRP=BANKB3 SRVID=8 ACCT SRVGRP=BANKB1 SRVID=11 ACCT SRVGRP=BANKB2 SRVID=7 ACCT SRVGRP=BANKB3 SRVID=13 BTADD SRVGRP=BANKB1 SRVID=12 BTADD SRVGRP=BANKB2 SRVID=14 BTADD SRVGRP=BANKB3 SRVID=16 Servers for the Credit Authorizatio Part TLRA SRVGRP=BANKB4 SRVID=5 CLOPT= -A -- -T 600 ACCTA SRVGRP=BANKB4 SRVID=9 CRDT SRVGRP=BANKB4 SRVID=15 *SERVICES DEFAULT: LOAD=50 AUTOTRAN=N Services for the bakapp part BR_ADD PRIO=20 ROUTING=BRANCH_ID TLR_ADD PRIO=20 ROUTING=BRANCH_ID WITHDRAWAL PRIO=50 ROUTING=ACCOUNT_ID DEPOSIT PRIO=50 ROUTING=ACCOUNT_ID TRANSFER PRIO=50 ROUTING=ACCOUNT_ID INQUIRY PRIO=50 ROUTING=ACCOUNT_ID CLOSE_ACCT PRIO=40 ROUTING=ACCOUNT_ID OPEN_ACCT PRIO=40 ROUTING=BRANCH_ID Services for the Credit Authorizatio part WITHDRAWALA INQUIRYA OPENCA CLOSECA DEPOSITA OPEN_ACCT2 OPENC PRIO=50 PRIO=50 PRIO=40 PRIO=40 PRIO=50 PRIO=40 PRIO=40 Usig the BEA Tuxedo Domais Compoet 2-7

44 2 Plaig ad Cofigurig ATMI Domais *ROUTING ACCOUNT_ID BRANCH_ID FIELD=ACCOUNT_ID BUFTYPE= FML RANGES= :BANKB1, :BANKB2, :BANKB3, *:* FIELD=BRANCH_ID BUFTYPE= FML RANGES= 1-3:BANKB1, 4-6:BANKB2, 7-10:BANKB3, *:* Limitatios of Optio 1 Admiisterig a sigle large applicatio ca be more cumbersome tha admiisterig two smaller oes; each smaller oe has its ow admiistrative iterface. Bootig a etworked applicatio ca be more costly because of the time required to boot each server ad because of the eed to propagate bulleti boards across the etwork. Smaller, separate applicatios ca be booted simultaeously. 2-8 Usig the BEA Tuxedo Domais Compoet

45 Optio 2: Redefie the Applicatios as Separate BEA Tuxedo Domais Optio 2: Redefie the Applicatios as Separate BEA Tuxedo Domais The followig figure shows the combied applicatio recofigured as four BEA Tuxedo domais (TDomais). (Three of the domais are i the left-had box.) Figure 2-3 Domais Cofiguratio Modifyig the Applicatio Cofiguratio Files To recofigure the combied applicatio as TDomais, make the followig chages to the UBBCONFIG files: Chage MODEL to SHM. Remove the NETWORK sectio. Note: You ca use MP mode ad also write the NETWORK sectio i a multiple domai eviromet depedig o your specific applicatio eeds. Add domai-specific servers, for example DMADM, GWADM, ad GWTDOMAIN, to the SERVERS sectio. Usig the BEA Tuxedo Domais Compoet 2-9

46 2 Plaig ad Cofigurig ATMI Domais The followig code shows a sample coverted UBBCONFIG file. Listig 2-2 Coverted UBBCONFIG File *RESOURCES IPCKEY UID 7901 GID 601 PERM 0660 MAXACCESSERS 40 MAXSERVERS 35 MAXSERVICES 75 MAXCONV 10 MASTER SITE1 SCANUNIT 10 MODEL SHM LDBAL Y MAXGTT 100 MAXBUFTYPE 16 SCANUNIT 10 SANITYSCAN 5 BBLQUERY 50 BLOCKTIME 2 *MACHINES sfexpz *GROUPS DEFAULT: LMID=SITE1 TUXDIR= /home/mylogi/tuxroot APPDIR= /home/mylogi/creditapp ENVFILE= /home/mylogi/creditapp/envfile TLOGDEVICE= /home/mylogi/creditapp/tlog TLOGNAME=TLOG TUXCONFIG= /home/mylogi/creditapp/tuxcofig ULOGPFX= /home/mylogi/creditapp/ulog TYPE= type1 LMID=SITE1 BANKB1 GRPNO=1 TMSNAME=TMS_SQL TMSCOUNT=2 OPENINFO= TUXEDO/SQL:/home/mylogi/creditapp/crdtdl1:bakdb:readwrite BANKB2 GRPNO=2 BANKB3 GRPNO=3 BANKB4 GRPNO=4 DMADMGRP LMID=mach1 GRPNO= Usig the BEA Tuxedo Domais Compoet

47 Optio 2: Redefie the Applicatios as Separate BEA Tuxedo Domais *SERVERS DEFAULT: RESTART=Y MAXGEN=5 REPLYQ=Y CLOPT= -A GWADM SRVGRP=BANKB2 SRVID=30 REPLYQ = N RESTART = Y GRACE = 0 GWTDOMAIN SRVGRP=BANKB2 SRVID=31 REPLYQ = N RESTART = Y GRACE = 0 GWADM SRVGRP=BANKB3 SRVID=24 REPLYQ = N RESTART = Y GRACE = 0 GWTDOMAIN SRVGRP=BANKB3 SRVID=25 REPLYQ = N RESTART = Y GRACE = 0 GWADM SRVGRP=BANKB4 SRVID=20 REPLYQ = N RESTART = Y GRACE = 0 GWTDOMAIN SRVGRP=BANKB4 SRVID=21 REPLYQ = N RESTART = Y GRACE = 0 DMADM SRVGRP= DMADMGRP SRVID=50 REPLYQ = N RESTART = Y GRACE = 0 TLRA SRVGRP=BANKB1 SRVID=2 CLOPT= -A -- -T 100 BTADD SRVGRP=BANKB1 SRVID=3 ACCTA SRVGRP=BANKB1 SRVID=4 CRDT SRVGRP=BANKB1 SRVID=5 CRDTA SRVGRP=BANKB1 SRVID=6 *SERVICES DEFAULT: LOAD=50 INQUIRYA PRIO=50 WITHDRAWALA PRIO=50 OPEN_ACCT2 PRIO=40 OPENC PRIO=40 OPENCA PRIO=40 CLOSECA PRIO=40 BR_ADD PRIO=20 TLR_ADD PRIO=20 Usig the BEA Tuxedo Domais Compoet 2-11

48 2 Plaig ad Cofigurig ATMI Domais Addig DMCONFIG Files You also eed to create four DMCONFIG files, as show i the followig sample. Listig 2-3 Sample DMCONFIG File *DM_LOCAL_DOMAINS QDOM1 QDOM2 QDOM3 GWGRP=BANKB2 TYPE=TDOMAIN DOMAINID=QDOM1 BLOCKTIME=10 MAXDATALEN=56 MAXRDOM=89 DMTLOGDEV= /home/mylogi/creditapp/dmtlog AUDITLOG= /home/mylogi/creditapp/auditlog GWGRP=BANKB3 TYPE=TDOMAIN DOMAINID=QDOM2 BLOCKTIME=10 MAXDATALEN=56 MAXRDOM=89 DMTLOGDEV= /home/mylogi/creditapp/dmtlog AUDITLOG= /home/mylogi/creditapp/auditlog DMTLOGNAME= DMTLOG_TDOM2 GWGRP=BANKB4 TYPE=TDOMAIN DOMAINID=QDOM3 BLOCKTIME=10 MAXDATALEN=56 MAXRDOM=89 DMTLOGDEV= /home/mylogi/creditapp/dmtlog AUDITLOG= /home/mylogi/creditapp/auditlog DMTLOGNAME= DMTLOG_TDOM3 *DM_REMOTE_DOMAINS TDOM1 TYPE=TDOMAIN DOMAINID=TDOM Usig the BEA Tuxedo Domais Compoet

49 Sample Domais Applicatio: creditapp TDOM2 TYPE=TDOMAIN DOMAINID=TDOM2 TDOM3 *DM_TDOMAIN QDOM1 QDOM2 QDOM3 TDOM1 TDOM2 TDOM3 TYPE=TDOMAIN DOMAINID=TDOM3 NWADDR= 0x0002DEEF NWDEVICE= /dev/tcp NWADDR= 0x0002BEEF NWDEVICE= /dev/tcp NWADDR= 0x0002CEEF NWDEVICE= /dev/tcp NWADDR= 0x0002DEEF NWDEVICE= /dev/ull NWADDR= 0x0002BEEF D NWDEVICE= /dev/tcp NWADDR= 0x0002CEEF E NWDEVICE= /dev/tcp *DM_LOCAL_SERVICES WITHDRAWALA INQUIRYA OPENCA CLOSECA Sample Domais Applicatio: creditapp A sample applicatio, creditapp, is distributed with the BEA Tuxedo system. creditapp is a ruable versio of the hypothetical applicatio that was the basis for separatig bakapp ad the credit card applicatio ito domais, as discussed earlier i this topic. The applicatio is located i TUXDIR/apps/creditapp ad icludes the followig files. Usig the BEA Tuxedo Domais Compoet 2-13

50 2 Plaig ad Cofigurig ATMI Domais Listig 2-4 creditapp Files ACCT.ec ACCTA.ec AUDITC.c BAL.ec BALANCE.m BALANCEA.m BALC.ec BTADD.ec CBALANCE.m CCLOSE.m CDEPOSIT.m CLOSE.m COPEN.m CRDT.ec CRDTA.ec CRMENU.m CRMENU2.m CTRANSFER.m CWITHDRAW.m DEPOSIT.m DEPOSITA.m FILES HCBALANCE.m HCCLOSE.m HCLOSE.m HCOPEN.m HCWITHDRAW.m HELP.m HOPEN.m OPEN.m README RUNME RUNME.sh SETUP.sh TLR.ec TLR1.ec TLR2.ec TLR3.ec TLRA.ec TRANSFER.m WITHDRAW.m WITHDRAWA.m XFER.c appiit.c aud.h aud.v audit.c auditco.c bak.flds bak.flds.h bak.h cleaup.sh crbak.sh crbakdb.sh crdt_app.mk crdt_app2.mk crdt_app3.mk crdt_app4.mk crdt_flds.h crdtvar crdtvar2 credit.flds crtlog.sh crtlog2 crtlog2.sh domco1 domco2 domco3 domco4 driver.sh evfile.sh gedata.c getra.c hostmk listr populate.sh ru.sh setev ubbdom1 ubbdom2 ubbdom3 ubbdom4 util.c The creditapp README File The followig README file is from the creditapp directory. The README file documets a script that istalls ad rus creditapp. It has bee edited to iclude a few thigs that were ot icluded i the origial script. Listig 2-5 README File for creditapp SIMPLE BUILD PROCEDURE The creditapp applicatio is a ehacemet of the bakapp ad hostapp applicatios. The creditapp applicatio is desiged to be a four domai applicatio, so the software must be built o four machies. The RUNME.sh script will lead you through the ecessary steps. Step 1: Copy the Software for creditapp. Make a ew directory uder your $HOME directory ad copy all of the source files from <TUXDIR>/apps/creditapp ito that directory Usig the BEA Tuxedo Domais Compoet

51 Sample Domais Applicatio: creditapp TUXDIR is the root directory uder which your BEA TUXEDO System software is istalled. We call the ew directory $HOME /creditapp. The rest of the steps i this procedure are doe i the directory $HOME/creditapp. Step 2: O each of the remaiig three machies: Make a directory creditapp i a directory that ca be used for the applicatio. We call this directory $HOME/creditapp. Make a ote of the full directory path for $HOME/creditapp ad TUXDIR for each machie. These will be eeded by the RUNME.sh script. Step 3: O the master site execute the RUNME.sh script. The shell script RUNME.sh is a iteractive program desiged to lead you through iitializatio, bootig, shutdow ad cleaup of the four domai creditapp applicatio. The shell is iteractive ad requires o commad lie argumets. All you eed i the directory is the source from the TUXDIR/apps/creditapp directory that you copied i Step 1. You will be prompted to eter values for RSH ad RCP eviromet variables, or accept the defaults. IT IS VERY IMPORTANT THAT VALUES FOR RSH AND RCP BE ENTERED AS THEY ARE USED TO REMOTE COPY AND EXECUTE THE NECESSARY SCRIPTS. The followig eviromet variables are importat. The script picks up the values for TUXDIR ad APPDIR from your eviromet ad prompts you (i OPTION 4) for BLKSIZE: TUXDIR APPDIR BLKSIZE Root directory of the BEA TUXEDO System where you have istalled the software. Directory i which the creditapp applicatio resides. crdtvar.dm1 iitially is set to allow this to default to the curret workig directory, which agrees with our itetio to use $HOME/creditapp. This is the directory ito which you copied the creditapp files i Step 1. Logical blocksize for the database i bytes. Must be a itegral multiple of the physical page size of the computer (for example, 512 bytes or 4096 bytes). Whe you ivoke RUNME.sh you are show a meu with 10 optios (11 coutig quit ). Here is the list of choices: Usig the BEA Tuxedo Domais Compoet 2-15

52 2 Plaig ad Cofigurig ATMI Domais 1) Iitialize cofiguratio files ad makefiles. 2) Copy files to remote sites. 3) Build crdtapp cliets ad servers. 4) Create databases. 5) Geerate biary tuxcofig ad bdmcofig files. 6) Create Trasactio Log file. 7) Boot the applicatio. 8) Populate the database. 9) Shutdow the applicatio. 10) Cleaup IPC Resources, database files ad log files. q) Quit. To go through the complete process of buildig ad ruig the sample applicatio, start with choice No. 1. Whe the script completes a step, the meu is displayed for your ext choice. OPTION 1. Iitialize cofiguratio files ad makefiles. This optio sets up makefiles, UBBCONFIG ad DMCONFIG files that are ecessary for the applicatio. All questios must be aswered. ENTER the system ame: eter uame for machies you are usig begiig with the curret machie you are o. ENTER TUXDIR for each machie. ENTER APPDIR for each machie. Cotiue to aswer all queries. A example of 4 hexadecimal digits may be (beef, cfff, 6774, aeef). NOTE: EACH MACHINE MUST HAVE A UNIQUE HEX SEQUENCE. OPTION 2. Copies the files to the other domais i the cofiguratio. OPTION 3. Builds cliets ad servers o all machies. NOTE: CAREFULLY CHECK THAT THE BUILDS ARE COMPLETED SUCCESSFULLY ON EACH SITE. IF NECESSARY YOU MAY RUN THE BUILD YOURSELF. ON THE SPECIFIC SITE ENTER ohup make -f CRDT{$MACH}.mk Usig the BEA Tuxedo Domais Compoet

53 Sample Domais Applicatio: creditapp where ${MACH} is the uame for the machie you are buildig o. For example, ohup make -f CRDTtux1.mk2 OPTION 4. Builds the databases o each site. NOTE: ON EACH SITE MAKE SURE THE BLKSIZE VALUE IN files crdt${mach}.dm1 for the primary site or crdt${mach}.dm2 for the remote sites where ${MACH} is the uame for the machie you are buildig o ARE CORRECT FOR THAT SPECIFIC MACHINE OPTION 5. Geerates the tuxcofig ad bdmcofig files. All other optios are similar to bakapp. After OPTION 8 : Populate the database RUNNING CREDITAPP. Eter q to Quit the meu. ru At the respose : O each machie a script ru.sh exists. Execute ru.sh. Is this machie the Credit Card Authorizatio Ceter(y/)? If machie is the primary machie aswer y. If machie is ay other aswer. O the primary machie a differet meu will be see tha the other 3 machies. All Credit accouts exist o primary machie ad all machies ca access ay accout. ACCOUNTS Usig the BEA Tuxedo Domais Compoet 2-17

54 2 Plaig ad Cofigurig ATMI Domais Machies 2,3,4 are the ehaced bakapp applicatio. ACCOUNTS exist o machie 2 ACCOUNTS exist o machie 3 ACCOUNTS exist o machie 4 All processig is doe usig the /DOMAIN software. A tail -f of the ULOG will show the actual processig of the requests. O the machie that will process the request eter : tail -f ULOG where is today s date. Cofigurig a Domais Eviromet To cofigure a Domais eviromet, a admiistrator eeds to specify all the iformatio a BEA Tuxedo domai eeds to kow about other domais. This iformatio icludes services imported from other domais, addressig ad security parameters for cotactig remote domais, access cotrol lists, services exported to these domais, whether data-depedet routig is used, ad parameters for cotrollig access to exported services. This iformatio is defied i the UBBCONFIG cofiguratio file ad i the DMCONFIG cofiguratio file Usig the BEA Tuxedo Domais Compoet

55 Cofigurig a Domais Eviromet Cofigurig a Sample Domais Applicatio (simpapp) The Domais example illustrated i the followig figure cosists of two applicatios: lapp, a local applicatio, ad rapp, a remote applicatio. Both are based o the simpapp example provided with the BEA Tuxedo system. lapp is cofigured to allow its cliets to access a service called TOUPPER, which is advertised i rapp. Figure 2-4 Local ad Remote Applicatios i simpapp Usig the BEA Tuxedo Domais Compoet 2-19

56 2 Plaig ad Cofigurig ATMI Domais Cofiguratio Tasks The followig tasks are required to cofigure the simpapp domai cosistig of two applicatios: lapp (the local applicatio) ad rapp (the remote applicatio) Usig the BEA Tuxedo Domais Compoet

57 How to Set Eviromet Variables for lapp How to Set Eviromet Variables for lapp You eed to set the followig eviromet variables for the applicatio to be cofigured successfully: TUXDIR the BEA Tuxedo system root directory (for example, /opt/tuxedo) TUXCONFIG the applicatio cofiguratio file (for example, lapp.tux) BDMCONFIG the domai gateway cofiguratio file (for example, lapp.bdm) PATH must iclude TUXDIR/bi LD_LIBRARY_PATH must iclude TUXDIR/lib (this pathame varies, depedig o your operatig system) Example $ TUXDIR=/opt/tuxedo $ TUXCONFIG=/home/lapp/lapp.tux $ BDMCONFIG=/home/lapp/lapp.dom $ PATH=$TUXDIR/bi:$PATH $ LD_LIBRARY_PATH=$TUXDIR/lib:$LD_LIBRARY_PATH $ export TUXDIR TUXCONFIG BDMCONFIG PATH LD_LIBRARY_PATH Usig the BEA Tuxedo Domais Compoet 2-21

58 2 Plaig ad Cofigurig ATMI Domais How to Defie the Domais Eviromet for lapp (i the ubbcofig File) For the sample local applicatio cofiguratio file, lapp.ubb, oly the required parameters are defied. Default settigs are used for the other parameters. Two server groups are defied: The first group cotais the Domais admiistrative server (DMADM). The secod group cotais the gateway admiistrative server (GWADM) ad the domai gateway (GWTDOMAIN). Note: For a gateway type other tha GWTDOMAIN, a executable other tha GWTDOMAIN must be used. Refer to the BEA elik for Maiframe documetatio ad Usig the BEA Tuxedo TOP END Domai Gateway for additioal iformatio. Server Defiitios DMADM the Domais admiistrative server eables ru-time modificatio of the cofiguratio iformatio, required by domai gateway groups, that resides i the biary Domais cofiguratio file. DMADM supports a list of registered gateway groups. There must be oly oe istace of DMADM per Domais applicatio. GWADM the gateway admiistrative server eables ru-time admiistratio of a particular domai gateway group. This server gets Domais cofiguratio iformatio from the DMADM server. It also provides admiistrative fuctioality ad trasactio loggig for the gateway group. GWTDOMAIN the Domais gateway server eables access to ad from remote Domais, allowig iteroperability of two or more BEA Tuxedo domais. Iformatio about the local ad remote services it eeds to export ad import is icluded i the Domais cofiguratio file. The Domais gateway server should always be cofigured with REPLYQ=N Usig the BEA Tuxedo Domais Compoet

59 How to Defie the Domais Eviromet for lapp (i the ubbcofig File) Example of a Applicatio Cofiguratio File for lapp Listig 2-6 Example of a Applicatio Cofiguratio File (lapp.ubb) lapp.ubb *RESOURCES IPCKEY MASTER MODEL LAPP SHM *MACHINES giselle LMID=LAPP TUXDIR= /opt/tuxedo APPDIR= /home/lapp TUXCONFIG= /home/lapp/lapp.tux *GROUPS LDMGRP LGWGRP GRPNO=1 LMID=LAPP GRPNO=2 LMID=LAPP *SERVERS DMADM GWADM GWTDOMAIN SRVGRP=LDMGRP SRVID=1 SRVGRP=LGWGRP SRVID=1 SRVGRP=LGWGRP SRVID=2 REPLYQ=N *SERVICES Usig the BEA Tuxedo Domais Compoet 2-23

60 2 Plaig ad Cofigurig ATMI Domais How to Defie Domais Parameters for lapp (i the DMCONFIG File) For the sample local Domai gateway cofiguratio file, lapp.dom, oly the required parameters are defied. Default settigs are used for optioal parameters. The DM_LOCAL_DOMAIN sectio idetifies the local domais ad their associated gateway groups. This sectio has oe etry, LAPP, ad specifies the followig parameters required for the domai gateway processes i that group: GWGRP specifies the ame of the gateway server group as specified i the applicatio. TYPE of TDOMAIN idicates that the local domai will be commuicatig with aother BEA Tuxedo domai. This parameter idicates the protocol used by the gateways. Other optios iclude SNA, OSI TP, TOP END Domai gateway, TCP for CICS, ad TCP for IMS. DOMAINID idetifies the ame of the domai gateway ad must be uique across all domais. The DM_REMOTE_DOMAINS sectio idetifies the kow set of remote domais ad their characteristics. This sectio has oe etry (RAPP). TYPE is used to classify the type of domais. DOMAINSID is a uique domai idetifier. The DM_TDOMAIN sectio defies the addressig iformatio required by the BEA Tuxedo Domais compoet. Followig are etries i the sectio for each local ad remote domai specified i this cofiguratio file: NWADDR specifies either the etwork address at which coectios will be accepted from other BEA Tuxedo domais (local domai etry), or the etwork address at which coectios to other BEA Tuxedo domais will be made (remote domai etry). The DM_LOCAL_SERVICES sectio provides iformatio about the services that are exported. This sectio of our sample file has o etries because o services are beig exported Usig the BEA Tuxedo Domais Compoet

61 How to Defie Domais Parameters for lapp (i the DMCONFIG File) The DM_REMOTE_SERVICES sectio provides iformatio about the services that are imported. The TOUPPER service is imported so that it ca be accessed by cliets i the local domai. Example of a Domai Gateway Cofiguratio File for lapp Listig 2-7 Example of a Domai Gateway Cofiguratio File (lapp.dom) lapp.dom *DM_LOCAL_DOMAINS LAPP GWGRP=LGWGRP TYPE=TDOMAIN DOMAINID= " *DM_REMOTE_DOMAINS RAPP TYPE=TDOMAIN DOMAINID= " *DM_TDOMAIN LAPP RAPP NWADDR= //mach1:5000" NWADDR= //mach2:5000" *DM_LOCAL_SERVICES *DM_REMOTE_SERVICES TOUPPER Usig the BEA Tuxedo Domais Compoet 2-25

62 2 Plaig ad Cofigurig ATMI Domais How to Compile Applicatio ad Domais Gateway Cofiguratio Files for lapp The local applicatio cofiguratio file (lapp.ubb) cotais the iformatio ecessary to boot the local applicatio. You must compile this file ito a biary data file (lapp.tux) by ruig tmloadcf(1). The local domai gateway cofiguratio file (lapp.dom) cotais the iformatio used by the domai gateway for oe domai for commuicatio with other domais. You must compile this file ito a biary data file (lapp.bdm) by ruig dmloadcf(1). To compile both cofiguratio files, complete the procedure show i the followig sample sessio. $ cd /home/lapp $ TUXCONFIG=/home/lapp/lapp.tux; export TUXCONFIG $ tmloadcf -y lapp.ubb $ BDMCONFIG=/home/lapp/lapp.dom; export BDMCONFIG $ dmloadcf -y lapp.dom Oce you create both the local ad remote domais, you ca the boot the applicatio usig tmboot(1). The order i which the two domais are booted does ot matter. Moitor the applicatios with dmadmi(1). Oce both applicatios are booted, a cliet i the local applicatio ca call the TOUPPER service residig i the remote applicatio. $ tmboot -y 2-26 Usig the BEA Tuxedo Domais Compoet

63 How to Set Eviromet Variables for rapp How to Set Eviromet Variables for rapp You must set the followig eviromet variables for a applicatio to be cofigured successfully: TUXDIR the BEA Tuxedo system root directory (for example, /opt/tuxedo) TUXCONFIG the full path ame of the applicatio cofiguratio file (for example, rapp.tux) BDMCONFIG the full path ame of the domai gateway cofiguratio file (for example, rapp.bdm) PATH must iclude TUXDIR/bi LD_LIBRARY_PATH must iclude TUXDIR/lib (this pathame varies, depedig o your operatig system) Example $ TUXDIR=/opt/tuxedo $ TUXCONFIG=/home/rapp/rapp.tux $ BDMCONFIG=/home/rapp/rapp.dom $ PATH=$TUXDIR/bi:$PATH $ LD_LIBRARY_PATH=$TUXDIR/lib:$LD_LIBRARY_PATH $ export TUXDIR PATH LD_LIBRARY_PATH TUXCONFIG BDMCONFIG Usig the BEA Tuxedo Domais Compoet 2-27

64 2 Plaig ad Cofigurig ATMI Domais How to Defie the Domais Eviromet for rapp (i the UBBCONFIG File) For the sample remote applicatio cofiguratio file, rapp.ubb, oly the required parameters are defied. Default settigs are used for optioal parameters. The followig three server groups are defied: The first server group (SRVGP=RDMGRP) cotais the Domais admiistrative server (DMADM). The secod server group (SRVGP=RGWGRP) cotais the gateway admiistrative server, GWADM, ad the domai gateway, GWTDOMAIN. The third server group (SRVGP=APPGRP) cotais the applicatio server simpserv. The followig four servers are defied: DMADM Domais admiistrative server GWADM gateway admiistrative server GWTDOMAIN Domais gateway server simpserv applicatio server for simpapp that advertises the TOUPPER service, which coverts strigs from lowercase to uppercase characters 2-28 Usig the BEA Tuxedo Domais Compoet

65 How to Defie the Domais Eviromet for rapp (i the UBBCONFIG File) Example of a Applicatio Cofiguratio File for rapp Listig 2-8 Example of a Applicatio Cofiguratio File (rapp.ubb) rapp.ubb *RESOURCES IPCKEY MASTER MODEL RAPP SHM *MACHINES juliet LMID=RAPP TUXDIR= /opt/tuxedo APPDIR= /home/rapp TUXCONFIG= /home/rapp/rapp.tux *GROUPS RDMGRP RGWGRP APPGRP GRPNO=1 LMID=RAPP GRPNO=2 LMID=RAPP GRPNO=3 LMID=RAPP *SERVERS DMADM GWADM GWTDOMAIN simpserv SRVGRP=RDMGRP SRVID=1 SRVGRP=RGWGRP SRVID=1 SRVGRP=RGWGRP SRVID=2 REPLYQ=N SRVGRP=APPGRP SRVID=1 *SERVICES TOUPPER Usig the BEA Tuxedo Domais Compoet 2-29

66 2 Plaig ad Cofigurig ATMI Domais How to Defie Domais Parameters for rapp (i the DMCONFIG File) For the sample remote Domai gateway cofiguratio file, rapp.dom, oly the required parameters are defied. Default settigs are used for optioal parameters. This cofiguratio file is similar to the local Domais gateway cofiguratio file. The differece is that the two files list differet services to be exported ad imported. The DM_LOCAL_SERVICES sectio provides iformatio about the services exported by each local domai. I this example, the TOUPPER service is exported ad icluded i the DM_LOCAL_SERVICES sectio. No service is imported so there are o etries i the DM_REMOTE_SERVICES sectio of our sample file. Example of a Domai Gateway Cofiguratio File for rapp Listig 2-9 Example of a Domai Gateway Cofiguratio File (rapp.dom) rapp.dom *DM_LOCAL_DOMAINS RAPP GWGRP=RGWGRP TYPE=TDOMAIN DOMAINID= " *DM_REMOTE_DOMAINS LAPP TYPE=TDOMAIN DOMAINID= " *DM_TDOMAIN RAPP LAPP NWADDR= //mach2:5000" NWADDR= //mach1:5000" 2-30 Usig the BEA Tuxedo Domais Compoet

67 How to Compile Applicatio ad Domai Gateway Cofiguratio Files for rapp *DM_LOCAL_SERVICES TOUPPER *DM_REMOTE_SERVICES How to Compile Applicatio ad Domai Gateway Cofiguratio Files for rapp The remote applicatio cofiguratio file (rapp.ubb) cotais the iformatio used by the domai gateway for oe domai, for commuicatio with other domais. You must compile this file ito a biary data file (rapp.tux). The remote domai gateway cofiguratio file (rapp.dom) cotais the iformatio used by domai gateways to iitialize the cotext required for commuicatios with other domais. This cofiguratio file is similar to the local domai gateway cofiguratio file. The differece is that the two files list differet services to be exported ad imported. You must compile this file ito a biary data file (rapp.bdm). $ cd /home/rapp $ TUXCONFIG=/home/rapp/rapp.tux; export TUXCONFIG $ tmloadcf -y rapp.ubb $ BDMCONFIG=/home/rapp/rapp.dom; export BDMCONFIG $ dmloadcf -y rapp.dom Oce you create both the local ad remote domais, you ca the boot the applicatio usig tmboot(1). The order i which the two domais are booted does ot matter. Moitor the applicatios with dmadmi(1). Oce both applicatios are booted, a cliet i the local applicatio ca call the TOUPPER service residig i the remote applicatio. $ tmboot -y See Also What Is the Domais Cofiguratio File? o page 1-19 How to Compress Data Betwee Domais o page 2-32 How to Route Service Requests to Remote Domais o page 2-32 Usig the BEA Tuxedo Domais Compoet 2-31

68 2 Plaig ad Cofigurig ATMI Domais Covertig the Domais Cofiguratio File o page 1-21 DMCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece UBBCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece How to Compress Data Betwee Domais Data set betwee domais ca be compressed for faster performace. To cofigure compressio, set the CMPLIMIT parameter i DMCONFIG. See Also DMCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece Compressig Data Over a Network o page 4-2 i Admiisterig a BEA Tuxedo Applicatio at Ru Time How to Route Service Requests to Remote Domais Data-depedet routig iformatio used by gateways to sed service requests to specific remote domais is provided i the DM_ROUTING sectio of the DMCONFIG file. The FML32, VIEW32, FML, VIEW, X_C_TYPE, ad X_COMMON typed buffers are supported. To create a routig table for a domai, specify the followig: Buffer type for which the routig etry is valid 2-32 Usig the BEA Tuxedo Domais Compoet

69 How to Route Service Requests to Remote Domais Name of the routig etry ad field Rages ad associated remote domai ames of the routig field. The followig table describes these fields. Routig Table Field Buffer type Descriptio A list of types ad subtypes of data buffers for which this routig etry is valid. The types may be icluded: FML32, VIEW32, FML, VIEW, X_C_TYPE, ad X_COMMON. No subtype ca be specified for type FML; subtypes are required for the other types. The * (or wildcard) value is ot allowed. Duplicate type/subtype pairs caot be specified for the same routig criteria ame; oe criteria ame ca be specified i multiple routig etries as log as the type/subtype pairs are uique. If multiple buffer types are specified for a sigle routig etry, the data types of the routig field for all buffer types must be the same. Valid values for type are: [:subtype1[,subtype2...]] [;type2[:subtype3[,subtype4... ]]]... The maximum total legth of 32 type/subtype combiatios is 256 characters. Valid values for subtype may ot iclude semicolos, colos, commas, or asterisks. Example: FML Domai routig criteria Routig field ame The ame (idetifier) of the routig etry. A valid value is ay strig of 1-15 characters, iclusive. Example: ROUTTAB1 The ame of the routig field. It is assumed that the value of this field is a ame idetified i a FML field table (for FML buffers) or a FML VIEW table (for VIEW, X_C_TYPE, or X_COMMON buffers). A valid value is a idetifier strig that is 1-30 characters, iclusive. Example: FIELD1 Usig the BEA Tuxedo Domais Compoet 2-33

70 2 Plaig ad Cofigurig ATMI Domais Routig Table Field Rages Descriptio (Cotiued) A value comprised of a set of umbers (that must have umeric values) ad a alphaumeric strig (that must have strig values) associated with remote domai ames (RDOM) for the routig field. The routig field ca be of ay data type supported i FML. Strig rage values for strig, carray, ad character field types must meet the followig criteria: Placed iside a pair of sigle quotes ad ot preceded by a sig. Short ad log iteger values are a strig of digits, optioally preceded by a plus or mius sig. Floatig poit umbers are of the form accepted by the C compiler or atof()as follows: a optioal sig, the a strig of digits optioally cotaiig a decimal poit, the a optioal e or E followed by a optioal sig or space, followed by a iteger. Whe a field value matches a rage, the associated RDOM value specifies the remote domais to which the request should be routed. A RDOM value of * idicates that the request ca go to ay remote domai kow by the gateway group. Valid values for this field are a comma-separated ordered list of rage/rdom pairs where a rage is oe of two types: (a) a sigle value (siged umeric value or character strig i sigle quotes); or (b) a rage of the form lower-upper (where lower ad upper are both siged umeric values or character strigs i sigle quotes). Note that lower must be less tha or equal to upper. Withi a rage/rdom pair, the rage is separated from the RDOM by a colo ( : ). MIN ca be used to idicate the miimum value for the data type of the associated FIELD: For strigs ad carrays, it is the ull strig For character fields, it is 0 For umeric values, it is the miimum umeric value that ca be stored i the field. MAX ca be used to idicate the maximum value for the data type of the associated FIELD: For strigs ad carrays, it is a ulimited strig of octal-255 characters For a character field, it is a sigle octal-255 character For umeric values, it is the maximum umeric value that ca be stored i the field. Thus, MIN - -5 is all umbers less tha or equal to -5; ad 6 - MAX is the set of all umbers greater tha or equal to 6. The metacharacter * (wildcard) i the rage positio idicates ay values ot covered by other rages previously see i the etry; oe wildcard rage is allowed per etry, which should be listed last i the field (rages followig it are igored). Example: 1-100:REMDOM Usig the BEA Tuxedo Domais Compoet

71 Settig Up Security i Domais Settig Up Security i Domais The BEA Tuxedo ATMI eviromet provides the followig applicatio security mechaisms: Autheticatio proves the stated idetity of users or system processes; safely remembers ad trasports idetity iformatio; ad makes idetity iformatio available whe eeded. The default autheticatio plug-i provides security at three levels: o autheticatio (NONE), applicatio password (AP_PW), ad user-level autheticatio (USER_AUTH). Authorizatio cotrols access to resources based o idetity or other iformatio. The default authorizatio plug-i provides security at two levels: optioal access cotrol lists (ACL) ad madatory access cotrol lists (MANDATORY_ACL). Auditig safely collects, stores, ad distributes iformatio about operatig requests ad their outcomes. Default auditig security is implemeted by the BEA Tuxedo EvetBroker ad userlog (ULOG) features. Ecryptio security mechaisms to covert data to coded format that is uitelligible to users. The default ecryptio is RC4 symmetric key ecryptio. Security Plug-i Iterface allows istallatio of third-party security systems such as custom autheticatio, authorizatio, ad auditig. The plug-i iterface is available to applicatios ruig BEA Tuxedo release 7.1 or later software. For iformatio o settig up security i domais usig the security plug-i iterface, see Establishig a Lik Betwee Domais o page 2-24 i Usig Security i ATMI Applicatios. Usig the BEA Tuxedo Domais Compoet 2-35

72 2 Plaig ad Cofigurig ATMI Domais Impact of BEA Tuxedo Applicatio Security o Domais Security The BEA Tuxedo security mechaisms provided for idividual applicatios ad those provided for Domais cofiguratios are relatively idepedet but compatible: The BEA Tuxedo ATMI eviromet provides the followig security mechaisms for Domais cofiguratios: l l l autheticatio of remote domais access cotrol o exported local services for remote domais ecryptio mechaisms to protect iterdomai commuicatio If BEA Tuxedo applicatio security is set to USER_AUTH or above, ad the ACL_POLICY ad CREDENTIAL_POLICY parameters are set to GLOBAL i the DM_REMOTE_DOMAINS sectio of the DMCONFIG, the user IDs flow across domais with requests. ACL checkig is performed o the user IDs. If BEA Tuxedo applicatio security is set to USER_AUTH or above, ad the ACL_POLICY ad CREDENTIAL_POLICY parameters are set to LOCAL i the DM_REMOTE_DOMAINS sectio of the DMCONFIG, the user IDs do ot flow across domais with requests. ACL checkig is hadled via the Domai ID of the requestig domai. Eve if you assig a security level of NONE to your BEA Tuxedo applicatio, you ca still set the Domais coectio security to DM_PW. Note, however, that i order to use a applicatio password i a Domais cofiguratio, you must have already set a value of APP_PW (or higher: USER_AUTH, ACL, or MANDATORY_ACL) for the security level i each participatig applicatio Usig the BEA Tuxedo Domais Compoet

73 Settig Up Security i Domais Domais Security Mechaisms Because distict domais may exist uder differet owership, the ative BEA Tuxedo applicatio password scheme may ot, of itself, provide sufficiet security. Domais, therefore, provides additioal security mechaisms: Access Cotrol Lists restricts availability of resources i a local domai to a list of selected remote domais. You cofigure this security level i the DM_ACCESS_CONTROL sectio of DMCONFIG. Domais Autheticatio techiques are required to esure the proper idetity of each remote domai. Domais provides three levels of password security: NONE specifies o autheticatio; APP_PW is autheticatio usig the applicatio password, which must match o the two domais; ad DM_PW, which is autheticatio usig specific passwords per local/remote domai pair. Each of these is selected by settig the SECURITY parameter i the DM_LOCAL_DOMAINS sectio for the local domai access poit ivolved to the required level (NONE, APP_PW, DM_PW). Lik-Level Ecryptio you ca use ecryptio across domais to esure data privacy. I this way, a etwork-based eavesdropper caot lear the cotet of BEA Tuxedo messages or applicatio-geerated messages flowig from oe domai gateway to aother. You cofigure this security mechaism by settig the MINENCRYPTBITS ad MAXENCRYPTBITS parameters i the DMCONFIG file. Local Domais Access restricts local services to remote domais. If a service is ot exported to remote domais, it is simply uavailable to them. A service is exported by placig a etry i the DM_LOCAL_SERVICES sectio of the DMCONFIG file for the service. User Idetity Mappig to Maiframes provides a mechaism whereby user idetities withi a domai ca be mapped to ad from exteral user idetities. This mechaism is curretly used by BEA elik for Maiframe-SNA to map to ad from RACF (remote access cotrol facility) user ames o IBM LU6.2 maiframes. To use this mechaism, refer to the followig dmadmi cofiguratio commads: l addumap add local user mappigs to remote user mappigs for a local/remote domai pair. Mappigs are defied to be iboud, outboud, or both. Usig the BEA Tuxedo Domais Compoet 2-37

74 2 Plaig ad Cofigurig ATMI Domais l l l l addusr add remote userames ad passwords to the remote user ad password tables of a remote domai. delumap delete local to remote user mappigs for a local/remote domai pair. delusr delete remote userames ad passwords from the remote user ad password tables of a remote domai. modusr chage remote passwords i the password tables of a remote domai. See Also How to Create a Domais Access Cotrol List (ACL) o page 2-39 How to Set Up Domais Autheticatio o page 2-42 Examples of Codig Security Betwee Domais o page 2-44 dmadmi(1)i the BEA Tuxedo Commad Referece 2-38 Usig the BEA Tuxedo Domais Compoet

75 How to Create a Domais Access Cotrol List (ACL) How to Create a Domais Access Cotrol List (ACL) To create a domai ACL, you must specify the ame of the domai ACL ad a list of the remote domais that are part of the list (the Domai Import VIEW List) i the DM_ACCESS_CONTROL sectio of the DMCONFIG file. The followig table describes these two fields. Domai ACL Field Domai ACL ame Remote Domai list Descriptio The ame of this ACL. A valid ame cosists of a strig of 1-30 characters, iclusive. It must be pritable ad it may ot iclude a colo, a poud sig, or a ewlie character. Example: ACLGRP1 The list of remote domais that are grated access i this access cotrol list. A valid value i this field is a set of oe or more comma-separated remote domai ames. Examples: REMDOM1,REMDOM2,REMDOM3 Usig Stadard BEA Tuxedo Access Cotrol Lists with Imported Remote Services A remote service imported from a remote domai is viewed simply as a service withi a BEA Tuxedo domai. The stadard BEA Tuxedo ACL mechaism the, ca be used to restrict access to this service by particular groups of users. For iformatio o usig BEA Tuxedo access cotrol lists, refer to the followig etries i the BEA Tuxedo Commad Referece: tpacladd(1), tpaclmod(1), tpacldel(1), tpusradd(1), tpusrmod(1), tpusrdel(1), tpgrpadd(1), tpgrpmod(1), ad tpgrpdel(1). Usig the BEA Tuxedo Domais Compoet 2-39

76 2 Plaig ad Cofigurig ATMI Domais Settig the ACL Policy for a Remote Domai As the admiistrator, you ca use the followig cofiguratio parameters to set ad cotrol the access cotrol list (ACL) policy for remote domais ruig BEA Tuxedo release 7.1 or later software. Parameter Name Descriptio Settig ACL_POLICY i DMCONFIG (TA_DMACLPOLICY i DM_MIB) May appear i the DM_REMOTE_DOMAINS sectio of the DMCONFIG file for each remote domai access poit. Its value for a particular remote domai access poit determies whether or ot the local domai gateway modifies the idetity of service requests received from the remote domai.* LOCAL or GLOBAL. Default is LOCAL. LOCAL meas that the local domai modifies the idetity of service requests received from this remote domai to the pricipal ame specified i the LOCAL_PRINCIPAL_NAME parameter for this remote domai. GLOBAL meas that the local domai uses ay credetial it might receive from the remote domai o iboud service requests. If o credetial is received from the remote domai the the service request will be forwarded to the service without credetials (which will usually fail). Note: This parameter cotrols whether or ot the local domai accepts a credetial from a remote domai. A parameter related to this oe is CREDENTIAL_POLICY, which cotrols whether or ot a local domai seds credetials to the remote domai. LOCAL_PRINCIPAL_ NAME i DMCONFIG (TA_DMLOCALPRINC IPALNAME i DM_MIB) May appear i the DM_REMOTE_DOMAINS sectio of the DMCONFIG file for each remote domai access poit. If the ACL_POLICY parameter is set (or defaulted) to LOCAL for a particular remote domai access poit, the local domai gateway modifies the idetify of service requests received from the remote domai to the pricipal ame specified i LOCAL_PRINCIPAL_NAME characters. If ot specified, the pricipal ame defaults to the DOMAINID strig for the remote domai access poit. * A remote domai access poit is also kow as a RDOM (proouced are dom ) or simply remote domai Usig the BEA Tuxedo Domais Compoet

77 How to Create a Domais Access Cotrol List (ACL) For more iformatio about ACL Policy, refer to Chapter 2, Admiisterig Security, i Usig Security i ATMI Applicatios. Settig the Credetial Policy for a Remote Domai As the admiistrator, you ca use the followig cofiguratio parameters to set ad cotrol the credetial policy for remote domais ruig BEA Tuxedo release 8.0 or later software. Parameter Name Descriptio Settig CREDENTIAL_POLICY i DMCONFIG (TA_DMCREDENTIAL POLICY i DM_MIB) May appear i the DM_REMOTE_DOMAINS sectio of the DMCONFIG file for each remote domai access poit. Its value for a particular remote domai access poit determies whether or ot the local domai gateway modifies the idetity of service requests received from the remote domai.* LOCAL or GLOBAL. Default is LOCAL. If the policy is LOCAL the the domai will ot attach the credetials of the user that origiated a request with the ivocatio to the remote domai. If the policy is GLOBAL the the domai will attach the credetials of the user that origiated a request with the ivocatio to the remote domai. Note: This parameter cotrols whether or ot user credetials are set to a remote domai. A parameter related to this oe is ACL_POLICY, which cotrols whether or ot icomig credetials are accepted by a domai. * A remote domai access poit is also kow as a RDOM (proouced are dom ) or simply remote domai. For more iformatio about Credetial Policy, refer to Chapter 2, Admiisterig Security, i Usig Security i ATMI Applicatios. Usig the BEA Tuxedo Domais Compoet 2-41

78 2 Plaig ad Cofigurig ATMI Domais How to Set Up Domais Autheticatio Domai gateways ca be made to autheticate icomig coectios requested by remote domais ad outgoig coectios requested by local domais. The autheticatio mechaism is optioal ad compatible with the BEA Tuxedo mechaism specified i the TUXCONFIG file. Applicatio admiistrators ca defie whe security should be eforced for icomig coectios from remote domais. You ca specify the level of security used by a particular local domai by settig the SECURITY parameter i the DM_LOCAL_DOMAINS sectio of the DMCONFIG file. There are three levels of password security: No Security (usig the NONE optio) icomig coectios from remote domais are ot autheticated. Applicatio Password (usig the APP_PW optio) icomig coectios from remote domais are autheticated usig the applicatio password defied i the TUXCONFIG file. The BEA Tuxedo applicatio password is admiistered with tmloadcf(1), which prompts for the password whe the SECURITY optio is eabled i the TUXCONFIG file. The password is automatically propagated with the TUXCONFIG file to the other machies i the cofiguratio. You ca update the password dyamically usig the tmadmi commad. Remote Domais Password (usig the DM_PW optio) BEA Tuxedo Domais uses this feature to eforce security betwee two or more BEA Tuxedo domais. Coectios betwee the local ad remote domais are autheticated usig passwords defied i the DM_PASSWORDS sectio of the BDMCONFIG file. These passwords are added to the biary cofiguratio file after dmloadcf has bee ru, usig the passwd subcommad of the dmadmi(1) commad. Each etry cotais the password used by a remote domai to access a particular local domai ad the password required by the local domai, i tur, to access the remote domai. If the SECURITY parameter is ot set i TUXCONFIG (that is, if it defaults to NONE or if it is set explicitly to NONE), the Domais cofiguratio ca still require the Domai gateways to eforce security at the DM_PW level. If the DM_PW optio is selected, the each remote domai must have a password defied i the DM_PASSWORDS sectio of the BDMCONFIG file. I other words, icomig coectios from remote domais without a password are rejected by domai gateways Usig the BEA Tuxedo Domais Compoet

79 How to Set Up Domais Autheticatio T_DM_PASSWORDS MIB Class Defiitios The T_DM_PASSWORDS class represets cofiguratio iformatio for iter-domai autheticatio through local ad remote access poits of type TDOMAIN. The T_DM_PASSWORDS class cotais the followig etries for each remote domai. TA_DMLACCESSPOINT the ame of the local domai access poit to which the password applies. TA_DMRACCESSPOINT the ame of the remote domai access poit to which the password applies. TA_DMLPWD the local password used to autheticate coectios betwee the local domai access poit (idetified by TA_DMLACCESSPOINT) ad the remote domai access poit (idetified by TA_DMRACCESSPOINT). TA_DMRPWD the remote password used to autheticate coectios betwee the remote domai access poit (idetified by TA_DMRACCESSPOINT) ad the local domai access poit (idetified by TA_DMLACCESSPOINT). Note: Passwords are stored securely i ecrypted format. Settig Domais Passwords BEA Tuxedo Domais passwords (DM_PW) are set usig the dmadmi(1) commad, as follows: passwd [-r] local_domai_ame remote_domai_ame This commad prompts the admiistrator for ew passwords for the specified local ad remote domais. See Also Examples of Codig Security Betwee Domais o page 2-44 dmadmi(1) i the BEA Tuxedo Commad Referece Usig the BEA Tuxedo Domais Compoet 2-43

80 2 Plaig ad Cofigurig ATMI Domais DMCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece DM_MIB(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece Examples of Codig Security Betwee Domais The SECURITY parameter i the DM_LOCAL_DOMAINS sectio of the DMCONFIG file specifies the security type of a local domai. If autheticatio is required, it is doe every time a coectio is established betwee the local domai ad a remote domai. If the security types of the two domais are icompatible, or if the passwords do ot match, the coectio fails. Example 1: Settig Security to NONE If SECURITY is set to NONE for a local domai, icomig coectio attempts are ot autheticated. Eve with SECURITY set to NONE, a local domai ca still coect to remote domais that have SECURITY set to DM_PW, but before such a coectio ca be established, you must defie the passwords o both sides by ruig dmadmi(1) or by usig DM_MIB(5). Listig 2-10 Settig Security to NONE for Both Applicatio ad Domais DOM1: SECURITY i UBBCONFIG set to NONE SECURITY i DMCONFIG set to NONE DOM2: SECURITY i UBBCONFIG set to NONE SECURITY i DMCONFIG set to DM_PW 2-44 Usig the BEA Tuxedo Domais Compoet

81 Examples of Codig Security Betwee Domais I this example, DOM1 is ot eforcig ay security but DOM2 is eforcig DM_PW security. O the iitiator side, the pertiet attributes i UBBCONFIG ad DMCONFIG are set as follows: UBBCONFIG SECURITY=NONE DMCONFIG *DM_LOCAL_DOMAINS DOM1 DOMAINID=DOM1 SECURITY=NONE *DM_REMOTE_DOMAINS DOM2 DOMAINID= DOM2 O the respoder side, the pertiet attributes i UBBCONFIG ad DMCONFIG are set as follows: UBBCONFIG SECURITY=NONE DMCONFIG *DM_LOCAL_DOMAINS DOM2 DOMAINID=DOM2 SECURITY=DM_PW *DM_REMOTE_DOMAINS DOM1 DOMAINID= DOM1 After the required attributes have bee set i the TUXCONFIG ad BDMCONFIG files, boot the applicatios o DOM1 ad DOM2. O DOM1: dmadmi passwd DOM1 DOM2 Eter Local Domai Password:foo1 Reeter Local Domai Password:foo1 Eter Remote Domai Password:foo2 Reeter Remote Domai Password:foo2 O DOM2: dmadmi passwd DOM2 DOM1 Eter Local Domai Password:foo2 Reeter Local Domai Password:foo2 Eter Remote Domai Password:foo1 Reeter Remote Domai Password:foo1 Usig the BEA Tuxedo Domais Compoet 2-45

82 2 Plaig ad Cofigurig ATMI Domais Oce passwords have bee created o both domais, a coectio ca be established ad services ca be ivoked o the remote domai. Listig 2-11 Settig Applicatio Security to NONE ad Domais Security to DM_PW O the iitiator side, the pertiet attributes i UBBCONFIG ad DMCONFIG are set as follows: UBBCONFIG SECURITY=NONE DMCONFIG *DM_LOCAL_DOMAINS DOM1 DOMAINID=DOM1 SECURITY=DM_PW *DM_REMOTE_DOMAINS DOM2 DOMAINID= DOM2 O the respoder side, the pertiet attributes i UBBCONFIG ad DMCONFIG are set as follows: UBBCONFIG SECURITY=NONE DMCONFIG *DM_LOCAL_DOMAINS DOM2 DOMAINID=DOM2 SECURITY=DM_PW *DM_REMOTE_DOMAINS DOM1 DOMAINID= DOM1 After the required attributes have bee set i the TUXCONFIG ad BDMCONFIG files, boot the applicatios o DOM1 ad DOM2: O DOM1: dmadmi passwd DOM1 DOM2 Eter Local Domai Password:foo1 Reeter Local Domai Password:foo1 Eter Remote Domai Password:foo2 Reeter Remote Domai Password:foo Usig the BEA Tuxedo Domais Compoet

83 Examples of Codig Security Betwee Domais O DOM2: dmadmi passwd DOM2 DOM1 Eter Local Domai Password:foo2 Reeter Local Domai Password:foo2 Eter Remote Domai Password:foo1 Reeter Remote Domai Password:foo1 Oce passwords have bee created o both domais, a coectio ca be established ad services ca be ivoked o the remote domai. Example 2: Settig Security to APP_PW If the SECURITY parameter i the UBBCONFIG is set to APP_PW or higher, the SECURITY i the DMCONFIG ca be set to NONE, APP_PW, or DM_PW. Because you ca defie multiple views of a domai i oe DMCONFIG file (oe view per local domai defiitio), you ca assig a differet type of security mechaism to each of those views. Note: If SECURITY is set to APP_PW for a local domai access poit i the DMCONFIG, the SECURITY i the UBBCONFIG must be set to APP_PW or higher. Listig 2-12 Settig Security to APP_PW for Both Applicatio ad Domais DOM1: SECURITY i UBBCONFIG set to APP_PW SECURITY i DMCONFIG set to APP_PW DOM2: SECURITY i UBBCONFIG set to APP_PW SECURITY i DMCONFIG set to APP_PW I this example, both DOM1 ad DOM2 eforce APP_PW security. Usig the BEA Tuxedo Domais Compoet 2-47

84 2 Plaig ad Cofigurig ATMI Domais O the iitiator side, the pertiet attributes i UBBCONFIG ad DMCONFIG are set as follows: UBBCONFIG SECURITY=APP_PW DMCONFIG *DM_LOCAL_DOMAINS DOM1 DOMAINID=DOM1 SECURITY=APP_PW *DM_REMOTE_DOMAINS DOM2 DOMAINID= DOM2 O the respoder side, the pertiet attributes i UBBCONFIG ad DMCONFIG are set as follows. UBBCONFIG SECURITY=APP_PW DMCONFIG *DM_LOCAL_DOMAINS DOM2 DOMAINID=DOM2 SECURITY=APP_PW *DM_REMOTE_DOMAINS DOM1 DOMAINID= DOM1 After the TUXCONFIG ad BDMCONFIG files have bee created, boot the applicatios o DOM1 ad DOM Usig the BEA Tuxedo Domais Compoet

85 Cofigurig the Coectios Betwee Your Domais Cofigurig the Coectios Betwee Your Domais You ca specify the coditios uder which a local domai gateway tries to establish a coectio to a remote domai. To specify these coditios, assig a value to the CONNECTION_POLICY parameter i the Domais cofiguratio file. You ca select ay of the followig coectio policies: Coect at boot time (ON_STARTUP) Coect whe a cliet program requests a remote service (ON_DEMAND) Accept icomig coectios but do ot iitiate a coectio automatically (INCOMING_ONLY) For coectio policies of ON_STARTUP ad INCOMING_ONLY, Dyamic Status is ivoked. Dyamic Status is a BEA Tuxedo Domais capability that checks ad reports the status of remote services. How to Request Coectios at Boot Time (ON_STARTUP Policy) A policy of ON_STARTUP meas that a domai gateway attempts to establish a coectio with its remote domais whe the gateway server is iitialized. By default, this coectio policy retries failed coectios every 60 secods, but you ca specify a differet value for this iterval (usig the RETRY_INTERVAL parameter). This policy ivokes Dyamic Status. CONNECTION_POLICY=ON_STARTUP Usig the BEA Tuxedo Domais Compoet 2-49

86 2 Plaig ad Cofigurig ATMI Domais The followig diagram shows how coectios are attempted ad made by a gateway for which the coectio policy is ON_STARTUP. Figure 2-5 Coectios Made with a ON_STARTUP Policy How to Request Coectios for Cliet Demads (ON_DEMAND Policy) A coectio policy of ON_DEMAND meas that a coectio is attempted oly whe either a cliet requests a remote service or a admiistrative coect commad is ru. The default settig for CONNECTION_POLICY is ON_DEMAND. Coectio retry processig is ot allowed whe the coectio policy is ON_DEMAND. This policy does ot ivoke Dyamic Status Usig the BEA Tuxedo Domais Compoet

87 Cofigurig the Coectios Betwee Your Domais CONNECTION_POLICY=ON_DEMAND The followig diagram shows how coectios are attempted ad made by a gateway for which the coectio policy is ON_DEMAND. Figure 2-6 Coectios Made with a ON_DEMAND Policy How to Limit Coectios to Icomig Messages Oly (INCOMING_ONLY Policy) A coectio policy of INCOMING_ONLY meas that a domai gateway does ot try to establish a coectio to remote domais upo startig. Coectio retry processig is ot allowed whe the coectio policy is INCOMING_ONLY. This policy ivokes Dyamic Status. To use this policy, eter the followig lie i your Domais cofiguratio file: CONNECTION_POLICY=INCOMING_ONLY Note: You ca also establish a coectio maually usig the dmadmi coect commad. Usig the BEA Tuxedo Domais Compoet 2-51

88 2 Plaig ad Cofigurig ATMI Domais The followig diagram shows how coectios are attempted ad made by a gateway for which the coectio policy is INCOMING_ONLY. Figure 2-7 Coectios Made with a INCOMING_ONLY Policy (accept icomig coectios) How to Cofigure the Coectio Retry Iterval for ON_STARTUP Oly Whe the CONNECTION_POLICY parameter is set to ON_STARTUP, the the coectio retry capability is available. The coectio retry capability eables a domai gateway to retry, automatically, a failed attempt to coect to a remote domai. As a admiistrator, you ca cotrol the frequecy of automatic coectio attempts. To do so, specify the legth (i secods) of the iterval durig which the gateway should wait before tryig, agai, to establish a coectio. You ca specify the retry iterval by settig the RETRY_INTERVAL parameter i the DM_LOCAL_DOMAINS sectio of the Domais cofiguratio file as follows: RETRY_INTERVAL=umber_of_secods 2-52 Usig the BEA Tuxedo Domais Compoet

89 Cofigurig the Coectios Betwee Your Domais Note: You ca specify betwee 0 ad secods. If the coectio policy is ON_STARTUP ad you do ot specify a value for the RETRY_INTERVAL parameter, a default of 60 is used. The RETRY_INTERVAL parameter is valid oly whe the coectio policy is ON_STARTUP. For the other coectio policies (ON_DEMAND ad INCOMING_ONLY), retry processig is disabled. How to Cofigure the Maximum Retry Number You idicate the umber of times that a domai gateway tries to establish coectios to remote domais before quittig by assigig a value to the MAXRETRY parameter: the miimum value is 0; the default ad maximum value is the value of the MAXLONG parameter. If you set MAXRETRY=0, automatic coectio retry processig is tured off. The server does ot attempt to coect to the remote gateways automatically. If you set MAXRETRY=umber, the gateway tries to establish a coectio the specified umber of times before quittig. Note: The RETRY_INTERVAL is rouded up to a multiple of SCANUNIT. If you set MAXRETRY=MAXLONG, retry processig is repeated idefiitely or util a coectio is established. Usig the BEA Tuxedo Domais Compoet 2-53

90 2 Plaig ad Cofigurig ATMI Domais The MAXRETRY parameter is valid oly whe the coectio policy is ON_STARTUP. For the other coectio policies (ON_DEMAND ad INCOMING_ONLY), retry processig is disabled. Table 2-1 Example Settigs of the MAXRETRY ad RETRY_INTERVAL Parameters If You Set... CONNECTION_POLICY=ON_STARTUP RETRY_INTERVAL=30 MAXRETRY=3 CONNECTION_POLICY=ON_STARTUP MAXRETRY=0 CONNECTION_POLICY=ON_STARTUP RETRY_INTERVAL=30 The... The gateway makes 3 attempts to establish a coectio, at 30 secods itervals, before quittig. The gateway attempts to establish a coectio at iitializatio time but does ot retry if the first attempt fails. The gateway attempts to establish a coectio every 30 secods util a coectio is established. See Also Cotrollig the Coectios Betwee Domais o page 2-55 Cofigurig Domais-level Failover ad Failback o page 2-58 DMCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece 2-54 Usig the BEA Tuxedo Domais Compoet

91 Cotrollig the Coectios Betwee Domais Cotrollig the Coectios Betwee Domais As the admiistrator, you ca cotrol the umber of coectios you wat to establish betwee domais. You ca also break the coectios betwee local ad remote domais. How to Establish Coectios Betwee Domais To establish a coectio betwee a local gateway ad a remote domai, ru the dmadmi commad with the coect (co) subcommad, as follows: dmadmi co -d local_domai_ame By default, coectios are established betwee the local domai you have specified ad all remote domais cofigured for the local gateway. If you wat to establish a coectio to oly oe remote domai, specify that domai o the commad lie with the -R optio, as follows: dmadmi co -d local_domai_ame -R remote_domai_ame If a coectio attempt fails ad you have cofigured the domai to try agai, repeated attempts to coect (via automatic coectio retry processig) are made. How to Break Coectios Betwee Domais To break a coectio betwee a local gateway ad a remote domai (makig sure that the gateway does ot try to reestablish the coectio through automatic coectio retry processig), ru the dmadmi commad with the discoect (dco) subcommad, as follows: dmadmi dco -d local_domai_ame Usig the BEA Tuxedo Domais Compoet 2-55

92 2 Plaig ad Cofigurig ATMI Domais By default, all remote domais cofigured for the local gateway are discoected. If you wat to ed the coectio to oly oe remote domai, specify that domai o the commad lie with the -R optio as follows: dmadmi dco -d local_domai_ame -R remote_domai_ame Automatic coectio retry processig is stopped by this commad, regardless of whether there are ay active coectios whe the commad is ru. How to Report o Coectio Status Usig the pritdomai commad, you ca geerate a report o coectio status ad the coectios beig retried. The coect commad reports whether a coectio attempt has succeeded. The pritdomai commad prits iformatio about the specified local domai, icludig a list of remote domais, a list of remote domais to which it is coected, a a list of remote domais to which it is tryig to establish coectios. The followig example shows a dmadmi sessio i which the pritdomai commad is issued (i its abbreviated form, pd) for a local domai called LDOM. $ dmadmi dmadmi - Copyright (c) 1996 BEA Systems, Ic. Portios * Copyright RSA Data Security, Ic. All Rights Reserved. Distributed uder licese by BEA Systems, Ic. TUXEDO is a registered trademark. pd -d LDOM Local domai :LDOM Coected domais: Domaiid: RDOM1 Discoected domais beig retried: Domaiid: RDOM2 dco -d LDOM -R RDOM1 Operatio completed successfully. Use pritdomai(pd) to obtai results. dco -d LDOM -R RDOM2 Operatio completed successfully. Use pritdomai(pd) to obtai results Usig the BEA Tuxedo Domais Compoet

93 Cofigurig Failover ad Failback i a Domais Eviromet co -d LDOM -R RDOM3 Operatio completed successfully. Use pritdomai(pd) to obtai results. pd -d LDOM Local domai :LDOM Coected domais: Domaiid: RDOM3 Cofigurig Failover ad Failback i a Domais Eviromet Two types of failover ca be performed i a Domais eviromet: lik-level failover ad Domais-level failover. This sectio provides istructios for both: How to Cofigure Domais to Support Lik-level Failover o page 2-57 Cofigurig Domais-level Failover ad Failback o page 2-58 If you wat failover ad failback fuctioality i your domai, you must cofigure your Domais cofiguratio file to support it. For details about the Domais cofiguratio file, see the DMCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece. How to Cofigure Domais to Support Lik-level Failover Lik-level failover is a mechaism that esures that a alterate etwork lik becomes active whe a primary lik fails. To use lik-level failover, the primary ad alterate gateways must reside o differet remote domais (that is, gateway mirrorig must be used). Curretly, lik-level failover does ot support multiple alterate liks to the same gateway. Usig the BEA Tuxedo Domais Compoet 2-57

94 2 Plaig ad Cofigurig ATMI Domais To implemet lik-level failover, specify it i the DM_TDOMAINS sectio of the Domais cofiguratio file (DMCONFIG) as follows: *DM_TDOMAINS RDOM1 NWADDR=//addr1:0 RDOM1 NWADDR=//addr2:0 The first etry refers to the primary etwork lik for remote domai RDOM1; the secod etry refers to the alterate lik. Lik-level failback is a maual procedure. Whe the primary lik is restored, the admiistrator must brig dow the alterate lik maually. This operatio may cause requests that are i progress to fail, ad ew traffic to be resumed over the primary lik. Note: For more detailed iformatio o gateway mirrorig, see DMCONFIG(5) i the File Formats, Data Descriptios, MIBs, ad System Processes Referece. Cofigurig Domais-level Failover ad Failback Domais-level failover is a mechaism that trasfers requests to alterate remote domais whe a failure is detected with a primary remote domai. It also provides failback to the primary remote domai whe that domai is restored. This level of failover/failback depeds o Dyamic Status. The domai must be cofigured with a CONNECTION_POLICY of ON_STARTUP or INCOMING_ONLY to eable Domais-level failover/failback. Domais-level failover/failback defies a remote domai as available whe a etwork coectio to the remote domai exists, ad uavailable whe a etwork coectio to the remote domai does ot exist. Prerequisite to Usig Domais-level Failover ad Failback To use Domais-level failback, you must specify ON_STARTUP or INCOMING_ONLY as the value of the CONNECTION_POLICY parameter. A coectio policy of ON_DEMAND is usuitable for Domais-level failback as it operates o the assumptio that the remote domai is always available. If you do ot specify ON_STARTUP or INCOMING_ONLY as your coectio policy, your servers caot fail over to the alterate remote domais that you have specified with the RDOM parameter Usig the BEA Tuxedo Domais Compoet

95 Cofigurig Failover ad Failback i a Domais Eviromet Note: A remote domai is available if a etwork coectio to it exists; a remote domai is uavailable if a etwork coectio to it does ot exist. How to Cofigure Domais to Support Failover Example To support failover, you must specify a list of the remote domais resposible for executig a particular service i your Domais cofiguratio file. Specifically, you must specify such a list as the value of the RDOM parameter i the DM_REMOTE_SERVICES sectio. You ca also specify alterate domais, as follows: RDOM=idetifier_1, idetifier_2, idetifier_3 Suppose the TOUPPER ad TOUPPER2 services are available from three remote domais: R1 (the primary remote domai), R2, ad R3. Iclude the followig etry i your Domais cofiguratio file: *DM_REMOTE_SERVICES DEFAULT: RDOM=R1, R2, R3 TOUPPER TOUPPER2 How to Cofigure Domais to Support Failback Failback occurs whe a etwork coectio to the primary remote domai is reestablished for ay of the followig reasos: Automatic retries (ON_STARTUP oly) Icomig coectios Maual dmadmi coect commad Note: For automatic retries, coectio retry must be tured o (that is, MA54ETRY>0). Usig the BEA Tuxedo Domais Compoet 2-59

96 2 Plaig ad Cofigurig ATMI Domais 2-60 Usig the BEA Tuxedo Domais Compoet

97 3 Plaig ad Cofigurig CORBA Domais Domais i a BEA Tuxedo CORBA eviromet are a extesio of the core ATMI BEA Tuxedo eviromet domais. A domai is a costruct that is etirely admiistrative. There are o programmig iterfaces that refer to domais. Everythig cocerig domais is doe by cofiguratio files; oly a admiistrator is aware of domais. This topic icludes the followig sectios: Cofigurig Multiple CORBA Domais Types of CORBA Domai Cofiguratios Examples: Cofigurig Multiple CORBA Domais Overview of Multiple CORBA Domais Sice a eterprise ca have may differet kids of applicatios, be geographically dispersed, ad be orgaized ito differet areas of resposibility, there might be may separate domais. Each domai is a separately admiistered uit. Perhaps it is orgaized for geographical cosideratios (all the machies i a give locatio). Perhaps it is orgaized o departmetal grouds withi a eterprise (accoutig, maufacturig, shippig, ad so o). Usig the BEA Tuxedo Domais Compoet 3-1

98 3 Plaig ad Cofigurig CORBA Domais Evetually, a eterprise wats the differet applicatios i those domais to be able to cooperate. It is ofte impossible to expad a sigle domai to ecompass the eterprise. However, the size of a expaded domai i terms of the umber of machies ad services would be impractical. Sice a sigle domai must be admiistered as a whole, the cofiguratio would rapidly become huge ad require more effort i admiisterig tha i developig ad implemetig applicatios. Therefore, to keep a domai relatively compact for admiistratio, there must be a way to separate applicatios ito multiple domais ad still allow applicatios i oe domai to access services i other domais. This capability for iterdomai commuicatio is what is geerically called BEA Tuxedo domais. Iterdomai Commuicatio The followig figure shows a simple multiple-domai cofiguratio. Figure 3-1 Multiple-domai Cofiguratio Domai A Domai C Cliet X Server for Q text Domai Gateway Domai Gateway Server for R The followig steps describe sigle-domai commuicatio betwee Cliet X ad Domai A: 1. Cliet X coects to Domai A usig the Bootstrap object. The cliet applicatio uses the Bootstrap object to locate a FactoryFider ad the uses the FactoryFider to ask for a factory for objects of type Q. (The FactoryFider call is itself a ivocatio o Domai A.) 2. Whe the FactoryFider returs a factory, the cliet the ivokes that factory i Domai A. 3-2 Usig the BEA Tuxedo Domais Compoet

99 3. The factory returs a referece to a object of type Q, called Q1. 4. The cliet ow ivokes o object Q1 i Domai A. Note: Throughout all of these steps, the cliet does ot kow where ay of the objects are, or which domais they are i. It might ot eve kow that there is somethig called a domai. The admiistrative actios for coectig a cliet to Domai A are relatively simple for a cliet, because the cliet is a simple machie ad has very little ifrastructure; it stads aloe for the most part. Ideed, the coectio to a BEA Tuxedo domai is the primary admiistratio for a cliet. The actual admiistrative chore is settig the address of the ISL that is i Domai A. For multiple-domai commuicatio, Q1 eeds the services of Object R1, which is i Domai C; therefore, object Q1 must execute operatios similar to those described i steps 1 through 4 above, but across domai boudaries. The actual steps are as follows: 1. Object Q1 uses a Bootstrap object to locate a FactoryFider ad the uses the FactoryFider to ask for a factory for objects of type R. 2. Whe the FactoryFider returs a referece to a factory i Domai C, Object Q1 ivokes that factory. 3. The factory returs a referece to a object of type R, called R1. 4. Object Q1 ivokes o Object R1. Note: As with Cliet X, there must be some admiistratio to allow Object Q1 to get at the factories ad objects i Domai C. As Figure 3-1 shows, the mechaism for commuicatio betwee domais is a domai gateway. A domai gateway is a system server i a domai. A system server is differet tha a user-writte server because it is provided as part of the BEA Tuxedo product; other system servers are the ame servers, FactoryFiders, ad ISLs. A domai gateway is somewhat similar i cocept to a ISL because it is the cotact poit for a domai. It is differet from a ISL, however, because a domai gateway coects to aother domai gateway, which is itself a cotact poit for a domai; that is, a domai gateway s job is to coect to aother domai gateway. Thus, the pair of domai gateways cooperate to make sure that ivocatio o objects that ihabit differet domais are routed to the correct domai. Usig the BEA Tuxedo Domais Compoet 3-3

100 3 Plaig ad Cofigurig CORBA Domais For domai gateways to operate i this maer, they must be cofigured properly. That cofiguratio is the subject of the followig sectios. Fuctios of Multiple-domai Cofiguratio Elemets The followig elemets work together to accomplish the cofiguratio of multiple domais: BEA Tuxedo cofiguratio file The UBBCONFIG file ames a domai ad idetifies the group ad service etry for a domai gateway server. No attributes of domai gateways are specified i the UBBCONFIG file; all such attributes are i the DMCONFIG file. Domai cofiguratio file The domai cofiguratio file (DMCONFIG) describes the remote domais that are coected to the local domai. If there is o DMCONFIG file, there are o coectios. FactoryFider domai cofiguratio file Oe FactoryFider domai cofiguratio file (factory_fider.ii) is required for each domai that is coected to oe or more other domais. If a domai is ot coected to aother domai, there is o eed for this file. This file specifies which factories ca be searched for or foud across domai boudaries. You must carefully coordiate the factory_fider.ii file with the DMCONFIG so that they both have iformatio about the same coected domais ad provide the same coectivity. Ivocatio of a object i a remote domai The whole poit of the BEA Tuxedo domais feature is for a applicatio i oe CORBA domai to be able to make a ivocatio o a object i aother CORBA domai, without either the cliet or server applicatios beig aware that domais are a factor. Cofiguratio iformatio is iteded to allow such ivocatios to cross domai boudaries ad to hide the fact of those boudaries from applicatios. Beig able to make a ivocatio o a referece for a object i a remote domai depeds o a satisfactory set of three cofiguratio files the UBBCONFIG, DMCONFIG, ad factory_fider.ii files for each domai ad 3-4 Usig the BEA Tuxedo Domais Compoet

101 Cofigurig Multiple CORBA Domais o the coordiatio of two of those cofiguratio files the DMCONFIG ad factory_fider.ii files betwee domais. As the umber of domais grows, the coordiatio effort grows. Refereces to objects i a remote domai Ay object referece may specify a local domai or a remote domai. A referece to a remote domai typically happes whe a FactoryFider returs a referece to a factory i a remote domai. It also happes whe that factory, i tur, creates ad returs a referece to a object i that remote domai (although, of course, the referece is local to the domai of the factory). Note: Applicatios are ot aware of the domai of a object referece. Applicatios caot fid out what domai a object referece refers to. Thus, ivocatios o a object referece for a remote domai are trasparet to the applicatio. This trasparecy allows admiistrators the freedom to cofigure services i idividual domais ad to spread resources across multiple domais. If applicatios were to iclude iformatio about domais, chagig cofiguratios would require that the applicatios be rewritte as well. FactoryFiders For a server i a local domai to obtai a object referece to a object i aother domai, the applicatio uses the same FactoryFider patter as it does for objects i the local domai. The applicatio uses the same patter because it is ot aware that the factory fider returs a referece to a factory i aother domai. The cofiguratio files hide this fact. Oce a object referece has bee obtaied via a FactoryFider or factory, the object referece ca be passed aywhere; that is, passed to objects i the local domai, retured to a cliet, or passed to aother domai. Cofigurig Multiple CORBA Domais You use the followig three cofiguratio files to cofigure multiple domais: The mai cofiguratio UBBCONFIG file The domai cofiguratio (DMCONFIG) file, ad Usig the BEA Tuxedo Domais Compoet 3-5

102 3 Plaig ad Cofigurig CORBA Domais The FactoryFider domai cofiguratio file (factory_fider.ii). The Cofiguratio File You must specify the followig parameters i the UBBCONFIG file to cofigure multiple domais: Domai ame Gateway group Gateway service Domai Name Though ot required for sigle domais (that is, stadaloe domais), a domai that is coected to aother domai must have a DOMAIN ID. You specify this parameter i the RESOURCES sectio of the UBBCONFIG file, as follows: DOMAIN ID = <domai-ame> The <domai-ame> must be 1 to13 characters log. For example: DOMAIN ID = headquarters <domai-ame> is the ame that will be refereced i the DM_REMOTE_SERVICES ad DM_LOCAL_SERVICES sectios of the related DMCONFIG file. I that file, the <domai-ame> will be refereced as: "//<domai-ame>" The quotes are part of the referece. The slashes (//) mea that the ame applies to BEA Tuxedo CORBA domais, rather tha to BEA Tuxedo ATMI domais. For example: "//headquarters" Note: Every domai i a eterprise must have a uique <domai-ame>. 3-6 Usig the BEA Tuxedo Domais Compoet

103 Cofigurig Multiple CORBA Domais Gateway Group ad Service As with every other system service, there must be a group ad a service ame specified for a gateway. For example, the GROUPS sectio might cotai: LGWGRP GRPNO=4 LMID=LDOM I this example, LGWGRP is a ame chose by a user (perhaps a abbreviatio for Local Gateway Group ). The service ame for a domai gateway is GWTDOMAIN ad must be associated, like every other group, with a server group ad a server ID. You specify the service ame i the SERVERS sectio associated with the server group ame chose. For example: GWTDOMAIN SRVGRP=LGWGRP SRVID=1 This tells the BEA Tuxedo CORBA server that a domai gateway is to be used ad that additioal iformatio is foud i the DMCONFIG file. The Domai Cofiguratio (DMCONFIG) File There is oe DMCONFIG file per domai. It describes the relatioship betwee the local domai (the domai i which the DMCONFIG file resides) ad remote domais (ay other domais). The DMCONFIG file cotais domai iformatio for the core BEA Tuxedo domais ad for BEA Tuxedo CORBA domais. The sectios below cocetrate o the iformatio that applies to BEA Tuxedo CORBA domais. I other documetatio for the DMCONFIG file, the commuicatio betwee local ad remote domais is based o BEA Tuxedo ATMI services, a cocept ot used i BEA Tuxedo CORBA eviromets. For BEA Tuxedo CORBA eviromets, the service ame is the ame of aother BEA Tuxedo domai that ca service BEA Tuxedo CORBA requests. The DMCONFIG file cosists of up to eight parts, but oe part, DM_ROUTING, does ot apply to BEA Tuxedo CORBA eviromets. The other seve parts refer to BEA Tuxedo CORBA eviromets, but may of the BEA Tuxedo ATMI parameters are ot used. Those seve parts are: DM_RESOURCES, DM_LOCAL_DOMAINS, DM_REMOTE_DOMAINS, DM_LOCAL_SERVICES, DM_REMOTE_SERVICES, DM_ACCESS_CONTROL, ad DM_TDOMAIN. The followig sectios refer to the sample DMCONFIG file show i Listig 3-1. Usig the BEA Tuxedo Domais Compoet 3-7

104 3 Plaig ad Cofigurig CORBA Domais Listig 3-1 Sample DMCONFIG File BEA Tuxedo CORBA DOMAIN CONFIGURATION FILE *DM_RESOURCES VERSION=Experimetal8.9 *DM_LOCAL_DOMAINS LDOM GWGRP=LGWGRP TYPE=TDOMAIN DOMAINID="MUTT" *DM_REMOTE_DOMAINS TDOM1 TYPE=TDOMAIN DOMAINID="JEFF" *DM_TDOMAIN LDOM NWADDR="//MUTT:2507" TDOM1 NWADDR="//JEFF:3186" *DM_LOCAL_SERVICES "//MUTT" *DM_REMOTE_SERVICES "//JEFF" RDOM=TDOM1 DM_RESOURCES The DM_RESOURCES sectio ca cotai a sigle field, VERSION. It is ot checked by software; it is provided simply as a place where users ca eter a strig that may have some documetatio value to the applicatio. *DM_RESOURCES VERSION=Experimetal Usig the BEA Tuxedo Domais Compoet

105 Cofigurig Multiple CORBA Domais DM_LOCAL_DOMAINS The DM_LOCAL_DOMAINS sectio specifies some attributes for gateways ito the local domai from the outside. The sectio must have a etry for each gateway group defied i the UBBCONFIG fle that will provide access to the local domai from other domais. Each etry specifies the parameters required for the domai gateway processes ruig i that group. Etries have the form: LDOM required-parameters [optioal-parameters] where LDOM is a idetifier used to refer to the gateway to the local domai. LDOM must be uique amog all LDOM ad RDOM etries across the eterprise (that is, amog the set of domais coected to each other). Note that LDOM is ot the same ame as the <domai-ame> or the gateway group that is specified i the UBBCONFIG file. Rather, LDOM is a ame used oly withi the DMCONFIG file to provide a extra level of isulatio from potetial chages i the UBBCONFIG file (chages i UBBCONFIG will affect oly this oe part of DMCONFIG). The followig are required parameters: GWGRP = idetifier This parameter specifies the ame of a gateway server group (the ame provided i the UBBCONFIG file) represetig this local domai. TYPE = TDOMAIN The TYPE parameter is required to specify the use of domais for BEA Tuxedo CORBA eviromets. DOMAINID = strig The DOMAINID parameter is used to idetify the local domai for the purposes of security. The gateway server group i GWGRP uses this strig durig ay security checks. It has o required relatioship to the <domai-ame> foud i the RESOURCES sectio of the UBBCONFIG file. DOMAINID must be uique across both local ad remote domais. The value of strig ca be a sequece of characters (for example, BA.CENTRAL01 ), or a sequece of hexadecimal digits preceded by 0x (for example, 0x0002FF98C0000B9D6 ). DOMAINID must be 32 octets or fewer i legth. If the value is a strig, it must be 32 characters or fewer (coutig the trailig ull). Usig the BEA Tuxedo Domais Compoet 3-9

106 3 Plaig ad Cofigurig CORBA Domais For example, the lies DM_REMOTE_DOMAINS *DM_LOCAL_DOMAINS LDOM GWGRP=LGWGRP TYPE=TDOMAIN DOMAINID="MUTT" idetify LDOM as a access poit to the local domai. It is associated with the service group LGWGRP (as specified i the UBBCONFIG file). If the gateway is ever ivolved i a domai-to-domai security check, it goes by the ame MUTT. Optioal parameters describe resources ad limits used i the operatio of domai gateways. For a descriptio of these parameters, refer the dmcofig(5) referece page i the File Formats, Data Descriptios, MIBs, ad System Processes Referece. The DM_REMOTE_DOMAINS sectio specifies some attributes for gateways to remote domais. The sectio has a etry for each UBBCONFIG file-defied gateway group that will sed requests to remote domais. Each etry specifies the parameters required for the domai gateway processes ruig i that group. Etries have the form: RDOM required-parameters where RDOM is a idetifier used to refer to the gateway providig access to the remote domai. RDOM must be uique amog all LDOM ad RDOM etries across the eterprise (that is, amog the set of domais coected to each other). Note that RDOM is ot the same ame as the <domai-ame> or the gateway group that is specified i the UBBCONFIG file. Rather, RDOM is a ame used oly withi the DMCONFIG to provide a extra level of isulatio from potetial chages i UBBCONFIG (chages i UBBCONFIG will affect oly this oe part of DMCONFIG). The required parameters are: TYPE = TDOMAIN The TYPE parameter is required to specify the use of domais for BEA Tuxedo CORBA eviromets. DOMAINID = strig The DOMAINID parameter is used to idetify the remote domai for the purposes of security. The gateway uses this strig durig ay security checks. DOMAINID has o required relatioship to the <domai-ame> foud i the RESOURCES sectio of the UBBCONFIG file. DOMAINID must be uique across both local ad remote domais. The value of strig ca be a sequece of 3-10 Usig the BEA Tuxedo Domais Compoet

107 Cofigurig Multiple CORBA Domais characters (for example, BA.CENTRAL01 ), or a sequece of hexadecimal digits preceded by 0x (for example, 0x0002FF98C0000B9D6 ). DOMAINID must be 32 octets or fewer i legth. If the value is a strig, it must be 32 characters or fewer (coutig the trailig ull). Etries associated with a remote domai ca be specified more tha oce. The first oe specified is cosidered to be the primary address, which meas it is the first oe tried whe a coectio is beig attempted to a remote domai. If a etwork coectio caot be established usig the NWADDR of the primary etry, the NWADDR associated with the secodary etry is used. (NWADDR is the physical address; see the DM_TDOMAIN sectio.) For example, the lies *DM_REMOTE_DOMAINS TDOM1 TYPE=TDOMAIN DOMAINID="JEFF" idetify TDOM1 as the access poit ame of a gateway. If the gateway is ever ivolved i a domai-to-domai security check with a parter gateway, the gateway expects that parter to go by the ame JEFF. DM_TDOMAIN The DM_TDOMAIN sectio defies the etwork addressig iformatio for gateways implemetig BEA Tuxedo CORBA domais. There should be oe etry for each domai gateway that accepts requests from remote domais, ad oe etry for each domai gateway that seds requests to remote domais. The format of each etry is: DOM required-parameters [optioal-parameters] where DOM is a idetifier value used to idetify either a local domai access poit (LDOM i the DM_LOCAL_DOMAINS sectio) or a remote domai access poit (RDOM i the DM_REMOTE_DOMAINS sectio). The followig parameter is required: NWADDR = strig This parameter specifies the etwork address associated with a local domai or a remote domai. If the associatio is with a local domai, the NWADDR is used to accept coectios from other domais. If the associatio is with a remote domai, the NWADDR is used to iitiate a coectio. This parameter specifies the etwork address to be used by the process as its listeig address. The listeig address for a domai gateway is the meas by which it Usig the BEA Tuxedo Domais Compoet 3-11

108 3 Plaig ad Cofigurig CORBA Domais DM_REMOTE_SERVICES is cotacted by other gateway processes participatig i the applicatio. If strig has the form "0xhex-digits" or "\\xhex-digits", it must cotai a eve umber of valid hex digits. These forms are traslated iterally ito a character array cotaiig TCP/IP addresses. The addresses may also be i either of the followig two forms: "//hostame:port_umber" "//...:port_umber" I the first of these formats, hostame is resolved to a TCP/IP host address at the time the address is boud, usig the locally cofigured ame resolutio facilities accessed via gethostbyame(3c). The "..." is the dotted decimal format, where each represets a decimal umber i the rage 0 to 255. Port_umber is a decimal umber i the rage 0 to (the hexadecimal represetatios of the strig specified). For example: *DM_TDOMAIN LDOM NWADDR="//MUTT:2507" TDOM1 NWADDR="//JEFF:3186" Cotiuig the example from above, the first etry specifies a gateway with the domai access ame of LDOM (meaig that it correspods to the local gateway group LGWGRP, specified i UBBCONFIG). Sice LDOM was defied i DM_LOCAL_DOMAINS, that meas the gateway is cofigured to accept requests from other domais. It listes o the address "//MUTT:2507". Similarly, the secod etry is for the domai access ame TDOM1, which appears i DM_REMOTE_DOMAINS, trasferrig requests to a remote domai. I this case, the gateway associated with TDOM1 seds requests to the address "//JEFF:3186". For a descriptio of the optioal parameters, refer to the dmcofig(5) referece page i the File Formats, Data Descriptios, MIBs, ad System Processes Referece. The DM_REMOTE_SERVICES sectio specifies additioal attributes for gateways to remote domais. The format of each etry is: service RDOM=<rdom-ame> [LDOM=<ldom-ame>] [TRAN_TIME=...] 3-12 Usig the BEA Tuxedo Domais Compoet

109 Cofigurig Multiple CORBA Domais where service is of the form: "//<domai-ame>" DM_LOCAL_SERVICES This <domai-ame> is the ame that occurs RESOURCES sectio of the UBBCONFIG file as <domai-ame>. Each etry specifies a rdom-ame ad, optioally, a ldom-ame. The gateway uses the attributes for those etries for establishig a gateway pair for BEA Tuxedo CORBA domai commuicatio. Gateways operate i pairs. At boot time, the local domai uses attributes of rdom-ame (the address specified i the DM_TDOMAIN sectio) to establish a coectio to a gateway i the other domai. If security is used, the other attributes of rdom-ame ad ldom-ame are used for mutual autheticatio. At ru time, whe BEA Tuxedo determies that a request must travel to domai <domai-ame>. It uses the gateway specified by rdom-ame to sed the request to aother domai. Most ofte, <domai-ame> is the ame of the domai specified i the address of the rdom-ame. I that situatio, whe the request eds up at the other ed of the gateway, it is served i that domai. For example: *DM_REMOTE_SERVICES "//JEFF" RDOM=TDOM1 I this case, the domai ame JEFF is located at the address "//JEFF:3186". That address might or might ot have a UBBCONFIG file that specifies its domai ame as JEFF. If it does, the request ca be serviced immediately. It is possible to have etries that sed requests for the specified domai-ame to a itermediary domai that acts as a pass-through for routig purposes. The remaiig optioal parameter, TRANTIME = iteger, specifies the default timeout value, i secods, for a trasactio automatically started for the associated service. The value must be greater tha or equal to 0 (zero) ad less tha The default is 30 secods. A value of 0 (zero) implies the maximum timeout value for the machie. The DM_LOCAL_SERVICES sectio specifies additioal attributes for gateways that accept requests ito the local domai from the outside. Lies withi this sectio have the form: Usig the BEA Tuxedo Domais Compoet 3-13

110 3 Plaig ad Cofigurig CORBA Domais service [LDOM=<ldom-ame>] [ACL=...] where service is of the form: "//<domai-ame>" This <domai-ame> is the ame that occurs i the RESOURCES sectio of the UBBCONFIG file as <domai-ame>. Most likely this is the ame of the domai i which the gateway resides, meaig that this (local) domai accepts BEA Tuxedo CORBA eviromet requests from other domais. It is also possible (but ot ecessary, except for purposes of security) to have a etry that accepts requests for a differet domai ame i the case where the local domai acts as a pass-through for routig purposes. Notice that exported services iherit the properties specified for the service i a etry i the SERVICES sectio of the TUXCONFIG file, or their defaults. Some of the properties that may be iherited are LOAD, PRIO, AUTOTRAN, ROUTING, BUFTYPE, ad TRANTIME. The optioal parameter, ACL = idetifier, specifies the ame of the access cotrol list (ACL) to be used by the local domai to restrict requests made to this service by remote domais. The ame of the ACL is defied i the DM_ACCESS_CONTROL sectio. If this parameter is ot specified, access cotrol is ot performed for requests to this service. For example, the lies: *DM_LOCAL_SERVICES "//MUTT" state that this domai accepts requests destied for the domai with ame MUTT. DM_ACCESS_CONTROL The DM_ACCESS_CONTROL sectio specifies the access cotrol lists used by a local domai. Lies i this sectio are of the form: ACL_NAME required parameters where ACL_NAME is a (idetifier) ame used to idetify a particular access cotrol list; it must be 15 characters or less i legth Usig the BEA Tuxedo Domais Compoet

111 Cofigurig Multiple CORBA Domais The oly required parameter is: ACLIST = idetifier [,idetifier] where a ACLIST is composed of oe or more remote domai ames (RDOM) separated by commas. The wildcard character (*) ca be used to specify that all the remote domais defied i the DM_REMOTE_DOMAINS sectio ca access a local domai. Note: The factory_fider.ii ad DMCONFIG files must be coordiated; that is, if the factory_fider.ii file declares aother domai to have accessible factories, there must be a way i DMCONFIG to get to that domai. The factory_fider.ii File Admiistrators are required to idetify ay factory objects that ca be used i the curret (local) /Domai, but that are residet i a differet (remote) /Domai. You idetify these factories i a FactoryFider domai cofiguratio file, also referred to as the factory_fider.ii file. This is a ASCII file that ca be created ad updated usig a text editor. The factory_fider.ii file ca be used to idetify remote CORBA factories that ca be used i the local domai. The format of the factory_fider.ii file is modeled after the sytax used to describe /Domais, ad is show below: *DM_REMOTE_FACTORIES "local_factory_id.factory_kid" DOMAINID="domai_id" RNAME="remote_factory_id.factory_kid"... *DM_LOCAL_FACTORIES "factory_id.factory_kid"... Sample sytax for CORBA factory objects is as follows: *DM_REMOTE_FACTORIES "AccoutFactory.FactoryKid" "DOMAINID="MyAccoutFactoryDomai" RNAME="MyAccoutFactory.FactoryKid Usig the BEA Tuxedo Domais Compoet 3-15

112 3 Plaig ad Cofigurig CORBA Domais where: AccoutFactory is the ame used to register the factory i the local domai s FactoryFider, MyAccoutFactoryDomai is the ame of the remote domai, MyAccoutFactory is the ame used to register the factory i the remote domai s FactoryFider. The Master NameMaager reads the factory_fider.ii file whe the process is started. The reaso for startig the Master NameMaager affects which portios of the factory_fider.ii file are processed. If the Master NameMaager is beig started as part of bootig a applicatio, the iitializatio mode, the etire cotets of the file is processed. As a result, the iformatio i the DM_REMOTE_FACTORIES sectio results i etries beig added for the factory objects beig imported. O the other had, if the Master NameMaager is beig restarted as a result of a process failure, oly the DM_LOCAL_FACTORIES sectio of the file is read. This sectio of the factory_fider.ii file must be re-read to reload the iformatio that is used to restrict the exportatio of certai factory objects ito aother domai. Note: Sice the Master NameMaager reads the factory_fider.ii file oly whe the process is started, there is o way to update the Master NameMaager (for example, whe a ew domai with factory objects to be imported eeds to be added) without shuttig dow the Master NameMaager. A factory_fider.ii file applies to the domai i which it resides. It cotais two sectios: the DM_REMOTE_FACTORIES sectio ad the DM_LOCAL_FACTORIES sectio. Either sectio ca be abset or cotai othig. The followig sectios provide more iformatio o how to use the DM_REMOTE_FACTORIES sectio ad the DM_LOCAL_FACTORIES sectio. DM_REMOTE_FACTORIES The DM_REMOTE_FACTORIES sectio provides iformatio about the factory objects that are available i remote domais ad that are imported so that applicatios i the local domai ca use them. Idetifiers for remote factory objects are listed i this sectio. The idetifier, uder which the object is registered, icludig a kid value of FactoryIterface, must be listed i this sectio. For example, the etry for a remote factory object to be registered by the TP Framework with the idetifier Teller i domai Norwest would be specified as: 3-16 Usig the BEA Tuxedo Domais Compoet

113 Cofigurig Multiple CORBA Domais *DM_REMOTE_FACTORIES "Teller.FactoryIterface" DOMAINID="Norwest" RNAME="BakTeller.FactoryIterface" If the RNAME is ot specified, the factory_kid must be specified i the factory ame ad the factory ame must be eclosed i quotatio marks; otherwise, the NameMaager is ot able to locate the appropriate factory. A etry that does ot cotai a factory_kid value is ot defaulted with a value of FactoryIterface. The followig example shows a factory object to be registered with the idetifier Teller i domai Norwest. Note the absece of the RNAME specificatio, the specificatio of the factory_kid value, ad the quotatio marks aroud the factory ame. *DM_REMOTE_FACTORIES "Teller.FactoryIterface" DOMAINID="Norwest" Because the idetities of factories i a multidomai cofiguratio may collide, the factory idetifier ad the RNAME parameters allow you to specify alterative idetities, or aliases, i the local domai for remote factories. Listig 3-2 shows two examples of a remote factory that is registered by the TP Framework with the idetifier BakTeller i domai Norwest. I both examples, the factory is made available i local domai with a alias of Teller. Listig 3-2 Assigig a Alias to a Remote Factory EXAMPLE 1: *DM_REMOTE_FACTORIES Teller DOMAINID="Norwest" RNAME= BakTeller.FactoryIterface EXAMPLE 2: *DM_REMOTE_FACTORIES "Teller.FactoryIterface" DOMAINID="Norwest" RNAME="BakTeller.FactoryIterface" Usig the BEA Tuxedo Domais Compoet 3-17

114 3 Plaig ad Cofigurig CORBA Domais You ca also assig multiple aliases to the same remote factory. I the example show i Listig 3-3, the remote factory will be registered i the local domai with two aliases: Teller ad BakTeller. Listig 3-3 Assigig Multiple Aliases to a Remote Factory *DM_REMOTE_FACTORIES "Teller.FactoryIterface" DOMAINID="Norwest" RNAME="BakTeller.FactoryIterface" "BakTeller.FactoryIterface" DOMAINID="Norwest" RNAME="BakTeller.FactoryIterface" Usage Note: I multidomai cofiguratios, factory object idetifiers must be uique across domais i the eterprise. I a multidomai cofiguratio, two differet domais must ot have factory objects with the same factory_id.factory_kid idetifier, for example: "Teller.FactoryIterface". If the same idetifier, or ame, is used i two domais, the software s behavior varies depedig o whether BEA WebLogic Eterprise was used to cofigure the CORBA domai eviromet: I releases prior to BEA WebLogic Eterprise 5.1, the software allows the first server i a domai to register the factory without issuig a error message. If two factories with the same ame are registered i a domai, the Master NameMaager fails. I BEA WebLogic Eterprise release 5.1 or later ad BEA Tuxedo release 8.0 or later, the software geerates a error ad writes it to the ULOG. Note: I a sigle domai cofiguratio, a BEA Tuxedo CORBA eviromet supports multiple factories objects with the same ame. This type of cofiguratio is allowed so as to achieve load-balacig. There are two ways to esure that your idetifiers, or ames, are uique across domais ad thus avoid this problem: 3-18 Usig the BEA Tuxedo Domais Compoet

115 Cofigurig Multiple CORBA Domais DM_LOCAL_FACTORIES 1. Use uique idetifiers throughout the eterprise. This may mea keepig a master list of all idetifiers. 2. I the factory_fider.ii file, use the RNAME parameter so that a alias is used by the local NameMaager. (This also meas that local cliets will have to be modified to use the alias to access the remote factory object.) Listig 3-2 shows a example of a factory_fider.ii file that uses the RNAME parameter to create a alias. The DM_LOCAL_FACTORIES sectio specifies factory objects i the local domai that are available to be exported to other domais. This sectio ca be used i the followig ways: If the DM_LOCAL_FACTORIES sectio does ot exist i a factory_fider.ii, or exists but is empty, all factory objects i the local domai are available to remote domais. This allows admiistrators a easy meas to make local factory objects available to remote domais without havig to provide a etry for every factory object i the local domai. If the DM_LOCAL_FACTORIES sectio exists i a factory_fider.ii file but cotais the reserved keyword NONE, oe of the factory objects i the local domai are available to remote domais. This allows admiistrators to restrict access without havig to provide a etry for every factory object i the local domai. The idetifier, or ame, uder which the factory object is registered, icludig a kid value of FactoryIterface, must be listed i this sectio. For example, the etry for a factory object to be registered by the TP Framework with the idetifier Teller would be specified as: *DM_LOCAL_FACTORIES "Teller.FactoryIterface" The factory_kid must be specified for the NameMaager to locate the appropriate factory object. A etry that does ot cotai a factory_kid value is ot defaulted with a value of FactoryIterface. This allows for the use of the CORBA NamigService. Usig the BEA Tuxedo Domais Compoet 3-19

116 3 Plaig ad Cofigurig CORBA Domais The factory_fider.ii file specifies that the process of fidig a factory ca be exported to a remote domai by icludig a sectio begiig with *DM_REMOTE_FACTORIES. I other words, icludig this sectio meas that the local domai ca fid factories i a remote domai. A etry ito the file for domai A might be: *DM_REMOTE_FACTORIES fa.factoryiterface DOMAINID=B This meas that a request i Domai A to fid a factory with the idetifier fa ca be satisfied by the FactoryFider i domai B. Of course, the UBBCONFIG ad DMCONFIG files for the two domais must also be set up so that there are coected domai gateways betwee the two domais.) A alterate form of the etry is: CDE.FactoryIterface DOMAINID=B RNAME=fA.FactoryIterface This meas that a request i Domai A to fid a factory with the idetifier CDE will be satisfied by the FactoryFider i domai B usig the ID fa. This is sometimes called a alias. Note: The factory ID must have.factoryiterface at the ed. For simplicity, whe talkig about test cofiguratios, we will leave that off, but it should appear i the file. For more iformatio about the factory_fider.ii file, see the descriptio of the factory_fider.ii file i the File Formats, Data Descriptios, MIBs, ad System Processes Referece. Local Factories A domai ca specify which of its factories ca be accessed by other domais. This is specified i a sectio begiig with *DM_LOCAL_FACTORIES. If the factory_fider.ii file does ot exist, or if it exists ad this sectio does ot appear, or is empty, all local factories ca be accessed by remote domais. If the sectio exists ad cotais the keyword Noe, oe of the local factories are exportable; that is, oe are allowed to be foud by a remote FactoryFider. If the sectio exists, it ca cotai a list of factories available to remote domais. For example, 3-20 Usig the BEA Tuxedo Domais Compoet

117 Types of CORBA Domai Cofiguratios *DM_LOCAL_FACTORIES fa.factoryiterface fb.factoryiterface This specifies that factories fa ad fb are fidable from other domais. All factories other tha factories explicitly listed are ot fidable. Ulike remote factories, there is o provisio for a alias with local factories. Note: The factory_fider.ii ad DMCONFIG files must be coordiated, that is, if the factory_fider.ii file declares aother domai to have accessible factories, there must be a way i DMCONFIG to get to that domai. Types of CORBA Domai Cofiguratios Whe usig the multiple domais feature, you ca cofigure two types of cofiguratios: directly coected domais ad idirectly coected domais. You, as the admiistrator, cofigure both types usig the domai cofiguratio file, DMCONFIG. Directly Coected Domais It is possible for every domai i a eterprise to have a gateway to every other domai it might use. Such a cofiguratio has the advatage that a request goes directly to the target domai, with the miimum of delay. Such a -way cofiguratio is quite reasoable whe the umber of domais is small, but each ew domai requires two ew gateways. At some poit, a admiistrator may cosider a differet cofiguratio, givig up speed of delivery for ease of maagemet of domai coectios. This is whe the ability to cofigure idirectly coected domais becomes advatageous. Idirectly Coected Domais A admiistrator should cosider what the likely traffic patters are. Domais that have oly occasioal iteractios are cadidates for gateway removal. Sice there will still be iteractios, it must still be possible to reach the other domai. The techique used is to route the request through a itermediate domai that does have direct access Usig the BEA Tuxedo Domais Compoet 3-21

118 3 Plaig ad Cofigurig CORBA Domais to the target domai. For example, we might have three domais, A, B, ad C. Domais A ad B are directly coected ad Domais B ad C are directly coected, but A ad C are ot directly coected (see Figure 3-2). For Domais A ad C to commuicate, they must use domai B as the itermediary. Therefore, the DMCONFIG file for Domai A must state that it is possible to coect to domai C by goig through Domai B (ad vice versa). That is, the coectivity is: Domais A <-> B <-> C Gateways GAB GBA GBC GCB Domai A has a gateway process, GAB (the Gateway from A to B), that coects to Domai B. The Domai A DMCONFIG file states that GAB acts as a gateway to two domais, Domais B ad C. The DMCONFIG file for Domai C has a similar cofiguratio, statig that GCB is coected to B ad A. The DMCONFIG file for Domai B has two gateway processes, oe which coects to A (GBA) ad oe which coects to C (GBC). This is called a idirect coectio. Give this idirect coectio, whe a server i A ivokes a request o a object i C, BEA Tuxedo CORBA server kows that it ca sed the request to gateway GAB. The BEA Tuxedo gateway does ot kow that its parter gateway i B caot service the request itself, but that is acceptable. Oce the request is i domai B, it is routed through GBC to C, which ca service the request. Thus, the request is serviced with oe extra hop. It is eve possible for the two gateways i Domai B to be a sigle gateway, so that there is ot a extra hop withi B. I effect, the same processig occurs i Domai B, but it all occurs withi a sigle gateway process. Figure 3-2 Idirectly Coected Domais 3-22 Usig the BEA Tuxedo Domais Compoet

119 Examples: Cofigurig Multiple CORBA Domais Examples: Cofigurig Multiple CORBA Domais The followig sectios provide examples of how to cofigure directly coected domais. Note: These examples are provided for iformatioal purposes oly. If you wat to use these examples, you will have to chage the APPDIR, TUXCONFIG, ad TUXDIR variables to match your eviromet. Also, you will have to substitute appropriate iformatio wherever text is eclosed by left (<) ad right (>) agle brackets (for example, <App Server Name>) ad delete the agle brackets. Sample UBBCONFIG Files Listig 3-4, Listig 3-5, ad Listig 3-6 show the UBBCONFIG files for three directly coected domais: Here, There, ad Yoder. Note: To use these files, you must replace host with the ame of the local machie. Listig 3-4 UBBCONFIG File for the Here Domai Copyright (c) 1999 BEA Systems, Ic. All rights reserved RESOURCES *RESOURCES IPCKEY DOMAINID HereD MASTER LAPP Usig the BEA Tuxedo Domais Compoet 3-23

120 3 Plaig ad Cofigurig CORBA Domais MODEL LDBAL SHM N MACHINES *MACHINES <host> GROUPS *GROUPS LMID=LAPP APPDIR="/tst1/wle4.2/test_dom/t07: /tst1/wle4.2/dec_uix/wlemdomai" TUXCONFIG="/tst1/wle4.2/test_dom/tuxcofig" TUXDIR="/lclobb/lc" MAXWSCLIENTS=10 DEFAULT: LMID=LAPP ICEGRP GRPNO=11 OPENINFO=NONE GROUP1 GRPNO=21 OPENINFO=NONE LDMGRP GRPNO=3 LGWGRP GRPNO=4 SERVERS *SERVERS DEFAULT: CLOPT="-A" DMADM SRVGRP=LDMGRP SRVID=1 GWADM SRVGRP=LGWGRP SRVID=1 GWTDOMAIN SRVGRP=LGWGRP SRVID=2 TMSYSEVT SRVGRP=ICEGRP SRVID=1 TMFFNAME SRVGRP=ICEGRP SRVID=2 CLOPT="-A -- -N -M -f <FF ii file for Here>" TMFFNAME SRVGRP=ICEGRP SRVID=3 CLOPT="-A -- -N" TMFFNAME SRVGRP=ICEGRP SRVID=4 CLOPT="-A -- -F" <App Server Name> SRVGRP=GROUP1 SRVID=2 ISL SRVGRP=GROUP1 SRVID=1 CLOPT="-A -- -d /dev/tcp - //<host>:<port>" SERVICES *SERVICES 3-24 Usig the BEA Tuxedo Domais Compoet

121 Examples: Cofigurig Multiple CORBA Domais Listig 3-5 UBBCONFIG File for the There Domai Copyright (c) 1999 BEA Systems, Ic. All rights reserved RESOURCES *RESOURCES IPCKEY DOMAINID ThereD MASTER LAPP1 MODEL SHM LDBAL N MACHINES *MACHINES <host> LMID=LAPP1 APPDIR="D:\test_dom\t07;D:\Iceberg\qa\orb\bld\wlemdomai" TUXCONFIG="D:\test_dom\tuxcofig" TUXDIR="D:\Iceberg" MAXWSCLIENTS=10 GROUPS *GROUPS DEFAULT LMID=LAPP1 ICEGRP GRPNO=11 OPENINFO=NONE GROUP1 GRPNO=21 OPENINFO=NONE LDMGRP GRPNO=3 LGWGRP GRPNO=4 SERVERS *SERVERS DEFAULT: CLOPT="-A" DMADM SRVGRP=LDMGRP SRVID=1 GWADM SRVGRP=LGWGRP SRVID=1 GWTDOMAIN SRVGRP=LGWGRP SRVID=2 TMSYSEV SRVGRP=ICEGRP SRVID=1 TMFFNAME SRVGRP=ICEGRP SRVID=2 CLOPT="-A -- -N -M -f <FF ii file for There>" TMFFNAME SRVGRP=ICEGRP SRVID=3 CLOPT="-A -- -N" TMFFNAME SRVGRP=ICEGRP SRVID=4 CLOPT="-A -- -F" <App Server Name> SRVGRP=GROUP1 SRVID=2 ISL SRVGRP=GROUP1 SRVID=1 Usig the BEA Tuxedo Domais Compoet 3-25

122 3 Plaig ad Cofigurig CORBA Domais SERVICES *SERVICES CLOPT="-A -- -d /dev/tcp - //<host>:<port>" Listig 3-6 UBBCONFIG File for the Yoder Domai Copyright (c) 1999 BEA Systems, Ic. All rights reserved RESOURCES *RESOURCES IPCKEY DOMAINID YoderD MASTER LAPP MODEL SHM LDBAL N MACHINES *MACHINES <host> LMID=LAPP APPDIR="/tst1/wle4.2/test_dom/t07p: /tst1/wle4.2/<host3>/wlemdomai" TUXCONFIG="/tst1/wle4.2/test_dom/<host3>/tuxcofig" TUXDIR="/lclobb/lc" MAXWSCLIENTS=10 GROUPS *GROUPS DEFAULT: LMID=LAPP ICEGRP GRPNO=11 OPENINFO=NONE GROUP1 GRPNO=21 OPENINFO=NONE LDMGRP GRPNO=3 LGWGRP SERVERS *SERVERS GRPNO=4 DEFAULT: CLOPT="-A" DMADM SRVGRP=LDMGRP SRVID= Usig the BEA Tuxedo Domais Compoet

123 Examples: Cofigurig Multiple CORBA Domais GWADM SRVGRP=LGWGRP SRVID=1 GWTDOMAIN SRVGRP=LGWGRP SRVID=2 TMSYSEVT SRVGRP=ICEGRP SRVID=1 TMFFNAME SRVGRP=ICEGRP SRVID=2 CLOPT="-A -- -N -M" TMFFNAME SRVGRP=ICEGRP SRVID=3 CLOPT="-A -- -N" TMFFNAME SRVGRP=ICEGRP SRVID=4 CLOPT="-A -- -F" <App Server Name> SRVGRP=GROUP1 SRVID=2 ISL SRVGRP=GROUP1 SRVID=1 CLOPT="-A -- -d /dev/tcp - //<host>:<port>" SERVICES *SERVICES Sample DMCONFIG File Listig 3-7, Listig 3-8, ad Listig 3-9 show the DMCONFIG files for three directly coected domais: Here, There, ad Yoder. Note: To use Listig 3-7 i a multidomai cofiguratio, you must replace host1 with the ame of the local machie for the Here domai, replace host2 with the ame of the local machie for the There domai, ad replace host3 with the ame of the local machie for the Yoder domai, Listig 3-7 DMCONFIG File for the Local Machie i the Here Domai i a Three-Domai Cofiguratio Copyright (c) 1999 BEA Systems, Ic. All rights reserved Tuxedo DOMAIN CONFIGURATION FILE *DM_RESOURCES VERSION=U22 DM_LOCAL_DOMAINS *DM_LOCAL_DOMAINS Usig the BEA Tuxedo Domais Compoet 3-27

124 3 Plaig ad Cofigurig CORBA Domais LDOM1 GWGRP=LGWGRP TYPE=TDOMAIN DOMAINID="HereG" DM_REMOTE_DOMAINS *DM_REMOTE_DOMAINS TDOM1 TDOM2 TYPE=TDOMAIN DOMAINID="ThereG" TYPE=TDOMAIN DOMAINID="YoderG" DM_TDOMAIN *DM_TDOMAIN LDOM1 NWADDR="//<host1>:<tcpport>" TDOM1 NWADDR="//<host2>:<tcpport>" TDOM2 NWADDR="//<host3>:<tcpport>" DM_LOCAL_SERVICES *DM_LOCAL_SERVICES "//HereD" DM_REMOTE_SERVICES *DM_REMOTE_SERVICES "//ThereD "//YoderD "RDOM=TDOM1 "RDOM=TDOM2 Note: To use Listig 3-8 i a multidomai cofiguratio, you must replace host1 with the ame of the local machie for the There domai, replace host2 with the ame of the local machie for the Here domai, ad replace host3 with the ame of the local machie for the Yoder domai, Listig 3-8 DMCONFIG File for the There Domai i a Three-Domai Cofiguratio Copyright (c) 1999 BEA Systems, Ic. All rights reserved 3-28 Usig the BEA Tuxedo Domais Compoet

125 Examples: Cofigurig Multiple CORBA Domais Tuxedo DOMAIN CONFIGURATION FILE *DM_RESOURCES VERSION=U22 DM_LOCAL_DOMAINS *DM_LOCAL_DOMAINS LDOM1 GWGRP=LGWGRP TYPE=TDOMAIN DOMAINID="ThereG" DM_REMOTE_DOMAINS *DM_REMOTE_DOMAINS TDOM1 TDOM2 TYPE=TDOMAIN DOMAINID="HereG" TYPE=TDOMAIN DOMAINID="YoderG" DM_TDOMAIN *DM_TDOMAIN LDOM1 NWADDR="//<host1>:<tcpport>" TDOM1 NWADDR="//<host2>:<tcpport>" TDOM2 NWADDR="//<host3>:<tcpport>" DM_LOCAL_SERVICES *DM_LOCAL_SERVICES "//ThereD" DM_REMOTE_SERVICES *DM_REMOTE_SERVICES "//HereD "//YoderD "RDOM=TDOM1 "RDOM=TDOM2 Usig the BEA Tuxedo Domais Compoet 3-29

126 3 Plaig ad Cofigurig CORBA Domais Note: To use Listig 3-9 i a multidomai cofiguratio, you must replace host1 with the ame of the local machie for the Yoder domai, replace host2 with the ame of the local machie for the Here domai, ad replace host3 with the ame of the local machie for the There domai. Listig 3-9 DMCONFIG File for the Yoder Domai i a Three-Domai Cofiguratio Copyright (c) 1999 BEA Systems, Ic. All rights reserved Tuxedo DOMAIN CONFIGURATION FILE *DM_RESOURCES VERSION=U22 DM_LOCAL_DOMAINS *DM_LOCAL_DOMAINS LDOM1 GWGRP=LGWGRP TYPE=TDOMAIN DOMAINID="YoderG" DM_REMOTE_DOMAINS *DM_REMOTE_DOMAINS TDOM1 TDOM2 TYPE=TDOMAIN DOMAINID="HereG" TYPE=TDOMAIN DOMAINID="ThereG" DM_TDOMAIN *DM_TDOMAIN LDOM1 NWADDR="//<host1>:<tcpport>" TDOM1 NWADDR="//<host2>:<tcpport>" TDOM2 NWADDR="//<host3>:<tcpport>" DM_LOCAL_SERVICES *DM_LOCAL_SERVICES 3-30 Usig the BEA Tuxedo Domais Compoet

127 Examples: Cofigurig Multiple CORBA Domais "//YoderG" DM_REMOTE_SERVICES *DM_REMOTE_SERVICES "//HereD "//ThereD "RDOM=TDOM1 "RDOM=TDOM2 Sample factory_fider.ii File This sectio shows the factory_fider.ii files for the Here ad There domais. The Yoder domai does ot require a factory_fider.ii file. Listig 3-10 factory_fider.ii File for the Here Local Domai Copyright (c) 1999 BEA Systems, Ic. All rights reserved Factory Fider Iitializatio file for Domai "Here". This is the local Domai. DM_LOCAL_FACTORIES *DM_LOCAL_FACTORIES "AFactory.FactoryIterface" DM_REMOTE_FACTORIES *DM_REMOTE_FACTORIES "AFacYoder.FactoryIterface" DOMAINID="YoderD" RNAME="AFactory.FactoryIterface" "BFactory.FactoryIterface" DOMAINID="YoderD" Usig the BEA Tuxedo Domais Compoet 3-31

128 3 Plaig ad Cofigurig CORBA Domais Listig 3-11 factory_fider.ii File for the There Remote Domai Copyright (c) 1999 BEA Systems, Ic. All rights reserved Factory Fider Iitializatio file for Domai "There". This is a remote domai. DM_LOCAL_FACTORIES *DM_LOCAL_FACTORIES "AFactory.FactoryIterface" DM_REMOTE_FACTORIES *DM_REMOTE_FACTORIES "AFacYoder.FactoryIterface" DOMAINID="YoderD" RNAME="AFactory.FactoryIterface" "BFactory.FactoryIterface" DOMAINID="YoderD" 3-32 Usig the BEA Tuxedo Domais Compoet

129 CHAPTER 4 Admiisterig Domais This topic icludes the followig sectios: Usig Domais Ru-time Admiistrative Commads Usig the Admiistrative Iterface, dmadmi(1) Usig the Domais Admiistrative Server, DMADM(5) Usig the Gateway Admiistrative Server, GWADM(5) Usig the Gateway Process Maagig Trasactios i a Domais Eviromet Usig Domais Ru-time Admiistrative Commads To itegrate the Domais compoet with a existig BEA Tuxedo applicatio, add etries for domai gateway groups ad gateway servers to the TUXCONFIG file. You ca use either the tmcofig(1) (see tmcofig, wtmcofig(1)) or tmadmi(1) commad to add a multiple-domai cofiguratio to a ruig BEA Tuxedo applicatio. You ca also use tmadmi to list the iformatio available i the bulleti board for Domai gateway groups ad idividual gateways. Usig the BEA Tuxedo Domais Compoet 4-1

130 4 Admiisterig Domais Oce your Domais eviromet is cofigured ad itegrated, you ca admiister it dyamically usig a set of admiistrative tools provided by the Domais software. For example, you ca specify ad modify the list of services that are accessible across applicatios. The Domais software preserves the characteristics of the BEA Tuxedo programmig iterface (ATMI) ad exteds the scope of the ATMI so that cliets ca ivoke services across domais. This fuctioality allows programmers to expad or partitio applicatios without chagig ay applicatio code. The followig figure shows the relatioship betwee admiistrative commads ad servers i the Domais admiistrative subsystem. Figure 4-1 Domais Ru-time Admiistratio Domais offers the followig admiistrative commads: dmadmi(1) commad, a geeric admiistrative service eables admiistrators to cofigure, moitor, ad tue domai gateway groups dyamically, ad to update the Domais cofiguratio file (BDMCONFIG) while the BEA Tuxedo applicatio is ruig. The commad acts as a frot-ed process that traslates admiistrative commads ito service requests which it the seds to the DMADMIN service, a geeric admiistrative service advertised by the DMADM server. The DMADMIN service ivokes the validatio, retrieval, or update of fuctios provided i the DMADM server to maitai the BDMCONFIG file. DMADM(5), the gateway group admiistrative server provides the admiistrative processig required for updatig the Domais cofiguratio. This server acts as a back-ed to the dmadmi commad. It provides a registratio service to 4-2 Usig the BEA Tuxedo Domais Compoet