The wsadmin utility is a tool provided with WebSphere® Application Server that you can use to manage applications hosted by the WebSphere Application Server, including Lotus® Connections.
The wsadmin tool runs script-based commands that you enter into a wsadmin command session. Behind the scenes, these scripts are based on the Jython scripting language, and they invoke commands that do the actual work of changing properties. A Jython script parameter is provided for each property that you can change. These scripts can both change XML-based file values that control an application's configuration and get and set MBean values, which control the invocation of application server tasks, such as indexing.
You can change the behavior of Lotus Connections by using the wsadmin client to perform one of the following actions:
These properties control configurable aspects of the applications and are stored in XML-formatted configuration files. When you change these types of properties, you must use scripts that check out the configuration file, make the change, and then check the configuration file back in. After checking in your changes, you must restart the servers for the changes to take effect. In a network deployment, you must also synchronize the nodes to propagate the changes across a cluster.
Run administrative commands to change MBean values associated with the product. MBeans control the tasks that run on the server. When you run an administrative command, you must start the Jython script interpreter, but you do not have to check out any configuration files nor restart the server. Your changes take effect immediately.
For more detailed information about the wsadmin tool, go to the IBM® WebSphere Application Server information center at the following web site:
Starting the wsadmin client
Use the wsadmin client to make configuration changes to common Lotus Connections settings and individual application settings.
Editing configuration files
You can edit configuration files in two ways: by editing configuration settings in the wsadmin client, or by editing the configuration XML files directly. In both cases, you must first check out the configuration files and later check them back in using the wsadmin client.
Changing common configuration property values
Configuration settings control how and when various common operations take place. You can edit the settings to change how Lotus Connections behaves.
Running administrative commands
Use administrative commands to run tasks on the server.
Changing WebSphere Application Server environment variables
The directory paths to Lotus Connections application data and other resources are given associated WebSphere Application Server environment variables.
Disabling an application
You might decide to stop an application temporarily for maintenance or if, for example, you are deploying the product and this application is not yet ready for use.
Disabling the social analytics service
The social analytics service is enabled by default, but you can disable it if you do not want to use it in your deployment.
Managing stored credentials
Lotus Connections does not create nor store user names and passwords. Instead, it uses the user credentials that already exist in your LDAP directory for authentication. Lotus Connections does not store administrative user IDs and passwords either. It does, however, create and store references to existing administrative user credentials. You can make changes to those references.
Changing the name of the session cookie ID
The session cookie ID for Lotus Connections is named JSESSIONID by default. Other products hosted by the WebSphere Application Server often use the same name for their session cookie. If IBM HTTP Server is hosting multiple web servers, you might want to change the cookie name of one of them to prevent the cookie from being lost when the user is redirected from one product to another.
Describes the roles defined for Lotus Connections users on WebSphere Application Server.
As employees come and go from your organization, the corporate directory changes, and there are some steps that you, as the administrator, must take to make sure that those changes are reflected in the product by keeping the IBM Lotus Connections membership tables up-to-date with the changes that occur in your corporate directory.
Using the LDAP directory as the user directory
Edit configuration property settings to disable IBM Lotus Connections directory service extensions.
The Activities, Communities, Files, Forums, News, Search, and Wikis applications use the IBM WebSphere Application Server scheduling service for performing regular tasks.
Maintaining application databases
Backup the application databases and any associated content stores on a regular schedule using the methods documented by the vendor from whom you purchased the database and file system that you are using.
Find out whether people are using the Lotus Connections applications and which applications are most popular.
If you did not create a mail session on the WebSphere Application Server during the initial installation, you can configure it afterwards to enable support for email notifications in the Lotus Connections applications.
Hiding email addresses
Run a script provided with the product to configure Lotus Connections to prevent email addresses from being displayed in the product and protect the privacy of your users.
Exposing email addresses
If you configured Lotus Connections to prevent email addresses from being displayed, and later decide that you want to allow email addresses to be exposed in the product, perform this procedure.
Enabling users to set a language preference
By default, the IBM Lotus Connections user interface (UI) is displayed in the language identified in the locale settings of the web browser being used. You can set it up to allow users to explicitly select the language in which the product is displayed.
Changing the context root of an application
The Web address from which a Lotus Connections application is available contains a default context root value. After installing the application, you can change this value to a different context root to conform to corporate restrictions or policies that limit where server applications can be deployed and how they can be addressed.
Find out what level of content moderation is available for the applications in version 3.
Adding Sametime awareness though the Sametime client
If you have a Sametime® 8.0.1 client or later and the Profiles application deployed, you can enable presence awareness in Lotus Connections.
Removing sections from the help system's table of contents
If you installed a subset of the IBM Lotus Connections applications, remove the help files associated with the applications that you did not install from the product's help system.