Administration
This topic lists the Known Issues related to Administration.
| Key | Description |
|---|---|
| AMBW-49047 | Summary: HTTPS AppNode fails to start on the remote machine.
Workaround: Change the keystore path location in the AppNode's |
| BWCE-5592 | Summary: Unable to add Activity execution stats on PCF environment.
Workaround: None |
| AMBW-47153 | Summary: Monitoring-related error occurs in bwagent console\logs after enabling process monitoring and running the agent in DEBUG Mode.
Workaround: None |
| AMBW-46059 |
Summary: The application properties are not displayed in the Internet Explorer browser. Workaround: Use any other web browser such as Google Chrome, Firefox, or Microsoft Edge. |
| AMBW-44868 | Summary: The bwadmin --help command still shows help for the upgrade command that is not supported in this release.Workaround: None |
| AMBW-44826 |
Summary: When OpenTelemetry is enabled or disabled via Admin UI or Admin CLI, in pertaining debug level log, Workaround: None |
| AMBW-41955 | Summary: If an AppNode log is not present and you click the
Download Log button from Admin UI, an exception is thrown.
Workaround: Start an AppNode and try again |
| AMBW-41795 | Summary: When agent is started with MySQL 8.x jar, a harmless message about the driver being deprecated is displayed on bwagent and the bwadmin console.
Workaround: None |
| AMBW-41794 | Summary: A harmless warning is shown when starting a BWAgent.
Workaround: None |
| AMBW-41555 | Summary: The
Appnodeconfig button is not available under the Appnode Data view.
Workaround: Navigate to any other page within an AppNode and then navigate to appnode config. |
| AMBW-37468 | Summary: Harmless logs are shown at Admin Console on SUSE 12 Linux.
Workaround: None |
| AMBW-32929 | Summary: Process monitoring statistics are not populated if checkpoint has been used in the process.
Workaround: None |
| AMBW-32922 | Summary: On Process Monitoring page, Job filter displays results for records on the current page only.
Workaround: None |
| AMBW-32904 | Summary: Sometimes all the transitions are not highlighted and input/output data is not seen for activities when process monitoring is enabled using UDP transport.
Workaround: Use FTL transport for process monitoring. |
| AMBW-32594 | Summary: On the Process Monitoring page, the Datetime value in the MM/DD/YYYY format for filtering jobs does not work.
Workaround: Use the datetime value as displayed in the database |
| AMBW-32071 | Summary: Failed to Upload Large EAR file larger than 10MB with MariaDB.
Workaround: Use any other database. |
| AMBW-32057 | Summary: Agent Count is getting increased for AppSpace after restoring Domain.
Workaround: None |
| AMBW-31832 | Summary: In the process diagram view of Process Monitoring, if a constructor block includes a catch block, then it is not highlighted after its execution.
Workaround: None |
| AMBW-31831 | Summary: In Process Monitoring, sometimes, because of uid issue references are not highlighted and input or output data might not displayed.
Workaround: Remove all uid related warnings from TIBCO Business Studio™ for BusinessWorks™. Create an EAR file. Deploy the EAR file, and then enable process monitoring. |
| AMBW-31600 | Summary: When an application is running and AppNode is restarted, the job id is duplicated and two jobs with same id is present under process monitoring.
Workaround: None |
| AMBW-31493 | Summary: User is getting considered as Role in file based authorization.
Workaround: None |
| AMBW-30759 | Summary: Failed to get AppNode
Config.ini file's property details by REST API.
Workaround: None |
| AMBW-30398 |
Summary: Unable to register BWAgent from the command line on some machines. Workaround: None |
| AMBW-29846 |
Summary: Process diagrams are not visible on the Admin UI when the project name has a period (.) between the numbers. Workaround: Remove the number from the process package name, regenerate the EAR file, and re-deploy it. |
| AMBW-29725 | Summary: The Internal Server Error is displayed intermittently in logs when there is a change in the network.
Workaround: None |
| AMBW-29632 | Summary: Process diagram is not shown in TIBCO® Enterprise Administrator when the
TIBCO ActiveMatrix BusinessWorks™ process package name contains number.
For example com.tibco.bw.service.SIXXXZZZ.1.0 Workaround: None |
| AMBW-29235 |
Summary: When application components are started or stopped multiple times from the Admin UI, the TIBCO-BW-TEAAGENT-500506: Failed to get components for Application error is sometimes displayed. Workaround: Refresh the entire page or navigate to different tab, for example, the AppNodes or AppSpaces page and then go back to the Components tab. |
| AMBW-28244 | Summary: Admin UI shows wrong information under
Installation tab after upgrade.
Workaround: None. |
| AMBW-27654 |
Summary: Identity-Truststore is not created for the SSL Client post migration. Workaround: After migrating the SSL enabled service , it will create the SSL client resource. In SSL client resource, provide the keystore provider resource in Keystore Provider as Trust Store. Provide the Keystore only. This will import all the certificates required for SSL enabled services in ActiveMatrix BusinessWorks™ 6x. |
| AMBW-26286 | Summary: Unable to upload large sized EAR files (~10 MB) when the DB2 database is used for the DBEMS or DBFTL mode.
Workaround: None |
| AMBW-25889 | Summary: From the command line, users can enable the OSGi and create a new AppNode on the same OSGi port.
Workaround: Use the Admin UI to enable the OSGi port. |