Configure monitoring and metering for your tethered node

Edit online

You must configure the Aspera Event Journaling Daemon (AEJD) to enable event data transmission to the Aspera on Cloud Activity App. You must also configure the Aspera License Entitlement Engine (ALEE) to use token authentication for enhanced security of metering data transmissions (by default, ALEE uses entitlement credentials).

This is step 10 in tethering a node

Before you begin step 10, be sure you have completed step 9: Mark remote storage attached to your tethered node as mount points.

Procedure

The asp-cloud-config CLI utility is used in the instructions below to perform service registration with Aspera on Cloud, but it has additional functionality. For detailed information, use the asp-cloud-config -h command.

Log on to Aspera on Cloud.
Select Admin > Integrations > Aspera node services.
Click Create new to open the Create a new node services integration dialog.
In the Name field, enter the name that you want to use for registering the service (or services).
Select the node services to integrate: select both AEJD and ALEE.
Click Generate token to generate and display the token.
Copy the registration token.
You will use the registration token to configure the services on your transfer server, so copy it to a place that will be convenient for this purpose.
Click Done.
- The new entry is listed on Aspera node services, under Registration pending.
- If you need to retrieve the token later, click the service name. If the token has expired, you see a prompt to generate a new one.
- Once you complete the registration process on the server, you can click the service name to display the service client ID, the type of service, the creation date, and the creator's user name.
  
  CAUTION:
  Do note delete an ALEE registration. ALEE registration is required to transfer files to and from the server (files on the server will not be affected).
  
  CAUTION:
  Do not delete an AEJD registration. AEJD registration is required to report usage and events to the Activity app.
Log on to your transfer server.

For event reporting with the Aspera on Cloud Activity App, update aspera.conf to enable AEJD usage.

$ sudo /opt/aspera/bin/asconfigurator -x "set_server_data;https_port,9092;activity_logging,true;activity_event_logging,true;aej_logging,true;aej_port,28000;aej_host,127.0.0.1"

$ sudo /opt/aspera/bin/asconfigurator -x "set_node_data;pre_calculate_job_size,yes"

To use token authentication with ALEE, retrieve your customer ID and entitlement ID, and then disable ALEE.
1. If you not registered your entitlement, you will need to have the customer ID and the entitlement ID on hand for a later step.
  If have already registered your entitlement, retrieve the information from the transfer server with the following command, and save it to a convenient location for later use. You will not be able to retrieve it from the server after you disable ALEE.
```
$ sudo /opt/aspera/bin/alee-admin entitlement
```
2. Disable ALEE.
```
$ sudo /opt/aspera/bin/asalee-config.sh disable
```
Using the registration token that you generated, register your services with Aspera on Cloud.
Use the following asp-cloud-config command syntax:
```
sudo /opt/aspera/bin/asp-cloud-config tether --aoc-registration-token reg_token_value --aoc-url https://api.ibmaspera.com
```
Note: You can use a registration token only once. If for some reason the registration command fails (for example, due to network connection problems), you must generate a new token on Aspera on Cloud.
If you have registered the ALEE service with Aspera on Cloud, enable the service and set up your entitlement.
1. First, enable ALEE.
```
$ sudo /opt/aspera/bin/asp-cloud-config alee enable
```
2. Then use the following syntax with your customer ID and entitlement ID to register your entitlement:
```
sudo /opt/aspera/bin/alee-admin register customer_ID entitlement_ID
```
If you have registered AEJD with Aspera on Cloud, first restart AEJD and then restart asperanoded.
1. Restart AEJD, so that it picks up the Aspera on Cloud registration configuration.
```
$ sudo systemctl restart asperaejd
```
2. Restart asperanoded, so that the server picks up the aspera.conf changes. Use one of the following commands. The second command below is for Linux systems that use init.d.
  - ```
  $ sudo systemctl restart asperanoded
```
- ```
$ sudo service asperanoded restart
```
To verify that your service configuration is correct, log on to Aspera on Cloud and select Admin > Organization > Integrations > Aspera node services.
If your configuration is correct, and your service has been registered with Aspera on Cloud, it will be listed under Registered node services.

For the AEJD service, you can also initiate file transfers, and then go to the Aspera on Cloud Activity app to view transfer data. For details, see Architecture and components of the activity app.

Next step in tethering a node

You've configured your tethered node for activity and usage monitoring and for metering.

To allow your Aspera on Cloud users use the content in this node, you must give them access. Note that when you administratively share a folder with users, as in this procedure, all admins in your org can manage the folder access. This shared management ability is typically preferable to having one admin user share a folder as an individual user; in such case, only that individual admin can manage access to that folder.

For important maintenance procedures, see Backing up and restoring a tethered node database.