Configuring JMS in Production mode

Hi all
I need to configure JMS queue and i tried this flow, correct me if i am wrong
1.persistent store
2.JMS server
3.JMS module
3.1.Connection factory with default targetting
3.2 Queue with soa_server1 as target.
I am getting a error while creating persistent store when activating changes in admin console.
"FujitsuJMSFileStore" is the filestore name
Server Log is
<Warning> <Management> <BEA-141197> <The deployment of FujitsuJMSFileStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:182)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist
at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
at weblogic.store.io.file.StoreDir.checkOK(StoreDir.java:202)
at weblogic.store.io.file.Heap.<init>(Heap.java:185)
at weblogic.store.io.file.Heap.<init>(Heap.java:163)
Truncated. see log file for complete stacktrace
>
<Apr 30, 2012 2:48:04 AM PDT> <Critical> <Management> <BEA-141190> <The commit phase of the configuration update failed with an exception:
weblogic.descriptor.DescriptorUpdateFailedException: one or more registered update listeners reported activation problems.
The following failures occurred:
-- The following failures occurred:
weblogic.management.DeploymentException:
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:182)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist
at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
at weblogic.store.io.file.StoreDir.checkOK(StoreDir.java:202)
at weblogic.store.io.file.Heap.<init>(Heap.java:185)
at weblogic.store.io.file.Heap.<init>(Heap.java:163)
at weblogic.store.io.file.FileStoreIO.<init>(FileStoreIO.java:79)
at weblogic.store.xa.PersistentStoreManagerXA.makeXAStore(PersistentStoreManagerXA.java:51)
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:178)
... 21 more
weblogic.descriptor.BeanUpdateFailedException: The following failures occurred:
weblogic.management.DeploymentException:
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:182)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist
at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
at weblogic.store.io.file.StoreDir.checkOK(StoreDir.java:202)
at weblogic.store.io.file.Heap.<init>(Heap.java:185)
at weblogic.store.io.file.Heap.<init>(Heap.java:163)
at weblogic.store.io.file.FileStoreIO.<init>(FileStoreIO.java:79)
at weblogic.store.xa.PersistentStoreManagerXA.makeXAStore(PersistentStoreManagerXA.java:51)
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:178)
... 21 more
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:189)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:257)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
Truncated. see log file for complete stacktrace
I tried restarting the admin and SOA server more than twice still i am getting this error .
Thanks in advance
Anand.U

Hi Anand,
here is your error,
*Caused by: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist*
/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore does not physically exists on your WLS host as a directory or file system to write to
Or it is not mounted
Or you don't have the permissions to write in it.
For detailed explanation about how to configure JMS queue,can be obtained from the below link
http://middlewaremagic.com/weblogic/?p=1987
Regards
Fabian

Similar Messages

Start Weblogic 10.3.5 in production mode

I am doing a Weblogic upgrade from 9.1 to 10.3.5.
I am also simultaneously doing a Java upgrade to 1.6.0_27.
All changes are done and the project is in in System test mode.
I have configured my Sysytem test environment in development mode and used JDk installed on my computer.
To move the changes to the UAT server, I want to start weblogic in production mode.
can anyone help me as to how will this be different,I am planning thing for UAT and production right now.
Can I run my System test server in production mode .
Is it that with production mode ,we have to use jrockit and not Sun Jdk?
Please help.
Thanks,

Hi
When you started the Weblogic Server, in the starup window (or nohup output file) search for the word named like "Development". When I started my AdminServer and in the output from startup window, I could see a line like this: and in the end it says like AdminServer started in Development mode. On your side search for the word like "Production" or just "WLS Start Mode".
WLS Start Mode=Development
There should be a way to find out from Weblogic Admin Console, but I am not aware of this.
Coming to redirecting the log file(s). do you want to redirect the startup log file(s) like when you start weblogic, you want all the outputs to go to someother file. Or is it the full log files from each server which are under like domain/servers/AdminServer/logs folder. I guess from weblogic console you should be able to control this.
Coming to redirecting startup log files on Linux, under the domain root folder I created a simple file like admin_start.sh with below contents. And I run this admin_start.sh instead of startWeblogic.sh command. This takes care of starting weblogic and all output goes to specific file I mentioned. Also I can kill this window and still weblogic will be starting:
DOMAIN_HOME="/home/ravijegga/Oracle/Middleware115/user_projects/domains/myDomain1"
LOG_FILE="/home/ravijegga/Oracle/Middleware115/user_projects/domains/myDomain1/logs/admin.log"
nohup ${DOMAIN_HOME}/bin/startWebLogic.sh > ${LOG_FILE} &
The point is if you use > you can redirect to any log file. Google around and you should be able to find more examples for Windows OS also.
Thanks
Ravi Jegga

Usage of default keyStores(.jks) in WLS production mode

