IBM Connections – WAS Plugin issue

If you get an HTTP 404 Error in a browser, after trying to access an IBM Connections Application and errors like

“File does not exist: E:/IBM/HTTPServer/htdocs/profiles”

start popping out in “error.log” file of the IBM HTTP Server, then most probably there is an issue with WAS Plugin.

I had this error just after the Installation of IBM Connections and the reason was the incorrect value of “WebSpherePluginConfig” variable, which contains the path to the “plugin-cfg.xml” file in the HTTP Server configuration. After the value was corrected and a correct path was supplied, IBM Connections could be accessed without any issue.

Advertisements

Domino Mail Routing – A tip about Global Domain documents

Some time ago we had a request from a customer to make sure that the incoming SMTP mails, for a specific internet domain, are routed only to users who have Internet Address with this exact internet domain set in their Person Document.

The Domino Router task behavior, at that point was the following (extremely simplified):

  1. Router gets an E-Mail over SMTP for intended recipient john.doe@acme.com.
  2. Router searches the “names.nsf” for the recipient.
  3. Finds john.doe@acme-marketing.tv and delivers the mail to this user.

There was one Domino Global Domain document in the “names.nsf” with a lot of alternate internet domain aliases. So, this would mean that if the primary domain is “acme.com” and an alternate internet domain “acme-marketing.tv”, your users would be receive e-mails addressed with alternate domain even though they do not have it specified in their Domino Person document.

For one specific Internet Domain, this was not a way to go. The solution for this was quite simple, we needed to create a new Global Domain document with this Internet Domain specified as a Primary Internet Domain and remove the same domain from the first (“old”) Global Domain Document. This prevents the Domino Router task from looking up this Domain as Alias, thus making sure the E-Mails addressed with this domain are only routed to users who have this domain specified in their Person document.

After a new Global Domain document is created and you are satisfied with the config, restart the Domino Router task, to make sure that the change is picked up by the Router task.

This behavior is described, in detail, in the following article.

https://www.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/conf_specifyinghowdominolooksuptherecipientsofincoming_t.html