Sametime Community configure HTTP tunneling + push settings

Per default Sametime will listen on port 1533. As some network infrastructures will
not allow outgoing connections on this port, as an alternative you can specify to
use the HTTP port 80. This technique is called HTTP tunneling.

To configure your Domino/Sametime Community setup for this you can
follow the steps in the Blog item.

With your Notes client open the names.nsf on your Sametime Community server. Navigate to Configuration -> Servers -> “All server documents” and double click on the entry of the Sametime Community server

Within this document go to Ports ->Internet Ports -> Web.

ports 1

 

ports 2

 

 

 

 

 

 

 

Change the TPC/IP port number to something different then port 80. We will
go with port 8080.

Save the changes and restart the http task.

In the Domino console use the following commands to do this.

tell http quit

load http

Change the connection for the Sametime Community server in the SSC. Per default the SSC will make contact to the Sametime server through the Domino HTTP port.

As this changes you will need to change this connection setting in the SSC.

Navigate to the Community server.

ssc1

 

 

 

Click edit “Connection Properties”

ssc2

Change the HTTP port to the value you now configured as the HTTP port for Domino.
In our situation this is port 8080. Press Save.

ssc3

 

 

 

Now click on the “Deployment Identifier” link.

The configuration page of the Community server should open without any errors.

ssc4

 

 

 

 

Scroll down to the “HTTP Tunneled Client Connections” section on the Connectivity tab.

ssc5

 

 

 

 

 

Set the port to 80. Now press OK at the bottom of the page to save the changes.

Now switch back to the Domino console and restart the Sametime Community server.

res server

Now with “managed-settings.xml” and “managed-community-configs.xml” you can
push these setting to the clients. Pushing settings to Sametime clients with these files
is the preferred way to go. Working with Domino policies is far from predictable.

Follow these steps to configure the location from where to provide these two XML files.

Within the SSC menu on the left side go to “Manage policies”

policy1

 

 

 

 

policy 2
Click Edit for the “Sametime Instant Messaging Default Policy”.

policy 3

 

 

 

Find the “Sametime update site URL (IC):” entry.

We use the FQDN of the Sametime Community server + the update directory.

policy 4

 

 

On filesystem level on the Community server you should create this update
directory under /local/notesdata/domino/html/

When done press OK at the bottom of the page.

For initially setting the correct port you can configure the following settings in the
managed-settings.xml file.

<?xml version=”1.0″ encoding=”UTF-8″?>
<ManagedSettings>

>>SNIP<<

 

<settingGroup name=”com.ibm.collaboration.realtime.community”>
<setting name=”loginByToken” value=”true” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”loginAtStartup” value=”true” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”useCanonicalNamesOverride” value=”1″ isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”name” value=”sametime.acmecorp.org” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”host” value=”sametime.acmecorp.org” isLocked=”false” overwriteUnlocked=”true”/>
<setting name=”port” value=”80″ isLocked=”false” overwriteUnlocked=”true”/>

</settingGroup>

 

>>SNIP<<

</ManagedSettings>

For updating existing server communities you can use the following section
in the managed-community-configs.xml file.

<?xml version=”1.0″ encoding=”utf-8″?>
<managed-communities>

>>SNIP<<

<managed-community id=”sametime.e-office.com” host=”sametime.acmecorp.org” port=”80″/>
<managed-community-action type=”update” managed-community-id=”sametime.acmecorp.org”/>

>>SNIP<<

</managed-communities>

A complete list of configurable options can be found here

The settings should work for the stand-alone Sametime Connect client
and the embedded version within IBM Notes.

Shutdown your Sametime Connect client and start it again.
The server community port should now be listed as 80.

This entry was posted in sametime and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

Please leave these two fields as-is:

Protected by Invisible Defender. Showed 403 to 807,336 bad guys.