877.245.5629
sales@billmax.com
|
BillMax Billing Solutions 877.245.5629 sales@billmax.com |
| CI Administration | ||
|---|---|---|
 |
Chapter 5. Configuring the BillMax Customer Interface | 
|
The CI supports the concept of not allowing customer to register new Service with objectionable login names. The list of names that are not allowed is maintained in disallowedname list.
In certain cases, the interpretation of numeric data in BillMax may be as money or currency. As the interpretation of these fields may not be known beforehand by the developers of BillMax, BillMax has supplied a mechanism for specifying the display of numeric data as money or currency. This is done by clicking on either the ""ACCOUNT MONEY FIELDS", ""USER MONEY FIELDS" or ""SERVICEMONEY FIELDS" button. This will display a List that may be used to specify the database field that should be interpreted/displayed in a monetary format.
Log files for the bmuid are contained in /usr/local/billmax/logs. The bmuid-access.log file list all requests while the bmuid-error.log file logs certain errors.
If the interface fails or doesn't give the expected result, start by checking the log files (described above). For detailed logs from the bmuid and bmui.cgi processes, set the cgidebuglvl parameter to -2. (If debugging the client, remember to re-generate/re-copy the bmui.config file). These detailed logs are written to the /tmp directory on each machine. The name of logs begins with the prefix bmuid_ or bmui_. After debugging remember to reset cgidebuglvl as this setting will generate many files over time possibly resulting in a full file system.
No connection to the server:
Ensure that the daemon in running. It listens on TCP/IP port 5023. It must run under the root user.
Test to see if you can access your server within your firewall. You can do so without using the client. Try: telnet <your BillMax Host> 5023. You should see something similar to the following if the connection was made:
Trying 206.54.190.232...Connected to demo20.billmax.com.
Escape character is '^]'.
1000 Command OK.
Enter "QUIT" to shut down this instance of the Daemon.
2000 Closing Connection
Connection closed by foreign host.
If the connection wasn't made from within the firewall, bmuid is more than likely not running. Use the ps command to look for a process named "bmuid" to see if the daemon is running.
Repeat the test from outside your firewall. If the connection failed then you need to allow port 5023 access in your firewall rules.
Connection to the server, but failure:
Ensure that both the bmui.cgi and bmuid are at the correct level. bmui.cgi and bmuid are not backward compatible with prior versions (e.g., 1.5.4 client will not work with a 2.0.0 and vice versa).
Check that bmui.config has been generated since the last changes to the ciparms list and that the new file has been copied to the appropriate location.
Check the settings for cgihtml, cgiimages and cgipath in the ciparms list. Check that bmui.config has been generated since the last changes to the ciparms list and that the new file has been copied to the appropriate location.
Ensure that there is data for every POP and parameter listed in the POP_FIELDS form variable. Also, check the DATA TO POP filter settings. At least one POP must be found, otherwise an error results.
See the section called “Configuring Customer Registration Services”
|
|
 |
|
| Advanced CI topics |  |
CI Client/Server Protocol |