Open mic IBM Sametime 9 limited use server

IBM Collaboration Solutions
23 September 2015
Open Mic : Sametime 9 Limited Use Server
Deployment

2 © 2015 IBM Corporation
Open Mic Team
• Kok Yen Feng – IBM ESS Support Manager
• Facilitator for Open Mics
• Hansraj Mali - IBM ESS Technical Expert
• Jayavel Rajendran - IBM ESS Technical Expert
• Ranjit Rai - IBM ESS Technical Expert
• Xiao Yang - IBM ESS Support Engineer
• Presenter
• Kee Ching Nam - IBM ESS Support Engineer
• Presenter
• Catherine Loh - IBM ESS Support Engineer
• Presenter

© 2015 IBM Corporation3
IBM Presentation Template Full Version
Agenda
 What is Sametime 9.0 Limited Use Entitlement?
 Major Community Server related changes to Sametime 9
 Upgrade to Sametime Limited Use 9
 Community Server deployment with native Domino directory
 Checklist for deploying Sametime Limited Use
 Required files for a deployment on Windows
 Sametime 9 Limited Use Installation walk through (Community
Server, SSC)
 Troubleshooting installation failure
 Open Q&A

What is Sametime 9.0 Limited Use Entitlement?
 The limited entitlement to IBM Sametime Entry software restricts its use to only
selected integrated instant messaging and presence awareness functions, and
only within the context of IBM Notes and Domino software.
 Who should attend this Open Mic:
- Target customers who purchase Domino/Notes licenses, but have not yet
deployed Sametime chat functions that comes together with the current licenses.
- You would be :
* An existing customer of Domino server and not yet deployed Sametime
components.
* Already running Sametime server of older version, but would like to upgrade to
the latest Sametime 9.0 server version.

Features Limited Use Standard
Instant Messaging Chat Y Y
Contact List Sorting Options Y Y
Online Presence status Y Y
Availability status icons Y Y
Set presence state and status message on
start-up
Y Y
Chat history Y Y
Rich text Y Y
Emoticons Y Y
Emoticon palettes Y Y
Business card display Y Y
Contact type ahead Y Y
Spell Check Y Y
Lotus Sametime Connect Client Y Y

Features Limited Use Standard
Access from Lotus Domino Web Mail
(DWA/iNotes)
Y Y
Integration with Microsoft Office or Sharepoint Y Y
Web conferences/Instant Meetings N Y
Lotus Sametime Gateway (Public IM federation) N Y
Mobile access (Lotus Sametime Mobile) N Y
Selective who can see me N Y
Selective do not disturb/privacy lists N Y
Send File (File Transfer) N Y
3rd party telephony (click-to-call or multi-way
video)
N Y
Voice and Video chat N Y
Screen Capture tool N Y

Major Community Server related changes to Sametime 9
 Sametime System Console (SSC) is now a mandatory component.
 ST 9 deployment with no SSC is not supported
 Legacy policies (stpolicy.nsf) are no longer supported
 Community Server that uses native Domino Directory can (and must) be
registered with SSC

Upgrade to Sametime Limited Use 9
 If older Community Server used legacy policies (stpolicy.nsf), the server is
automatically reconfigured during the upgrade to SSC policies.
 The previous policies should be manually entered in the SSC.
 If older Community server did not use SSC, it must be registered to SSC with the
registration script after the Community Server upgrade
 stconfig.nsf cannot be copied to ST9 server as is.

Community Server deployment with native Domino
directory
 While using native Domino Directory with the Community Sever is supported, it is
highly recommended that customers that want to use Domino Directory will use it
as Domino LDAP
 Community Server must be deployed without SSC and then be registered to the
SSC through a registration script
 SSC connects to the same Directory as Domino LDAP
 As another option SSC can connect to another Directory (like AD) and still be
registered with the Community Server. This creates a dual Directory deployment
which complicates the environment and has a number of limitations mostly related
group policies.

Checklist for deploying Sametime Limited
 Install and set up Sametime Community Server Limited Use.
 Prerequisites: Install DB2.
 Install Sametime System Console.
 (Optional) Install and set up Sametime Proxy Server for browser and web client
access.
 (Optional) Install Sametime Connect Clients for Sametime Limited Use.

Required files for a deployment on Windows
For a Windows installation you need to download these files from Passport
Advantage:
 CITN2ML IBM Sametime Community Server Limited Use V9.0 Windows
