Database Reference
In-Depth Information
<import>
The import tag is a subelement of the
<composite>
tag. Essentially, any
search-replace within the
<import>
tag will apply to the
<import>
sections in
composite.xml
. You can have any number of search-replace elements here.
<service>
All composites will likely have a service. A service definition is synonymous to
the input of the composite. A composite may have multiple services (for multiple
interfaces), each of which can be invoked separately.
In the configuration plan, the
<service>
and
<reference>
tags use similar
approaches. In the preceding example, there appears to be an inbound File Ad-
apter that has an
inFileFolder
property. The code may be hardcoded with
folder property
/u01/input/dev
. But here, the configuration plan will over-
write that property with the setting of
/u01/input/test
as the input folder.
<reference>
Composites may or may not have references, which refer to other resources
such as another web service or an adapter.
Often, the reference could be the fully qualified URL to some other service either
on the same server or a different one. Here, the configuration plan will replace all
references to
http://payment-processing-server-dev:7777/proc/
servlet
(development server) with
https://payment-processing-
server-test:7778/proc/servlet
(test server).
Attaching a configuration plan
Attaching a configuration plan is quite simple. The ant command to deploy a
composite application does not change and only an additional argument, which
is the references to the fully qualified path to the configuration plan, is required:
