Describes steps to deploy a single node of IBM Sametime 9 on AIX® 7.1 systems, including:
-- Preparing the environment prior to installation
-- Screen shots of the user interface during the configuration of each component
-- Common problems encountered during deployment
Note that this document supplements but does not replace the official Sametime 9 technical documentation. http://www-01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/welcome/welcome.html
2. Note that this document supplements but does not replace the official Sametime 9
technical documentation.
Prerequisites
Using SMIT (System Manager Interface Tool)
Before deploying Sametime 9 on AIX there are various administrative tasks that
may be necessary such as alterations to memory, or installation of certain packages or
fixes that may be needed in AIX. SMIT is an administrative application that can be used to
alter the sizes of the logical partitions and volumes in the AIX file system, and also to
change the paging space on the AIX system. An example of where SMIT has been used in
deployment of AIX is where the sizes of logical partitions need to be modified to create
sufficient memory on the file system for Sametime server builds and for installations.
Changing Logical partition sizes
Login to the AIX server (LPAR) using Putty as root user, type smit (this presents a menu system shown below):
# smit
System Management
Move cursor to desired item and press Enter.
Software Installation and Maintenance
Software License Management
Manage Editions
Devices
System Storage Management (Physical & Logical Storage)
Security & Users
Communications Applications and Services
Workload Partition Administration
Print Spooling
Advanced Accounting
Problem Determination
Manage the AIX Cryptographic Framework
Performance & Resource Scheduling
System Environments
Processes & Subsystems
Applications
Installation Assistant
Electronic Service Agent
Using SMIT (information only)
To change the size of logical partitions follow this path:
System Storage Management (Physical & Logical Storage) -> File Systems -> Add / Change / Show / Delete File
Systems -> Enhanced Journal File Systems
-> Change / Show Characteristics of an Enhanced Journaled File System
Select the desired item to change from the menu system...and hit enter.
+--------------------------------------------------------------------------+
| File System Name |
| |
| Move cursor to desired item and press Enter. |
| |
| / |
| /home |
| /usr |
| /var |
| /tmp |
| /admin |
| /opt |
3. | /var/adm/ras/livedump |
| |
| F1=Help F2=Refresh F3=Cancel |
| F8=Image F10=Exit Enter=Do |
| /=Find n=Find Next |
|---------------------------------------------------------------------------+
tab down to the mount point e.g. /tmp and hit enter.
This will display a field showing the number of units of 512 byte blocks.
Increase/decrease this number accordingly to increase/decrease the size of the partition.
Update the figure for the number of units and hit enter to apply the changes.
Then hit F10.
On the command line observer the size of the partition has changed with
# df -g
This will display all the file system sizes conveniently in GigByte blocks.
For more information on SMIT see Reference [1].
Increasing Paging Space (Swap Space)
The logical volume for paging space in AIX is usually 'hd6'. To see the paging space that is
available enter the following command:
# lsps -a
An example is given below:
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type Chksum
hd6 hdisk0 rootvg 512MB 66 yes yes lv 0
To display the information for the logical volume enter the following command:
# lslv hd6
LOGICAL VOLUME: hd6 VOLUME GROUP: rootvg
LV IDENTIFIER: 00c50f7700004c0000000142c87bd924.2 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: paging WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 256 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 2 PPs: 2
STALE PPs: 0 BB POLICY: non-relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: off
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
INFINITE RETRY: no
#
Here the size is calculated as the logical partition number times the size of each partition.
i.e. LP * PP SIZE (2 * 256 MB) = 512 MB
To increase the size of swap space, increase the value for the logical partition number, LP.
e.g. to increase LP by 8.
chps -s 8 hd6
4. To reduce the size of paging space, decrease the value for the logical partition number, LP.
chps -d 2 hd6
To reduce the size of a mount point:
chfs -a size=-5G /tmp
To increase the size of a mount point:
chfs -a size=+5G /tmp
Install all latest AIX updates
Obtain the latest AIX updates:
>smitty suma
Service Update Management Assistant (SUMA)
Move cursor to desired item and press Enter.
Download Updates Now (Easy)
Custom/Automated Downloads (Advanced)
Configure SUMA
Select "Download Updates Now (Easy)" -> "Download All Latest Fixes"
then enter yes to proceed
This downloads the .bff files to /usr/sys/inst.images/installp/ppc by default.
Install UltraVNC on AIX
Retrieve the vncserver (rpm) software from the following location:
ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/vnc/vnc-3.3.3r2-6.aix5.1.ppc.rpm
Upload the rpm to the AIX server using WinScp or other software.
Login using Putty (root/<password>) and install the package:
# rpm -ivh vnc-3.3.3r2-6.aix5.1.ppc.rpm
Set the VNC password:
# vncpasswd
Note: if this does not work responding with a response such as "Cannot write password file /.vnc/passwd"
then try:
# mkdir /.vnc
# /opt/freeware/bin/vncpasswd /.vnc/passwd
Password:
Verify:
#
Start the VNCServer:
/opt/freeware/bin/vncserver
List vnc processes to see what port to access using your vnc client..
e.g.
ps -ef | grep vnc
root 4587530 1 0 11:46:52 pts/0 0:00 Xvnc :1 -deskt
Login to the LPAR using UltraVNC (or other VNC) specifying server at port 1.
5. e..g ares-lpar10.mul.ie.ibm.com:1
and enter the vnc password that was set from above.
Install IBM Installation Manager, on AIX
The IM package to install is typically agent.installer.aix.gtk.ppc_1.6.2000.zip .
The procedure to install Installation Manager from IBM Infocentre can be found in Reference [2].
An unzip package is also required for use of an unzip command to extract the Installation Manager package itself:
unzip-5.51-1.aix5.1.ppc.rpm
The latest verions of these can be obtained from IBM. Upload these packages to the AIX server.
Install the unzip package:
# rpm -ivh unzip-5.51-1.aix5.1.ppc.rpm
Once the size of the logical partitions are ok (from SMIT procedure above) extract the IBM Installation package:
# unzip agent.installer.aix.gtk.ppc_1.6.2000.zip
Installing IBM Installation Manager can be done using console mode Reference [2] and Reference [3].
Install IBM Installation Manager in all AIX servers where it is required.
Launch IBM Installation Manager
When IBM Installation Manager is successfully installed it must be launched. Before it can be launched succesfully
however without error the following libraries are required to be installed on the AIX system. This is a type of error that can
be observed when attempting to launch IM if these libraries are NOT installed.
java.lang.UnsatisfiedLinkError: Could not load SWT library.
To launch IM successfully install the GTK libraries (see Reference [4]), verify any verisons of these packages that
already exist are uninstalled. Here is the list of libraries (run them in the order below):
rpm -ivh zlib-1.2.3-3.aix5.1.ppc.rpm
rpm -ivh xrender-0.9.1-3.aix5.2.ppc.rpm
rpm -ivh freetype2-2.3.9-1.aix5.2.ppc.rpm
rpm -ivh expat-2.0.1-1.aix5.2.ppc.rpm
rpm -ivh fontconfig-2.4.2-1.aix5.2.ppc.rpm
rpm -ivh xft-2.1.6-5.aix5.1.ppc.rpm
rpm -ivh xcursor-1.1.7-3.aix5.2.ppc.rpm
rpm -ivh pixman-0.12.0-3.aix5.2.ppc.rpm
rpm -ivh gettext-0.10.40-6.aix5.1.ppc.rpm
rpm -ivh glib2-2.12.4-2.aix5.2.ppc.rpm
rpm -ivh libpng-1.2.32-2.aix5.2.ppc.rpm
rpm -ivh cairo-1.8.8-1.aix5.2.ppc.rpm
rpm -ivh libtiff-3.8.2-1.aix5.2.ppc.rpm
rpm -ivh libjpeg-6b-6.aix5.1.ppc.rpm
rpm -ivh atk-1.12.3-2.aix5.2.ppc.rpm
rpm -ivh pango-1.14.5-4.aix5.2.ppc.rpm
rpm -ivh gtk2-2.10.6-4.aix5.2.ppc.rpm
Upload the rpms to the server and install using rpm *.rpm (Reference [4])
# cd /opt/IBM/InstallationManager/eclipse
# ./launcher
Installation Manager GUI should install successfully.
6. Deployment
Before proceeding to install Sametime 9 components on AIX refer to the pre-Installation
planning documentation in the Infocentre. This section illustrates the installation steps
undertaken to deploy a single node environment in AIX. The documentation in the
Sametime 9 Infocentre should be followed while performing this procedure. The logical
partitions on the AIX system should be sized accordingly for uploading of Sametime builds.
Install DB2
Upload DB2 (v10.1) build to AIX system and begin installation. See Reference [5].
Start setup: ./db2setup
13. Select above and click Next.
Enter information above, instance user, are email (containing hostname).
14. Finally Click Finish and follow any on screen post-install instructions that are presented
see next section.
Validation of DB2 installation
When DB2 installation has been completed you should verify that DB2 has been
successful installed in the post installatons steps. You should run the db2val script to
check the status of the installation, /opt/IBM/db2/V10.1_01/bin/db2val (see below).
Check the log file mentioned also for any errors/warnings.
15.
16.
17. Install Sametime Systems Console (SSC)
Launch Installation Manager Preferences and select the repository.config
Click OK.
36. Enter server name and title.
Enter password information for organisation.
37.
38. Enter Admin ID. Here it is “Admin notes”, for “Admin” insert Admin in Last name field and
leave First name and Middle 'blank'. Check the option highlighted also.
42. Install Community Server
Run setupaix.bin (from the installation package)
See Reference [8], and section Common Problems for chmod (below).
launches...
61. Check installation logs when install is complete and follow all post-install steps
see Reference [9].
Install Advanced Server
See Reference [10]
In SSC ISC:
62.
63. Specify hostname for Advanced and enter SSC admin credentials.
Chat room admin credentials.
83. Configure Single Sign-On (SSO)
Create a new LTPA Token in SSC:
Click LTPA
Specify a key file with username and password.
84. Export keys, this will create the LTPA key file at the specified location on the SSC.
Note: To import the LTPA Token one can use an IBM Domino Administrator client on
another machine e.g. a windows machine. To do this the admin.id file is copied over from
the AIX machine to that windows machine. This is the admin.id file that was saved during
the Domino server setup. It is located in /local/notesdata/.
If the primary Domino server does not have an IBM Admin client installed it may therefore be
desirable to use an IBM Admin client on another platform like windows for example. This can be
done to configure SSO and to register a secondary domino server. To do this:
1. Logon to a windows box that has IBM Domino Admin client installed.
2. Launch IBM Domino Admin and login as Admin user.
3. Copy over the admin.id file from the primary domino server (/local/notesdata) and store it on
the file system of the windows box hosting Domino Admin. Place it on the desktop for
convenience.
4. In Domino Admin choose File → Security → Switch ID and
85. 5. Navigate to the admin.id file on the desktop and click Open.
6. Now go to File → Open Server and under Select a server to administer, enter in the ipaddress
of the primary (AIX) Domino server. Click OK. The server is now added to the list of
administered servers in Domino Admin.
92. Extending the Sametime environment for HA and Failover
Failover and load balancing can be implemented in a Sametime deployment by creating a
cluster of multiple IBM® Sametime® servers of the same type. All Sametime servers can
be clustered except for the Sametime System Console, and the Video MCU and TURN
Server components of the Sametime Media Manager.
Clustering Domino and Community Server
Register the new secondary Domino server
1. Login to IBM Domino Admin client as Admin user.
2. Select the Configuration tab and choose File → Open Server
3. Select the primary Domino server that was configured earlier (Ensure Domino is started first)
4. Copy over the cert.id from the same location on the primary domino server (local/notesdata)
and store it on the windows desktop.
93. 5. On the right hand side select Registration dropdown list and choose server. Enter in the Server
<primary server>/ibm and path to the Certifier ID on the desktop. Click OK.
6. Enter in the certifier password. It was defined during the Domino setup for the primary node.
Click OK.
7. On Register servers window, Click Continue.
94. 8. Enter the secondary Domino server hostname. Uncheck 'In Domino Directory'. Check 'In File'
and click on the 'Set ID File' button, speciifying the path to the id file for the secondary node.
Specify desktop. Then click green tick button in screenshot below.
9. Select the new server and click Register.
95. Now install Domino on the secondary node as an additional server.
Create cluster in Domino Admin.
Create a deployment plan for the new Community server
Bring down Domino and Install Community server on the secondary node
Clustering WebSphere Components (Proxy, Meetings, Advanced)
• Ensure system clocks for two nodes are synchronized.
• Create a deployment plan for the secondary node in the cluster e.g. PS2.
• Install the application software.
• Create the cluster.
The procedure for clustering WebSphere based Sametime components is generic.
See Reference [12]. Here we will give an example of how this is achieved for Sametime
Proxy.
101. Common Problems
Installation Manager will not launch
On AIX navigate to /opt/IBM/INstallationManager/eclipse.
Launch IM as follows by running the launcher script.
# ./launcher
Result: fails to Launch with error:
java.lang.UnsatisfiedLinkError: Could not load SWT library.
Soln: Ensure all GTK library files are installed as described in section,
“Launch IBM Installation Manager”, see Reference [4].
A Sametime 9 build wont upload due to lack of space
Run df -g to see the size of the various mount points.
Check the amount of memory used where the build is being uploaded, e.g. /tmp, /home.
If it is a high percentage figure ~80/90% then use smit to alter the size of the logical partitions.
See “Changing Logical Partition sizes” above.
Reference [1] or information.
DB2 database create script fails
./createSCDB.sh STSC db2admin
Processing...
./createSCDB.sh[62]: db2: not found
Database creation failed
Soln:
Edited the .profile for db2admin
adding the following lines:
if [ -f /home/db2inst2/sqllib/db2profile ]; then
. /home/db2inst2/sqllib/db2profile
fi
The DB2 script needs to be run as instance user,
in this case it is db2inst2
./createSCDB.sh STSC db2inst2
102. AIDSC1352E: Unable to access the Sametime System Console database.
Problem connecting to DB2 database for SSC when using the Sametime System Console
This is a comment in relation to connecting to the DB2 database that was created when the
SSC script was run on the DB2 machine.
IF a db2inst (instance user)is used to run the script... ./createSCDb.sh STSC db2inst2
AND during the SSC installion (at the Common Configurations phase "Configure DB for the
System Console" user DB2ADMIN (default)is specified for Application User Id, the install
will succeed..but
Problem:
1. Try to connect to SSC database.. Sametime Prerequisites -> Connect to DB2 databases
as db2admin or db2instX (instance user) results in:
AIDSC1352E: Unable to access the Sametime System Console database.
Solution:
Go to Resources -> JDBC -> Data Sources.
Test the connections for the resources that are availble. if ok then
Select each data Source e.g. sscScheduler and select JAAS - J2C authentication data.
Click on the resource and change the database alias to instance user.
Repeat for all relevant Data Sources.
Finally: restart the node agent and App server for SSC.
Login again and it should be possible to connect to the database as instance user.
For more info:
see http://www-01.ibm.com/support/docview.wss?uid=swg21611878
Install of SSC fails : error=12, Not enough space (versionInfo.sh)
On AIX 7.1 an install of SSC may fail with a typical error:
This is the script being run the installation fails: i.e. /opt/IBM/WebSphere/AppServer/bin/versionInfo.sh"
(in directory "/opt/IBM/WebSphere/AppServer/bin"): error=12, Not enough space
if the /opt directory has sufficient space, check the swap space also:
e.g.
# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type Chksum
hd6 hdisk0 rootvg 512MB 66 yes yes lv 0
increase swap space (probably hd6 as above). See Increasing Paging Space (Swap Space)
e.g. chps -s 8 hd6
if you receive an error:
0516-404 allocp: This system cannot fulfill the allocation request.
then you may need to decrease some other volume in rootvg to free up space for hd6.
103. For example chfs -a size=-10G /tmp (/tmp or other mountpoint with free space)
then try chps -s <nof_PPs> hd6
and it should create more swap space.
http://aixdoc.wordpress.com/2012/02/20/increase-paging-space-logical-volume-size/
retry installation of SSC, (may also need to uninstall WAS first)
Installing Domino: I/O completion ports error
If the installation of Domino fails with the above error then follow the procedure in Reference [12].
Install Domino9, InstallShield Wizard wont start up
The script used to install Domino9 on AIX was in this location below
/tmp/Domino/Domino9-AIX/aix/domino
and the command
./install starts the installation for Domino9. ( as root)
Problem: Installshield wizard fails to start..
Solution:
The ./install script makes calls to setupAix.bin and setup.jar in the ./tools
subdirectory.. The permissions on these files was -rw-------
when I turned on the executable bit on these files it works then..
-rwx------ 1 root system 31240115 Mar 9 2013 setupAix.bin
-rwx------ 1 root system 742213540 Mar 9 2013 setup.jar
104. Domino9 server setup wizard wont initialize , with 'unlocked terminal' message
When using a Graphical Desktop to logon to the Domino server, the following steps are required to set up
Domino:
1. Change to user 'notes', su notes
2. cd /local/notesdata where the notes.ini is located.
3. Start Domino9 setup: /opt/ibm/domino/bin/server
Problem:
When attempting to start Domino after installation the following error message may appear:
”Please edit your shell's DISPLAY environment variable to reflect an unlocked terminal that you
would like to launch the Domino Setup Program on”.
Solution:
1. Logon as root
2. Add server to the ACL: /usr/lpp/X11/bin/xhost ares-lpar28.mul.ie.ibm.com
Response: ares-lpar28.mul.ie.ibm.com being added to access control list
3. Switch to user notes and then cd /local/notesdata
4. Export display: export DISPLAY=ares-lpar28.mul.ie.ibm.com:1
5. /opt/ibm/domino/bin/server
Result: Domino server setup wizard should now start up.
105. Cannot connect to LDAP from SSC
Cannot connect to database from SSC
-SSC install inst user must be specified
-space in /home
installation of WAS Component fails because of space.. /opt/IBM/WebSphere/AppServer/bin/versionInfo.sh"
error=12, Not enough space
Sso.
SAMETIME services wont all start up/shut down
- reboot
Specification of WebSphere folder in IBM Installation Manager (Recommendation)
When installing WebSphere Application Server (for AIX) through the IBM Installation Manager GUI, at the
page "Install Packages" one is required to specify the installation directory for WAS.
Note that it may default to /usr/IBM/Websphere/AppServer. This is acceptable.
But it is nonetheless advisable to modify it to /opt/IBM/Websphere/AppServer if desirable.
References
[1] Introducing AIX System Management Interface Tool (SMIT)
[2] Installing IBM Installation Manager on AIX
[3] Installing Installation Manager
[4] Required gtk libraries for installation of Installation Manager on AIX
[5] Installing DB2 on AIX, Linux, or Windows
[6] Installing and configuring IBM Lotus Domino 8.5 on AIX
[7] Sametime 9: Installing Domino
[8] Sametime 9: Installing the Sametime Community Server on AIX
[9] Sametime 9: Install Proxy on AIX, Linux, Windows
[10] Installing a Sametime Advanced Server on AIX, Linux, or Windows
[11] Sametime 9: Installing Sametime Meeting Server
[12] Expanding the deployment for high availability and failover
