有用的 WebSphere Application Server 管理脚本

当您安装 IBM WebSphere Application Server (WAS) 时，它包含超过 125 个 shell 脚本文件。

并非所有这些都有用。另外，如果您是学习者，您可能不知道一些可以在日常工作中使用的强大脚本。

为了让您作为 WebSphere 管理员的生活更加轻松，我们列出了一些最有用的脚本。

下面的脚本已经在 IBM WAS ND 8.5.5 环境中进行了测试，我不知道为什么它在其他环境中不起作用。

停止和启动部署管理器、节点代理和 JVM

停止管理器.sh

您可以使用上述命令停止部署管理器。

 [root@localhost bin]# ./stopManager.sh
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/stopServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.
[root@localhost bin]# 

注意：这必须在 DMGR 配置文件路径中完成。

启动管理器.sh

您可以使用上述命令启动部署管理器。

 [root@localhost bin]# ./startManager.sh
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 9183
[root@localhost bin]# 

注意：这必须在 DMGR 配置文件路径中完成。

启动服务器.sh

要启动 JVM，请使用 startServer.sh 和服务器名称：

 [root@localhost bin]# ./startServer.sh server1
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 10633
[root@localhost bin]# 

注意：您必须在启动 JVM 之前启动节点代理。

停止服务器.sh

您可以通过运行指定 JVM 名称的上述命令来关闭 JVM。

 [root@localhost bin]# ./stopServer.sh server1
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/stopServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server server1 stop completed. 
[root@localhost bin]# 

停止节点.sh

要停止每个 Node Agent，您需要转到其配置文件并运行 stopNode.sh 以停止 Node Agent。

 [root@localhost bin]# ./stopNode.sh
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/stopServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server nodeagent stop completed. 
[root@localhost bin]# 

启动节点.sh

转到相应的配置文件并运行 startNode.sh 以启动 Node Agent。

 [root@localhost bin]# ./startNode.sh
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 11363
[root@localhost bin]# 

服务器状态.sh

将此脚本与 –all 参数结合使用来检查 JVM 的状态。

这必须在相应的配置文件级别完成。在 DMGR 配置文件级别运行此命令将仅显示 DMGR 的状态。

 [root@localhost bin]# ./serverStatus.sh -all
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/serverStatus.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: server1
ADMU0508I: The Node Agent "nodeagent" is STARTED
ADMU0508I: The Application Server "server1" is STARTED
[root@localhost bin]# 

恢复

备份配置.sh

在生产支持工作时，您首先要学习的事情之一就是如何进行备份。当没有任何效果时，备份会很有帮助。

您可以使用此脚本来备份 WebSphere 环境配置。作为最佳实践，您可以使用“-nostop”参数进行备份，而无需停止 Deployment Manager。

 [root@localhost bin]# ./backupConfig.sh -nostop
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/backupConfig.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU5001I: Backing up config directory
          /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config to file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/WebSphereConfig_2015-04-12.zip
....................................................................................................................................................................................................................................................................
ADMU5002I: 933 files successfully backed up
[root@localhost bin]# 

恢复配置.sh

如果您更改配置并且结果没有达到您的预期，您有时间恢复配置。您可以使用备份文件恢复您的配置。

 [root@localhost bin]# ./restoreConfig.sh WebSphereConfig_2015-04-12.zip -nostop
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/restoreConfig.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU5502I: The directory /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config
           already exists; renaming to
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config.old
ADMU5504I: Restore location successfully renamed
ADMU5505I: Restoring file WebSphereConfig_2015-04-12.zip to location
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config
.........................................................................................................................................................................
ADMU5506I: 933 files successfully restored
ADMU6001I: Begin App Preparation -
ADMU6009I: Processing complete.
ADMU6002I: Begin Asset Preparation -
ADMU6009I: Processing complete.
[root@localhost bin]# 

到目前为止喜欢吗？向下滚动以获得更多乐趣。

获取版本和修复包信息

版本信息.sh

查看服务器上安装的 WAS 版本、构建级别、软件包、体系结构和已安装的功能。

 [root@localhost bin]# ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2012; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.48, dated 2/8/12 
