Open Mic - IBM Sametime Proxy Clustering

IBM Collaboration Solutions

Open MicDate: 24-08-2017

IBM Sametime Proxy Server & Web Client – Tips and Tricks

IBM Corporation ©20172

Open Mic Team

● Jayesh Parmar - IBM Advisory Software Engineer● Presenter

● Ranjit Rai - IBM - SWAT● Focusing on entire Notes/Domino/Traveler/Sametime/Connections/Cloud

● Jayavel Rajendran – IBM - SWAT ● Focusing on entire Notes/Domino/Traveler/Sametime/Connections/Cloud

● Vinayak Tavargeri - IBM Senior Manager and facilitator for Open Mics


➢ IBM Sametime Proxy Server & its features:-

➢ IBM Sametime Proxy Server Installation (Primary & Secondary Node)

➢ Clustering Sametime Proxy Servers

➢ Things to remember while installing Sametime Proxy Server through SSC

➢ Tips & Tricks

➢ References

➢ Questions

Agenda Items:-


IBM Sametime Proxy Server & its features:-

IBM Sametime Proxy Server

→ enables browser-based clients to participate in Sametime instant messaging and online meetings

→ works with Sametime Community Server or IBM Connections to enable the business card feature

→ provides rich presence and chat over the web, and also is the Android and iOS mobile chat clients

→ provides live names awareness

→ is required to provide awareness in the Sametime Meeting room, and is required for web A/V

→ helps Hybrid cloud customers to integrate the cloud sametime with on-premises sametime for presence awareness


IBM Sametime Proxy Server 9.0.1 Installation (Primary Node):-

What is required before you start installing Proxy Server:

● IBM Websphere Application Server 8.5.5.8● IBM Sametime 9.0.1 System Console Server● IBM DB2 9.7/10.1/10.5● IBM Sametime community server 9.0.1

Part Numbers: IBM Sametime 9.0.1 Complete

http://www-01.ibm.com/support/docview.wss?uid=swg24041255

Steps:

→ Creating a database for the Sametime Proxy Server→ Setting up the Connect to DB2 Databases prerequisite for Sametime Proxy Server→ Setting up the Install Sametime Proxy Server guided activity→ Installing a Sametime Proxy Server→ Adding a Sametime Proxy Server to the Sametime Community Server’s trusted IP addresses→ Verifying a Sametime Proxy Server installation



1. Creating a database for the Sametime Proxy Server

→ Before installing the IBM Sametime Proxy Server, create a database to store its data.

→ Extract SametimeProxyServer.zip to C:\temp . Open an admin command prompt, and navigate to the \SametimeProxyServer\DatabaseScripts\ProxyServer directory, and run the command to create the Proxy database called STPS: createProxyDB.bat STPS db2admin



2. Setting up the Connect to DB2 Databases prerequisite for Sametime Proxy Server

→ Open the IBM Sametime System Console and start the Connect to DB2 Databases prerequisite activity.

→ Connect the DB2 database in SSC – Login as wasadmin in WAS and under Sametime System Console → Sametime Prerequisites → Connect to DB2 Databases you will see the previously created STSC database used for System Console. Push Add. The DB2 host name = db2serverFQDN, port = 50000 the name of the Sametime Proxy database example: STPS, user credentials = xxxxxx Leave IBM i unchecked, and hit Finish. If the SSC can connect to the database successfully, it will return.



3. Setting up the Install Sametime Proxy Server guided activity

→ Open the IBM Sametime System Console and start the Install Sametime Proxy Server guided activity.

→ Create a New Deployment Plan, specify a name such as “Sametime 9.0.1 Proxy Server”, and choose 9.0.1, However since this is a WebSphere product, we must choose between a Primary Node, Secondary Node, or a Cell deployment of the Proxy server.

→ If this was the second server in a cluster, we'd choose secondary node. If this was a stand alone WebSphere server that was NOT going to use an existing WAS deployment manager, we would choose cell. However, since we are using the System Console as our WAS deployment manager, and this is the first Proxy server in our deployment, we will choosePrimary Node. Click Next.

