GW24.3 and SMG integration - where is the documentation?

It is really fine to have a GW24.3 web client integration to SMG.

But how to do? Yes, there are a few lines in GroupWise 24.3 documentation. But no explanation to get the SMG application key.

On the other side I have not detected any hint how to configure SMG! There are some more steps necessary to prepare a successful integration.


Use "Verified Answers" if your problem/issue has been solved!

Parents Reply
  • 0   in reply to 

    Sorry Pam. But I do not find any chapter for the web client. Yes, there is one for 3rd party but in a very, very common way ...

    I am not sure if someone is able to make it run. Fortunately I have access to the beta corner where discussion will help and lead to the right end point; but that's me ...


    Use "Verified Answers" if your problem/issue has been solved!

Children
  • 0   in reply to   

    I feel the same way, I found this

    hub.docker.com/.../web

    and this one


    www.novell.com/.../gwweb_smg.html

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

  • Verified Answer

    +1   in reply to   

    this is the basic config in both SMG under the Manage 3rd Party Applications and GW under the SMG tab in Groupwise Web, the application key gets created in SMG when you create an 3rd Party Applications and you copy/paste this to GW. 

    The certificate you import in GW should be the same as the one used in SMG 

    then run once the GW web config and the info is pulled down to the local docker server in /opt/novell/gw adding the smg.conf with this info 

    # Format: server <smg Address>:<smg Port>;
    # Example: server gwdva-100.lab.com:8301;
    
    server smg.robvk.com:443;


    In the SMG directory the smg.json having the info needed to make GW web use SMG with this info 

    {
    "enabled":true,
    "smgApi":"https://smg.robvk.com:443/api/1/mimescan.xml?appkey=",
    "name":"SMG SYSTEM DEFAULT",
    "id":"SMG.SMG SYSTEM DEFAULT",
    "ipAddress":"smg.robvk.com",
    "ipPort":443,
    "processWithoutAccess":true
    }



    Starting the docker container when SMG does not have a commercial certificate needs the additional option-e SMG_SSL_VERIFY=off

    When GW web connected to the SMG server this info will be added in SMG on the page of the 3rd party application