SAAJ issue on WLS

Hello,
I have deployed OPA determination server (10.1.0.27 from Edelivery) on my WLS 10.3.1. and I get this issue in the server log when calling the list-rulebases-request
<10.6.2010 9:30:04 CEST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@1e80719 - appName: 'determinations-server', name: 'determinations-server.war', context-path: '/determinations-server', spec-version: '2.5', request: weblogic.servlet.internal.ServletRequestImpl@15a8121[
POST /determinations-server/soap HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://oracle.com/determinations/server/10.0/server/types/ListRulebases"
User-Agent: Jakarta Commons-HttpClient/3.1
Content-Length: 260
]] Root cause of ServletException.
java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
     at weblogic.webservice.core.soap.SOAPMessageImpl.getSOAPBody(SOAPMessageImpl.java:634)
     at com.oracle.determinations.server.servlet.SOAPAction.doAction(SOAPAction.java:324)
     at com.oracle.determinations.server.servlet.DeterminationsServerServlet.doPost(DeterminationsServerServlet.java:227)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     Truncated. see log file for complete stacktrace
Any idea?
Thank you, Ladislav.

Hi Ladislav,
If you look at the section "Deploying Oracle Determinations Server to a Java Application Server" in the Oracle Policy Automation Installation Guide ("Oracle Policy Automation Installation Guide.pdf") you will see that Oracle Determinations Server requires the application server to support SAAJ 1.1, and includes the following guidance:
There is a specific procedure for enabling SAAJ 1.1 support for Oracle Weblogic. This is outlined in the Section Deploying Oracle Determinations Server for Java on Oracle WebLogic Server belowTherefore please read the section "Deploying Oracle Determinations Server for Java on Oracle WebLogic Server" for instructions on how to enable SAAJ 1.1 on Oracle WebLogic Server.

Similar Messages

Performance issue on WLS Plugins

I also have some performance issue on wls plugins. tried to load test to
weblogic directly with 1000 concurrent connection, it's fine on Weblogic
server. when try to use SunOne Web Server 6.0 + wls plugins, it becomes slow
through web server, if configure wls plugins with Weblogic Cluster , even
worse, very slow response. look like this plugins can not support so much of
load . it's a bottleneck.

Duplicate post:
Performance issue on AFPO
Performance issue on AFPO

SSL certificate issue with WLS 10.3

Hi All,
I am facing this issue with my WLS cluster.
<21-Apr-2010 10:42:00 o'clock BST> <Warning> <Security> <BEA-090482> <BAD_CERTIF
ICATE alert was received from system.core.com - 10.15.135.30.
Check the peer to determine why it rejected the certificate chain (trusted CA co
nfiguration, hostname verification). SSL debug tracing may be required to determ
ine the exact reason the certificate was rejected.>
<21-Apr-2010 10:42:00> <Warning> <Uncaught exception in server handler: javax.ne
t.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from
system.core.com - 10.15.135.30. Check the peer to determine wh
y it rejected the certificate chain (trusted CA configuration, hostname verifica
tion). SSL debug tracing may be required to determine the exact reason the certi
ficate was rejected.>
Please suggest. I have also tried the below settings.
Node Manager:
-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false
Admin Server:
-Dweblogic.security.SSL.ignoreHostnameVerification=true
Many thanks in advance.

Hi Sandip,
I am facing this issue right after when I have configured the listen address to my system IP in Machine(NodeManager), earlier it was "localhost".
Also I have tried to generate the certificates e.g.
C:\bea\wlserver_10.3\server\bin>java utils.CertGen -cn system.core.com -keyfilepass DemoIdentityPassPhr
ase -certfile mycertificate -keyfile .keystore
Generating a certificate with common name system.core.com and key strength 1024
issued by CA with certificate from C:\bea\WLSERV~1.3\server\lib\CertGenCA.der file and key from C:\bea\WLSERV~1.3\server
\lib\CertGenCAKey.der file
C:\bea\wlserver_10.3\server\bin>java utils.ImportPrivateKey -keystore DemoIdentity.jks -storepass DemoIdentityKeyStorePa
ssPhrase -keyfile .keystore.pem -keyfilepass DemoIdentityPassPhrase -certfile mycertificate.pem -alias demoidentity
No password was specified for the key entry
Key file password will be used
Imported private key .keystore.pem and certificate mycertificate.pem
into a new keystore DemoIdentity.jks of type jks under alias demoidentity
Tried the above but not wokring. Please advise.
Edited by: R Vashi on 21-Apr-2010 03:38

VARRAY mapping issues using WLS spk2 connection pools

