Weblogic HA for Active-Passive Admin Server configuration

Hi,
We are trying to install Admin servers in Active passive mode in a single domain to manage single set of managed servers (for OAM component). The scenerio is that I have Admin Server + Managed Server on OAMHOST1 and OAMHOST2 both. I can start Admin server on OAMHOST1 and then manage both the managed servers on OAMHOST1 and OAMHOST2. Now in case my Admin Server on OAMHOST1 goes down, the requirement is that secondary Admin Server on OAMHOST2 should be started and use to manage the managed servers on OAMHOST1 and OAMHOST2. So i have stopped the admin server on OAMHOST1 and then tried to start the Admin Server on OAMHOST2 but its not starting up. It is simply throwing the error that port 7001 on OAMHOST1 is in use but i can clearly see that there is no service running on 7001 port on OAMHOST1 and ALSO why its trying to connect OAMHOST1:7001. As per oracle documentation this is feasible (this is mentioned in their HA guide) but they haven't mentioned any step to configure this or test this.
Please advise if anyone has any idea to implement this. Since OAM admin is deployed on Admin server, the HA is crucial for Admin Server unavailability.

Hi,
From your note, I think OAMHOST1 and OAMHOST2 are physical hostnames of the server. You need to create one virtual ip which will be listened from both the physical servers and change the listen address for admin server to this VIP. Please see below mentioned link. Also there is requirement of shared directory, for that you can refer to the enterprise deployment guide for identity management.
http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e21032/create_domain_im.htm#CFHBIAIC
Regards,
Kishore

Similar Messages

How to Uninstall SQL instance on active-passive SQL server , which failed during Cluster Setup (Error-Failed at Validate Active Directory Configuration)

How to Uninstall SQL instance on active-passive SQL server , which failed during Cluster Setup (Error-Failed at Validate Active Directory Configuration)
active-passive SQL server cluster setup failed due to some steps missed in initial cluster setup,
now i have unistall sql instance from nodes,
Your help will higly appriciated.
Regards,
Anish
Asandeen

Hello,
Please refer to the following link about remove a node of SQL Server Failover Cluster Instance:
http://msdn.microsoft.com/en-us/library/ms191545.aspx#Remove
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

RMAN for active passive 10g R2 RAC

Hi,
I am having 10g R2 Active-Passive RAC setup.
in this environment,If I am taking the backup using RMAN,
how can I handle the failover?
In active-active instance, if channel allocated to one node is failed, backup will be completed from channel allocated to other node.
how can i handle the failover in active-passive RMAN backup??/

What was the reason you went for active/passive RAC setup ?
--> this is requirement.
I thought cluster could achieve the same thing.
1) How can we achive active/passive setup by using cluster?
2) In RAC active/passive configuration and Cluster setup, which one is good option?
3) Any URLs on this topic
Thanks in Advance....
Regards:
Abdul Rajak

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>

Step for Active/Passive RAC Patching (CPU Patch )

Hi
I know how to patch active /active configuration patching done in RAC.
I need to patch (CPU) for acitve/passive , how to i proceed ,is it the same ? i.e i can open passive node any how and the patch one by one .
Please suggest the step

Hi,
1) Will the 9.2.0.8 upgrade patching modified the SYSTEM tablespace and corresponding SYSTEM datafilesYes it will modify the SYSTEM tablespace and corresponding datafiles.
If I upgrade my active primary database first, will I be still able to upgrade the passive primary database without error laterYes u can upgrade passive primary database without error later
I shall be patching the database after failover the passive DB to become activecan u elaborate this further.
I suggest u to create a formal service request at MyoracoleSupport
Regards,
X A H E E R

