### Example License Service Container Startup Logs

Source: https://docs.axinom.com/services/drm/onboard/onboard-deployment

This snippet shows an example output of the License Service container logs, indicating successful startup, configuration overrides, and the service listening on a specific port.

```text
docker logs 3bc85e55c

Overriding the app's configuration... Done.
Overriding the app's logging configuration... Done.
Overriding the hosts configuration... Done.
Overriding the Nginx configuration... Done.
The setup has been successfully completed.
2019-05-21 10:48:12,702 CRIT Supervisor running as root (no user in config file)
2019-05-21 10:48:12,703 INFO Supervisor started with pid 12
2019-05-21 10:48:13,705 INFO spawned: 'nginx' with pid 15
2019-05-21 10:48:13,706 INFO spawned: 'app' with pid 16
[2019-05-21T10:48:14.3959460+00:00] Listening on: http://127.0.0.1:8089
Press Ctrl+C to quit.
2019-05-21 10:48:15,398 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-05-21 10:48:15,398 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
```

--------------------------------

### Basic Shell Echo Command Example

Source: https://docs.axinom.com/services/drm/onboard/onboard-deployment

This snippet demonstrates a simple `echo` command used to print text to the console. It serves as an example of how commands and their output are represented throughout this documentation, indicating the format for command-line instructions.

```Shell
echo "Text"
```

--------------------------------

### Setup FMP4 Muxing

Source: https://docs.axinom.com/services/drm/encoders/bitmovin-intro

Setup the muxing. For this example, we are only using fmp4 muxing.

```javascript
const segmentLength = 4;
const segmentNaming = 'seg_%number%.m4s';
const initSegmentName = 'init.mp4';

const fmp4Muxing = await bitmovinApi.encoding.encodings.muxings.fmp4.create(encoding.id,
    new Fmp4Muxing({
    segmentLength: segmentLength,
    segmentNaming: segmentNaming,
    initSegmentName: initSegmentName,
    streams: [new MuxingStream({ streamId: inputStream.id })]
    })
);
```

--------------------------------

### Run Widevine API Application

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

These commands start the Widevine API application using `mono`. The `LD_LIBRARY_PATH` is set to the current directory to locate necessary libraries. The first example runs it with the default localhost listener, while the second demonstrates how to specify a custom listening URL and port.

```bash
$ sudo su axdrm -c "LD_LIBRARY_PATH=. mono /opt/axdrm/WidevineApi/WidevineApi.exe"
```

```bash
$ sudo su axdrm -c "LD_LIBRARY_PATH=. mono /opt/axdrm/WidevineApi/WidevineApi.exe http://192.168.2.15:8080"
```

--------------------------------

### Example PlayReady Server Certificate XML

Source: https://docs.axinom.com/services/drm/onboard/onboard-deployment

Illustrates the structure of a PlayReady Server Certificate XML file, containing certificate data, private key, public key, and curve information. This file is required for PlayReady DRM.

```xml
<?xml version="1.0" encoding="utf-8"?>
<ServerCertificateData>
	<Certificate>Qblablabla[...]blablablaQpP6xas=</Certificate>
	<ECCKeyValue>
		<PrivateKey>7LX1IrfLsjE6V8CXNGviGSP5U9M3OYKD0PyKqm+igUQ=</PrivateKey>
		<PublicKey>2cxfn1WIGXwpL1kCa5t48D64GueK0cf2c+yQQbNqafc=</PublicKey>
		<Curve>1</Curve>
	</ECCKeyValue>
</ServerCertificateData>
```

--------------------------------

### JSON Example for Multi-Media Type Ingest

Source: https://docs.axinom.com/services/media/ingest/start-ingest

This JSON payload demonstrates a full ingest example for the Media Service, encompassing a Movie and an Episode. It illustrates the structure for defining content metadata, video and image assets, licensing information, and multi-language localizations for different media types within a single ingest file.

