IBM Verse On-Premises V1.0.4 brings enhanced extensibility, increased offline mail support, and third-party file repository support

Today IBM/HCL announced some new features coming in IBM VoP 1.0.4, which will be available on August 14th, 2018:

  • Easy access to your files repository directly from a mail message when storing or choosing attachments
  • Capability to accept an invite directly from the calendar pop-up window
  • Extended offline mail limits, with capability to synchronize up to 30 days of mail
  • Navigation bar and attachment management customization options

You´ll need the following software requirements:

  • Red Hat Enterprise Linux® and Windows™ Server 64-bit systems are supported.
  • IBM® Domino® V9.01, Feature Pack 9, or later
  • IBM Connections™ V5.5, or later

You can read the full announcement here: VoP104 announcement

Advertisements

New license options for IBM Domino Applications on Cloud ( DAC )

Yesterday IBM published a new Software announcement including new options about licensing IBM Domino Applications on Cloud.

The complete announcement can be accessed here.

Overview of the announcement:

IBM® Domino® Applications on Cloud is a subscription-based service that offers an IBM-hosted solution for Domino Applications on IBM Cloud™. The service offers robust performance and high availability for mission-critical applications. The solution is offered as a managed service and can help reduce the cost, complexity, and risk of managing your own infrastructure.

Benefits of IBM Domino Applications on Cloud:

  • Improved economics. Reduce capital expenditure that is related to hardware, hardware maintenance, and hardware refreshes; and further reduce operating expenses that are related to internal resource costs and costs related to system down time.
  • Re-deploy skills on new growth initiatives. With the managed cloud infrastructure, your organization can worry less about in-house infrastructure maintenance, thereby freeing up skills and resources to drive new growth initiatives.
  • Improved agility. Your business benefits from the flexibility and scalability offered by IBM cloud infrastructure and the pay-as-you-go pricing model that can grow and shrink according to your needs.

Domino Applications on Cloud enhanced capabilities include two new Non-BYOL (Bring Your Own License) subscription editions along with add-ons such as development or replica environment, additional storage, and two labor service editions to help your organization migrate to the cloud.

New services include:

  • An Entry edition that no longer requires clients to carry a requisite on-premises license entitlement. This edition is designed for smaller application needs.
  • A Standard edition that no longer requires clients to carry a requisite on-premises license entitlement. This edition can grow to larger enterprise requirements. The Standard edition also provides the following optional add-ons:
    • Replica application instances for clustering needs
    • Development application instance
    • Additional storage for an application instance

Labor services:

  • Cloud Migration Advisory Services engagement provides expert guidance to accelerate the client’s environment move to Domino Applications on Cloud (DAC).
  • Cloud Migration Fast Track Services engagement provides access to IBM experts who can help clients analyze, remediate, and move up to 10 Domino applications to their Domino Applications on Cloud (DAC) environment.

Apache Reverse Proxy / http>https Redirect with multiple IP addresses

Yesterday I had the issue, that I configured 3 NIC´s for an Apache Reverse Proxy, but only for one IP the redirect for http >> https worked.

I did some investigation and found out, that the entry “HWADDR” with the corresponding MAC address was missing in the additional NIC configuration for “eth1”, “eth2” and “eth3”. So I added the information in the ifcfg-eth1, … file and restarted the network services and also the httpd service.

But >> did not work at all… 😦

Today I did some further investigation and figured out the problem: checking, which IP is listening on port 80 I received the following information:

[root@ibmpxy.company.com sites-available]# netstat -an | grep “:80”
tcp 0 0 172.18.0.15:80 0.0.0.0:* LISTEN

This was the IP address of eth0… But why did the Apache server not listen on port 80 for the additional IP addresses bound to the other NIC´s ??

The problem was located in the httpd.conf:

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
Listen 172.18.0.15:80

Only eth0 was listed in here !! After adding the additional IP addresses

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
Listen 172.18.0.9:80
Listen 172.18.0.10:80
Listen 172.18.0.15:80

and restarting the httpd service, it looked much better:

[root@ibmpxy.company.com conf]# netstat -an | grep “:80”
tcp 0 0 172.18.0.15:80 0.0.0.0:* LISTEN
tcp 0 0 172.18.0.10:80 0.0.0.0:* LISTEN
tcp 0 0 172.18.0.9:80 0.0.0.0:* LISTEN

And now the redirection of http >> https also is working for the other connect requests with a simple configuration:

<VirtualHost 172.18.0.10:80>
ServerName connect.company.com

ErrorLog /var/www/virtual/logs/connect.company.com_error.log
CustomLog /var/www/virtual/logs/connect.company.com_access.log common

# Redirect all requests to SSL
Redirect permanent / https://connect.company.com/

</VirtualHost>

Restore of “DAOSified” mail databases

Some weeks ago I had the issue to restore a mail database in a cluster environment for which DAOS was enabled. I took the following steps:

1. Disable replication on the Mail-/Home server of the user

2. Delete the replica on the cluster server

3. Restore the database on the cluster server

4. Enter the following command on the cluster server tell daosmgr listnlo -o missing.txt MISSING mail/databasename.nsf

5. lo updall mail/databasename.nsf -RX

6. Reenable the replication on the Mail-/Home server of the user

 
If the database cannot be opened on the Cluster Server, you can run the following commands:

> lo fixup mail/databasename.nsf -F

> lo updall mail/databasename.nsf -RX