如何将监听端口从默认的7001更改为不同的?

Can anyone tell me how to change the default listening port of Weblogic 10.3 to something different? I saw some posts on discussion boards which say that change it under ...//config/config.xml. Even I thought so, but surprisingly, there is no mention of word "port" in that file. Here is the file:

有人能告诉我如何将Weblogic 10.3的默认监听端口更改为不同的吗?我在讨论板上看到了一些帖子，上面写着将它修改为…//config/config.xml。甚至我也这样认为，但令人惊讶的是，在那个文件中没有提到“端口”。这是文件:

<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
  <name>vistakon</name>
  <domain-version>10.3.5.0</domain-version>
  <security-configuration>
    <name>vistakon</name>
    <realm>
      <sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
      <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
        <sec:active-type>AuthenticatedUser</sec:active-type>
      </sec:authentication-provider>
      <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
      <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
      <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
      <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
      <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
      <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
      <sec:name>myrealm</sec:name>
      <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
        <sec:name>SystemPasswordValidator</sec:name>
        <pas:min-password-length>8</pas:min-password-length>
        <pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
      </sec:password-validator>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>{AES}1NMyZAwXiucj9+d8cj/LGFmw+yhHyIj/YprGOq/PA9Vg0Se2+DkV54N5AwFzW+fN2SWvU5YtojWvVSTnifrUdT6uso4fpO6inAa3LQccOQv59VFxdceHOMv2h1dkngxq</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>{AES}tRw5L/hFc8+4J4w1H8uBj3unE0BC06cdk42CyMLR6Pk=</node-manager-password-encrypted>
  </security-configuration>
  <server>
    <name>AdminServer</name>
    <ssl>
      <name>AdminServer</name>
      <enabled>true</enabled>
    </ssl>
    <listen-port>8080</listen-port>
    <listen-port-enabled>true</listen-port-enabled>
    <listen-address></listen-address>
    <java-compiler>javac</java-compiler>
    <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
    <server-diagnostic-config>
      <wldf-diagnostic-volume>Low</wldf-diagnostic-volume>
    </server-diagnostic-config>
  </server>
  <embedded-ldap>
    <name>vistakon</name>
    <credential-encrypted>{AES}U6dM6LlDLLUYzefQ3M3NnsqijzWKSOgqLqNdJHVJEmeIU5v0wRZGm3ffumXif/uX</credential-encrypted>
  </embedded-ldap>
  <configuration-version>10.3.5.0</configuration-version>
  <app-deployment>
    <name>tbl</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>C:\Documents and Settings\bchitte\Desktop\tbl.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
  </app-deployment>
  <app-deployment>
    <name>DatabaseLoggerService</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>C:\Documents and Settings\bchitte\workspace\DatabaseLoggerService\DatabaseLoggerService.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
  </app-deployment>
  <app-deployment>
    <name>ReadingsProgressLogService</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>C:\Documents and Settings\bchitte\workspace\ReadingsProgressLogService\ReadingsProgressLogService.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
  </app-deployment>
  <app-deployment>
    <name>de</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>C:\Documents and Settings\bchitte\workspace\de.vogella.jersey.first\de.vogella.jersey.first.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
  </app-deployment>
  <app-deployment>
    <name>UpdateWIPQService</name>
    <target>AdminServer</target>
    <module-type>war</module-type>
    <source-path>C:\Documents and Settings\bchitte\workspace\UpdateWIPQService\UpdateWIPQService.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
  </app-deployment>
  <jms-server>
    <name>VistakonJMSServer</name>
    <target>AdminServer</target>
    <persistent-store>VistakonFileStore</persistent-store>
  </jms-server>
  <file-store>
    <name>VistakonFileStore</name>
    <target>AdminServer</target>
  </file-store>
  <jms-system-resource>
    <name>VistakonModule</name>
    <target>AdminServer</target>
    <sub-deployment>
      <name>sdVistakon</name>
      <target>VistakonJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/VistakonModule-jms.xml</descriptor-file-name>
  </jms-system-resource>
  <admin-server-name>AdminServer</admin-server-name>
  <jdbc-system-resource>
    <name>jdbc/MSSQL1</name>
    <target></target>
    <descriptor-file-name>jdbc/jdbc2fMSSQL1-5853-jdbc.xml</descriptor-file-name>
  </jdbc-system-resource>
</domain>

9 个解决方案

#1

Simplest option ...your can change it from AdminConsole. Login to AdminConsole--->Server-->--->Configuration--->ListenPort (Change it)!

简单的选择……您可以从AdminConsole更改它。登录到AdminConsole--->服务器->--->配置--->听(修改)!

