Installation and Upgrade Guides › Policy Server Installation Guide › Installing the Policy Server on Windows Systems › How to Install the Policy Server on Windows › Configure the SNMP Agent on Windows › How to Configure SNMP Event Trapping on Windows

How to Configure SNMP Event Trapping on Windows

Configuring SNMP event trapping on Windows requires you to:

1. Enable SNMP event trapping.
2. Configure snmptrap.config.

Enable SNMP Event Trapping

To enable SNMP event trapping, use the XPSConfig utility to set the event handler library (eventsnmp.dll) to the XPSAudit list. The default location of eventsnmp.dll is policy_server_home\bin.

policy_server_home

Specifies the Policy Server installation location.

Note: More information on using the XPSConfig utility to set event handler libraries exists in the Policy Server Administration Guide.

After enabling SNMP event trapping, configure the snmptrap.conf file.

Configure snmptrap.conf

To configure the SNMP configuration file

1. Edit snmptrap.conf.

   Note: snmptrap.conf is located in policy_server_home\config.

   policy_server_home

   Specifies the Policy Server installation location.

2. For the specified trap(s) that you want to receive, uncomment out the appropriate line(s).
3. Specify the IP Address, port number, and community for where you want the trap to be sent.
4. Save the snmptrap.config file with the new changes.
5. Restart the Policy Server.

More Information:

Stop and Restart the Policy Server

Gather Information for the Installer

The Policy Server installer requires specific information to install the Policy Server and any optional components.

Required Information

Gather the following required information before running the Policy Server installer or the Configuration wizard.

• Java version ‑ Identify the supported Java Runtime Environment version for the Policy Server to use. On UNIX, verify that the JAVA_HOME system variable is set to the location of the JRE. The installer cannot locate the JRE if the JAVA_HOME system variable is incorrectly set.
• Policy Server installation location ‑ Determine where the installer is to install the Policy Server.

  Default: C:\Program Files\CA

• SiteMinder Encryption key value ‑ Determine the encryption key value. An encryption key is a case–sensitive, alphanumeric key that secures the data sent between the Policy Server and the policy store. All Policy Servers that share a policy store are required to use the same encryption key. For stronger protection, define a long encryption key.

  Limits: 6 to 24 characters.

More information:

Required Information Worksheet

Active Directory LDS Server Information

Gather the following required information to configure Microsoft Active Directory LDS as a policy store:

• System IP address—Identify the IP address of the directory server host system.
• Port number—Identify the port number on which the directory server is listening.
• Root DN of the application partition—Identify the root DN location of the application partition in the directory server where the policy store schema data must be installed.

  Example: dc=ca,dc=com

• Administrator domain name—Identify the full domain name, including the guid value, of the directory administrator.

  Example: CN=user1,CN=people,CN=Configuration,CN=guid

• Administrator password—Identify the password of the directory administrator.
• Alternate user account—By default, SiteMinder uses the administrator account to communicate with the directory server. However, you can use a different user account to administer the policy store. Identify the complete administrator DN and password to configure SiteMinder to use an alternative user account to administer the policy store.

  Note: This user must have the necessary permissions to modify attributes and change passwords.

• SiteMinder superuser password—The default SiteMinder superuser account has maximum permissions. Determine the password for the default superuser account. The name of the default account is:

  siteminder
  

  Limits:

  • The password must contain at least six (6) characters and cannot exceed 24 characters.
  • The password cannot include an ampersand (&) or an asterisk (*).
  • If the password contains a space, enclose the passphrase with quotation marks.

  Note: We recommend that you do not use the default superuser for day-to-day operations. Rather, use the default superuser to access the Administrative UI for the first–time and then create an administrator with superuser permissions.

Oracle Directory Server Information

Gather the following required information to configure Oracle Directory Server to function as a policy store:

• System IP address—Determine the IP address of the Oracle Directory Server host system.
• Directory instance port number—Determine the port number for the Oracle Directory Server instance.

  Default: 389

• Root DN—Identify the root DN of the Oracle Directory Server.

  Example: o=yourorg.com

• Administrator account—Identify the user name (Bind DN) for the LDAP administrator account.

  Example: cn=Directory Manager

• Administrator password—Identify the password for the Oracle Directory Server administrator.
• Alternate LDAP administrator—By default, SiteMinder uses the LDAP administrator account to communicate with the LDAP server. However, you can use a different LDAP user account to administer the policy store. Identify the complete administrator DN and password to configure SiteMinder in this way.

  Note: This user must have the necessary permissions to modify attributes and change passwords.

• SiteMinder superuser password—The default SiteMinder superuser account has maximum permissions. Determine the password for the default superuser account. The name of the default account is:

  siteminder
  

  Limits:

  • The password must contain at least six (6) characters and cannot exceed 24 characters.
  • The password cannot include an ampersand (&) or an asterisk (*).
  • If the password contains a space, enclose the passphrase with quotation marks.

  Note: We recommend that you do not use the default superuser for day-to-day operations. Rather, use the default superuser to access the Administrative UI for the first–time and then create an administrator with superuser permissions.

