Category: Uncategorized

There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition, Version 6 SR16FP7 that is used by IBM Notes and Domino. These issues were disclosed as part of the IBM Java SDK updates in October 2015. They are fixed as part of IBM® SDK Java™ Technology Edition, Version 6 SR16FP15.

See the security bulletim here

Uncategorized

A compressed file of your Liberty profile containing a server runtime environment, server configuration, and applications can be created using the included packaging wizard. Because a Liberty profile server is lightweight, it is useful to package up applications and the server in a compressed file. You can then store this package, distribute it to colleagues, use it to deploy the application to a different location or to another machine.

To package your Liberty profile environment:

  1. Stop the server.
  2. Right-click your Liberty profile server, and select Utilities > Package Server.
  3. In the Archive field on the Package Server panel, type a filename and path for your archive package, or click Browse to locate a filename and path. This filename can include a full path name.
  4. In the Include field, select one of these options, depending on what you want in your packaged file:
    • All server content, which includes binary files
    • Only server configuration and applications
  5. Click Finish

Uncategorized

A smart host is a directory server to which SMTP-routed messages are sent when the message recipient cannot be found in the IBM® Lotus® Domino® Directory or other secondary directories configured on the server.

Typically, a smart host is used in organizations that employ multiple mail systems within a single Internet domain. Users on these systems may not be in the Domino Directory. For example, if some users are on a UNIX® sendmail system but their inbound messages are routed through the Domino mail system, you can set up a smart host to ensure proper address resolution.

Last week i need to setup a kind of odd routing.  I need to relay messages sent to Domino users to an Smart Host.  This routing is odd because the users exist on Domino Directory with the same smtp domain.

On the person document set mailsystem to Other Internet Mail and Internet Address and Forward Address to the same address like [email protected]

Configure the Smart Host on the server configuration document

 

Uncategorized

Congratulations to all IBM Champions Class 2016. Since the first 50 i was a member of this group.

I will be back! 🙂

Complete list here

Uncategorized

To change the log language:

Create the file  jvm.options on <install root>/etc/

Add the parameter -Duser.language=en (for english).

Restart the Liberty Server.

Uncategorized

I setup my IBM Connecitons integration with Sametime Proxy 9.  The Connections server SSL is made using a self certificate.

Uncategorized

For a long time i used Domino Blog template, since version 7.0.2.   I moved the blog to WordPress  this weekend.

The migration process was not so beautifull. I just read the blog posts using a feed reader and then import into WordPress.

I had some problems, related to WordPress security plugin, but now almost everything is ok.

 

Uncategorized

Today a customer ask why his IBM Connections is not sending notifications and recent upddates is not working anymore.

I got the SystemOut.log and see the following:

[10/1/15 11:20:15:201 BRT] 000001e2 JMSPublisher E com.ibm.lconn.events.internal.publish.impl.JMSPublisher publishEvent CLFWY0148E: Could not obtain an event connection
[10/1/15 11:20:15:201 BRT] 000001e2 LocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "publishEvent" on bean "BeanId(Communities#lc.events.publish.jar#EventPublisher, null)". Exception data: com.ibm.lconn.events.internal.invoke.async.AsyncEventInvokerException: CLFWY0148E: Could not obtain an event connection
at com.ibm.lconn.events.internal.publish.impl.JMSPublisher.publishEvent(JMSPublisher.java:200)
at com.ibm.lconn.events.internal.publish.impl.JMSPublisher.publishEvent(JMSPublisher.java:164)


The problem: The message engine was not working (started).

To solve the problem:

1 - Shutdown the Connections nodes
2- Clear some files on the disk

/data/shared/messageStores//log/Log
/data/shared/messageStores//store/PermanentStore
/data/shared/messageStores//store/TemporaryStore

(Delete only the files but not the directories)

Restart the servers

Uncategorized

IBM's internal testing on iOS 9.x devices has shown that the iOS 9.x native Calendar app may remove some repeating Domino calendar entries from the mobile device.

See this  technote

Uncategorized

From CF07, you can manually syndicate by using the following methods:

Update
  • This method syndicates items that are newer than the previous syndication. Items that are newer than the last syndication on the syndicator are sent to the subscriber. Items that are newer on the subscriber are not updated. Items that are created on the subscriber that do not exist on the syndicator are not removed from the subscriber.
Rebuild

This method syndicates all items that are newer on the syndicator. All items that are newer on the syndicator are sent to the subscriber. Items that are newer on the subscriber are not updated. Items that are created on the subscriber that do not exist on the syndicator are not removed from the subscriber.
Rebuild with mirror

If you select the mirror option, all items on the subscriber are reset to mirror the syndicator. All items that are newer on the syndicator are sent to the subscriber. Items that are newer on the subscriber are overwritten with the older version from the syndicator. Items that are created on the subscriber that do not exist on the syndicator are removed from the subscriber. Version history is not syndicated.

Uncategorized

Uncategorized

In IBM Notes/Domino 9.0.1 FixPack 4 and in releases containing the fix for SPR#MKEE9TKDEM, you may see an error page with the following error message:

CLFAD0382E: The databaseName URL parameter value is not one of the allowed database names. The parameter is &databaseName=otherserver!!app.nsf.

The allowed names are configured in the option xsp.data.domino.param.databaseName.whitelist.
There has been a change in the XPages default behavior, that now requires that the allowable databaseNames be configured in a whitelist. The white list is an option that lists allowed databaseNames. Where the whitelist has not been configured, the error above will occur for remote applications (i.e., applications that are not on the current server). There is an option to revert to the previous behavior but there are security implications associated with that decision.

Read all information here

Uncategorized