Multilingual
 CITN1ML IBM Sametime Connect Client Limited Use V9.0 Windows
 CIQ4CML IBM Sametime System Console Server V9.0 Windows
 CI6TYML IBM DB2 10.1 - Limited Use for Windows
 CIK2HML IBM WebSphere Application Server Network Deployment V8.5.5 (1 of
3)
 CIK2IML IBM WebSphere Application Server Network Deployment V8.5.5 (2 of 3)
 CIK2JMLIBM WebSphere Application Server Network Deployment V8.5.5 (3 of 3)
 CIQ6JML IBM WebSphere V8.5.5 iFixes for IBM Sametime V9.0 Windows
 CIL0DML IBM Installation Manager V1.6.2 for Windows x86_64 (required to install
WebSphere Application Server V8.5.5)

Sametime 9 Limited Use Installation walk through
Install and set up Sametime Community Server Limited Use.
 Navigate to the folder where you extracted the installation package Windows and
run setupwin32.exe.

 Select the language to use for the installation, and then click OK.

 At the Welcome screen, click Next.

 Accept the terms in the license agreement, and then click Next.

 Select either “Domino Directory” or “LDAP Server” depending on your system architecture.

 Choose whether to Enable HTTP Tunneling, and then click Next.

 Review the summary, and then click Install to start the installation.

 Click Finish to close the installation program.

 Start domino server. You should see Sametime Server running message in
domino console.

 Check windows services to make sure all sametime services are started
successfully.

 Launch Sametime embedded client to connect to Sametime Community Server
Limited Use to verify installation is successful.

 Verify user awareness is working.

DB2 Limited Use Installation
 Start the installation program by running setup.exe.

 Find DB2 Workgroup Server Edition Version 10.1 and click Install New.

 At the Welcome page, click Next.

 Select Install DB2 Workgroup Server Edition on this computer and click Next.

 For the installation directory, change the directory to the following C:IBMSQLLIB.

 Specify the following directory for the SSH Server installation. C:IBMIBM SSH
Server.

 Select “None” for Domain and specify User name and Password.

 Leave the default selection for Configure DB2 instances and click Next.

 Clear the checkbox for Set up your DB2 server to send notifications and click
Next.

 Select Enable operating system security and enter the following values. Click
Next.

 Review the summary, then click Install to start the installation.

 Installing DB2 in progress...

 When installation is complete, click Finish.

Install IBM Installation Manager
 Navigate to the folder where you extracted Installation Manager.

 Verify that Installation Manager > Version 1.6.2 is selected, and then click Next.

 Accept the terms in the license agreement, and then click Next.

 On the Location page, specify the installation directory and click Next.

 When installation is complete, ensure there is a green check mark next to the text
"The packages are installed." Ensure there is no error message.
 Click Restart Installation Manager.

WebSphere Application Server Installation
 Extract the contents of downloaded packages to the same folder as shown below

 Start IBM Installation Manager.

 In the Installation Manager window, click File > Preferences > Repositories.
 Click the repository.config file to select it, and then click OK.

 Back in the main Installation Manager Windows, click Install.

 Select the IBM Websphere Application Server Network Deployment 8.5.5 and click
Next.

 Accept the terms in the license agreements, and click Next.

 Verify or correct the shared resources directory, and click Next.

 Verify or correct the installation directory.

 Accept English as the language, and click Next.

 Select the feature set to install, and then click Next.
 Verify that IBM 64-bit WebSphere SDK for Java is selected. Do not select IBM 32-
bit WebSphere SDK for Java.

 Review the summary information, and click Install.

 Installation in progress....

 At the end of the installation, click None when prompted to select a profile.
configuration tool, and then click Finish.

Install WebSphere Application Server Fixes
 Use the same procedure to add the repository for each WebSphere Application
Server interim fix. Be sure to do this for every fix in the package as shown below.

 Back in the main Installation Manager window, click update.

 Click Next.

 Review the update package summary information, and click update.

 When the update is complete, click Finish, close Installation Manager by clicking
File > Exit.

Creating a database for the Sametime System Console
 Open a command window, Navigate to the DatabaseScriptsSystemConsole folder.
 Create the database by running the command: createSCDb.bat STSC db2admin

 The window will remain blank for several minutes. Do not close the window.

 Wait until you see confirmation that the database has been created and the
