Struggling to understand exactly what is going on with your broker instance? We have added a bunch of new guides which aim to distill the documentation down into just the core set of steps you need to do, check out the following new articles

Installing The Broker
Find Out What Broker Servers Are Running On A Machine
How To Start and Stop A Broker Monitor
Upgrade Broker Monitor from 6.5 to 7.1

Just added is a guide to help you install and configure Optimize for Infrastructure. Its kind of tricky to get going and we think this walk through will be of good use to you!

Dont forget how Software AG positions their Optimize products.

• Optimize for Infrastructure: Allows you to monitor metrics out of a number of Integration Servers and Brokers. Great for things like "how many documents are in that queue?" or "do we have enough free JDBC adapter connections?"

• Optimize for Process: Point it at your process models and it provides you all kinds of great aggregate data about how they are running for example "80% of processes go down this path"

• Optimize for B2B: Monitor your Trading Networks installations, "how many of doc type XXX have gone through?"

• Optimize for SAP: Allows you to hook into your SAP Business Processes.

Now all of these products have conceptually different uses however under the surface they are all very similar, mainly just being separate "satellites" which feed into the same analysis engine. For example if you had a modest Infrastructure and Process instance, they would run together, you wouldnt have seperate installations.

Now you have no excuse for your servers to be down, Optimize is checking them for you!

Hi All,

We were facing duplicate documents problem with the trigger ,then we switched the exactly once button on and the history time to live to 15 mins but still we are facing some duplicate documents,how is it possible ....I want to stop these documents at the broker level itself how to proceed on this?

Please reply as this has been a crucial issue for us.

Thanks in advance

A document received from the broker can have a value of 'new' 'duplicate' or 'in doubt'. IS will use the following logic to determine the status:  DB history -> resolver service -> redelivery count

When you enable exactly once processing by setting detect duplicates property for a trigger to true; these 3 methods are used to identify how many times a document has been received from the broker and processed. These are:
Document history db: this records the service execution for a particular document, if a document has been received before and the service has completely been executed the db will contain a processed status of "completed"

Document resolver service: a custom service you can write to check if the document has previously been processed. E.g. if you are receiving orders from the broker, you might want to check for the order id in the db. If the order id exists you then know it has been processed.

Redelivery count: number of times the document has been sent as maintained by the broker, it should be 0 for the very first document and  increase on subsequent deliveries. Note that earlier versions of the broker server&e.g. v6 does not maintain the delivery count.

I assume in this case there is no DB history or a resolver service and redelivery count is not maintained for the document, i.e. you are using an old broker server, v6?

What are some practical uses for the following built-in services? 
I presume they are useful internally within Integration Server itself,
but are they useful for developers?

pub.document:XMLValuesToDocument
pub.document:documentToXMLValues

As at 14th October, 2005 there are over 350 registered members of the CustomWare repository.