We have an ongoing issue with VARRAY's and WLS Connection pools. The connection
pool of WebLogic does not support certain data structures of Oracle such as VARRAY.
To create array/struct object in java application, we have to register these
objects through array/struct descriptor methods. These methods require Oracle.sql.Connection
as a parameter. There is no way to get Oracle.sql.Connection from Weblogic Server
Connection Pool because the Oracle.sql.Connection is not serializable.
So, what is the recommended solution for a situation in which the application
tends to need to use VARRAYs and can we instead pass tables?
Any recommendations?

More information on this issue.
I'm using the method DriverManager.getConnection(URL) to get a connection to
the database, passing in the name of the connection pool. This method is
throwing the following SecurityException:
java.lang.SecurityException: User "john" does not have Permission
"reserve"
based on ACL "weblogic.jdbc.connectionPool.ICOM_DEV2_A".
When running under the LDAP realm:
-calls to getConnection() from within a jsp fail
-calls to getConnection() from within a Session Bean or Entity Bean work
-calls to getConnection() from a non-EJB class fail if it is called directly
from the jsp
-calls to getConnection() from a non-EJB class work if it is called from a
Session Bean
When running under the RDBMS realm, all calls to getConnection() work,
whether they are a jsp, non-EJB class or a Session Bean.
Is there some security context that is only present inside the EJB
container?

We are having issues with WLS 5.1   pdf   SSL

We are running IE 5.0 and above browser with our application and the server is Weblogic 5.1 We are having issues with a generated pdf being sent down from the server using the response outputStream in an SSL connection. We tried setting the content type before getting the outputstream. IE comes back with a dialog for download. When we select either of the options IE comes back with "Unable to download <url> from <server>. We are using WLS 5.1 service pack 6. Any help will be greatly appreciated


          I tried this option, but did not help. We have two weblogic servers on different
          machines. One works fine in downloading pdf file over https, but not the other.
          The error we are getting after selecting it to save it to a file:
          IE cannot download xx.pdf from www.xxx.com
          From the link, when we say "save target as", we get different error as:
          This file could not be written to cache.
          Someone suggested to pass "pragma: public" or "pragama: no-cache" in the header.
          But we are just simply serving it as a file, neither from servlet nor from jsp.
          So I suspect it something to do with our weblogic proxy or security configuration.
          Any ideas/help is much appreciated.
          Thanks
          Jayashree Raghavan <[email protected]> wrote:
          >If you ever have a similar problem it might help to check in browser
          >settings.
          >In IE goto tools/internet options/
          >Goto advanced Tab
          >go down to Security.
          >Uncheck the "donot save encrypted pages to disk".
          >This will make downloading a pdf work in ssl.
          >
          >
          >Jayashree Raghavan wrote:
          >
          >> We resolved this problem thanks to Maxim, by commenting out the code
          >that sends to the browser not to cache these pdf files. response.setHeader("Pragma",
          >"no-cache");
          >

How to get some good docs for general troubleshooting issues of WLS 8.1?

Hi,
In my company we just have started WLS, m working as WLS admin.
How can i get some good docs for general issues as I m facing a lot problem in this early stage.
If ther is any link, or community which can help me?
I have tried on google n got some basic info.
I think ther r some useful info is available on the site " http://eudownload.bea.com/" but m not able to open it.....is this url is changed?

Troubleshoot Cluster :-
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/cluster/trouble.html
Troubleshoot JMS :-
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs92/jms_admin/troubleshoot.html
Troubleshoot SAF :-
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/saf_admin/troubleshoot.html
Troubleshoot JDBC:-
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/jdbc/troubleshooting.html
Troubleshoot JTA:-
http://download.oracle.com/docs/cd/E11035_01/wls100/jta/trbtrx.html
Its more or less same for all versions. You can refer to specific version docs. Hope this helps.

WLST : We face this issue on WLS 8.1, 9.2, 10.3

