使用 wsadmin 远程部署到 Websphere 6.1.x

发布于 2024-08-18 19:28:54 字数 296 浏览 2 评论 0原文

我正在尝试将 war 文件远程部署到 websphere 应用程序服务器。我知道使用 wsadmin 可以做到这一点,但我是 Websphere 新手。

我知道我可以运行 wsadmin 并使用 SOAP 连接到远程应用程序服务器,但这就是我所处的位置。

这看起来应该是一个常见的用例,有人可以帮助我吗?

我想用例如下: 1. 更新应用程序 2. 保存所有更改 3. 重新启动远程应用程序服务器

我将使用 Hudson WAS Builder 或 Maven 进行部署,无论哪个有效。

感谢您的帮助

I am trying to remotely deploy a war file to a websphere application server. I understand this is possible to do using wsadmin, but I am a Websphere newb.

I know I can run wsadmin and connect using SOAP to the remote app server, but that is where I am at.

This seems like it should be a common use case, can anyone help me with?

I suppose the use case follows:
1. Update the application
2. Save all changes
3. Restart the remote application server

I am going to do the deployment using either Hudson WAS Builder or Maven, whichever works.

Thanks for your help

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

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

发布评论

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

评论(3

沉默的熊 2024-08-25 19:28:54

这个问题已经很老了,但我想展示一下我们如何远程做到这一点。在这种情况下,使用 Ant

<target name="postbuild">
    <exec executable="C:\MyThinClient\wsadmin.bat" failonerror="true">
        <arg line="-conntype SOAP -host ${deployServer} -port ${deployPort} -user ${deployUser} -password ${deployPassword} -c" />
        <arg value="$AdminApp update ${projectName}EAR app {-operation update -contents {${artifactsDir}/${projectName}-${buildVersion}.ear}}" />
    </exec>
</target>

如果正确设置了 wsadmin.bat,您可以从任何服务器运行它(未安装 WAS) 至少在 WAS 6.1/7.0 ND 上,这只会使用新的二进制文件重新启动应用程序,而不是整个服务器

This question is pretty old, but id like to show how we do this remotly. In this case with Ant

<target name="postbuild">
    <exec executable="C:\MyThinClient\wsadmin.bat" failonerror="true">
        <arg line="-conntype SOAP -host ${deployServer} -port ${deployPort} -user ${deployUser} -password ${deployPassword} -c" />
        <arg value="$AdminApp update ${projectName}EAR app {-operation update -contents {${artifactsDir}/${projectName}-${buildVersion}.ear}}" />
    </exec>
</target>

Given the correct setup of the wsadmin.bat you can run this from any server (without WAS installed) At least on WAS 6.1/7.0 ND this will only restart the application with the new binaries, not the whole server

堇年纸鸢 2024-08-25 19:28:54

由于 WAS Builder Plugin 比较新,所以我还没有对其进行测试(评估已经在 ToDo 列表中)。为了从命令行运行部署,我们使用 jython-scripts 和 wsadmin。我的理解是我需要在我想要部署的机器上。您可以将本地 wsadmin 部署到与目标计算机处于同一级别的不同计算机 ID(相同的版本相同的功能包)。

有关 wsadmin 的更多信息,请参阅 http://publib.boulder.ibm.com/infocenter/wsdoc400/v6r0/index.jsp?topic=/com.ibm.websphere.iseries.doc/info/ ae/ae/rxml_commandline.html

顺便说一句,当您使用基于 Web 的管理控制台进行部署时,部署过程末尾的某个位置有一个链接,向您显示 jython 命令。不要使用 jacl,因为 WAS 7 仅使用 jython。

Since the WAS Builder Plugin is relatively new, I haven't tested it (The evaluation is already on the ToDo list). For running deployments from the command line we use jython-scripts and wsadmin. My understanding is that I need to be on the machine where I want to deploy. You can deploy to a different machine id your local wsadmin is on the level than your target machine (same version and same feature packs).

for more information on wsadmin see http://publib.boulder.ibm.com/infocenter/wsdoc400/v6r0/index.jsp?topic=/com.ibm.websphere.iseries.doc/info/ae/ae/rxml_commandline.html

BTW, when you deploy using the web based admin console, there is a link somewhere at the end of the deployment process that shows you the jython command. Don't use jacl, since WAS 7 only uses jython.

小瓶盖 2024-08-25 19:28:54

脚本的链接没有出现在我的评论中,所以这里是: IBM 示例脚本

The link to the scripts didn't show up right in my comment, so here it is: IBM SAMPLE SCRIPTS

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文