Setting up Myriad News SE v4/v5 "Publish to" options to send to a 3rd party CMS

Modified on Tue, 24 Sep at 12:44 PM

Prerequisites

This article assumes you have a working knowledge of Myriad Playout and Myriad Remote Edit Server, and have installed and successfully configured Myriad News Capture.

You will also need to have already received the correct CMS Publishing application for your CMS provider from the Broadcast Radio Support Team. Please contact support@broadcastradio.com for more information about supported CMS applications.  

In this walkthrough we will be configuring Myriad News to be able to publish news stories to the Aiir content management platform. Please contact Aiir for more information on enabling this feature.

Setup:

Deploying and configuring the CMSPublish configuration files:

In Windows Explorer, navigate to your Myriad Data Location and go into the "News" sub directory. Normally this would be a network location such as \\MyServer\Myriad\Data\News,  For this walkthrough we will assume that the location is:

C:\Myriad\Data\News

Under this folder you should a CmsApp folder.  If you do not see this folder, check that Myriad News Capture SE has been successfully installed and is running.

mceclip0.png

From the CMS Publishing application files you received from Broadcast Radio, copy the 2 CMSPublish files (CMSPublish.ini and CMSPublish.ico) directory into the main News folder:

mceclip1.png

You now need to configure the CMS Publisher with your Aiir and Amazon S3 account details. Double click on the CMSPublish.Ini file and it will open in Notepad and scroll down the [RemoteLocations] section. You need to replace all the fields that are highlighted below with the information provided by Aiir, and from your Amazon AWS storage account. You only need to replace the section that starts and ends with the 3 asterisks:

 

mceclip3.png

Once you have you entered these details, click File>Save and close Notepad.

Deploying the CMS Publishing helper application:

Back in Windows Explorer, navigate into the CmsApp folder - in our example, this is C:\Myriad\Data\News\CmsApp and place the remainder of the files into this folder which should then look like this:

mceclip2.png

 

Configuring Myriad News to use the new Publishing tool:

Open Myriad News Capture and on the Settings menu, choose News Database Settings. In the Settings windown, switch to the Bulletins/Dests tab, and at the bottom you will see the Send To Locations area, and click on the button to add a new Send To Location

mceclip4.png

 

On the Send To Location Details window, enter a suitable Name, select News Story as the Item Type and make sure that File Type is set to Custom CMS:

Then click OK.

mceclip5.png

The new Send To will now show in the list on the Database Settings window.

mceclip6.png

Click OK to save the database settings.

Publishing a story to your CMS Provider:

In Myriad Anywhere News, open a story and on the toolbar at the top you should now see the new icon for your CMS provider (shown in green below).

Select the "Internet" tab on the Story (shown in red) and make sure that have entered the version of the story to send to your CMS. You can use the copy buttons on the right hand side of the window to quickly copy across the original version of the story then edit if necessary. 

Click the Send To CMS button to open the Send To window and you will see the preview of the information that will be sent to your CMS provider:

mceclip8.png

You can change the Category, and if your CMS provider allows it, you can also control when the story will appear and if it needs to be removed at a certain point.

If you happy with the options, click Send. This will post the story to the queue to be sent, and a few moments later the Myriad Remote Edit Server will package up the story and associated information and dispatch it to your CMS provider.

 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article