Hi All,
Unless I have a copy of the boot.properties file in the domain root directory I cannot get weblogic.WLST to "utilize" the boot.properties. I thought there was a java option I should be able to set to "point" WLST to the boot.properties in the servers/instance/security directory?
we need to be able to check state of instances programmatically - we cannot use the admin console to do this. We prefer to use weblogic.Admin to do this because we can run the weblogic.Admin GETSTATE command against each individual instance (which I have not been able to do with weblogic.WLST - you have to run the weblogic.WLST state command only via the admin instance which if the admin instance is down you won't be able to tell the state of the other instances in the domain.
I'm hoping that if we can find a way to "tell" webogic.WLST where the boot.properties file is located.
Putting a copy of the boot.properties file in the domain root works fine - but I don't have to do this based on the documentation provided by Oracle.
Any help is appreciated.

Hi,
It is better to create the "userConfig" file abd pass it to the WLST connect() function...
How to create user Config file:
BEA_HOME :- /usr/bea10mp1
WL_HOME :- BEA_HOME/wlserver_10.0
STEP-1) Go to WL_HOME/server/bin and set the environment by executing "setWLSEnv.sh".
STEP-2) Then execute below command which generate "*userconfig*" and "*userkey*" files in the directory you had execute this command
java weblogic.Admin -adminurl t3://adminserverl:port -username <adminusername> -password <adminpassword> -userconfigfile userconfig -userkeyfile userkey -STOREUSERCONFIG
This command prompts for "Y" or "N", select "Y", then creates two files "userconfig" and "userkey"
STEP-3) Validate above keys are correct, execute below command
java weblogic.Admin -adminurl t3://adminserverl:port -userconfigfile userconfig -userkeyfile userkey -GETSTATE
Above command should display "RUNNING".
STEP-4) Now you can use the following link of connect() in your WLSt script...
connect(userConfigFile='/usr/someLocation/userconfig',userKeyFile='/usr/someLocation/userkey',url='t3://localhost:7001')
Why we need to create userConfig ...please see below...
http://download-llnw.oracle.com/docs/cd/E12840_01/wls/docs103/config_scripting/reference.html#wp1049091
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Feb 24, 2010 10:26 AM

WLST startserver issues in WLS 12.1

Trying to upgrade to WLS 12.1 (and WebSPhere 8.x)
We create a Domain through WLSt. Save it, start it and then deploy our app. All though WLST.
Part 1), creating the domain worked. While starting the server, it complained about "JAX-WS 2.2 API is required, but an older version was found in the JDK.". That was resolved when I added java.endorsed.dirs. Now, I have the domain created and then WLSt tries to start it using
startServer('AdminServer','MyDomain','t3://localhost:7001', 'weblogic', 'weblogic1',
'c:/release/v78/weblogic/config/MyDomain',
serverLog='c:/release/v78/weblogic/config/logs/wlstStartServer.log', timeout=360000,
systemProperties='weblogic.alternateTypesDirectory=c:/release/v78/weblogic/config/lib/jmx,com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0,java.endorsed.dirs=C:/bea/java6_29_64bit/jre/lib/endorsed;c:/bea/wls12/wlserver_12.1/endorsed;c:/release/v78/weblogic/config/vendor/jaxws22/jaxws-ri/lib',
jvmArgs='-Xms256m -Xmx1024m -XX:MaxPermSize=128m')
and the above always results in the following. Interestingly, if I simply used the MyDomain/startWebLogic.cmd, the server starts.
*+.WLST-WLS-1326381258658: <Jan 12, 2012 10:14:26 AM EST> <Error> <HTTP> <BEA-101064> <[WebAppModule(bea_wls_internal:bea_wls_internal.war)] Error parsing descriptor in Web appplication "C:\release\v78\Webworks\weblogic\config\MyDomain\serves\AdminServer\tmp\.internal\bea_wls_internal.war"+*
WLST-WLS-1326381258658: java.lang.StringIndexOutOfBoundsException: String indexout of range: 0*
WLST-WLS-1326381258658:         at java.lang.String.charAt(String.java:686)*
WLST-WLS-1326381258658:         at weblogic.servlet.internal.WebAppReader2.getText(WebAppReader2.java:190)*
WLST-WLS-1326381258658:         at weblogic.application.descriptor.BasicMunger2._onDTD(BasicMunger2.java:471)*
WLST-WLS-1326381258658:         at weblogic.application.descriptor.BasicMunger2.next(BasicMunger2.java:433)*

unable to start a domain through WLST startServer

SSO using Kerberos issue in WLS 8.1 SP4

In the documentation, it is stated to if the host is myhost.bea.com the use must be named myhost. Is this the onl way, or may I have a user name different from my host name? Any help is greatly appreciated.
Erik

I've configured wls8.1 SP4 in a Windows 2000 Domain. The name of the user hasn't to be the same as the host. If you change it, you have to change jass login file and keytab too.

Problems - WLS 10.0 web service client

I'm having a few issues with WLS 10.0 web service client.
          I generated a service control from the WSDL. The service is provided by a 3rd party (non-WLS) at another company. I generated the control within my web project and it's deployed as part of the web application. I experience the following problems with the service control API:
          1) The methods setKeyStore(), setTrustStore(), setClientCert() all seem to be ignored - the server always uses the values set in the server's environment definition. Note - the setEndpointAddress() seems to work.
          2) The client request does not set the 'Content-Type' HTTP header correctly (it's set to text/html) - I have no way to override this via the service control API (that I can see).
          3) I don't see any way/place to turn on more detailed tracing of what's going on internally with the service control invocation - is there a way to enable a detailed trace log of what is happening within the service control?
          Note: I'm able to call the web service via the test client (after importing the 3rd party server cert into my local cacerts).
          Thanks,
          [email protected]

