Good video on How to connect WAS7 with JDBC TO MySql 5.5
Category: <span>Uncategorized</span>
| When troubleshooting a Notes client problem, a troubleshooting technique consists of performing a clean reinstall of the Notes client. A clean reinstall of the Notes client is a logical next step if running setup again does not fix the problem. This information is from TN1245159
To perform a clean reinstall of the Notes client, complete the following steps: 1. Backup key Notes files by copying them to a folder that is located outside the current Notes installation. A list of key files to save or backup can be found in the Lotus Notes Help topic “Important Notes files to save or backup.” For your convenience, this list is repeated below. 2. Uninstall Notes using the Add or Remove Programs utility (to remove Program files and the Registry entries). 3. Delete the Notes folder and all folders within it (to remove Notes data files). 4. Reinstall the Notes client. 5. Replace key Notes files (from Step 1) to their original location. Additional Information When Notes is uninstalled using Add/Remove programs in Control Panel, these things happen:
The Notes folder, the data directory, and all files modified after the install (such as those created or modified during Setup or subsequently by a user) remain on the system. The goal of performing a clean reinstall is to remove any ambiguity about whether a file from the original install is causing a problem. Therefore, you must be absolutely thorough when performing a clean reinstall. For this reason, the removal of any leftover files is required. Copy of Help topic: “Important Notes files to save or backup” The following is a list of Notes files that you may want to save or backup in case you ever need to uninstall Notes and then reinstall it at another time. Note You may not have all of these files.
|
Found it today from TN 1596479
If the Synchronize Contacts feature is in use in IBM Lotus Notes 8.x, then a user who uses a Location document to switch to another mail file can unintentionally replicate deletions to that other mail file if they have Editor with delete documents access. Conversely, any delete operations in that other mail file will also propagate when switching locations back to their own mail file.
To be impacted by this issue, the following must be true:
1) You must have this option enabled: FilePreferencesContacts->’Enable “Synchronize Contacts” on the replication and Sync Tab’.
2) You must be editor (or above) with delete documents access to another mail file/mail-in database.
3) You must have a Location document that specifically points to the other mail file.
4) You must switch to that location.
5) You must have deleted a mail message that went to your mail file AND the other mail file, thereby sharing the same document UNID.
6) The message must not have been deleted in the other mail file
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.
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
- 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=noneA reboot is needed after making this changes.
- 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.
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
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
Websphere Portal 8 was launched and the downloads will be available on Friday .
See the what´s new in this link