Page Comparison

Follow the instructions below to add/edit an analytic script in WSO2 BAM:

...

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:

...

3. You can click 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 see Scheduling an Analytic Script.

5. The script will be redirected added to Available Scripts page where , where saved script are listed as show below.

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:

1. Go Navigate to <BAM_HOME>/repository/deployment/server/bam-toolbox folder / directory, and select the.tbox file you want to edit.
2. Open the .tbox file using any file archiving utility (e.g. , 7z).
3. Edit the script file in the toolbox according to your requirements. Scripts are saved inside the Analytics folder in the .tbox file.
4. Once the edits are done, archive the main folder again and simply change its extension to .tbox.
5. Save the edited .tbox file in the same bam-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:

1. Log in to the BAM management console, and click  List  in the Analytics  menu menu in the Main  menumenu.
   

2. Click Edit corresponding to the script you want to edit and as shown below. 
   

   InfoYou 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

3. Do required modifications to the existing script and save it in a new name.