Oracle Internet Directory (OID) and Weblogic installation on Linux

Installation manual:

http://download.oracle.com/docs/cd/E17904_01/install.1111/e12002/instps2001.htm

Basic steps:
1. Install Oracle
2. Install OID (and FMW control and ODSM)
Oracle installation is quite trivial, so let’s focus on the OID installation.
- Just remember to use the AL32UTF8 character set on the database!
You need to download:
- Oracle WebLogic Server 10.3.4.
- Oracle Identity Management 11.1.1.2.0 & 11.1.1.3.0




Actual installation:
1. Install WLS 10.3.4
- Run the installation .bin
* In 64 bit environments use: JAVA_HOME/bin/java -jar wls1034_generic.jar
* You need JDK 1.6 or later
- Create a new FMW home
- Register for security updates..
- Typical or Custom
- Change or accept the installation directories (df -h …)
- Summary => Next
- Installation…
2. Install OID 11.1.1.2.0
- unzip ../ofm_idm_linux_11.1.1.2.0_32_disk1_1of1.zip …
- ./runInstaller
- Install Software – DO NOT CONFIGURE!
- Use SAME MIDDLEWARE HOME as WLS above!
- Oracle Home Directory: This will be the directory name under Middleware Home
- Installation …
- Run root script: /middleware_home_directory/oracle_home_dir/oracleRoot.sh
- Save Summary.
3. Install OID 11.1.1.3.0 Patch Set
- unzip ../ofm_idm_linux_11.1.1.3.0_32_disk1_1of1.zip …
- ./runInstaller
- Install Software
- Use same homes !
- Next, next
- Root script
- Save Summary
OID Configuration with FMW Control and ODSM:
1. Configuration
/middleware_home_directory/oracle_home_dir/bin/config.sh
- Installer starts
- Create new domain
=> FMW Control is being configured to manage OID here
* User Name: WLS Admin user details
* Domain name
- Installation location
* Weblogic Server Directory
* Oracle Instance location, new “ASInstance” (Not actual Oracle Instance)
* Oracle Instance Name, new “ASInstance” (Not actual Oracle Instance)
- De-select others than Oracle Internet Directory
=> We will configure only that
- Auto configuration ports normally OK, you can select them if you want
- Create Schema
* Create ODS Database Schema
* Connect string, for example: myserver:1521:orcl
* SYS
* Sys_password
- OID Passwords
* ODS Schema password & confirm (all directory content)
* ODSSM Schema password & confirm (OID statistics and DIP schema)
- OID information
* Realm, for example: dc=us,dc=oracle,dc=com
* Admin user: orcladmin
* Admin password: …
- Install
- Save Summary
* Note: Weblogic Console ie: http://myhost.us.oracle.com:7001/console
Verify installation:
- …home/bin/opmnctl status -l
- Alive:
* OVD
* oidldapd
* oidldapd
* oidmon => LDAP port, LDAPS port
* EMAGENT
- ldapsearch -p LDAP_port -b “” -s base “objectclass=*” orcldirectoryversion
=> orcldirectoryversion=OID 11.1.1.3.0
Open Enterprise Manager Fusion Middleware Control 11g
* For example: http://myhost.us.oracle.com:7001/em
- Find oid1 in FMW Control
- Verify version number in FMW Control
Open Oracle Directory Services Manager
* For example: http://myhost.us.oracle.com:7005/odsm
- Connect to a directory
* OID – directory name
* User Name: cn=orcladmin
* password
- Verify OID version
After you’re done installing and configuring the OID itself, you can proceed to netca to configure the destination databases “tnsnames.ora”.
That will update sqlnet.ora and ldap.ora
Examples
LDAP.ORA:
DEFAULT_ADMIN_CONTEXT = “ou=ora,dc=company,dc=com”
DIRECTORY_SERVERS = (ldap1.company.com:389, ldap2.company.com:389)
DIRECTORY_SERVER_TYPE = OID
Oracle can “officially” only use OID or AD as LDAP servers.
The type can be OID or AD. The multiple servers are for redundancy; it will not try each one in turn. Then in SQLNET.ORA:
NAMES.DIRECTORY_PATH=(LDAP, TNSNAMES)
The means try LDAP first, then try TNSNAMES.ORA, then give up.
If you want to use a third-party LDAP server, Oracle has a product called Virtual Directory that will act as a proxy between them.

