Merge branch 'main' into bug6060

### General

* [[Information about this Wiki and HowTo|wiki/info/general/wiki]]

* [[General Project Information|wiki/info/general/general-information]]

* [[Project History|wiki/info/general/project-history]]

* [[Workspace, Bundles, Projects|wiki/info/general/workspace-bundles-projects-structure]]

* [[Runtime Environment|wiki/info/landscape/runtime-environment]]

* [[Basic architectual principles|wiki/info/landscape/basic-architectural-principles]]

* [[User Management|wiki/info/landscape/usermanagement]]

* [[Igtimi Windbot Riot Connector|wiki/info/landscape/igtimi-riot]]

* [[Production Environment|wiki/info/landscape/production-environment]]

* [[Internationalization (i18n)|wiki/howto/development/i18n]]

* [[AI Agent|wiki/info/landscape/ai-agent]]

* [[Malware Scanning|wiki/info/landscape/malware-scanning]]

* Environment Overview [[PDF|wiki/info/mobile/event-tracking/architecture.pdf]] | [[SVG|wiki/info/mobile/event-tracking/architecture.svg]]

* Amazon

* [[Amazon EC2|wiki/info/landscape/amazon-ec2]]

* [[Upgrading ARCHIVE server|wiki/info/landscape/archive-server-upgrade]]

* [[Downloading and Archiving TracTrac Events|wiki/howto/downloading-and-archiving-tractrac-events]]

* [[Data Mining Architecture|wiki/info/landscape/data-mining-architecture]]

* [[Typical Data Mining Scenarios|wiki/info/landscape/typical-data-mining-scenarios]]

* [[sail-insight.com website|wiki/info/landscape/sail-insight.com-website]]

* [[Docker Registry|wiki/info/landscape/docker-registry]]

### Mobile

* [[Mobile Development|wiki/info/mobile/mobile-development]]

echo "

"

BODY=$( cat )

REF=$( echo "${BODY}" | jq -r '.ref' )

PUSHER=$( echo "${BODY}" | jq -r '.pusher.email' )

logger -t github-cgi "ref is $REF, pusher was $PUSHER"

# For testing:

#if [ "${PUSHER}" = "tmsatsls+github.tools.sap_service-tip-git@sap.com" -a "${REF}" = "refs/heads/translation" ]; then

# The filter for github.com:

if [ "${PUSHER}" = "tmsatsls+github.com_service-tip-git@sap.com" -a "${REF}" = "refs/heads/translation" ]; then

echo "Identified a push to refs/heads/translation by ${PUSHER}."

cd /home/wiki/gitwiki

sudo -u wiki git fetch github translation:translation 2>&1

sudo -u wiki git push origin translation:translation 2>&1

else

fi

sudo dnf -y update

sudo dnf -y install mongodb-org-server mongodb-org-tools mongodb-mongosh-shared-openssl3

# ensure that logrotate can work nicely with SIGUSR1:

}

# Copies the /root/secrets and /root/mail.properties file to the local instance, ensuring only root can read it

events=Události

pairingList=Rozpis

pairingLists=Rozpisy

pairingListCreationInfo=Nejprve se vypočítá předloha, která obsahuje pouze čísla závodníků a kterou lze použít i pro jiné výsledkové tabule. Není-li počet závodníků beze zbytku dělitelný počtem lodí, do rozpisu se zadají prázdné zástupné znaky. \ Pokud se počet závodníků nerovná počtu registrovaných závodníků v aktuální výsledkové tabuli, rozpis nebude možné použít pro závodní logy. \ Počet rozjezdů, na jehož základě se tvoří rozpis, je definován počtem rozjezdů ve výsledkové tabuli bez finálových rozjížděk. \ Používají-li se opakované rozjezdy, lze přiřazení do rozjezdů opakovat (např. 15 rozjezdů se třemi opakováními: 5 přiřazení do jedinečných rozjezdů, přičemž se každý bude třikrát opakovat). \ Koeficient změny lodě rovnající se 0 povede k náležitému rozdělení závodníků mezi lodě, zatímco maximální hodnota (=počet rozjezdů) povede k nižšímu počtu změn lodí zvýšením pravděpodobnosti, že závodník popluje na stejné lodi dvě po sobě jdoucí rozjížďky v rozjezdu.

