Oracle BEA WebLogic

The Oracle BEA WebLogic DSM allows JSA to retrieve archived server logs and audit logs from any remote host, such as your Oracle BEA WebLogic server.

Enabling Event Logs

By default, Oracle BEA WebLogic does not enable event logging.

To enable event logging on your Oracle WebLogic console:

1. Log in to your Oracle WebLogic console user interface.
2. Select Domain >Configuration >General.
3. Click Advanced.
4. From the Configuration Audit Type list, select Change Log and Audit.
5. Click Save.

You can now configure the collection of domain logs for Oracle BEA WebLogic.

Configuring Domain Logging

Oracle BEA WebLogic supports multiple instances. Event messages from instances are collected in a single domain-wide log for the Oracle BEA WebLogic server.

To configure the log file for the domain:

1. From your Oracle WebLogic console, select Domain >Configuration >Logging.
2. From the Log file name parameter, type the directory path and file name for the domain log.

   For example, OracleDomain.log.

3. Configure any additional domain log file rotation parameters.
4. Click Save.

You can now configure application logging for the server.

Configuring Application Logging

You can configure application logging for Oracle BEA WebLogic:

1. From your Oracle WebLogic console, select Server >Logging >General.
2. From the Log file name parameter, type the directory path and file name for the application log.

   For example, OracleDomain.log.

3. Configure any additional application log file rotation parameters.
4. Click Save.

You can now configure an audit provider for Oracle BEA WebLogic.

Configuring an Audit Provider

You can configure an audit provider:

1. Select Security Realms >Realm Name >Providers >Auditing.
2. Click New.
3. Configure an audit provider by typing a name for the audit provider that you are creating.
4. From the Type list, select DefaultAuditor.
5. Click OK.

   The Settings window is displayed.

6. Click the auditing provider that you created in Configuring an Audit Provider.
7. Click the Provider Specific tab.
8. Add any Active Context Handler Enteries that are needed.
9. From the Severity list, select Information.
10. Click Save.

You can now configure JSA to pull log files from Oracle BEA WebLogic.

Configuring a Log Source

You can configure JSA to retrieve log files from Oracle BEA WebLogic.

1. Log in to JSA.
2. Click the Admin tab.
3. On the navigation menu, click Data Sources.

   The Data Sources pane is displayed.

4. Click the Log Sources icon.

   The Log Sources window is displayed.

5. From the Log Source Type list, select Oracle BEA WebLogic.
6. Using the Protocol Configuration list, select Log File.
7. Configure the following parameters:

   Table 1: Log File Parameters

   Parameter	Description
   Log Source Identifier	Type the IP address or host name for the log source. This value must match the value that is configured in the Remote Host IP or Hostname parameter. The log source identifier must be unique for the log source type.
   Service Type	From the list, select the File Transfer Protocol (FTP) you want to use for retrieving files. You can choose: SSH File Transfer Protocol (SFTP), File Transfer Protocol (FTP), or Secure Copy (SCP). The default is SFTP.
   Remote IP or Hostname	Type the IP address or host name of the host from which you want to receive files.
   Remote Port	Type the TCP port on the remote host that is running the selected Service Type. If you configure the Service Type as FTP, the default is 21. If you configure the Service Type as SFTP or SCP, the default is 22. The valid range is 1 - 65535.
   Remote User	Type the user name necessary to log in to the host that runs the selected Service Type. The user name can be up to 255 characters in length.
   Remote Password	Type the password necessary to log in to the host that runs the selected Service Type.
   Confirm Password	Confirm the Remote Password to log in to the host that runs the selected Service Type.
   SSH Key File	If you select SCP or SFTP as the Service Type, this parameter gives the option to define an SSH private key file. Also, when you provide an SSH Key File, the Remote Password option is ignored.
   Remote Directory	Type the directory location on the remote host from which the files are retrieved.
   Recursive	Select this check box if you want the file pattern to also search sub folders. The Recursive parameter is not used if you configure SCP as the Service Type. By default, the check box is clear.
   FTP File Pattern	If you select SFTP or FTP as the Service Type, this gives the option to configure the regular expression (regex) that is needed to filter the list of files that are specified in the Remote Directory. All matching files are included in the processing. For example, if you want to list all files that start with the word server, followed by one or more digits and ending with .log, use the following entry: server[0-9]+\.log. Use of this parameter requires knowledge of regular expressions (regex). For more information, see the following website: http://docs.oracle.com/javase/tutorial/essential/regex/
   FTP Transfer Mode	This option appears only if you select FTP as the Service Type. The FTP Transfer Mode parameter gives the option to define the file transfer mode when log files are retrieved over FTP. From the list, select the transfer mode that you want to apply to this log source: Binary - Select a binary FTP transfer mode for log sources that require binary data files or compressed .zip, .gzip, .tar, or .tar+gz archive files. ASCII Select ASCII for log sources that require an ASCII FTP file transfer. You must select None for the Processor parameter and LineByLine the Event Generator parameter when you use ASCII as the FTP Transfer Mode.
   SCP Remote File	If you select SCP as the Service Type you must type the file name of the remote file.
   Start Time	Type the time of day you want the processing to begin. This parameter functions with the Recurrence value to establish when and how often the Remote Directory is scanned for files. Type the start time, based on a 24-hour clock, in the following format: HH:MM.
   Recurrence	Type the frequency, beginning at the Start Time, that you want the remote directory to be scanned. Type this value in hours (H), minutes (M), or days (D). For example, type 2H if you want the directory to be scanned every 2 hours. The default is 1H.
   Run On Save	Select this check box if you want the log file protocol to run immediately after you click Save. After the Run On Save completes, the log file protocol follows your configured start time and recurrence schedule. Selecting Run On Save clears the list of previously processed files for the Ignore Previously Processed File(s) parameter.
   EPS Throttle	Type the number of Events Per Second (EPS) that you do not want this protocol to exceed. The valid range is 100 - 5000.
   Processor	If the files on the remote host are stored in a .zip, .gzip, .tar, or .tar.gz archive format, select the processor that allows the archives to be expanded and contents that are processed.
   Ignore Previously Processed File(s)	Select this check box to track files that are already processed and you do not want these files to be processed a second time. This applies only to FTP and SFTP Service Types.
   Change Local Directory?	Select this check box to define the local directory on your JSA system that you want to use for storing downloaded files during processing. It is suggested that you leave the check box clear. When the check box is selected, the Local Directory field is displayed, and this gives you the option to configure the local directory for storing files.
   Event Generator	From the Event Generator list, select Oracle BEA WebLogic.

8. Click Save.
9. On the Admin tab, click Deploy Changes.

   The configuration is complete.