websphere concepts for sametime

8/4/2019 Websphere Concepts for Sametime

1/40

Lotus

Version 1

Overview of IBM WebSphereApplication Server Concepts for IBMLotus Sametime Administrators

Authors: Ellen Tiberi and Jessica Piziak, IBM WPLC

Support Education


2/40


3/40

Overview of IBM WebSphere Application Server Concepts forIBM Lotus Sametime Administrators

This document covers several WebSphere

Application Server concepts that come into play whenadministering IBM Lotus Sametime, such as terminology, common commands, and the serversinvolved in a WebSphere Application Server deployment.

Time required

It should take approximately 80 minutes to complete this content.

Prerequisites and system requirements

There are no prerequisites or system requirements for this content. No prior WebSphere ApplicationServer knowledge is required.

Learning topics

The following learning topics are covered:

v Define terminology related to WebSphere Application Server architecture.

v Describe the function of a WebSphere Application Server Profile.

v Define WebSphere Application Server terminology related to Lotus Sametime topologies.

v Describe the key WebSphere Application Server profiles related to Lotus Sametime.

v Define which types of server components are installed in relation to other WebSphere ApplicationServer components.

v Discuss the WebSphere Application Server setting inheritance model, also known as resource scope.

v Start and stop WebSphere Application Servers using several methods.

v Log on to the WebSphere Application Server administrative console.v Check the status of the server using the serverStatus command.

v Describe the servers that comprise a WebSphere Application Server environment.

v Describe the function of the WebSphere Application Server's Deployment Manager.

v Define WebSphere Application Server types in the context of Sametime.

v Explain the function of Deployment Manager and Integrated Solutions Console in the context ofSametime.

v Troubleshoot issues with accessing Sametime System Console.

v Use WASServiceCmd utility to set up Sametime servers to load as Windows services

Agenda

Read through each of the sections in the order that they are listed in the following table:

Title Approximate Timing (in minutes)

IBM WebSphere Application Server Terminology on page 2 30

Common WebSphere Application Server commands on page 19 30

WebSphere Application Server types in the context of LotusSametime on page 23

20

Total: 80

1


4/40

IBM WebSphere Application Server Terminology

In this document you will learn about IBM WebSphere Application Server terminology and how it isused in an IBM Lotus Sametime environment.

Time needed

It will take approximately 30 minutes to complete this content.

Objectives

After reading this document, you should be able to:

v Define terminology related to WebSphere Application Server architecture.

v Describe the function of a WebSphere Application Server Profile.

v Define WebSphere Application Server terminology related to Lotus Sametime topologies.

v Describe the key WebSphere Application Server profiles related to Lotus Sametime.

v Define which types of server components are installed in relation to other WebSphere ApplicationServer components.

vDiscuss the WebSphere Application Server setting inheritance model, also known as resource scope.

The ABC's of IBM WebSphere Application ServerIn this section, you will learn about commonly used WebSphere Application Server architectural terms.

The following diagram shows one possible architecture of a WebSphere Application Server environment:

2 Overview of IBM WebSphere Application Server Concepts for IBM Lotus Sametime Administrators


5/40

Below, you will find definitions for each of the terms shown in the graphic above.

Application Server

According to the WebSphere Application Server Glossary, an application server is "a server programin a distributed network that provides the execution environment for an application program."

More specifically:

The application server is the primary runtime component in all configurations and is wherean application actually executes. All WebSphere Application Server configurations can haveone or more application servers. ... With Network Deployment, you can build a distributedserver environment consisting of multiple application servers maintained from a centraladministration point. In a distributed server environment, you can cluster applicationservers for workload distribution.

Source: WebSphere Application Server V6 Technical Overview

Cell

Overview of IBM WebSphere Application Server Concepts for IBM Lotus Sametime Administrators 3
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redpapers/pdfs/redp3918.pdfhttp://www.redbooks.ibm.com/redpapers/pdfs/redp3918.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.html


6/40

The WebSphere Application Server Glossary defines a cell as: "A group of managed processes thatare federated to the same deployment manager and can include high-availability core groups."

The IBM Redbooks publication WebSphere Application Server V7: Concepts, Planning, and designprovides the following, more detailed, explanation:

A cell is a grouping of nodes into a single administrative domain. ... In a Network

Deployment environment, a cell can consist of multiple nodes (and node groups), which areall administered from a single point, the deployment manager. If your cell configurationcontains nodes running on the same platform, it is called a homogeneous cell. It is alsopossible to have a cell made up of nodes on mixed platforms. This is referred to as aheterogeneous cell.

Cluster

A cluster is defined as "a group of application servers that collaborate for the purposes ofworkload balancing and failover" in the WebSphere Application Server Glossary.

In other words:

... A cluster is a logical collection of application server processes that provides workloadbalancing and high availability. Application servers that belong to a cluster are members ofthat cluster and must all have identical application components deployed on them. Otherthan the applications configured to run on them, cluster members do not have to share anyother configuration data. For example, one cluster member might be running on a largemulti-processor server while another member of that same cluster might be running on asmall mobile computer. The server configuration settings for each of these two clustermembers is very different, except in the area of the application components that areassigned to them. In that area of configuration, they are identical. The members of a clustercan be located on a single node (vertical cluster), across multiple nodes (horizontal cluster),or on a combination of the two. When you install, update, or delete an application, theupdates are automatically distributed to all members in the cluster.


Deployment Manager

A Deployment Manager is "a server that manages operations for a logical group or cell of otherservers," as stated in the WebSphere Application Server Glossary.

A more detailed explanation is that the deployment manager is:

... the central administration point of a cell that consists of multiple nodes and node groupsin a distributed server configuration. ... The deployment manager uses the node agent tomanage the application servers within one node. A deployment manager providesmanagement capability for multiple federated nodes and can manage nodes that spanmultiple systems and platforms. A node can only be managed by a single deploymentmanager and must be federated to the cell of that deployment manager. The configurationand application files for all nodes in the cell are centralized into a master configurationrepository. This centralized repository is managed by the deployment manager andsynchronized with local copies that are held on each of the nodes.