```JSON
{
  "name": "Full Ingest Example",
  "items": [
    {
      "type": "MOVIE",
      "external_id": "avatar",
      "data": {
        "title": "Avatar",
        "original_title": "James Cameron's Avatar",
        "description": "Avatar is a 2009 American epic science fiction film...",
        "synopsis": "In 2154, humans have depleted Earth's natural resources...",
        "released": "2009-12-10",
        "studio": "20th Century Fox",
        "tags": ["3D", "SciFi", "Highlight"],
        "cast": ["Sam Worthington", "Zoe Saldana", "Sigourney Weaver"],
        "production_countries": [
          "United States of America",
          "Estonia",
          "Germany",
          "COL",
          "ESP"
        ],
        "genres": ["Sci-Fi", "Drama"],
        "licenses": [
          {
            "start": "2020-08-01T00:00:00.000+00:00",
            "end": "2020-08-30T23:59:59.999+00:00",
            "countries": ["AW", "AT", "FI"]
          }
        ],
        "main_video": {
          "source": "example_videos/videos/avatar",
          "profile": "DEFAULT"
        },
        "trailers": [
          {
            "source": "example_videos/trailers/avatar_1",
            "profile": "DEFAULT"
          },
          {
            "source": "example_videos/trailers/avatar_2",
            "profile": "DEFAULT"
          }
        ],
        "images": [
          {
            "path": "example_images/covers/avatar_1.jpg",
            "type": "COVER"
          },
          {
            "path": "example_images/teasers/avatar_1.jpg",
            "type": "TEASER"
          }
        ],
        "localizations": [
          {
            "language_tag": "de-DE",
            "title": "Avatar – Aufbruch nach Pandora",
            "description": "Avatar ist ein US-amerikanischer Science-Fiction-Epos aus dem Jahr 2009...",
            "synopsis": "Im Jahr 2154 haben die Menschen die natürlichen Ressourcen der Erde erschöpft..."
          },
          {
            "language_tag": "et-EE",
            "title": "Avatar",
            "description": "Avatar on 2009. aasta Ameerika eepiline ulmefilm...",
            "synopsis": "Aastal 2154 on inimesed ammendanud Maa loodusvarad..."
          }
        ]
      }
    },
    {
      "type": "EPISODE",
      "external_id": "mandalorian_s2_e1",
      "data": {
        "index": 1,
        "parent_external_id": "mandalorian_s2",
        "title": "The Marshal",
        "original_title": "Chapter 9: The Marshal",
        "description": "After the stories of Jango and Boba Fett, another warrior emerges in the Star Wars universe...",
        "synopsis": "The Mandalorian is drawn to the Outer Rim in search of others of his kind.",
        "released": "2020-10-30",
        "studio": "Lucasfilm",
        "tags": ["star wars", "mandalorian", "bounty hunter"],
        "genres": ["Action", "Sci-Fi"],
        "cast": ["Pedro Pascal", "Carl Weathers", "Gina Carano"],
        "production_countries": ["USA"],
        "licenses": [
          {
            "start": "2020-08-01T00:00:00.000+00:00",
            "end": "2020-08-30T23:59:59.999+00:00",
            "countries": ["AW", "AT", "FI"]
          }
        ],
        "main_video": {
          "source": "example_videos/videos/mandalorian_s2_e1",
          "profile": "DEFAULT"
        },
        "trailers": [
          {
            "source": "example_videos/trailers/mandalorian_s2_e1_t1",
            "profile": "DEFAULT"
          },
          {
            "source": "example_videos/trailers/mandalorian_s2_e1_t2",
            "profile": "DEFAULT"
          }
        ],
        "images": [
          {
            "path": "example_images/covers/mandalorian_s2_e1_t1.jpg",
            "type": "COVER"
          },
          {
            "path": "example_images/teasers/mandalorian_s2_e1_t1.jpg",
            "type": "TEASER"
          }
        ],
        "localizations": [
          {
            "language_tag": "de-DE",
            "title": "The Mandalorian",
            "description": "Nach den Geschichten von Jango und Boba Fett taucht ein weiterer Krieger im Star Wars-Universum auf...",
            "synopsis": "Der Mandalorianer zieht es auf der Suche nach Artgenossen in den Outer Rim."
          },
          {
            "language_tag": "et-EE",
            "title": "The Mandalorian"
          }
        ]
      }
    }
  ]
}
```

--------------------------------

### Enable Supervisor on Ubuntu 16.04

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Configures Supervisor to start automatically with the operating system, specifically addressing an issue on Ubuntu 16.04 where it is disabled by default.

```Bash
$ sudo systemctl enable supervisor
```

--------------------------------

### Initialize Messaging Broker with setupMessagingBroker

Source: https://docs.axinom.com/platform/packages/mosaic-message-bus

This example demonstrates the basic usage of the `setupMessagingBroker` function to initialize the messaging broker. It shows how to register `RascalConfigBuilder` instances for sending and receiving events/commands, and how to pass configuration, application context, and components like a message counter.

```JavaScript
// general setup (plus database pools and other setup-related work)
const app = express();
const config = getFullConfig();
const counter = initMessagingCounter(getOwnerPgPool(app));

// register all your builders to send or receive events/commands:
const builders = [
  new RascalConfigBuilder(MediaServiceMessagingSettings.StartIngest, config)
    .sendCommand()
    .subscribeForCommand<
StartIngestCommand>(
      (broker: Broker) => new IngestHandler(broker, getLoginPgPool(app), config)
    ),
  // ...
];

const broker = await setupMessagingBroker({
  app,
  config,
  builders,
  components: { counters: { postgresCounter: counter } },
  // ...
});
```

--------------------------------

### Bootstrap a New Project with Mosaic CLI

Source: https://docs.axinom.com/platform/media-template

This command initializes a new project based on the Mosaic Media Template. It guides the user through the setup process and creates a new project structure. For more details on this command and its available options, refer to the Mosaic CLI documentation.

```bash
npx -p @axinom/mosaic-cli@latest mosaic create
```

--------------------------------

### Get Axinom Mosaic CLI Command Help

Source: https://docs.axinom.com/platform/packages/mosaic-cli

Learn how to list all available commands for the `@axinom/mosaic-cli` utility and how to retrieve detailed information, including parameters and examples, for a specific command.

```Shell
npx mosaic --help
```

```Shell
npx mosaic <command-name> --help
```

--------------------------------

### Ingest Movie with Localizations JSON Example

Source: https://docs.axinom.com/services/media/ingest/start-ingest

This JSON example demonstrates how to ingest a movie asset including localized titles, descriptions, and synopses for multiple languages (e.g., 'de-DE' and 'et-EE'). It requires the specified locales to be defined in the Localization Service settings.

```JSON
{
  "name": "Movie with Localizations",
  "items": [
    {
      "type": "MOVIE",
      "external_id": "avatar_external_id",
      "data": {
        "title": "Avatar",
        "description": "Avatar is a 2009 American epic science fiction film...",
        "synopsis": "In 2154, humans have depleted Earth's natural resources...",
        "localizations": [
          {
            "language_tag": "de-DE",
            "title": "Avatar – Aufbruch nach Pandora",
            "description": "Avatar ist ein US-amerikanischer Science-Fiction-Epos aus dem Jahr 2009...",
            "synopsis": "Im Jahr 2154 haben die Menschen die natürlichen Ressourcen der Erde erschöpft..."
          },
          {
            "language_tag": "et-EE",
            "title": "Avatar",
            "description": "Avatar on 2009. aasta Ameerika eepiline ulmefilm...",
            "synopsis": "Aastal 2154 on inimesed ammendanud Maa loodusvarad..."
          }
        ]
      }
    }
  ]
}
```

--------------------------------

### Install Supervisor

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Installs the Supervisor process control system on the operating system using the apt package manager.

```Bash
$ sudo apt install supervisor
```

--------------------------------

### Install Core Software Packages

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

This command installs essential software packages including `unzip` for archive extraction, `tzdata` for timezone information, and `mono-complete` for the full Mono runtime and development tools on a Debian-based system.

