Wednesday, October 1, 2008

How to troubleshoot Oracle Web Conferencing?

1. Log into Web Conferencing as SYSADMIN (user with businessadmin role):
http://host.domain:port/imtapp/app/prelogin.uix

The following tabs are visible for such a user having administrative privileges:
• Monitor tab
• Reports tab
• Sites tab
• System tab

2. imtctl> runTests -> Self-test for all Web Conferencing components.

3. Log files:
Oracle Web Conferencing provides the administrator with a lot of log files. They are stored under $MIDTIER_HOME/imeeting/logs directory.

Viewing log files with a browser:
An important prerequisite is that you're logged in as a system administrator (businessadmin role) to the Web Conferencing main page.

Then, log files can be accessed with:
http://host.domain:port/imtapp/logs/system.jsp
&
http://host.domain:port/imtapp/logs/imtLogs.jsp

Just follow the links to check what happened during each session.

Self tests via the Web:
The Web Conferencing application can also test itself via the following URLs:
http://host.domain:port/imtapp/app/adm_sa_insttests.uix

Meeting capability can be self-tested:
http://host.domain:port/imtapp/servlet/ImtTestServlet?mtgtest=True

Database connectivity can be self-tested:
http://host.domain:port/imtapp/servlet/ImtTestServlet?dbtest=True

The System Sanity Tests URL is:
http://host.domain:port/imtapp/app/imttests.jsp

No comments:

Post a Comment