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

Similar Messages

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

Integrating Messaging Server and Identity Server

I've got JES 2004Q2, and I'm trying to install the various components on different workstations to prove that a) the software works, and b) it's a viable alternative to Exchange (so please please help me get it working!)
The problem I have is getting Messenger Server and Directory Server talking properly so that I can create users and then log in as those users. After days of frustrating searching for solutions to this problem (and also find people who have successfully done this), I decided to install the components onto one server.
And it worked. Installing Messaging Server, Identity Server, Web Server (contained for Identity Server), Directory Server, and Admin Server all on the same box, configuring them all to use the same directory server for UG and preferences, running the various configuration tools that come with the software, and it all works together fine. Using "./commadmin domain modify .... -S mail", I get "OK". I can add users with the "-S mail" option, log in as those users, and send emails between those users. So this tells me that the software does work, albeit on one box.
When I try to separate the services out to separate boxes, they don't seem to integrate properly. I thought that maybe the order in which you configured applications made a difference (ie. configuring Identity Server after Messenger Server means IS will pick up on the changes made to the directory by MS, and enable it). I also tried to see if using the same options directory server from different boxes helped, but nothing. I've even tried patching them using 116568-52 and 116585-10 but no luck.
Therefore, I've found that installing all servers on one box works, but installing them on separate boxes doesn't (despite using the same directory servers). My conclusion in this is that one of two things must be the case:
a) there's something in the install that has to be changed to reflect the fact that the services are running on different boxes
b) the install of the services adds files to the system somewhere which other packages in JES pick up on (hence the reason why installing everything on one box works), and this isn't documented anywhere
Unfortunately, the output of commadmin when it fails isn't that helpful (nothing against the developers, however it doesn't really help in the fault finding process). I do believe however that the problem is with Identity Server and its configuration, rather than Messaging Server.
Here's some (possibly) useful info:
kipling# ./imsimta version
Sun Java(tm) System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004)
libimta.so 6.1 HotFix 0.01 (built 12:52:04, Jun 24 2004)
SunOS kipling 5.8 Generic_117350-02 sun4u sparc SUNW,Sun-Blade-1500
kipling#
(on UG server)
# ./commadmin domain modify -D admin -w <password> -d uwe.ac.uk -n uwe.ac.uk -S mail -H kipling.uwe.ac.uk
FAIL
Unable to set attribute(s)
(some verbose mode output)
[Debug]: Contacting : http://bronte.uwe.ac.uk:10080/commcli/TaskManager
[Debug]: To servlet: task=ModifyDomain&objecttype=Domain&domain=uwe.ac.uk&add_services=mail&add_preferredmailhost=kipling.uwe.ac.uk
[Debug]: RECV: FAIL
[Debug]: RECV: Unable to set attribute(s)
[Debug]: CLITask: status returned =FAIL
FAIL
Unable to set attribute(s)
[Debug]: DBG: doOne returned code=6
[Debug]: Contacting : http://bronte.uwe.ac.uk:10080/commcli/logout
[Debug]: Logout ...
[Debug]: RECV: SSOToken id AQIC5wM2LY4SfcyW5hbVBGXqCdsYYDjVarSFRMd6HIxsGho=@AAJTSQACMDE=#
[Debug]: RECV: destroyed
Root suffix: dc=uwe,dc=ac,dc=uk (all "o=" references have been dropped)
All services have their own local options directory server.
Can anyone give me any suggestions? If I log a support call with Sun, what is the likely resolution time? My ultimate goal is to get the whole suite running together, then install Portal server. Once that's working, download the connectors for Outlook and get it all working with Outlook. As I said at the start, we're hoping to show this is a viable alternative to Exchange (certainly for the backend) so any help will be greatly appreciated!
Iain

