Within the WebMaker Design Studio the View Debugger option is integrated and available from most screens as an icon on the task bar. This version of the Debugger application operates on the test runtime application on your local development machine. The Test Settings screen allows the user to configure various Application configuration settings for logging and platform optimization.
In some situations you may need to deploy a version of the Debugger that runs on a System Test, Acceptance Test or Production Server that is a "standalone" application server deployment.
Typically, this is only required if you have performed a "WAR" or "Tomcat" Publication.
This can be required if you are looking to debug or manage some platform optimization aspects of applications in that environment.
Dashboard WAR installation on an Application Server
In order to use the Dashboard (Debugger and Application Configuration capabilities) within a "standalone" runtime environment please use the following installation steps.
Download the Dashboard V5 WAR file and deploy it to your remote Application Server using the standard Application Server deployment technique.
If needed, ensure that the morphyc-licence-file system property is correctly configured to point to the location of your WebMaker license file.
Dashboard Startup
Once installed, you can start the Dashboard using the following URL (assuming the application was deployed at the +?+?++dashboard+?+?+? context using the appropriate Application Server options.):
http://<your-server>:<port>/dashboard/dashboard.do
Unlike the WebMaker Design Studio environment, the Dashboard on the server environment does not know which project to load by default.
You can use the Dashboard in two modes, either provide it the location of a log file to view just those logs, or more commonly provide the location of the morphyc configuration file for a deployed application. In this second mode, you will be able to view the current logs, as well as configure the logging and optimization settings for the application.
In either case, the path you enter must be the path to the relevant file on the server where the Dashboard application is running. You can use the Browse buttons to help enter these paths, but this will select a file path on your current machine so generally is only useful if you are accessing the Dashboard application from the machine on which it is running.
For a published application, these files are usually located in the doc directory within the application+?+?+?s webapp structure.
Reloading an Application after changes
If you have used the runtime Dashboard to change Application Configuration settings you will need to restart your application for the changes to take effect. The easiest way to do this is to call the following URL against your application: http://<your-server>:<port>/<your-webapp>/reload_application.do
Refreshing logs
When using the runtime Dashboard to review an application you have the capability to clear the log file at any point if required.
This clearing of the logs can be useful if you want to start/stop logging for a particular point in an application screen flow.
Log Settings can be changed at any point in time, but won't take effect until the refresh logs command is issued to the application project.
Use the following URL to refresh the logs in order to ensure revised log settings are applied and to clear any existing logs:
http://<server>:<port>/<your-webapp>/refresh_logs.do
Note: You will need to use the buttons in the Dashboard application to redisplay the updated logs.
For more information on how to use the Dashboard application please refer to the WebMaker Documentation
In some situations you may need to deploy a version of the Debugger that runs on a System Test, Acceptance Test or Production Server that is a "standalone" application server deployment.
Typically, this is only required if you have performed a "WAR" or "Tomcat" Publication.
This can be required if you are looking to debug or manage some platform optimization aspects of applications in that environment.
Dashboard WAR installation on an Application Server
In order to use the Dashboard (Debugger and Application Configuration capabilities) within a "standalone" runtime environment please use the following installation steps.
Download the Dashboard V5 WAR file and deploy it to your remote Application Server using the standard Application Server deployment technique.
If needed, ensure that the morphyc-licence-file system property is correctly configured to point to the location of your WebMaker license file.
Dashboard Startup
Once installed, you can start the Dashboard using the following URL (assuming the application was deployed at the +?+?++dashboard+?+?+? context using the appropriate Application Server options.):
http://<your-server>:<port>/dashboard/dashboard.do
Unlike the WebMaker Design Studio environment, the Dashboard on the server environment does not know which project to load by default.
You can use the Dashboard in two modes, either provide it the location of a log file to view just those logs, or more commonly provide the location of the morphyc configuration file for a deployed application. In this second mode, you will be able to view the current logs, as well as configure the logging and optimization settings for the application.
In either case, the path you enter must be the path to the relevant file on the server where the Dashboard application is running. You can use the Browse buttons to help enter these paths, but this will select a file path on your current machine so generally is only useful if you are accessing the Dashboard application from the machine on which it is running.
For a published application, these files are usually located in the doc directory within the application+?+?+?s webapp structure.
Reloading an Application after changes
If you have used the runtime Dashboard to change Application Configuration settings you will need to restart your application for the changes to take effect. The easiest way to do this is to call the following URL against your application: http://<your-server>:<port>/<your-webapp>/reload_application.do
Refreshing logs
When using the runtime Dashboard to review an application you have the capability to clear the log file at any point if required.
This clearing of the logs can be useful if you want to start/stop logging for a particular point in an application screen flow.
Log Settings can be changed at any point in time, but won't take effect until the refresh logs command is issued to the application project.
Use the following URL to refresh the logs in order to ensure revised log settings are applied and to clear any existing logs:
http://<server>:<port>/<your-webapp>/refresh_logs.do
Note: You will need to use the buttons in the Dashboard application to redisplay the updated logs.
For more information on how to use the Dashboard application please refer to the WebMaker Documentation