Apama 10.3 | Apama Documentation | Building and Using Apama Dashboards | Dashboard Deployment | Preparing Dashboards for Deployment | Using the Deployment Configuration editor | Using the Dashboard Package wizard
Using the Dashboard Package wizard
The Dashboard Package tool, (which is on the Title bar/Toolbar) brings up a wizard that guides you through the process of generating a deployment package for specified configurations.
* To use the wizard
1. Click The Dashboard Package tool (which is on the Title bar/Toolbar) to start the wizard.
The Dashboard Selection screen appears.
2. In the Available Configurations section, use the check boxes to select one or more configurations on which to perform the specified operations and click Next. The Package Dashboard Configurations appears.
The Package Dashboard Configurations screen appears.
3. In the Package Location field, enter or browse to the path name of the directory into which you want Apama to place the generated deployment package. For local deployments, this is a directory that is accessible to end users.
If the desired final destination of the deployment package is not accessible to you, the deployment package can be installed by the dashboard administrator as part of the deployment process. See Deploying Dashboards.
4. Your deployment can include .jar files that define custom classes and functions used by your project's dashboards. The .jar files that are specified in Dashboard Properties (select Properties from Software AG Designer's Project menu) are automatically included in the generated deployment package. This screen allows you to direct Apama to sign .jar files before including them in the deployment package.
Click the Default button, to specify the keystore shipped with Apama (%APAMA_HOME%\etc\DashboardKeystore). Use the default unless you require a custom keystore. If you require a custom keystore, use the following fields:
*Signature file text field: Enter the full path name of (or click Browse... and navigate to) the keystore to use for singing .jar files. Leave this field empty to skip signing the .jar files.
*Alias text field: Enter the private key to be used to sign the .jar files. If you are using the keystore shipped with Apama, click the Default button (which specifies the alias dashboard).
*Password text field: Enter the password for the private key specified in the Alias text field. Or click the default button for default Alias/Password being used for the DashboardKeystore.
5. Click Finish.
The operations are performed and then the Dashboard package/deploy/publish summary appears. The summary indicates which operations succeeded for which configurations. A green check mark indicates success. A red x indicates failure.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.