Databases Reference
In-Depth Information
importUpdates
is used in conjunction with the
exportUpdates
command
and allows the import of composite configuration information. It has the
following parameters:
serverURL
compositeName
revision
jarFile
: Location of the
.jar
file containing configuration
to import
user
password
•
°
°
°
°
°
°
Test parameters (ant-sca-test.xml)
scatest.input
: Name of the composite to test (test)
scatest.result
: Directory for test results (test)
jndi.properties.input
: JNDI properties file to use for server
connection (test)
•
•
•
Tests are executed on the SOA server and the JNDI file contains the properties
needed to connect to the server. A sample JNDI property file is as shown:
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://target-server:8001/soa-infra
java.naming.security.principal=weblogic
java.naming.security.credentials=welcome1
dedicated.connection=true
dedicated.rmicontext=true
The
test
command can be used to automate the initiation of test scripts. For example,
allow test scripts to be run every evening against the latest build in the source
repository and the test results will be available for the developers in the morning.
Revisions and milestones
When deploying a composite, we are required to provide a revision or a version
number. The revision number is a sequence of numeric digits with '.' as separators.
For example, the default revision in JDeveloper for a composite is '1.0'. Each revision
number represents a different composite on the SOA server. For example, Calculator
revision 1.0 and Calculator 1.1 are different composites. All the artifacts in a
composite, including the rules, Mediator configuration, BPEL processes, and human
workflow, are part of the versioning of the composite. The only exception is the
custom UI components of the human workflow, which are not deployed as