Weblogic jDriver for oracle/xa thin driver configuration

          Hi,
          I try to configure an XA thin connection pool to oracle.
          Using the configuration from page 16-11 of adminguide.pdf,
          the start is with the error "No suitable driver".
          The driver is configured like that:
          DriverClassname=oracle.jdbc.xa.client.OracleXADataSource
          Also, with the classes12.zip for oracle 8.1.7 for jdk1.2 taken from oracle site,
          before weblogic.jar in classpath, same error:(.
          The error:
          <Jan 14, 2001 2:22:01 PM EET> <Error> <JDBC> <Cannot startup connection pool "OracleJDBCTxConnectionPool"
          weblogic.common.ResourceException: java.sql.SQLException: No suitable driver
               at java.sql.DriverManager.getConnection(DriverManager.java:537)
               at java.sql.DriverManager.getConnection(DriverManager.java:177)
               at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:111)
               at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:88)
               at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:68)
               at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:194)
               at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
               at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
               at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
               at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
               at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
               at $Proxy41.updateDeployments(Unknown Source)
               at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
               at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
               at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
               at $Proxy34.start(Unknown Source)
               at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
               at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
               at weblogic.management.Admin.finish(Admin.java:520)
               at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
               at weblogic.Server.main(Server.java:35)
               at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:203)
               at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
               at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
               at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
               at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
               at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
               at $Proxy41.updateDeployments(Unknown Source)
               at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
               at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
               at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
               at $Proxy34.start(Unknown Source)
               at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
               at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
               at weblogic.management.Admin.finish(Admin.java:520)
               at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
               at weblogic.Server.main(Server.java:35)
          >
          Thank you in advance.
          kind regards, adrian


          Hi,
          it works :) !
          Thank you,
          Adrian
          "John Harby" <[email protected]> wrote:
          >
          >Mine seems to work ok but I have classes12.zip after weblogic.jar.
          >
          >set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.C:\oracle\ora81\jdbc\l
          >ib\classes12.zip;.\config\examples\serverclasses
          >
          >
          >"adrian balaban" <[email protected]> wrote:
          >>
          >>Hi,
          >>
          >>I try to configure an XA thin connection pool to oracle.
          >>
          >>Using the configuration from page 16-11 of adminguide.pdf,
          >>the start is with the error "No suitable driver".
          >>
          >>The driver is configured like that:
          >>DriverClassname=oracle.jdbc.xa.client.OracleXADataSource
          >>
          >>Also, with the classes12.zip for oracle 8.1.7 for jdk1.2 taken from
          >oracle
          >>site,
          >>before weblogic.jar in classpath, same error:(.
          >>
          >>The error:
          >>
          >><Jan 14, 2001 2:22:01 PM EET> <Error> <JDBC> <Cannot startup connection
          >>pool "OracleJDBCTxConnectionPool"
          >>weblogic.common.ResourceException: java.sql.SQLException: No suitable
          >>driver
          >>     at java.sql.DriverManager.getConnection(DriverManager.java:537)
          >>     at java.sql.DriverManager.getConnection(DriverManager.java:177)
          >>     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:111)
          >>     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:88)
          >>     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:68)
          >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:194)
          >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
          >>     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
          >>     at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
          >>     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
          >>     at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          >>     at java.lang.reflect.Method.invoke(Native Method)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
          >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          >>     at $Proxy41.updateDeployments(Unknown Source)
          >>     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
          >>     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
          >>     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
          >>     at java.lang.reflect.Method.invoke(Native Method)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
          >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          >>     at $Proxy34.start(Unknown Source)
          >>     at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
          >>     at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
          >>     at weblogic.management.Admin.finish(Admin.java:520)
          >>     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
          >>     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
          >>     at weblogic.Server.main(Server.java:35)
          >>
          >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:203)
          >>     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:54)
          >>     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:707)
          >>     at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:306)
          >>     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:679)
          >>     at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:109)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
          >>     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          >>     at java.lang.reflect.Method.invoke(Native Method)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
          >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          >>     at $Proxy41.updateDeployments(Unknown Source)
          >>     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2571)
          >>     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:333)
          >>     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:149)
          >>     at java.lang.reflect.Method.invoke(Native Method)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:587)
          >>     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:573)
          >>     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:319)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >>     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          >>     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          >>     at $Proxy34.start(Unknown Source)
          >>     at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
          >>     at weblogic.management.Admin.startApplicationManager(Admin.java:1098)
          >>     at weblogic.management.Admin.finish(Admin.java:520)
          >>     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:473)
          >>     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
          >>     at weblogic.Server.main(Server.java:35)
          >>>
          >>
          >>Thank you in advance.
          >>
          >>kind regards, adrian
          >

