Class EssAiReadiness

java.lang.Object
com.appliedolap.essbase.EssAiReadiness

public final class EssAiReadiness extends Object
Why a cube's AI features will or won't work, worked out before calling one of them.

Every AI capability sits on top of the same chain of setup, and the server reports a break anywhere in that chain with one indiscriminate message - HTTP 400 "Unable to get associated AI connection for application [Sample]" - whether nobody has ever configured generative AI on the server, or a connection exists and this application simply isn't pointed at it. Those need opposite responses from whoever is reading the error, so this walks the chain and says which link is missing.

A readiness check is diagnostic and never throws: a failure to reach the server is itself a result (EssAiReadiness.State.UNDETERMINED, carrying the cause).