When importing certificates into BusinessConnect or importing .csx files through the Administrator, the certificate import fails.  In the logs, the error may look like this: class com.tibco.ax.fw.impl.cm.CmKSHelper (in unnamed module @0l042f5b6fa) cannot access class sun.security.pkcs.PKCS7 (in module java.base) because module java.base does not export sun.security.pkcs.PKCS7 to unnamed module @0l042f5b6fa

all platforms

This is a known issue related to JDK 17 usage in TIBCO Administrator 5.13 with BusinessConnect 7.5 or BC 7.4 with HF4 installed.

You can resolve the issue by opening the $TIBCO_HOME/administrator/domain/<your domain name>/bin/tibcoadmin_<your domain name>.tra file and looking for this line:

java.extended.properties=-XX\:MaxMetaspaceSize\=128m --add-exports\=java.base/sun.security.ssl\=ALL-UNNAMED --add-exports\=java.base/com.sun.crypto.provider\=ALL-UNNAMED

Modify this line by appending this string to it:

--add-exports\=java.base/sun.security.x509\=ALL-UNNAMED --add-exports\=java.base/sun.security.pkcs\=ALL-UNNAMED

The final line should look like this:

java.extended.properties=-XX\:MaxMetaspaceSize\=128m --add-exports\=java.base/sun.security.ssl\=ALL-UNNAMED --add-exports\=java.base/com.sun.crypto.provider\=ALL-UNNAMED --add-exports\=java.base/sun.security.x509\=ALL-UNNAMED --add-exports\=java.base/sun.security.pkcs\=ALL-UNNAMED

Since you are running the Administrator as a Windows service, you will also have to make sure the updated in the Windows registry entry is updated with the corrected parameter above..

Restart the Administrator after making the change.

These extended properties are already incorporated into the BusinessConnect engine .tra files, so there is no need to modify them.

When importing certificate into BusinessConnect or importing .csx files, the certificate import fails.  T