Installing the Oracle OSB on Red Hat 6

HomeAboutArticlesPresentationsSubscribe

A blog without a catchy title

by Peter Lorenzen

Installing the Oracle OSB on Red Hat 6

Peter Lorenzen05/03-2013

I have a new and improved post about installing OSB 11.1.1.7

Here is my experiences with installing OSB 11.1.1.6 on Red Hat 6 (64-bit) using Java 7.

By the way you might also be interested in my post about Silent installation of the OSB on Red Hat 6.

First have a look at the documentation:Oracle Fusion Middleware Download, Installation, and Configuration ReadMeOracle Fusion Middleware Installation Planning GuideOracle Fusion Middleware Installation Guide for Oracle Service Bus

Overview

Download the softwarePrepare the OS

Install JavaInstall the latest Java SE CPUInstall the WebLogic Server 10.3.6Install the latest WebLogic Server PSU patchInstall the OSBPatch the OSBCreate database schemas via the RCUConfigure the OSBHomes overviewStarting the serversJava parametersConfiguring the Node ManagerConfigure automatic start of the serversJava 7Warnings in log filesMiscellaneous

Installing the Oracle OSB on Red Hat 6 http://theheat.dk/blog/?p=573

1 de 52 07/08/2014 16:55

Configure OCM

Download the software

JDK 6 64-bit latests update (See explanation in the Install Java section)JDK 7 64-bit latests updateRepository Creation Utility 11.1.1.6.0 (RCU)WebLogic 10.3.6WebLogic 10.3.6 January 2013 CPU/PSU (Patch 14736139)OSB 11.1.1.6WebLogic Server/OSB performance patch (Patch 13573621)Latest OPatch (Patch 6880880 11.1.0.0.0)OSB patch bundle (Patch 14389126)Latest version of the OCM

Please notice

Before using the direkt download links to http://download.oracle.com you need to login in to the siteand accept a License Agreement.The RCU only exists as a 32-bit download

Prepare the OS

I am using Red Hat 6 64-bit. Check the System Requirements for UNIX Operating Systems.Also check Special Startup Requirements for Linux x86 or Linux x86-64 Operating Systems in the samedocument.

This should install the needed packages:

Change the open file limits in /etc/security/limits.conf

123456789

10111213141516171819

yum install binutils-2*.x86_64 -yyum install compat-libcap1-1* -yyum install compat-libstdc++-33*.i686 -yyum install compat-libstdc++-33*.x86_64 -yyum install gcc-4*.x86_64 -yyum install gcc-c++-4*.x86_64 -yyum install glibc-2*.x86_64 -yyum install glibc-2*.i686 -yyum install glibc-devel-2*.i686 -yyum install libaio-0.*.x86_64 -yyum install libaio-devel-0.*.x86_64 -yyum install libgcc-4.*.x86_64 -yyum install libstdc++-4.*.i686 -yyum install libstdc++-4.*.x86_64 -yyum install libstdc++-devel-4.*.x86_64 -yyum install libXext.i686 -yyum install libXtst.i686 -yyum install sysstat-9.*.x86_64 -yyum install redhat-lsb-4.*.x86_64 -y


2 de 52 07/08/2014 16:55

Change the kernel parameters that need changing. Often the default values are OK.Normally I only change/add these two and this is really only needed if you use Coherence.

Create user, group and directories.

Enabling Unicode Support in the .bash_profile for the oracle user.

Install Java

Unzip and untar the downloaded file:

After I install Java I always create a softlink to the installation directory and reference it everywhere. Thismakes it is easier later when you have to upgrade.

I could not get the WebLogic Installer to work with Java 7. The Installer start without any problems but insome of the screens you cannot select options with the mouse or input text. I have reproduced this withOracle Linux 6 and with the WebLogic Server 12c Installer. I have the problem on both physical and virtualservers.

As a workaround I use Java 6 during the installation and later switch to Java 7. This works fine.

Install the latest Java SE CPU

Check the Java SE Critical Patch Update (CPU) to see if you need to patch the Java you have installed.

12345

