Topics: |
Patches are cumulative, and as such, include content from all prior cumulative patches. Installing the latest cumulative patch installs the newly resolved issues and all fixes from prior patches for version 3.15.
Certified Editions:
Certified DBs:
If you require this patch for a database environment not listed above, contact iWay Customer Support for assistance. You are advised to move to the latest available release of the product, or at a minimum, to the latest available patch for the product and your environment. This enables iWay to quickly provide support and issue resolutions, in addition to you benefitting from the latest updates in the product.
java –jar omnigen-patch-patch-3.15-cumulative.33.jar
Topics: |
This section describes the key features in Omni-Gen Version 3.15 Cumulative Patch 1.
To cut down on disk clutter, the retention policy for the OGC Tomcat access log can now be set to the number of days the logs should be retained.
The following table lists the issues that are resolved in Omni-Gen Version 3.15 Cumulative Patch 1.
Jira Ticket |
Summary |
---|---|
OG-6908 |
Allow OmniAPI role to execute Get a Master. |
OG-7314 |
Server Swagger API authentication shows 401 for primary/ibi user. |
OG-7368 |
API server call POST /api/v1/server/cdc/subscribe/loopback Loopback Test fails with ERROR 400 "Required request body is missing:". |
OG-7369 |
New install: Omni-Gen Console shows Unable to determine management port. |
OG-7401 |
OGC Tomcat localhost access log polls for OmniDomain and /ogc/health. |
OG-7402 |
java.io.FileNotFoundException when installing 3.15 patch 1. |
OG-7412 |
Server Swagger API authentication shows 401 for primary/omniapi user. |