Fabric Studio enables you to develop, test and monitor projects within the Studio using Fabric’s test and log capabilities.
To display a list of recent messages from the server, click Server / Activity Logs (left menu). By default, this window only displays warnings and error messages, however additional messages and notices can also be reviewed.
The following are the main log options:
Click for more information about UI Components and Menus.
Server Logs
Activity Logs
Compilation Errors
Output
Logs and messages can also be used for debugging purposes. The log.info () method is available to enable Fabric’s runtime Debug options. This method can be added to any Java code and its output can be viewed after deployment and during runtime.
For example, see the fnCreateInstID function under Customer LU in the demo project:
if (i_id!=null && !i_id.isEmpty()){
// Increase the input by 10 and return
log.info("o_id: "(Integer.sum(Integer.valueOf(i_id),10)+""));
return Integer.sum(Integer.valueOf(i_id),10)+"";
}
return "0";
The runtime log (k2fabric.log) can be reviewed in the Fabric Server’s Logs directory or in the Studio’s Output logs.
Press the Log icon at the Activity Bar to open the Log Viewer, where you can see list of logs.
The most useful log file is the k2fabric.log. Click and see it at main pane.
Log files are shown with two important features:
Like any file which is shown and automatically opened at the main panel, you can drag and drop it to other panels. for example - drag the log to the bottom panel and track on issues, while continuing work and debug your project at the main panel. In the below illustration, Graphit file is opened at main panel while log is at the bottom panel
Use the bottom status bar log items to:
Fabric Studio enables you to develop, test and monitor projects within the Studio using Fabric’s test and log capabilities.
To display a list of recent messages from the server, click Server / Activity Logs (left menu). By default, this window only displays warnings and error messages, however additional messages and notices can also be reviewed.
The following are the main log options:
Click for more information about UI Components and Menus.
Server Logs
Activity Logs
Compilation Errors
Output
Logs and messages can also be used for debugging purposes. The log.info () method is available to enable Fabric’s runtime Debug options. This method can be added to any Java code and its output can be viewed after deployment and during runtime.
For example, see the fnCreateInstID function under Customer LU in the demo project:
if (i_id!=null && !i_id.isEmpty()){
// Increase the input by 10 and return
log.info("o_id: "(Integer.sum(Integer.valueOf(i_id),10)+""));
return Integer.sum(Integer.valueOf(i_id),10)+"";
}
return "0";
The runtime log (k2fabric.log) can be reviewed in the Fabric Server’s Logs directory or in the Studio’s Output logs.
Press the Log icon at the Activity Bar to open the Log Viewer, where you can see list of logs.
The most useful log file is the k2fabric.log. Click and see it at main pane.
Log files are shown with two important features:
Like any file which is shown and automatically opened at the main panel, you can drag and drop it to other panels. for example - drag the log to the bottom panel and track on issues, while continuing work and debug your project at the main panel. In the below illustration, Graphit file is opened at main panel while log is at the bottom panel
Use the bottom status bar log items to: