Admin Console Applet Login Connection Error

Hello,
I have done some Corba programming before and now I want to do more
serious work on Tuxedo. So I wish you will bear with my simple questions.
- I have brought up Tuxwsvr and wlisten (no errors) and listner is
running on port 3050 (windows platform)
- Now I open the web admin page and insert my login/pass (I have
controled it in the "tlisten.pw" file and its correct.
- The applet issues the error : "Connection Failed"
I appreciate if someone can help or forward me to an FAQ if this is a
frequently asked question.
Regards,
Mac

Mac,
This error usually indicates tuxwsvr can not connect to the wlisten. So you
need to make sure wlisten started correctly.
The default port for "tlisten" is 3050, if you specify it to wlisten in the
%TUXDIR%\udataobj\webgui\webgui.ini, then wlisten can not bind to the same
port.
So I would suggest configure another port and have a try.
Regards,
Wayne
"news.bea.com" <[email protected]> wrote in message
news:[email protected]..
Hello,
I have done some Corba programming before and now I want to do more
serious work on Tuxedo. So I wish you will bear with my simple questions.
- I have brought up Tuxwsvr and wlisten (no errors) and listner is
running on port 3050 (windows platform)
w
- Now I open the web admin page and insert my login/pass (I have
controled it in the "tlisten.pw" file and its correct.
- The applet issues the error : "Connection Failed"
I appreciate if someone can help or forward me to an FAQ if this is a
frequently asked question.
Regards,
Mac

Similar Messages

Weblogic Admin console applet does not load

I have installed Weblogic 6.1 SP3 with JDK 1.4.2_03. The admin console applet was
working initially but when I installed oracle 8.1, the applet failed to load.
A cross sign appears instead of navigation applet tree in the console application.
I have set the classpath and java_home variables correctly. I tried to point java_home
to jdk1.3.1 (java version shipped with Weblogic 6.1) and also changed entire classpath
to point to jdk1.3.1 but no effect. The same configuration works on another machine
where oracle is not installed.
Please help...
Thanks in advance
Mahesh

If you have any pride you will get off Tripod as quickly as possible. It forces popups and other unwanted advertising on visitors. Any time I see that a site is on Tripod or About, I just ignore it and click the next choice.
BTW if you stay on Tripod, you should consider changing the 'e' in your user name to an 'o'.

Admin console applet error

I have successfully installed the Weblogic Server 6.1 (sp2), in Win XP Professional. When I started the admin. console http://server:7001/console...it is not able to load left navigation tree. I also tried loading Java Applet in Internet Explorer, to check it. But it says Internet Explorer is ignoring <APPLET> tags. Please help!!

In XP Professional , i think there is no Java VM to run applets.
Either install the SUN's Java VM or Microsoft's Java VM which can be
downloaded separately.
Let me know if it works.
Karthi.
"Kumar.M" <[email protected]> wrote in message
news:3f8e2489$[email protected]..
I have successfully installed the Weblogic Server 6.1 (sp2), in Win XPProfessional. When I started the admin. console
http://server:7001/console...it is not able to load left navigation tree. I
also tried loading Java Applet in Internet Explorer, to check it. But it
says Internet Explorer is ignoring <APPLET> tags. Please help!!

Just downloaded JMS (3.6) and the admin console is getting an error...

Upon running the admin console I am getting this error "java.Lang.ClassNotFoundException.javax.help.HelpBroker" for some reason I am not going to be able to get any online help at all???
what is the problem and how can I fix this?

Start Firefox in [[Safe Mode]] to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
* Don't make any changes on the Safe mode start window.
See:
* [[Troubleshooting extensions and themes]]
* [[Troubleshooting plugins]]
If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.
* Use "Disable all add-ons" on the [[Safe mode]] start window to disable all extensions.
* Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")

7.5 -Admin Console - Active X control error

Hi,
When i try to open BPC admin Console, its opening a blank page with Title "BPC Active X document framer Control"
How to fix this issue? this in BPC 7.5 MS
Thanks in advance

Hi,
sometimes the admin console doesn't open right and it's remain only the shell but normally if you close and reopen than it's open correctly.
Kind regards
Roberto

Unable to change password from admin console getting the following error

BEA-159907
USER admin INVOKED ON Security:Name=myrealm AD METHOD getCurrentName PARAMS Users6839815711
Info: USER user INVOKED ON objectId METHOD method PARAMS params
can any one help me out

Hi,
Please try changing it using WLST Script: http://middlewaremagic.com/weblogic/?p=4334
or still if you are facing any issue then Reset the Admin Server Account Using: http://middlewaremagic.com/weblogic/?p=323
Or else please post the complete Stack Trace from the Server Log.
Thanks
Jay SenSharma

Could not retain the repository connections in portal admin console.

Hi
i have created additional WLP repository (stream based) in oracle.
and configured as datasource in server console. and added respective JNDI name in portal admin console.
and i could add/delete the content. But when ever i am restarting the machine i am loosing the added connection from portal admin console only.the connection configuration server console is safe.
each time i have to configure it with same JNDI name add work with it in portal admin console only when ever i restart the machine.
The content and datasources configuration is safe .
but When ever i am creating additional WLP repository i could not see the respective details have updated in content-mgmt.xml in EAR meta-inf.
is that because of that. if so why it is getting updated when it is adding new connection in admin console.

When you create a Repository connection at run-time using the Portal Admin, the configuration is written to a Deployment Plan. By default, the Deployment Plan is written to a location which can be deleted during an application redeployment. You can specify a location for the deployment plan, which will not get deleted, via the WebLogic Server Console or you can add the information to the content-config.xml in <earProject>/meta-inf.
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/deployment.html#wp1045617
Brad

Can't start manager server on other machine from admin console

hi, m fredzh
i have weblogic 10.3.2 where i created a cluster named cluster1 on production mode
the machines and servers list as follow:
cluster1 192.168.1.100
--machine1
--server1 192.168.1.100
--machine2
-server2 192.168.1.101
i create nodemanager on machine2, and set the type as ssl, the listener address 192.168.1.101,
then login on 192.168.1.101, and run wlst.sh , nmEnroll and then start startNodemanaged.sh ..
start server2 on the admin console(on 192.168.1.100), failed and the log as follow:
can anbody help me, thank you..
==============================================================================
<Critical> <WebLogicServer> <localhost.localdomain> <managerServer2> <main> <<WLS Kernel>> <> <> <1286788326928> <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:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
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:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
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:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
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:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:125)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:173)
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:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
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:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: fredzh on 2010-10-12 下午6:54

hi,Jay
i followed the steps as follow:
1、change prod mode to dev
2、modified the config.xml entrys on the all two servers:
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<credential-encrypted>test</credential-encrypted>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
3、enrolled the node, then started the two adminservers, started server2's nodemanager..server2 can be started from the cluster admin console.
4、change the dev mode to prod mode on admin console, it failed throw error:
"in production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean"
i checked the config.xml ,the entrys i had changed were not aotomatically encrypted,may i manually encryp the clear text value? ..follow is 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>cluster_domain</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>cluster_domain</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>
<anonymous-admin-lookup-enabled>false</anonymous-admin-lookup-enabled>
<credential-encrypted>test</credential-encrypted>
<web-app-files-case-insensitive>false</web-app-files-case-insensitive>
<compatibility-connection-filters-enabled>false</compatibility-connection-filters-enabled>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<principal-equals-case-insensitive>false</principal-equals-case-insensitive>
<principal-equals-compare-dn-and-guid>false</principal-equals-compare-dn-and-guid>
<downgrade-untrusted-principals>false</downgrade-untrusted-principals>
<enforce-strict-url-pattern>true</enforce-strict-url-pattern>
<cross-domain-security-enabled>false</cross-domain-security-enabled>
</security-configuration>
<jta>
<security-interop-mode>default</security-interop-mode>
</jta>
<server>
<name>AdminServer</name>
<ssl>
<hostname-verifier xsi:nil="true"></hostname-verifier>
<hostname-verification-ignored>true</hostname-verification-ignored>
<export-key-lifespan>500</export-key-lifespan>
<client-certificate-enforced>false</client-certificate-enforced>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<inbound-certificate-validation>BuiltinSSLValidationOnly</inbound-certificate-validation>
<outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
<allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
<use-server-certs>false</use-server-certs>
</ssl>
<listen-port>7110</listen-port>
<listen-address></listen-address>
</server>
<server>
<name>server2</name>
<machine>machine2</machine>
<listen-port>7110</listen-port>
<listen-address>192.168.1.101</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>/opt/jdk1.6.0_21</java-home>
<bea-home>/root/Oracle/Middleware</bea-home>
<root-directory>/root/Oracle/Middleware/user_projects/domains/cluster_domain</root-directory>
<username>weblogic</username>
<password-encrypted>{AES}xhSI75AxXtXdMrCXRgA2uY5pfcxUGE9X4YXTjfe1XEY=</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>machine2</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>192.168.1.101</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<admin-server-name>AdminServer</admin-server-name>
</domain>
Edited by: fredzh on 2010-10-13 下午7:57