HI All,
I need confirmation on usage of default keystore(.jks) on web logic servers 10.3.5 running in PRODUCTION Mode ?
I have configured Demo-trust.jks and Demo-identity.jks files in web logic server which is running on production mode , but the below link says we should not use the demoidentity.jks and demotrust.jks file in Production and default key-stores for only testing.
In general, production mode requires you to configure additional security features.
FYi ...http://oracle-solutions.com/en/configuration-ssl-weblogic-server/
FYI, Some of key web logic server log entries :
- The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.
- <BEA-000330> <Started WebLogic Managed Server "bi_server1" for domain "bifoundation_domain" running in Production Mode>.
- Warning : domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\oracle.applcore.model\vy4gk6/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future   versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
Basically we are trying to implement the SSO between OBIEE11g and j2e application in WLS 10.3.5   , I have completed the SAML2 configuration on two different managed servers ,but SSO not working and also not able to find ERROR messages on server logs
I would like to know , If we chose/use default keystores in WLS production mode , is there impact on SSO functionality (SAML2) ?
Thanks in Advance

Hi ,
Thanks for valuable input and after configuring I am able to see the SAML2.0 logs
In Web logic custom authentication provider configured for performing authentication on j2ee application .    SS0-Saml2.0 configured in single web-logic server11g ,in which two different managed servers .(One managed server for application and another managed server for OBIEE).
We are able to login successfully on application side using the custom database authenticator (User: Tony) and then if we try to access the OBIEE urls(example: http://ctodomain.test.com:8704/saml2/analytics/saw.dll?) ,its redirecting to OBIEE URL as   http://ctodomain.test.com:8704/saml2/sp/acs/artifact?SAMLart=AAQAAP4DqhE1B5fw5nvpzoSbqW9KLgCPhgkl21qQKIG3naZsi9f75Uk8HdQ%3D   and WLS log says “Authentication Failed: User ‘Tony’ denied
Looks like SAML token generating properly on IDP(app) and not able to authenticate on service provider (OBIEE)
In order to achieve the SSO using SAML2.0 , do we need to configure any steps at OBIEE side to bring the users in console ? , b’coz below log says application user not able to login authenticate at OBIE E side .
OBIEE wls log:
Apr 13, 2015 11:18:39 PM IST> <Debug> <SecuritySAML2Service> <BLR00AFE> <bi_server1> <[ACTIVE] Execute-thread: '0' for queue: 'web-logic.kernel.Default (self-tuning)'> <<WLS Kernel>> <
<3c7a43ee732d37f3:4702fadb:14cb333962b:-8000-000000000000238c> <1428947319400> <BEA-000000> <exception info
javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User Download javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User Download denied
                at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
                at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
                at sun.reflect.GeneratedMethodAccessor354.invoke(Unknown Source)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                at java.lang.reflect.Method.invoke(Method.java:606)
Appreciate if any inputs on above issue
Thanks

OBIEE 11g installation Issue - Demo Cert in production mode

Hello All, I installed OBIEE 11g along with Weblogic 10.3.5 on Linux 64 bit server. I searched entire <<MW_HOME>> folders and changed PRODUCTION_MODE to false in all possible .sh files. However, the error doesn't go away.
Is there any other location, I need to check for this flag?
Also, when I login to WebLogic console, Domains --> Configuration --> General .. I still see Production mode = true.
Thanks in advance for your help and assistance.
Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Thu Mar 21 12:12:27 PST 2002,
To: Tue Mar 22 13:12:27 PDT 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign

Hi Vagic
Did you get any clue on this problem? I'm facing the same warning and I'm not sure if that's releant or not.
Thank you

Production mode startup failure for 8.1SP2

I'm running BEA WL 8.1 on Windows 2000 and have created a new server configuration
in production mode with JRocket using the Configuration Wizard through Express
Setup. I am unable to successfully start the server manually or through the Workshop
interface. Below is the exception stack trace. Any suggestions would be most appreciated.
<> <000000> <Error in startup class com.bea.wli.init.WLIDBCreate Method: init:
com.bea.wli.init.WLIDBCreateException: At least one WLI data base object (TABLE
WLI_USER) was missing
     at com.bea.wli.init.WLIDBCreate$WLIDataSource.checkDBObjects(WLIDBCreate.java:875)
     at com.bea.wli.init.WLIDBCreate.init(WLIDBCreate.java:994)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:324)
     at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:189)
     at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.java:229)
     at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.java:160)
     at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.java:36)
     at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:121)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassService.java:116)
     at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:88)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
     at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
     at weblogic.Server.main(Server.java:32)

