IFS Server and Weblogic Server compatibility.

We are planning to host IFS Server on one Machine and Weblogic Server on another machine. Can we access IFS Server from Weblogic Server, which resides in another machine?
Presently we have installed Oracle IFS along with apache and we are comfortable running our programs developed using the IFS Java API, JSP and Java Beans.
Please let us know whether it is possible for the same, where Oracle IFS is installed in another machine and Weblogic is installed in another machine.
Best Regards
Sujeem Haries

It's not advisable, the general advice is to try to keep the SharePoint servers as clean as possible for both stability and security.
Having said that it is possible to install the Office suite on a SharPoint server and there are no massive gotchas i'm aware of. It is also worth noting that MS do not support automated (unattended) use of office applications.
http://support.microsoft.com/kb/257757/en-gb

Similar Messages

What is diff between oracle application server and weblogic server?

what is the exact difference between oracle application server and weblogic application server?

The difference between Oracle Application Server AND WebLogic Server has been discussed in a lot of forums dated 2008 and earlier comparing OAS10g with WebLogic10.0/WebLogic9.2
But, now since Oracle has taken over WebLogic, this is not really important.
Now, OAS has no further releases post 10g. WebLogic Server will be the Oracle's strategic application server going forward.
So, if your query is for choosing one of them for a new environment, you are better of with WebLogic Server 10.3.6 OR WebLogic Server 12g
As we will not have further releases of OAS and also OAS10g will be end of life soon, we recommend Oracle WebLogic Server.
If you still want to know the differences, here is one such old oracle documentation link that talks about it
http://docs.oracle.com/cd/B10467_16/migrate.904/b10425/asmwl02.htm
Arun

Differences between Weblogic Server and Weblogic Server Suite?

Hi
What is the differences between Weblogic Server and Weblogic Server Suite, beside licens costs?
Regards
/Martin

WebLogic server standard edition, you get the WebLogic with no clustering.
Clustering is available in the WebLogic Enterprise Edition.
The WebLogic Suite also gives you Coherence and JRockit real-time
A desciption of the various products can be found here: http://www.oracle.com/us/products/middleware/application-server/index.html

Compatibility issues between solaris 10 patches and Weblogic server 9.2

Is there any documentation about possible incompatibility between certain solaris patches and Weblogic server?

Hi,
Can you post the output of below commands from your OS?
uname -a
getconf LONG_BIT
Do you want to download and install 64-bit WLS 9.2 on your OS?
- - Tarun

Jbuilder 6 enterprise and weblogic server 6.1 integration problem

hello,
i am using jbuilder 6 enterprise and weblogic server 6.1. i just got a new
workstation and imported my old project from cvs into jbuilder and
everything is fine up to this point.
the application in question is using servlet filters, so i absolutely need
web application version 2.3. it seems, though, that my jbuilder believes for
some reason that only tomcat 4 and borland enterprise server are capable of
using servlet filters. i cannot remember how i fixed this last time around,
but i did somehow. i had a recollection that the jb6_all_001 patch did the
trick, but obviously it didn't this time, at least. what is really annoying
is that the wizard does not allow me to create servlet filters and the
webapp dd editor does not allow me to configure filters, either. of course,
i can edit web.xml manually, but starting the server changes the dtd back to
2.2 and removes everything that is 2.3 specific.
please help me fix this?

at the moment it is possible for me to work, though. i worked around the
problem and i set web.xml as a read only file. i still can't use wizards to
create servlets and i can't edit web.xml with jbuilder.

Apache and weblogic server

hi all.
i am using oracle application server 10g R2 over windows server 2003 64bit
but now i planned to go for apache and weblogic server for this i do not have idea that
should i do? plz what softwares are required to use apache and weblogic server with current version
10g R2.?

The WebLogic Server (WLS) is a Java container similar to OC4J in Application Server 10g release 2. If you want to use WLS, you will have to upgrade your Application Server 10g installation to Fusion Middleware 11g. The upgrade path typically depends on the products which you are using in 10g, e.g. the upgrade path for SOA is different than the upgrade path for Forms/Reports or Oracle Portal. The [url http://docs.oracle.com/cd/E23943_01/upgrade.1111/e10125/before_you_begin.htm]Upgrade Planning Guide is a good start.
Thanks,
EJ

Different service packs in admin server and managed server

Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace

Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace

P13N Server and App Server on separate systems - strange ports opened

Hi -
          We have a configuration using WebLogic Personalization Server 3.1.1 on one
          server and WebLogic Application Server 5.1 w/Service Pack 6 on another
          server. What we've seen with our firewall configuration is that it appears
          there are high-number random ports opened occasionally from the App Server
          to the P13N Server, which d not appear to be related to connection attempts
          (ex: port 42100). The only communication that we know should be happening
          between the two systems are T3-based JNDI lookups, LDAP lookup/update
          requests, and SQL queries. My questions, then, are as follows:
          1) In handling JNDI requests, are there any callbacks that can occur between
          the two servers in this configuration on a different port?
          2) When separating the P13N Server and App Server, are there any "private"
          ports opened between the two systems for management? As far as I know, the
          App Server should simply view the P13N Server as another client, but the
          firewall log would indicate that something is going on related to this.
          If anyone has a similar config and can provide some info related to
          potentially unseen port connections, please let me know. Thanks in advance!
          Andy
          [email protected]


