XDA 4.1 Tutorial: Setting up the Configuration GTO

Purpose: To create a configuration GTO using the XDA Configuration Utility (Config GUI). The resulting gto will be intended for the other tutorial examples but can be used as a template for other XDA encapsulated components.

Tutorial requirements: Click here to get descriptions of the software and environment variables.

Software	Required
Forte	No
.NET	No
Java	Yes
ACE+TAO	No
JAC	No
ANT	No
Environment Variable	Required
XDA_ROOT	Yes
ACE_ROOT	No
TAO_ROOT	No
ANT_HOME	No
JAVA_HOME	Yes
JACORB_HOME	Yes

Procedure:

1. To start the Config GUI, go to $(XDA_ROOT)/share/bin and run config.bat on Windows or config.sh on Unix.
2. To create a completely new configuration gto, select "New". The Config GUI will take you through a wizard containing 8 steps. Please refer to the XDA Configuration Utility User's Manual for a more in-depth guide to the tool. A typical place to save the completed configuration GTO is $(XDA_ROOT)/share/data/usr. The configuration GTO file shown here is saved as $(XDA_ROOT)/share/data/usr/xdausr_config_sample.gto, but only the WinXP set-up is shown. To run the tutorials, the user can either copy xdausr_config_sample.gto to xdausr_config.gto or create a new configuration gto using the Configuration Utility. In either case, the configuration gto must be modified to correspond to your installation of XDA. For example, the xda_home parameter for Unix installations will likely be different than the one set in xdausr_config_sample.gto.

   Step	Node	Type	Parameter Name	Sample Value	Description
   1	root				Conventional root of the configuration gto.
   		cfg:str_param	resource_manager	root.xda.res_mgr	The node path to your resource manager. If you are not using a resource manager, any string value can be used.
   		cfg:str_param	task_manager	xda.task_mgr	The name of the XDA Task Manager registered in the Naming Service.
   2	root.orb.tao_win				TAO configurations.
   		cfg:str_param	tao.ImplRepoService	-ORBInitRef ImplRepoService=file://C:/vc70tao/tao_imr.ior	Uses the IOR file created when you start the Implementation Repository.
   		cfg:str_param	tao.NameService	-ORBInitRef NameService=file://C:/vc70tao/tao_ns.ior	Uses the IOR file created when you start the Naming Service.
   		cfg:str_param	tao.ORBUseIMR	-ORBUseIMR 1	ORB command line argument.
   3	root.orb.jac_win				JacORB configurations.
   		cfg:str_param	jac.NameService	ORBInitRef.NameService=file://C:\vc70tao\ns.ior	Uses the IOR file created when you start the Naming Service.
   		cfg:str_param	jac.ImplRepoService	ORBInitRef.ImplementationRepository=file://C:\vc70tao\jac_imr.ior	Uses the IOR file created when you start the Implementation Repository Service.
   		cfg:str_param	jac.imr.table	jacorb.imr.table_file=C:\vc70tao\table.dat	Uses the table.dat created by the ImplRepoService to store registered names.
   4	root.env.std_win				Standard named Windows environment sets.
   5	root.env.std_unix				Standard named UNIX environment sets.
   6	root.user.xdausr_user_win				User information.
   		cfg:str_param	xda_home	C:/vc70tao	Typically the same as your XDA_ROOT environment variable.
   		cfg:str_param	user_home	C:/vc70tao/share/data/usr	A user home directory.
   		cfg:str_param	user_env	root.env.std_win	Should be set to a root.env node.
   		cfg:str_param	res_config_file	C:/vc70tao/share/data/res_cfg.gto	Optional; may set to the Resource Manager configuration GTO file.
   7a	root.xda.xdausr_win				Base configurations.
   		cfg:str_param	orb	root.orb.tao	Set to the appropriate root.orb node. For TAO, user root.orb.tao.
   		cfg:str_param	user	root.user.xdausr_user	Set to the appropriate root.user node.
   		cfg:str_param	name_context	xda	Set to any string to be used to store name bindings in the Naming Service.
   		cfg:str_v_param	add_onts	[C:/vc70tao/share/data/XDAexamples/geom_poly.gto]	Optional; vector/list of additional ontologies needed by an XDA component.
   		cfg:str_param	dbg_off		Optional; if present, indicates that XDA debugging should be turned off.
   7b	root.xda.xdausr_jac_win				Base configurations.
   		cfg:str_param	orb	root.orb.jac	Set to the appropriate root.orb node. For JAC ORB, use root.orb.jac.
   		cfg:str_param	user	root.user.xdausr_user	Set to the appropriate root.user node.
   		cfg:str_param	name_context	xda	Set to any string to be used to store name bindings in the Naming Service.
   		cfg:str_v_param	add_onts	[C:/vc70tao/share/data/XDAexamples/geom_poly.gto]	Optional; vector/list of additional ontologies needed by an XDA component.
   		cfg:str_param	dbg_off		Optional; if present, indicates that XDA debugging should be turned off.
   8	root.cfg.taskmaster				Intended for component specific configuration information.
   		cfg:str_param	cfg	root.xda.xdausr_win	XDA node used by the TaskMaster to find ORB components.

3. You can modify an existing configuration GTO by selecting "Modify" on the opening screen of the Config GUI. Select the node you wish to modify in the tree on the left-hand side of the GUI.

Discussion: Each XDA user should create a configuration GTO for his/her own use. The configuration GTO is the only way in which XDA components can be configured by the user. The configuration GTO that has been created for this tutorial is for a generic XDA component. For example, should your component require additional ontologies than the XDA system ontologies, you should either modify the add_onts parameter in the root.xda.<user_supplied_name> node or create a new node under root.xda whose add_onts parameter contains the needed ontologies.

---

Previous

Index

Next