IBM Sametime 9 was launched a few weeks ago. When i saw this video i do the upgrade of my embedded Sametime client on Notes 9
The process was very easy, just download the package, shutdown the Notes Client and run the installer.
IBM Sametime 9 was launched a few weeks ago. When i saw this video i do the upgrade of my embedded Sametime client on Notes 9
The process was very easy, just download the package, shutdown the Notes Client and run the installer.
Just finish the integration between our Sametime 8.5.2 IFR1 and IBM Connections.
This guide is a excellent material to get started. My environment is not the same, but with few modifications, i got Sametime and Connections working together.
On the page 208 the author show hot to display connections photos ins Sametime web client instant messages.
If you have a few users it is easy to fill the PhotoURL field but if you have a lot of users you need the power of Domino Agents and @Functions.
This single line agent do the job (I schedule this agent to run once a day)
FIELD PhotoURL :=”https://
I have several servers with Centos running Domino, Sametime etc. I need to setup Sametime Proxy just to use with IBM Connections and Mobile Devices.
We are a small deployment but need more disk space to setup the Proxy on the same machine of the community server
This command above show the hard drives installed
# ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2
After instal a new one i get this
# ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sdb
dev/sdb is the new hard disk
Create a new partition
# su –
# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xd1082b01.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won’t be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
WARNING: DOS-compatible mode is deprecated. It’s strongly recommended to
switch off the mode (command ‘c’) and change display units to
sectors (command ‘u’).
Command (m for help):
Switch off DOS compatible mode and change the units to sectors by entering the c and u commands:
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
In order to view the current partitions on the disk enter the p command:
Command (m for help): p
Disk /dev/sdb: 34.4 GB, 34359738368 bytes
255 heads, 63 sectors/track, 4177 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd1082b01
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4):
Partition number (1-4): 1
First sector (2048-67108863, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-67108863, default 67108863):
Using default value 67108863
Now that we have specified the partition we need to write it to the disk using the w command:
If we now look at the devices again we will see that the new partition is visible as /dev/sdb1:
# ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sdb /dev/sdb1
Create the file system
# /sbin/mkfs.ext3 -L /proxy /dev/sdb1
Mounting the filesystem
mkdir /stproxy
# mount /dev/sdb1 /stproxy
Configuring Centos 6 to Automatically Mount a Filesystem
Edit /etc/fstab
add the line
LABEL=/proxy /stproxy ext3 defaults 1 2
This link helps a lot
A good document on how setup SSO between connections and other IBM products.
Here in Brazil we are known by first name. The Domino Directory only lists people using Last Name, First Name.
I know is not a good idea to change Domino Directory but users are very confused to work with Last Name , First Name.
So i change some views (column name) on the Domino Directory and change the person name order to First Name Last Name
For reference you can read the article Personal names around the world
People
DisplayPersonName := @Trim(@Implode(@Trim(@Subset(FirstName; 1) : MiddleInitial:@Subset(LastName; 1)); ” “));
DisplayName := @If(DisplayPersonName = “”; @Subset(FullName; 1); @Trim(DisplayPersonName:@Name([Abbreviate];AltFullName)));
@Name([Abbreviate]; DisplayName)
$PeopleGroupsFlat
DisplayPersonName := @Trim(@If(Type = “Person”; @Implode(@Trim(@Subset(FirstName; 1) : MiddleInitial : @Subset(LastName; 1)); ” “); “”):AltFullName);
DisplayName := @If(Type = “Group”; @Subset(ListName; 1); Type=”Server”;ServerName;@If(DisplayPersonName = “”; @Subset(FullName; 1); DisplayPersonName));
@Name([Abbreviate]; DisplayName)
$PeopleGroupsHier
DisplayPersonName := @Trim(@If(Type = “Person”; @Implode(@Trim(@Subset(FirstName; 1) : MiddleInitial: @Subset(LastName; 1)); ” “); “”):@Name([CN];AltFullName));
DisplayName := @If(Type = “Group”; @Subset(ListName; 1); Type=”Server”;ServerName;@If(DisplayPersonName = “”; @Subset(FullName; 1); DisplayPersonName));
@Name([Abbreviate]; DisplayName)
$PeopeGroupsCorpHier
DisplayPersonName := @If(Type = “Person”; @Implode(@Trim(@Subset(FirstName; 1) : MiddleInitial : @Subset(LastName; 1)); ” “); “”);
DisplayName := @If(Type = “Group”; @Subset(ListName; 1);Type=”Server”;Servername; @If(DisplayPersonName = “”; @Subset(FullName; 1); DisplayPersonName));
AltName:=@If(AltFullName!=””;@True;@False);
@Trim(@If(JobTitle!=””;JobTitle + ” “;””)+ (@Name([Abbreviate]; DisplayName)) + @If(AltName=@True;” (“+@Name([Abbreviate];AltFullName)+”)”;””))
From my inbox today
http://memeburn.com/2013/09/should-microsoft-kill-sharepoint-gartner/
The past week has been very productive and exciting. I worked with two engineers from RedPill which are very famous in the community of ICS and IBM also Champions.
This week I was totally immersed in a process of modernization of Notes/Domino applications that really impressed everybody, as much as for the customer, which has one of the highest Notes/Domino installations in the world.
The numbers are impressive, both in number of users, servers and applications. In a week we have created 200+ Notes applications that are now available for mobile devices.
Take a look on what RedPill can do for modernizing Notes/Domino applications
Thank you Nathan Freeman and Peter Presnell for an amazing week working together.
When trying to create the initial index for Global Search from the Homepage server, the index update fails with an error.
To prevent further problems with indexing, perform a search in the Profiles database for any null entries in the table EMPINST.EMPLOYEE.
select * from EMPINST.EMPLOYEE If any entries are returned they must be updated with an entry in the display name column for the Profiles feature to index successfully. To prevent this issue from occurring, change the value of PROF_DISPLAY_NAME=256 in the validate_dbrepos_fields.properties file, to contain the following: PROF_DISPLAY_NAME=(x != null) && (x.length() > 0) && (x.length() <= 256) Then repopulate the peopledb database. This will cause any name that contains a null value in the Prof_Display_Name field to fail initially when you populate the profiles database. |
TN1321806 |
Notes Traveler users using BlackBerry 10 devices must delete and recreate their BlackBerry 10 Notes Traveler account on the device when the Notes Traveler server is upgraded from 9.0.0.0 to 9.0.0.1 or later to ensure maximum compatibility.
NOTE: This is required only if the device had previously been connected to a Notes Traveler 9.0.0.0 server. No action is required if setting up a new 9.0.0.1 or later server or if connecting a new device to an existing 9.0.0.1 server. The BlackBerry 10 maintenance level 10.1.0.4651 introduced a severe issue when syncing with IBM Notes Traveler 9.0.0.0. Using this version of the BlackBerry 10 calendar synchronization client, any update that a BB10 user makes to a repeating meeting will corrupt the meeting on the Domino server. Calendar sequence numbers for the meeting are inadvertently reset to 1, which will prevent any further updates or reschedules to the meeting by the meeting owner (subsequent updates will be seen as being out of date, so attendees will not be able to apply these updates to their calendar). As a workaround for this device issue, IBM recommends that you upgrade IBM Notes Traveler servers to version 9.0.0.1 Interim Fix 1 or later. For a download link and fix list for Notes Traveler 9.0.0.1 Interim Fix 1, see technote 1648195. The issue does not occur when BlackBerry 10 devices running maintenance level 10.1.0.4651 have provisioned their IBM Notes Traveler account against Notes Traveler 9.0.0.1 or later. However, BlackBerry 10 devices at this fix level provisioned against an earlier version of the server will still exhibit this behavior. The only known workaround is to remove the existing IBM Notes Traveler account on the device, and then add it back. Both the upgrade of the IBM Notes Traveler server and the removal of the IBM Notes Traveler account on the BB10 device are required to avoid this problem. For questions or additional information regarding users activated on BlackBerry Enterprise Service 10, contact BlackBerry Support directly. If the IBM Notes Traveler account on the BB10 device has never connected to a IBM Notes Traveler server level prior to 9.0.0.2, then the above problem and fix do not apply. |
From TN1648847
How should I start tuning WebSphere portal Server for better performance ?
This tuning guide provides details about the parameters that you can tune to improve portal performance. This guide serves as a very good starting point to start portal tuning process before production usage.
Performance tuning guide for WebSphere portal on IBM i
This document discusses additional performance tuning recommendations that is specific to running WebSphere Portal on the IBM i platform. The focus is more on platform level recommendations unique to the IBM i and are minimally discussed in the above guide.
Monitoring Performance in a WebSphere Portal environment
To tune your WebSphere Portal environment for optimal performance, you need to know what needs tuning. The monitoring methods discussed in this article cover several key areas of WebSphere Portal. They help you to view the true behavior of your WebSphere Portal environment and ultimately identify bottlenecks and potential problems. This article is meant to be an overview of monitoring methods rather than an in-depth look at any specific methods.
IBM WebSphere Portal performance testing and analysis
Finding and fixing performance problems in a production environment is challenging on a number of levels. Optimally, most bottlenecks in the system should be found and fixed before the system is allowed into production. This article explains a tested process that can ensure that, with high probability, most of the significant performance issues are found and addressed before you promote a system to production.
IBM WebSphere portal performance considerations for custom portal code
This article provides general guidance for creating well performing custom code for IBM WebSphere Portal. Custom code does not only refer to portlets (although they are the most common programming model for portals), but also includes code for WebSphere Portal themes and skins.
Performance management tools for IBM WebSphere Portal
This article describes the tools and how they were used to evaluate an IBM WebSphere Portal 7.0 performance and/or problem determination issue during a recent engagement at a customer site.
WebSphere Portal Performance Troubleshooting Guide
This document is intended as a guide for resolving performance problems in IBM WebSphere Portal V5.1 or later.
How to set an appropriate number of Portal Datasource connections in WebSphere Portal
For a given maximum number of Portal WebContainer threads set, what should I set my maximum Portal datasource connections to? This is important parameter and may lead to portal hang if not tuned correctly.
WebSphere Portal Server and Dynacache Replication(DRS) issues
This technote discusses some common issues observed with a WebSphere Portal server cluster having performance, memory issues, and HAManager/DRS exceptions. The cache replication suggestions are also valid for portal version 7.0.x.x.