Product Configuration

This topic provides guidance for the following:

Enabling plugins and portlets
Sending email notifications within the workflows
Enabling the journaling feature
Defining users and permissions
Enabling remote access capabilities
Adding remote nodes
Adding Aspera FASP transfer capability
Editing the global configuration parameters

Enable plugins and portlets.
All Aspera transfer plugins, as well as some commonly used plugins from third-party providers, are enabled by default. You will need to enable other plugins you plan to use.
- To enable other plugins you plan to use, click Engine > Plugins > Reload Plugins, then click Engine > Processes > Force maintenance.
- To enable browsing of the list of plugins, click Engine > Plugins > Enable all plugins, then click Yes.
- To enable the use of portlets in the Dashboard, click Engine > Portlets > Enable all.
v
To send email notifications within the workflows, configure the SMTP servers.
Click Engine > Mailer Configuration > New mail server. To test the configuration, click Send test email.
In Orchestrator, journals collect run-time data about where a file can be found in the workflow. To enable the journaling feature, click Workflows > Journals; under Saved Configurations, click Activate.
Further details about journals can be found in the Aspera Orchestrator User Guide.
Define users, groups, permissions, and passwords.
See the section on administering user accounts in the Aspera Orchestrator User Guide.
If you plan to use remote access capability with remote file operation and remote file watcher plugins, install IBM Aspera Point-to-Point on the remote node.
It is necessary to install Point-to-Point because the Aspera ascmd executable is required.
Add remote nodes, if needed.
For a detailed procedure, refer to the article on creating a remote node in the Orchestrator User Guide.
If you plan to use the Aspera FASP transfer capability, install Point-to-Point and a standard Point-to-Point license on the controlled node (the one which initiates the file transfers).
The controlled node may be Orchestrator itself.
1. On the controlled node, open the configuration file (aspera.conf):
```
/opt/aspera/etc/aspera.conf
```
2. Check to see if the file contains persistent-store lines such as the following:
```
<central_server>
    <port>40001</port>
    <address>127.0.0.1</address>
    <persistent_store>enable</persistent_store>
    <persistent_store_max_age>259200</persistent_store_max_age>
    <persistent_store_on_error>ignore</persistent_store_on_error>
</central_server>
```
  If they do not already exist, add them.
3. If aspera.conf has been changed in the above steps, restart Aspera Central.
4. Add a remote node for the controlled node with these elements: Node type = Aspera FASP; ssh port = 33001; and your root login information.
  For a detailed procedure, see the article on creating a remote node in the Orchestrator User Guide.
Edit the global configuration parameters.

You can customize your environment by editing configuration parameters in orchestrator.yml or the Orchestrator UI. For more detailed information, see the article on editing the global configuration parameters in the Orchestrator User Guide.