sed -i '/.*End of file/d' /etc/security/limits.confecho "* soft nofile 16384" >> /etc/security/limits.confecho "* hard nofile 16384" >> /etc/security/limits.confecho "# End of file" >> /etc/security/limits.confcat /etc/security/limits.conf

123

echo "net.core.rmem_max=4192608" >> /etc/sysctl.confecho "net.core.wmem_max=4192608" >> /etc/sysctl.conf/sbin/sysctl -p

123456789

groupadd oinstalluseradd -g oinstall -G oinstall oraclepasswd oracle mkdir -p /u01/app/oracle/productmkdir -p /u01/tmp chown -R oracle:oinstall /u01chmod -R 750 /u01

1 export LANG="en_US.UTF-8"

123

gunzip jdk-7u15-linux-x64.tar.gztar xvf jdk-7u15-linux-x64.tarmv jdk1.7.0_15 /u01/app/oracle/product/.

1 ln -s /u01/app/oracle/product/jdk1.7.0_15 /u01/app/oracle/product/java_current


3 de 52 07/08/2014 16:55

The latest Java SE CPU is from February 2013. It patches update 13 and earlier. I use update 15 so there is noneed to patch it.

Install the WebLogic Server 10.3.6

Take care when downloading the wls1036_generic.jar file since some browsers will rename it towls1036_generic.zip.

-Djava.io.tmpdir is only needed if there is not enough tmp space.

Below I have ignored the screens where you can sign up for security updates etc.

12

/u01/app/oracle/product/java_current/bin/java-Djava.io.tmpdir=/u01/tmp -jar wls1036_generic.jar -log=wls_install.log


4 de 52 07/08/2014 16:55


5 de 52 07/08/2014 16:55


6 de 52 07/08/2014 16:55

Here my Java soft link is ignored so we have to fix this later.


7 de 52 07/08/2014 16:55


8 de 52 07/08/2014 16:55

The Java soft link was ignored so we have to fix this:

Install the latest WebLogic Server PSU patch

Oracle releases quarterly security updates. You can read more about CPU, SPU, PSU and BP patches here.

WebLogic 10.3.6 January 2013 PSU patch 14736139. (p14736139_1036_Generic.zip)

Make sure all WebLogic servers are stopped and remove any previously applied Patch Set Update andassociated overlay patches.

Make sure that the patch-catalog_18682.xml is renamed to patch-catalog.xml!

Verify that the patch is installed.

Alternative use.

For example.

Install the OSB

Red Hat 6 is certified with the 11.1.1.6 OSB but because the OSB was shipped before it was certified youneed the -ignoreSysPrereqs parameter.

The documentation does not reflect this yet but this MOS note does:OSB 11.1.1.6 Installation Fails on Red Hat Enterprise Linux (EL) 6 [ID 1530125.1]

1234

cd /u01/app/oracle/product/osbgrep -R jdk1.6.0_39 *find . -type f -exec sed -i "s/\/u01\/app\/oracle\/product\/jdk1.6.0_39/\/u01/app\/oracle\/product\/java_current/g" {} \;

1234

mkdir /u01/app/oracle/product/osb/utils/bsu/cache_dircp HYKC.jar /u01/app/oracle/product/osb/utils/bsu/cache_dir/.cp patch-catalog_18682.xml /u01/app/oracle/product/osb/utils/bsu/cache_dir/patch-catalog.xml

123

cd /u01/app/oracle/product/osb/utils/bsu/./bsu.sh -prod_dir=/u01/app/oracle/product/osb/wlserver_10.3 -patchlist=HYKC -verbose -install

12

./bsu.sh -prod_dir=/u01/app/oracle/product/osb/wlserver_10.3 -status=applied -verbose -view

12

. /u01/app/oracle/product/osb/wlserver_10.3/server/bin/setWLSEnv.shjava weblogic.version

1234

[oracle@wintermute ~]$ java weblogic.version WebLogic Server 10.3.6.0.3 PSU Patch for BUG14736139 Fri Nov 23 10:16:54 IST 2012WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050