Thank you for the reply..
But im still geting the same error. I have tried to include all the libraries in JWSDP pack but still.. I have managed to narrow down the place where the error occures.. It actually happens when I try to get the WebService Client Servant which is located in the package LSC:
---> LSC.LWServiceGenClient.LWS_Impl service = new LSC.LWServiceGenClient.LWS_Impl();
LSC.LWServiceGenClient.LWSServantInterface lagerServiceServant = LSC.LWServiceGenClient.LWSServantInterface_Stub)service.getLWSServantInterfacePort();
return lagerServiceServant;
Could something be wrong with the way I package the Jar? I'm using Sun One Studio and have tried including the 5 packages the application consists of; I have tried including just the files; moving the main class to <root>.. Still same problem..
Or could there be some different fundemental thingy I have forgotten ??
thanks
Aqoi

Error re-starting WLS server

Hi,
I was trying to configure the Apps adapter on WLS (10.3.4) following Metalink Note: 974949.1. I completed all the steps for WLS server, but when I try to re-start the server, i get the following error and the server fails to start:
####<May 13, 2011 3:46:46 PM IST> <Error> <Security> <HCILT014> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1305281806625> <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>
####<May 13, 2011 3:46:46 PM IST> <Critical> <WebLogicServer> <HCILT014> <AdminServer> <main> <<WLS Kernel>> <> <> <1305281806636> <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)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
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)
     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)
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)
     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)
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)
     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)
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)
     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)
Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: oracle.security.jps.JpsRuntimeException: JPS-00026: The value null is invalid for the application config..
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getIdStoreConfig(LdapIdentityStoreProvider.java:195)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.access$300(LdapIdentityStoreProvider.java:70)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:242)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:114)
     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:70)
     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)
>
####<May 13, 2011 3:46:46 PM IST> <Notice> <WebLogicServer> <HCILT014> <AdminServer> <main> <<WLS Kernel>> <> <> <1305281806749> <BEA-000365> <Server state changed to FAILED>
####<May 13, 2011 3:46:46 PM IST> <Error> <WebLogicServer> <HCILT014> <AdminServer> <main> <<WLS Kernel>> <> <> <1305281806750> <BEA-000383> <A critical service failed. The server will shut itself down>
####<May 13, 2011 3:46:46 PM IST> <Notice> <WebLogicServer> <HCILT014> <AdminServer> <main> <<WLS Kernel>> <> <> <1305281806753> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<May 13, 2011 3:46:46 PM IST> <Info> <WebLogicServer> <HCILT014> <AdminServer> <main> <<WLS Kernel>> <> <> <1305281806764> <BEA-000236> <Stopping execute threads.>
How do I fix the issue?
WLS Server: 10.3.4
SOA Suite: 11.1.1.4
Thanks,
Ashish

I was able to start the server. Following the Metalink note, I had tried to configure JAAS on weblogic server (created a new realm, role-mapper etc).
When I commented the below code in C:\Oracle\Middleware\user_projects\domains\base_domain1\config\config.xml, the server started.
<realm>
<sec:authentication-provider xmlns:ext="http://xmlns.oracle.com/weblogic/security/extension" xsi:type="ext:ext-authenticatorType">
<sec:name>extAuth</sec:name>
<sec:control-flag>OPTIONAL</sec:control-flag>
<ext:connection-reference>jdbc/ebiz</ext:connection-reference>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType">
<sec:name>XACMLRoleMapper</sec:name>
</sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType">
<sec:name>XACMLAuthorizer</sec:name>
</sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType">
<sec:name>DefaultAdjudicator</sec:name>
</sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType">
<sec:name>DefaultCredentialMapper</sec:name>
</sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType">
<sec:name>WebLogicCertPathProvider</sec:name>
</sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:deploy-credential-mapping-ignored>false</sec:deploy-credential-mapping-ignored>
<sec:name>ebsRealm</sec:name>
</realm>
<default-realm>ebsRealm</default-realm>
Not sure what could have gone wrong.

Using updated tools with WLS 8.1 SP3

