英文:
How to stop application,application server,node,nodeagent in websphere
问题
我们的Java应用部署在Solaris服务器上的WebSphere中，在Solaris服务器上需要进行一些升级。在进行升级之前，我需要在WebSphere中停止应用程序。
所以请帮忙说明我需要按顺序停止哪些内容以及如何停止？这些内容包括应用程序、应用程序服务器、节点、节点代理、HTTP服务器和管理节点（dmgr）。
告诉我如何按正确顺序停止和启动上述所有内容。
提前感谢！
英文:
our java application is deployed in web sphere in solaris server, and in the solaris some upgrades need to be performed, before they perform upgraded i need to stop the application in websphere.
so please help what are the things i need to stop in a sequence and how?, there will be a application,application server,node,nodeagent,httpserver,dmgr all those.
tell me how can stop and start above all in a sequence.
Thanks, in advance!..
答案1
得分: 1
通常的关闭顺序如下：
- Web服务器（们）
- 应用程序（们）
- 应用服务器（们）
- 节点代理（们）（在你的问题中也代表节点）
- 管理节点（们）（通常只有一个，参见此链接）
然后重新启动的顺序如下：
- 管理节点（们）
- 节点代理（们）
- 应用服务器（们）
- 应用程序（们）
- Web服务器（们）
你可以在 WebSphere Application Server 控制台上逐步执行大部分这些停止活动... 而对于启动，你必须从命令行启动 dmgr（管理节点），然后才能访问控制台，你必须从命令行启动节点代理以便从控制台执行启动活动，但除此之外，并没有从头到尾以定义的顺序自动执行所有这些操作的内建方法，或许可以通过 wasservice 等配置具有依赖关系的操作服务来实现，但在 Windows、Linux、Solaris 之间会有所不同... 在 WebSphere Application Server V8：管理与配置指南 的 7.9.2 小节中有一些关于如何在 Linux/Unix 上执行的信息，因此大多数人会编写自定义的启动脚本和关闭脚本，这些脚本会调用底层提供的脚本，并需要添加延迟或其他逻辑以实现所需的控制级别... 可以在这里找到一些示例，但基本上：
关闭时：
- apachectl 停止（停止 Web 服务器）
- stopServer（或参见下方 stopNode 命令的 -stopservers）
- stopNode
- stopManager
启动时：
- startManager
- startNode（取决于你如何设置 监控策略，这可能会为你启动应用服务器，而应用程序的启动设置将在服务器启动时处理应用程序（默认情况下，应用程序会在服务器启动时启动））
- apachectl 启动（启动 Web 服务器）
你甚至可以在本地 WebSphere Application Server 元素中使用 wsadmin 进行更复杂的脚本编写，但关于这一主题已经有课程和书籍发布了，所以我认为无法在这里对其进行完全解释。
英文:
The usual shutdown approach would be to shutdown in this order
- WebServer(s)
- Application(s)
- Appserver(s)
- Nodeagent(s) (this represents the node too in your question)
- Dmgr(s) (usually only one see this link)
Then starting back up would be the same list but like this:
- Dmgr(s)
- Nodeagent(s)
- Appserver(s)
- Application(s)
- Webserver(s)
You could step through most of these stop activities on the WebSphere Application Server console ... and for starting you have to get the dmgr running from the command line before you can access the console and you have to start the nodeagent from the command line to do the start activities from the console, but there is no built in way from a to z to make this all happen in a defined sequence, other than perhaps configuring operating services with dependencies via wasservice etc and that varies between Windows, Linux, Solaris... there is some information in WebSphere Application Server V8: Administration and Configuration Guide in 7.9.2 about how to do this in Linux/Unix so most people write a bring up script and a shutdown script that is custom to their environment to call lower level scripts provided, and need to add delays or other logic to sequence to their desired level of control ... see some of these here but basically:
to stop
- apachectl stop (to stop webserver)
- stopServer (or see -stopservers on stopNode command below)
- stopNode
- stopManager
and to start
- startManager
- startNode (depending on how you have the Monitoring policy set this could start the appservers for you and how you have the applications set to start or not will handle the applications (default is to have apps start when server starts)
- apachectl start (to start webserver)
You could get even more complex with using scripting in wsadmin for the native WebSphere Application Server elements, but there have been courses and books published on that subject, so I don't think it can fully be explained here.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论