Websphere 7集群部署

发布于 2024-09-24 06:43:43 字数 250 浏览 5 评论 0原文

我们有一个 J2EE 应用程序作为 EAR 文件,部署在 WAS 7 中,为了使应用程序可用性尽可能高,需要部署在 3 个集群中。我们有一个 Quartz Scheduler 类,其工作是每天凌晨 2:00 将数据从一个数据库上传到另一个数据库。

现在的问题是,如果将ear部署在3个不同的节点上以实现负载均衡和高可用性,则所有3个ear文件将同时触发上传。我们该如何处理这个问题。是否可以在WAS 7环境中进行一些配置。任何帮助/建议将不胜感激。

谢谢

We have a J2EE application as EAR file which is deployed in WAS 7, for making the application availability as high it needs to be deployed in 3 clusters. We have a Quartz Scheduler class whose job is to upload data from one database to another daily at 2:00 am.

Now, the problem is if the ear will be deployed in 3 different nodes for load balancing and high availability, all the 3 ear file will trigger the upload at the same time. How we can handle this. Is it possible to do some configuration in WAS 7 environment. Any help/suggestion would be appreciated.

Thanks

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

腹黑女流氓 2024-10-01 06:43:43

您有两种可能性:

  1. Quartz 数据库后端,所有节点都将连接到该后端到 Quartz 用于同步任务运行的同一数据库。可以配置此选项以防止任务同时在多个节点上运行。
  2. EJB 3.x 计时器。例如,请参阅此示例。然而,这可以确保只有每个集群的成员触发计时器。

You have two possibilities:

  1. The Quartz database backend where all your nodes would connect to the same database that Quartz uses for synchronizing the task running. This can be configured to prevent the task from running on several nodes simultaneously.
  2. EJB 3.x timer. See for instance this example. This however works for ensuring that only member from each of the clusters fire the timer.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文