setCompetitors=Nastavte počet závodníků:

setBoatChangeFactor=Nastavte koeficient změny lodě:

successfullyUpdatedCORSAllowedOrigins=Povolené původy CORS byly úspěšně aktualizovány

commandLogOutput=Výstup protokolu příkazu

errorLoadingLeaderboard=Chyba při načítání výsledkové tabule {0}: {1}

events=Begivenheder

pairingList=Parliste

pairingLists=Parlister

pairingListCreationInfo=for det første beregnes en skabelon, der kun indeholder deltagernumrene, og som kan anvendes til andre ranglister. Hvis antallet af deltagere ikke kan divideres med antallet af både uden rest, indsættes tomme pladsholdere i parlisten. \ Hvis antallet af deltagere derudover ikke er lig med antallet af tilmeldte deltagere i den faktiske rangliste, kan parlisten ikke anvendes på kapsejladsprotokoller. \ Antallet af løb, der bruges til at generere en parliste, defineres af antallet af løb i ranglisten, der ikke er medaljesejladser. \ Når gentagne løb bruges, kan tildelinger af løb gentages (fx 15 løb med 3 gentagne løb: 5 unikke tildelinger af løb, og hver af dem gentages 3 gange). \ En bådændringsfaktor lig med 0 medfører en veldistribueret tildeligen af deltagere til både, hvorimod maksimumværdien (antal løb) medfører færre bådændringer ved at øge chancen for, at en deltager sejler med den samme båd i mere end 2 fortløbende kapsejladser på tværs af en løbsgrænse.

setCompetitors=Sæt antallet af deltagere:

setBoatChangeFactor=Sæt bådændringsfaktor:

successfullyUpdatedCORSAllowedOrigins=Tilladte oprindelser for CORS blev opdateret

commandLogOutput=Logoutput for kommando

errorLoadingLeaderboard=Fejl ved indlæsning af rangliste {0}: {1}

events=Eventos

pairingList=Lista de emparejamientos

pairingLists=Listas de emparejamientos

pairingListCreationInfo=Inicialmente se calculará una plantilla que contenga solo los números de los competidores y que pueda aplicarse a otras clasificaciones. Si el recuento de competidores no es divisible por recuento de embarcaciones sin remanente, se introducirán marcadores de posición en blanco en la lista de emparejamientos. \ Además, si el recuento de competidores difiere del recuento de competidores registrado en la clasificación real, la lista de emparejamientos no podrá aplicarse a los registros de la prueba. \ El recuento de flights, que se utiliza para generar una lista de emparejamientos, está definido por el número de flights de la clasificación que no son pruebas de medalla. \ Cuando se utilizan repeticiones de flight, se pueden repetir asignaciones de flights (por ejemplo, 15 flights con 3 repeticiones de flight: 5 asignaciones de flight únicas que se repetirán 3 veces cada una de ellas). \ Un factor de cambio de embarcación equivalente a 0 da como resultado una asignación bien distribuida de competidores y embarcaciones, considerando que el máximo (número de flights) provoca menos cambios de embarcación aumentando las posibilidades de que un competidor navegue con la misma embarcación en dos pruebas contiguas a través de un límite de flights.

setCompetitors=Fije el recuento de competidores:

setBoatChangeFactor=Fije el factor de cambio de embarcación:

successfullyUpdatedCORSAllowedOrigins=Orígenes permitidos CORS actualizados correctamente

commandLogOutput=Salida de log de comandos

errorLoadingLeaderboard=Error al cargar la tabla de clasificación {0}: {1}

events=Manifestations

pairingList=Liste d''appariement

pairingLists=Listes d''appariement

pairingListCreationInfo=Tout d''abord, un modèle contenant uniquement le nombre de concurrents sera calculé. Il pourra être appliqué à d''autres palmarès. Si la division du nombre de concurrents par le nombre de bateaux ne permet pas d''obtenir un nombre entier, des espaces réservés vides seront ajoutés à la liste d''appariement. \ En outre, si le nombre de concurrents ne correspond pas au nombre de concurrents inscrits au palmarès actuel, la liste d''appariement ne pourra pas être appliquée aux journaux de course. \ Le nombre de flights (matchs) utilisé pour générer une liste d''appariement est défini par tous les flights du palmarès, hors courses médaillées. \ En cas de répétition des flights, les affectations de flights peuvent être répétées (par exemple, 15 flights avec 3 répétitions : 5 affectations de flights uniques, et chacun sera répété 3 fois). \ Un facteur de changement de bateau équivalent à 0 permet une répartition correcte des concurrents sur les bateaux, alors que le nombre de flights maximum implique moins de changements de bateaux en augmentant les chances qu''un concurrent navigue sur un même bateau pour deux courses consécutives trans-flight.