```bash
$ sudo apt -y install unzip tzdata mono-complete
```

--------------------------------

### Check License Service Container Logs

Source: https://docs.axinom.com/services/drm/onboard/onboard-deployment

This command displays the logs of a running Docker container, identified by its ID, to verify that the License Service started successfully and is operating as expected.

```bash
sudo docker logs {container_id}
```

--------------------------------

### Complete Shaka Player with Axinom DRM Integration Example

Source: https://docs.axinom.com/services/drm/players/shaka

A full HTML page demonstrating the end-to-end integration of Shaka Player with Axinom DRM. It includes script and stylesheet imports, video element setup, player initialization, DRM configuration, token passing, and video loading.

```HTML
<!DOCTYPE html>
<html>
	<head>
		<title>Shaka Player with Axinom DRM</title>
	</head>
	<body>
           <script src="https://cdn.jsdelivr.net/npm/shaka-player@4.3.5/dist/shaka-player.compiled.min.js"></script>
           <link
			rel="stylesheet"
			href="https://cdn.jsdelivr.net/npm/shaka-player@4.3.5/dist/controls.min.css"
		/>

		<video id="videoPlayer" controls></video>

		<script>
			videoElement = document.getElementById('videoPlayer')
			player = new shaka.Player(videoElement)
			shaka.polyfill.installAll()

			protection = {
				drm: {
					servers: {
						'com.widevine.alpha': 'https://drm-widevine-licensing.axprod.net/AcquireLicense',
					},
				},
			}

			player.configure(protection)

			player.getNetworkingEngine().registerRequestFilter(function (type, request) {
				if (type === shaka.net.NetworkingEngine.RequestType.LICENSE) {
					request.headers['X-AxDRM-Message'] =
						'X-AxDRM-Message token'
				}
			})
			player.load(
				'source url',
			)

			$('#shaka-player').show()
		</script>
	</body>
</html>
```

--------------------------------

### Example Format for Axinom Stream Map File

Source: https://docs.axinom.com/services/drm/encoders/wowza

This plain text snippet illustrates the expected format for the StreamMapFile.txt, which associates video filenames with their unique content key IDs. Each line represents a single entry, allowing manual specification of content key IDs for specific videos.

```Text
video1.mp4:20fc67d5-917e-42e8-a391-25115734f9d9
video2.mp4:0c00e59a-3c7d-4896-aca2-bed46fc4e554
video3.mp4:47064333-a1db-4bf8-8a2b-48ff1993f8ea
```

--------------------------------

### Install Nginx on Debian/Ubuntu

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Command to install the Nginx web server package using the apt package manager on Debian or Ubuntu systems.

```bash
$ sudo apt install nginx
```

--------------------------------

### Examples of Valid Axinom-Compatible FairPlay Key URIs

Source: https://docs.axinom.com/services/drm/license-service/fairplay/preparing-fps

Illustrates various valid formats for the FairPlay Key URI expected by Axinom DRM, showing cases with and without the 'skd://' prefix and the Key IV. These examples demonstrate the flexibility in specifying the Key URI.

```Text
sdk://72ea9ec1-abb4-40d8-b3a9-e0bd1833bd58:0123456789ABCDEF0123456789ABCDEF
```

```Text
sdk://72ea9ec1-abb4-40d8-b3a9-e0bd1833bd58
```

```Text
72ea9ec1-abb4-40d8-b3a9-e0bd1833bd58:0123456789ABCDEF0123456789ABCDEF
```

```Text
72ea9ec1-abb4-40d8-b3a9-e0bd1833bd58
```

--------------------------------

### Combined Movie Ingestion JSON Example with Full Metadata

Source: https://docs.axinom.com/services/media/ingest/start-ingest

This comprehensive JSON example illustrates the ingestion of a movie asset with extensive metadata, including original title, release date, studio, tags, cast, production countries, genres, licenses, main video, trailers, images, and localizations. It combines various aspects of movie relations and metadata into a single structure.

```JSON
{
  "name": "Full Movie",
  "items": [
    {
      "type": "MOVIE",
      "external_id": "avatar_external_id",
      "data": {
        "title": "Avatar",
        "original_title": "James Cameron's Avatar",
        "description": "Avatar is a 2009 American epic science fiction film...",
        "synopsis": "In 2154, humans have depleted Earth's natural resources...",
        "released": "2009-12-10",
        "studio": "20th Century Fox",
        "tags": ["3D", "SciFi", "Highlight"],
        "cast": ["Sam Worthington", "Zoe Saldana", "Sigourney Weaver"],
        "production_countries": [
          "United States of America",
          "Estonia",
          "Germany",
          "COL",
          "ESP"
        ],
        "genres": ["Sci-Fi", "Drama"],
        "licenses": [
          {
            "start": "2020-08-01T00:00:00.000+00:00",
            "end": "2020-08-30T23:59:59.999+00:00",
            "countries": ["AW", "AT", "FI"]
          }
        ],
        "main_video": {
          "source": "test_video",
          "profile": "DEFAULT"
        },
        "trailers": [
          {
            "source": "trailers/test_video_1",
            "profile": "DEFAULT"
          },
          {
            "source": "trailers/test_video_2",
            "profile": "DEFAULT"
          }
        ],
        "images": [
          {
            "path": "avatar_1.jpg",
            "type": "COVER"
          },
          {
            "path": "avatar_2.jpg",
            "type": "TEASER"
          }
        ],
        "localizations": [
          {
            "language_tag": "de-DE",
            "title": "Avatar – Aufbruch nach Pandora",
            "description": "Avatar ist ein US-amerikanischer Science-Fiction-Epos aus dem Jahr 2009...",
            "synopsis": "Im Jahr 2154 haben die Menschen die natürlichen Ressourcen der Erde erschöpft..."
          },
          {
            "language_tag": "et-EE",
            "title": "Avatar",
            "description": "Avatar on 2009. aasta Ameerika eepiline ulmefilm...",
            "synopsis": "Aastal 2154 on inimesed ammendanud Maa loodusvarad..."
          }
        ]
      }
    }
  ]
}
```