Thanks, I fixed the problem following the steps you outlined.
All that was needed was to create a database named Workshop, and then execute the scripts as explained.
For the benefit of others here is what I followed before going by your suggestion:
1. Go to: weblogic81\common\eval\pointbase\tools
2. Start pointbase by executing: startPointBase.cmd
(edit this file if it should run on any specific port that you require e.g 9093)
3. Under the same directory, execute: startPointBaseConsole.cmd so that the pointbase console comes up.
4.Click on the radio button: Create new database
5. In the dialog box, specify URL as:
jdbc:pointbase:server://localhost:9093/workshop
(I used port 9093 on localhost)
6. specify username and password
7. Click OK.
Now follow the steps on the links below:
http://forums.bea.com/bea/thread.jspa?messageID=202437477&tstart=0
or
http://www.webservertalk.com/message148326.html
Also, it does not matter whether you start the server in prod. mode or dev mode as this DB lookup is before you specify dev mode or prod. mode startup while creating the domain (when you test connection through config. wizard while creating the domain). I created the domain in custom mode and not in express mode to have greater visibility of what I am configuring (On Windows env.).
Rommel Sharma.

Configuring JMS Bridges between COM and SOM

Hi,
We started working on OSM 7.0.2 and I have a question about the configuration of JMS Bridges between COM and SOM.
When COM and SOM Cartridges are installed in the same OSM instance on non-cluster env., it is mandatory to configure JMS Bridges between COM and SOM?
If it is case, could you please detail the procedure to follow?
In the document called "Application Integration Architecture Order-to-Activate Cartridge Guide Release 7.0.2 E18005-01" it is not obvious to understand. If you have a look in the table 2-1 page 2-15, I don't see all the mandatory field values to create a new destination bridges (for instance, what is the value of destination JNDI name?). Does anyone configure this part in the setting up OSM to the Order-to-Activate Solution?
Best regards.

The COM-SOM bridge is only required when COM and SOM are deployed on separate osm server instances and AIA Emulators are deployed (on both) for development/demo/quick testing purposes.
In QA/SIT/PRODUCTION environments, OSM should be integrated via AIA, this means that all participant applications ( CRM , OSM-COM, OMS-SOM, BRM ) should be using queue bridges (or SAF in 7.0.3)

SOA 11g in Production Mode

Hi Everybody
I am going to install SOA Suit 11g for a production mode, any helpfull tutorial or steps?? I googled the net, I didn't find , all are talking about development mode..
Any help please??

"High Abvailability" and "Clusturing" are general basic requirement for any production installation but it does NOT mean that any system installed in production MUST have "High Abvailability" and "Clusturing" configured.
Regards,
Anuj

Configure JMS in Jetty

Hi,
I have an application which is internally calling Jetty jar and starting the server.
My requirement is to configure JMS in it.
Could you please tell me what approach i should follow?
can it be done through API? any other solution?
Thanks in advance for your response.
Arun.

JoachimSauer wrote:
I'm pretty sure he meant "Jetty doesn't give you a JMS implementation", and as far as I can tell he's rightYeh I did. Sorry, OP, I was in a hurry!
Jetty doesn't come with a JMS implementation, it's "just" a web server with servlet engine, not a fully-fledged application server.Correct
You'll need to integrate a separate JMS product. Google for "JMS jetty" and you'll find plenty of help.I'd recommend Apache ActiveMQ. It gives you a product called Camel, which helps you integrate all manner of things neatly, including Jetty

Cannot change to Production mode using WLST

Is it possible or may be it is bug?
Even <pre>configToScript()</pre> command throws an exception
when i'm trying to convert a Domain with <i>Production mode</i> enabled (created with Configuration wizard)!

Since DomainMBean.ProductionModeEnabled attribute is non-dynamic, you may want to restart your server immediately after you change that attribute using WLST.
If you still get exeception for configToScript() command after server restart, please attach the exception stack trace.
Jason Zheng
BEA Systems

SP2 Weblogic Integration Template Production Mode Failure

I was surprised that in SP2, this simple failure is still not fixed:
Launch configuration wizard.
Choose Integration Template
Choose Express Configuration
Choose Production Mode
Launch new domain
You'll see the startup fails because the WLI tables are missing. This
was broken in every release so far, and is pretty sad since it's one of
the most basic things you can do with WL.

