Installing a Scenario Authority
To install your authorization customization, do both of the following:
Replace "
com.apama.dashboard.security.DefaultScenarioAuthority" with the fully qualified name of your class in the file
EXTENSIONS.ini, which is in the
lib directory of your Apama installation.
Create a
jar file that contains your
IScenarioAuthority implementation, and add the
jar or its directory to
APAMA_DASHBOARD_CLASSPATH (changes to this environment variable are picked up by dashboard processes only at process startup) or else add the
jar or its directory to the list of
External Dependencies in your project's
Dashboard Properties (In
Software AG Designer, right click on your project and select
Properties, expand
Apama, select
Dashboard Properties, activate the
External Dependencies tab, and click the
Add External button). You can also use the
--dashboardExtraJars jarFiles command line argument to specify this
jar file.
If your scenario authority has dependencies on other .jar files, add these .jar files to the manifest of the scenario authority .jar file.
Software AG Designer allows you to sign your
.jar files when you create a deployment package. See
Preparing Dashboards for Deployment.
If you are installing NoOpScenarioAuthority, you do not need to create a jar file as described above, as this class is provided with your Apama installation and is included in an existing jar.
The EXTENSIONS.ini specifies the scenario authority to use. This file identifies all the user supplied extension classes (including functions and commands). Here is a sample EXTENSIONS.ini:
function com.apama.dashboard.sample.SampleFunctionLibrary
command com.apama.dashboard.sample.SampleCommandLibrary
scenarioAuthority com.apama.dashboard.sample.SampleScenarioAuthority
This file installs a function library, a command library, and a Scenario authority.
If multiple authorities are specified, a user must be authorized by each.