Symantec Access Management

  • 1.  Policy Store Failover using ODBC

    Posted Sep 09, 2015 10:59 PM

    How to configure SiteMinder (CA SSO) to support fail-over for policy store using ODBC? 

     

    We are using Oracle DB as Policy store and when we configured Policy Store database using Management console using ODBC ; the console only allows us to enter 1 DSN.



  • 2.  Re: Policy Store Failover using ODBC
    Best Answer

    Posted Sep 10, 2015 02:18 AM

    Hello,

     

    You could check the following documentation;

     

    https://support.ca.com/cadocs/0/CA%20SiteMinder%2012%2052%20SP1-ENU/Bookshelf_Files/HTML/idocs/360332.html#o238505

     

    Configure ODBC Failover

    If you have multiple ODBC data sources and you want to configure failover, list the data source names in the Data Source Information field, separated by commas. For example, entering CA SiteMinder® Data Source1,CA SiteMinder® Data Source2 causes the Policy Server to look at Data Source 1 first. If CA SiteMinder® Data Source1 does not respond, the Policy Server automatically looks for CA SiteMinder® Data Source2.

    Note: Using the method described above, you can configure failover for data sources used as policy stores, key stores, session stores, and audit logs.

     

    Julien.



  • 3.  Re: Policy Store Failover using ODBC

    Broadcom Employee
    Posted Sep 10, 2015 02:43 AM

    Hi,

     

    You can also configure 1 DNS to have the

    failover with the AlternateServer configuration.

    Here's a sample of failover configuration

    with Oracle :

     

    [SiteMinder Oracle Data Source]

    Driver=/opt/CA/siteminder/odbc/lib/NSora23.so

    Description=DataDirect 5.3 Oracle Wire Protocol

    HostName=data1.training.com

    PortNumber=1521

    ServiceName=myodbc1

    AlternateServers=(Hostname=data2.training.com:PortNumber=1521:ServiceName=myodbc1)

    LoadBalancing=1

    CatalogOptions=0

    ProcedureRetResults=0

    EnableDescribeParam=0

    EnableStaticCursorsForLongData=0

    ApplicationUsingThreads=1

    ConnectionRetryDelay=5

    ConnectionRetryCount=5

     

    Best Regards,

    Patrick