More information:

Oracle Directory Server Enterprise Edition Information Worksheet

Microsoft SQL Server Information

To configure Microsoft SQL Server as a policy store, gather the following required information:

Database server name

Identify the IP address or name of the database host system.

Note: For more information about IPv6 support, see the SiteMinder Platform Support Matrix.

Database name

Identify the named instance or the name of the database that is to function as the policy store.

Database port

Identify the port on which the database is listening.

Database administrator user name and password

Identify the name and password of an administrator account with permission to do the following operations:

• Create schema
• Create, read, modify, and delete objects.

Note: If the SiteMinder schema is already present in the database, the wizard does not require the credentials of a database administrator with create permission. For more information, see Configure a SQL Server Policy Store.

SiteMinder superuser password

The default SiteMinder superuser account has maximum permissions. Determine the password for the default superuser account. The name of the default account is:

siteminder

Limits:

• The password must contain at least six (6) characters and cannot exceed 24 characters.
• The password cannot include an ampersand (&) or an asterisk (*).
• If the password contains a space, enclose the passphrase with quotation marks.

Note: We recommend that you do not use the default superuser for day-to-day operations. Rather, use the default superuser to access the Administrative UI for the first–time and then create an administrator with superuser permissions.

More information:

SQL Server Information Worksheet

Oracle RDBMS Information

Gather the following required information to configure Oracle RDBMS as a policy store.

Database server name

Identify the IP address or the name of the database host system.

Note: For more information about IPv6 support, see the SiteMinder Platform Support Matrix.

Database service name

Identify the service name of the database that is to function as the policy store.

Database port

Identify the port on which the database is listening.

Database administrator user name

Identify the name of an administrator account with permission to do the following operations:

• Create schema
• Create, read, modify, and delete objects.

Database administrator password

Identify the password of the administrator account.

SiteMinder superuser password

The default SiteMinder superuser account has maximum permissions. Determine the password for the default superuser account. The name of the default account is:

siteminder

Limits:

• The password must contain at least six (6) characters and cannot exceed 24 characters.
• The password cannot include an ampersand (&) or an asterisk (*).
• If the password contains a space, enclose the passphrase with quotation marks.

Note: We recommend that you do not use the default superuser for day-to-day operations. Rather, use the default superuser to access the Administrative UI for the first–time and then create an administrator with superuser permissions.

More information:

Oracle RDBMS Worksheet

OneView Monitor Information

You only have to gather OneView Monitor information if you plan on configuring the OneView Monitor.

Gather the following required information to configure the OneView Monitor. You can use the OneView Monitor Information Worksheet to record your values.

• JDK path—Identify the path to the required JDK version.
• ServletExec installation directory—Identify ServletExec installation directory.

  Example: /usr/local/NewAtlanta/ServletExecAS

• ServletExec port number—Determine the port number for the ServletExec instance.
• Sun Java System administrator directory—Determine the following information:
  • The installed location of the Sun Java System.
  • The installed location of the Sun Java System Web servers.

  Example: /sunjavasystem_home/location

  sunjavasystem home

  Specifies the installed location of the Sun Java System.

  location

  Specifies the installed location of the Sun Java System Web servers.

• Multiple ServletExec instances—If you have multiple ServletExec instances, determine the instance to which you want to configure the OneView Monitor GUI.

More information:

OneView Monitor Information Worksheet

Run the Policy Server Installer

You install the Policy Server using the installation media on the Technical Support site.

Note: For a list of installation media names, see the Policy Server Release Notes.

Follow these steps:

1. Be sure that the system meets the windows requirements.
2. Exit all applications that are running.
3. Do the step appropriate for your version of Windows:
   • Windows 2008 and Windows 7: Right-click installation_media and select Run as administrator.
   • Other Windows versions: Double–click installation_media.

     installation_media

     Specifies the name of the Policy Server installation executable.

   The installer starts.

4. Use the gathered system and component information to install the Policy Server and configure Policy Server components. Considering the following items when running the installer:
   • You are prompted to select a FIPS mode of operation. For more information about which FIPS mode to select, see FIPS Considerations.
   • When the installer prompts you to select components, clear the Policy Store check box if you are not configuring a policy store automatically. For more information about which stores can be automatically configured as a policy store, see Policy Store Considerations.
   • If you are initializing a policy store, you are prompted to enter a password for the default SiteMinder user account. The default account name is

     siteminder
     

   • You are prompted to install the default certificate authority certificates to the certificate data store. You can add additional certificates and private keys to the certificate data store after installation.
   • If you are using IPv6 addresses, surround entries with brackets.

     Example: [2001:db8::1428:57ab]

5. Review the installation settings and click Install.

   The Policy Server and all selected components are installed and configured.

6. (Optional) If you did not use the installer to configure a policy store, manually configure the policy store.

Note: If you experience problems during the installation, you can locate the installation log file and the policy store details file in siteminder_home\siteminder\install_config_info.

siteminder_home

Specifies the Policy Server installation path.

More information:

Locate the Installation Media

Installation Media Names