PowerConnect for SAP Solutions
Auto Light Dark
Auto Light Dark

PowerConnect Java 9.2.1 Release Notes

Overview

PowerConnect for Java 9.2.1 release.
For SAP Business Objects and Data Services Systems install the war package.

Added

  • Data Services job runs can now be reported once when they start and once when
    they finish, rather than on every poll for as long as they run
    (ds_job_monitoring_changed_only, default on).

  • Trace log collection now has three settings instead of two - off, failed runs
    only, or all completed runs (ds_job_monitoring_trace_logs), with a matching
    control on the DS Jobs configuration page.

  • Error log collection can be disabled (ds_job_monitoring_error_logs, default on).

  • Per-log entry caps, so a single oversized job log cannot exhaust heap
    (ds_job_monitoring_max_error_log_entries, ..._max_trace_log_entries,
    ..._max_monitor_log_entries). Where a log is shortened the job event carries
    error_log_truncated / trace_log_truncated / monitor_log_truncated and the
    agent log names the run, so a shortened log is never presented as complete.

  • An optional cap on HTTP response size for inbound calls
    (http_client_input_max_body) and the ability to disable response compression
    (http_client_input_compression).

Changed

  • The agent acquires one Data Services session per poll instead of revalidating
    before every call, roughly halving the number of requests made to the Job Server.

  • Logs are no longer requested for job runs that have not finished, since no final
    log exists for them.

  • Data Services only: response compression is now off and a 20 MB response cap
    applies, so an oversized SOAP response is rejected rather than decompressed into
    heap.

  • Stopping the agent no longer pings Data Services before logging out, and no
    longer retries the logout. Previously an unreachable Job Server could delay
    shutdown by up to 98 seconds; it is now bounded by a single request timeout.

  • Added embedded user store for authentication of PC UI for Data Services and Business Objects

Fixed

  • Job runs whose status arrived as Failed, Error or any other casing had their
    error log skipped; only an exact lowercase error was recognised.

  • A null pointer exception when session validation returned no response, which
    could cost a repository one polling cycle.

  • The one poll per year that spans the end of daylight saving time is now skipped
    rather than issued with a time range that runs backwards.

Upgrade notes

  • Expect job event volume to fall sharply. Data Services returns a job in
    response to any query overlapping the period it was running, so a long-running
    job was previously reported once per poll for its whole duration. It is now
    reported at start and at finish. The size of the reduction depends on how long
    jobs run relative to the polling interval; where jobs run for hours it is
    substantial. Set ds_job_monitoring_changed_only=false to restore the previous
    behaviour.

  • Job runs that never record an end time are no longer reported repeatedly.
    If a system leaves runs in that state, they will be reported once and then
    ignored. This should be investigated at the Data Services end, as those runs are
    returned by every query indefinitely.

  • Trace log settings carry over unchanged. true and false keep their
    meaning; error is the new third value. An earlier agent reading error treats
    it as off.

  • Responses from Data Services are now uncompressed on the wire, which increases
    network volume between the agent and the Job Server while reducing peak memory
    in the Tomcat JVM.