Search in book...
Toggle Font Controls
Create new playlist

Name your new playlist

Playlist description (optional)
Sign In

Email address

Password

Forgot Password?

or

Continue with Facebook

Continue with Google
Sign Up

Full Name

Email address

Confirm Email Address

Password

or

Continue with Facebook

Continue with Google

Installing Oracle SOA Suite

Oracle SOA Suite is installed on a shared storage. Follow the next steps to install Oracle SOA Suite:

On SOAHOST1, start the SOA installer:

source envMidTier.sh
$JAVA_HOME/bin/java -d64 -jar $SOFTWARE_DIR/fmw_12.1.3.0.0_soa.jar

In the Inventory Directory field, enter /u01/share/oracle/oraInventory and then click on OK.
Click on Next.
In the Oracle Home field, enter the value for [ORACLE_HOME] (for example, /u01/share/oracle/middleware/products/fmw1213) and then click on Next.
Select SOA Suite and then click on Next.
Click on Next.
Click on Install.
Click on Finish once the installation is done.

Creating Oracle SOA Suite database schemas

To create the SOA database schemas, use the following steps:

On SOAHOST1, start the RCU:

source envMidTier.sh
cd $ORACLE_HOME/oracle_common/bin
./rcu

Click on Next.
Select Create Repository and choose System Load and Product Load, and then click on Next.
Enter your database information as shown in Figure 12.2, and click on Next.
Click on OK to confirm the validation of the global prerequisites.
Select Select existing prefix and then choose DEV.
Click on the SOA Suite checkbox and then click on Next.
Click on OK to confirm the validation of the component prerequisites.
In the password fields, enter a password (for example., welcome1) and then click on Next.
Change the value from SMALL to LARGE and then click on Next.
Click on Next.
If prompted to create tablespaces, click on OK.
Click on OK to confirm the validation and creation of the tablespaces.
Click on Create.
Click on Close once the RCU is complete.

Configuring SOA schemas for transaction recovery

Follow these steps to configure SOA schemas for transaction recovery:

On the database server, start SQL*Plus as the sysdba:
```
sqlplus "/ as sysdba"
```
On the SQL*Plus prompt, run the following commands:
```
GRANT select ON sys.dba_pending_transactions TO DEV_soainfra;
GRANT force any transaction TO DEV_soainfra;
```
Figure 12.5. Executing SQL commands from the SOA database host

Extending the domain with Oracle SOA Suite

To extend the domain with Oracle SOA suite, follow these steps:

On SOAHOST1, stop the Admin Server:

source envMidTier.sh
$ASERVER_HOME/bin/stopWebLogic.sh

Start the WebLogic Server Configuration Wizard:

cd $ORACLE_HOME/oracle_common/common/bin
./config.sh

Click on Update an existing domain.
In the Domain Location field, enter [ASERVER_HOME] (for example, /u01/share/oracle/middleware/config/domains/soa_domain).
Click on Next.
Check Oracle SOA Suite – 12.1.3.0 [soa] and then click on Next.
Click on Get RCU Configuration.
Click on Next.
Click on Next.
Click on Next.
Check Managed Servers, Clusters and Coherence, and JMS File Store, and then click on Next.
Rename soa_server1 as wls_soa1.
Change Listen Address to soahost1.packt.com.
Change port 7003 to 8001.
Under Server Groups, select only SOA-MGD-SVRS-ONLY.
Click on Add and then enter wls_soa2, soahost2.packt.com, and 8001; then select only SOA-MGD-SVRS-ONLY.
Click on Next.
Click on Add.
For Cluster Name, enter SOA_Cluster.
For Frontend Host, enter soa.packt.com.
For Frontend HTTP Port, enter 7777.
For Frontend HTTPS Port, enter 4443.
Click on Next.
Assign wls_soa1 and wls_soa2 to SOA_Cluster and then click on Next.
Click on Next.
Click on Next.
Assign wls_soa1 to the soahost1 machine.
Assign wls_soa2 to the soahost2 machine.
Click on Next.
Assign the [ASERVER_HOME]/SOA_Cluster/jms directory (for example, /u01/share/oracle/middleware/config/domains/soa_domain/SOA_Cluster/jms) for each of the SOA persistence store directories except for mds-owsm.
Click on Next.
Click on Update.
Click on Next.
Click on Finish.

Configuring the default persistence store for transaction recovery

Follow the next steps to configure the default persistence store for transaction recovery:

On SOAHOST1, start the Admin Server:

source envMidTier.sh
cd $ASERVER_HOME/servers/AdminServer/logs
nohup $ASERVER_HOME/bin/startWebLogic.sh > AdminServer.out &

Navigate to http://admin.packt.com:7001/console.
Log in as the weblogic user.
Navigate to soa_domain | Environment | servers | wls_soa1 | Configuration | Services.
In the Directory field, enter [ASERVER_HOME]/SOA_Cluster/tlogs (for example, /u01/share/oracle/middleware/config/domains/soa_domain/SOA_Cluster/tlogs).
Repeat steps 3 and 4 for wls_soa2.
Shut down the wls_wsm1 and wls_wsm2 managed servers.
Save and activate the changes.
Start up the wls_wsm1 and wls_wsm2 managed servers.

Propagating the domain to the domain directories and machines

Use the following steps to propagate the domain to the domain directories and machines:

On SOAHOST1, pack and unpack the domain:

source envMidTier.sh
cd $ORACLE_COMMON_HOME/common/bin

./pack.sh -managed=true -domain=${ASERVER_HOME} -template=soadomaintemplateExtSOA.jar -template_name=soadomaintemplateExtSOA

./unpack.sh -domain=${MSERVER_HOME} -overwrite_domain=true -template=soadomaintemplateExtSOA.jar -app_dir=${APPLICATION_HOME}

On SOAHOST2, unpack the domain:

source envMidTier.sh
cd $ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=${MSERVER_HOME} -overwrite_domain=true -template=soadomaintemplateExtSOA.jar -app_dir=${APPLICATION_HOME}

On SOAHOST1, start the SOA managed server:

source envMidTier.sh
cd $MSERVER_HOME/servers/wls_soa1/logs

nohup $MSERVER_HOME/bin/startManagedWebLogic.sh wls_soa1 http://admin.packt.com:7001 > wls_soa1.out &

On SOAHOST2, start the SOA managed server:

source envMidTier.sh
cd $MSERVER_HOME/servers/wls_soa2/logs

nohup $MSERVER_HOME/bin/startManagedWebLogic.sh wls_soa2 http://admin.packt.com:7001 > wls_soa2.out &

Configuring Oracle HTTP Server for Oracle SOA Suite

Follow these steps to configure Oracle HTTP ${MSERVER_HOME}:

On SOAHOST1, edit the soa_vh.conf file:

source envMidTier.sh
vi $OHS_ADMIN_CONFIG_DIR/moduleconf/soa_vh.conf

Add the OHS routing rules for SOA, OSB, WSM, and ESS:

<VirtualHost webhost1.packt.com:7777>
  ServerName soa.packt.com:7777
  ServerAdmin [email protected]
  RewriteEngine On
  RewriteOptions inherit
  # SOA Infra
  <Location /soa-infra>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  # SOA inspection.wsil
  <Location /inspection.wsil>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  # Worklist
  <Location /integration>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  # UMS prefs
  <Location /sdpmessaging/userprefs-ui>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  # Default to-do taskflow
  <Location /DefaultToDoTaskFlow>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  # Workflow
  <Location /workflow>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  #Required if attachments are added for workflow tasks
  <Location /ADFAttachmentHelper>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  # SOA composer application
  <Location /soa/composer>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  <Location /frevvo>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8001,soahost2.packt.com:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  <Location /ess>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8021,soahost2.packt.com:8021
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
  <Location /EssHealthCheck>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:8021,soahost2.packt.com:8021
    WLProxySSL ON
    WLProxySSLPassThrough ON
  </Location>
</VirtualHost>
<VirtualHost webhost1.packt.com:7777>
  ServerName soainternal.packt.com:7777
  ServerAdmin [email protected]
  RewriteEngine On
  RewriteOptions inherit
  # WSM-PM
  <Location /wsm-pm>
    SetHandler weblogic-handler
    WebLogicCluster soahost1.packt.com:7010,soahost2.packt.com:7010
  </Location>
</VirtualHost>

Repeat steps 1 and 2 on SOAHOST2, replacing all occurrences of webhost1 with webhost2.

On SOAHOST1, stop and start the Admin Server to propagate the changes to WebTier:

source envMidTier.sh
$ASERVER_HOME/bin/stopWebLogic.sh
cd $ASERVER_HOME/servers/AdminServer/logs
nohup $ASERVER_HOME/bin/startWebLogic.sh > AdminServer.out &