1 cd /u01/software/ofm_osb_generic_11.1.1.6.0_disk1_1of1/Disk1


9 de 52 07/08/2014 16:55


23

./runInstaller -ignoreSysPrereqs -jreLoc /u01/app/oracle/product/java_current/jre


10 de 52 07/08/2014 16:55


11 de 52 07/08/2014 16:55


12 de 52 07/08/2014 16:55


13 de 52 07/08/2014 16:55


14 de 52 07/08/2014 16:55


15 de 52 07/08/2014 16:55


16 de 52 07/08/2014 16:55


17 de 52 07/08/2014 16:55


18 de 52 07/08/2014 16:55

Patch the OSB

To find out if there exists any patches that you should install check the Information Center: Oracle ServiceBus (OSB) [ID 1293368.2] on MOS.

Currently they have listed two patches, one for the WebLogic Server and one for the OSB.

WebLogic PatchCheck Performance Impact in WLS 10.3.6 / Oracle Service Bus 11.1.1.6 if Using Work Manager orDispatch Policy for OSB JMS Services [ID 1388057.1]

Patch 13573621 (p13573621_103603_Generic.zip).

Make sure that the patch-catalog_19101.xml is renamed to patch-catalog.xml!

123

cp DYCA.jar /u01/app/oracle/product/osb/utils/bsu/cache_dir/.cp patch-catalog_19101.xml /u01/app/oracle/product/osb/utils/bsu/cache_dir/patch-catalog.xml

12

cd /u01/app/oracle/product/osb/utils/bsu/./bsu.sh -prod_dir=/u01/app/oracle/product/osb/wlserver_10.3


19 de 52 07/08/2014 16:55

Verify that the patch is installed.

Alternative use.

OSB PatchOSB patches are not applied via the BSU but uses the well-known Oracle OPatch tool.

Always download and install the latest OPatch version from MOS!

The OSB patch is 14389126: PS5 Bundle Patch 1 (11.1.1.6.1). (p14389126_111160_Generic.zip)

Check OSB 11g: Bundle Patch Reference [ID 1499170.1]

To validate that it has been installed:

You should see one product and one interim patch.

Create database schemas via the RCU

You most likely do not need a database with your OSB. It is only required if you want to use the OSBReporting features or the OWSM. Talk to your developers to check if they are using Report actions orOWSM policies.

You can see how to deal with a couple of issues if you are not using a database here.

For this installation I will use a database.

3 -patchlist=DYCA -verbose -install

12

./bsu.sh -prod_dir=/u01/app/oracle/product/osb/wlserver_10.3 -status=applied -verbose -view

12

. /u01/app/oracle/product/osb/wlserver_10.3/server/bin/setWLSEnv.shjava weblogic.version

12345678

export ORACLE_HOME=/u01/app/oracle/product/osb/Oracle_OSB1cd /u01/app/oracle/product/osb/Oracle_OSB1/OPatch./opatch | grep version unzip p6880880_111000_Linux-x86-64.zip -d /u01/app/oracle/product/osb/Oracle_OSB1 cd /u01/app/oracle/product/osb/Oracle_OSB1/OPatch./opatch | grep version

12345

export ORACLE_HOME=/u01/app/oracle/product/osb/Oracle_OSB1cd p14389126_111160_Generic/14389126/u01/app/oracle/product/osb/Oracle_OSB1/OPatch/opatch apply -jdk /u01/app/oracle/product/java_current -jre /u01/app/oracle/product/java_current/jre

12

cd /u01/app/oracle/product/osb/Oracle_OSB1/OPatch./opatch lsinventory


20 de 52 07/08/2014 16:55

First have a look at the documentation:Oracle Fusion Middleware Repository Creation Utility Users Guide

Check the database requirements and notice:

AL32UTF8 character setIf you use a database that does not use the AL32UTF8 character set the RCU will complain. As long as youare not using Oracle WebCenter or Oracle Identity Management you can ignore this.For more information see the RCU MOS FAQ: Oracle Fusion Middleware 11g Repository Creation Utility(RCU) FAQ [ID 1304790.1]

