specifying JVM file recording path

by default WLS admin server dont have JVM flight recording location, so it create JVM flight recording files at /tmp. you can check this parameter in Admin server JVM instance parameter and you can specify different path at Admin server instance.

in order to enable path you can run following command with parameter (repository=file_location) 

Option:

-XX:FlightRecorderOptions=parameter1=value[,parameter2=value]



Example:
java -XX:+FlightRecorder -XX:FlightRecorderOptions=disk=true,repository=file_location,maxchunksize=10M MyApp

to making this change thru console

make sure to take the backup of config.xml


a.       
Log on to
the weblogic console.

b.      
Go to
managed serverà server start à arguments

c.       specify log file location.
Add -XX:FlightRecorderOptions=defaultrecording=true,repository=/idm/oracle/tmpJFR

and save

how to find out OS Port blocking information command

here is the command to check OS port blocking. this command should not return anything

 [bin]\> netstat -an | grep FIN_WAIT1

if this command is bringing any values it means this server port is being blocked. unblock the port in order to for other server to access information at this server.

federation protocols and their differences

Federation Protocols

In building a federated architecture that addresses interoperability, assurance, and trust concerns across security domains, the following protocols have emerged as useful building blocks for identity management integration:

• SAML 1.0 and 1.1, which define a format for security data exchange known as an assertion, and profiles which provide the means for using the assertions
• SAML 2.0, which extends SAML 1.1 to provide additional profiles.
• WS-Federation, which enables different security realms to federate by brokering trust of identities, user attributes, authentication between participating Web services

SAML 1.x

SAML 1.0 defines two key concepts:

1. a security token format, known as an assertion, which associates a given identity with specific access rights
2. profiles that describe ways to package these assertions to provide single sign-on

SAML 1.1 updates SAML 1.0 with feedback and corrections. Specifically, SAML 1.1 introduces XML Digital Signatures changes that greatly improve interoperabilty. Because of these XML Digital Signature changes, Oracle recommends that you use the SAML 1.1 protocol over SAML 1.0 whenever possible as it greatly reduces issues when verifying signatures.

SAML 2.0

SAML 2.0 includes support for single sign-on based largely on the framework developed by the Liberty Alliance ID-FF specifications.
Although the concept of identity federation is not present in the specifications, SAML 2.0 promotes the existence of a name identifier for a specific use. SAML 2.0 supports a number of named profiles that largely mirror the functionality of the Liberty ID-FF 1.2 profiles, on top of the name identifiers inherited from SAML 1.x.

WS-Federation

The WS-Federation specification is "an integrated model for federating identity, authentication, and authorization across different trust realms and protocols." WS-Federation is a Web services-oriented standard which supports profiles for passive requestors, such as Web browsers, as well as active requestors such as SOAP-enabled applications.

How to De-install the Enterprise Manager Cloud Control 12c Agent

follow below oracle instruction if you have to uninstall EM 12c Agent.


Before you deinstall a Management Agent, do the following:
    a. Stop the Agent using command from Management Agent home:

$ emctl stop agent
Example:
../agent12c/agent_inst/bin/emctl stop agent

    b. Wait for the Management Agent to go to the unreachable state in the Cloud Control console.
    c. It is mandatory to delete the Management Agent and their monitored targets using any of the following methods:
      

Example:
$ emcli login -username=SYSMAN
$ emcli sync
$ emcli delete_target -name="example.com:1836" -type="oracle_emd" -delete_monitored_targets -async

       Or
 

2. Deinstalling using Graphical Method:

2.a.) Invoke the installer from Management Agent home by running the following command:
    

$<AGENT_HOME>/oui/bin/runInstaller -deinstall ORACLE_HOME=<absolute_path_to_agent_home> [-removeallfiles]

Example:
$ /u01/app/oracle/agent/core/12.1.0.1.0/oui/bin/runInstaller -deinstall ORACLE_HOME=/u01/app/oracle/agent/core/12.1.0.1.0 -removeallfiles

2.b.) In the Installation wizard click on "Installed Products" button.

2.c.) On the Inventory screen, select the plug-in homes, and click "Remove" button.

2.d.) On the Inventory screen, select the sbin home, and click "Remove" button.

2.e.) On the Inventory screen, select the Management Agent, and click "Remove" button.

OR
Deinstalling using Silent Method:

2.i) Deinstall the plug-in homes:
$/oui/bin/runInstaller -silent -deinstall -removeallfiles "REMOVE_HOMES={absolute_path_to_plug-in_home}" -invPtrLoc

Example:
$ ../agent/core/12.1.0.1.0/oui/bin/runInstaller -silent -deinstall -removeallfiles "REMOVE_HOMES={../agent/plugins/oracle.sysman.emas.oms.plugin_12.1.0.1.0, ../agent/plugins/oracle.sysman.emct.oms.plugin_12.1.0.1.0}" -invPtrLoc /home/oracle/oraInst.loc

2.ii) Deinstall the sbin home:
$/oui/bin/runInstaller -silent -deinstall -removeallfiles "REMOVE_HOMES={absolute_path_to_sbin_directory}" -invPtrLoc

