build_dgw-build customized domain gateway process
build_dgw[-cdmtype] [-oname] [-v]
build_dgw is used to construct a customized BEA TUXEDO domain gateway module. The files included by the caller should include only the application buffer type switch and any required supporting routines. The command combines the files supplied by the -c option with the standard BEA TUXEDO libraries necessary to form a gateway load module. The load module is built by the cc(1) command described in UNIX System reference manuals which build_dgw invokes. The options to build_dgw have the following meaning:
-c dmtype
dmtype must appear in the domain type table located in $TUXDIR/udataobj/DMTYPE. Each line in this file has the form:
dmtype:access_module_lib:comm_libs:tm_typesw_lib:gw_typesw_lib
Using the dmtype value, build_dgw retrieves the corresponding entry from $TUXDIR/udataobj/DMTYPE. The access_module_lib specifies the libraries used by a this particular type of domain instantiation. The comm_libs parameter contains a list of the networking communications libraries used by the access module. The tm_typesw_lib parameter defines a list of libraries or object modules with the definition of the typed buffers used by the local application. If this parameter is not defined, the gateway will be linked with the default typed buffer definitions. The gw_typesw_lib parameter applies only to a gateway of type OSITP (see below) and defines a list of libraries or object modules used by the gateway to transform buffers into the protocol required by the remote domain. There should be a one-to-one mapping between the buffer types defined in the tm_typesw array (see typesw(5) and tuxtypes(5)) and the gw_typesw array. If this parameter is not defined, the gateway will be linked with the default typed buffer definitions provided with the OSITP instantiation.
Currently, dmtype may be set to one of the following values:
TDOMAIN
build_dgw command will use the standard BEA TUXEDO libnws.a networking library. This is the default option.
OSITP
-o name
GWTDOMAIN for the TDOMAIN type and GWOSITP for the OSITP type. Note that the name selected for the load module must also be the name used for the definition of the gateway in the *SERVERS section of the TUXCONFIG file.
-v
build_dgw should work in verbose mode. In particular, it writes the cc command to its standard output.
build_dgw normally uses the cc command to produce the a.out. In order to allow for the specification of an alternate compiler, build_dgw checks for the existence of a shell variable named CC. If CC does not exist in build_dgw 's environment, or if it is the string "", build_dgw will use cc as the compiler. If CC does exist in the environment, its value is taken to be the name of the compiler to be executed. Likewise, the shell variable CFLAGS is taken to contain a set of parameters to be passed to the compiler.
build_dgw is supported as a BEA TUXEDO-supplied compilation tool on UNIX operating systems only.
The following example shows how to build a domain gateway of type TDOMAIN.
CC=ncc CFLAGS="-I $TUXDIR/include"; export CC CFLAGS build_dgw -o DGW
The following example shows use of build_dgw for an OSI TP instantiation:
build_dgw -c OSITP -o OTPGW
For the /TDOMAIN and /OSITP instantiations, the DMTYPE file will contain the following entries:
TDOMAIN:$TUXDIR/lib/libgwt.a:$TUXDIR/lib/libnwi.a $TUXDIR/lib/libnws.a::
OSITP:$TUXDIR/lib/libgwo.a:-l xaptp -l ositp::
The paths for the libxaptp.a and libositp.a libraries are installation and provider dependent. The application administrator must specify the correct pathnames before building an OSITP gateway instantiation.
cc(1), ld(1) in UNIX System reference manuals , tuxtypes(5), typesw(5)