This appendix provides information about arguments for VisiTransact commands and ORB_init() and environment variables used with VisiTransact.
“vbconsole”.
This command starts the VisiBroker Console. “ots”.
This command starts an instance of the VisiTransact Transaction Service.“vshutdown”.
This command shuts down an instance of the VisiTransact Transaction Service. “xa_resdir”.
This command starts an instance of the XA Resource Director, part of the Session Manager.“smconfig_server”.
This command starts an instance of the Session Manager Configuration Server.“vshutdown”.
This command shuts down an instance of the XA Resource Director or Session Manager Configuration Server. “smconfigsetup”.
This utility creates the connection profile for use with the Pluggable Resource Interface for creating a customized Session Manager.
To see the debug log statements from this service, set this property to true. For the various source names options for debug log filtering, see the Debug Logging properties section of the VisiBroker for C++ Developer's Guide. prompt>smconfig_server [-Dvbroker.sm.pstorePath=<path>]
[-Dvbroker.sm.configName=<name>] [-m{32|64}]
Provide the name of the Session Manager Configuration Server you're using. By default, the name assigned to the Session Manager Configuration Server is <host>_smcs where host is the name of the host on which you created the Session Manager profile. You can use this command to shutdown an instance of the VisiTransact Transaction Service that is embedded within an application process provided the -OTSexit_on_shutdown argument was passed to the application's ORB_init() method. For information about shutting down an instance of the VisiTransact Transaction Service that is embedded in an application process, see “Arguments for applications with an embedded VisiTransact Transaction Service instance”.
Use this argument to display the usage information for this command. If you use this argument, vshutdown ignores all other arguments and just gives you usage information.
• ots for VisiTransact Transaction Service
• rd for XA Resource Director
• smcs for Session Manager Configuration ServerIf you specify only the type, vshutdown lists all the services of that particular type and prompts you whether to shut them down or not. The name of the object to be shutdown. By default vshutdown looks up all the objects of the specified type and prompts you whether to shut them down or not. The host machine where the service resides that you wish to shutdown. By default vshutdown locates all the objects of a particular type and name (if mentioned) on the network and prompts you whether to shut them down or not.
Provide the name of the Session Manager Configuration Server you're using. By default, the name assigned to the Session Manager Configuration Server is <host>_smcs where host is the name of the server on which you created the Session Manager profile.
1 Enter smconfigsetup at the command prompt.Please enter the name for the new profile: quickstartAttribute name "native_handle_type"
New value for attribute Native Handle Type
(default value <ITSoracle9i_handles>) : ITSoracle9i_handleYou can pass arguments to ORB_init() which affect the VisiTransact Transaction Service and your application components. The following sections explain these options.As a component of VisiBroker, command line arguments are passed to VisiTransact components through the VisiBroker ORB initialization call ORB_init(). Therefore, in order for arguments specified on the command line to have effect on the VisiTransact operation in a given application process, applications must pass the original argc and argv arguments to ORB_init() from the main program. For example,The ORB_init() function will parse both ORB arguments and VisiTransact arguments, removing them from the argv vector before returning.By default, the first time you start a transaction with Current::begin(), an instance of the VisiTransact Transaction Service is found using the Smart Agent. You can specify an instance of the VisiTransact Transaction Service to use, and the timeout value for transactions, by using the arguments described in this section.You pass these arguments at the command line when starting your transactional server manually. Your application handles these command-line input arguments using the ORB_init() method as described in “Passing command-line arguments to ORB_init() using argc and argv”.The following table explains the arguments that can be passed to ORB_init() from the command line for applications that originate transactions.
VisiTransact uses the specified IOR for the requested Transaction Service (CosTransactions::TransactionFactory) to locate the desired instance of the VisiTransact Transaction Service on the network. This argument enables VisiTransact to operate without the use of a Smart Agent (osagent). For example, to start the billing C++ transactional server that uses the Accounting VisiTransact Transaction Service, you would use the following command:To start the Billing transactional server that uses the Accounting VisiTransact Transaction Service, and has a timeout period of 2400 seconds, you would use this commandIf you specify a combination of -Dvbroker.ots.currentHost and ‑Dvbroker.ots.currentName, the Smart Agent will find the named VisiTransact Transaction Service instance on the named host. If you specify the ‑Dvbroker.ots.currentFactory with either the -Dvbroker.ots.currentHost or ‑Dvbroker.ots.currentName, the Smart Agent will find the VisiTransact Transaction Service instance by IOR only—it ignores the other arguments.You pass these arguments at the command line when starting your transactional server manually. Your application handles these command-line input arguments using the ORB_init() method as described in “Passing command-line arguments to ORB_init() using argc and argv”.The following table explains the arguments that can be passed to ORB_init() from the command line for applications that embed an instance of the VisiTransact Transaction Service.
By default, the Session Manager Configuration Server for the machine where the Session Manager connection profile was created is used—<host>_smcs. The persistent store classes are located in <VBROKER_ADM>\its\session_manager by default.You pass these arguments at the command line when starting your transactional server manually. Your application handles these command-line input arguments using the ORB_init() method as described in “Passing command-line arguments to ORB_init() using argc and argv”.The following table explains the arguments that can be passed to ORB_init() from the command line for applications that use the Session Manager.
The name of the Session Manager Configuration Server (profileset). By default, this value is <host>_smcs where host is the name of the server on which you created the Session Manager profile. The path to the directory where the persistent store classes are located. By default, this is <VBROKER_ADM>\its\session_manager.