Figured it out. When you try to create a new domain, it must be created in development mode (even if you want to run it in production mode). Start it at least once in development mode before trying to start it in production mode. To change whether the server starts in development or production - edit the setDomainEnv.sh file (in the same directory as config.xml). Towards the bottom of the file, there is an if condition that looks like this:
if ("" = "true"){
change it to
if ("true" = "true) {
then your server will start in production mode.

Unable to complete: configuration Assistants in GUI mode

Dear All,
I am tring the install RAC 10g clusterware software on HPUX 11i v1 machine
I excuted the root.sh file on both nodes and then while trying to excute the VIPCA script its getting an error
and also i am not able to complete 1st step in Configuration Assistants in GUI mode
Please find the below error....Kindly help on this issue
# /opt/oracle/product/CRS/bin/vipca
PRKH-1010 : Unable to communicate with CRS services.
[Communications Error(Native: prsr_initCLSS:[3])]
PRKH-1010 : Unable to communicate with CRS services.
[Communications Error(Native: prsr_initCLSS:[3])]
PRKH-1010 : Unable to communicate with CRS services.
[Communications Error(Native: prsr_initCLSS:[3])]
# ./crsctl check crs
Failure 1 contacting CSS daemon
Cannot communicate with CRS
Cannot communicate with EVM
Regards,
Veera

Hi!
I suppose your failure it's easy: your CRS server is stopped. Start it and all will be fine.
Chao!

How to Configure JMS MQ In WeLogic?

Hello. I am new to this forum. Can anybody gives instructions on how to create or configure JMS MQ in WebLogic ?
Thanks.

I recommending starting by reading through the [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E12839_01/web.1111/e13727/interop.htm#JMSPG553 ] FAQ, in order to assess the various options.
You may also want to look at "[ Integrating WebSphere MQ 6 with BEA Weblogic Server 10 using Weblogic Server Foreign (JMS) Server feature | http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html ]".
If you need exactly-once (transactions), and the MQ server is on a different machine than WebLogic, then you will need to use the MQ Extended Transactional client from IBM (http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf). I think IBM still requires a license for this client.
Finally, you might find some useful information in the following white-paper: "[ Integrating an Oracle Service Bus Cluster with an IBM WebSphere MQ Cluster in a Service-Oriented Architecture | http://www.oracle.com/technology/products/integration/service-bus/docs/osb-websphere-whitepaper.pdf ]".
Tom

How to recompile a single JSP in WLS10.3 running in production mode

In OAS there was a parameter...something like ?precompile=true which would force recompile of a JSP. Does anyone know any equivalent setting in WLS? We are running in production mode, but there are cases where we need to make a JSP change to fix an issue. And I dont want to have to run the server in development mode.
Thanks

Just an update...It cannot be done. Even if you compile the class manually and put it in place of the old class, it will not take effect. The WLS must cache the classes in production mode, which makes perfect sense. Just a pain.

Weblogic starting in production mode LINUX x86

I am having a problem when creating a new weblogic 10.3.3 domain. I created this domain in development mode yet when i try and start the domain the admin server always starts in Production mode?
Does anyone know why this is happening as i've check the weblogic console and it shows that the domain is set to development. Below is the message recieved on start up of the admin server:
<Warning> <Management> <BEA-141274> <Production mode has specified at the command line via the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in config.xml. However, the console and WLST show the attribute values and defaults that correspond to the development mode specified in config.xml.>
Thanks for your help in advance.

I have the same problem during the start of Oracle Identity Manager 11G...Admin Server and Managed Server on different machines...
####<Dec 2, 2010 5:25:17 PM MSK> <Error> <Security> <asoim.sgp.gazprom.ru> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1291299917129> <BEA-090892> <The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.>
####<Dec 2, 2010 5:25:17 PM MSK> <Critical> <WebLogicServer> <asoim.sgp.gazprom.ru> <oim_server1> <main> <<WLS Kernel>> <1291299917132> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1394)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.security.jps.JpsRuntimeException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:273)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
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:1312)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.security.jps.JpsException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:705)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
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:1312)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.security.jps.JpsException: JPS-01514: The default context is missing in jps-config.xml.
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:665)
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
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:1312)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: 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:218)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:140)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.<init>(SspCredentialStore.java:127)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:115)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider.getInstance(SspCredentialStoreProvider.java:53)
and help???

How to configure JMS queue on OC4J server. Development in JDeveloper 10G

Hi there,
I have to configure a JMS for an Asynchronous process in my Application which will be running in Oracle 10G Application Server. Development Environment is Oracle JDeveloper 10G.
I am facing a problem on how to configure JMS queue.
Steps Followed are:
in the <JDevloperHome>/j2ee/home/config
1. Made the new queue and connection factory's JMS entry in jms.xml.
2. Specifed the queue in oc4j-connectors.xml.
3. played around with application.xml
and tried all combinations, but the message producer always failed to lookup the queue.
Need help on the steps to follow so that the producer can post the message in the queue.
Also please help how to configure the MDB to listen to the queue.
Thanx and Regards
Subham

If you were dealing with Oracle 10g app server as opposed to standalone, I might be better able to help you.
One thing though, when you are configuring your MDB in the orion-ejb-jar.xml file, do not forget to specify attribute listener-threads, otherwise no matter how many beans you have in your MDB pool, only one bean will be listening to the queue. Many listener-threads equal to max number of beans in pool.

Configuring JMS in Production mode

Similar Messages

Maybe you are looking for