[AIX Solaris HP-UX Linux Windows][IBM i]

Configuring the service log

The settings for service logs are typically shared for all servers, but you can configure a separate service log for each server process by overriding the configuration values at the server level.

About this task

The configuration values for the service log are inherited by each server process from the node configuration, but under certain circumstances you might wish to configure the service logs differently for individual servers. You can use the administrative console to change the service log settings from the server level configuration panels.
Note: Cette rubrique fait référence à un ou plusieurs des fichiers journaux de serveur d'applications. Il est recommandé de configurer le serveur de telle sorte qu'il utilise l'infrastructure de journalisation et de trace HPEL (High Performance Extensible Logging) à la place des fichiers SystemOut.log, SystemErr.log, trace.log et activity.log sur les systèmes distribués et IBM® i. Vous pouvez également utiliser HPEL conjointement avec vos fonctions de journalisation z/OS® natives. Si vous utilisez l'infrastructure HPEL, vous pouvez accéder à toutes les informations de journalisation et de trace en utilisant l'outil de ligne de commande LogViewer à partir de votre répertoire bin de profil de serveur. Pour plus d'informations sur l'utilisation de HPEL, voir les informations sur l'utilisation de HPEL en vue du traitement des incidents liés aux applications.

In WebSphere Application Server Version 7 and earlier, the service log is enabled by default. In WebSphere Application Server Version 8x, however, the service log is disabled by default. Configure your servers to use HPEL log and trace mode and use the HPEL API if you need to be able to merge log file content from multiple servers. Use the HPEL log, trace mode and the HPEL LogViewer command if you need to be able to render log content in Common Base Event XML format.

Procedure

  1. Start the administrative console.
  2. Click Troubleshooting > Logs and Trace > server_name > IBM Service Logs.
  3. Select the Enable box to enable the service log, or clear the check box to disable the log.
  4. Set the name for the service log.

    [AIX Solaris HP-UX Linux Windows]The default name is profile_root/logs/activity.log. If the name is changed, the run time requires write access to the new file, and the file must use the .log extension.

    [IBM i]The default name is profile_root/logs/activity.log. If the name is changed, the run time requires write access to the new file, and the file must use the .log extension.

  5. Set the maximum file size.

    Specifies the number of megabytes to which the file can grow. When the file reaches this size, it wraps, replacing the oldest data with the newest data.

  6. Save the configuration.
  7. Restart the server to apply the configuration changes.

Icône indiquant le type de rubrique Rubrique de tâche



Icône d'horodatage Dernière mise à jour: July 9, 2016 2:34
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=ttrb_cfgsvclog
Nom du fichier : ttrb_cfgsvclog.html