Hi Diethmar - the doc is here - https://www.novell.com/documentation/secure-messaging-gateway24.3/secure-messaging-gateway/data/bookinfo.html

Pam

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 ...

I feel the same way, I found this

hub.docker.com/.../web

and this one


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

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

Great, Rob. Let's create a knowledgebase article!

SMG documentation has not been refreshed for some time

Can you have a look at https://portal.microfocus.com/s/article/KM000032172 as i added some additional info, let me know if anything is missing

Rob, I think this document is still in a protected area ...

my bad... forgot one checkbox 

I am also writing up a seperate article about "debugging" the scans from 3rd party scanners, such as GroupWise-Web towards SMG.

In short to get "verbose output" of requests and responses and see if there is "any activity", the following steps can be helpful.

Debugging SMG Scan Requests from External Scannners.

In order to check external scan requests, you can do the following.

1. Switch to the Folder "/opt/opentext/smg/smg-supervisor/http/api/1/" in your SMG System.
2. Open up the file "mimescan.php" to edit.
3. Adjust the "$SaveRequest = false;" value in Line 6 so it reads "$SaveRequest = true;"

The file should look like this after saving.
       // Set SaveRequest to TRUE to write the request and response files in the SaveRequestPath.
        // Set SaveRequestPath to a valid path on the apache server with proper rights in order to save request and response files for debugging issues
        // Set SaveFilenameFormat to the datetime format string you want to use for the debugging files
        $SaveRequest = true;
        if ( $SaveRequest )
        {
                $SaveRequestPath = './debug/';
                $SaveFilenameFormat = 'Md_His_u';
                $RequestTimeMicroTime = microtime( true );
                $micro = sprintf( "%06d",( $RequestTimeMicroTime - floor( $RequestTimeMicroTime ) ) * 1000000 );
                $dt = new DateTime( date( 'Y-m-d H:i:s.'.$micro, $RequestTimeMicroTime ) );
                $RequestSaveFilename = $dt->format( $SaveFilenameFormat );
        }

4. Make sure that a debug-folder exists in that folder.
You can use "§ mkdir debug" to create it. and give it the right permissions. "§ chown smg:smg ./debug".

Now when a request goes in,
you SHOULD see "3 Files" in that debug folder, which are created.
A mime.822-File, which is the actual message-content,
a directive.xml-File which contains information about the scan-request
and a response.xml-file which contains the scan-response towards the external scanner


Example List of files:
-rw-r--r-- 1 wwwrun www    557 Jul 19 09:15 Jul19_091528_483417_directive.xml
-rw-r--r-- 1 wwwrun www  29922 Jul 19 09:15 Jul19_091528_483417_mime.822
-rw-r--r-- 1 wwwrun www    508 Jul 19 09:15 Jul19_091528_483417_response.xml

In the response file, you also get more verbose information which "event" caused the scan to fail.
A rule of thumb is, "if you see a requests going in / creating these files", you SHOULD see a message-scan in your SMG-Scanner log.


In one single-command, this will enable the debugging option.

cd '/vastorage/smg/smg-supervisor/http/api/1/' && mkdir debug &&chown smg:smg ./debug && sed -i 's/\$SaveRequest = false;/\$SaveRequest = true;/g' mimescan.php