Source: WebSphere Application Server V7: Concepts, Planning, and design

Node

As defined in the WebSphere Application Server Glossary, a node is "a logical grouping ofmanaged servers."

In particular:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redpapers/pdfs/redp3918.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redpapers/pdfs/redp3918.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.html


7/40

A node is an administrative grouping of application servers for configuration andoperational management within one operating system instance (virtualization allowsmultiple operating systems on one machine). It is possible to create multiple nodes insideone operating system instance, but a node cannot leave the operating system boundaries. Ina stand-alone application server configuration, there is only one node. With NetworkDeployment, you can configure a distributed server environment consisting of multiplenodes, which are managed from one central administration server.


Node Agent

A Node Agent is "an administrative agent that manages all application servers on a node andrepresents the node in the management cell" according to the WebSphere Application ServerGlossary

In addition:

In distributed server configurations, each node has a node agent that works with thedeployment manager to manage administration processes... A node agent is createdautomatically when you add (federate) a stand-alone node to a cell. It is not included in the

Base and Express

configurations.


In simpler terms, the node agent's purpose is to pass information between the deploymentmanager and the application server.

Profile

A profile is "an instance of a WebSphere Application Server configuration."

More specifically:

Profiles are collections of user files. They share core product files. A profile contains its own set ofscripts, its own environment, and its own repository. Each profile is stored in a unique directory

path selected by the user at profile creation time. Profiles are stored in a subdirectory of theinstallation directory by default, but they can be located anywhere.

WebSphere Profiles were introduced in WebSphere Application Server v6.0. One main advantageof profiles is that they allow an administrator to have multiple application servers on a singlemachine that all use the same binaries from one install of WebSphere Application Server.

Administration is greatly enhanced when using profiles instead of multiple product installations.Not only is disk space saved, but updating the product is simplified when you maintain a singleset of product core files. Also, creating new profiles is more efficient and less prone to error thanfull product installations, allowing a developer to create separate profiles of the product fordevelopment and testing.

Templates for several types of profiles are provided with WebSphere Application Server NetworkDeployment:

v Cell

This environment creates two profiles:

- A management profile with a deployment manager

- An application server profile added (federated) to the management profile

v Management

A management profile provides components for managing multiple application serverenvironments. Possible profiles are as follows:

- Deployment manager

http://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.help.glossary.doc/topics/glossary.htmlhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdf


8/40

- Administrative agent

- Job manager

v Application server

An application server profile runs your enterprise applications and makes them available tothe internet or to an intranet. It contains a stand-alone application server.

v Custom

A custom profile contains an empty node with no servers. However, a server can be addedafter the profile is created.

v Secure proxy (configuration-only)

A secure proxy (configuration-only) profile is for use with a DeMilitarized Zone (DMZ)secure proxy server. This configuration-only profile is intended only to be used to configurethe profile using the Integrated Solutions Console. After you configure the profile, you canexport the profile configuration and then import it into the secure proxy profile in yourDMZ. Secure proxy (configuration-only) profile is only an administrative component.


For more information on profiles, watch the IBM Education Assistant module WebSphere Profiles

The following screen capture shows where profiles, cells, nodes, and servers are found in asimple WebSphere Application Server deployment with no Lotus products installed:

Note: The colors of the boxes correspond to the color scheme of the first graphic.

http://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.was_v6/was/6.0/Install_Migration/WASv6_Profiles/player.htmlhttp://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.was_v6/was/6.0/Install_Migration/WASv6_Profiles/player.htmlhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdf


9/40

The following screen capture shows where profiles, cells, nodes, and servers are found in aWebSphere Application Server deployment, with no Lotus products installed, that uses aDeployment Manager:

Note: The colors of the boxes correspond to the color scheme of the first graphic.

WebSphere Application Server terminology in the context of Lotus

SametimeIn this part you will learn how the WebSphere Application Server components that you learned about inthe previous part come into play with the Lotus Sametime System Console, Lotus Sametime MeetingServer, Lotus Sametime Proxy Server, and the Sametime Media Manager.

You will explore the following configurations of Lotus Sametime:

v Standalone environment (installed using the Cell Profile option)

v Vertical Cluster

v Horizontal Cluster



10/40

The following graphics show how profiles, cells, nodes, and servers are used in a WebSphere ApplicationServer configuration with Lotus Sametime installed:

In the first graphic, Lotus Sametime is installed using the Cell Profile option with all servers installed onthe same machine. When you select the Cell Profile option during the configuration of Lotus Sametime,two profiles are created in each cell: a Deployment Manager profile, DMProfile and afederated Application Server profile, PNProfile. In this configuration, the Application

Server is federated to the cell of the Deployment Manager.



11/40



12/40

In the second graphic, Lotus Sametime is installed using the Network Deployment option with horizontalclustering configured. Horizontal clustering is the most commonly used clustering topology for LotusSametime configurations. As described in the Lotus Sametime Information Center topic ClusteringSametime servers for high enterprise availability, "A horizontal cluster contains multiple physical machines (ornodes), each with one type of Sametime server. A horizontal cluster distributes the load across servers onmultiple machines as needed. The advantage of a horizontal cluster is that users can still use theSametime application even if one machine in the cluster fails." Although this graphic shows the Lotus

Sametime System Console as the deployment manager, the clustering guided activity can use anydeployment manager visible to the Lotus Sametime System Console within its own product, ie: A LotusSametime Meetings server can only use a deployment manager that has been installed for a LotusSametime Meetings server. Using the Lotus Sametime System Console as the deployment manager is theconfiguration recommended by IBM Lotus Development.

http://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.htmlhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.htmlhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.htmlhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.htmlhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.html


13/40



14/40

In the third image, Lotus Sametime is installed using the Network Deployment option with verticalclustering configured. The Lotus Sametime Information Center topic Clustering Sametime servers for highenterprise availability defines a vertical cluster as follows:

v A vertical cluster contains multiple instances of one type of Sametime server hosted on the samephysical machine (or node).

v A vertical cluster distributes the load as appropriate across servers. Machine maintenance in a

vertical cluster is easier and more convenient because everything is on one machine.