NLS_LENGTH_SEMANTICSOnly Byte length semantics is supported so if you use CHAR you probably need to use another database.See RCU 11g Fails When Creating Index on MDS_COMPONENTS ORA-01450: maximum key length(6398) exceeded [ID 987906.1]

SID != Service NameRCU uses the Service Name when connecting to a database, not the SID. The SID and the Service Name cancontain different values.You can find the Service Name in the database via:

Which schemas are required?To support OSB Reporting you need to select the SOA Infrastructure component in the RCU. I cannot findany documentation that states this though. You can get information about other FMW products here but theOSB is not mentioned.

Does anybody know where this information can be found?

TablespacesYou can create tablespaces via the RCU but I prefer to create them myself.A database will often have a default tablespace called USERS. It often ends up being a mess with all kind ofdifferent objects that nobody really knows why are there You should create separate tablespaces and use them after the kind of data that goes in them: Object size,growth rate, object type (Tables, LOBs, etc.)

Start the RCUcd ofm_rcu_linux_11.1.1.6.0_disk1_1of1/rcuHome/bin./rcu

12345

SQL> show parameter service_names NAME TYPE VALUE------------------------------------ ----------- ------------------------------service_names string xdb.egf

12

create smallfile tablespace OSB_REPO datafile'/u01/app/oracle/oradata/osb/osb_repo01.dbf' size 150m autoextend on next 100m maxsize 1g extent management local autoallocate;


21 de 52 07/08/2014 16:55


22 de 52 07/08/2014 16:55


23 de 52 07/08/2014 16:55


24 de 52 07/08/2014 16:55


25 de 52 07/08/2014 16:55


26 de 52 07/08/2014 16:55


27 de 52 07/08/2014 16:55


28 de 52 07/08/2014 16:55

Configure the OSB

The CONFIG_JVM_ARGS is set to speed things up if the system is low on entropy.

export CONFIG_JVM_ARGS=-Djava.security.egd=file:/dev/./urandomcd /u01/app/oracle/product/osb/oracle_common/common/bin./config.sh



29 de 52 07/08/2014 16:55


30 de 52 07/08/2014 16:55


31 de 52 07/08/2014 16:55


32 de 52 07/08/2014 16:55


33 de 52 07/08/2014 16:55


34 de 52 07/08/2014 16:55


35 de 52 07/08/2014 16:55


36 de 52 07/08/2014 16:55


37 de 52 07/08/2014 16:55


38 de 52 07/08/2014 16:55


39 de 52 07/08/2014 16:55


40 de 52 07/08/2014 16:55


41 de 52 07/08/2014 16:55


42 de 52 07/08/2014 16:55


43 de 52 07/08/2014 16:55


44 de 52 07/08/2014 16:55

Homes overview

There are many homes:

Application Home /u01/app/oracle/applications/osbDomain Home /u01/app/oracle/domains/osbMiddleware Home /u01/app/oracle/product/osbOracle Common Home /u01/app/oracle/product/osb/oracle_commonOracle OSB Home /u01/app/oracle/product/osb/Oracle_OSB1WebLogic Server Home /u01/app/oracle/product/osb/wlserver_10.3

For more information check the Oracle Fusion Middleware Installation Planning Guide.

Starting the servers

Start the Admin Server:

Waite till you see:

12

cd /u01/app/oracle/domains/osb./startWebLogic.sh


45 de 52 07/08/2014 16:55

Now you should be able to access the Admin Console:

http://wintermute:7001/console

Start the Managed Server in another terminal:

When it reaches the Running state check that all the deployments has state Active.

Java parametersYou can set Java memory parameters in several ways. Here I use setDomainEnv.sh in /u01/app/oracle/domains/osb/bin.I place the below just after all the comments in the top of the file:

Development Mode

Production Mode

1

12

cd /u01/app/oracle/domains/osb/bin./startManagedWebLogic.sh osb_server1

123456789

101112131415

