This content has been marked as final. Show 9 replies
try restarting the server and see if that helps
First off can you explain what "Server Hardening is all about"?
Secondly, this looks like the JGroups isn't starting up correctly. Have you locked (shutdown) ports which applications can't use? You can modify the setup of JGroups by exporting the global workspace settings via the AdminUI.
1. Go to: http://localhost:8080/adminui
3. Select "Services"
4. Select "LiveCycle Workspace ES"
5. Select "Global Administration"
6. Under Export global settings, click "Export".
7. Save the settings locally.
You might have to modify the JChannelConnectionProperties value to fit your environment.
After making modifications to this re-import the settings via the "Import global settings" import.
Hope that helps.
What exactly is JGroups? How should we know what the settings need to be?
JGroups is an open source project that allows processes to send messages to one another. LiveCycle data services uses it for its messaging implementation (basically it configures the server to multicast messages to all the listening clients...even in a clustered environment across different LAN/WAN).
In most cases the default configuration will work fine, the problem is that if you are running a firewall on the server (or your local machine...i.e. windows firewall) the ports that JGroups uses for its communications can be blocked. In a local environment its easy enough to disable windows firewall and bounce your server to get things working.
In a production environment you need to open the ports that JGroups is using. These settings are in the Global Administration settings (as mentioned by WorkspaceUser above). If you export it and look at the JChannelConnectionProperties you'll see the ports its using and you can set your firewall to allow communication to those ports.
What about the mcast_addr? Should that be my machine's IP address?
No you don't need that to be set to your IP. The bind_addr will be set at runtime to your IP address. The mcast_addr is set to the correct reserved range for your OS (I think 224 on Unix and maybe 235 on Windows...guessing there, not 100% sure).
Same problem here(with the turn key install, just beginning to work with livecycle).
Did you found the answer?
What should we exactly change in the settings file to make the automatic refresh of the todo-list work?
There are also know issues with FireFox 3.x.
Probably not the problem, but related for anyone searching: my To Do list does not get updated for groups that are part of an enterprise domain. I was told this is a known issue as well and slated to be fixed in the next SP. I created a local group with the enterprise group as a member and that works.