E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (10)
View Page History
...
{section} \\
In the scope of this tutorial, we are going to work with the version 3.0 2.4 of the File Transfer component.
Which gives us:
...In particular, it defines the interface, service and end-point names of the service that will be invoked when a file is added in the watched directory.
!petals-studio-tuto-consumes-ft-2.jpg!
\\
{note}
A service is identified by a triplet, interface, service and end-point names. This triplet is unique in a Petals topology.
When you consume a service, the service is selected in a set. This set is defined by the invocation properties.
If the 3 fields are set in the consume properties, then the set will contain at most 1 result (there can be only 1 service with this ID).
If 2 fields are set, then the third one is considered as a wildcard and the set will larger.
Consume possibilities are the following ones:
* By interface, service and end-point names.
* By interface and service names.
* By interface name only.
{note}
\\
\\
{note}
A service is identified by a triplet, interface, service and end-point names. This triplet is unique in a Petals topology.
When you consume a service, the service is selected in a set. This set is defined by the invocation properties.
If the 3 fields are set in the consume properties, then the set will contain at most 1 result (there can be only 1 service with this ID).
If 2 fields are set, then the third one is considered as a wildcard and the set will larger.
Consume possibilities are the following ones:
* By interface, service and end-point names.
* By interface and service names.
* By interface name only.
{note}
\\
You can obviously fill-in these fields by hand.
However, the most efficient way is to use the [Petals Services explorer|Getting familiar with the Petals Services view] (provided it was populated).
Click *Select a service*. A selection dialog shows up, providing filtering assistance.
However, the most efficient way is to use the [Petals Services explorer|Getting familiar with the Petals Services view] (provided it was populated).
Click *Select a service*. A selection dialog shows up, providing filtering assistance.
!petals-studio-tuto-consumes-ft-2bis.jpg!
\\
...This page defines information which are specific to the Petals File Transfer component.
There are three parameters to take care of here:
There are three parameters to take care of here:
* The first one There is the *directory* that will be polled regularly.
* The second parameter There is the *name pattern* of the file that must be sent to the invoked service.
* The third one And there is the *polling period*, i.e. the time interval between each polling of the read directory.
The other displayed parameters are optional.
There is still one to configure manually after the jbi.xml is created.
The meaning of all the parameters can be read in the documentation of the [Petals-BC-FileTransfer|petalscomponents:Petals-BC-Filetransfer] component.
...This page requires information related to the CDK.
If the service to consume is described by a WSDL, then there is a list of the possible operations that can be invoked.
You Otherwise, you have three parameters to complete here (others are optional or have default values):
* The name space of the invoked operation's name (WSDL operations are QNames).
* The local part of the invoked operation's name (WSDL operations are QNames).
* The Message Exchange Pattern (MEP).
* The local part of the invoked operation's name (WSDL operations are QNames).
* The Message Exchange Pattern (MEP).
\\
With this component, only operations that work with the *InOnly* MEP can invoked.
The wizard only shows these operations.
With this component, only operations that work with the *InOnly* MEP can invoked.
The wizard only shows these operations.
The meaning of all the CDK parameters for File Transfer can be found in the documentation of the [Petals-BC-FileTransfer|petalscomponents:Petals-BC-Filetransfer] component.
...