Free tool to collect performance information on servers AIX / Linux.
See this link
MySphere Posts
This type of question i answered a several times.
The solution posted here is only one of the several solutions and depends on the architecture and servers on your deployment.
How can you implement LDAP failover for IBM WebSphere Portal version 6.1, 6.1.5, and 7 so that a replica LDAP server can be leveraged for cases in which your primary LDAP server is unavailable?
TN 1282720
Use the following steps for cases in which you configure security to a standalone LDAP:
1. Perform the WebSphere Application Server configuration steps by referencing the topic, Configuring multiple LDAP servers for user registry failover.
In addition to following the steps documented in the above link, you must follow the steps below to ensure that the Virtual Member Manager (VMM) component used by WebSphere Portal is aware of the replica LDAP servers.
2. Open the wimconfig.xml file.
For a stand-alone portal, use
For a portal cluster, use
3. Search for the following line:
4. Add the failover LDAP entry under the line in Step 3:
5. Disable connection pooling with the following setting: connectionPool="false"
6. Save the changes and restart the servers.
Use the following steps for cases in which you configure security to a federated LDAP:
1. Log into the Deployment Manager or the WebSphere Administration Console.
2. Navigate to Secure administration, applications, and infrastructure --> Federated repositories --> Manage repositories --> repository name.
3. Find the following line:
Failover server used when primary is not available
4. Add your hostname and port for the failover server.
5. Confirm the connectionPool is set to false in the wimconfig.xml file.
For a stand-alone portal, use
For a portal cluster, use
6. Save the changes and restart all servers.
From developerworks…
For any database, the first step to accessing data is making a connection from the client to the server. You may need to establish connections from clients to your IBM® DB2® Universal Database™ server across a wide area network or from the Web. If you have many connections coming in, with the potential for overloading your network or server at peak times, you may be looking at implementing a load balancing solution to spread requests across multiple servers. The flexibility of routing these connections by using facilities outside of DB2 has many potential applications.
This article discusses one method of routing TCP/IP DB2 connections using an open source TCP proxy utility called Balance.
See the complete article on developerworks
If you want to know wich properties the replace or refresh design of a database can be change you need to see this TN
A customer would like to set “No Letterhead” and prevent changes for all users using policies but it not work.
I found a SPR LMAN6H6HB7 and the workaround is:
the "No letterhead" setting does go into effect correctly if it's changed to 'set value when modified' and changed back to 'set value and prevent changes.
1- go to the Policy Settings document and edit it
2- change from " Set Value and prevent changes" to "Set value whenever modified" , save & Close
3- Control&Shift&F9 to refresh the views
4- Go back to the Policy setting and edit the document, Set this time back to " Set Value and prevent changes"
5- Push the policy now to users, " tell adminp process mail"
6- Restart notes client, authenticate with server and check letterhead
and it works 🙂
Starting a review of Domino environment today.
Our goal is to reduce the size of databases and enable DAOS.
I start converting all the databases (test server) to ODS 51. To covert i use the command load compact -c -v -n.
The switch -c is copy style, -v enables the “Compress document data” database property and -n enables “Compress database design”.
The next step used was load compact -c -ZU to upgrade attachments to LZ1 compression from Huffman compression.
Using this two steps we save 63% of disk space in one database. DAOS is not enabled yet.
The resut is from :
to:
I am honored to have been chosen as one of 50 World Champions of IBM Collaboration Solutions
Thanks to IBM for recognition and congratulations to all nominated.
The list is here http://www.ibm.com/developerworks/lotus/champions/
From TN 1182264
This behavior can occur if you have not set the “Enforce server access setting” field to Yes. The default value is No, which does not apply the “Not Access Server” information to Web (HTTP) traffic. You must set this field to Yes to have the HTTP task honor the settings on the Security tab.
The “Enforce server access setting” field is in the Server document on the Ports -> Internet Ports -> Web tab. After changing the value to Yes, restart the HTTP task to apply the changes. In one particular case, the changes did not take effect with restarting the HTTP task, so the customer restarted the server.
Today i finished the setup of Sametime for a client in my city. The MS AD administrator asked about how to prevent users from loggin in based on a Group.
Sametime doesn’t have this kind of police. If you use the TN 1166845 the solution is to add a new attribute for every user. :-(.
This workaround doesn’t meet our requirements (restricting using groups). I change the LDAP search filter in stconfig.nsf from;
Search filter for resolving person names: (&(objectclass=organizationalPerson)(|(cn=%s*)(givenname=%s*)
(sn=%s*)(mail=%s*)))
Search filter to use when resolving a user name to a distinguished name: (&(objectclass=organizationalPerson)(|(cn=%s)(givenname=%s)
(sn=%s)(mail=%s)))
To:
Search filter for resolving person names: (&(objectclass=organizationalPerson)(memberOf=CN=GroupName,OU=OUName,DC=domain,DC=com,DC=br)(|(cn=%s*)(givenname=%s*)
(sn=%s*)(mail=%s*)))
Search filter to use when resolving a user name to a distinguished name: (&(objectclass=organizationalPerson)(memberOf=CN=GroupName,OU=OUName,DC=domain,DC=com,DC=br)(|(cn=%s)(givenname=%s)
(sn=%s)(mail=%s)))
Reboot the Sametime and it will work.
Yesterday i started installing the Sametime 8.5.x for 1200 users. The client will use virtually all the capabilities, audio, video, integration with Outlook and mobile clients.