<commit_before>See also [Installation Instructions](https://github.com/qcri-social/AIDR/wiki/Installation-instructions)

# 1. Starting AIDR

Deployment of all aidr.* WAR files (e.g., aidr_collector.war, aidr_tagger_api.war, etc.) to application server (e.g., GlassFish) means AIDR platform is up and running. 

# 2. Stopping AIDR

One can simply un-deploy one of the AIDR applications from application server using standard un-deploy operation. For example, in case of GlassFish server, use GlassFish administration console (i.e., http://localhost:4848/), go to application tab select application that you want to un-deploy and press the un-deploy button.

# 3. Re-starting AIDR

To re-starting an application perform the above two steps by stopping the application first and then starting it again.

One can re-start the application server to re-start all applications by using re-start command of application server. For example, in case of GlassFish server do:

`./bin/asadmin restart-domain`
<commit_msg>Updated System administrator manual (markdown)<commit_after>See also [Installation Instructions](https://github.com/qcri-social/AIDR/wiki/Installation-instructions)

# 1. Starting AIDR

Successful deployment of all aidr.* WAR files (e.g., aidr_collector.war, aidr_tagger_api.war, etc.) to application server (e.g., GlassFish) means AIDR platform is up and running. For example, in case of GlassFish server, use GlassFish administration console (i.e., http://localhost:4848/), go to the application tab select application that you want to deploy and press the deploy button. 

# 2. Stopping AIDR

One can simply un-deploy one of the AIDR applications from application server using standard un-deploy operation. For example, in case of GlassFish server, use GlassFish administration console (i.e., http://localhost:4848/), go to application tab select application that you want to un-deploy and press the un-deploy button.

# 3. Re-starting AIDR

To re-starting an application perform the above two steps by stopping the application first and then starting it again.

One can re-start the application server to re-start all applications by using re-start command of the application server. For example, in case of GlassFish server do:

`./bin/asadmin restart-domain`

{'fraction_non_alphanumeric': 0.0730312362516498, 'fraction_numerical': 0.007919049714034315, 'mean_word_length': 4.614814814814815, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5875030', 'n_tokens_mistral': 641, 'n_tokens_neox': 603, 'n_words': 288}