======================================================================================================================================== INUBIT 7.4 ======================================================================================================================================== Contents: - Installation - Migration of an existing system - Notes for operators of the inubit software as appliance - Known incompatibilities - Announcements of discontinuation -------------------------------------------------------------------------------------------------------------------------------------- INSTALLATION -------------------------------------------------------------------------------------------------------------------------------------- NOTE: You can find the supported hardware platforms, operating systems, databases, web browsers, and portals in the Installation Guide: https://files.virtimo.net/Userportal/Inubit/7.4/Docs/online-help/en/index.htm#Installation.SystemRequirements.html NOTE: To open the context-sensitive inubit online help in the inubit Workbench using Google Chrome you need to add the following option to the Chrome call in the inubit application profile: --allow-file-access-from-files Refer to: - https://files.virtimo.net/Userportal/Inubit/7.4/Docs/online-help/en/index.htm#Configuration.ApplicationProfiles.html - https://files.virtimo.net/Userportal/Inubit/7.4/Docs/online-help/en/index.htm#features_online_help.html 1. Preparation: Read the Installation Guide carefully: https://files.virtimo.net/Userportal/Inubit/7.4/Docs/online-help/en/index.htm#installation_guide.html 2. Installation: Execute the setup file that is appropriate for your operating system to start the installation. -FO Converter: Along with many improvements for creating PDF files using Apache FOP 2.3, there is an incompatibility with previous versions of Apache FOP: If there is an empty element in the XSLT style sheet, the layout of the PDF file differs as the new version 2.3 of FOP does not consider empty blocks. To resolve this issue, add a element to each section so that it is no longer an empty element, e.g. as follows: For other changes, please refer to the Apache FOP 2.3 history of changes: https://xmlgraphics.apache.org/fop/2.3/changes_2.3.html -------------------------------------------------------------------------------------------------------------------------------------- MIGRATION OF AN EXISTING SYSTEM -------------------------------------------------------------------------------------------------------------------------------------- You can find detailed migration instructions in the Virtimo User Portal at https://files.virtimo.net/Userportal/index_en.html. Refer to: https://files.virtimo.net/Userportal/Inubit/7.4/Docs/online-help/en/index.htm#Migration_Guide.html If you have any questions concerning the migration, please contact Virtimo support: - Phone: +49 30 555 744 044 - Support system: https://support.virtimo.de -------------------------------------------------------------------------------------------------------------------------------------- NOTES FOR OPERATORS OF INUBIT SOFTWARE AS APPLIANCE -------------------------------------------------------------------------------------------------------------------------------------- Do not update appliance versions yourself! Please contact the Virtimo AG. -------------------------------------------------------------------------------------------------------------------------------------- KNOWN INCOMPATIBILITIES AGAINST INUBIT 7.1 AND BELOW -------------------------------------------------------------------------------------------------------------------------------------- - Variable mappings with a password variable or a password module property as mapping source and with a mapping target that contains an XPath now cause an error if the server configuration property "RestrictedPasswordPropertyAccess" is set to "true", which has been the default since inubit 6.0. As of inubit 6.0, it is impossible to create these mappings. If there are workflows using these mappings (created in an earlier inubit version), these workflows have to be adapted so that on the mapping source side a variable of type "is:maskedString" is used. -------------------------------------------------------------------------------------------------------------------------------------- KNOWN INCOMPATIBILITIES AGAINST INUBIT 7.3 -------------------------------------------------------------------------------------------------------------------------------------- - The REST interface authentication has been changed. The user should add either the "userType=processEngineUser" or "userType=processUser" parameter in the request to authenticate against the Process Engine User or the Process User. By default, requests will be authenticated against the Process User if process user is configured, else against process engine user. requests will be authenticated against the Process User if the "userType" parameter is not set. - File Connector: New sorting capabilities have been added; by default, items are sorted in ascending order. - Configuration Panel: Validations have been added for some configuration properties so that invalid entries can no longer be entered. - Process Data Logger: Only XPath 2.0 is available, XPath 1.0 cannot be used in this utility anymore. - REST Interface: Restricting access to USER REST API (http://:/ibis/rest/user/*) based on user role. - Process Engine users: Users with System Administrator roles are authorized. - Liferay/IM users: Users with Administrator roles are authorized. - LDAP users: LDAP users, which are imported to inubit and have System Administrator roles, are authorized. - Adaptations: Use users with authorized role or add authorized role to the user. - Workbench: - The "Windows" menu has been removed, as its functionality was redundant. - Adaptations: Use the panel tabs to navigate to different windows. - In the inubit Workbench configuration dialog (File > Settings), sections have been consolidated and partly rephrased. - "Miscellaneous" folder has been renamed to "Caching and Performance". - "Editor" folder has been renamed to "Editor options". - "Auto Save" and "Auto Refresh" folders have been deleted and the options "Auto save artifacts", "Auto save interval", and "Workbench auto refresh interval" have been moved to "Caching and Performance". - Folders "XPath Assistant", "XSLT auto save", and "Auto Complete" have been deleted and the options "Custom functions (list of Java classes)", "Save source and target files in the Process Engine", and "Auto Complete", were moved to "Editor options". - Technical Workflows and BPEL diagrams neither can be deleted nor published, as long as a Module Editor dialog is open. A warning message is provided saying that before deleting/publishing Technical Workflows and BPEL diagrams all Module Editor dialogs must be closed. - Other diagrams can be deleted or published even if a Module Editor dialog is open. - Help Menu is changed: - The former "Online help" menu item is renamed to "Help" and it is linked to the local HTML help. - The new "Online help" menu item is added which is linked to the online documentation. - Both the "Overview System Connectors" and "Online Version check" menu items are removed from the Help menu. - The new "User portal" menu item is added which is linked to the "Bosch Software Innovations User Portal". - CLI/User Management: CLI login has been restricted to "System Administrator" only. Other user roles can be given the distinct permission to access CLI by a new "CLI Login Access" setting in user roles "Miscellaneous Rights". - User Management: The former permission "Edit" is restricted and is now complemented by distinct rights to "create" and "delete". - Monitoring: In the Queue Manager context menu, the "Delete Process" item is deactivated on entries with status "Retry". - Designer: - Displaying tooltips when moving mouse over in the global search text has been truncated to 100 characters. - Adaptations: If a tooltip of a variable is longer than 100 characters, navigate to variable window in order to read it in full. - Moving of modules between user groups has been restricted to provide more data integrity: In module editor, module should be moved from child to parent user group. However, in the reverse case, validations should be done to check if the module is used in workflows by any other user/user group. If a workflow is found under target's user/user group, the module cannot be moved. In addition, if there is any other user other than target's children where in the workflow is present, then module cannot be moved. - User/User group name cannot be renamed to existing names by changing the case to avoid naming conflicts. - Workflows cannot have the same name for diagram and group. Otherwise, the error message "Group name cannot be same as diagram name" is displayed. - If a workflow, which has the same value for diagram name and group name, is migrated from lower versions of inubit to inubit 7.4, the name validation does not happen until the user edits the workflow properties. When editing the Workflow properties and clicking the "Next" button in the workflow wizard, the error message "Group name cannot be same as diagram name" is displayed. - JRE: inubit is no longer shipped with JRE/JVM. - Adaptations: JAVA 11 or OpenJDK 11 must be installed on the system and JAVA_HOME variable must be set accordingly prior to inubit setup. - Import/Export/Deployment: - If multiple diagrams and modules from multiple user resp. user groups are to be imported or deployed, the target user or user group will be analog to the source user or user group (if they exist). Otherwise, they will be imported/deployed to selected user or user group. - Adaptations: This behavior needs to be considered for automated import/deployment where multiple diagrams and modules from different user groups are included. - The check of imported files has been refined to avoid the import of e.g. a *.user.zip instead of *.diagram.zip. This is restricted and an error is displayed. - Adaptations: This may need to be adapted, e.g. in automation of importing artifacts where the formerly tolerant handling of importing was effective. - The handling of activation state of workflows has been changed. Now, as there is a selection possible to either activate or deactivate all workflows during import, the latter is no longer the default. If new workflows are imported to the system, they will have the activation state as set in the import file. - Make sure to select either "Activate" or "Deactivate" if you need this activation state after the import. - LDAP Connector: - When using secured connection (ldaps), after a JDK upgrade the "No subject alternative names present" error occurs. - Adaptations: Hostname or IP address should be added under SAN category in the certificate. - AS2 Connector: - The MDN report has been extended with the following values and therefore the order in the report has been changed: - MDN-From - MDN-To - MDN-Message-ID - MDN-Message-Date -------------------------------------------------------------------------------------------------------------------------------------- KNOWN ISSUES -------------------------------------------------------------------------------------------------------------------------------------- - Workbench: - Concatenated strings (e.g. file paths) that become longer than 255 characters may cause issues in schedulers and web application submits. - Workaround: Try to limit names to reasonable length for files, workflows, modules, etc. - Workbench icons and fonts look blurry. - Workaround: Go to "Display Settings". Reduce the scaling size to 100%. The icons will look normal but the size of the workbench looks smaller. - TCP/IP Connector: The maximum number of TCP/IP connections is restricted up to 30. Please make sure that not more than 30 connections to inubit BPM are opened. Otherwise, this data will get lost. Up to maximum TCP/IP connections, processing entries are visible in Queue Manager tab. - Offline Modelling: - Cryptographer Module: Encoding types are not available for HMAC Algorithm, because it uses the Process Engine?s key encoding. - Process Data Logger: Table details are not editable (Logging Target: Table cannot be found without server connection). - General module properties: On the "General module properties" wizard page, both the Input drop-down list and the Output drop-down list are empty. - CP850 & CP437 encoding will not be available when working offline because this is checked with Process Engine encoding. - When Process Engine is restarting, the workbench is detecting this, however, idles for the duration of the Process Engine startup. - Instant messages are not displayed in offline mode. - In Offline mode, module properties will be only be available for modules, which have been already opened once in online mode, (e.g. using "Show properties" option). - In some cases pointer turns to hourglass temporarily impeding flawless working on workbench. - Global search: Currently, multiple language settings are not supported and additional language terms will not be found. - Import and Export BPMN: - General: - Message artifact where initiating has been deselected must be checked, as this does not represent a BPMN attribute. - Choreography Task and Call Choreography Activity elements are not differentiated in BPMN. - Export BPMN: - Events with different event definitions are adopted as default elements. - Image and Black Box Pool elements are not supported by BPMN and will not be exported. - If a diagram has been imported containing a Lane without Pool, it can be exported as it has been imported. - Import BPMN: - The "isExecutable" variable is set to the value "false" by default. - If a sub-process does not contain child elements, the boundary elements are not displayed. - Links between message flow and elements of sub-process are not adopted. - If there is a lane without a pool in the diagram to be imported, it will not be displayed. - Message elements, which are linked to ta Choreography participant, should be checked after import. - Call Activity elements should be checked after import. - The XSLT converter removes the CR from the CRLF combination when parsing the input message. This is due to dom4j.jar's internal parsing process, which is recommended by W3C. - Global variables: - Global variable usage cannot be tracked if a global variable is used in the settings for the following modules: - Data Converter: Complex Lookup Table, Lookup Table, Task Generator - Utilities: Process Data Logger - FTP Connector: The remote file chooser works for FTP protocol only, and it is disabled for both the SFTP protocol and the FTPS protocol, which can be used as before. In addition, the remote file chooser is enabled for Linux and Windows 7. For Windows 10, the remote file chooser is disabled for all the protocols. - MongoDB Connector: The existing MongoDB Connector modules will have QueryType values such as "Find_All" or "Find_using_filter". If inubit has been patched from 7.4.0.13 or below versions to the latest, the values will be shown as "FindAll" or "FindUsingFilter" for newly created modules. Even for existing MongoDB Connector modules, the configured module property values are displayed and the modules work as expected. However, the module property values will be changed once the module is opened and saved in the module wizard - DB Connector: - When using the type "call" in a Database Connector query, the attribute "queryId" is ignored. If a "SELECT" query is executed prior to this call, the previous "queryId" is used instead. Therefore, a parallel call of two StoredProcedures/Functions does not work correctly because resultSets cannot be allocated. - EDI Adapter: - As of inubit BPM 7.0, the EDI Adapter requires plain text as input message. Processing messages in other formats might fail. -------------------------------------------------------------------------------------------------------------------------------------- ANNOUNCEMENTS OF DISCONTINUATION AS OF INUBIT 7.4 -------------------------------------------------------------------------------------------------------------------------------------- - AS1 Connector - Baan Connector - Exchange Connector - GAEB Adapter - ITA Connector - JAAS Connector - MSMQ Connector - OFTP Connector - RFID Connector - ICR Connector - Solaris support - 32-bit installer (Linux, Windows) - Liferay 6.x support