Overview of the Web & Mobile Back Ends

The topics in this book explain how to configure web back ends, which provides the services and data required by PcVue Web & Mobile client applications, and instant messaging.

  • Core back end: Required to take advantage of any Web & Mobile client applications, including WebVue, Touchvue, SnapVue, the WebScheduler and Web Services Toolkit clients. It exposes the interface for core services such as authentication.
  • Geolocation back end: Required to take advantage of the geolocation and tracking features with SnapVue. It hosts the geolocation server.
  • Instant messaging back end: Required to take advantage of the Instant Messaging feature with SnapVue and the Messaging control in mimics. It hosts the Instant Messaging server.

Depending on your network architecture and the level of segmentation in place, back ends can be on the same computer as the IIS web server, or be hosted on another server.

For more information on how to deploy the Web Server, see the Deployment help book.

For more information on how to configure and use WebVue, see the WebVue help book.

For more information on how to configure and use the TouchVue mobile app, see the TouchVue help book.

For more information on how to configure and use the SnapVue mobile app, see the SnapVue help book.

Why do I need to configure a Core back end

The Core back end exposes the interface used by the IIS web server for the core services including authentication, real time data, alarms, historical data and graphic rendering.

A Core back end must be configured to use any of the Web & Mobile client applications.

When deploying the IIS web server with the Web Deployment Console, you will configure the endpoint of the Core back end so that the deployed web services can connect to the main PcVue process.

Why do I need to configure a Geolocation back end

The Geolocation back end exposes the interface used by the IIS web server and the main PcVue process for the geolocation and tracking services.

A Geolocation back end must be configured to use the geolocation and tracking features in SnapVue and in PcVue.

If a Geolocation back end is configured, the Geolocation server is launched at start-up on the station configured as producer. It runs as a child process of the main PcVue executable.

When deploying the IIS web server with the Web Deployment Console, you will configure the endpoint of the Geolocation back end so that the deployed geolocation and tracking web services can connect to the Geolocation server process.

Why do I need to configure an Instant Messaging back end

The Instant Messaging back end exposes the interface used by the IIS web server and the main PcVue process for the Instant Messaging services.

An Instant Messaging back end must be configured to use the instant messaging feature in SnapVue and in PcVue mimics.

If an Instant Messaging back end is configured, the Instant Messaging server is launched at start-up on the station configured as producer. It runs as a child process of the main PcVue executable.

When deploying the IIS web server with the Web Deployment Console, you will configure the endpoint of the Instant Messaging back end so that the deployed instant messaging web service can connect to the Instant Messaging server process.

While the Core and Geolocation back ends are only required if using Web & Mobile client applications, configuring an Instant Messaging back end is also required even if users only take advantage of the Instant Messaging via mimics in the desktop application.

Characteristics and file formats:

  • Text messages can have a maximum of 500 characters.
  • Attachments, irrespective of type, can be a maximum of 200 Mb.
  • Video recording (mobile apps only) is limited to a maximum of 30 seconds. Pre-recorded videos can be longer as long as they are less than 200 Mb.
  • Attached files are managed as follows.
    • .3gp, .aac, .wav, .mp3, .aiff are treated as audio (voice) messages.
    • .png, .jpg, .jpeg, .gif, .bmp are treated as images.
    • .mp4, .mov are treated as video.
    • Any other file extension has no special treatment and is downloaded.

The Instant Messaging is licensed. If it has not been license-enabled, it operates as if in trial mode.