As is the case with horizontal clustering, although this graphic shows the Lotus Sametime SystemConsole as the deployment manager, the clustering guided activity can use any deployment managervisible to the Lotus Sametime System Console within its own product, ie: A Lotus Sametime Meetingsserver can only use a deployment manager that has been installed for a Lotus Sametime Meetings server.Using the Lotus Sametime System Console as the deployment manager is the configurationrecommended by IBM Lotus Development.

http://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.htmlhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.htmlhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.htmlhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/plan/plan_clusters.html


15/40

WebSphere Application Server Profiles in Lotus SametimeAs described previously in this document, a profile is "an instance of a WebSphere Application Serverconfiguration." Each Lotus Sametime server installation uses several WebSphere Application Serverprofiles, as shown in the following table:



16/40

Table 1. Profiles used by Lotus Sametime servers

Lotus Sametime Server WebSphere Application Server profiles

Lotus Sametime System Consolev STSCAppProfile

v STSCDMgrProfile

Lotus Sametime Meeting Serverv serverNameMediaDMProfile

v serverNameMediaPNProfile

Lotus Sametime Proxy Serverv serverNameMeetingDMProfile

v serverNameMeetingPNProfile

Lotus Sametime Media Managerv serverNameProxyDMProfile

v serverNameProxyPNProfile

The following graphic shows where these profiles are found at the Operating System level for a CellProfile configuration:

Keep the location of these profiles in mind when examining log and configuration files. The files

associated with the server that you are troubleshooting will be located under the profile for that server.For example, if you are troubleshooting an issue with the Lotus Sametime System Console, then youwould look for the log and configuration files under the profile for the Lotus Sametime System Consoledeployment manager profile. On a Microsoft Windows machine using the default installation directories,the log files for the Lotus Sametime System console are located in the C:\Program Files\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\logs\dmgr directory, as shown in the following screen capture:



17/40

Keep the same thoughts in mind when troubleshooting the configuration files for a particular server. For

example, if you are trying to solve a problem with the Lotus Sametime System Console, the only placethat you should need to make a change to a configuration file is in the Lotus Sametime System Consoledeployment manager profile. The security.xml file is located in the C:\Program Files\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\config\cells\ directory on a Microsoft Windowsmachine using the default installation directories, as shown in the following screen capture:



18/40

The wimconfig.xml file is located in the C:\Program Files\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\config\cells\\wim\config directory on a Microsoft Windows machineusing the default installation directories, as shown in the following screen capture:

The Websphere Application Server components, such as clusters, nodes, and cells need to be taken intoaccount when configuring resources for Lotus Sametime. Certain settings can be configured at multiple



19/40

levels, or scopes, using the Lotus Sametime System Console. This concept is referred to as resource scope.The IBM Redbooks Publication WebSphere Application Server V7: Concepts, Planning, and design describesresource scope as follows:

Resource scope is a powerful concept to prevent duplication of resources across lower-level scopes.For example, if a data source can be used by multiple servers in a node, it makes sense to definethat data source once at the node level, rather than create the data source multiple times, possibly

introducing errors along the way. Also, if the data source definition needs to change (maybe due tochanges to an underlying database), the data source definition can be changed once and is visible toall servers within the node. The savings in time and cost should be self-evident. Some thoughtneeds to be put toward outlining what resources you will need for all the applications to bedeployed and at what scope to define each. You select the scope of a resource when you create it.

The following list describes the scope levels, listed in order of granularity with the most generalscope first:

Cell scope

The cell scope is the most general scope and does not override any other scope. [It is]recommended that cell scope resource definitions should be further granularized at a morespecific scope level. When you define a resource at a more specific scope, you providegreater isolation for the resource. When you define a resource at a more general scope, youprovide less isolation. Greater exposure to cross-application conflicts occur for a resourcethat you define at a more general scope.

The cell scope value limits the visibility of all servers to the named cell. The resourcefactories within the cell scope are defined for all servers within this cell and are overridden

by any resource factories that are defined within application, server, cluster, and nodescopes that are in this cell and have the same Java Naming and Directory Interface (JNDI)name. The resource providers that are required by the resource factories must be installedon every node within the cell before applications can bind or use them.

Cluster scopeThe cluster scope value limits the visibility to all the servers on the named cluster. The

resource factories that are defined within the cluster scope are available for all the membersof this cluster to use and override any resource factories that have the same JNDI name thatis defined within the cell scope. The resource factories that are defined within the cell scopeare available for this cluster to use, in addition to the resource factories that are definedwithin this cluster scope.

Node scope (default)The node scope value limits the visibility to all the servers on the named node. This is thedefault scope for most resource types. The resource factories that are defined within thenode scope are available for servers on this node to use and override any resource factoriesthat have the same JNDI name defined within the cell scope. The resource factories that aredefined within the cell scope are available for servers on this node to use, in addition to theresource factories that are defined within this node scope.

Server scopeThe server scope value limits the visibility to the named server. This is the most specificscope for defining resources. The resource factories that are defined within the server scopeare available for applications that are deployed on this server and override any resourcefactories that have the same JNDI name defined within the node and cell scopes. Theresource factories that are defined within the node and cell scopes are available for thisserver to use, in addition to the resource factories that are defined within this server scope.

Application scopeThe application scope value limits the visibility to the named application. Application scoperesources cannot be configured from the Integrated Solutions Console. Use Rational

http://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdf


20/40

Application Developer Assembly and Deploy V7.5, or the wsadmin tool to view or modifythe application scope resource configuration. The resource factories that are defined withinthe application scope are available for this application to use only. The application scopeoverrides all other scopes.

You can define resources at multiple scopes but the definition at the most specific scope is used. Whenselecting a scope, the following rules apply:

v The application scope has precedence over all the scopes.

v The server scope has precedence over the node, cell, and cluster scopes.

v The cluster scope has precedence over the node and cell scopes.

v The node scope has precedence over the cell scope.

When viewing resources, you can select the scope to narrow the list to just the resources defined at thescope. Alternatively, you can select to view resources for all scopes. Resources are always created at thecurrently selected scope. Resources created at a given scope might be visible to lower scopes. Forexample, a data source created at a node level might be visible to servers within the node.

