After the initial installation or upgrade of Platform Services, other tasks that you may need to perform from time to time include the following:
If you have chosen to configure for authentication redirection on a platform that is running UNIX, you will need to manually configure PAM on that UNIX system. For technical instructions on how to configure PAM for authentication, see Section B.1, PAM Configuration Notes.
The Platform Services installer automatically copies sample configurations you can use as templates at the following location:
/usr/local/ASAM/PlatformServices/pam.d/
Upon initial deployment of the Fan-Out Driver Platform Services, you may find it useful and necessary to perform an initial migration or synchronization of users and groups within the Identity Vault. You can perform a full synchronization by executing asamrcvrd fullsync. Location of this executable will vary depending on your target platform. See Table 11-3 for the appropriate full command line that includes your directory location.
Table 11-3 Command for Full Synchronization by Platform
Starting Platform Services requires you to start one or more of the following components, depending on your configuration:
Platform Receiver
Platform Services Process
Platform Services Cache Daemon
For more information about these components, see Section 11.1, About Platform Services for Linux and UNIX and Section 12.0, Configuring and Administering Platform Services.
You can start the Platform Receiver by executing asamrcvrd start. Location of this executable will vary depending on your target platform. See Table 11-4 for the appropriate full command line that includes your directory location.
Table 11-4 Command for Starting the Platform Receiver
You can start the Platform Services Process by executing asampspd start. Location of this executable will vary depending on your target platform. See Table 11-5 for the appropriate full command line that includes your directory location.
Table 11-5 Command for Starting the Platform Services Process
You can start the Platform Services Cache Daemon by executing asampsd start. Location of this executable will vary depending on your target platform. See Table 11-6 for the appropriate full command line that includes your directory location.
Stopping Platform Services requires you to start one or more of the following components, depending on your configuration:
Platform Receiver
Platform Services Process
Platform Services Cache Daemon
For more information about these components, see Section 11.1, About Platform Services for Linux and UNIX and Section 12.0, Configuring and Administering Platform Services.
You can stop the Platform Receiver by executing asamrcvrd stop. Location of this executable will vary depending on your target platform. See Table 11-7 for the appropriate full command line that includes your directory location.
Table 11-7 Command for Stopping the Platform Receiver
You can stop the Platform Services Process by executing asampspd stop. Location of this executable will vary depending on your target platform. See Table 11-8 for the appropriate full command line that includes your directory location.
Table 11-8 Command for Stopping the Platform Services Process
You can stop the Platform Services Cache Daemon by executing asampsd stop. Location of this executable will vary depending on your target platform. See Table 11-9 for the appropriate full command line that includes your directory location.
If you are using PAM for password authentication, it may be helpful to verify that the Platform Services Process (asampsp) and the API Library (libascauth) are functioning properly, before you finalize PAM configuration. You can do this with a program called asctest, which is included with your Platform Services installation. Here’s where to find it:
/usr/local/ASAM/bin/PlatformServices/PlatformClient/asctest
This program allows you to test the various calls (listed in Table 11-10) that can be made to the API library in support of PAM. To use asctest, simply enter it from a command line with no parameters. When prompted select the desired method by entering its corresponding letter () and respond to any further prompts. The following table provides descriptions of the API methods.
Table 11-10 API methods used for PAM.