Application architecture

A Streamezzo Rich Media application will have such architecture:

The grayed parts are third party elements; according to your needs they may be optional and/or distant services. This diagram shows that you will have to deploy both server part - hosted on Streamezzo Rich Media Server (RMS) - and client part - installer(s) for the devices you target - of your Streamezzo application. Of course, if your Streamezzo application does not contains any server side scenes, meaning that you are building a static application without any online content, you won't have to deal with the server deployment part.

Write once, run everywhere

You may probably have already seen that a single dynamic client scene in Workbench Developer will allow you generating a result for all different sizes and user interfaces required combinations, assuming that your application has been developed following Streamezzo guidelines about adaptation. So you won't have to develop more than once your client scenes, even if you are targeting numerous families of devices.

Concerning the server part, even if your service targets more than one family, you will need to deploy only once for all your devices, assuming that your application has been developed following Streamezzo guidelines about adaptation.

Application deployment workflow

The deployment workflow is the following:

1. Publish on Streamezzo Rich Media Server (RMS): server part (webapp) to be deployed on Streamezzo Rich Media Server instance. See tutorial here.
2. Create client packages: Installer(s), which include local/pre-embedded scenes, and Streamezzo Rich Media Client (RMC). See tutorial here.
3. Deploy client packages on provisioning server (not provided in Streamezzo solution)

For both publishing the service on a Streamezzo RMS and generating the client packages, Streamezzo Workbench Developer will be the dedicated tool to use: 

Concerning the client part of your application, you may want to deploy on many platforms supported by Streamezzo Rich Media Solution.

Obviously, addressing various platforms will require various installers to deploy your application. You will also have to deal with different screen sizes and/or different ergonomics (touch screen and/or keypad, for example), meaning different sizes and/or different end user interface for the static client scenes that will be embedded in your client application. Following the Streamezzo guidelines about adaptation will help you dealing with such issues in the most efficient way.

Concerning the server part of your application, you should be able to deploy in your own platform, among the many platforms supported by Streamezzo Rich Media Solution.

Key steps

In few words, the key steps to achieve the deployment of your rich media application will be:

• Defining the adapted production server platform, according to your infrastructure and requirements
• Publishing the server-side part on a Streamezzo Rich Media Server instance
• Packaging the client-side part (i.e. the installer to be downloaded then deployed on devices)
• Benchmarking the server platform to properly size it in order to support the planned capacity
• Provisioning your application for the addressed devices (and your end-users)
• Updating your rich media application (with new features…) during its lifetime

With this guided approach you will be able to deploy your rich media application live in the appropriate configuration to support the set of your addressed devices and end-users.