Be sure to keep this precedence structure in mind when configuring Lotus Sametime. Here is a screencapture of one place where you will see resources configurable by scope:

For more information, consult the IBM Redbooks Publication WebSphere Application Server V7Administration and Configuration Guide , Chapter 5.1.5.

http://www.redbooks.ibm.com/redbooks/pdfs/sg247615.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247615.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247615.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247615.pdf


21/40

Common WebSphere Application Server commands

In this section, you will learn about common server commands used when administering LotusSametime.

Time needed

It will take approximately 30 minutes to complete this section.

Objectives

After reading this section, you should be able to:

v Start and stop WebSphere Application Servers using several methods.

v Log on to the WebSphere Application Server administrative console.

v Check the status of the server using the serverStatus command.

Starting and stopping WebSphere Application ServerThere are several ways to start and stop WebSphere Application Server:

vFrom a command line

v From the WebSphere Application Server administrative console

v If you are using Microsoft Windows, from the Microsoft Windows Start Menu

v If you are using Microsoft Windows, by starting the Microsoft Windows Service if the applicationserver is registered as a service

Be sure to always start the servers in the correct order:

1. Deployment Manager

2. Node Agent

3. Application Server

Note: When stopping servers, the order does not matter if all will be shut down. However, as a bestpractice, shut down the servers in the reverse of the order listed above.

Starting and stopping an application server using the command lineUse the following steps to start a server from a command line:

Procedure

1. If WebSphere Application Server Network Deployment is installed, you must first start thedeployment manager. To start the deployment manager, navigate to the bin directory under thedeployment manager profile from a command line. For example, C:\Program Files\IBM\WebSphere\AppServer\profiles\MyDMgrProfile\bin

2. On Microsoft Windows systems, enter the command startManager.bat. On AIX, Linux, or Solaris

systems, the command is startManager.sh.3. Next, start the node agent. Navigate to the bin directory under the profile for the server. For example,

C:\Program Files\IBM\WebSphere\AppServer\profiles\MyAppSvrProfile\bin.

4. On Microsoft Windows systems, enter the command startNode.bat. On AIX, Linux, or Solaris systems,the command is startNode.sh.

5. After the node agent successfully starts, enter the command startServer.bat where is the name of the application server. For example, startServer.bat MyAppSvr.

Note: On AIX, Linux, or Solaris systems, the command is startServer.shAttention: The name of the server is case sensitive, even for servers running on Microsoft Windows.



22/40

The results returned will resemble the following screen capture:

Note: Although this screen capture was taken from a Microsoft Windows system, the output will be

similar on other operating systems.6. To stop the application server, enter the command stopServer.bat where is the name of the application server. You can append the -username and -password parameters to the command or you will beprompted to enter the credentials for your WebSphere Application Server administrator.

Note: On AIX, Linux, or Solaris systems, the command is stopServer.sh.

7. To stop the node, enter the command stopNode.bat. You can append the -username and-password parameters to the command or you will be prompted to enter the credentialsfor your WebSphere Application Server administrator.

Note: On AIX, Linux, or Solaris systems, the command is stopNode.sh.

8. To stop the deployment manager, navigate to the bin directory under the deployment managerprofile. Enter the command stopManager.bat. You can use the -username and -password parameters or you will be prompted to enter the credentials for your WebSphereApplication Server administrator.

Note: On AIX, Linux, or Solaris systems, the command is stopManager.sh

What to do next

Note: When you start the servers you do not need to enter the WebSphere Application Serveradministrator credentials. It is only when you stop the servers, or check the server status, that thecredentials are needed.

Starting a server using the Microsoft Windows Start MenuOn a Windows machine, you can start an application server using the Start Menu.

Procedure

1. First, start the deployment manager by clicking Start All Programs IBM WebSphere Application Server Network Deployment V7.0 (or the folder corresponding to your WebSphereApplication Server install) Profiles (such asMyDmgrProfile) Start the Deployment Manager



23/40

2. After the deployment manager starts, start the node agent by opening a command prompt andnavigating to the bin directory under the profile for the application server. For example, C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\MyAppSvrProfile\bin.

3. Enter the command startNode.bat.

Note: On AIX, Linux, or Solaris systems, the command is startNode.sh.

4.Next, start the application server by clicking Start All Programs IBM WebSphere ApplicationServer Network Deployment V7.0 (or the folder corresponding to your WebSphere ApplicationServer install) Profiles (such as MyAppSvrProfile) (such as MyAppSvrProfile) Start the server.

Starting a server using the Windows Service

Procedure

1. All servers must be registered as Windows Services for the following steps to work. Open theWindows Services utility by clicking Start All Programs Administrative Tools Services.Depending on your Operating System, the sequence to open the Windows Services utility may differ.

2. First, start the service corresponding to the deployment manager.

3. Next, start the service corresponding to the node agent for the server.4. Last, start the service corresponding to the application server.

Starting a server using the IBM Integrated Solutions Console

Procedure

1. Start the administrative console server if it is not already running.

Tip: You will learn how to check the status of a server in the next part.

2. Launch the administrative console in a Web browser.

Tip: You will learn how to launch the administrative console in the last part.

3. In the administrative console, navigate to Servers > Server Types > WebSphere application servers.

4. Click the check box next to the server that you want to start, and then click the Start button.

Checking the status of a serverAt times, you may need to check the status of a particular server. You can use the serverStatus commandto list the status of one or all servers of the servers configured in a node.

Procedure

1. Navigate to the bin directory under the profile for the server. For example, C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\MyAppSvrProfile\bin

2. To view the status of all of the servers in the configuration, enter the command serverStatus.bat -all.

To view the status of a particular server in the configuration, enter the command serverStatus.bat- where is the server.

Note: On AIX, Linux, or Solaris systems, the command is serverStatus.sh.

Tip: You can append the -username and -password parameters to the command. For example: serverStatus.bat -all -username wasadmin-password waspassword. Otherwise, you will be prompted to enter the credentials for your WebSphereApplication Server administrator.The status of the specified server(s) will be displayed on the command line.



