Copyright © 2003 - 2004 OMS Project, DORSCH Consult, NGWA
Copyright © 2005, 2006 DORSCH Consult
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is available from the Free Software Foundation (http://www.gnu.org).
$Date: 2006-09-26 14:06:35 +0300 (Tue, 26 Sep 2006) $
Table of Contents
List of Figures
Table of Contents
General information for BMFO administrators.
This document describes how to setup and administer the Bulk Meter Flow and Operations (BMFO) application version 1.2.4.
BMFO is available from http://bmfo.sourceforge.net.
Warning | |
---|---|
BMFO is a web-based application, but it should be used only in an intranet environment. If you are going to use BMFO on the internet, you should perform a security review of the application sources or add additional security measures like authentication on the web server level and SSL. BMFO is free software you can find more information available in user guides and development guides |
This section describes the hard- and software requirements of the BMFO application.
A PC with at least two GHz CPU speed and one GB RAM is required to run the BMFO application. Note that depending on the size of the data, number of concurrent users and database backend, the actual hardware requirements can be much higher.
The following software packages are required to run the PHP application:
Web browser
Web server
PHP
JPGraph
RDBMS
Java Development Kit
JasperReports
Servlet Engine, e.g. Apache TOMCAT
BMFO
Caution | |
---|---|
JpGraph is released under a dual license. QPL 1.0 (Qt Free License) for non-commercial, open-source and educational use and JpGraph Professional License for commercial use. For BMFO systems in a production environment, a JpGraph Professional License is required. The license and more information on JpGraph are available from http://www.aditus.nu/jpgraph/. |
A relational database management system supported by the PHP dbx extension is required in order to run the application. ORACLE and PostgreSQL have been tested.
If you would like to use a different database backend contact the BMFO developers.
If ORACLE is used as the database backend, at least version 9i is required..
The free ORACLE 10g Express Edition(XE) is available for download from http://www.oracle.com/technology/software/products/database/xe/index.html.
ORACLE versions 9i and 10g have been tested with BMFO.
PostgreSQL versions 7.3, 7.4, 8.0 and 8.1 have been tested as database backends for BMFO.
Version PostgreSQL version 8.1 is recommended.
PostgreSQL is freely available from http://www.postgresql.org
Table of Contents
The reference for BMFO administrators.
This section describes the BMFO installation on Windows.
Installation on other operating systems such as Linux is possible but not described in detail in this document.
Section 1.3 explains the installer-based installation. Section 1.4 has more detailed information - use this if the installer does not work for you. Installation steps that are common to both installation types are described under Section 1.1.
In the following, $BMFO
and %BMFO%
reference the directory where the application is installed. Replace this
with the actual path or set an environment variable. $BMFO
is a bash environment variable and
%BMFO%
a Windows enviroment variable.
The recommended installation folder for BMFO is
c:\program files\bmfo
.
After the installation has finished, see the Section 2.1.
This section describes BMFO installation steps that are common to both the installer-based and manual installation.
Please choose one database backend, either ORACLE (Section 1.2.1) , ORACLE XE (Section 1.2.2) or PostgreSQL (Section 1.2.3).
A webserver supporting PHP is required. The Apache webserver has been used for the development.
Apache version 2.0.59 or higher is recommended to operate BMFO.
Caution | |
---|---|
Until Apache 2.2 is supported by PHP 5 (Most probably in PHP 5.2.0), stick to Apache 2.0. |
Tip | |
---|---|
If you are running Skype, you may want to shutdown Skype while you are installing Apache as Skype might otherwise prevent Apache from using port 80. |
Tip | |
---|---|
If the Apache installation is not fully
successful because another program (e.g. IIS) is already using port
80, simply edit |
Run the Apache installer. The Apache
installer is available from the setup
folder of
the BMFO CD or from the Apache website: http://httpd.apache.org.
C:\Program Files\Apache Group
and click
.Tip | |
---|---|
The BMFO installer reads the Apache installation folder from the Windows registry. You can install Apache to different locations. |
Tip | |
---|---|
If the Apache installation fails because another application is using port 80, you can use the following commands to find out which application is using port 80: netstat -aon tasklistLook for the process id (PID) of the process occupying port 80 and find the application of the process id. |
If you would like to use the Apache webserver distributed with ORACLE, please consult the ORACLE documentation for configuration and PHP installation instructions.
The Java 2 Software Development Kit
(J2SDK), version 1.5 or higher is required to run
BMFO. Earlier Java versions will also work
but require a recompilation of the bmfo_report.war
web application archive.
J2SDK is available from http://java.sun.com. The download page is http://java.sun.com/j2se/1.5.0/download.html.
Select the link Download JDK 5.0 Update 5 and follow the instructions.
Run the J2SDK installer (jdk-1_5_0_05-windows-i586-p.exe
).
Apache TOMCAT version 5.5.17 has been tested with BMFO. Other version as well as other servlet containers should work but are not described in detail.
TOMCAT is available from the BMFO CD or http://tomcat.apache.org. The download page is http://tomcat.apache.org/download-55.cgi. Select Windows Executable under binary core distribution.
Note | |
---|---|
Java needs to be installed before you can run TOMCAT. |
Run the TOMCAT setup
(apache-tomcat-5.5.17.exe
).
Caution | |
---|---|
Make sure to remember the TOMCAT administrator password as it will be required later during the installation process and for administration purposes. |
Tip | |
---|---|
In case port 8080 is occupied already (e.g. by an ORACLE installation), you can use an alternative port like 8081. Make sure to remember the alternative port number as it will be required later during the installation process and for administration purposes. |
You have to choose one of the possible database backends:
ORACLE (See Section 1.2.1) |
ORACLE XE (See Section 1.2.2) |
PostgreSQL (See Section 1.2.3) |
Caution | |
---|---|
You don't have to follow the instructions in this chapter if you are using ORACLE XE or PostgreSQL as the database backend. See Section 1.2.2 or Section 1.2.3 in this case. |
Installation instructions for ORACLE 9i or 10g.
Start the ORACLE installer.
Select Standard Installation and click (Figure 20).
Select the General Purpose configuration and click (Figure 21).
Enter bmfo
as the Global
Database Name. Click (Figure 22).
Caution | |
---|---|
If you need Arabic support, make sure to use the Windows-1256 codepage when creating the database. Changing the characterset later on in the registry will not work. |
Caution | |
---|---|
Restart the system before continuing with the BMFO installation. |
Caution | |
---|---|
You don't have to follow the instructions in this chapter if you are using ORACLE or PostgreSQL as the database backend. See Section 1.2.1 or Section 1.2.3 in this case. |
Installation instructions for the ORACLE 10g Express Edition (XE) backend.
Start the ORACLE installer
(OracleXE.exe
).
Caution | |
---|---|
Make sure to remember the administrator password as it will be required later during the installation process (Section 1.3.2) and for administrative purposes. |
Caution | |
---|---|
Restart the system before continuing with the BMFO installation. This will make sure that the necessary environment variables are in place. |
This section describes how to install PostgreSQL for Windows.
Caution | |
---|---|
You don't have to follow the instructions in this chapter if you are using ORACLE or ORACLE XE as the database backend. See Section 1.2.1 or Section 1.2.1 in this case. |
The PostgreSQL installer is available from the
setup
folder of the BMFO CD or from http://www.postgresql.org.
Run the PostgreSQL installer and select the English language.
Caution | |
---|---|
Make sure to remember the administrator password as it will be required later during the installation process and for administrative purposes. |
Accept the default selection as shown in Figure 38 and click .
Instructions for a BMFO installation on Windows using the BMFO installer. The installer automates the installation as much as possible. This is the easiest way to install BMFO.
PHP can be installed using the BMFO scripting installer, which is available from the BMFO CD or from http://bmfo.sourceforge.net. If you don't want to use the BMFO scripting installer to install PHP, please refer to Section 1.4.
Start the BMFO Scripting installer
(bmfo-scripting-setup-5.1.4-1.exe
.
Tip | |
---|---|
PEAR modules can be easily installed and upgraded over the internet. See the PEAR documentation for details. However, the BMFO scripting installer provides all necessary packages. |
c:\windows\php
, by clicking
(Figure 44).
Follow these steps if you are installing BMFO with an ORACLE or ORACLE XE database backend. If you are using PostgreSQL as the database backend, refer to Section 1.3.3.
The BMFO installer is available from http://bmfo.sourceforge.net.
Run the BMFO installer
(bmfo-setup-XXX.exe
).
Choose ORACLE as your database backend.
Make sure that the following components (Figure 46) are selected:
BMFO
Apache/PHP Config
ORACLE
Servlet
JpGraph
Scheduled Cleanup
Caution | |
---|---|
Unlike shown in Figure 53, you will most probably be using a different port than 8080 because ORACLE is occupying port 8080. Review the port number critically. Check that TOMCAT is up and running on the port you expect if necessary. See the TOMCAT documentation for details. |
You can accept the default installation location as shown in Figure 49.
Once the BMFO installer has finished, you should be able log on to BMFO using the shortcut from the Start Menu.
The default URL is http://localhost/bmfo/.
See the Quick Start section in the BMFO user guide.
The default user name is bmfo and the default password is bmfo.
Warning | |
---|---|
It is recommended that you change the default password "bmfo" for the ORACLE user bmfo as soon as possible for security reasons. |
This section contains information how to install BMFO using the installer for a PostgreSQL backend. If you are installing with and ORACLE or ORACLE XE backend, please refer to Section 1.3.2.
Run the BMFO installer
(bmfo-setup-XXX.exe
).
Select the components as shown in Figure 51.
Caution | |
---|---|
Change the user name to "postgres" as shown in Figure 52. Enter the PostgreSQL superuser password which you've entered before (Section 1.2.3, Figure 36). Click . |
You can accept the default installation location as shown in Figure 54.
Once the BMFO installer has finished, you should be able log on to BMFO using the shortcut from the Start Menu.
The default user name is bmfo and the default password is bmfo.
Warning | |
---|---|
It is recommended that you change the default password "bmfo" for the PostgreSQL user bmfo as soon as possible for security reasons. |
General installation instructions to run BMFO on Windows. Similar installation steps are required on other operating systems, like Linux.
SQL Data Definition Language scripts are available for creating the required tables in ORACLE or Postgres databases. The scripts are located in the script folder of the BMFO distribution.
The scripts set up the necessary table structure for the application.
Note | |
---|---|
%BMFO% in this section refers to the actual BMFO installation directory. If this path contains spaces, you have to quote appropriately. |
%BMFO%\script\prepare_oracle.sql
is the
first script, to be executed by the ORACLE system account.
The scripts
%BMFO%\script\create_bmfo_ddl.sql
,
%BMFO%\script\oracle_ddl.sql
and
%BMFO%\script\create_views.sql
have to be executed
using the bmfo user.
For example in SQL Plus:
@%BMFO%\script\create_bmfo_ddl.sql @%BMFO%\script\oracle_ddl.sql @%BMFO%\script\create_views.sql
Remember to replace
%BMFO%
with the actual location of the
BMFO application.
Warning | |
---|---|
The default password for the ORACLE user bmfo is "bmfo". For security reasons it should be changed as soon as possible. |
To finish, run script\oracle_role.sql
as
the ORACLE system user.
Use the following commands to manually create and initialize the bmfo database on a PostgreSQL backend:
createdb -U postgres bmfo createuser -U postgres bmfo createlang -d bmfo -U postgres plpgsql psql -d bmfo -U bmfo -f %BMFO%\script\create_bmfo_ddl.sql psql -d bmfo -U postgres -f %BMFO%\script\postgresql_ddl.sql psql -d bmfo -U postgres -f %BMFO%\script\create_views.sql
Warning | |
---|---|
The default password for the PostgreSQL user bmfo is "bmfo". For security reasons it should be changed as soon as possible. |
If you are using an ORACLE backend, the following lines have to
be added to httpd.conf
:
SetEnv ORACLE_HOME "c:\ORACLE\Ora90" SetEnv TEMP "c:\temp"
As the admin folder contains pages that perform administrative tasks, it should be protected by a password on the Apache level. See the Apache documenation for the details.
PHP, the Hypertext Pre-Processor is required in order to run the application. PHP versions older than 5.1.4 have not been tested with BMFO 1.2.0.
Caution | |
---|---|
Please install the zipfile distribution (windows binaries zip file)of PHP, not the installer version. Also install the PECL modules. Notice the difference between the PHP installer and the BMFO Scripting installer. |
PHP is available from http://www.php.net. The following page provides the required package (version 5.1.4): http://www.php.net/get/php-5.1.4-Win32.zip/from/a/mirror
Extract the zip file to c:\windows
and
rename the folder php-5.1.4
to
php
.
At least the following PHP extensions have to be loaded:
dbx
gettext
dbase
gd
pgsql
The php.ini
file should be edited
accordingly. The important settings are summarized
below:
[PHP] max_execution_time = 300 extension=php_dbase.dll extension=php_dbx.dll extension=php_gd2.dll extension=php_gettext.dll extension=php_iconv.dll extension=php_oci8.dll extension=php_pgsql.dll [mail function] SMTP = igwa_2 sendmail_from = bmfoadministrator@ngwa.com.jo
Caution | |
---|---|
Remember to adjust the |
PHP should serve the pages with UTF-8 encoding. This can be
achieved by adding the following line to
php.ini
:
default_charset = "utf-8";
Make sure that session support is enabled, by adjusting the following line:
session.save_path=c:\tmp
Make sure that the temporary directory c:\tmp exists.
The PHP installation can be completed with the following three
lines in httpd.conf
:
ScriptAlias /php/ "c:/windows/php/" AddType application/x-httpd-php .php Action application/x-httpd-php "/php/php-cgi.exe"
Install the following PEAR packages:
Pager |
DataObject |
DataObject_FormBuilder |
PEAR is the PHP Extensible Application Repository.
PEAR can be found under http://pear.php.net.
JPGraph is a graphing package for PHP. It is required for the graph display in the application.
JpGraph is available from http://www.aditus.nu/jpgraph/.
In order to install JPGraph, unzip the JPGraph zipfile and copy
the files from the folder stripped-src
if available
to%BMFO%\jpgraph
Caution | |
---|---|
Some PDF reports require that the Arial TrueType font is
installed in |
Copy %BMFO%\conf\dataobject.ini.oracle
or %BMFO%\conf\dataobject.ini.postgresql
to
%BMFO%\conf\dataobject.ini
.
If you are using ORACLE, copy
%BMFO%\include\dbx_connect_oracle.php
to
%BMFO%\include\dbx_connect.php
. If you are using
PostgreSQL, copy
%BMFO%\include\dbx_connect_postgresql.php
to
%BMFO%\include\dbx_connect.php
. Please review the
connection settings in the files and adjust them if required.
Description of various BMFO administration tasks.
BMFO has some configuration options available through variables
in include/dbx_config.php
.
In case of problems opening the PDF and XLS reports generated
by the servlets, replace "localhost" in strServletUrl
with the name of the server.
BMFO allows to limit access to selected operational areas on a per-user basis.
After you installed BMFO the wizard will create two roles,bmforole role which you have to assign it from SQL to any new full control user and bmforeadonly role which you have to assign it from SQL for any new read only user.
Access for a user to an operational area is granted by
inserting a record to the UserOperationalArea
table containing the user name and the operational area's coded
value.
As of BMFO version 1.0.6, access control is enforced for all write operations and a number of reporting functions.
The following SQL statement can be used to allow the user "Username" to all operational areas:
insert into UserOperationalArea (select UserOperationalArea_seq.nextval, 'Username', codedvalue from OperationalArea)
BMFO allows to aggregate meter readings using the Aggregation field
of the Meter
table.
If you don't plan to use aggregation, simply fill the Aggregation field from the FacilityID field like in the following example:
update Meter set Aggregation=FacilityID
See the user guide for details.
The admin
folder of the BMFO distribution
contains a utility script that allows loading of a dBase (.dbf) file
to the meter table.
The default path to load the file (c:\temp\meter.dbf
) can be adjusted by editing
admin/load_meter_data.php
.
Tip | |
---|---|
When managing meter location in a geographic information system (GIS), the DBF file can be created by saving the locations as a shapefile. |
Information regarding the link to WIS. WIS is the Water Information System. It uses an ORACLE backend. BMFO interacts with WIS in both directions:
Export of production data through the WIS export file created from the BMFO web interface (SQL script with WIS insert statements is created).
Import of meter locations (Meter objects) from WIS. This requires a database link to WIS.
In order to create a database link to the WIS database,
tnsnames.ora
should contain configuration
statements like the following:
WIS = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = wisserver)(PORT = 1521)) ) (CONNECT_DATA = (SID = ORCL) ) )
The SQL statement to create the link from the BMFO database (ORACLE backend) to the WIS database looks like this:
create database link wislink connect to username identified by password using 'wis';
A script to create the meters from WIS is available in
script/wis2bmfo.sql
.
On the WIS side, the BMFO_METER_VIEW is required. This can be
created using script/create_wis_views.sql
.
Deletion of existing Meter
, OperationaArea
and AdministrativeArea
together with the insertion of new
values is done through script/wis2bmfo.sql
.
The following commandline statement should be scheduled to run every night:
sqlplus user/password@bmfo @wis2bmfo.sql
This section gives detailed information on the necessary steps to update the BMFO application.
Caution | |
---|---|
Please backup the database before updating. |
To upgrade the application, do the following:
Run the BMFO installer and select the "BMFO" and "Update" components.
Update the servlet. Use the TOMCAT Manager to verify that the version number of the servlet is now 1.2.4.
BMFO versions 1.2.0 to 1.2.2 were inserting superfluous installation records upon data entry of operation records. To overcome this problem, verify that you have only installation records for the "Unknown" meter:
select distinct EquipmentOID from InstallationRecordIf the query only returns "Unknown", delete the superfluous installation records with the following query:
delete from InstallationRecord where ID in (select ID from Installationrecord i where RecordDate > (select min(i2.RecordDate) from InstallationRecord i2 where i.NetworkOID = i2.NetworkOID))
You should also make sure that there is at least one installation record for every meter location that has operation records:
insert into InstallationRecord (select NetworkOID, 1, 'Unknown', '', ID, installationrecordid.nextval, RecordDate from OperationsRecord o where NetworkOID in (select OperationsRecord.NetworkOID from OperationsRecord left outer join InstallationRecord on InstallationRecord.NetworkOID = OperationsRecord.NetworkOID where InstallationRecord.NetworkOID is null) and RecordDate in (select min(RecordDate) from OperationsRecord o2 where o.NetworkOID = o2.NetworkOID) and ID = (select min(ID) from OperationsRecord o3 where o.NetworkOID = o3.NetworkOID and o.RecordDate = o3.RecordDate));
To upgrade the application, do the following:
Run the BMFO installer and select the "BMFO" and "Update" components.
Update the servlet.
If you are using an ORACLE backend, add the following function to dbx_connect.php:
/** * Escape a string for a database query. * @param $strString String that should be escaped. * Returns the string escaped by dbx_escape_string(). */ function bmfo_escape_string($strString) { GLOBAL $rdbms; return dbx_escape_string($rdbms, $strString); }
If you are using an PostgreSQL backend, add the following function to dbx_connect.php:
/** * Escape a string for a database query. * @param $strString String that should be escaped. * Returns the string escaped by pg_escape_string(). */ function bmfo_escape_string($strString) { return pg_escape_string($strString); }
Run the BMFO installer and select the "BMFO" and "Update" components.
Update the Servlet.
The major change in version 1.2.1 is the switch to PHP 5. It is recommended to completely remove PHP 4 from the system before installing BMFO Scripting 5.1.4. If necessary, see the complete uninstallation instructions (Section 4.3).
Please follow the steps below to update the sytem:
Install JDK 1.5.0-08.
Install TOMCAT 5.5.17
Delete Apache's httpd.conf
.
Update Apache to version 2.0.59.
Delete c:\windows\php.ini
.
Install BMFO Scripting (PHP) 5.1.4.
Run the BMFO installer.
For an installation with an ORACLE database backend select the following components:
BMFO
Apache/PHP Configuration
Upgrade ORACLE
Servlet
When asked for database connection information, use the bmfo account with the respective password.
For an installation with a PostgreSQL database backend, select the following components:
BMFO
Apache/PHP Configuration
Upgrade PostgreSQL
Servlet
Please insert the following configuration line to
include/dbx_connect.php
:
$GLOBALS['boolDebug'] = false;
Please follow the steps below to update the system:
Install JDK 1.5.0-07.
Install TOMCAT 5.5.17
Update Apache to version 2.0.58.
Install DCMMS Scripting (PHP) 4.4.2-2.
Run the BMFO Installer.
For an installation with an ORACLE database backend, grant the right to create public synonyms to the bmfo user.
Warning | |
---|---|
You will have to create the synonyms yourself, if you forget to grant this right to user bmfo. |
Run the BMFO 1.1.0 installer and select the following components:
BMFO
Upgrade ORACLE
Servlet
When asked for database connection information, use the bmfo account with the respective password.
For an installation with a PostgreSQL database backend, select the following components:
BMFO
Upgrade PostgreSQL
Servlet
Note | |
---|---|
Make sure that the new field
|
Caution | |
---|---|
When you are using an ORACLE backend and are experiencing
problems logging on after the ugrade, make sure that you use the
"===" operator instead of "==" in
|
Please follow the steps below to update the system:
Run the DCMMS Installer.
For an installation with an ORACLE database backend, grant the right to create public synonyms to the bmfo user.
Warning | |
---|---|
You will have to create the synonyms yourself, if you forget to grant this right to user bmfo. |
Run the BMFO 1.0.8 installer and select the following components:
BMFO
Upgrade ORACLE
Servlet
When asked for database connection information, use the bmfo account with the respective password.
For an installation with a PostgreSQL database backend, select the following components:
BMFO
Upgrade PostgreSQL
Servlet
The 1.0.7 release is a pure bugfix release of the 1.0.6 release. As no changes were done to the data model, simply running the installer, selecting the DCMMS component and updating the servlet is sufficient.
Please follow the steps below to update the system:
Install JDK 1.5.0.
Install TOMCAT 5.5.
Update Apache to version 2.0.55.
Install DCMMS Scripting (PHP) 4.4.1.
Run the DCMMS Installer.
For an installation with an ORACLE database backend, grant the right to create public synonyms to the bmfo user.
Warning | |
---|---|
You will have to create the synonyms yourself, if you forget to grant this right to user bmfo. |
Run the BMFO 1.0.6 installer and select the following components:
BMFO
Upgrade ORACLE
Servlet
Scheduled Cleanup
When asked for database connection information, use the bmfo account with the respective password.
For an installation with a PostgreSQL database backend, select the following components:
BMFO
Upgrade PostgreSQL
Servlet
Scheduled Cleanup
Set up access control using the UserOperationalArea
table (Section 2.3).
Fill the Aggregation field in the
Meter
table (Section 2.4).
This section gives help to solve problems with the BMFO installation.
The BMFO info mailing list may provide help
to solve problems, either through the archives which are available under
http://sourceforge.net/mailarchive/forum.php?forum_id=32236.
or by sending an email to
<bmfo-info@lists.sourceforge.net>
.
The bug and support trackers are available through the BMFO website, http://bmfo.sourceforge.net .
Caution | |
---|---|
Please make sure that you look at all bug reports support requests, not only the open ones. |
The uninstallation steps described below will completely remove BMFO and all of its components.
Warning | |
---|---|
Make sure that you have backed up your BMFO data (database dump file). |
Uninstall Apache through the Control Panel.
Uninstall ORACLE, ORACLE XE or PostgreSQL through the Control Panel.
Uninstall TOMCAT through the Control Panel.
Uninstall BMFO through the Control Panel.
Uninstall BMFO Scripting through the Control Panel.
Delete c:\program files\postgresql
.
Delete c:\program files\bmfo
.
Delete c:\windows\php
.
Delete c:\windows\pear
.
Delete c:\windows\php.ini
.
Delete c:\program files\Apache Group
.
Delete c:\program files\Apache Software Foundation
.
Delete c:\tmp
Verify that the Scheduled Task "at1" was removed. Delete if necessary.
Delete the Windows user "postgres", e.g. with the following command:
net user postgres /delete
Verify that the BMFO folder was removed from the Start Menu.
Reboot.
Frequently asked questions.
Check if the Aggregation
field of the
Meter
table is filled if the generated
Summary Well Production Reports are empty or if the value
"null" appears in the record.
If you encounter an error like the following the Apache's
error.log
, restart the database:
[Tue Sep 26 12:14:40 2006] [error] [client 127.0.0.1] PHP Warning: oci_connect(): ORA-12520: TNS:listener could not find available handler for requested type of server
This was encountered for example during the webtest run.
When trying to open a page, the following message appears on the server: Unknown(): Unable to load dynamic 'C:/Program Files/PHP/extensions\php_gettext.dll' - The specified module could not be found.
The following points may help to solve the problem:
Make sure that you've installed the zip distribution of PHP and not the installer version
Copy the file libintl-1.dll
to
c:\winnt\system32
or
c:\windows\system32
.
This also applies to iconv.dll
- in
this case, copy iconv.dll
to
c:\windows\system32
or
c:\winnt\system32
.
The dll files can be found in the folder
dlls
of the PHP
distribution
In case the PDF and XLS report generation does not work
because of a wrong URL (e.g. using localhost instead of the real
server name), make sure that strServletUrl
is
configured correctly (Section 2.1).
Caution | |
---|---|
This information only applies to BMFO prior to version 1.0.6. |
The PDF reports are not working. An empty page or a page with an error message appears.
Check the [Java] section in
php.ini
. Make sure that the filenames are
correct.
Review the error log of the webserver. In the case of
Apache, this is the file
error.log
in the logs
folder
of the Apache installation.