Shop Floor Connect / DNC Connect / 3rd Party Integration / Mcenter Service Release 2610

The new Shop Floor Connect, DNC Connect, 3rd Party Integration, API, MMR Service version 2610 is released and now available. Please look below for the enhancements and changes of the different modules.

The release is now available to all customers with a maintenance contract in our new helpdesk. Please register on the following page. You will then receive confirmation of your access. You can then submit support requests and download the releases. All customers who do not yet have access to our helpdesk and want to download the software, please request access via the following link.

Please send an email to service@aplusb-solutions.com if you want the release on a data medium. Direct Siemens PLM Software customers can get the release from the GTAC download area.

This Shop Floor Connect Release 2610 supports all Teamcenter UA versions from 12.x up to the actual version Teamcenter 2606.

Urgent Service notes

  • DNC Connect only supports the actual NX versions who are under maintenance from Siemens.
  • For customers who want to update on the Teamcenter 11.3 version or higher: From TC 11.3 and on, a new license verification will be done upon the creation of manufacturing objects like MEProcess, MEOP, MEWorkArea and their sub-types (including custom types). This check will be done on server side per Teamcenter policy and to ensure license verification. It will use two new feature keys: 1) mfg_planning_lite for verifying MEProcess, MEOP and their sub-types 2) mfg_plant_author for verifying MEWorkArea and its sub-types.
    This new license check will be done in addition to other license verification that exists today. If you don't find them in your Teamcenter 11.3 or higher license key please get in contact with Siemens Digital Industries Software.

SFC/DNC Connect/3rd Party Integration/Mcenter Service

Shop Floor Connect

Enhancements

  • ActiveDNC: Support for Czech language.
  • ActiveDNC: The configuration of the TCSS connection is now managed in the SFCAdmin and no longer in the local configuration file. Existing entries may need to be transferred manually after the update.
  • SFCAdmin: The MTC server management page has been redesigned. In the previous version, no more than 101 servers could be entered. The list of servers is now scrollable. The automatic pagination of the table has been removed.
  • SFCAdmin: Ability to configure the access data of the technical SFC user of a TcX 2606 cloud environment.
  • SFCAdmin: Teamcenter connection (including TCSS and TcX cloud connection) is now configured in the SFCAdmin and no longer in the configuration files. Existing entries are transferred to the SFCAdmin after the update (as far as this is possible). After the update, the entries should be reviewed once.
  • Core: Updating the used Teamcenter SOA client package to version 2506.

Bugfixes/Changes

  • ActiveDNC: If the item ID of a workplace contains spaces, the new implementation to query the assigned MTC in SFC 2607 ended it with an error. This problem has been fixed.
  • ActiveDNC: If SFC was installed in a path with spaces in the path name, the internal JT viewer could not be opened and an error message was displayed. This problem has been resolved.
  • WebClient: The Apache Velocity framework used has been updated from version 1.7 to 2.4.1. Through this update, any existing customer-specific templates must be checked and adjusted. This applies above all to the loop counter '$velocityCount' used so far - this must be replaced by '$foreach.count'. See also the note in the README file.
  • Setup: The used Apache Ant Library has been updated to version 1.10.18.
  • Upgrade internal Tomcat to version 9.0.123.
  • Common: Update Jackson library to version 2.21.8.
  • SFCAdmin: The configuration page for managing the MTC instances of an MTC server has been revised. If too many MTC servers are created, the previous tab-based view became confusing. The list of MTCS servers is now displayed as a list on the left.
  • SFCCore/SFCAdmin: The email configuration now additionally supports 'StartTLS'. Furthermore, the generation of debug outputs can be activated for troubleshooting and a test e-mail can be generated directly from the configuration page.
  • SFCCore: Bugfixing in the classification filter 'removeUnimportantTPs'.
    SFCCore: Bugfixing in the classification filter 'sortTPsByAdjust'.
  • SFCCore: Bugfixing in the classification filter 'combineTPs'.
  • SFCCore: Bugfixing in the ?RemoveEmptyTPs? classification filter.
  • FCCore: The availability check when loading MENCMachining Revisions now outputs additional log messages in the TRACE level when accessing the parts list. For this, the following logger must be adjusted in 'ShopFloorConnectwebappsSOAPWrapperWEB-INFclasseslogback.xml':
    <logger name="com.aplusb.tcdnc" level="TRACE"/>

Announcements

  • General: Starting with Release 2901, the internally used Tomcat will be upgraded to version 10 or 11. Until this upgrade takes place, Tomcat version 9.0 or 9.1 (as soon as it becomes available) will continue to be used.
  • API: The SOAP API currently available will be supplemented by a REST API starting with the next release. The REST API will provide as many of the functions used to date as possible, but with different data types (JSON-based). External components that use the SFC SOAP API should be migrated in the coming years!
  • API: With the upgrade of the internal Apache Tomcat from version 9 to 10 (or 11) in Release 2901, the SOAP API will no longer be available as of that date. The SOAP API uses an encoding that is no longer supported by newer implementations and will therefore not be migrated. Externally connected systems or programs that use the SFC SOAP API must be migrated to the new REST API by 2028.

MI-Server

Enhancements

  • Update Apache Tomcat to version 9.0.120.

Mcenter Service

Enhancements

  • MFG MMR: It is now possible to change the status of the last current NcRevision in Mcenter via a workflow from Teamcenter.
  • MFG MMR: The owner group of the generated upload dataset can be changed to the group of the workpackage to which the dataset was imported.

Bugfixes/Changes

  • MRL MMR: Updating a tool component or complete tool can fail if the generated PATCH operation must copy existing values from a cutting edge. This problem has been resolved.
  • MRL MMR: The mapping for component 'TC_HOLDER_20_00_900' has been changed from 'DIN4000-089_504' to 'DIN4000-089'. The update will not change the active configuration files. This adjustment must be entered by hand in the file 'MRL2MMR.mapping.component.classes.properties'.
  • MRL_MMR: If the bills of materials are to be exported from Teamcenter in a packed format (Teamcenter preference ?PSEAutoPackPref=1?), the quantity of individual components was not previously evaluated. Now, the BOMLine attribute ?bl_quantity? is also evaluated and set as the quantity in the Mcenter bill of materials for the tool components.
  • MRL MMR: The order of the attributes for "ToolClassV2.CuttingEdgeDefinitionV2.CuttingEdgeGeometryV2.A1" has been adjusted in the default mapping configuration. This change must be adjusted by hand in the active configuration file after an update.

Announcments

  • Siemens has placed the Mcenter software – specifically the MMR/P and MMR/T modules relevant to the 3rd Party Integration Mcenter Service – into maintenance mode. This means that no further relevant developments will take place and only bugs will be fixed. For us and the 3rd Party Integration Mcenter Service, this means that it too will be placed in maintenance mode, and no further relevant developments will take place; only bugs will be fixed.

 

Subject to change without notice!