|
1 | 1 | # WebLogic Logging Exporter |
2 | 2 |
|
3 | | -The WebLogic Logging Exporter (the "logging exporter") adds a log event handler to WebLogic Server, such that WLS server logs can be integrated into [Elastic Stack](https://www.elastic.co/products) in Kubernetes directly, by using the [Elasticsearch](https://www.elastic.co/products/elasticsearch) REST API. |
| 3 | +The WebLogic Logging Exporter (the "logging exporter") adds a log event handler to WebLogic Server, |
| 4 | +such that WLS server logs can be integrated into [Elastic Stack](https://www.elastic.co/products) |
| 5 | +in Kubernetes directly, by using the [Elasticsearch](https://www.elastic.co/products/elasticsearch) REST API. |
4 | 6 |
|
5 | | -The blog, [Let WebLogic work with Elastic Stack in Kubernetes](https://blogs.oracle.com/weblogicserver/let-weblogic-work-with-elk-in-kubernetes), outlines the steps to harvest WLS server logs using Logstash so that they can be filtered, manipulated, and viewed using Elasticsearch and Kibana. |
6 | | -However, that approach requires the setup of a shared volume which is outside of the pod, and the logs needs to be written to an intermediate log file for harvesting and parsing. |
7 | | - |
8 | | -The goal of this project is to provide an easy to configure, robust, and production-ready solution to access WLS log information through Elasticsearch and Kibana. |
| 7 | +The goal of this project is to provide an easy to configure, robust, and production-ready solution to access |
| 8 | +WLS log information through Elasticsearch and Kibana. |
9 | 9 |
|
10 | 10 | ## Getting Started |
11 | 11 |
|
12 | 12 | These instructions outline the steps to build the `weblogic-logging-exporter.jar` file, which can then be integrated into the [WebLogic Kubernetes Operator](https://github.com/oracle/weblogic-kubernetes-operator/) for handling the server logs generated by the WebLogic Server domain. |
13 | 13 |
|
14 | | -## Prerequisites |
| 14 | +## Download the release |
| 15 | + |
| 16 | +You can download the WebLogic Logging Exporter already compiled for you from the [releases page](). |
| 17 | + |
| 18 | +## Building from source |
| 19 | + |
| 20 | +If you prefer, you can build the WebLogic Logging Exporter from the source code. To do this, you will |
| 21 | +need access to some WebLogic Server libraries. There are two ways to get these libraries: |
| 22 | + |
| 23 | +* Populate you local Maven repository with the required files from a local WebLogic Server installation |
| 24 | + using the Oracle Maven Synchronization plugin, or |
| 25 | +* Use the Oracle Maven repository to download them as part of your build, this requires registration and |
| 26 | + configuring your local Maven installation with the appropriate authentication details. |
| 27 | + |
| 28 | +### Populating your local Maven repository from a local WebLogic Server installation |
| 29 | + |
| 30 | +You can use the Oracle Maven Synchronization plugin, which is included in your WebLogic Server installation, |
| 31 | +to install the necessary dependencies into your local Maven repository. |
| 32 | + |
| 33 | +There are two steps: |
| 34 | + |
| 35 | +* Install the Oracle Maven Synchronization plugin, |
| 36 | +* Run the "push" goal to populate your local Maven repository from your WebLogic Server installation. |
| 37 | + |
| 38 | +#### Installing the Oracle Maven Synchronization plugin |
| 39 | + |
| 40 | +To install the plugin, navigate to your WebLogic Server installation then enter the commands (this example |
| 41 | +assumes you installed WebLogic Server in /u01/wlshome): |
| 42 | + |
| 43 | +``` |
| 44 | +cd /u01/wlshome/oracle_common/plugins/maven/com/oracle/12.2.1/oracle-maven-sync |
| 45 | +mvn install:install-file -DpomFile=oracle-maven-sync-12.2.1.pom -Dfile=oracle-maven-sync-12.2.1.jar |
| 46 | +``` |
| 47 | + |
| 48 | +#### Popoulating your local Maven repository |
| 49 | + |
| 50 | +To populate your local Maven repository from your WebLogic Server installation, enter this command: |
| 51 | + |
| 52 | +``` |
| 53 | +mvn com.oracle.maven:oracle-maven-sync:push -DoracleHome=/u01/wlshome |
| 54 | +``` |
| 55 | + |
| 56 | +You can verify the dependencies were installed by looking in your local Maven repository which is |
| 57 | +normally located at `~/.m2/repository/com/oracle/weblogic`. |
| 58 | + |
15 | 59 |
|
16 | | -The logging exporter depends on the WebLogic logging JAR which is available from the [ Oracle Maven Repository](http://maven.oracle.com/). |
| 60 | +### Using the Oracle Maven repository |
17 | 61 |
|
18 | | -To access the Oracle Maven Repository, there are two fundamental requirements to be aware of: |
| 62 | +Note: If you populated your local repository using the Oracle Maven Synchronization plugin, then this |
| 63 | +step is *not* required. |
19 | 64 |
|
20 | | -1. You must be using [Maven 3.2.5](http://maven.apache.org/docs/3.2.5/release-notes.html) or later. This contains the version of the [Wagon 2.8](http://maven.apache.org/wagon/) component that has been enhanced to support access to artifacts that are protected by [HTTP authentication schemes](https://issues.apache.org/jira/projects/WAGON/issues/WAGON-422). |
| 65 | +To access the Oracle Maven repository, there are two requirements to be aware of: |
21 | 66 |
|
22 | | -2. You must be registered with OTN and have accepted the license agreement to access and use the Oracle Maven Repository. This can be done with either a new or an existing OTN user account by accessing the http://maven.oracle.com site and selecting the registration link. |
23 | | -After registering, then you just need to configure your local Maven environment with the details of the Oracle Maven Repository, including the information that relates to the authentication model specifying your OTN user name and password. |
| 67 | +1. You must be using [Maven 3.2.5](http://maven.apache.org/docs/3.2.5/release-notes.html) or later. |
| 68 | +This contains the version of the [Wagon 2.8](http://maven.apache.org/wagon/) component that has |
| 69 | +been enhanced to support access to artifacts that are protected by |
| 70 | +[HTTP authentication schemes](https://issues.apache.org/jira/projects/WAGON/issues/WAGON-422). |
24 | 71 |
|
25 | | -## Building |
26 | | -### Configure Maven |
| 72 | +2. You must be registered with OTN and have accepted the license agreement to access and use the |
| 73 | +Oracle Maven Repository. This can be done with either a new or an existing OTN user account by |
| 74 | +accessing the http://maven.oracle.com site and selecting the registration link. |
| 75 | +After registering, then you just need to configure your local Maven environment with the details |
| 76 | +of the Oracle Maven Repository, including the information that relates to the authentication model |
| 77 | +specifying your OTN user name and password. |
| 78 | + |
| 79 | +#### Configure Maven |
27 | 80 |
|
28 | 81 | #### 1. Encrypt your OTN Password. |
29 | 82 |
|
@@ -123,13 +176,17 @@ To configure the HTTP Wagon, add the following `<server>` element to the `<serve |
123 | 176 |
|
124 | 177 | If needed, specify the `proxies` that are required. |
125 | 178 |
|
126 | | -#### 3. Clone the project and build it. |
| 179 | +### Building the WebLogic Logging Exporter |
| 180 | + |
| 181 | +To build the WebLogic Logging Exporter, simply clone the project from GitHub and then build it |
| 182 | +with Maven: |
| 183 | + |
127 | 184 | ``` |
128 | 185 | git clone git@orahub.oraclecorp.com:oracle/wls-logging-exporter.git |
129 | 186 | mvn install |
130 | 187 | ``` |
131 | 188 |
|
132 | | -The `weblogic-logging-exporter-1.0-SNAPSHOT.jar` will be available under the `target` directory. |
| 189 | +The `weblogic-logging-exporter-0.1-SNAPSHOT.jar` will be available under the `target` directory. |
133 | 190 |
|
134 | 191 | ## Deployment |
135 | 192 |
|
|
0 commit comments