The table describes the various attributes.
Table 2 Poll Request
Attribute Name |
Description |
---|---|
Message Repository |
The Message Repository path pointing to a directory on the remote FTP server where messages will be processed and archived. For more information, see Table 3. For example, book_updates |
Message Name |
Message Name is the filename where a message is put into, usually in the form of a name pattern. Pattern is a string containing special characters preceded by a percentage sign. For more information, see Table 4.
|
Message Name Prefix |
Prefix for outbound (OB) message name. |
Enable Overwrite Protect |
Indicate if overwrite protection is required for message send, when true, existing message will be moved to dedicated directory before the current message is put to the target, otherwise, current message overwrites existing message. The checkbox is selected, by default. |
Enable Staging When Put Message |
Indicate if staging is enabled for message transfer. The check box is selected, by default. |
Payload Processing |
|
The table describes the various message repository directories.
Table 3 Message Repository Directories
Directory |
Description |
---|---|
/inbox |
This is the default location where the consumer puts the request message and the provider polls for a request message. |
/instage |
This is the default location where the consumer stages a request message before it is completely uploaded. |
/inprotect |
This is the default location where consumer moves an existing request message so that it is not overwritten by current request message. |
/inarchive |
This is the default location where provider archives request message after it is processed. |
/outbox |
This is the default location where the provider puts a response message and the consumer polls for the response message. |
/outstage |
This is the default location where the provider stages the response message before it is completely uploaded. |
/outprotect |
This is the default location where provider moves an existing response message to so that it is not overwritten by current response message. |
/outarchive |
This is the default location where consumer archives response message after it is processed. |
The table describes the various Java Timestamp Patterns.
Table 4 Java Timestamp Patterns
Letter |
Data or Time Component |
Presentation |
Examples |
---|---|---|---|
G |
Era designator |
Text |
AD |
y |
Year |
Year |
1996; 96 |
M |
Month in year |
Month |
July; Jul; 07 |
w |
Week in year |
Number |
27 |
W |
Week in month |
Number |
2 |
D |
Day in year |
Number |
189 |
d |
Day in month |
Number |
10 |
F |
Day of week in month |
Number |
2 |
E |
Day in week |
Text |
Tuesday; Tue |
a |
Am/pm marker |
Text |
PM |
H |
Hour in day (0-23) |
Number |
0 |
k |
Hour in day (1-24) |
Number |
24 |
K |
Hour in am/pm (0-11) |
Number |
0 |
h |
Hour in am/pm (1-12) |
Number |
12 |
m |
Minute in hour |
Number |
30 |
s |
Second in minute |
Number |
55 |
S |
Millisecond |
Number |
978 |
z |
Time zone |
General time zone |
Pacific Standard Time; PST; GMT-08:00 |
Z |
Time zone |
RFC 822 time zone |
-0800 |
The FTP Message Active/Passive element for the WSDL binding element functions the same as the FTP message element, but contains flags that allow you to set passive FTP messaging for both the consumer and the provider.
The Table lists the properties that enable passive FTP messaging for the FTP Message Active/Passive element.
Table 5 FTP MessageActivePassive Element
Attribute Name |
Description |
---|---|
consumerUsePassive |
Specifies whether to use passive FTP on the consumer side. Default value: true |
providerUsePassive |
Specifies whether to use passive FTP on the provider side. Default value: true |