Incremental Publish in EP

December 15th, 2007

Just found an excellent option "Table-only Publish Post-GTP" that detects changes that make incremental publish incompatible and republishes application. It should be set to "Yes" by default, imho.

See how incremental publish can streamline your reporting in these posts: 1, 2.

RSS feed | Trackback URI

2 Comments »

Comment by Joel Vander Weele UNITED STATES
2008-04-09 04:44:01

Ykud,

I read with interest your blog entries regarding reporting in near real time against Contributor with a incremental publish…

I havent tried it yet, but will soon.

I had one question/concern…doesn’t the nodestate table change during a reconcile? If it did, wouldnt that force a incremental publish for each elist item? That probably isn’t a good thing…

Does this option hear resolve that problem? Where did you find this option?

 
Comment by ykud RUSSIAN FEDERATION
2008-04-09 19:22:00

Hello, Joel.

“doesn’t the nodestate table change during a reconcile? If it did, wouldnt that force a incremental publish for each elist item? That probably isn’t a good thing…”

During Reconcile nodestate table is updated, but if you set up monitoring on date edit field, Event Manager will fire an event only if reconcile brings new data (like import).
Moreover, incremental publish publishes all elists changed since last incremental publish (not reconciled, but with new\changed data). Detecting those elist with data change is internal cognos process ;)

“Does this option hear resolve that problem? Where did you find this option?”

Incremental publish works only after intial table layout publish and if application structure changes (new dlists,cubes) after initial table only layout publish — incremental publish stops working until next full table-layout publish. That was a problem in 8.2, you usually had to republish applications after synchronize.
Option mentioned in the post adds a gtp step, that detects whether such structural occured and if they happend, starts a full table-layout publish automatically.

PS: Too many mentions of “publish” :) Let me know if this answer isn’t clear.

 
Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.

Trackback responses to this post