fatwire可以在tomcat上运行吗？
目前在weblogic上运行fatwire，是否可以轻松将其移植到tomcat，是否需要J2EE？如果不是tomcat，Jboss怎么样？
Currently running fatwire on weblogic, would it be easy to port it to to tomcat, does it require J2EE? If not tomcat how about Jboss?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
支持 Tomcat 和 JBoss
Both Tomcat and JBoss are supported
根据文档，您可以在 Tomcat、WebSphere、Weblogic、Jboss、Resin 上运行 Fatwire 。我亲眼目睹 Fatwire 在 Tomcat、Weblogic、WebSphere 上运行得相当成功。
您可以在 Tomcat 上运行，因为主要组件是 JSP，并且您可能不需要使用带有 EJB 容器的应用程序服务器。
Accoding to the documentation, you can run Fatwire on Tomcat, WebSphere, Weblogic, Jboss, Resin. I've personally seen Fatwire running on Tomcat, Weblogic, WebSphere quite successfully.
You can run on Tomcat, because the main components are JSPs and you may not need to use an app server with EJB container.
将 Content Server 从 weblogic 移动到 tomcat 或 jboss 应该相当简单，假设 CS 安装文件的位置没有改变，并且它侦听的主机名：端口也没有改变。 ContentServer 仅使用 servlet、过滤器、jsps 和 jdbc 数据源。没有 EJB 要求。它被认证可以在tomcat和jboss上运行，过去也可以在resin上运行。
不过，请谨慎对待未来的升级/修补，修补程序/升级安装程序会在 omininstallinfo 中查找 omproduct.ini，其中包含一些安装元数据，例如应用程序服务器位置。此信息在升级期间用于插入新目录和部署新的 .war/.ear 文件。 omproduct.ini 仍将引用旧 weblogic 的位置，因此修补/升级可能会失败。
如果您要移动到新的主机：端口或更改 CS 安装文件的位置以及切换应用程序服务器，那么最好联系支持人员，因为这可能会很麻烦。
菲尔
It should be fairly straightforward to move Content Server from weblogic to tomcat or jboss, assuming that the location of the CS install files do not change, and nor does the hostname:port that it listens on. ContentServer uses only servlets, filters, jsps, and jdbc datasources. There is no EJB requirement. It is certified to run on tomcat and jboss, and in the past also ran on resin.
There will be a .war file under <INSTALLDIR>/ominstallinfo/app that can be copied to your (for example) tomcat/webapps directory. You will need to add a datasource configuration to tomcat's server.xml so that CS can find the database, and you can copy the database driver to tomcat's lib folder.
Be cautious about future upgrades/patching though, the patch/upgrade installer looks to the omininstallinfo for an omproduct.ini which contains some installation metadata, such as the application server location. This info is used during upgrade for inserting new catalogs, and deploying the new .war/.ear file. The omproduct.ini will still reference the location of the old weblogic and it's, and so patching/upgrading may fail.
If you are moving to a new host:port or changing the location of the CS install files as well as switching application server, then it'e best to contact Support because it could get hairy.
Phil