→ Note, even if we were deploying the Proxy server on a separate box, we'd still choose Primary Node and use the deployment manager remotely – WebSphere would handle those connections for us.







4. Installing a Sametime Proxy Server

→ Run the installation program to set up the Sametime Proxy Server.

→ In the Installation Manager window, click File > Preferences > click Repositories

→ Add the repository for the Sametime Proxy package:On the Repositories page, click Add Repository.

→ Select Sametime Proxy Server, and open the STProxy subdirectory Click the repository.config file to select it, and then click Apply.

Note: Deselect any listed repositories that you will not use for installing the Sametime Proxy Server. Click OK.

→ Back in the main Installation Manager window, click Install.









Note:

→ On machine where the IBM Sametime Proxy Server is being installed, it should have WAS installed on it as a pre-requisite.

→ Without WAS, the configuration step of Validation will fail

→ The location of WAS should be entered and Validated to proceed further











→ Let's create startProxy.bat & stopProxy.bat – note the path names may be slightly different:

startProxy.bat

@echo off time /t call "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\startNode.bat" call "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\startServer.bat" STProxyServer time /t call pause

stopProxy.bat

@echo off time /t call "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\stopServer.bat" STProxyServer -username wasadmin -password passwordcall "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\stopNode.bat" -username wasadmin -password passwordtime /t call pause



5. Adding a Sametime Proxy Server to the Sametime Community Server’s trusted IP addresses

→ Whenever you install an IBM Sametime server that communicates with a Sametime Community Server, you must add the new server's IP address to the Community Server's list of trusted IP addresses.

→ To add proxy server IP address to trusted field:a. Go to Sametime System Console > Sametime Servers > Sametime Community Servers.b. In the Sametime Community Servers list, click name of Community Server that you want to update.3. Click the Connectivity tab. In the Trusted Servers section, locate the New IP Address



6. Verifying a Sametime Proxy Server installation→ Open the IBM Sametime browser-based client to verify the installation of a primary node was successful.


IBM Sametime Proxy Server 9.0.1 Installation (Secondary Node):-

→ To cluster the Sametime Proxy Server, We have to install the Sametime Proxy Server on secondary node

→ Create another deployment plan same as earlier. Refer the below capture

→ This time, you have to select Secondary Node. The Host should be reachable at time when you create deployment plan


IBM Sametime Proxy Server 9.0.1 Installation (Secondary Node):-

→ The installation steps remains same. The WAS needs to be installed in the machine where you are going to install the Sametime proxy Server.

→ Only difference is the Install Type Here. We select SN Secondary Node here to cluster the proxy server

Note: Not all screen captures are included here as the installation steps remains same for secondary node


Clustering Sametime Proxy Server:-

→ Install the first Sametime Proxy Server using the Primary Node profile, and then install one or more additional Sametime Proxy Servers using the Secondary Node profile.

→ Synchronize the system clocks on the Sametime Proxy servers to be clustered

→ Use the IBM Sametime System Console to create a cluster of Sametime Servers hosted on IBM WebSphere Application Server.

→ A vertical cluster consists of multiple members of the same product cluster installed on a single computer.

→ A horizontal cluster consists of multiple members of the same product cluster with each installed on a separate computer

→ Setting up load balancing for clustered Sametime Proxy Servers. Install a load balancer in front of a cluster of IBM Sametime servers to distribute connections among the servers.

Note: Here in the slides, we have covered the Horizontal Cluster


Clustering Sametime Proxy Servers:-

→ Till now, we installed first Sametime Proxy Server using the Primary Node profile, and then installed one or more additional Sametime Proxy Servers using the Secondary Node profile.

→ Configuring a cluster of IBM Sametime Proxy Servers involves several tasks, including synchronizing system clocks, configuring the cluster settings, and optionally deploying an IBM Load Balancer in front of the cluster.

→ For each server that will be added to the cluster, set the system clock to exactly the same time as the deployment manager's (the Sametime System Console) system clock.

