Before you run the FSS sample application, you must satisfy the following requirements:
The web server where the Web Agent is installed does not require an SSL port.
Important! Core SiteMinder must function properly to run the sample application successfully.
Important! If you initialize a new policy store, the Policy Server installer automatically imports the affiliate objects contained in the ampolicy.smdif file. These objects are necessary for federation. If you use an existing policy store that you do not initialize, import the affiliate objects manually. To verify that the import is successful, log in to the FSS Administrative UI and click on Domains in the System tab. If the import is successful, you can see the FederationWebServices domain object.
For installation instructions, see the Web Agent Option Pack Guide.
Note: SOA Security Manager r12.1 SP3 is shipped with a ServletExec license key file named ServletExec_AS_6_license_key.txt. If you do not have this license key, contact CA Technical Support. From this license file, copy the license key and enter it in the ServletExec License dialog of the ServletExec Administration Console. For instructions on licensing ServletExec, see ServletExec documentation, available at the New Atlanta Communication website.
You do not have to setup the Federation Web Services Application; the sample application does these tasks. However, you do have to deploy Federation Web Services as a ServletExec web application. You deploy a web application using the ServletExec Administration Console.
Note: For instructions on installing ServletExec, setting the license key, and deploying web applications, see New Atlanta Communication ServletExec documentation.
For instructions on configuring a session server, see the SOA Security Manager Policy Server Installation Guide. To point the Policy Server to the session server after you have created it, see the SOA Security Manager DNA Always Current Scheduler.
Note: If you are using two separate systems, install all these components on both systems.
Important! Verify that the Perl binary bundled with the Policy Server is the first or only such binary in the PATH so that the bundled Perl binary is invoked and not another Perl script.
Note: If your Federation Security Services system is communicating with a SiteMinder Federation Endpoint system, see the SiteMinder Federation Endpoint Guide for the additional endpoint requirements.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |