• Browse
  • Pages
  • Blog
  • Labels
  • Attachments
  • Mail
  • Bookmarks
  • Activity
  • Advanced
• Log In

1. Dashboard
2. Open Source: Whydah
3. Whydah Home
4. Installing Whydah
5. Application configuration
6. Information
7. Page Comparison

Application configuration

Version 8 by Thor Henning Hetland on Mar 06, 2019 18:21. << Changes from 7 to 8 compared with Current by Thor Henning Hetland on Mar 06, 2019 18:26.

Key This line was removed. This word was removed. This word was added. This line was added.

Comment:

Changes (4)

View Page History

...

h2. Today

h3. Command line
{code}
/usr/bin/java -DIAM_MODE=PROD -DCONSTRETTO_TAGS=DEV -Dlogback.configurationFile=/home/uib/logback.xml -jar /home/uib/UserIdentityBackend.jar
{code}


h4. File system
{code}
clean_logs.sh
CRON
logback.xml
psql_client.sh
start-service.sh
update-service.sh
UserIdentityBackend-2.4.9-20180312.192059-2.jar
UserIdentityBackend-2.5.9.jar
UserIdentityBackend.jar
useridentitybackend_override.properties
data/*
logs/*
{code}


h2. To-be/plan

# Get rid of constretto and stop using the tags concept.

## Use https://github.com/statisticsnorway/dynamic-configuration ?
### https://mvnrepository.com/artifact/no.ssb.config/dynamic-configuration/0.4

# Get rid of ApplicationMode ? ApplicationMode?

## Pros: Less property-files for running instance (
## Cons: Risk of adding and mixing ApplicationMode parameters for a running instance, i.e. an sandbox DEVTEST environment pushing data to persitent storage/state++
# Continue to use _override_ file for properties
# logback.xml is masterfile

* Continue to use _override_ file for properties
* logback.xml is masterfile

h4. Configuration of whydah-application with propertyfile:

...

*On Application startup*
1. Copy uib.properties from jar to filesystem with the name uib_example.properties (Always overwrite)
2. Create an empty file named uib_override.properties, if file does not exists
3. Copy logback.xml from jar to filesystem if file does not exists. (Jeg tror det vil tydeliggjøre hvilke filer man skal endre på filsystemet på en god måte, samtidig som det gjør oppstartskommandoer og systemd-oppsett ganske ryddig. Det vil også gjøre det ganske enkelt å spore forskjeller mellom miljø og applikasjonens defaultkonfigurasjon.)

h4. Some comments/discussion points
Implementasjonsmessig så tror jeg det blir mange små trinn som må gjøres. big bang på alt blir fort vanskelig.
a. Logikk for å kopiere ut config-eksempler fra jar-fil og legge disse i en egen mappe. Alltid overskrive.
b. Lage en mappe config og flytte logback.xml og uib_override.properties dit. Opprette hvis de ikke eksisterer
c. Bli kvitt web.xml-filen og xml-basert spring-konfigurasjon.
Vil gjerne begynne i UIB, for der tror jeg testfeilen henger sammen med at flere tester går i beina på hverandre. Jeg ser ingen kurrant måte å unngå dette på uten å få kontroll på hvilken konfig serveren starter med, som henger sammen med endringene vi nå diskuterer.


h3. File system

{code}
clean_logs.sh
psql_client.sh
start-service.sh
update-service.sh
UserIdentityBackend-2.4.9-20180312.192059-2.jar
UserIdentityBackend-2.5.9.jar
UserIdentityBackend.jar (softlink to versioned jar-file)
logs/*
config/useridentitybackend_override.properties
config/logback.xml
config_examples/useridentitybackend_embeddedLdap_and_db.properties
config_examples/useridentitybackend_everything_on_localhost.properties
config_examples/useridentitybackend_ci.properties
{code}

Powered by a free Atlassian Confluence Community License granted to Cantara AS. Evaluate Confluence today.

• Powered by Atlassian Confluence 3.5.17, the Enterprise Wiki
• Printed by Atlassian Confluence 3.5.17, the Enterprise Wiki.
•   |  Report a bug
•  |  Atlassian News