Haakon,
I think the BPEL forum is the better source to ask
BPEL
Frank

Failed to start Admin Server for Weblogic Server Domain

I Created a domain named mydomain in weblogic server 10.3 in server 2003.But when i start Admin Server for Weblogic Server Domain from startmenu, it failed.
I examined the log under domains\mydomain\servers\AdminServer\logs\AdminServer.log and got the following information:
java.lang.NoClassDefFoundError:weblogic/ldap/EmbeddedLDAPChange
at weblogic.ldap.EntryChangeListenerImpl.receiveEntryChanges(EntryChangeListenerImpl.java:28)
Caused by :java.lang.ClassNotFoundException: weblogic.ldap.EmbeddedLDAPChange
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
Caused by :java.util.zip.ZipException: error reading zip file
at java.util.zip.ZipFile.read(Native Method)
at java.util.zip.ZipFile.access$1200(ZipFile.java:29)
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
at ...(CommonSecurityServiceManagerDelegateImpl.java:465)
Caused by: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
at .. (ServiceEngineImpl.java:365)
Caused by: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
at .. (BootStrapServiceImpl.java:910)
Caused by: <openjpa-1.1.1-SNAPSHOT-r422266:891341 nofatal user error>kodo.jdo.UserException: This operation cannot be perfomed while a Transaction is active.
at org.apache.openjpa.kernel.BrokerImpl.close(BrokerImpl.java:4087)
####<Critical><WebLogicServer><SOA><Adminserver><main><<WLS Kernel>><><><1282012271468><BEA-000362><Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399] Security Services Unavailable
at weblogic.security.service.CommonSecurityserviceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
I ignored some detailed error message.The runtime environment is server 2003 Enterprise Edition sp2.
Thx in advance for any reply.

Hello Djam,
Please review the following:
The FMW WebLogic Server (WLS) installation has been configured to use a non-default Java temporary files directory,
i.e. the following has been set in the WebLogic startup or setDomainEnv.sh script:
EXTRA_JAVA_PROPERTIES="-Djava.io.tmpdir=/appl/oracle/temp_java_files ${EXTRA_JAVA_PROPERTIES}"
Reference: How to Change the WebLogic Server Location for Temporary Files (Doc ID 1336002.1)
When the Middleware home was restored the directory specified by java.io.tmpdir parameter was missing,
Therefore an IOException occurred when opening the wallet and WLS was unable to initialize the OPSS successfully.
To resolve the issue re-create the directory specified by the java.io.tmp dir parameter, and make sure the owner and group access are the same as for the FMW installation.
Unable Start AdminServer: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException (Doc ID 1923395.1)
Bogdan

Starting Commerce Server and Personalization Server

I am trying to evaluate these products. I am running NT 4.0, SP5 with
256MB RAM. I have installed Weblogic Server 5.1.0 with SP 6. I have
installed the latest version of the Commerce Server and Personalization
Server. I had to remove the -server switch from the java command line in
the startup script in order to get the JVM to start. The Commerce server
begins to initialize, then a bunch of exceptions are thrown, then it
shuts itself down.
I have attached the log file
WeblogicCommerceServer3.2\server\weblogic.log
Thanks for any help on this.
[weblogic.log]

The error in your weblogic.log file of:
2001:<E> <T3Services> COMMERCE_SERVER_FRAMEWORK,LOG_ERROR,"Current WebLogic build may
not be compatible with the WebLogic Commerce Server implementation. Minimum Build:
83914 Current Installation Build: 66825"
Tue Apr 24 16:50:53 EDT
means that WLCS cannot find the correct service pack files for WLS 5.10. Might check
to see if the WLS 5.10 SP6 files (weblogic510sp6.jar and weblogic510s6boot.jar) are
located in d:\weblogic\lib.
Ted
jcerruto wrote:
I am trying to evaluate these products. I am running NT 4.0, SP5 with
256MB RAM. I have installed Weblogic Server 5.1.0 with SP 6. I have
installed the latest version of the Commerce Server and Personalization
Server. I had to remove the -server switch from the java command line in
the startup script in order to get the JVM to start. The Commerce server
begins to initialize, then a bunch of exceptions are thrown, then it
shuts itself down.
I have attached the log file
WeblogicCommerceServer3.2\server\weblogic.log
Thanks for any help on this.
Name: weblogic.log
weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
Encoding: base64

Problem creating a domain w/ one Admin Server and Managed Server

I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error:
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
     at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
     at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
     at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
     at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
     at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
     at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
     at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
     at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <JMS> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
     at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
     at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-141197> <The deployment of pfJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
     at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:198)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
     at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
     at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
     at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
     at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
     at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Deployer> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328461> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
     at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
     at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
     at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
     at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
     at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
     at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
     at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
     at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
     at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1633)
     at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
     at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1809)
     at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
     at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
     at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
     at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
     at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
     at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
     at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>

