Configuration File Examples: Server and Spawner

Here is a sample configuration file that defines a spawner named Simple, which services one object server named SimpleServer:

#
##  Define a Simple spawner to run on our
##  localhost machine.
#
dn: sasSpawnercn=Simple
objectClass: sasSpawner
sasMachineDNSName: localhost
sasSpawnercn: Simple
sasOperatorPort: 5306
description: Example spawner executing on our localhost machine

#
##  SimpleServer only handles clear text connections
#
dn: sasServercn=SimpleServer
objectClass: sasServer
sasServercn: SimpleServer
sasCommand: /sasv9/usrlibsas/sas
sasMachineDNSName: localhost
sasPort: 5307
sasProtocol: bridge
description: Example server that does not handle encrypted connections

Here is a sample configuration file that defines a spawner named Example that services two object servers; ExampleServer1 and ExampleServer2:

#
##  Define the Example spawner to run on our
##  demo machine.
#
dn: sasSpawnercn=Example
objectClass: sasSpawner
sasMachineDNSName: demo.unx.abc.com
sasSpawnercn: Example
sasOperatorPort: 5306
description: Example spawner executing on our demo machine

#
##  ExampleServer1 handles encrypted connections
#
dn: sasServercn=ExampleServer1
objectClass: sasServer
sasServercn: ExampleServer1
sasCommand: /sasv9/usrlibsas/sas
sasMachineDNSName: demo.unx.abc.com
sasNetEncrAlg: sasproprietary
sasNetEncrAlg: des
sasNetEncrAlg: tripledes
sasNetEncrAlg: rc2
sasNetEncrAlg: rc4
sasPort: 5307
sasProtocol: bridge
# Don't require encryption
sasRequiredEncryptionLevel: none
description: Example server that handles encrypted connections

#
##  ExampleServer2 only handles clear text connections
#
dn: sasServercn=ExampleServer2
objectClass: sasServer
sasServercn: ExampleServer2
sasCommand: /sasv9/usrlibsas/sas
sasMachineDNSName: demo.unx.abc.com
sasPort: 5308
sasProtocol: bridge
description: Example server that does not handle encrypted connections

The example above illustrates these points:

• Comments are ignored. Therefore, they do not affect processing that is associated with empty lines.

• The distinguished name attribute, preceded by a blank line, identifies the beginning of the next object definition.