Proyecto

General

Perfil

Wildfly by Neodoo En » Histórico » Versión 2

Francisco Javier Solans Benedí, 2024-04-10 07:26

1 2 Francisco Javier Solans Benedí
{{toc}}
2 1 Francisco Javier Solans Benedí
3 2 Francisco Javier Solans Benedí
# Usage Instructions
4 1 Francisco Javier Solans Benedí
5 2 Francisco Javier Solans Benedí
## Getting started
6 1 Francisco Javier Solans Benedí
7 2 Francisco Javier Solans Benedí
1. Launch the product via 1-Click
8
2. Use a web browser to access the Admin console at: http://[ec2-ip]:9990/console, where [ec2_ip] is the public ip provided by Amazon for your instance.
9
3. Log in using the following credentials:
10
   * Username: admin
11
   * Password: the instance_id of the instance
12 1 Francisco Javier Solans Benedí
13
You can also access your instance via SSH using the username and your Amazon private key.
14
15 2 Francisco Javier Solans Benedí
The **username** depends on the operative system:
16
* Centos 9 Stream: 'ec2-user'
17
* Other Centos: 'centos'
18
* Ubuntu: 'ubuntu'
19
* Rocky Linux: 'rocky'
20 1 Francisco Javier Solans Benedí
21 2 Francisco Javier Solans Benedí
## Installation details
22
23 1 Francisco Javier Solans Benedí
To change the default username and password, edit the $WILDLFY_HOME/standalone/configuration/mgmt-users.properties file. You can also add users with $WILDLFY_HOME/bin/add-user.sh script.
24 2 Francisco Javier Solans Benedí
25 1 Francisco Javier Solans Benedí
WildFly server is deployed in /usr/java/wildfly-[version] directory, which is linked to /usr/java/wildfly.
26 2 Francisco Javier Solans Benedí
27 1 Francisco Javier Solans Benedí
The server is launched in standalone mode by default, using the file: 'standalone.xml'.
28 2 Francisco Javier Solans Benedí
29 1 Francisco Javier Solans Benedí
The service configuration file is located at '/etc/wildfly/wildfly.conf'.
30 2 Francisco Javier Solans Benedí
31 1 Francisco Javier Solans Benedí
Server service is configured with systemd.
32
33
View status server:
34 2 Francisco Javier Solans Benedí
``` shell
35 1 Francisco Javier Solans Benedí
[centos@ip-172-31-9-232 etc]$ sudo systemctl status wildfly
36 2 Francisco Javier Solans Benedí
```
37 1 Francisco Javier Solans Benedí
38 2 Francisco Javier Solans Benedí
Stop server:
39
``` shell
40 1 Francisco Javier Solans Benedí
[centos@ip-172-31-9-232 etc]$ sudo systemctl stop wildfly
41 2 Francisco Javier Solans Benedí
```
42 1 Francisco Javier Solans Benedí
43 2 Francisco Javier Solans Benedí
Start server:
44
``` shell
45 1 Francisco Javier Solans Benedí
[centos@ip-172-31-9-232 etc]$ sudo systemctl start wildfly
46 2 Francisco Javier Solans Benedí
```
47 1 Francisco Javier Solans Benedí
48 2 Francisco Javier Solans Benedí
## Other useful data
49
50
**Location of sensitive information**
51 1 Francisco Javier Solans Benedí
There is no sensible data
52
53 2 Francisco Javier Solans Benedí
**Encryption configuration**
54 1 Francisco Javier Solans Benedí
There is no encrypted data.
55
56 2 Francisco Javier Solans Benedí
**Changing system credentials**
57 1 Francisco Javier Solans Benedí
To change the Wildfly credentials you can follow the instructions in the following link:
58
59
http://www.mastertheboss.com/jbossas/jboss-configuration/how-to-set-wildfly-admin-console-password/
60
61 2 Francisco Javier Solans Benedí
**Instructions on how the user interacts with Wildfly to decrypt necessary data**
62 1 Francisco Javier Solans Benedí
You can use the Wildfly management console to view all necessary data.
63
64 2 Francisco Javier Solans Benedí
**How to assess and monitor the health and proper function of the application.**
65 1 Francisco Javier Solans Benedí
1. Navigate to your Amazon EC2 console and verify that you're in the correct region.
66
2. Choose Instance and select your launched instance.
67
3. Select the server to display your metadata page and choose the Status checks tab at the bottom of the page to review if your status checks passed or failed.
68
69 2 Francisco Javier Solans Benedí
## Additional resources
70
71
* Wildfly website: https://wildfly.org/