Project

General

Profile

Administration » History » Version 4

chin-yeh, 04/20/2011 03:56 PM

1 2 chin-yeh
{{toc}}
2
3 1 chin-yeh
h1. Administration
4 2 chin-yeh
5
Describes how to administrate the common tasks, for instance, update properties files, change logging level and etc.
6
7
h2. Monitor Log Files
8
9 4 chin-yeh
All of the log files can be found in:
10 2 chin-yeh
<pre>
11
{jboss folder}/server/{profile name}/log/qconnector/info.log
12
{jboss folder}/server/{profile name}/log/qconnector/error.log
13 1 chin-yeh
{jboss folder}/server/{profile name}/log/qconnector/debug.log
14 4 chin-yeh
</pre>
15
16
All of the log files for daemon/batches can be found in:
17
<pre>
18
/var/ecwyconnector/qconnector-batch-info.log
19
/var/ecwyconnector/qconnector-batch-error.log
20
/var/ecwyconnector/qconnector-batch-debug.log
21 2 chin-yeh
</pre>
22
23
The log file rotates *daily* or every *10MB* for maximum *100 files*.
24
25
h2. Change Logging Level
26
27
The available logging level:
28
* *INFO* - default level
29
* *DEBUG* - should not set to this level unless necessary
30
* *ERROR*
31
* *WARN*
32
33 3 chin-yeh
_JBoss 4.0.x_
34
> {jboss folder}/server/{profile name}/conf/log4j.xml
35
36
_Jboss 4.2.x / Jboss 5.1.x_
37
> {jboss folder}/server/{profile name}/conf/jboss-log4j.xml
38
39 2 chin-yeh
h2. Update Properties Files
40
41
All of the properties files can be found in:
42
<pre>
43
/data/qconnector
44
</pre>
45
46
h3. ws-mimic
47
48
List of the properties files:
49
* /data/qconnector/application.properties
50
* /data/qconnector/jndi-factory.properties
51
52
* *application.properties*
53
|_.Property name|_.Description|
54
|ws.url|The URL of the web service which process the request|
55
|status.callback.url|the callback URL of the caller to update the status, e.g. Dot Com mall |
56
57
* *jndi-factory.properties*
58
|_.Property name|_.Description|
59
|jndi.initial|the initial context of the JNDI|
60
|jndi.url|the URL of the JNDI provider (JMS)|
61
|jndi.url.pkgs|the naming packages of the JNDI|
62
|jndi.connection.factory|the JNDI name of the JMS connection factory|
63
|session.cache.size|the number of JMS session to be cached|
64
|request.queue.name|the name of the JMS queue which keeps the web service request|
65
|response.queue.name|the name of the JMS queue which keeps the web service response|
66
67
h3. ws-status
68
69
List of the properties files:
70
* /data/qconnector/ws-status/database.properties
71
72
* database.properties
73
|_.Property name|_.Description|
74
|jndi.datasource|the JNDI name of the data source|
75
|db.dialect|the database dialect, e.g. DB2|
76
|db.show.sql|indicates whether to show the SQL used|
77
|db.sql.comment|indicates whether to show the comment of the SQL used|
78
79
h3. ecosway-adaptor
80
81
List of the properties file:
82
* /data/qconnector/ecosway-adaptor/application.properties
83
* /data/qconnector/ecosway-adaptor/database.properties
84
* /data/qconnector/ecosway-adaptor/registration/template.properties
85
86
* *application.properties*
87
|_.Property name|_.Description|
88
|ws.url|the URL of the web service. Currently this is the URL of the mimic of the actual web service|
89
90
* *database.properties*
91
|_.Property name|_.Description|
92
|jndi.datasource|the JNDI name of the data source|
93
|db.dialect|the database dialect, e.g. DB2|
94
|db.show.sql|indicates whether to show the SQL used|
95
|db.sql.comment|indicates whether to show the comment of the SQL used|
96
97
98
* *registration/template.properties*
99
|_.Property name|_.Description|
100
|registration.template|the template of the web service request|