关于 Sitecore 的publish:end:remote 事件的简单问题

发布于 2024-10-29 02:47:12 字数 1447 浏览 2 评论 0原文

任何人都对 publish:end:remote Sitecore 事件有好运，或者可以阐明它的工作原理吗？我根本无法让它点火。

据我了解，这是一个在成功发布到 Sitecore 远程实例后将触发的事件。问题是，似乎没有文档说明该事件在哪些服务器（主服务器或从服务器）上触发，或者哪个服务器应包含配置设置。

我在两台服务器上为所有数据库启用了“历史引擎”，如下所示：

<Engines.HistoryEngine.Storage>
  <obj type="Sitecore.Data.$(database).$(database)HistoryStorage, Sitecore.Kernel">
    <param connectionStringName="$(id)">
    </param>
  </obj>
</Engines.HistoryEngine.Storage>

作为测试，我向两台服务器上的publish:end:remote 事件添加了一个自定义类。该类只是通过 Log.Info() 记录“Hello World”，但没有显示任何内容。

我正在使用 Sitecore 6.4.1（修订版 101221）。

更新 1

我已阅读最新的扩展指南并进行了所有必需的配置更改。我们的单个 Staging/CM 服务器和 (2) Prod/CD 服务器都将 EnableEventQueues 设置为 true，并且所有实例上都已设置 ScalabilitySettings.config。也就是说，我认为问题在于 Sitecore 将这些排队事件存储在核心数据库中。我们的 CD 服务器与暂存核心数据库隔离，它们仅通过“Web”数据库链接到暂存。我是否应该像这样将这些排队事件存储在生产“web”数据库中......

/eventing/providers/add[@name="sitecore"]

并设置以下属性：systemDatabaseName="~~core~~< em>web"

更新 2

我已将事件提供程序设置为使用（共享）生产“web”数据库，现在我看到了事件队列涌入 EventQueue 表。在任何给定时间，该表中大约有 60 条“PublishEndRemoteEvent”事件记录。所有这些事件都将“InstanceName”设置为我的暂存实例名称。 “RaiseLocally”设置为 FALSE，“RaiseGlobally”设置为 TRUE。 奇怪的是，新事件的“创建”日期不知何故是未来 7 小时。我们的临时服务器距离我工作的地方仅早 3 小时。我想这个时间差可能是罪魁祸首。

原文

Anyone have luck with the publish:end:remote Sitecore event or can shed some light on how it's supposed to work? I simply cannot get it to fire.

From what I understand, it's an event that will trigger after a successful publish to a remote instance of Sitecore. The trouble is, there appears to be no documentation on which server(s) this event is fired on (master or slave) or which server should contain the config setting.

I have the "History Engine" enabled on both of my servers for all databases like so:

<Engines.HistoryEngine.Storage>
  <obj type="Sitecore.Data.$(database).$(database)HistoryStorage, Sitecore.Kernel">
    <param connectionStringName="$(id)">
    </param>
  </obj>
</Engines.HistoryEngine.Storage>

As a test, I added a custom class to the publish:end:remote event on both servers. The class simply logs "Hello World" via Log.Info(), but nothing shows up.

I am using Sitecore 6.4.1 (rev. 101221).

UPDATE 1

I have read the latest Scaling guide and instituted all of the required configuration changes. Both our single Staging/CM server and (2) Prod/CD servers have EnableEventQueues set to true and the ScalabilitySettings.config is in place on all instances. That said, I believe the issue is that Sitecore is storing these queued events in the core database. Our CD servers are isolated from the staging core database and they are only linked to Staging via the "web" database. Should I be storing these queued events in the production 'web' database like so...

/eventing/providers/add[@name="sitecore"]

... and set the following attribute: systemDatabaseName="~~core~~web"

UPDATE 2

I have set the eventing provider to use the (shared) production 'web' database and I now see event queues pouring into the EventQueue table. There are around 60 records for the "PublishEndRemoteEvent" event in that table at any given time. All of these events have the "InstanceName" set to my Staging instance name. "RaiseLocally" is set to FALSE and "RaiseGlobally" set to TRUE. Oddly, the "Created" date for new events are somehow 7 hours in the future. Our Staging server is located only 3 hours ahead of where I work. I'm thinking this time difference might be the culprit.

分享到QQ

分享到微博