I am using the default db the installation uses which is PointBase. I am not using any specific db, JDBC Datasource/Connection pool Configuration.
Just to try something different, I tried creating a domain w/ one Admin and Managed Server which uses a Cluster and I did not get any errors. From what I read, a cluster is not necessary but not sure why it works without errors w/ a cluster.
I will try commenting out the datasource from the config and see what happens and will let you know.

Communication protocol between Admin Server and Managed Server

Hello - I am hoping someone can help me here to understand the communication protocols used in my setup.
Here is my understanding of the protocol that are used between each component.
End User <--->HTTPS<--->LoadBalancer Device<--->HTTPS<--->Web Server<---->HTTPS<--->WebLogic Server(Managed Server)<--->LDAP/JDBC<-->Data tier components
AdminServer<--->T3<--->Managed Server i.e. The communication protocol between Admin Server and Managed server is T3
The communication protocol between Managed Servers running in one cluster on two seperate machine is What?
Thank you.

Hello, interesting question.
In the documentation " [cluster multicast communication|http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001] " don't specify the used protocol to pack the information for example in a session replication.
Although in a session replication all objects must be serializable i don't think rmi protocol is used.
I hope some expert give us some light in this issue :-)
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001

NPE Starting v8.1 Server using WebLogic Server Tools 1.0.0

After installing/configuring Eclipse JEE Europa and BEA WLS 1.0.0, I receive an NPE when attempting to start a v8.1 Server. The log message is listed below. Any ideas?
- Ron
!ENTRY org.eclipse.core.jobs
!MESSAGE An internal error occurred during: "Starting server - BEA WebLogic Server v8.1".
!STACK 0
java.lang.NullPointerException
at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.setupLaunch(GenericServerBehaviour.java:408)
at org.eclipse.jst.server.generic.core.internal.ExternalServerBehaviour.setupLaunch(ExternalServerBehaviour.java:66)
at com.bea.workshop.wls.legacy.Weblogic81ServerBehaviour.setupLaunch(Weblogic81ServerBehaviour.java:183)
at org.eclipse.jst.server.generic.core.internal.ExternalLaunchConfigurationDelegate.launch(ExternalLaunchConfigurationDelegate.java:97)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:766)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:608)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:601)
at org.eclipse.wst.server.core.internal.Server.start(Server.java:1265)
at org.eclipse.wst.server.core.internal.Server.synchronousStart(Server.java:1662)
at org.eclipse.wst.server.core.internal.StartServerJob.run(StartServerJob.java:34)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Ron,
I am sorry to hear that you are experiencing problems with WLS Tools. We
will investigate the issue you've reported as soon as possible. To make
the investigation move along more smoothly, can I ask you to open a bug
report in our public bug tracking system?
http://bugzilla.bea.com
Please include the stack trace from your message, which operating system
you are running on and which service pack of WLS 8.1 you are using.
Thanks,
- Konstantin

Mail, iCal Server and iChat server will not work over VPN

I have an Airport Extreme Base Station at the office running the network. Behind it sits a Mac Mini Snow Leopard server running 10.6.3. The ports necessary for Mail, iCal Server and iChat work fine through that external connection. I can also connect with VPN from my 10.6.3 clients.
HOWEVER, when I connect with the VPN clients, I am suddenly unable to access the Mail, iCal Server, Wiki server and iChat server. All connections time out. I can ping the server and I can do other things that do NOT work on the public Airport like ssh or VNC. ssh and VNC are closed at the airport extreme.
So it's pretty odd. When I'm connected via the VPN, all ports that are forwarded to the Snow Leopard server time out over the VPN.
I've tried various and sundry configurations with the VPN client. This includes trying to send all traffic over the VPN, moving it up in the service order, etc. etc. Nothing fixes it. DNS resolution is working fine, however when I do a wireshark capture of ppp0 traffic, I notice that SSL and TLSv1 handshakes appear to occur on the public IP address instead of the private network IP address... and they're all resets.
Has anyone gotten this to work successfully? Like I said, all ports that are NOT forwarded through the Airport work fine over the VPN, but will not work when connected to the VPN. It's really bizarre.

New data: any ports that are normally forwarded on the Airport Extreme to the Mac Mini server will not work when connected to the VPN.
For instance, if I have imaps/993 forwarded from the Airport Extreme to the Mac Mini, it works fine over the Internet. If I connect to the VPN, I can connect to all OTHER services on the Mac Mini, but Mail, for instance, will not work.

How do I set up a mail server and SMTP server to send messages to other mail servers at mavericks

How do I set up a mail server and SMTP server to send messages to other mail servers at mavericks

You need to get the settings for your email from your email provider and enter them in Internet Accounts (System Preferences). Many of the common systems are already available, all you need is a password and an email address to set them up.

IFS Server and Weblogic Server compatibility.

Similar Messages

Maybe you are looking for