Distribution of content between separated Kaltura plublisher accounts in CE

Hi @jess,

I tried to configure a distribution profile in Kaltura admin console in CE:
target: sharing content between separated Kaltura Publisher accounts

But the existing provider types are not helpful in this case, right!?
Bildschirmfoto 2020-03-20 um 12.15.05

It would be great to hear from you, which feature I have to configure to reach the content share between diffenrent publisher accounts.

Thanks a lot,
Best
Verena

Hello @Emily,

First, you need to enable the plugin by adding CrossKalturaDistribution to /opt/kaltura/app/configurations/plugins.ini. Each plugin is listed in its own line, \n is the separator/delimiter.
Then, invoke /opt/kaltura/app/deployment/base/scripts/installPlugins.php, clear the cache with:

# find $APP_DIR/cache/ -type f -exec rm {} \;

And restart Apache.

Next, there’s the issue of configuring the CrossKaltura connector.
After following the steps above, it will be listed in the select box. Upon clicking on Create New you will see all the available options. At the bare minimum, you will need to input:

  • Name
  • All inputs under Target
  • Access Control Profile IDs map
  • Conversion Profile IDs map

For the last two, the format is as follows:

[{"key":"$ORIGINAL_PROFILE_ID1","value":"$TARGET_PROFILE_ID1","relatedObjects":null}]

So, for example, if the access control profile ID on the original partner is 21 and the corresponding profile on the target partner is 23, it should be:

[{"key":"21","value":"23","relatedObjects":null}]

If you have multiple profiles:

[{"key":"$ORIGINAL_PROFILE_ID1","value":"$TARGET_PROFILE_ID1","relatedObjects":null},{"key":"$ORIGINAL_PROFILE_ID2","value":"$TARGET_PROFILE_ID2","relatedObjects":null}]

If you have custom metadata schemas, you should do the same for the Metadata Profile IDs map input.

Under Submit Action, Update Action and Delete Action, choose one of the available values;
Automatic - will create an export job for every new entry; this is not typically desired
Manual - will allow a user to export a given entry by going to KMC->Content->entry drill down (by clicking on the entry name)->Distribution
Disabled - do not allow the action (for example, you may not want to allow users to delete or update an exported entry).

Once you’ve configured the profile to suit your requirements, save and enable it by selecting Enable from the Action select box.

For troubleshooting an export job: Admin Console->Batch process control->Entry investigation.

Cheers,

2 Likes

We have tried to configure Kaltura in the way above.

But we get the error:

==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Wed May 27 09:44:21 2020] [error] [client 172.48.9.179] PHP Fatal error: Cannot instantiate abstract class Kaltura_Client_ContentDistribution_Type_DistributionProvider in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ParseUtils.php on line 47

This error is shown in kaltlog, if we try to configure distibution profiles.

What is wrong? Any idea? Thx.