Along with its powerful recording features, RealProducer includes assistants that allow you to publish your streaming content to the Internet or and Intranet. Using these assistants, you can create a RealMedia-enhanced Web page and upload it to a server.
A primary publishing feature of RealProducer is the Web Page Assistant. With this assistant, you can instantly create a Web page enhanced with RealMedia. The assistant creates all of the HTML necessary to provide a page that contains your streaming media file.
Guided through a series of prompts, you choose how to stream your RealMedia file: either with a RealPlayer in a separate window, or with a RealPlayer embedded within the page. The assistant then allows you to preview the finished page with your Web browser and a RealPlayer.
Follow these steps to create either type of RealMedia Web page, pop-up or embedded.
The name of the last RealMedia file created by RealProducer appears by default. Click the Browse button to locate another file.
The Web Page Results page opens. This page informs you that a Web page and a RealMedia metafile have been created.
You must have RealPlayer installed to view your page properly.
The name of the last RealMedia file created by RealProducer appears by default. Click the Browse button to locate another file.
The Player Control Layout page appears. In this page, you can decide what components of the RealPlayer to include within the Web page.
The Web Page Results page opens. This page informs you that a Web page and a RealMedia metafile have been created.
You must have RealPlayer installed to view your page properly.
Keep in mind that the Web pages you create with the Web Page Assistant will initially point to files located on your local hard drive. If you upload your pages to a Web server, these local file references will be automatically updated. Therefore, you should avoid making manual changes to any file references in HTML files created by the assistant.
Alterations to these files or any file references contained in the associated .ram/.rpm metafile may cause errors when publishing Web pages to a remote server.
A metafile points a Web page link to one or more RealMedia clips located on a remote server. The function of a metafile is to point to the location where your media file actually resides and is required for your file to stream, rather than simply download and play. Typically, a metafile is located on a server and contains the URL where a RealMedia clip can be found.
Metafiles created by the RealProducer Web Page Assistant reside on your local hard drive and point to files on your local file system. When you publish your files to a server, these metafiles are automatically updated to include information about the server where your media files will be sent.
Another assistant included with RealProducer is the Publish to Server Assistant. This assistant allows you to publish your RealMedia-enhanced Web page to a remote server. The server can be either a RealNetworks RealServer or a standard HTTP Web server.
The assistant leads you through a series of prompts to help you specify the type of server and the directory where you will upload your page. You can also specify the name of the Web server and the URL directory where your Web page will be located. The assistant then allows you to preview the finished page.
When you upload your Web pages to a remote server, RealProducer automatically updates your Web page and .ram/.rpm metafile to point to the appropriate server addresses, directories and files.
To avoid confusion during the publishing process, you should make sure you have a valid account. Contact your Internet Service Provider (ISP) for the following information before you begin.
![]() |
Note |
---|
You must have an FTP program installed, either Anarchie or Fetch, to successfully publish your files. |
If you are using a RealServer to stream your files, you will also need to obtain the following information from your system administrator or ISP. Please note that for streaming from a RealServer your Web page will be copied to a standard HTTP Web server, while your RealMedia file may be copied to a separate RealServer.
File Server: Name or IP address of the file server where your Web page will be uploaded. For example, ftp.server.com
.
Directory: Name of the directory on the file server where your Web page will be uploaded. For example, if the personal directory assigned to you by your system administrator is public_html, enter public_html
as the directory name. This may be left blank.
RealServer: Name or IP address of the RealServer where you will upload your RealMedia file. For example, ftp.server.com
.
Media Directory: Name of the media directory on the RealServer where your RealMedia file will be uploaded. For example, if the media directory assigned to you by your system administrator is upload, you would enter upload
as the directory name.
RealServer Location: Name or IP address of the RealServer that users will use to locate your media file. This can include the port. For example, if the full URL users will use to locate your media file on the Internet is rtsp://real.server.com:6060/~username/file.rm you would enter real.server.com:6060
as the RealServer name and port.
URL Directory: The directory on the RealServer that users will use to locate your media file. For example if the full URL that users will use to locate your media file is rtsp://real.server.com:6060/~username/file.rm you would enter ~username
as the URL Directory.
If you are using a standard HTTP Web server to stream RealMedia, you should obtain the following information from your system administrator or ISP. For simple HTTP streaming, your Web page and media file will be copied to the same location.
File Server: Name or IP address of the file server where your Web page will be uploaded. For example, ftp.server.com
.
Directory: Name of the directory on the file server where your Web page will be uploaded. For example, if the personal directory assigned to you by your system administrator is public_html, enter public_html
as the directory name. This may be left blank.
Web Server: Name or IP address of the Web server users will use to locate your Web page. For example, if the full URL users will use is http://www.server.com/~username/file.htm, enter www.server.com
as the Web server name.
URL Directory: The directory on the Web server that users will use to locate your Web page. For example, if the full URL is http://www.server.com/~username/file.htm, enter ~username
as the URL Directory.
The following instructions are for publishing your RealMedia clip to a RealNetworks RealServer. Using a RealServer allows you to publish Web pages that have RealMedia without losing functionality (such as SureStream).
Before you begin the procedure, make sure you have all of the information described in "RealServer Information".
The full URL of the clip that you are publishing appears below.
Your files automatically upload to your Web server. If any errors occur while uploading your files, you will receive and error message describing the problem and potential solutions.
The following instructions are for publishing your RealMedia clip to a standard HTTP Web server. While these servers may be more common, they don't allow you to fully use all RealMedia features.
Before you begin the procedure, make sure you have all of the information described in "HTTP Server Information".
Your files automatically upload to your Web server. If any errors occur while uploading your files, you will receive and error message describing the problem and potential solutions.