Category: <span>Uncategorized</span>

O Sametime 8.5 estará dispnível em 22 de Dezembro segundo a IBM. A carta de anúncio está neste link

Sametime version 8.5 will be launched on 22 December.

I was “synchronizing” two clustered Domino Servers. I opened a PMR about  the trash folder is different on two replicas.  The answer:

When you create a new replica with soft deletions enabled, the soft deletions are not being carried over to the new replica.

Notes and Domino are working as designed. An enhancement request to include this functionality has been submitted to Quality Engineering; however, there are no current plans to implement this functionality.

Workaround used in one case to synchronize the trash folder.

Once that the new replica is being created, if new documents are deleted and sent to the trash folder, these new document do correctly replicate between the replicas and you can see them on the trash folder to the two replicas.

In one occasion this steps helped to synchronize the trash folder of the two replicas:

– Restored the document/s that are present on the trash folder on one of the replicas, therefore you can see the document/s on the Inbox of the database

– Replicate the two databases, the document/s are now present on the Inbox of the 2 replicas.

– Delete the document/s again from one of the replicas.

– Replicate again and now you can see the Trash folder synchronized in the two replicas containing the same number of documents

* If you only do the following, restore the document /s on the database where you have the documents in the trash folder ( you can see the document in the Inbox or this database) and delete them again, so the documents come back to the trash folder, and then you replicate, the trash folder does not get synchronized.

Today i have a issue with thow clustered mail servers. Some databases are different and one server goes down. Some users complain about deletion documents still on their mail databases. I found the cause. I don’t know why yet, but replica setings was not the default settings (like the figure bellow) and deletions doesn’t replicate.

Hoje eu tive um problema com dois servidores clusterizados de correio. Algumas bases estavam diferentes e um dos servidores caiu. Alguns usuários reclamaram que emails antigos ainda estavam nas suas bases. Achei a causa mas não sei porquê estava assim. As definições de replcia estavam marcadas para não replicar deleções.

I have a lot of mail databases and then i use the agent bellow to make sure all databases has the same configuration as the screen above.

Como eu tenho muitas bases eu usei o agente abaixo para verificar as configurações.

Sub Initialize
        Dim db As NotesDatabase
        Dim ses As New NotesSession
        Dim doc As NotesDocument
        Dim dbdir As NotesDbDirectory
        Dim maildb As NotesDatabase
        Dim server As String
        Dim subdir As String
        Dim rep As NotesReplication
        Dim i As integer
        server = InputBox (“Nome do Servidor) (Enter para Local)”)
        subdir = InputBox (“Em qual subdiretório o agente deve procurar as bases? ( Enter para todos os diretórios) “)
        If subdir <> “” Then subdir=subdir & “”
        Set db = ses.CurrentDatabase
        Set dbdir = ses.GetDbDirectory(server)        
        Set maildb = dbdir.GetFirstDatabase(DATABASE)
        i = 0
        While Not (maildb Is Nothing)        
                If InStr(1,maildb.FilePath,subdir,5)<>0 Then
                       
                        Call maildb.Open(“”,“”)
                        If maildb.IsOpen Then
                                Set rep = maildb.ReplicationInfo
                                If  rep.IgnoreDeletes Then
                                                                  rep.IgnoreDeletes = False
                                                                   i = i + 1
                                                                End If
                                                        Call rep.Save()
                        End If
                End If
                Set maildb = dbdir.getnextdatabase
        Wend
        MsgBox (“Foi (ram) modificado (s)  “+ CStr(i) +” banco(s) de dados!” )
End Sub

Acesso ao correio particular usando o Notes não é muito comum mas pode ser necessário. A configuração é simples, basta criar uma conta POP3 e SMTP e pronto. Mas e se você desejar que o correio recebido do seu email particular seja colocado em uma pasta? Regras?
Regras não funcionam em replicas locais. A solução encontrada foi até simples: Faça um encaminhamento da mensagem no seu email particular para seu endereço no Domino e crie uma regra para mover as mensagens do email particular para a pasta desejada

Access to private mail using Notes is not very common but may be necessary. Setup is simple, just create a POP3 and SMTP and ready. But what if you want the incoming mail from your private email is placed in a folder? Rules? Rules do not work on local replicas. The solution was to simple: Make a forwarding of the message on your private email address to the Domino and create a rule to move email messages to a desired folder

If you forget your WebSphere Application Server administrator’s password and/or your WebSphere Portal administrator’s password, and your administrative users are stored in the file registry, how can you reset the forgotten password in the file registry? You can use this TN and solve the problem.

Se você esquecer a senha no WebSphere Portal 6.1 o procedimento neste TN resolve o problema. Válido apenas para o Portal 6.1

The new version will be launched on 25/11/2009. See the details here

This technote covers a new feature being made available in Notes/Domino 8.5.1 which takes further advantage of the Domino Attachment and Object Service (DAOS), first introduced in Domino 8.5.

Users want to configure their Notes 8.0.x and 8.5x (standard configuration) client to automatically log on to a Lotus Sametime server using the Domino SSO (Single Sign On) feature. However, the option  “Automatically log-in” only becomes available when selecting “Remember password”.

The TN1321569  explain how to setup this configuration.

Domino does not have a code to notify administrators when users are deleted from names.nsf i need to know who deleted the user.
 To solve this problem i wrote an agent to do the job.  
Just put the code on database script inside the QueryDocumentDelete.

Sub Querydocumentdelete(Source As Notesuidatabase, Continue As Variant)
        Dim docMemo As NotesDocument
        Dim docsDelete As NotesDocumentCollection
        Dim ses As New NotesSession
        Dim db As NotesDatabase
        Set db = ses.currentdatabase
        Set docMemo = New NotesDocument(db)
        Set docsDelete = Source.Documents ‘ Selected documents
        For x = 1 To docsDelete.count
                Set doc = docsDelete.GetNthDocument( x )
                If doc.form=”Person” Then
                docMemo.Form=”memo”
                docMemo.SendTo = “Administrator/Acmel”
                docMemo.subject = “Document delection”
                Set rtbody = New NotesRichTextItem (docMemo, “Body”)        
                Call rtbody.AppendText  (“Deleted by ” + ses.UserName + ” – “+ Cstr(doc.StartDateTime(0)) + ” – ” + doc.Subject(0) +” – User Name = ” + doc.FullName(0))
                Call docMemo.Send(False)
      End if
        Next
       
End Sub