#2

if your port is 7001, since it's the default it might not be mentioned in the config.xml. config.xml only reports stuff which differs from the default, for sake of simplicity.

如果您的端口是7001，因为它是默认的，在config.xml中可能没有提到它。配置。为了简单起见，xml只报告与默认值不同的东西。

apart from the config.xml, you should look into a number of other places under your domain-home:

除了配置。xml，你应该在你的领域内寻找一些其他的地方:

bin/stopWebLogic.sh
bin/stopManagedWebLogic.sh
bin/startManagedWebLogic.sh
config/fmwconfig/servers/osbts1as/applications/em/META-INF/emoms.properties
config/config.xml
init-info/startscript.xml
init-info/tokenValue.properties

servers/osbts1as/data/nodemanager/osbts1as.url
servers/osbts1as/data/ldap/conf/replicas.prop
servers/osbts1ms1/data/nodemanager/osbts1ms1.url
servers/osbts1ms1/data/nodemanager/startup.properties

servers/osbts1ms2/data/nodemanager/osbts1ms2.url
servers/osbts1ms2/data/nodemanager/startup.properties
startManagedWebLogic_readme.txt
sysman/state/targets.xml

And don't forget to update any internal URIs of your deployed code.

不要忘记更新部署代码的内部uri。

参见http://www.javamonamour.org/2013/04/weblogic-change-admin-port-number.html

Especially changing the listen address/port of the admin can be troublesome. If you change only the managed server, it's a lot easier.

特别是更改管理员的监听地址/端口会很麻烦。如果只更改托管服务器，则会容易得多。

The best option is just rebuilding the domain.

最好的选择就是重建域名。

#3

The following lines are used to control the listen-port of a server, both are necessary:

下面的行用于控制服务器的listen-port，两者都是必需的:

    <listen-port>7002</listen-port>
    <listen-port-enabled>true</listen-port-enabled>

#4

You can change the listen port as per your requirement. This task can be accomplished in two diffrent ways. By changing config.xml file By changing in admin console Change the listen port in config.xml as per your requirement and bounce the domain. Admin Console Login to AdminConsole->Server->Configuration->ListenPort (Change it) Note: It is a bad practice to edit config.xml and try to edit in admin console(It's a good practise as well)

您可以根据您的需求更改侦听端口。这个任务可以用两种不同的方式来完成。通过改变配置。通过更改管理控制台中的xml文件，可以更改配置中的监听端口。根据您的需求xml，并在域上反弹。管理控制台登录到AdminConsole->服务器->配置->监听(更改它)注意:编辑config是一个错误的做法。xml并尝试在管理控制台进行编辑(这也是一个很好的练习)

#5

As my experience, you can add another domain which listens different port than 7001, and use this domain in to deploy app.

根据我的经验，您可以添加一个侦听不同端口的域，而不是7001，并使用这个域来部署应用程序。

Here's an example: http://st-curriculum.oracle.com/obe/fmw/wls/10g/r3/installconfig/install_wls/install_wls.htm

这里有一个例子:http://st-curriculum.oracle.com/obe/fmw/wls/10g/r3/installconfig/install_wls/install_wls.htm

HTH.

HTH。

#6

That file has a listen-port element - that should be what you need to change, although it is currently set to 8080, not 7001.

该文件有一个listen-port元素——这应该是您需要更改的内容，尽管它当前设置为8080，而不是7001。

#7

If you still get the exception in the server startup after changing listen port, you should try changing Pointbase server port and debug port in setDomainEnv.cmd

如果您在更改侦听端口后仍然在服务器启动中获得异常，那么您应该尝试更改setDomainEnv.cmd中的Pointbase服务器端口和调试端口。

#8

I solved the issue by Changing the port no. in adrs-instances.xml file:

我通过改变港口号来解决这个问题。在adrs-instances。xml文件:

\JDEV_USER_HOME\system11.1.1.3.37.56.60\o.j2ee\adrs-instances.xml

\ JDEV_USER_HOME \ system11.1.1.3.37.56.60 \ o.j2ee \ adrs-instances.xml

#9

To update the listen ports for a server: 1.Click Lock & Edit in the Change Center of the webLogic Administration Console 2.expand Environment and select Server 3.click the name of the server and select Configuration > General 4.Find Listen Port to change it 5.click Save and start server.

更新服务器的侦听端口:1。在webLogic管理控制台2的更改中心单击Lock & Edit。展开环境并选择Server 3。单击服务器的名称并选择Configuration > General 4。找个监听端口，把它改成5。单击Save并启动服务器。

#1