slo_chewie wrote:
Does the email recipient address change when the email is sent to gmail i.e. does an email sent to [email protected] become [email protected]?
We've got google for domains setup, so users would retain a @domain.com address regardless if there mailbox was hosted on the internal server or hosted at google.You can make use of the mailRoutingAddress: user attribute and source routing to get the desired behaviour e.g.
=> Set the following value to the LDAP entry of the user who is hosted on the gmail server. The "[email protected]" address should match the users mail: address:
mailRoutingAddress: @gmail.com:[email protected]=> Ensure the following option has been tcp_local channel in your imta.cnf file. This option strips off the "@gmail.com" value of the recipient address before sending the email to the gmail.com servers.
dequeue_removerouteMake sure you run "./imsimta cnbuild;./imsimta restart" after modifying the imta.cnf file.
Regards,
Shane.

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

WRT160NL built in DHCP server and WEB server stop to work

Hello all!
My home network based on the WRT160NL with one wireline PC, two wireless PCs and wireless printer works with no problems - connections are at full speed, no drop outs, wireless and wireline QOS is perfect. But then quite regularly every two or three days suddenly the router internal DHCP servers stops to work - I see with the wireshark that my wireline PC sends the DHCP requests to the router but router does not reply to them. If at the same moment the other PC's are allready in use and got theirs IP before they can surf the internet uninterrupted. Only router reboot helps to solve this situation. After the reboot DHCP server immediately acknowledges DHCP request from the PC and assigns him his IP number.
Sometime this situation occurs when IP address is already assigned, I can surf the internet, routing works, I can ping the router but I can not access the router's built in web server. Neither via IE, neither via FF.
I do not use P2P programs, IP traffic over the router is very light - no internal traffic between PCs, no file transfers to the USB flash key and WAN internet connection is 1Mbs. I have upgraded to the latest firmware Ver.1.00.01.17. Nevertheless problem occurs quite regularly about every three days.
I try to reproduce the problem more frequently and there is the way how to do that - I start to watch IP TV on my wireline PC (usually I watch my IP TV via the STB connected directly to the DSL modem) so IP TV multicast now goes through the router. It is about 5 - 6 Mbs and about 500 pps of IP traffic. This IP TV stream very often causes internal web server and DHCP server to stop. So although I can watch IP TV and surf the web on my PC with no problems, if other PC's are powered up during this situation they will not get theirs IP addresses.
I see in other posts on this forum that similar behavior can be triggered also with the heavy read/write traffic to the attached USB flash key.
So my conclusion would be:
- are the problems above known to Linksys/Cisco, do they acknowledge them, do they work on them
- when we can expect new firmware release - can we expect new release for this model at all
Best regards
Message Edited by srus on 02-12-2010 04:05 AM
Message Edited by srus on 02-12-2010 04:14 AM

Ridcully thank you for your post, I did not execute the procedure you suggested. Prior to execute it I want to get more background on it? Why do you think that reconfiguring from the factory defaults would solve my problem? Are you 100% sure that this is the solution or are you just guessing?
Router offers backup and restore functionality where you can store current configuration into file on PC and latter restore it. Can I use this functionality in your procedure or should I reconfigure all router settings manually?

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.

ARCHITECTURE OF SAP R/3 AND APPLICATION SERVER AND DATABASE SERVER IN ABAP

ARCHITECTURE OF SAP R/3 AND APPLICATION SERVER AND DATABASE SERVER IN ABAP?
PLEASE EXPLAIN

hi
Presentation Server
It is actually a program named sapgui.exe.
It usually installed in users workstation.
The interface accepts the input from the user in the form of keystrokes, mouse-clicks, and function keys, and sends these requests to the application server.
It receives and displays the result from the application server.
Application Server
An application server is a set of executables that collectively interpret the the ABAP/4 programs.
Each application server has a profile called application server profile, that specifies its characteristics when it starts up and while it is running. It specifies:
1. Number of processes and its types.
2.Amount of memory each process may use.
3. Length of time a user is inactive before being automatically logged off.
If your ABAP/4 program requests information from the database, the application server will format the request and send it to the database server
Database Server
The database server is a set of executables that accepts database requests from the application server.
These requests are passed on to the RDBMS (Relation Database Management System).
The RDBMS sends the data back to the application server.
The RDBMS may run on database servers computer or may be installed on its own computer.
The components of application server are dispatcher, dispatcher queue, work process.
All requests that come in from presentation servers are directed first to the dispatcher.
The dispatcher writes them to the dispatcher queue.
The dispatcher pulls the requests from the queue on a first-in, first-out basis.
Each request is then allocated to the first available work process.
A work process handles one request at a time.
The work process needs two memory areas, the user context and the roll area.
The user context is a memory area that contains the information about the user.
The roll area is a memory area that contains about the program execution.
User Context
User context is a memory area that contains the characteristics of a user that is logged on the R/3 system.
1)It holds, users current settings.
2. The users authorizations.
3. The names of the programs the user is currently running.
When a user logs on, the user context is allocated for that logon. When logs off, it is freed.
Roll Area 
A roll area is a memory that is allocated by a work process for an instance of a program.
It holds the information needed by R/3 about the program execution, such as: 1. The values of the variables
2. The dynamic memory allocations
3. The current program pointer.
Each time a user starts a program, a roll area is created for that instance of the program.
If two users are using the same program at the same time, two roll areas will exist-one for each user.
The roll area is freed when the program ends.
Both roll area and the user context play an important roll in dialog processing
pls reward points dor useful ans
regards
vivek
Message was edited by:
 Vivek Saxena

