Troubleshooting Common Errors on Application Servers

The following topic covers troubleshooting issues on non-NetWeaver application servers.

Locating Log Files

When Redwood Server is installed on an application server and you have an issue that prevents you from accessing the Redwood Server interface, you must locate the application server log files. The specific location can usually be customized, this topic lists the default location of log files.

Redwood Platform

The log files for the application server can be found in the following location:

• <install_dir>/j2ee/cluster/server1/log - default log directory of the Redwood Server application
  • dbinit.log - log file listing the database
  • scheduler.log - revolving Redwood Server log file
  • scheduler.log<n> - older log files
• <install_dir>/j2ee/cluster/adminserver1/log - default log directory of the admin server application
  • scheduler.log - revolving log file of the Redwood Server admin server

IBM WebLogic

• base directory (for example bea/wlserver_10.3) - this will be referred to as <weblogic_home>
• domain (for example <weblogic_home>/samples/domains/wl_server) - this will be referred to as <weblogic_domain>
• server instance (for example <weblogic_domain>/servers/examplesServer) - this will be referred to as <server_home>

The primary log files are in a location that you will have defined when installing the application and configuring log4j logging:

Within <weblogic_domain>/lib/log4j.properties are two properties:

• log4j.appender.SCHEDULER.File - defines where the scheduler.log file is. The default is /var/log/scheduler/scheduler.log
• log4j.appender.DBINIT.File - defines where the db-init.log file is. The default is /var/log/scheduler/db-init.log

Other logs that may contain useful information are the general WebLogic server logs:

• $server_home/logs - server runtime logs should keep details of startup/shutdown as well as application deployment logs, it is also where the job logs are stored.

Depending on whether you have changed the configuration in the log4j.properties file or not the two directories that are needed are:

1. /var/log/scheduler.
2. $server_home/logs.

SAP JCo Issues

The JCo library is used to connect to the ABAP stack of an application server. Incorrectly installed JCo libraries will prevent you from connecting and scheduling workload on SAP application servers.

The most common reasons for not being able to load the JCo libraries are dependency issues.

onsiteTopic