Просмотр сообщений
1
IBM Lotus Sametime / Сохранение стенограм ST в БД на сервере
« : 17 Июль 2014, 10:23:50 »
Настраивал по следующей инструкции
Цитировать
How to enable Chat Logging on the Sametime 8.5 server
Question
How do you enable chat logging on a Lotus Sametime 8.5 server?
Answer
This technote specifies how to enable chat logging in Lotus® Sametime® 8.5 Server. This process is different from earlier versions of Sametime.
For instructions on enabling chat logging for previous versions of Sametime or for client side logging, see the related technote #1086729.
Step 1: Updating the sametime.ini and creating the chatlogging.ini
In Sametime 8.5 some Black Box library names can be configured by using the sametime.ini file. This is controlled by a new section called [ST_BB_NAMES], and the value that controls the chat logging black box is ST_CHAT_LOG.
Use a text editor to edit the sametime.ini file, which is located in the Lotus Sametime Community Server installation directory.
(Example: C:\Program Files\lotus\domino).
a. Set ST_CHAT_LOG to file in the sametime.ini file under the ST_BB_NAMES section.
ST_CHAT_LOG=file
Example:
For Windows:
To use StChatLogFile.dll as the chat logging black box, set
[ST_BB_NAMES]
ST_CHAT_LOG=File
For IBM i:
To use stchatlogf.srvpgm as the chat logging blackbox, set
[ST_BB_NAMES]
ST_CHAT_LOG=File
b. Create chatlogging.ini in the same directory as sametime.ini.
c. Move all the attributes from sametime.ini related to [ChatLogging] to chatlogging.ini. For example:
[ChatLogging]
CL_CHAT_START_DISCLAIMER=Disclamer message.
CL_CHAT_START_DISCLAIMER_RICH_TEXT=<span style="color:#ff0000;
font-size:11pt;font-family:Tahoma;"><b><i>Rich Text Disclaimer message.</i></b></span>
Note: If you want to use BB_CL_LIBRARY_PATH to change the default location of where the chat logs are stored, then move the [Library] section from sametime.ini to the chatlogging.ini file.
Example:
[Library]
BB_CL_LIBRARY_PATH=<full_path_name_of_new_directory>
Step 2: Updating stconfig.nsf (database)
There are two ways to enable chat logging, depending on your environment. If using the Sametime System Console (SSC), changes MUST be made through the SSC.
Using the Sametime System Console
If you have configured Sametime 8.5 using the SSC.
1. Log in to the Integrated Solutions Console.
2. Click Sametime System Console > Sametime Servers > Sametime Community Servers.
3. In the Sametime Community Servers list, click the deployment name of the server with the connectivity information that you want to change.
4. Click the Community Services tab.
5. In the Server Features section, under Enable chat logging, select one of the following choices:
Always
When available
Never
6. Click OK
Restart the Lotus Sametime Community Server for settings to take effect.
Using Notes Client to access stconfig.nsf
If you have configured Sametime 8.5 without the SSC.
1. Stop the Sametime 8.5 server. Refer to the technote titled, "Shutting down a Sametime server without shutting down the Domino server" (#1088677).
2. Use a Lotus Notes® client to open the Sametime Configuration database (stconfig.nsf) on the Sametime server.
3. In the right hand pane, open the CommunityServices document by double-clicking on the date associated with the document.
4. Double-click on the CommunityServices document to put the document in edit mode.
5. For the "Chat Logging Flag" parameter, select either "relax" or "strict" for the chat logging mode.
"strict" indicates that chat should be disallowed if it is not possible to log chats for any reason.
6. Update the "Capture Service Type" parameter.
If you selected "strict" as the chat logging mode, enter the value "0x1000" (e.g., Capture Service Type = 0x1000).
If you selected "relax" mode, enter Capture Service Type = 0.
Note: If the Chat Logging service becomes unavailable for any reason when "Chat Logging Flag" is set to "strict" and "Capture Service Type" is set to "0x1000" in the CommunityServices document, users will receive "Chat services unavailable" when attempting to chat. This is by design; the strict setting is being enforced.
7. Save and close the CommunityServices document.
Restart the Lotus Sametime Community Server for changes to take effect.