--------------------------------

### Complete HTML example for Radiant Media Player integration

Source: https://docs.axinom.com/services/drm/players/radiant

A full HTML document demonstrating the integration of Radiant Media Player with Axinom DRM, including script embedding, container setup, and player configuration with media source and DRM settings.

```HTML
<!DOCTYPE html>
<html>

<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
    <title>RMP</title>
</head>

<body>
    <!-- Include Radiant Media Player JavaScript library -->
    <script src="https://cdn.radiantmediatechs.com/rmp/9.15.0/js/rmp.debug.js"></script>

    <!-- Add a div container with a unique id -->
    <div id="rmp"></div>
    <!-- Set up player configuration options -->
    <script>
        const src = {
            dash: 'https://media.axprod.net/TestVectors/Cmaf/protected_1080p_h264_cbcs/manifest.mpd'
        };
        const settings = {
            licenseKey: 'Your-Radiant-media-player-license-key',
            src: src,
            width: 640,
            height: 360,
            shakaDrm: {
                servers: {
                    'com.widevine.alpha': 'https://drm-widevine-licensing.axtest.net/AcquireLicense',
                    'com.microsoft.playready': 'https://drm-playready-licensing.axprod.net/AcquireLicense',
                }
            },
            shakaRequestConfiguration: {
                license: {
                    headers: {

```

--------------------------------

### Create Minimal Movie Ingest JSON File

Source: https://docs.axinom.com/services/media/ingest/start-ingest

This JSON file defines a minimal movie entry for the ingest process, including its name, type, external ID, and title. It serves as a basic example to demonstrate the ingest workflow in the Media Service.

```json
{
  "name": "Minimal Movie Ingest",
  "items": [
    {
      "type": "MOVIE",
      "external_id": "avatar_external_id",
      "data": { "title": "Avatar" }
    }
  ]
}
```

--------------------------------

### Example: Basic HTTP Authorization Header for Axinom Key Service

Source: https://docs.axinom.com/services/drm/encoders/aws-media-services-convert

Demonstrates the format for the Basic HTTP authentication header, combining Tenant ID and Management Key GUIDs Base64-encoded and prefixed with 'Basic '. This header is required for authenticating requests to the Axinom Key Service Management API.

```Configuration
'Basic MjAyODcxOGYtMWVkZC00ODJhLWI2YjUtODA2N2U5M2NmYmZhOmUwYjgxYjM0LWRkODItNDg5Ny04OWYyLWJkZjMyZDcwMjNmNw=='
```

--------------------------------

### Create Widevine API Installation Directory

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

This command creates the necessary directory structure for the Widevine API application at `/opt/axdrm/WidevineApi`. The `-p` flag ensures that parent directories are created if they don't exist, preventing errors if `/opt/axdrm` is not present.

```bash
$ sudo mkdir -p /opt/axdrm/WidevineApi
```

--------------------------------

### Configure MediaPackage V2 Channel Group and Channel Creation

Source: https://docs.axinom.com/services/drm/encoders/aws-media-services-package-live

This guide explains how to set up a channel group and then create a channel within MediaPackage V2, specifying the naming conventions for both the channel group and the channel, along with the required input type.

```APIDOC
MediaPackage V2 Channel Group Configuration:
  Channel group name: "MediaPackageV2-ChannelGroup01"

MediaPackage V2 Channel Configuration:
  Channel Name: "MediaPackageV2-Channel01"
  Input Type: HLS
```

--------------------------------

### Configure Nginx Main Settings

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Example Nginx main configuration (`nginx.conf`) including worker processes, file limits, event settings, HTTP settings, and virtual host includes. This configuration disables default logging and gzip for license responses, and turns off server tokens.

```nginx
user www-data;
worker_processes auto;
worker_rlimit_nofile 131072;
pid /run/nginx.pid;

# No logging by default. It must be explicitly enabled by the user, if needed.
error_log /dev/null;

events {
    worker_connections 4096;
    accept_mutex off;
    multi_accept on;
    use epoll;
    }

http {
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;
    types_hash_max_size 2048;
    server_tokens off; # No need to advertise the version of Nginx.
    gzip off; # License responses cannot be compressed efficiently.

    error_page 502 504 =503 /503.html;

    include /etc/nginx/mime.types;
    default_type application/octet-stream;

    # No HTTPS by default. It must be explicitly enabled by the user, if needed.

    # No logging by default. It must be explicitly enabled by the user, if needed.
    access_log off;
    error_log /dev/null;

    # Virtual Host Configs.
    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;

}
```

--------------------------------

### PlayReady License Request Info Message Example

Source: https://docs.axinom.com/services/drm/license-service/license-request-info-message

An example of the JSON structure for a PlayReady License Request Info Message. This message provides basic information including the version, type, and device information (device ID and recommended client ID).

```json
{
    "version": 1,
    "type": "playready_license_request_info",
    "device_info": {
        "device_id": "82c9dbcb-277f-4792-a8ad-9cd00f4afbf1",
        "recommended_client_id": "82c9dbcb-277f-4792-a8ad-9cd00f4afbf1"
    }
}
```

--------------------------------

### Start Bitmovin Encoding Process

Source: https://docs.axinom.com/services/drm/encoders/bitmovin-intro

Constructs a StartEncodingRequest to initiate the encoding process. It specifies the manifest generator version and links the previously created DASH manifest by its ID. The request is then sent to the Bitmovin API to start the encoding.

```JavaScript
const startEncodingRequest = new StartEncodingRequest({
    manifestGenerator: ManifestGenerator.V2,
    vodDashManifests: [
        new ManifestResource({ manifestId: dashManifest.id })
    ]
});

await bitmovinApi.encoding.encodings.start(encoding.id, startEncodingRequest);
```

--------------------------------

### Configure Mono Repository for Linux Distributions

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

