Skip Headers

Agile Product Lifecycle Management Recipe Management for Pharmaceuticals Administrator Guide Release 9.3.3 E39287-01 |
| Contents

Previous | Next |

# 12 General Administration

This chapter provides information about managing log files and other general administration tasks.

## 12.1 Manage Log Files

As part of general administration and maintenance of R&M Workspace, ensure that backup for the following log files are done periodically:

- The <servername>.log file is located in <AGILE_HOME>\domain\servers\<servername>\logs.

- The nohup.out file in the <CFM_HOME> directory.

- All log files in the <CFM_HOME>/logs directory.

- All log files in the <CFM_HOME>/bin directory.

These files are useful in reporting issues to Oracle support for troubleshooting.

### 12.1.1 Default Log Files

In the production environment, when a log file reaches a specified size, the system automatically closes it and creates a new one. Only the latest seven are retained by the system. Files earlier than the latest seven are regularly deleted by the system. It is therefore advised that you maintain a backup of twenty log files.

### 12.1.2 Rotate Log Files

Log file rotation ensures that log files do not grow indefinitely. It allows you to keep an efficient and useful amount of data, without using up too much disk space. You can choose to rotate log files at specific time intervals or when the current log file reaches a specific size.

To set up log file rotation:

1. Log on to the WebLogic server console.

2. Click the Lock & Edit button in the Tools & Settings tree/options.

3. In the left pane, expand Environment and select Servers.

4. In the Servers table, click the name of the server instance whose log files you want to configure for rotation.

5. Select Logging > General.

6. To move old messages to another file when the current log file reaches a specific size:

   a. In the Rotation Type list box, choose By Size.

   b. In the Rotation File Size field, enter the file size that triggers the server to move log messages to a separate file. After the log file reaches the specified size, the next time the server checks the file size, it will rename the current log file. After the server renames the file, subsequent messages accumulate in a new file named filename.log.

   c. If you want to limit the number of log files that the server creates to store old log messages, select the Limit Number of Retained Files check box. Then in the Files to Retain field, enter the maximum number of files. If the server receives additional log messages after reaching the capacity of the last log file, it overwrites the oldest log file.

7. If you want to move old messages to another file at specific time intervals:

   a. In the Rotation Type list box, choose By Time.

   b. In the Begin Rotation Time field, enter the start time.

   c. Use the following format: hh:mm, where hh is the hour in a 24-hour format and mm is the minute. At the time that you specify, the server rotates the current log file. If the time that you specify is already past, the server starts its file rotation immediately. Thereafter, the server rotates the log file at an interval that you specify in Rotation Interval.

   d. In the Rotation Interval field, enter the interval at which the server saves old messages to another file.

   e. If you want to limit the number of log files that the server creates to store old log messages, select the Limit Number of Retained Log Files check box. Then in the Files to Retain field, enter the maximum number of files. If the server receives additional log messages after reaching the capacity of the last log file, it overwrites the oldest log file.

8. In the Log File Rotation Directory field, enter the directory location where the rotated log files will be stored. Enter an absolute pathname or a pathname that is relative to the server's root directory. By default, the rotated files are stored in the same directory where the log file is stored.

9. To include a time and date stamp in the file name when the log file is rotated, in the File Name field, add java.text.SimpleDateFormat variables to the file name and surround each variable with percentage (%) characters.

   For example, if you enter the following value in the File Name field:

   myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the server's log file will be named:

   myserver_yyyy_MM_dd_hh_mm.log.

   When the server instance rotates the log file, the rotated file name contains the date stamp. For example, if the server instance rotates its local log file on 4 March, 2008 at 10:15 AM, the log file that contains the old log messages will be named: myserver_2005_03_08_10_15.log.

   If you do not include a time and date stamp, the rotated log files are numbered in order of creation filename, where filename is the name configured for the log file. For example: myserver.log00007.

10. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

    Not all changes take effect immediately-some require a restart.

## 12.2 Manage Batch Size for Results Screens

The number of rows that appear in the results screens in the application can be configured. The batch sizes provided are 5, 10, 20, 30, 50, and 1000. If you require a specific number, edit the Enumerated Valid Value named "RowsPerPage".

To change the number of rows displayed in search results:

1. Navigate to Tools & Settings > Object Modeling > Enumerated Valid Value > Manage.

2. In the EVV Name field, type the value RowsPerPage.

3. Click Search.

4. Select the RowsPerPage row, and click Edit.

5. In the Details tab, edit the values as desired, and click OK.

   A confirmation message displays when the new values are saved.

## 12.3 Troubleshooting

If the application system response becomes slow, check the following:

- Check CPU usage and memory usage of the process at that point in time (in case of UNIX systems use the following commands: prstat and memstat, and mpstat.

- Using the application server console, check queue length and memory utilization in the performance monitoring tab.

- Check the CPU usage and memory usage of the database process (Oracle processes) at the same time on the database server.

- Check the network to see if the connectivity between the application server, the database and the Web server is established.