I'm attempting to take advantage of some ant 1.6 features. However, it appears that the ant XML parsers are getting in the way of the embedded WLS xml parsers:
[servicegen] java.lang.ClassCastException
[servicegen] at weblogic.apache.xerces.parsers.SAXParser.<init>(SAXParser.java:140)
[servicegen] at weblogic.apache.xerces.parsers.SAXParser.<init>(SAXParser.java:125)
[servicegen] at weblogic.apache.xerces.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:102)
[servicegen] at weblogic.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:112)
[servicegen] at weblogic.apache.xerces.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:140)
[servicegen] at weblogic.xml.jaxp.WebLogicSAXParserFactory.setFeature(WebLogicSAXParserFactory.java:56)
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot invoke boolean constructor of processor ] - with nested exception:
[servicegen] [java.lang.reflect.InvocationTargetException - with target exception:
[servicegen] [weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[servicegen] [java.lang.ClassCastException]]]
Based on some research this appears to be an issue with WLS getting a parser that it cannot handle. Given that the version of ant included with 8.1sp3 is pretty old, is there a way to use newer versions? I'm giving up for now on macrodef's but would, as a general statement, like to keep up with new tools as they become available. I'd like to not be dependent on turning a battleship to incorporate 15 months of development work (the time between now and the release of ant 1.5.3 as included with 8.1sp3).
Thanks for any information.

Had some problems like this before. Even thought I cannot offer specific advice as to how to fix this. If you do this, it could help.
Encountered a problem in eclipse while using WLS servicegen ANT task and, of course, the optional FTP task. I am using Eclipse Version: 3.0.0 Build id: 200406192000. With this comes ANT 1.6.1 standard. In order to get servicegen ANT task working I had to include the weblogic.jar in the ANT Classpath. Ofcourse this had another side effect, the FTP task that used to work earlier quit working. I still havent figured out the root cause of the problem but inorder to get around I did the following. To fix this, I added a new Task called FTP, I picked the c:\....\lib\ant-commons-net.jar in the location. The name I retained it as ftp. In the left page, I nagivated down to the lead of the tree [root]/->org->apache->...->net and in the right pane, I chose FTP. After this step when I ran I ran into an odd error Buildfile: C:\Work\JSSE-EJB.xml BUILD FAILED: java.lang.NoClassDefFoundError: com/oroinc/net/ftp/FTP Total time: 78 milliseconds I was under the impression that this is a legacy component and that the new version of the net component has org.apache....FTP structure. I am really not sure where, but to fix the issue, I had to get the NetComponents.jar from http://www.savarese.org/downloads/NetComponents/ and included it in the classpath. After this step, presto, servicegen task works fine with FTP task. However, I cannot imagine doing this for all the optional tasks. But for now there is a winding work around.

Resource Allocation Issue in Weblogic messaging bridges

Hi,
We are using
Weblogic version à WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic Temporary Patch for CR250915 04/18/2006 22:21:33
Java JDK version à 1.4.2_11
Oracle version à 9.2.08
Solaris version à Solaris 5.8
The weblogic application is deployed on Unix Solaris.
We have configured 8 message bridges within weblogic between the 8 Topics in weblogic (source JMS destination) and 8 topics in the External EMS server (Target JMS destination) .
The properties set for the message bridges are
1] AsyncEnabled ="true"
2] DurabilityEnabled ="true"
3] QualityOfService="Exactly-once"TransactionTimeout="10"
4] TransactionTimeout="10"
The source and target JMS destinations are bridge using the resource adapter of jms-xa-adp (connector module)
The properties for the Source JMS Destination are
1] ConnectionFactory = weblogic.jms.client.JMSXAConnectionFactory
The properties for the Target JMS Destination are
1] InitialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory
2] ConnectionFactory = XATopicConnectionFactory
The EMS client version library is EMS version client library à 4.2.0
The message Bridge Thread Pool Size is à 12
When the weblogic is started, all the bridges comes up properly and are forwarding message to the target, however after some time (1 to 2 days) we observe some that some of the bridges are going down and we get see following error in the weblogic logs
####<May 26, 2010 12:00:56 AM GMT> <Warning> <Connector> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
####<May 26, 2010 12:00:56 AM GMT> <Info> <MessagingBridge> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200042> <Bridge RefDataCompanyBridge failed to connect to the source destination and will try again in 60 seconds. (javax.resource.ResourceException: Failed to start the connection)>
Can you please help us resolve the above issue?
Thanks,
Mohanraj

There seems to be couple of known issues with WLS 8.1 and Tibco EMS.. Check with support whether your issue is related to any of the below:
Message bridge will stop responding and WLS has to be restarted to overcome this.
There is a known bug on WLS 8.1. Bug 8062571 is for the issue.
Should the connection be interrupted by a problem on the Tibco side, the messaging bridge never tries to reconnect. the problem can be that Tibco EMS is restarted for some reason or that the maximum number of messages that Tibco EMS can handle is reached.
Unpublished bug8066979 is available for WebLogic Server 8.1 SP6 and later
Unpublished bug8172940 is available for WebLogic Server 9.2 MP2 and later
Note you can get more info about bridge problems by following the below steps:
To debug the bridge you can enable debugging for the messaging bridge using either of the followings methods:
* Add the following lines to your WebLogic start script (before the weblogic.Server line):
-Dweblogic.debug.DebugMessagingBridgeStartup=true
-Dweblogic.debug.DebugMessagingBridgeRuntime=true
* Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:
DebugMessagingBridgeStartup="true"
DebugMessagingBridgeRuntime="true"
Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add “DumpToConsole” to the statements show above. For example:
-Dweblogic.debug.DebugMessagingBridgeStartupDumpToConsole=true
Edited by: atheek1 on May 30, 2010 5:19 AM