Weblogic Error(unable to start Admin Server)

"Error Message"
In the linux terminal I tried to start the Weblogic Adminserver. While starting the weblogic server it is showing the following error.
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode)
Starting WLS with line:
/mwhome/BEA/Middleware/jdk160_21/bin/java -client -Xms768m -Xmx1536m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=AdminServer -Djava.security.policy=/mwhome/BEA/Middleware/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/mwhome/BEA/Middleware/wlserver_10.3 -Dwls.home=/mwhome/BEA/Middleware/wlserver_10.3/server -Dweblogic.home=/mwhome/BEA/Middleware/wlserver_10.3/server -Dcommon.components.home=/mwhome/BEA/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/mwhome/BEA/Middleware/user_projects/domains/soa_domain -Djrockit.optfile=/mwhome/BEA/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/mwhome/BEA/Middleware/user_projects/domains/soa_domain/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/mwhome/BEA/Middleware/user_projects/domains/soa_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/mwhome/BEA/Middleware/user_projects/domains/soa_domain/config/fmwconfig/carml -Digf.arisidstack.home=/mwhome/BEA/Middleware/user_projects/domains/soa_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/mwhome/BEA/Middleware/user_projects/domains/soa_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/mwhome/BEA/Middleware/user_projects/domains/soa_domain/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/mwhome/BEA/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/mwhome/BEA/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=/mwhome/BEA/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/mwhome/BEA/Middleware/Oracle_SOA1 -Dsoa.instance.home=/mwhome/BEA/Middleware/user_projects/domains/soa_domain -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/mwhome/BEA/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/mwhome/BEA/Middleware/oracle_common -Djava.awt.headless=true -Dums.oracle.home=/mwhome/BEA/Middleware/Oracle_SOA1 -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/mwhome/BEA/Middleware/patch_wls1034/profiles/default/sysext_manifest_classpath:/mwhome/BEA/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
<Sep 8, 2011 5:41:07 PM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Sep 8, 2011 5:41:07 PM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Sep 8, 2011 5:41:07 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 17.0-b17 from Sun Microsystems Inc.>
<Sep 8, 2011 5:41:07 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<Sep 8, 2011 5:41:09 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Sep 8, 2011 5:41:09 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Sep 8, 2011 5:41:09 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file /mwhome/BEA/Middleware/user_projects/domains/soa_domain/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Sep 8, 2011 5:41:09 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /mwhome/BEA/Middleware/user_projects/domains/soa_domain/servers/AdminServer/logs/AdminServer.log00033. Log messages will continue to be logged in /mwhome/BEA/Middleware/user_projects/domains/soa_domain/servers/AdminServer/logs/AdminServer.log.>
<Sep 8, 2011 5:41:09 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /mwhome/BEA/Middleware/user_projects/domains/soa_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
Sep 8, 2011 5:41:10 PM oracle.security.jps.internal.credstore.ssp.CsfWalletManager openWallet
WARNING: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:177)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:217)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:139)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:126)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:114)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:52)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:798)
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:792)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:792)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:289)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:282)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:261)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
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)
<Sep 8, 2011 5:41:10 PM IST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider>
<Sep 8, 2011 5:41:10 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:282)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:261)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:847)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:289)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:282)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:261)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:792)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:289)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:282)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:261)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:808)
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:792)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:792)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:289)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.credstore.CredStoreException: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
at oracle.security.jps.internal.credstore.ssp.CsfWalletManager.openWallet(CsfWalletManager.java:177)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.doInit(SspCredentialStore.java:217)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:139)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:126)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:114)
Truncated. see log file for complete stacktrace
>
<Sep 8, 2011 5:41:10 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 8, 2011 5:41:10 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 8, 2011 5:41:10 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
"Hope I'll get a solution soon"

You probably run the WebLogic once as the super user and are now trying to run it as another.
you could issue a chown or chmod -R 777
Also a remark that provided here: Opening of wallet based credential store failed. Reason java.io.IOException
"It appears the my config/fmwconfig/cwallet.sso file was corrupted, possibly by a previous WebLogic crash. The cwallet.sso file in my fmwconfig directory was only 77bytes, but it should have been larger. I was able to find a previous version of the cwallet.sso file in the /tmp/cred* directories, and restored the file. That allowed me to start up WebLogic, but I had lost some data in cwallet.sso that I needed to re-enter in FMW Control."