How to data insert Source server and Linked server (Target Server) at same transaction

I have try several times for Data insert Source server and Linked server (Target Server) at same transaction. I am using Begin transaction. but Source server is completed and Linked server error (or Linked server Completed and source server
ERROR). at this moment I want ROLL back. how?

Hi
Run below query by changing to yourr linked server name and see if DTC is enable or not.. if not
Begin distributed transaction
select * from [ServerName].master.dbo.sysprocesses
Commit Transaction
To enable MSDTC on each Web server on Windows Server 2008
Click Start, click Run, type dcomcnfg and then click OK to open Component Services.
In the console tree, expand Component Services, expand Computers, expand My Computer, and then expand Distributed Transaction Coordinator.
Right click Local DTC, and click Properties to display the Local DTC Properties dialog box.
Click the Security tab.
In the Security Settings section, click Network DTC Access.
In the Client and Administration section, select Allow Remote Clients and Allow Remote Administration.
In the Transaction Manager Communication section, select Allow Inbound and Allow Outbound.
In the Transaction Manager Communication section, select Mutual Authentication Required (if all remote machines are running Windows Server 2003 SP1), select Incoming Caller Authentication Required (if running MSDTC in a cluster), or select No Authentication
Required if some of the remote machines are pre-Windows Server 2003 SP1. No Authentication Required is the recommended selection.
Select Enable XA Transactions, and then click OK.
Repeat steps 1 through 9 on the other Web servers.
Thanks
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Upgrading both SharePoint 2010 server and DB server with latest available patch

We have 2 servers in the farm ( SharePoint server and Database server)
We are planning to patch the database server and SharePoint server as well at the same time.
For this activity I have found some ways :
Way 1:
First I will do the patching in SP server and run the configuration wizard.
Once it's finished , I will shutdown the SP server.
Start patching in SQL server
After done in Sql server , I will restart the SP server.
Way 2:
First I will do the patching in SP server and run the configuration wizard.
Once it's finished , I will disconnect the SP server from SQL server by using the configuration wizard.
Start patching in SQL server
After done in Sql server , I will reconnect both the server's.
Way 3:
I don't follow any one of the above ways. Simply patch both the server's one by one (Here might be, when we do the DB server patch upgrade database connection failed entries will be track into event viewer because of DB server unavailability )
Here my questions are :
If disconnect the server's from each other , can I reestablish the connection again ?? Is there that option ???
Is it compulsory to disconnect / shutdown the SP server while patching in DB server ???????
Suppose I don't follow any of the above way , cause any issues ?????
If any DB connection related entries will track into Event Viewer, is this cause any issues ?????
Any suggestions would be appreciated.
RameshNK

Patching order will not matter. You also do not necessarily have to shutdown SharePoint while patching SQL. Yes, SharePoint will throw errors in the Event Log and ULS log.
I might suggest patching SQL Server first, simply because it is quick and in my experience, "safe". That is, the patching process works and works well. It is unlikely you'll come out with an unserviceable SQL Server instance.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

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.

Diff. between content server and archive server(SARA on content server)

