Install JDK
Install a valid JDK software (like JRockit JDK) and export the location of the installed jdk as JAVA_HOME.
We can either go with an installable package or just unzip a compressed archive version available.
[oracle@vinod Middleware]$ pwd
/u01/Middleware
[oracle@vinod Middleware]$unzip jdk6.zip
[oracle@vinod Middleware]$ ls -ltr
drwxr-xr-x 10 oracle oinstall 4096 Sep 7 2011 jdk6
[oracle@vinod Middleware]$ cd jdk6/
[oracle@vinod jdk6]$ ls
bin include lib oracle_jdk_install src.zip
demo jremissioncontrol sample THIRDPARTYLICENSEREADME.txt
[oracle@vinod jdk6]$ cd ~
Replace JAVA_HOME with the installation location of the supported JDK you installed for your platform.
vi .bash_profile
JAVA_HOME=/u01/Middleware/jdk6; export JAVA_HOME
. .bash_profile
Check the java version installed.
[oracle@vinodweblogic]$ $JAVA_HOME/bin/java -version
java version “1.6.0_24”
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1432-linux-x86_64, compiled mode)
Install Oracle WeblogicServer(10.3.5)
If you are installing a 64-bit Oracle WebLogic Server on a 64-bit platform:
• Use the -d64 flag when using 32/64-bit hybrid JDK’s (such as the HP JDK
for HP-UX and SUN JDK for Solaris SPARC).
Execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version on 32/64-bit hybrid JDKs) to ensure that your JAVA_HOMErefers to a 64-bit JDK. (JAVA_HOME/bin/java -d64 -jar wls1031_generic.jar)
# xhost +
[root@vinod ~]# su – oracle
[oracle@vinod ~]$ echo $JAVA_HOME
/u01/Middleware/jdk6
[oracle@vinod ~]$ cd /stage/fusion_installers/weblogic/
[oracle@vinodweblogic]$ ls
wls_generic.jar
Invoke the 64-Bit Installer
[oracle@vinodweblogic]$ $JAVA_HOME/bin/java -d64 -jar wls_generic.jar
Extracting 0%……………………………………………………………………………………….100%
Aug 29, 2012 4:00:57 PM java.util.prefs.FileSystemPreferences$2 run
INFO: Created user preferences directory.
Check upon the Weblogic directories created.
[oracle@vinodweblogic]$ cd /u01/Middleware/
[oracle@vinod Middleware]$ ls -ltr
drwxr-x— 10 oracle oinstall 4096 Sep 7 2011 jdk6
drwxr-xr-x 7 oracle oinstall 36864 Aug 29 16:00 modules
-rw-rw—- 1 oracle oinstall 133 Aug 29 16:01 domain-registry.xml
drwxr-xr-x 8 oracle oinstall 4096 Aug 29 16:01 utils
-rw-r–r– 1 oracle oinstall 852 Aug 29 16:02 ocm.rsp
-rw-r–r– 1 oracle oinstall 86951 Aug 29 16:02 registry.dat
-rw-r–r– 1 oracle oinstall 1908 Aug 29 16:02 registry.xml
drwxr-xr-x 2 oracle oinstall 4096 Aug 29 16:02 logs
drwxr-xr-x 9 oracle oinstall 4096 Aug 29 16:02 wlserver_10.3
drwxr-xr-x 6 oracle oinstall 4096 Aug 29 16:02 coherence_3.6
[oracle@vinod Middleware]$
Fusion Applications: Running Repository Creation Utility For SOA.
We can directly go ahead with creating necessary schemas for IDM which will include the dependent SOA schemas creation too.
But to get more familiar with weblogic domain creations, extending the domains, starting and stopping servers we will go with installing SOA initially, and then go ahead with IDM.
So first we will run rcu for SOA, create and configure soa domains, and then we will go on with IDM.
Pre-Requisites
- Applying Oracle Database Patch 8625762 for Oracle Business Process Management Suite
If you are planning on installing Oracle Business Process Management Suite (BPM) and you are using an Oracle database(version less than 11.2.0 ) you must apply patch 8625762 to avoiderror ORA-03137 and OutOfMemory exception.
- Component-Specific RCU Requirements for Oracle Databases (SOA and BPM Components)
Component Schema Owner Requirement
Oracle BAM prefix_ORABAM None.
SOA Infrastructure prefix_SOAINFRA processes: 200
User Messaging Server(ORASDPM) prefix_ORASDPM None.
- Enable Unicode Support
Your operating system configuration can influence the behavior of characters supported by Oracle SOA Suite.
On a UNIX operating system, it is highly recommended that you enable Unicodesupport by setting the LANG and LC_All environment variables to a locale with theUTF-8 character set. This enables the operating system to process any character inUnicode. SOA technologies are based on Unicode.
If the operating system is configured to use a non-UTF-8 encoding, SOA componentsmay function in an unexpected way.
[oracle@vinod Middleware]$ locale |grep –e LANG –e LC_ALL
LANG=en_US.UTF-8
LC_ALL=
[oracle@vinod Middleware]$ LC_ALL=en_US.UTF-8
[oracle@vinod Middleware]$ export LC_ALL
[oracle@vinod Middleware]$ locale|grep –e LANG –e LC_ALL
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8
Starting the Repository Creation Utility to create Schemas for SOA, BAM in the Database:
Make sure that the database is up and running.
Check the processes parameter value as mentioned in component specific requirements for SOA, BAM.
SQL>sho parameter processes
NAME TYPE VALUE
———————————— ———– ——————————
processes integer 500
Run the RCU script located in the stage directory.
[oracle@vinod bin]$ pwd
/stage/fusion_installers/fmw_rcu/linux/bin
[oracle@vinod bin]$ set linux32 bash
[oracle@vinod bin]$ ./rcu
Fusion Applications: Installing Oracle SOA Suite
Starting the Installer
The installer requires the location of a Java Runtime Environment (JRE) on your system.
Use the location of the jre directory installed, to start the installer.
The default location for the JRE is MW_HOME/jdk160_11 .
> ./runInstaller -jreLoc JRE_LOCATION
[oracle@vinod Middleware]$ cd /stage/fusion_installers/soa/Disk1/
[oracle@vinod Disk1]$ ls
doc installrunInstaller setup.exe stage
[oracle@vinod Disk1]$ ./runInstaller -jreLoc /u01/Middleware/jdk6/
Starting Oracle Universal Installer…
Checking if CPU speed is above 300 MHz. Actual 2294 MHz Passed
Checking Temp space: must be greater than 150 MB. Actual 104745 MB Passed
Checking swap space: must be greater than 512 MB. Actual 8189 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2012-08-29_04-44-38PM. Please wait …[oracle@vinod Disk1]$ Log: /u01/app/oraInventory/logs/install2012-08-29_04-44-38PM.log
Oracle BAM and Oracle SOA Suite are both installed onto your system by default.
After the products are installed, you must run the Configuration Wizard to configure the product(s) of your choice.
Have a look at the installed SOA Directories:
[oracle@vinod Disk1]$ cd /u01/Middleware/
[oracle@vinod Middleware]$ ls -ltr
‘
‘
drwxr-x— 27 oracle oinstall 4096 Aug 29 17:10 Oracle_SOA
drwxr-x— 32 oracle oinstall 4096 Aug 29 17:10 oracle_common
[oracle@vinod Middleware]$ cdOracle_SOA/
[oracle@vinodOracle_SOA]$ ls
bam bin cfgtoollogs common diagnostics inventory jlib modules oraInst.locrcusoauixutil
BC4J bpm clone communications doc jdk lib OPatchouirdauddi upgrade webcenter
[oracle@vinodOracle_SOA]$ cd ../oracle_common/
[oracle@vinodoracle_common]$ ls
admin BC4J cfgtoollogs diagnostics install jlib network ouisoa upgrade webservices
adminserver_registration bin clone doc inventory lib OPatchrcusysmanutil
atgpfbpm common hapowertoolsjdk modules oraInst.locrdauixwebcenter
Configuring The Oracle SOA Suite: Creating a new WebLogic domain for Oracle SOA components
• During the configuration, the Oracle Fusion Middleware Configuration Wizard automatically creates managed servers in the domain to host the Fusion Middleware systemcomponents. Oracle recommends that you use the default configuration settings for these managed servers.
• Before you start the Configuration Wizard, you must shut down any managed serversthat are currently running. If you do not, validation of your managed servers will faildue to port number conflicts from the managed servers that are currently running.
Since, this is a new installation,we need to create a new WebLogic domain.
We can also run the Configuration Wizard to extend an existing WebLogic domain.
Create a new WebLogic domain for your Oracle SOA components
Run the configuration wizard to create WebLogic domain for SOA components installed and create respective servers in the domain.
The Configuration Wizard is located in the SOA_ORACLE_HOME/common/bin.
Go to this directory, and then run the config.sh (./config.sh)
To create a log file of your configuration session, start the Configuration Wizard with
the -log option, as shown below:
./config.sh -log=log_filename
[root@vinod ~]# su – oracle
[oracle@vinod u01]$ cd Middleware/Oracle_SOA/common/bin/
[oracle@vinod bin]$ ./config.sh -log=/u01/Middleware/SOADomain_config_1stattempt.log
Confirm admin username and password
weblogic_soa / *******
Configure JDBC Component Schema
Schema Password: ******
[oracle@vinod bin]$ ./config.sh -log=/u01/Middleware/SOADomain_config_1stattempt.log
[oracle@vinod bin]$
Access TheWebLogic& EM URLs
http://vinod.ibizsoft.com:7001
WebLogic Server Console URL
http://vinod.ibizsoft.com:7001/console
EM Fusion Middleware Control URL
http://vinod.ibizsoft.com:7001/em
Check upon the Directories created when the domain and servers are created and configured.
[oracle@vinod Middleware]$ ls -lrt
drwxr-x— 10 oracle oinstall 4096 Sep 7 2011 jdk6
drwxr-xr-x 7 oracle oinstall 36864 Aug 29 16:00 modules
drwxr-xr-x 8 oracle oinstall 4096 Aug 29 16:01 utils
-rw-r–r– 1 oracle oinstall 852 Aug 29 16:02 ocm.rsp
-rw-r–r– 1 oracle oinstall 86951 Aug 29 16:02 registry.dat
-rw-r–r– 1 oracle oinstall 1908 Aug 29 16:02 registry.xml
drwxr-xr-x 2 oracle oinstall 4096 Aug 29 16:02 logs
drwxr-xr-x 9 oracle oinstall 4096 Aug 29 16:02 wlserver_10.3
drwxr-xr-x 6 oracle oinstall 4096 Aug 29 16:02 coherence_3.6
drwxr-x— 27 oracle oinstall 4096 Aug 29 17:10 Oracle_SOA
drwxr-x— 32 oracle oinstall 4096 Aug 29 17:10 oracle_common
drwxr-x— 4 oracle oinstall 4096 Aug 30 11:56 user_projects
-rw-r—– 1 oracle oinstall 19435 Aug 30 11:58 SOADomain_config_1stattempt.log
-rw-rw—- 1 oracle oinstall 204 Aug 30 11:58 domain-registry.xml
[oracle@vinod Middleware]$ cduser_projects/
[oracle@vinoduser_projects]$ ls
applications domains
[oracle@vinoduser_projects]$ cd applications/
[oracle@vinod applications]$ ls
SOA_Domain
[oracle@vinod applications]$ cdSOA_Domain/
[oracle@vinodSOA_Domain]$ ls
em.ear
[oracle@vinodSOA_Domain]$ cd ../../domains/
[oracle@vinod domains]$ ls
SOA_Domain
[oracle@vinod domains]$ cdSOA_Domain/
[oracle@vinodSOA_Domain]$ ls
autodeployinit-info startManagedWebLogic_readme.txt
binlib startWebLogic.sh
BPMJMSFileStorelogs sysman
configsecurity UMSJMSFileStore_auto_1
console-extservers UMSJMSFileStore_auto_2
fileRealm.propertiesSOAJMSFileStore
[oracle@vinodSOA_Domain]$ cd servers/
[oracle@vinod servers]$ ls
AdminServer
[oracle@vinod servers]$ cdAdminServer/
[oracle@vinodAdminServer]$ ls
security
[oracle@vinodAdminServer]$
[oracle@vinoduser_projects]$ tree -L 3
.
|– applications
| `– SOA_Domain
| `– em.ear
`– domains
`– SOA_Domain
|– BPMJMSFileStore
|– SOAJMSFileStore
|– UMSJMSFileStore_auto_1
|– UMSJMSFileStore_auto_2
|– autodeploy
|– bin
|– config
|– console-ext
|– fileRealm.properties
|– init-info
|– lib
|– logs
|– security
|– servers
|– startManagedWebLogic_readme.txt
|– startWebLogic.sh
`– sysman
[oracle@vinoduser_projects]$ cd domains/SOA_Domain/servers/
[oracle@vinod servers]$ tree
.
`– AdminServer
`– security
`– boot.properties
Starting & Stopping The Servers
Starting the Servers
1. To start the Administration Server, run the startWebLogic.sh in the directory where you created your new domain.
MW_HOME/user_projects/domains/<domain_name>/startWebLogic.sh
/u01/Middleware/user_projects/domains/SOA_Domain
You entered the domain name and location on the Specify Domain Name and Location Screen in the configuration wizard.
2. To start the Managed Servers, run the startManagedWebLogic.sh script in the bin directory inside the directory where you created your domain.
These managed servers must be started from the command line.
This command also requires that you specify a server name.
The servers that need to be started are:
¦ soa_server(Oracle SOA Server)
¦ bam_server (Oracle BAM Server)
MW_HOME/user_projects/domains/<domain_name>/bin/startManagedWebLogic.sh soa_server
Before the managed server is started, you will be prompted for the WebLogicServer user name and password. These were provided on the ConfigureAdministrator Username and Password Screen in the Configuration Wizard.
Note: If this is the first time that both Oracle SOA Server and Oracle BAM Server are being started after installation and configuration, youmust make sure that your startup of Oracle SOA Server is complete
before starting Oracle BAM Server.
Start the Admin Server
[oracle@vinodSOA_Domain]$ pwd
/u01/Middleware/user_projects/domains/SOA_Domain
[oracle@vinodSOA_Domain]$ ls
autodeployfileRealm.propertiesservers UMSJMSFileStore_auto_1
bininit-info SOAJMSFileStore UMSJMSFileStore_auto_2
BPMJMSFileStorelib startManagedWebLogic_readme.txt
configlogs startWebLogic.sh
console-extsecurity sysman
[oracle@vinodSOA_Domain]$ nohup ./startWebLogic.sh &
[1] 15631
[oracle@vinodSOA_Domain]$ nohup: appending output to `nohup.out’
[oracle@vinodSOA_Domain]$ tail -f nohup.out
Check if the admin server is running in WebLogic Console
http://vinod.ibizsoft.com:7001/console/
è Start the Managed Server (soa_server)
[oracle@vinod bin]$ pwd
/u01/Middleware/user_projects/domains/SOA_Domain/bin
[oracle@vinod bin]$ ls
nodemanagerserver_migrationsetDomainEnv.sh setSOADomainEnv.sh.bak startWebLogic.sh stopWebLogic.shsecureWebLogic.sh service_migrationsetSOADomainEnv.sh
startManagedWebLogic.sh stopManagedWebLogic.sh
[oracle@vinod bin]$ nohup ./startManagedWebLogic.sh soa_server http://vinod.ibizsoft.com:7001 -Dweblogic.management.username=weblogic_soa -Dweblogic.management.password=*******&
[1] 16027
[oracle@vinod bin]$ nohup: appending output to `nohup.out’
[oracle@vinod bin]$ tail -f nohup.out
Check if the managed server soa_server is running in WebLogic Console
http://vinod.ibizsoft.com:7001/console/
Start the Managed Server (bam_server)
[oracle@vinod bin]$ nohup ./startManagedWebLogic.sh bam_server http://vinod.ibizsoft.com:7001 -Dweblogic.management.username=weblogic_soa -Dweblogic.management.password=*******&
[2] 17275
[oracle@vinod bin]$ nohup: appending output to `nohup.out’
[oracle@vinod bin]$ tail -f nohup.out
Check if the managed server soa_server is running: http://vinod.ibizsoft.com:7001/console
Stopping the Servers
Stop the Managed Server (bam_server)
[oracle@vinod bin]$ pwd
/u01/Middleware/user_projects/domains/SOA_Domain/bin
[oracle@vinod bin]$ nohup ./stopManagedWebLogic.sh bam_server&
[3] 28326
[oracle@vinod bin]$ nohup: appending output to `nohup.out’
[oracle@vinod bin]$ tail -f nohup.out
Stop the Managed Server (soa_server)
We can also use the weblogic console to stop the managed servers.
Select Control tab — Select the server to shut down – Click shutdown
Stop the Admin Server (Stop the WebLogic Domain)
[oracle@vinod bin]$ nohup ./stopWebLogic.sh &
[1] 29716
[oracle@vinod bin]$ nohup: appending output to `nohup.out’
[oracle@vinod bin]$ tail -f nohup.out
Now that we are done with Installing and Configuring SOA suite, and having learnt about weblogic domains, admin and managed servers usage, we will go on with Installing and Configuring IDM and IAM components in the next parts.
