We will now give step-by-step instructions for quickly manually configuring OneGate for use with an application. This assumes that you have OneGate installed, and the global configuration has been performed. The same directory conventions as found in the Configuration Instructions section will be used in this section. Bear in mind that you can also use the ogconfig configuration tool to configure applications, as well as the rest of OneGate. Depending on your preference, this may or may not make things easier/faster.

To configure a new application manually, perform the following steps:

1. Change directory to the [maindir]/configs directory.

2. Decide on a program set name, and make a directory with that name.

3. Change directory into your program set directory.

4. Edit the program.set file, and enter your desired commands for the program set.

5. Edit the fields file, and add all field definitions required for your application.

6. Edit the cookies file, and add all cookie names your application needs to have the data retrieved for. This step is optional.

7. Edit the config file if local application configuration options are necessary. This step is optional.

8. Edit the environment file if you require applications-specific environment variables. This step is optional.

9. Edit the host.allow file and any denial message files as necessary if you require application-level virtual firewalling. This step is optional.

10. Edit the allowed.users file and create valid ht.users, ht.groups, and invalid.user.message files if you require application-level user authentication. This step is optional.

11. Change directory to [maindir].

12. Edit the valid.sets file and add your program set name.

That's it! You should now be ready to test your application, assuming you've configured your application for use with OneGate. The minimal configuration required there is that it write the appropriate response file to the [maindir]/spool/[progset] directory.