24/40

3. Alternately, you can check the server status using the WebSphere Application Server administrativeconsole. Launch the administrative console and navigate to Servers Server Types WebSphereapplication server. The status of each of the application servers in the configuration are displayed inthe status column. The following screen capture shows the results of running the serverStatuscommand from both the Deployment Manager profile and the Sametime System System ConsoleServer profile:

Note: Although this screen capture was taken from a Microsoft Windows system, the output will besimilar on other operating systems.

Logging on to the IBM Integrated Solutions ConsoleThe IBM Integrated Solutions Console (ISC) is a Web-based tool that is used to administer a WebSphereApplication Server environment.

Before accessing the IBM Integrated Solutions Console through the Web browser, you must first start theserver that is hosting the console. In a stand-alone environment, the console is hosted on the applicationserver. Therefore, you need to start the application server before attempting to access the console. In adistributed environment, available with the use of the IBM WebSphere Application Server NetworkDeployment, the console is hosted on the deployment manager server, which must be started beforeaccessing the console.

Use the following URL to access the WebSphere Administrative Console: http://:/ibm/console where WC_adminhost is the admin port.

If you are not sure of the admin port, locate the portdef.props file in the properties directory under theprofile for the server hosting the admin console. For example, C:\Program Files\IBM\WebSphere\AppServer\profiles\MyDMgrProfile\properties. In the portdef.props file, WC_adminhost is the defaultadmin port and WC_adminhost_secure is the secure port used if administrative security enabled.

Note: If you use the default port and administrative security is enabled for the server, you willautomatically be redirected to the secure port.



25/40

WebSphere Application Server types in the context of Lotus Sametime

In this section you will learn about the servers that comprise a WebSphere Application Serverenvironment and where the Lotus Sametime servers/components fit into the WebSphere ApplicationServer structure.

Time needed

It will take approximately 30 minutes to complete this section.

Objectives

After reading this section, you will be able to:

v Describe the servers that comprise a WebSphere Application Server environment

v Describe the function of the WebSphere Application Server's Deployment Manager

v Define WebSphere Application Server types in the context of Sametime

v Describe the function of the Deployment Manager and the Integrated Solutions Console in the contextof Sametime

v

Troubleshoot issues with accessing Sametime System Consolev Use WASServiceCmd utility to set up Sametime servers to load as Windows Services

Server types in a WebSphere Application Server environment

System requirements for IBM WebSphere Application Server, such as supported Database servers,Directory servers, and Web servers, are found in: IBM WebSphere Application Server Detailed Requirementsand in WebSphere Application Server V7: Concepts, Planning, and design. This part briefly explains thefunction of some of the server types that are used/required in a WebSphere Application Serverdeployment. The graphic below represents the servers to be defined. Skip ahead to the next part if youalready know the function of these servers and want to see how they are used in a Lotus Sametimedeployment.

http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27006921http://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27006921


26/40

Application Server

The first section of this document defined an application server as follows:

The application server is the primary runtime component in all configurations and is wherean application actually executes. All WebSphere Application Server configurations can haveone or more application servers. ... With Network Deployment, you can build a distributedserver environment consisting of multiple application servers maintained from a centraladministration point. In a distributed server environment, you can cluster applicationservers for workload distribution.


Web Server

The function of the Web/HTTP server in the WebSphere Application Server environment isexplained in theWebSphere Application Server V7: Concepts, Planning, and design as follows:

WebSphere Application Server can work with a Web server (like the IBM HTTP Serverincluded in WebSphere Application Server) to route requests from browsers to theapplications that run in WebSphere Application Server. A WebSphere Web Server Plug-in is

http://www.redbooks.ibm.com/redpapers/pdfs/redp3918.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdfhttp://www.redbooks.ibm.com/redpapers/pdfs/redp3918.pdf


27/40

provided for installation with supported Web servers. This plug-in directs requests to theappropriate application server and performs workload balancing and fail-over amongservers in a cluster.

Although Web servers are products that are separate from WebSphere Application Server, theycan be defined in the WebSphere Application Server administration process, to enable theadministrator to associate applications with one or more defined Web servers in order to generate

the proper routing information for Web server plug-ins. In addition, Web server managementcapabilities are available in some circumstances.

Source:WebSphere Application Server V6.1 Planning and Design

Database Server

The database server plays an integral role in the WebSphere Application Server environment. Thedatabase server is defined on the IBM Terminology site as:

1. A software program that uses a database manager to provide database services to othersoftware programs or computers.

2. The server on which the database application and database are installed.

3. A computer that is dedicated to running a database manager to provide databaseservices to other software programs or computers. See also data server. ..A server that

provides services for the secure and efficient management of information.

Directory Server

The directory server is defined on the IBM Terminology site as:

A server that can add, delete, change or search directory information on behalf of a client.

A directory is a data structure that enables the look up of names and associated attributesarranged in a hierarchical tree structure. In the context of enterprise application servers, thisenables applications to look up a user principal and determine what attributes the user hasand of which groups the user is a member. Decisions about authentication and authorizationcan then be made using this information.

Source: WebSphere Application Server V6.1 Planning and DesignThe common protocol used for the directory server is Lightweight Directory Access Protocol(LDAP) which is defined on the IBM Terminology site as:

An open protocol that uses TCP/IP to provide access to directories that support an X.500model and that does not incur the resource requirements of the more complex X.500Directory Access Protocol (DAP). For example, LDAP can be used to locate people,organizations, and other resources in an Internet or intranet directory.

Proxy Server

A Proxy server is defined on the IBM Terminology site as:

1. A server that receives requests intended for another server and that acts on the client's

