ICON_Outbound_HA ??!

[phil]

Hi everybody,

as there is no deduplication function for an outbound ICON intended in 7.6.x environments yet, i am trying to set up a secondary ICON for Outbound which has to be run manually in case of "primary" failure. I already did so in our lab environment, but i got a lil issue

In case of ICON_Outbound failure, i replace the DAP_JDBC_ICON_Outbound by DAP_JDBC_ICON_Outbound_2 among the Infomart's connections. When starting ICON_Outbound_2, following error is put out:

[b]ICON_Outbound_2 Persistent Queue operation error:
Cannot start pqueue provider ICON Error 09-25012[/b]

Allthough the *.pq- file is rebuild after this error , the same message occurs each time restarting this ICON. This seems not to be a critical issue, as GIM works appearently properly. GIM gathers outbound related data and writes them into the DB.

Any ideas to the PQ- issue or any experiences/ known issues about setting up a backup application for ICON Outbound?

See ya

Phil

[ecki]

Hi Phil,

What is the topology you have there?

e.

[phil]

moin ecki,

do you mean the reporting topology only or the whole environment?
therefore, i tried to upload an overview of our environment, but it doesnt work. are there restriction for the resolution? what is meant by the message: "The attachments upload directory is not writable" ?

regards from kiel

phil

[ecki]

Just the ICON. Where are yours OCS ICONs sitting, are they on the same host using the same binary files?
Anyway, it looks like it is just ICON's standard behavior. Can you see that ICON is populating IDBs tables? Then it should be alright.

[phil]

Hi ecki,

the "primary" ICON dedicated for Outbound is on the same Host as the OCS. These two Outbound ICONs are not using same binaries, but each one is using its own installtion on a different host. The "secondary" ICON  is on a different host, which is supposed to be ok that way, as in case of host failure a "backup" on the same host would not take much effect, isn't it.
I even saw the Infomart populating GIM tables, from the time where the backup was running on its own. so this should be fine, indeed. I just was unsettled because, of the PQ-File Exception.
Basicly, its just a simple Standalone- deployment of an ICON, but which serves the purpose of a backup, again.

Cheers

Phil