Installing and Setting Up Bolero

Stage 5-Minimal Configuration of the Bolero Settings File

This section describes the initial modifications you must make to the Settings file so that Bolero can begin logging information. Other modifications can be made to this file after Bolero has been launched; these modifications are described for you in the Additional Configuration of the Bolero Settings File section (under the Using Bolero chapter).

Many aspects of Bolero's operation, including the information it logs, and when it reports information, are controlled through the Bolero Settings file, which is found in the Bolero application folder. To modify this file, use SimpleText or another text editor.

You need to have Butler SQL, Tango, and Bolero installed before doing this configuration, and must have set up your ODBC data source called 'Bolero'.

You can click on the headings below to go directly to those sections.

Setting Up Access to the Data Source
Identifying the Web Servers
Setting Up Web Server Logging

Setting up Access to the Data Source

In the Data Source subsection of the Settings File, you need to enter a username and password that will provide access to the Bolero database If access privileges have been enabled on the Butler SQL server, this name and password must belong to a valid Butler SQL user.

If you are not using Butler SQL's access privileges, you should still enter a username in the Settings file, as this name is used to identify Bolero activity on the Butler SQL server. See your Butler SQL documentation for details).

The Data Source information in the default Bolero Settings file looks like this:
[DataSource]
Type = ODBC
DSN = Bolero
Username =
Password =
Enter a username and password for your server that will provide access to the Bolero database.

For example:
[DataSource]
Type = ODBC
DSN = Bolero
Username = BoleroServer
Password = webstats

Identifying the Web Servers


For each Web server to be accessible by Bolero, you must edit the Web Servers subsection of the Bolero Settings file to identify:
The default Settings file identifies two example Web servers:
[www.myserver1.com]
DomainName = www.myserver1.com
IPAddress = 255.255.255.255
Type = WebSTAR
Zone = ServerLand
Machine = My Server 1
Program = WebSTAR 1.2.4
Timeout = 300

[www.myserver2.com]
DomainName = www.myserver2.com
IPAddress = 255.255.255.255
Type = WebSTAR
Zone = ServerLand
Machine = My Server 2
Program = WebSTAR
Timeout = 600

Note


If you only have one Web server, you can delete the second server example provided in the Web Servers subsection of the Settings File. You can also add more Web server entries if necessary.

Be sure that you do not create more than one Web server with the same name in the Web Server Logging or Web Servers subsections. Bolero reads the entry in the Web Server Logging subsection, then finds the name of that server in the Web Server subsection. If two servers are named the same, Bolero only finds the first entry in the Web Servers subsection.
Using the previous example, if:
the following entry to the WebServers subsection of the Bolero Settings file must be made:
[www.everyware.com]
DomainName = www.everyware.com
IPAddress = 255.255.255.255
Type = WebSTAR
Zone = ServerLand
Machine = EveryWare Web Server
Program = WebSTAR 1.2.4
Timeout = 300

Note


Filling in the domain name and IP Address is optional. This field will default to the name specified between [brackets] if the domain name is not entered. You may need these two items to be different if your site consists of a RAIC (Redundant Array of Inexpensive Computers), where each machine must be identified uniquely (the name that appears between the [ ]), yet they all share the same domain name.

Server Reconnections and Timeouts


The WebSTAR server broadcasts a null Apple Event every 15 to 30 seconds. Bolero uses this event as a 'heartbeat' to monitor the active status, or presence, of each Web server on the network.

If Bolero does not receive a 'heartbeat' from a Web server within a specified period of time, it will try to reconnect to the Web server. The time that elapses between the last 'heartbeat' received and an attempt to reconnect is the 'timeout' value. The value is entered as seconds (for example, a timeout value of 300 equals five minutes). Valid values are 60 and up. A value of -1 means there will not be an attempt to reconnect.

Setting Up Web Server Logging

The Web Server Logging section lists all the Web servers identified in the WebServers subsection that will or will not be logged by Bolero. The on/off setting allows you to maintain a list of all your Web servers in the Bolero Settings file and selectively enable or disable logging of each server without having to delete and later retype the information.

The Web Server Logging subsection of the default Settings file contains one entry for each server listed in the Web Servers subsection:
[WebServerLogging]
www.myserver1.com = Off
www.myserver2.com = Off
myserver1.historical = Off
myserver2.historical = Off
You need to replace these sample Web server names with the names of the servers you identified in the Web Servers subsection. For each Web server, indicate if logging is initially enabled or disabled. For instance, if you wish to log a Web server named 'www.everyware.com', replace the sample information with:
[WebServerLogging]
www.everyware.com = on

Note


This Web server information must be set up before attempting to launch Bolero and start the logging process.

Go to Stage 6 to launch Bolero.

Click here to return to the main Installing and Setting Up page.

Home Page - Reports