OIF EMAGENT error Startup of UPLOAD MANAGER failure (00722)

emagent.log
===========
  Thread-1 Starting Agent 10.2.0.5.0 from /opt/oracle/Middleware2/Oracle_IDM1 (00701)
  Thread-1 <Agent Startup> : Startup of UPLOAD MANAGER failure (00722)




emagentfetchlet.log
================
  [nmefmgr_getJNIFetchlet] WARN emd.fetchlets getMetric.387 - oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
at oracle.sysman.emd.fetchlets.JMX.JMXFetchletWrapperBase.getMetric(JMXFetchletWrapperBase.java:96)
at oracle.sysman.emd.fetchlets.FetchletWrapper.getMetric(FetchletWrapper.java:382)




emagent.trc
=========
Thread-1 WARN upload: Upload manager has no Failure script: disabled
Thread-1 WARN main: failed to start upload manager, disabled


Solution:
your EMAGENT password is not correct. you can update EMAGENT password thru EM console by following.


1. Login to EM console
2. Navigate to Farm-->Agent-Monitored Targets
3. Click Configure for OIF.
4. Update "WebLogic Monitoring Password" with existing password.
5. Restart the OIF and EMAGENT services.

OIF, updating EMAGENT password thru EM console

1. Login to EM console
2. Navigate to Farm-->Agent-Monitored Targets
3. Click Configure for OIF.
4. Update "WebLogic Monitoring Password" with existing password.
5. Restart the OIF and EMAGENT services.

OIF metadata configuration file cot.xml

$DOMAIN_HOME/config/fmwconfig/servers/<OIF_SERVER_NAME>/applications/OIF_11.1.1.2.0/configuration/*.xml files (the federated partner data is stored in the cot.xml file) prior to loading the new metadata


when you are planning to upload medata and want to have backup of existing metadata you can either backup cot.xml or i prefer to backup whole "config" directory.

weblogic enable debugging thru console

1. Servers--> select the managed server--> Debug tab --> Expand Weblogic by clicking the "+" Expand Security by clicking the "+" Check the boxes next to atn and atz. Click the "Enable" button.

2. Before activating the changes Please click the Logging tab. Click Advanced In the first drop-down box (Severity Level) ensure this is set to "Debug" You do not need to restart the server for the changes to take effect. Just save the changes.

OHS-9999 VirtualHost: main] (13)Permission denied: make_soc k: could not bind to address :80

[OHS-9999] [worker.c] [host_id: orasystems] [host_ad
 [tid: 1] [user: shahbaz] [VirtualHost: main] (13)Permission denied:  make_soc
k: could not bind to address  80


solution:
go to ohs home <>/ohs/bin

ls -altr

find file .apachectl (make sure it have "." dont make changes to apachectl file

run below commands

chown root .apachectl

 chmod 6750 .apachectl

now restart ohs  with the user who owns the OHS installation, the reason is any port that is below 1024 can only be started by root. my this ohs have port 80 that's why regular user was unable to start it.

oif opensaml::FatalProfileException Assertion contains upaccepitable AudianceRestraction

oif 10g error opensaml::FatalProfileException Assertion contains upaccepitable AudianceRestraction


Solution:
this error happened due to mistakes at url.
check OIF and adminserver logs you will see clear message. some times you are trying with wrong ProviderId. correct providerID and try again.

symbolic link soalris link unlink and remove command

desktop:~$ mkdir mydir
desktop:~$ ln -s mydir  mylink
desktop:~$ ls -l mylink
lrwxrwxrwx 1 oracle oracle 3 2016-04-06 14:00 mylink -> mydir
desktop:~$ rm mylink
desktop:~$ ls -l mylink
ls: cannot access mylink: No such file or directory
desktop:~$ ls -l mydir
total 0
desktop:~$

to unlink link:

unlink linkname

to remove link:

rm linkname