This table presents a list of various properties that can be set on the BJN_CLIENT object before including embed.js.
|content||No||String||ID of HTML DOM element in which to create the meeting. If not provided, the content is added inline with a document.writeln.|
|meetingId||Yes||String||Blue Jeans meeting ID|
|pin||No||String||Moderator pin or attendee pin for the meeting. If no pin, then do not include property.|
|name||No||String||Name of the user joining. If not provided, user will be prompted.|
|No||String||Email address of the user joining.|
|width||No||String||Used to define the width of the IFRAME for the meeting. Treated as a string so % can be used. Default is 100%.|
|height||No||String||Used to define the height of the IFRAME for the meeting. Treated as a string so % can be used. Default is 600 pixels.|
|onJoin||No||Function||Provide a function that will be called upon launch of the meeting.|
This table presents a list of various properties that are set on BJN_CLIENT for you. They are normally to be read in cases where you might need to inspect the setup.
|version||Integer||A version number for the embed.js script. This may help in backwards-compatability in the future.|
|protocol||String||Set to "http:" or "https:" based on where embed.js was loaded from.|
|hostname||String||The hostname that embed.js was loaded from.|
It is helpful to place an HTML ID on the script include named "bjn-embed". This is used by the embed.js to detect the hostname used for situations where your implementation is running on different Blue Jeans partitions (production, beta, etc).
When launching a Blue Jeans meeting, there are various parameters that can be set to customize the experience. The embed.js script will setup a variety of these parameters in according to values set on the BJN_CLIENT object. If you are using the embed.js option, these query parameters are not used directly as embed.js will handle them for you. However, some implementations may need further customizations so this is provided a reference.
|embed||Boolean||True signals Blue Jeans to use the embedded user interface, which removes branded headers and footers from the page.|
|fullscreen||Boolean||True signals the meeting client to utilize the full width and height that is has been allocated in its parent window/frame.|
|name||String||The name of the user joining the meeting.|
|String||The email address of the user joining the meeting.|
Depending on your use case, you may not want the <script> tag to automatically start your meeting. One such situation is when you have a list of meeting and you may want a user to choose one before proceeding. In this case, you may use a special query parameter to the script called "defer". This will keep the <script> from starting the meeting.
<script id="bjn-embed" src="http://bluejeans.com/static/js/embed.js?defer=true"></script>
After using the defer tag, you will need to start the meeting when ready. To do that, you can call functions that have been added to BJN_CLIENT:
|launch()||callback function||Launches the meeting in a new tab with id "bluejeans". This is an option if you do not want to embed the meeting into your page, but a separate window.|
|load()||callback function||Launches the meeting inside your prescribed content area configured in BJN_CLIENT.|
A sample implementation demonstrating the pieces working together.