: 4400 | 106119 | 11884
|
: 1 : 5 : 4 |
If you create a new database with replicas on other locations servers, and publish the new database by sending a doclink to the users at the same day, the doc/database link will always try to open the replica on the server the doclink was created from. This is because at this time does not yet exist database catalog entries for that new database. For that reason, the notes clients are not able to locate the "best" replica from the database catalog, and will try to open the new database from the "server hint" in the link which in many (most?) cases is not desired.
Solution: In addition to the usual nightly scheduled run, catalog task should also be resident in memory. This way, the catalog task could intercept database creation/deletion events, and (almost) immediately create/remove database catalog entries for the newly created database replica in the local catalog (or perhaps via AdminP).
Because now the catalog entries exist everywhere almost immediately after creation, db/doclinks sent at the same day always would open the "best" replica for a Notes client regardless of its location.
|
1) Bruce Lill6677 (23 Oct 2009)
Thats why as an Admin, I always plan ahead. Emails get sent after the environment is configured.
I launch the catalog task on each server to force an update early if needed.
Running in real time would have an impact on performance while only giving marginal improvement in functionality.
I launch the catalog task on each server to force an update early if needed.
Running in real time would have an impact on performance while only giving marginal improvement in functionality.
2) Dietmar Dumke907 (23 Oct 2009)
Launching catalog task on each replica server just to add a single new database to the catalogs is not only boring admin work but also has an unnecessary load overhead on the servers, especially on servers with many databases.
"Plan ahead" means being forced to unnecessarily split a single task into 2 tasks, to be processed at different days. Day 1: Initiate replica creation, set a reminder for the next day. Day 2: Send a link message to the users notifying them.
I want to create replicas and then almost immediately send notifications to users. Not one day later, or - if almost immediately but after forcing catalog to run - for the cost of unnecessary server load.
The in-memory catalog task would hook into database creation events only, nothing else. That should not - if at all - impact performance so much.
"Plan ahead" means being forced to unnecessarily split a single task into 2 tasks, to be processed at different days. Day 1: Initiate replica creation, set a reminder for the next day. Day 2: Send a link message to the users notifying them.
I want to create replicas and then almost immediately send notifications to users. Not one day later, or - if almost immediately but after forcing catalog to run - for the cost of unnecessary server load.
The in-memory catalog task would hook into database creation events only, nothing else. That should not - if at all - impact performance so much.
3) Ralph Borcherds542 (14 Jan 2011)
In large installations this is not a possible. Way to much overhead and replication.
Welcome to IdeaJam™
You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.
Use IdeaJam to:
- Collect ideas from employees
- Solicit feedback and suggestions from employees and customers
- Run innovation contests and competitions
- Validate concepts
- Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top
IdeaJam™ works with:
- IBM Connections
- IBM Lotus Quickr
- Blogs and Wikis
- Websphere Portal
- Microsoft Sharepoint
- and other applications.
IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.
Learn more about IdeaJam >>
IdeaJam developed by
