OAM 11.1.2.3 New installation - There was issue in deployment on oam_server1 managed server which was in failed state.

  • Installed and configured OAM. However the oam_server (11.1.2.0.0) and oam_policy_mgr (11.1.2.0.0) application failed to deploy even though the OAM and policy server is up and running. 



Soution:



1. Shut down the entire domain, including the WebLogic Admin Server and all OAM Managed Servers
2. Locate the correct "oam-config.xml" file. This will be located on the Admin Server node in the following location: <DOMAIN_HOME>/config/fmwconfig/oam-config.xml
3. Make a backup of the existing file prior to editing
4. Make the required change...

Update the parameter "SetWellKnownAddress" by setting the value from TRUE to FALSE
Update the Socket Buffer Size by following the instructions (May need the help of your OS/System Admin)
5. Locate the version number and increment the value by 1. The following snippet is from the oam-config.xml file. The version number will occur near the top of the file.

<Setting xmlns="http://www.w3.org/2001/XMLSchema" Name="NGAMConfiguration" Type="htf:map">
...
<Setting Name="Version" Type="xsd:integer">175</Setting>
Using this as an example, increment the number from "175" to "176" prior to saving oam-config.xml. 
6. Save the changes 
7. Restart the WebLogic Admin Server, followed by the OAM Managed Servers. 
8. If applicable, as a verification step, check <DOMAIN_HOME>/config/fmwconfig/oam-config.xml on each of the OAM Managed Server nodes to ensure that the updated version has propagated correctly.


Courtesy: Oracle Access Manager (OAM 11g) oam_server and oam_policy_mgr Receive Error "Application Failed to Deploy" (Doc ID 2133259.1)

Comments

Post a Comment

Popular posts from this blog

ORA-46697: Keystore password required - create pluggable database pdb1clone from pdb1

  select con_id,name,open_mode from v$pdbs;     CON_ID NAME     OPEN_MODE ---------- -------------------------------------------------------------------------------------------------------------------------------- ---------- 2 PDB$SEED     READ ONLY 3 PDB1     READ WRITE SQL> create pluggable database pdb1clone from pdb1; create pluggable database pdb1clone from pdb1 * ERROR at line 1: ORA-46697: Keystore password required. Solution: If  TDE is configured, you have to supply the keystore password  SQL> CREATE PLUGGABLE DATABASE PDB1clone FROM PDB1  KEYSTORE IDENTIFIED BY password;
Read more

OAM 11.1.2.3 - Bad Oracle Access Manager Request Error After Applying OAM Patch 27373151 + Webgate Patch 27393427 BP 11.1.2.3.180717

After Applying OAM Patch 27373151 + Webgate Patch 27393427 BP 11.1.2.3.180717, when accessing the http resource then it was giving Bad Oracle Access Manager Like when accessing "http://hostname.domain:7779/index.html" we get following message in the logfile "diagnostics/logs/OHS/ohs1/oblog.log" 2018/10/26@15:29:46.68427       1890    1950    WEB     ERROR   0x0000151F      /ade/aime_ngamac_748106/ngamac/src/palantir/commonlib/src/apache2_req_info.cpp:294     ecid^005UIDZfNp87U8ups^h8iX0000SX00001w  rid^0   "WebGate Error Report"  Message^Unable to process the request due to unexpected error.  ReqReq^GET /public/index.html HTTP/1.1  ReqProto^HTTP/1.1       ReqHost^bdrvl-pd-oid01  ReqStatLine^    ReqStatus^200   ReqRawUri^/public/index.html    ReqUri^/public/index.html       ReqFilename^...
Read more