Troubleshooting

Troubleshoot the following:

• Report Error
  
• Restart Application Server After Redeploying TMS Lite Browser
  
• Cannot Log In to Application
  

Report Error

If you are getting an error message like "Java exception" followed by another message like "http://127.0.0.1/opaxdo/getXdoReport not found" when you try to run a TMS report, you may want to modify the setting of registry variable OPA_LOCAL_MT_URL. This variable is used to redirect the server to the opaxdo servlet to get reports. When not defined, http://127.0.0.1 is used as default value.

Depending on the settings on middle tier, you may encounter this problem. To fix it, add a port number to the registry variable OPA_LOCAL_MT_URL value on the middle tier; for example, http://127.0.0.1:7777.

To confirm that the path in the registry variable is correct, submit the value such as http://127.0.0.1:7777 (or, without port, http://127.0.0.1) from a browser on the middle tier. If the registry value is correct, you receive the message "Got Request."

Restart Application Server After Redeploying TMS Lite Browser

If you redeploy the TMS Lite Browser .ear file—for example, to apply a patch—restart the application server, including the WebLogic Admin Server. This helps clear connection pools and any DLLs that may be loaded.

If you do not restart the server, an error message may be displayed the next time a user opens the TMS Lite Browser that includes:

java.lang.UnsatisfiedLinkError: Native Library

Cannot Log In to Application

If you cannot log in to the TMS Lite Browser, you may have entered the application's URL twice in the same browser window.

Close all browser windows and try the URL again.