首页 > Linux操作系统 > Linux操作系统 > Disabling global security when the V5.0 administrative server cannot be started

Disabling global security when the V5.0 administrative server cannot be started

原创 Linux操作系统 作者:echo_huang 时间:2019-06-27 22:12:05 0 删除 编辑


2、同时在“本地 OS 用户注册表 ”中输入的服务器用户标识和密码是对应操作系统的登录用户名和密码的。



Technote (FAQ)

If the administrative server is running, you can use either the administrative console or the wsadmin tool to disable security. However, if you cannot start the administrative server, you must use wsadmin to disable security. This technote explains the procedure.

Occasionally when WebSphere® global security is enabled and you need to be disable it, you cannot start the administrative Application Server or deployment manager. This situation can occur when the administrative server does not start due to a problem with the security configuration. In this case, you are locked out of the administrative console, and you cannot use it to disable security; therefore, you must use a wsadmin command to disable security.


You can disable security by modifying the security.xml file or by using wsadmin.

The security.xml file is located under install_root/config/cells/cellname. Always store a copy of the security.xml file in a temporary directory before making any changes.

To disable security in security.xml:

  1. Open the security.xml file and search for the very first occurrence of enabled="true". This is located inside the tag.
  2. Change enabled="true" to enabled="false", then save the file.
  3. You must restart the server for the change to take effect.

    To disable security using a wsadmin command:

    From the $WAS_HOME/bin directory of the Deployment Manager or application server, issue the following command:

    wsadmin -conntype NONE

    The result is a command-line prompt for wsadmin.
  4. Issue the following wsadmin command:


来自 “ ITPUB博客 ” ,链接:,如需转载,请注明出处,否则将追究法律责任。

下一篇: httpd.conf中文说明
请登录后发表评论 登录


  • 博文量
  • 访问量