setCompetitors=Veuillez définir le nombre de concurrents :

setBoatChangeFactor=Veuillez définir le facteur de changement de bateau :

successfullyUpdatedCORSAllowedOrigins=Origines autorisées CORS mises à jour

commandLogOutput=Édition du journal des commandes

errorLoadingLeaderboard=Erreur lors du chargement du palmarès {0} : {1}

events=Eventi

pairingList=Pairing list

pairingLists=Pairing lists

pairingListCreationInfo=Innanzitutto verrà calcolato un modello contenente solo i numeri dei concorrenti che potrà essere applicato ad altre classifiche. Se il numero di concorrenti non è divisibile per il numero di barche senza promemoria, nella pairing list verranno inseriti segnaposti vuoti. \ Inoltre, se il numero dei concorrenti è diverso dal numero di concorrenti registrati nella classifica effettiva, la pairing list non potrà applicarsi ai registri della gara. \ Il numero di voli utilizzato per generare una pairing list è definito dal numero di voli nella classifica di gare diverse dalla medal race. \ Quando si utilizzano ripetizioni di volo, è possibile ripetere assegnazioni di volo (ad esempio 15 voli con 3 ripetizioni: 5 assegnazioni univoche di voli, ciascuna delle quali verrà ripetuta 3 volte). \ Un fattore di cambio barca uguale a 0 porta a un''assegnazione ben distribuita di concorrenti nelle barche, mentre il massimo (numero di voli) porta a un numero inferiore di cambi barca aumentando le possibilità che un concorrente gareggi nella stessa barca per due gare contigue oltre un confine del volo.

setCompetitors=Impostare il numero di concorrenti:

setBoatChangeFactor=Impostare il fattore di cambio barca:

successfullyUpdatedCORSAllowedOrigins=Origini CORS consentite aggiornate correttamente

commandLogOutput=Output del registro di comando

errorLoadingLeaderboard=Errore di caricamento della classifica {0}: {1}

events=イベント

pairingList=対戦表

pairingLists=対戦表

pairingListCreationInfo=まず最初に、競技者番号のみが含まれていて、他のリーダーボードに適用できるテンプレートがすべて計算されます。競技者カウントが艇カウントで割り切れない場合、空のプレースホルダーが対戦表に入力されます。 \ また、競技者カウントが実際のリーダーボードにある登録済の競技者カウントと等しくない場合、対戦表をレースログに適用することはできません。 \ 対戦表を生成するために使用されるフライトのカウントは、リーダーボードにあるメダルレースでないフライトの回数によって設定されます。 \ フライト繰返の使用時に、フライト割当を繰り返すことができます (例: 3 つのフライト繰返がある 15 回のフライトでは、別々の 5 つのフライト割当でそれぞれが 3 回繰り返されます)。 \ 艇変更係数が 0 に等しければ、艇への競技者の割当がうまく配分されることにつながり、一方、最大 (フライト回数) になると、フライトの境界を超えて隣接している 2 つのレースで競技者が同一艇で帆走する可能性が高くなることで艇変更がより少なくなります。

setCompetitors=競技者カウントを設定してください:

setBoatChangeFactor=艇変更係数を設定してください:

successfullyUpdatedCORSAllowedOrigins=CORS 許可済みソースが更新されました

commandLogOutput=コマンドログ出力

errorLoadingLeaderboard=リーダーボード {0} のロードでエラーが発生: {1}

events=Eventos

pairingList=Lista de pares

pairingLists=Listas de pares

pairingListCreationInfo=Primeiro será calculado um modelo que contém somente os números dos competidores e pode ser aplicado a outros painéis de classificação. Se contagem de competidores não for divisível pela contagem de barcos sem restante, os caracteres de preenchimento em branco serão inseridos na lista de pares. \ Além disso, se a contagem de competidores for diferente da contagem de competidores registrados no painel de classificação real, a lista de pares não pode ser aplicada aos registros das corridas. \ A contagem de voos, que é utilizada para gerar uma lista de pares, é definida pelo número de voos no painel de classificação que não sejam corridas para medalha. \ Ao utilizar repetições de voo, as atribuições de voo podem ser repetidas (por exemplo, 15 voos com 3 repetições de voo: 5 atribuições de voo únicas e cada uma será repetida 3 vezes). \ Um fator de mudança de barco igual a 0 leva a uma atribuição bem distribuída de competidores a barcos, sendo que o (número de voos) máximo leva a menos mudanças de barco aumentando as hipóteses de um competidor navegar no mesmo barco em duas corridas contínuas além do limite do voo.

setCompetitors=Defina a contagem dos competidores:

setBoatChangeFactor=Defina o fator de mudança de barco:

successfullyUpdatedCORSAllowedOrigins=Origens permitidas CORS atualizadas com êxito

commandLogOutput=Saída do log de comando

errorLoadingLeaderboard=Erro ao carregar o painel de classificação {0}: {1}

events=События

pairingList=Список пар

pairingLists=Списки пар

pairingListCreationInfo=Первым будет рассчитан шаблон, который содержит только номера участников и может быть применен к другим таблицам лидеров. Если число участников не делится на число лодок без остатка, в списке пар будут пустые места. \ Если число участников не равно числу зарегистрированных участников в фактической таблице лидеров, список пар не может быть применен к журналам гонки. \ Для генерирования списка пар используется число всех флайтов таблицы лидеров, не являющихся гонками на медали. \ Если используются повторы флайтов, то присвоения флайтов могут повторяться (например, 15 флайтов с 3 повторами: 5 уникальных присвоений флайтов, каждый из которых повторяется 3 раза). \ Результатом нулевого коэффициента смены лодки является хорошее распределение участников по лодкам, то есть максимум (число флайтов) ведет к меньшему числу смен лодок, и это увеличивает шансы, что участник будет плыть на одной и той же лодке в двух смежных гонках до окончания флайта.

setCompetitors=Укажите число участников:

setBoatChangeFactor=Укажите коэффициент смены лодки:

successfullyUpdatedCORSAllowedOrigins=Разрешенные происхождения CORS обновлены

commandLogOutput=Вывод журнала команд

errorLoadingLeaderboard=Ошибка при загрузке таблицы лидеров {0}: {1}

events=Dogodki

pairingList=Seznam parov

pairingLists=Seznami parov

pairingListCreationInfo=Najprej bo izračunana predloga, ki vsebuje samo številke tekmovalcev in jo je mogoče uporabiti za druge lestvice vodilnih. Če število tekmovalcev ni deljivo s številom jadrnic brez ostanka, bodo na seznam parov dodane prazne označbe mesta. \ Če število tekmovalcev ni enako številu registriranih tekmovalcev na aktualni lestvici vodilnih, seznama parov ni mogoče uporabiti za dnevnike plovov. \ Število jadranj, uporabljeno za generiranje seznama parov, je opredeljeno kot število jadranj na lestvici vodilnih, ki niso plovi za kolajne. \ Pri uporabi ponovitev jadranj je mogoče ponoviti dodelitve jadranj (npr. 15 jadranj s 3 ponovitvami jadranj: 5 enkratnih dodelitev jadranj, kjer se vsaka ponovi 3-krat). \ Faktor menjave jadrnice, ki je enak 0, pomeni enakomerno porazdeljeno dodelitev tekmovalcev jadrnicam, največje (število jadranj) pa pomeni manj menjav jadrnic, zato je večja verjetnost, da bo tekmovalec z isto jadrnico jadral dva plova zapored znotraj meja jadranja.

setCompetitors=Nastavite število tekmovalcev:

setBoatChangeFactor=Nastavite faktor menjave jadrnic:

successfullyUpdatedCORSAllowedOrigins=Uspešno posodobljeni CORS - dovoljeno poreklo

commandLogOutput=Izdaja dnevnika ukazov

errorLoadingLeaderboard=Napaka pri prenosu lestvice vodilnih {0}: {1}

events=活动

pairingList=配对清单

pairingLists=配对清单

pairingListCreationInfo=首先，将计算仅包含参赛队数并且可以应用到其他积分榜的模板。如果参赛队数量无法被船只数量除尽，则在配对清单中输入空占位符。\ 此外，如果参赛队数量不等于实际积分榜中注册的参赛队数量，配对清单无法应用到比赛轮次日志。\ 用于生成配对清单的航程数由积分榜中不是奖牌轮的航程数定义。\ 使用航程重复时，可以重复航程分配（例如，有 3 个航程重复的 15 个航程：5 个独特的航程分配，每个重复 3 次）。\ 船只更换系数等于 0 导致向船只平均分配参赛队，而最大值（航程数）通过提高参赛队在两个连续的比赛轮次驾驶同一船只驶过航程边界的机会来减少换船次数。

setCompetitors=请设置参赛队数量：

setBoatChangeFactor=请设置船只更换系数：

successfullyUpdatedCORSAllowedOrigins=已成功更新 CORS 允许的来源

commandLogOutput=命令日志输出

errorLoadingLeaderboard=加载积分榜 {0} 出错：{1}

<li>Upon popular demand, the series editing dialog now supports not only 50 but 100

race columns / flights to be created in the drop-down list.</li>

<li>AI Agent credentials can now be reset from the Admin Console.</li>

</ul>

<h2 class="articleSubheadline">June 2025</h2>

<ul class="bulletList">

