Author: <span>kenio.carvalho</span>

IBM® WebSphere® Portal treats wpsadmin (the administrator) as any other user, just with more permissions granted. With a normal configuration, it is possible to change the wpsadmin or equivalent password through the user interface, just like any other user can manage their own password through the user interface. However, if the wpsadmin account is also used for more than just the administrator, then additional changes, outlined in other steps in this section, must be made to accommodate the change.

Perform the following steps to change the administrator password:

Note: You can also change the Administrator password, like any other user password, using an LDAP editor.

1.        Log in to WebSphere Portal as an administrator.

2.        Click your user ID and select Edit My Profile.

Your user ID is located at the upper-right of the screen.

3.        Complete the appropriate fields to change your password.

4.        Click Continue.

5.        Complete the following steps to change the information stored in the SearchAdminUser alias:

a.        Log in to the WebSphere Application Server Administrative Console.

b.        Click Security -> Global security.

c.        Under Authentication, click Java Authentication and Authorization Service -> J2C authentication data.

d.        Edit the SearchAdminUser alias.

e.        Update the user ID and/or password to match your WebSphere Portal administrator information.

Additionally, you should also change the password in the wkplc.properties file, located in the wp_profile_root/ConfigEngine/properties directory.

Verify if the password changed on the LDAP Server.

6.        Perform the following steps to update the RunAsRole, which changes the stored password:
You can change the password for the WebSphere Application Server administrator user ID using the WebSphere Portal Edit My Profile portlet, the native utilities for the user repository, such as the LDAP administration interface or the WebSphere Application Server Administrative utilities. Regardless of which option you choose, once you have updated the successfully updated the password, you must also update the RunAsRole for the PZNScheduler application.

a.        Log in to the WebSphere Application Server Administrative Console with your new password.

b.        Navigate to Applications -> Application Types -> WebSphere enterprise applications.

c.        Locate and click the pznscheduler application.

d.        Click User RunAs Roles under Detail Properties.

e.        Select RuleEventRunAsRole and then click Remove.

f.        Enter the fully distinguished name (DN) of the WebSphere Application Server Administrator in the username field and the new password in the password field.

g.        Select RuleEventRunAsRole and then click Apply to apply your changes.

h.        Click OK, save your changes, and then restart the server, using the new password.

Uncategorized

Without a special configuration step, various server applications log out from the Sametime Community server on Microsoft Windows 2008 under load

The steps bellow are from From TN 1441275

To resolve the problem perform the following steps

  1. The TCP stack in Windows 2008 has a few new features that are not yet supported by every
    hardware. The following configuration changes will set the TCP stack to work in a more “conventional” way.  To do so, type from command line:

        netsh int tcp set global autotuninglevel=disabled
        netsh int tcp set global rss=disabled
        netsh int tcp set global chimney=disabled
        netsh int tcp set global congestionprovider=none

    A reboot is needed after making this changes.

  2. For Sametime 8.5.1, set the following flag under the [Config] section of the sametime.ini file:

BREAK_CONN_ON_ZERO_BYTES_SENT=0

This setting is set automatically during install of 8.5.2 on Windows 2008.

For 8.5.0, a hotfix, LKRK-86RGNA, is available for part of the components: STCommunity, STMux, STOnlineDir, STUserStorage.  Open a service request with IBM Support to determine if this hotfix is applicable for your environment if you are not able to upgrade to 8.5.1 or later.

Uncategorized

The scriptable setup option uses a setting in the notes.ini file to provide information to the client setup wizard. During installation, the wizard displays only the panels that users need to set up the Notes client.

See more information on this TechNote

Uncategorized

When my laptop sleep Sametime doesn’t auto-reconnect.

The  following flag needs to be added to the plugin_customization.ini:

com.ibm.collaboration.realtime.community/forceLoginTokenRefresh=false

Uncategorized

You can read about de announcement here

Uncategorized

Websphere Portal 8 was launched and the downloads will be available on Friday .

See the what´s new in this link

Uncategorized

This is a big projet here. Last week we start the setup of servers on top of zLinux.

The machine is big a new Dinosaur z196 . Very fast.

Image:Installing WebSphere Portal on zLinux - Machine z196

mainframe z196 websphere portal

The Repair Calendar feature fixes issues with repeating calendar entries. This functionality only works if the user is running an 8.5 Notes client and the user’s mail database is based on the mail85.ntf template from Notes 8.5.

What is the Repair Calendar feature?

The Repair Calendar feature has been provided to help customers fix issues they encounter with repeating calendar entries such as meetings.

Specifically, this feature in Notes 8.5 fixes issues where duplicate repeating calendar entries exist in the mail file.

Please note that this functionality works only if the user is running an 8.5 Notes client AND the user’s mail database is based on the mail85.ntf template from Notes 8.5.

For more information see the TN 1326680

Uncategorized

Very interesting articles of two friends who work at IBM support

Uncategorized

If you want to know more about the recent contacts

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/ibm-lotus-notes-8-recent-contacts-and-type-ahead-features-faqs

Uncategorized