使用 Maximo 更改 Websphere 6 上的 RMI 端口
设置
我有 websphere 6.1 运行两个应用程序服务器。每个都运行相同的应用程序 (Maximo)。每个应用程序都指向不同的数据库。
有一个第三方应用程序通过 RMI 端口 13400 连接 VIA。
两个 Maximo 应用程序的属性文件中都包含此内容。
mxe.registry.port=13400
问题
当第三方程序调用 RMI 端口时，错误的应用程序进程会收到该调用。
我已经尝试过
我在WebSphere 控制台中找不到任何可以让我更改端口的内容。
将 Maximo 属性文件中的 RMI 端口更改为 13400 并重新部署 Ear。然后在第三方软件上更改端口。没有骰子。事实上，我在访问 Maximo 时收到错误 500 System not bond on。
ServletWrappe E SRVE0100E: Did not realize init() exception thrown by servlet ReportBridgeServlet: java.lang.NoClassDefFoundError: com.ibm.tivoli.maximo.report.birt.logging.ReportLoggerFactory
at com.ibm.tivoli.maximo.report.birt.bridge.launcher.FrameworkLauncher.<init>(FrameworkLauncher.java:83)
at com.ibm.tivoli.maximo.report.birt.servlet.MXWebAppOSGiFrameworkLauncher.<init>(MXWebAppOSGiFrameworkLauncher.java:33)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1328)
...... 12000++ lines of errors like this one.
正如环承载者所指出的，此错误与更改 RMI 端口无关。然而，当我将 proprieties 文件更改回 13400 时，没有任何错误。
问题
如何更改每个应用程序服务器的 RMI 端口？
假设
我希望它位于应用程序服务器中的某个位置。
The set up
I have websphere 6.1 running two application servers. Each running the same application (Maximo). Each application point to a different database.
There is a third party app that connects VIA an RMI port of 13400.
Both Maximo applications have this in the proprieties file.
mxe.registry.port=13400
The issue
When the third party program makes a call to the RMI port the wrong application processes gets the call.
What I have tried
I can't find anything in the WebSphere console that would let me change the port.
Changing the RMI port in the Maximo properties file to 13400 and redeploying the ear. Then changed the port on the third party software. No dice. In fact I get a Error 500 System not bound on when accessing Maximo.
ServletWrappe E SRVE0100E: Did not realize init() exception thrown by servlet ReportBridgeServlet: java.lang.NoClassDefFoundError: com.ibm.tivoli.maximo.report.birt.logging.ReportLoggerFactory
at com.ibm.tivoli.maximo.report.birt.bridge.launcher.FrameworkLauncher.<init>(FrameworkLauncher.java:83)
at com.ibm.tivoli.maximo.report.birt.servlet.MXWebAppOSGiFrameworkLauncher.<init>(MXWebAppOSGiFrameworkLauncher.java:33)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1328)
...... 12000++ lines of errors like this one.
As ring bearer pointed out this error doesn't correlate with changing the RMI port. Yet when I change the proprieties file back to 13400 there are no error what so ever.
The Question
How do I change the RMI port for each application server?
Hypothesis
I'm hoping it's somewhere in the application server.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
终于找到了我要找的东西：
在 maximo.properties 文件中添加这个...
我将其设置为 12222 重建了耳朵并重新部署。端口 12222 从未打开。
真正的问题是 mxe.name 所有应用程序在属性文件中都具有相同的名称。更改名称解决了问题。
https://www-304.ibm.com/support/docview.wss ?uid=swg21262022
Finally found what I was looking for:
In the maximo.properties file add this...
I set it to 12222 rebuilt the ear and redeployed. Port 12222 never opened up.
The real issue was the mxe.name all there applications had the same name in the proprieties file. Changing the names resolved the issue.
https://www-304.ibm.com/support/docview.wss?uid=swg21262022
登录管理控制台并遵循此选择路径 - Application_servers >服务器1>端口> BOOTSTRAP_ADDRESS
请注意，一旦您进入“Server1”选择页面，端口链接将出现在右侧的“Communications”部分下
假设您的默认服务器名称为 server1
您将看到一个屏幕，您可以在其中编辑 BOOTSTRAP_ADDRESS 的端口号 - 这是 WebSphere Application Server 名称服务或 RMI 连接器端口。
Logon to admin console and follow this selection path - Application_servers > server1 > Ports > BOOTSTRAP_ADDRESS
Note that once you are on the "Server1" selection page, the ports link will appear on the right hand side, under "Communications" section
Assuming your default server name is server1
You will have a screen where you can edit port number for BOOTSTRAP_ADDRESS- which is the WebSphere Application Server name Service or RMI Connector Port.
复制您的 weblogic 文件夹并将其重命名为其他名称。您可以更改第二个实例上的设置。
Make a copy of your weblogic folder and rename it something else. You can change the settings on the second instance.