command has finished.

 Verify that the new database was created by entering the following command:
db2 connect to STSC
 Verify that you can connect to the database STSC.

Install Sametime System Console
 Start the installation program by running launchpad.exe.

 Select "Install IBM Sametime System Console".

 Select "launch IBM Sametime System Console 9.0.0 Installation".

 Installation Manager will be launched and click “Install”.

 Click Next.

 Accept the terms in the license agreements, and click Next.

 On the Install Packages window, verify that the path is accurate in the Installation
Directory field.

 Select IBM Sametime System Console, Version 9.x as the feature to install and
click Next.

 Specify the location of the WebSphere Application Server and then click Validate.

 When the button label changes to Validated, click Next.

 Verify the cell, node, and input Fully Qualified Host Name of SSC.
 Create the WebSphere Application Server administrator account by supplying the
user name and password. Click Next.

 Provide Database Name STSC, Application user ID and password. Click Validate.

 Review the summary, then click Install to start the installation.

 When installation is complete, ensure there is a green check mark next to the text
"The packages are installed." Ensure there is no error message. click Finish.

Sametime Prerequisite: Connect to LDAP Servers
 Connect to LDAP Server.
 Log in to SSC Dmgr using wasadmin/password.
 URL: http://st9lu.renovations.com:8700/ibm/console

 In the Connect to LDAP Servers guided activity, click Add.

 Provide LDAP bind settings, and then click Next.

 Provide the base distinguished name and filter for use when searching the LDAP
directory, leave it blank if you use an IBM Domino LDAP directory.
 Click Next.

 Review the LDAP Configuration Summary, and click Finish to connect to the
LDAP server.

 you will get message "AIDSC1852I: The System Console LDAP Configuration has
been updated. Restart the System Console Deployment Manager for the changes
to take effect".
 Restart the Deployment Manager, Nodeagent and Sametime System Console to
complete the LDAP federation process.

Increasing the heap size on the Sametime System Console
 Login to WebSphere Integrated Solutions Console, Select System Administration
> Deployment Manager > Java and Process Management > Process Definition.
 Additional properties > click Java Virtual Machine.
 In the Maximum Heap Size field, type 2048 as the new maximum heap size.
 Click OK.

 Click Preferences.
 Select Synchronize changes with Nodes.
 Click Apply.
 Click the Save link in the "Messages" box at the beginning of the page Restart
WebSphere Application Server.

 After synchronization has completed, click OK.

Registering Sametime Community Server with SSC
 Navigate to the Community Server's Sametime console directory. Make backup
copies of the console.properties and productConfig.properties files.

 Update the following values in the console.properties file: SSCHostName,
SSCUserName and SSCPassword.
 Save and close the file.

 Update the following values in the productConfig.properties : DepName and
NodeHostName and save the file.

 Run registerSTServerNode.bat at Dominoconsole folder.
 As the registration utility runs, you will be prompted to enter the following
information: location of notes.ini, Domino administrator user name and password.

 Restart the Sametime Community Server and Verify Registration to SSC.

 Test Chat via Notes client & ST connect client.
 File transfer & screen capture options are greyed out as working as designed for
limited use version.

Troubleshooting installation failure
 Setting up the Sametime System Console database manually
To install the IBM® Sametime® System Console server, the DB2® application user
ID must have administrator rights to be able to create and update tables in the
database. If the user does not have administrator rights create the tables manually
before installing the Sametime System Console.
Procedure
- Start the DB2 command window by running the following command:
AIX® or Linux: db2
Windows: db2cmd
- Connect to the System Console database by running the following command:
AIX or Linux: db2 connect to STSC
Windows: db2 connect to STSC
- Create the createSchedTable by running the following command: db2 -tf
createSchedTable.ddl
Close the DB2 command window.

 Unregistering a Sametime Community Server
This step is required before uninstalling a Community Server that you installed
without a deployment plan and then registered with the Sametime System Console
later using the registration utility.
Before you begin
The Sametime System Console must be started.
About this task
During this task you will edit the following files; click the topic titles to see details on
each file. You may want to open each topic in a new browser tab or window so you
can keep it open for reference:
console.properties
productConfig.properties

 Unregistering a Sametime Community Server Cont...