11g node manager reachable but server does not start from admin console

I have a issue with node manager is reachable from admin console and from command prompt it is not connected and could not able to start the managed server.
If i change /config/nodemanager/nm_password.properties plain text and restart it is not reachable in admin console abut can connect from command prompt. I could not able to start the even with this scenario.
i see below error when try to check machine monitor tab.
<Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'dom_11gint' for user 'Ckr10ycOJN' denied".>
Ckr10ycOJN username in config.xml
node manager and managed servers are not root user process.
Please help me if have any suggestions.

Pls. make sure the following points in your environment.
1) Check '*nodemanager.domains*' file in <<WL_HOME>>\commo\nodemanager directory
     a) This file should have the entry for your domain 'dom_11gint'.
     b) Ensure the path referred in the nodemanager.domains file is correct one.
2) Ensure the following remote server startup parameters are passed properly.
     a) In the Admin Console, Navigate Servers --> <<SERVER_NAME>> -->Configuration --> Server Start
     b) Pass the required Class Path, Arguments, User Name, Password(User name and Password to boot the managed servers)

Admin Console not logging in on AWS

This topic has come up a lot and I've ready through many of them, but none of them seem to have my exact issue. I recently setup Flash Media Server on Amazon EC2 and things are going well so far; however the admin console wont login. I've set the username, password, and port in the config file and opened that port, among others, in the security group. I've then restarted both FMS and admin server multiple times.
When I try to login I get no errors. Nothing happens at all. When I open FireBug and/or Fiddler2 to watch the communication, I'm not seeing a single thing happen. Clicking "Login" submits no requests at all. Do I just not understand how FMS works? I would assume some sort of request would need to be made.
Eric

Does firebug/fiddler captures "rtmp" traffic - i suppose not and hence you are not catching anything.
Are you able to telnet to <serverip>:1111 from your machine(which you are using to login) ?
Also did you check Admin logs if there is anything logged and also checked if Admin server started successfully.

Unable to access Admin Console

Hi,
I have installed Oracle Database11g and WebLogic 10.3.0 Application Server successfully in LINUX-64 bit environment. At the end of OIM server 9.1.0.1 it displays "The Oracle Identity Manager Application Server setup has some problem. Refer OIM_HOME/Xellerate/logs/setup_weblogic.log for information about the problem" in the console. So, when i able to access Admin console. It throws Error:404.
Also setup_weblogic.log has the following error details
BUILD FAILED
/oracle/oimserver/xellerate/setup/setup.xml:443: The following error occurred while executing this line:
/oracle/oimserver/xellerate/setup/weblogic-setup.xml:196: Could not create task or type of type: wlst.
Ant could not find the task or a class this task relies upon.
Also nexaweb.war and xlWebApp.war is missing in Weblogic console page-> Deployment tab.
I have reinstalled the weblogic and OIM again but still getting the same problem..
Please help me to resolve this issue.
Thanks in advance.
Regards
Katheresh
Edited by: Katheresh on May 10, 2010 9:47 PM

