JBOSS - FATAL: The Appian data source cannot be reached.

Do you have a user/password set up in mysql and have you configured the ds-security in standalone.xml?

Yes.

I got fed up enough to make the password "password" so I could confirm the hash directly against the documentation.

And I did command prompt connection to MySQL to confirm that the password works.

Make sure any appian-mysql.ds.xml.failed or any other marker files are removed from standalone/deployments folder before starting up. Upload a full server.log if you can

2022.server.log

I've got the furthest I've ever gotten before.

Short answer:  When the documentation tells you to download the most recent MySQL J Connector , don't do it!  They're lying.  You need to get 5.1.46.  The newest one doesn't even have a 8.0.0.11-bin.jar file.  You'll think OK, I should just use the .jar file they do have.  No, that's why I've been struggling for a week!

Now I can actually connect to the database.  It doesn't complain about drivers anymore.

Now, there's something weird going on with AccentText, whatever that is.

ERROR com.appiancorp.type.config.xsd.XsdImporter - Error when importing type 'www.appian.com/.../2009. XSD: <xs:complexType name="AccentText">

Anyone have any idea how I'm constantly unable to import "Accent Text" on jboss startup? This is a local install on Windows 10 machine. Everything else I would think has to be working for me to be getting as far as trying to load AccentText. Why would it be crashing on a consistent basis?

This Accent Text error is keeping jboss from successfully deploying. So far it's never successfully deployed.