![]() Once you have added the wished log folders with the applied configuration for the SAP Web AS Java, a search via the indexed files might look like the following example: All versions of the SAP Web AS Java up to Composition Environment 7.1 support the log-file version 1.5. Available are the versions "sap_webas_java_log1.5" and "sap_webas_java_log2.0". To define the version of the log files of your SAP Web AS java installation one only needs to open one of the log-/trace-files and check, if the log events are starting with the prefix "#1.5" or "#2.0".Īccording to the given version one needs to apply the correct log format as it is illustrated in the screen shot above (Data Inputs -> Files and Directories -> Add Input). There are 2 log formats available, one format for the log file version 1.5 and one for the version 2.0. When adding the shared folders to the Data Inputs of Splunk it is also necessary to select the appropriate log-file format fitting to the log-files of the shared folder. The files to be indexed are accessed via their global shares (\\\sapmnt\\\j2ee\cluster\server\log*), where the feature of Splunk is used to add shared directories as "Data Inputs".Īt this step you might configure the host from where the folder is added. The first instance is located on host ldai2q1m and the second one is installed on host ldai1q1m. The second system with the System-ID Q1M consists out of 2 instances each 2 server process. Both instances are installed on host wdfd00184513a and host wdfd00145834a. The first system with the System-ID OLE consists out of 2 instances each 1 server process. The picture illustrates that Splunk adds the log directories of 2 different SAP Web AS Java installations ( OLE and Q1M). ![]() The picture is taken from the Splunk web frontend and shows the added file shares of the several installations of an SAP Web AS Java. It is recommended to install and setup Splunk on a separate host so that the performance of the SAP Web AS Java is not influenced.Īs a precondition to index log files of the SAP Web AS Java, the configuration should already be applied (see the last paragraph regarding the configuration).Ī recommended setup might look like the following screen shot (Data Inputs -> Files and Directories). One Splunk installation can also be used to operate via a clustered SAP Web AS Java or via many SAP Web AS Java systems. Recommended setup of Splunk in combination with SAP's Web AS Java This configuration has been tested sucessfully with Splunk 3.2 and Splunk 3.3.1. Now you need just to add your folders you want to observe. After restarting Splunk the configuration for log-/trace-files of the SAP Web AS Java is installed. This can be achieved with extracting the provided configuration-file, unzip it and store the folder "local" into the installation directory of Splunk's installation below ".//etc/bundles/". To enable Splunk to detect and parse SAP Web AS Java log-/trace-files a specific configuration has to be applied to the Splunk configuration. How to enable Splunk to detect log files of the SAP Web AS Java? It's easy to download and use and it's very powerful. ![]() If a machine can generate it - Splunk can eat it. Logs, configurations, messages, traps and alerts, scripts, code, metrics and more. Search and navigates IT data from applications, servers and network devices in real-time. What is Splunk?įirst it should be explained what exactly Splunk is, so that also non experienced users get an idea of the possibilities of Splunk.Īn comprehensive definition of this is given on Splunk's website with the following explanation: And you'll get the advanced feature set of Splunk which will transform your log-file analysis into a walk-over. Then you might just add the log folders of the SAP Web AS Java as "Data Inputs" into Splunk. ![]() Are you using the SAP Web AS Java and are you interested in Splunk to search in its produced output files (log- and trace-files)? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |