Weblogic Admin Authentication
I want to write an application which will be authenticated by weblogic for the
same login as the admin login console.
Is that possible, how can I do it?
I am not sure i understand this completely.
Create a webapp and allow only "system "to access it .
The webapp docs show how you can restrict access to the different components of a
webapp using web.xml and weblogic.xml files
Anand wrote:
I want to write an application which will be authenticated by weblogic for the
same login as the admin login console.
Is that possible, how can I do it?
Similar Messages
-
Authentication denied on Weblogic admin console
I was playing with security policy for web applications and now I can't login from
console any more. It gives following error : Authentication Denied
The username or password has been refused by WebLogic Server. Please try again.
I can start the server from command line. How can I find out what is the problem
and how can I fix it ?
Thanks,
MKHi AB.
You can write your own pages and add them to WebLogic admin console by writing a console extension, here is a link to bea doc http://e-docs.bea.com/wls/docs100/console_ext/understandext.html
Regards,
Felix -
Weblogic Admin server - Configuration/Server Start/Arguments ignored?
Hi,
I'm trying to specify a http proxy for a WebLogic Admin Server in order for an application to access external resources. I've placed the settings into the "Server Configuration / Server Start / Arguments", and verified that they have been saved into the config/config.xml file for that domain:
<server-start>
<arguments>-Dhttp.proxyHost=[XXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXX]</password-encrypted>
</server-start>
However, no matter how I start the server, these settings are ignored despite that the documentation states these should be added to the java command line.
starting weblogic with Java version:
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
As a test I created a new managed server in the same domain, specifying the same startup properties, and they were picked up during startup.
If I manually place the settings into the bin/setDomainEnv.cmd batch file for the domain they are also picked up and work.
Is there an undocumented restriction on Admin Servers that they ignore the "Server Start / Arguments" setting, or is there something else I can check as to why this is not working?
Many thanks,
- Micha.Umm... I already pasted the relevant snippet out of the config.xml, but following is the entire file. The startup arguments, as specified in the admin console, are:
-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080
which matches what is saved in the 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>wls_starter</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>wls_starter</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>[XXXXXXXXXX]</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>[XXXXXXXX]</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<max-http-message-size>-1</max-http-message-size>
<ssl>
<enabled>false</enabled>
</ssl>
<log>
<file-name>logs/AdminServer.log</file-name>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-min-size>500</file-min-size>
<rotate-log-on-startup>true</rotate-log-on-startup>
<logger-severity>Trace</logger-severity>
<logger-severity-properties></logger-severity-properties>
<log-file-severity>Info</log-file-severity>
<stdout-severity>Info</stdout-severity>
<domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
<memory-buffer-severity>Debug</memory-buffer-severity>
<log4j-logging-enabled>false</log4j-logging-enabled>
<redirect-stdout-to-server-log-enabled>false</redirect-stdout-to-server-log-enabled>
<domain-log-broadcaster-buffer-size>1</domain-log-broadcaster-buffer-size>
</log>
<machine>[XXXXXXXXXX]</machine>
<listen-port>8080</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<web-server>
<frontend-http-port>0</frontend-http-port>
<frontend-https-port>0</frontend-https-port>
<keep-alive-enabled>true</keep-alive-enabled>
<keep-alive-secs>30</keep-alive-secs>
<https-keep-alive-secs>60</https-keep-alive-secs>
<post-timeout-secs>30</post-timeout-secs>
<max-post-size>-1</max-post-size>
<send-server-header-enabled>false</send-server-header-enabled>
<wap-enabled>false</wap-enabled>
<accept-context-path-in-get-real-path>false</accept-context-path-in-get-real-path>
</web-server>
<listen-address></listen-address>
<java-compiler>javac</java-compiler>
<tunneling-enabled>false</tunneling-enabled>
<tunneling-client-ping-secs>45</tunneling-client-ping-secs>
<tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
<server-start>
<arguments>-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXXXXX]</password-encrypted>
</server-start>
<server-life-cycle-timeout-val>30</server-life-cycle-timeout-val>
<startup-timeout>0</startup-timeout>
<graceful-shutdown-timeout>30</graceful-shutdown-timeout>
<ignore-sessions-during-shutdown>false</ignore-sessions-during-shutdown>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
</server>
<embedded-ldap>
<name>wls_starter</name>
<credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<machine>
<name>[XXXXXXXXXX]</name>
</machine>
<jms-server>
<name>WseeJmsServer</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<jms-server>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<self-tuning>
<work-manager>
<name>weblogic.wsee.mdb.DispatchPolicy</name>
<target>AdminServer</target>
</work-manager>
</self-tuning>
<file-store>
<name>WseeFileStore</name>
<directory>WseeFileStore</directory>
<target>AdminServer</target>
</file-store>
<jms-system-resource>
<name>WseeJmsModule</name>
<target>AdminServer</target>
<sub-deployment>
<name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
<target>WseeJmsServer</target>
</sub-deployment>
<descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<sub-deployment>
<name>[XXXXXXXXXX]</name>
<target>[XXXXXXXXXX]</target>
</sub-deployment>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jdbc-system-resource>
<saf-agent>
<name>ReliableWseeSAFAgent</name>
<target>AdminServer</target>
<store>WseeFileStore</store>
</saf-agent>
</domain> -
Changing the weblogic admin user password
I have faced an issue in reseting weblogic admin user password. Following are the steps i have executed in sequence.please help to understand why it is not working this way
I have 2 managed instances running on two separate computers.
`Step 1.` shutdown the admin server instance ( i did not shutdown the node manager and other 2 manage server instances
`Step 2.` Set the environment variables
`cd $DOMAIN_HOME/bin`
. ./setDomainEnv.sh
`Step 3.` then executed the command below to create the new password
cd ../security
mv DefaultAuthenticatorInit.ldift oldDefaultAuthenticator
java weblogic.security.utils.AdminAccount weblogic new_password .
`Step 4.` backed up existing `boot.properties` file and created a new file. Also backed up data directory of admin server. created a new `boot.properties` file with following configuration
with plain text username(weblogic_admin) and password (new_password).
cd ../servers/AdminServer
mv data data_old
cd security/
mv boot.properties oldboot.properties
Step 5. Then i restarted the admin server. admin server is restarted successfully and i was able to login the admin console with my new username and password. Issue came when i try to shoutdown the admin server. when i execute sh stopWeblogicAdmin.sh , it will through following exception. But , if i kill the admin server process , then i am able to start the admin server with out any problem. and i am able to login to the server also. I am also able to stop and start manage server instances through admin console. But why it is failing only when i try to stop.could anybody help me on this
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://jipsl13t:12001 with userid weblogic_admin ...
This Exception occurred at Fri Jan 18 12:20:09 GMT-00:00 2013.
javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic_admin, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:682)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:520)
at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:573)
at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:313)
at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx4.connect$1(<iostream>:16)
at org.python.pycode._pyx4.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx15.f$0(/product/jip/jipsl11t/wls/eni132_domain/shutdown.py:6)
at org.python.pycode._pyx15.call_function(/product/tsm/jipsl11t/wls/eni132_domain/shutdown.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.util.PythonInterpreter.execfile(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
Caused by: java.lang.SecurityException: User: weblogic_admin, failed to be authenticated.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Problem invoking WLST - Traceback (innermost last):
File "/product/jip/jipsl11t/wls/eni132_domain/shutdown.py", line 6, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : User: weblogic_admin, failed to be authenticated.
Use dumpStack() to view the full stacktrace
Done
Stopping Derby Server...
Edited by: user8643895 on Jan 18, 2013 9:28 AMHi,
This issue was occurring because stopWebLogic.sh was picking the username and password from properties user config files in user's home directory: username-WebLogicConfig.properties, username-WebLogicKey.properties.
If the credentials for weblogic server are changed then new user config files should be created, if these are not created then stopWebLogic.sh will pick up the old credentials and hence fail.
Please refer the following document for information on user configuration files:
http://docs.oracle.com/cd/E21764_01/web.1111/e13813/reference.htm#WLSTC430
Connecting to the server after deleting username-WebLogicConfig.properties, username-WebLogicKey.properties resolves the issue as it forces the script to use the credentials provided by the user while running stopWebLogic.sh
There are two ways you can resolve this issue:
1) Create new user config files with the correct credentials as explained in the following document:
http://docs.oracle.com/cd/E21764_01/web.1111/e13813/reference.htm#WLSTC430
Or
2) To force the stopWeblogic.sh script to use credentials provided by the user while running the script follow these steps:
In the stopWeblogic.sh file use the following connect command:
connect(userConfigFile='',userKeyFile='', url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')instead of:
connect(${userID} ${password} url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')Hence in the stopWebLogic.sh script replace:
echo "import os" >"shutdown.py"
echo "if os.environ.has_key('wlsUserID'):" >>"shutdown.py"
echo " wlsUserID = os.environ['wlsUserID']" >>"shutdown.py"
echo "if os.environ.has_key('wlsPassword'):" >>"shutdown.py"
echo " wlsPassword = os.environ['wlsPassword']" >>"shutdown.py"
echo "connect(${userID} ${password} url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')" >>"shutdown.py"
echo "shutdown('${SERVER_NAME}','Server')" >>"shutdown.py"
echo "exit()" >>"shutdown.py"with:
echo "import os" >"shutdown.py"
echo "if os.environ.has_key('wlsUserID'):" >>"shutdown.py"
echo " wlsUserID = os.environ['wlsUserID']" >>"shutdown.py"
echo "if os.environ.has_key('wlsPassword'):" >>"shutdown.py"
echo " wlsPassword = os.environ['wlsPassword']" >>"shutdown.py"
echo "connect(userConfigFile='',userKeyFile='', url='${ADMIN_URL}', adminServerName='${SERVER_NAME}')" >>"shutdown.py"
echo "shutdown('${SERVER_NAME}','Server')" >>"shutdown.py"
echo "exit()" >>"shutdown.py"
Regards,
Kishore -
Conver weblogic Admin server to a windows service
I used the following scripts to conver weblogic Admin server to a windows service :
SETLOCAL
set DOMAIN_NAME=Sayesaman
set USERDOMAIN_HOME=C:\jdev11.1.1.6\user_projects\domains\Sayesaman
set SERVER_NAME=Sayesaman
set WL_HOME=C:\jdev11.1.1.6\wlserver_10.3
set WLS_USER=weblogic
set WLS_PW=weblogic110
set PRODUCTION_MODE=false
set MEM_ARGS=-Xms512m –Xmx512m
call "C:\jdev11.1.1.6\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
after running these scripts the windows service created successfully and running properly .
but the state of all web application is failed and even I can't deploy any web application and I get the following error :
Class Not Found : oracle.dms.wls.DMSServletFilterr
Please help me to conver weblogic Admin server to a windows service correctly .
Edited by: 950222 on Aug 1, 2012 2:46 AMRequest you to share the entire stack of error.
Meanwhile,I would recommend that you deleet the existing service created and re-create the service by following the below steps:-
1. Create a text file
%MIDDLEWARE_HOME%\user_projects\domains\servers\AdminServer\security\boot.properties
Add the following lines
username=weblogic
password=
Important to Note:
a. If this step is not performed you will see the following generic error when the Admin Server is started in " background mode " via an MS Windows Service.
BEA-090403 Authentication for user weblogic denied
This error occurs because, by default, startup of Admin Server interactively prompts for the weblogic username and password. If the password is not supplied the error is thrown.
b. As soon as you start the Admin Server the username and password values in this file will be encrypted. Be sure to stop / start the Admin Server as soon as possible to ensure the credentials are not exposed for longer than necessary.
2. Create a command script called installAdmServer_Service.cmd which has lines like
SETLOCAL
set DOMAIN_NAME=ClassicDomain
set USERDOMAIN_HOME=C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "C:\middleware\FMW11g\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
3. For troubleshooting / debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it include the -log parameter e.g
"%WL_HOME%\server\bin\beasvc" -install
-svcname:"%DOMAIN_NAME%_%SERVER_NAME%"
-javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%"
-extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%"
-cmdline:%CMDLINE%
-log:"C:\Middleware\FMW11g\user_projects\domains\ClassicDomain\%SERVER_NAME%-stdout.txt"
4. Now run "installAdmServer_Service.cmd". The Service should be installed, it will have a name like ""beasvc %DOMAIN_NAME%_%SERVER_NAME%" e.g
beasvc ClassicDomain_AdminServer
The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.
Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for AdminServer to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Notes:
An alternative to the boot.properties approach to specifying the Admin Server weblogic username / password is to add the following environment variables to your wrapper cmd script - installAdmServer_Service.cmd
set WLS_USER=weblogic
set WLS_PW=manager11g
The beasvc utility encrypts the login credentials and stores them in the Windows registry.
This is one of two possible methods for avoiding the username/password prompt when a server instance starts. The disadvantage to this method is that changing the username or password for the server instance requires you to delete the Windows service and set up a new one with the new username and password. Instead of this method, you can use a boot identity file. With a boot identity file, you can change the login credentials without needing to modify the Windows service.
Create a MS Windows Service for a Managed Server e.g WLS_FORMS
Important to Note:
1. The ADMIN_URL value should reference the AdminServer hostname and listen port.
2. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
3. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
<Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
3. Now run "installAdmServer_Service.cmd". The Service should be installed, it will have a name like ""beasvc %DOMAIN_NAME%_%SERVER_NAME%" e.g
beasvc ClassicDomain_AdmServer
The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.
Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Hope this helps!
-Sandeep -
How to prepend or append classpath using weblogic.Admin or WLST
When I call weblogic.Admin or WLST, is there any way to append or prepend to the existing classpath?
Currently I am calling weblogic.Admin with the following argument:
set -mbean base_domain:Name=base-server,Server=base-server,Type=ServerStart -property ClassPath "C:\test\test.jar"
But this overwrite the Server classpath with the new entry.
I want to keep the existing entries as it is and add the new one. Is it possible with Weblogic 8.1 or Weblogic 9.1fyi
A tricky SQL statement issue was fixed in the example application
at http://www.consideringred.com/files/oracle/2011/SQLAuthenticatorApp-v0.03.zip
So, it allows for the setup of a SQLAuthenticator (see README.txt for details), but in short : run Ant target "wlst.create-domain" (possibly preceded by Ant target "delete.domain-dir"), Ant target "create.wls-start-stop-bat-files", run wls-start.bat, setup tables TS_USER, TS_GROUP and TS_GROUPMEMBER, Ant target "wlst.create-datasource", Ant target "wlst.create-authentication-provider", run wls-stop.bat, run wls-start.bat, Ant target "wlst.create-user", Ant target "wlst.create-group.sqla-groupname", Ant target "wlst.add-user-member-to-group", deploy SQLAuthenticatorApp (using JDeveloper or otherwise), try http://localhost:7001/sqlauthenticatorweb , try to authenticate using tsusertwo/welcome1
Several Ant targets calling OPSS MBeans API were added (e.g. "wlst.opss.printmembersforallapplicationroles"), to review adding a SQLAuthenticator group as member to an application role, resulting in the forum thread "OPSS : addMembersToApplicationRole : The search for role failed"
at OPSS : addMembersToApplicationRole : The search for role failed
So, suggestions to resolve that grant application role issue are welcome in that forum thread.
regards
Jan -
Weblogic admin console default password ?
Hi All
I am trying to log in to Peoplesoft Weblogic admin console
http://<server>:<port>/console/login/LoginForm.jsp is the url i am using and i am getting the log in page
entered the default user id and password as " system and password as password "
Below is the error message:
Authentication Denied
The username or password has been refused by WebLogic Server. Please try again.
What could be the reason?
WebLogic Server "PIA" version: WebLogic Server 10.3.1.0
PeopleTools 8.50
HR 9.1
Tuxedo10gR3_32_win_2k3_x86_VS2005
Have installed successfully, and Peoplesoft application is working fine.
Please let me know.
Thanks for your help.
Edited by: AfjalK on Dec 26, 2009 12:21 PMThe logon credentials have changed from Tools 8.50. Instead of system/password it's now system/Passw0rd. It is in the install guide but I didn't spot it first time through either.
Duncan -
Error starting weblogic Admin server
Hi All,
I am not very familiar with Fusion and weblogic but here is my situation:
Background: I am trying to install Fusion Middleware so I can integrate Oracle Transport Management with E-Business Suite (as per note Integrating Oracle E-Business Suite Release 12 with Oracle BPEL in Oracle SOA Suite 11g (Doc ID 1321776.1))
I just installed the following on Oracle Enterprise Linux 64bits
- SOA Suite 11.1.1.7.0
- Weblogic Server 10.3.6
-JDK 1.7.0_25
-Jdev 11.1.1.7.0
When starting the weblogic Admin server using "DOMAIN_HOME/startWebLogic.sh' I get an error:
Starting weblogic with Java version:
Unrecognized option -jrockit
Error: Could not create the Java virtual machine
I found a few thread with similar issue (for different versions of SOA suite) where it got fixed by changing some parameters in the cmd file but I am not sure they apply to my case.
Is the jdk version compatible? (I can start JDeveloper ok) , if not which one is the appropriate version. If i need to change it, can you provide details of how to do it? (I am not expert on SOA/Jdev )
Can you please help me here ?
Thanks in advance!Well, I tested it
java -version and it shows :
1.7.0_25
Java HotSpot 64 bit Server VM
--> So I guess the problem is I don't seem to have the jrockit.
I donwloaded it (Rel 28.7) and installed it. During installation it says "for JDK 1.6.0_45"
Anyway. I let it install anyway and I modified the PATH to point to the Jrockit bin directory. Then run java -version and it now shows JDK 1.6.0_45 and jvm as rockit
Now I tried to start the weblogic server and I get the same error. it still uses the JDK 1.7
So.. again.. is this supported with JDK 7 ?
How can I fix it now that I installed everything using the JDK 7?
Thanks -
No output at all from weblogic.Admin HELP | GETSTATE | VERSION on linux
Hi, somehow I am getting zero output from weblogic.Admin command, is it redirected somewhere?
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD VERSION
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD GETSTATE
#>
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -username weblogic -password $WPWD HELP
#>
Thanks.Hi,
You need to Run the SetDomainEnv.sh/cmd from the Domain_Home/bin and then you can execute the below Commands and they will execute succesfully
Eg:From Windows Environment Same applies in Linux Environmet as well
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 VERSION
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 GETSTATE
Current state of "AdminServer" : RUNNING
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 HELP
Usage: java [<SSL trust options>] weblogic.Admin
[ [-url | -adminurl] [<protocol>://]<listen-address>:<port>]
-username <username> [-password <password>]
<COMMAND> <ARGUMENTS>
Hope it helps -
Is there a way to disable concurrent Weblogic Admin Console sessions for the same user?
A coworker on another workstation and I are able to log into same user account on the Weblogic Admin Console at the same time. I would like to restrict access so only one session per user account can be logged in to the Admin Console. Is this possible?
Alternatively, is there a way to log identifiable information (IP/workstation) when multiple sessions for one account occur at the same time?
I am using 10.3.6.0Hi,
You could also check the http access logs for such info. There you could see records for the received requests, with each record starting with the source IP that initiated the request.
The default location for access logs is ${DOMAIN_HOME}/servers/${SERVER_NAME}/logs. Of course in your case, the ${SERVER_NAME} would be your admin server name (AdminServer if left as default).
Regards,
Mohab -
Setting timeout in weblogic.admin command
Hello:
I run a script that checks the state of several thing in my platform. One of the commands I use in this script
is
java -cp .. weblogic.Admin localhost:7001 ..... GETSTATE
IS there anyway to set a timeout in this command for the case weblogic server is hang and doesn´t answer anything. I have tried using sun properties for connect timeout and readTimeout but they haven´t worked(I suppose that it is because weblogic.admin uses t3 instead http). I have thought to make the following
sleep 10|ps -efx| grep -i GETSTATE|grep -v grep|awk '{ print $2 }'|xargs kill -9 &
java -cp .. weblogic.Admin localhost:7001 ..... GETSTATE
but I don´t like at all this solution
Regards,
Mario.hi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM -
Not able to start the weblogic admin server
Hi,
I am getting the error while starting the weblogic admin server of OAM console.
Below is the stack trace of the error
####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834234> <BEA-000000> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834387> <BEA-000000> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
####<Sep 18, 2013 4:47:14 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834847> <BEA-000000> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
####<Sep 18, 2013 4:47:15 AM IST> <Info> <Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459835526> <BEA-000000> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the username attribute value of {AES}MCSBg4hMfpsECc7LXYV6gR52kLO5DHUWyo9I1UZXMaE= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the password attribute value of {AES}1hgzo9/RGaCoWQyFXIJEbYMqmz5gg9LQzjQ/J6DxbQM= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849081> <BEA-000000> <Server state changed to STARTING>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WorkManager> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849088> <BEA-000000> <Initializing self-tuning thread pool>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849138> <BEA-000000> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849208> <BEA-170019> <The server log file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849213> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Diagnostics> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849260> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3s" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "http" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "https" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiop" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiops" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldap" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849310> <BEA-002622> <The protocol "cluster" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849311> <BEA-002622> <The protocol "clusters" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849313> <BEA-002622> <The protocol "snmp" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002622> <The protocol "admin" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <RJVM> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849325> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address :7003
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Sep 18, 2013 4:47:29 AM IST> <Critical> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849347> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: weblogic.security.internal.encryption.EncryptionServiceException
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000365> <Server state changed to FAILED>
####<Sep 18, 2013 4:47:29 AM IST> <Error> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849411> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849412> <BEA-000236> <Stopping execute threads.>
Kindly help me to solve this issue.
Is anyone had faced this issue.....Hi,
I had tried by putting the username and password in boot.properties but we are getting the same issue.
we tried by editing the config.xml file of the domain.
i.e. by
Before: <credential-encrypted>{AES}b3I7UhWtRyj4DuKMIDVtW4Ln2nzH+HiYRhhQw1H2qpU0qJMOaDlK8iFZ+LvlJu+iZs6pptFJgWz8ryyudL1Zyvf00Rg11z9Iib7hoDC8covMFuig8wx7iOGK88zeKH7U</credential-encrypted>
After: <credential-encrypted>MyCredentialInPlainText</credential-encrypted>
and restarted the admin server but shows the same error.
kindly suggest us... -
Weblogic Admin Server Doesnt start.
I have installed Oracle 11g, RCU (WCC 11.1.1.6), Web Center Content 11.1.1.6 (C:\Oracle\Middleware\Oracle_ECM1) and created a domain for Content and was trying to restart the Weblogic Admin Server (C:\Oracle\Middleware\user_projects\domains\WC_Domain6\bin).
I get the below error:
'C:\Oracle\MIDDLE~1\Oracle_ECM1\ucm\idc\bin\\Installer -noCommEnv -platform win3
2 -dumpFormat %s=%s -show IDC_NATIVE_PATH' is not recognized as an internal or e
xternal command,
operable program or batch file.
Content Server provided no native path information in idcCommEnv.cmd.
'C:\Oracle\MIDDLE~1\Oracle_ECM1\ucm\idc\bin\\Installer -noCommEnv -platform win3
2 -show NativeOsUtils_classpath' is not recognized as an internal or external co
mmand,
operable program or batch file.
The directory name is invalid.
Any help is greatly appreciated. Thank you.I have a batch file i create that will start everything up. I don't think i've ever seen your error, but the admin server can be called using the startWeblogic up one dir from Bin, i dont know if it makes a difference but i've always used that one. Copy and paste below into a text file (update your paths and urls accordingly), rename to a .bat and you should be able to start everything at once
@echo off
START "ECMAdmin" C:\Oracle\Middleware\user_projects\domains\IMTST\startweblogic.cmd
TIMEOUT 100
START "NodeManager" C:\Oracle\Middleware\wlserver_10.3\server\bin\startNodeManager
TIMEOUT 15
START "soaserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic soa_server1 http://IMTSTipm01:7001
START "UCMserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic UCM_server1 http://IMTSTipm01:7001
TIMEOUT 150
START "IPMserver1" C:\Oracle\Middleware\user_projects\domains\IMTST\bin\startmanagedweblogic IPM_server1 http://IMTSTipm01:7001 -
Weblogic Admin server restart issue
While restarting Oracle Weblogic Admin server, it is not running after below log.
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
Mar 12, 2015 7:33:07 PM oracle.security.jps.internal.idstore.util.LibOvdUtil pushLdapNamesToLibOvd
INFO: Pushed ldap name and types info to libOvd. Ldaps : DefaultAuthenticator:idstore.ldap.provideridstore.ldap.Hi,
These messages are Info Message Can you please post the complete Error stack for the same
Check the below threads which have similar issue reported
Integrated JDeveloper Weblogic 12C issues
Weblogic server not starting due to OutOfMemory
SOA Suite 12c Integrated Weblogic / Coherence Issue
Unable to run my application
Hope it helps -
WebLogic Admin server fails to start after reboot
Hi Gurus,
Weblogic Admin server won't start up after a server reboot. Note that weblogic was gracefully shutdown before the restart.
Also note that the following files were accidentally deleted after the reboot (but I don't think that should cause an issue..):
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
Looking at the AdminServer.log:
*####<Oct 11, 2012 11:27:53 AM EDT> <Critical> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969273846> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException:*
java.lang.AssertionError: weblogic.management.provider.EditFailedException:
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:79)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: weblogic.management.provider.EditFailedException:
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:81)
at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274051> <BEA-000365> <Server state changed to FAILED>
####<Oct 11, 2012 11:27:54 AM EDT> <Error> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274053> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274069> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274140> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274141> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274146> <BEA-220028> <Web Service reliable agents are suspended.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274153> <BEA-220029> <Web Service reliable agents are shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <MessagingBridge> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274318> <BEA-200001> <The messaging bridge service has successfully shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274426> <BEA-040308> <JMS service is suspending.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274506> <BEA-040107> <Undeployed 8 default connection factories.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274510> <BEA-040015> <JMS shutdown is complete.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274530> <BEA-001144> <Force Suspending the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274536> <BEA-001146> <Force suspend of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274538> <BEA-001147> <Shutting down the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274552> <BEA-001149> <Shutdown of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274694> <BEA-000236> <Stopping execute threads.>
Kindly guide me with this. Thanks!
Edited by: Kent Pawar. on Oct 11, 2012 8:51 AMIssue is :
Caused By: weblogic.management.provider.EditFailedException:
One probable reason can be some change made to the config.xml file . If you have previous backup for the config.xml file then try to replace the config.xml file and restart the server .
Another reason for this exception may be that there were some changes made to configuration through the Admin Console which were not activated completely and Admin Server was restarted . under this scenario weblogic will create a /pendig dir and have a config.xml file created there with the un-activated changes .
some workaround you can try to restore the Admin Server :
Under domain dir ,
\pending directory -- take backup and delete the dir .
Under Admin Server Dir :
data\store --- take backup and delete the dir .
thanks,
Sandeep
Maybe you are looking for
-
We use MP3 files for music at church. I need to access my music files and send them to a D/A through a USB port then to my mixer. (Much better quality than internal audio card) Guidance please!! "G"
-
How do I select rows where 2 numbers are closest?
Hi, I need to select one row from each person where the days are the closest between the rows. In this example, I have rows of order data, and when a company first set up an account and then a column with the number of days it took for a certain orde
-
Battery replacement in different country
Hi All, I found that if your phone is in a different country from where you bought it, Apple will NOT provide you with the battery replacement. So I need to travel from India to UK, just to get the replacement. This when, Apple provided me with a def
-
Why is it that my iMovie app keeps shutting off randomly! I'm trying to export my movie and it shuts down each time it's a 1/4 of the way through downloading! Ah! Please help.
-
Hi, i am new to SAP and new to this group also, Can any one help me how to create new employee(HR) in SAP using the BAPIs, after creation of employee how can i check the new employee details in SAP.Can one give me step by step approach to solve this