If your pipelines are not working correctly, review the Forms Services Platform SystemOut.log file to help determine your problem point.
When deployed to WebSphere® Application Server, Forms Services Platform log messages are displayed in the server SystemOut.log file.
Log messages from a standalone Forms Services Platform are forwarded to System.out and are displayed in the console.
Turning on debugging help
If your pipeline does not produce the results you want you can turn on debugging information for any pipe by setting the following configuration entry in the pipeline properties file:
ibm.mypipe.pipeline.debuginfo = string:true
You must add this flag to each pipe in the pipeline that you want the debug message to be printed for. Adding this flag causes the pipe to write out information messages when it is run indicating that the pipe loaded properly. You can then see the order in which all your pipes are executed.
For a description of what each information message means, see Forms Services Platform log messages
When you deploy your system into production, turn off this flag.
Problem: Your pipeline is not running
If your pipeline is not running, use the following flow chart:
Problem: The pipe is not called in the log file
If you do not see your pipe being called in the log file, use the following flow chart to fix this problem.
Parent topic: Developing applications using the Forms Services Platform
Previous topic: Running pipelines