These commands configure the APT package manager to use the official Mono repository, allowing installation of the latest stable Mono version. Specific instructions are provided for Ubuntu 16.04, Debian 9, and Raspbian 9, addressing potential version specificities.

```bash
$ sudo apt install apt-transport-https
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
$ echo "deb https://download.mono-project.com/repo /ubuntu stable-xenial main" | sudo tee /etc/apt /sources.list.d/mono-official-stable.list
$ sudo apt update
```

```bash
$ sudo apt install apt-transport-https dirmngr
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
$ echo "deb https://download.mono-project.com/repo /debian stable-stretch main" | sudo tee /etc/apt /sources.list.d/mono-official-stable.list
$ sudo apt update
```

```bash
$ sudo apt install apt-transport-https dirmngr
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
$ echo "deb https://download.mono-project.com/repo /debian stable-raspbianstretch/snapshots/5.14.0.177 main" | sudo tee /etc/apt/sources.list.d/monoofficial-stable.list
$ sudo apt update
```

--------------------------------

### Restart Nginx Service

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Command to restart the Nginx service, applying all configuration changes made to the Nginx server.

```bash
$ sudo service nginx restart
```

--------------------------------

### SingleTar Archiving Output Example

Source: https://docs.axinom.com/services/encoding/encoding-service/phase-packaging

This example illustrates the "SingleTar" archiving option, where a single .tar archive is created for the entire output folder. This archive contains all subfolders (like "Dash" and "Hls") and their respective contents, along with an MD5 checksum file for the main archive.

```text
+
|--- VideoArchive.tar
|--- VideoArchive.md5

VideoArchive.tar:
+
|--- Dash +
|         |--- file1.m4s
|         |--- ...
|--- Hls  +
          |--- file1.ts
          |--- ...
```

--------------------------------

### API Authorization Header Example

Source: https://docs.axinom.com/services/drm/key-service/key-service-management-api

Demonstrates the required Authorization header format for requests to the Key Service Management API. It includes the general format and a concrete example with a base64 encoded Tenant ID and Management Key.

```APIDOC
Authorization: Basic base64("TenantID:ManagementKey")

Example:
Authorization: Basic YzcyZDdmNmEtYzRiMy00MTQxLWI5OTYtMDZjNjI2NmQ1NTg4OjhhMjc2ZTkwLTY5MjMtNGJkYS05ZjVlLThlZGRjOTE1OWExZQ==
```

--------------------------------

### Example HTTP Basic Authentication Header with Credentials

Source: https://docs.axinom.com/services/drm/license-service/license-service-management-api/blocked-users

An example of a fully constructed `Authorization` header using a sample Tenant ID and Management Key, demonstrating the base64 encoding of the credentials.

```HTTP
Basic MjAyODcxOGYtMWVkZC00ODJhLWI2YjUtODA2N2U5M2NmYmZhOmUwYjgxYjM0LWRkODItNDg5Ny04OWYyLWJkZjMyZDcwMjNmNw==
```

--------------------------------

### Verify Nginx Proxy for Widevine API

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Curl command to test if Nginx is successfully proxying requests to the Widevine API endpoint. A successful proxy setup should return the response 'Use POST to get a license'.

```bash
$ curl http://HOSTNAME/WidevineApi/AcquireLicense
```

--------------------------------

### Create DASH Manifest Output

Source: https://docs.axinom.com/services/drm/encoders/bitmovin-intro

Create a Dash Manifest. For this example we only consider creating a DASH manifest. You can refer to Bitmovin documentation for further details.

```javascript
const manifestOutput = new EncodingOutput({
    outputId: azureOutput.id,
    outputPath: outputPath,
    acl: [
        new AclEntry({
            permission: AclPermission.PUBLIC_READ,
            scope: '*'
        })
    ]
    });
```

--------------------------------

### Sample Deployment Manifest Configuration

Source: https://docs.axinom.com/platform/hosting/understanding-the-deployment-manifest

Illustrates a complete example of a Deployment Manifest, defining service metadata, DNS mappings, pilet configurations, required service accounts with permissions, and various environment variables (regular and secure) for a 'media-service'.

```yaml
version: '1.0'
serviceId: media-service

dnsMappedPorts:
  - name: api
    port: 10200

pilets:
  - name: media_workflows
    args:
      MEDIA_SERVICE_BASE_URL: https://${__ax_hosted__.dns.self.api}

serviceAccounts:
  - name: primary
    permissionStructure:
      - serviceId: ax-id-service
        permissions:
          - PERMISSIONS_SYNCHRONIZE
          - ACCESS_TOKENS_GENERATE_LONG_LIVED_TOKEN
      - serviceId: ax-image-service
        permissions:
          - IMAGE_TYPES_DECLARE

regularVariables:
  POSTGRESQL_HOST: ${__ax_hosted__.pg.host}
  POSTGRESQL_PORT: '${__ax_hosted__.pg.port}'
  POSTGRESQL_USER_SUFFIX: '${__ax_hosted__.pg.user_suffix}'
  PGSSLMODE: '${__ax_hosted__.pg.sslmode}'
  DATABASE_NAME: '${__ax_hosted__.pg.database_name}'
  RABBITMQ_PROTOCOL: '${__ax_hosted__.rmq.protocol}'
  RABBITMQ_HOST: '${__ax_hosted__.rmq.host}'
  RABBITMQ_PORT: '${__ax_hosted__.rmq.port}'
  RABBITMQ_MGMT_PROTOCOL: '${__ax_hosted__.rmq.mgmt_protocol}'
  RABBITMQ_MGMT_HOST: '${__ax_hosted__.rmq.mgmt_host}'
  RABBITMQ_MGMT_PORT: '${__ax_hosted__.rmq.mgmt_port}'
  RABBITMQ_VHOST: '${__ax_hosted__.rmq.vhost}'
  NODE_ENV: production
  SERVICE_ID: media-service
  LOG_LEVEL: DEBUG
  GRAPHQL_GUI_ENABLED: true
  PORT: '${__ax_hosted__.port.api}'
  TENANT_ID: '${__ax_hosted__.env.tenant_id}'
  ENVIRONMENT_ID: '${__ax_hosted__.env.environment_id}'
  IMAGE_SERVICE_BASE_URL: '${__ax_hosted__.svc.ax-image-service.management_base_url}'
  CATALOG_SERVICE_BASE_URL: '${__ax_hosted__.dns.ax-catalog-service.api}'
  ID_SERVICE_AUTH_BASE_URL: '${__ax_hosted__.svc.ax-id-service.auth_base_url}'
  ENCODING_SERVICE_BASE_URL: '${__ax_hosted__.svc.ax-encoding-service.management_base_url}'
  BILLING_SERVICE_END_USER_URL: '${__ax_hosted__.svc.ax-billing-service.end_user_base_url}'

secureVariables:
  RABBITMQ_USER: '${__ax_hosted__.rmq.username}'
  RABBITMQ_PASSWORD: '${__ax_hosted__.rmq.password}'
  DATABASE_OWNER: '${__ax_hosted__.pg.db_owner_role}'
  DATABASE_OWNER_PASSWORD: '${__ax_hosted__.pg.db_owner_password}'
  DATABASE_LOGIN: '${__ax_hosted__.pg.db_login_role}'
  DATABASE_LOGIN_PASSWORD: '${__ax_hosted__.pg.db_login_password}'
  DATABASE_GQL_ROLE: '${__ax_hosted__.pg.db_gql_role}'
  SERVICE_ACCOUNT_CLIENT_ID: '${__ax_hosted__.sa.client_id.primary}'
  SERVICE_ACCOUNT_CLIENT_SECRET: '${__ax_hosted__.sa.client_secret.primary}'
```