behalf (as the client's proxy) to obtain the requested service. A proxy server is often usedwhen the client and the server are incompatible for direct connection. For example, theclient is unable to meet the security authentication requirements of the server but should

be permitted some services.

2. A server that acts as an intermediary for HTTP Web requests that are hosted by anapplication or a Web server. A proxy server acts as a surrogate for the content servers inthe enterprise.

http://www.redbooks.ibm.com/redbooks/pdfs/sg247305.pdfhttp://www.ibm.com/software/globalization/terminology/cd.jsp#d03http://www.ibm.com/software/globalization/terminology/cd.jsp#d03http://www.redbooks.ibm.com/redbooks/pdfs/sg247305.pdfhttp://www.ibm.com/software/globalization/terminology/kl.jsp#l11http://www.ibm.com/software/globalization/terminology/op.jsp#p15http://www.ibm.com/software/globalization/terminology/op.jsp#p15http://www.ibm.com/software/globalization/terminology/kl.jsp#l11http://www.redbooks.ibm.com/redbooks/pdfs/sg247305.pdfhttp://www.ibm.com/software/globalization/terminology/cd.jsp#d03http://www.ibm.com/software/globalization/terminology/cd.jsp#d03http://www.redbooks.ibm.com/redbooks/pdfs/sg247305.pdf


28/40

WebSphere Application Server types in the context of Lotus Sametime8.5The IBM Lotus Sametime 8.5 system requirements document, Detailed system requirements - Sametime 8.5provides, among other requirements, the supported database servers, directory servers, HTTP servers, etc.The previous section briefly explained the function of some of the key servers that comprise a WebSphereApplication Server environment. This section discusses those server types in the context of the Lotus

Sametime 8.5. Some of the servers cited in the requirements are shown in the graphic below .

Application ServersMost of the Lotus Sametime 8.5 servers run on the IBM WebSphere Application Server platform,and are application servers themselves. The purpose of each server is described briefly here:

v The IBM Lotus Sametime System Console provides a central location for installing, configuringand administering the Sametime components.

v The IBM Lotus Sametime Meeting Server provides a central meeting place for communitymembers.

http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27016451http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27016451


29/40

v The IBM Lotus Sametime Media Manager provides audio and visual services for Sametimemeetings and chats.

v The IBM Lotus Sametime Proxy Server hosts the Lotus Sametime client for browsers.

v The IBM Lotus Sametime Gateway Server provides the means of sharing awareness withexternal instant messaging communities.

Note: The IBM Lotus Sametime Community server runs on IBM Lotus Domino

server rather thanWebSphere Application Server.

Database Server

Several of the Lotus Sametime servers/components require a Database server, specifically IBMDB2, which can be downloaded with the Lotus Sametime 8.5 installation. For more informationsee the download document, IBM Lotus Sametime Standard 8.5. The Lotus Sametime SystemConsole, the Lotus Sametime Meeting Server, and the Lotus Sametime Gateway Server all requireDB2. The Lotus Sametime System Console requires DB2 to store user policy information anddeployment topology information; this information is fed to the installers when setting up serversand also at runtime to connect to other servers. The Lotus Sametime Meeting Server requires DB2for storing meeting room user data. The Sametime Gateway Server requires DB2 for policyinformation.

Directory Server

The Lotus Sametime System Console, the Lotus Sametime Meeting Server and the LotusSametime Gateway Server all require an LDAP directory server. The LDAP directory contains theperson records for the users in the local Lotus Sametime Community, and these servers cansearch the LDAP directory and authenticate Lotus Sametime users when required.

Proxy Server

There are several roles for proxy servers in a Lotus Sametime deployment. One example is whenthe IBM WebSphere Proxy Server is configured to handle routing and caching tasks for a clusterof Lotus Sametime Meeting Servers. IBM WebSphere Proxy Server is distributed with theWebSphere Application Server that is included with the Lotus Sametime installation. The LotusSametime system requirements also lists several supported proxy servers that can be used for

secure networking.

Deployment Manager and the IBM Integrated Solutions Console

With the IBM WebSphere Application Server Network Deployment edition, you administer the serversand components associated with the WebSphere Application Server environment using the deploymentmanager. The environment where there are multiple servers being managed from a single deploymentmanager is referred to as a Distributed server environment. The deployment manager itself is a server thatcentrally manages and administers all servers and components in a given node(s) in a given WebSphereApplication Server cell.

The deployment manager also hosts powerful advanced deployment capabilities that are available in a

distributed server environment; including high availability, dynamic scalability, and advanced clusteringfor workload balancing and failover. In a distributed server environment, the deployment managercontains the master configuration files (such as .xml files) and Java EE application files to start and runthe WebSphere components and processes that run in the environment. The deployment managersynchronizes its configuration files with those held locally on each node associated with that deploymentmanager. Each node contains a node agent, and the deployment manager communicates with the nodeagents to synchronize the configuration information and file transfer, and perform other administrativeactivities on those nodes.

The file synchronization process that occurs between the deployment manager and the nodes that arefederated into the same cell where the deployment manager resides, is always one-way; from the

http://www.ibm.com/support/docview.wss?rs=477&uid=swg24024322http://www.ibm.com/support/docview.wss?rs=477&uid=swg24024322http://www.ibm.com/support/docview.wss?rs=477&uid=swg24024322


30/40

deployment manager to the nodes. Configuration changes made at the node level are temporary and willbe overwritten by the master configuration on the deployment manager during the next filesynchronization.

Federation is an important process in a distributed server environment, and it is handled by thedeployment manager. Federation is the process by which a node becomes a part of the deploymentmanager cell. During federation, a node agent server is created on the node to manage WebSphere

Application Server environment on that node.

A tool that is hosted by the deployment manager and executes the management and administration tasksin the WebSphere Application Server distributed server environment is the IBM Integrated SolutionConsole. The IBM Integrated Solutions Console, which has been cited throughout this document, isfurther defined in the WebSphere Application Server v7.0 Information Center topic Overview of IntegratedSolutions Console as follows:

Integrated Solutions Console provides a single, common interface for system administration. Itprovides the main platform on which IBM and non-IBM products can build administrative userinterfaces as individual plug-ins to a common console framework. Standardizing productadministration functions to run on the Integrated Solutions Console platform gives them a morecommon look and feel and a more consistent behavior, thereby reducing the learning curve andadoption as new management components are introduced. Administrators can interact with multipleIBM and non-IBM products from a single browser-based console.

Deployment Manager and the Lotus Sametime System ConsoleLotus Sametime 8.5.x can be deployed in several ways, but a recommended method is to use the LotusSametime System Console (SSC) as the central point of configuration for deployment planning. OnceLotus Sametime is deployed its runtime features and functions can be administered mostly using the IBMIntegrated Solutions Console and the Lotus Sametime System Console. The document IBM WebSphere

Application Server Introduction for Lotus explains that the Lotus Sametime System Console is built on JavaEE technology and is a plug-in with a set of portlets within the IBM Integrated Solutions Console, whichis hosted on the Deployment Manager. Here we will dig a little deeper by explaining the followingimage.

.

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/isc/overview.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/isc/overview.htmlhttp://www.lotus.com/ldd/stwiki.nsf/dx/1_hour_course_to_demystify_WebSphere_Application_Server_for_LotusWPLC_http://www.lotus.com/ldd/stwiki.nsf/dx/1_hour_course_to_demystify_WebSphere_Application_Server_for_LotusWPLC_http://www.lotus.com/ldd/stwiki.nsf/dx/1_hour_course_to_demystify_WebSphere_Application_Server_for_LotusWPLC_http://www.lotus.com/ldd/stwiki.nsf/dx/1_hour_course_to_demystify_WebSphere_Application_Server_for_LotusWPLC_http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/isc/overview.htmlhttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/isc/overview.html


31/40

There are three application servers, or Java Virtual Machines (JVMs), that run in the Lotus SametimeConsole Server cell (labeled as SSC Cell in the diagram above): the Deployment Manager, Node Agent,and the Lotus Sametime System Console Server. As mentioned previously in this document, the LotusSametime System Console database (labeled as STSC DB in the diagram above), which runs on IBM DB2,stores user policy data and much of the Lotus Sametime deployment topology data; it feeds this data tothe installers when setting up the Lotus Sametime servers, and at runtime to connect to the servers. Thenode agent is used for communication between the Deployment Manager and the Sametime SystemConsole Server. The Deployment Manager hosts the Integrated Solutions Console, and Sametime SystemConsole Portlets (labeled as SSC Portlets in the diagram above) within the ISC provide the user interfacefor administering the Sametime servers and components. The SSC Framework applications are used todrive the REST APIs that the Sametime installers connect to and also provide policy and administrativeinterfaces that the applications connect to in order to do necessary updates of information from the SSC.

One of the important functions of the ISC and the SSC is to make sure that changes made at thedeployment manager level are propagated to the nodes in the same cell as the deployment manager.When you make a change on an the Sametime System Console Server, such as increase trace levels, it isimportant to save the change to the master configuration, which is located on the deployment manager.To make sure the nodes know of the changes you made, you then trigger file synchronization byselecting System Administration Save Changes to Master Repository Synchronize Changes withNodes Save . Once the synchronization has completed, you must then restart the server.

http://www-01.ibm.com/software/globalization/terminology/qr.jsp#x3220976http://www-01.ibm.com/software/globalization/terminology/qr.jsp#x3220976


32/40

Things to check when you cannot access the Lotus Sametime SystemConsoleThe Deployment Manager, Node Agent, and Lotus Sametime System Console application server must all

be running to access the Lotus Sametime System Console. Once all three of these servers are started, youlog into the IBM Integrated Solutions Console (ISC), and access the Sametime System Console within theISC, from your Web browser using http:///ibm/console. Details on determining the

correct port to use were discussed previously in this document, in the section Logging on to the IBMIntegrated Solutions Console.

At times you may have trouble accessing the Lotus Sametime System Console; for example, you may notbe successful when logging into the IBM Integrated Solutions Console and you may see an error in yourbrowser such as "Unable to connect" or "Cannot display web page". In this case, these particular errorsnormally occur if the deployment manager is not running. As a first step, it is a good practice to verifythat all three servers are running by executing the serverStatus command in your operating system'scommand prompt. Refer to the topic in the previous section of this document titled, Checking the Status ofa Server for the proper syntax of the serverStatus command.

If the deployment manager is running, the results of the serverStatus command execution will state:ADMU0509I: The Deployment Manager "dmgr" is STARTED"

If the deployment manager is not running, the serverStatus command will state ADMUxxxxI: TheDeployment Manager "dmgr" cannot be reached. It appears to be stopped."

Note: The numerical portion of the ADMUxxxxI code in the console messages will differ depending onthe server you are starting and its state.

If the deployment manager is not running, start it using the appropriate command for your operatingsystem. Refer to the previous section of this document titled Common WebSphere Application ServerCommands for step-by-step instructions on navigating to the proper location for checking server statusand starting not only the deployment manager server but also the node agent server and the LotusSametime System Console application server.

At other times you may be able to successfully log into the ISC, but cannot access the specific LotusSametime System Console options.. The image below shows an example of an error that occurs when thedeployment manager is running and you have successfully logged into the Integrated Solutions Console,

but you cannot access some of the options in the Sametime System Console. A likely cause of thisbehavior is that the Lotus Sametime System Console application server is not running.



33/40

In this case, it is best to issue a serverStatus -all command in the proper directory to verify the status ofboth the node agent and the Sametime System Console server. If either or both servers are not running,

start them accordingly. Again, a good place to verify your steps, and to see examples of the output youwill see from the serverStatus command and others, is the previous section of this document titledCommon WebSphere Application Server Commands.

If you have confirmed that all three servers are started, but are still experiencing issues with accessing theLotus Sametime System Console, first check the systemOut.log file located in the deployment managerprofile's log directory: \profiles\STSCDMgrProfile\logs\dmgr for errorsstarting with AIDSC. All Sametime System Console errors begin with these characters, followed by a 4digit number. Then check the Sametime System Console application server's systemOut.log file for theAIDSC errors; this systemOut.log is located in the Sametime System Console application server's logdirectory: \profiles\STSCAppProfile\logs\STConsoleServer.

If you attempt to log into the Integrated Solutions Console and instead see a blank screen, it could be

that the LDAP server is down or otherwise inaccessible. The SystemOut.log for the deployment managerunder \profiles\STSCDMgrProfile\logs\dmgr (or trace.log in the same location,if you have trace enabled) will contain an error that resembles:

"[date time] 0000002f exception E com.ibm.ws.wim.adapter.ldap.LdapConnection getDirContextcom.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520EThe'java.naming.CommunicationException: :389 [Root exception is

java.net.ConnectException: Connection refused]' naming exception occurred during processing.