Weird issue with 10.0.1.0 on Linux - 5 mins delay in server start-up!!

Hi ...
I am having some weird (and unique??) issue with WLS 10.0.1.0 on RHEL servers.
WLS installation on our DEV env works perfectly fine and the server starts up in 15-20 secs. for each of the two domains created on it.
But the QA server is another story all together ! ... It has the same OS and version, WSL installation and version, hardware configs, processes running at the time of start-up etc. But the problem is that when I try to start the server on the only domain on that server, it always gets delayed by 5-6 mins in between the startup at this point -
+<Feb 17, 2009 *7:04:50 *PM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 >+
+<Feb 17, 2009 *7:10:56 *PM UTC> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /opt/bea/license.bea>+
(Notice the 6 mins delay in the timestamps)
There are no logs getting generated within this time and it seems like the WLS 10.0.1.0 just spaces out
After the delay it starts up pretty fast .. within 10-15 secs!!
Anybody here seen such behavior with WLS
thanks,
--Shailesh Welankar

I recommend taking some thread dumps during this delay and contacting support to get some advice.
You can take the thread dumps by kill -3, JRockit Mission Control, etc.

No Lock & Edit button in WLS 10 Console

I don't have the Lock & Edit button in the WLS 10 Console. I know that this could be turned on and off in previous versions of WebLogic in the config.xml file, but I didn't find this anywhere in the documentation anymore.
Can anybody tell me how to make the Lock & Edit buton visible again in WebLogic 10.3a?
Thanx
Peter

