Open-Xchange - User contributions [en]

AppSuite:Web Tests

2018-05-28T09:56:52Z

Benedikt.kroening: Updated page

= OX App Suite Web Tests =

Functional tests for the web interface of OX App Suite simulate end-user operations. To use it, you can either download a pre-built jar-package or you can clone the source-files from the repository

== Downloading the pre-built package ==
Simply download the package and follow the execution information provided in the sample-tests project:
* [https://gitlab.open-xchange.com/qa/appsuite-testing/sample-tests#configuring-your-environment Configuration]
* [https://gitlab.open-xchange.com/qa/appsuite-testing/sample-tests#execution Execution]

Download the desired version:
* [https://artifactory.open-xchange.com/artifactory/qa/com/openexchange/testing/appsuite-core-tests/7.8.4-SNAPSHOT/appsuite-core-tests-7.8.4-SNAPSHOT.jar AppSuite Core Tests (7.8.4)]

== Building tests on your own (or creating your own test-project) ==
Clone the tests from the repository and follow the instructions provided in the sample-tests project:
* [https://gitlab.open-xchange.com/qa/appsuite-testing/sample-tests/#building-your-project Building]

Clone the desired version (e.g. 7.8.4):

<code>
$ git clone -b 7.8.4 https://gitlab.open-xchange.com/qa/appsuite-testing/appsuite-core-tests
</code>

After cloning and building you can follow the [https://gitlab.open-xchange.com/qa/appsuite-testing/sample-tests#configuring-your-environment configuration] and [https://gitlab.open-xchange.com/qa/appsuite-testing/sample-tests#execution execution] steps shown in the sample-tests project.

Keep in mind that you have to adapt the project names and paths according to your environment.

[[Category: AppSuite]] [[Category: Testing]]

Jolokia

2013-09-25T13:44:03Z

Benedikt.kroening: /* jolokia.properties */

= How to interact with Jolokia for Open-Xchange=

Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.

By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties

Additional information can be found at http://www.jolokia.org/ .

== jolokia.properties ==
{|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'
! scope="col" width="30%" | Key
! scope="col" width="20%" | Default value
! scope="col" width="35%" | Comment
|-
| com.openexchange.jolokia.start
| false
| start switch for jolokia
|-
| com.openexchange.jolokia.servlet.name
| /monitoring/jolokia
| <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki>
|-
| com.openexchange.jolokia.user
|
| <nowiki>User used for authentication with HTTP Basic Authentication. If not given, Jolokia will not start!</nowiki>
|-
| com.openexchange.jolokia.password
|
| <nowiki>Password used for authentification, if not set "secret" is used.</nowiki>
|-
| com.openexchange.jolokia.restrict.to.localhost
| true
| <nowiki>This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present</nowiki>
|}

Keep in mind that Jolokia will not start, unless you set <code> com.openexchange.jolokia.start = true </code> , <code> com.openexchange.jolokia.user = yourUser</code> and to <code> com.openexchange.jolokia.password = yourPassword</code>.

When using Munin-Scripts with Jolokia, this user and password also need to be changed.

== Things to mention about Jolokia ==

As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!
This is by default set through the use of <code>com.openexchange.jolokia.restrict.to.localhost = true</code> and can be changed by either setting it to <code>false</code> or providing a <code>jolokia-access.xml</code> inside <code>/opt/open-xchange/etc/</code>

for further information how to setup this file, http://www.jolokia.org/reference/html/security.html is a good start as all those settings are usable.

=== Jolokia with Grizzly ===

When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1:8009/monitoring/jolokia

=== Jolokia with AJP ===

When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.

An Apache proxy_ajp.conf could look like this:
<code>
<Location /internal>
# restrict access to internal
Order Deny,Allow
Deny from all
Allow from 127.0.0.1
# you might add more ip addresses / networks here
# if the apache is not on the same machine as the OX-server
# Allow from 192.168 10 172.16
</Location>
...
<Proxy /internal/ox1/monitoring>
ProxyPass ajp://oxhost1:8009/monitoring
</Proxy>
...
</code>

Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .

Jolokia

2013-09-25T13:43:07Z

Benedikt.kroening: /* jolokia.properties */

= How to interact with Jolokia for Open-Xchange=

Open-Xchange does support Jolokia as a remote JMX-Bridge over HTTP.

By Version 7.4.0 ongoing, it is located inside Open-Xchange Bundle and configured by jolokia.properties

Additional information can be found at http://www.jolokia.org/ .

== jolokia.properties ==
{|width="100%" style="table-layout: fixed" class='wikitable sortable' border='1'
! scope="col" width="30%" | Key
! scope="col" width="20%" | Default value
! scope="col" width="35%" | Comment
|-
| com.openexchange.jolokia.start
| false
| start switch for jolokia
|-
| com.openexchange.jolokia.servlet.name
| /monitoring/jolokia
| <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal</nowiki>
|-
| com.openexchange.jolokia.user
|
| <nowiki>User used for authentication with HTTP Basic Authentication. If not given, Jolokia will not start!</nowiki>
|-
| com.openexchange.jolokia.password
|
| <nowiki>Password used for authentification, if not set "secret" is used.</nowiki>
|-
| com.openexchange.jolokia.restrict.to.localhost
| true
| <nowiki>This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present</nowiki>
|}

Keep in mind that Jolokia will not start, unless you set <code> com.openexchange.jolokia.start = true </code> , <code> com.openexchange.jolokia.user = "yourUser"</code> and to <code> com.openexchange.jolokia.password = "yourPassword"</code>.

When using Munin-Scripts with Jolokia, this user and password also need to be changed.

== Things to mention about Jolokia ==

As Jolokia represents a JMX-Interface it is highly recommended to not forward it to the internet!
This is by default set through the use of <code>com.openexchange.jolokia.restrict.to.localhost = true</code> and can be changed by either setting it to <code>false</code> or providing a <code>jolokia-access.xml</code> inside <code>/opt/open-xchange/etc/</code>

for further information how to setup this file, http://www.jolokia.org/reference/html/security.html is a good start as all those settings are usable.

=== Jolokia with Grizzly ===

When using Grizzly, you can connect to jolokia directly with the servers address, e.g.: http://oxserver1:8009/monitoring/jolokia

=== Jolokia with AJP ===

When using AJP, you need to enable forwarding for each server, keep in mind that those should be only accessable inside your intranet.

An Apache proxy_ajp.conf could look like this:
<code>
<Location /internal>
# restrict access to internal
Order Deny,Allow
Deny from all
Allow from 127.0.0.1
# you might add more ip addresses / networks here
# if the apache is not on the same machine as the OX-server
# Allow from 192.168 10 172.16
</Location>
...
<Proxy /internal/ox1/monitoring>
ProxyPass ajp://oxhost1:8009/monitoring
</Proxy>
...
</code>

Jolokia on oxhost1 is accessable by http://apacheaddress/internal/ox1/monitoring/jolokia .