--------------------------------

### Create Directory Structure for Axinom DRM Service

Source: https://docs.axinom.com/services/drm/onboard/onboard-deployment

Establishes the necessary directory structure for Axinom DRM License Service configuration and logs. These folders will be mapped to the container during startup.

```bash
mkdir ~/{drm_technology}
mkdir ~/{drm_technology}/config
mkdir ~/{drm_technology}/logs
mkdir ~/{drm_technology}/logs/nginx
```

--------------------------------

### FairPlay License Request Info Message Example

Source: https://docs.axinom.com/services/drm/license-service/license-request-info-message

An example of the JSON structure for a FairPlay License Request Info Message. This message includes the version, type, device information (device ID, recommended client ID, supported license protocol versions), the specific license protocol version used, playback state, streaming indicator, and session ID.

```json
{
    "version": 1,
    "type": "fairplay_license_request_info",
    "device_info": {
        "device_id": "82c9dbcb-277f-4792-a8ad-9cd00f4afbf1",
        "recommended_client_id": "82c9dbcb-277f-4792-a8ad-9cd00f4afbf1",
        "supported_license_protocol_versions": [ "1", "2" ]
    },
    "license_protocol_version": "1",
    "playback_state": "new_session",
    "streaming_indicator": "requesting_device",
    "session_id": "bb529255-ee30-4d2d-b5b2-879359c6aadd"
}
```

--------------------------------

### Start Local HTTP Server for Receiver Application

Source: https://docs.axinom.com/services/drm/players/chromecast

Navigates to the sample receiver application folder and starts a simple HTTP server using the `http-server` module. This makes the application files accessible locally, typically on port 8080.

```Shell
	http-server
```

--------------------------------

### Generate Key ID (KID) from Hashed Input

Source: https://docs.axinom.com/services/drm/key-service/speke/speke-overriding-samples

This code snippet demonstrates the complete process of generating a 16-byte Key ID (KID) from an input string. It includes hashing the input using SHA256, XORing the first and second 16-byte halves of the hash, and converting the resulting 16-byte XOR hash into a GUID with little-endian byte ordering. The Python example focuses on the XOR and GUID conversion, while JavaScript and Java provide full examples including hashing.

```Python
# XOR the first and second half of the base hash to make a 16 bytes hash
hashPartOne = baseHashValue[:16]
hashPartTwo = baseHashValue[16:32]
xorHash = bytes([_a ^ _b for _a, _b in zip(hashPartOne, hashPartTwo)])

# Convert to a GUID (based on little-endian bytes)
kid = uuid.UUID(bytes_le=xorHash)

print(kid)
```

```JavaScript
const crypto = require("crypto");

const inputParameters = "<see above>";
var baseToHashAsBytes = Buffer.from(inputParameters);

// SHA256 hash
var sha256Hasher = crypto.createHash("sha256");
sha256Hasher.update(buffbaseToHashAsByteser);
const baseHashValue = sha256Hasher.digest();

// XOR the first and second half of the base hash to make a 16 bytes hash
const partOne = baseHashValue.slice(0, 16);
const partTwo = baseHashValue.slice(16, 32);

let xorHash = Buffer.alloc(16);
for (let n = 0; n < 16; n++)
    xorHash[n] = partOne[n] ^ partTwo[n % partTwo.length];

// Convert to a GUID (based on little-endian bytes)
const kid = createGUID(xorHash);

console.log(kid);

function createGUID(buffer:any) {
    // mind the reverse endianess for the first three parts
    return buffer.subarray(0, 4).reverse().toString('hex') + '-' +
        buffer.subarray(4, 6).reverse().toString('hex') + '-' +
        buffer.subarray(6, 8).reverse().toString('hex') + '-' +
        buffer.subarray(8, 10).toString('hex') + '-' +
        buffer.subarray(10, 16).toString('hex');
}
```