Here is my config.xml ( I guess I cannot just attach it):
<?xml version='1.0' encoding='UTF-8'?>
<domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/920/domain.xsd" xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
     <name>IOP5</name>
     <domain-version>10.3.0.0</domain-version>
     <security-configuration>
          <name>IOP5</name>
          <realm>
          
               <sec:auditor xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-auditorType">
                    <sec:name>CSRealmCSAuditor</sec:name>
                    <prov:audit-logger-name>@audit.WLSAuditChannel</prov:audit-logger-name>
                    <prov:use-wls-log-handler>false</prov:use-wls-log-handler>
                    <prov:providers-logs-enabled>false</prov:providers-logs-enabled>
               </sec:auditor>
               <sec:authentication-provider xsi:type="wls:saml-identity-asserter-v2Type">
                    <sec:name>SAMLIdentityAsserter</sec:name>
                    <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
               </sec:authentication-provider>
               <sec:authentication-provider xsi:type="prov:cssaml-authenticatorType" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xmlns:dom="http://www.bea.com/ns/WebLogic/920/domain" xmlns:xsi1="xsi">
                    <sec:name>CS SAML Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
               </sec:authentication-provider>


               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-identity-asserterType">
                    <sec:name>CS Identity Asserter</sec:name>
                    <prov:credentials-validators>X.509=com.csg.cs.security.wls.authentication.pki.ext.CSPKICredentialValidator</prov:credentials-validators>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-principal-authenticatorType">
                    <sec:name>CS Principal Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                    <prov:credential-validator>com.csg.cs.security.wls.authentication.pki.ext.CSPrincipalCredentialValidator</prov:credential-validator>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:csb1-authenticatorType">
                    <sec:name>CS B1 Authenticator</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                    
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authenticatorType">
                    <sec:name>CS Authentication Provider</sec:name>
                    <sec:control-flag>SUFFICIENT</sec:control-flag>
                    <prov:log-in-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:log-in-module-class-name>
                    <prov:assertion-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:assertion-module-class-name>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-internal-identity-asserterType">
                    <sec:name>CS Internal Identity Asserter</sec:name>
               </sec:authentication-provider>
               <sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-data-layer-providerType">
                    <sec:name>CS Data Layer Security Provider</sec:name>
                    <sec:control-flag>OPTIONAL</sec:control-flag>
                                   <prov:key-alias>SYSTEM</prov:key-alias>
                                   <prov:key-store-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-store-pass-phrase-encrypted>
                                   <prov:key-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-pass-phrase-encrypted>
               </sec:authentication-provider>
               <sec:role-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-role-mapperType">
                    <sec:name>CS Role Mapper</sec:name>
                    <sec:role-deployment-enabled>true</sec:role-deployment-enabled>
                    <prov:is-debug>false</prov:is-debug>
                    <prov:application-role-mapper-class-name></prov:application-role-mapper-class-name>
               </sec:role-mapper>
               <sec:authorizer xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authorizerType">
                    <sec:name>CS Authorization Provider</sec:name>
               </sec:authorizer>
               <sec:credential-mapper xsi:type="sam:saml2-credential-mapperType" xmlns:sam="http://www.bea.com/ns/weblogic/90/security/saml2">
                    <sec:name>SAML2CredentialMapper</sec:name>
                    <sam:issuer-uri>http://www.credit-suisse.com</sam:issuer-uri>
                    <sam:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</sam:name-qualifier>
                    <sam:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAML2NameMapperImpl</sam:name-mapper-class-name>
               </sec:credential-mapper>
               <sec:credential-mapper xsi:type="wls:saml-credential-mapper-v2Type" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers">
                    <sec:name>SAMLCredentialMapper</sec:name>
                    <wls:issuer-uri>http://www.credit-suisse.com</wls:issuer-uri>
                    <wls:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</wls:name-qualifier>
                    <wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
               </sec:credential-mapper>
               <sec:credential-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-credential-mapperType">
                    <sec:name>CSCredentialMapper</sec:name>
               </sec:credential-mapper>
               <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
               <sec:cert-path-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cert-path-providerType">
                    <sec:name>CS Certificate Path Provider</sec:name>
                    <prov:cert-path-validator-class-name>com.csg.cs.security.wls.authentication.cert.ext.CSPKICertPathValidator</prov:cert-path-validator-class-name>
               </sec:cert-path-provider>
               <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
               <sec:deploy-role-ignored>true</sec:deploy-role-ignored>
               <sec:deploy-policy-ignored>true</sec:deploy-policy-ignored>
               <sec:deploy-credential-mapping-ignored>false</sec:deploy-credential-mapping-ignored>
               <sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
               <sec:security-dd-model>Advanced</sec:security-dd-model>
               <sec:name>CSRealm</sec:name>
               <sec:delegate-m-bean-authorization>true</sec:delegate-m-bean-authorization>
          </realm>
          <default-realm>CSRealm</default-realm>
          <anonymous-admin-lookup-enabled>true</anonymous-admin-lookup-enabled>
          <credential-encrypted>{3DES}Zk0PFQd/y2JbBwcVCkoTVA==</credential-encrypted>
          <connection-filter>com.csg.cs.security.wls.net.ConnectionFilterImpl</connection-filter>
          <connection-logger-enabled>true</connection-logger-enabled>
     </security-configuration>
     <server>
          <name>IOPWLS5</name>
          <reverse-dns-allowed>true</reverse-dns-allowed>
          <ssl>
               <use-java>true</use-java>
               <enabled>true</enabled>
               
               <ciphersuite>TLS_RSA_WITH_RC4_128_SHA</ciphersuite>
               <ciphersuite>TLS_RSA_WITH_3DES_EDE_CBC_SHA</ciphersuite>
               <cert-authenticator></cert-authenticator>
               <hostname-verifier>com.csg.cs.security.wls.net.SSL.ext.CSPKIHostNameVerifier</hostname-verifier>
               <hostname-verification-ignored>false</hostname-verification-ignored>
               <export-key-lifespan>500</export-key-lifespan>
               <client-certificate-enforced>false</client-certificate-enforced>
               <listen-port>7002</listen-port>
               <two-way-ssl-enabled>true</two-way-ssl-enabled>
               <server-private-key-alias>tipd.csintra.net</server-private-key-alias>
               <server-private-key-pass-phrase-encrypted>{3DES}mQrgg0qTDHAhuU+2FACgZQ==</server-private-key-pass-phrase-encrypted>
               <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
               <inbound-certificate-validation>BuiltinSSLValidationAndCertPathValidators</inbound-certificate-validation>
               <outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
          </ssl>
          <log>
               <rotate-log-on-startup>true</rotate-log-on-startup>
               <logger-severity>Notice</logger-severity>
               <stdout-severity>Notice</stdout-severity>
               <log-file-filter xsi:nil="true" />
               <stdout-filter xsi:nil="true" />
               <domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
               <domain-log-broadcast-filter xsi:nil="true" />
               <memory-buffer-filter xsi:nil="true" />
               <redirect-stdout-to-server-log-enabled>true</redirect-stdout-to-server-log-enabled>
               <redirect-stderr-to-server-log-enabled>true</redirect-stderr-to-server-log-enabled>
          </log>
          <machine xsi:nil="true"></machine>
          <listen-port>7001</listen-port>
          <listen-port-enabled>true</listen-port-enabled>
          <cluster xsi:nil="true"></cluster>
          <web-server>


               <send-server-header-enabled>false</send-server-header-enabled>
          </web-server>
          <iiop-enabled>false</iiop-enabled>
          <listen-address>127.0.0.1</listen-address>
          <staging-directory-name>./stage</staging-directory-name>
          <classpath-servlet-disabled>true</classpath-servlet-disabled>
          <key-stores>CustomIdentityAndCommandLineTrust</key-stores>
          <custom-identity-key-store-file-name>./keystores/identity.properties</custom-identity-key-store-file-name>
          <custom-identity-key-store-type>CS_PKI</custom-identity-key-store-type>
          <custom-identity-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-identity-key-store-pass-phrase-encrypted>
          <custom-trust-key-store-file-name>./keystores/trustedca.properties</custom-trust-key-store-file-name>
          <custom-trust-key-store-type>CS_PKI</custom-trust-key-store-type>
          <custom-trust-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-trust-key-store-pass-phrase-encrypted>
     </server>
     <embedded-ldap>
          <name>IOP5</name>
          <credential-encrypted>{3DES}nQpvTCkYlf4h4+8bAEI7JH8pg2Zo4uqNrVEu9bfYSr8=</credential-encrypted>
     </embedded-ldap>
     <administration-port-enabled>true</administration-port-enabled>
     <administration-port>9999</administration-port>
     <configuration-version>10.3.0.0</configuration-version>
     <app-deployment>
          <name>IOPA_root</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/root.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPD_prsysmgmt</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPD/prsysmgmt.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPC_prhelp</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPC/prhelp.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPA_prpc_j2ee14</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/prpc_j2ee14.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>
     <app-deployment>
          <name>IOPB_prdbutil</name>
          <target>IOPWLS5</target>
          <source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPB/prdbutil.ear</source-path>

          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </app-deployment>



     <library>
          <name>CSWSPolicySAML11#[email protected]</name>
          <target>IOPWLS5</target>
          <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\WSS11SAML1WSPolicy.jar</source-path>
          <deployment-order>1</deployment-order>
          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </library>
     <library>
          <name>CSWSPolicySAML20#[email protected]</name>
          <target>IOPWLS5</target>
          <source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\SAML2WSPolicy.jar</source-path>
          <deployment-order>1</deployment-order>
          <security-dd-model>Advanced</security-dd-model>
          <staging-mode>nostage</staging-mode>
     </library>






     
     <jms-server>
          <name>PRJMS_Server</name>
          <target>IOPWLS5</target>
     </jms-server>
     <jmx>
          <management-ejb-enabled>false</management-ejb-enabled>
     </jmx>
     <shutdown-class>
          <name>CSServerLifeCycleShutdown</name>
          <target>IOPWLS5</target>
          <class-name>com.csg.cs.security.wls.CSServerLifeCycleShutdown</class-name>
     </shutdown-class>
     <startup-class>
          <name>CSServerLifeCycle</name>
          <target>IOPWLS5</target>
          <class-name>com.csg.cs.security.wls.CSServerLifeCycle</class-name>
          <failure-is-fatal>true</failure-is-fatal>
          <load-before-app-deployments>true</load-before-app-deployments>
          <load-before-app-activation>false</load-before-app-activation>
     </startup-class>

     <jms-system-resource>
          <name>PRJMS_Module</name>
          <target>IOPWLS5</target>
          <sub-deployment>
               <name>PRJMS_Subdeployment</name>
               <target>PRJMS_Server</target>
          </sub-deployment>
          <sub-deployment>
               <name>PRJMS_Subdeployment_Topic</name>
               <target>PRJMS_Server</target>
          </sub-deployment>
          <descriptor-file-name>jms/prjms_module-jms.xml</descriptor-file-name>
     </jms-system-resource>
     <admin-server-name>IOPWLS5</admin-server-name>
     <jdbc-system-resource>
          <name>pega-rules</name>
          <target>IOPWLS5</target>
          <descriptor-file-name>jdbc/pega-rules-jdbc.xml</descriptor-file-name>
     </jdbc-system-resource>

     

     <webservice-security>
          <name>default_wss</name>
          <webservice-token-handler>
               <name>CSTokenHandler</name>
               <class-name>com.csg.cs.security.wls.authentication.wsee.TokenHandler</class-name>
               <token-type>ut</token-type>
               <handling-order>0</handling-order>
          </webservice-token-handler>
     </webservice-security>
</domain>
Regards
Peter

SAAJ issue on WLS

Similar Messages

Maybe you are looking for