The TN contains pre-install information as well as specific steps and configuration changes for setting up the Domino 8 server and Sametime server for people awareness and instant messaging functionality in Domino Web Access (iNotes Web Access) 8.x.
See the full TN
From developerworks
Linux® continues to innovate in the area of file systems. It supports the largest variety of file systems of any operating system. It also provides cutting-edge file system technology. Two new file systems that are making their way into Linux include the NiLFS(2) log-structured file system and the exofs object-based storage system. Discover the purpose behind these two new file systems and the advantages that they bring.
See the full article here
From Notes Help
To set up DOLS on clustered servers
Before using DOLS on a clustered Domino 6 server, make sure that:
How to configure ICM
You configure the ICM by making entries in the Internet Cluster Manager section of the Server document. You can also set up a separate IP address for the ICM. You can then start the ICM.
You can configure the ICM settings on one server and have more than one ICM access these settings. This lets ICMs on different servers share a common configuration. You should include the ICM configuration information on every Web server in the cluster, not just the server on which you run the ICM. You do this because each Web server uses its own Server document to determine how to generate URLs that refer to the ICM. The Web server obtains the host name of the ICM from the Server document. The Web server then uses that host name to generate URLs that reference the ICM.
To configure the ICM
1. From the Domino Administrator or the Web Administrator, click the Configuration tab.
2. In the Tasks pane, expand Server and click All Server Documents.
3. Do one of the following:
4. Click the Server Tasks – Internet Cluster Manager tab.
5. Complete the following fields:
| Section | Field name | Description |
| Basics | Cluster name | The name of the cluster the ICM will service. If this field is blank, which is the default, Domino uses the name of the cluster that contains this server. |
| ICM Notes port | The name of the Domino port the ICM will use to communicate with HTTP clients. If this field is blank, which is the default, the ICM can use any Domino TCP/IP port to communicate with HTTP clients. Enter a port name only if you want to restrict ICM communication to one specific port. | |
| ICM SSL keyfile | The name of the SSL key file that contains certificates to identify the ICM when communicating with HTTP clients. If this field is blank, the ICM uses the key file specified on the Ports – Internet Ports tab of the Server document. | |
| Allow users to browse databases in the cluster over HTTP | Lets HTTP clients view a list of the databases in a cluster.
When you enable this field, users can enter http://icmhostname/?OpenServer as the URL to access. Entering this URL displays a list of databases on the servers in the cluster associated with the ICM named in icmhostname. | |
| Configuration | Get configuration from | Lets you specify a different Server document from which to get configuration information. This field lets multiple ICMs share the same configuration. |
| Obtain ICM configuration from | This field appears when you select “another server document” in the field “Get configuration from.” Enter the name of the server whose Server document contains the configuration you want to use. | |
| ICM hostname | The fully qualified name of the host that clients should use to communicate with the ICM. This can be the registered DNS name or the IP address.
The Domino Web server uses this field to create URLs that reference the ICM. If this field is blank, the Web server will not be able to generate URLs that refer to the ICM. | |
| ICM HTTP Port Settings | TCP/IP port number | Enter the port number for the ICM to use.
If you are running the ICM on the same server as the Web server, you must avoid address and port conflicts. If you do not give the ICM its own IP address, be sure the port number the ICM uses is different from any of the other port numbers you use on the server. |
| TCP/IP port status | To enable HTTP communication with the ICM, choose enabled. To disable HTTP communication with the ICM, choose Disabled. | |
| SSL port number | Enter the port number to use for SSL.
If you are running the ICM on the same server as the Web server and you do not give the ICM its own IP address, be sure the SSL port number is different from any of the other port numbers you use on the server. | |
| SSL port status | To enable HTTPS communication with the ICM, choose enabled. To disable HTTPS communication with the ICM, choose Disabled. |
6. Click save & Close to save the Server document.
When the ICM starts, it looks at the Server document on the server on which it is running to find the ICM cluster name and its network address. It then obtains the host name and port settings from the same Server document or from the Server document specified in the field “Obtain ICM configuration from.”
If you run the ICM on the same system as a Domino Web server, you must avoid IP address or port number conflicts. The best approach is to assign the ICM its own IP address. You can also have the ICM share an IP address with the Web server if you specify different port numbers for the ICM and the other protocols on the Web server.
From TN 1385425:
Certain diagnostic NOTES.INI settings related to dbdirman can cause an undercount of DAOS references during resync. Undercounting can lead to premature deletion of attachments from the DAOS repository during prune operations.
DAOS resync scans all .NSF files on the Domino server and counts the number of references to each .NLO file in the DAOS repository. If any of the following NOTES.INI parameters are enabled, dbdirman can provide an incomplete list of .NSF files to the resync process. If an .NSF file containing DAOS references is not scanned, the reference count for the associated .NLO files will be too low, or zero. A subsequent prune operation will delete these .NLO files when the reference count reaches zero, even though there are actually references to them in the .NSF files that were not scanned. (Unless the prune operation is run manually with a different argument, deletions will occur in accordance with the DAOS deferred deletion interval.)
To correct this problem, if any of the following settings are enabled in a DAOS-enabled Domino server’s NOTES.INI file, remove them immediately, and then shut down the Domino server and all related processes. The shut-down ensures that shared memory structures are flushed, so they will be re-created without the settings on restart. After the restart, issue a ‘tell daosmgr resync force’ command to re-count all of the references.
DEBUG_DISABLE_DIRMAN_REFRESH
DEBUG_DISABLE_REFRESH_CACHE_FROM_DISK
DEBUG_DISABLE_CACHE_DB_UPDATES
DEBUG_DISABLE_UPDATE_CACHE_DB
DEBUG_DISABLE_DIRECTORY_CACHE
This affects only 8.5.0. Fix PMAO7RSQCT (included in 8.5.0 FP1, and in 8.5.1) will check for all of these flags. If any are found to be enabled, it will print a warning message about them, and prevent the resync operation from running to avoid putting the DAOS catalog in a false ‘Synchronized’ state.
The file name roamingdata.nsf is reserved, do not create a Notes database named roamingdata.nsf, according the TN 1403641
The text bellow is from TN 1391477
When running a Lotus Domino 32-Bit server on Microsoft Windows 64-Bit, you notice a high memory allocation. This results in poor system performance and the server being low on physical memory. This is a result of a change Microsoft has made to their API SetSystemFilecache()…..
Quando instalar Domino 32 Bits em um servidor MS 64 Bits melhor dar uma olhada no TechNote para não ter surpresas de performance.
This White Paper explains how to write code in java for Domino Applications. It is beginner level. Java is getting more importance in our Domino world.
See the Withe Paper here
Este White Paper explica como escrever código Java em aplicações Domino. É de nÃvel inicial e mostra um paralelo entre o Lotusscript e Java.
Achei a publicação importante devido ao fato de que já na versão 8.5.1 temos classes Front End para usar em Java.
Lotus Domino 8.5.1 Administrator Help Errata
Some information in the Domino Administrator 8.5.1 Help is wrong see this TN
The following notes.ini file variables are now obsolete in Notes/Domino 8.x:
Obsolete variables as of Notes/Domino 8.0:
| ADMINUSEPROCESSES |
| BypassNewTotaling |
| CLUSTER_NAME_CACHE_SIZE |
| DEBUG_CONSOLETOSCRAP |
| DEBUG_DB2_QV_ENABLE_HTTP |
| DEBUG_DISABLE_JIT_SUPPORT |
| DEBUG_DISABLE_LARGE_FILE_SUPPORT |
| DEBUG_ENABLE_ODS42 |
| DEBUG_LOGGER_BUF_FULL_MIN_WAIT |
| DEBUG_NAMELOOKUP_MISSES |
| DEBUG_NAMELOOKUP_NOHITS_NOERRORS |
| DEBUG_NLCGTRACE_TEARDOWN |
| DEBUG_NONQUINCY_DEBUGGER |
| DEBUG_SCR_ENABLED |
| DEBUG_SECURE_ALLOW_2048 |
| DEBUGGING_NLMS |
| DEDICATED |
| DONT_CACHE_MONITOR_FORMULAS |
| DWSAddinMaxThreads |
| EVENT_SETUP_LEVEL_CLEAN_MESSAGES |
| FT_SUMM_DEFAULT_LANGUAGE |
| FT_SUMMARY_SIZE |
| HTTPDomWSForceFromValue |
| HTTPNoDomWSAppSpace |
| LSMODULE_TRACE |
| MACR6StatusBar |
| MAPI_602PSTFILE |
| MCC_DefaultLang |
| MEMORY_LOW_CUSHION |
| POLICY_USE_POLLASTMOD |
| PREEMPTIONTIMER |
| SEG_PER_FIXED_ALLOC |
| ServerRequiredFileHandles |
| SESSIONKEY_CHECK_FILE |
| SKIP_FIXUP |
| WINCON_GEOMETRY |
Obsolete variables as of Notes/Domino 8.0.1:
| ABSort |
| CALLWS_DUMPHEAP |
| DEBUG_CA_SERVER |
| DEBUG_CHECK_ABSTRACT_LENGTH |
| DEBUG_LS_MEMORY_DUMP |
| DEBUG_LS_MEMORY_DUMP_OUTFILE |
| DEBUG_SIMULATE_UNDO_LEAK |
| ENABLE_ON_DEMAND_COLLATIONS |
| EnableRTFMergedCells |
| WSINVOKE_DEBUG |
Fazer análise de performance de qualquer software é um grande desafio. Hoje estou trabalhando com um time investigando problemas com IHS.
Este link tem uma documentação que ajuda muito a coletar informações sobre performance do IHS que é a porta de entrada para o WebSphere