Implementing WebSphere Business Integration Express for Item Synchronization

34 Implementing WebSphere BI Express for Item Synchronization

can be delivered asynchronously or synchronously and can be signed and

encrypted using the same technologies that are available for sending documents.

The status of a document, including several statistics, can be generated by the

P2PAgent in the form of a notice. Again, this notice can be a message in a queue

or a file in a named directory. Any errors can be reported in a daily log file.

Alternatively, an error for a given document can result in an error file or message

specifically tied to that document. The error document can contain, for example,

HTTP error codes. The P2PAgent can also be configured to try to send a

document several times, for example three times at an interval of one minute. If

the agent has tried to send a document the maximum allowed number of times,

the document can be stored in a separate location: a given directory or queue.

This feature is sometimes referred to as the

recycle feature. The message or file

contains nothing but the original document, while the error itself is stored in the

error message or file. The advantage of this separation is that the recycled

document can be used without any alteration in a back-up transmission system,

such as a VAN.

4.3 Administration features

Configuring and managing a P2PAgent configuration can be done in a variety of

ways. The simplest form is to use the interactive session when the agent is

started. The agent runs in a command window and commands can be entered at

the prompt.

Example 4-1 shows the console view of the P2PAgent. After start-up, the user

has executed the status command for which you can see the output in the lower

part of the example. This output also shows us what different options can be

configured and tuned. We will introduce and use some of them throughout this

redbook. For a complete reference, please consult the product documentation.

Example 4-1 Agent startup

:\iSoft_Advanced>p2pagent_odbc_ibm_unlimited.exe

iSoft(R) Peer-to-Peer Agent(TM) for MQSeries(R)

(C) Copyright 2001-2002 iSoft Corp.

Build: 3.1.2002.10.30.1 [Nov 27 2002 15:06:36]

IBM Unlimited Edition

Authorized License

2003.02.05 15:30:09.521 POPT OK Error path set to [error]

2003.02.05 15:30:09.521 POPT OK Inbound errant will be stored

2003.02.05 15:30:09.531 POPT OK Log path set to [log]

2003.02.05 15:30:09.531 POPT OK Trace set to WRITE_FILE

2003.02.05 15:30:09.541 POPT OK Notice path set to [mq://FMCQM/notices]

2003.02.05 15:30:09.541 POPT OK Notices will be written to file

Chapter 4. iSoft Peer-to-Peer Agent 35

2003.02.05 15:30:09.561 POPT OK Work-order path set to

[mq://FMCQM/workorders]

2003.02.05 15:30:09.561 POPT OK Work-order searching enabled

2003.02.05 15:30:09.571 POPT OK Work-order file-spec set to [wo]

2003.02.05 15:30:09.581 POPT OK PKI path set to [pki]

2003.02.05 15:30:09.591 POPT OK Async. receipt path set to

[mq://FMCQM/receipts]

2003.02.05 15:30:09.611 POPT OK First-receive interval set to [300000ms]

2003.02.05 15:30:09.621 POPT OK Mailbox host set to [mq://FMCQM]

2003.02.05 15:30:09.621 POPT OK Mailbox address set to [0.0.0.0]

2003.02.05 15:30:09.631 POPT OK Mailbox port set to [0]

2003.02.05 15:30:09.711 HPIM OK HTTP inbound service started

status

ok

Build: 3.1.2002.10.30.1 Data Source: NONE

Host: vdputteg SMTP Host: NONE

Control IP: 9.24.104.115:3501 SMTP User: NONE

--Services-------- --Config------------- --Timeouts-----------------------

Serialize: ON Partner-Pairs: 2 Connect: 30.000s

Outbound: ON Key-Pairs: 3 First-Receive: 300.000s

Control: OFF Inbound Ctlrs: 1 Next-Receive: 90.000s

Work-Orders: ON Outbound Txns: 0 First-Send: 30.000s

Beacon: OFF Transports: 0 Next-Send: 90.000s

Router: OFF Trace Level: 3 Resend Wait: 60.000s

Web-UI: OFF Buffer Size: 4096 Beacon Wait: 20.000s

PKI Admin: OFF Peer Group: 0 Work Order Interval: 10.000s

Role: Stop Thread: 10.000s

--Options--------- --Locations----------------------------------------------

Local Config: YES Error Path: error

Show Trace: YES Log Path: log

Write Trace: YES Notice Path: mq://FMCQM/notices

Fast Write: NO PKI Path: pki

Notices: FILE Receipt Path: mq://FMCQM/receipts

Work-Order Path: mq://FMCQM/workorders

For settings and commands that you need to execute every time at start-up of the

agent, you should use the configuration file, which is named by default

p2pagent.cfg. We will use the configuration file often when implementing an iSoft

solution in this redbook. Some packages of the iSoft product provide a command

line utility, called buildcfg, that will quickly generate such a configuration file by

asking the end user to answer some simple questions. This utility only builds a

starting configuration file. It is very probable that you will need to edit this file to

optimize the final configuration.