|
|
|
|
|
|
Configuring the Application
When configuring an RPC server, it is configured the same as a Request/Response server. One entry is needed in the SERVERS page for each RPC server or group of RPC servers. (MAX can be set to a value greater than one to configure multiple RPC servers with one entry.) An RQADDR can optionally be specified so that multiple instances of an RPC server share the same request queue (multiple servers, single queue configuration). The CONV parameter must be not specified or must be set to N (for example, CONV=N). See the sample configuration file in A Sample Application.
If a server will be part of a transaction, then it must be in a group on a machine that has a TLOGDEVICE. The GROUPS entry must be configured with a TMSNAME and an OPENINFO string that are used to access the associated resource manager.
It is optional to specify SERVICES entries. If specified, the service name must be the name described in the previous chapter, based on the interface name and version number. This entry is needed only if you want to give a specific load, priority, or transaction time that is different than the defaults. It can also be used to turn on the AUTOTRAN feature, which ensures that a transaction is automatically started for the service if the in-coming request is not in transaction mode. Do not use the service entry to specify buffer types BUFTYPE since the only buffer type handled is CARRAY. Also, do not specify ROUTING because routing is not supported for RPC requests.
The tmloadcf(1) command is used to load the ASCII configuration file into a binary TUXCONFIG file before the application is booted.
Note that entries for RPC servers can be added to a booted application using the tmconfig command, as described in tmconfig, wtmconfig(1) in the BEA Tuxedo Command Reference.
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|