* "default" version. See, e.g., {@link LaunchTemplateSpecification#version()}.

*/

String DEFAULT_LAUNCH_TEMPLATE_VERSION_NAME = "$Default";

InstanceType[] INSTANCE_TYPES_BANNED_FROM_INSTANCE_BASED_NLB_TARGET_GROUPS = new InstanceType[] { InstanceType.CC1_4_XLARGE, InstanceType.C1_MEDIUM, InstanceType.C1_XLARGE,

InstanceType.CC2_8_XLARGE, InstanceType.CG1_4_XLARGE, InstanceType.CR1_8_XLARGE, InstanceType.G2_2_XLARGE,

import software.amazon.awssdk.services.route53.paginators.ListResourceRecordSetsIterable;

import software.amazon.awssdk.services.sts.StsClient;

import software.amazon.awssdk.services.sts.model.Credentials;

public class AwsLandscapeImpl<ShardingKey> implements AwsLandscape<ShardingKey> {

private static final String SSL_SECURITY_POLICY = "ELBSecurityPolicy-FS-1-2-Res-2019-08";

return getClient(ElasticLoadBalancingV2Client.builder(), region);

}

private ElasticLoadBalancingV2AsyncClient getLoadBalancingAsyncClient(Region region) {

return getClient(ElasticLoadBalancingV2AsyncClient.builder(), region);

}

final ApplicationLoadBalancer<ShardingKey> result = new ApplicationLoadBalancerImpl<>(region, response.loadBalancers().iterator().next(), this);

createLoadBalancerHttpListener(result);

createLoadBalancerHttpsListener(result);

return result;

}

private Subnet getSubnetForAvailabilityZoneInSameVpcAsSecurityGroup(AwsAvailabilityZone az, SecurityGroup securityGroup, Region region) {

final Ec2Client ec2Client = getEc2Client(region);

final String vpcId = ec2Client.describeSecurityGroups(b->b.groupIds(securityGroup.getId())).securityGroups().iterator().next().vpcId();

## Collecting measurements using Hudson/Jenkins

# OnBoarding Information

This document describes the onboarding process for a new team member (developer)

First of all, make sure you've looked at [http://www.amazon.de/Patterns-Elements-Reusable-Object-Oriented-Software/dp/0201633612](http://www.amazon.de/Patterns-Elements-Reusable-Object-Oriented-Software/dp/0201633612). That's a great book, and knowing at least some of it will help you a great deal finding your way around our solution.

### Accounts

1. Git Account

Note: If you want to use the ssh-key in the context of our solution, it can be an RSA or ED25519 format. Example for creating a key: `ssh-keygen -t ed25519 -b 512 -C "test@test.com"`. Make sure to set a non-empty password for your key.

2. Bugzilla

- Create an account at https://bugzilla.sapsailing.com

3. Wiki

4. Hudson

- Request a [Hudson](https://hudson.sapsailing.com) user by sending e-mail to Axel Uhl or Simon Marcel Pamies.

### Installations

1. Eclipse IDE for Eclipse Committers, version ["2025-03"](https://www.eclipse.org/downloads/packages/release/2025-03/r/eclipse-ide-eclipse-committers). If you are using a Mac and want to use SAPJVM, this has to be the 64 bit version. This is because SAPJVM is not available for Apple Silicon Macs, and Eclipse's OS architecture must match the JVM architecture.

2. JDK 1.8 (Java SE 8), ideal is the SAPJVM 1.8: Go to [https://tools.eu1.hana.ondemand.com/#cloud](https://tools.eu1.hana.ondemand.com/#cloud), scroll down to `SAP JVM` select your operating System, extract the downloaded .zip into desired location (e.g. Windows `C:\Program Files\Java`. If you want to make this your default JDK, set the `JAVA_HOME` variable to it. In any case, set the `JAVA8_HOME` variable to it which is required by a few build scripts where certain steps currently are not yet compatible with newer JDK releases, such as our Android build process, keeping us on Gradle 6.0.1 for the time being which isn't Java 17-compatible.

3. Git (e.g. Git for Windows v2.18), [http://git-scm.com](http://git-scm.com) / [https://git-for-windows.github.io](https://git-for-windows.github.io)still

9. Standalone Android SDK (see section "Additional steps required for Android projects"). OPTIONALLY: You may additionally install Android Studio ([https://developer.android.com/tools/studio/index.html](https://developer.android.com/tools/studio/index.html)) or IntelliJ IDEA ([https://www.jetbrains.com/idea/download/](https://www.jetbrains.com/idea/download/)).

Make sure that the environment variable `ANDROID_HOME` is set (e.g. Windows C:\Users\\**'user'**\AppData\Local\Android\Sdk )

10. Get the content of the git repository

11. Install the eclipse plugins (see [Automatic Eclipse plugin installation](#onboarding-information_sap-sailing-analytics-development-setup_automatic-eclipse-plugin-installation))

12. Configure Eclipse (see [Tuning the Eclipse Installation](#onboarding-information_sap-sailing-analytics-development-setup_tuning-the-eclipse-installation))

13. Configure Maven to use the correct JRE by following the instructions in the paragraph [maven-setup](#onboarding-information_sap-sailing-analytics-development-setup_maven-setup)

### Further optional but recommended installations

Please note that when using one of the newer versions of Cygwin, your Cygwin home folder setting might differ from your Windows home folder. This will likely lead to problems when issuing certain commands. For troubleshooting, take a look at the following thread: [https://stackoverflow.com/questions/1494658/how-can-i-change-my-cygwin-home-folder-after-installation](https://stackoverflow.com/questions/1494658/how-can-i-change-my-cygwin-home-folder-after-installation)

2. Eclipse Mylyn Bugzilla extension

3. kdiff3 (git tool)

4. Firebug (javascript & .css debugging, included in Firefox Developer Tools in newer versions of Firefox by default)

### Git repository configuration essentials

The project has some configuration of line endings for specific file types in ".gitattributes". To make this work as intended, you need to ensure that the git attribute "core.autocrlf" is set to "false". This can be done by navigating to your local repository in a Bash/Git Bash/Cygwin instance and executing the command `git config core.autocrlf false`.

### Maven Setup

### Automatic Eclipse plugin installation

The necessary Eclipse plugins can be automatically installed into a newly unzipped version of ["2023-09"](https://www.eclipse.org/downloads/packages/release/2023-09/r/eclipse-ide-eclipse-committers) by using the `./configuration/pluginsForEclipse2025-03.p2f` file, found in the git repository cloned in _step 11_. To install the plugins open Eclipse and install Software Items from File. (File ⇒ Import ⇒ Install ⇒ Install Software from File). The description file is located at `/configuration/pluginsForEclipse2025-03.p2f`.

- For Eclipse-based debugging of GWT web applications with SDBG, make sure that Chrome is set as your default browser: "General ⇒ Web Browser". If missing, add a profile for Chrome and specify "%URL%" as the parameter.

- Consider installing [https://marketplace.eclipse.org/content/protocol-buffer-editor](https://marketplace.eclipse.org/content/protocol-buffer-editor) for a Protocol Buffers (protobuf) editor

2. Setup and configure Eclipse

- Import all Race Analysis projects from the `java/` subdirectory of the git main folder (make sure to import via the wizard [but without smart import] "Import ⇒ General ⇒ Projects from Folder or Archive" in Eclipse, and additionally make sure to scan for nested projects!)

- In "Window ⇒ Preferences ⇒ Plug-in Development ⇒ Target Platform" set the Eclipse target platform to `Race Analysis Target` (located in com.sap.sailing.targetplatform/definitions//race-analysis-p2-remote.target)

- Wait until the target platform has been resolved completely

- Start a clean build (Project ⇒ Clean)

1. Run "GWT Dashboards SDM" launch configuration. After successful start, launch configuration can be stopped.

2. Run "GWT Security SDM" launch configuration. After successful start, launch configuration can be stopped.

3. Run "GWT xdStorage Sample SDM" launch configuration. After successful start, launch configuration can be stopped.

4. Run the Race Analysis Suite

1. Create a folder for the mongoDB to store the data. For existing folders make sure they do not contain a `mongod.lock` file

2. Open a terminal and navigate to the location of the MongoDB installation `cd /somePathTo MongoDBInstallation/mongodb/bin`

3. Start the databse in the with the mongoDB Datafolder as db path:

`./mongod --dbpath /somePathTo/MongoDBDataDirectory`

2. Run "GWT Sailing SDM" in the debug dropdown

5. Import races within the Race Analysis Suite

- Default Login: user "admin", password "admin"

- In the list on the left, click on "Connectors"

- For TracTrac Events: In the "TracTrac Connections" Form, fill in the JSON URL [http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php](http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php)(all other required information will be filled in automatically)

- Press "List Races"

6. Further useful launch configurations

- Use SAP JVM Profiler. If you used the script above and installed the SAPJVM instead of the jdk, you can now open the profiling perspective by clicking on Window ⇒ Perspective ⇒ Open Perspective ⇒ Profiling)

- Debugging gwt: For further instructions please see [here](./development/super-dev-mode)

If you want to use **breakpoints**, *avoid* clicking on the options in the Development Mode tab. Instead, within the _Debug Configurations_ menu, select the _Debug AdminConsole_ (found in the _Launch Browser_ subtab); change the browser search order, such that chrome is the leftmost; and then launch. This is necessary because SDBG is compatible with Chrome. Further, details of how GWT Super Dev Mode (SDM) works, can be found in the link above.

The Android Apps can be built in Android Studio or gradle command line. Android Studio is built on top of IntelliJ IDEA, so it is possible to use IntelliJ IDEA as well.

If git is not in the Path system environment variable, the gradle build will not work.

### Git usage troubleshooting

There are some inconsistencies regarding line endings (unix vs windows) in our git repository. There is a configuration named ".gitattributes" committed to the root folder of the repository that helps to prevent inconsistencies of line endings when committing files. Files that existed before are partially using unix (LF) or windows (CRLF) line endings. When committing files, git will ensure unix line endings for e.g. \*.java files. This can lead to big diffs that hurt when trying to merge/diff.

In such cases it might help to set AWT to headless mode (`-Djava.awt.headless=true`, see [stackoverflow](https://stackoverflow.com/questions/13796611/imageio-read-with-mac for more information)).

Another struggle can be to install the JVM Profiler Plug-in on ARM based Eclipse. It seems to block the necessary Software while the Automatic Eclipse plugin installation. One way is to use the Eclipse x64 Installer. It will take more time for transformation, but you will be able to use the Profiler.

Install the GWT Browser Plugin for the GWT Development mode. As of 2016-08-31 Firefox is the only browser supporting the GWT plugin, you have to download Firefox version 24 for it to work. The Plugin can be found on this page: [https://code.google.com/archive/p/google-web-toolkit/downloads](https://code.google.com/archive/p/google-web-toolkit/downloads)

### Create Hudson Job

If you want a hudson job to run when you push your branch then you can run a script in `configuration` called . Run options for a branch titled `createHudsonJobForBug.sh`. For you bug branch titled `bug<bug number>`, create a build job, which will create a release, by running the script like so: `./createHudsonJobForBug.sh <bug number>`.

### Issues when playing around with AWS

- The problem: **aws cli (used for aws ec2 describe-tags) hangs in eu-west-2** in all AZs on new instances I created, using a target group which permitted all outbound connections and inbound https, http and ssh connections. I tried permitting everything but that didn’t work. When I attached (at Axel’s suggestion) the Java Application with Reverse Proxy security group, it worked but — even if I duplicated this security group, and applied that copy instead — it still didn’t work.

Curl issue solution: it turns out that the network interface only permits certain outbound and inbounds from certain target groups.

- Problem: A load balancer's target group health checks fail. I was told the checks failed with 403 errors.

Solution: This was occurring because the website didn't have any content in the /var/www/html. Whilst a site was still served (namely the Apache test page) it does throw a 403 error. If you fill the directory with and index.html the test then passes and a 200 code is returned

- Problem: Target platform reload in Eclipse. Sometimes reloading via Window -> Plug-in Development -> Target Platform doesn't work, so open the target definition itself and try reloading there. Often a restart proves helpful after the reload. In addition, you can clean all projects and rebuild; then rebuild the individual projects that fail. Sometimes the errors are actually just warnings and you can try to run the GWT SDM (remember the other SDM's must be run if everything is brand new). Lastly, try clearing the plugins content found at `WORKSPACE_HOME/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins`.

- if the request method is ``GET`` then forward to the public target group

- forward all other request for the hostname to the master target group

There are currently three MongoDB replica sets:

## Legacy Documentation for Manual Operations

#### Starting an instance

[[_TOC_]]

## Maven Build and Tests

We have a top-level Maven pom.xml configuration file in the root folder of our Git workspace. It delegates to the pom.xml file in the java/ folder where all the bundle projects are defined. We rely on the Tycho Maven plug-in to build our OSGi bundles, also known as the "manifest-first approach." The key idea is to mainly develop using Eclipse means, including its OSGi manifest editing capabilities, and keep the Maven infrastructure as simple as possible, deriving component dependencies from the OSGi manifests. See the various pom.xml files in the projects to see the project-specific settings. By and large, a pom.xml file for a bundle needs to have the bundle name and version defined (we currently have most bundles at version 1.0.0.qualifier in the manifest or 1.0.0.SNAPSHOT in Maven), and whether the bundle is a test or non-test bundle, expressed as the packaging type which here can be one of eclipse-plugin or ecplise-test-plugin.

All these build lines also creates a log file with all error messages, just in case the screen buffer is not sufficient to hold all scrolling error messages.

By default the duration of each test is published and can be viewed in comparison with older builds. It is possible to publish other values using the Measurement Plugin, which reads them out of a `MeasurementXMLFile`.

MeasurementCase performanceReportCase = performanceReport.addCase(getClass().getSimpleName());

performanceReportCase.addMeasurement(new Measurement("MeasurementName", measurementValue));

```

[[_TOC_]]

## Adding a Bundle to the Target Platform

* Add a New Library which can not be found in any SAP Repository

* Currently this scripts work for the cygwin shell and the git bash, if the path to your files in the target definition is incorrect, this may be the reason.

* Test the new overall target platform

* by setting the race-analysis-p2-local.target as target platform in the IDE

* The admin of the central p2 repository (currently at sapsailing.com) must now replace the content of the central server /home/trac/p2-repositories/sailing with the content of the new local base p2 repository (com.sap.sailing.targetplatform.base/target/repository), using the 'uploadRepositoryToServer.sh' script

* Reload the target platform in the IDE

This document describes the basics of how the Shiro framework has been selected and is being used to implement role-based access control. See [Permission Concept](/wiki/info/security/permission-concept) to understand how, based on Shiro, a security architecture with user groups, users, qualified roles, ownerships and access control lists works.

[[_TOC_]]

We plan to turn the `UserManagementPanel` which is the widget behind the `UserManagementEntryPoint` into a drop-in component for a generalized administration console concept. So, when the AdminConsole becomes an SSE concept then the user management tab can be made available to all applications using the AdminConsole concept. See also bugs [2424](http://bugzilla.sapsailing.com/bugzilla/show_bug.cgi?id=2424) and [2425](http://bugzilla.sapsailing.com/bugzilla/show_bug.cgi?id=2425).

## Sample Session

When you try to reach a protected resource without having the necessary permissions, Shiro will redirect you to the sign-in page.