Installing the Oracle SOA Suite on Red Hat 6
•
1 like•705 views
The document describes the steps to install Oracle SOA Suite 11.1.1.7 on Red Hat 6 (64-bit) including: 1) Downloading and preparing the required software, installing Java, WebLogic Server, and the SOA Suite; 2) Configuring the installation including creating database schemas, configuring servers, and securing the installation; 3) Additional post-installation steps like patching the SOA Suite, configuring the Node Manager, and configuring automatic server startup.
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (13)
Similar to Installing the Oracle SOA Suite on Red Hat 6
Similar to Installing the Oracle SOA Suite on Red Hat 6 (20)
More from TUSHAR VARSHNEY
More from TUSHAR VARSHNEY (17)
Installing the Oracle SOA Suite on Red Hat 6
- 22. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 22/54 To find out if there exists any patches that you should install check “Information Center: Oracle SOA Suite 11g [ID 1369339.2]” on MOS and Known Issues for Oracle SOA Products and Oracle AIA Foundation Pack on OTN. Also make sure you check for SPU patches for the SOA Suite. Currently there are no SPU and no bundle patches for this release. When you patch the SOA Suite always remember to download and install the latest OPatch version from MOS. Create database schemas via the RCU First have a look at the documentation: Oracle Fusion Middleware Repository Creation Utility User’s Guide Also have a look at the RCU MOS FAQ: “Oracle Fusion Middleware 11g Repository Creation Utility (RCU) – FAQ [ID 1304790.1]” Check the database requirements. SID != Service Name RCU uses the Service Name when connecting to a database, not the SID. The SID and the Service Name can contain different values. You can find the Service Name in the database via: Which schema’s are required? To figure out which schema’s are required have a look at the documentation. Tablespaces You 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 of different 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 RCU cd ofm_rcu_linux_11.1.1.7.0_64_disk1_1of1/rcuHome/bin ./rcu 1 2 3 4 5 SQL> show parameter service_names NAME TYPE VALUE ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ service_names string xdb.egf 1 2 create smallfile tablespace SOA_REPO datafile'/u01/app/oracle/oradata/SOATST size 150m autoextend on next 100m maxsize 1g extent management local autoal
- 46. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 46/54 Now you should be able to access the Admin Console: http://wintermute:7001/console And the Fusion Middleware Control: http://wintermute:7001/em Start the Managed Server in another terminal: Input username and password when prompted. It takes a while before soa_server1 reaches the Running state and you will also see a some warnings/errors being reported. When it reaches the Running state check the status for the deployments in the Admin Server Console. The deployments should all have status Active. There will be a few that has status Installed. These are optional modules that default is not target to anything. For more information about which modules should be targeted where check the appendix “Targeting Applications and Resources to Servers“. Java parameters You can set Java memory parameters in several ways. I normally do it by setting USER_MEM_ARGS in DOMAIN_HOME/bin/startWebLogic.sh. For the SOA Suite the setSOADomainEnv.sh in the same directory overwrites USER_MEM_ARGS so for SOA Suite I use setSOADomainEnv.sh and PORT_MEM_ARGS. Development Mode Production Mode 1 <Server started in RUNNING mode> 1 2 cd /u01/app/oracle/domains/soa/bin ./startManagedWebLogic.sh soa_server1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 # ************************************************************************* # lorenzen Begin # ************************************************************************* if [ "${SERVER_NAME}" = "" ] ; then SERVER_NAME="AdminServer" export SERVER_NAME fi if [ "${SERVER_NAME}" = "AdminServer" ] ; then PORT_MEM_ARGS="‐Xms256m ‐Xmx768m ‐XX:MaxPermSize=350m ‐Djava.security.egd elif [ "${SERVER_NAME}" = "soa_server1" ] ; then PORT_MEM_ARGS="‐Xms768m ‐Xmx1536m ‐XX:MaxPermSize=768m ‐Djava.security.eg fi # ************************************************************************* # lorenzen End # ************************************************************************* 1 2 3 # ************************************************************************* # lorenzen Begin # *************************************************************************
- 48. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 48/54 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 “NodeManager Username” 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 SSL certificates not the default demo certificates. Navigate to Environment => Machines => machine_1 => Node Manager. Change Type to Plain. 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 it’s setup files and we need to make a couple of changes in nodemanager.properties in: /u01/app/oracle/product/soa/wlserver_10.3/common/nodemanager Change these lines: 1 2 cd /u01/app/oracle/product/soa/wlserver_10.3/server/bin ./startNodeManager.sh 1 INFO: Secure socket listener started on port 5556 1 2 javaHome=/u01/app/oracle/product/java_current JavaHome=/u01/app/oracle/product/java_current/jre
- 49. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 49/54 This should do it. Start the NM again. Wait until you see: 5. Start the Admin Server In another terminal start the Admin Server: 6. Start the Managed Server 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 the server boots. Here is a very simple boot script: /etc/init.d/soaNodeManager Java 7 2 3 4 5 6 JavaHome=/u01/app/oracle/product/java_current/jre ListenAddress=localhost SecureListener=false CrashRecoveryEnabled=true StartScriptEnabled=true 1 2 3 4 5 6 sed ‐i 's/javaHome=.*/javaHome=/u01/app/oracle/product/java_current/g' sed ‐i 's/JavaHome=.*/javaHome=/u01/app/oracle/product/java_current/jr sed ‐i 's/ListenAddress=/ListenAddress=localhost/g' nodemanager.properties sed ‐i 's/SecureListener=true/SecureListener=false/g' nodemanager.properties sed ‐i 's/CrashRecoveryEnabled=false/CrashRecoveryEnabled=true/g' nodemanage sed ‐i 's/StartScriptEnabled=false/StartScriptEnabled=true/g' nodemanager.pr 1 INFO: Plain socket listener started on port 5556 1 2 3 4 . /u01/app/oracle/product/soa/wlserver_10.3/server/bin/setWLSEnv.sh java weblogic.WLST nmConnect(username='nodemgr', password='manager2', domainName='soa', domainD nmStart('AdminServer') 1 2 3 4 5 cd /etc/init.d chmod 755 soaNodeManager chkconfig ‐‐add soaNodeManager chkconfig ‐‐list soaNodeManager ./soaNodeManager start
- 50. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 50/54 Because of the mentioned problem with Xming I have used Java 6 during the installation. 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: AQ errors When you start the WebLogic server you might encounter errors like these in the log files. There are more than 20 AQ queues in the schemas the RCU has created. Have a look. For these initial errors errors to go away you only need to enable enqueue/dequeue on 3 of them. 1 2 3 4 5 6 mkdir /u01/app/oracle/product/jdk1.7.0_25/jre/lib/endorsed cd /u01/app/oracle/product/soa/modules cp javax.annotation_* /u01/app/oracle/product/jdk1.7.0_25/jre/lib/endorsed cp javax.xml.bind_* /u01/app/oracle/product/jdk1.7.0_25/jre/lib/endorsed cp javax.xml.ws_* /u01/app/oracle/product/jdk1.7.0_25/jre/lib/endorsed ls /u01/app/oracle/product/jdk1.7.0_25/jre/lib/endorsed 1 2 3 rm ‐f /u01/app/oracle/product/java_current ln ‐s /u01/app/oracle/product/jdk1.7.0_25 /u01/app/oracle/product/java_curre ls ‐l /u01/app/oracle/product/java_current 1 2 3 4 5 6 <Jul 13, 2013 12:29:35 PM CEST> <Warning> <oracle.integration.platform.block java.sql.SQLException: ORA‐25226: dequeue failed, queue DEV_SOAINFRA.EDN_OAO ORA‐06512: at "SYS.DBMS_AQ", line 335 ORA‐06512: at "DEV_SOAINFRA.EDN_DEQUEUE_OAOO_DELIVERY", line 14 ... > 1 <Jul 13, 2013 12:29:10 PM CEST> <Error> <oracle.soa.b2b.transport> <BEA‐0000 1 2 3 4 5 6 7 8 9 set pagesize 1000 set linesize 1000 select owner, name, enqueue_enabled, dequeue_enabled from dba_queues where owner like 'DEV%' order by owner, name; 1 2 3 exec dbms_aqadm.start_queue(queue_name => 'DEV_SOAINFRA.EDN_OAOO_QUEUE',enqu exec dbms_aqadm.start_queue(queue_name => 'DEV_SOAINFRA.IP_OUT_QUEUE',enqueu exec dbms_aqadm.start_queue(queue_name => 'DEV_SOAINFRA.IP_IN_QUEUE',enqueue
- 51. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 51/54 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 the old configuration files will automatically be save so you can revert to an old version if you get in trouble. Securing your installation Have a look at Oracle Fusion Middleware Securing a Production Environment for Oracle WebLogic Server 11g It is of cause only the top of the iceberg but is a start. Configure OCM If your servers has access to the Internet OCM will automatically download the latest version. If not you should download it yourself and install it manually. Verify that it is working: Feedback If you feel that I am missing something or find mistakes please tell me. I always want to learn! 1 System.out.println("This is forbidden! Use Java Logging or Log4j"); 1 2 3 4 5 . /u01/app/oracle/domains/soa/bin/setDomainEnv.sh export ORACLE_HOME=/u01/app/oracle/product/soa/utils export JAVA_HOME=/u01/app/oracle/product/java_current cd $ORACLE_HOME/ccr/bin ./setupCCR ‐s 12345678 nobody@cgi.com DK 1 2 3 4 5 6 7 8 9 cd $ORACLE_HOME/ccr/bin ./emCCR start ./emCCR status ./emCCR ‐register test ./emCCR ‐verbose test ./emCCR register ./emCCR collect ./emCCR upload ./emCCR disable_target
- 52. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 52/54 Follow @theheatDK Google+ { 6 comments… read them below or add one } Chandra October 9, 2013 at 14:54 Peter, Thanks for the nice article..I see you have set two linux kernel parameters(net.core.rmem_max and net.core.wmem_max)..I am not seeing them in the installation guide..Did oracle recommended them? Thanks/Chandra Peter Lorenzen October 13, 2013 at 17:09 Hi Chandra, That is a very good question and it took me a while to remember why It is only when you use Coherence you need to set thous. See http://theheat.dk/blog/? p=1140#warnings and The Error “java.net.SocketException: No Buffer Space Available” is Reported when Starting Coherence (Doc ID 1150113.1). I will write a comment in the post about this. Thanks Regards Peter jyothi October 25, 2013 at 06:05 Very nice blog. Very explanatory and covered many critical topics which we usually forget to do. thank you for your great effort. thanks. Ravi Kishore August 18, 2014 at 10:09 I was searching for an article into soa installation and ended up here. You done a great job by explaining each and every step clearly. Thanks for the information Peter. About to install SOA on Oracle Linux 6.4 version in VMware. Will post comments if i miss anything. Once again thanks dude. vinodh October 8, 2014 at 10:29 Hi Team, Thank you for your great article.
- 53. 1/19/2016 Installing the Oracle SOA Suite on Red Hat 6 http://theheat.dk/blog/?p=1052 53/54 i have small doubet. My database team moved the oracle database from one unix to onther unix box. how can i reconfigure SOA servers to access the database in new unix box? Is changing the datasource is enough or do i have to configure all this thing like configuring RCU? Thanks In advance. Peter Lorenzen October 8, 2014 at 13:03 Yes all you need to do is to change the connection pool in the data sources. Regards Peter Leave a Comment Name * Email * Website Submit Previous post: Create a CA, issue server/client certificates and test them via Apache Next post: Installing the Oracle OSB on Red Hat 6 Archive Archive Select Month Categories Categories Select Category Follow Me Twitter LinkedIn