Follow the instructions below to add/edit an analytic script in WSO2 BAM:
Adding an analytic script
1. Log on to the BAM Management Console and click Analytics on the Add menu of the Main menu. That will open the Script Editor window.
2. Provide a script name and add the required HiveQL script in the editor pane as shown below:
Note
For information on writing HiveQL scripts, see https://cwiki.apache.org/confluence/display/Hive/LanguageManual.
3. You can click Run to execute the script and view results. The results appear in the panel below the script editor as shown in the screenshot below.
4. Click Save to save the script. Click No in the pop up dialog box if it is not required to schedule the script immediately. Else click Yes to schedule the script before saving. For more information on scheduling, refer to section Scheduling an Analytic Script .
5. The script will be redirected to Available Scripts page where saved script are listed.
Editing an analytic script
There are two ways to edit an analytic script as follows:
Editing scripts installed with toolboxes
Follow the instructions below to edit a script that came with a BAM toolbox:
- Go to
<BAM_HOME>/repository/deployment/server/bam-toolbox
folder and select the.tbox
file you want to edit. - Open the
.tbox
file using any file archiving utility (e.g., 7z). - Edit the script file in the toolbox according to your requirements. Scripts are saved inside
Analytics
folder in the.tbox
file. - Once the edits are done, archive the main folder again and simply change its extension to
.tbox
. - Save the edited
.tbo
x file in the samebam-toolbox
folder mentioned above and restart the server.
Editing scripts added manually
If you have already installed BAM, you can change analytics scripts that are manually added, using the management console as follows:
- Log in to the BAM management console and click List in the Analytics menu in the Main menu.
Click Edit corresponding to the script you want to edit and as shown below.
You cannot use the management console to edit a script after it is deployed. The only way to do this through the UI is, by duplicating the old script and renaming it
- Do required modifications to the existing script and save it in a new name.