...
Before you start, please decide:
which role is going to be given to the local and which to the remote environment (Extract or Load)
which delivery methods you are going to use
find out the name of the remote environment
Choose a relevant case most relevant for you:
...
| title | Local Load, Remote Extract |
|---|
Local Load, Remote Extract
Local Load Settings
For JMS, MQ or FTP delivery methods you have to create streams based on the default distribution rule:
...
| title | For JMS (click to expand): |
|---|
...
| title | For MQ (click to expand): |
|---|
...
| title | For FTP (click to expand): |
|---|
If you want to use WS, please define the following parameters:
Remote Extract Settings
For JMS or MQ delivery methods you have to create streams on the base of default distribution rule:
...
| title | For JMS (click to expand): |
|---|
...
| title | For MQ (click to expand): |
|---|
...
| Child pages (Children Display) |
|---|
...
| title | Local Extract, Remote Load |
|---|
Local Extract, Remote Load
Local Extract Settings
FTP and WS delivery methods do not require any streams, just define the following parameters:
If you want to use JMS or MQ, you have to create a separate inbound stream based on the default distribution rule:
...
| title | For JMS (click to expand): |
|---|
...
| title | For MQ (click to expand): |
|---|
Remote Load Settings
For JMS, MQ or FTP you have to create a stream on the base of default control message rule:
...
| title | For JMS (click to expand): |
|---|
...
| title | For MQ (click to expand): |
|---|
...
| title | For FTP (click to expand): |
|---|
WS delivery method requires only some configuration parameters to be set:
|
Set specific configuration parameters if you are using custom streams to read RTRs and TSRs:
w_i2i_delivery_stream
w_i2i_tsr_reader_stream
Assign LinkIds, if necessary.
Make up a control message and you are ready to go!