Generating Reports and Using Analytics Using Docker¶

• Generating Reports and Using Analytics Using Docker
  • Introduction
  • Creating a Custom Directory for Reporting
  • Generating Reports
  • Running the Analytics Server
  • Accessing Analytics

Introduction¶

Your 4GL code and schemata has been placed into a project on which the FWD tools can execute. The FWD Code Analytics is a powerful toolset that gives deep insight into your 4GL codebase. This can save hours or weeks of time by answering questions that would otherwise be time consuming to determine.

At the beginning of a conversion project, the Code Analytics tools would be used for performing an Assessment, which is critical for planning the migration of your project to Java using FWD. If you have already performed this Assessment, then additional usage of this tooling is optional.

This section covers generating reports that can be accessed via the FWD Analytics server. This also includes details of how to run and access the Analytics server. Before executing these steps, you MUST have gone through the Conversion Project Setup Using Docker section.

For general information on FWD Code Analytics, see Code Analytics.

Creating a Custom Directory for Reporting¶

The same conversion project directory (created in Conversion Project Setup Using Docker) cannot be used simultaneously for both Analytics and Conversion. Instead, you must duplicate the setup to create two independent project directories if Analytics and Conversion are needed simultaneously. That is why it is a good reason to have made a backup of the original configuration project, or checked it into source control.

If you are using your new project, pick up from Conversion Project Setup Using Docker after the source code and schemata is in place. You might want to repeat the steps, and add _reports to the directory name.

If you are using Hotel GUI sample:

1. Run Step 1, using hotel_gui_reports as the <optional_directory> parameter.
2. Use the newly created hotel_gui_reports project directory for the ./bootstrap_conversion.sh step.

Generating Reports¶

This should be executed from a Docker bash shell opened under fbash.sh (described here).

cd ~/projects/<project_name>
ln -s /opt/fwd p2j
ant clean rpt

It should take less than 10 minutes on most systems for Hotel GUI. Your application may vary, depending upon the size.

When FWD finished generating the reports, exit the container.

Running the Analytics Server¶

After the reports are generated, you can then start the report server. This must be done from a new fbash.sh that shares the 8443 port. Start with the report server on the command line:

cd ~/projects/<project_name>
fbash.sh --manual_port=8443:8443 -c "sh -c \"(cd deploy/server; ./report.sh)\"" 

This passes the command which starts the reports server directly to the container.

Stop the Analytics Server with Control+Break in this session.

Accessing Analytics¶

When the Analytics Server is running, you can access the web UI for Analytics using https://localhost:8443/ with username admin and password the configured appname (this is hotel for Hotel GUI). Press "Cancel" when prompted to change the password, and you can proceed with your reporting.

---

© 2004-2026 Golden Code Development Corporation. ALL RIGHTS RESERVED.