Tips for Using the Integrated Solution Console (ISC) and Sametime System Console (SSC) with IBM Sametime

Tips for Using the Integrated Solution Console (ISC) and Sametime System Console (SSC) with IBM Sametime October 28, 2015 Miguel Macias, Sandy Lee, Casey Toole IBM Corporation 2015 1

Agenda Integrated Solution Console vs. Sametime System Console Versions and Hotfixes Common Db2 Issues Expired license Wrong version Testing data source connectivity Changing Password DB2 WAS Admin vs SSC Admin Virtual Hosts and Ports Policies Troubleshooting Synchronizing Nodes GUI and command line Changing historical files Runtime vs Configuration mode for debugging IBM Corporation 2015 2

Integrated Solution Console vs Sametime System Console Integrated Solution Console (ISC) Use to view and configure WebSphere settings, you use the web-based administrative console. Provide a consistent and integrated capability for administering IBM software. The ISC enables you to access settings related to key areas of server administration, including: Servers, Applications, Security, Environment, Users and Groups, Monitoring, Tuning and Logging Sametime System Console (SSC) Used to install, administer, and configure other Sametime servers. Sametime System Console is installed into the Integrated Solution Console. IBM Corporation 2015 4

How to Identify Versions and Hotfixes Installed Log into the Integrated Solution Console or the Sametime System Console and click on Welcome to find the versions. IBM Corporation 2015 6

How to Identify Versions and Hotfixes Installed 1. Go to Integrated Solution Console. 2. Click on Applications - Application Types - WebSphere Enterprise Application IBM Corporation 2015 7

How to Identify Versions and Hotfixes Installed 3. One at a time, select each application type and then click Application Binaries Sametime System Console -> deployment.ear Sametime Proxy Server -> SametimeProxy Sametime Meeting Server -> Sametime Meeting Server Sametime Media Manager -> ConferenceFocus Example for finding the SSC version: IBM Corporation 2015 8

Common DB2 Issues Expired License: DB2 - DB2COPY1 Fails To Start in the Sametime Environment ( https://ibm.biz/bdhryu ) From command line / terminal: db2cmd ; db2licm -l Expiry date: Expired Apply license included with Sametime 9.0 download of DB2 using: db2licm -a <license_file> e.g. c:\>db2licm -a D:\st9\WSER\image\db2\license\db2wse_o.lic Wrong Version: If you installed a different product of DB2 other than Workstation Server Edition You will need to uninstall DB2 and install the Workstation product of DB2 then apply the license file as described above. You can not downgrade a DB2 license only upgrade to a higher level. Testing a connection with the administrative console ( https://ibm.biz/bdhrmi ) IBM Corporation 2015 10

1 3 2 4

Updating the DB2 admin password Update the password for each data source Restart the environment starting with the DM, SSC, other servers IBM Corporation 2015 13

Updating the DB2 admin password (cont) IBM Corporation 2015 14

Updating the DB admin password (cont) Repeat ==> IBM Corporation 2015 15

Updating WebSphere Application Server administrator password Vs Updating the System Console administrator password Updating WebSphere Application Server administrator password ( https://ibm.biz/bdhruj ) Change the password using Users and Groups > Manage Users Update SSC with new password of the server's password you changed e.g. Media Manager, Meeting Server, Sametime Proxy Server, Gateway, etc. Updating the System Console administrator password ( https://ibm.biz/bdhruv ) Change the password using Users and Groups > Manage Users Unregister SSC copy unregisterwasproduct.sh/bat from other WAS based Sametime server and run it Register SSC update console.properties and productconfig.properties with new password and run registerproduct.sh/bat This is needed to update the SSC Admin ( WAS Admin ) password stored in DB2

Changing WAS Admin Password The user ID and password that you enter during installation are considered to be the WAS Administrator ID and password for the site. To secure your Sametime deployment, you may want to periodically change the WAS administrator password. After you change the password for the WebSphere Application Server(s) you change the Sametime System Console password. IBM Corporation 2015 17

Changing WAS Admin Password Step 1: Update the password on the WebSphere Application Server: a) Log in to the Integrated Solutions Console for the Sametime System Console. b) Click Users and Groups > Manage Users. c) In the "Search for Users" section, select User ID in the Search by field, and then type the WebSphere Application Server administrator user name in the Search for field; then click Search. d) In the results dialog box, click the user name to select it. e) Type a new password in the Password and Confirm Password fields. f) Click OK. g) Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page. IBM Corporation 2015 18

Changing WAS Admin Password (cont) IBM Corporation 2015 19

Changing WAS Admin Password (cont) IBM Corporation 2015 20

Changing WAS Admin Password (cont) Step 2: Update the Sametime System Console with the new password for each Sametime Server: a) Log in to the Integrated Solutions Console for the Sametime System Console. b) Click Sametime System Console > Sametime Servers. c) In the list of servers, click the name of the server that has the administrator password that you changed in Step 1. d) Locate the deployment name and click Edit in the Connection Properties section. e) Type a new password, making sure to spell it exactly as you did on the other server. f) Click Save and then click Done. IBM Corporation 2015 21

