1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
|
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe PageMill 2.0 Mac">
<TITLE>Options for TAO Components</TITLE>
</HEAD>
<BODY text = "#000000"
link="#000fff"
vlink="#ff0f0f"
bgcolor="#ffffff">
<HR><P>
<H3 ALIGN=CENTER>Options for TAO Components</H3>
<H3>Overview</H3>
<blockquote>
<P>Certain components in TAO such as the ORB Core or Object Adapter
can be tuned by users by providing value for options or environment
variables to them. These options are commonly specified as (1)
environment variables or (2) strings passed on the command-line. They
are generally passed to component initialization methods for
consumption.</P>
<p>Both command-line options and environment variables are used to
control the global ORB features like the IOR format or ORB's
bootstraping methods. Options in <code>svc.conf</code> file on the
other hand provides a mechanism to fine-tune the internal components
in TAO and they are specific to individual components.
<code>svc.conf</code> files are not required to run TAO programs.
However, if you know the behavior of your programs, you can tune-up
your programs and use various optimization provided by TAO thru the
use of svc.conf files.</p>
<P><EM>Programmer's Note:</EM> the internal structure for options is
the traditional <CODE>argc</CODE>/<CODE>argv</CODE> vector of strings
style popularized by C and Unix. By convention, an initialization
method will consume, <EM>i.e.</EM>, remove from the vector, any
options that it recognizes.</P> </blockquote>
<HR><P>
<H3><A NAME="ev">Environment Variables</A></H3>
The following environment variables are supported by TAO:
<BLOCKQUOTE>
<P><TABLE BORDER="2" CELLSPACING="2" CELLPADDING="0" >
<TR>
<TH>Environment Variable</TH>
<TH>Description</TH></TR>
<TR>
<TD><CODE>NameServiceIOR</CODE> <EM>which</EM></TD>
<TD>
Specifies which IOR the Naming Service is listening on.
</TD></TR>
<TR>
<TD><CODE>NameServicePort</CODE> <EM>which</EM></TD>
<TD>
Specifies which port the Naming Service is listening on.
</TD></TR>
<TR>
<TD><CODE>TradingServiceIOR</CODE> <EM>which</EM></TD>
<TD>
Specifies which IOR the Trading Service is listening on.
</TD></TR>
<TR>
<TD><CODE>TradingServicePort</CODE> <EM>which</EM></TD>
<TD>
Specifies which port the Trading Service is listening on.
</TD></TR>
</TABLE>
</P>
</BLOCKQUOTE>
<HR><P>
<H3>Types of Options</H3>
<blockquote>
<P>The following components can be tuned via options:</P>
<UL>
<LI><A HREF="#ORB"><CODE>CORBA::ORB</CODE></A>
<LI><A HREF="#ResourceFactory"><CODE>TAO_Resource_Factory</CODE></A>
<LI><A HREF="#DefaultServer"><CODE>TAO_Default_Server_Strategy_Factory</CODE></A>
<LI><A HREF="#DefaultClient" TARGET="_top"><CODE>TAO_Default_Client_Strategy_Factory</CODE></A>
</UL>
Typically, CORBA::ORB options are set via command line parameters,
while the rest of the options are set via the service configurator
(svc.conf) file.
</blockquote>
<blockquote>
<H3><CODE>CORBA::ORB</CODE><A NAME="ORB"></A></H3>
<blockquote>
<P><TABLE BORDER="2" CELLSPACING="2" CELLPADDING=
"0">
<TR>
<TH>Option</TH>
<TH>Description</TH></TR>
<!-- <TR NAME="ORBsvcconf"> -->
<TD><CODE>-ORBsvcconf</CODE> <EM>config file name</EM></TD>
<TD>Specifies the name of the file from which it will read dynamic service configuration
directives <EM>ala</EM> ACE's Service Configurator.</TD></TR>
<TD><CODE>-ORBsvcconfdirective</CODE> <EM>directivestring</EM></TD>
<TD>Specifies a service configuration
directive, which is passed to ACE's Service Configurator.</TD></TR>
<TR>
<TD><CODE>-ORBdaemon</CODE></TD>
<TD>Specifies that the ORB should <I>daemonize</I> itself.</TD></TR>
<TR>
<TD><CODE>-ORBdebug</CODE></TD>
<TD>Turns on the output of debugging messages within ACE's Service Configurator
componentry.</TD></TR>
<TR>
<TD><CODE>-ORBdebuglevel</CODE> <EM>level</EM></TD>
<TD>Control the level of debugging in the ORB. Higher number produce
more output (try 10).
</TD></TR>
<TR>
<TD><CODE>-ORBhost</CODE> <EM>hostname</EM></TD> <TD><a
name="-ORBhost"></a>Tells the ORB to listen for requests on the
interface associated with the host named
<I><EM>hostname</EM></I>.</TD></TR>
<TR>
<TD><CODE>-ORBport</CODE> <EM>portspec</EM></TD> <TD>Tells the ORB to
listen for requests on the port specified by
<I><EM>portspec</EM></I>. If not specified, the OS gets to choose a
random empty port.</TD>
</TR>
<TR>
<TD><CODE>-ORBobjrefstyle</CODE> <EM>which</EM></TD>
<TD>Specifies the user-visible style of object references. The range of values
is <CODE>IOR</CODE>, which is the traditional nonsensical object reference,
or <CODE>URL</CODE>, which looks more like a URL.</TD></TR>
<TR>
<TD><CODE>-ORBrcvsock</CODE> <EM>receive buffer size</EM></TD>
<TD><A NAME="-ORBrcvsock"></a>Specify the size of the socket receive buffer as a positive, non-zero integer.
If not specified, the system-dependent default is used.</TD></TR>
<TR>
<TD><CODE>-ORBsndsock</CODE> <EM>send buffer size</EM></TD>
<TD><A NAME="-ORBsndsock"></a>Specify the size of the socket send buffer as a positive, non-zero integer.
If not specified, the system-dependent default is used.</TD></TR>
<TR>
<TD><CODE>-ORBnameserviceport</CODE> <EM>portspec</EM></TD>
<TD>Specifies which port the Naming Service is listening on.</TD></TR>
<TR>
<TD><CODE>-ORBnameserviceior</CODE> <EM>ior</EM></TD>
<TD>Specifies the IOR for the Naming Service.</TD></TR>
<TR>
<TD><CODE>-ORBtradingserviceior"</CODE> <EM>ior</EM></TD>
<TD>Specifiles the IOR for the Trading Service.</TD></TR>
<TR>
<TD><CODE>-ORBtradingserviceport"</CODE> <EM>portspec</EM></TD>
<TD>Specifies to which port the tradingservice is listening
on.</TD></TR>
<TR>
<TD><CODE>-ORBcollocation</CODE> <EM>yes/no</EM></TD>
<TD>Specifies the use of collocation object optimization. Default is yes.</TD></TR>
<TR>
<TD><CODE>-ORBpreconnect</CODE> <EM>host</EM><STRONG>:</STRONG><EM>port</em>[<STRONG>,</STRONG><EM>host</EM><STRONG>:</STRONG><EM>port</em>...]</TD>
<TD><A name="-ORBpreconnect"></a>Pre-establishes a blocking connection to each listed
<em>host</em>:<em>port</em> combination. If a connection cannot
be established, a warning is announced and it continues with the
next listed. Listing the same combination multiple times will
properly establish multiple connections to that endpoint.</TD></TR>
<TR>
<TD><CODE>-ORBcdrtradeoff</CODE> <EM>maxsize</EM></TD>
<TD><A name="-ORBCDRtradeoff"></a>Control the strategy to tradeoff
between copy vs no copy marshalling of octet sequences.
If an octet sequence is smaller than <EM>maxsize</EM> and the current
message block contains enough space for it the octet sequence is
copied instead of appended to the CDR stream.</TD></TR>
<TR>
<TD><CODE>-ORBgioplite</CODE></TD>
<TD><A name="-ORBgioplite"></a>Enable a lightweight version of the
GIOP protocol. This protocol removes some of the fields in
the GIOP and the Request header. It only works on
homogenous environments..</TD></TR>
<TR>
<TD><CODE>-ORBdotteddecimaladdresses</CODE> <EM>boolean (0 / 1)</EM></TD>
<TD><A name="-ORBdotteddecimaladdresses"></a> Use the dotted decimal
notation for addresses.</TD></TR>
<TR>
<TD><CODE>-ORBInitRef</CODE> <EM>ObjectId=IOR</EM></TD>
<TD><A name="-ORBInitRef"></a> Allows specification of an arbitrary object reference for an initial service. The IOR could be in the one of the following formats : OMG IOR, URL or iioploc form. iioploc is a multiple end-point IORs understood by the string_to_object () and used as a boot-strapping mechanism by the resolve_initial_references (). The mappings specified through this argument override the orb-install-time defaults.</TD></TR>
<TR>
<TD><CODE>-ORBDefaultInitRef</CODE> <EM>IOR prefix</EM></TD>
<TD><A name="-ORBDefaultInitRef"></a> This argument allows resolution of initial references not explicitly specified with -ORBInitRef. It requires a URL prefix that, after appending a slash '/' and a simple object key, forms a new URL to identify an initial object reference. The URL prefix format currently supported is iioploc.</TD></TR>
</TABLE>
</P>
</blockquote>
<H3><CODE>TAO_Resource_Factory</CODE><A NAME="ResourceFactory"></A></H3>
<blockquote>
<P><TABLE BORDER="2" CELLSPACING="2" CELLPADDING="0">
<TR>
<TH>Option</TH>
<TH>Description</TH></TR>
<TR>
<TD><CODE>-ORBresources</CODE> <EM>which</EM></TD>
<TD>Specify whether each thread uses a global
(<em>which</em> = <code>global</code>) or a thread-specific
(<em>which</em> = <code>tss</code>) instance for the resources it returns.</TD></TR>
<TR>
<TD><CODE>-ORBreactorlock</CODE> <EM>which</EM></TD>
<TD><a name="-ORBreactorlock"></a>Specify whether the ORB reactor is
thread-safe
(<em>which</em> = <code>token</code>) or not
(<em>which</em> = <code>null</code>). Default is <code>token</code>.
<P>This option has been superseeded by
<CODE>-ORBreactortype</CODE>
</P>
</TD></TR>
<TR>
<TD><CODE>-ORBreactortype</CODE> <EM>which</EM></TD>
<TD><a name="-ORBcoltable"></a>Specify what kind of reactor does the
ORB use, the options are:
<TABLE BORDER="1" CELLSPACING="2" CELLPADDING="0">
<TR><TH><em>which</em></TH><TH>Reactor</TH></TR>
<TR><TD><CODE>select_mt<CODE></TD><TD>Use the
<CODE>ACE_Select_Reactor</CODE> with the usual
locking mechanism for this platform</TD></TR>
<TR><TD><CODE>select_st<CODE></TD><TD>Use the
<CODE>ACE_Select_Reactor</CODE> with null locks
</TD></TR>
<TR><TD><CODE>fl_reactor<CODE></TD><TD>Use the
<CODE>ACE_FlReactor</CODE> only available if ACE
was compiled with support for the FL toolkit
</TD></TR>
<TR><TD><CODE>xt_reactor<CODE></TD><TD>Use the
<CODE>ACE_FlReactor</CODE> only available if ACE
was compiled with support for the XWindows Toolkit
</TD></TR>
<TR><TD><CODE>WFMO<CODE></TD><TD>Use the
<CODE>ACE_WFMO_Reactor</CODE> only available on
Win32 platforms.
</TD></TR>
<TR><TD><CODE>MsgWFMO<CODE></TD><TD>Use the
<CODE>ACE_Msg_WFMO_Reactor</CODE> only available on
Win32 platforms.
</TD></TR>
</TABLE>
The default is <code>select_mt</code></TD></TR>
<TR>
<TD><CODE>-ORBcoltable</CODE> <EM>which</EM></TD>
<TD><a name="-ORBcoltable"></a>Specify whether each ORB uses a global
(<em>which</em> = <code>global</code>) or a per-ORB
(<em>which</em> = <code>orb</code>) collocation table.</TD></TR>
<TR>
<TD><CODE>-ORBinputcdrallocator</CODE> <EM>which</EM></TD>
<TD><a name="-ORBinputcdrallocator"></a>
Specify whether the ORB uses a global
(<em>which</em> = <code>global</code>)
or a per-thread (<em>which</em> = <code>tss</code>)
allocator for the incoming CDR buffers.
Though <CODE>tss</CODE> should give the
optimal performance;
we made the default <CODE>global</CODE>.
TAO optimizations for octet sequences will not work when
returning that data type if the allocator is
<CODE>tss</CODE>.
Using global allocator also allows the users to
take advantage of the TAO octet sequence
extensions to preserve the buffer after the upcall.
</TD></TR>
</TABLE>
</P>
</blockquote>
<H3><CODE>TAO_Default_Server_Strategy_Factory</CODE><A NAME="DefaultServer"></A></H3>
<p><em>Note:</em> <code>-ORBdemuxstrategy</code> flag has been changed to <code>-ORBsystemidpolicydemuxstrategy</code> and <code>-ORBuseridpolicydemuxstrategy</code>.
<p><em>Note:</em> <code>-ORBtablesize</code> flag has been changed to <code>-ORBactiveobjectmapsize</code>.
<blockquote>
<P><TABLE BORDER="2" CELLSPACING="2" CELLPADDING="0" >
<TR>
<TH>Option</TH>
<TH>Description</TH></TR>
<TR>
<TD><CODE>-ORBconcurrency</CODE> <EM>which</EM></TD> <TD>Specify which
concurrency strategy to use. Range of values is <code>reactive</code>
for a purely Reactor-driven concurrency strategy or
<code>thread-per-connection</code> for creating a new thread to
service each connection.</TD></TR> <TR>
<TD><CODE>-ORBactiveobjectmapsize</CODE> <EM>active object map
size</EM></TD> <TD>Specify the size of the active object map. If not
specified, the default value is 64.</TD></TR> <TR>
<TD><CODE>-ORBuseridpolicydemuxstrategy</CODE> <EM>user id policy
based demultiplexing strategy</EM></TD> <TD>Specify the demultiplexing
lookup strategy to be used with the user id policy. The
<EM>demultiplexing strategy</EM> can be one of <CODE>dynamic</CODE> or
<CODE>linear</CODE>. This option defaults to use the
<CODE>dynamic</CODE> strategy. </TD></TR> <TR>
<TD><CODE>-ORBsystemidpolicydemuxstrategy</CODE> <EM>system id policy
based demultiplexing strategy</EM></TD> <TD>Specify the demultiplexing
lookup strategy to be used with the system id policy. The
<EM>demultiplexing strategy</EM> can be one of <CODE>dynamic</CODE>,
<CODE>linear</CODE>, or <CODE>active</CODE>. This option defaults to
use the <CODE>active</CODE> strategy. </TD></TR> <TR>
<TD><CODE>-ORBuniqueidpolicyreversedemuxstrategy</CODE> <EM>unique id
policy based reverse demultiplexing strategy</EM></TD> <TD>Specify the
reverse demultiplexing lookup strategy to be used with the unique id
policy. The <EM>reverse demultiplexing strategy</EM> can be one of
<CODE>dynamic</CODE> or <CODE>linear</CODE>. This option defaults to
use the <CODE>dynamic</CODE> strategy. </TD></TR> <TR>
<TD><CODE>-ORBallowreactivationofsystemids</CODE> <EM>allows
reactivation of system ids</EM></TD> <TD>Specify whether system ids
can be reactivated, i.e., once an id that was generated by the system
has be deactivated, will the user reactivate a new servant using the
old id. If the user is not going to use this feature, the IORs can be
shortened, an extra comparison in the critical upcall path removed,
and some memory on the server side can be saved. The
<CODE>ORBallowreactivationofsystemids</CODE> can be <CODE>0</CODE> or
<CODE>1</CODE>. This option defaults to <CODE>1</CODE>. </TD></TR>
<TR>
<TD><CODE>-ORBactivehintinids</CODE> <EM>adds an active hint in
ids</EM></TD> <TD>Specify whether an active hint should be added to
ids. With active hints, ids can be found quickly. However, they lead
to larger IORs. Note that this option is disregarded
<CODE>-ORBallowreactivationofsystemids</CODE> is set to
<CODE>0</CODE>. The <EM>-ORBactivehintinids</EM> can be <CODE>0</CODE>
or <CODE>1</CODE>. This option defaults to <CODE>1</CODE>. </TD></TR>
<TR>
<TD><CODE>-ORBpoamapsize</CODE> <EM>poa map size</EM></TD> <TD>Specify
the size of the poa map. If not specified, the default value is
24.</TD></TR> <TR>
<TD><CODE>-ORBpersiententidpolicydemuxstrategy</CODE> <EM>persistent
id policy based demultiplexing strategy</EM></TD> <TD>Specify the
demultiplexing lookup strategy to be used with the persistent id
policy. The <EM>demultiplexing strategy</EM> can be one of
<CODE>dynamic</CODE> or <CODE>linear</CODE>. This option defaults to
use the <CODE>dynamic</CODE> strategy. </TD></TR> <TR>
<TD><CODE>-ORBtransientidpolicydemuxstrategy</CODE> <EM>transient id
policy based demultiplexing strategy</EM></TD> <TD>Specify the
demultiplexing lookup strategy to be used with the transient id
policy. The <EM>demultiplexing strategy</EM> can be one of
<CODE>dynamic</CODE>, <CODE>linear</CODE>, or
<CODE>active</CODE>. This option defaults to use the
<CODE>active</CODE> strategy. </TD></TR> <TR>
<TD><CODE>-ORBactivehintinpoanames</CODE> <EM>adds an active hint in
poa names</EM></TD> <TD>Specify whether an active hint should be added
to poa names. With active hints, poa names can be found quickly.
However, they lead to larger IORs. The
<EM>-ORBactivehintinpoanames</EM> can be <CODE>0</CODE> or
<CODE>1</CODE>. This option defaults to <CODE>1</CODE>. </TD></TR>
<TR>
<TD><CODE>-ORBthreadflags</CODE> <EM>thread flags</EM></TD>
<TD>Specify the flags used for thread creation. Flags can be any
logical-OR combination of <CODE>THR_DETACHED</CODE>,
<CODE>THR_BOUND</CODE>, <CODE>THR_NEW_LWP</CODE>,
<CODE>THE_SUSPENDED</CODE>.</TD></TR> <TR>
<TD><CODE>-ORBpoalock</CODE> <EM>lock type</EM></TD> <TD><a
name="-ORBpoalock"></a>Specify the type of lock to be used for POA
accesses. Possible values for <em>lock type</em> are
<code>thread</code>, which specifies that an inter-thread mutex is
used to guarantee exclusive acccess, and <code>null</code>, which
specifies that no locking be performed. The default is
<code>thread</code>.</TD></TR> <TR>
<TD><CODE>-ORBcoltbllock</CODE> <EM>lock type</EM></TD> <TD><a
name="-ORBcoltbllock"></a>Specify the type of lock to be used for the
global collocation table. Possible values for <em>lock type</em> are
<code>thread</code>, which specifies that an inter-thread mutex is
used to guarantee exclusive acccess, and <code>null</code>, which
specifies that no locking be performed. The default is
<code>thread</code>.</TD></TR> <TR>
<TD><CODE>-ORBconnectorlock</CODE> <EM>lock type</EM></TD> <TD><a
name="-ORBconnectorlock"></a>Specify the type of lock to be used by
the connector. Possible values for <em>lock type</em> are
<code>thread</code>, which specifies that an inter-thread mutex is
used to guarantee exclusive acccess, and <code>null</code>, which
specifies that no locking be performed. The default is
<code>thread</code>.</TD></TR> <TR>
</TABLE>
</P>
</blockquote>
<H3><CODE>TAO_Default_Client_Strategy_Factory</CODE><A NAME="DefaultClient"></A></H3>
<BLOCKQUOTE>
<P><TABLE BORDER="2" CELLSPACING="2" CELLPADDING="0" >
<TR>
<TH>Option</TH>
<TH>Description</TH></TR>
<TR>
<TD><CODE>-ORBiiopprofilelock</CODE> <EM>which</EM></TD>
<TD>
Specify, whether to use a lock for accessing the IIOP Profile or not.
Default is <code>thread</code>, which means that a lock is used. The
second option is <code>null</code>, which means a null lock is used.
This makes sense in case of optiziations and is allowed when
no forwarding is used or only a single threaded client.
</TD></TR>
<TR>
<TD><CODE>-ORBclientconnectionhandler</CODE> <EM>MT / ST / RW</EM></TD>
<TD><A name="-ORBclientconnectionhandler"></a>
ST means use the single-threaded client connection handler, i.e., the
leader follower model will not be used. However, ST does support
nested upcalls and handling of new requests while waiting for the
reply from a server. <p>
MT means use the multi-threaded client connection handler which uses
the leader follower model. This model allows the use of multiple
threads with a single Reactor. <p>
RW selects a strategy that simply blocks in recv() when waiting for a
response from the server instead of waiting in the Reactor. The RW
strategy only works when the application does not have to worry about
new request showing up when waiting for a response. Therefore, this
strategy is appropriate only for "pure" clients. Note that
applications with nested upcalls are not "pure" clients. Also note
that this strategy will only effect two way calls, since there is no
waiting for one way calls. This strategy can also be used in an
application that is both a client and a server if the server side is
handled by a separate thread and the client threads are "pure"
clients. <p>
Default for this option is MT.
</TD></TR>
</TABLE>
</P>
</BLOCKQUOTE>
</blockquote>
<P><HR><P>
Back to the TAO <A HREF="components.html">components documentation</A>.
<!--#include virtual="/~schmidt/cgi-sig.html" -->
</HTML>
|
