The Platform Receiver obtains provisioning events from Event Journal Services and calls the appropriate Receiver script to process the given type of event. For more information about Receiver scripts, see Receiver Scripts.
The Platform Receiver must be running if you plan to use Identity Provisioning on the platform.
Set up routine operation of the i5/OS Platform Receiver using Persistent Mode or Polling Mode, in a subsystem as an autostart entry. For information, see Section 8.8.1, Modes of Operation.
To start and stop the Platform Receiver, execute GO ASAM to load the ASAM menu, and select the desired option. The ASAM library must be in your library list.
To start the Platform Receiver at the command line, enter ASAMRCVR, specifying command line parameters as appropriate. The ASAM library must be in your library list.
Table 12-1 Platform Receiver Command Line Parameters
The MODE option determines the mode of operation for the Platform Receiver. If this option is not specified, the mode of operation specified by the RUNMODE statement in the platform configuration file is used. If there is no RUNMODE statement, the Platform Receiver uses Persistent Mode.
For details about the Platform Receiver modes of operation, see Section 8.8.1, Modes of Operation.
Maintenance involves four types of files.
The i5/OS Platform Receiver uses the Attribute Name Mapping file to convert attribute names obtained from Event Journal Services to Profile and System Distribution Directory field names for use by the Receiver scripts. The attribute names used by Event Journal Services are the names that appear in the Identity Manager Subscriber filter.
The Attribute Name Mapping file is /usr/local/ASAM/data/attrmap.conf.
Each line of the file contains the name of an attribute received from Event Journal Services, a comma, and the name to which the attribute is to be mapped for use by Receiver scripts.
Any line in the file beginning with an octothorpe (#) is a comment. Blank lines are ignored.
For more information about provisioning attributes to your platform, see Section A.0, OS/400 Provisioning Tips.
The Platform Receiver reads the platform configuration file to locate the Core Driver, to determine which users and groups are managed using provisioning events, and to find other configuration information. For more information, see Section 10.0, The Platform Configuration File.
Receiver scripts for i5/OS platforms are implemented as Control Language (CL) programs. The Platform Receiver runs the Receiver scripts from the ASAM library. The source code for the Receiver scripts is stored in the SCRIPTS file in the ASAM library. Several varieties of Receiver scripts are placed in subdirectories of asam/bin/platformservices/platformreceiver/scripts by the installation process.
The i5/OS Platform Receiver writes messages to standard i5/OS joblogs. Use DSPJOBLOG or iSeries* Navigator to view these logs. Log messages are documented in the Messages Reference.