bildwelt
E2E FORUM
E2E Bridge E2E Commerce

E2E Developer News 2017 | 3

E2E Forum News E2E Developer News 2017 | 3

Tagged: 

This topic contains 0 replies, has 1 voice, and was last updated by  Kirstin 3 months, 1 week ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #2884

    Kirstin
    Keymaster

    A new maintenance release of the E2E BRIDGE has been released. With this edition of our E2E Developer Newsletter we inform you about the latest features and bug fixes of the E2E BRIDGE software components. As usual, you find all details in our release notes that are provided in our Online Documentation.

    New E2E Forum

    In our completely re-designed E2E Forum you have the opportunity to compare notes on E2E BRIDGE and to exchange experiences on everything around the topic of IT integration and EDI.

    The questions posed by other E2E BRIDGE users in particular can often result in input helpful for your own integration project. In addition, discussions with other users and IT developers offer you an opportunity to benefit from their experiences.

    End of Life Platforms

    This is the last release of E2E BRIDGE and RUNTIME for RedHat Enterprise Linux 5. Reason is end of production phase for RedHat Enterprise Linux 5 since March 31, 2017. Please upgrade to a newer RedHat version.

    This is also the last release of E2E BRIDGE and RUNTIME for Oracle Solaris x86. Please migrate to Linux or Windows.

    Compatibility Hints Concerning REST Support

    We hereby announce that the E2E REST Adapter and REST Service (see REST Adapter and REST Service) have now reached stable release status. As of this BRIDGE version we guaranty backwards compatibility.

    Please note the following restrictions for this release, if you use REST service or REST adapter:

    • services compiled with BUILDER 6.0.23 will only run on an E2E BRIDGE with RUNTIME 2017.5
    • services compiled with a BUILDER previous to 6.0.23 will not start on BRIDGE 6.0.61 with RUNTIME 2017.5

    Please use matching BRIDGE, RUNTIME and BUILDER versions and re-compile your services if necessary.

    The Release at a Glance

    E2E BRIDGE

    • 6.0.61
    • 5.1.61
    • both contain xUML RUNTIME 2017.5

    E2E BUILDER

    • 6.0.23 (64-bit only)
    • 5.1.23
    • both contain xUML RUNTIME 2017.5

    E2E ANALYZER

    • 6.0.23 (64-bit only)
    • 5.1.23

    E2E RUNTIME

    • 2017.5

    E2E RESTIFIER FOR SAP

    • 2.2.1

    New with this Release

    Rest Improvements

    The E2E REST Adapter and REST Service (see REST Adapter and REST Service) have now reached stable release status. As of this BRIDGE version we guaranty backwards compatibility.

    • External names for REST parametersUse this, if you want to access a REST service that has parameter names with special characters. In this case, set this name (e.g. ugly@parameter-name) to externalName and give a better name. So you do not have to escape the parameter every time you use it.


      See REST Adapter Reference > <<RESTParameter>> for more details.

    • Support for response headers in method signatureAs it is increasingly common to transfer meta information of e.g. query results, etc. in HTTP headers, we now support response headers as REST method output parameters.


      See Implementing REST Methods > Output: Header Parameter for more details.

    • Possibility to ignore HTTP response codes >= 400It’s quite often that a HTTP response >= 400 does not mean that the situation is exceptional, but merely a signal (like 404). Flag ignoreHTTPErrors now allows the modeler to ignore those errors and implement cleaner models. Default of this flag is true, absence of this flag will still be considered false.

      • With tagged value ignoreHTTPErrors set to true, no exception will be thrown upon HTTP status codes >= 400 given back by the REST service. You should read the httpStatus from the adapter response (as described on Getting the REST Adapter Response) and decide yourself, if any additional error treatment is needed.
      • With tagged value ignoreHTTPErrors set to false, the E2E Runtime will throw an exception for HTTP status codes >= 400. You can catch these exceptions directly after a REST Adapter call as described on Catching Errors and do some error handling.

      See REST Adapter Error Handling for more details.

    • Allow path segments to be marked as verbatim (as-is)

      If certain path segment contains special characters you don’t want to be URL-encoded, use option isVerbatimPath. This option will make the compiler process the variables, but doesn’t touch the path otherwise. The modeler himself will be responsible for the path to be encoded correctly, trimmed, etc.

      See REST Adapter Reference > <<REST>> for more details.

    • Support for segment composition for the REST AdapterSometimes the remote REST API is defined so that the variable segment must have a specific format, but only a part of it is really a variable, like e.g. /api/flights/date=2017-06-18/LAX-ZRH. This is not pure REST thinking, but nevertheless sometimes REST services you need to access may be implemented that way.
      Use path segmentation like date=:aDateVariable/... together with option isVerbatimPath to access those REST resources.

    BRIDGE API

    You now can read and update Node.js service configurations via the BRIDGE API.

    What’s New in Detail

    E2E BRIDGE 6.0.61

    • This BRIDGE version contains E2E xUML RUNTIME 2017.5 with SAPNW.
    • Features and Improvements
      • Bridge API 2.3.0: Read and update Node.js service configuration (config.json) (see E2E Bridge API).
    • Fixed
      • Error message “Object doesn’t exist.” if persistent state object is too big.
      • Custom UI is broken if HTML uses <base href=”…”>.
    • Other bug fixes and improvements (see E2E BRIDGE Release Notes).

    E2E RUNTIME 2017.5

    E2E BUILDER 6.0.23

    • This BUILDER version contains E2E xUML RUNTIME 2017.5 with SAPNW.
    • Features and Improvements
      • Compiler: Option to hide/mask passwords in service settings UI (E2EAttribute) (see setting() Macro and Attribute Specification > Initial Value).
      • Compiler: Java Callback Service: add ‘start’ and ‘stop’ hooks.
      • Importer: REST importer should generate REST parameters from header parameters.
      • Improved examples: REST, Memory Adapter, Settings, Persistent State Purchase Order.
    • Fixed
      • Compiler: REST ports exported from libraries lose all documentation and REST tag information.
      • Compiler: Scheduler cannot be exposed as library class.
      • Compiler: JMS Listener within Library does not work.
      • Compiler: Select distinct does not work together with a where clause.
    • Other bug fixes and improvements (see E2E BUILDER Release Notes).

    E2E ANALYZER 6.0.23

    • Fixed
      • Regression Test Tool: Reference data/test output data difference is not displayed in some cases.
      • Regression Test Tool: Test selection tree has lost colors.
      • Regression Test Tool: Test names are not properly escaped when passed to XPath.
      • Regression Test Tool: Sporadic failures when building and deploying using RegTestRunner from Jenkins.
    • Other bug fixes and improvements (see E2E ANALYZER Release Notes).

    E2E RESTIFIER FOR SAP 2.2.1

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.