Introduction
This document covers the installation of Oracle SOA Suite Server for ReadSoft PROCESSIT. The installation procedure is chronological, so each step should be performed in the sequence appearing in this document.
For details regarding PROCESSIT workflow installation, please refer to the standard PROCESSIT installation guide.
PROCESSIT uses Oracle BPEL Process Manager (a component of Oracle SOA Suite) 11.1.1.7 patched to the latest level.
Typographic conventions
Please note that all commands that should be typed are presented like this
.
Recommendations
If installing on VMware we recommend that you take snapshots at various points throughout the installations to avoid restarting if something goes wrong.
SOA Software Install
Prerequisites
Dehydration Store / PROCESSIT Database must be installed and available prior to SOA installation.
Software setup
Download
- Download the files from ftp.readsoft.us.com/Software/Oracle/PROCESSIT/Prereqs11g/Linux/.
- Move all the files to a staging directory.
- Make sure that the oracle user owns all the files, for instance with the command
chown -R oracle:oracle *
Login to the server
Log in to the server where you wish to install SOA Suite Server software using the user oracle.
Repository Creation Utility
- Unzip the file ofm_rcu_linux_11.1.1.7.0_64_disk1_1of1.zip.
- Change to the rcuHome/bin directory.
./rcu
- Welcome. Click Next.
- Create Repository. Select Create and click Next.
- Database Connection Details. Enter connection information for the database for the repository. This should match the database installed previously. Click Next when complete.
- Host Name
- port
- Service Name
- Username
- Password
- Checking Prerequisites. Click OK.
- Select Components.
- Select the text entry box for Create a new Prefix and enter RS .
- Under Component, select SOA and BPM Infrastructure. The dependent components are automatically selected.
- Click Next.
- Checking Prerequisites. Click OK
- Schema Passwords.
- Select Specify different passwords for all schema.
- Enter and confirm passwords for each of the requested schemas.
- Click Next.
- Map Tablespaces. Click Next.
- Confirmation. Click OK.
- Creating Tablespaces. Click OK.
- Summary. Click Create.
- Completion Summary. Click Close.
Oracle SOA Suite 11.1.1.7 Installation
unzip the files ofm_soa_generic_11.1.1.7.0_disk1_1of2.zip and ofm_soa_generic_11.1.1.7.0_disk1_2of2.zip
You must run the following procedure in a GUI Environment.
Run the SOA installer
You must run this in a GUI console Environment.
cd /oracle/Stage/soa/Disk1
./runInstaller
- Enter the JRE locate. This can vary depending on JDK installed.
- The SOA installer is shown.
- Welcome. Click Next.
- Install Software Updates. Select Skip Software Updates and click Next.
- Prerequisite Checks. Click Next.
- Specify Installation Directory.
- Oracle Midleware Home:
/oracle/middleware
- Oracle Home Directory:
Oracle_SOA1
- Click Next.
- Oracle Midleware Home:
- Application Server. Click Next.
- Installation Summary. Click Install.
- Installation Progress. Click Next.
- Installation Complete. Click Finish.
Create Domain
- Execute the WebLogic Configuration Wizard.
/oracle/middleware/wlserver_10.3/common/bin/config.sh
- Welcome. Select Create a new WebLogic Domain and click Next.
- Select Domain Source. Select Oracle SOA Suite - 11.1.1.0 [Oracle_SOA1], Oracle Enterprise Manager - 11.1.1.0 [oracle_common] and click Next.
- Specify Domain Name and Location. Enter
d4
for Domain Name and click Next. - Configure Administrator User Name and Password. Enter and confirm the password for the admin user, weblogic, and click Next.
- Configure Server Start Mode and JDK. Select Development Mode for WebLogic Domain Startup Mode and select the JDK install previously, then click Next.
- Configure JDBC Component Schema. Only one Component Schema at a time should be checked.
- Check SOA Infrastructure and complete the fields above with the appropriate connection details. The Schema Owner will be RS_SOAINFRA.
- Check User Messaging Service and complete the fields above with the appropriate connection details. The Schema Owner will be RS_ORASDPM.
- Check OWSM MDS Schema and complete the fields above with the appropriate connection details. The Schema Owner will be RS_MDS.
- Check SOA MDS Schema and complete the fields above with the appropriate connection details. The Schema Owner will be RS_MDS.
- When all Component Schemas have been updated, click Next.
- Test JDBC Component Schema. Click Next.
- Select Optional Configuration.
- Check Managed Servers, Clusters and Machines, and Deployments and Services and click Next.
- Configure Managed Servers.
- Click Add
- Enter processit_server1 for the Name. The Listen Port should be 7003.
- Click Next.
- Configure Clusters
- Click Add.
- Enter processit_cluster for the Name. The Cluster messaging mode should be unicast.
- Click Add.
- Enter soa_cluster for the Name. The Cluster messaging mode should be unicast.
- Click Next.
- Assign Servers to Clusters
- Click processit_cluster in the right pane.
- Click processit_server1 in the left pane.
- Click the right arrow button between the panes.
- Click soa_cluster in the right pane.
- Click soa_server1 in the left pane.
- Click the right arrow button between the panes.
- Click Next.
- Configure Machines
- Enter a name to identify the machine to the domain. The default is LocalMachine.
- Click Next.
- Assign Servers to Machines
- Select machine defined in previous screen in the right pane.
- Click AdminServer in the left pane.
- Click the right arrow button between the panes.
- Click processit_server1 in the left pane.
- Click the right arrow button between the panes.
- Click Next.
- Target Deployments to Clusters or Servers
- Select processit_cluster in the left pane.
- Check the box in the right pane for the following components:
- DbAdapter
- oracle.jsp.next
- oracle.adf.dconfigbeans
- oracle.jrf.system.filter
- adf.oracle.domain
- adf.oracle.businesseditor
- oracle.adf.mangement
- adf.oracle.domain.webapp
- jsf
- jstl
- oracle.adf.desktopintegration.model
- oracle.adf.desktopintegration
- Click Next.
- Target Services to Clusters or Servers
- Select processit_cluster in the left pane.
- Check the box in the right pane for the following components:
- JOC-Shutdown
- JRF Startup Class
- JPS Startup Class
- ODL Startup
- AWT Application Context Startup Class
- JMX Framework Startup Class
- JOC-Startup
- mds-soa
- Click Next.
- Configuration Summary. Click Create.
- Creating Domain: Click Done.
The base installation process is now complete.
Apply Patches to Install
p18277370
Unzip the file p18277370_111170_Generic.zip
Change directory to p18277370_111170_Generic/18277370/oui/18277370
Apply patch by executing the following command:
/oracle/middleware/oracle_common/Opatch/opatch apply
Answer the question Ist the local system ready for patching? [y|n] by entering Y.
Logs directory
Create logs directory
mkdir -p ~/logs
Node Manager Setup
Create boot.properties file for AdminServer
export DOMAIN_HOME=/oracle/middleware/user_projects/domains/d4
mkdir -p $DOMAIN_HOME/servers/AdminServer/security
vi $DOMAIN_HOME/servers/AdminServer/security/boot.properties
The contents of the file should be like below:
username=weblogic
password=weblogic1
Start Node Manager
nohup $WLS_HOME/server/bin/startNodeManager.sh >~/logs/nodemanager.log 2>&1 &
Start AdminServer
nohup $DOMAIN_HOME/startWebLogic.sh >~/logs/weblogic.log 2>&1 &
tail -f ~/logs/weblogic.log
Wait for a few minutes and look out for the following to ensure the Admin Server starts up correctly (CTRL+C to exit from the tail command above):
<BEA-000360> <Server started in RUNNING mode>
Add boot.properties for Managed Servers
mkdir -p $DOMAIN_HOME/servers/processit_server1
cp $DOMAIN_HOME/servers/AdminServer/security/boot.properties $DOMAIN_HOME/servers/processit_server1
mkdir -p $DOMAIN_HOME/servers/soa_server1
cp $DOMAIN_HOME/servers/AdminServer/security/boot.properties $DOMAIN_HOME/servers/soa_server1
Start the Managed Servers
- processit_server1
nohup $DOMAIN_HOME/startWebLogic.sh >~/logs/processit_ms.log 2>&1 &
tail -f ~/logs/processit_ms.log
Wait for a few minutes and look out for the following to ensure the Managed Server starts up correctly (CTRL+C to exit from the tail command above):
<BEA-000360> <Server started in RUNNING mode>
- soa_server1
nohup $DOMAIN_HOME/startWebLogic.sh >~/logs/soa_ms.log 2>&1 &
tail -f ~/logs/soa_ms.log
Wait for a few minutes and look out for the following to ensure the Managed Server starts up correctly (CTRL+C to exit from the tail command above):
<BEA-000360> <Server started in RUNNING mode>
Sample scripts to start domain
startDomain.sh
# Set environment variables
export MW_HOME=/oracle/middleware
export WLS_HOME=$MW_HOME/wlserver_10.3
export DOMAIN_NAME=d4
export DOMAIN_HOME=$MW_HOME/user_projects/domains/$DOMAIN_NAME
echo Starting Node Manager...
nohup $WLS_HOME/server/bin/startNodeManager.sh > ~/logs/nodemanger.log 2>&1 &
sleep 10
echo Starting WebLogic Admin Server...
nohup $DOMAIN_HOME/bin/startWebLogic.sh > ~/logs/nodemanger.log 2>&1 &
sleep 120
echo Starting WebLogic Managed Servers...
echo Starting WebLogic Managed Server : processit_server1
nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh processit_server1 > ~/logs/processit_ms.log 2>&1 &
echo Starting WebLogic Managed Server : soa_server1
nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1 > ~/logs/soa_ms.log 2>&1 &
echo Done!
stopDomain.sh
# Set environment variables
export MW_HOME=/oracle/middleware
export WLS_HOME=$MW_HOME/wlserver_10.3
export DOMAIN_NAME=d4
export DOMAIN_HOME=$MW_HOME/user_projects/domains/$DOMAIN_NAME
echo Stopping WebLogic Managed Servers...
echo Stopping WebLogic Managed Server : soa_server1
$DOMAIN_HOME/bin/stopManagedWebLogic.sh soa_server1
echo Stopping WebLogic Managed Server : processit_server1
$DOMAIN_HOME/bin/stopManagedWebLogic.sh processit_server1
echo Stopping WebLogic Admin Server...
$DOMAIN_HOME/bin/stopWebLogic.sh
echo Stopping Node Manager...
nm_pid=`ps -ef | grep [N]odeManager | awk '{print $2}'`
if [ "$nm_pid" = "" ];
then echo Node Manager not running
else echo Killing Node Manager processes: $nm_pid
kill -9 $nm_pid 2>&1 > /dev/null
fi
echo "Tidying up temp files..."
find $DOMAIN_HOME/servers -name "*.lok" -exec rm -f {} ;
find $DOMAIN_HOME/servers -name "*.DAT" -exec rm -f {} ;
echo Done!