Xperience.cloud

Setup

2FA, Multi- oder Zwei-Faktor-Authentifizierung

For 2FA, Twilio must be Setup to send SMS Text Messages and do automated Voicecalls:

Login

https://www.twilio.com/console

Ask Sebastian Druschel or David Smith for your user account.

Setup for the xperience.cloud

Setup a Alpha Sender ID (Showing a Name instead of a Number as SMS Sender)

Please mind that Alpha Sender ID's does not work global. For Details read here: https://support.twilio.com/hc/en-us/articles/223133767-International-support-for-Alphanumeric-Sender-ID.

1. Goto Messaging Services: https://www.twilio.com/console/sms/services
2. "Create a Messaging Service", if non exists for your Client. Mind to use our Agentursoftware Common Client Name.
3. "Add Senders to Service" and choose "Alpha Sender" as "Sender Type".
4. Add your senders name to the "Sender Pool", please mind that there is a max of 11 characters.
5. Add one or more Long Code Fallback Senders to your "Sender Pool"
6. Choose "Messaging Services"/"Properties" to get the "Messaging Service SID".
7. Configure "(Global) Event Settings"/"Twilio (SMS/ Voice) Seetings"/"Alpha Sender ID (Messaging/ Messaging Services/ SID)" in your xperience.cloud Subsite.
8. Test!

Cookie Consent Bar

Setup Usercentrics for the xperience.cloud

Due to mission Multisite Support, Usercentrics is configured to show a generic Cookie Consent Bar pointing to two relative url's.

1. The "Cookies Policy" is pointing to /cookie-policy/
2. The "Privacy Policy" is pointing to /privacy/

Due to this relative url's, the link will point to https://{your_sites_url}/cookie-policy/ and https://{your_sites_url}/privacy/. If you have to forward this urls to a different location, e.g. an url or pdf, please use the "Redirection" Plugin:

1. Goto "Tools"/"Redirection"
2. "Add New"
3. "Source URL": /cookie-policy/ or /privacy/
4. "Query Parameters": "Exact match all parameters in any order"
5. "Target URL": Your Target URL. If you point to an url within your xperience.cloud Subsite, please use a relative url.
6. "Group": "Redirections" or something else. Important! All Groups must use "Module" for redirects.

Streaming

3Q Streaming Provider

Generell kann die xperience.cloud mit jedem Streaming Provider streamen und jedes VOD Format integrieren.

Gute Erfahrung für das Live Video Streaming in Europa haben wir mit 3Q erzieht.

Setup

"Video Livestream" Projekt anlegen. Folgende Parameter sind wichtig:

Eingangssignal/Stream Typ

RTMP PUSH von Ihrem Encoder	Der normale RTMP Stream aus bsp. OBC oder Wirecast.
RTMP PUSH von Ihrem Encoder mit Low-Latency	"Low-Latency" bezieht sich auf den Wiedergabe Puffer, das Video hat also weniger Latenz beim User. Zwischen Aufnahme und Wiedergabe liegt also weniger Zeit. Dies kann insbesondere bei Live Interaktionen (Chat, Live Components, ...) wichtig sein.
SRT	Sofern möglich unterstützt 3Q auch SRT.

Billing Template (Streaming)

	EUR
Live Video Streaming Setup	EUR 200,00	Event
Transcoding/ Minute (6 Auto-Transcoder)	EUR 0,04	Minute
Bandwidth/ GB	EUR 0,10	GB
Handlingfee Live Streaming	10%

Billing Template (VOD)

	EUR	Einheit
Bandwidth/ GB	EUR 0,10	GB
Storage	EUR ??	GB
Encoding	EUR ??	Minute

Hosting

Gearman (Parallel worker execution)

The xperience.cloud runs a parallel worker execution service using http://gearman.org

Enviroment

Stage and Live-Servers are using separate Gearman instances.

Stage

The Stage Servers Gearman is configured as "GEARMAN_SERVER" in the .env file and is pointing to

GEARMAN_SERVER = ip-172-31-34-64.eu-central-1.compute.internal

what is the private DNS for the Stage-Server himself.

Prod

The Prod Servers Gearman is configured as "GEARMAN_SERVER" in the .env file and is pointing to

GEARMAN_SERVER = ip-172-31-27-199.eu-central-1.compute.internal

what is the service.xperience.cloud EC2 Instances private DNS.

Worker

Gearman Jobs are called "Worker". The workers are located in "/gearman/jobs/" and will be initialised by "gearman/worker.php".

New Worker Code / Restarting the Workers

To use new code, you have to restart the workers. You can restart the workers by just killing them using

sudo pkill -f worker.php

on the corresponding gearman machine.

Logging

The Gearman Worker's php code should log into the syslog ("/var/log/syslog"). The Gearman Job Server itself is logging into his own log at "/var/log/gearman-job-server/gearmand.log". To watch your Gearman Jobs running or debug them, you can use<syntaxhighlight lang="shell"> sudo tail -f /var/log/syslog /var/log/php7.3-fpm.log /var/log/gearman-job-server/gearmand.log </syntaxhighlight>

Using

You can use the Gearman worker in your code by adding a new Client <syntaxhighlight lang="php" line="1"> $client = new GearmanClient(); $client->addServer(getenv('GEARMAN_SERVER')); </syntaxhighlight> and sending your payload to it <syntaxhighlight lang="php" line="1"> $result = $client->doBackground('send_twilio_sms_or_voice', json_encode(array(

   "meta" => array(
       'twilio_number_voice' => $phone_from_voice
   ),
   "data" => array(
       'phone_to' => $telephone,
       'phone_type' => 'voice',
       'phone_body' => $phone_body
   )

))); </syntaxhighlight> Please mind, that Gearman workers do not give an execution result.

Current Workers

There are two workers for

• Sending (RAW) Emails via Amazon AWS / SES (gearman/jobs/send_aws_ses.php)
• Sending SMS and doing Voicecalls via Twilio (gearman/jobs/send_twilio_sms_or_voice.php)

Performance Log

			AWS/ EFS (MiB/Sek)		AWS/ RDS		AWS/ ElastiCache/ Redis		AWS/ EC2
Event-Datum	Event-Name	ca. Teilnhemer	Bereitgestellt	Max. Auslastung	Bereitgestellt	Max. Auslastung (CPU)	Bereitgestellt	Max. Auslastung (CPU)	Bereitgestellt	Max. Auslastung (CPU)	xpcl.service.	xpcl.matomo.
	StandBy Config		50 MiB/s		db.m6g.large		cache.t2.small		2 * c5.2xlarge
20.01.2020	https://www.brandsummit2021.com	2.500	100 MiB/s	6%	db.m5.xlarge	1%	cache.t2.small	16%	4 * c5.2xlarge	8%	3,7%	60% (Fixed with "Number of requests that are processed in one batch: 150")
09.02.2021	https://mitgeredet.schalke04.de	3*1.000