Engage Stryker Adapter

Release Notes - Version 1.0.102

Updated: April 16, 2021

About Engage Stryker Adapter

The Engage Stryker Adapter provides the ability to receive alarms generated by Stryker smart beds, such as the Secure II line of beds. The beds report to a Stryker iBed Gateway server which in turn makes the alarms and other data the beds generate available for access via update subscriptions. The Engage Stryker Adapter subscribes to these notifications and generates Engage alerts based on the adapter's configuration and reported alarms.

What's New

This section summarizes the new features in this release.

What's New in Engage Stryker Adapter 1.0.102 SR1

The Engage Stryker Adapter 1.0.102 SR1 solution provides the following new features:

This is a maintenance release only that introduces no new features.

What's New in Engage Stryker Adapter 1.0.101

The Engage Stryker Adapter 1.0.101 solution provides the following new features:

The adapter has been re-built for compatability with Platform 5.5.

What's New in Engage Stryker Adapter 1.0

The Engage Stryker Adapter 1.0 (1.0.7) solution is the initial release of this adapter.

What's Fixed

This section provides information about fixes and improvements made to the Engage Stryker Adapter product.

What's Fixed in the Engage Stryker Adapter 1.0.102 SR1 Release

The following issues are fixed in Engage Stryker Adapter 1.0.102 SR1:

When the Stryker adapter attempts to subscribe a new bed, the "Unknown Request" reponse now triggers a re-try attempt. (ADP-6365)

What's Fixed in the Engage Stryker Adapter 1.0.101 Release

The following issues are fixed in Engage Stryker Adapter 1.0.101:

NONE

What's Fixed in the Engage Stryker Adapter 1.0 Release

The following issues are fixed in Engage Stryker Adapter 1.0 (1.0.7):

NONE

Known Issues

This section provides information about known product defects and limitations in the current release.

Installing the Engage Stryker Adapter generates a java.lang.IllegalStateException: Unable to retrieve EntityManagerFactory for unitName stryker. (PFM-9074)

Workaround: Restart extension-glassfish.service after installing extension-stryker-interface rpm.