weblogic托管服务器自动启动
朋友们 我已经配置了具有 2 个托管服务器的 WebLogic 集群，并在 nodemanager.properties 中将 crashrecoveryenabled 设置为“true”，以便在服务器崩溃时托管服务器可以自动启动。节点管理器和管理服务器设置为 Windows 服务，以便它们可以启动服务器重新启动时自动。我有 2 个问题 1.如何确保托管服务器在服务器重新启动后自动启动（我知道将托管服务器添加为Windows服务是一种选择）。 2.在生产环境中，我需要在nodemanager.properties中将startscriptenabled设置为true吗？
谢谢
Friends
I have configured WebLogic cluster with 2 managed servers and set crashrecoveryenabled to 'true' in nodemanager.properties so that in case of server crash the managed servers can start automatically.The Node manager and admin server are setup as windows services so that they can start automatically on server reboot. I have 2 questions
1.How can I make sure that the managed servers will start automatically after server reboot(I know adding managed servers as windows service is one option).
2.In nodemanager.properties do I need to set startscriptenabled to true in production environments?
thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
设置服务以使托管服务器在系统重新引导时启动是首选方法。
Setting up a service to have the managed servers start on system reboot is the preferred approach.
我总是在生产环境中设置 startScriptEnabled=true 。这仅使用脚本来启动托管服务器。
如果 crashRecoveryEnabled 设置为 true 并且您已启动每个托管服务器，那么它将启动。
如果您愿意，您可以使用 wlst 通过某种计划任务来检查它们是否正在运行（或启动它们）。
编辑：来自 Oracle 文档 4.2.4 将节点管理器配置为启动受管服务器
如果受管服务器包含其他 Oracle 融合中间件产品，例如 Oracle SOA Suite、Oracle WebCenter Portal 或 Oracle JRF，则必须配置受管服务器环境以设置正确的类路径和参数。此环境信息是通过位于域目录中的启动脚本（例如 startWebLogic 和 setDomainEnv）提供的。
如果受管服务器由节点管理器启动（如服务器由 Oracle WebLogic Server 管理控制台或融合中间件控制启动时的情况），则必须指示节点管理器使用这些启动脚本，以便正确配置服务器环境。具体来说，节点管理器必须使用属性 StartScriptEnabled=true 启动。
有多种方法可以确保节点管理器在启用此属性的情况下启动。为了方便起见，Oracle Fusion Middleware 提供了以下脚本，它将属性 StartScriptEnabled=true 添加到 nodemanager.properties 文件中：
(UNIX) ORACLE_COMMON_HOME/common/bin/setNMProps .sh。
(Windows) ORACLE_COMMON_HOME\common\bin\setNMProps.cmd
例如，在 Linux 上，执行 setNMProps 脚本并启动节点管理器：
ORACLE_COMMON_HOME/common/bin/setNMProps.sh
MW_HOME/wlserver_n/server/bin/startNodeManager.sh
当您启动节点管理器时，它会读取带有 StartScriptEnabled=true 属性的 nodemanager.properties 文件，并在随后启动受管服务器时使用启动脚本。请注意，您只需运行 setNMProps 脚本一次。
I always set startScriptEnabled=true in production environments. This just uses the script to start up the managed servers.
Provided crashRecoveryEnabled is set to true and you have started each of your managed servers then it will start.
You can use wlst to check if they are running (or start them) through some sort of scheduled task if you wish.
EDIT: From the Oracle Documentation 4.2.4 Configuring Node Manager to Start Managed Servers
If a Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter Portal, or Oracle JRF, the Managed Servers environment must be configured to set the correct classpath and parameters. This environment information is provided through the start scripts, such as startWebLogic and setDomainEnv, which are located in the domain directory.
If the Managed Servers are started by Node Manager (as is the case when the servers are started by the Oracle WebLogic Server Administration Console or Fusion Middleware Control), Node Manager must be instructed to use these start scripts so that the server environments are correctly configured. Specifically, Node Manager must be started with the property StartScriptEnabled=true.
There are several ways to ensure that Node Manager starts with this property enabled. As a convenience, Oracle Fusion Middleware provides the following script, which adds the property StartScriptEnabled=true to the nodemanager.properties file:
(UNIX) ORACLE_COMMON_HOME/common/bin/setNMProps.sh.
(Windows) ORACLE_COMMON_HOME\common\bin\setNMProps.cmd
For example, on Linux, execute the setNMProps script and start Node Manager:
ORACLE_COMMON_HOME/common/bin/setNMProps.sh
MW_HOME/wlserver_n/server/bin/startNodeManager.sh
When you start Node Manager, it reads the nodemanager.properties file with the StartScriptEnabled=true property, and uses the start scripts when it subsequently starts Managed Servers. Note that you need to run the setNMProps script only once.