Configuration Artifact

The Configuration artifact is one of the most important artifacts in the Saxbi repository and Saxbi will not operate without it. Below is an example of a Configuration artifact:

  &lt;!-- The fields below are used to setup the Saxbi built-in management ID. This ID is used to perform administrative functions, as well as to provide a       user that can be used with the Saxbi server before an authentication provider (see below) is established. --&gt; admin password &lt;!-- Use the authenticationProvider element to specify the artifact ID that maps out a connection to your Essbase EDS or APS server. You must have an        appropriate artifact with the given name uploaded to the Saxbi repository. Uncomment the below line to indicate that the mapped server is to be used to authenticate users (in addition to the built-in admin/password.    --&gt;    &lt;!--    authentication-provider-essbase     --&gt; 

As you can see, there isn't much to it. The configuration artifact has a class of com.saxifrages.stellaris.application.StellarisConfiguration and must be named configuration in the artifact repository. For those that are managing the artifacts with consistent filenames in a secure location on the client side, it would be in a file named configuration.xml. The configuration format allows for the specification of an admin username and password (see the adminUsername and adminPassword elements). This is a built-in user that can administer Saxbi. This is important because if the underlying authentication provider cannot be contacted or needs to be configured, there is still a native user that can administer Saxbi.

Also, at the moment, users in the underlying authentication provider cannot be granted admin roles so the built-in administrator ID must be used to manage artifacts in the Saxbi repository.

The last field that may be configured in the Configuration artifact is the authenticationProvider. The authentication provider element must contain the artifact name (in this case the artifact ID is authentication-provider-essbase) of an artifact that is an authentication provider. In this case the authentication provider is presumably an Essbase authentication provider.

This is all the information that the configuration artifact needs in order to function properly.