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

Similar Messages

How to restart Java Engine in ABAP+JAVA dual stack installation ?

Dear Experts
if i use stopsap r3 in this dual stack installation - it stops both ABAP & JAVA Web Application Servers.
I want to restart only JAVA Weba pplication server.
How do it ?
Thaks in Advance !
Rgds

But theoritically they are 2 indpeendent installations like
AS ABAP
AS JAVA
..Do you aggree ?? really am not good on basics!!
During the installation also - if select AS ABAP & AS JAVA - it will become dual installation
and it does not show
any dependency while installing that AS JAVA requires AS ABAP.[Installation Component Selection and Dependency Screen shot|http://i303.photobucket.com/albums/nn153/S0002919350/SAP%20Issues/Oracle_Patches.jpg]
Installation Component Selection and Dependency Screen shot
Is it because if AS ABAP is down - AS JAVA UME is 001 client - and Java authentication fails ?
Can we de attatch from ABAP UME for my requirement like - running JAVA WAS alone w/o ABAP.
Regards
PR
Regards
Edited by: P.R. SRINIVAS on Jun 16, 2008 4:15 PM

How to separate ABAP+JAVA Dual stack in stand alone engins?

Hello SDN!
We are thinking about to separate our Dual Stack ERP 6.00 System on Windows/Oracle in two stand alone system Java und ABAP. Wie have afew small implementation in Dual Stack such as ESS and wie have no modifications at all.
Has somebody an expiearence with that? Knows somebody about some tools for such an action?
I will be very pleased for any help
With best regards
Vladimir

You may find attached link helpful and interesting
[Doublestack : separate JAVA Stack from ABAP Stack ...;

MSCS H/A enqueue, replication and message servers services

Hi,
I'm looking at the documentation about "Installation of multiple SAP Systems in MSCS: MSSQL Server" but I have a few questions about the SCS and ASCS process.
Are the process setup as generic cluster service? Or are they SAP provided cluster services?
What monitoring is done with the the enqueue, replication and message server services in the cluster?

Mike,
The SAPINST installer will install SCS and ASCS services into MSCS for you. They are installed inside the SAP group in cluster.
The message servers, controlled by either SCS is HA with MSCS. The enqueue services is HA with installation of ERS locally on both nodes. SCS + ERS + ERS provides a triangular HA that means the services is always on and can withstand an cluster failover. The cluster only controls the SCS service. The ERS services are local to each server.
Let me know if I did not answer the question.
jwise

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.

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 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.

Identity and Messaging Server 6

I've installed JES 2004Q2, Identity and Messaging Server 6 in Schema 2.
I may understand that identity provides managing user from Messaging. Where can i find a procedure to add and configure Identity to do that ?
Does Sun really not support this way to manage Messaging Users ?
Thanks.

Here are the main steps...
1.
Install JES from the installer with identity, mailserver, and commadmin (and the extra msg queue, LDAP etc that is required).
2.
configure mailserver and commadmin separately (config script in the software main directory). Probably best (if not required) to start with mail before commadmin...
3.
Administration is done with cmd util "commadmin" against identity server. There is also a sample service modules for mail that can be used in the web gui for user admin. This module is however NOT supported as Jay Plesset earlier said.
btw
the docs are much better now and describes this well.
/Per-Olov

PI 7.11: Cannot connect to server using message server:...

Hello Guys,
we make the Application Management for a Customer PI System.
Scenario:
- the SAP Gui Connection to the ABAP Stack is routed via SAPRouter and Works fine.
SAP Gui -> our SAP Router -> VPN Box from Customer -> Firewall Customer -> ABAP Stack PI System
- WebAccess its working fine, the Customer use Webdispatcher on every PI Server...
Browser -> VPN Box from Customer -> Firewall Customer -> Java Stack (Port: 5xx00 btw. 81xx (Webdispatcher))
Problem:
Our Problem ist, we can not proceed the Integration Builder or the ESB, the Java Web Start works fine and open the Logon Screen Correctly -> but i fill the Logon Screen with my User name and Password and press Logon come the follwing Error:
"Cannot connect to server using message server: ms://<hostname>.<domain>:8134/P4"
In the Details from the Error Message:
"<hostname>.<domain>:53404 Reason: com.sap.engine.services.rmi_p4.P4IOException:
Cannot open connection to host: <IP-Adress of Central Instance> and Port: 53404"
The Customer says, the Firewall is open with the IP Adresses and P4 Port but i dont think so...
Can everybody help me, or have tips for me! I have checked a lot of OSS Messages (PI High Availabilty etc... its all correct on the System)
Sorry for my bad English
Best Regards,
Markus

Hi Markus,
did you check if the browser is using a proxy? (In this case your scenario unfortunately won't work).
P4-port should generally be routed via a proxy (described in the help.sap.com), but within the PI-Tools(JNLP) the proxy-usage is not implemented. There is even a SAP-note that describes how to check the JavaWebStart-Proxyconfiguration, but this won't help either.
If there is a proxy defined in the browser everything is working fine till you pass the logon-screen but even with the correct "javaws"-settings you won't be able to go on.
(This problem is pretty bad if you do have developers and the SAP-servers seperated because of security issues. I'm hoping that this malfunction will be solved with upcoming patches.)
Solution: Establish a connection without any proxy in between.
E.g.: a terminal server in the same network
It would be helpful to find more people with the same problem to force a fix from SAP for that.
If anyone else is having problems with this, please add a comment to this thread.
Best regards
Christian

Cannot connect to server using message server: ms://xiidhasoft:50004/P4

Hi SAP Guru's
When PISUPER or any any of the enduser is trying to login in the Integration Builder , they are getting error
Cannot connect to server using message server: ms://xiidhasoft:50004/P4
I have tryed to search in SDN and got below solution but no success
1. Exchange Profile of PI - http://host:port/exchangeProfile
2. Check with the rmi port number.
3. if rmi port number is empty or any number is present ( check with Tr code: SMICM - services - check for p4 port number - it will be ex: 5<nr>04)
4. fill the rmi port number as present in the P4.
OR
implement note 864268
I have Netweaver PI 7.1 .
Please suggest some alternative solution.
Thanks & Regards
Vinay Patel

You may check your local PC Java Network Setting.
Troubleshooting:
Probably Javau2122 WebStart does not detect the correct Proxy Settings. In this case please proceed as follows:
To change the Proxy Settings for Javau2122 Web Start:
1. Click Start --> Run and enter javaws. Press button OK.
2. Control Panel -> Programs ->Java -> Network Settings...
3. Select Direct Connection to switch off the proxy settings and press button OK.
If this still does not work, select Use proxy server to set manually the HTTP Proxy and Port.
Contact your network administrator for the correct settings.

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.

Integrating calendar server with messaging server

hi all,
i have installed messaging server but am not able to bind messaging server and calendar server together.the calendar server does not start with ./start-cal command.i am attaching the ics.conf file below.
!!!! ics.conf Parameter Specification: You can have three kinds of records
!!!! #1) Uncommented Key: Starts with alphabet [a-z] and in the form a="b"
!!!! #2) Commented key: Start with !!<alphabet> OR !![a-z]
!!!! And in the form !!a="b" (min 7 chars length)
!!!! #3) Commented Lines: Starts with ! But not with !![a-z]
!!!! #4) Records other than types #1, #2, #3 will be ignored or won't be
!!!! processed e.g. blank lines, lines starting with non-alphabets etc..
!!!! All these parameters are SINGLE valued
!!!! Imaginary Domain Names siroe.com, varrius.com, florizel.com, and sesta.com
!!!! are used in the examples below.
! Description sent with insufficient disk space messages.
alarm.diskstat.msgalarmdescription = "percentage calendar partition diskspace available"
! Number of seconds between monitoring disk space.
alarm.diskstat.msgalarmstatinterval = "3600"
! Percentage of available disk space that triggers sending a warning message.
alarm.diskstat.msgalarmthreshold = "10"
! Whether alarm.diskavail.msgalarmthreshold is above or below percentage. -1 is below and 1 would be above.
alarm.diskstat.msgalarmthresholddirection = "-1"
! Number of hours between sending warning messages about insufficient disk space sent out.
alarm.diskstat.msgalarmwarninginterval = "24"
! Specifies the SMTP host for server alarms.
alarm.msgalarmnoticehost = "sonlinux.bg2iop.com"
! Specifies the SMTP port for server alarms.
alarm.msgalarmnoticeport = "25"
! Who are server alarms sent to?
alarm.msgalarmnoticercpt = "[email protected]"
! When server alarms are sent, who is the sender?
alarm.msgalarmnoticesender = "[email protected]"
! Default is "From: %s\nTo: %s\nSubject: ALARM: %s of \"%s\" is %u\n\n%s\n"
alarm.msgalarmnoticetemplate = ""
! Description sent with no service response messages.
alarm.responsestat.msgalarmdescription = "calendar service not responding"
! Number of seconds between monitoring services.
alarm.responsestat.msgalarmstatinterval = "3600"
! Only trigger sending a warning message if no service response.
alarm.responsestat.msgalarmthreshold = "100"
! Whether alarm.responsestat.msgalarmthreshold is above or below percentage. -1 is below and 1 would be above.
alarm.responsestat.msgalarmthresholddirection = "-1"
! Number of hours between sending warning messages about no service response sent out.
alarm.responsestat.msgalarmwarninginterval = "24"
! Enable (yes) or Disable (no) browser cache for performance reasons.
browser.cache.enable = "no"
! Retry time in seconds after a recoverable alarm delivery error.
caldb.berkeleydb.alarmretrytime = "300"
caldb.berkeleydb.archive.enable = "0"
! Interval between hotbackup or archivebackup in seconds
caldb.berkeleydb.archive.interval = "120"
! Maximum number of days of archivebackup
caldb.berkeleydb.archive.maxdays = "6"
! Minimum number of days of archivebackup
caldb.berkeleydb.archive.mindays = "3"
caldb.berkeleydb.archive.path = "/var/opt/sun/calendar/csdb/archive"
! Percentage threshold of allowable disk space usage
caldb.berkeleydb.archive.threshold = "70"
! Seconds between checkpointing.
caldb.berkeleydb.checkpointinterval = "60"
! Remove checkpoint files after synchronized? (yes/no)
caldb.berkeleydb.circularlogging = "yes"
! Milliseconds between checking database deadlocks.
caldb.berkeleydb.deadlockinterval = "100"
! Enable more advanced notifications - replyevent/refreshevent/replytodo/refreshtodo considered
! as advanced topics. By default, all these notifications will be published to
! modifyevent and modifytodo respectively. If it is enabled modifyevent will get only
! organizer updates to components and attendees replies and the refreshes triggered by replies
! to components will be published to the respective topics. (yes/no)
caldb.berkeleydb.ensmsg.advancedtopics = "no"
! Create an ENS message when a calendar is created? (yes/no)
caldb.berkeleydb.ensmsg.createcal = "no"
! Create an ENS message when an event is created? (yes/no)
caldb.berkeleydb.ensmsg.createevent = "no"
! Create an ENS message when a task is created? (yes/no)
caldb.berkeleydb.ensmsg.createtodo = "no"
! Create an ENS message when a calendar is deleted? (yes/no)
caldb.berkeleydb.ensmsg.deletecal = "no"
! Create an ENS message when an event is deleted? (yes/no)
caldb.berkeleydb.ensmsg.deleteevent = "no"
! Create an ENS message when a task is deleted? (yes/no)
caldb.berkeleydb.ensmsg.deletetodo = "no"
! Create an ENS message when a calendar is modified? (yes/no)
caldb.berkeleydb.ensmsg.modifycal = "no"
! Create an ENS message when an event is modified? (yes/no)
caldb.berkeleydb.ensmsg.modifyevent = "no"
! Create an ENS message when a task is modified? (yes/no)
caldb.berkeleydb.ensmsg.modifytodo = "no"
! Initial size of the in-memory Event Notification Server message queue. This queue stores all ENS messages other than alarm reminders.
caldb.berkeleydb.ensmsg.qsize = "10000"
! Create an ENS message when an event is refreshed? (yes/no)
caldb.berkeleydb.ensmsg.refreshevent = "no"
! Create an ENS message when a task is refreshed? (yes/no)
caldb.berkeleydb.ensmsg.refreshtodo = "no"
! Create an ENS message when an event is replied? (yes/no)
caldb.berkeleydb.ensmsg.replyevent = "no"
! Create an ENS message when a task is replied? (yes/no)
caldb.berkeleydb.ensmsg.replytodo = "no"
! Create an ENS message when a scheduling request written to the calendar is deleted? (yes/no)
caldb.berkeleydb.ensmsg.schedreq = "no"
! Physical path location of database event, task, and alarm files.
caldb.berkeleydb.homedir.path = "/var/opt/sun/calendar/csdb"
caldb.berkeleydb.hotbackup.enable = "0"
! Maximum number of days of hotbackup
caldb.berkeleydb.hotbackup.maxdays = "6"
! Path for archivebackup
!caldb.berkeleydb.archive.path
! Path for hobackup
!caldb.berkeleydb.hotbackup.path
! Enable/disable of archivebackup feature, yes/no
!caldb.berkeleydb.archive.enable
! Enable/disable of hotbackup feature, yes/no
!caldb.berkeleydb.hotbackup.enable
! Minimum number of days of hotbackup
caldb.berkeleydb.hotbackup.mindays = "3"
caldb.berkeleydb.hotbackup.path = "/var/opt/sun/calendar/csdb/hotbackup"
! Percentage threshold of allowable disk space usage
caldb.berkeleydb.hotbackup.threshold = "70"
! Max megabytes of checkpoint file.
caldb.berkeleydb.logfilesizemb = "10"
! Max threads of database.
caldb.berkeleydb.maxthreads = "10000"
! Megabytes of shared memory.
caldb.berkeleydb.mempoolsizemb = "4"
! Time before which to purge deletelog
caldb.berkeleydb.purge.deletelog.beforetime = "86400"
! Time interval between auto purge of deletelog
caldb.berkeleydb.purge.deletelog.interval = "86400"
! If "yes", open the database in readonly mode
caldb.berkeleydb.readonly = "no"
! Email of calendar database administrator.
caldb.calmaster = "[email protected]"
! Seconds between checkpointing.
caldb.cld.cache.checkpointinterval = "60"
! Remove checkpoint files after synchronized? (yes/no)
caldb.cld.cache.circularlogging = "yes"
!service.calendarsearch.ldap.primaryownersearchfilter = "(&(|(uid=*%s*)(cn=*%s*))(objectclass=icsCalendarUser))"
! Enables ("yes") or disables ("no") cld db cache
caldb.cld.cache.enable = "yes"
! Physical path location of cache database
caldb.cld.cache.homedir.path = "/var/opt/sun/calendar/csdb/cld_cache"
! Max megabytes of checkpoint file.
caldb.cld.cache.logfilesizemb = "10"
! Max threads of database.
caldb.cld.cache.maxthreads = "1000"
! Megabytes of shared memory.
caldb.cld.cache.mempoolsizemb = "4"
! Type of Calendar Lookup Database plugin to use ("local" "algorithmic" or "directory").
caldb.cld.type = "local"
! Count data base statistics? (yes/no)
caldb.counters = "yes"
! Maximum number of calendars with counters.
caldb.counters.maxinstances = "100"
! Maximum number of backlogged requests before the server obtains a new network connection.
caldb.dwp.connthreshold = "1"
! Initial number of connections for DWP client to make to each DWP host.
caldb.dwp.initconns = "2"
! Initial number of threads for handling DWP requests.
caldb.dwp.initthreads = "2"
! Maximum number of connections allowed to a DWP server.
caldb.dwp.maxcons = "1000"
! Maximum number of threads to service HTTP requests in csdwpd.
caldb.dwp.maxthreads = "1000"
! Specifies if the server performs MD5 hash checking of all DWP requests.
caldb.dwp.md5 = "n"
! IP address of a specified DWP server.
!!caldb.dwp.server.[hostname.xyz.com].ip = "a.b.c.d"
! Port number of a specified DWP server (Algorithmic CLD only).
!!caldb.dwp.server.[hostname.xyz.com].port = "59779"
! Default DWP server (LDAP CLD only), used if user's icsDWPhost value does not exist.
!!caldb.dwp.server.default = "hostname.xyz.com"
! Stack size for DWP threads.
caldb.dwp.stacksize = "65536"
! Process alarms on the alarm queue -- that is, store them in the alarm queue when an event/todo is saved
caldb.serveralarms = "1"
! Timeout for contacting ENS. If no response, we assume ENS is not running
caldb.serveralarms.acktimeout = "30"
! Dispatch -- that is, enable alarm dispatching. When an alarm trigger time arrives send out email or ENS message.
caldb.serveralarms.dispatch = "yes"
! Enable binary alarms. Used by csnotifyd and csadmind. (default: yes)
!caldb.serveralarms.binary.enable = "yes"
! Binary alarm url. Used by csnotifyd and csadmind. (default: enp:///ics/alarm)
!caldb.serveralarms.binary.url = "enp:///ics/alarm"
! Custom alarm url. Use this to get xml or calendar mime type contents
!caldb.serveralarms.url = "enp:///ics/customalarm"
! Custom alarm url contenttype. (text/xml or text/calendar)
!caldb.serveralarms.contenttype = "text/calendar"
! Dispatch type for Calendar Server alarms ("ens" o "smtp").
caldb.serveralarms.dispatchtype = "ens"
! Initial number of threads for the Event Notification Server.
caldb.serveralarms.initthreads = "0"
! Specifies how long, in seconds, the server will continue to try reconnecting to ENS before giving up. -1 means forever.
caldb.serveralarms.maxretrytime = "-1"
! Maximum number of threads for the Event Notification Server
caldb.serveralarms.maxthreads = "10"
! Time to sleep, in seconds, after a timeout connecting to ens before making another attempt to connect to ens
caldb.serveralarms.retryinterval = "5"
! Stack frame size for Event Notification Server threads.
caldb.serveralarms.stacksize = "65536"
! Total time, in seconds, to retry connecting to ENS on startup.
caldb.serveralarms.startupretrytime = "30"
! Send alarms to this SMTP host.
caldb.smtphost = "sonlinux.bg2iop.com"
! Specifies the directory in cal/bin/config containing the localized version of the files used to format email notifications.
caldb.smtpmsgfmtdir = "en"
! Specifies the SMTP port.
caldb.smtpport = "25"
! Event reminder format file.
calmail.eventreminder.fname = "mail_eventreminder.fmt"
! Event cancellation format file.
calmail.imipeventcancel.fname = "mail_eventcancel.fmt"
! Event CANCEL NOTIFICATION message format file
calmail.imipeventcancelnotification.fname = "mail_eventcancelnotification.fmt"
calmail.imipeventcancelnotificationrecur.fname = "mail_eventcancelnotificationrecur.fmt"
! Event NOTIFICATION message format file
calmail.imipeventnotification.fname = "mail_eventnotification.fmt"
calmail.imipeventnotificationrecur.fname = "mail_eventnotificationrecur.fmt"
! Event notification format file.
calmail.imipeventpublish.fname = "mail_eventpublish.fmt"
! Event REPLY message format file
calmail.imipeventreply.fname = "mail_eventreply.fmt"
! Event REQUEST message format file
calmail.imipeventrequest.fname = "mail_eventrequest.fmt"
! Task cancellation format file.
calmail.imiptodocancel.fname = "mail_todocancel.fmt"
! Task notification format file
calmail.imiptodopublish.fname = "mail_todopublish.fmt"
! Task REPLY message format file
calmail.imiptodoreply.fname = "mail_todoreply.fmt"
! Task REQUEST Message format file
calmail.imiptodorequest.fname = "mail_todorequest.fmt"
! Task reminder format file.
calmail.todoreminder.fname = "mail_todoreminder.fmt"
! Anonymous login CALID.
calstore.anonymous.calid = "anonymous"
! Does server support only two privacy types for components - PRIVATE (acts as confidential) /PUBLIC instead of PRIVATE/CONFIDENTIAL/PUBLIC
calstore.binaryprivacy.mode = "no"
! When creating new calendar of user, whether to lowercase calendar or not
! Also, when looking up calendar, whether to lowercase or not
calstore.calendar.create.lowercase = "n"
! For a newly created calendar, set the ACL to this
calstore.calendar.default.acl = "@@o^a^r^g;@@o^c^wdeic^g;@^a^fs^g;@^c^^g;@^p^r^g"
! Definition of the "owner" acl
calstore.calendar.owner.acl = "@@o^a^rsf^g;@@o^c^wdeic^g"
! Timezone ID used when importing files.
calstore.default.timezoneID = "America/New_York"
! Whether to filtering the private/confidential events on queries to server
calstore.filterprivateevents = "yes"
! Is user's default calendar included in user's freebusy-calendar-list or not
calstore.freebusy.include.defaultcalendar = "yes"
! Can user's default calendar be removed from user's freebusy-calendar-list or not
calstore.freebusy.remove.defaultcalendar = "no"
! Maximum number attendees to be allowed in a LDAP group when expanding event. Value of 0 means expand group entirely.
calstore.group.attendee.maxsize = "0"
! Maximum number of events created by recurrence
calstore.recurrence.bound = "60"
! Is user's default calendar included in user's subscribed-calendar-list or not
calstore.subscribed.include.defaultcalendar = "yes"
! Can user's default calendar be removed from user's subscribed-calendar-list or not
calstore.subscribed.remove.defaultcalendar = "no"
! For attendee calendar lookup, when encountering string that looks like (jdoe OR jdoe:tv), treat string as a userid (uid) when looking-up in Directory.
! Value can be {uid | cn | gid | res | mailto | cap}
calstore.unqualifiedattendee.fmt1.type = "uid"
! For attendee calendar lookup, when encountering string that looks like ([email protected]) (has @ sign), treat string as a mailto address when looking-up in Directory
! Value can be {uid | cn | gid | res | mailto | cap}
calstore.unqualifiedattendee.fmt2.type = "mailto"
! For attendee calendar lookup, when encountering string that looks like (John Doe) (has space), treat string as a common name (cn) when looking-up in Directory
! Value can be {uid | cn | gid | res | cap}
calstore.unqualifiedattendee.fmt3.type = "cn"
! Maximum number of results returned from LDAP lookup from user search. Value of 0 means no limit.
calstore.userlookup.maxsize = "200"
! Is Server in Virtual Domain mode or not (this affects 5.0p2 only)
calstore.virtualdomain.mode = "n"
! Enable (y) or disable (n) Access Control plugin.
csapi.plugin.accesscontrol = "n"
! Load only the plugin specified in csapi.plugin.authentication.name? (y/n)
csapi.plugin.authentication = "n"
! Enable (y) or disable (n) Calendar Lookup Database plugins.
csapi.plugin.calendarlookup = "n"
! Specifies the name of a specific Calendar Lookup Database plugin to load. If "*", load the plugins.
csapi.plugin.calendarlookup.name = "*"
! Load only the plugin specified in csapi.plugin.database.name or if not specified, load all database plugins in alphabetical order.
csapi.plugin.database = "y"
! Only load this specific plugin if csapi.plugin.loadall is no and csapi.plugin.database is yes.
csapi.plugin.database.name = "cs_caldb_berkeley10"
! Load only the plugin specified in csapi.plugin.datatranslator.name? (y/n)
csapi.plugin.datatranslator = "y"
! Only load this specific plugin if csapi.plugin.loadall is no and csapi.plugin.data translator is yes.
csapi.plugin.datatranslator.name = "cs_datatranslatorcsv10"
! Enable (y) or disable (n) database-to-output format plugins.
csapi.plugin.dbtranslator = "y"
! If "*", then load all the database-to-output format plugins. If a library name, only load that plugin. csapi.plugin.dbtranslator must be set to "yes" to load plugin
csapi.plugin.dbtranslator.name = "*"
! Load all plugins found in the plugins directory? (y/n)
csapi.plugin.loadall = "n"
! Load only the plugin specified in csapi.plugin.userprefs.name? (y/n)
csapi.plugin.userprefs = "n"
! Load only this plugin if csapi.plugin.loadall is no and csapi.plugin.userprefs is yes.
!!csapi.plugin.userprefs.name = "plugin_name"
! Enable the RSA Cypher Encryption Family Services for SSL
!!encryption.rsa.nssslactivation = "on"
! Define the Certificate name for the RSA Cypher Encryption Family
!!encryption.rsa.nssslpersonalityssl = "SampleSSLServerCert"
! Define the location of the RSA Cypher Encryption Family token
!!encryption.rsa.nsssltoken = "internal"
! Specifies if the auto refresh feature is enabled or disbaled. (yes/no)
gse.autorefreshreplystatus = "yes"
! Specifies (in seconds) how long to wait before the server scans the schedule queue for incoming jobs.
gse.belowthresholdtimeout = "3"
! Maximum number of concurrent threads the server uses to process the schedule queue.
gse.maxthreads = "10"
! Maximum length of time the server will retry to complete a group scheduling job.
gse.retryexpiredinterval = "86400"
! Specifies (in seconds) how often the server will retry a previous failing job.
gse.retryinterval = "300"
! Maximum stack size (in bytes) of a group scheduling thread
gse.stacksize = "65535"
! global flags to control notification for invitation and cancellation.
! Enable (yes) Disable (no), default is enabled. Notification will be sent.
ine.cancellation.enable = "yes"
ine.invitation.enable = "yes"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.basedir.path = "/opt/sun"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.betamajorversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.betaminorversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.caldbtype = "local"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csinstalldir.path = "/opt/sun"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodbasedir.path = "/opt/sun/calendar"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodclassesdir.path = "/opt/sun/calendar/classes"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csproddir.path = "/opt/sun"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodjavadir.path = "???"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodlibdir.path = "/opt/sun/calendar/lib"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodtoolsdir.path = "/opt/sun/calendar/tools"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csproduicustdir.path = "/opt/sun/calendar/uicust"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.fullversion = "6.0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.majorversion = "6"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.minorversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.osarch = "i386"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.osname = "linux"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.ostype = "unix"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.osversion = "2.6.9-22.el"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.patchversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.serveruidpassword = "icsuser"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.startupafterinstall = "no"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.startupatboot = "no"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.userauthtype = "ldap"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.userprefstype = "ldap"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.version = "6.0"
! Base DN for LDAP authentication. If not specified, use local.ugldapbasedn.
local.authldapbasedn = "o=bg2iop.com, dc=bg2iop,dc=com"
! Bind credentials (password) for user specified in local.authldapbinddn.
local.authldapbindcred = "admin123"
! DN used to bind to LDAP authentication host to search for user's dn.
local.authldapbinddn = "cn=Directory Manager"

Hi Venigalla,
You can implement a federated portal network (FPN) using the SAP NetWeaver platform to share content between portals.
A federated portal network allows organizations with distributed portal installations, both SAP and non-SAP, to provide a single portal access point per user to portal information, services and applications distributed on portals in the network.
WSRP-based application sharing (FPN Mode used for for integrating content between SAP and Non SAP portals) :-
--> Content administrators on a SAP NetWeaver consumer portal can integrate WSRP portlets (i.e. iViews) from remote non-SAP portals into SAP NetWeaver Portal.
--> SAP NetWeaver developers can create WSRP compliant iViews that can be consumed in non-SAP consumer portals.
You may kindly go through the below link, should be helpful:
http://help.sap.com/saphelp_nw70/helpdata/EN/43/23fb36cad10d23e10000000a1553f7/frameset.htm
Regards,
Anagha

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

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

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?

Enqueue server and Message server in ABAP/Java dual stack

Similar Messages

Maybe you are looking for