If you find this error in the logs, or otherwise suspect an issue with the LDAP server, add the parameterallowOperationIfReposDown=true to the wimconfig.xml fie. The presence of this parameter in



34/40

wimconfig.xml allows you to log into the Integrated Solutions Console and access the Sametime SystemConsole even though the LDAP server is not accessible. If a defunct LDAP server is defined, you canthen make the necessary changes. As cited in the section of this document titled WebSphere ApplicationServer Profiles in Lotus Sametime, the wimconfig.xml file is located in the \profiles\ STSCDMgrProfile\config\cells\\wim\config directory. Open the file in a texteditor and locate these lines:

Important note: Editing configuration files in general is not recommended. Extreme caution should beused when making edits to the wimconfig.xml file; incorrect changes could render the serversinaccessible.

Add the parameter allowOperationIfReposDown="true" in the exact location specified below, and savethe file:

This change allows you to log into the Integrated Solutions Console as long as the credentials you enterare accepted by a working/running LDAP server. Once you have logged in you can view the LDAPrepository configurations and make any needed changes (such as removing a defunct LDAP server thatWebSphere Application Server is trying to query on login and causing the login failure) by selecting toSecurity Global Security , and under the User Account Repository section, select FederatedRepositories for Available Realm Definitions and select Configure. You will see the defined repositoriesin the realm. Make any necessary changes so that the settings reflect your current LDAP servers, thenselect Manage Repositories and make any needed changes there. After you select OK, make sure thatyou select Save at the top of the Global Security page to ensure the changes are saved to the master