Changing WAS Admin Password (cont) IBM Corporation 2015 22

Virtual Hosts and Ports Custom virtual host tables and mapping them to specific server applications. Needed if there is more than one type of cluster - e.g Sametime Proxy and Sametime Meetings ( https://ibm.biz/bdhfpq ) Some of the issues resolved/prevented: When Sametime Advanced is federated to the same cell as Sametime Meetings, users have multiple issues attending meetings ( https://ibm.biz/bdhrp5 ) WebSphere Application Server (WAS) proxy will sometimes route internal requests to the wrong node This is due to an internal URI conflict and mapping of both applications to the default virtual host. WebSphere Proxy redirects to Sametime Proxy unexpectedly ( https://ibm.biz/bdhrys ) Unable to Initialize Framework Errors when using the Sametime System Console ( https://ibm.biz/bdhryy ) caused by the SSCConnector application being incorrectly mapped to the wrong application server IBM Corporation 2015 24

Virtual Hosts and Ports (cont) IBM Corporation 2015 25

Virtual Hosts and Ports (cont) IBM Corporation 2015 26

Virtual Hosts and Ports (cont) IBM Corporation 2015 27

Virtual Hosts and Ports (cont) Make sure there are no conflicting default_host entries for a port: In the navigation pane, click Environment > Virtual hosts. In the list of virtual hosts, click default_host. In the Additional Properties section, click Host Aliases. Remove all aliases that map to the fully qualified host names and ports you just added to the stmeetings_host. IBM Corporation 2015 28

Virtual Hosts and Ports (cont) IBM Corporation 2015 29

Virtual Hosts and Ports (cont) Re-synchronize all nodes in the cluster by completing the procedure Synchronizing and restarting nodes in the cluster. IBM Corporation 2015 30

Virtual Hosts and Ports Think about ports up front This is why you can find information about ports in our planning section https://ibm.biz/bdxqn7 Issues related to Ports ISC Server Status Status shows a green arrow if the server is running, a red cross if the server is stopped, and a question mark in a circle if the node agent for the server is stopped which prevents the ISC from querying the server status. A question mark also shows if the ISC has problems reaching the server, usually due to DNS or firewall (closed port) issues. Failed registration Correct SSC Port Values should be entered in console.properties before running the SSC registration Utility (https://ibm.biz/bdhry4 ) Keep in mind, when you federate a node to a cluster, it's ports will usually be incremented by 1 e.g. 9080 will become 9081 When clustering is competed, confirm all cluster members are listening on the correct ports IBM Corporation 2015 31

Virtual Hosts and Ports (cont) Resource: My go to resource is a presentation snipped from a large one shared with me by Tony Payne I blogged about it and shared it here (https://ibm.biz/bdhich ) Here is a direct link to the file ( https://ibm.biz/bdhiyk ) IBM Corporation 2015 32

Manage Policies Sametime policies control user access to features. All users are assigned to the default policy settings which administrator can modify. Additional user policies can be created and you can assign users and groups to these new policies. Unauthenticated users will have the Anonymous Policy applied to them. Policies are grouped based on the following features: Instant messaging (chat, image settings, file transfer, plug-in management, and mobile features provided by the Sametime Community Server and Sametime Proxy Server) Meetings (conferencing features provided by Sametime Meeting Server) Media Manager (audio and video features provided by Sametime Media Manager, VoIP feature provided by Sametime Media Manager) IBM Corporation 2015 34

Manage Policies (cont) To edit Policy setting for Nested groups and caching, click Edit Policy Settings. For performance reasons we don't recommend going further than 4 deep. To view the Policies currently in use for a particular user, click Find Active Policies. All unauthenticated users will have the Anonymous Policy applied to them. Authenticated users the policy engine will search for an exact user ID match, and then apply the highest weighted policy. If there is no match for the user ID in any policy, then the policy engine will apply the highest weighted group match. If no group matches are found, then the Default policy will be applied. Community Server retrieves policies from System Console and caches them to \domino\policies.user.xml. Media Manager policies are received by the client through the community server. System Console and Meeting Server directly access the policy database. IBM Corporation 2015 35

Manage Policies (cont) \domino\policies.user.xml is where the Community server caches polices NOTE: You do not ever edit policies.user.xml to make changes to policies. Make all changes through SSC IBM Corporation 2015 36

Manage Policies (cont) NOTES: Community server gets policy updates through the STConsoleServer on startup and every hour Media server gets policies through Community Server Community Server will use the cached policy, in the event SSC is not running IBM Corporation 2015 37

Synching Nodes Synchronize node(s) after making changes to a node or configuration changes on the SSC Synchronization ensures there is no mismatch between node and cell configuration From the GUI can do a Synchronize or Full Resynchronize Synchronize fast, but might not fix problems from manual file edits that occur on the node Full Resynchronize takes longer, clears all synch optimization and synchronizes all configuration IBM Corporation 2015 39

Synching Nodes (cont) After some configuration changes; new or updated trusted certificate, a manual node synchronization is required Using syncnode.sh/bat from terminal/command line During the synchronization you are prompted to accept the trusted certificate Node agent must be stopped, Deployment Manager must be running, always performs full synchronization a) From the node, open a terminal/command line window and navigate to the profiles bin directory b) syncnode <dmgr_host> <dmgr_port> For additional synchronization information see: WebSphere Application Server synchronization process explained ( https://ibm.biz/bdhsuf ) syncnode command ( https://ibm.biz/bdhsux ) IBM Corporation 2015 40

ISC > Troubleshooting Setting log file size and rotation for JVM log files You can specify the maximum size and number of log files to be stored on the server. Before performing this procedure, make sure you have the required disk space. Retain a history at least 2 GB in size and if can spare more disk space than that, set the file maximum size to more than 20 MB and 5 historical files. This process is covered in the IBM Knowledge Center: https://ibm.biz/bdhsm6 IBM Corporation 2015 42

ISC > Troubleshooting Setting log file size and rotation for JVM log files In ISC for the server where the logs will be stored click Servers > Server Types > WebSphere application servers > Server_Name. In the "Server Infrastructure" section, click Java and Process management > Process Definition. In the "Additional Properties" section, click Logging and Tracing > JVM Logs. In the "General Properties" section, update the following fields both for System.out and System.err sections: Click OK. Return to the "Additional Properties" section and click Logging and Tracing > Diagnostic Trace. Click File and update the following fields in the "Trace" section: Click OK. Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page. In a clustered environment, repeat these steps for each node within the cluster. IBM Corporation 2015 43

ISC > Troubleshooting When sending logs up for analysis: Include the entire profiles 'logs' folder, not just the trace! Do your best to note the time the problem was reproduced. Include the names and IP addresses of the users and servers which are involved. Symptoms and error messages. A network diagram detailing the environment. Sometimes the smallest detail is important, so include everything you noticed. The Integrated Solutions Console provides a variety of logs to collect logging messages. System messages from the server are written to generalpurpose logs such as the JVM logs. These log files collect output for the System.out and System.err output streams for the application server process. One log file is specified for the SystemOut.log output stream and one file specified for the SystemErr.log output stream. Other logs are very specific in nature and focused on a component or activity. The general purpose logs such as the JVM logs and the IBM service log can be helpful in monitoring the health of the application server, however, the problem determination procedure for a specific component might instruct you to examine the contents of a component- or product-specific log. Review this link on setting JVM logging: Using JVM Logs to troubleshoot a Sametime server ( https://ibm.biz/bdhsu2 ) IBM Corporation 2015 44

ISC > Troubleshooting Handy links to bookmark when troubleshooting: Setting tracing http://www-01.ibm.com/support/knowledgecenter/ssktxq_9.0.0/admin/trouble/trbl_setting_a_diagtrace.dita Recommended trace strings http://www-01.ibm.com/support/knowledgecenter/ssktxq_9.0.0/admin/trouble/trbl_recommended_trace_settings.dita? cp=ssktxq_9.0.0%2f8-0-0-1-0 Troubleshooting Sametime Servers http://www.ibm.com/support/knowledgecenter/ssktxq_9.0.0/admin/trouble/trbl_sametime_servers.dita IBM Corporation 2015 45

ISC > Troubleshooting > Logs and trace > Diagnostic Trace Setting a diagnostic trace on a WebSphere Application Server Choose whether to make configuration or runtime changes 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, but 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. Note: In a clustered environment, perform these steps for each node in the cluster. You can expand the Components and Groups section, pick a component name to select the log level from a context menu. Each setting you select is appended to the default *=info setting, and appears in the text box. A colon (:) followed by a space is appended to each setting as a delimiter. For example, if you select the setting com.ibm.rtc.*=all, the following text displays in the text box:: We suggest you use the settings in the Recommended trace settings link. Click Apply. IBM Corporation 2015 46

ISC > Troubleshooting > Logs and trace > Diagnostic Trace Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page. Note: This step is needed only if you made changes on the Configuration tab, or if you made changes on the Runtime tab, and then selected Save Runtime changes to configuration as well. Location of log directory: AIX/Linux log location - /opt/ibm/websphere/appserver/profiles/profile_name/logs Windows log location - WAS_Install_Root\WebSphere\AppServer\profiles\Profile_Name\logs If you made changes in the Configuration tab, restart the server. When you have identified and fixed the problem, free up system resources by reverting the trace level back to its default *=info setting! IBM Corporation 2015 47

ISC > Troubleshooting > Logs and trace > Diagnostic Trace IBM Corporation 2015 48

Recommended Past OpenMic to View SSL and Sametime: POODLE Training 101-11 March 2015 [presentation, audio & video recordings attached] http://www-01.ibm.com/support/docview.wss?uid=swg27045127 Securing Domino LDAP - 10 June 2015 [presentation, audio, videos] http://www-01.ibm.com/support/docview.wss?uid=swg27045591 IBM Corporation 2015 49

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 Corporation 2015 IBM Collaboration Solutions Support http://twitter.com/ibm_icssupport 50