More Here

Courtesy:http://www.database.fi/2011/03/oracle-internet-directory-oid-and-weblogic-installation-on-linux/

Weblogic Application Server – Startup without asking for password

After installing the latest WebLogic Release, at startup it asks for the username and password.


Solution here: http://blogs.oracle.com/middleware/2010/05/weblogic_not_reading_bootproperties_1111x.html


Just go to user_domains/MYDOMAIN where MYDOMAIN is the domain that you want to start.
Goto Servers/SERVER where SERVER is the SERVER that you want to start.

Create, if does not exist a security directory

On the security directory create a file named boot.properties with the following entries:


username=
password=


Just put your un-encripted password. At startup the password will be encrypted.

More Here

Courtesy:http://primalcortex.wordpress.com/2010/11/04/weblogic-application-server-startup-without-asking-for-password/

Weblogic Server Basic Components

Domain
A Weblogic server domain is an administrative grouping of servers and/or clusters. You configure, manage, monitor the domain from central location; this central location is the administration (admin) server.


Admin Server
Admin server is just a Weblogic Server instance which maintains a repository of configuration information for the domain. Admin server acts as a centralized application deployment server which provides browser based admin console for configure, manage and monitor all aspects of the domain.


Managed Server
A Managed server is a term for any other server in the domain other than the admin server. Managed Servers host the components and associated resources that constitute your applications – for example, JSPs and EJBs. When a Managed Server starts up, it connects to the domain’s Administration Server to obtain configuration and deployment settings.


Two or more Managed Servers can be configured as a WebLogic Server cluster (more about this in next blog) to increase application scalability and availability. In a WebLogic Server cluster, most resources and services are deployed to each Managed Server (as opposed to a single Managed Server,) enabling failover and load balancing.


Node Manager
Node Manager is a Java utility that runs as separate process from WebLogic Server and allows you to perform common operations tasks for a Managed Server, regardless of its location with respect to its Administration Server. While use of Node Manager is optional, it provides valuable benefits if your WebLogic Server environment hosts applications with high availability requirements.


If you run Node Manager on a machine that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Administration Console or from the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.


WebLogic Server Cluster
A WebLogic Server cluster consists of multiple WebLogic Server server instances running simultaneously and working together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines. You can increase a cluster’s capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances. Each server instance in a cluster must run the same version of WebLogic Server.

How Does a Cluster Relate to a Domain?


* A cluster is part of a particular WebLogic Server domain.


* A domain is an interrelated set of WebLogic Server resources that are managed as a unit.
* A domain includes one or more WebLogic Server instances, which can be clustered, non-clustered, or a combination of clustered and non-clustered instances.
* A domain can include multiple clusters.

More Here

Courtesy:http://jamesminks.wordpress.com/2010/09/02/weblogic-server-basic-components/

Test Connectivity with Weblogic to Database server

Weblogic server provides two very handy utilities to test/ping the connectivity.
1. Client to Weblogic server
2. Weblogic to Database server
And it proves to very helpful the time when you are facing lots of problem with the connectivity vice versa.
1. Test Client to Weblogic
Set the weblogic environment using setWLSEnv.cmd(windows) or setWLSenv.sh(Unix)

Run the below command
java weblogic.Admin -adminurl t3://localhost:6001 -username weblogic -password weblogic PING
OUTPUT
2. Test Weblogic to Database
Set the weblogic environment using setWLSEnv.cmd(windows) or setWLSenv.sh(Unix)
Run the below Command
java utils.dbping ORACLE_THIN DB_USER DB_PASSWORD 127.0.0.1:1521:MY_SID01


Courtesy:http://rocksolutions.wordpress.com/2010/03/31/test-connectivity-with-weblogic-and-wls-to-database/

Steps to configure SAML 2 on Weblogic Server 10.3.x

1) First we need to create a security database for SAML configuration. This has to be done even before domains are created.
Steps to use a pointbase database provided with Weblogic Installation :

