Configuration File Example: Using Logical Names

Logical names provide a mechanism to identify similar functionality. They are specified via the sasLogicalName attribute.

For instance, your installation may want to stage a new application without altering its production applications. To do this, the SAS Object Server definitions specify the same logical name. Here is a configuration file that illustrates how this is accomplished:

#
##  Define our production MyApplication SAS Object Server
#
dn: sasServercn=MyApplication,sascomponent=sasServer,cn=SAS,o=ABC Inc,c=US
objectClass: sasServer
sasServercn: MyApplication
sasDomainName: mvs.abc.com
sasLogicalName: stage
sasMachineDNSName: bigiron.mvs.abc.com
sasProtocol: com

#
##  Define our test MyApplication SAS Object Server
#
dn: sasServercn=testApplication,sascomponent=sasServer,cn=SAS,o=ABC Inc,c=US
objectClass: sasServer
sasServercn: testApplication
sasDomainName: mvs.abc.com
sasLogicalName: stage
sasMachineDNSName: bigiron2.mvs.abc.com
sasProtocol: com