Hey Kathy
did you setup ORACLE_HOME to weblogic_home, JAVA_HOME and added java to PATH. Also do you have any other ANT installed on your server.
Have you checked the OIM certification matrix for the version of various components like OIM, Weblogic and Database.
If you are sure that you did all this correctly, then perform the following:
The nexaweb classloader error is seen at times prior to performing the post installation steps. Then make a backup of the weblogic domain directory and the <OIM_HOME> directory.
1. Please continue and perform the postinstallation steps.
2. Restart the server
3. In the weblogic console, shcek to see that the xellerate and nexaweb applications have an "ok" status.
4. If not:
a. Please upload the oim server log.
b. Using the WebLogic console undeploy all oim applications including, xellerate, nexaweb and, if there, XIMDD, and SPML.
c. Delete the directory <OIM_HOME>/xellerate/webapp/precompiled
d. Delete the xellerate.ear and Nexaweb.ear from the directory <OIM_HOME>/xellerate/OIMApplications (Note: do this on all nodes of the cluster)
e. Delete the ant_backup.jar, optional_backup.jar and xercesImpl_backup.jar files from the OIM_HOME/xellerate/ant/lib directory.
f. Delete the xellerate and Nexaweb directories from the BEA_HOME/user_projects/domains/DOMAIN_NAME/servers/AdminServer/tmp/_WL_user directory.
g. Delete the xellerate and Nexaweb directories from the BEA_HOME/user_projects/domains/DOMAIN_NAME/servers/MANAGED_SERVER_NAME/tmp/_WL_user directory.
Delete the xellerate and Nexaweb directories from the BEA_HOME/user_projects/domains/DOMAIN_NAME/servers/MANAGED_SERVER_NAME/stage directory.
h. In the OIM_HOME/xellerate/setup/weblogic-setup.xml file:
i. Search for the following element:
<wldeploy action="deploy"
source="${WL_APP_LOCATION}/OIMApplications/WL${application.filename}"
name="Xellerate"
user="${weblogic_login_user}"
password="${weblogic_login_password}"
verbose="true"
adminurl="t3://${weblogic_server_target_url}:${weblogic_server_admin_port}"
debug="${action.deploy.debug}"
targets="${wl.deploy.target}" />
ii. Add a timeout value of 5400 as shown:
<wldeploy action="deploy"
source="${WL_APP_LOCATION}/OIMApplications/WL${application.filename}"
name="Xellerate"
user="${weblogic_login_user}"
password="${weblogic_login_password}"
verbose="true"
adminurl="t3://${weblogic_server_target_url}:${weblogic_server_admin_port}"
debug="${action.deploy.debug}"
targets="${wl.deploy.target}"
timeout="5400" />
i. Restart the WebLogic server and managed servers.
j.Open a terminal session and export the the JAVA_HOME and PATH environment variables.
k. In the same terminal session, change to the directory <OIM_HOME>/xellerate/setup
l. Run "patch_weblogic.sh"
This should reinstall that xellerate applications on WebLogic.
Hope this helps.

Fix for Admin Console UN/PW problem!!

Hi all,
The following will allow you to log on to the AdminConsole after setup in Win2000.
First, open config.xml for your in your \bea\weblogic600\config\yourdomain directory in an editor. I used XMLWriter, but I'm sure Notepad would work.
Next, find the following:
<Security Name="mydomain" GuestDisabled="false"/>
Add a SystemUser attribute to the line so that it looks like this:
<Security Name="mydomain" GuestDisabled="false" SystemUser="system"/>
where "system" is the UserName you want to log into the AdminConsole with.
Now, fire up the Admin Console and login with this username. The password will be the password you entered during setup. To locate this password, open password.ini from the same directory where you found the XML file. Open password.ini in Notepad to see your password. If it's empty, no password is required.
Good luck
Bill

Can you check if your admin-server's server.xml (admin-server/config/server.xml) has the following settings?
<default-auth-db-name>ldap</default-auth-db-name>
<auth-db>
    <name>ldap</name>
    <url>ldap://<hostname>:<port>/<base-dn></url>
    <property>
      <name>bindpw</name>
      <value><passwd></value>
      <encoded>true</encoded>
    </property>
    <property>
      <name>binddn</name>
      <value><binddn-value></value>
    </property>
</auth-db>Can you also verify if the file under admin-server/config/default-sun-web.xml has the following settings?
# cat default-sun-web.xml
<?xml version="1.0" encoding="UTF-8"?>

<sun-web-app>
<security-role-mapping>
    <role-name>admin</role-name>
    <group-name><your_group></group-name>
</security-role-mapping>
</sun-web-app>- Amit

Why cannot login to weblogic admin console . no error.

