This discussion is archived
9 Replies Latest reply: Jan 4, 2013 11:26 AM by 891772 RSS

Unable to migrate content at specific date, through automated replication

891772 Newbie
Currently Being Moderated
Hi,

We currently have a serious replication issue. We have a contribution content server as well as a consumption server, and content synchronisation is achieved through automated replication with export/import archives. When we release new content revisions, there are some that can migrate to consumption immediately, but that is not always the case.

There's often a need to coordinate migrations for specific contents, which are related (composing a Web page). We have created a custom metadata field named "Delivery date" and we want to use that date so the archiver doesn't immediately transfer contents for which the delivery date hasn't been reached yet. However, we need it to be replicated, thus transferred from contribution to consumption, when that date is reached. We have then created an export query that treats content revisions as such. Our problem is that if a new released content has a delivery date set in the future, the archive ignores it for now (which is OK) but never considers it afterwards, even when the date is reached. What's puzzling is that when the date is reached, those contents do show up when we use the "preview" feature of the export query.

It is our understanding that the automated export feature is linked with the indexing process, when a content revision passes from a non-indexed state, to indexed. If that is so, that would explain why a released content is never treaded afterwards. Do we understand correctly? Nevertheless, we need to find a way to solve this issue. So in short, how can we make sure that a content that has previously been indexed and ignored by the archiver, be treated later on? This is really a blocking issue for us at the moment and we must know where we are heading regarding that. Here is the export query we are using :

(xWebsiteObjectType = 'Data File' AND
(
     (xDeliveryDate is NULL) OR (xDeliveryDate <= <$dateCurrent()$>)
)
)


Thanks in advance for any reply!
  • 1. Re: Unable to migrate content at specific date, through automated replication
    jiri.machotka Guru
    Currently Being Moderated
    Any chance that the cause is the item's status?

    http://docs.oracle.com/cd/E23943_01/doc.1111/e10792/c08_migration.htm#CHDHJHDI states that "You can export revisions that are in RELEASED, DONE, EXPIRED, and GENWWW status. You cannot export revisions that are in an active workflow (REVIEW, EDIT, or PENDING status) or that are DELETED."

    I wonder what's the relation between your "Delivery date" and the standard Release Date (dInDate). Note that you could also replicate items immediately, but make it available in the other system (via dInDate, or any other mechanism) only when it reaches the "delivery date".
  • 2. Re: Unable to migrate content at specific date, through automated replication
    882509 Newbie
    Currently Being Moderated
    Hi,

    Your export query is not getting fired , if the xDeliveryDate is setup for future date and content is not getting exported.

    You should configure a scheduler, which triggers at some time intervals and that will execute export query and then export contents automatically.

    Recently, I did the similar setup and it works.

    Regards
    Ram
  • 3. Re: Unable to migrate content at specific date, through automated replication
    891772 Newbie
    Currently Being Moderated
    Thanks everyone for your replies. However, the problem is not with the status, because the items are no longer in the workflow. They are in a released status. Also don't be mistaken with the actual release date, for firing the export query. I know that the publish date (dInDate) has that exact effect on the replication process and content with publish date set in the future won't migrate until that date is reached. However, it will also not be visible on the contribution server until that same date is reached. That is why we created another date that could be used specifically for the replication process.
  • 4. Re: Unable to migrate content at specific date, through automated replication
    William Phelps Expert
    Currently Being Moderated
    Our problem is that if a new released content has a delivery date set in the future, the archive ignores it for now (which is OK) but never considers it afterwards, even when the date is reached. What's puzzling is that when the date is reached, those contents do show up when we use the "preview" feature of the export query.
    By chance, in your export query definition, do you have the "Export Revisions with Release Date later than the most recent Export Date" box checked? If so, uncheck it. The export query uses this box to act as a filter for incremental type archival (as opposed to always exporting all possible items), and would explain the "never considers it afterwards" statement.
  • 5. Re: Unable to migrate content at specific date, through automated replication
    891772 Newbie
    Currently Being Moderated
    William Phelps wrote:
    By chance, in your export query definition, do you have the "Export Revisions with Release Date later than the most recent Export Date" box checked? If so, uncheck it. The export query uses this box to act as a filter for incremental type archival (as opposed to always exporting all possible items), and would explain the "never considers it afterwards" statement.
    That's what I was wondering also. So I unchecked it and still doesn't anything. As soon as a content has been ignored once, by the query, it's never considered again.
  • 6. Re: Unable to migrate content at specific date, through automated replication
    William Phelps Expert
    Currently Being Moderated
    Is this a clustered environment?

    If you manually click the export button on the source, and manually transfer the archive, and manually import the archive in the destination, does it work?

    For starters, if you manually export the archive, go into the archive's manifest file list that was just exported. Do the older documents appear in the list? If you preview the export results, do you get the same list of documents in the preview as you do in the manifest?
  • 7. Re: Unable to migrate content at specific date, through automated replication
    891772 Newbie
    Currently Being Moderated
    William Phelps wrote:
    Is this a clustered environment?

    If you manually click the export button on the source, and manually transfer the archive, and manually import the archive in the destination, does it work?

    For starters, if you manually export the archive, go into the archive's manifest file list that was just exported. Do the older documents appear in the list? If you preview the export results, do you get the same list of documents in the preview as you do in the manifest?
    Yes to both questions. It's only when the automated export is enabled that it stops working. Thanks a bunch anyway, but I think we'll have to settle for the start date (dInDate)...
  • 8. Re: Unable to migrate content at specific date, through automated replication
    William Phelps Expert
    Currently Being Moderated
    If the source is a clustered environment, I'm wondering if the cluster itself is part of the problem. My thought here is that the system is getting confused about which node should be doing the work. Since it works "manually", there's no logical reason why it won't work in an automated fashion.

    You could try one more thing if you want to.

    If this is 11g, add the "IsAutoArchiver=false" configuration entry in all but one (the one node you want to run Archiving on) of each cluster node's <wcc local non-shared WebLogic domain dir>/ucm/cs/bin/intradoc.cfg. (this is from support note "Archiver Fails to Transfer Data, or Resends Data, To a Target Content Server In a Clustered Environment. [ID 733926.1]").
  • 9. Re: Unable to migrate content at specific date, through automated replication
    891772 Newbie
    Currently Being Moderated
    William Phelps wrote:
    If the source is a clustered environment, I'm wondering if the cluster itself is part of the problem. My thought here is that the system is getting confused about which node should be doing the work. Since it works "manually", there's no logical reason why it won't work in an automated fashion.

    You could try one more thing if you want to.

    If this is 11g, add the "IsAutoArchiver=false" configuration entry in all but one (the one node you want to run Archiving on) of each cluster node's <wcc local non-shared WebLogic domain dir>/ucm/cs/bin/intradoc.cfg. (this is from support note "Archiver Fails to Transfer Data, or Resends Data, To a Target Content Server In a Clustered Environment. [ID 733926.1]").
    Will do! Thanks a lot for your help ;)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points