Introduction

Customer may need to change his network configuration : IP or FQDN or hostname.

These changes need to be updated at application level and are detailed below.

In example below, we are assuming firewalld is performing port forwarding from 443 to 3449.

 

1) GDICT Reconfiguration

Make sur host defined in "GDICT settings" is resolved :

 

This change needs to be taken in account by restart of console :

# systemctl restart systran-ses-console

 

Verify in "Advanced Configuration\Services" that "GDICT" service is green.

 

2) CM Reconfiguration

Make sur host defined in "GDICT settings" is resolved :

 

 

3) Public URLs reconfiguration

This change needs to be taken in account by restart of console :

# systemctl restart systran-ses-console

 

4) Gateway reconfiguration

Check the yaml files in /opt/systran/apps-node/translation-gateway/config/ :

• `hostname`.yaml
• default.yaml

If `hostname`.yaml is present, then there is no need to update default.yaml file.

Just make sure all of the configuration fields have been ported to `hostname`.yaml.

 

In `hostname`.yaml, please update all FQDNs/URLs, output similar to :

  InputInterfaces:
    translate-api:
      authorizationUrl: https://<URL>
      ses8Url: https://<URL>

      OfficePluginsAPI:
        host: <URL>
        port: 8904
        Settings:
          authenticationMode: spnsOAuthPkce # [spnsOAuthPkce, spnsPro]
          resourceUrl: https://<URL>:8904
          authorizationUrl: https://<URL>/oidc

 

This change needs to be taken in account by restart of gateway :

# systemctl restart systran-ses-gateway

 

5) ses-frontend reconfiguration

Make sure /opt/systran/apps-node/enterprise-server/web/config/<hostname>.yaml points to proper FQDN :

 

Restart ses-frontend :

systemctl restart systran-ses-frontend

 

6) Certificate reconfiguration

If FQDN/URL has been changed, check if the corresponding certificates need to be updated from "[STS10] How to update TLS/SSL certificates".

 

7) Services status

Verify in services are all green :

 

 

8) RabbitMQ reconfiguration following hostname change : in case of rabbitMQ issues

If hostname has been changed and if rabbitMQ does not start, please refer to "[SPN9] RabbitMQ server/ Broker failed following a change of hostname".

 

If rabbitMQ still fails to start, you can delete the mnesia/ directory and reconfigure rabbitMQ :

# for i in $(systemctl -a | grep -o "systran.*service"); do systemctl stop $i; done
# systemctl stop rabbitmq-server

# rm -rf /var/lib/rabbitmq/mnesia

# systemctl start rabbitmq-server
# rabbitmqctl add_user systran SESpassword 
# rabbitmqctl set_permissions -p '/' systran '.*' '.*' '.*' 
# rabbitmqctl set_user_tags systran administrator 

# for i in $(systemctl -a | grep -o "systran.*service"); do systemctl start $i; done