Deployment Example 1: Access Manager 7.1 Load Balancing, Distributed Authentication UI, and Session Failover

ProcedureTo Edit the J2EE Policy Agent 1 AMAgent.properties File

  1. As a root user, log into the ProtectedResource–1 host machine.

  2. Change to the directory that contains the AMAgent.properties file.


    # cd /export/J2EEPA1/j2ee_agents/am_wl92_agent/agent_001/config
    

    Tip –

    Backup AMAgent.properties before you modify it.


  3. Make the following modifications to AMAgent.properties.

    1. Set the following property.

      com.sun.identity.agents.config.bypass.principal[0] = weblogic

      This ensures that the WebLogic administrator will be authenticated against WebLogic itself and not Access Manager.

    2. At end of the file, insert the following new property.

      com.sun.identity.session.resetLBCookie=true

      You must add this property if session failover has been configured for Access Manager. If session failover is not configured and this property is added, it could negatively impact performance. If session failover is enabled for Access Manager and this property is not added, the session failover functionality will work properly but, the stickiness to the Access Manager server will not be maintained after failover occurs. This property is not required for web policy agents.


      Tip –

      This property must be also be added to the Access Manager file, AMConfig.properties if added here.


  4. Save and close the file.

  5. Log out of the ProtectedResource–1 host machine.