+49 (30) 467086-20 service@microtool.de
Products » objectiF RM » Collaboration » Set up collaboration

Version 8.0 and higher

Set up collaboration

Starting with version 8.0, you can use the Collaboration functions, which allow you to conduct live chats and video conferences directly in objectiF RM. In order to use these functions optimally, you need a valid certificate and you must set up SignalR and Node.js for the web service.

Certificates

If you have installed objectiF RM Server and the Client or Web Service (Web Client) on one computer, you will need a valid certificate that is not self-signed. If objectiF RM Server and the client or web service (web client) are installed on different computers, you will need an additional certificate which is also not self-signed. For this case, it is recommended to set up SignalR and Node.js where the web service is installed.

Self signed certificates

It is recommended not to use self-signed certificates because they are considered untrustworthy. You can use self-signed certificates for testing purposes. If you want to use self-signed certificates, install it on (each of) the computer on which objectiF RM Client/ Web Client is installed. The location of the certificate store is LocalMachine. Install the certificate under Trusted Certificates.

Hint
Note that current browser versions no longer accept self-signed certificates created in IIS. Alternatively, you can use Open SSL to create a self-signed certificate.

Import certificate

If you have a valid certificate, you still need to deposit it in Internet Information Services (IIS).

  1. Open the IIS Manager.
  2. Select the machine (top entry) on the left and double-click to open the Server Certificates.
  1. Select Import on the right side.
  1. Click on the […]  button to select the certificate, enter a configured password and select Webhosting as the certificate store.
  2. Confirm with OK.
  1. Now select the WebSite in IIS and open its configuration by clicking Bindings.
  2. In the following dialog click on Add.
  3. Use the dropdown to specify https under Type and enter a free port.
Hint
Especially if video conferences are to take place via the web client, https must be set under Type. If this is not the case, the browser cannot access the input media (camera and microphone).
  1. Now select the WebSite in IIS and open its configuration by clicking Bindings.
  1. Then start the web service by clicking Restart under Manage Server on the right.
Set up SignalR 

With the SignalR server configuration, chat messages and invitations to video conferences are transmitted immediately.

  1. Open the Service Manager of a web service and go to the configuration of the service for which you want to configure collaboration.
  1. Switch to the SignalR tab and check the SignalR option there. The SignalR address field is unlocked.
  2. In the SignalR address field, enter any free port after the host name following a colon.
  1. Select the Use HTTPS check box if you want to use the collaboration features in the web client as well.
  2. Under Thumbprint of the certificate, specify the value of the thumbprint (certificate for the SignalRServer).
Hint
If the web service (web client) and the application server (objectiF RPM Server) are installed on different computers, enter the thumbprint of the certificate that applies to the application server under Thumbprint of certificate.
  1. Click Initialize SignalR. The SignalR server is set up with the specified configuration. The port is released and the address is reserved. A message indicates whether SignalR has been set up.
Set up Node.js

If you want to do video conferencing, you need to set up Node.js. This is true even if you have already installed Node.js using the extension features.

  1. In the Service Manager, switch to the Collaboration tab.

  2. Click the Initialize Node.js button. Wait until you get a message that the Collaboration server has been set up.

  3. Select the Collaboration server (Node.js) option.

  4. In the Address field, enter the address where you want the Node.js server to be accessible. It starts with https:// and is followed by the computer name.

  5. In the Port field, enter the port at which the Node.js server should be reachable.

  1. Enter the required Certificate settings under Certificate::
    • StoreLocation Enter here the location of the certificate store where the certificate is installed.
    • StoreName Enter here the name of the certificate store where the certificate is located.
    • FindValue Specify here the value of the certificate attribute to be searched for. The value of the attribute depends on which certificate attribute you have selected. If you have already set up the SignalR server, it is recommended to use the thumbprint of the certificate as the value. Copy the value from the SignalR tab.
    • x509FindType Specify the attribute of the certificate to search for.
  1. Click the Test configuration button to see if the settings are correct.
Hint
If you do not have sufficient access to the certificate, you may get an error message so that some properties cannot be queried. In this case, save your changes and restart the Service Manager with administration rights. You can then run the test again.