Procedure
1. Back up the console.properties and productConfig.properties files:
Navigate to the Community Server's Sametime console directory:
AIX®, Linux: The console directory is in the Community Server data
directory; for example: /opt/IBM/domino85/notesdata/console
Windows: The console directory is in the Domino® directory; for example:
C:LotusDominoconsole
Make backup copies (using different names) of the console.properties and
productConfig.properties files.

 Unregistering a Sametime Community Server Cont..
2. Update the following values in the console.properties file and save the file.
Property Value
SSCHostName Provide the fully qualified host name of the Sametime
System Console server.
SSCHTTPPort Specify the HTTP port used for the Sametime System
Console server if SSL is not enabled and the value for
SSCSSLEnabled is "false."
To determine the correct HTTP port, open the
AboutThisProfile.txt file for the Sametime System Console
Application Server Profile and use the setting specified for
the "HTTP transport port." The default profile name is
STSCAppProfile.
For example, on Windows the file is stored at:
C:/IBM/WebSphere/AppServer/profiles/AppServerProfile/l
ogs/AboutThisProfile.txt

Property Value
SSCUserName Enter the IBM WebSphere® Application Server User ID
that you created when you installed Sametime System
Console. The default is wasadmin
SSCPassword Enter the WebSphere Application Server password
associated with the SSCUserName.
SSCSSLEnabled Change this value to "true" to connect to the Sametime
System Console using a secure connection.
SSCHTTPSPort Specify the HTTPS port used by the Sametime System
Console server if SSCSSLEnabled is set to "true."

3. Verify that the settings in the productConfig.properties file are correct, modifying
them as needed before saving and closing the file.
Only the required values in this file are listed here:
Property Value
DepName The Dep Name must be the name that was used when
you installed: the unique name for this deployment as
known by the Sametime System Console.
NodeHostName Provide the fully qualified host name for the Community
Server that is being unregistered.

4. Start the Sametime Community Server.
5. Now unregister the server:
a. Run the unregister utility with the following command:
AIX, Linux: unregisterProductNode.sh
Windows: unregisterProductNode.bat
b. As the unregister utility runs, you will be prompted enter the Location of the
notes.ini file. You are only prompted for the notes.ini file location when unregistering
the server. Type the full path to the directory containing the notes.ini file (for
example, /stserver/data), and press Enter.
The utility unregisters the server, generating a log file called ConsoleUtility.log and
storing it in the console/logs directory. If the unregistration is successful, the
console.pid will be removed.

Troubleshooting Login failure
Error Message: “Login Failure....Not Authorized...”
Resolution:
- Need configure allowed client types
Edit sametime.ini file and append Notes 9.0 and above Client Ids
(1246 &1247) to the VP_ALLOWED_LOGIN_TYPES field.
Restart Sametime Server for settings to take effect
- See technote 1114318 for more details:
http://www-01.ibm.com/support/docview.wss?uid=21114318

References
 Deploying Sametime Limited Use
http://www-01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/admin/install/inst_deploy_stlu_intro.html
 Policy differences with Sametime Limited Use
http://www-
01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/admin/install/inst_stlu_unsupported_policies.dita
 Configuration step required for Sametime Community Server & Stand alone Mux on Microsoft™
Windows™ Server 2008
http://www-01.ibm.com/support/docview.wss?uid=swg21441275
 Troubleshooting installation or uninstallation
http://www-
01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/admin/install/inst_uninst_troubleshooting.html?
lang=en
 Troubleshooting a Sametime Community Server
http://www-01.ibm.com/support/knowledgecenter/SSKTXQ_9.0.0/admin/trouble/st_adm_intro_troubleshooting_r.html

Questions?
Press *1 on your telephone to ask a question.
Visit our Support Technical Exchange page or our Facebook page
for details on future events.
To help shape the future of IBM software, take this quality survey
and share your opinion of IBM software used within your
organization: https://ibm.biz/BdxqB2
IBM Collaboration Solutions Support page
http://www.facebook.com/IBMLotusSupport
IBM Collaboration Solutions Support
http://twitter.com/IBM_ICSSupport

Open mic IBM Sametime 9 limited use server

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Open mic IBM Sametime 9 limited use server

Ähnlich wie Open mic IBM Sametime 9 limited use server (20)

Mehr von Ranjit Rai

Mehr von Ranjit Rai (14)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Open mic IBM Sametime 9 limited use server