Configuration » History » Version 6
chin-yeh, 10/28/2010 11:03 AM
| 1 | 3 | chin-yeh | {{toc}} |
|---|---|---|---|
| 2 | |||
| 3 | 1 | chin-yeh | h1. Configuration |
| 4 | 2 | chin-yeh | |
| 5 | 4 | chin-yeh | *Prerequisite:* |
| 6 | 2 | chin-yeh | * Completed the [[Installation]] section. |
| 7 | 1 | chin-yeh | |
| 8 | 4 | chin-yeh | This section describes how to configure the logging and settings on the application server. All of the configuration files can be found from SCM repository: |
| 9 | > Production environment: |
||
| 10 | >> http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/production |
||
| 11 | 5 | chin-yeh | > Development environment: |
| 12 | 4 | chin-yeh | >> http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/development |
| 13 | 3 | chin-yeh | |
| 14 | 1 | chin-yeh | h2. log4j (Jboss AS 5 + HornetQ) |
| 15 | |||
| 16 | Describes how to configure the *log4j* logging in Jboss AS 5. |
||
| 17 | 4 | chin-yeh | |
| 18 | *Assumes* that Jboss AS 5 is installed in: |
||
| 19 | > /opt/jboss-5.1.0.GA |
||
| 20 | |||
| 21 | 5 | chin-yeh | *List of the configuration files needed:* |
| 22 | * *note*: replace {environment} with either *production* (for production environment) or *development* (for development environment) |
||
| 23 | 4 | chin-yeh | * http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ws-mimic/logging/log4j-appender.xml |
| 24 | 1 | chin-yeh | * http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/ws-mimic/logging/log4j-category.xml |
| 25 | |||
| 26 | *Steps:* |
||
| 27 | 5 | chin-yeh | # login as jboss user |
| 28 | # <code>cd</code> to <code>/opt/jboss-5.1.0.GA/server/default-with-hornetq/conf</code> |
||
| 29 | <pre> |
||
| 30 | $ cd /opt/jboss-5.1.0.GA/server/default-with-hornetq/conf |
||
| 31 | </pre> |
||
| 32 | # open the *jboss-log4j.xml* |
||
| 33 | <pre> |
||
| 34 | $ vi jboss-log4j.xml |
||
| 35 | </pre> |
||
| 36 | # append the content of *log4j-appender.xml* (see above) into the *jboss-log4j.xml* |
||
| 37 | # append the content of *log4j-category.xml* (see above) into the *jboss-log4j.xml* |
||
| 38 | # save the file, *jboss-log4j.xml* |
||
| 39 | # restart the jboss |
||
| 40 | # done |
||
| 41 | |||
| 42 | 3 | chin-yeh | |
| 43 | h2. init script for Jboss AS 5 |
||
| 44 | |||
| 45 | 6 | chin-yeh | Describes how to configure the <code>init</code> script for Jboss AS in RHEL. Once configured, the server will start the <code>Jboss AS</code> process upon bootup. However, you may skip this section if you plan to start the Jboss AS manually. |
| 46 | |||
| 47 | *Assumes* that Jboss AS 5 is installed in: |
||
| 48 | > /opt/jboss-5.1.0.GA |
||
| 49 | |||
| 50 | *List of the configuration files needed:* |
||
| 51 | * *note*: replace {environment} with either *production* (for production environment) or *development* (for development environment) |
||
| 52 | * *note*: replace {servername} with the targeted hostname, e.g. cwyrnd3-server |
||
| 53 | * http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/{servername}/jboss-init/jboss5hq |
||
| 54 | * http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/{environment}/{servername}/jboss-init/jboss5hq |
||
| 55 | |||
| 56 | *Steps:* |
||
| 57 | # login as root |
||
| 58 | # upload the file, *jboss5hq* to */etc/init.d* via ftp or sftp |
||
| 59 | # execute the following command to put the <code>init</code> into appropriate run level directory: |
||
| 60 | <pre> |
||
| 61 | # chkconfig --add jboss5hq |
||
| 62 | </pre> |