Cisco Cisco MXE 3500 (Media Experience Engine)
2
Integration Note for Configuring Cisco Media Experience Engine 3500 Release 3.1 with Cisco Show and Share Release 5.2.1
OL-24356-01
About Cisco MXE 3500 Integration with Cisco Show and Share
Transcoded videos are editable in the Cisco Show and Share video editor.
Workflow Overview
When you complete the Cisco MXE 3500 and Cisco Show and Share integration, this is the end user
workflow:
workflow:
1.
User uploads a video to the Cisco Show and Share video portal.
2.
Cisco Show and Share submits the video by using FTP to the Cisco MXE 3500 for transcoding.
3.
Cisco Show and Share uses the MXE API to submit and poll the status of the job it submitted. When
the Cisco MXE 3500 completes transcoding the video, Cisco Show and Share uses FTP to copy the
transcoded video to the Cisco Show and Share video portal.
the Cisco MXE 3500 completes transcoding the video, Cisco Show and Share uses FTP to copy the
transcoded video to the Cisco Show and Share video portal.
4.
The user publishes the transcoded video.
Guidelines and Limitations
The following guidelines and limitations apply to Cisco MXE 3500 integration with Cisco
Show and Share:
Show and Share:
•
You can only configure one Cisco MXE or Cisco MXE cluster in Cisco Show and Share.
•
There is no co-location requirement for Cisco Show and Share and Cisco MXE 3500 hardware. The
appliances can be deployed anywhere in the network provided that they can communicate by using
FTP (TCP port 21) and HTTP (TCP port 80). Cisco Show and Share uses FTP to submit user videos
to Cisco MXE 3500 and retrieve transcoded versions, and uses HTTP to submit transcoding job
requests. If network loading or bandwidth are a concern with large video files, Cisco
Show and Share and the Cisco MXE 3500 should be co-located.
appliances can be deployed anywhere in the network provided that they can communicate by using
FTP (TCP port 21) and HTTP (TCP port 80). Cisco Show and Share uses FTP to submit user videos
to Cisco MXE 3500 and retrieve transcoded versions, and uses HTTP to submit transcoding job
requests. If network loading or bandwidth are a concern with large video files, Cisco
Show and Share and the Cisco MXE 3500 should be co-located.
•
The Cisco MXE 3500 licenses, Standalone and Resource Manager, both work for this integration.
Other than the functional differences between the two licenses, there are no specific configuration
limitations.
Other than the functional differences between the two licenses, there are no specific configuration
limitations.
When using the Standalone license, the Cisco MXE will continue to perform network transcoding
jobs in addition to those submitted from Cisco Show and Share. When using the Resource Manager
license, you can integrate the Cisco MXE with Cisco Show and Share by using one of these
scenarios:
jobs in addition to those submitted from Cisco Show and Share. When using the Resource Manager
license, you can integrate the Cisco MXE with Cisco Show and Share by using one of these
scenarios:
–
Add Cisco Show and Share-specific profiles to the Cisco MXE 3500 system default profiles.
–
Create separate profiles and use these in place of the system default profiles.
•
Cisco MXE 3500 does not include the workflow profiles: encoder, output, preprocessor, for
integration with Cisco Show and Share. You must download and install the profiles from Cisco.com.
integration with Cisco Show and Share. You must download and install the profiles from Cisco.com.
•
When integrating Cisco Show and Share with a Cisco MXE 3500 cluster (resource nodes managed
by a resource manager), observe these guidelines:
by a resource manager), observe these guidelines:
–
Verify that the resource nodes (RNs) have full control access to the c:\dms shared folder on the
resource manager (RM).
resource manager (RM).
–
By default, a Cisco MXE 3500 cluster is in a Windows workgroup. Verify that the mxe-service
account on both the RNs and the RM have the same password.
account on both the RNs and the RM have the same password.
–
If the Cisco MXE 3500 cluster is in a Windows domain, the mxe-service user account could be
set up as a Windows domain account and both the RM and the RNs would share this account.
set up as a Windows domain account and both the RM and the RNs would share this account.