Fanout Configuration File Location#
You can use a command line parameter to specify the configuration file to be used. If not specified, the following are the default Fanout Configuration File Location.Fanout Configuration File Statements#
Statements and syntax for the configuration files.My Configuration File for Unix#
AUTHENTICATION 192.168.1.4 PORT 3451 PROVISIONING 192.168.1.4 PORT 3451 PASSWORDPROMPT "eDir Password: " PASSWORDPROMPTCURRENT "Current eDir Password: " PASSWORDPROMPTCHANGE "New eDir Password: " PASSWORDPROMPTCHANGEAGAIN "Re-enter New eDir Password: " DEBUGLOGFILE /usr/local/ASAM/data/plat.log DEBUGTOSTDOUT *
Sample Platform Configuration File#
# Sample Platform Configuration File # # This is a sample platform configuration file. You can use it as a # guide in preparing your own configuration file. # # This file is used by Platform Services components. You can use a # command line parameter to specify the configuration file to be used. # The defaults are as follows: # MVS ASCLIENT: Member ASCPRM00 in the PDS at ddname ASCPARMS # MVS PLATRCVR: Sequential file at ddname ASAMCONF # NetWare: sys:asam\data\asamplat.conf # OS/400 /usr/local/ASAM/data/asamplat.conf # UNIX: /usr/local/ASAM/data/asamplat.conf # Windows: c:\novell\asam\data\asamplat.conf # # Parameter values that contain spaces must be quoted. For example: # PASSWORDPROMPT "Password: " # Do not quote other values. # # Lines that begin with an octothorpe (#) are comments. # # This example file lists some of the most common statements. For complete # details about the platform configuration file, see the Platform Services # Planning Guide and Reference. # # # Sample Configuration Statements # # AUTHENTICATION coredriver1.company.org PORT 3451 # AUTHENTICATION coredriver2.company.org PORT 3451 # AUTHENTICATION coredriver3.company.org PORT 5009 PREF 2 # The AUTHENTICATION statement specifies the network address of a core driver. # The network address can be a DNS name or an IP address. At least one # AUTHENTICATION statement must appear in the platform configuration file of # the Platform Services Process. The optional PORT parameter specifies # the TCP port number to be used. The optional PREF parameter specifies # the core driver selection preference. # # AM.GROUP.INCLUDE * # AM.GROUP.EXCLUDE sys*, marketing # The AM.GROUP.INCLUDE and AM.GROUP.EXCLUDE statements determine which # groups are managed by provisioning events. The default is to # include all groups except those in the standard exclude list. # # AM.USER.INCLUDE * # AM.USER.EXCLUDE eng*, boss27 # The AM.USER.INCLUDE and AM.USER.EXCLUDE statements determine which # users are managed by provisioning events. The default is to # include all users except those in the standard exclude list. # # AS.USER.INCLUDE * # AS.USER.EXCLUDE eng*, local01 # The AS.USER.INCLUDE and AS.USER.EXCLUDE statements determine which # users are authenticated using Authentication Services. The default # is to include all users except except those in the standard exclude list. # # IGNORESTANDARDEXCLUDES # The IGNORESTANDARDEXCLUDES statement specifies that the list of standard # excluded users and groups is ignored for this system. The default is # to exclude all users and groups that are defined in the standard exclude list # from being managed or authenticated. For a list of the standard excluded # users and groups, see the Platform Services Planning Guide and Reference. # # DIRECTTOAUTHENTICATION # The DIRECTTOAUTHENTICATION statement causes Authentication Services to # connect directly to core drivers without using the Platform Services # Process. # # ENTROPY /etc/entropy # The ENTROPY statement specifies where components on UNIX systems obtain # entropy for SSL. It is not used on other systems. The default is to use # the /dev/random device. # # PROVISIONING asammgr.company.org PORT 3451 # The PROVISIONING statement specifies the network address of a Provisioning # Manager core driver. The network address can be a DNS name or an IP address. # At least one PROVISIONING statement must appear in the Platform Configuration # file of the Platform Receiver and when obtaining a security certificate. The # optional PORT parameter specifies the TCP port number to be used. # # RUNMODE polling # The RUNMODE statement specifies the Platform Receiver mode of operation. # Valid values are PERSISTENT, POLLING, and SCHEDULED. # In Persistent Mode, the Platform Receiver keeps a persistent socket # connection to the Provisioning Manager in order to receive events in real time. # In Polling Mode, the Platform Receiver establishes a new connection # to the Provisioning Manager every five minutes to receive any new events. # Scheduled Mode is intended for use with external job schedulers, such # as the UNIX cron utility. In Scheduled Mode, the Platform Receiver # connects to the Provisioning Manager and receives any new events. In Scheduled # Mode, the Platform Receiver ends after all new events have been # processed. The default mode is PERSISTENT.