# *************************************************************************# lorenzen Begin # *************************************************************************if [ "${SERVER_NAME}" = "" ] ; then SERVER_NAME="AdminServer" export SERVER_NAMEfiif [ "${SERVER_NAME}" = "AdminServer" ] ; then USER_MEM_ARGS="-Xms256m -Xmx768m -XX:MaxPermSize=350m -Djava.security.egd=file:/dev/./uranelif [ "${SERVER_NAME}" = "osb_server1" ] ; then USER_MEM_ARGS="-Xms768m -Xmx1024m -XX:MaxPermSize=350m -Djava.security.egd=file:/dev/./urafi# *************************************************************************# lorenzen End# *************************************************************************

123456789

101112131415

# *************************************************************************# lorenzen Begin # *************************************************************************if [ "${SERVER_NAME}" = "" ] ; then SERVER_NAME="AdminServer" export SERVER_NAMEfiif [ "${SERVER_NAME}" = "AdminServer" ] ; then USER_MEM_ARGS="-Xms256m -Xmx768m -XX:MaxPermSize=350m"elif [ "${SERVER_NAME}" = "osb_server1" ] ; then USER_MEM_ARGS="-Xms768m -Xmx1024m -XX:MaxPermSize=350m"fi# *************************************************************************# lorenzen End# *************************************************************************


46 de 52 07/08/2014 16:55

In Development Mode I have added a parameter to take care of any entropy problems.

If you are not running in Production Mode I always set debugFlag and ALSB_DEBUG_FLAG to false.If you do not do this you can get errors like the below, becuase several servers are trying to use the same port:

So add this:

This should do it:

If your developers need the debug ports, make sure each server uses unique ports.

Configuring the Node Manager

I always use the Node Manager (NM) to start and stop WebLogic servers.

1. Set NM user name and password

Use the Admin Console and navigate to the domain. Select Security and then Advanced. Set NodeManagerUsername and NodeManager Password:

2. Set the NM type to plain

The NM default uses SSL. I normally do not use SSL for the NM and if you do you should use valid SSLcertificates not the default demo certificates.Navigate to Environment => Machines => Machine_1 => Node Manager.Change Type to Plain.

123

ERROR: transport error 202: bind failed: Address already in useERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized

12

debugFlag="false"ALSB_DEBUG_FLAG="false"

12

sed -i 's/debugFlag="true"/debugFlag="false"/g' setDomainEnv.shsed -i 's/ALSB_DEBUG_FLAG="true"/ALSB_DEBUG_FLAG="false"/g' setDomainEnv.sh


47 de 52 07/08/2014 16:55

3. Stop the Admin Server and the Managed Server

Stop them via the Admin Console or just ctrl+c in the two terminals.

4. Start the NM

When you see:

Stop NM again with ctrl+c. The NM has now create its setup files and we need to make a couple of changesin nodemanager.properties in:/u01/app/oracle/product/osb/wlserver_10.3/common/nodemanager

Change these lines:

This should do it.

Start the NM again. Wait until you see:

In another terminal start the Admin Server:

12

cd /u01/app/oracle/product/osb/wlserver_10.3/server/bin./startNodeManager.sh

1 INFO: Secure socket listener started on port 5556

123456

javaHome=/u01/app/oracle/product/java_currentJavaHome=/u01/app/oracle/product/java_current/jreListenAddress=localhostSecureListener=falseCrashRecoveryEnabled=trueStartScriptEnabled=true

123456

sed -i 's/javaHome=.*/javaHome=\/u01\/app\/oracle\/product\/java_current/g'sed -i 's/JavaHome=.*/javaHome=\/u01\/app\/oracle\/product\/java_current\/jre/g'sed -i 's/ListenAddress=/ListenAddress=localhost/g' nodemanager.propertiessed -i 's/SecureListener=true/SecureListener=false/g' nodemanager.propertiessed -i 's/CrashRecoveryEnabled=false/CrashRecoveryEnabled=true/g' nodemanager.propertiessed -i 's/StartScriptEnabled=false/StartScriptEnabled=true/g' nodemanager.properties

1 INFO: Plain socket listener started on port 5556

12

. /u01/app/oracle/product/osb/wlserver_10.3/server/bin/setWLSEnv.shjava weblogic.WLST