→ In WAS, Sametime System Console, click on Cluster WebSphere Application Servers. Click Next to begin the clustering activity.



→ Select the product server to cluster, and then click Next.

→ The list only displays Sametime products for which one or more servers have been installed and registered with the Sametime System Console

→ To create a cluster: Click Create Cluster if you are setting up a new cluster. To modify an existing cluster; for example, to add a new cluster member: Click Select Existing Cluster. Select a cluster in the Cluster Name list.

→ Provide descriptive name for new cluster. Here we gave NewCuster



→ Select the deployment manager. select the Sametime System Console as the cluster's deployment manager, and then click Next.Note: Every cluster must have exactly one deployment manager; the Sametime System Console can function as the deployment manager for multiple clusters.

→ Create the Cluster with the primary node. You created and federated a primary node when you installed the first server for this product. Make sure that the primary node's application server is running. Click Create cluster to configure the cluster settings, and then click Next.Do not click anywhere on the browser until the operation completes or it may interrupt the clustering process.



→ Select One or More Secondary Nodes.

Note:If you are creating a horizontal cluster where each node is hosted on a separate computer, add one or more secondary nodes to the cluster. You created and federated the secondary nodes when you installed them. In the secondary node Name list, click the node you want to add to the cluster and click Next.



→ Add Cluster Members. If you are creating a vertical cluster where multiple copies of the application are hosted on a single computer, add one or more "cluster members" to the primary node. If you are creating a horizontal cluster, add one cluster member to each of the secondary nodes you federated in the previous step.

→ Here, we presented Horizontal cluster:

→ One at a time, select each cluster member and click Add to Cluster.

Note: Do not proceed until the current cluster member's status changes from "Ready to cluster" to "Clustered," then you can add the next cluster member. If you want to add more cluster members, click New to add another row to the table, and then fill out the information accordingly.Click Next.





→ Stop the deployment manager:Click System Administration > Deployment manager.Click the "Configuration" tab.On the Configuration tab of the deployment manager settings, click Stop.

→ Now start the deployment manager:Open a command window and navigate to the was_install_root/profiles/DeploymentManagerName/bin directory.Run the following command:

Microsoft WindowsstartManager.bat

→ In the deployment manager's Integrated Solutions Console, click System Administration > Nodes. Select all nodes in the cluster. Click Full Resynchronize.



→ Restart all nodes in the cluster:In the deployment manager's Integrated Solutions Console, click System Administration > Node agents.Click a node agent, and then click Restart (the node agent should already be running).Wait until the nodes have all started before proceeding to another task.

→ Log in to the Deployment Manager's (the Sametime System Console) Integrated Solutions Console as the WebSphere administrator.Click Servers > Clusters > WebSphere application server clusters in the navigation tree.Select the cluster's check box and click Start to start all cluster member servers.




Things to remember while installing the Sametime Proxy Server through SSC:-

→ Adding a Sametime Proxy Server to the Sametime Community Server’s trusted IP addresses.

→ The Community Server accepts connections from the Sametime Proxy Server. To ensure that the Sametime Community Server trusts this server when it establish a connection, you must add the IP addresses to the Community Server.


→ STProxy doesn't communicate directly with LDAP, it communicates with the Sametime Community server, which in turn communicates with the LDAP directory.

→ The Community server provides service to the Proxy server. Refer the below “Show task” command capture.

→ The servers should be able to ping each other over FQDN.

→ All Sametime servers should be able to communicate with community server on port 1516

> All Sametime Servers have the same security level. This is configured using VP_SECURITY_LEVEL in the sametime.ini.



→ All Sametime Servers have the same case sensitivity value. This is configured using AWARENESS_CASE_SENSITIVE in the sametime.ini, and the recommended value is 0, means case insensitive.

→ If you have multiple community server then make sure the proper community server has been added to the field in "List of Sametime Community Server cluster names".



Tips & Tricks Sametime Proxy Server:-

