|
|
 |
| e-docs > Tuxedo > Using the Tuxedo TOP END Domain Gateway with ATMI Applications > Sample Configuration File for a TOP END Domain Gateway |
|
Using the Tuxedo TOP END Domain Gateway with ATMI Applications
|
Sample Configuration File for a TOP END Domain Gateway
This topic includes the following sections:
See Also
Sample Program Description
This sample program, which is an extension of Example 1 in the core BEA Tuxedo DMCONFIG(5) reference page, shows five Bank Branch domains communicating with a Central Bank Branch. Three of the Bank Branches run within one BEA Tuxedo system domain (TDomain). The fourth Branch runs under the control of another TP domain and uses OSI TP to communicate with that domain. Example 1 has been extended to include a TEDG with a single connection to a BEA TOP END system. The BEA TOP END system is running a banking application that offers services needed by the BEA Tuxedo application. Conversely, certain BEA Tuxedo services need to be available to BEA TOP END clients. A simple queuing example is also included.
Functions Available for the BEA TOP END EBANK Product
The BEA TOP END system, BANKSYS, offers a single product called EBANK. The following table lists the functions available for the EBANK product.
BEA Tuxedo Service Mappings for the EBANK Functions The following DM_REMOTE_SERVICES mappings are used to make the functions shown in the table Functions Available for BEA TOP END EBANK Product available to the BEA Tuxedo application. Additionally, the BEA TOP END RTQ TEQNAME and two services accessed via the queue, REPORT and UPDATE, are made available to the BEA Tuxedo application.
SERVICE and QUEUE Mappings for the BEA Tuxedo Service "balance" The following DM_LOCAL_SERVICES mappings are used to make the BEA Tuxedo service called balance available to the BEA TOP END system. Additionally, the BEA Tuxedo queue space qspace and its queue name qname are made available to the BEA TOP END system.
Note: Because this sample configuration includes multiple gateway types, the LDOM parameter is specified in the DM_LOCAL_SERVICES section for the balance entry. See Also
Sample DMCONFIG File for the TEDG
The DMCONFIG file for the Central Bank Branch is shown below. Entries specific to the TEDG configuration are shown in bold.
# TUXEDO DOMAIN CONFIGURATION FILE FOR THE CENTRAL BANK
#
#
*DM_LOCAL_DOMAINS
# <local domain name> <Gateway Group name> <domain type> <domain id> <log device>
# [<audit log>] [<blocktime>]
# [<log name>] [<log offset>] [<log size>]
# [<maxrdtran>] [<maxtran>]
# [<maxdatalen>] [<security>]
# [<tuxconfig>] [<tuxoffset>]
#
#
DEFAULT: SECURITY = NONE
c01 GWGRP = bankg1
TYPE = TDOMAIN
DOMAINID = "BA.CENTRAL01"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C01"
c02 GWGRP = bankg2
TYPE = OSITP
DOMAINID = "BA.CENTRAL02"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C02"
c03 GWGRP = bankg3
TYPE = TOPEND
DOMAINID = "CENTRALBKGW"
DMTLOGDEV = "/usr/apps/bank/DMTLOG"
DMTLOGNAME = "DMTLG_C03"
SECURITY = CLEAR
#
*DM_REMOTE_DOMAINS
#<remote domain name> <domain type> <domain id>
#
b01 TYPE = TDOMAIN
DOMAINID = "BA.BANK01"
b02 TYPE = TDOMAIN
DOMAINID = "BA.BANK02"
b03 TYPE = TDOMAIN
DOMAINID = "BA.BANK03"
b04 TYPE = OSITP
DOMAINID = "BA.BANK04"
b05 TYPE = TOPEND
DOMAINID = "BANK05"
*DM_TDOMAIN
#
# <local or remote domain name> <network address> [<nwdevice>]
#
# Local network addresses
c01 NWADDR = "//newyork.acme.com:65432" NWDEVICE ="/dev/tcp"
# Remote network addresses
b01 NWADDR = "//192.11.109.5:1025" NWDEVICE = "/dev/tcp"
b02 NWADDR = "//dallas.acme.com:65432" NWDEVICE = "/dev/tcp"
b03 NWADDR = "//192.11.109.156:4244" NWDEVICE = "/dev/tcp"
*DM_OSITP
#
#<local or remote domain name> <apt> <aeq>
# [<aet>] [<acn>] [<apid>] [<aeid>]
# [<profile>]
#
c02 APT = "BA.CENTRAL02"
AEQ = "TUXEDO.R.4.2.1"
AET = "{1.3.15.0.3},{1}"
ACN = "XATMI"
b04 APT = "BA.BANK04"
AEQ = "TUXEDO.R.4.2.1"
AET = "{1.3.15.0.4},{1}"
ACN = "XATMI"
*DM_TOPEND
#Local network addresses
c03 NWADDR = "//newyork.acme.com:65434"
TP_SYSTEM = "BANKSYS"
#Remote network addresses
b05 NWADDR = "//sandiego.acme.com:65434"
TP_SYSTEM = "BANKSYS"
*DM_LOCAL_SERVICES
#<service_name> [<Local Domain name>] [<access control>] [<exported svcname>]
# [<inbuftype>] [<outbuftype>]
#
#Not available to TOP END, no mapping
open_act ACL = branch LDOM=c01
close_act ACL = branch LDOM=c01
credit LDOM=c01
debit LDOM=c01
loan LDOM = c02 ACL = loans
#Services exported to TOP END and other domains
balance TYPE=SERVICE TE_PRODUCT="TUX" TE_FUNCTION="BALANCE" LDOM = c03
#Queues available to TOP END
qspace TYPE=QSPACE TE_RTQGROUP="TUXQUEUE" TE_RTQNAME="TUXQ" LDOM=c03
qname TYPE=QNAME TE_PRODUCT="TUX" TE_FUNCTION="QSERV" LDOM=c03
*DM_REMOTE_SERVICES
#<service_name> [<Remote domain name>] [<local domain name>]
# [<remote svcname>] [<routing>] [<conv>]
# [<trantime>] [<inbuftype>] [<outbuftype>]
#
tlr_add LDOM = c01 ROUTING = ACCOUNT
tlr_bal LDOM = c01 ROUTING = ACCOUNT
tlr_add RDOM = b04 LDOM = c02 RNAME ="TPSU002"
tlr_bal RDOM = b04 LDOM = c02 RNAME ="TPSU003"
#
# New TOP END services available to TUXEDO
DEFAULT: LDOM=c03 RDOM=b05
TYPE=SERVICE TE_PRODUCT="EBANK"
te_start TE_FUNCTION="START"
te_end TE_FUNCTION="END"
te_login TE_FUNCTION="LOGIN"
te_listacct TE_FUNCTION="LISTACCT"
te_getpayees TE_FUNCTION="GETPAYES"
te_elecpay TE_FUNCTION="ELECPAY"
te_bal TE_FUNCTION="BAL"
te_transfer TE_FUNCTION="TRANSFER"
te_withdrawl TE_FUNCTION="WITHDRAW"
te_deposit TE_FUNCTION="DEPOSIT"
#
#TOP END RTQ queues available to Tuxedo
DEFAULT: LDOM=c03 RDOM=b05 TYPE=QSPACE
tuxqspace TE_RTQGROUP="TEQGROUP" TE_RTQNAME="TEQNAME"
#
#TOP END services available to TUXEDO via tpenqueue and RTQ.
DEFAULT: LDOM=c03 RDOM=b05 TYPE=QNAME
te_report TE_PRODUCT="EBANK" TE_FUNCTION="REPORT"
te_update TE_PRODUCT="EBANK" TE_FUNCTION="UPDATE"
*DM_ROUTING
# <routing criteria> <field> <typed buffer> <ranges>
#
ACCOUNT FIELD = branchid BUFTYPE ="VIEW:account"
RANGES ="MIN - 1000:b01, 1001-3000:b02, *:b03"
*DM_ACCESS_CONTROL
#<acl name> <Remote domain list>
#
branch ACLIST = b01, b02, b03
loans ACLIST = b04
See Also
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||