I am very interested about difference between content server and archive server. Is there content server supplied by SAP and archive server by third party producers or something else?
If so dditionally what needs to be done to archive data (via Sara) on content server. I did it on sap R/3 4.0 on an archive server. Is it huge difference to do it on 4.7x2 on content server?

Hey,
The content server is used to save documents,
and SARA (and other third party producers) are used to archive old data.
For example:
You should use Content server - When you need to save un-structured data about worker (e.g: pictures, documents and etc) .
You should use SARA (and other third parties) - When you need to move to archive old
worker which have left your organization before 5 or more years (there for they are not relevant for you)
Here is some more information about Content server
from help.sap.com:
"Therefore, besides the SAP database, an external content server is always available in every SAP system installation. In this way, the necessary technical infrastructure is provided for all document-centric applications and business scenarios that do not require a long-term archiving solution"
Here is some more information about SARA and archiving
from help.sap.com:
"Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode."
for more information:
http://help.sap.com/saphelp_nw70/helpdata/en/8c/e9ddbb5d9a524bbb7854d31b963248/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/73/c335406ee32e34e10000000a155106/frameset.htm

Differences between CTI OS Server and CTI Server ?

Hello community,
I've been working with CTI Desktop for a while but I'm not clear about the differences between CTI OS Server and CTI Server?
If you go to http://docwiki.cisco.com/wiki/Unified_CCE_Software_Compatibility_Matrix_for_8.5(x) and read note 10, they make diffrences between both products.
Thanks in advance,
Alejandro

CTI Server was the original CTI interface into ICM. It uses a network communication protocol, GED-188 I believe, for communication between the client and server. This is relatively difficult to program against. CTIOS and it's related SDKs were developed to provide an easier method of developing desktops and integrating desktop applications. CTI Server communicates with ICM, CTIOS Server communicates with CTI Server, and desktop applications using the various SDKs communicate with CTIOS Server. Cisco may be looking to get away from CTIOS Server in the future because of their decision to integrate Finesse with CTI Server rather than CTIOS Server. Hope that helps.

Enqueue server and Message server in ABAP/Java dual stack

Hi you guys,
I have some questions when studying SAP, could you please explain for me:
- In ABAP and Java system, do each stack have it own enqueue server and message server?
- What is the difference between Enqueue server and enqueue work process in ABAP stack?
- If there is one message server for each stack, which messager server (ABAP or Java) will the Web dispatcher connect directly to?
- How do ABAP message server and Java message server communicate with each other?
Thank you very much.

1. in Dual Stack, normally you have ABAP Stack and SCS Central service Instance. ABAP Instance has Message server, SCS has it own Message server and enqueue server. ABAP instance doesn't have enqueue server, because the SCS already has enqueue service
2. Communication between ABAP and J2EE Engine uses RFC (JCo) or HTTP Interface.
Web Dispatcher will connect to the ICM of that instance, and the ICM is talking to Abap dispatcher and J2EE Dispatcher.
3. The term: enqueue server and enqueue work process , already shows its different quite obviously.
What so confuse about it ? do some search on SAP Online Documentation.
Regards,
Vincent

Calendar Server and Email Server on Same Machine - Email Issue

Hi.
I've installed email and calendar on the same host. The email domain for test purposes is the name of the machine. I noticed in the configuration guide, it says that if you put the calendar server and email server on the same machine you need to configure sendmail.cf and modify incoming rules in order to get email reminders from Calendar to Email. I have done this but am still not able to. I get the emails kicked back to root and they say:
553 5.3.5 System Config Errors
553 5.3.5 <machine name> config error: mail loops back to me (MX problem?)
Has someone seen this before?
Thank You,
Matt

Hi Russ,
We have the same problem as Matt.
We have properly set up OCS Email it works well both inside and outside our network.
The only thing that appears not to be working is the email notification capabilities of OCS Calendar.
We have changed sendmail.cf as stated in the documentantion.
we are using -
RedHat Advanced Server 2.1,
sendmail 8.11.6
bind 9.1.3
I would be very gratefull of any information on this, as we're out of ideas...

Starting Commerce Server and Personalization Server

Similar Messages

Maybe you are looking for