--------------------------------------------------------------------------------
IBM WebSphere Product Installation Status Report
-------------------------------------------------------------------------------- 
Report at date and time April 12, 2015 3:18:41 AM PDT 
Installation
--------------------------------------------------------------------------------
Product Directory       /opt/IBM/WebSphere/AppServer
Version Directory       /opt/IBM/WebSphere/AppServer/properties/version
DTD Directory           /opt/IBM/WebSphere/AppServer/properties/version/dtd
Log Directory           /var/ibm/InstallationManager/logs 
Product List
--------------------------------------------------------------------------------
NDTRIAL                 installed
Installed Product
--------------------------------------------------------------------------------
Name                 IBM WebSphere Application Server Network Deployment
Version               8.5.5.0
ID                   NDTRIAL
Build Level           gm1319.01
Build Date           5/14/13
Package               com.ibm.websphere.NDTRIAL.v85_8.5.5000.20130514_1044
Architecture         x86-64 (64 bit)
Installed Features   IBM 64-bit WebSphere SDK for Java
                     WebSphere Application Server Full Profile
                     EJBDeploy tool for pre-EJB 3.0 modules
                     Embeddable EJB container
                     Stand-alone thin clients and resource adapters 
--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------
[root@localhost bin]# 

注意：您可能对支持的论点感兴趣。

• -fixpacks：显示修订包信息。
• -long：显示所有修订包和 ifix。
• -ifixes：显示ifixes信息。

获取历史报告.sh

如果您正在运行审核或想要列出组件、修复程序和带日期的刷新包，运行此命令将在您当前的工作目录（通常是 bin 文件夹）中生成historyReport.html。

获取版本报告.sh

查看 WebSphere 安装的构建版本和构建日期。 IBM 支持人员经常要求您调查特定版本是否存在可疑问题。

清除缓存

清除缓存的原因有很多，但最明显的原因是升级后。您应该考虑清除两个缓存 (1) JVM 2) OSGi。

清除类缓存.sh

运行上面的脚本来清除 JVM 的类缓存。

注意：清除类缓存之前必须停止 JVM。

osgiCfgInit.sh

运行上述命令以清除 OSGi 配置文件和服务器缓存。

 [root@localhost bin]# ./osgiCfgInit.sh
OSGi profile cache successfully cleaned for /opt/IBM/WebSphere/AppServer/profiles/Dmgr01.
OSGi server cache successfully cleaned for /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/servers/dmgr.
[root@localhost bin]# 

注意：请记住在清除缓存之前停止所有正在运行的进程。

管理您的个人资料

管理dk.sh

如果您安装了多个SDK，您可以在版本之间切换。您还可以使用此脚本查找与您的配置文件关联的可用 SDK。下面的示例显示了可用 SDK 的列表。

 [root@localhost bin]# ./managesdk.sh -listAvailable
CWSDK1003I: Available SDKs :
CWSDK1005I: SDK name: 1.6_64
CWSDK1001I: Successfully performed the requested managesdk task.
[root@localhost bin]# 

下午茶

您可以使用 PMT（配置文件管理工具）以 GUI 模式创建 WebSphere 配置文件。使用 PMT 创建配置文件非常简单。只需创建您想要的级别的配置文件并按照向导操作即可。请尝试一下！

同步节点.sh

如果由于某种原因您无法从管理控制台执行节点同步，您可以从配置文件级别使用syncNode.sh。使用此脚本之前必须停止节点代理。

您必须传递 DMGR 主机和 SOAP 端口号参数。

 [root@localhost bin]# ./syncNode.sh localhost 8879
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0401I: Begin syncNode operation for node localhostNode01 with Deployment
           Manager localhost: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node localhostNode01 has been synchronized
           with Deployment Manager localhost: 8879
[root@localhost bin]# 

• localhost = 部署管理器主机名
• 8879 = DMGR SOAP 端口号

希望以上脚本对您的日常工作有用。通过学习云计算将您的职业生涯提升到一个新的水平。