Scope
This article aims to install a Sametime V8.5.2 Server with Audio Visual meeting components enabled on a CentOS 5/RHEL 5 Linux server.
Getting Started
If you would like a Sametime Server to have Media (Audio & Visual) capabilities you must install several components.
- Sametime Community Server
- DB2
- Sametime System Console
- Sametime Media Server
If you also want the new style meeting capability, which I haven't even seen yet and will eventually get to, you must also install Meeting Server. So there you have it, that's all you need to know...hah yah right. This is an extremely complicated installation and very daunting. You need to spend hours toiling over the IBM documentation and contacting IBM support to get this working, or you can just read this post and save yourself some headaches.
Tips, things to know, and mistakes I made along the way:
- Check some of your other sametime servers' sametime.ini for the current VP_SECURITY_LEVEL setting and make the new one matches the others in your environment. That will ensure you can communicate among community servers.
- Make sure your server's security settings Internet Security Setting is set to: More name variations with lower security. This enables the use of Domino short-names and full User Names (First and Last Name) to be used when logging into the server.
- Replicate the vpuser.nsf from your current sametime server to the new one, in a new connection document until you plan on decommissioning the old server. This will keep your user's Sametime Contact lists in sync.
- I had problems launching the launchpad application, so I opened a support PMR and was informed I could use Installation Manager directly by running the install file inside of the IM directory:
- su - (To login as root. It will not allow you install if you are not root.)
- #cd <extracted installation files>/<InstallationName>/IM/
- #./install
- *****You can not do Audio/Video between pre-8.5 versions of Sametime
Gather Installers:
So start off by downloading all the necessary parts and build up a clean RHEL server (or whatever you prefer from IBM's supported systems list.) Also I'll state this now. I'm not using RHEL, but actually CentOS and will probably be unsupported by IBM if I'm honest with them, but with that being said I was able to trick the installer. I'll write a separate post on how to make a CentOS system appear to be a RHEL system later as well I suppose.
Domino 8.5.2 and FP3 for it. (I'm not going 8.5.3 until there's an FP1)
Install your Domino server as normal and make sure you click "This is a sametime server - Yes" in it's server document.
The "IBM Sametime Standard V8.5.2 Multiplatform Multilingual" eAssembly is part CRE9WML.
For Linux you will need:
- CZYD8ML.tar IBM Sametime Standard Community Server V8.5.2 AIX Linux Solaris Multilingual
- IBM DB2 9.7 (eAssembly is part CRE9VML)
- DB2_97_limited_CD_Linux_x86-64.tar.gz - Part CZ1HSEN IBM DB2 9.7 - Limited Use for Linux® on AMD64 and Intel® EM64T systems (x64)
- CZYF4ML.tar IBM Sametime Standard V8.5.2 System Console Server Linux on x86 Multilingual
- CZYF1ML.tar IBM Sametime Standard V8.5.2 Media Manager Linux on x86 Multilingual
- CZYE4ML.tar IBM Sametime Standard V8.5.2 Meeting Server Linux on x86 Multilingual
Install DB2 (Start to finish ~1 hour)
DB2 is required by the System Console, and System Console is required by Media Manager, so you will definitely need this if you want to be able to do AV calls in your Sametime Environment.
Planning is important. If you're running a large scale environment you would want to install each one of these server pieces on a separate machine. In this scenario we are building a stand-alone sametime server.
Copy the DB2_97_limited_CD_Linux_x86-64.tar.gz up to your server.
Unpack the files:
#tar -xvf DB2_97_limited_CD_Linux_x86-64.tar.gz
#cd wser
I found it easier to create your DB2 group and user first rather than letting the installer do it. It was giving strange errors on my standard password:
groupadd dasadm1
useradd dasusr1 -G dasadm1
passwd dasusr1
<enterapassword>
groupadd db2iadm1
useradd db2inst1 -G db2iadm1
passwd db2inst1
<enterapassword>
groupadd db2fadm1
useradd db2fenc1 -G db2fadm1
passwd db2fenc1
<enterapassword>
Run the graphical setup:
#./db2setup
Choose to install a Product.
Choose DB2 Workgroup Server Edition
Accept license aggreement.
Point the response file to a path such as /opt/ibm so you can replicate your install if needed.
Point it to your desired install path. Mine is /opt/ibm/db2/V9.7_01
Point the installer to the users we created in the order we created them as it prompts on each screen.
Give the installer your mail relay server hostname.
Create a local contact. I used a distribution group in my case. You just need to give it a name and an e-mail address.
Click Finish.
Log in as db2inst1 and run the application /opt/ibm/db2/V9.7_01/bin/db2fs
This will launch DB2 First Step.
Click the Create a New Database
Name it: STSC
Default Directory> I gave it /opt/ibm/db2/data/db2inst1
(***if the path doesn't exist yet you need to create it first. Change ownership to your db2inst1 user for the install path as well. chown db2inst1.db2iadm1 /opt/ibm/db2/data/db2inst1)
Alias> I left blank
Comment> Sametime System Console
Click Next
Maintenance> "Yes I can specify an offline maintenance window of at least an hour when the database is inaccessible."
Click Next
This is all your choice for when maintenance will occur. I'm letting mine run on weekends at 3AM and have a window of up to 5 hours to complete.
Timing> Start Time 03:00
Duration 5 hours
Only on selected days: Saturday and Sunday selected
Notification>You will probably already see the contact you created earlier selected. This is fine for me.
Click Next
Summary>Make everything is to your liking. You can click on the "Show Command" button to see what is going to run on your system.
Click Finish
As long as all of your directory permissions were set properly by changing owner, you should see some progress on the creation of your new DB.
As long as all of your directory permissions were set properly by changing owner, you should see some progress on the creation of your new DB.
You will see a window with post installation tasks and a log file. You will want to record the db2inst1 port number for your System Console install. My port was 50001.
Install IBM Sametime Standard V8.5.2 System Console (~1hr 20 mins.)
Copy the installer to the server and extract the files.
Switch to the db owner user:
su db2inst1
We are now going to create the System Console Database and Tables
cd ~/sqllib/
. ./db2profile
cd <extracted system console files path>/DatabaseScripts/SystemConsole/
./createSCDb.sh
It should return something like this:
Processing...
Database Connection Information
Database server = DB2/LINUXX8664 9.7.0
SQL authorization ID = DB2INST1
Local database alias = STSC
*** createSCDb.sh: skipping granting privileges to self
DB20000I The SQL command completed successfully.
DB20000I The SQL command completed successfully.
CREATE SCHEMA SSC
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.DEPLOYMENTPLAN ( PLANID VARCHAR(300) NOT NULL, PLANSTATUS VARCHAR(500), PLANDETAIL CLOB, PRIMARY KEY (PLANID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PHYSICALNODE ( NODEID VARCHAR(300) NOT NULL, HOSTNAME VARCHAR(300), DEPLOYMENTID VARCHAR(300), PREREQID VARCHAR(300), DEPTYPE VARCHAR(500), PLATFORMDETAIL CLOB, GEOID VARCHAR(500), PRIMARY KEY (NODEID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQMASTER ( PREREQTYPE VARCHAR(300) , PRODUCTNAME VARCHAR(300) NOT NULL, OFFERING CLOB, PRIMARY KEY (PRODUCTNAME) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.DEPLOYMENT ( DEPID VARCHAR(500) NOT NULL, PRODUCTTYPE VARCHAR(500), OFFERINGVERSION VARCHAR(500), DEPNAME VARCHAR(500), DPLAN CLOB, DEPNODE VARCHAR(4000), DEPPREREQ CLOB, DEPCONF CLOB, PRODUCTGENID CLOB, DEPSTATUS VARCHAR(100), INSTALLTYPE VARCHAR(100), PRODUCTNAME VARCHAR(500), DEPENDENTPRODUCT CLOB, CLUSTERINFO CLOB, COMPONENTINFO VARCHAR(4000), GEOID VARCHAR(500), DISPLAYVERSION VARCHAR(500), PRIMARY KEY (DEPID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PLATFORM ( PLATFORMTYPE VARCHAR(300) NOT NULL, OSTYPE CLOB, PRIMARY KEY (PLATFORMTYPE) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQDEPLOYMENT ( PREQDEPID VARCHAR(500) NOT NULL, PREQDEPNAME VARCHAR(500), PREQPRODNAME CLOB, PREREQTYPE VARCHAR(500), PRECONFIG CLOB, PRENODE CLOB, PRODUCTDEPLOYMENT CLOB, PARAMID CLOB, CONFIGID CLOB, GEOID VARCHAR(500), PRIMARY KEY (PREQDEPID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQMASTERCONFIG ( PREREQTYPE VARCHAR(300) NOT NULL, CONFIGDETAIL CLOB, PRIMARY KEY (PREREQTYPE) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.MASTERDEPLOYMENTPLAN ( DEPPLANID VARCHAR(500) NOT NULL, DEPPLANNAME VARCHAR(500), PLANID VARCHAR(500), PLANNAME VARCHAR(500), PLANDETAIL CLOB, PRIMARY KEY (DEPPLANID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PRODUCTOFFERING ( PRODUCTTYPE VARCHAR(500) NOT NULL, PRODUCTNAME VARCHAR(500), OFFERINGDETAIL CLOB, PRIMARY KEY (PRODUCTTYPE) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQCONFIG ( PARAMID VARCHAR(500) NOT NULL, PARAM CLOB, PRIMARY KEY (PARAMID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PRODUCTCONFIG ( PRODUCTGENID VARCHAR(500) NOT NULL, PARAMID VARCHAR(500), CONFIGURATION CLOB, PRODUCTTYPE VARCHAR(500), PRIMARY KEY (PRODUCTGENID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.CLUSTERDEPLOYMENT ( CLUSTERDEPID VARCHAR(500) NOT NULL, CLUSTERNAME VARCHAR(300), CLUSTERTYPE VARCHAR(200), PRODUCTTYPE VARCHAR(200), CELLNAME VARCHAR(300), NODELIST CLOB, CLUSTERMEMBER CLOB, CLUSTERCONFIG CLOB, CLUSTERSTATUS VARCHAR(500), DMDEPID VARCHAR(500), GEOID VARCHAR(500), CLUSTERVERSION VARCHAR(200), PRIMARY KEY (CLUSTERDEPID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.SCHEDULEDTASK ( DEPID VARCHAR(500), TASKID VARCHAR(500) NOT NULL, UPDATECONFIG CLOB, TASKTYPE VARCHAR(500), PRIMARY KEY (TASKID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.GEOGRAPHYDATA ( GEOID VARCHAR(500) NOT NULL, GEONAME VARCHAR(500), PRIMARY KEY (GEOID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.VERSIONINFO ( ID VARCHAR(300) NOT NULL, PRODUCTTYPE VARCHAR(500), TYPE VARCHAR(300), VERSIONHISTORY CLOB, CURRENTVERSION VARCHAR(300), PRIMARY KEY (ID) )
DB20000I The SQL command completed successfully.
CREATE TABLE POLICY.TEMPLATE ( POLICY_ID VARCHAR(128) NOT NULL, POLICY_LABEL VARCHAR(128) NOT NULL, POLICY_WEIGHT VARCHAR(128), POLICY_PRODUCT VARCHAR(128), POLICY_TYPE VARCHAR(128), POLICY_XML LONG VARCHAR, PRIMARY KEY(POLICY_ID) )
DB20000I The SQL command completed successfully.
CREATE TABLE POLICY.ASSIGNMENT ( POLICY_ID VARCHAR(128) NOT NULL, POLICY_PRODUCT VARCHAR(128) NOT NULL, USER_ID VARCHAR(128) NOT NULL, IS_GROUP SMALLINT NOT NULL, FOREIGN KEY(POLICY_ID) REFERENCES POLICY.TEMPLATE(POLICY_ID) )
DB20000I The SQL command completed successfully.
DB20000I The SQL DISCONNECT command completed successfully.
db2 connect to STSC
db2 -tf createSchedTable.ddl
Make sure your SELINUX setting is disabled or permissive with /etc/selinux/config. You will need to restart the server if you make a change.
In GNOME (Graphical environment):
Copy the installer to the server and extract the files.
Switch to the db owner user:
su db2inst1
We are now going to create the System Console Database and Tables
cd ~/sqllib/
. ./db2profile
cd <extracted system console files path>/DatabaseScripts/SystemConsole/
./createSCDb.sh
It should return something like this:
Processing...
Database Connection Information
Database server = DB2/LINUXX8664 9.7.0
SQL authorization ID = DB2INST1
Local database alias = STSC
*** createSCDb.sh: skipping granting privileges to self
DB20000I The SQL command completed successfully.
DB20000I The SQL command completed successfully.
CREATE SCHEMA SSC
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.DEPLOYMENTPLAN ( PLANID VARCHAR(300) NOT NULL, PLANSTATUS VARCHAR(500), PLANDETAIL CLOB, PRIMARY KEY (PLANID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PHYSICALNODE ( NODEID VARCHAR(300) NOT NULL, HOSTNAME VARCHAR(300), DEPLOYMENTID VARCHAR(300), PREREQID VARCHAR(300), DEPTYPE VARCHAR(500), PLATFORMDETAIL CLOB, GEOID VARCHAR(500), PRIMARY KEY (NODEID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQMASTER ( PREREQTYPE VARCHAR(300) , PRODUCTNAME VARCHAR(300) NOT NULL, OFFERING CLOB, PRIMARY KEY (PRODUCTNAME) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.DEPLOYMENT ( DEPID VARCHAR(500) NOT NULL, PRODUCTTYPE VARCHAR(500), OFFERINGVERSION VARCHAR(500), DEPNAME VARCHAR(500), DPLAN CLOB, DEPNODE VARCHAR(4000), DEPPREREQ CLOB, DEPCONF CLOB, PRODUCTGENID CLOB, DEPSTATUS VARCHAR(100), INSTALLTYPE VARCHAR(100), PRODUCTNAME VARCHAR(500), DEPENDENTPRODUCT CLOB, CLUSTERINFO CLOB, COMPONENTINFO VARCHAR(4000), GEOID VARCHAR(500), DISPLAYVERSION VARCHAR(500), PRIMARY KEY (DEPID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PLATFORM ( PLATFORMTYPE VARCHAR(300) NOT NULL, OSTYPE CLOB, PRIMARY KEY (PLATFORMTYPE) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQDEPLOYMENT ( PREQDEPID VARCHAR(500) NOT NULL, PREQDEPNAME VARCHAR(500), PREQPRODNAME CLOB, PREREQTYPE VARCHAR(500), PRECONFIG CLOB, PRENODE CLOB, PRODUCTDEPLOYMENT CLOB, PARAMID CLOB, CONFIGID CLOB, GEOID VARCHAR(500), PRIMARY KEY (PREQDEPID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQMASTERCONFIG ( PREREQTYPE VARCHAR(300) NOT NULL, CONFIGDETAIL CLOB, PRIMARY KEY (PREREQTYPE) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.MASTERDEPLOYMENTPLAN ( DEPPLANID VARCHAR(500) NOT NULL, DEPPLANNAME VARCHAR(500), PLANID VARCHAR(500), PLANNAME VARCHAR(500), PLANDETAIL CLOB, PRIMARY KEY (DEPPLANID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PRODUCTOFFERING ( PRODUCTTYPE VARCHAR(500) NOT NULL, PRODUCTNAME VARCHAR(500), OFFERINGDETAIL CLOB, PRIMARY KEY (PRODUCTTYPE) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PREREQCONFIG ( PARAMID VARCHAR(500) NOT NULL, PARAM CLOB, PRIMARY KEY (PARAMID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.PRODUCTCONFIG ( PRODUCTGENID VARCHAR(500) NOT NULL, PARAMID VARCHAR(500), CONFIGURATION CLOB, PRODUCTTYPE VARCHAR(500), PRIMARY KEY (PRODUCTGENID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.CLUSTERDEPLOYMENT ( CLUSTERDEPID VARCHAR(500) NOT NULL, CLUSTERNAME VARCHAR(300), CLUSTERTYPE VARCHAR(200), PRODUCTTYPE VARCHAR(200), CELLNAME VARCHAR(300), NODELIST CLOB, CLUSTERMEMBER CLOB, CLUSTERCONFIG CLOB, CLUSTERSTATUS VARCHAR(500), DMDEPID VARCHAR(500), GEOID VARCHAR(500), CLUSTERVERSION VARCHAR(200), PRIMARY KEY (CLUSTERDEPID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.SCHEDULEDTASK ( DEPID VARCHAR(500), TASKID VARCHAR(500) NOT NULL, UPDATECONFIG CLOB, TASKTYPE VARCHAR(500), PRIMARY KEY (TASKID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.GEOGRAPHYDATA ( GEOID VARCHAR(500) NOT NULL, GEONAME VARCHAR(500), PRIMARY KEY (GEOID) )
DB20000I The SQL command completed successfully.
CREATE TABLE SSC.VERSIONINFO ( ID VARCHAR(300) NOT NULL, PRODUCTTYPE VARCHAR(500), TYPE VARCHAR(300), VERSIONHISTORY CLOB, CURRENTVERSION VARCHAR(300), PRIMARY KEY (ID) )
DB20000I The SQL command completed successfully.
CREATE TABLE POLICY.TEMPLATE ( POLICY_ID VARCHAR(128) NOT NULL, POLICY_LABEL VARCHAR(128) NOT NULL, POLICY_WEIGHT VARCHAR(128), POLICY_PRODUCT VARCHAR(128), POLICY_TYPE VARCHAR(128), POLICY_XML LONG VARCHAR, PRIMARY KEY(POLICY_ID) )
DB20000I The SQL command completed successfully.
CREATE TABLE POLICY.ASSIGNMENT ( POLICY_ID VARCHAR(128) NOT NULL, POLICY_PRODUCT VARCHAR(128) NOT NULL, USER_ID VARCHAR(128) NOT NULL, IS_GROUP SMALLINT NOT NULL, FOREIGN KEY(POLICY_ID) REFERENCES POLICY.TEMPLATE(POLICY_ID) )
DB20000I The SQL command completed successfully.
DB20000I The SQL DISCONNECT command completed successfully.
This will prevent the need for the db2inst1 user from needing admin rights:
db2 connect to STSC
db2 -tf createSchedTable.ddl
Make sure your SELINUX setting is disabled or permissive with /etc/selinux/config. You will need to restart the server if you make a change.
In GNOME (Graphical environment):
If you are still logged in to GNOME with db2inst1 open a terminal and switch to root:
su -
Launch the System Console Installation:
<path to extracted installation files>/launchpad.sh
You will be prompted to install IBM Installation Manager. I installed it to /opt/ibm/InstallationManager
Once done you can install System Console. Accept the license agreements and click Next.
Choose your installation path. I chose /opt/ibm/SSPShared Click Next.
Choose your installation path for WebSphere. I chose /opt/ibm/WebSphere Click Next.
WAS Location> "Use Sametime installed Websphere Application Server"
WAS Configuration> Accept the defaults for Cell and Node (unless you know better than me here suggestions are welcome.) Ensure your FQDN is correct for host name field. Accept the default user for websphere (wasadmin) and give it a password.
Configure DB2 for the System Console>enter the db2 server FQDN. Since we're installing everything on the same server enter the same server FQDN you've used in previous steps. Make sure you enter the port that was displayed in the post-installation steps of your DB2 install. Mine was port 50001. Accept the default DB name for the System Console/Policy.
Enter db2inst1 for the application user id and the password you gave this user in previous steps.
Click the Validate button to ensure you can connect to the db2 database properly.
Click Install. Installation progress will be displayed. You should be done with no warning or exceptions.
Click Finish.
Test that you can log-in to the System Console
For more details refer to: http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_the_console_on_AIX_Linux_Solaris_or_Windows_st852
su -
Launch the System Console Installation:
<path to extracted installation files>/launchpad.sh
You will be prompted to install IBM Installation Manager. I installed it to /opt/ibm/InstallationManager
Once done you can install System Console. Accept the license agreements and click Next.
Choose your installation path. I chose /opt/ibm/SSPShared Click Next.
Choose your installation path for WebSphere. I chose /opt/ibm/WebSphere Click Next.
WAS Location> "Use Sametime installed Websphere Application Server"
WAS Configuration> Accept the defaults for Cell and Node (unless you know better than me here suggestions are welcome.) Ensure your FQDN is correct for host name field. Accept the default user for websphere (wasadmin) and give it a password.
Configure DB2 for the System Console>enter the db2 server FQDN. Since we're installing everything on the same server enter the same server FQDN you've used in previous steps. Make sure you enter the port that was displayed in the post-installation steps of your DB2 install. Mine was port 50001. Accept the default DB name for the System Console/Policy.
Enter db2inst1 for the application user id and the password you gave this user in previous steps.
Click the Validate button to ensure you can connect to the db2 database properly.
Click Install. Installation progress will be displayed. You should be done with no warning or exceptions.
Click Finish.
Test that you can log-in to the System Console
- http://sametime.example.com:8700/ibm/console https://sametime.example.com:8701/ibm/console Use your wasadmin account that was created during the install and password.
For more details refer to: http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_the_console_on_AIX_Linux_Solaris_or_Windows_st852
Install IBM Sametime Standard Community Server V.8.5.2
Install IBM Sametime Standard V8.5.2 Media Manager (~45 mins.)
su - (To login as root. It will not allow you install if you are not root.)
#cd <extracted Sametime Media Manager files>/SametimeMediaManager/IM/
#./install
Click Install (you can click file>preferences to ensure you have a repository selected)
Choose: I accept the terms in the license agreements
Next
Choose: Use existing WebSphere
Use Lotus Sametime System Console to install
Next
WAS Location>Use existing Location
SSC Login>
System console information
Hostname:foo.bar.com
Use SSL
HTTPS Port:
9443
User ID:
wasadmin
Pssword:
XXXXX
Enter the hostname of this computer:
foo.bar.com
Deployment Plan List>
Choose one we created earlier
Deployment Details>
Details of deployment we created.
Click Next.
Click Install.
Install IBM Sametime Standard V8.5.2 Meeting Server (~1 1/2 hrs)
su - (To login as root. It will not allow you install if you are not root.)
#cd <extracted Sametime Media Manager files>/SametimeMediaManager/IM/
#./install
Click Install (you can click file>preferences to ensure you have a repository selected)
Choose: I accept the terms in the license agreements
Next
Choose: Use existing WebSphere
Use Lotus Sametime System Console to install
Next
WAS Location>Use existing Location
SSC Login>
System console information
Hostname:foo.bar.com
Use SSL
HTTPS Port:
9443
User ID:
wasadmin
Pssword:
XXXXX
Enter the hostname of this computer:
foo.bar.com
Deployment Plan List>
Choose one we created earlier
Deployment Details>
Details of deployment we created.
Click Next.
Click Install.
Install IBM Sametime Standard V8.5.2 Proxy Server (~1 hr.)
In Sametime System Conole click:
Sametime System Console> Sametime Guided Activies>Install Sametime Proxy Server
Choose "Create a New Deployment Plan"
Click Next
Give it a name
Click Next
Choose Product Version 8.5.2
Click Next
Choose Primary Node
Click Next
Select the System Console
Click Next
Enter the Host name where the Proxy server will be installed
User ID: wasadmin
Password: xxxx
Confirm: xxxx
Click Next
Choose your Sametime COmmunity Server to connect to
Click Next
Click Finish
Log into Gnome as db2isnt1
Open a terminal and log-in as root:
su -
<password>
cd <extracted Proxy server install files>\IM\linux
#./install
Installation Manager will launch
Click Install
Choose Sametime Proxy Server
Click Next
Choose I accept the terms in the license agreements
Click Next
Choose "Use the existing package group"
Click Next
Ensure "Use Lotus Sametime System Console to Install" is selected.
Click Next
WAS Location>
"USe Sametime installed Websphere Application Server"
SSC Login>
Host Name: your Sametime system console server's FQDN
Use SSL selected
HTTPS Port: 9443
User ID: wasadmin
pasword: xxxx
Installation host name: where you're installing the software
Click Validate
Deployment Plan List>
Choose the plan you created in the SSC
Deployment Details>
Review your deployment summary
Click Next
Review the Install Summary
Click Install
Reboot Problems with Services:
# locate db2set
/home/db2inst1/sqllib/adm/db2set
/opt/ibm/db2/V9.7/adm/db2set
/opt/ibm/db2/V9.7/bin/db2setres
/opt/ibm/db2/V9.7_01/adm/db2set
/opt/ibm/db2/V9.7_01/bin/db2setres
/opt/ibm/sametime_installs/wser/db2setup
/opt/ibm/sametime_installs/wser/db2/linuxamd64/install/db2setup
/opt/ibm/sametime_installs/wser/db2/linuxamd64/install/db2setup_exec
/opt/ibm/sametime_installs/wser/nlpack/db2setup
/opt/ibm/sametime_installs/wser/nlpack/db2/linuxamd64/install/db2setup
/opt/ibm/sametime_installs/wser/nlpack/db2/linuxamd64/install/db2setup_exec
# /opt/ibm/db2/V9.7/adm/db2set
DB2SET processing complete, rc = 1302, SQLCODE = 0
# /opt/ibm/db2/V9.7_01/adm/db2set
DB2COMM=tcpip
# ./db2iauto -off db2inst1
# locate db2fmcu
/opt/ibm/db2/V9.7/bin/db2fmcu
/opt/ibm/db2/V9.7_01/bin/db2fmcu
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -d
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fm
db2fm db2fmcd db2fmcu db2fmd
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fm
db2fm db2fmcd db2fmcu db2fmd
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fmc
db2fmcd db2fmcu
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fmcd
# ./db2iauto -on db2inst1
# /opt/ibm/db2/V9.7_01/adm/db2set
DB2COMM=tcpip
DB2AUTOSTART=YES
# /opt/ibm/db2/V9.7/adm/db2set
DB2SET processing complete, rc = 1302, SQLCODE = 0
/opt/ibm/WebSphere/AppServer/bin/wasservice.sh -add STMediaServer_NA -serverName nodeagent -
profilePath /opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMSPNProfile1 -logRoot
/opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMSPNProfile1/logs/nodeagent -username domino -password
******
chkconfig --list | grep STMediaServer
to ensure you see the services for the appropriate run levels
/opt/ibm/WebSphere/AppServer/bin/wasservice.sh -add STMeetingServer_NA -serverName nodeagent -
profilePath /opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMPNProfile1 -logRoot
/opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMPNProfile1/logs/nodeagent -username domino -password *****
chkconfig --list | grep STMeetingServer
to ensure you see the services for the appropriate run levels
/opt/ibm/WebSphere/AppServer/bin/wasservice.sh -add STProxyServer_NA -serverName nodeagent -
profilePath /opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTPPNProfile1 -logRoot
/opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTPPNProfile1/logs/nodeagent -username domino -password
******
chkconfig --list | grep STProxyServer
to ensure you see the services for the appropriate run levels
Migrating Contact/Buddy Lists from Old Community Server
Start by replicating the vpuserinfo.nsf to your new server from the old Sametime server environment. If you are still setting up a test environment, then it's a great idea to create a push connection document from the old server to the new server to get any new updates to contact lists in the meantime.
If you are coming from a domino directory style community server (most likely) you will need to convert the vpuserinfo.nsf into the new LDAP format. To accomplish this you will need to create a Name Change task on the Sametime server.
...More to come on this soon.
Configuring Meeting Server to be used instead of classic Sametime Meetings
...More to come on this soon
Configuring Proxy Server
Proxy server enables mobile devices such as iOS (iphones) and Android to connect to the Sametime community.
...More to come on this soon
Upgrading to IFR1
Once you've got all of your Sametime Services up and running on 8.5.2 you're done with installations, right? Nope, there's lot's more work to be done. 8.5.2 has an interim fix release 1 out (IFR1). No need to worry, all of your upgrades should go smoothly on a fresh install...Not really, but we'll work through all the problems and short-comings.
Gather all the Installation Packages
Here's a listing of almost everything available.
The eAssembly Part is: CRG85ML
IBM Sametime System Console V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3Y8ML)
IBM Sametime Community Server V8.5.2 IFR 1 AIX, x86 Linux, Solaris Multilingual(CI3YAML)
IBM Sametime Media Manager V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YEML)
IBM Sametime Proxy Server V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YCML)
IBM Sametime Meeting Server V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YDML)
IBM Sametime Gateway Server V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YFML)
IBM Sametime Connect Client V8.5.2 IFR 1 Windows, x86 Linux, Mac Multilingual(CI3YGML)
su - (To login as root. It will not allow you install if you are not root.)
#cd <extracted Sametime Media Manager files>/SametimeMediaManager/IM/
#./install
Click Install (you can click file>preferences to ensure you have a repository selected)
Choose: I accept the terms in the license agreements
Next
Choose: Use existing WebSphere
Use Lotus Sametime System Console to install
Next
WAS Location>Use existing Location
SSC Login>
System console information
Hostname:foo.bar.com
Use SSL
HTTPS Port:
9443
User ID:
wasadmin
Pssword:
XXXXX
Enter the hostname of this computer:
foo.bar.com
Deployment Plan List>
Choose one we created earlier
Deployment Details>
Details of deployment we created.
Click Next.
Click Install.
Install IBM Sametime Standard V8.5.2 Proxy Server (~1 hr.)
In Sametime System Conole click:
Sametime System Console> Sametime Guided Activies>Install Sametime Proxy Server
Choose "Create a New Deployment Plan"
Click Next
Give it a name
Click Next
Choose Product Version 8.5.2
Click Next
Choose Primary Node
Click Next
Select the System Console
Click Next
Enter the Host name where the Proxy server will be installed
User ID: wasadmin
Password: xxxx
Confirm: xxxx
Click Next
Choose your Sametime COmmunity Server to connect to
Click Next
Click Finish
Log into Gnome as db2isnt1
Open a terminal and log-in as root:
su -
<password>
cd <extracted Proxy server install files>\IM\linux
#./install
Installation Manager will launch
Click Install
Choose Sametime Proxy Server
Click Next
Choose I accept the terms in the license agreements
Click Next
Choose "Use the existing package group"
Click Next
Ensure "Use Lotus Sametime System Console to Install" is selected.
Click Next
WAS Location>
"USe Sametime installed Websphere Application Server"
SSC Login>
Host Name: your Sametime system console server's FQDN
Use SSL selected
HTTPS Port: 9443
User ID: wasadmin
pasword: xxxx
Installation host name: where you're installing the software
Click Validate
Deployment Plan List>
Choose the plan you created in the SSC
Deployment Details>
Review your deployment summary
Click Next
Review the Install Summary
Click Install
Reboot Problems with Services:
- DB2 database not autostarting (fixed by logging in as dasusr1 and running ~/das/adm/dasauto -on) reboot to test:
# locate db2set
/home/db2inst1/sqllib/adm/db2set
/opt/ibm/db2/V9.7/adm/db2set
/opt/ibm/db2/V9.7/bin/db2setres
/opt/ibm/db2/V9.7_01/adm/db2set
/opt/ibm/db2/V9.7_01/bin/db2setres
/opt/ibm/sametime_installs/wser/db2setup
/opt/ibm/sametime_installs/wser/db2/linuxamd64/install/db2setup
/opt/ibm/sametime_installs/wser/db2/linuxamd64/install/db2setup_exec
/opt/ibm/sametime_installs/wser/nlpack/db2setup
/opt/ibm/sametime_installs/wser/nlpack/db2/linuxamd64/install/db2setup
/opt/ibm/sametime_installs/wser/nlpack/db2/linuxamd64/install/db2setup_exec
# /opt/ibm/db2/V9.7/adm/db2set
DB2SET processing complete, rc = 1302, SQLCODE = 0
# /opt/ibm/db2/V9.7_01/adm/db2set
DB2COMM=tcpip
# ./db2iauto -off db2inst1
# locate db2fmcu
/opt/ibm/db2/V9.7/bin/db2fmcu
/opt/ibm/db2/V9.7_01/bin/db2fmcu
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -d
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fm
db2fm db2fmcd db2fmcu db2fmd
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fm
db2fm db2fmcd db2fmcu db2fmd
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fmc
db2fmcd db2fmcu
# /opt/ibm/db2/V9.7_01/bin/db2fmcu -u -p /opt/ibm/db2/V9.7/bin/db2fmcd
# ./db2iauto -on db2inst1
# /opt/ibm/db2/V9.7_01/adm/db2set
DB2COMM=tcpip
DB2AUTOSTART=YES
# /opt/ibm/db2/V9.7/adm/db2set
DB2SET processing complete, rc = 1302, SQLCODE = 0
- System Console websphere app not autostarting although init scripts seem to be in place. Init scripts not working properly. It turned out the installers do not create node agent scripts as it should. You need to manually do this by using the wasservice.sh command. Here's how to do it:
- For Media Server:
/opt/ibm/WebSphere/AppServer/bin/wasservice.sh -add STMediaServer_NA -serverName nodeagent -
profilePath /opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMSPNProfile1 -logRoot
/opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMSPNProfile1/logs/nodeagent -username domino -password
******
chkconfig --list | grep STMediaServer
to ensure you see the services for the appropriate run levels
- For Meeting Server:
/opt/ibm/WebSphere/AppServer/bin/wasservice.sh -add STMeetingServer_NA -serverName nodeagent -
profilePath /opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMPNProfile1 -logRoot
/opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTMPNProfile1/logs/nodeagent -username domino -password *****
chkconfig --list | grep STMeetingServer
to ensure you see the services for the appropriate run levels
- For Proxy Server:
/opt/ibm/WebSphere/AppServer/bin/wasservice.sh -add STProxyServer_NA -serverName nodeagent -
profilePath /opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTPPNProfile1 -logRoot
/opt/ibm/WebSphere/AppServer/profiles/usfr-sameSTPPNProfile1/logs/nodeagent -username domino -password
******
chkconfig --list | grep STProxyServer
to ensure you see the services for the appropriate run levels
Start by replicating the vpuserinfo.nsf to your new server from the old Sametime server environment. If you are still setting up a test environment, then it's a great idea to create a push connection document from the old server to the new server to get any new updates to contact lists in the meantime.
If you are coming from a domino directory style community server (most likely) you will need to convert the vpuserinfo.nsf into the new LDAP format. To accomplish this you will need to create a Name Change task on the Sametime server.
...More to come on this soon.
Configuring Meeting Server to be used instead of classic Sametime Meetings
...More to come on this soon
Configuring Proxy Server
Proxy server enables mobile devices such as iOS (iphones) and Android to connect to the Sametime community.
...More to come on this soon
Upgrading to IFR1
Once you've got all of your Sametime Services up and running on 8.5.2 you're done with installations, right? Nope, there's lot's more work to be done. 8.5.2 has an interim fix release 1 out (IFR1). No need to worry, all of your upgrades should go smoothly on a fresh install...Not really, but we'll work through all the problems and short-comings.
Gather all the Installation Packages
Here's a listing of almost everything available.
The eAssembly Part is: CRG85ML
IBM Sametime System Console V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3Y8ML)
IBM Sametime Community Server V8.5.2 IFR 1 AIX, x86 Linux, Solaris Multilingual(CI3YAML)
IBM Sametime Media Manager V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YEML)
IBM Sametime Proxy Server V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YCML)
IBM Sametime Meeting Server V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YDML)
IBM Sametime Gateway Server V8.5.2 IFR 1 Windows, AIX, x86 Linux, Solaris, IBM i Multilingual(CI3YFML)
IBM Sametime Connect Client V8.5.2 IFR 1 Windows, x86 Linux, Mac Multilingual(CI3YGML)
No comments:
Post a Comment