configuration.

How to Set up Sametime servers to automatically load as WindowsServicesFor Microsoft Windows operating systems, one way to ensure that the servers associated with the LotusSametime System Console are started, thereby avoiding some of the access issues cited in the previoussection, is for the servers to be defined as Windows Services so that they always start on operatingsystem startup. However, there is an overall caveat where, by default, when you install any WebSphereApplication Server components, Windows Services are not automatically created for them. There areseveral methods you can choose from to set up your Lotus Sametime servers to load as WindowsServices.

One method is to create and run batch files. Follow the instructions in the Lotus Sametime 8.5 wiki articleSametime 8.5 Components as a Windows service .

As manual creation of the batch files can be susceptible to issues such as typos, another method is to useof the WebSphere Application Server utility WASServiceCmd. Perform the following steps to use theWASServiceCmd utility to set up the Sametime System Console servers as Windows services.

1. Detach the compressed file from the document, Using WASServiceCmd to create Windows services forWebSphere Application Servers,

2. Open a Windows cmd prompt and switch to the \bin directory.

3. Type wasservicecmd.bat and press ENTER. A list of menu options appears.

http://www-10.lotus.com/ldd/stwiki.nsf/dx/Sametime_8.5_Components_as_a_Windows_servicehttp://www-01.ibm.com/support/docview.wss?uid=swg21397335http://www-01.ibm.com/support/docview.wss?uid=swg21397335http://www-01.ibm.com/support/docview.wss?uid=swg21397335http://www-01.ibm.com/support/docview.wss?uid=swg21397335http://www-01.ibm.com/support/docview.wss?uid=swg21397335http://www-10.lotus.com/ldd/stwiki.nsf/dx/Sametime_8.5_Components_as_a_Windows_service


35/40

4. Type 1 to select the first menu option. A list of profiles, associated with the Application Serverdirectory you started the utility from, appears. The same list of profiles appears under the\profiles directory.

5. Type the number corresponding to the profile containing the servers you want to set up as services.In this example, STSCDMgrProfile is the name of the profile associated with the Lotus SametimeSystem Console server's deployment manager. When you select the number corresponding to theprofile, setupcmdLine.bat launches, which lists the Cell and Node associated with that profile as wellas the server(s) associated with that node. In the example, the Deployment Manager server, "1 dmgr"is listed under Servers.

6. Type a desired service name for the server. Example: Since this server is the Deployment Managerserver, type STConsoleServerDM or ConsoleServerDM. The following image shows an example ofexecuting the steps above.



36/40

Once you have named the service, the utility will ask you several questions regarding yourpreferences on service startup and security. The image below shows these questions and choices.

7. Select a desired Restart Policy.

8. Select a desired Start Type.

9. Indicate whether WebSphere Security is enabled.

10. An Execute command will appear; type Y to run the service creation process.

11. Once the command completes and you are again prompted to type a number corresponding to thedesired menu option, type 1 to initialize the steps to set up a Windows service for the node agent

12. Type the number corresponding to the profile containing the servers you want to set up as services.In the example graphic in step 5 above, STSCAppProfile is the name of the profile associated withthe Lotus Sametime System Console server.

13. From the list of servers that appear select 2 nodeagent.

14. Type the desired service name . Example: ConsoleServerNodeagent.15. Select a desired Restart Policy.

16. Select a desired Start Type.

17. Indicate whether WebSphere Security is enabled

18. Type Y to run the service creation process.

19. Repeat these steps once more for the Lotus Sametime System Console server.

You can check if the services were successfully created by selecting Start - Run and typing services.msc.Look for a service starting with "IBM WebSphere Application Server v7.0 - ". The image below shows the



37/40

result of the steps taken above:

Repeat these steps to configure Windows services for the remaining Sametime servers associated with thecell.

Note that with either method of setting up the services, the services will start with an operating systemstart or restart, but may not always start after a crash. It is always best to check the logs such asstartServer.log for each server that is suspected of not starting or starting properly to determinewhether the server fully started. A startServer.log file exists for each server in the each profile, and islocated in the \profiles\\logs\ directory.



38/40



39/40


40/40

Printed in USA

websphere concepts for sametime

Documents