48 de 52 07/08/2014 16:55

When the Admin Server is Running start the Managed Server via the Admin Console.

Notice that things are a bit different if you use Production Mode.

Configure automatic start of the servers

Now everything is running but of cause the NM should not be started manually but automatically when theserver boots.

Here is a very simple boot script:/etc/init.d/osbNodeManager

Java 7

Before switching to Java 7 you should read Using WebLogic Server with JDK 7.

The java_current soft link still points to Java 6 so we should change this:

Warnings in log files

When you start the OSB you will see a lot of warnings in the log files. Since they are warnings they can beignored. But it is nice to know what they mean. Some of them you can get rid of if you want to.

You are missing some MQ libraries. If you are not using MQ transport you can untarget the MQ TransportProvider application.See BEA-000000 & BEA-381917 Warning Messages During OSB Cluster Domain Admin Server Startup[ID 1074857.1]

If you are not using the provider it can be ignored. See Why Do We Get BEA-387042 Alert at ServerStart-up? [ID 1267945.1]

Metric table oracle_oim:overall has no key column. It will not be collected

There is nothing you can do about these messages. See After migration to FMW 11.1.1.6 and WLS 10.3.6,Warning Messages In Stdout When Weblogic Starts [ID 1434193.1]

UnicastUdpSocket failed to set send buffer sizeUnicastUdpSocket failed to set receive buffer sizePreferredUnicastUdpSocket failedMulticastUdpSocket failed

Coherence is complaining because the OS socket buffers are to small. You can increase them in/etc/sysctl.conf:

Run /sbin/sysctl -p

Oracle Coherence 3.7.1.1 (member=n/a): Local address 127.0.0.1 is a loopback address; this cluster node will not

If you dont use Coherence you can disable it via the SBConsole. Operations => Global settings. Remove thecheck mark from Enable Result Caching.

No test table set up for pool wlsbjmsrpDataSource. Connections will not be tested

You should change the Connection Pool for the Data Source to have SQL SELECT 1 FROM DUAL inTest Table Name.

Miscellaneous

You should audit the Logging settings for the domain and the servers to make sure log rotation is configured.Notice that .out log files cannot be rotated by WebLogic. The are only rotated when the servers are restarted.On Windows this is a problem on Linux not so much But make sure you developers know that:

You should configure Configuration Archiving for the domain. Domain => Configuration => General =>Advanced. Set Configuration Archive Enabled and Archive Configuration Count.When you change the configuration a backup of config.xml will be save so you can revert to an old version ifyou get in trouble.

Configure OCM

If your servers has access to the Internet OCM will automatically download the latest version. If not youshould download it yourself and install it manually.

12

net.core.rmem_max=4192608net.core.wmem_max=4192608

1 System.out.println("This is forbidden! Use Java Logging or Log4j");


50 de 52 07/08/2014 16:55

Verify that it is working:

Follow @theheatDKGoogle+

Leave a Comment

Name *

E-mail *

Website

{ 2 trackbacks }

Silent installation of the OSB on Red Hat 6Installing the Oracle SOA Suite on Red Hat 6

Previous post: Creating a Data Source via WLST Offline

Next post: Getting the size of the HTTP Session State in WebLogic

Archive

12345

. /u01/app/oracle/domains/osb/bin/setDomainEnv.shexport ORACLE_HOME=/u01/app/oracle/product/osb/utilsexport JAVA_HOME=/u01/app/oracle/product/java_currentcd $ORACLE_HOME/ccr/bin./setupCCR -s 12345678 [email protected] DK

123456789

cd $ORACLE_HOME/ccr/bin./emCCR start./emCCR status./emCCR -register test./emCCR -verbose test./emCCR register./emCCR collect./emCCR upload./emCCR disable_target


51 de 52 07/08/2014 16:55

Categories

Follow Me

Twitter

LinkedIn

Facebook

GoodReads

Last.fm


52 de 52 07/08/2014 16:55

Installing the Oracle OSB on Red Hat 6

Documents

Transcript of Installing the Oracle OSB on Red Hat 6