Example:
$ ../agent/agent_inst/oui/bin/runInstaller -silent -deinstall -removeallfiles "REMOVE_HOMES={../agent/sbin}" -invPtrLoc /home/oracle/oraInst.loc

2.iii) Deinstall the Management Agent:
$/oui/bin/runInstaller -silent -deinstall -removeallfiles "REMOVE_HOMES={absolute_path_to_agent_oracle_home}" -invPtrLoc

Example:
$ ../agent/core/12.1.0.1.0/oui/bin/runInstaller -silent -deinstall -removeallfiles "REMOVE_HOMES={../agent/core/12.1.0.1.0}" -invPtrLoc /home/oracle/oraInst.loc

Note: Parameter -invPtrLoc is optional

For Windows: Instead of runInstaller use setup.exe

3. (Only for Graphical Mode) Verify whether the Oracle Homes and other directories were successfully deinstalled. To do so, follow these steps:

3.a.) Invoke the installation wizard by running the following command from the Management Agent Home:
$/oui/bin/runInstaller

Example:
$ ../agent/core/12.1.0.1.0/oui/bin/runInstaller

3.b.) In the installation wizard, on the My Oracle Support Details screen, click on "Installed Products" button.

3.c.) On the Inventory screen, check whether or not the Oracle Homes and other directories you deinstalled appears. If the deinstallation was successful then those Oracle Homes and directories should not appear.

4. Open inventory.xml and check Agent plugin home and Agent sbin home entries are removed or not. These entries should be removed during deinstallation.

Note: inventory.xml would be located under ContentsXML folder under the inventory location in oraInst.loc file.

5. Remove the Cloud Control Management Agent base directory:

For UNIX platforms:

$ rm -rf <absolute_path_to_agent_base_dir>
Example:
$ rm -rf /u01/app/oracle/product/agent12c

For Microsoft Windows platforms:

C:\app\oracle> del <absolute_path_to_agent_base_dir
Example:
C:\app\oracle> del c:\app\oracle\product\agent12c

If the Windows Service Oracleagent12c1Agent (the service name may be different) is not deleted, you can delete it using the windows command:

C:\> sc delete Oracleagent12c1Agent

admin server WLS start up error BEA-000386

ERROR:

<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
       at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
       at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
       at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
       at weblogic.security.SecurityService.start(SecurityService.java:141)
       at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
       Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
       at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
       at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
       at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       Truncated. see log file for complete stacktrace
>
 <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
 <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>


Solution:

taking the "servers/<managed>/data/ldap" directory and putting it in place of AdminServer's "ldap" directory solves this issue: the AdminServer boots fine

how to get EJBs pools size information at weblogic

below is the place where you can find EJBs Pool size setting information.



navigate to Weblogic console > deployments > oam_server > EJBs > ControllerMessageBean > Configuration 

how to disable OAM managed servers broadcast log information into Amdin Domain log

this action is performed when you don't want Manage Server send log information to Admin server logs for each action and which will increase traffic and cause high CPU usage. Each Manage Server already recording this information into its own logs. so sending same information to Admin Server is an extra load on Admin server to record in its logs. this will improve the performance of admin server

here is how to disable OAM Manager Server logs broad casing to Admin Server

1. connect to WebLogic admin console

2. Click on 'Environment --> Servers'

3. Click on 'oam_serverX' (X=1,2,3,4)

4. Click on 'Logging' tab

 5. Expand the 'Advanced' section

6. Under the 'Domain log broadcaster' change the 'Severity level' to 'Critical'

7. click Save and exit.

lsnrctl status error. set ORACLE_HOME to fix this issue

./lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 04-DEC-2014 11:36:08
Copyright (c) 1991, 2009, Oracle.  All rights reserved.
Message 1053 not found; No message file for product=network, facility=TNSMessage 1020 not found; No message file for product=network, facility=TNSMessage 1021 not found; No message file for product=network, facility=TNSMessage 1022 not found; No message file for product=network, facility=TNSMessage 1023 not found; No message file for product=network, facility=TNSMessage 1026 not found; No message file for product=network, facility=TNSMessage 1034 not found; No message file for product=network, facility=TNSMessage 1024 not found; No message file for product=network, facility=TNSMessage 1025 not found; No message file for product=network, facility=TNSMessage 1040 not found; No message file for product=network, facility=TNSMessage 1033 not found; No message file for product=network, facility=TNSMessage 1028 not found; No message file for product=network, facility=TNSMessage 1415 not found; No message file for product=network, facility=TNS  Message 1050 not found; No message file for product=network, facility=TNS
  Message 1050 not found; No message file for product=network, facility=TNS
Message 1029 not found; No message file for product=network, facility=TNSMessage 1411 not found; No message file for product=network, facility=TNS
  Message 1408 not found; No message file for product=network, facility=TNS
  Message 1408 not found; No message file for product=network, facility=TNS
  Message 1408 not found; No message file for product=network, facility=TNS
Message 1411 not found; No message file for product=network, facility=TNS
  Message 1408 not found; No message file for product=network, facility=TNS
Message 1052 not found; No message file for product=network, facility=TNS[idmadm


Solution
please set ORACLE_HOME parameter

e.g
export ORACLE_HOME=/home/oracle/11.2.0

now start
./lsnrctl start

now you should be able to check status