Followers

Tuesday, March 18, 2014

The Server Lifecycle

SHUTDOWN. In this state, the server is configured but inactive. 


STARTING. When you start a server, it takes the following actions:Retrieves its configuration data.  

STANDBY. (Available only if you have configured an administration port.) You can issue a command that starts a server and places it in this state. In this state, a server has initialized all of its services and applications and can accept administration commands and participate in cluster communication. It is not accessible for requests that come from external clients.
A typical use of the STANDBY state is to keep a server available as a "hot" backup, especially in a high-availability or mission-critical environment. When you need to use the backup server, you can quickly resume its ability to process client requests. 

RUNNING. In this state, a server offers its services to clients and can operate as a full member of a cluster

SHUTDOWN. You can move a server into this state either from the RUNNING state or the STANDBY state. As it transitions to SHUTDOWN, a server goes through the SHUTTING_DOWN state

FAILED. If one or more critical services become dysfunctional during the lifetime of server, the server transitions to the FAILED state. Your only option to recover from the FAILED state is to shut down the server. You can set up a server to restart itself if critical services become dysfunctional. For information about automatic restarts, Guide. 

UNKNOWN. If a server cannot be contacted, it is considered to be in the UNKNOWN state.


Thursday, March 13, 2014

Register or de-register the Oracle Web Tier with the Oracle Weblogic Domain

Once an Oracle WebLogic domain has been created, the Oracle web tier can be linked to the domain. The advantages of doing this are that the Oracle web tier can be managed and monitored via the Oracle Fusion Middleware console.
1.      To register the Oracle web tier with the WebLogic domain, execute the following commands  on each web tier instance.
cd <ORACLE_WT_HOME>/instances/instance_name/bin
./opmnctl registerinstance -adminHost <hostname> -adminPort <adminport> -adminUsername Weblogic
<Enter the Weblogic password when prompted>
2.      To de-register the Oracle web tier with the WebLogic domain, execute the following commands on each web tier instance. 
cd <ORACLE_WT_HOME>/instances/instance_name/bin
./opmnctl unregisterinstance -adminHost <hostname> -adminPort <adminport> -adminUsername Weblogic
<Enter the Weblogic password when prompted>
Note: Ensure the weblogic admin server is running while registering or de-registering !

Wednesday, March 12, 2014

how SSL works

Secure Sockets Layer (SSL): How It Works
What Happens When a Browser Encounters SSL

    A browser attempts to connect to a website secured with SSL.
    The browser requests that the web server identify itself.
    The server sends the browser a copy of its SSL Certificate.
    The browser checks whether it trusts the SSL Certificate. If so, it sends a message to the server.
    The server sends back a digitally signed acknowledgement to start an SSL encrypted session.
    Encrypted data is shared between the browser and the server and https appears.

Encryption Protects Data During Transmission

Web servers and web browsers rely on the Secure Sockets Layer (SSL) protocol to help users protect their data during transfer by creating a uniquely encrypted channel for private communications over the public Internet. Each SSL Certificate consists of a key pair as well as verified identification information. When a web browser (or client) points to a secured website, the server shares the public key with the client to establish an encryption method and a unique session key. The client confirms that it recognizes and trusts the issuer of the SSL Certificate. This process is known as the "SSL handshake" and it begins a secure session that protects message privacy, message integrity, and server security.