Databases Reference
In-Depth Information
<searchReplace>
<search>http://my-dev-server</search>
<replace>http://my-test-server</replace>
<searchReplace>
</wsdlAndSchema>
</SOAConfigPlan>
Creating a configuration plan
Having created a configuration plan to use a template, we can use this to create
configuration plans for each specific environment. We do this by creating a copy
of the configuration plan by selecting
Save As
from the
file
menu in JDeveloper
and then editing the
<replace>
and
<searchReplace>
tags to match our
target environment.
For example, we could search and replace all instances of our local development
machine hostname,
w2k3
, with the name of our test server,
testserver
, across
WSDL and XSD files. To do this, we modify the search and replace elements, as
shown in the following snippet of code:
<wsdlAndSchemaname="*">
<searchReplace>
<search>w2k3</search>
<replace>testserver</replace>
</searchReplace>
</wsdlAndSchema>
This will cause the SOA server to search all WSDL and schema files "
*
" in the
suitcase at deployment time and replace the string
w2k3
with the string
testserver
.
Note that it is possible to have multiple
<searchReplace>
elements.
Attaching a configuration plan to an SCA archive
Having created and saved a deployment plan specific to one or more environments,
we will want to deploy our process into an environment. When deploying the
composite, either through the command line, JDeveloper, or the EM Console, we
have the option of attaching a configuration plan. When using JDeveloper, the
configuration file is attached to the
Deploy Configuration
step of the deployment
wizard. When using the command line, the configuration file is specified using the
configPlan
parameter.
