Skip to content
This repository has been archived by the owner on Jan 12, 2021. It is now read-only.

ConfigNow SOA Suite Guide

sandychunchu edited this page Mar 8, 2017 · 2 revisions
<title></title> <style type="text/css">code{white-space: pre;}</style>

SOA Suite Functionality

The ConfigNOW solution has specific extensions to support the installation and configuration of Oracle SOA Suite 11g instances, the details of which are below.

Installing the SOA Suite Using ConfigNOW

The installation and configuration of the Oracle SOA Suite in ConfigNOW is defined as a multi-step process. While it is possible to define the entire process to run as a single ConfigNOW command, we have historically found that due to the complexity of the SOA Suite environment it makes more sense to run the installation as a set of discrete steps.

Note that if you have already installed the SOA Suite, then steps 1 to 4 can be skipped and you can move straight to the process of configuring the domain.

Step 1 - Install WebLogic Server

The first step in the process is to install the core WebLogic Server. To do this you run the install_weblogic command in ConfigNOW. This step is only required if you do not already have the WebLogic Instance installed.

confignow install.weblogic local soa11g
-Dwls.install.file=C:\installers\wls1034_generic.jar

For more details on installing WebLogic using ConfigNOW please refer to the ConfigNOW User Guide.

Step 2 – Run the Repository Creation Utility

The repository creation utility is used to set up the necessary database tables to support the SOA Suite.

This step is required to be run before installing the SOA Suite, but can also be run again at a later stage if you wish to re-create the SOA Suite database repositories.

confignow run_rcu local soa11g

-Drcu.home=C:\temp\ofm_rcu_win_11.1.1.3.0_disk1_1of1\rcuHome

For more details on running RCU using ConfigNOW see the ConfigNOW User Guide.

Step 3 - Install SOA Suite (11g Release 1)

Depending on the version of the SOA Suite that you are using, the ConfigNOW commands to run are slightly different.

To install SOA Suite 11gR1 patch set 4:

confignow install_soa_suite local soa11g
-Dsoa.suite.install.part1.zip=C:/temp/ofm_soa_generic_11.1.1.5.0_disk1_1of2.zip
-Dsoa.suite.install.part2.zip=C:/temp/ofm_soa_generic_11.1.1.5.0_disk1_2of2.zip

To install SOA Suite 11gR1 patch set 3:

confignow install_soa_suite local soa11g
-Dsoa.suite.install.part1.zip=C:/temp/ofm_soa_generic_11.1.1.4.0_disk1_1of2.zip
-Dsoa.suite.install.part2.zip=C:/temp/ofm_soa_generic_11.1.1.4.0_disk1_2of2.zip

To install SOA Suite 11g patch set 2 follow the two step process which involves first installing patch set 1

confignow install_soa_suite local soa11g
-Dsoa.suite.install.dir=C:/temp/ofm_soa_generic_11.1.1.2.0_disk1_1of1/Disk1

confignow install_soa_suite local soa11g
-Dsoa.suite.install.dir=C:/temp/ofm_soa_generic_11.1.1.3.0_disk1_1of1/Disk1

To install SOA Suite 11g patch set 1:

confignow install_soa_suite local soa11g
-Dsoa.suite.install.dir=C:/temp/ofm_soa_generic_11.1.1.2.0_disk1_1of1/Disk1

For more details on installing SOA Suite using ConfigNOW see the ConfigNOW Command Reference.

Step 4 – Create the Domain

The final step in the process is to create the SOA Suite domain. If you have previously installed the SOA Suite either via steps 1 to 4 of this process or separately, then you can run this command at any time to recreate the actual SOA Suite domain.

confignow create_domain local soa11g

SOA Suite Composite Deployment

As well as the creation of the domain, ConfigNOW also includes functionality to enable the deployment of SOA composite applications. In order for SOA Suite composite deployments to work you must have the following properties defined in your ConfigNOW environment configuration file. The properties required for a SOA Suite domain as contained in the ConfigNOW template file soa11g_template.properties can be overwritten as required in your own properties files.

  • soa.home – The absolute path to your SOA Suite home directory, eg. c:/oracle/middleware/Oracle_SOA1

The following properties are optional, but make the composite management commands easier to use:

  • A property for each composite archive, eg. my.composite.rev1.sar=c:/work/my_composite_rev1.0.jar

  • A property for each configuration plan, eg. my.composite.rev1.cp=c:/work/my_composite_cfgplan.xml

Deploy a Composite:

confignow deploy_composite <env> <config>

-D"composite.location=<loc>"