Log in to http://admin.packt.com:7001/em.
Expand HTTP Server.
Click on ohs_1, then click on Shut Down then Start Up.
Click on ohs_2, then click on Shut Down and Start Up.
Validate that the following URLs are accessible:
http://soahost1.packt.com:8001/soa-infra
http://soahost2.packt.com:8001/soa-infra
http://soa.packt.com:7777/soa-infra
http://soa.packt.com:7777/integration/worklistapp
http://soa.packt.com:7777/sdpmessaging/userprefs-ui
http://soa.packt.com:7777/soa/composer
http://soa.packt.com:7777/integration/services/IdentityService/identity?WSDL

Configuring the WebLogic proxy plug-in

Follow these steps to configure the WebLogic proxy plug-in:

Navigate to http://admin.packt.com:7001/console.
Log in as the weblogic user.
Navigate to soa_domain | Environment | Clusters | SOA_Cluster | Configuration | General | Advanced.
For WebLogic Plug-In Enabled, set the value to yes.
Save and activate the changes.
Restart the wls_soa1 and wls_soa2 managed servers.

Configuring the Oracle File Adapter for Oracle SOA Suite

To configure the Oracle File Adapter, follow these steps:

On SOAHOST1, run the following commands to create the shared deploy plan directory:
```
source envMidTier.sh
mkdir -p $DEPLOY_PLAN_HOME/soaedg_domain
```
Navigate to http://admin.packt.com:7001/console.
Log in as the weblogic user.
Navigate to Deployments | FileAdapter | Configuration | Outbound Connection Pools.
Expand javax.resource.cci.ConnectionFactory.
Click on eis/HAFileAdapter.
For the controlDir property, enter the value [ASERVER_HOME]/SOA_Cluster/fadapter (for example, /u01/share/oracle/middleware/config/domains/soa_domain/SOA_Cluster/fadapter).
Click on Save.
On the Save Deployment Plan Assistant page, enter the Path [DEPLOY_PLAN_HOME]/soaedg_domain/FileAdapterPlan.xml (for example, /u01/share/oracle/middleware/config/dp/soaedg_domain/FileAdapterPlan.xml).
Click on OK.
Save and activate the changes.

Configuring the Oracle FTP Adapter for Oracle SOA Suite

To configure the Oracle FTP Adapter, follow these steps:

On the WebLogic Server Administration Console, click on Deployments.
Navigate to Deployments | FtpAdapter | Configuration | Outbound Connection Pools.
Expand javax.resource.cci.ConnectionFactory.
Click on eis/Ftp/HaFtpAdapter.
For the controlDir property, enter the value [ASERVER_HOME]/SOA_Cluster/fadapter (for example, /u01/share/oracle/middleware/config/domains/soa_domain/SOA_Cluster/fadapter).
Click on Save.
On the Save Deployment Plan page, enter the Path [DEPLOY_PLAN_HOME]/soaedg_domain/FtpAdapterPlan.xml (for example, /u01/share/oracle/middleware/config/dp/soaedg_domain/FtpAdapterPlan.xml).
Click on OK.
Save and activate the changes.

Configuring the Oracle JMS Adapter for Oracle SOA Suite

Follow these steps to configure the Oracle JMS Adapter:

On the WebLogic Server Administration Console, click on Deployments.
Navigate to Deployments | JmsAdapter | Configuration | Outbound Connection Pools.
Expand oracle.tip.adapter.jms.IJmsConnectionFactory.
Click on eis/wls/Queue.
In the FactoryProperties property, enter: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://soahost1.packt.com:8001,soahost2.packt.com:8001;java.naming.security.principal=weblogic;java.naming.security.credentials=welcome1
Click on Save.
On the Save Deployment Plan page, enter the Path [DEPLOY_PLAN_HOME]/soaedg_domain/JmsAdapterPlan.xml (for example, /u01/share/oracle/middleware/config/dp/soaedg_domain/JmsAdapterPlan.xml).
Click on OK.
Save and activate the changes.
Navigate to Deployments | JmsAdapter | Configuration | Outbound Connection Pools.
Expand oracle.tip.adapter.jms.IJmsConnectionFactory.
Click on eis/wls/Topic.
In the FactoryProperties property, enter: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://soahost1.packt.com:8001,soahost2.packt.com:8001;java.naming.security.principal=weblogic;java.naming.security.credentials=welcome1
Click on Save.
Click on Deployments.
Check the checkbox beside JmsAdapter.
Click on Update.
Click on Finish.
Activate the changes.
Restart the wls_soa1 and wls_soa2 managed servers.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.

Table of Contents for Installing Oracle SOA Suite

Create new playlist

Sign In

Sign Up