Recently I had worked on a requirement where OAM 11g configurations has to be exported and imported from one environment to the other without using any of the UI consoles. This is case of migration but the execution is entirely different compared to Oracle Documentation (supported procedure). I’ll explain the complete steps of export and import in a different post but for now I’d like to brief how OAM configurations such as Authentication Module can be created in OAM 11g without using Admin console. It is assumed that OAM 11g server is setup in Target environment.
In OAM 11g all the configuration details are stored in oam-config.xml located at $WL_DOMAIN/config/fmwconfig. Please note that it is neither recommended nor supported to edit this file.
<Setting Name=”staticMemberDNAttribute” Type=”xsd:string“>uniqueMember</Setting>
<Setting Name=”connectionPool” Type=”xsd:string“>100</Setting>
<Setting Name=”VALIDATE_PASSWORD” Type=”xsd:boolean“>false</Setting>
<Setting Name=”ldapProtocol” Type=”xsd:string“>sslv3</Setting>
<Setting Name=”jaasControlFlag” Type=”xsd:string“>SUFFICIENT</Setting>
<Setting Name=”domainCredential” Type=”xsd:string“>test-credential</Setting>
<Setting Name=”domainName” Type=”xsd:string“>my-domain</Setting>
<Setting Name=”serverName” Type=”xsd:string“>my-server</Setting>
<Setting Name=”domainRealmName” Type=”xsd:string“>my-realm</Setting>
<Setting Name=”dynamicGroupNameAttribute” Type=”xsd:string“>ou=people,ou=myrealm,dc=base_domain</Setting>
<Setting Name=”dynamicMemberURLAttribute” Type=”xsd:string“>memberURL</Setting>
<Setting Name=”sslEnabled” Type=”xsd:string“>false</Setting>
<Setting Name=”ldapid” Type=”xsd:string“>032E2D6DEBDF1B0786</Setting>
<Setting Name=”rootDirectory” Type=”xsd:string“>.</Setting>
<Setting Name=”name” Type=”xsd:string“>OVDAuthModule</Setting>
<Setting Name=”groupBaseDN” Type=”xsd:string“>ou=groups,ou=myrealm,dc=base_domain</Setting>
<Setting Name=”dynamicGroupObjectClass” Type=”xsd:string“>groupofURLs</Setting>
</Setting>
We’re done. No other parameter values need to be specified here. Start the weblogic and OAM servers and login to OAM console to see if the new authentication module is created succesfully.