EntireX 10.15 | Added, Removed, Deprecated, or Changed Items | Release 10.9
 
Release 10.9
Added Items
*Security Enhancements
*Broker Administration.EntireX Broker now supports SSL-encrypted JMX communication with authentication when you use the Broker Administration client (etbsrv).
*PKCS#12 Support.The SSL parameter trust_store specifies the file name of a PKCS#12 certificate store that needs a password for unlocking. This password is set by the new SSL parameter trust_passwd.
*Passphrases in CICS Scenarios.Passphrases are supported using CICS IPIC connections and CICS Socket Listener connections.
*Authorization Rule Enhancements.Authorization rules are now also supported by EntireX on platform z/OS. With new command REFRESH-RULES, currently active rules are replaced by new rules from section AUTHORIZATION-RULES of the broker attribute file.
*Increased Platform SupportEntireX now supports the following additional platforms:
*z/OS 2.6
*CICS 6.1
*Linux Red Hat 9 (Intel x86 only)
*Windows 11 and Windows Server 2022
*IMS version 15.2
*REST Enhancements
*CI/CD Scenarios.Creating or Updating Connections using the REST API has been simplified. This new feature is particularly useful with regards to automation of development processes.
*REST Inbound Scenarios.REST Clients calling COBOL or Natural: The Designer has been enhanced to allow easier extraction of COBOL or Natural sources and modeling to REST APIs without a request body. These REST APIs use the HTTP method GET and transfer their input parameters as URL parameters.
*EntireX Adapter Enhancements
*New Connection Type CICS IPIC.The EntireX Adapter has been enhanced with connections to CICS IPIC. This connection enables you to call CICS interface types Channel Container and DFHCOMMAREA programs without installing EntireX components on the mainframe (Zero Footprint).Use a Secure Autoinstalled IPIC Connection to check Passphrases, Passwords and PassTickets in the CICS back end.
*CICS Socket Listener Connections.CICS Socket Listener connections have been enhanced to support Passphrases in the CICS back end.
*Creating or Updating Connections using the REST API.Creating or updating connections using the REST API has been enhanced in the following areas:
*Sensitive DataHandling of sensitive data such as passwords/passphrases has been enhanced. We now strongly recommend using encryption inside a JSON document.
*Simplified REST APIsA new service is provided to create/update simplified REST APIs without a payload, just using the HTTP method GET.
*Enhanced CICS Support
*Calling CICS interface type Channel Container with Zero Footprint.Programs with CICS interface type Channel Container can be called without installing EntireX components on the mainframe (Zero Footprint) using
*CICS IPIC Connections with the EntireX Adapter for Integration Server scenarios
*RPC Server for CICS IPIC for RPC client scenarios
In addition to Channel Container, DFHCOMMAREA programs are also supported.
*CICS Socket Pool for Broker Stub CICSETB.The Socket Pool allows you to reuse TCP/IP socket connections across multiple Broker calls. Reusing sockets saves resources and speeds up Broker calls.
*Command Central Enhancements
*c-tree Configuration of EntireX Broker Persistent Store.You can now use Command Central to configure a persistent store of type c-tree. You can edit maximum size, page size, and path of the c-tree persistent store using the Command Central GUI or command line.
*Designer Enhancements
*API Modeling.The COBOL Mapping Editor and Natural Mapping Editor now support API modeling where group data items from the extracted source can be excluded in the extracted IDL (API), but the subordinated data items remain. This allows you to set IDL directions (IN, OUT) correctly, with the following advantages:
*Reduced payload, which means less traffic at runtime.
*The extracted API is simplified. For REST inbound scenarios, this means you can model the REST API more easily to simple HTTP GET methods without any input payload. With the GET method, REST clients transfer level-1 input parameters as simple URL parameters - there is no request body.
*XML Mapping Editor.In the XML Mapping Editor, the Fault Document generation has been aligned to the SOAP 1.1 specification, that is, the default value generation for faultActor is removed.
*XML Tester.The EntireX XML Tester supports EntireX parameters defined in WSDL corresponding with XMM or AAR. These parameters are added to the EntireX Parameters setting and can be used in a request document or as an HTTP header. The sample generation reflects this setting.
*Integration Server Wrapper Wizard.With the Integration Server Wrapper Wizard you can now create a new package in the package selection area of the pages Define Adapter Services for... and Define Adapter Listener for....
*EntireX RPC Server Enhancements
*New RPC Server for CICS IPIC.The EntireX RPC Server for CICS® IPIC allows standard RPC clients to communicate with CICS programs running on IBM CICS® without installing EntireX components on the mainframe (Zero Footprint). The CICS interface types Channel Container and DFHCOMMAREA are supported.Use a Secure Autoinstalled IPIC Connection to check Passphrases, Passwords and PassTickets in the CICS back end.
*RPC Server for CICS Socket Listener.The RPC Server for CICS Socket Listener has been enhanced to support Passphrases in the CICS back end.
*EntireX Broker Enhancements
*Stub Trace Enhancements.Broker stubs NATETB23 and NATETBZ now support trace.
*Other Changes and Enhancements
*z/OS Installation.Only the EXB load library requires APF authorization.
*ICU Support.EntireX Broker now supports ICU 63.2 on platforms z/OS, Linux and Windows.
*com-plete Stub COMETB.A member with the name DEFAULT in the EXAENV environment store may contain global variables valid for all users.
*Trace Utility under Windows.The EntireX Trace Utility is now started with traceutility.bat (formerly: exxtracutil.exe).
Removed Item
*z/VSE Batch Server Support.The Software AG Designer tools IDL Extractor for COBOL and COBOL Wrapper no longer support z/VSE Batch Server.(The EntireX RPC Server for z/VSE Batch was dropped in version 10.7.)
*RUN-MODE.Broker-specific attribute RUN-MODE is no longer supported.
Deprecated Item
*AS/400 Platform.EntireX will no longer support the AS/400 platform in a future version.
*COBOL CICS with DFHCOMMAREA Large Buffer Interface Server Programs.The programming model CICS with DFHCOMMAREA Large Buffer Interface for a COBOL CICS server will be dropped in a future version.For scenarios where CICS data is longer than 32K, use the programming model CICS with Channel Container Calling, an IBM CICS standard.
*SMA-based Installation.SMA-based installation will be retired in a future EntireX version. The new procedure-based installation will:
*allow non-SMA procedure-level installation
*provide a new simplified installation in addition
*exploit browser-based z/OSMF workflows
*address generational change issues
*align our version numbers with the webMethods Suite release again
*CentraSite.EntireX CentraSite Integration will no longer be supported in the next version of EntireX.
*UDDI Registry.The following functinality will no longer be supported in the next version of EntireX: -Registering a Web Service in a UDDI Registry. -Importing from a UDDI Registry with the IDL Extractor for WSDL.
*DCOM Wrapper.The EntireX DCOM Wrapper will no longer be supported in the next version.
*Broker ActiveX Control.EntireX Broker ActiveX Control will no longer be supported in the next version.
*Platform Consolidation - BS2000.Adabas and Natural are consolidating and streamlining platform support. With EntireX the platform BS2000 is affected by retirements.The final version to support BS2000 will be EntireX 10.3 with the following retirement schedule:
*BS2000 11.0 FTSEnd of Maintenance: Dec. 31, 2023End of Sustained Support: Dec. 31, 2024
*BS2000 10.0 FTSEnd of Maintenance: March 31, 2022End of Sustained Support: March 31, 2022
*SVM Files at runtime in RPC Servers.Support for server-side mapping files (SVM) in the EntireX RPC Servers for CICS ECI, IMS Connect, CICS, Batch and IMS, together with the Deployment Wizard, will be dropped in a future version.We strongly recommend using client-side server mapping files (CVM).
*Authorization Rules in LDAP Repository.Administering Authorization Rules using an LDAP Repository will no longer be supported from the next version. Use the Broker attribute file instead.
*Microsoft Visual Studio Wizard for EntireX .NET Wrapper.The .NET Wrapper Wizard will no longer be supported in the next version of EntireX.Note:The .NET Wrapper is still supported in the Software AG Designer.
Changed Items
*APF Authorization.APF authorization is no longer required for the EXX library under z/OS. This means that clients and servers no longer have to work with an authorized library.
*Authorization Rules.If section DEFAULTS=AUTHORIZATION-RULES is defined in the broker attribute file, this has precedence over other security settings:
*z/OSAttribute file settings take precedence over RACF and any authorization rules in RACF are ignored.
*Linux, WindowsAttribute file settings take precedence over LDAP and any authorization rules in the LDAP repository are ignored.
*XML Mapping Editor.In the XML Mapping Editor, the Fault Document generation has been aligned to the SOAP 1.1 specification, that is, the default value generation for faultActor is removed.
*EntireX LOAD Library.On z/OS, modules ETBFATTR and USRSEC have been moved from EXX109.MVSLOAD to EXB109.MVSLOAD.Alias BROKER31 and module BROKERZ are no longer needed and have been removed from EXX109.MVSLOAD.
*Worker Tasks.For broker attributes NUM-WORKER, WORKER-MAX, WORKER-MIN, the maximum number of worker tasks has been increased from 32 to 64.The check of the attributes has been simplified. Only WORKER-MIN greater than WORKER-MAX is rejected.
*Trace Utility under Windows.The EntireX Trace Utility is now started with traceutility.bat (formerly: exxtracutil.exe).
*Relocation of SAGTOKEN.In previous versions, the SAGTOKEN utility was delivered in the EXX load library. It is now delivered in the EXB load library.You may need to adapt your JCL scripts accordingly.
*Relocation of Executables.In previous versions, the following executables were delivered in the EXB load library:
*BCOC, BCOS
*ETBCMD, ETBINFO
*ETBNATTR
*EXXMSG
They are now delivered in the EXX load library. You may need to adapt your JCL scripts accordingly..