→ In Security → Global Security → Web and SIP security → Single sign-on (SSO), see if all fields are appropriately set.



→ In WAS, go to Global Security → LTPA. You can export the key and import in Community Server “Web Configurations” → “Web SSO Configuration for LtpaToken”



→ In WAS, Go to Troubleshooting → Logs and trace → STProxyServer → Diagnostic Trace → Change log detail levels.

→ Click the Configuration tab if you want to save the changes after a server restart.→ Click the Runtime tab to make changes that are not saved & will apply until the server is restarted.

Tip: If you make changes on the Runtime tab, and then decide you want to preserve your changes after a server restart, select Save runtime changes to configuration as well



→ Check the STProxyDataSource connection and see, if it is successfully connected



→ Ensure user name and password is valid

→ Ensure that community server and proxy server are able to trace each other over FQDN

→ Check whether Sametime Proxy IP address is trusted

→ Check the SSO configuration and see if it is working. The Token Format in the Web SSO document (names.nsf) must include both Ltpatoken and LtpaToken2 when Interoperability mode is enabled (located in the WAS settings).

→ Check VPS_ALLOWED_LOGIN_TYPES parameter in sametime.ini

→ Check the Directory Assistance configuration

→ LDAP server should be reachable. STProxy doesn't communicate directly with LDAP, it communicates with the Sametime Community server, which in turn communicates with the LDAP directory.


Flavor= IMWC translates to Instant Messaging Web CommunityFlavor=IMLU translates to Instant Messaging Limited Use

→ Sametime Proxy may not initially work with IMLU, Flavor is found in the buildinfo.txt of the CS.Here are other ways to check: Sametime.ini

Limited Use:ST_BRANDING_INFO=entryIMOnly=1VPS_ALLOWED_LOGIN_TYPES= (does NOT list proxy devices!)

Standard:ST_BRANDING_INFO=standardIMOnly=0

→ SSO debug for community server:

set config LDAPDEBUG=7set config Debug_SSO_Trace_Level=2set config webauth_verbose_trace=1



References :

→ Error: Prompt "Guest log in is not allowed, please use a valid user name and password." seen when user tries to login in IBM Sametime Web Chat:http://www-01.ibm.com/support/docview.wss?uid=swg21991761

→ SSO Configuration Steps:https://www.ibm.com/support/knowledgecenter/SSKTXQ_9.0.1/admin/config/config_sso_commsvr_importkeys.html

→ Recommended trace settings:http://www.ibm.com/support/knowledgecenter/SSKTXQ_9.0.1/admin/trouble/trbl_recommended_trace_settings.html

→ Table of Client types that are connecting to a Sametime server:http://www-01.ibm.com/support/docview.wss?uid=swg21114318

→ IBM Sametime 9.0.1 Complete (part numbers):http://www-01.ibm.com/support/docview.wss?uid=swg24041255

→ InstallingSametime Proxy Server:https://www.ibm.com/support/knowledgecenter/SSKTXQ_9.0.1/admin/install/inst_prox.html


https://www.ibm.com/support/knowledgecenter/SSKTXQ_9.0.1/admin/config/config_sso_commsvr_importkeys.html

http://www.ibm.com/support/knowledgecenter/SSKTXQ_9.0.1/admin/trouble/trbl_recommended_trace_settings.html



https://www.ibm.com/support/knowledgecenter/SSKTXQ_9.0.1/admin/install/inst_prox.html


Questions?

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 Supporthttp://twitter.com/IBM_ICSSupport

http://www.ibm.com/support/entry/portal/scheduled_tech_exchanges/lotus/lotus_brand_support_(general)

https://www.facebook.com/IBMLotusSupport

https://ibm.biz/BdxqB2

http://www.facebook.com/IBMLotusSupport

http://twitter.com/IBM_ICSSupport

Date post:	22-Jan-2018
Category:	Technology
Upload:	jayeshpar2006
View:	257 times
Download:	1 times

Open Mic - IBM Sametime Proxy Clustering

Technology