ST 12.0.1: using local sametime.ini

Hi Community Members,

If I use local sametime.ini I can't login to sametime anymore (Notes embedded, Verse/iNotes, fqdn/chat,fqdn /meeting

What i've done so far:

1/ Extract sametime.ini from docker container

docker cp sametime_community_1/local/notesdata/sametime.ini .

2/ Edit docker-compose.yml to add sametime.ini:

community:
image: hclcr.io/st/chat-server:${BUILD_LEVEL}
restart: ${RESTART_POLICY}
env_file:
- custom.env
- tlsldap.env
environment:
- JWT_SECRET_ENV=${JWT_APP_SECRET}
- DOMINO_SERVER_HOST_ENV=domino
- DOMINO_SERVER_NAME_ENV=CN\=domino\/O\=test
- DOMINO_SERVER_DOMAIN_ENV=test
- ST_BRANDING_INFO_ENV=standard
volumes:
- ./policies.user.xml:/local/notesdata/policies.user.xml
- ./policies.server.xml:/local/notesdata/policies.server.xml
- ./StCommunityConfig.xml:/local/notesdata/StCommunityConfig.xml
- ./UserInfoConfig.xml:/local/notesdata/UserInfoConfig.xml
- ./ldaptruststore.p12:/local/notesdata/ldaptruststore.p12
- ./sametime.ini:/local/notesdata/sametime.ini

3/ docker-compose down: OK

4/ docker-compose up -d: OK

5/ cannot login to sametime

6/ docker-compose down

7/ Edit again the file docker-compose.ym, remove the sametime.ini line

l- ./sametime.ini:/local/notesdata/sametime.ini

8/ docker-compose up -d

9/ I can login successfully (Notes embedded with domino sso, vers/inotes with SSO)

Any idea about what I am doing wrong?

After step 4, i've just tried:

docker container exec -it sametime_community_1 /bin/bash
Error response from daemon: Container 22536d06f0653c074b59abd296a78bd5bb7a77555db974f3e904da41441cee9b is restarting, wait until the container is running

Your steps are 'correct', however we do not support over-riding the sametime.ini - it is dynamically generated.

What are you trying to set in the ini? there are other methods to update setttings.

Hi @Anthony Payne , I was just interested with that page "https://support.hcltechsw.com/csm?id=community_question&sys_id=34224bd4db491d50a45ad9fcd39619b6&view_source=searchResult" concerning the local sametime.ini. But well I'll just have to get the old sametime.ini variables list and manually put them into custom.env or others env files...

I see.

That is not a method I would recommend for the sametime.ini, for multiple reasons. We have the ability (as noted in that post) to over-ride the various settings as needed.

Let us know if you need assistance with them.