–D"composite.overwrite=<true|false>"

–D"composite.default=<true|false>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.location Yes The absolute path of the composite archive, eg. c:/work/my_composite_rev1.0.jar, this can also be a ZIP file containing multiple composites, eg. c:/work/some_composites.zip
composite.overwrite No Overwrite if the revision already exists. Defaults to false
composite default No Set this revision as the default. Defaults to true

Examples:

os_prompt> confignow deploy_composite dev my_soa.properties

–D"composite.location=${my.composite.rev1.sar}"

os_prompt> confignow deploy_composite dev my_soa.properties

–D"composite.location=${my.composite.rev1.sar}"

-D"composite.overwrite=true"

os_prompt> confignow deploy_composite dev my_soa.properties

–D"composite.location=c:/work/some_composites.zip"

Deploy a Composite with a Configuration Plan:

confignow deploy_composite_with_cp <env> <config>

-D"composite.location=<loc>"

-D"composite.cp=<loc>"

–D"composite.overwrite=<true/false>"

–D"composite.default=<true/false>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.location Yes The absolute path of the composite archive, eg. c:/work/my_composite_rev1.0.jar
Composite.cp Yes The absolute path of the configuration plan, eg c:/work/my_composite_cfgplan.xml
composite.overwrite No Overwrite if the revision already exists. Defaults to false
composite default No Set this revision as the default. Defaults to true

Examples:

os_prompt> confignow deploy_composite.with.cp dev my_soa.properties

–D"composite.location=${my.composite.rev1.sar}"

–D"composite.cp=${my.composite.rev1.cp}"

os_prompt> confignow deploy_composite.with.cp dev my_soa.properties

–D"composite.location=${my.composite.rev1.sar}"

–D"composite.cp=${my.composite.rev1.cp}"

-D"composite.overwrite=true"

Undeploy a Composite:

confignow undeploy_composite <env> <config>

-D"composite.name=<name>"

–D"composite.revision=<rev>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.name Yes The name of the composite to undeploy, eg. my_composite
composite revision Yes The revision of the composite to undeploy, eg. 1.0

Example:

os_prompt> confignow undeploy_composite dev my_soa.properties

–D"composite.name=my_composite"

-D"composite.revision=1.0"

List the Deployed Composites:

confignow list_composites <env> <config>

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties

Example:

os_prompt> confignow list_composites dev my_soa.properties

SOA Composite Lifecycle Commands

Start a Composite:

confignow start_composite <env> <config>

-D"composite.name=<name>"

–D"composite.revision=<rev>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.name Yes The name of the composite to start, eg. my_composite
composite revision Yes The revision of the composite to start, eg. 1.0

Example:

os_prompt> confignow start_composite dev my_soa.properties

–D"composite.name=my_composite"

-D"composite.revision=1.0"

Stop a Composite:

confignow stop_composite <env> <config>

-D"composite.name=<name>"

–D"composite.revision=<rev>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.name Yes The name of the composite to stop, eg. my_composite
composite revision Yes The revision of the composite to stop, eg. 1.0

Example:

os_prompt> confignow stop_composite dev my_soa.properties

–D"composite.name=my_composite"

-D"composite.revision=1.0"

To Activate a Composite:

confignow activate_composite <env> <config>

-D"composite.name=<name>"

–D"composite.revision=<rev>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.name Yes The name of the composite to activate, eg. my_composite
composite revision Yes The revision of the composite to activate, eg. 1.0

Example:

os_prompt> confignow activate_composite dev my_soa.properties

–D"composite.name=my_composite"

-D"composite.revision=1.0"

To Retire a Composite:

confignow retire_composite <env> <config>

-D"composite.name=<name>"

–D"composite.revision=<rev>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.name Yes The name of the composite to retire, eg. my_composite
composite revision Yes The revision of the composite to retire, eg. 1.0

Example:

os_prompt> confignow retire_composite dev my_soa.properties

–D"composite.name=my_composite"

-D"composite.revision=1.0"

Set a Default Revision for a Composite:

confignow set_default_composite <env> <config>

-D"composite.name=<name>"

–D"composite.revision=<rev>"

Param Required Description
Env Yes The name of the environment being configured, eg. dev
Config Yes The name of the properties file used to configure the environment, eg. my_soa.properties
composite.name Yes The name of the composite, eg. my_composite
composite revision Yes The revision of the composite to make the default, eg. 1.0

Example:

os_prompt> confignow set_default.composite dev my_soa.properties

–D"composite.name=my_composite"

-D"composite.revision=1.0"