Thanks to all who attended today's OpenText Support Community Event: Customer Contributions to Knowledge Program.

A recording of the event and the next steps to start your contributions can be found here:

Customer Contributions to Knowledge Presentation

Let's get started!
Important message to TeamSite, LiveSite, and OpenDeploy community.

Today we are pleased to announce another community release for docker support (version 3). As part of this enhancement now applying the patch and upgrade from a previously created container using Docker Orchestration scripts provided by OpenText for TeamSite, LiveSite, and OpenDeploy. We support 16.2 and 16.3 containerization using provided automation scripts. This release marks our third release of docker support for TeamSite, LiveSite, and OpenDeploy.

Please join us on this journey and contribute by engaging on a special focus forum: TeamSite, LiveSite, and OpenDeploy - Docker. To obtain the automation for Docker, log in to MySupport, navigate to Product>OTDN>Web Content Management (TeamSite)>TeamSite, LiveSite, OpenDeploy> Docker Automation>16.3 or Product>OTDN>Web Content Management (TeamSite)>TeamSite, LiveSite, OpenDeploy> Docker Automation>16.2.”

A new bit of oddness with iw.cfg on 8.2 with server_locale

Set server_locale in iw.cfg to UTF-8. Upon restarting teamsite, it inserts a line setting it back to Latin1.

Before restart:

[email protected];

After restart:

[email protected];
[email protected];

This is munging any character with diacritics, which is **** our install big time.


  • Adding: TS, Solaris10, OS is set to utf-8

  • Poking around on this, came across this in the 8.0 docs:

    The iw.cfg file contains a server_locale entry in the [iwserver] section. The entry specifies the locale in which current execution of the TeamSite server (iwserver) runs. For example:

    server_locale=English_UnitedStates.MS1252 (Windows)US-ASCII (Unix)@Binary;

    This setting is automatically created in the iw.cfg file when iwserver is started. The native/system locale is determined by reading the LANG environment variable (Unix)/System Locale setting in the Regional Settings control (Windows). Once the server_locale setting exists in the iw.cfg file, it is used to determine the TeamSite server’s native/system locale at every invocation of iwserver. If this setting is not present, iwserver determines its locale from the LANG environment variable (Unix) /System Locale setting in the Regional Settings control panel (Windows).

    While this setting can be user-modified, it is designed to serve as reference as to the locale in which iwserver is currently running. If you have a situation where you want to force iwserver to run in a particular locale (independent of the LANG environment variable (Unix)/System Locale setting (Windows), you can stop the TeamSite server, manually edit the server_locale line, then restart the TeamSite server.

    Which is not working as expected. Our OS language is set to UTF-8.

    [email protected]: echo $LANG


    Continuing to dig into it.

  • edited October 2017

    Opened a ticket with support about this issue. So far the response has been "You can't have two server_locale lines in iw.cfg."

    Well yes, we know that, the problem isn't that we're putting in two lines, it's that TeamSite is ADDING the second line.


  • You can have any color you want as long as it is black...... :-)

  • FYI: Finally heard back on support regarding this issue. It's a confirmed bug, but they won't be fixing it anytime soon.

  • Just confirmed at my current client: this also affects windows.

  • edited January 15

    It looks like the might be failing during the installation and not reporting it, but I can't be 100% certain. Just something to keep an eye on for installations of 8.2.

Sign In or Register to comment.