Category: <span>Uncategorized</span>

Lotus Notes Traveler customers are NOT recommended to upgrade to Domino 8.5.2.3 and later releases until they have applied APAR LO62635 to the Traveler server.

Domino server 8.5.2.3 (Fix Pack 3) changed one of the API calls that Lotus Traveler server uses.  Running Domino 8.5.2.3 and Lotus Traveler 8.5.2.x without LO62635 can cause a server crash scenario.  Once LO62635 is installed on the server, the Domino server can be at any 8.5.2.*  level.

WORKAROUND:

Until the Traveler APAR LO62635 fix is available, Administrators may uninstall Domino Server Fix Pack 3 and install Fix Pack 2 instead.

The information above is from TN 1507380

At the beginning of a portal project is very important to setup a good  user repository schema  and choose the configuration that best fits.

If you are new to WebSphere Portal you need to read this article and this topic on the wiki

This is my NSF Knife 🙂
I like to cook. I noticed this brand in my 8 inches knife.

Today several people at Plansis got IBM Certifications.  

Congratulations to our new Certified Professionals and good vacation for me 🙂

Free tool to collect performance information on servers AIX / Linux.

See this link

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 /config/cells//wim/config/wimconfig.xml.
For a portal cluster, use /config/cells//wim/config/wimconfig.xml

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 /config/cells//wim/config/wimconfig.xml.
For a portal cluster, use /config/cells//wim/config/wimconfig.xml

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