Database Reference
In-Depth Information
ant -f ant-sca-deploy.xml deploy -DserverURL=$SOAURL/soa-infra/deployer -Duser=$USERNAME -Dpassword=$PASSWORD -DsarLocation=$CODE/HelloWorld/deploy/sca_HelloWorld_rev1.0.jar -Dpartition=default -Doverwrite=true -DforceDefault=true -Dconfigplan=/tmp/cfgplan_test.xml
Best practices with configuration plans
The approach to managing code promotion effectively involves following a
simple process to maintain consistency, and ensure proper substitution of
environment-specific settings and deployment to other environments.
The summarized approach we recommend is as follows:
1.
Developers should ensure that all URLs, JNDIs, hostnames, ports, and so
on, reference development environments and they should try to remain as
consistent as possible.
For example, if multiple developers are working on multiple pieces of code
that reference the same external service, they should try to be as consistent
as possible. If this is the reference:
http://payment-processing-server-dev:7777/proc/servlet
They should avoid being inconsistent across their code:
http://payment-processing-server-dev.somedomain.org:7777/proc/servlet
http://PAYMENT-PROCESSING-SERVER-DEV:7777/proc/servlet
https://payment-processing-server-dev:7778/proc/servlet
The lack of consistency only means that additional search-replace state-
ments will need to be added in the configuration plans.
2.
The Oracle SOA Suite 11g administrator should create a configuration plan
for every environment:
•
Test:
cfgplan_test.xml
•
QA:
cfgplan_qa.xml
