Category: <span>Uncategorized</span>

Good TN i found today on the LNKB

How To Speed Up WebSphere Portal Server 7 After the Initial Installation

When any version of WebSphere Portal is first installed, there is always a significant load time for each JSP page.   The poor load time is attributed to the fact that each JSP page must be compiled the first time it is accessed.  To avoid the delay, execute the precompile-jsp command.

1. Open a command line and navigate to the following directory:

C:IBMWebSpherewp_profilebin

2. Execute the following command (all on one line)

ConfigEngine.bat precompile-jsp –DwasUser=wasadmin –DWasPassword=wasadmin

When you have a portal for a long time (My case since 6.0.0.1) you apply a list of Fix during the life of your portal.
The directory version grows and you need to clean up to free disk space,

I open a PMR and the answer was:

“It is critical that the client does not remove the jar files from the   
backup folder.  This folder is very important if you decide to uninstall
a fix/fixpack or upgrade to a new fixpack.  If you install a fix, say   
PM0001 and it affects the portal.jar file.  What happens is that the    
original portal.jar file is stored in the backup folder and the new     
portal.jar is deployed.                                                 
                                                                        
So if we have a scenario where the client wants to upgrade to the latest
fixpack and their current Portal has several fixes applied.. when you go
to upgrade, part of the install process is to uninstall those fixes     
(thus those jar files that each fix affects are removed and replaced    
with the associated backed-up jar files in the backup folder).  You will
break Portal and it will be very painful to recover.                    
                                                                        
The logs folder can be emptied.”

You can use a compact command successfully with wildcards or without specifying databases on all databases in the Data folder and sub-folders but you can’t do this for templates. This prevents templates being compacted every time you issue a generic compact command. You can also run a batch command if multiple templates must be compacted.

Another workaround is to create a notepad document which lists all of the templates listed one template name per line as shown below:

This notepad document would need to be saved as file type ‘ All Files ‘ with the extension  of ‘ .ind ‘ such as ‘ templates.ind ‘ and placed in the Domino Data folder .
This file can then be specified to run compact -c against as in the following command ‘ load compact -c templates.ind ‘

I found today this paper and i think it can help new administrators or for someone start learning Domino admin.

This pdf is a preview. If you want the full version go to this link

Go to the link on the top and click

You will see a window like this

When Domino will have this feature?

I have 3 Domino Servers installed on top of Linux.
Eight months without logon as a root.   After 15 days of vacation and then i forgot the password 🙂

This link  show how to reset the root password

Today me and some colleagues saw the OGS using the internet.
Good image and sound

Some new features was addet to calendar profile.   After convert some users from 7.0.4 to 8.5.2 some problems arrived.

I deleted the profile using the LotusScript  and instruct the user to recreate the profile.

Just put the code bellow in a button and send to the user.

Sub Click(Source as Button)
Dim session As New NotesSession
Dim db As NotesDatabase
Dim doc As NotesDocument
Set db=session.CurrentDatabase
Set doc=db.GetProfileDocument(“CalendarProfile”)
Call doc.remove(True)
If doc Is Nothing Then
MsgBox “Profile Document Was Successfully Removed”
Else
MsgBox “Profile Document WAS NOT Removed”,48
End if
End Sub