This document is written to give system administrators and installation technicians a quick introduction to the Foundation1 language concepts in IFS Applications.
The purpose with the language concept is to give the end user as much as possible translated texts. In IFS Applications we differ between client language and database server language.
We also differ between database server stateful session language and stateless session language.
The language is set when the client logins or makes a call to the database, by passing the language to the server session.
The client language is set either by your environment settings, regional settings or by settings a language in the client. The client language is used to translate all text in the client to the chosen language. It is also used to send down to the server in order to tell the server which language all text should be translated to. The client language can be sent to the database server either by login or by every database call dependent on the state of the session.
Database server language is set upon creation of the session. The database session has either retrieved the value from the client or from the environment. Together with the language, territory is also set.
Language impacts the following:
Territory impacts the following:
These definitions is not correct anymore
IFS Windows client use stateful Oracle sessions. During login the language is set and it can not be changed again unless you log off and login again.
All other clients uses stateless Oracle sessions. In this scenario the language is set when the session is created and a user who makes a call must get a server session that matches the client language setting.