Admin server configuration

I have a domain that within resides a number of servers for developers. What
I would like to do is create user id's for the developers within the domain.
I want these id's to have access to only there respective server(s) within
the domain. This is for the purpose of prohibiting a developer from
inadvertently shutting down another developer's server.
Do anyone know if this is possible?
Herb Smith
Systems Engineer
BEA Systems, Inc.
7300 W. 110th St. 7th Floor
Overland Park, KS 66210
Phone: (913) 317-1668
Mobile: (816) 550-7588

I have a domain that within resides a number of servers for developers. What
I would like to do is create user id's for the developers within the domain.
I want these id's to have access to only there respective server(s) within
the domain. This is for the purpose of prohibiting a developer from
inadvertently shutting down another developer's server.
Do anyone know if this is possible?
Herb Smith
Systems Engineer
BEA Systems, Inc.
7300 W. 110th St. 7th Floor
Overland Park, KS 66210
Phone: (913) 317-1668
Mobile: (816) 550-7588

How to configure admin server failover in weblogic

Hi all,
Can anyone please tell me how can I configure Admin server failover in weblogic.
Please guide!!

Hi,
From the word "Failover" this means you are doing Active-Passive configuration for weblogic Admin server. For Active-Passive clustering, without shared storage you can do it. But the domain directory should be on a storage mount point, when node -1 will do down the same mount point should be mounted to node2.
mark If this helps.
Thanks,
Kishore

Weblogic does not support failover for the admin server.

There is a single point of failure in the current weblogic architecture. If the
admin server dies there is no automatic alternate admin server.

That is true, and we plan to fix it in one of the next major releases. Currently
the story is not as bad as it appears to be for following reasons:
1. Failure of admin server doesn't mean failure of already running managed server.
2. You can start a new server as admin server of domain with discover flag=true and
it will recognize all already exisiting managed server.
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
naresh gupta wrote:
There is a single point of failure in the current weblogic architecture. If the
admin server dies there is no automatic alternate admin server.

Weblogic 8.1 managed server unable to contact Admin server

I have a strange issue here.
I have admin server on Linux Machine A
Managed server on Linux Machine B.
When i try to start managed server on Machine B, i get the following error.
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://MachineA:7100/wl_management_internal2/Bootstrap, user: system
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readFully(ObjectInputStream.java:2571)
at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:1990)
The error suggests that managed server on machine B, is unable to contact Admin server on Machine A.
But i know for sure that Admin server is running on that port 7100 for sure.
It has been for the last 3 years.
To see if Machine B and Machine A have network issues, i did telnet.
From Machine B: i typed the following
telnet MachineA 7100
Connected to MachineA.
Escape character is '^]'
The above telnet command tells us that no network issues exist.
After a few tries, the managed server contacts to admin server and comes up.
This is not a one time thing.
I saw this behavior many times.
How should i resolve this?
Edited by: gvamsius on Feb 12, 2009 1:23 PM

Every thing is configured fine.
Nothing wrong with Configuration.
This domain has been running for the past 3 years.
Recently, i found something interesting in admin server logs, when i try to start the managed servers.
I realized there will be some amount of hand shake that happens during managed server startup, when it tries to communicate with admin server.
Here is the log snippet when managed server A contacts Admin server and starts up successfully.
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server A.>
####<Mar 10, 2009 12:11:46 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> <*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Here is the log snippet when managed server B contacts Admin server and does not start.
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server B.>
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server B.>
####<Mar 10, 2009 12:07:08 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server B.>
The difference as you can see here is that managed server starts up only when Admin Server does the following
<*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Does any one knows why Admin server would not send the above bootstrap configuation all the times for the managed servers?

Non-domain user authentication against SSAS on Active/Passive Cluster