• Copy ” pbembedded.lic ” located in ” C:\bea10.3\wlserver_10.3\common\eval\pointbase\lib ” to ” C:\bea10.3\wlserver_10.3\common\eval\pointbase\tools “
• We need to create two security database – one for the source side domain and another for the destination end domain.
• Now start the PointBase server ( run ” startPointBase.cmd ” located in ” C:\bea10.3\wlserver_10.3\common\eval\pointbase\tools “
• Start the PointBase console  ( run ” startPointBaseConsole.cmd ” located in ” C:\bea10.3\wlserver_10.3\common\eval\pointbase\tools “
• Login using the user name ” EXAMPLES ” and password ” EXAMPLES “

• Now lets create a database table using the sample ” rdbms_security_store_pointbase.sql ” located in ” C:\bea10.3\wlserver_10.3\server\lib “

• Now we need to create another database using the user name ” PUBLIC ” and password ” PUBLIC “

So now we have successfully created two security database, lets cerate the domains now.
We need to create the following domains on WLS 10.3.x :
Domain1 name : saml_source   ;    non ssl port : 7001 ;  ssl port : 7002
Domain2 name : saml_destination  ;  non ssl port : 7003  ;  ssl port : 7004
Now run the ” Configuration Wizard ” On the ” Customize Environment and Services Settings ” screen select the option ” Yes “

• Select the option “I want to create, change, or remove RDBMS support” and make the changes as shown in the figure below, and also click on ” Test Connection ” button to make sure that the database is configured properly.

• We need to configure ” Custom Identity and Custom Trust ” on Weblogic servers.

Refer the link below to know more about configuring ” Custom Identity and Custom Trust ” :
Link : http://wls4mscratch.wordpress.com/2010/06/08/steps-to-configure-custom-identity-custom-trust-on-wls/

• Now we need to configure ” Credential Mapper ” on the IDP end.
• So to ” myrealm ” –> ” Providers ” –> ” Credential Mapping ” –> and add a ” SAML2CredentialMapper ” as shown below :

• Now click on the newly created SAML2CredentialMapper say ” saml_IDP ” and make the following changes :
  • Issuer URI : http://www.souresite.com/saml
  • Name Qualifier : sourcesite.com
  • Web Service Assertion Signing Key Alias : cooldragon
  • Web Service Assertion Signing Key Pass Phrase : **********
  • Please type again To confirm : *********

• Click on ” Servers ” –> Admin Server –> ” Federation Services ” –> ” SAML 2.0 Identity Provider ” and make the following changes :
  • Enabled : check
  • Only Accept Signed Authentication Request : check
  • Preferred Binding : POST

• Now click on ” Servers ” –> Admin Server –> ” Federation Services ” –> ” SAML 2.0 General ” and make the following changes :
  • Replicated Cache Enabled – Uncheck
  • Contact Person Given Name
  • Contact Person Surname
  • Contact Person Type
  • Contact Person Company
  • Contact Person Telephone Number
  • Contact Person Email Address
  • Organization Name
  • Organization URL
  • Published Site URL : http://:/saml2
  • Entity ID : ( Source Domain name)
  • Single Sign-on Signing Key Alias
  • Single Sign-on Signing Key Pass Phrase
  • Confirm Single Sign-on Signing Key Pass Phrase
• Save the changes and export the IDP metadata into a XML file –> Click on “ Publish Meta Data ” button. ( say IDP_Metadata.xml ). We need to copy this file to the destination domain later.

————–
Destination Side :
Now we need to generate the SAML destination site ( SP ) metadata

• Click on ” myrealm ” –> ” Providers ” –> ” Authentication ” –> new ” SAML2IdentityAsserter “

• Click on ” Servers ” –> Admin Server –> ” Federation Services ” –> ” SAML 2.0 Service Provider ” and make the following changes :
  • Enabled : check
  • Always Sign Authentication Requests : check
  • Force Authentication : Check
  • Preferred Binding : POST
  • Default URL : http://:/samldest01App

• Now click on ” Servers ” –> Admin Server –> ” Federation Services ” –> ” SAML 2.0 General ” and make the following changes :
  • Replicated Cache Enabled : Uncheck
  • Contact Person Given Name
  • Contact Person Surname
  • Contact Person Type
  • Contact Person Company
  • Contact Person Telephone Number
  • Contact Person Email Address
  • Organization Name
  • Organization URL
  • Published Site URL : http://:/saml2
  • Entity ID : ( Destination Domain name)
  • Single Sign-on Signing Key Alias
  • Single Sign-on Signing Key Pass Phrase
  • Confirm Single Sign-on Signing Key Pass Phrase

More Here

Courtesy:http://wls4mscratch.wordpress.com/2010/07/22/steps-to-configure-saml-2-on-weblogic-server-10-3-x/