- •Table of Contents
- •1) Technical Support Specialist – Level 2
- •Qualification Requirements
- •2 ) Exceptions
- •3) Tier 2 Tools a) Solutions.24hourwebhostingsupport.Com
- •C) Linux Shell Commands
- •D) ipconfig
- •4) Absolute and Relative Paths a) Absolute Path
- •5) Possible Causes for Broken Sites
- •6) Installed Software:
- •B) Relative Path
- •7) Unix Services on the Hostopia Platform
- •A) cgi (Common Gateway Interface) faq
- •I.E. /services/webpages/h/o/hosting.Bluegenesis.Com/chat/chat.Log
- •B) Server Side Includes (ssi) faq
- •Can I use server-parsed image maps?
- •C) perl faq
- •How do I install and use Perl modules?
- •What is cpan?
- •What is supported by the jsp service?
- •What is a jsp file?
- •Where should my end users upload their jar files?
- •How do I Connect to an ms sql Database Source with .Jsp?
- •Upload appropriate libraries to your /public/web-inf/lib location
- •How do I Create a test .Jsp file?
- •Are there any potential issues ?
- •8) Windows® Services on the Hostopia Platform
- •A) Differences between Windows only Hosting and the Hybrid System
- •B) Functional Components
- •C) Non Functional Components
- •9) Asp 3.0 iis 6 (Active Server Pages)
- •A) asp Third Party Components
- •B) Server.MapPath()
- •C) The #include Directive
- •D) asp Coding Examples
- •1. Asp dsn connection for ms access
- •2. Asp dsn connection for MySql
- •3. Asp dsNless Connection for ms access
- •4. Asp dsnLess Connection To a MySql Database
- •5. Asp dsNless connection for ms sql
- •6. Defining Paths
- •7. AspMail Sample Code for Components
- •8. AspUpload Sample Code for Components
- •9. Cdonts Sample Code for Components
- •11. Sa Fileup Sample Code for Components
- •A) Features in asp.Net 2.0
- •B) asp.Net codebehind and Precompiled dll
- •C) Coding Considerations:
- •D) asp.Net codebehind and dll File Explanation
- •D) asp.Net ajax
- •E) Supported asp.Net File Extensions
- •F) Unsupported asp.Net file extensions:
- •G) Retrieving asp.Net Error Messages
- •H) asp.Net Coding Examples
- •11) ColdFusion 5 a) About ColdFusion 5
- •B) ColdFusion Applications
- •C) ColdFusion Tags
- •D) Supported ColdFusion Tags
- •E) Unsupported ColdFusion Tags
- •F) ColdFusion Error Messages
- •G) Custom ColdFusion Tags
- •H) ColdFusion Coding Examples
- •12) ColdFusion mx 7
- •13) Payment Gateways
- •13) Ssl (Secure Socket Layer)
- •A) Security Certificates
- •B) Common Issues with Installing a Custom ssl Certificate.
- •C) Creating Symbolic Links aka Symlink
- •Cd name_of_symlink
- •Rm name_of_link
- •Cd name_of_symlink
- •14) Databases a) ms access (Microsoft Access)
- •B) ms sql (Microsoft sql)
- •C) MySql
- •Import the dump.Sql file into a database:
- •15) Common Issues for Tier 2 a) Email
- •I. How to read Email Headers; Check for delays and Time Zone Discrepancies
- •II. How to Convert to utc (gmt)
- •1) Find the Time and Convert to utc!
- •2) Find the delay!
- •III. Bigfoot Mail System
- •IV. How to Test if the inbox is Corrupt
- •B) Formmail
- •2) Create a Test Form.
- •3) Copy and Paste Code into Form Non Secure Site
- •4) Verify that there is a cgi-bin.
- •6) Test the form. C) Sub Domains
- •D) Common Ports
- •E) Permissions
- •E) RealServer
- •F) EasySiteWizard 7
- •G) htaccess directives
- •H) Serrahost ProStores
- •I) FaxWire
- •J) Bell dns Remaps
E) RealServer
RealServer is the software that streams RealMedia (RealAudio and RealVideo) over a network. You receive the media in real-time, and don't have to wait for the clip to download.
RealMedia is any media that is specifically created to be streamed from RealServer. RealAudio is an audio only streaming format. RealVideo is a video streaming format that includes both audio and video.
You can create RealAudio and RealVideo files with RealNetworks products. More information on obtaining and using RealNetworks products can be found at: http://www.realnetworks.com/products/
The RealPlayer client for viewing RealAudio and Real Video is available as a free download at: http://www.real.com/player/
Real.com main download and info site http://www.real.com
Real.com's support page http://service.real.com/
RealNetworks developer support http://www.realnetworks.com/devzone/
Shared Vs. Dedicated Streams
Shared RealVideo/RealAudio streams are a pool of streams shared between many users.
The streams are available on a first-come, first-served basis. It is difficult to determine the number of shared streams that a user can have access to since that depends on how many other people are accessing the streams.
Theoretically, the maximum number of shared streams available to a user is the number of streams in the pool. (This requires that only one user is accessing the shared pool of streams.)
A dedicated RealVideo/RealAudio stream is a stream that is guaranteed to be available to the user, unlike a shared stream. Dedicated streams must be purchased separately in order for you to access them. Streams are available for sale in units of five.
The bandwidth used by RealServer shared streams is applied to the monthly transfer limit.
http://help.websiteos.com/support/realmedia_shared_streams.htm
http://help.websiteos.com/support/realmedia_dedicated_streams.htm
Supported protocols
The RealServer supports three protocols.
RTSP: The Real Time Streaming Protocol (RTSP) is designed specifically for clips created and read with RealSystem G2 tools. It is an open standard protocol that supports SureStream files as well as SMIL, RealText and RealPix files.
PNA/PNM: The Progressive Networks Audio (PNA also known as PNM) protocol is designed and used with RealSystem versions 5.0 and earlier. RealServer supports PNA for compatibility with older versions of RealPlayer. PNA is a proprietary protocol.
HTTP: The Hyper Text Transport Protocol (HTTP) is used for meta files that point to RealServer content, and for HTML pages that are served by RealServer (such as RealSystem Administrator). It may also be used for delivering clips to clients that are located behind firewalls.
Choosing a Protocol
The protocol is determined by the type of media you are streaming and to some extent on the client's network configuration. Using the correct protocol ensures that the media will be streamed as quickly as possible. Using the wrong protocol can result in poor streaming quality.
RTSP is the best protocol for media created with RealSystem G2 tools. It supports many media styles and is open standard. Older (legacy) media developed with RealSystems 5.0 and earlier should use the PNA protocol. HTTP can be used if the client is located behind a firewall and cannot be reached by RTSP and PNA.
Making Your RealMedia Work on Your Website
You must upload your RealMedia files to your public directory. If you upload to a subdirectory of your public directory, the subdirectory must be reflected in the access URL.
The URL used to access your RealMedia files depends on the protocol being used.
Connecting to RealMedia files
The URL used to access a RealMedia file depends on the protocol being used:
Substitute "domain" with your domain in the form of "domain.tld" and "file.rm" with the name of your RealMedia file. If you place your RealMedia files in a subdirectory of public, the subdirectory must be reflected in the access URL. Example: If your domain is domain.tld, and you upload the file, yourvideo.rm to the directory /public/files, the URL for the file (using the RTSP protocol) must be: rtsp://www.domain.tld/domain.tld/files/yourvideo.rm
-
Protocol
URL
RTSP
rtsp://domain.tld/domain/file.rm
PNM
pnm://domain.tld/domain/file.rm
HTTP
http://domain.tld:8080/ramgen/file.rm
Server Side Configuration done by Technical Support
Shared RealMedia Streams require no configuration however dedicated RealMedia Streams require special setup on our servers.
Once the added service is enabled by the Sales Department, a ticket to Tier 2 must be created to properly setup the dedicated servers to accept the domain's streams.