Editing the Configuration File for Your Site

Before invoking the Broker, you must customize the configuration file to define your Application Servers as available services.

This page explains the changes you must make to customize the configuration file for your site. However, there are additional changes you can make. For complete details, see Creating Your Own Configuration File.

1. Open the Broker configuration file (broker.cfg) that you installed as part of the Broker installation.

   Note: Each statement in the file is referred to as a directive.

2. Define the administrator's name and e-mail address using the Administrator and AdministratorMail directives. This name and e-mail address appears in error messages so that users of the system know who to call if they have questions. Enter your name and address here inside the double quotation marks.

3. Go to the section in the configuration file that starts with SocketService default. Think of a service as a kind of nickname for your Application Server. Replace the ID, name, server, and port information in the template with values that are correct for your site. The ID is completely up to you, but we recommend you define at least one service with an ID of default that can be used when a specialized server is not needed. There is nothing special about the name default; it is simply a convention you can use at your site.

   Fill in the machine name (DNS name) of the SAS server and its port number using the server and port directives. If your SAS server and your Web server are on the same machine, you can specify localhost for the server directive.

   If you installed using the Windows install program, use the default port number provided in the Broker configuration file. Otherwise, use the port number you specified when you started the Application Server.

4. The next section in the configuration file starts with LaunchService newsas. Edit the ID, name, path to SAS software (SASBin), SAS options, and the AF command, as needed for your site. When defining SASBin for Windows systems, include the .exe extension in the SAS executable and specify paths using the double back slashes as shown in the Windows configuration file template.

5. You can also set the administrator's name and address for a particular service to be a different person than the global administrator set in the configuration file. This is helpful when your site has many services supported by different administrators.

6. Save and close the configuration file.

7. You now have both pieces of the Application Dispatcher installed. Proceed to Testing the Installation.