sunhux

<div>
<div class="content wysiwyg-content">
We're configuring our Solaris Weblogic to send via syslog 
to Qradar log collector &amp;&nbsp;vendor gave us the steps below: 
however, I don't see anywhere in the steps below indicating 
IP of the log collector (ie syslog server) &amp;&nbsp;I think some steps 
are missing. &nbsp;Can anyone enhance it &amp;&nbsp;add on any missing 
steps/inaccuracies? 
 
1.1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;WebLogic 12.1.3.0 
=================== 
Enable configuration auditing by one of these methods: 
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use the Administration Console. Select the Configuration &gt;&nbsp;General page for your domain and set the Configuration Audit Type. See &quot;Enable configuration auditing&quot; in the Oracle WebLogic Server Administration Console Help. 
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;When you start the Administration Server, include one of the following Java options in the weblogic.Server command: 
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-Dweblogic.domain.ConfigurationAuditType=&quot;audit&quot; 
Causes the domain to emit Audit Events only. 
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-Dweblogic.domain.ConfigurationAuditType=&quot;log&quot; 
Causes the domain to write configuration auditing messages to the Administration Server log file only. 
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-Dweblogic.domain.ConfigurationAuditType=&quot;logaudit&quot; 
Causes the domain to emit Audit Events and write configuration auditing messages to the Administration Server log file.
</div>
</div>

We're configuring our Solaris Weblogic to send via syslog
to Qradar log collector & vendor gave us the steps below:
however, I don't see anywhere in the steps below indicating
IP of the log collector (ie syslog server) & I think some steps
are missing.  Can anyone enhance it & add on any missing
steps/inaccuracies?

1.1	WebLogic 12.1.3.0
===================
Enable configuration auditing by one of these methods:
•	Use the Administration Console. Select the Configuration > General page for your domain and set the Configuration Audit Type. See "Enable configuration auditing" in the Oracle WebLogic Server Administration Console Help.
•	When you start the Administration Server, include one of the following Java options in the weblogic.Server command:
•	-Dweblogic.domain.ConfigurationAuditType="audit"
Causes the domain to emit Audit Events only.
•	-Dweblogic.domain.ConfigurationAuditType="log"
Causes the domain to write configuration auditing messages to the Administration Server log file only.
•	-Dweblogic.domain.ConfigurationAuditType="logaudit"
Causes the domain to emit Audit Events and write configuration auditing messages to the Administration Server log file.

configuring WL to send syslog

We&amp;#39;re configuring our Solaris Weblogic to send via syslog
to Qradar log collector &amp;amp; vendor gave us the steps below:
however, I don&amp;#39;t see anywhere in the steps below indicating
IP of the log collector (ie syslog server) &amp;amp; I think some steps
are missing.  Can anyone enhance it &amp;amp; add on any missing
steps/inaccuracies?

1.1	WebLogic 12.1.3.0
===================
Enable configuration auditing by one of these methods:
•	Use the Administration Console. Select the Configuration &amp;gt; General page for your domain and set the Configuration Audit Type. See &amp;quot;Enable configuration auditing&amp;quot; in the Oracle WebLogic Server Administration Console Help.
•	When you start the Administration Server, include one of the following Java options in the weblogic.Server command:
•	-Dweblogic.domain.ConfigurationAuditType=&amp;quot;audit&amp;quot;
Causes the domain to emit Audit Events only.
•	-Dweblogic.domain.ConfigurationAuditType=&amp;quot;log&amp;quot;
Causes the domain to write configuration auditing messages to the Administration Server log file only.
•	-Dweblogic.domain.ConfigurationAuditType=&amp;quot;logaudit&amp;quot;
Causes the domain to emit Audit Events and write configuration auditing messages to the Administration Server log file.

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.

Java

An application server is a software framework that provides both facilities to create applications and a server environment to run them. Most application server frameworks contain a comprehensive service layer model, acting as a set of components accessible to the software developer through an API defined by the platform itself. For Web applications, these components are usually performed in the same running environment as their web server(s), and their main job is to support the construction of dynamic pages. However, many application servers target much more than just Web page generation: they implement services like clustering, fail-over, and load-balancing.

Application Servers

Unix is a multitasking, multi-user computer operating system originally developed in 1969 at Bell Labs. Today, it is a modern OS with many commercial flavors and licensees, including FreeBSD, Hewlett-Packard’s UX, IBM AIX and Apple Mac OS-X. Apart from its command-line interface, most UNIX variations support the standardized X Window System for GUIs, with the exception of the Mac OS, which uses a proprietary system.