Hello,
We have an Active/Passive SQL Server setup (DB1 & DB2 Servers) connected to a cluster for SQL & SSAS. I have a web server not on the same domain that I am trying to authenticate with SSAS. This works OK if I set the website to impersonate
myUser and I add local account myUser as an Admin on SSAS for the active server (DB1). But when this fails over to DB2 then it fails to authenticate. SSAS won't allow us to add myUser as an admin for local accounts on both DB1 & DB2 as it errors
adding the second one. Could anyone advise how such a scenario should be approached?
We have tried creating a domain user too which DB1 & DB2 can of course both share but I don't think the web server can impersonate this with being not part of the domain.
Thanks.

Hi Jcorker,
According to your description, you need to access the SQL Serve Analysis Services database which is configured as cluster for SQL & SSAS from another domain, right?
In SSAS we can use the solution below achieve the requirement.
1.Create new domain account and impersonate the web site with that.
2.Create local user account on the analysis service with same exact username/password as like domain account created in the previous step.
However, you cannot create a local account with the same name on both servers. I have tested it on my local environemnt, we can create the same local account with the same name on both servers. In your scenario, if DB1 and DB2 on different server, you can
create a local account with the same name on both servers. Please post the detail errors, so that we can make further analysis.
Besides, SSAS only allows users of the same domain or trusted domains and it does not allow users from any domain except from these two. You can configure the trust relationship between the domains.
http://technet.microsoft.com/en-us/library/cc961481.aspx
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Error Admin server

Hi all,
I've a snowleopard server on 10.6.8.
After a reboot of the server, I opened admin server but impossible to see my list of services in the left column.
By going on the forums, I saw that we could remove preferences files. But I made a mistake, I deleted in the root Library com.apple.servermgrXXX.plist files.
So now when I open adminserver: he said "admin backup server was not able to connect."
Help me... please.
Is there a way to recreate the admin server configuration?
Thanks so much (and excuse me for my bad english "googled")
Arnaud

the correct file that you need modify is setDomainEnv.sh
File: $DOMAIN_HOME/bin/setDomainEnv.sh
Add the next lines:
if [ "${SERVER_NAME}" = "soa_server1" ] ; then
        EXTRA_JAVA_PROPERTIES="-Xms256m -Xmx5000m -XX:PermSize=256m -XX:MaxPermSize=5000m ${EXTRA_JAVA_PROPERTIES}"
        export EXTRA_JAVA_PROPERTIES
fi
Note: Replace "soa_server1" for your AdminServer Name.
After that you need to restart your weblogic.

Managed server trying to start as admin server

I have one VM with SOA Suite that it is fully functional.
I made a copy of that VM and changed the hostname and IP.
Making a search under all the disk I replaced all occurences of the old hostname and IP with the new ones.
Now I can start AdminServer and soa_server, but when I try to start bam_server I'm getting the following error:
weblogic.management.ManagementException: Booting as admin server, but servername, bam_server, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
The steps I'm following to start the servers it is as follows:
cd $NM
wlst.sh
startNodeManager()
nmConnect('weblogic','welcome1','localhost','5556','soa_domain','/u01/app/oracle/user_projects/domains/soa_domain')
nmStart('AdminServer')
nmStart('soa_server')
nmStart('bam_server')
This post is related to this other post, but I don't have permissions to reply on that one, so I created a new one:
starting managed server with nodemanager
Thanks in advance for any tip you can give me.

The servers starts correctly if I run the scripts, but not from the wlst.sh console:
$nohup $WL_HOME/server/bin/startNodeManager.sh > nodemanager.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/startWebLogic.sh > adminserver.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh soa_server > soa_server.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh bam_server > bam_server.out &

Sub:when trying to open "adminisration server configuration"

Hi
all,
when i am trying to open component definitions in admin server configuration, I am getting following error.
An error has occurred creating business component 'Enterprise Service Definitions' used by business object 'Server Admin'. Please ask your systems administrator to check your application configuration.(SBL-DAT-00222)
please let me know the solution.
thanks
sudhakar

Hi,
Maybe you would have already done this activity.
If not just check if the responsibility "Siebel Administrator" is mapped to the user id using which you were getting such errors.
Regards,
Sambit

Weblogic HA for Active-Passive Admin Server configuration

Similar Messages

Maybe you are looking for