```Java
public class App {
    private static String formatByteArrayToUUID(byte[] bytes) {
        StringBuilder formattedString = new StringBuilder();

        for (int i = 0; i < bytes.length; i++) {
            formattedString.append(String.format("%02x", bytes[i]));

            if (i == 3 || i == 5 || i == 7 || i == 9) {
                formattedString.append("-");
            }
        }

        return formattedString.toString();
    }

    public static void main(String[] args) throws NoSuchAlgorithmException {
        String inputParameters = "<see above>";
        byte[] baseToHashAsBytes = inputParameters.getBytes(StandardCharsets.UTF_8);

        // SHA256 hash
        MessageDigest digest = MessageDigest.getInstance("SHA-256");
        byte[] baseHashValue = digest.digest(baseToHashAsBytes);

        // XOR the first and second half of the base hash to make a 16 bytes hash
        byte[] hashPartOne = new byte[16];
        System.arraycopy(baseHashValue, 0, hashPartOne, 0, 16);

        byte[] hashPartTwo = new byte[16];
        System.arraycopy(baseHashValue, 16, hashPartTwo, 0, 16);

        byte[] xorHash = new byte[16];
        for (int i = 0; i < 16; i++) {
            xorHash[i] = (byte) (hashPartOne[i] ^ hashPartTwo[i]);
        }

        // Convert to a GUID (based on little-endian bytes)
        byte[] bytes_le = xorHash;
        int resultLength = 4 + (6 - 4) + (8 - 6) + (bytes_le.length - 8);
        byte[] result = new byte[resultLength];

        int index = 0;
        for (int i = 4 - 1; i >= 0; i--) {
            result[index++] = bytes_le[i];
        }
        for (int i = 6 - 1; i >= 4; i--) {
            result[index++] = bytes_le[i];
        }
        for (int i = 8 - 1; i >= 6; i--) {
            result[index++] = bytes_le[i];
        }
        for (int i = 8; i < bytes_le.length; i++) {
            result[index++] = bytes_le[i];
        }

        String formattedLowerCaseString = formatByteArrayToUUID(result);
        System.out.println(formattedLowerCaseString);
    }
}
```

--------------------------------

### Install Node.js Modules for Local Web Server and Tunneling

Source: https://docs.axinom.com/services/drm/players/chromecast

Installs the `http-server` and `ngrok` Node.js modules globally. `http-server` is used to host the receiver application locally, and `ngrok` creates a publicly accessible tunnel to the local server, which is essential for Chromecast devices to access the application.

```Shell
    npm install -g http-server
    npm install -g ngrok
```

--------------------------------

### Import Bitmovin API SDK and Initialize

Source: https://docs.axinom.com/services/drm/encoders/bitmovin-intro

Import the Bitmovin API SDK into your environment and specify your API key.

```javascript
const BitmovinApi = require('@bitmovin/api-sdk').default;

const bitmovinApi = new BitmovinApi({
            apiKey: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
        });
```

--------------------------------

### Verify Widevine API License Acquisition Endpoint

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

This `curl` command sends a simple GET request to the Widevine API's license acquisition URL (`127.0.0.1:8089/AcquireLicense`) to verify that the API is running and responsive. The expected response, 'Use POST to get a license', confirms the service is active and awaiting POST requests.

```bash
$ curl 127.0.0.1:8089/AcquireLicense
```

--------------------------------

### Create Supervisor Configuration File

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Opens or creates a new Supervisor configuration file for the Widevine API application in the /etc/supervisor/conf.d/ directory using the nano text editor.

```Bash
$ sudo nano /etc/supervisor/conf.d/WidevineApi.conf
```

--------------------------------

### HTTP Authorization Header for JWT

Source: https://docs.axinom.com/getting-started/make-service-mosaic-compatible

An example of the standard HTTP Authorization header format used to transmit a JSON Web Token (JWT) with a request. The JWT should be base64-encoded and prefixed with 'Bearer '.

```HTTP
Authorization: Bearer <JWT-as-base64>
```

--------------------------------

### Log in to Axinom Docker Registry

Source: https://docs.axinom.com/services/drm/onboard/onboard-deployment

Authenticates with Axinom's private Docker registry using provided credentials to enable pulling images.

```bash
docker login registry.axinom.com -u {username} -p {password}
```

--------------------------------

### setupMessagingBroker Input Parameters

Source: https://docs.axinom.com/platform/packages/mosaic-message-bus

This section defines the input parameters for the `setupMessagingBroker` function, detailing each property's purpose, type, and usage.

```APIDOC
setupMessagingBroker(options: object): Promise<Broker>
  options:
    app: MessagingRegistry - A MessagingRegistry object to store and share objects by keys e.g. the express app.
    config: MessagingConfig - The MessagingConfig object with settings on how to connect to the RabbitMQ server, vhost, and other similar settings.
    builders: RascalConfigBuilder[] - A list of RascalConfigBuilder configuration builder objects. They are responsible to configure the message bindings for sending and receiving events and commands in your code.
    components: object - Extension possibility for the broker initialization. In this example, a message counter is added to protect from "poisonous" messages.
    onMessageMiddleware: OnMessageMiddleware[] - An array of OnMessageMiddleware middleware objects. Each of them will be called before a message is given to the corresponding message handler.
    logger: MosaicLogger - A Mosaic logger instance used during setup and for error/debug logging during message processing.
    shutdownActions: function[] - Used to nicely shut down the message broker and RabbitMQ connections when your application is being shut down.
    rascalConfigExportPath: string - A relative path from your project root to a folder where the generated config JSON will be saved to.
```

--------------------------------

### Ingest Data: 1:N Relation for Complex Managed Objects (e.g., Licenses)

Source: https://docs.axinom.com/services/media/ingest

Example of defining an array of complex objects within the `data` field to manage related entities that have multiple properties, such as licenses with start date, end date, and country codes.

```JSON
"data": { "licenses": [ { "start": "2020-11-01", "end": "2022-07-31", "countries": [ "us","ee" ] } ] }
```

--------------------------------

### Restart Supervisor Service

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Restarts the Supervisor service to apply new configurations and initiate the startup of any newly defined or modified managed applications.

```Bash
$ sudo service supervisor restart
```

--------------------------------

### Publish Messages with Broker in JavaScript

Source: https://docs.axinom.com/platform/packages/mosaic-message-bus

