-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathconfigHostsDef.htm
428 lines (383 loc) · 24.4 KB
/
configHostsDef.htm
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
<!DOCTYPE html>
<html lang="en-us">
<head>
<title>The configHosts.txt File</title>
<meta http-equiv="X-UA-Compatible" content="IE=Edge">
<meta charset="UTF-8">
<link rel="stylesheet" href="style.css">
</head>
<body>
<!-- ********** Header 1 ******************** -->
<font class="subhead1">
The configHosts.txt File
</font>
<!-- ********** Header 2 ******************** -->
<p></p><font class="subhead2">
Overview
</font>
<p>This article describes the configHosts.txt file, its purpose and its
contents.</p>
<ul>
<a href="#Purpose" class = "subnav">
» Purpose of configHosts.txt</a><br>
<a href="#Settings" class = "subnav">
» Using the configHosts.txt file</a><br>
<a href="#CheckFile" class = "subnav">
» Verifying the Values in configHosts.txt</a><br>
<a href="#TechnicalContact" class = "subnav">
» Technical Contact</a><br>
</ul>
<p>For information on the external configuration file used for building
***Name Omitted***.dll, see the article on the
<a href="ConfigHostsDef.htm">***Name Omitted***</a> file.</p>
<!-- ********** Header 2 ******************** -->
<p></p><hr><font class="subhead2">
Purpose
</font>
<p>The configHosts.txt file is an external configuration file that aids in
dynamically changing the test and use environment. Its contents list host names and directories, both physical
and logical, that the source may be required to use. Therefore, if QA or production needs to change their
current host configuration, they need only change this file in order to make it work with the source. This is
especially true for Database hosts.
</p>
<p>These files (in QATE) are the responsibility of release management. They keep them in clearcase
and are responsible for rolling out changes to the QATE environment. You may find old versions in
the buildtools VOB. If your build requires
changes or a specific schema or confighosts.txt file to work properly, please note it in the
build request. If these changes are permanent, please note that as well, and we will put them
under source control. Please do not roll these files out to QATE yourself as it can create
confusion if we are not aware of these changes. At best, it means a little head-scratching as
we try to figure out where the new file came from. At worst, it can mean lost QA cycles.</p>
<!-- ********** Header 2 ******************** -->
<p></p><hr><font class="subhead2">
<a NAME="Settings">Using the configHosts.txt file</a>
</font>
<p>The configHosts.txt file must be located in the directory specific to the platform that uses it.
On NT boxes, it should be located in</p>
<ol><pre>D:\ebayconfig</pre></ol>
<p>On UNIX machines, it should be present in the current directory where the batch job is executing,
as specified in the configBuild.txt (~www/etc/configBuild.txt) file, or in</p>
<ol><pre>/usr/local/etc</pre></ol>
<p>Below is an example of a confighosts.txt file followed by the explanation
for each line:</p>
<ul><pre>
physical
FirstHost(e119_staging_acc, e119_staging_acc, acc_test, retryCount=1, delay=0, reanimate=0)
EverythingElseHost(e119_staging_main, e119_staging_main, bigfoot, retryCount=1, delay=2, reanimate=3)
logical
AccountsHostRetry(Sequential, FirstHost, EverythingElseHost)
AccountsHost(Single, FirstHost)
Default(Single, EverythingElseHost)
</pre></ul>
<!-- ********** Header 3 ******************** -->
<p></p><font class="subhead3">
Sections
</font>
<p>The configHosts.txt file is divided into two sections using labels in the
file: <b>physical</b> and <b>logical</b>. The <b>physical</b> section contains
the database topology information. The second section, <b>logical</b>, contains
logical mapping settings. Each of these two sections are represented in
configHosts.txt by a label of the same name. The settings for the
<b>physical</b> section continue until the <b>logical</b> label is reached.
After that point, the settings for the <b>logical</b> section are listed.</p>
<!-- ********** Header 3 ******************** -->
<p></p><font class="subhead3">
<a name="Physical">The Physical Section</a>
</font>
<p>The <b>physical</b> section contains two sets of database topology
configuration values, labeled <b>FirstHost</b> and <b>EverythingElseHost</b>.
</p>
<p>Configuration settings defined in the <b>physical</b> section are used later
in the <a href="#LogicalSection"><b>logical</b></a> section. For example, both
the <a href="#FirstHost"><b>FirstHost</b></a> and <a href="#EverythingElseHost">
<b>EverythingElseHost</b></a> labels are used by name in
<a href="#AccountsHostRetry"><b>AccountsHostRetry</b></a> in the <b>logical</b>
section.</p>
<!-- ********** Header 4 ******************** -->
<p><b>
<a name="FirstHost">The FirstHost Label</a>
</b></p>
<ul><font face="Courier New, Courier"><pre>
FirstHost(e119_staging_acc, e119_staging_acc, acc_test, retryCount=1, delay=0, reanimate=0)
</pre></font></ul>
<p>The first set of configuration values in the <b>physical</b> section,
<b>FirstHost</b>, pertain to login and access configuration. Table 1 shows the
values specified in the <b>FirstHost</b> label.</p>
<ul>
<table border="0" cellspacing="4" cellpadding="4" width="80%">
<tfoot><font class="P"><b>Table 1:</b> FirstHost Settings</font></tfoot>
<th bgcolor="#e0e0e0" width="10%"><p>Field</p></th>
<th bgcolor="#e0e0e0"width="30%"><p>Value in Example</p></th>
<th bgcolor="#e0e0e0" width="60%"><p>Purpose</p></th>
<tr>
<td align="center" valign="top">
<p>1</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">e119_staging_acc</font>
</td>
<td align="left" valign="top">
<p>The user name for login to the database.</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>2</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">e119_staging_acc</font>
</td>
<td align="left" valign="top">
<p>The password for login to the database.</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>3</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">acc_test</font>
</td>
<td align="left" valign="top">
<p>The instance as defined in the tsnames.ora file.</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>4</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">retryCount=1</font>
</td>
<td align="left" valign="top">
<p>The default number of times a database access request is retried if
the first request does not succeed. Use this default value, this feature is not
yet supported</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>5</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">delay=0</font>
</td>
<td align="left" valign="top">
<p>The number of seconds that the request waits before performing the
current action. Use this default value, this feature is not
yet supported</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>6</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">reanimate=0</font>
</td>
<td align="left" valign="top">
<p>The number of seconds that the requests waits before starting
reanimation. Use this default value, this feature is not
yet supported</p>
</td>
</tr>
</table>
</ul>
<!-- ********** Header 4 ******************** -->
<p><b>
<a name="EverythingElseHost">The EverythingElseHost Label</a>
</b></p>
<ul><font face="Courier New, Courier"><pre>
EverythingElseHost(e119_staging_main, e119_staging_main, bigfoot, retryCount=1, delay=2, reanimate=3)
</pre></font></ul>
<p>The second set of configuration values is represented by the
<b>EverythingElseHost</b> label. The values in <b>EverythingElseHost</b> are
the same as those in <a href="#FirstHost"><b>FirstHost</b></a>, but are used
for subsequent database accesses.</p>
<!-- ********** Header 3 ******************** -->
<p></p><font class="subhead3">
<a name="LogicalSection">The Logical Section</a>
</font>
<p>The label <b>logical</b> signals the end of the database topology
section (<a href="#Physical"><b>physical</b></a>) and the beginning of the
logical mapping section. The <b>logical</b> section consists of three sets of
mapping configuration settings, using the labels
<a href="#AccountsHostRetry"><b>AccountsHostRetry</b></a>,
<a href="#AccountsHost"><b>AccountsHost</b></a>, and
<a href="#Default"><b>Default</b></a>.</p>
<!-- ********** Header 4 ******************** -->
<p><b>
<a name="AccountsHostRetry">The AccountsHostRetry Label</a>
</b></p>
<ul><font face="Courier New, Courier">
<pre><font size="2">
AccountsHostRetry(Sequential, FirstHost, EverythingElseHost)
</font></pre>
</font>
</ul>
<p>Table 2 shows the settings defined in <b>AccountsHostRetry</b>. These settings
define the logical mapping topology of the database on subsequent accesses.
<b>AccountsHostRetry</b> sets the access type, and then uses login values specified
in <a href="#FirstHost"><b>FirstHost</b></a> and <a href="#EverythingElseHost"><b>EverythingElseHost</b></a>
(defined previously in the <a href="#Physical"><b>physical</b></a> section).</p>
<ul>
<table border="0" cellspacing="4" cellpadding="4" width="80%">
<tfoot><font class="P"><b>Table 2:</b> AccountsHostRetry Definitions</font></tfoot>
<th bgcolor="#e0e0e0" width="10%"><p>Field</p></th>
<th bgcolor="#e0e0e0"width="30%"><p>Value in Example</p></th>
<th bgcolor="#e0e0e0" width="60%"><p>Purpose</p></th>
<tr>
<td align="center" valign="top">
<p>1</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">Sequential</font>
</td>
<td align="left" valign="top">
<p>Defines the access type.</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>2</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">FirstHost</font>
</td>
<td align="left" valign="top">
<p>Defines the primary physical database topology.</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>3</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">EverythingElseHost</font>
</td>
<td align="left" valign="top">
<p>Defines the secondary physical database topology.</p>
</td>
</tr>
</table>
</ul>
<!-- ********** Header 4 ******************** -->
<p><b> <a name="AccountsHost">The AccountsHost Label</a> </b></p>
<ul>
<font face="Courier New, Courier">
<pre><font size="2">
AccountsHost(single, FirstHost)
</font></pre>
</font>
</ul>
<p>The settings defined in <b>AccountsHost</b>, define the logical mapping database
access type on the initial access. <b>AccountsHost</b> specifies the access
type and uses login information previously given in the <a href="#FirstHost"><b>FirstHost</b></a>
label (in the <a href="#Physical"><b>physical</b></a> section). Table 3 shows
the values in <b>AccountsHost</b>.</p>
<ul>
<table border="0" cellspacing="4" cellpadding="4" width="80%">
<tfoot><font class="P"><b>Table 3:</b> AccountsHost Definitions</font></tfoot>
<th bgcolor="#e0e0e0" width="10%"><p>Field</p></th>
<th bgcolor="#e0e0e0"width="30%"><p>Value in Example</p></th>
<th bgcolor="#e0e0e0" width="60%"><p>Purpose</p></th>
<tr>
<td align="center" valign="top">
<p>1</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">Single</font>
</td>
<td align="left" valign="top">
<p>Define the access type.</p>
</td>
</tr>
<tr>
<td align="center" valign="top">
<p>2</p>
</td>
<td align="left" valign="top">
<font face="Courier New, Courier">FirstHost</font>
</td>
<td align="left" valign="top">
<p>Defines the physical database topology.</p>
</td>
</tr>
</table>
</ul>
<!-- ********** Header 4 ******************** -->
<p><b> <a name="Default">The Default Label</a> </b></p>
<ul>
<font face="Courier New, Courier">
<pre><font size="2">Default(Single, EverythingElseHost)
</font></pre>
</font>
</ul>
<p>The settings defined in <b>default</b> establish the default logical database
mapping. The purposes of the individual settings and are the same as those for
<a href="#AccountsHost"><b>AccountsHost</b></a>. The <b>Default</b> label sets
the access type and then uses login values specified in the <a href="#EverythingElseHost"><b>EverythingElseHost</b></a>
label (defined previously in the <a href="#Physical"><b>physical</b></a> section).</p>
<!-- ********** Header 2 ******************** -->
<p></p><hr><font class="subhead2">
<a NAME="checkfile">Verifying the Values in configHosts.txt</a>
</font>
<p>To verify that the settings in configHosts.txt are valid, use SQL*Plus to
execute two commands using the settings. If the settings are correct, the
commands result in a successful connection to the database.</p>
<p>The first command tests the values defined in <a href="#FirstHost">
<b>FirstHost</b></a> (of the <a href="#Physical"><b>physical</b></a> section).
Following the example used in this article, the <b>FirstHost</b> line from
configHosts.txt is:</p>
<ul><font face="Courier New, Courier"><pre>FirstHost(e119_staging_acc, e119_staging_acc, acc_test, retryCount=1, delay=0, reanimate=0)
</pre></font></ul>
<p>The second command tests the values defined in the
<a href="#EverythingElseHost"><b>EverythingElseHost</b></a> line:</p>
<ul><font face="Courier New, Courier"><pre>EverythingElseHost(e119_staging_main, e119_staging_main, bigfoot, retryCount=1, delay=2, reanimate=3)
</pre></font></ul>
<p>To execute the test commands, take the text between the parentheses of each
line and construct SQL*Plus statements as follows:</p>
<ul>
<font face="Courier New, Courier">
<pre><font size="2">sqlplus FirstField/SecondField@ThirdField
</font></pre>
</font>
</ul>
<p>This translates to:</p>
<ul>
<font face="Courier New, Courier">
<pre><font size="2">sqlplus username/passwd@connect
</font></pre>
</font>
</ul>
<p>So, given the example above, the SQL*Plus command should look like this:</p>
<ul>
<font face="Courier New, Courier">
<pre><font size="2">sqlplus e119_staging_acc/e119_staging_acc@acc_test
</font></pre>
</font>
</ul>
<p>Execute the command twice, once using the first three fields from <b>FirstHost</b>
and once with the same fields from <b>EverythingElseHost</b>. </p>
<p>If the command fails to connect to the database, you have one of two
problems:</p>
<ol>
<li>Either or both username/password are incorrect.
<li>Or ebay.world is not set to point to the proper instance on the machine
you are testing on. This information is set in the tnsnames.ora file on the
machine.
</ol>
<p>If the SQL*Plus connect commands work but your configHosts.txt still does
not work, there are other problems with the configHosts.txt file.</p>
<!-- ********** Header 2 ******************** -->
<p></p><hr><font class="subhead2">
<a name="TechnicalContact">Technical Contact</a>
</font>
<p>The technical information for the update to this article was provided by
<a href="ConfigHostsDef.htm">***Name Omitted***</a>.</p>
<p>Product Development's
<a href="ConfigHostsDef.htm">Technical Publications team</a> is
responsible for maintaining this page. This HTML document was updated by
<a href="mailto:ffwhite@live.com">Forest White</a>.</p>
</body>
</html>