Administration

This topic lists the Known Issues related to Administration.

Key Description
AMBW-37423 Summary: Post upgrade, too many unnecessary error messages are displayed while starting BWAgent.

Workaround: Remove the link file from the <BW_HOME>/<Old_Versions>/ext folder

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-31447 Summary: The Same .EAR file is uploaded in different folders without using the replace option in AS Enterprise Mode.

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-27440 Summary: In the DBEMS mode when you upgrade from ActiveMatrix BusinessWorks 6.3.1 to ActiveMatrix BusinessWorks 6.4.0 and restore Domain, the error, ERROR: null value in column "commandid" violates not-null constraint, is thrown.

Workaround: After upgrade, drop the old commandhistory table and run the new ActiveMatrix BusinessWorks 6.4.0 bundled script to create the commandhistory table and then restore the domain.

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.