This example shows how to publish an event or command message using the `broker.publish` method. It includes the message type, payload, and optional envelope overrides like an authentication token. Messages can be sent from anywhere in your code.

```JavaScript
await this.broker.publish(
  MediaServiceMessagingSettings.IngestStarted.messageType,
  {
      entity_id: 123,
      entity_type: 'movie'
  },
  {
      auth_token: my_auth_token,
  },
);
```

--------------------------------

### Create Nginx Widevine API Site Configuration File

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Command to create a new Nginx site configuration file specifically for the Widevine API in the `sites-available` directory using the nano text editor.

```bash
$ sudo nano /etc/nginx/sites-available/WidevineApi
```

--------------------------------

### Expected HTTP Response for PlayReady License Acquisition

Source: https://docs.axinom.com/services/drm/onboard/onboard-deployment

This text shows the expected HTTP response for PlayReady license acquisition, which is slightly different from Widevine/FairPlay.

```text
LicensingService
...
```

--------------------------------

### Add Clear CMAF Content Endpoint to MediaPackage

Source: https://docs.axinom.com/services/drm/encoders/aws-media-services-package-live

This guide outlines the steps to add an endpoint for clear CMAF content to a MediaPackage channel. It includes settings for the endpoint ID, manifest name, packager type, HLS manifest ID, and confirms that no encryption is used.

```APIDOC
MediaPackage Endpoint Configuration (Clear CMAF):
  ID: "CMAF-Clear"
  Manifest Name: "Manifest"
  Packager settings:
    Type: Common Media Application Format (CMAF)
  HLS manifest:
    ID: "CMAF-Clear"
  Package encryption: No encryption
```

--------------------------------

### Enable Nginx Widevine API Site

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Command to create a symbolic link from the `sites-available` configuration to `sites-enabled`, thereby activating the Widevine API Nginx site configuration.

```bash
$ sudo ln -s /etc/nginx/sites-available/WidevineApi /etc/nginx/sites-enabled/WidevineApi
```

--------------------------------

### GraphQL API Setup with @axinom/mosaic-graphql-common Components

Source: https://docs.axinom.com/platform/packages/mosaic-graphql-common

Describes the core functionalities and key components provided by the `@axinom/mosaic-graphql-common` library for setting up a GraphQL API from a PostgreSQL database, including features for subscriptions, validation, and permission annotations.

```APIDOC
@axinom/mosaic-graphql-common Library Components:
  PostgraphileOptionsBuilder:
    Description: Encapsulates common functionality and best-practices to initialize the GraphQL API from a PostgreSQL database.
  SubscriptionsPluginFactory:
    Description: Enables GraphQL subscriptions (web-socket based GraphQL push notifications). Notifies subscribers if an entity or its related tables were modified.
  ValidationDirectivesPlugin:
    Description: Adds annotations to the GraphQL schema about validation rules that were added on table columns.
  AnnotateTypesWithPermissionsPlugin:
    Description: Adds annotations which describe the required permissions to access or modify an entity.
```

--------------------------------

### Example Mosaic JWT Structure

Source: https://docs.axinom.com/getting-started/make-service-mosaic-compatible

Illustrates the structure and typical claims found in a JSON Web Token (JWT) issued by Axinom Mosaic, including tenant, environment, user name, permissions, subject type, issuance and expiration times, audience, issuer, and subject.

```JSON
{
  "tenantId": "13d99de7-b726-45f8-a03d-7935e116b111",
  "environmentId": "22202f00-19e2-462b-885a-da5948eb50cb",
  "name": "myUserName",
  "permissions": {
    "myService": [
      "read",
      "contribute"
    ]
  },
  "subjectType": "ServiceAccount",
  "iat": 1671462868,
  "exp": 1671466468,
  "aud": "*",
  "iss": "ax-id-service",
  "sub": "69cb7e46-69d4-4323-a935-404444100d48"
}
```

--------------------------------

### Run Axinom Mosaic CLI Command to Upload Deployment Manifest

Source: https://docs.axinom.com/platform/hosting/deploy-a-customized-service

Execute the `mosaic hosting manifest upload` command to upload a deployment manifest file. The `yarn util:load-vars` utility loads environment variables from a `.env` file. This example demonstrates uploading a manifest from the `services/media/service` folder.

```bash
yarn util:load-vars mosaic hosting manifest upload -n "My Media Manifest #1" -i my-media-service -p "./services/media/service"
```

--------------------------------

### Complete dash.js Player Integration with Axinom DRM

Source: https://docs.axinom.com/services/drm/players/dashjs

A full HTML page example demonstrating the complete integration of dash.js with Axinom DRM. This includes the HTML structure, script inclusion, player initialization, DRM protection data setup, and source attachment for a functional DRM-protected video player.

```HTML
<!DOCTYPE html>
<html>
	<head>
		<title>Dash Player with Axinom DRM</title>
		<script src="https://cdn.dashjs.org/latest/dash.all.min.js"></script>
	</head>
	<body>
		<video id="videoPlayer" controls></video>
		<div id="dash-player"></div>
		<script>
			const player = dashjs.MediaPlayer().create()

			player.initialize(document.querySelector('#videoPlayer'))
			const protData = {
				'com.widevine.alpha': {
					serverURL: 'https://drm-widevine-licensing.axprod.net/AcquireLicense',
					httpRequestHeaders: {
						'X-AxDRM-Message':
							'X-AxDRM-Message token',
					},
				},
			}
			player.setProtectionData(protData)
			const url = 'url'
			player.attachSource(url)
			player.on(dashjs.MediaPlayer.events.STREAM_INITIALIZED, streamInitialized.bind(this))
			document.querySelector('#dash-player').style.display = 'block'
		</script>
	</body>
</html>
```

--------------------------------

### Open Nginx Main Configuration File

Source: https://docs.axinom.com/services/drm/onboard/onboard-widevine-non-docker

Command to open the main Nginx configuration file (`nginx.conf`) for editing using the nano text editor.

```bash
$ sudo nano /etc/nginx/nginx.conf
```