Why I cannot login to weblogic admin console. I keep getting login screen. I reset the userid and password but still cannot login
Here is what's in the log file:
Sep 26, 2010 8:55:14 PM EDT> <Warning> <HTTP> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914272> <BEA-101296> <Unable to load the default compiler class "com.sun.tools.javac.Main". Using the default javac compiler to compile JSPs.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914319> <BEA-000365> <Server state changed to STANDBY>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914335> <BEA-000365> <Server state changed to STARTING>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <SAFService> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-281003> <SAF Service has been initialized.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <SAFService> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-281002> <SAF Service has been started.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <WseeCore> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914351> <BEA-220502> <The Wsee Service is starting>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Deployer> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914366> <BEA-149209> <Resuming.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Diagnostics> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-320000> <The Diagnostics subsystem is initializing on Server myserver.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Store> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=C:\mydomain\servers\myserver\data\store\diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Store> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914413> <BEA-280009> <The persistent file store "WLS_DIAGNOSTICS" (430fff8d-1448-4efe-ae57-8e17de6fd97a) has been opened: blockSize=512 actualWritePolicy="Disabled(single-handle-non-direct)" explicitIOEnforced=false records=0.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Log Management> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914429> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to C:\mydomain\servers\myserver\logs/mydomain.log.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Log Management> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914429> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Diagnostics> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914507> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914538> <BEA-000365> <Server state changed to ADMIN>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914569> <BEA-000365> <Server state changed to RESUMING>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Management> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914663> <BEA-141052> <The auto deployment poller has started.>
####<Sep 26, 2010 8:55:14 PM EDT> <Info> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002610> <Dynamic Listener Service initialized.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <Server> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-002613> <Channel "Default" is now listening on 172.16.37.59:7001 for protocols iiop, t3, ldap, snmp, http.>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548914694> <BEA-000331> <Started WebLogic Admin Server "myserver" for domain "mydomain" running in Development Mode>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914741> <BEA-000365> <Server state changed to RUNNING>
####<Sep 26, 2010 8:55:14 PM EDT> <Notice> <WebLogicServer> <TAXWARE_TEST> <myserver> <main> <<WLS Kernel>> <> <> <1285548914741> <BEA-000360> <Server started in RUNNING mode>
####<Sep 26, 2010 8:55:15 PM EDT> <Info> <J2EE> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548915429> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
####<Sep 26, 2010 8:55:15 PM EDT> <Info> <EJB> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548915569> <BEA-010008> <EJB Deploying file: mejb.jar>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916085> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916179> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916194> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916194> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916210> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <WebService> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548916210> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Sep 26, 2010 8:55:16 PM EDT> <Info> <EJB> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548916288> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
####<Sep 26, 2010 8:55:27 PM EDT> <Info> <WorkManager> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1285548927226> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<Sep 26, 2010 8:55:28 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548928226> <BEA-423101> <[console] Initializing the NetUIx container>
####<Sep 26, 2010 8:55:28 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548928523> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
####<Sep 26, 2010 8:55:29 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548929164> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
####<Sep 26, 2010 8:55:29 PM EDT> <Info> <netuix> <TAXWARE_TEST> <myserver> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1285548929195> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
####<Sep 26, 2010 8:56:14 PM EDT> <Info> <Health> <TAXWARE_TEST> <myserver> <weblogic.GCMonitor> <<anonymous>> <> <> <1285548974540> <BEA-310002> <86% of the total memory in the server is free>

There is no error. Is there another domain on your OS? can you please put here your config.xml file and your login screen image here.
May be you use wrong console to login.

Error 500--Internal Server Error while login to OIM11gr2 admin console

could you help me how to resolve this error
I have installed and configured OIAM 11gr2(11.1.2.0.0)->SOA 11.1.1.6.0 on oracle linux 6.4
every thing goes good but got a problem while login to admin console(Admin console:: \\localhost:14000\sysadmin)
it throws the error << Error 500--Internal Server Error_
*javax.servlet.ServletException: oracle.iam.identity.exception.UserManagerException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException*
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
>>>>
many thanks
Jagdish.

am able to login
http://192.168.75.140:7001/console/login/LoginForm.jsp
from this environment-> servers-> all servers(adminserver,soa_server1, oim_server1, oam_server1) status is running,and health is ok.
I have started these servers from command line <base_domain/bin/sh startManagedWebLogic.sh oim_server1
result is <server started in running mode>
now I shutdown the oam_server1 and oim_server1
again I started the oim_server1 as above
command line result is < <May 30, 2013 7:54:47 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
but in (http://localhost:7001/console) window oim_server1 status is unknown...

Admin console login error

Hi i just downloaded the jdk-6u6-windows-i586-p.exe and java_ee_sdk-5_05-windows-nojdk.exe .I installed them both and start the server.But when i want to login the admin page i get this error below.After getting this error i simply refresh the page and im in the admin page.Also im getting this page below some features of admin page.For example application server page's jvm tab and logging tab.
Any suggestions and solutions would be great thanks
HTTP Status 500 -
type Exception report
message
descriptionThe server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: java.lang.reflect.InvocationTargetException while attempting to process a 'beforeCreate' event for 'sun_page1'.
root cause
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException while attempting to process a 'beforeCreate' event for 'sun_page1'.
root cause
java.lang.reflect.InvocationTargetException
root cause
java.lang.reflect.UndeclaredThrowableException
root cause
javax.management.AttributeNotFoundException: AdminSessionTimeoutInMinutes
note The full stack traces of the exception and its root causes are available in the Sun Java System Application Server 9.1_02 logs.
Sun Java System Application Server 9.1_02

When I get same error I changed locale en_US

Admin Console Applet Login Connection Error

Similar Messages

Maybe you are looking for