It is a common task on every WebSphere Portal setup.
Redirect the root “/” of the IBM HTTP Server to the context of WebSphere Portal ( /wps/portal)
Put the bellow lines on the httpd.conf and restart the IBM HTTP Server before the line of the WebSphere Plugin.
RewriteEngine on
RewriteCond %{HTTP_HOST} sample.com.br [NC]
RewriteCond %{REQUEST_URI} ^/$
Rewriterule ^(.*)$ http://portal.sample.com.br/wps/portal [L,R=301]
This video show how to setup IBM Worklight Studio
Learn how to configure and use the IBM Directory Change analyzer, which scans the Server Document and Configuration document in a Domino Directory, and reports what had changed, and who made the change, with timestamps.
More information here
Information is circulating describing a method called “Heartbleed,” which exploits a vulnerability caused by a design error in OpenSSL. This technote provides confirmation that IBM Notes and Domino are not susceptible to the Heartbleed attack
For more information see this TN from IBM
Yesterday i was updating a portal V8.0.0.1 CF5 to CF10 and the CF10 failed.
I restore the full backup of the file system but i got the following :
Erro durante a fase “configurar pós-instalação”:
Excluindo arquivos de C:IBMWebSpherePortalServerwcmprereq.wcm
Falha ao excluir C:IBMWebSpherePortalServerwcmprereq.wcmwcmsharedappilwwcm-api-impl.jar
java.lang.Exception: ConfigTask CONFIG-WP-PTF-CF failed.
CRIMA1020E: Falha ao extrair zip prereq.wcm 8.0.1.201304260218. O arquivo C:IBMWebSpherePortalServerwcmprereq.wcmwcmsharedappilwwcm-api-impl.jar já existe.
java.lang.Exception: ConfigTask UNCONFIG-WP-PTF-CF failed.
I found that some things was left on the ProgramData.
Solution: Restore the ProgramData folder and run the CF10 setup again.
Yesterday i was on a customer site and all Portal Servers are installed on Windows Servers. The language settings are set using policies and the logs are in Brazilian Portuguese. Too bad for troubleshooting.
So i change the language to English using the following:
Append the following to the existing value for the property “Generic JVM arguments”: -Duser.language=xx -Duser.region=YY
where xx and YY values are dependent upon the desired language.
For English US the values are bellow
-Duser.language=en -Duser.region=US
ATLUG’s Day of Champions event is being held on Monday April 7 in Atlanta. Registrations are now open for an event that provides the unique opportunity to attend 26 separate presentations in a single stream all on the one day. That’s right, 26 separate presentations from a wide range of experts, almost all of whom are from the local Atlanta region.
The Purge Interval Replication settings stop expired documents from replicating back into databases
The Purge Interval Replication Controle ( PIRC ) is set on a database, to prevent expired documents or deletions to replicate back into that database from a different replica
It will not stop new documents or new deletions from replicating to that replica.
– If Pirc is disabled on a replica, then expired documents and deletions will replicate to that replica.
New documents and new deletions will always replicate – Pirc does not interfere with new documents
PIRC is set in the Notes client : File > Replication > Options for this Application > Space Savers.
There are 6 different scenario’s possible :
1- Push ( sent ) from a PIRC enabled to a Pirc enabled database replica
2.- Pull ( receive ) from a PIRC enabled to a Pirc enabled database replica
3.- Push ( sent ) from a PIRC enabled to a Pirc disabled database replica
4.- Push ( sent ) from a PIRC disabled to a Pirc enabled database replica
5.- Pull ( receive ) from a PIRC disabled to a Pirc enabled database replica
6.- Pull ( receive ) from a PIRC enabled to a Pirc disabled database replica
What will the result be in the different scenario’s above ?
Expired documents and deletions will NOT replicate in scenarios 1. 2, 4 and 5. Pirc stops them because Pirc is Enabled on the destination.
Expired documents and deletions will replicate in scenarios 3 and 6
So only in the case where the destination of the replication does not have PIRC enabled, the replication will pull in expired documents and deletions.
This happens even if the source replica has PIRC enabled.
I found the information above on a draft TN when i was searching information about PIRC
EditLive9 for Portal is available as a fix 8.0.0.1-WCM-IFPI11933-CF10
Download it here
The Lotus Domino server is designed to execute agents that exist in the same database sequentially, with only one agent running at a time. The Agent Manager task has a built-in scheduler that, for optimization reasons, runs only scheduled agents that exist in the same database with the same agent start time as sequential.
You need to run multiple agents at the same time or outside of the frequency of the Agent Manager’s schedule.
Create a Program document, and fill out the following fields on the form as shown:
Program Name: nserver (or server if not Windows platform)
Command Line: -c “tell amgr run ‘database.nsf‘ ‘agent‘”
Substitute your database name and agent name. The correct use of quotation marks ( ” ) and apostrophe ( ‘ ) is important.
When Domino runs the agent this way, a separate thread is created to process the agent. This separate thread allows it to run while other agents are being processed through the Agent Manager task.
Caveats
There are a number of serious issues you should be aware of if you plan to use such a process.
Because the agent is spawned in a separate thread, the Agent Manager task is unable to access this agent once it is running. This means that you cannot stop the agent once it is running.
A large number of agents running on the same database at the same time can have potential performance issues.
Your agent must be coded to anticipate other agents working on the same data. For example, having one agent write to a document while the other agent is reading could have unexpected results. You might need document locking logic in the agent.
The information above is from this TechNote